# Preventive Maintenance Compliance Report

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

- Type: Report, Custom development, ALV report
- Module: PM
- Estimated effort: M (4–6 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/preventive-maintenance-compliance-report/


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

### Closest standard alternatives

- IP19: Gives the scheduling overview of maintenance plans; it does not calculate the compliance percentage per period.
- IP30: Creates calls through deadline monitoring; it does not report completion compliance.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| MHIS | Maintenance plan scheduling history: planned, call and completion dates (driving table) | Read | - | ECC + S/4 |
| MPLA | Maintenance plan text and strategy | Read | MPLA-WARPL = MHIS-WARPL | ECC + S/4 |
| MPOS | Plan item: planning plant, planner group, equipment | Read | MPOS-WARPL = MHIS-WARPL | ECC + S/4 |
| AFIH | Maintenance order created by the call | Read | AFIH-WARPL = MHIS-WARPL AND AFIH-ABNUM = MHIS-ABNUM | ECC + S/4 |
| AUFK | Technical completion date of the order | Read | AUFK-AUFNR = AFIH-AUFNR | ECC + S/4 |
| ILOA | Functional location | Read | ILOA-ILOAN = MPOS-ILOAN | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_IWERK | Maintenance planning plant | Range / multiple | MPOS-IWERK | Yes |
| S_WPGRP | Planner group | Range / multiple | MPOS-WPGRP | No |
| S_WARPL | Maintenance plan | Range / multiple | MPLA-WARPL | No |
| S_STRAT | Maintenance strategy | Range / multiple | MPLA-STRAT | No |
| S_EQUNR | Equipment | Range / multiple | MPOS-EQUNR | No |
| S_NPLDA | Planned date (period) | Range / multiple | MHIS-NPLDA | Yes |
| P_TOLER | Tolerance (days) | Single value | - | No |
| P_KEYDT | Key date (default: today) | Single value | SY-DATUM | Yes |

## Output columns

| Column | Source |
|---|---|
| Maintenance plan | MPLA-WARPL |
| Plan text | MPLA-WPTXT |
| Strategy | MPLA-STRAT |
| Equipment | MPOS-EQUNR |
| Functional location | ILOA-TPLNR |
| Call no. | MHIS-ABNUM |
| Planned date | MHIS-NPLDA |
| Call date | MHIS-HORDA |
| Maintenance order | AFIH-AUFNR |
| Completion date | MHIS-LRMDT |
| Deviation (days) | Calculated: Completion (or key date) − MHIS-NPLDA |
| Compliance status | Calculated: On time, late, open overdue or not called |

## How does the report work?

1. 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.
2. 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).
3. 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.
4. 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.
5. Compliance % = on time ÷ number of calls due × 100. ALV shows the compliance rate in subtotals per planner group and strategy.

## Authorization objects

- I_IWERK: Display by maintenance planning plant
- I_TCODE: Plant 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=pm-preventive-maintenance-compliance
