SAP defines an inspection lot as a request to carry out a quality inspection for a specific quantity of material or, in relevant scenarios, equipment or functional locations. The inspection-lot record is used to manage inspection processing information, specifications, recorded results, defects and the usage decision.
What causes an inspection lot?
Inspection lots can be created automatically or manually, depending on the scenario and configuration. SAP QM can automatically create lots from logistics events such as goods movements, production or process orders, deliveries, maintenance orders and recurring-inspection deadlines. The inspection lot origin describes the business reason for the lot, while the inspection type controls how that inspection is processed.
What information does the lot carry?
| Information | Why it matters |
|---|---|
| Origin, dates and status | Explains why the inspection exists and where it is in processing. |
| Inspection specifications | Define what is to be checked, often from a task list or material specification. |
| Results | Store recorded characteristic values from the inspection. |
| Defects | Capture quality problems identified during inspection. |
| Usage decision | Records the decision on whether the inspected goods are accepted or rejected and can drive follow-up. |
Inspection lot and inspection type are not the same
The inspection lot is the individual inspection record. The inspection type is a control that links a business process to the quality inspection and influences processing. When an automatic business event occurs, SAP uses the lot origin and active material inspection settings to determine the applicable inspection type.
Start with the triggering business event.
If a user asks why an inspection lot did or did not appear, first identify the event—goods receipt, production, delivery, recurring inspection or another origin—then inspect the material's active inspection setup and the relevant QM configuration.
Why inspection lots matter beyond QM
They are integration points. A goods receipt can trigger quality inspection from procurement; production can create in-process or receipt inspections; deliveries can trigger outbound quality checks; maintenance can trigger calibration-related inspections. The lot therefore carries quality processing into a broader logistics process rather than operating as an isolated QM object.
What should a beginner remember?
- The inspection lot represents a specific inspection request.
- The lot origin explains why it was created.
- The inspection type influences how it is processed.
- Specifications define what to inspect; results record what was found.
- The usage decision closes the quality decision loop.