{"audience":"Maintenance managers, maintenance planners, quality and audit teams (ISO, food safety, customer audits).","authorization_objects":[{"note":"Display by maintenance planning plant","object":"I_IWERK"},{"note":"Plant maintenance transaction code authorization","object":"I_TCODE"}],"components":[],"countries":[],"effort_days_max":6,"effort_days_min":4,"effort_size":"M","faq":[{"a":"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.","q":"Are counter-based plans reported as well?"},{"a":"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.","q":"Can the tolerance differ per plan?"},{"a":"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.","q":"Does it work on S/4HANA?"}],"features":[{"code":"alv","label":"ALV list (sort, filter, subtotals)","note":""},{"code":"layout","label":"User-specific layout variants","note":""},{"code":"drilldown","label":"Double-click drill-down to the document","note":"The plan number opens IP03, the order number opens IW33."},{"code":"excel","label":"Export to Excel","note":""},{"code":"background","label":"Runs as a background job","note":""},{"code":"email","label":"Send the result by email","note":"A monthly compliance summary per planner group can be sent to managers."}],"functions":[],"gap":"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.","id":"pm-preventive-maintenance-compliance","industries":[],"input_columns":[],"kind":"report","language":"en","lastmod":"2026-11-17","logic":"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.\n2. 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).\n3. 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.\n4. Deviation = completion date − planned date; key date − planned date when not completed. Status: completed and deviation ≤ tolerance → on time; completed and deviation \u003e tolerance → late; not completed and planned date + tolerance passed → open, overdue; planned date passed and call date blank → not called.\n5. Compliance % = on time ÷ number of calls due × 100. ALV shows the compliance rate in subtotals per planner group and strategy.","module":"PM","object_type":"alv_report","output_columns":[{"calculated":false,"formula":"","label":"Maintenance plan","source_field":"WARPL","source_table":"MPLA"},{"calculated":false,"formula":"","label":"Plan text","source_field":"WPTXT","source_table":"MPLA"},{"calculated":false,"formula":"","label":"Strategy","source_field":"STRAT","source_table":"MPLA"},{"calculated":false,"formula":"","label":"Equipment","source_field":"EQUNR","source_table":"MPOS"},{"calculated":false,"formula":"","label":"Functional location","source_field":"TPLNR","source_table":"ILOA"},{"calculated":false,"formula":"","label":"Call no.","source_field":"ABNUM","source_table":"MHIS"},{"calculated":false,"formula":"","label":"Planned date","source_field":"NPLDA","source_table":"MHIS"},{"calculated":false,"formula":"","label":"Call date","source_field":"HORDA","source_table":"MHIS"},{"calculated":false,"formula":"","label":"Maintenance order","source_field":"AUFNR","source_table":"AFIH"},{"calculated":false,"formula":"","label":"Completion date","source_field":"LRMDT","source_table":"MHIS"},{"calculated":true,"formula":"Completion (or key date) − MHIS-NPLDA","label":"Deviation (days)","source_field":null,"source_table":null},{"calculated":true,"formula":"On time, late, open overdue or not called","label":"Compliance status","source_field":null,"source_table":null}],"parameters":[{"example":"1000","kind":"select_option","label":"Maintenance planning plant","name":"S_IWERK","ref_field":"MPOS-IWERK","required":true},{"example":"M01","kind":"select_option","label":"Planner group","name":"S_WPGRP","ref_field":"MPOS-WPGRP","required":false},{"example":"100023","kind":"select_option","label":"Maintenance plan","name":"S_WARPL","ref_field":"MPLA-WARPL","required":false},{"example":"A","kind":"select_option","label":"Maintenance strategy","name":"S_STRAT","ref_field":"MPLA-STRAT","required":false},{"example":"10000045","kind":"select_option","label":"Equipment","name":"S_EQUNR","ref_field":"MPOS-EQUNR","required":false},{"example":"01.10.2026 – 15.11.2026","kind":"select_option","label":"Planned date (period)","name":"S_NPLDA","ref_field":"MHIS-NPLDA","required":true},{"example":"3","kind":"parameter","label":"Tolerance (days)","name":"P_TOLER","ref_field":"","required":false},{"example":"17.11.2026","kind":"parameter","label":"Key date (default: today)","name":"P_KEYDT","ref_field":"SY-DATUM","required":true}],"part_of":["pm-maintenance-kpi-pack"],"performance":"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.","quote_url":"https://nekuhub.com/en/request-a-quote/?report=pm-preventive-maintenance-compliance","related":["pm-maintenance-cost-by-equipment","pm-overdue-maintenance-orders-backlog"],"releases":[],"source":"custom","standard_alternatives":[{"note":"Gives the scheduling overview of maintenance plans; it does not calculate the compliance percentage per period.","tcode":"IP19"},{"note":"Creates calls through deadline monitoring; it does not report completion compliance.","tcode":"IP30"}],"summary":"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.","tables":[{"access":"read","join_on":"","role":"Maintenance plan scheduling history: planned, call and completion dates (driving table)","table":"MHIS","variant":"both"},{"access":"read","join_on":"MPLA-WARPL = MHIS-WARPL","role":"Maintenance plan text and strategy","table":"MPLA","variant":"both"},{"access":"read","join_on":"MPOS-WARPL = MHIS-WARPL","role":"Plan item: planning plant, planner group, equipment","table":"MPOS","variant":"both"},{"access":"read","join_on":"AFIH-WARPL = MHIS-WARPL AND AFIH-ABNUM = MHIS-ABNUM","role":"Maintenance order created by the call","table":"AFIH","variant":"both"},{"access":"read","join_on":"AUFK-AUFNR = AFIH-AUFNR","role":"Technical completion date of the order","table":"AUFK","variant":"both"},{"access":"read","join_on":"ILOA-ILOAN = MPOS-ILOAN","role":"Functional location","table":"ILOA","variant":"both"}],"title":"Preventive Maintenance Compliance Report","url":"https://nekuhub.com/en/reports/preventive-maintenance-compliance-report/","vendor_id":"nekudos"}