# Production Order Schedule Adherence Report (Planned vs Actual Start and Finish)

> A custom ALV report that compares the planned and actual start and finish dates of completed production orders and calculates the days of delay and the schedule adherence rate. The result is available per order or as a summary by MRP controller, production supervisor and order type.

- Type: Report, Custom development, ALV report
- Module: PP
- Estimated effort: S (3–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/production-schedule-adherence-report/


## Why is the standard not enough?

COOIS can show planned and actual dates as columns, but it does not calculate the days of delay, an on-time / early / late classification by tolerance or an adherence percentage. To get a KPI by MRP controller or production supervisor at summary level, the list is exported to Excel and formulas are built by hand. The existing overdue orders report looks at open orders; here the goal is to measure the past performance of finished orders.

### Closest standard alternatives

- COOIS: Lists planned and actual dates; does not calculate delay days, adherence class or a summary KPI.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| AFKO | Planned and actual start/finish dates, MRP controller and production supervisor (driving table) | Read | - | ECC + S/4 |
| AUFK | Order type, plant and object number | Read | AUFK-AUFNR = AFKO-AUFNR | ECC + S/4 |
| AFPO | Material, order and received quantity, last goods receipt date | Read | AFPO-AUFNR = AFKO-AUFNR | ECC + S/4 |
| JEST | Delivered, TECO and deletion status | Read | JEST-OBJNR = AUFK-OBJNR | ECC + S/4 |
| MAKT | Material description | Read | MAKT-MATNR = AFPO-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_WERKS | Plant | Range / multiple | AUFK-WERKS | Yes |
| S_AUART | Order type | Range / multiple | AUFK-AUART | No |
| S_DISPO | MRP controller | Range / multiple | AFKO-DISPO | No |
| S_FEVOR | Production supervisor | Range / multiple | AFKO-FEVOR | No |
| S_GLTRP | Basic finish date range | Range / multiple | AFKO-GLTRP | Yes |
| P_TOL | Tolerance (days) | Single value | - | No |
| P_DLVPCT | Under-delivery threshold (%) | Single value | - | No |
| P_DETAIL | List per order | Radio button | - | No |
| P_SUMM | Summary by MRP controller / supervisor | Radio button | - | No |

## Output columns

| Column | Source |
|---|---|
| Production order | AFKO-AUFNR |
| Order type | AUFK-AUART |
| Material | AFPO-MATNR |
| Description | MAKT-MAKTX |
| MRP controller | AFKO-DISPO |
| Production supervisor | AFKO-FEVOR |
| Planned start | AFKO-GSTRP |
| Actual start | AFKO-GSTRI |
| Start delay (days) | Calculated: AFKO-GSTRI − AFKO-GSTRP |
| Planned finish | AFKO-GLTRP |
| Last goods receipt | AFPO-LTRMI |
| Finish delay (days) | Calculated: AFPO-LTRMI − AFKO-GLTRP |
| Order quantity | AFPO-PSMNG |
| Received quantity | AFPO-WEMNG |
| Delivery rate % | Calculated: AFPO-WEMNG ÷ AFPO-PSMNG × 100 |
| Adherence class | Calculated: On time, early or late by tolerance; under-delivered when below the delivery threshold |

## How does the report work?

1. Production orders are read from AUFK and AFKO by the plant, order type and basic finish date range on the selection screen; orders with delivery completed (AFPO-ELIKZ) or with delivered (I0012) or TECO (I0045) active in JEST are taken, deleted orders (I0076) are skipped.
2. Start delay = AFKO-GSTRI − AFKO-GSTRP (days); finish delay = AFPO-LTRMI (last goods receipt date) − AFKO-GLTRP. When an actual date is blank the line is flagged as 'date missing'.
3. A finish delay within the tolerance days is classified as 'on time', below it as 'early' and above it as 'late'.
4. Delivery rate = AFPO-WEMNG ÷ AFPO-PSMNG × 100; when it is below the selected threshold the order is flagged as 'under-delivered' even if it finished on time.
5. In the summary view, the number of orders, the on-time rate and the average delay are calculated for the selected grouping (MRP controller, production supervisor or order type).

## Authorization objects

- C_AFKO_AWK: Display production orders by plant and order type

## Frequently asked questions

### Why is the last goods receipt date used for the finish?

From the customer's and the warehouse's point of view an order is finished when the product enters stock; that date is held in AFPO-LTRMI. If required, the last confirmation date (AFKO-GETRI) can be shown as a second finish measure in a separate column.

### Which planned date is used for rescheduled orders?

The report uses the current basic dates of the order. If measurement against the order's first planned date is required, the original value can be read from change documents; this extension adds about one day.

### Does this report work on S/4HANA?

Yes. AFKO, AFPO and AUFK keep the same structure in S/4HANA; the report runs without changes.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=pp-schedule-adherence
