PM Report Custom development ALV report

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

  • IP19 Maintenance Scheduling Overview. Gives the scheduling overview of maintenance plans; it does not calculate the compliance percentage per period.
  • IP30 Maintenance Plan Date Monitoring. Creates calls through deadline monitoring; it does not report completion compliance.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
MHISMaintenance Plan HistoryMaintenance plan scheduling history: planned, call and completion dates (driving table)—ECC + S/4
MPLAMaintenance PlanMaintenance plan text and strategyMPLA-WARPL = MHIS-WARPLECC + S/4
MPOSMaintenance ItemPlan item: planning plant, planner group, equipmentMPOS-WARPL = MHIS-WARPLECC + S/4
AFIHMaintenance Order HeaderMaintenance order created by the callAFIH-WARPL = MHIS-WARPL AND AFIH-ABNUM = MHIS-ABNUMECC + S/4
AUFKOrder Master DataTechnical completion date of the orderAUFK-AUFNR = AFIH-AUFNRECC + S/4
ILOAPM Object Location and Account AssignmentFunctional locationILOA-ILOAN = MPOS-ILOANECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_IWERKMaintenance planning plantRange / multipleMPOS-IWERKYes1000
S_WPGRPPlanner groupRange / multipleMPOS-WPGRPNoM01
S_WARPLMaintenance planRange / multipleMPLA-WARPLNo100023
S_STRATMaintenance strategyRange / multipleMPLA-STRATNoA
S_EQUNREquipmentRange / multipleMPOS-EQUNRNo10000045
S_NPLDAPlanned date (period)Range / multipleMHIS-NPLDAYes01.10.2026 – 15.11.2026
P_TOLERTolerance (days)Single value—No3
P_KEYDTKey date (default: today)Single valueSY-DATUMYes17.11.2026

Output columns

#ColumnSource
1Maintenance planMPLA-WARPL
2Plan textMPLA-WPTXT
3StrategyMPLA-STRAT
4EquipmentMPOS-EQUNR
5Functional locationILOA-TPLNR
6Call no.MHIS-ABNUM
7Planned dateMHIS-NPLDA
8Call dateMHIS-HORDA
9Maintenance orderAFIH-AUFNR
10Completion dateMHIS-LRMDT
11Deviation (days)Calculated Completion (or key date) − MHIS-NPLDA
12Compliance statusCalculated On time, late, open overdue or not called

Sample output

Maintenance planPlan textStrategyEquipmentFunctional locationCall no.Planned dateCall dateMaintenance orderCompletion dateDeviation (days)Compliance status
100023Press monthly serviceA10000045TR01-URT-PRS1010/01/202609/24/2026400009810/02/20261On time
100023Press monthly serviceA10000045TR01-URT-PRS1110/31/202610/24/2026400012711/09/20269Late
100031Compressor 2000-hour serviceB10000078TR01-YRD-KMP410/15/202610/08/2026400013133Open, overdue
100044Conveyor lubricationA10000102TR01-URT-KNV2211/05/202612Not called
A view built with fictional sample data; not real system data.

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.

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

PM Package Custom

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 …

4 components · v1.0

Related reports

PM Report Custom ALV report

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 …

AFIH · AUFK · COEP · QMIH

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.

Related report: Preventive Maintenance Compliance Report