QP03 — Display Inspection Plan in QM
QP03 displays an existing quality inspection plan (task list type Q) either by material and plant or by plan group and group counter, showing the operations, inspection characteristics, and sampling procedures attached to it. It is read-only; use QP02 to change the same object.
This page covers QP03, the display transaction for QM inspection plans, and the structural split between the plan itself (group/counter) and its assignment to a material and plant that most confusion traces back to. It focuses on why a lot does not pick up the characteristics a consultant expects to see, and where to look first.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,108 words
Purpose
QP03 opens an inspection plan (task list type Q) in display mode and shows its header, operations, inspection characteristics, and sampling procedures. The one structural fact that explains most confusion: the plan is a generic object identified by a plan group and group counter, and it only becomes usable for a specific material when that material and plant are linked to the plan through a separate assignment record. A plan can exist, be fully built out with characteristics, and still never fire for a material because the assignment step was skipped, or was made against the wrong plant. QP03 lets entry by material/plant or directly by group/counter, and the two paths do not always land on the same result if the assignment is missing or points elsewhere.
When it is used
QP03 is reached for whenever an inspection lot is missing characteristics that should be there, or is showing characteristics that should not be, and the question is what the plan actually contains rather than what the lot did with it. It sits upstream of the inspection lot transactions entirely: the plan is master data, the lot is a transactional consumer of that master data at the moment of creation. Consultants use QP03 instead of QP02 when the goal is just to look, not touch, because QP02 places a lock on the plan and can interrupt someone else's maintenance. It is also the fastest way to confirm plan status and validity before blaming the lot creation logic for a missing characteristic.
How to use it in practice
- Open QP03 and choose the material/plant entry route if the starting point is a material, or the group/group counter route if the plan number is already known.
- Enter the key and confirm; the overview screen lists the operations that make up the plan.
- Double-click an operation to see its inspection characteristics, including whether each references a master inspection characteristic or is defined inline.
- Check the sampling procedure attached to each characteristic, since this drives how many units get inspected.
- Check the header data for status (in preparation versus released) and the validity period, since an unreleased or expired plan is invisible to lot creation even though it displays fine here.
- If entry was by group/counter, cross-check the material assignment separately to confirm which materials and plants actually point to this counter.
Key data objects
- PLKO - task list header: plan group, group counter, status, validity dates, usage.
- PLPO - task list operations: the sequence of operations that make up the plan, each carrying a counter and work center reference.
- PLMK - inspection characteristics attached to a plan operation, including reference to a master inspection characteristic where used.
- MAPL - the material task list allocation: the link between a material, a plant, and a plan group/counter, without which the plan is orphaned from any material.
How to prove it in the data
Start in SE16 on MAPL filtered by material and plant to get the plan group and group counter actually assigned; if no row comes back, the plan is not linked to that material/plant and the symptom is explained right there. With the group and counter in hand, check PLKO for status and validity dates covering the date the inspection lot was created. Then check PLPO for the operation and PLMK for the characteristics under it, comparing what is listed there against what the inspection lot's characteristic results screen actually shows.
ECC vs S/4HANA
QP03 exists unchanged on S/4HANA and still runs through the classical SAP GUI screens. The underlying tables and the group/counter versus material-assignment structure have not changed. There is no dedicated Fiori app that replaces plan display for this transaction; consultants continue to use the GUI transaction for inspection plan review even in an otherwise Fiori-first S/4HANA landscape.
Common pitfalls and how to diagnose them
- No assignment found: the plan looks complete in QP03 by group/counter but a lookup by material/plant returns nothing. This means the MAPL link was never created or was created against a different plant. The lot fell back to no plan, or to a different plan entirely, and nobody edited the intended one.
- Plan not released: status still shows in preparation. A plan in this state is skipped during lot creation even if correctly assigned. This is the most common reason a plan someone 'just finished' does not show up on the next batch of lots.
- Usage mismatch: the plan was built for one usage, such as production order inspection, but the inspection lot was generated by a different origin, such as goods receipt. The assignment exists and the plan is released, but the inspection type on the lot does not match what the plan was authorized for, so the system selects nothing or a different plan.
- Validity gap or overlap: the plan's date range does not cover the lot creation date, or two counters for the same plan group have overlapping validity, forcing an ambiguous or unexpected selection. Always check the validity dates on PLKO before assuming the assignment is the problem.
- Wrong group counter displayed: QP03 by material shows only the currently valid counter, hiding older counters that may still be referenced by open orders created before the last change. When a change 'did not take effect' on an existing order, this is usually why.
Whose problem this is
This is functional QM territory, owned by the quality management consultant responsible for inspection planning. ABAP involvement is only needed if a characteristic uses a custom formula or user exit for value determination. A good handover includes the material, plant, plan group and counter, the inspection lot number showing the symptom, and a note on whether the issue is missing characteristics, wrong sampling, or wrong plan selection.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/qp03ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.