SAP Knowledge Base Article

3461941 - 102 Movement Type does not update a 17-origin Inspection Lot Quantity
Component: SCM-EWM-QM (Supply Chain Management > Extended Warehouse Management > Quality
Management), Version: 1, Released On: 20.06.2024

Symptom
You work with quality inspection integration between ERP and EWM. For an IOT4 inspection process (Inbound inspection),
you post partial goods receipt and the quantity is reflected into the EWM inspection lot.
At some point, a reversal of the goods receipt is required, so you post a 102 movement from ERP (through MIGO, for
example) after the inbound delivery has been completed. But the inspection lot quantity that corresponds to the "Quantity to
be posted" field (QALS-LMENGEZUB) is not updated with this movement.

Environment
SAP S/4HANA;
SAP Extended Warehouse Management (SCM-EWM);
SAP Extended Warehouse Management Quality Management (SCM-EWM-QM);
SAP Extended Warehouse Management Goods Movement (SCM-EWM-GM);
SAP ERP Quality Inspection Engine (CA-QIE);
SAP ERP Quality Inspection Management (QM-IM);
SAP NetWeaver

Reproducing the Issue

1. After inspection lot creation and goods receipt completed, execute transaction "MIGO" (for example);
2. Input the data details;
3. Initiate a reversal movement (e.g. specifying movement type 102).

Cause
The 102 movement is posted after the inbound delivery completion (DCO=9). Since the putaway of the assigned inbound
delivery is completed, it is no longer possible to reverse the goods receipt.
So once the 102 movement is posted on ERP, this is reflected as a Goods Issue on EWM side.
A Goods Issue movement does not update an EWM inspection lot quantity. An IOT4 document is designed for inbound
process, so only a goods receipt reversal on EWM side will update the quantity of the inspection lot.

Resolution
Putaway warehouse task to final bin should not be confirmed before quality inspection decision.
For workaround, there are 2 possibilities:
1. Adjust the PPF logic to check if the inbound delivery is quality-relevant.
If it is, do not create the putaway task to final bin immediately after goods receipt and use the follow-up action
"Putaway" to create the WT after taking Usage Decision for the inspection lot assigned;
OR
2. Set the flag "Forbid Goods Issue of Quality Stock" in EWM customizing (SPRO).
This will restrict the GI posting in case the stock still contains the inspection reference, so you will need to post the
Usage Decision before goods issue which will avoid a mismatch on the inspection lot quantity and MD04 calculations.

See Also
2551912 - Goods Receipt Reverse not possible by EWM inbound delivery
 Keywords
LMENGEIST, LOSMENGE, 101, QA11, /SCWM/PRDI, QA03, MRP, IOT3, IOT5, /SCWM/QIDPR, QA03, SE16, Embedded,
Decentral, Decentralized,quality stock, lot origin 17, lot, document,EWM inspection, GI, GRR, Goods Issue, Goods Receipt
Reversal, QALS, LMENGEIST, QALS-LMENGEIST,Quantity to Be Posted,.

Attributes
Key Value

Other Components Supply Chain Management > Extended Warehouse Management > Goods Movements (SCM-EWM-GM)

Other Components Cross-Application Components > Quality Inspection Engine (CA-QIE)

Other Components Quality Management > Quality Inspection (QM-IM)

Requires Action 0

Products
Products

SAP ERP all versions

SAP Extended Warehouse Management all versions

SAP NetWeaver all versions

SAP S/4HANA all versions