Recording Results Against Characteristics and Samples
Learn how inspectors enter quantitative and qualitative results per characteristic and sample unit, how valuation rules determine pass/fail, and how catalogs capture defects during results recording.
Explanation
Results Recording is the step where the inspection plan meets reality: an inspector or automated interface enters the actual measured or observed values for each inspection characteristic on an inspection lot, and the system valuates those values against the plan's specification limits to determine whether the characteristic is accepted or rejected. This matters because the Usage Decision, batch status, stock posting, and any downstream notification or SPC trend all depend on accurate, timely results capture. If recording is sloppy, incomplete, or entered against the wrong sample, the quality decision built on top of it is unreliable even though the transaction completes successfully. In practice, results recording starts from a worklist of open inspection lots, typically filtered by material, plant, or inspection type. For each lot, the inspector selects a characteristic and records either single values (each sample unit recorded individually), summarized results (one representative value for the sample), or a defects-only entry using a catalog. The choice depends on how the master inspection characteristic (MIC) and the sampling procedure were configured in the inspection plan: MICs flagged for single-value recording require entry per sample unit, useful for quantitative characteristics like dimensional measurements where you want statistical evidence per unit; summarized recording is faster and appropriate for attributes where one entry represents the whole sample, such as a visual check. Each characteristic in the plan carries specification limits (target, upper, lower) or a pass/fail indicator if it is qualitative. When a value is entered, the system automatically valuates it against these limits and proposes an acceptance or rejection at the characteristic level, which is separate from and feeds into the eventual lot-level Usage Decision. Characteristics can also be marked as not inspected, skipped, or valuated manually if a control indicator or dynamic modification rule permits a deviation from full recording -- but any manual override should be traceable and usually requires a reason code, especially in regulated environments. Defects are recorded using a catalog structure (a hierarchy of defect types, codes, and groups configured at the client or plant level) rather than free text, which keeps the resulting quality data structured for later Pareto analysis or trend reporting. When a characteristic fails or a defect is logged, the system can automatically trigger creation of a quality notification if the inspection type or characteristic configuration is set to propose one, linking the physical defect finding directly into the CAPA workflow. A critical integration point is that results recording is lot-specific: the correct inspection lot must be open and not already closed by a Usage Decision, and the sample size shown must match what was actually drawn on the shop floor or receiving dock -- discrepancies here are a common source of audit findings. In ECC this work is typically done in the classic results recording transaction with characteristic overview and single-result screens; in S/4HANA the same logic is exposed through Fiori apps that present a similar worklist-and-detail pattern but with a more modern, task-based UI and better support for mobile or tablet-based entry. The underlying valuation and specification logic is functionally consistent, but the presentation layer, personalization options, and integration with system-wide search differ.
Real project scenario
A pharmaceutical packaging plant found that operators were recording all dimensional checks as summarized results even though the inspection plan characteristics were configured for single-value recording, because the summarized entry screen was faster. This meant the statistical sample data required for the annual product quality review was missing individual data points, forcing a manual reconstruction from paper logs before the audit. The quality team retrained operators, adjusted the worklist layout to default to the single-value screen, and added a lot-level check before Usage Decision that flagged any characteristic where the recorded sample count did not match the plan's sample size.
Common mistakes
• Recording summarized results against characteristics configured for single-value recording, losing statistical granularity needed for SPC or audits • Entering results against the wrong inspection lot when multiple lots exist for the same material and delivery, causing incorrect batch disposition • Free-texting defect descriptions instead of using the configured catalog, breaking Pareto and trend reporting • Overriding a failed characteristic valuation without a documented reason code, creating an audit gap • Assuming results recording alone closes the lot -- forgetting that a separate Usage Decision step is still required
Best practices
• Configure MICs for single-value recording whenever individual sample-unit data feeds statistical process control or regulatory reporting • Enforce catalog-based defect entry rather than free text so defect data remains analyzable • Reconcile the recorded sample count against the physical sample drawn before allowing the lot to proceed to Usage Decision • Require documented reason codes for any manual valuation override • Validate that inspection type and characteristic settings for automatic notification creation match the organization's CAPA policy before go-live
Interview angle
Interviewers use this topic to check whether a candidate understands the difference between characteristic-level valuation and the lot-level Usage Decision, and whether they know when single-value versus summarized recording is appropriate. Be ready to explain how a failed characteristic can automatically trigger a notification and how catalogs structure defect data for later analysis.