MM Report Custom development ALV report

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.

TableRoleJoinSystem
EKKOPurchasing Document HeaderOrder header: release group, strategy, status and creation date (driving table)—ECC + S/4
EKPOPurchasing Document ItemOrder items: net value total; deleted items are excludedEKPO-EBELN = EKKO-EBELNECC + S/4
T16FSRelease StrategiesOrdered release codes of the release strategyT16FS-FRGGR = EKKO-FRGGR AND T16FS-FRGSX = EKKO-FRGSXECC + S/4
CDHDRChange Document HeaderDate and user of the last release stepCDHDR-OBJECTCLAS = 'EINKBELEG' AND CDHDR-OBJECTID = EKKO-EBELNECC + S/4
LFA1Vendor Master (General Section)Vendor nameLFA1-LIFNR = EKKO-LIFNRECC + S/4
I_PurchaseOrderAPI01Purchase Order (API)In S/4HANA it can replace EKKO with a clean core approachPurchaseOrder = EKKO-EBELNS/4HANA only

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_BUKRSCompany codeRange / multipleEKKO-BUKRSYes1000
S_EKORGPurchasing organizationRange / multipleEKKO-EKORGNo1000
S_EKGRPPurchasing groupRange / multipleEKKO-EKGRPNo001
S_BSARTOrder typeRange / multipleEKKO-BSARTNoNB
S_FRGGRRelease groupRange / multipleEKKO-FRGGRNo01
S_FRGSXRelease strategyRange / multipleEKKO-FRGSXNoS1
S_BEDATOrder date rangeRange / multipleEKKO-BEDATNo01.09.2026 – 16.11.2026
P_KEYDTKey date for waiting time (default: today)Single value—Yes17.11.2026
P_MINDYMinimum days waitingSingle value—No3

Output columns

#ColumnSource
1Purchase orderEKKO-EBELN
2Order typeEKKO-BSART
3Vendor nameLFA1-NAME1
4Purchasing groupEKKO-EKGRP
5Order dateEKKO-BEDAT
6Created byEKKO-ERNAM
7Release groupEKKO-FRGGR
8StrategyEKKO-FRGSX
9Steps completedEKKO-FRGZU
10Next release codeCalculated T16FS-FRGCn; n = number of filled positions in EKKO-FRGZU + 1
11Order valueCalculated Σ EKPO-NETWR (items with LOEKZ blank)
12CurrencyEKKO-WAERS
13Waiting sinceCalculated CDHDR-UDATE of the last release; otherwise EKKO-AEDAT
14Days waitingCalculated Key date − waiting since
15Age bucketCalculated 0–3 / 4–7 / 8–15 / 15+ days

Sample output

Purchase orderOrder typeVendor namePurchasing groupOrder dateCreated byRelease groupStrategySteps completedNext release codeOrder valueCurrencyWaiting sinceDays waitingAge bucket
4500013210NBAtlas Ambalaj00111/03/2026BUYER0101S1XZ2184,500TRY11/05/2026128–15 days
4500013244NBDelta Metal00211/10/2026BUYER0201S2Z146,200TRY11/10/202674–7 days
4500013198NBEge Kimya00110/21/2026BUYER0102S3XXZ31,250,000TRY10/28/20262015+ days
4500013251FOMarmara Lojistik00311/14/2026BUYER0301S1Z138,750EUR11/14/202630–3 days
A view built with fictional sample data; not real system data.

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.

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

MM Package Custom

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 …

4 components · v1.0

Related reports

MM Report Custom ALV report

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 …

EKKO · EKPO · EKET · LFA1

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.

Related report: Purchase Orders Awaiting Release Approval Aging Report