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

- Type: Report, Custom development, ALV report
- Module: MM
- Estimated effort: S (3–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/purchase-orders-awaiting-release-approval-report/


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

### Closest standard alternatives

- ME28: Releases the orders waiting for one release code in bulk; no waiting time, next approver or value summary.
- ME2N: The release status can be filtered via dynamic selection, but the approval step and days waiting are not calculated.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| EKKO | Order header: release group, strategy, status and creation date (driving table) | Read | - | ECC + S/4 |
| EKPO | Order items: net value total; deleted items are excluded | Read | EKPO-EBELN = EKKO-EBELN | ECC + S/4 |
| T16FS | Ordered release codes of the release strategy | Read | T16FS-FRGGR = EKKO-FRGGR AND T16FS-FRGSX = EKKO-FRGSX | ECC + S/4 |
| CDHDR | Date and user of the last release step | Read | CDHDR-OBJECTCLAS = 'EINKBELEG' AND CDHDR-OBJECTID = EKKO-EBELN | ECC + S/4 |
| LFA1 | Vendor name | Read | LFA1-LIFNR = EKKO-LIFNR | ECC + S/4 |
| I_PurchaseOrderAPI01 | In S/4HANA it can replace EKKO with a clean core approach | Read | PurchaseOrder = EKKO-EBELN | S/4HANA only |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_BUKRS | Company code | Range / multiple | EKKO-BUKRS | Yes |
| S_EKORG | Purchasing organization | Range / multiple | EKKO-EKORG | No |
| S_EKGRP | Purchasing group | Range / multiple | EKKO-EKGRP | No |
| S_BSART | Order type | Range / multiple | EKKO-BSART | No |
| S_FRGGR | Release group | Range / multiple | EKKO-FRGGR | No |
| S_FRGSX | Release strategy | Range / multiple | EKKO-FRGSX | No |
| S_BEDAT | Order date range | Range / multiple | EKKO-BEDAT | No |
| P_KEYDT | Key date for waiting time (default: today) | Single value | - | Yes |
| P_MINDY | Minimum days waiting | Single value | - | No |

## Output columns

| Column | Source |
|---|---|
| Purchase order | EKKO-EBELN |
| Order type | EKKO-BSART |
| Vendor name | LFA1-NAME1 |
| Purchasing group | EKKO-EKGRP |
| Order date | EKKO-BEDAT |
| Created by | EKKO-ERNAM |
| Release group | EKKO-FRGGR |
| Strategy | EKKO-FRGSX |
| Steps completed | EKKO-FRGZU |
| Next release code | Calculated: T16FS-FRGCn; n = number of filled positions in EKKO-FRGZU + 1 |
| Order value | Calculated: Σ EKPO-NETWR (items with LOEKZ blank) |
| Currency | EKKO-WAERS |
| Waiting since | Calculated: CDHDR-UDATE of the last release; otherwise EKKO-AEDAT |
| Days waiting | Calculated: Key date − waiting since |
| Age bucket | Calculated: 0–3 / 4–7 / 8–15 / 15+ days |

## How does the report work?

1. 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.
2. 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".
3. The order value is the NETWR total of the EKPO items that are not deleted (LOEKZ blank).
4. 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.
5. 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.

## Authorization objects

- M_BEST_BSA: Display authorization by order type
- M_BEST_EKO: Display authorization by purchasing organization
- M_BEST_EKG: Display authorization by purchasing group
- M_EINK_FRG: Release 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=mm-po-release-pending-aging
