Purchase Requisition to Payment End-to-End Document Flow and Cycle Time Report
Short answer: A custom ALV report that follows each purchase requisition item through the purchase order, goods receipt, invoice and payment on a single row and calculates the days between the steps. Purchasing and accounting teams see where the process gets stuck and how long requisition-to-payment takes on average.
- Estimated effort
- M · 5–7 working days
- System
- ECC and S/4HANA
- Tables
- 10
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
ME5A shows the requisition and the linked order number, and ME80FN shows the goods receipts and invoices in the order history; but no standard list puts requisition, order, goods receipt, invoice and payment dates on the same row and calculates the time between the steps. Payment information requires a separate trip to FBL1N. The custom report builds the chain in one run and flags the step that is still open.
Who uses it? Purchasing managers, accounts payable, process owners and internal audit.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| EBANPurchase Requisition | Purchase requisition item: requisition and release date (driving table) | — | ECC + S/4 |
| EKPOPurchasing Document Item | Order item created from the requisition | EKPO-BANFN = EBAN-BANFN AND EKPO-BNFPO = EBAN-BNFPO | ECC + S/4 |
| EKKOPurchasing Document Header | Order date, vendor and company code | EKKO-EBELN = EKPO-EBELN | ECC + S/4 |
| EKBEPurchasing Document History | Order history: goods receipt and invoice dates | EKBE-EBELN = EKPO-EBELN AND EKBE-EBELP = EKPO-EBELP | ECC + S/4 |
| RBKPDocument Header: Incoming Invoice | Logistics invoice header: posting date and payment block | RBKP-BELNR = EKBE-BELNR AND RBKP-GJAHR = EKBE-GJAHR | ECC + S/4 |
| BKPFAccounting Document Header | FI document of the invoice | BKPF-AWKEY = RBKP-BELNR + RBKP-GJAHR | ECC + S/4 |
| BSAKVendor Cleared Items | Cleared vendor item: payment date and payment document | BSAK-BUKRS = BKPF-BUKRS AND BSAK-BELNR = BKPF-BELNR AND BSAK-GJAHR = BKPF-GJAHR | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor name | LFA1-LIFNR = EKKO-LIFNR | ECC + S/4 |
| I_PurchaseRequisitionItemAPI01Purchase Requisition Item (API) | Released CDS view that can replace EBAN in S/4HANA | PurchaseRequisition = EBAN-BANFN | S/4HANA only |
| I_SupplierInvoiceAPI01Supplier Invoice (API) | Can replace RBKP in S/4HANA | SupplierInvoice = RBKP-BELNR | S/4HANA only |
S/4HANA notes
- BSAK → I_OperationalAcctgDocItem: In S/4HANA BSAK is not filled as a separate table; it is read through a compatibility view of the same name. For new developments the I_OperationalAcctgDocItem CDS view is recommended.
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_WERKS | Plant | Range / multiple | EBAN-WERKS | Yes | 1000 |
| S_EKGRP | Purchasing group | Range / multiple | EBAN-EKGRP | No | 001 |
| S_BSART | Requisition type | Range / multiple | EBAN-BSART | No | NB |
| S_BADAT | Requisition date range | Range / multiple | EBAN-BADAT | Yes | 01.07.2026 – 31.10.2026 |
| S_AFNAM | Requisitioner | Range / multiple | EBAN-AFNAM | No | BAKIM |
| S_LIFNR | Vendor | Range / multiple | EKKO-LIFNR | No | 100245 |
| P_OPEN | Only chains not yet paid | Checkbox | — | No | X |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Requisition | EBAN-BANFN |
| 2 | Req. item | EBAN-BNFPO |
| 3 | Release date | EBAN-FRGDT |
| 4 | Purchase order | EKPO-EBELN |
| 5 | Order date | EKKO-BEDAT |
| 6 | Vendor name | LFA1-NAME1 |
| 7 | First goods receipt | Calculated Earliest EKBE-BUDAT (VGABE = 1) |
| 8 | Invoice document | RBKP-BELNR |
| 9 | Invoice posting date | RBKP-BUDAT |
| 10 | Payment date | BSAK-AUGDT |
| 11 | Req. → order (days) | Calculated EKKO-BEDAT − EBAN-FRGDT |
| 12 | Order → GR (days) | Calculated First goods receipt − EKKO-BEDAT |
| 13 | GR → invoice (days) | Calculated RBKP-BUDAT − first goods receipt |
| 14 | Invoice → payment (days) | Calculated BSAK-AUGDT − RBKP-BUDAT |
| 15 | Total cycle (days) | Calculated Date of the last step reached − EBAN-FRGDT |
| 16 | Open step | Calculated First step not yet reached: order, goods receipt, invoice, payment or completed |
Sample output
| Requisition | Req. item | Release date | Purchase order | Order date | Vendor name | First goods receipt | Invoice document | Invoice posting date | Payment date | Req. → order (days) | Order → GR (days) | GR → invoice (days) | Invoice → payment (days) | Total cycle (days) | Open step |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0010004521 | 00010 | 09/02/2026 | 4500012890 | 09/05/2026 | Atlas Ambalaj | 09/19/2026 | 5105600112 | 09/22/2026 | 10/22/2026 | 3 | 14 | 3 | 30 | 50 | Completed |
| 0010004587 | 00020 | 09/15/2026 | 4500013015 | 09/24/2026 | Delta Metal | 10/14/2026 | 5105600398 | 10/30/2026 | 9 | 20 | 16 | 45 | Payment | ||
| 0010004633 | 00010 | 10/01/2026 | 4500013102 | 10/03/2026 | Ege Kimya | 10/27/2026 | 2 | 24 | 47 | Invoice | |||||
| 0010004702 | 00010 | 10/20/2026 | 28 | Order |
How does the report work?
- EBAN is read by plant, purchasing group, document type and requisition date; deleted items (LOEKZ) are skipped.
- Order items linked to the requisition are found via EKPO-BANFN/BNFPO; the order date and vendor come from EKKO. If a requisition is split over several orders, each order item becomes its own row.
- The first goods receipt (VGABE = 1) and first invoice (VGABE = 2) dates are taken from EKBE; reversals (SHKZG) are taken into account.
- The invoice document is read from RBKP; the FI document is found via BKPF-AWKEY = RBKP-BELNR + RBKP-GJAHR. The clearing date and document of the vendor line come from BSAK (payment date).
- Durations: requisition release → order, order → goods receipt, goods receipt → invoice, invoice → payment and total. The first step not yet reached is shown as the “open step”.
Performance notes
Always restrict the EBAN selection by requisition date and plant. Read EKBE in one pass for the selected order items. For BKPF access via AWKEY, supply AWTYP = RMRP together with AWKEY; on large systems a nightly background job is recommended.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document The requisition opens ME53N, the order ME23N, the invoice MIR4 and the payment document FB03.
- Export to Excel
- Runs as a background job
- Send the result by email A monthly cycle time summary can be sent to purchasing and accounting managers.
Authorization objects
- M_BANF_WRKRequisition display authorization by plant
- M_BEST_WRKOrder display authorization by plant
- F_BKPF_BUKAccounting document display authorization by company code
Frequently asked questions
Which date is used when an order is invoiced several times?
By default the first invoice and its payment are shown. The last invoice date can be chosen on the selection screen; for partly invoiced orders both dates can be added to the ALV as extra columns.
Do orders created without a requisition appear?
No, the report starts from requisition items. If the share of orders without a requisition matters for process compliance, an extra option can show orders with an empty EKPO-BANFN in a separate list.
Where is payment data read from in S/4HANA?
In S/4HANA, BSAK is a compatibility view and keeps working; for a clean core approach the clearing can be taken from ACDOCA or released CDS views. I_PurchaseRequisitionItemAPI01 and I_SupplierInvoiceAPI01 can be used for requisitions and invoices.
Packages that include this solution
Purchasing Approval and Cycle Time Pack
A four-component pack that shows where purchasing waits between requisition and payment: released requisitions not yet ordered, purchase orders …
Related reports
Vendor Open Items Aging Report
A custom ALV report that ages vendor open items by net due date and spreads the amounts into not-due, 0–30, 31–60, 61–90 and 90+ day buckets. The …
Goods Received Not Invoiced Purchase Orders Report (GR/IR)
A custom ALV report that compares received and invoiced quantity and amount per purchase order item and lists items that were received but not …
Released Purchase Requisitions Not Yet Converted to Purchase Orders Report
A custom ALV report that lists released purchase requisition items not yet converted to a purchase order, with open quantity, open value and days …
Purchase Orders Awaiting Release Approval Aging Report
A custom ALV report that lists purchase orders held by a release (approval) strategy, together with the next release code, the order value and how …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.