Results Recording Fundamentals: Why Quality Data Capture Drives the Usage Decision
Understand what results recording is, why it exists in the quality lifecycle, and how it links inspection characteristics, master data and the Usage Decision.
Explanation
Results Recording is the step in the SAP QM process where a quality inspector or lab technician enters actual measured, valuated, or classification data against the characteristics defined on an inspection lot. It sits between inspection lot creation (triggered by goods receipt, production order confirmation, or manual inspection) and the Usage Decision (UD), which determines whether the inspected material or batch can move forward in the supply chain, be blocked, be reworked, or be scrapped. Without accurate results recording, the UD becomes a guess rather than a data-driven decision, and downstream processes such as stock posting, invoice verification, and customer complaint handling lose their factual basis. Every inspection lot inherits its characteristics from an inspection plan (or from a routing/task list assigned to a material and plant). Each characteristic has a control indicator set (Required, Recording indicator, Lower/Upper Specification Limits, Sample size, and so on) that determines how the inspector interacts with it during recording: whether a single numeric value is expected, whether a code group/catalog selection is required (Boolean or classed characteristics), or whether summarized statistical results are entered instead of individual readings. The business purpose of results recording is threefold. First, it creates a verifiable, auditable quality record tied to the inspection lot, batch and material document - critical for regulated industries (pharma, automotive, aerospace) where traceability to raw data is a compliance requirement. Second, it enables statistical process control: recorded values feed control charts, capability indices (Cp/Cpk), and trend analysis when quality info records or SPC evaluation is configured. Third, it directly determines system behavior: characteristics with acceptance/rejection logic can automatically propose a Usage Decision code, trigger a quality notification for out-of-spec results, or lock the lot from being closed until all mandatory characteristics are recorded. In a typical beginner scenario, a goods receipt for a raw material triggers an inspection lot in origin 01. The inspector navigates to the results recording transaction, sees the list of characteristics from the assigned inspection plan (e.g., pH value, viscosity, appearance), enters values or a catalog code for each, and the system compares entered values against the specification limits stored in the characteristic master or plan. If a value falls outside tolerance, the system can flag the characteristic as rejected, and this rejection is one of the inputs the quality engineer uses when making the Usage Decision (accept, reject, accept with deviation, etc.). A foundational concept to grasp early is the distinction between the inspection lot (the header, holding origin, material, batch, quantity and status) and the inspection characteristics (the individual test parameters recorded within that lot). Results recording always happens at the characteristic level, but the system aggregates characteristic-level pass/fail status up to lot-level status, which in turn constrains what Usage Decision codes are available. Another foundational point is that results recording can be manual (typed by an inspector) or automatic, where measurement values are transferred from an external system (lab equipment, PLC data collection) via interfaces - though the interface mechanics themselves are a more advanced topic. Finally, beginners should understand that results recording is not just data entry; it is a controlled business transaction with statuses (e.g., record complete, characteristic results existing) that gate whether the lot can proceed to Usage Decision. Attempting to make a UD before all required characteristics are recorded is a common early configuration and process constraint that beginners encounter and must understand rather than bypass.
Real project scenario
A consumer goods company receives a raw material shipment. The MM goods receipt automatically creates an inspection lot (origin 01) because the material master has inspection setup active for that movement type. A quality technician opens the inspection lot, sees three required characteristics inherited from the inspection plan (appearance, moisture content, particle size), records a visual pass for appearance via a catalog code, types a moisture percentage that falls just above the upper specification limit, and the system automatically flags that characteristic as rejected. The technician cannot complete recording as 'fully passed' and the quality engineer is notified to review the lot before the Usage Decision is made, preventing the batch from silently entering unrestricted stock.
Common mistakes
• Assuming a Usage Decision can be entered before all required characteristics are recorded, then being blocked by lot status and not understanding why. • Confusing the inspection plan (master data defining what to test) with the inspection lot (the actual instance being tested) and editing the wrong object. • Entering values without checking measurement units, causing false out-of-tolerance flags. • Ignoring catalog codes for Boolean/qualitative characteristics and trying to force numeric entry. • Not recognizing that a characteristic marked 'not relevant' at the plan level will never appear in results recording, leading to confusion about missing tests.
Best practices
• Always verify the inspection plan/characteristic assignment before results recording begins, especially after material master or plan changes. • Record results as close to the actual measurement event as possible to preserve data integrity and timestamp accuracy. • Use catalog codes consistently for qualitative characteristics rather than free text, to keep statistics and reporting meaningful. • Treat any out-of-tolerance result as a trigger for review, not just a system flag to override quickly. • Confirm required characteristics are complete before attempting Usage Decision to avoid rework and status errors.
Interview angle
Interviewers commonly probe whether a candidate understands the sequence: inspection lot creation, characteristic inheritance from the inspection plan, results recording, and Usage Decision - and why skipping or reordering these steps breaks the audit trail. Be ready to explain the difference between a characteristic being 'recorded' versus 'valuated' (pass/fail), and why the Usage Decision cannot ignore rejected mandatory characteristics without a documented override.