QP07 — Display Missing Inspection Plans in Procurement
QP07 identifies procurement materials for which the purchasing/inspection context has no usable inspection plan for the selected key date. It helps QM find master-data gaps before goods-receipt inspections are blocked or incomplete. Confirm that the material and inspection setup actually require a plan before creating new master data or changing the inspection process.
Verified practitioner reference for QP07 — Display Missing Inspection Plans in Procurement. 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· 555 words
Esta página ainda não está disponível em português.
Purpose
identify procurement materials for which purchase orders exist but no valid inspection plan is available for the goods-receipt inspection process. 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
QP07 is typically used when QM wants to prevent purchase-order receipts from reaching inspection lots that cannot be processed because plans are missing. 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
- Select plant, inspection type and the relevant key date.
- Review materials with procurement activity but unusable inspection plans.
- Confirm whether a plan is required by the inspection setup.
- Create/release the correct inspection plan rather than changing the lot manually.
- Retest a representative procurement inspection.
Key data objects
These are the fields and objects most useful for explaining a QP07 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.
- purchasing document context — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove a QP07 result by capturing material, plant, inspection type, key date, and the relevant procurement context. Check existing inspection plans for validity, release, usage, and material assignment, then compare the purchasing/inspection setup. Rerun QP07 after correction and test a representative goods-receipt inspection flow.
ECC vs S/4HANA
SAP Help explicitly documents QP07 as the procurement-focused missing-inspection-plan transaction. 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
- Treating every procured material as requiring an inspection plan. Confirm the exact status and process ownership before applying a correction.
- Using the wrong key date and overlooking a valid future/current plan. Confirm the exact status and process ownership before applying a correction.
- Changing PO or inspection-lot data to work around master-data gaps. 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/qp07ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.