In an SAP S/4HANA Embedded EWM system, we are facing stock inconsistencies between EWM and ERP.
Issue description:
-
Stock quantity in EWM does not match ERP stock
-
Difference observed at storage location or batch level
-
Physical inventory completed successfully, but mismatch still exists
-
No open warehouse tasks or deliveries are found
System behavior:
-
EWM shows stock available, ERP shows zero (or vice versa)
-
Posting changes are not synchronizing correctly
-
No CIF or queue errors visible at first glance
Checks already performed:
-
/SCWM/MON stock overview
-
SMQ1 / SMQ2 queues
-
Physical Inventory documents closed
-
No open WTs or deliveries
Despite this, stock difference remains.
Questions:
-
What are the most common reasons for stock mismatch between SAP EWM and ERP?
-
Which reports and monitors should be checked to identify the root cause?
-
What is the safest way to correct stock differences in production systems?
-
When should stock be corrected in EWM vs ERP?
Looking for a practical troubleshooting guide based on real project experience.
Stock mismatch between SAP EWM and ERP is a very common production issue and usually indicates that a posting or synchronization step was interrupted or bypassed. Even when no open tasks or queues are visible, inconsistencies can still exist at a deeper level.
Below is a practical, real-project troubleshooting guide.
1. Understand Where the Mismatch Exists First
Before correcting anything, identify where the inconsistency originates.
Check:
– /SCWM/MON for EWM stock
– MMBE / MB52 for ERP stock
– Compare storage location, batch, and stock type
This helps decide whether EWM or ERP is the leading system for correction.
2. Check for Incomplete or Failed Posting Changes
Posting changes are a top reason for mismatches.
– Check open or canceled posting changes in /SCWM/MON
– Verify whether posting changes were confirmed in EWM but not posted to ERP
3. Verify Physical Inventory Posting in Both Systems
Even if PI documents are closed:
– Verify PI posting in EWM
– Check ERP material documents related to PI
4. Check qRFC Queues Carefully
Recheck SMQ1 / SMQ2 for:
– Stock synchronization queues
– Old or previously failed messages
5. Analyze Application Logs
Check SLG1 with objects:
– /SCWM/ERP
– /SCWM/PI
– /SCWM/POST
6. Check for Manual ERP Movements
Ensure no goods movements were posted directly in ERP using MIGO.
7. Validate Stock Type and Availability Group Mapping
Ensure EWM stock types are correctly mapped to ERP stock types.
Safest Way to Correct Stock Differences:
– If EWM stock is correct, adjust ERP stock
– If ERP stock is correct, adjust EWM stock using posting change or correction tools
Never delete stock directly from database tables.
In most real projects, stock mismatch is caused by incomplete posting changes, PI issues, manual ERP postings, or mapping errors.