Demo project — fictitious code, with the engine’s reading on every stage and no model drafts or test runs. Nothing you do here is saved. A demo run is never signed. No signed run, no audit pack and no export comes out of this screen — a signature says a named account analysed a named source, and none of that happened here.Nothing here counts against your five free analyses: the demo is the same for every account, and what you change lives in this browser only.Try an example or your own code

AnalyzeDesignTransformationDocumentationTestingEconomicsDelivery

Next: Analyze — Reads the code and signs a run — every other figure starts here. The other tools need a signed run first.

What the marks mean:donestartedout of date

DemoRead from the code

Demo · Z_MM_PO_APPROVAL — Documentation

A process description and 11 handbook chapters read from the code, 28 objects and 20 tables inventoried. The business layer comes from a model in a real run.

Process description

Written from the code when the stage opens, no model call. A project exports the same document; its appendix stands at the foot of this page. The demo exports nothing.

In short

Reconstructed· from the code

What it does

Creates purchase orders and starts workflows in SAP, reading purchase requisitions (EBAN) and suppliers (LFA1), selected by purchase requisition number.Source line 475Source line 421
It creates purchase orders (BAPI_PO_CREATE1) and starts workflows (SAP_WAPI_CREATE_EVENT) and changes purchase requisitions (EBAN) and two custom tables (ZMM_PO_APPR, ZMM_PO_ATTACH) in SAP.Source line 421Source line 475+2
It reads purchase requisitions (EBAN), suppliers (LFA1), supplier purchasing data (LFM1), cost centers (CSKS), 5 more tables, tables ZMM_VEND_BLOCK, ZMM_DEPT_HEAD and ZMM_NOTIFY_CFG and a file the user uploads from the PC.Source line 61Source line 154+2
The result is a list on screen.Source line 542
A user starts it from a selection screen with 4 inputs; it runs in the user's session.Source line 36Source line 129
12 business rules are fixed in the code.

What it does not do

It calls no other system: no call names a DESTINATION.

Limits of this reading

Supplier master data (LFA1, LFM1), cost center master data (CSKS) and material master data (MARC) are read as they are stored when it runs, not as they were on an earlier date.Source line 154Source line 161+1
1 place names its target only at run time; what it reaches is not determined.Not determined
Why the program exists is not written in its code: this says what it does, not what it is for in your company.Not determined
A line reference shows where a statement comes from in the code. It does not show that the business has confirmed it.

Owner and approval

Process owner: Not determined — the code names no owner, and none is recorded here.Not determined
Business approval: Not recorded — reconstructed from the code, not confirmed by the business.Not determined

Questions a reader asks

Why is an item missing? — It selects by purchase requisition number. The checks that skip a record are listed with their condition and line.
Why is a value unknown? — The business rules fixed in the code set the values; each says when it applies, and what happens when none does.
Why is there no proposal or result? — The cases that end the run or skip a record, each with the message the user sees.
What changes in S/4HANA? — Today it creates purchase orders (BAPI_PO_CREATE1) and starts workflows (SAP_WAPI_CREATE_EVENT) and changes purchase requisitions (EBAN) and two custom tables (ZMM_PO_APPR, ZMM_PO_ATTACH) in SAP. The move itself is decided in Design and Management, with the open questions.

Process description · At a glance

Reconstructed· from the code

Demo · Emergency purchase approval — Z_MM_PO_APPROVAL

Z_MM_PO_APPROVAL.abap · 552 lines

Creates purchase orders and starts workflows in SAP, reading purchase requisitions and suppliers, selected by purchase requisition number.

The result is a list on screen.

Started by: A user starts it from a selection screen with 4 inputs; it runs in the user's session. Who carries out the steps is not provable from the code.

Steps: 11
Decision points: 17
Business rules: 21
Exceptions: 19
Integrations: 7
Open questions: 7

Main path

Start
Check authority1 table read
Read requisition1 table read
Check requisition2 tables read
Rejected?Yes: ends the runDecision point: Yes: the run ends; No: continue with “Upload attachment”
Upload attachment1 table changed
Read vendor2 tables read
Check vendor1 table read
Rejected?Yes: ends the runDecision point: Yes: the run ends; No: continue with “Read info record”
Read info record2 tables read
Check price
On hold?Yes: ends the runDecision point: Yes: the run ends; No: continue with “Decide approval”
Decide approval3 tables read1 table changed
Notify requester1 table read
Write result list
End

Changes3

Purchase requisitionEBAN
custom tableZMM_PO_APPR
custom tableZMM_PO_ATTACH

Rules and risks to know

Business rule BR-009 Deviation percent above 5 → runs “Hold for buyer” and ends “Check price”. Source line 315Source lines 316 to 317
Business rule BR-010 Emergency set and amount at most 50000.00 → runs “Find department head” and “Request approval”. Source lines 325 to 327
Business rule BR-004 Currency other than EUR → runs “Convert to EUR”. Source lines 69 to 70
Changes SAP data directly: the purchase requisition. EBANSource line 240
5 values are fixed in the code, not in customizing. BR-001, BR-002, BR-003 +1Source line 17Source line 18+1

What this covers

The process in Z_MM_PO_APPROVAL.abap: 11 steps, 17 decision points, 21 rules. Source lines 1 to 552
An authorization check limits who can complete it. M_BANF_EKGSource lines 116 to 118

What it leaves out

Settings and master data in 3 custom tables it only reads. ZMM_VEND_BLOCK, ZMM_DEPT_HEAD, ZMM_NOTIFY_CFGSource line 222+2
Jobs, variants and schedules that start it, and manual steps around a run.
What the 6 SAP functions and transactions it calls do inside SAP. GUI_UPLOAD, CONVERT_TO_LOCAL_CURRENCY, SAP_WAPI_CREATE_EVENT +3Source lines 129 to 140+3
2 includes whose source was not uploaded. Z_MM_PO_NOTIFY, Z_MM_PO_LOGSource line 363+1

Reconstructed from the code by the Clean-Core.io engine. Line references (L…) point at the source. What the code cannot answer is asked once, in the open questions. Text marked "Model proposal" was written by a language model.

1. How the process works

11 steps on the main path; 3 decision points between them can end the run. A run starts from a selection screen with 4 inputs.

How a run starts

A user starts the report Z_MM_PO_APPROVAL and fills in its selection screen (4 fields); it can also run as a background job with a variant, which the code does not show. Source line 11Source line 36
The processing runs in START-OF-SELECTION. Source line 41

Purchase requisition number · Requisition item · File

Selection screen
Input	Required	Default	Source
Purchase requisition number	RequiredYes	Default0010000001	SourceP_BANFNSource line 36
Requisition item	RequiredNo	Default00010	SourceP_BNFPOSource line 37
File	RequiredNo	Default—	SourceP_FILESource line 38
Test run	RequiredNo	DefaultX	SourceP_TESTSource line 39

Steps

How a run starts is read from the code; who carries out the steps is not provable from it: the steps hold no dialogue, background or update-task statement that says so.

Check authority — Reads the purchase requisition; can end early.
CHECK_AUTHORITYSource line 42Source lines 103 to 122
Read requisition — Reads the purchase requisition; converts currency; can end early.
READ_REQUISITIONSource line 43Source lines 60 to 75
Check requisition — Reads the cost center and the material plant data; can end early.
CHECK_REQUISITIONSource line 44Source lines 77 to 98
Decision: Rejected? — Yes: the run ends; No: continue with “Upload attachment”
gv_rejected = abap_falseSource line 45
Upload attachment — Changes a custom table; reads a file from the user's PC; can end early.
UPLOAD_ATTACHMENTSource line 46Source lines 124 to 146
Read vendor — Reads the supplier and the supplier purchasing data; can end early.
READ_VENDORSource line 47Source lines 151 to 167
Check vendor — Reads a custom table.
CHECK_VENDORSource line 48Source lines 219 to 228
Decision: Rejected? — Yes: the run ends; No: continue with “Read info record”
gv_rejected = abap_falseSource line 49
Read info record — Reads the purchasing info record and the info record purchasing data; can end early.
READ_INFO_RECORDSource line 50Source lines 250 to 269
Check price
CHECK_PRICESource line 51Source lines 303 to 319
Decision: On hold? — Yes: the run ends; No: continue with “Decide approval”
gv_on_hold = abap_falseSource line 52
Decide approval — Reads the release strategy and 2 more tables; changes a custom table; starts workflow; calls 2 more SAP functions.
DECIDE_APPROVALSource line 53Source lines 324 to 340
Notify requester — Reads a custom table; can end early.
NOTIFY_REQUESTERSource line 54Source lines 379 to 395
Write result list
WRITE_RESULT_LISTSource line 55Source lines 540 to 552

2. Business rules and decision points

21 rules: 9 business rules, 7 decision points, 5 fixed values.

Business rules and decision points
Rule	When	Then	Step	Source
BR-009	WhenDeviation percent above 5	ThenRuns “Hold for buyer” and ends “Check price”	StepCheck price	SourceSource line 315Source lines 316 to 317
BR-010	WhenEmergency set and amount at most 50000.00	ThenRuns “Find department head” and “Request approval”	StepDecide approval	SourceSource lines 325 to 327
BR-004	WhenCurrency other than EUR	ThenRuns “Convert to EUR”	StepRead requisition	SourceSource lines 69 to 70
BR-005	WhenMRP controller EMG or tracking number EMERG*	ThenHandled separately in “Read requisition”	StepRead requisition	SourceSource lines 72 to 73
BR-006	WhenPlant 1000	ThenHandled separately in “Check requisition”	StepCheck requisition	SourceSource lines 95 to 96
BR-008	WhenMmsta 01 or Z9	ThenRuns “Reject”	StepCheck material status	SourceSource lines 277 to 278
BR-007	WhenAccount assignment category is 'K'	ThenRuns “Check cost center”	StepCheck account assignment	SourceSource line 202Source lines 203 to 204
BR-012	WhenAccount assignment category is 'F'	ThenRuns “Reject”	StepCheck account assignment	SourceSource line 202Source lines 205 to 208
BR-011	WhenRole DEPT_HEAD	ThenHandled separately in “Request approval”	StepRequest approval	SourceSource lines 432 to 433
Decision point	WhenNot rejected	ThenRuns “Upload attachment”, “Read vendor” and “Check vendor”	StepStart of selection	SourceSource line 45Source line 46Source line 47+1
Decision point	WhenNot rejected	ThenRuns “Read info record” and “Check price”	StepStart of selection	SourceSource line 49Source line 50Source line 51
Decision point	WhenNot on hold	ThenRuns “Decide approval”, “Notify requester” and “Write result list”	StepStart of selection	SourceSource line 52Source line 53Source line 54+1
Decision point	WhenNo order number (only inside the branch where account assignment category is 'F', L205)	ThenRuns “Reject”	StepCheck account assignment	SourceSource line 206Source line 207
Decision point	WhenNot reference price at most 0	ThenRuns “Hold for buyer”	StepCheck price	SourceSource line 308Source line 316
Decision point	WhenApproved	ThenRuns “Create purchase order”	StepDecide approval	SourceSource line 336Source line 337
Decision point	WhenReturn message found	ThenRuns “Create purchase order by simulated entry”; otherwise runs “Save the changes”	StepCreate purchase order	SourceSource line 487Source line 488Source lines 490 to 492Open question: Add ATC results
BR-001	WhenAlways (fixed in the code)	ThenProcesses only document type NB	StepWhole program	SourceSource line 17
BR-002	WhenAlways (fixed in the code)	ThenProcesses only release group ZE	StepWhole program	SourceSource line 18
BR-003	WhenAlways (fixed in the code)	ThenProcesses only purch org 1000	StepWhole program	SourceSource line 19
Fixed values	WhenAlways (fixed in the code)	ThenUses approver 'PURCH_LEAD' in “Find department head”	StepFind department head	SourceSource line 360
Fixed values	WhenAlways (fixed in the code)	ThenUses comp code '1000' and purchase order item '00010' in “Create purchase order”	StepCreate purchase order	SourceSource line 453Source line 460

3. Exceptions

3 cases stop the run with an error; 3 warn and continue; 13 end a step or the run early.

Exceptions
What happens	Step	The user sees	Result	Source
No purchase requisition found	StepRead requisition	The user sees“Purchase requisition not found …”	ResultRun stops (error)	SourceE001 · ZMM_POSource line 65Source line 66
No purchase requisition found	StepCheck authority	The user sees“Purchase requisition not found …”	ResultRun stops (error)	SourceE001 · ZMM_POSource line 109Source line 110
No authorization for purchasing group …	StepCheck authority	The user sees“No authorization for purchasing group …”	ResultRun stops (error)	SourceE002 · ZMM_POSource line 120
Attachment could not be read	StepUpload attachment	The user sees“Attachment could not be read …”	ResultWarning; run continues	SourceW003 · ZMM_POSource lines 129 to 140Source line 142
No exchange rate for …	StepConvert to EUR	The user sees“No exchange rate for …”	ResultWarning; run continues	SourceW004 · ZMM_POSource line 187
Notification failed	StepNotify requester	The user sees“Notification failed for …”	ResultWarning; run continues	SourceW007 · ZMM_POSource lines 386 to 391Source line 393Open question: Name the call target
Rejected? — Yes	StepMain path	The user sees—	ResultRun ends	SourceSource line 45
Rejected? — Yes	StepMain path	The user sees—	ResultRun ends	SourceSource line 49
On hold? — Yes	StepMain path	The user sees—	ResultRun ends	SourceSource line 52
Rejected: no material	StepCheck requisition	The user sees—	ResultStep ends	SourceSource line 80
Rejected: release indicator set	StepCheck requisition	The user sees—	ResultStep ends	SourceSource line 84
Stopped: rejected	StepCheck requisition	The user sees—	ResultStep ends	SourceSource line 88
Stopped: rejected	StepCheck requisition	The user sees—	ResultStep ends	SourceSource line 92
No supplier found	StepRead vendor	The user sees—	ResultStep leaves its path	SourceSource line 156
Rejected: no supplier found	StepRead vendor	The user sees—	ResultStep ends	SourceSource line 158
No supplier purchasing data found	StepRead vendor	The user sees—	ResultStep leaves its path	SourceSource line 164
No purchasing info record found	StepRead info record	The user sees—	ResultStep leaves its path	SourceSource line 257
Stopped: no purchasing info record found	StepRead info record	The user sees—	ResultStep ends	SourceSource line 259
Nothing found	StepNotify requester	The user sees—	ResultStep leaves its path	SourceSource line 385

4. What it changes and produces

8 effects on data and documents, the weightiest first.

What it changes and produces
Effect	What	Source
Creates a document	WhatCreates the purchase order	SourceBAPI_PO_CREATE1Source lines 475 to 484
Creates a document (batch input)	WhatCreates the purchase order by simulated entry through a transaction (batch input)	SourceME21N, MEPO_TOPLINE-SUPERFIELDSource line 508Source line 515Source lines 515 to 518
Starts a workflow	WhatStarts the workflow	SourceSAP_WAPI_CREATE_EVENTSource lines 421 to 427
Changes data	WhatCreates an entry in a custom table	SourceZMM_PO_APPRSource line 353
Changes data	WhatCreates an entry in a custom table	SourceZMM_PO_ATTACHSource lines 531 to 534
Changes data	WhatUpdates the purchase requisition	SourceEBANSource lines 240 to 242
Reads or writes a file	WhatReads a file from the user's PC	SourceGUI_UPLOADSource lines 129 to 140
Shows a list	WhatShows the result of the run as a list (“Write result list”)	SourceSource lines 541 to 551

5. Systems and data

It reads 12 tables; calls 7 functions by name; holds 4 controls.

Data it reads

12 tables read; which rows each read takes, as the code filters them.

Purchase requisition · Supplier · Supplier purchasing data

Data it reads
Business object	Owner	Which rows	Source
Purchase requisition	OwnerSAP	Which rowsOnly where loekz = space (fixed in the code); restricted by the selection screen: banfn = p_banfn, bnfpo = p_bnfpo / Restricted by the selection screen: banfn = p_banfn, bnfpo = p_bnfpo	SourceEBANSource line 61Source line 106
Supplier	OwnerSAP	Which rowsBy lifnr = gs_eban-flief	SourceLFA1Source line 154
Supplier purchasing data	OwnerSAP	Which rowsOnly where ekorg = c_purch_org (fixed in the code); by lifnr = gs_eban-flief	SourceLFM1Source line 161
Cost center	OwnerSAP	Which rowsOnly where kokrs = '1000' and datbi >= sy-datum (fixed in the code); by kostl = gs_eban-kostl	SourceCSKSSource line 192
Custom table	OwnerCustomer	Which rowsOnly where blocked = 'X' (fixed in the code); by lifnr = gs_eban-flief	SourceZMM_VEND_BLOCKSource line 222
Purchasing info record	OwnerSAP	Which rowsBy matnr = gs_eban-matnr and lifnr = gs_eban-flief	SourceEINASource line 254
Info record purchasing data	OwnerSAP	Which rowsOnly where ekorg = c_purch_org (fixed in the code); by infnr = ls_eina-infnr and werks = gs_eban-werks	SourceEINESource line 262
Material plant data	OwnerSAP	Which rowsBy matnr = gs_eban-matnr and werks = gs_eban-werks	SourceMARCSource line 274
Release strategy	OwnerSAP	Which rowsOnly where frggr = c_release_group (fixed in the code)	SourceT16FSSource line 289
Custom table	OwnerCustomer	Which rowsBy kostl = gs_eban-kostl	SourceZMM_DEPT_HEADSource line 357
Communication data	OwnerSAP	Which rowsOnly where subty = '0001' (fixed in the code); by usrid = gs_eban-afnam / Only where subty = '0001' (fixed in the code); by pernr = lv_pernr	SourcePA0105Source line 368Source line 371
Custom table	OwnerCustomer	Which rowsBy werks = gs_eban-werks	SourceZMM_NOTIFY_CFGSource line 383

Amount · Reference price · Price

Values it computes
Value	Computed as	Kind	Source
Amount	Computed asQuantity × Price ÷ Price unit	KindComputed	Sourcegv_amount = gs_eban-menge * gs_eban-preis / gs_eban-peinh · READ_REQUISITIONSource line 68
Reference price	Computed asNet price ÷ Price unit	KindComputed	Sourcegv_ref_price = ls_eine-netpr / ls_eine-peinh · READ_INFO_RECORDSource line 267
Price	Computed asPrice ÷ Price unit	KindComputed	Sourcelv_price = gs_eban-preis / gs_eban-peinh · CHECK_PRICESource line 309
Deviation percent	Computed as(Price - Reference) × 100 ÷ Reference	KindComputed	Sourcelv_dev_pct = ( lv_price - lv_ref ) * 100 / lv_ref · CHECK_PRICESource line 311

Integrations

7 calls to other functions: 1 file, 2 functions, 1 workflow, 2 BAPIs, 1 transaction.

Open question for 2 of the 7 rows: Add ATC results

Reads a file from the user's PC · File on the user’s PC GUI_UPLOADSource lines 129 to 140
Converts currency in the step “Convert to EUR”. · Function module CONVERT_TO_LOCAL_CURRENCYSource lines 173 to 183
Used in the step “Run a step chosen at runtime”. · Dynamic function call (name computed at run time)Source lines 386 to 391Open question: Name the call target
Starts the workflow · Workflow event SAP_WAPI_CREATE_EVENTSource lines 421 to 427
Creates the purchase order · BAPI BAPI_PO_CREATE1Source lines 475 to 484
Saves the changes in the step “Save the changes”. · BAPI BAPI_TRANSACTION_COMMITSource lines 490 to 492
Creates the purchase order by simulated entry through a transaction (batch input) · Transaction by batch input ME21NSource lines 515 to 518

Controls

4 controls in the code: authorization check, record of each case, saving changes, result check of a BAPI.

Authorization check. Checks the user’s authorization before it goes on.
M_BANF_EKG · NFR-05Source lines 116 to 118Source line 119Source line 120
Record of each case. Keeps a record of each case in a custom table.
NFR-04Source line 234Source line 244Source line 339+3
Saving changes. Saves its changes in 3 separate places in one run.
COMMIT WORK, CALL FUNCTION BAPI_TRANSACTION_COMMITSource line 243Source line 428Source lines 490 to 492Open question: Add ATC results
Result check of a BAPI. Checks the result of the SAP call for errors.
GT_RETURN · NFR-08Source lines 475 to 484Source line 486

6. Open questions

7 open questions; 3 block the decision; 0 of 5 groups closed.

Add the includes2ITOpen — blocks the decisionSource line 363Source line 396
Parts of the program were not in the upload, so what they do is unknown. This project cannot take further includes, so the answer is yours to give.
Choose the target1ManagementOpen — blocks the decision
No target edition is declared, so what “works on the target” means is not settled.
Name the call target1ITSource line 386
What these statements call or which table they use is decided only while the program runs; the code alone cannot name it, so the answer is yours to give.
Add ATC results2ITSource line 173Source line 490
Whether these function-module calls and file accesses still work on the target is not checked by this engine; your system’s ATC cloud-readiness check judges them.
Add usage data1IT
Whether the program still runs is unknown until a usage export is imported. Never imported is unknown, not unused.

This reading does not cover classic list output (2 places): limits of the engine, noted here and not questions anyone can answer.

19 questions about the requirements are decisions of the requirements workspace in Design; A.4 Questions about the requirements lists them.

Business SOP and RACI

Model proposal

Who does what at each step, who is accountable, and the controls — proposed by a language model from the process documentation read from your code. The steps and their lines stay the code reading.

The demo stops where the model begins. The business SOP and RACI layer on top of this description comes out of a model call against the source in a real run. A demo makes no model call, so there is none here — and writing a convincing one by hand is the one thing this product may never do. What you see above is what the deterministic engine produced, which is the half that carries the line numbers.

Who is responsible Model proposalThe roles are a proposal for the business to confirm.

Responsible
Accountable
Consulted
Informed

A project starts from the model’s proposal; the demo calls no model. Name the roles yourself and say who does what at each step.

Explore the process

The process drawn from the code, with the chapter of each step beside it. Select a step to read its chapter.

Process as the code runs it Reconstructed· code reading

Select a step to read its chapter

Chapter 1 of 11 · select a step to change it

Check authority

CHECK_AUTHORITYReconstructed

Reads purchase requisition (EBAN). Can end early in 1 place.

Business rules

No business rule decides in this chapter.

Roles · model proposal only

No model proposal for roles exists for this run. The code names authorizations, not people.

Reads · writes

Purchase requisition EBANSource line 104

Exception

No purchase requisition foundSource line 109

Steps in this chapter

Source lines 106 to 108
Source line 119

What the code says

The purchasing group of the purchase requisition with the entered purchase requisition number and the entered bnfpo is read.Source lines 106 to 108
Without authorization for M_BANF_EKG, an error message is output.Source line 119
Without a hit, an error message is output.Source line 109

Appendix: details and evidence

What the body says shorter, in the code's own words, then every process element and statement the engine read. Each sentence is printed once (22 repeats merged); nothing is left out.

Steps at a glance

Steps at a glance
No.	Step	What it does	Lines	Details
1	StepCheck authority	What it doesReads the purchase requisition; can end early.	LinesSource line 42Source lines 103 to 122	Details5
2	StepRead requisition	What it doesReads the purchase requisition; converts currency; can end early.	LinesSource line 43Source lines 60 to 75	Details7
3	StepCheck requisition	What it doesReads the cost center and the material plant data; can end early.	LinesSource line 44Source lines 77 to 98	Details13
4	StepUpload attachment	What it doesChanges a custom table; reads a file from the user's PC; can end early.	LinesSource line 46Source lines 124 to 146	Details3
5	StepRead vendor	What it doesReads the supplier and the supplier purchasing data; can end early.	LinesSource line 47Source lines 151 to 167	Details7
6	StepCheck vendor	What it doesReads a custom table.	LinesSource line 48Source lines 219 to 228	Details1
7	StepRead info record	What it doesReads the purchasing info record and the info record purchasing data; can end early.	LinesSource line 50Source lines 250 to 269	Details5
8	StepCheck price	What it does—	LinesSource line 51Source lines 303 to 319	Details0
9	StepDecide approval	What it doesReads the release strategy and 2 more tables; changes a custom table; starts workflow; calls 2 more SAP functions.	LinesSource line 53Source lines 324 to 340	Details12
10	StepNotify requester	What it doesReads a custom table; can end early.	LinesSource line 54Source lines 379 to 395	Details3
11	StepWrite result list	What it does—	LinesSource line 55Source lines 540 to 552	Details0

Step details

Reads the purchase requisition; can end early.
- Technical CHECK_AUTHORITY · L42, L103–122
- Reads purchase requisition (EBAN). Can end early in 1 place.
- The purchasing group of the purchase requisition with the entered purchase requisition number and the entered bnfpo is read. (L106–108)
- Without authorization for M_BANF_EKG, an error message is output. (L119, L120)
- Step Read purchase requisition (L106–108)
- Decision point Not authorized? (L119)
Reads the purchase requisition; converts currency; can end early.
- Technical READ_REQUISITION · L43, L60–75
- Reads purchase requisition (EBAN). Calls CONVERT_TO_LOCAL_CURRENCY. Can end early in 1 place.
- Purchase requisitions with the entered purchase requisition number and the entered bnfpo are selected. (L61–64)
- Without a hit, an error message is output. (L65, L66)
- Step Read purchase requisition (L61–64)
- Decision point Currency not EUR? (L69)
- Service step Convert to EUR (L70)
- Decision point MRP controller EMG or tracking number EMERG*? (L72)
Reads the cost center and the material plant data; can end early.
- Technical CHECK_REQUISITION · L44, L77–98
- Reads cost center (CSKS) and material plant data (MARC). Can end early in 4 places.
- Without a material number, reject is called and the block is exited. (L78, L79, L80)
- Decision point Material given? (L78)
- Step Reject (L79)
- Decision point Release indicator set? (L82)
- Step Reject (L83)
- Step Check material status (L86)
- Decision point Rejected? (L87)
- Sub-process: Check account assignment (L90)
- – Decision point: Account assignment category? (L202)
- – Step: Check cost center (L204)
- – Decision point: Order number given? (L206)
- and 4 more sub-steps — see the process elements below
Decision point “Rejected?” (the code: gv_rejected = abap_false, L45) — Yes: the run ends; No: continue with “Upload attachment”.
Changes a custom table; reads a file from the user's PC; can end early.
- Technical UPLOAD_ATTACHMENT · L46, L124–146
- Changes ZMM_PO_ATTACH. Calls GUI_UPLOAD. Can end early in 1 place.
- Step Read a file from the user's PC (L129–140)
- Step Store attachment (L144)
Reads the supplier and the supplier purchasing data; can end early.
- Technical READ_VENDOR · L47, L151–167
- Reads supplier (LFA1) and supplier purchasing data (LFM1). Can end early in 3 places.
- Suppliers are selected. (L154–155)
- Without a hit, reject is called and the block is exited. (L156, L157, L158)
- Step Read supplier (L154–155)
- Step Read supplier purchasing data (L161–163)
- Step Reject (L157)
- Step Reject (L165)
Reads a custom table.
- Technical CHECK_VENDOR · L48, L219–228
- Reads ZMM_VEND_BLOCK.
Decision point “Rejected?” (the code: gv_rejected = abap_false, L49) — Yes: the run ends; No: continue with “Read info record”.
Reads the purchasing info record and the info record purchasing data; can end early.
- Technical READ_INFO_RECORD · L50, L250–269
- Reads purchasing info record (EINA) and info record purchasing data (EINE). Can end early in 2 places.
- Without a hit, the block is exited. (L257, L258, L259)
- Step Read purchasing info record (L254–256)
- Step Read info record purchasing data (L262–265)
- Decision point Found and price unit above 0? (L266)
- Technical CHECK_PRICE · L51, L303–319
Decision point “On hold?” (the code: gv_on_hold = abap_false, L52) — Yes: the run ends; No: continue with “Decide approval”.
Reads the release strategy and 2 more tables; changes a custom table; starts workflow; calls 2 more SAP functions.
- Technical DECIDE_APPROVAL · L53, L324–340
- Reads release strategy (T16FS), ZMM_DEPT_HEAD and communication data (PA0105). Changes ZMM_PO_APPR. Calls SAP_WAPI_CREATE_EVENT, BAPI_PO_CREATE1, BAPI_TRANSACTION_COMMIT and 1 more.
- Decision point Which case applies? (L325)
- Step Find department head (L326)
- Message step Request approval (L327)
- Decision point Approved? (L336)
- Sub-process: Create purchase order (L337)
- – Service step: Create purchase order (L475–484)
- – Decision point: Return message found? (L487)
- – Call: Create purchase order by simulated entry (L488)
- – Service step: Save the changes (L490–492)
- Step Log approval (L339)
- and 3 more sub-steps — see the process elements below
Reads a custom table; can end early.
- Technical NOTIFY_REQUESTER · L54, L379–395
- Reads ZMM_NOTIFY_CFG. Can end early in 2 places.
- Step Read ZMM_NOTIFY_CFG (L383–384)
- Service step Run a step chosen at runtime (L386–391)
- Technical WRITE_RESULT_LIST · L55, L540–552

The evidence, complete

Every process element and every statement the engine read, with its lines.

Wording as read from the code
Section	Item	As read from the code	Lines
2. Business rules and decision points	ItemBR-001	As read from the codeThe system shall process only document type NB. No decision point tests the constant directly.	LinesL17
2. Business rules and decision points	ItemBR-002	As read from the codeThe system shall process only release group ZE. No decision point tests the constant directly.	LinesL18
2. Business rules and decision points	ItemBR-003	As read from the codeThe system shall process only purch org 1000. No decision point tests the constant directly.	LinesL19
2. Business rules and decision points	ItemDecision point	As read from the codeThe system shall run “Upload attachment”, “Read vendor” and “Check vendor” unless rejected.	LinesL45, L46, L47 +1
2. Business rules and decision points	ItemDecision point	As read from the codeThe system shall run “Read info record” and “Check price” unless rejected.	LinesL49, L50, L51
2. Business rules and decision points	ItemDecision point	As read from the codeThe system shall run “Decide approval”, “Notify requester” and “Write result list” unless on hold.	LinesL52, L53, L54 +1
2. Business rules and decision points	ItemBR-004	As read from the codeThe system shall run “Convert to EUR” when currency other than EUR.	LinesL69–70
2. Business rules and decision points	ItemBR-005	As read from the codeThe system shall handle the case where MRP controller EMG or tracking number EMERG* separately in “Read requisition”.	LinesL72–73
2. Business rules and decision points	ItemBR-006	As read from the codeThe system shall handle the case where plant 1000 separately in “Check requisition”.	LinesL95–96
2. Business rules and decision points	ItemBR-008	As read from the codeThe system shall run “Reject” when mmsta 01 or Z9.	LinesL277–278
2. Business rules and decision points	ItemBR-007	As read from the codeThe system shall run “Check cost center” when account assignment category is 'K'.	LinesL202, L203–204
2. Business rules and decision points	ItemBR-012	As read from the codeThe system shall run “Reject” when account assignment category is 'F'.	LinesL202, L205–208
2. Business rules and decision points	ItemDecision point	As read from the codeThe system shall run “Reject” when no order number (only inside the branch where account assignment category is 'F', L205).	LinesL206, L207
2. Business rules and decision points	ItemDecision point	As read from the codeThe system shall run “Hold for buyer” unless reference price at most 0.	LinesL308, L316
2. Business rules and decision points	ItemBR-009	As read from the codeThe system shall run “Hold for buyer” and end “Check price” when deviation percent above 5.	LinesL315, L316–317
2. Business rules and decision points	ItemBR-010	As read from the codeThe system shall run “Find department head” and “Request approval” when emergency set and amount at most 50000.00.	LinesL325–327
2. Business rules and decision points	ItemDecision point	As read from the codeThe system shall run “Create purchase order” when approved.	LinesL336, L337
2. Business rules and decision points	ItemFixed values	As read from the codeThe system shall use these fixed values in “Find department head”: approver 'PURCH_LEAD'.	LinesL360
2. Business rules and decision points	ItemBR-011	As read from the codeThe system shall handle the case where role DEPT_HEAD separately in “Request approval”.	LinesL432–433
2. Business rules and decision points	ItemFixed values	As read from the codeThe system shall use these fixed values in “Create purchase order”: comp code '1000' and purchase order item '00010'.	LinesL453, L460
2. Business rules and decision points	ItemDecision point	As read from the codeThe system shall run “Create purchase order by simulated entry” when return message found; otherwise it shall run “Save the changes”.	LinesL487, L488, L490–492
3. Exceptions	ItemRejected? — Yes	As read from the codeThe run ends; the later steps do not run.	LinesL45
3. Exceptions	ItemRejected? — Yes	As read from the codeThe run ends; the later steps do not run.	LinesL49
3. Exceptions	ItemOn hold? — Yes	As read from the codeThe run ends; the later steps do not run.	LinesL52
3. Exceptions	ItemNo purchase requisition found	As read from the codeError E001 of class ZMM_PO: “Purchase requisition not found …” — The run stops with an error message.	LinesL65, L66
3. Exceptions	ItemRejected: no material	As read from the code“Check requisition” ends here.	LinesL80
3. Exceptions	ItemRejected: release indicator set	As read from the code“Check requisition” ends here.	LinesL84
3. Exceptions	ItemStopped: rejected	As read from the code“Check requisition” ends here.	LinesL88
3. Exceptions	ItemStopped: rejected	As read from the code“Check requisition” ends here.	LinesL92
3. Exceptions	ItemNo purchase requisition found	As read from the codeError E001 of class ZMM_PO: “Purchase requisition not found …” — The run stops with an error message.	LinesL109, L110
3. Exceptions	ItemNo authorization for purchasing group …	As read from the codeError E002 of class ZMM_PO: “No authorization for purchasing group …” — The run stops with an error message.	LinesL120
3. Exceptions	ItemAttachment could not be read	As read from the codeWarning W003 of class ZMM_PO: “Attachment could not be read …” — A warning is shown; the run continues.	LinesL129–140, L142
3. Exceptions	ItemNo supplier found	As read from the codeThe step leaves its normal path here.	LinesL156
3. Exceptions	ItemRejected: no supplier found	As read from the code“Read vendor” ends here.	LinesL158
3. Exceptions	ItemNo supplier purchasing data found	As read from the codeThe step leaves its normal path here.	LinesL164
3. Exceptions	ItemNo exchange rate for …	As read from the codeWarning W004 of class ZMM_PO: “No exchange rate for …” — A warning is shown; the run continues.	LinesL187
3. Exceptions	ItemNo purchasing info record found	As read from the codeThe step leaves its normal path here.	LinesL257
3. Exceptions	ItemStopped: no purchasing info record found	As read from the code“Read info record” ends here.	LinesL259
3. Exceptions	ItemNothing found	As read from the codeThe step leaves its normal path here.	LinesL385
3. Exceptions	ItemNotification failed	As read from the codeWarning W007 of class ZMM_PO: “Notification failed for …” — A warning is shown; the run continues.	LinesL386–391, L393
4. What it changes and produces	ItemChanges data	As read from the codeCreates an entry in ZMM_PO_APPR	LinesL353
4. What it changes and produces	ItemReads or writes a file	As read from the codeReads a file from the user's PC (GUI_UPLOAD)	LinesL129–140
4. What it changes and produces	ItemChanges data	As read from the codeCreates an entry in ZMM_PO_ATTACH	LinesL531–534
4. What it changes and produces	ItemChanges data	As read from the codeUpdates the purchase requisition (EBAN)	LinesL240–242
4. What it changes and produces	ItemStarts a workflow	As read from the codeStarts the workflow (SAP_WAPI_CREATE_EVENT)	LinesL421–427
4. What it changes and produces	ItemCreates a document	As read from the codeCreates the purchase order (BAPI_PO_CREATE1)	LinesL475–484
4. What it changes and produces	ItemCreates a document (batch input)	As read from the codeCreates the purchase order (ME21N) by simulated entry through transaction ME21N (batch input) The batch input to ME21N (line 515) fills MEPO_TOPLINE-SUPERFIELD.	LinesL508, L515, L515–518
5. Systems and data	ItemAuthorization check	As read from the code“Check authority” checks M_BANF_EKG at L116-118 and tests the result right after it.	LinesL116–118, L119, L120
5. Systems and data	ItemRecord of each case	As read from the code“Log approval” inserts this row at L353, called from 3 places (L234, L244, L339), and fills ERDAT with sy-datum and ERZET with sy-uzeit.	LinesL234, L244, L339 +1
5. Systems and data	ItemSaving changes	As read from the codeCOMMIT WORK saves every change made so far without waiting for the update. COMMIT WORK saves every change made so far without waiting for the update. CALL FUNCTION BAPI_TRANSACTION_COMMIT saves every change made so far and waits for the update.	LinesL243, L428, L490–492
5. Systems and data	ItemResult check of a BAPI	As read from the codeThe program reads GT_RETURN for type E right after the call (L486).	LinesL475–484, L486
1. How the process works	ItemStart	As read from the codeA user starts the report Z_MM_PO_APPROVAL and fills in its selection screen (4 fields); it can also run as a background job with a variant, which the code does not show.	LinesL11, L36
1. How the process works	ItemStart	As read from the codeThe processing runs in START-OF-SELECTION.	LinesL41
At a glance	ItemCreates purchase orders and starts workflows in SAP, reading purchase requisitions and suppliers, selected by purchase requisition number.	As read from the codeSAP_WAPI_CREATE_EVENT, BAPI_PO_CREATE1, EBAN, LFA1	LinesL421, L475
At a glance	ItemA user starts it from a selection screen with 4 inputs; it runs in the user's session.	As read from the codeP_BANFN, P_BNFPO, P_FILE, P_TEST	LinesL11, L36
At a glance	ItemWhat the 6 SAP functions and transactions it calls do inside SAP.	As read from the codeGUI_UPLOAD, CONVERT_TO_LOCAL_CURRENCY, SAP_WAPI_CREATE_EVENT, BAPI_PO_CREATE1, BAPI_TRANSACTION_COMMIT, ME21N	LinesL129–140, L173–183, L421–427 +1
1. How the process works	ItemTraceability	As read from the code97 of 97 shapes on this map carry a line anchor — 100.0 % traceability. The map draws a small routine as one shape, so this count can differ from the number of process elements read from the code.	Lines

A.4 Questions about the requirements
No.	Question	Owner	Priority	Source ids	Why the code cannot answer it	As the engine asked
Q1	QuestionWhat is the currency of the amount 50000.00 in rule BR-010?	OwnerBusiness	PriorityBlocks the design	Source idsTBC-02	Why the code cannot answer itThe code compares with '50000.00' and does not state the currency of the amount.	As the engine askedThe currency of the amount in BR-010 ('50000.00')?
Q2	QuestionWhich function does “Notify requester” call? Its name is set at run time.	OwnerBusiness	PriorityBlocks the design	Source idsTBC-03	Why the code cannot answer itThe name is computed at run time; the code does not state it.	As the engine askedWhich function module does “Notify requester” call at L386?
Q3	QuestionWhat do the 2 includes do whose source was not uploaded?	OwnerIT operations	PriorityBlocks the design	Source idsC-01, C-02	Why the code cannot answer itInclude Z_MM_PO_NOTIFY was not uploaded — what it does is not determined. No detector read the statements in it, so nothing found or not found here speaks for them. This project cannot take further includes; an analysis of the program uploaded together with its includes reads them. Include Z_MM_PO_LOG was not uploaded — what it does is not determined. No detector read the statements in it, so nothing found or not found here speaks for them. This project cannot take further includes; an analysis of the program uploaded together with its includes reads them.	As the engine askedWhat does the include Z_MM_PO_NOTIFY do? Its source was not uploaded with the program. / What does the include Z_MM_PO_LOG do? Its source was not uploaded with the program.
Q4	QuestionWho maintains the 3 custom tables it reads after the switch, and is their content still correct?	OwnerBusiness	PriorityBlocks the cutover	Source idsTBD-01	Why the code cannot answer itThe program only reads these tables (L222, L357, L383); who fills them is not in this source.	As the engine askedWho maintains ZMM_VEND_BLOCK, ZMM_DEPT_HEAD and ZMM_NOTIFY_CFG after the switch, and is the current content still correct?
Q5	QuestionWhich existing rows of its 2 custom tables must be taken over — all, or only from a date?	OwnerBusiness	PriorityBlocks the cutover	Source idsTBD-02, TBD-03	Why the code cannot answer itThe program writes ZMM_PO_APPR at L353; how many rows exist and which are still needed is not in the code. The program writes ZMM_PO_ATTACH at L531; how many rows exist and which are still needed is not in the code.	As the engine askedWhich existing rows of ZMM_PO_APPR must be taken over — all, or only from a certain date? / Which existing rows of ZMM_PO_ATTACH must be taken over — all, or only from a certain date?
Q6	QuestionHow long must rows of its 2 custom tables be kept, and what happens to them then?	OwnerBusiness	Priority—	Source idsTBD-04, TBD-05	Why the code cannot answer itThe program writes them at L353 with the date in ERDAT (L351) and deletes none; a retention period is not in the code. The program writes them at L531 with the date in ERDAT (L531) and deletes none; a retention period is not in the code.	As the engine askedHow long must rows of ZMM_PO_APPR be kept, and what happens to them after that? / How long must rows of ZMM_PO_ATTACH be kept, and what happens to them after that?
Q7	QuestionWhen does the new solution take over, and how long do both run side by side?	OwnerBusiness	PriorityBlocks the cutover	Source idsTBD-14	Why the code cannot answer itThe program changes data at L240, L353, L475, L515, L531; the cutover date and any parallel period are not in the code.	As the engine askedWhen does the new solution take over, and is there a period in which both run — for how long, and which one makes the changes?
Q8	QuestionAre workflow items open at the switch finished in the old process, or moved?	OwnerBusiness	PriorityBlocks the cutover	Source idsTBD-15	Why the code cannot answer itThe program starts them at L421; how many are open on the day is not in the code.	As the engine askedAre the workflow items still open at the switch finished in the old process, or moved to the new one?
Q9	QuestionWho owns this process and decides on changes to it?	OwnerBusiness	Priority—	Source idsQ-01	Why the code cannot answer itABAP source names no organisational owner. Accountability in this product is the signed-in account, which is a self-declaration and not stored on the document.	As the engine askedWho owns this process and decides on changes to it?
Q10	QuestionWhich key figures measure this process, and what are their targets?	OwnerBusiness	Priority—	Source idsQ-02	Why the code cannot answer itNo key figure is measured in the source. A target would be an assumption, and none is entered here.	As the engine askedWhich key figures measure this process, and what are their targets?
Q11	QuestionWhy does the business need this process, and is it still needed in this form?	OwnerBusiness	Priority—	Source idsQ-03	Why the code cannot answer itWhy the program exists is not written in its statements. The business statements say what it does.	As the engine askedWhy does the business need this process, and is it still needed in this form?
Q12	QuestionMust the record it keeps also say who ran the program?	OwnerBusiness	Priority—	Source idsTBD-06	Why the code cannot answer itThe row written at L353 carries MANDT, BANFN, BNFPO, APPROVER, AMOUNT, MESSAGE, ERDAT and ERZET; none of them is filled with the user (sy-uname).	As the engine askedMust the record in ZMM_PO_APPR also say who ran the program?
Q13	QuestionMust its changes to the purchase requisition be traceable — who changed what, and when?	OwnerBusiness	Priority—	Source idsTBD-07	Why the code cannot answer itThe program changes EBAN directly (UPDATE at L240) and writes no change document.	As the engine askedMust the changes this program makes to EBAN be traceable — who changed what, and when?
Q14	QuestionWhich business roles may pass the authorization check, and with which limits?	OwnerBusiness	Priority—	Source idsTBD-08	Why the code cannot answer itThe code checks M_BANF_EKG at L116; who holds it is decided in role administration, not in the code.	As the engine askedWhich business roles shall grant M_BANF_EKG with ACTVT '02', and for which EKGRP values?
Q15	QuestionWhich changes must be saved together, and how does a restart after a failure work?	OwnerIT operations	Priority—	Source idsTBD-09	Why the code cannot answer itThe program saves in 3 places in one run (COMMIT WORK at L243, COMMIT WORK at L428, BAPI_TRANSACTION_COMMIT at L490); a failure after the first leaves the earlier changes saved.	As the engine askedWhich changes must be saved together, and what does a restart after a failure do?
Q16	QuestionShall a failed SAP call be retried — how often, and how far apart?	OwnerIT operations	Priority—	Source idsTBD-10	Why the code cannot answer itThe program calls it once (L475), with no retry loop around it.	As the engine askedShall a failed call of BAPI_PO_CREATE1 be retried — how often, and how far apart?
Q17	QuestionWhere must operations see that a run failed, and who is alerted?	OwnerIT operations	Priority—	Source idsTBD-11	Why the code cannot answer itThe program writes no application log; it reports with 7 MESSAGE statements (L66, L110, L120, L142, L187, L233 and 1 more), which a user sees on screen and a background run leaves in its job log.	As the engine askedWhere must operations see that a run failed, and who is alerted?
Q18	QuestionHow many records per run, how often, and by when must a run finish?	OwnerBusiness	Priority—	Source idsTBD-12	Why the code cannot answer itThe code sets no volume, schedule or time limit; it starts from a selection screen (L36) and runs from START-OF-SELECTION (L41).	As the engine askedHow many records does one run handle, how often does it run, and by when must it finish?
Q19	QuestionWhich availability and response time must the process meet?	OwnerIT operations	Priority—	Source idsTBD-13	Why the code cannot answer itAvailability and response time are service levels; no line of the code can state them.	As the engine askedWhen must the process be available, and what is an acceptable response time for one case?

ReconstructedZ_MM_PO_APPROVAL.abap · 552 lines

Demo · Z_MM_PO_APPROVAL

Process with 41 steps and 17 decision points.

97 of 97 shapes on this map carry a line anchor — 100.0 % traceability. The map draws a small routine as one shape, so this count can differ from the number of process elements read from the code.

Not generated. No Gemini key is available for this account — neither the community key nor one of your own. Every step keeps its technical name from the code, and every line anchor is unchanged.

Read by the engine out of the whole source the signed run analysed. No language model wrote its process structure or its statements. Every statement names the lines it was read from, or says that it is not determined and why. The one exception is marked where it appears: business names and lanes from the naming stage are model proposals.

by kind: Step 24, Decision point 17, End 14, Start 11, Sub-process 10, Error boundary 8, End (early) 6, Service step 4, Message step 2, Call 1 · every one with its lines

The process, element by element
Element	Name	What it does	Lines
Startnd-33-0	NameSTART-OF-SELECTION	What it does	Linesline 41
Sub-processnd-34-0	NameCHECK_AUTHORITY	What it doesThe subroutines check_authority, read_requisition and check_requisition are called one after another, each without parameters.	Linesline 42
Sub-processnd-35-0	NameREAD_REQUISITION	What it doesAs at nd-34-0	Linesline 43
Sub-processnd-36-0	NameCHECK_REQUISITION	What it doesAs at nd-34-0	Linesline 44
Decision pointnd-37-0	NameCHECK gv_rejected = abap_false	What it doesProcessing continues only if the field gv_rejected is not set; otherwise the event block START-OF-SELECTION is exited at this point.	Linesline 45
Endnd-47-0	NameSTART-OF-SELECTION	What it doesThe subroutines decide_approval, notify_requester and write_result_list are called one after another, each without parameters.	Linesline 55
Sub-processnd-38-0	NameUPLOAD_ATTACHMENT	What it doesThe subroutines upload_attachment, read_vendor and check_vendor are called one after another, each without parameters.	Linesline 46
Sub-processnd-39-0	NameREAD_VENDOR	What it doesAs at nd-38-0	Linesline 47
Stepnd-40-0	NameCHECK_VENDOR	What it doesAs at nd-38-0	Linesline 48
Decision pointnd-41-0	NameCHECK gv_rejected = abap_false	What it doesAs at nd-37-0	Linesline 49
Sub-processnd-42-0	NameREAD_INFO_RECORD	What it doesThe subroutines read_info_record and check_price are called one after another, each without parameters.	Linesline 50
Stepnd-43-0	NameCHECK_PRICE	What it doesAs at nd-42-0	Linesline 51
Decision pointnd-44-0	NameCHECK gv_on_hold = abap_false	What it doesProcessing continues only if the field gv_on_hold is not set; otherwise the event block START-OF-SELECTION is exited at this point.	Linesline 52
Sub-processnd-45-0	NameDECIDE_APPROVAL	What it doesAs at nd-47-0	Linesline 53
Sub-processnd-46-0	NameNOTIFY_REQUESTER	What it doesAs at nd-47-0	Linesline 54
Stepnd-47-1	NameWRITE_RESULT_LIST	What it doesAs at nd-47-0	Linesline 55
Startnd-82-0	NameCHECK_AUTHORITY	What it does	Linesline 103
Stepnd-84-0	NameSELECT EBAN	What it doesThe purchasing group of the purchase requisition with the entered purchase requisition number and the entered bnfpo is read.	Lineslines 106 to 108
Decision pointnd-89-0	NameIF sy-subrc <> 0	What it doesWithout authorization for M_BANF_EKG, an error message is output.	Linesline 119
Endnd-90-0	NameE002	What it doesAs at nd-89-0	Linesline 120
Endnd-92-0	NameCHECK_AUTHORITY	What it does	Linesline 122
Error boundarynd-85-0	NameEBAN	What it doesWithout a hit, an error message is output.	Linesline 109
Endnd-86-0	NameE001	What it doesAs at nd-85-0	Linesline 110
Startnd-48-0	NameREAD_REQUISITION	What it does	Linesline 60
Stepnd-49-0	NameSELECT EBAN	What it doesPurchase requisitions with the entered purchase requisition number and the entered bnfpo are selected.	Lineslines 61 to 64
Decision pointnd-54-0	NameIF gs_eban-waers <> 'EUR'	What it doesFor currencies not equal to EUR, convert_to_eur is called.	Linesline 69
Service stepnd-55-0	NameCONVERT_TO_EUR	What it doesAs at nd-54-0	Linesline 70
Decision pointnd-57-0	NameIF gs_eban-dispo = 'EMG' OR gs_eban-bednr CP 'EMERG*'	What it does	Linesline 72
Endnd-60-0	NameREAD_REQUISITION	What it does	Linesline 75
Error boundarynd-50-0	NameEBAN	What it doesAs at nd-85-0	Linesline 65
Endnd-51-0	NameE001	What it doesAs at nd-85-0	Linesline 66
Startnd-61-0	NameCHECK_REQUISITION	What it does	Linesline 77
Decision pointnd-62-0	NameIF gs_eban-matnr IS INITIAL	What it doesWithout a material number, reject is called and the block is exited.	Linesline 78
Stepnd-63-0	NameREJECT	What it doesAs at nd-62-0	Linesline 79
End (early)nd-64-0	NameCHECK_REQUISITION (RETURN)	What it doesAs at nd-62-0	Linesline 80
Decision pointnd-66-0	NameIF gs_eban-frgkz = 'X'	What it doesIf the field gs_eban-frgkz is set, reject is called and the block is exited.	Linesline 82
Stepnd-67-0	NameREJECT	What it doesAs at nd-66-0	Linesline 83
End (early)nd-68-0	NameCHECK_REQUISITION (RETURN)	What it doesAs at nd-66-0	Linesline 84
Stepnd-70-0	NameCHECK_MATERIAL_STATUS	What it doesThe subroutine check_material_status is called; it reads plant records of materials.	Linesline 86
Decision pointnd-71-0	NameIF gv_rejected = abap_true	What it doesIf the field gv_rejected is set, the block is exited.	Linesline 87
End (early)nd-72-0	NameCHECK_REQUISITION (RETURN)	What it doesAs at nd-71-0	Linesline 88
Sub-processnd-74-0	NameCHECK_ACCOUNT_ASSIGNMENT	What it doesThe subroutine check_account_assignment is called.	Linesline 90
Decision pointnd-75-0	NameIF gv_rejected = abap_true	What it doesAs at nd-71-0	Linesline 91
End (early)nd-76-0	NameCHECK_REQUISITION (RETURN)	What it doesAs at nd-71-0	Linesline 92
Decision pointnd-78-0	NameIF gs_eban-werks = '1000'	What it does	Linesline 95
Endnd-81-0	NameCHECK_REQUISITION	What it does	Linesline 98
Startnd-131-0	NameCHECK_ACCOUNT_ASSIGNMENT	What it does	Linesline 201
Decision pointnd-132-0	Namegs_eban-knttp	What it does	Linesline 202
Stepnd-134-0	NameCHECK_COST_CENTER	What it doesThe subroutine check_cost_center is called; it reads cost centers.	Linesline 204
Endnd-143-0	NameCHECK_ACCOUNT_ASSIGNMENT	What it does	Linesline 214
Decision pointnd-136-0	NameIF gs_eban-aufnr IS INITIAL	What it doesOnly when the field gs_eban-knttp is F (L205): without an order number, reject is called.	Linesline 206
Stepnd-137-0	NameREJECT	What it doesAs at nd-136-0	Linesline 207
Stepnd-141-0	NameREJECT	What it doesThe subroutine reject is called; it outputs a message.	Linesline 212
Startnd-93-0	NameUPLOAD_ATTACHMENT	What it does	Linesline 124
Stepnd-97-0	NameGUI_UPLOAD	What it doesThe code passes p_file to GUI_UPLOAD and takes its output into lv_length.	Lineslines 129 to 140
Stepnd-101-0	NameSTORE_ATTACHMENT	What it doesIf the call of GUI_UPLOAD fails, a warning is output; otherwise store_attachment is called.	Linesline 144
Endnd-103-0	NameUPLOAD_ATTACHMENT	What it does	Linesline 146
Error boundarynd-97-1	NameGUI_UPLOAD	What it doesAs at nd-97-0	Lineslines 129 to 140
Startnd-104-0	NameREAD_VENDOR	What it does	Linesline 151
Stepnd-106-0	NameSELECT LFA1	What it doesSuppliers are selected.	Lineslines 154 to 155
Stepnd-111-0	NameSELECT LFM1	What it doesRecords from lfm1 are selected.	Lineslines 161 to 163
Endnd-115-0	NameREAD_VENDOR	What it does	Linesline 167
Error boundarynd-107-0	NameLFA1	What it doesWithout a hit, reject is called and the block is exited.	Linesline 156
Stepnd-108-0	NameREJECT	What it doesAs at nd-107-0	Linesline 157
End (early)nd-109-0	NameREAD_VENDOR (RETURN)	What it doesAs at nd-107-0	Linesline 158
Error boundarynd-112-0	NameLFM1	What it doesWithout a hit, reject is called.	Linesline 164
Stepnd-113-0	NameREJECT	What it doesAs at nd-112-0	Linesline 165
Startnd-164-0	NameREAD_INFO_RECORD	What it does	Linesline 250
Stepnd-167-0	NameSELECT EINA	What it doesRecords from eina are selected.	Lineslines 254 to 256
Stepnd-172-0	NameSELECT EINE	What it doesRecords from eine are selected.	Lineslines 262 to 265
Decision pointnd-173-0	NameIF sy-subrc = 0 AND ls_eine-peinh > 0	What it does	Linesline 266
Endnd-176-0	NameREAD_INFO_RECORD	What it does	Linesline 269
Error boundarynd-168-0	NameEINA	What it doesWithout a hit, the block is exited.	Linesline 257
End (early)nd-170-0	NameREAD_INFO_RECORD (RETURN)	What it doesAs at nd-168-0	Linesline 259
Startnd-208-0	NameDECIDE_APPROVAL	What it does	Linesline 324
Decision pointnd-209-0	NameIF gv_emergency = abap_true AND gv_amount <= '50000.00'	What it doesIf the field gv_emergency is set and the amount is at most 50000.00, find_department_head is called and request_approval is called.	Linesline 325
Stepnd-210-0	NameFIND_DEPARTMENT_HEAD	What it doesAs at nd-209-0	Linesline 326
Message stepnd-211-0	NameREQUEST_APPROVAL	What it doesAs at nd-209-0	Linesline 327
Decision pointnd-220-0	NameIF gv_approved = abap_true	What it doesIf the field gv_approved is set, create_purchase_order is called.	Linesline 336
Sub-processnd-221-0	NameCREATE_PURCHASE_ORDER	What it doesAs at nd-220-0	Linesline 337
Stepnd-223-0	NameLOG_APPROVAL	What it doesThe subroutine log_approval is called; it creates records in ZMM_PO_APPR.	Linesline 339
Endnd-224-0	NameDECIDE_APPROVAL	What it does	Linesline 340
Stepnd-213-0	NameCHECK_LIMIT	What it doesIf the field gv_skip_limit is not set, check_limit is called, find_manager is called and request_approval is called.	Linesline 329
Stepnd-214-0	NameFIND_MANAGER	What it doesAs at nd-213-0	Linesline 330
Message stepnd-215-0	NameREQUEST_APPROVAL	What it doesAs at nd-213-0	Linesline 331
Startnd-282-0	NameCREATE_PURCHASE_ORDER	What it does	Linesline 440
Service stepnd-314-0	NameBAPI_PO_CREATE1	What it doesA row is added and BAPI_PO_CREATE1 is called.	Lineslines 475 to 484
Decision pointnd-316-0	NameIF sy-subrc = 0	What it doesWith a hit, create_po_batch_input is called; otherwise BAPI_TRANSACTION_COMMIT is called.	Linesline 487
Callnd-317-0	NameCREATE_PO_BATCH_INPUT	What it doesAs at nd-316-0	Linesline 488
Endnd-322-0	NameCREATE_PURCHASE_ORDER	What it does	Linesline 496
Service stepnd-319-0	NameBAPI_TRANSACTION_COMMIT	What it doesAs at nd-316-0	Lineslines 490 to 492
Startnd-249-0	NameNOTIFY_REQUESTER	What it does	Linesline 379
Stepnd-252-0	NameSELECT ZMM_NOTIFY_CFG	What it doesThe field fm_name from zmm_notify_cfg is read.	Lineslines 383 to 384
Service stepnd-254-0	NameLV_FM_NAME	What it doesThe function module lv_fm_name is called. Only at runtime does lv_fm_name settle which function module this is.	Lineslines 386 to 391
Endnd-258-0	NameNOTIFY_REQUESTER	What it does	Linesline 395
Error boundarynd-253-0	NameZMM_NOTIFY_CFG	What it doesProcessing continues only if there is a hit; otherwise the subroutine notify_requester is exited at this point.	Linesline 385
Error boundarynd-254-1	NameLV_FM_NAME	What it doesAs at nd-254-0	Lineslines 386 to 391

in program order · every one with its lines

130 statements, in the order of the program; 22 repeats merged.

- The subroutine check_authority is called; it reads purchase requisitions and outputs a message.Source line 42
- The subroutines check_authority, read_requisition and check_requisition are called one after another, each without parameters.Source line 42Source line 43Source line 44
- The subroutine read_requisition is called; it reads purchase requisitions and outputs a message.Source line 43
- The subroutine check_requisition is called.Source line 44
- Processing continues only if the field gv_rejected is not set; otherwise the event block START-OF-SELECTION is exited at this point.Source line 45
- The subroutine upload_attachment is called; it calls GUI_UPLOAD and outputs a message.Source line 46
- The subroutines upload_attachment, read_vendor and check_vendor are called one after another, each without parameters.Source line 46Source line 47Source line 48
- The subroutine read_vendor is called; it reads suppliers and LFM1.Source line 47
- The subroutine check_vendor is called; it reads ZMM_VEND_BLOCK.Source line 48
- The subroutine read_info_record is called; it reads EINA and EINE.Source line 50
- The subroutines read_info_record and check_price are called one after another, each without parameters.Source line 50Source line 51
- The subroutine check_price is called.Source line 51
- Processing continues only if the field gv_on_hold is not set; otherwise the event block START-OF-SELECTION is exited at this point.Source line 52
- The subroutine decide_approval is called.Source line 53
- The subroutines decide_approval, notify_requester and write_result_list are called one after another, each without parameters.Source line 53Source line 54Source line 55
- The subroutine notify_requester is called; it reads ZMM_NOTIFY_CFG and outputs a message.Source line 54
- The subroutine write_result_list is called; it outputs list lines.Source line 55
- The report needs the include z_mm_po_notify. It is not contained in the supplied excerpt.Source line 363
- The report needs the include z_mm_po_log. It is not contained in the supplied excerpt.Source line 396
- Purchase requisitions with the entered purchase requisition number and the entered bnfpo are selected.Source lines 61 to 64
- Without a hit, an error message is output.Source line 65Source line 66
- The error message 001 is output.Source line 66
- For currencies not equal to EUR, convert_to_eur is called.Source line 69Source line 70
- The subroutine convert_to_eur is called; it calls CONVERT_TO_LOCAL_CURRENCY and outputs a message.Source line 70
- Without a material number, reject is called and the block is exited.Source line 78Source line 79Source line 80
- The subroutine reject is called; it outputs a message.Source line 79
- If the field gs_eban-frgkz is set, reject is called and the block is exited.Source line 82Source line 83Source line 84
- The subroutine check_material_status is called; it reads plant records of materials.Source line 86
- If the field gv_rejected is set, the block is exited.Source line 87Source line 88
- The subroutine check_account_assignment is called.Source line 90
- The purchasing group of the purchase requisition with the entered purchase requisition number and the entered bnfpo is read.Source lines 106 to 108
- The authorization for M_BANF_EKG is checked.Source lines 116 to 118
- Without authorization for M_BANF_EKG, an error message is output.Source line 119Source line 120
- The error message 002 is output.Source line 120
- Processing continues only if the field p_file is not empty; otherwise the subroutine upload_attachment is exited at this point.Source line 128
- The code passes p_file to GUI_UPLOAD and takes its output into lv_length.Source lines 129 to 140
- If the call of GUI_UPLOAD fails, a warning is output; otherwise store_attachment is called.Source line 141Source line 141Source line 142+2
- The warning 003 is output.Source line 142
- The subroutine store_attachment is called; it creates records in ZMM_PO_ATTACH.Source line 144
- Suppliers are selected.Source lines 154 to 155
- Without a hit, reject is called and the block is exited.Source line 156Source line 157Source line 158
- Records from lfm1 are selected.Source lines 161 to 163
- Without a hit, reject is called.Source line 164Source line 165
- The code passes sy-datum to CONVERT_TO_LOCAL_CURRENCY and takes its output into lv_local.Source lines 173 to 183
- If the return code (sy-subrc) is not 0, a warning is output.Source line 186Source line 187
- The warning 004 is output.Source line 187
- Cost centers are selected.Source lines 192 to 195
- The subroutine check_cost_center is called; it reads cost centers.Source line 204
- Only when the field gs_eban-knttp is F (L205): without an order number, reject is called.Source line 206Source line 207
- The supplier number from zmm_vend_block is read.Source lines 222 to 224
- With a hit, reject is called.Source line 225Source line 226
- The status message 005 is output.Source line 233
- A status message is output and log_approval is called.Source line 233Source line 234
- The subroutine log_approval is called; it creates records in ZMM_PO_APPR.Source line 234
- The field gv_message is set to Price deviates from the info record - buyer review, a row is changed, COMMIT WORK is executed and log_approval is called.Source line 239Source lines 240 to 242Source line 243+1
- The field gv_message is set to Price deviates from the info record - buyer review.Source line 239
- The field statu of the specified purchase requisition is changed. The code does not guarantee that a row is hit.Source lines 240 to 242
- COMMIT WORK persists the change.Source line 243
- Records from eina are selected.Source lines 254 to 256
- Without a hit, the block is exited.Source line 257Source line 258Source line 259
- Records from eine are selected.Source lines 262 to 265
- The field mmsta of the plant record of a material is read.Source lines 274 to 276
- If the field lv_mmsta is 01 or the field lv_mmsta is Z9, reject is called.Source line 277Source line 278
- Records from t16fs are selected.Source lines 289 to 290
- The return value of the method check_limit of cl_mm_internal is placed in lv_ok. Its business behaviour is not evidenced in the supplied code.Source lines 292 to 293
- Only when there is a hit (L291): if the field lv_ok is not set, the field gv_message is set to Amount above the release limit.Source line 294Source line 295
- Processing continues only if the field gv_ref_price is greater than 0; otherwise the subroutine check_price is exited at this point.Source line 308
- If the field lv_dev_pct is greater than 5, hold_for_buyer is called and the block is exited.Source line 315Source line 316Source line 317
- The subroutine hold_for_buyer is called; it changes purchase requisitions and commits with COMMIT WORK.Source line 316
- If the field gv_emergency is set and the amount is at most 50000.00, find_department_head is called and request_approval is called.Source line 325Source line 326Source line 327
- The subroutine find_department_head is called; it reads ZMM_DEPT_HEAD.Source line 326
- The subroutine request_approval is called; it calls SAP_WAPI_CREATE_EVENT and commits with COMMIT WORK.Source line 327
- If the field gv_skip_limit is not set, check_limit is called, find_manager is called and request_approval is called.Source line 328Source line 329Source line 330+1
- The subroutine check_limit is called; it reads T16FS.Source line 329
- The subroutine find_manager is called; it reads PA0105.Source line 330
- If the condition "gv_emergency = abap_true AND gv_amount <= '50000.00'" does not hold and the field gv_skip_limit is set, the field gv_message is set to Approved without limit check (central warehouse).Source line 332Source line 333Source line 334
- If the field gv_approved is set, create_purchase_order is called.Source line 336Source line 337
- The subroutine create_purchase_order is called; it calls BAPI_PO_CREATE1 and commits with BAPI_TRANSACTION_COMMIT.Source line 337
- The field uname from zmm_dept_head is read.Source lines 357 to 358
- Without a hit, the field cv_approver is set to PURCH_LEAD.Source line 359Source line 360
- If there is no hit, the field cv_approver is set to PURCH_LEAD.Source line 360Source line 359
- The personnel number from pa0105 is read.Source lines 368 to 370
- The field usrid from pa0105 is read.Source lines 371 to 373
- The field fm_name from zmm_notify_cfg is read.Source lines 383 to 384
- Processing continues only if there is a hit; otherwise the subroutine notify_requester is exited at this point.Source line 385
- The function module lv_fm_name is called. Only at runtime does lv_fm_name settle which function module this is.Source lines 386 to 391
- If the call of lv_fm_name fails, a warning is output.Source line 392Source line 393
- The warning 007 is output.Source line 393
- If the field p_test is set, the field gv_message is set to Test mode: approval simulated and the block is exited.Source line 407Source line 408Source line 409+1
- If the field p_test is set, the field gv_message is set to Test mode: approval simulated.Source line 409Source line 407
- The field ls_cont-element is set to APPROVER.Source line 414
- A row is added to lt_cont.Source line 416
- A row is added and the field ls_cont-element is set to ROLE.Source line 416Source line 417
- The field ls_cont-element is set to ROLE.Source line 417
- A row is added, SAP_WAPI_CREATE_EVENT is called and COMMIT WORK is executed.Source line 419Source lines 421 to 427Source line 428
- The function module SAP_WAPI_CREATE_EVENT is called.Source lines 421 to 427
- The field ls_header-comp_code is set to 1000.Source line 453
- The field ls_item-po_item is set to 00010.Source line 460
- A row is added to lt_item.Source line 466
- A row is added and the field ls_itemx-po_item is set to 00010.Source line 466Source line 467
- The field ls_itemx-po_item is set to 00010.Source line 467
- A row is added to lt_itemx.Source line 473
- A row is added and BAPI_PO_CREATE1 is called.Source line 473Source lines 475 to 484
- The code passes ls_header to BAPI_PO_CREATE1 and takes its output into gv_ebeln.Source lines 475 to 484
- A matching row is searched for in the table gt_return.Source line 486
- With a hit, create_po_batch_input is called; otherwise BAPI_TRANSACTION_COMMIT is called.Source line 487Source line 487Source line 488+3
- The subroutine create_po_batch_input is called; it calls transaction ME21N.Source line 488
- The function module BAPI_TRANSACTION_COMMIT is called.Source lines 490 to 492
- The field ls_bdc-program is set to SAPLMEGUI, the field ls_bdc-dynpro is set to 0014, the field ls_bdc-dynbegin is set to X and a row is added.Source line 503Source line 504Source line 505+1
- The field ls_bdc-program is set to SAPLMEGUI.Source line 503
- The field ls_bdc-dynpro is set to 0014.Source line 504
- The field ls_bdc-dynbegin is set to X.Source line 505
- A row is added to lt_bdc.Source line 506
- The field ls_bdc-fnam is set to MEPO_TOPLINE-SUPERFIELD.Source line 508
- A row is added, the field ls_bdc-fnam is set to BDC_OKCODE and the field ls_bdc-fval is set to =MESAVE.Source line 510Source line 511Source line 512+1
- The field ls_bdc-fnam is set to BDC_OKCODE.Source line 511
- The field ls_bdc-fval is set to =MESAVE.Source line 512
- Transaction ME21N is triggered via batch input in mode N and updated synchronously; it fills MEPO_TOPLINE-SUPERFIELD. Whether and what is persisted is decided by the called transaction.Source lines 515 to 518
- If transaction ME21N reports an error, the field gv_message is set to Purchase order could not be created; otherwise the field gv_message is set to Purchase order created by batch input.Source line 519Source line 519Source line 520+2
- If transaction ME21N reports an error, the field gv_message is set to Purchase order could not be created.Source line 520Source line 519
- If the return code (sy-subrc) is 0, the field gv_message is set to Purchase order created by batch input.Source line 522Source line 521
- Emergency purchase approval, sy-datum and sy-uzeit are output.Source line 542Source line 542Source line 542
- Emergency purchase approval is output. The output only proves that this point in the code was reached.Source line 542
- Requisition:, the purchase requisition number, p_bnfpo, Vendor: , the supplier number, the name, Amount EUR: , the amount, Approver: , gv_approver, Order: , the purchase order number, Result: and gv_message are output.Source line 545Source line 545Source line 545+11
- Requisition: is output. The output only proves that this point in the code was reached.Source line 545
- Vendor: is output. The output only proves that this point in the code was reached.Source line 546
- Amount EUR: is output. The output only proves that this point in the code was reached.Source line 547
- Approver: is output. The output only proves that this point in the code was reached.Source line 548
- Order: is output. The output only proves that this point in the code was reached.Source line 549
- Result: is output. The output only proves that this point in the code was reached.Source line 550

COMMIT WORK, does not wait — line 243
COMMIT WORK, does not wait — line 428
CALL FUNCTION BAPI_TRANSACTION_COMMIT, waits for the update — lines 490 to 492

A lane is the token the source writes, never a job title.

ReconstructedZ_MM_PO_APPROVALprogram — line 11
ReconstructedM_BANF_EKGauthority, from AUTHORITY-CHECK — lines 116 to 118

by type: Form Routine 25, Include 2, Report 1 · 0 high criticality

28 objects parsed out of the source, each with the lines it occupies — the anchors every later statement hangs on.

Objects parsed out of the demo source
Object	Type	Criticality	Lines
Z_MM_PO_APPROVAL	TypeReport	CriticalityMedium	Lines—
READ_REQUISITION	TypeForm Routine	CriticalityLow	Lines—
CHECK_REQUISITION	TypeForm Routine	CriticalityLow	Lines—
CHECK_AUTHORITY	TypeForm Routine	CriticalityLow	Lines—
UPLOAD_ATTACHMENT	TypeForm Routine	CriticalityLow	Lines—
READ_VENDOR	TypeForm Routine	CriticalityLow	Lines—
CONVERT_TO_EUR	TypeForm Routine	CriticalityLow	Lines—
CHECK_COST_CENTER	TypeForm Routine	CriticalityLow	Lines—
CHECK_ACCOUNT_ASSIGNMENT	TypeForm Routine	CriticalityLow	Lines—
CHECK_VENDOR	TypeForm Routine	CriticalityLow	Lines—
REJECT	TypeForm Routine	CriticalityLow	Lines—
HOLD_FOR_BUYER	TypeForm Routine	CriticalityLow	Lines—
READ_INFO_RECORD	TypeForm Routine	CriticalityLow	Lines—
CHECK_MATERIAL_STATUS	TypeForm Routine	CriticalityLow	Lines—
CHECK_LIMIT	TypeForm Routine	CriticalityLow	Lines—
CHECK_PRICE	TypeForm Routine	CriticalityLow	Lines—
DECIDE_APPROVAL	TypeForm Routine	CriticalityLow	Lines—
LOG_APPROVAL	TypeForm Routine	CriticalityLow	Lines—
FIND_DEPARTMENT_HEAD	TypeForm Routine	CriticalityLow	Lines—
Z_MM_PO_NOTIFY	TypeInclude	CriticalityLow	Lines—
FIND_MANAGER	TypeForm Routine	CriticalityLow	Lines—
NOTIFY_REQUESTER	TypeForm Routine	CriticalityLow	Lines—
Z_MM_PO_LOG	TypeInclude	CriticalityLow	Lines—
REQUEST_APPROVAL	TypeForm Routine	CriticalityLow	Lines—
CREATE_PURCHASE_ORDER	TypeForm Routine	CriticalityLow	Lines—
CREATE_PO_BATCH_INPUT	TypeForm Routine	CriticalityLow	Lines—
STORE_ATTACHMENT	TypeForm Routine	CriticalityLow	Lines—
WRITE_RESULT_LIST	TypeForm Routine	CriticalityLow	Lines—

3 written (2 custom, 1 SAP standard), 11 read, 6 referenced · 3 high risk