# Purchase Requisition to Payment End-to-End Document Flow and Cycle Time Report

> 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.

- Type: Report, Custom development, ALV report
- Module: MM
- Estimated effort: M (5–7 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/purchase-requisition-to-payment-document-flow-report/


## 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.

### Closest standard alternatives

- ME5A: Lists requisitions with the linked order number; no goods receipt, invoice or payment dates.
- ME80FN: Shows the order history but does not start from the requisition and gives no payment data or step durations.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| EBAN | Purchase requisition item: requisition and release date (driving table) | Read | - | ECC + S/4 |
| EKPO | Order item created from the requisition | Read | EKPO-BANFN = EBAN-BANFN AND EKPO-BNFPO = EBAN-BNFPO | ECC + S/4 |
| EKKO | Order date, vendor and company code | Read | EKKO-EBELN = EKPO-EBELN | ECC + S/4 |
| EKBE | Order history: goods receipt and invoice dates | Read | EKBE-EBELN = EKPO-EBELN AND EKBE-EBELP = EKPO-EBELP | ECC + S/4 |
| RBKP | Logistics invoice header: posting date and payment block | Read | RBKP-BELNR = EKBE-BELNR AND RBKP-GJAHR = EKBE-GJAHR | ECC + S/4 |
| BKPF | FI document of the invoice | Read | BKPF-AWKEY = RBKP-BELNR + RBKP-GJAHR | ECC + S/4 |
| BSAK | Cleared vendor item: payment date and payment document | Read | BSAK-BUKRS = BKPF-BUKRS AND BSAK-BELNR = BKPF-BELNR AND BSAK-GJAHR = BKPF-GJAHR | ECC + S/4 |
| LFA1 | Vendor name | Read | LFA1-LIFNR = EKKO-LIFNR | ECC + S/4 |
| I_PurchaseRequisitionItemAPI01 | Released CDS view that can replace EBAN in S/4HANA | Read | PurchaseRequisition = EBAN-BANFN | S/4HANA only |
| I_SupplierInvoiceAPI01 | Can replace RBKP in S/4HANA | Read | SupplierInvoice = RBKP-BELNR | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_WERKS | Plant | Range / multiple | EBAN-WERKS | Yes |
| S_EKGRP | Purchasing group | Range / multiple | EBAN-EKGRP | No |
| S_BSART | Requisition type | Range / multiple | EBAN-BSART | No |
| S_BADAT | Requisition date range | Range / multiple | EBAN-BADAT | Yes |
| S_AFNAM | Requisitioner | Range / multiple | EBAN-AFNAM | No |
| S_LIFNR | Vendor | Range / multiple | EKKO-LIFNR | No |
| P_OPEN | Only chains not yet paid | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Requisition | EBAN-BANFN |
| Req. item | EBAN-BNFPO |
| Release date | EBAN-FRGDT |
| Purchase order | EKPO-EBELN |
| Order date | EKKO-BEDAT |
| Vendor name | LFA1-NAME1 |
| First goods receipt | Calculated: Earliest EKBE-BUDAT (VGABE = 1) |
| Invoice document | RBKP-BELNR |
| Invoice posting date | RBKP-BUDAT |
| Payment date | BSAK-AUGDT |
| Req. → order (days) | Calculated: EKKO-BEDAT − EBAN-FRGDT |
| Order → GR (days) | Calculated: First goods receipt − EKKO-BEDAT |
| GR → invoice (days) | Calculated: RBKP-BUDAT − first goods receipt |
| Invoice → payment (days) | Calculated: BSAK-AUGDT − RBKP-BUDAT |
| Total cycle (days) | Calculated: Date of the last step reached − EBAN-FRGDT |
| Open step | Calculated: First step not yet reached: order, goods receipt, invoice, payment or completed |

## How does the report work?

1. EBAN is read by plant, purchasing group, document type and requisition date; deleted items (LOEKZ) are skipped.
2. 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.
3. The first goods receipt (VGABE = 1) and first invoice (VGABE = 2) dates are taken from EKBE; reversals (SHKZG) are taken into account.
4. 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).
5. 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".

## Authorization objects

- M_BANF_WRK: Requisition display authorization by plant
- M_BEST_WRK: Order display authorization by plant
- F_BKPF_BUK: Accounting 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=mm-pr-to-payment-document-flow
