Production Order Schedule Adherence Report (Planned vs Actual Start and Finish)
Short answer: 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.
- Estimated effort
- S · 3–4 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? Production managers, planning teams, and operational excellence or KPI reporting teams.
Closest standard alternatives
- COOIS Production Order Information System. Lists planned and actual dates; does not calculate delay days, adherence class or a summary KPI.
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| AFKOOrder Header Data for PP Orders | Planned and actual start/finish dates, MRP controller and production supervisor (driving table) | — | ECC + S/4 |
| AUFKOrder Master Data | Order type, plant and object number | AUFK-AUFNR = AFKO-AUFNR | ECC + S/4 |
| AFPOOrder Item | Material, order and received quantity, last goods receipt date | AFPO-AUFNR = AFKO-AUFNR | ECC + S/4 |
| JESTIndividual Object Status | Delivered, TECO and deletion status | JEST-OBJNR = AUFK-OBJNR | ECC + S/4 |
| MAKTMaterial Descriptions | Material description | MAKT-MATNR = AFPO-MATNR AND MAKT-SPRAS = SY-LANGU | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_WERKS | Plant | Range / multiple | AUFK-WERKS | Yes | 1000 |
| S_AUART | Order type | Range / multiple | AUFK-AUART | No | PP01 |
| S_DISPO | MRP controller | Range / multiple | AFKO-DISPO | No | 001 |
| S_FEVOR | Production supervisor | Range / multiple | AFKO-FEVOR | No | 101 |
| S_GLTRP | Basic finish date range | Range / multiple | AFKO-GLTRP | Yes | 01.10.2026 – 31.10.2026 |
| P_TOL | Tolerance (days) | Single value | — | No | 1 |
| P_DLVPCT | Under-delivery threshold (%) | Single value | — | No | 95 |
| P_DETAIL | List per order | Radio button | — | No | X |
| P_SUMM | Summary by MRP controller / supervisor | Radio button | — | No | — |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Production order | AFKO-AUFNR |
| 2 | Order type | AUFK-AUART |
| 3 | Material | AFPO-MATNR |
| 4 | Description | MAKT-MAKTX |
| 5 | MRP controller | AFKO-DISPO |
| 6 | Production supervisor | AFKO-FEVOR |
| 7 | Planned start | AFKO-GSTRP |
| 8 | Actual start | AFKO-GSTRI |
| 9 | Start delay (days) | Calculated AFKO-GSTRI − AFKO-GSTRP |
| 10 | Planned finish | AFKO-GLTRP |
| 11 | Last goods receipt | AFPO-LTRMI |
| 12 | Finish delay (days) | Calculated AFPO-LTRMI − AFKO-GLTRP |
| 13 | Order quantity | AFPO-PSMNG |
| 14 | Received quantity | AFPO-WEMNG |
| 15 | Delivery rate % | Calculated AFPO-WEMNG ÷ AFPO-PSMNG × 100 |
| 16 | Adherence class | Calculated On time, early or late by tolerance; under-delivered when below the delivery threshold |
Sample output
| Production order | Order type | Material | Description | MRP controller | Production supervisor | Planned start | Actual start | Start delay (days) | Planned finish | Last goods receipt | Finish delay (days) | Order quantity | Received quantity | Delivery rate % | Adherence class |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1000352 | PP01 | FG-5003 | Packed product C | 001 | 101 | 10/02/2026 | 10/02/2026 | 0 | 10/06/2026 | 10/06/2026 | 0 | 1,000 | 1,000 | 100 | On time |
| 1000361 | PP01 | FG-6100 | Panel cabinet 80 cm | 001 | 102 | 10/07/2026 | 10/09/2026 | 2 | 10/13/2026 | 10/17/2026 | 4 | 150 | 150 | 100 | Late |
| 1000370 | PP02 | FG-7200 | Compressor unit K2 | 002 | 201 | 10/14/2026 | 10/13/2026 | -1 | 10/20/2026 | 10/19/2026 | -1 | 60 | 54 | 90 | Under-delivered |
| 1000384 | PP01 | FG-5003 | Packed product C | 001 | 101 | 10/21/2026 | 10/21/2026 | 0 | 10/24/2026 | 10/22/2026 | -2 | 800 | 800 | 100 | Early |
How does the report work?
- 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.
- 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’.
- A finish delay within the tolerance days is classified as ‘on time’, below it as ’early’ and above it as ’late’.
- 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.
- 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).
Performance notes
Narrow AFKO by the basic finish date range and read the status check from JEST once with the order object numbers. For a monthly KPI the report can run in the background at month end and the summary view can be emailed.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document The order number opens CO03.
- Export to Excel
- Runs as a background job
- Send the result by email The monthly summary can be sent automatically to production management.
Authorization objects
- C_AFKO_AWKDisplay 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.
Related reports
Overdue Production Orders and Remaining Quantity Report
A custom ALV report that lists production orders past their basic finish date that are not yet fully received, with days late, remaining quantity and …
Weekly Capacity Load by Work Center Report
A custom ALV report that shows, for every work center of the selected plant, the available capacity, the production order and planned order load and …
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.