SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANAManufacturing

SAP QM Inspection Lot Origins Reference

The inspection lot origin tells SAP QM which event created the lot. Knowing the origin is the fastest way to find out why a lot was or was not created.

Download:
OriginEvent that creates the lotTypical transactionFirst thing to check if no lot appears
01
Goods receipt for a purchase order
MIGO
QM view of the material, inspection type 01 active, plant level QM in procurement
04
Goods receipt from a production order
CO11N, MIGO
Inspection type 04 active and plan found for the produced material
05
Goods receipt without a PO or production order
MIGO
Movement type linked to the origin and inspection type 05 active
08
Stock transfer posting
MIGO, MB1B
Inspection type 08 active in the receiving plant
09
Outbound delivery
VL01N, VL02N
Inspection type 09 active and SD delivery type allows inspection
14
Recurring inspection of stock
QA07
Recurring inspection interval and inspection type 14 in the material master
15
Inspection of a production resource or tool
QA01
PRT usage and inspection type 15 active
89
Manual creation of an inspection lot
QA01
Inspection type 89 active and plan or specification entered

Origins and their link to movement types are customizing. Confirm in SPRO, Quality Management, Quality Inspection, Inspection Lot Creation, and test with a real posting.

Optional help with missing inspection lots

Send us a case where lots are not created and we will help trace it through master data and customizing.

Optional. The tool and every export work without this. No spam.

How to use this reference

Find the event in your process, such as a goods receipt or a delivery, and read the origin and the first thing to check. If the lot is missing, work through the check column in order. If a lot appears but follows the wrong plan, look at the origin in the lot header and compare it with the inspection type in the material master.

How origins relate to inspection types

The origin is stored in the inspection lot and describes the process that created it. The inspection type is the setting that activates it for a material and plant. In standard setups both use the same numbers, which is why the two lists look alike. The origin also decides which movement types and documents can create lots and how stock is posted into quality inspection.

  • Origin is a property of the lot
  • Inspection type activates the origin for a material
  • Movement types are linked to origins in customizing
  • Lot header shows origin and inspection type together

Troubleshooting missing lots

Work through four checks. First, confirm that the event posted successfully. Second, read the QM view of the material in the plant that received the goods. Third, check customizing for the movement type and origin. Fourth, test with a manual lot using QA01 to prove the plan and inspection setup are correct. This sequence usually isolates whether the problem is master data, configuration or the event itself.

  • Posting completed and document number exists
  • Inspection type active in the correct plant
  • Movement type linked to the origin
  • Plan with correct usage and status found

Frequently Asked Questions

Where do I see the origin of an inspection lot?

The lot header, for example in QA03, shows the inspection lot origin and the inspection type. You can also use QA32 and add the origin to the list layout.

Why does a manual lot use origin 89?

Manual creation with QA01 uses the manual origin, so it does not depend on a goods movement. It is helpful for tests and ad hoc inspections.

Can I add my own inspection lot origin?

Yes, customizing allows custom origins, but plan this carefully. Each new origin needs inspection type settings, links to movement types and testing. Most companies reuse the standard ones.

Do S/4HANA releases change these origins?

The core origins remain, but details and apps differ by release. Always check your own system and release notes.

Netray can add an AI layer over SAP QM tables so teams ask why a lot was not created and get a grounded, read only answer. Reach out if that would help your support team.