Results Recording and Usage Decision on Inspection Lots
Learn how characteristic results are recorded against an inspection lot's operations/characteristics, how sample size and valuation rules drive pass/fail logic, and how the Usage Decision (UD) closes the lot and triggers stock posting.
Explanation
An inspection lot is only a shell until someone records results against its inspection characteristics and confirms a Usage Decision. Once a lot is created (from goods receipt, in-process inspection, or a manual QA01 style entry), the system copies the inspection plan or master inspection characteristics valid at that time into the lot as a fixed snapshot. This means changing the inspection plan later does not retroactively change already-created lots - a common source of confusion in support tickets ('why is the old plan version still showing?'). Results recording happens against each characteristic in each operation of the lot. For quantitative characteristics, the inspector enters measured values; the system compares them against the tolerance (upper/lower specification limits) copied from the plan or characteristic master, and calculates a preliminary valuation (accepted/rejected) automatically if automatic valuation is configured. For qualitative characteristics, the inspector selects a code (e.g., 1 = OK, 2 = defect type A) from an assigned catalog. Sample-drawing procedures attached to the plan determine how many units must be inspected: fixed sample size, percentage-based, or a sampling scheme (e.g., based on lot size and AQL tables) that dynamically calculates sample size at lot creation. Defects can be recorded directly during results recording, each linked to a defect catalog (code group + code), a defect class (critical/major/minor), and optionally a location on the object. These defects feed downstream into quality notifications if a follow-up action is triggered. Once all mandatory characteristics have results (or the inspector overrides completeness with authorization), the lot is ready for a Usage Decision. The UD is selected from a UD catalog (e.g., A = Accepted, R = Rejected, PA = Partially accepted) and each UD code carries follow-up actions: stock posting to unrestricted, blocked, or return stock; automatic creation of a quality notification; certificate generation; or triggering of a subsequent inspection. The UD is what actually 'closes' the business transaction - a goods receipt inspection lot sitting in quality inspection stock will not move until UD is set, which is why UD delays are a frequent cause of blocked material and expediting calls from warehouse teams. In S/4HANA, the same underlying logic exists, but the Manage Inspection Lots and Inspection results Fiori apps provide a browser-based results/UD experience alongside the classical transactions; the data model and valuation rules are functionally unchanged, though app-based catalogs and layouts may differ slightly from GUI screen variants. Some public cloud scope items constrain catalog and follow-up action configuration to predefined content, so verify what is exposed before assuming on-premise flexibility is fully available.
Real project scenario
A pharmaceutical raw-material plant found that goods receipts were sitting in quality stock for days because inspectors keyed results correctly but never executed the Usage Decision, since UD authorization was restricted to a QA supervisor role that wasn't monitoring a work queue. The fix was procedural: a report-driven worklist showing lots with completed results but no UD, reviewed daily, plus authorization changes granting UD rights to a wider inspector group for pre-approved decision codes, with supervisor review reserved for rejections only.
Common mistakes
• Assuming a corrected inspection plan automatically updates characteristics on already-created open lots • Recording results but forgetting to trigger the Usage Decision, leaving stock stuck in quality inspection • Misconfiguring automatic valuation so numeric results within tolerance still require manual override • Not training inspectors on defect catalog usage, resulting in inconsistent or missing defect codes • Allowing UD codes with stock-posting follow-up actions to be assigned without required authorization checks
Best practices
• Configure automatic valuation for quantitative characteristics to reduce manual review workload • Build a monitoring worklist for lots with completed results awaiting Usage Decision • Align UD catalog codes with clear, unambiguous business meaning (avoid overlapping accept/reject semantics) • Restrict authorization for UD codes that directly release stock to trained, accountable roles • Document defect catalogs and codes consistently across plants sharing the same client
Interview angle
Interviewers often probe whether you understand that inspection lots freeze the inspection plan at creation time, and how automatic valuation versus manual UD interacts with stock posting; be ready to explain the difference between a preliminary characteristic valuation and the final Usage Decision, and how UD follow-up actions differ (stock posting vs notification creation vs certificate trigger).