Preventive Maintenance Compliance Report
Short answer: A custom ALV report that shows per maintenance plan how many preventive maintenance calls due in a period were completed within tolerance, completed late, are still open or were never called, and calculates the compliance percentage per planner group and strategy.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 6
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
IP19 gives the scheduling overview per maintenance plan and IP30 creates calls through deadline monitoring, but neither shows as a percentage how many maintenance tasks due in a period were completed within tolerance, completed late or never called. The preventive maintenance compliance rate asked for in audits is usually calculated by matching plan and order lists in Excel.
Who uses it? Maintenance managers, maintenance planners, quality and audit teams (ISO, food safety, customer audits).
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| MHISMaintenance Plan History | Maintenance plan scheduling history: planned, call and completion dates (driving table) | — | ECC + S/4 |
| MPLAMaintenance Plan | Maintenance plan text and strategy | MPLA-WARPL = MHIS-WARPL | ECC + S/4 |
| MPOSMaintenance Item | Plan item: planning plant, planner group, equipment | MPOS-WARPL = MHIS-WARPL | ECC + S/4 |
| AFIHMaintenance Order Header | Maintenance order created by the call | AFIH-WARPL = MHIS-WARPL AND AFIH-ABNUM = MHIS-ABNUM | ECC + S/4 |
| AUFKOrder Master Data | Technical completion date of the order | AUFK-AUFNR = AFIH-AUFNR | ECC + S/4 |
| ILOAPM Object Location and Account Assignment | Functional location | ILOA-ILOAN = MPOS-ILOAN | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_IWERK | Maintenance planning plant | Range / multiple | MPOS-IWERK | Yes | 1000 |
| S_WPGRP | Planner group | Range / multiple | MPOS-WPGRP | No | M01 |
| S_WARPL | Maintenance plan | Range / multiple | MPLA-WARPL | No | 100023 |
| S_STRAT | Maintenance strategy | Range / multiple | MPLA-STRAT | No | A |
| S_EQUNR | Equipment | Range / multiple | MPOS-EQUNR | No | 10000045 |
| S_NPLDA | Planned date (period) | Range / multiple | MHIS-NPLDA | Yes | 01.10.2026 – 15.11.2026 |
| P_TOLER | Tolerance (days) | Single value | — | No | 3 |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes | 17.11.2026 |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Maintenance plan | MPLA-WARPL |
| 2 | Plan text | MPLA-WPTXT |
| 3 | Strategy | MPLA-STRAT |
| 4 | Equipment | MPOS-EQUNR |
| 5 | Functional location | ILOA-TPLNR |
| 6 | Call no. | MHIS-ABNUM |
| 7 | Planned date | MHIS-NPLDA |
| 8 | Call date | MHIS-HORDA |
| 9 | Maintenance order | AFIH-AUFNR |
| 10 | Completion date | MHIS-LRMDT |
| 11 | Deviation (days) | Calculated Completion (or key date) − MHIS-NPLDA |
| 12 | Compliance status | Calculated On time, late, open overdue or not called |
Sample output
| Maintenance plan | Plan text | Strategy | Equipment | Functional location | Call no. | Planned date | Call date | Maintenance order | Completion date | Deviation (days) | Compliance status |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 100023 | Press monthly service | A | 10000045 | TR01-URT-PRS | 10 | 10/01/2026 | 09/24/2026 | 4000098 | 10/02/2026 | 1 | On time |
| 100023 | Press monthly service | A | 10000045 | TR01-URT-PRS | 11 | 10/31/2026 | 10/24/2026 | 4000127 | 11/09/2026 | 9 | Late |
| 100031 | Compressor 2000-hour service | B | 10000078 | TR01-YRD-KMP | 4 | 10/15/2026 | 10/08/2026 | 4000131 | 33 | Open, overdue | |
| 100044 | Conveyor lubrication | A | 10000102 | TR01-URT-KNV | 22 | 11/05/2026 | 12 | Not called |
How does the report work?
- Maintenance plans and items of the selected planning plant, planner group and strategy are read from MPLA and MPOS; the functional location is added through MPOS-ILOAN → ILOA-TPLNR.
- Scheduling records with a planned date (NPLDA) inside the selected period are read from MHIS: call number (ABNUM), call date (HORDA) and completion date (LRMDT).
- The maintenance order created by the call is found in AFIH with WARPL + ABNUM; when the completion date is blank, AUFK-IDAT2 (technical completion date) is used.
- Deviation = completion date − planned date; key date − planned date when not completed. Status: completed and deviation ≤ tolerance → on time; completed and deviation > tolerance → late; not completed and planned date + tolerance passed → open, overdue; planned date passed and call date blank → not called.
- Compliance % = on time ÷ number of calls due × 100. ALV shows the compliance rate in subtotals per planner group and strategy.
Performance notes
Read MHIS with the planned date range and the selected plan numbers; read AFIH once with FOR ALL ENTRIES on WARPL and ABNUM. The monthly compliance report can run in the background at the start of the month and be sent to managers.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document The plan number opens IP03, the order number opens IW33.
- Export to Excel
- Runs as a background job
- Send the result by email A monthly compliance summary per planner group can be sent to managers.
Authorization objects
- I_IWERKDisplay by maintenance planning plant
- I_TCODEPlant maintenance transaction code authorization
Frequently asked questions
Are counter-based plans reported as well?
Yes. For counter-based plans MHIS also holds a calculated planned date, and compliance is evaluated against it the same way. If needed, the planned and actual counter readings are shown in separate columns.
Can the tolerance differ per plan?
Yes. The default tolerance comes from the selection screen; during installation the shift tolerances of the maintenance plan or a separate tolerance table per strategy can be used.
Does it work on S/4HANA?
Yes. MPLA, MPOS and MHIS keep the same structure in S/4HANA. For a clean core approach, the I_MaintenancePlanBasic and I_MaintenanceCall CDS views can be used.
Packages that include this solution
Maintenance KPI Pack
A pack that delivers the four core indicators of the monthly maintenance review with one plant, work center and equipment selection: maintenance …
Related reports
Maintenance Cost and Downtime by Equipment Report
A custom ALV report that splits the actual cost of maintenance orders per equipment in a period into labor, material, external services and other, and …
Overdue Maintenance Orders and Backlog by Work Center Report
A custom ALV report that lists open maintenance orders past their basic finish date with days late and remaining work hours, and calculates how many …
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.