MM Report Custom development ALV report

Vendor On-Time Delivery Performance Report

Short answer: A custom ALV report that compares every goods receipt posted in the selected period with the delivery date of the purchase order and shows, per vendor, the number of on-time, early and late receipts, the on-time rate, the average and maximum delay and the in-full rate. It gives a measurable delivery scorecard in one list for vendor evaluation and supplier meetings.

Estimated effort
M · 4–6 working days
System
ECC and S/4HANA
Tables
5
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

ME2N and ME80FN show the order history item by item; they do not calculate the difference between the goods receipt date and the delivery date and give no rate per vendor. Standard vendor evaluation (the ME61–ME65 family) needs scoring criteria to be set up and periodic evaluation runs, and does not show tolerance days, early delivery and the in-full rate separately. Companies therefore match MB51 and ME2N output in Excel and build the monthly scorecard by hand.

Who uses it? Purchasing managers, supplier development and quality teams, supply chain planners.

Closest standard alternatives

  • ME80FN General Analyses of Purchasing Documents. Lists the order history flexibly; does not calculate delay days or an on-time rate per vendor.
  • MB51 Material Document List. Lists goods receipt documents; does not show the delivery date of the order.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
EKKOPurchasing Document HeaderOrder header: vendor, purchasing organization, document type (driving table)—ECC + S/4
EKPOPurchasing Document ItemOrder item: material, plant, material groupEKPO-EBELN = EKKO-EBELNECC + S/4
EKETPurchasing Schedule LinesSchedule line: delivery date, statistical date, scheduled quantityEKET-EBELN = EKPO-EBELN AND EKET-EBELP = EKPO-EBELPECC + S/4
EKBEPurchasing Document HistoryOrder history: goods receipt date, quantity and valueEKBE-EBELN = EKPO-EBELN AND EKBE-EBELP = EKPO-EBELPECC + S/4
LFA1Vendor Master (General Section)Vendor nameLFA1-LIFNR = EKKO-LIFNRECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_EKORGPurchasing organizationRange / multipleEKKO-EKORGYes1000
S_WERKSPlantRange / multipleEKPO-WERKSNo1100
S_LIFNRVendorRange / multipleEKKO-LIFNRNo100387
S_BUDATGoods receipt posting dateRange / multipleEKBE-BUDATYes01.01.2026 – 31.10.2026
S_MATKLMaterial groupRange / multipleEKPO-MATKLNo01
S_BSARTOrder document typeRange / multipleEKKO-BSARTNoNB
P_EARLYEarly delivery tolerance (days)Single value—No3
P_LATELate delivery tolerance (days)Single value—No2
R_EINDTCompare with delivery date (otherwise statistical date)Radio button—NoX

Output columns

#ColumnSource
1VendorEKKO-LIFNR
2Vendor nameLFA1-NAME1
3Purchasing org.EKKO-EKORG
4PlantEKPO-WERKS
5ReceiptsCalculated Goods receipt lines counted in the period (net of reversals)
6On timeCalculated Receipts whose delay is within the tolerance window
7EarlyCalculated Delay < −early tolerance
8LateCalculated Delay > late tolerance
9On-time rate (%)Calculated On time ÷ receipts × 100
10Avg. delay (days)Calculated Average delay of late receipts (EKBE-BUDAT − EKET-EINDT)
11Max. delayCalculated Largest delay in days among late receipts
12In-full rate (%)Calculated Schedule lines received in full within tolerance ÷ schedule lines due × 100
13Received valueCalculated Σ EKBE-DMBTR (VGABE = 1, reversals negative)
14CurrencyEKBE-HSWAE
15GradeCalculated On-time rate ≥ 95% A, ≥ 85% B, otherwise C

Sample output

VendorVendor namePurchasing org.PlantReceiptsOn timeEarlyLateOn-time rate (%)Avg. delay (days)Max. delayIn-full rate (%)Received valueCurrencyGrade
100245Atlas Ambalaj100011001421362495.803.50698.601,845,200TRYA
100387Delta Metal10001100887151280.709.2027912,410,750TRYC
100512Ege Kimya1000120064573489.104.809100356,900TRYB
100618Marmara Kablo1000110037330489.202.30594.60512,300TRYB
A view built with fictional sample data; not real system data.

How does the report work?

  1. EKKO and EKPO are read by purchasing organization, document type, vendor, plant and material group; deleted items (LOEKZ) and items without goods receipt are excluded.
  2. Goods receipts in the period (VGABE = 1) are read from EKBE; reversals (SHKZG = H) are deducted from the quantity of the receipt they cancel.
  3. Each receipt quantity is allocated in date order (FIFO) to the first EKET schedule line not yet covered. The reference date is EKET-EINDT (delivery date) or EKET-SLFDT (statistical delivery date), depending on the radio button.
  4. Delay = EKBE-BUDAT − reference date. If the delay lies between −early tolerance and +late tolerance the receipt is on time, below it early, above it late. A schedule line counts as in full when its quantity was received completely within the late tolerance.
  5. Results are summed by vendor, purchasing organization and plant; an on-time rate of ≥ 95% gives grade A, ≥ 85% grade B and below that grade C (thresholds are set during installation). The vendor line drills down to item detail.

Performance notes

Restrict EKBE by period and order list first, and read EKET for the same order list in one go. Even for a year of data the report usually runs in under a minute; the monthly scorecard can be prepared by a background job and sent by email.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document The vendor line opens the item-level receipt list, the order number opens ME23N and the material document opens MIGO display.
  • Export to Excel
  • Runs as a background job
  • Send the result by email The monthly scorecard can be emailed to each purchasing group or vendor owner.

Authorization objects

  • M_BEST_EKOPurchase order display authorization by purchasing organization
  • M_BEST_WRKPurchase order display authorization by plant

Frequently asked questions

How is the delay calculated when an order item is split into several schedule lines?

Goods receipts are allocated to schedule lines in date order. The first delivery is compared with the date of the first schedule line and the next delivery with the next line, so partial deliveries put the delay on the right line.

Which date is used when the delivery date was changed?

If the delivery date was postponed later, EKET-EINDT carries the new date. To measure the vendor against the originally agreed date, the statistical delivery date (EKET-SLFDT) can be chosen; it stays the same when the date is moved.

Does the report work on S/4HANA?

Yes. EKKO, EKPO, EKET and EKBE keep the same structure in S/4HANA. The Fiori supplier evaluation apps use a different scoring logic; this report applies tolerance days as the company defines them.

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: Vendor On-Time Delivery Performance Report