JinJin48
JinJin48
SAP Consultant | BTP · S/4HANA · US Global Rollout
· 12 min read

Cover: SAP QM Inspection Plan — master data linking Master Inspection Characteristics, Sampling Procedure, Work Center, and Material Master

SAP QM Inspection Plan

The Inspection Plan is the central planning object in SAP QM that defines which inspection characteristics must be checked, in what sequence, using which sampling procedure, and at which work center. It acts as the bridge between the foundation master data (Inspection Characteristics, Methods, and Sampling Procedures) and the material-level activation (Material Master QM View). Every inspection lot created by SAP — whether triggered by a goods receipt, a production order, or a stock transfer — is governed by an Inspection Plan assigned to the material.


Part 1: Inspection Plan — Core Concepts (All Modules)

1.1 What Is the Inspection Plan?

Hub-and-spoke diagram showing the Inspection Plan at center, connected to Material Master, Master Inspection Characteristic, Sampling Procedure, Work Center, and Inspection Lot

The Inspection Plan is a quality planning document that specifies the complete inspection procedure for a material. It defines the sequence of operations, the characteristics to be measured or evaluated at each operation, and the sampling strategy to apply — giving inspectors a structured, repeatable checklist derived from master data rather than ad-hoc instructions.

AspectDetails
RoleDefines the complete inspection procedure for a material: operations, characteristics, sampling, and work center assignment
Modules using itQM (primary owner — all inspection scenarios), PP (production-order-integrated inspections use shared routing/inspection plan logic), MM (goods receipt inspections reference the plan via Material Master QM View)
TransactionsQP01 (Create) / QP02 (Change) / QP03 (Display) / QP06 (Mass processing)
Key TablesPLKO (Inspection plan header) / PLPO (Operations) / QPAM (Characteristic assignments to operations) / MAPL (Material-plan assignment)
S/4HANA noteInspection Plan data model unchanged from ECC. Fiori app “Manage Inspection Plans” (App ID F2285) provides a simplified interface for QP01/QP02 tasks. Change documents are fully auditable.

1.2 Usage and Plan Types

2x2 matrix comparing key SAP QM Inspection Plan usage types: Usage 5 (Quality Inspection), Usage 9 (Routing Integration), and other usages

The Usage field is the most important classifier on the Inspection Plan header. It determines which inspection scenarios (inspection types) the plan is eligible for and whether it is treated as a standalone quality plan or integrated with a PP routing.

UsageDescriptionUse CaseKey Behavior
5Quality Inspection PlanStandard QM-only inspection: GR from PO (type 01), GR from production (type 02), delivery to customer (type 05), stock inspectionsThe most common usage. The plan is independent of PP and can be assigned to any material-inspection type combination in the Material Master QM View.
9Routing IntegrationProduction operations include in-process inspection stepsThe inspection plan is linked to the PP routing. Inspection characteristics are maintained directly on routing operations. Requires coordination between PP and QM master data teams.
1General MaintenancePreventive maintenance inspection plans (PM integration)Used in PM plant maintenance scenarios where equipment inspection is needed alongside quality verification.

Design principle: For most QM implementations, Usage 5 is the correct choice. Usage 9 (routing integration) should only be selected when PP and QM inspection steps are genuinely merged — it significantly increases PP master data maintenance complexity and requires careful synchronization.


1.3 Organizational Levels and Data Hierarchy

The Inspection Plan is plant-level and tied to one Material. It contains Operations, and each Operation contains Insp. Characteristics — these two levels are true parent-child containment.

Hierarchy diagram showing plant-level Inspection Plan under Material Master, with Operations, Insp. Characteristics copied from client-level Inspection Characteristics, and a Work Center reference

An Inspection Plan does not stand alone — it pulls together several client-level inspection masters. The most important of these are the Inspection Characteristic (IC), which supplies the master template for each Insp. Char. copied into an operation, and the Inspection Method, which each IC references to define how the value is measured. The Sampling Procedure is also client-level and is assigned at the operation level; the IC master itself never sits inside the plan — only a copy of it does.

Hierarchy diagram showing the client-level inspection masters — Inspection Characteristic, Inspection Method, Sampling Procedure — that an Inspection Plan draws from

Data hierarchy with a concrete example

Client 100
   │
   ├── IC "IC-DIA"        Diameter (quant.)   ── uses ──> Inspection Method "IM-CMM"
   ├── IC "IC-SURF"       Surface (qual.)     ── uses ──> Inspection Method "IM-VIS"
   └── Sampling Procedure "SP-05"             AQL 1.0 · Level II

Plant 1000
   │
   └── Material Master "4711"              QM · Insp. Type 01
          │
          └── Inspection Plan "Group 50 / Cnt 1"
                 │
                 ├── Operation 0010   Incoming Dim. Check
                 │      │
                 │      ├── Insp. Char. 10   Ø25±.02mm   ── copied from ──> IC "IC-DIA"
                 │      ├── Insp. Char. 20   Ø10±.05mm   ── copied from ──> IC "IC-DIA"
                 │      └── Insp. Char. 30   No Burrs    (no master ref.)
                 │
                 └── Operation 0020   Surface Inspection
                        │
                        ├── Insp. Char. 10   Ra≤1.6µm    ── copied from ──> IC "IC-SURF"
                        ├── Insp. Char. 20   Coat 10µm   (no master ref.)
                        └── ── uses ──> Work Center "WC-INSP-01"   Inspection Cell 1

Design principle: Copy Insp. Characteristics from client-level IC masters wherever the same measurement recurs across plans, rather than typing a local (no-master-ref) characteristic each time. Copying preserves the link back to the IC — a future tolerance change at the master level can be re-pulled into every plan that references it, while a local characteristic has no such traceability.


1.4 Integration with Other Master Data Objects

Hub-and-spoke diagram showing the Inspection Plan at center connected to Master Inspection Characteristic, Sampling Procedure, Work Center, Material Master (QM View), and Inspection Lot

The Inspection Plan does not stand alone. It is the convergence point for all foundational QM master data, and it feeds directly into runtime inspection lot processing.

ObjectRelationshipPractical Notes
Master Inspection Characteristic (MIC)Plan assigns MICs to operationsA single MIC can be reused across many inspection plans. Changes to a MIC (e.g., revised tolerance) propagate only if the plan is updated and re-released — existing released plans retain the snapshot values from the time of characteristic assignment.
Inspection MethodAssigned to each characteristic on the planDescribes the measurement technique (caliper, tensile test, visual). Optional but strongly recommended for regulated industries (automotive IATF, medical device ISO 13485) where traceability of measurement method is required.
Sampling ProcedureAssigned at the characteristic levelOverrides the default sampling procedure stored in the MIC. This allows the same characteristic to be inspected with different sampling intensities across different inspection scenarios.
Work CenterAssigned to each operationDefines the physical location and resource group responsible for the inspection. The work center must have a QM-compatible control key (e.g., QM01) configured in Customizing.
Material Master (QM View)Inspection Plan is activated via the QM ViewThe Material Master QM View specifies which inspection types are active for the material. For each active inspection type, an Inspection Plan must exist and be in Released (status 4) status for inspection lots to be created automatically.
Inspection Lot (QA01)Inspection Lot is created referencing this planAt runtime, the system copies the plan’s characteristic assignments into the inspection lot. The lot drives results recording (QE01) and usage decision (QA11).

Part 2: QM-Specific Field Details

2.0 Scope of QM Ownership

Checklist showing QM consultant ownership across Inspection Plan data sections: Header, Operations, and Characteristic Assignments

Data SectionQM InvolvementNotes
Plan Header (PLKO)◎ OwnerStatus, Usage, Valid-From, Lot Size Range — all QM-owned fields
Operations (PLPO)◎ OwnerWork Center assignment, control key, operation description
Characteristic Assignments (QPAM)◎ OwnerMIC selection, sampling procedure override, method assignment, characteristic attributes
Material Assignment (MAPL)◎ OwnerLinks plan to material-plant-inspection type — created and managed by QM team
Work Center Master Data○ Shared with PPWork Center itself is created/maintained by PP; QM only assigns it to operations

Legend: ◎ = Owner / Critical, ○ = Direct involvement


2.1 Plan Header (PLKO)

Checklist of key Inspection Plan header fields: Plan Group, Group Counter, Status, Usage, Valid-From, Lot Size From, Lot Size To, Plant

The plan header controls the lifecycle and applicability of the entire inspection plan. Errors here — especially in Status and Lot Size Range — are the leading cause of inspection lots being created without a plan assignment, bypassing quality inspection entirely.

FieldDescriptionPractical Usage
Plan Group (PLNNR)Numeric key grouping related plan versionsAssigned by system or entered manually. All Group Counters under the same Plan Group share the same Group number. In practice, one Plan Group per material-inspection purpose is the standard design pattern — use different Group Counters for lot-size tiers, not different Plan Groups.
Group Counter (PLNAL)Version discriminator within the Plan GroupTypically “1” for a single-version plan. Add a second counter (e.g., “2”) for a large-lot variant covering quantities above a threshold requiring more intensive sampling. The system selects the correct counter at lot creation based on the lot quantity matching the Lot Size Range.
StatusLifecycle status of the plan4 = Released is required before the plan can be used in production. Plans in status 1 (Created) or 2 (In Process) are ignored at inspection lot creation. Always set status to 4 after completing configuration and before go-live. Reverting to a lower status after release requires authorization and change documentation.
UsageInspection scenario eligibilityDetermines which inspection types can reference this plan. Usage 5 is the standard for all standalone QM inspection types. Mismatching Usage and inspection type (e.g., assigning a Usage 9 plan to inspection type 01) results in the plan not being found at lot creation.
Valid FromPlan validity start dateThe plan is only selectable for inspection lots created on or after this date. Set to the project go-live date for new configurations. For replacement plans (revised tolerances), set the Valid From to the effective change date and close the predecessor plan’s validity to avoid ambiguity.
Lot Size From / Lot Size ToLot quantity range for plan applicabilityDefines the production or delivery quantity range in which this plan applies. A plan with Lot Size 1–9999 covers all standard batch sizes. If multiple Group Counters exist for the same material-inspection type, their lot size ranges must be non-overlapping and collectively exhaustive to avoid gaps.
PlantOrganizational assignmentThe Inspection Plan is plant-specific. A material used across multiple plants requires separate plans per plant (or separate MAPL assignments pointing to a centrally-maintained plan).

2.2 Operations (PLPO)

Stack layered diagram grouping operation fields by category: Identification, Work Center, Control Key, Standard Values

Operations define the physical inspection steps within the plan. Most QM-only inspection plans have a single operation, but complex manufacturing scenarios may require multiple operations representing sequential inspection stations.

FieldDescriptionPractical Usage
Operation Number (VORNR)Sequential step number (10, 20, 30, …)Standard SAP convention is to number in increments of 10 to allow future insertions without renumbering. For a single-operation plan, use 0010. For multi-step plans, define the logical flow (0010 = Incoming Visual Check, 0020 = Lab Measurement, 0030 = Final Release Check).
Work Center (ARBPL)Physical location / resource group for the inspectionReferences a Work Center master (CR01) with a QM-compatible control key. The Work Center determines capacity planning visibility for QM — if QM inspection load should appear in capacity evaluations, this assignment is critical. For simple implementations where capacity planning for QM is not required, a generic “QMWC” work center is often created as a placeholder.
Control Key (STEUS)Controls confirmation, cost, and print behavior for the operationFor QM operations, use a control key configured without production scheduling requirements but with inspection-relevant settings. Typically a dedicated QM control key (e.g., QM01) is created in Customizing. Inherits from the Work Center default if not overridden at the operation.
Operation Short TextDescription of the inspection stepFree text visible on the inspection lot and work instruction printouts. Write in the standard inspection language (English for global templates). Examples: “Dimensional Check,” “Visual Inspection — Surface,” “Tensile Strength Test.”
Standard Values (Setup, Machine, Labor Time)Time values for capacity and cost calculationOptional for QM-only plans. If QM labor costs are being tracked (e.g., activity-based costing for quality department), standard times must be maintained and the Work Center must have an activity type configured. For pure inspection planning without cost tracking, leave these blank.

2.3 Characteristic Assignments (QPAM)

Checklist of characteristic assignment fields: MIC reference, Sampling Procedure, Inspection Method, Required/Optional flag, Quantitative/Qualitative indicator, Short text

Characteristic assignments are the heart of the Inspection Plan — they define exactly which attributes are measured or evaluated, how they are sampled, and what constitutes a pass/fail. Each row in the characteristic list corresponds to one inspection step the operator or lab technician will perform.

FieldDescriptionPractical Usage
Master Inspection Characteristic (MIC)Reference to the MIC master record (QS21)The MIC carries all baseline parameters: tolerance limits, units of measure, and qualitative codes. Assigning the same MIC across multiple plans ensures that when tolerance standards change, a single MIC update (plus plan re-release) updates all referencing plans consistently. Do not manually re-enter field-level parameters at the plan level when a valid MIC exists — it creates maintenance duplication and version drift.
Characteristic Short TextDescription of this characteristic as displayed to the inspectorDefaults from the MIC short text. Can be overridden at the plan level for contextual clarity (e.g., “Outer Diameter — Incoming GR” vs. “Outer Diameter — Final Inspection”). Keep overrides minimal to preserve MIC-driven consistency.
Inspection Method (PRUEFMETH)Measurement method reference (QS31)Specifies how the characteristic is measured (caliper, gauge, visual, chemical analysis). Inherited from the MIC if assigned there; overridable at the plan level for scenario-specific measurement tools. Essential for industries requiring documented measurement traceability.
Sampling Procedure (DNAMV)Sampling plan override for this characteristicOverrides the default sampling procedure stored in the MIC. Use this to apply stricter sampling (e.g., 100% inspection) to critical safety characteristics while using reduced sampling for non-critical dimensions within the same inspection plan. This is the primary tool for risk-based inspection intensity design.
Required / Optional IndicatorControls whether skipping this characteristic triggers an errorMark safety-critical characteristics as Required (system error if no result is recorded). Mark informational or monitoring characteristics as Optional. The split between Required and Optional should be agreed with the quality engineering team during blueprint and documented in the inspection plan design specification.
Characteristic CategoryQuantitative (measurement) or Qualitative (attribute)Inherited from the MIC. Quantitative characteristics generate numeric results against upper/lower specification limits. Qualitative characteristics generate a pass/fail or coded result. This field cannot be changed at the plan level — it is fixed by the MIC definition.
Long-term Characteristics IndicatorFlags a characteristic for SPC (Statistical Process Control) data retentionWhen set, result data for this characteristic is retained in the long-term statistical database for trend analysis and control chart generation. Activating this flag significantly increases database volume — limit to characteristics under active SPC monitoring.

L1) Big Picture

IDCategoryTitle
qm-001OverviewWhat is SAP QM?

L2-A) Master Data

IDCategoryTitle
qm-a01OverviewSAP QM Master Data: Overview, Hierarchy & Relationships
qm-a02-01Master DataSAP QM Catalog
qm-a02-02Master DataSAP QM Master Inspection Characteristic
qm-a02-03Master DataSAP QM Inspection Method
qm-a03-01Master DataSAP QM Sampling Procedure
qm-a03-02Master DataSAP QM Dynamic Modification Rule
qm-a05-01Master DataSAP QM Material Master
qm-a04-01Master DataSAP QM Work Center
qm-a04-02Master DataSAP QM Inspection Plan 📍
qm-a05-02Master DataSAP QM Quality Info Record

L2-B) Transaction

IDCategoryTitle
qm-b01OverviewSAP QM Transactions: Process Flow, Hierarchy & Relationships