QP06 — Display Inspection Plans - Missing or Unusable
QP06 identifies materials for which no valid or usable inspection plan is available for the selected plant, inspection type, and key date. Use it to find QM master-data gaps before or during inspection processing. A returned material does not automatically require a new plan; first check plan validity, release status, usage, material assignment, and key date.
Verified practitioner reference for QP06 — Display Inspection Plans - Missing or Unusable. 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· 582 words
Esta página ainda não está disponível em português.
Purpose
identify materials for which no valid, released or usable inspection plan is available for a selected plant, inspection type and key date. 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
QP06 is typically used when goods-receipt or other inspection processes cannot find an inspection plan and QM needs a preventive worklist. 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
- Enter plant, inspection type and key date matching the business process.
- Run a focused selection before mass analysis.
- Review whether the issue is no plan, wrong task-list usage or unreleased plan.
- Navigate to material/inspection plan master data for correction.
- Retest inspection-lot processing after a valid plan exists.
Key data objects
These are the fields and objects most useful for explaining a QP06 result. Record them in incident evidence and test scripts.
- material — verify the exact value, validity/status, and relationship to this transaction's business object.
- plant — verify the exact value, validity/status, and relationship to this transaction's business object.
- inspection type — verify the exact value, validity/status, and relationship to this transaction's business object.
- key date — verify the exact value, validity/status, and relationship to this transaction's business object.
- plan availability/release status — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove a QP06 finding by recording material, plant, inspection type, key date, and the reason no plan is usable. Search existing inspection plans for the same material/plant and verify validity, release status, task-list usage, and assignment. After correcting master data, rerun the same QP06 selection to show that the material is no longer reported.
ECC vs S/4HANA
SAP Help explicitly documents QP06 as Display Inspection Plans — Missing or Unusable, including current S/4HANA documentation. 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
- Checking today's key date for a historical inspection lot. Confirm the exact status and process ownership before applying a correction.
- Creating a duplicate plan when an existing plan is simply unreleased or invalid by date. Confirm the exact status and process ownership before applying a correction.
- Changing inspection type configuration to bypass missing master data. Confirm the exact status and process ownership before applying a correction.
Whose problem this is
Primary ownership is the QM 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/qp06ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.