Purchase Orders Awaiting Release Approval Aging Report
Short answer: 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 many days the order has been waiting for approval. Purchasing managers see at which approval step and at what value orders pile up, and can chase overdue approvals.
- Estimated effort
- S · 3–4 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
ME28 lists the orders waiting for one release code for collective release, but it does not show how many days an order has been waiting at that step, who is next in line or the total waiting value per release group. In ME2N the release status is only a dynamic selection and no waiting time is calculated. The custom report shows every approval step on one screen with age buckets and value totals.
Who uses it? Purchasing managers, buyers, approvers and internal control teams.
Closest standard alternatives
- ME28 Release Purchase Orders (Collective). Releases the orders waiting for one release code in bulk; no waiting time, next approver or value summary.
- ME2N Purchasing Documents per Document Number. The release status can be filtered via dynamic selection, but the approval step and days waiting are not calculated.
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| EKKOPurchasing Document Header | Order header: release group, strategy, status and creation date (driving table) | — | ECC + S/4 |
| EKPOPurchasing Document Item | Order items: net value total; deleted items are excluded | EKPO-EBELN = EKKO-EBELN | ECC + S/4 |
| T16FSRelease Strategies | Ordered release codes of the release strategy | T16FS-FRGGR = EKKO-FRGGR AND T16FS-FRGSX = EKKO-FRGSX | ECC + S/4 |
| CDHDRChange Document Header | Date and user of the last release step | CDHDR-OBJECTCLAS = 'EINKBELEG' AND CDHDR-OBJECTID = EKKO-EBELN | ECC + S/4 |
| LFA1Vendor Master (General Section) | Vendor name | LFA1-LIFNR = EKKO-LIFNR | ECC + S/4 |
| I_PurchaseOrderAPI01Purchase Order (API) | In S/4HANA it can replace EKKO with a clean core approach | PurchaseOrder = EKKO-EBELN | S/4HANA only |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | EKKO-BUKRS | Yes | 1000 |
| S_EKORG | Purchasing organization | Range / multiple | EKKO-EKORG | No | 1000 |
| S_EKGRP | Purchasing group | Range / multiple | EKKO-EKGRP | No | 001 |
| S_BSART | Order type | Range / multiple | EKKO-BSART | No | NB |
| S_FRGGR | Release group | Range / multiple | EKKO-FRGGR | No | 01 |
| S_FRGSX | Release strategy | Range / multiple | EKKO-FRGSX | No | S1 |
| S_BEDAT | Order date range | Range / multiple | EKKO-BEDAT | No | 01.09.2026 – 16.11.2026 |
| P_KEYDT | Key date for waiting time (default: today) | Single value | — | Yes | 17.11.2026 |
| P_MINDY | Minimum days waiting | Single value | — | No | 3 |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Purchase order | EKKO-EBELN |
| 2 | Order type | EKKO-BSART |
| 3 | Vendor name | LFA1-NAME1 |
| 4 | Purchasing group | EKKO-EKGRP |
| 5 | Order date | EKKO-BEDAT |
| 6 | Created by | EKKO-ERNAM |
| 7 | Release group | EKKO-FRGGR |
| 8 | Strategy | EKKO-FRGSX |
| 9 | Steps completed | EKKO-FRGZU |
| 10 | Next release code | Calculated T16FS-FRGCn; n = number of filled positions in EKKO-FRGZU + 1 |
| 11 | Order value | Calculated Σ EKPO-NETWR (items with LOEKZ blank) |
| 12 | Currency | EKKO-WAERS |
| 13 | Waiting since | Calculated CDHDR-UDATE of the last release; otherwise EKKO-AEDAT |
| 14 | Days waiting | Calculated Key date − waiting since |
| 15 | Age bucket | Calculated 0–3 / 4–7 / 8–15 / 15+ days |
Sample output
| Purchase order | Order type | Vendor name | Purchasing group | Order date | Created by | Release group | Strategy | Steps completed | Next release code | Order value | Currency | Waiting since | Days waiting | Age bucket |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 4500013210 | NB | Atlas Ambalaj | 001 | 11/03/2026 | BUYER01 | 01 | S1 | X | Z2 | 184,500 | TRY | 11/05/2026 | 12 | 8–15 days |
| 4500013244 | NB | Delta Metal | 002 | 11/10/2026 | BUYER02 | 01 | S2 | Z1 | 46,200 | TRY | 11/10/2026 | 7 | 4–7 days | |
| 4500013198 | NB | Ege Kimya | 001 | 10/21/2026 | BUYER01 | 02 | S3 | XX | Z3 | 1,250,000 | TRY | 10/28/2026 | 20 | 15+ days |
| 4500013251 | FO | Marmara Lojistik | 003 | 11/14/2026 | BUYER03 | 01 | S1 | Z1 | 38,750 | EUR | 11/14/2026 | 3 | 0–3 days |
How does the report work?
- EKKO is read by company code, purchasing organization, purchasing group and document type; only orders whose release is not yet complete (FRGRL = X) and that carry a release group/strategy (FRGGR, FRGSX) remain.
- The release codes of the strategy are read in order from T16FS (FRGC1–FRGC8). The number of filled positions in EKKO-FRGZU gives the completed step; the code in the next position becomes the “next release code”.
- The order value is the NETWR total of the EKPO items that are not deleted (LOEKZ blank).
- Waiting since: the date (UDATE) of the last release change in CDHDR for object class EINKBELEG; if no release has been made yet, the EKKO-AEDAT creation date.
- Days waiting = key date − waiting since, grouped into 0–3, 4–7, 8–15 and 15+ day buckets. The vendor name comes from LFA1; the ALV shows subtotals per release code.
Performance notes
Start the EKKO selection with FRGRL = X; this greatly reduces the number of orders read. Read CDHDR only for the selected orders with the OBJECTCLAS and OBJECTID key via FOR ALL ENTRIES. T16FS is a small table; buffer it once.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the order number opens ME29N; an approver with authorization can release the order from there.
- Export to Excel
- Runs as a background job
- Send the result by email Every morning the list grouped by next release code can be sent to the relevant approvers.
Authorization objects
- M_BEST_BSADisplay authorization by order type
- M_BEST_EKODisplay authorization by purchasing organization
- M_BEST_EKGDisplay authorization by purchasing group
- M_EINK_FRGRelease code and group authorization is checked when jumping to ME29N
Frequently asked questions
How is the number of days waiting determined?
The last release change for the order is taken from CDHDR (object class EINKBELEG) and its date becomes the waiting start. If no release has been given yet, the order creation date (EKKO-AEDAT) is used.
Does it work with flexible workflow in S/4HANA?
The classic release strategy is still supported in S/4HANA and the report works with the same fields. If flexible workflow is used, the approval step is read from the workflow items instead; this adaptation adds 1–2 days to the estimate.
Can approvers receive automatic reminders?
Yes. The report runs in the background, splits the list by next release code and emails each list to the address linked to that code. The mapping from release code to person comes from the customer's authorization role design.
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
Open Purchase Orders by Vendor Report
A custom ALV report that shows, per vendor, the quantity not yet received, the open order value and the days of delay since the delivery date in a …
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 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 …
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.