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

Cover: SAP QM Master Inspection Characteristic — the reusable quality criterion linking Catalogs and Inspection Plans

SAP QM Master Inspection Characteristic

The Master Inspection Characteristic (MIC) is the reusable quality criterion that defines exactly what is measured or evaluated in a quality inspection. It stores the characteristic type (quantitative or qualitative), measurement unit, tolerance limits, and catalog assignments that drive results recording at the shop floor. Every Inspection Plan references one or more MICs to specify its inspection scope, and shared MICs eliminate duplicate maintenance when the same criterion applies to multiple materials or processes.


Part 1: Master Inspection Characteristic — Core Concepts (All Modules)

1.1 What Is the Master Inspection Characteristic?

Hub-and-spoke diagram showing the Master Inspection Characteristic at center, connected to Catalog, Inspection Plan, Inspection Method, Material Master, and Inspection Lot

The Master Inspection Characteristic is a reusable inspection criterion that decouples the definition of “what to inspect” from the plan that specifies “how and when to inspect.” A single MIC can be assigned to many Inspection Plans across different materials, work centers, and inspection types, ensuring that the measurement standard remains consistent and centrally managed.

AspectDetails
RoleDefines the inspection criterion: type of measurement, units, tolerances, and result evaluation logic
Modules using itQM (primary owner — all inspection types), PP (in-process inspection via Inspection Plan operations), MM (goods-receipt inspection tied to Material Master QM View)
TransactionsQS21 (Create) / QS22 (Change) / QS23 (Display) / QS2X (Mass display)
Key TablesQPMK (MIC master header and characteristic attributes) / QPMD (MIC defect catalog assignment)
S/4HANA noteMIC structure unchanged from ECC. Fiori app “Manage Master Inspection Characteristics” (F2358) provides a modern UI with version overview, but QS21/QS22/QS23 remain the primary maintenance transactions in most implementations.

1.2 Quantitative and Qualitative Characteristic Types

2x2 matrix comparing Quantitative and Qualitative MIC types: measurement approach, result recording, tolerance setup, and typical use cases

The most fundamental design decision for any MIC is whether it is quantitative (measured on a scale) or qualitative (pass/fail or attribute-based). This choice controls the entire results recording experience and the statistical evaluation available for that characteristic.

Characteristic TypeCodeUse CaseKey Behavior
QuantitativeQDimensional checks, weight, viscosity, tensile strength — any measured valueUpper and lower specification limits are defined. The system computes process capability (Cpk) and triggers defect recording when results fall outside tolerance. Measurement unit is mandatory.
QualitativeAVisual inspection, color check, functionality verification — pass/fail judgmentNo measurement unit. Result is recorded as “Accepted” or “Rejected” based on a selected set from the defect catalog. Simpler to set up but no SPC data.
Summarized CharacteristicSSummary of multiple sub-characteristics rolled into one valuationUsed when individual sub-inspection results must be aggregated into a single accepted/rejected verdict. Less common; typically reserved for complex final inspections.
Reference to Another CharacteristicRReuse tolerance limits and settings from a master reference MICInherits all settings from the referenced MIC at plan assignment time. Useful for standardizing tolerance bands across a product family without maintaining multiple independent records.

Design principle: Decide the characteristic type at blueprint. Changing a quantitative MIC to qualitative after results have been recorded requires archiving all historical inspection lots using that MIC — a costly remediation in production systems.


1.3 Organizational Levels and Data Hierarchy

The Inspection Characteristic (IC) master is entirely client-level — one IC such as “IC-DIA” (Diameter) is defined once and can be reused across any plant, material, or inspection plan. It does not belong to a plant or material by itself; it becomes plant/material-specific only once it is copied into an Inspection Plan Operation.

Hierarchy diagram showing client-level Inspection Characteristics (IC) linked to Inspection Method, Sampling Procedure, Certificate Profile, and Dynamic Modification Rule

Two of IC’s neighboring client-level masters are directly linked from the IC itself: an IC references exactly one Inspection Method (how the value is measured), and optionally a Certificate Profile (for outbound quality certificates). Sampling Procedure and Dynamic Modification Rule are also client-level masters used during inspection, but they are assigned at the inspection plan/operation level, not on the IC record itself — they sit alongside IC as siblings, not as its children.

The IC’s second half of the picture is plant-level: once copied into an operation, it becomes an Insp. Characteristic that carries its own concrete value and an optional back-reference to the originating IC.

Hierarchy diagram showing plant-level Inspection Plan Operations, each containing Insp. Characteristics copied from client-level Inspection Characteristics

Data hierarchy with a concrete example

Client 100
   │
   ├── IC "IC-DIA"        Diameter (quant.)
   │      │
   │      └── uses ──> Inspection Method "IM-CMM"   CMM Measurement
   │
   ├── IC "IC-SURF"       Surface (qual.)
   │      │
   │      └── uses ──> Inspection Method "IM-VIS"   Visual Inspection
   │
   ├── Sampling Procedure "SP-05"          AQL 1.0 · Level II
   ├── Dynamic Mod. Rule "DMR-Q10"         Skip after 10 pass
   └── Certificate Profile "CP-4711"       Outbound QM cert

Plant 1000
   │
   └── Inspection Plan "Group 50 / Cnt 1"   Material 4711
          │
          ├── 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"

Design principle: Keep Inspection Characteristics client-level and reusable. An IC only becomes plant/material-specific the moment it is copied into an operation as an Insp. Char. — the master itself stays generic so the same “IC-DIA” can serve every plant and material that measures a diameter the same way.


1.4 Integration with Other Master Data Objects

Hub-and-spoke showing Master Inspection Characteristic at center connected to Catalog, Inspection Method, Sampling Procedure, Inspection Plan, and Material Master QM View

The Master Inspection Characteristic sits at the intersection of the QM foundation layer and the planning layer. It draws from Catalogs and Inspection Methods, and feeds into Inspection Plans, which in turn activate on Material Masters.

ObjectRelationshipPractical Notes
Catalog (QS41)MIC references selected sets from defect, cause, and action catalogsA qualitative MIC requires at least a Usage Decision catalog assignment (Catalog Type 1) to drive the accepted/rejected result. Without this, results recording is incomplete and the inspection lot cannot be closed.
Inspection Method (QS31)MIC can reference an Inspection Method for measurement procedure documentationThe method is informational at the MIC level — it describes how to perform the measurement. Referencing a method on the MIC ensures consistent procedure documentation even when the same criterion is used in different Inspection Plans.
Sampling Procedure (QDV1)MIC can carry a default sampling procedureWhen a sampling procedure is assigned at the MIC level, it is proposed as the default at Inspection Plan characteristic assignment. Plan-level overrides are possible, giving flexibility without losing the standard default.
Inspection Plan (QP01)Many Inspection Plans reference one MICThis N:1 relationship is the core value of the MIC. A dimensional tolerance defined once in the MIC propagates to all plans that reference it. When a specification changes, update the MIC once rather than updating every plan individually.
Material Master (QM View)Inspection Plan (which uses MICs) is linked to the Material MasterThe MIC influences inspection lot creation indirectly: when a material with an active QM inspection type generates an inspection lot, the lot’s characteristics are derived from the MIC definitions in the assigned Inspection Plan.
Inspection LotMIC characteristics appear as result recording lines in the inspection lotDuring results recording (QE01/QE02), each MIC assigned to the plan operation becomes a row where the inspector enters measured values or pass/fail verdicts.

Part 2: QM-Specific Field Details

2.0 Scope of QM Ownership

Checklist showing QM consultant ownership across MIC data sections: General Data, Control Indicators, Catalog Assignment, and Version Management

Data SectionQM InvolvementNotes
General Data◎ OwnerCharacteristic key, short text, plant, status — the identity and lifecycle of the MIC
Control Indicators◎ OwnerQuantitative/qualitative type, measurement unit, specification limits, target value — the core inspection logic
Catalog Assignment◎ OwnerSelected sets for defect, cause, action codes — drives results recording and defect classification
Version Management◎ OwnerValidity dates, version status, change document — controls when a revised specification takes effect

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


2.1 General Data

Checklist of key MIC general data fields: Characteristic Key, Short Text, Plant, Status, Long Text, Inspection Method Reference

General Data forms the identity layer of the MIC. These fields determine how the characteristic is identified, where it is valid, and whether it is available for use in Inspection Plans.

FieldDescriptionPractical Usage
PlantPlant to which the MIC belongsDefines the scope of the MIC. A blank plant creates a cross-plant characteristic; populating a plant restricts it to that plant. In multi-plant deployments, establish a naming convention that embeds the plant code or a “GLOBAL” prefix so plant-independent MICs are immediately distinguishable during plan maintenance.
Characteristic KeyUnique alphanumeric identifier for the MICThe key is the primary lookup field in Inspection Plan characteristic assignment. Establish a structured naming convention early (e.g., DIM-001 for dimensional, VIS-001 for visual) — renaming MICs after they are referenced in active plans requires careful archiving and reassignment.
Short TextBrief description of the inspection criterionAppears as the characteristic label in QE01 results recording screens. Keep it concise but unambiguous: “Outer Diameter (mm)” is better than “OD” alone. Used in standard QM reports and inspection lot printouts.
StatusRelease status of the MIC (e.g., 4 = Released)Only MICs with Released status (4) can be assigned to Inspection Plans for production use. During blueprint and testing, use a preliminary status (1 or 2) to prevent accidental use. Set to Released only after sign-off by the QM process owner.
Long TextExtended description, measurement procedure notesOptional but recommended for complex characteristics. Appears in the Inspection Plan characteristic detail screen and can serve as a brief measurement instruction supplement to the formal Inspection Method.
Inspection Method ReferenceLink to an Inspection Method masterCarries the measurement procedure documentation (instrument type, measurement conditions, reference standard). Assigning a method at the MIC level ensures procedure consistency across all plans that use the MIC.

2.2 Control Indicators

Stack layered diagram grouping MIC control indicator fields: Characteristic Type, Measurement Unit, Specification Limits, Evaluation Settings, and Sampling

Control Indicators are the technical core of the MIC. They define exactly how the characteristic is measured, what constitutes a passing result, and how the system evaluates results to determine acceptance or rejection of an inspection lot.

FieldDescriptionPractical Usage
Characteristic TypeQuantitative (Q) or Qualitative (A)The most consequential setting on the MIC. Drives measurement unit requirement, results recording UI, and available statistical functions. Set at creation and treat as immutable in production — type changes require archiving historical data.
Control IndicatorCharacteristic class flags (e.g., measurement, attribute, summarized)A combination field that governs calculation type, SPC chart type, and whether the system can auto-accept based on measured values. Standard quantitative MICs use “M” (Measured Value); standard qualitative use “A” (Attribute). Confirm with the QM consultant lead before using non-standard values.
Measurement UnitUnit for quantitative characteristics (e.g., mm, kg, %)Must match the unit used by the measurement instrument and be defined in UoM Customizing. Inconsistent units between the MIC and the measuring gauge master are a common source of results recording errors during go-live testing.
Lower Specification Limit (LSL)Minimum acceptable value for quantitative characteristicsTriggers a defect recording entry when a measured value falls below this threshold. Set to the engineering drawing tolerance lower bound. Document the source drawing revision in the MIC long text to maintain traceability when tolerances are updated.
Upper Specification Limit (USL)Maximum acceptable value for quantitative characteristicsThe upper tolerance bound. The system flags a characteristic as rejected when the measured value exceeds USL. Maintain LSL and USL together — a MIC with only one limit set is valid but unusual; confirm with the process engineer that a one-sided tolerance is intentional.
Target ValueNominal or ideal valueUsed in SPC calculations (Cp, Cpk) and as the center line in control charts. Set to the nominal dimension from the engineering specification. Leaving target value blank disables Cpk reporting for this characteristic, which may be acceptable for non-critical dimensions but should be a deliberate decision.
Decimal PlacesNumber of decimal places for result entryControls result input precision in QE01. Match to instrument resolution and specification precision (e.g., 2 decimal places for mm dimensions measured with a caliper, 3 for micrometer measurements). Setting fewer decimals than the instrument resolution loses data; more decimals implies false precision.
Sampling ProcedureDefault sampling procedure for this MICProposed when assigning the MIC to an Inspection Plan operation. Can be overridden at the plan level. Assigning a default here enforces a sampling standard for the characteristic across all plans that use it, reducing inconsistency between plans maintained by different QM administrators.

2.3 Catalog Assignment

Checklist of MIC catalog assignment fields: Selected Set for Defect Codes, Cause Codes, Action Codes, and Usage Decision Codes

Catalog Assignment links the MIC to pre-defined code sets from the Catalog master (QS41). These assignments determine which defect codes, cause codes, and action codes inspectors can select during results recording, and which usage decisions are available when closing an inspection lot characteristic.

FieldDescriptionPractical Usage
Selected Set (Catalog Type 1 — Usage Decision)Code set for accepted/rejected/conditional verdictsRequired for qualitative MICs. The selected set restricts which usage decision codes are valid for this characteristic, preventing miscoding. For quantitative MICs, usage decisions are typically auto-generated from specification compliance but a selected set can still be assigned for manual override scenarios.
Selected Set (Catalog Type 3 — Defect Codes)Code set listing possible defect typesDefines which defect classifications the inspector can record when a result is non-conforming (e.g., “Dimensional Out of Tolerance,” “Surface Scratch,” “Contamination”). Assign a catalog-type 3 selected set to every MIC where defect recording is expected — results without a defect code are difficult to analyze in QM reports and quality notifications.
Selected Set (Catalog Type 5 — Cause Codes)Code set for root-cause classificationEnables root cause assignment at the characteristic level during results recording. Assign when this characteristic is part of a defect analysis workflow. Not all MICs require cause codes — prioritize critical-to-quality characteristics and those with historical defect patterns.
Selected Set (Catalog Type 9 — Action Codes)Code set for corrective actionsLinks corrective actions directly to the inspection characteristic result. Useful for characteristics where standard reactions are predefined (e.g., “Rework,” “Scrap,” “Return to Vendor”). Reduces dependency on quality notifications for routine disposition decisions.

Prerequisite: Catalog selected sets must exist in QS41 before they can be assigned to MICs. Catalog setup (QM-A02-01) must be completed before MIC creation in every project. Attempting to assign a non-existent selected set causes a hard error at MIC save.


2.4 Version Management

Hierarchy tree showing MIC version structure: Version 1 (initial release), Version 2 (tolerance update), with validity date ranges and status transitions

Version Management allows the MIC to evolve over time — for example, when engineering tolerances are tightened, a new version of the MIC becomes effective on a given date while historical inspection lots retain their original specification for traceability. This is one of the most operationally critical features of the MIC compared to characteristics defined inline in an Inspection Plan.

FieldDescriptionPractical Usage
VersionVersion number of this MIC definitionEach version is an independent record with its own validity period and status. Version numbers are system-assigned sequentially. Never delete a superseded version — historical inspection lots reference the version active at lot creation time, and deletion breaks traceability and audit trails.
Valid FromStart date of this MIC version’s effectivityThe date from which this version is used for new inspection lot characteristic assignment. Coordinate the Valid From date with the engineering change order (ECO) effective date and the Material Master revision level if applicable. A mismatch between the MIC Valid From and the ECO effective date is a common source of compliance findings during quality audits.
Valid ToEnd date of this MIC version’s effectivityAutomatically set when a new version supersedes this one, or manually entered for a planned end-of-life. Leave blank for an open-ended current version.
StatusRelease status of this versionMirrors the overall MIC status — each version must reach Released status (4) before it can be used in a production Inspection Plan. Use preliminary statuses (1 = Created, 2 = Reviewed) as workflow stages before the QM process owner grants final release.
Change DocumentSystem-generated change logRecords every field change with user, timestamp, and old/new value. Provides the audit trail required for ISO 9001 document control and AS9100 aerospace quality system compliance. In regulated industries, supplement the system change document with a manual change reason entry in the long text.

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