IP16 — Display Maintenance Plan: Selection Criteria
IP16 displays maintenance plans as a selection-based list so planners can review many plans and drill into individual records. It is useful for finding plans by planning plant, planner group, category, technical object, scheduling attributes, or other criteria. The list is read oriented; use the plan detail and scheduling transactions to explain why a particular call was or was not generated.
Verified practitioner reference for IP16 — Display Maintenance Plan: Selection Criteria. 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· 560 words
Esta página aún no está disponible en español.
Purpose
list maintenance plans using selection criteria so planners can review multiple plans and drill into plan details. 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
IP16 is typically used when maintenance teams need a read-only worklist by plant, planning group, category, object or scheduling attributes. 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
- Define a focused plan selection.
- Add scheduling and end-date fields to the list where relevant.
- Identify plans requiring detailed review.
- Drill into IP03 for plan-level settings.
- Compare list results with scheduling runs and generated calls.
Key data objects
These are the fields and objects most useful for explaining a IP16 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.
- maintenance-plan category — verify the exact value, validity/status, and relationship to this transaction's business object.
- planning plant/group — verify the exact value, validity/status, and relationship to this transaction's business object.
- technical object — verify the exact value, validity/status, and relationship to this transaction's business object.
- scheduling/end-date criteria — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove an IP16 list issue by preserving the exact selection criteria and checking a representative plan in IP03. Compare end dates, cycles, scheduling parameters, and plan status with the list result. If the question concerns generated calls, continue to IP10/IP30 and the resulting maintenance order or notification instead of treating the list alone as execution evidence.
ECC vs S/4HANA
SAP Help documents IP16 as Display Maintenance Plan: Selection Criteria in current S/4HANA maintenance-plan validation. 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
- Comparing lists built with different selection criteria. Confirm the exact status and process ownership before applying a correction.
- Calling a plan inactive based only on absence of a recent call. Confirm the exact status and process ownership before applying a correction.
- Ignoring end-date/end-counter settings where configured. 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/ip16ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.