Configuring Results Recording: Control Keys, Single vs Summarized Recording, and Inspection Points (Part 2)

Once the basic recording workflow is understood, the intermediate consultant must know how the system's behavior during results recording is actually configured through characteristic control indicators, sampling procedures, and recording modes, since these decisions materially affect inspector workflow, data volume, and statistical usefulness.

Every quantitative or qualitative characteristic assigned to an inspection plan carries a control indicator set that determines: whether the characteristic is mandatory to record, whether specification limits apply and are checked automatically, whether an SPC criterion is active, whether the characteristic is scope-relevant for a particular usage decision code, and critically, whether it requires single-value recording or summarized (aggregate) recording. Single-value recording captures each individual sample measurement (e.g., ten separate weight readings from ten units), enabling full statistical analysis, control charting, and traceability to each unit tested. Summarized recording captures only aggregate results (e.g., number of units tested, number accepted, number rejected) and is typically used for attribute-type characteristics or Boolean pass/fail checks where recording each unit's exact value is unnecessary or impractical.

The sampling procedure attached to the inspection plan (via the sample size determination, which can be fixed, percentage-based, or driven by a sampling scheme/plan referencing AQL tables) determines how many units the inspector should actually test and record. In results recording, the system shows the target sample size, and the inspector's entered count is validated against it; incomplete sample entry can block the characteristic from being marked complete, which in turn blocks the inspection lot from moving to Usage Decision if the characteristic is mandatory.

A critical intermediate-level concept is inspection points, used heavily in process industries and repetitive/discrete production scenarios where a single inspection lot spans multiple partial confirmations, batches, or time-based samples (for example, one inspection lot covering an entire production order, with results recorded at multiple points during the shift). Inspection points allow results recording to be tied to a specific point in time or a specific partial lot quantity, rather than recording one flat result set for the whole lot. This is essential in continuous production where quality can drift within a single lot, and where the Usage Decision may need to consider trends across multiple points rather than a single snapshot.

Configuration decisions here have real consequences for reporting and compliance. Choosing single-value recording generates far more data (useful for Cpk calculation and SPC control charts) but requires more inspector time and system storage; choosing summarized recording is faster but loses granularity needed for capability studies. Getting this wrong for a regulated characteristic (e.g., a critical-to-quality dimension in an automotive part) can mean the quality system technically cannot demonstrate statistical control even though inspections were performed, because the underlying individual values were never captured.

Another configuration lever is the characteristic's relationship to the master inspection characteristic (MIC): control indicators can be defaulted from the MIC and then overridden at the plan level for a specific material/plant combination, which is useful when the same physical test (e.g., moisture content) has different tolerances or recording requirements across product lines. Consultants must trace whether a control indicator was inherited or explicitly overridden when troubleshooting unexpected recording behavior, since a change at the MIC level can silently affect many inspection plans unless overrides are in place.

In S/4HANA, results recording is available both in the classic SAP GUI transactions and via Fiito Fiori apps oriented toward record results, with the underlying control indicator logic remaining conceptually consistent with ECC; however, some Fiori apps present a more results-oriented, task-based UI (worklist of open inspection lots/characteristics) rather than the lot-centric navigation typical of the GUI transaction, which changes how inspectors are trained even though the configuration data model is largely unchanged. Consultants should validate, per system and release, which recording channels (GUI, Fiori, external interface) are actually enabled before designing training or support processes, rather than assuming universal parity.

An automotive supplier needs Cpk reporting on a critical bore diameter dimension for customer PPAP submission. During inspection plan setup, the quality engineer configures the characteristic for single-value recording with a sample size of 30 units per lot, referencing a sampling procedure that enforces this exact count in results recording. A separate cosmetic-appearance characteristic on the same plan is configured for summarized recording with a simple accept/reject catalog, since no statistical study is required for it. During go-live, an inspector reports being blocked from completing recording because only 28 of 30 required samples were entered; support traces this to the sampling procedure's fixed sample size and confirms this is expected behavior, not a defect, and the inspector completes the remaining two measurements.

• Configuring single-value recording for high-volume attribute checks, generating excessive data with no analytical benefit.
• Overriding control indicators at the plan level without documenting the deviation from the master inspection characteristic, causing confusion during later master data audits.
• Underestimating sample size requirements from the sampling procedure, leading to inspectors being blocked mid-recording without understanding why.
• Treating inspection points as optional in continuous production scenarios, resulting in a single averaged result that hides in-lot quality drift.
• Assuming Fiori and GUI recording apps in S/4HANA behave identically in every release without validating available features first.

• Reserve single-value recording for characteristics requiring statistical process control or capability analysis; use summarized recording for simple attribute checks.
• Document any control indicator overrides at the plan level against the master inspection characteristic to preserve traceability during audits.
• Align sampling procedure sample sizes with actual production/inspection capacity before go-live to avoid inspector confusion.
• Use inspection points for any scenario where quality can vary within a single inspection lot, such as continuous or long-running production orders.
• Validate available recording channels (GUI transaction, Fiori app, external interface) per system release rather than assuming feature parity across environments.

Expect questions distinguishing single-value from summarized recording and when each is appropriate, along with the business impact on SPC/Cpk reporting. Strong candidates can also explain how inspection points support multi-sample lots in process manufacturing and why sample size determination is tied to the sampling procedure rather than being freely typed by the inspector.