IP02 — Change Maintenance Plan
IP02 changes an existing preventive maintenance plan, including permitted cycle or strategy data, scheduling parameters, and maintenance items. Use it when an approved maintenance-policy change requires the plan itself to be updated. Review already generated calls before changing scheduling data, because modifying the master plan does not automatically mean existing orders or notifications should be rewritten.
Verified practitioner reference for IP02 — Change Maintenance Plan. The page covers the operational purpose, correct usage sequence, key data to capture, evidence-based diagnosis, S/4HANA context, frequent mistakes, ownership and related SAP objects.
Published 20 Sept 2026· 558 words
Purpose
change an existing preventive maintenance plan's cycle, scheduling parameters, items or other permitted master data. The transaction should be understood as one point in the full operational process. Master data, status, validity dates and preceding execution steps often determine what can happen here, so preserve that context before changing the symptom.
When it is used
IP02 is typically used when maintenance strategy, timing or assigned maintenance object needs an approved update. It is also useful in project testing and support reproduction because it exposes a concrete process state. In production, keep the initial selection narrow and separate display/analysis from actions that mass-change, count, clear or post.
How to use it in practice
- Open the plan and review current scheduling status before changing it.
- Identify whether the change affects cycle, call horizon, scheduling indicator or maintenance items.
- Use an effective change consistent with maintenance policy.
- Save and reschedule only as required by the change.
- Verify next planned/call dates after the update.
Key data objects
These are the fields and objects most useful for explaining a IP02 result. Record them in incident evidence and test scripts.
- maintenance plan — verify the exact value, validity/status, and relationship to this transaction's business object.
- plan category — verify the exact value, validity/status, and relationship to this transaction's business object.
- cycle/strategy — verify the exact value, validity/status, and relationship to this transaction's business object.
- scheduling parameters — verify the exact value, validity/status, and relationship to this transaction's business object.
- maintenance items — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove an IP02 change by capturing the plan settings and next scheduled call before the update, changing only the approved parameter, then rescheduling as required and comparing the new scheduling result in IP10 or the relevant monitoring transaction. Separate changes to future call calculation from maintenance orders or notifications that were already generated.
ECC vs S/4HANA
SAP Help explicitly documents IP02 as Change Maintenance Plan and references it in current S/4HANA maintenance-plan processes. Where a classic component is legacy, the page explicitly keeps that context so readers do not mistake technical availability for SAP's strategic architecture for new implementations.
Common pitfalls and how to diagnose them
- Changing cycle data without understanding already-generated calls. Confirm the exact status and process ownership before applying a correction.
- Using master-data changes to hide overdue maintenance. Confirm the exact status and process ownership before applying a correction.
- Copying another plan's settings without checking plan category and object. Confirm the exact status and process ownership before applying a correction.
Whose problem this is
Primary ownership is the PM EAM team, with adjacent functional, technical, Security, or integration teams joining only where the evidence crosses component boundaries. Escalate with the exact object/document, organizational keys, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ip02ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.