Quality Managementadvanced

QM in Production: Inspection Lots, Operations and Results Recording (Part 2)

Key takeaway

Integrate quality with production by generating in-process inspection lots and characteristics tied to operations, then record results without separating quality from the manufacturing context.

Explanation

QM in production can create inspection lots for in-process inspection according to material and process setup. Inspection characteristics can be linked to routing/master inspection characteristics and assigned to production operations.

Results recording captures measured values, qualitative codes or summarized outcomes. The quality result should retain reference to material, order, operation, characteristic, sample and inspector so process capability and defect trends can be analyzed.

In-process inspection differs from final goods-receipt inspection: its purpose is to detect process drift before the entire order is complete. Use inspection points or partial results where the manufacturing process requires repeated checks.

Do not create duplicate quality data in spreadsheets when SAP already has the production/inspection context. The value comes from linking quality result to the exact operation and order.

Integration with production status and confirmation needs clear rules for what happens when characteristics fail.

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

A machining operation recorded diameter checks in Excel while SAP held the production order. Defects were discovered only at final inspection. Moving the characteristic into in-process QM allowed earlier detection and traceable order-level analysis.

Common mistakes

Treating in-process QM as final inspection only.
Recording results without operation context.
Duplicating quality data outside SAP.
Having no reaction plan for failed characteristics.
Ignoring sampling/inspection-point design.

Best practices

Link characteristics to process operations.
Define reaction to failure.
Capture traceable samples/results.
Avoid duplicate external records.
Analyze trends by operation/work center.

Interview angle

Explain how production order/routing context drives inspection lots and results recording.

Practice this lesson

Quick check

1. Scenario — A machining operation recorded diameter checks in Excel while SAP held the production order. For the lesson "QM in Production: Inspection Lots, Operations and Results Recording", which response shows the strongest architecture and production judgment?

2. Which inspection type allows a quality check to occur during manufacturing operations without requiring a goods movement or being tied to a goods receipt posting?

3. In production quality inspections, what is the purpose of combining a dynamic modification rule with a quality level for a material?

Interview questions

1. 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.

2. 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.

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.