# Vendor On-Time Delivery Performance Report

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

- Type: Report, Custom development, ALV report
- Module: MM
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/vendor-on-time-delivery-performance-report/


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

### Closest standard alternatives

- ME80FN: Lists the order history flexibly; does not calculate delay days or an on-time rate per vendor.
- MB51: Lists goods receipt documents; does not show the delivery date of the order.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| EKKO | Order header: vendor, purchasing organization, document type (driving table) | Read | - | ECC + S/4 |
| EKPO | Order item: material, plant, material group | Read | EKPO-EBELN = EKKO-EBELN | ECC + S/4 |
| EKET | Schedule line: delivery date, statistical date, scheduled quantity | Read | EKET-EBELN = EKPO-EBELN AND EKET-EBELP = EKPO-EBELP | ECC + S/4 |
| EKBE | Order history: goods receipt date, quantity and value | Read | EKBE-EBELN = EKPO-EBELN AND EKBE-EBELP = EKPO-EBELP | ECC + S/4 |
| LFA1 | Vendor name | Read | LFA1-LIFNR = EKKO-LIFNR | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_EKORG | Purchasing organization | Range / multiple | EKKO-EKORG | Yes |
| S_WERKS | Plant | Range / multiple | EKPO-WERKS | No |
| S_LIFNR | Vendor | Range / multiple | EKKO-LIFNR | No |
| S_BUDAT | Goods receipt posting date | Range / multiple | EKBE-BUDAT | Yes |
| S_MATKL | Material group | Range / multiple | EKPO-MATKL | No |
| S_BSART | Order document type | Range / multiple | EKKO-BSART | No |
| P_EARLY | Early delivery tolerance (days) | Single value | - | No |
| P_LATE | Late delivery tolerance (days) | Single value | - | No |
| R_EINDT | Compare with delivery date (otherwise statistical date) | Radio button | - | No |

## Output columns

| Column | Source |
|---|---|
| Vendor | EKKO-LIFNR |
| Vendor name | LFA1-NAME1 |
| Purchasing org. | EKKO-EKORG |
| Plant | EKPO-WERKS |
| Receipts | Calculated: Goods receipt lines counted in the period (net of reversals) |
| On time | Calculated: Receipts whose delay is within the tolerance window |
| Early | Calculated: Delay < −early tolerance |
| Late | Calculated: Delay > late tolerance |
| On-time rate (%) | Calculated: On time ÷ receipts × 100 |
| Avg. delay (days) | Calculated: Average delay of late receipts (EKBE-BUDAT − EKET-EINDT) |
| Max. delay | Calculated: Largest delay in days among late receipts |
| In-full rate (%) | Calculated: Schedule lines received in full within tolerance ÷ schedule lines due × 100 |
| Received value | Calculated: Σ EKBE-DMBTR (VGABE = 1, reversals negative) |
| Currency | EKBE-HSWAE |
| Grade | Calculated: On-time rate ≥ 95% A, ≥ 85% B, otherwise C |

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

## Authorization objects

- M_BEST_EKO: Purchase order display authorization by purchasing organization
- M_BEST_WRK: Purchase 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=mm-vendor-on-time-delivery-performance
