Master Inspection Characteristics and Sampling Procedures in Inspection Plans

Explanation

Inspection planning becomes maintainable at scale only when characteristics and sampling logic are standardized rather than re-entered on every plan. A master inspection characteristic (MIC) is a reusable definition of what to inspect - for example 'Length', 'Surface Finish', or 'Weight Tolerance' - along with its control indicators, valuation rules (quantitative or qualitative), and default sampling procedure. MICs are created and maintained centrally (in ECC and S/4HANA on-premise this is done via the QM master data characteristic transactions, commonly referenced as QS21-family functions) and then referenced inside inspection plans rather than duplicated. This gives three benefits: consistent measurement units and tolerances across plants, faster plan creation because planners pull existing characteristics, and easier mass changes because updating the MIC master record can propagate to all plans referencing it (subject to plan status and change control). Each characteristic in a plan operation carries control indicators that decide behavior at inspection lot creation and results recording time: whether the characteristic is mandatory, whether it triggers automatic acceptance/rejection based on tolerance, whether skip lot logic can bypass it, and whether it requires a certificate print. These indicators are set at the plan level but often inherited from the MIC's default control key, which planners can override per plan if local requirements differ. Sampling procedures determine how much and how the population is inspected - fixed sample size, percentage sampling, sampling by attributes (e.g., referencing AQL-style sampling schemes), or 100% inspection. The sampling procedure is attached either to the whole inspection plan (as a default) or to individual characteristics, allowing a plan to have some characteristics inspected 100% (safety-critical dimensions) while others use reduced sampling (cosmetic attributes). Sampling procedures are configured with sample sizes, valuation modes and, when using statistical schemes, links to sampling scheme tables that define acceptance numbers by lot size. A practical constraint every intermediate planner must understand: master characteristics and sampling procedures are typically maintained under a plant or a cross-plant usage scope, and inspection plans reference them by key and version. Because MICs can be shared across many plans, changing a live MIC's tolerance or unit of measure has a wide blast radius - this is where engineering change management and plan status (released vs. in-work) become critical, which is expanded in advanced integration lessons. From a runtime perspective, when an inspection lot is created, the system resolves the plan, pulls the characteristics with their control keys and sampling procedures, and generates worklist items for results recording. Any mismatch between what a MIC master defines and what the plan operation actually needs (wrong sampling procedure assigned, missing tolerance limits) surfaces only during results recording or usage decision, often too late for the current lot - making design-time validation of MIC and sampling assignment a key quality-of-plan checkpoint before release.

Code example

Example plan structure (illustrative, not a system export):Inspection Plan: Material FG-1001, Plant 1000, Usage: 5 (Goods Receipt) Operation 0010 (Dimensional Check)  Characteristic 10: MIC 'LENGTH_MM' - Quantitative, Tolerance 100mm +/-0.5, Sampling Proc: FIXED_5  Characteristic 20: MIC 'SURFACE_FINISH' - Qualitative, Catalog-based defect codes, Sampling Proc: PCT_10 Operation 0020 (Weight Check)  Characteristic 10: MIC 'NET_WEIGHT_KG' - Quantitative, Tolerance 2.0kg +/-0.05, Sampling Proc: FULL_100 Note: FIXED_5 = fixed sample of 5 units; PCT_10 = 10% of lot; FULL_100 = 100% inspection for safety-critical weight check.

Real project scenario

A discrete manufacturing client had inconsistent tolerances for the same dimensional check across three plants because each site created its own free-text characteristic instead of using a shared master inspection characteristic. During a customer audit, inspectors discovered plant A used +/-0.5mm while plant B used +/-0.3mm for the same part family, with no documented rationale. The remediation project consolidated characteristics into shared MICs with plant-specific sampling procedures only where genuinely justified (e.g., higher-volume line using percentage sampling versus a low-volume line using 100% inspection), then repointed inspection plans to the standardized MICs during a controlled cutover aligned with a change number.

Common mistakes

• Creating a new master inspection characteristic for every plan instead of searching for and reusing an existing one, causing duplication and inconsistent tolerances. • Assigning a sampling procedure that does not match the lot size ranges configured in the sampling scheme, causing sample size calculation errors at inspection lot creation. • Overriding control indicators at the plan level without documenting why, making it unclear later whether a deviation from the MIC default was intentional. • Changing a widely-used MIC's tolerance directly in production without impact analysis on all plans referencing it. • Mixing qualitative and quantitative valuation logic on the same characteristic definition, leading to invalid results recording screens.

Best practices

• Search existing master inspection characteristics before creating new ones; enforce a naming/search convention for discoverability. • Assign sampling procedures at the most specific level needed - global default for the plan, exceptions per characteristic only when risk justifies it. • Document any deviation from a MIC's default control indicators directly in the plan's long text. • Treat changes to widely-used MICs as controlled changes requiring impact analysis and change number linkage. • Periodically audit sampling procedure assignments against current lot volumes to avoid outdated sample sizes.

Interview angle

Interviewers commonly probe whether a candidate understands the difference between characteristic-level and plan-level sampling assignment, and how master data reuse affects maintainability. Be ready to explain how you would investigate a reported tolerance discrepancy across plants and what governance you would put in place before allowing plan release with shared master characteristics.