SAP Inspection Lots Tutorial (Part 1)

📌 KEY POINTS
✅ The inspection lot ties a physical quantity of material to a defined inspection plan — and drives stock posting behavior.
⚠️ Material in quality-inspection stock is blocked from unrestricted use until a usage decision is made — that's the core control mechanism.
💡 The inspection lot origin (a 2-character key) determines which inspection-type settings and control indicators apply.

━━━━━━━━━━━━━━━━━━━━
▶ 1. WHAT AN INSPECTION LOT IS

• The document object SAP QM creates for a discrete quantity of material or event requiring inspection
• Generated automatically by a triggering transaction — GR against a PO, production-order-operation confirmation, outbound delivery creation
• NOT something a user typically creates manually

━━━━━━━━━━━━━━━━━━━━
▶ 2. WHY IT MATTERS

• Ties physical quantity (in quality-inspection stock) to an inspection plan/MICs
• Drives stock posting behavior — material stays blocked from unrestricted use until usage decision is made
• This is the core mechanism preventing unverified material from being consumed, sold, or moved into production

━━━━━━━━━━━━━━━━━━━━
▶ 3. STRUCTURE

• Header data: material, plant, lot quantity, origin, status
• Operations (if routing/plan has multiple), sample-relevant data, characteristics, eventual results and usage decision
• Status network: created → released → in results recording → usage decision made → closed/completed

━━━━━━━━━━━━━━━━━━━━
⚠️ 4. THE STOCK-QUANTITY WATCH POINT

• Lot quantity should match stock quantity in inspection status
• Partial usage decisions and stock postings can create divergence — support consultants must watch for this

━━━━━━━━━━━━━━━━━━━━
▶ 5. ACROSS RELEASES

• Concept unchanged in S/4HANA; Fiori apps and CDS-based analytics supplement classic transactions
• Public cloud typically exposes this via preconfigured scope items with more restricted customization — verify what's configurable rather than assuming on-premise parity

✅ CHECKPOINT: explain the mechanism that prevents unverified material from being consumed or sold.

A pharmaceutical manufacturer implementing S/4HANA needed every raw material goods receipt to be quarantined until a QA release. The consultant configured the material master QM view so quality inspection was active at goods receipt, which meant every purchase order receipt automatically created an inspection lot with the goods-receipt origin and posted the quantity to quality inspection stock instead of unrestricted-use stock. Warehouse staff initially expected to move received pallets directly into storage, so the project team had to run training explaining that the inspection lot, not a manual hold, was blocking usage until QA recorded results and made a usage decision.

• Assuming inspection lots must be created manually; in standard processes they are almost always system-generated from a triggering transaction.
• Confusing the inspection lot quantity with total plant stock, leading to incorrect reconciliation during audits.
• Not realizing that activating the QM view on a material after stock already exists will not retroactively inspect existing stock.
• Overlooking that a lot's origin determines default control indicators, then being surprised when behavior differs between goods receipt and in-process lots.
• Treating quality inspection stock as merely informational rather than as an actual stock-blocking mechanism tied to usage decisions.

• Always verify the QM view and inspection setup exist for a material-plant combination before assuming inspection will trigger.
• Document which origins are active for each material category early in a project to avoid unexpected lot volumes.
• Educate warehouse and production users that inspection lots, not manual blocks, control stock usability.
• Reconcile inspection stock quantities against open inspection lots periodically to catch discrepancies early.
• When troubleshooting missing inspections, check inspection setup, origin activation, and quality info records together rather than assuming a single cause.

Interviewers often ask candidates to explain, in their own words, what triggers inspection lot creation and how the lot relates to stock type. A strong answer distinguishes between manual inspection lots (rare, used for ad hoc situations) and automatically triggered lots from origins like goods receipt, production, or delivery, and explains the link to quality inspection stock as the core control mechanism, not just a status flag.