Quality Managementadvanced

Inspection Characteristics, Sampling Procedures and Defect Recording in Production (Part 3)

Key takeaway

Design master inspection characteristics, sampling procedures and defect recording so production quality is statistically meaningful, repeatable and comparable across orders and plants.

Explanation

A master inspection characteristic defines what is inspected and how: quantitative or qualitative behavior, unit, limits, catalog references and related control settings. Reusing MICs standardizes quality semantics.

Sampling procedure determines how much material or how many units are inspected and can incorporate fixed sample, percentage or more advanced sampling rules depending on configuration. The sample size must match quality risk and process capability; 100% inspection is not automatically better if it adds delay without value.

Defect recording captures nonconformities beyond the characteristic result and can classify defect type, location, cause or severity for analysis and follow-on notification/action.

The combination should support both acceptance decisions and continuous improvement. Too many local characteristics and free-text defects make cross-plant quality analytics impossible.

Order-related inspection lots and results recording remain conceptually identical across ECC and S/4HANA. S/4HANA adds Fiori-based shop-floor quality apps and, in some releases, tighter production-order/MES integration options on top of the same underlying model.

Real project scenario

Three plants measured the same dimension with different locally created characteristics and units. Corporate defect reporting could not compare results. Harmonizing MICs and sampling rules enabled common SPC and supplier/process analysis.

Common mistakes

Creating duplicate MICs for the same characteristic.
Choosing sample size without risk rationale.
Using free-text defects only.
Mixing units/limits across plants.
Recording defects with no follow-up.

Best practices

Standardize reusable MICs.
Base sampling on quality risk.
Use governed defect catalogs.
Harmonize units/limits.
Connect defects to corrective action.

Interview angle

Explain MIC, sampling procedure and defect record as different but connected quality objects.

Practice this lesson

Quick check

1. Scenario — Three plants measured the same dimension with different locally created characteristics and units. For the lesson "Inspection Characteristics, Sampling Procedures and Defect Recording in Production", which response shows the strongest architecture and production judgment?

2. When a recorded characteristic result during production falls outside its specification limits and needs formal follow-up on the defect, which SAP QM object is typically created to document and track corrective action?

3. What SAP QM functionality allows results to be recorded for the same inspection lot at multiple distinct stages of a production process, such as after each operation?

Interview questions

1. You are the senior consultant/architect responsible for Inspection Characteristics, Sampling Procedures and Defect Recording in Production. The project situation is: Three plants measured the same dimension with different locally created characteristics and units. How would you assess the design, identify the highest-risk failure modes, and define the evidence required before approving it for production?

Answer it in your own words first, then compare.

2. You are the senior consultant/architect responsible for QM in Production: Inspection Lots, Operations and Results Recording. The project situation is: A machining operation recorded diameter checks in Excel while SAP held the production order. How would you assess the design, identify the highest-risk failure modes, and define the evidence required before approving it for production?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.