In an SAP S/4HANA Embedded EWM system, we are facing a stock mismatch issue between ERP and EWM after goods movement processing.
Issue Description:
Goods Issue or Goods Receipt posted successfully
Material document created in ERP
However, stock quantity in ERP and EWM does not match
In some cases, EWM shows stock but ERP does not
In other cases, ERP stock updated but EWM stock remains unchanged
System Behavior:
No visible error during posting
No open warehouse tasks
Delivery appears completed
No immediate queue failure
Business Impact:
Inventory mismatch
Financial reporting incorrect
Risk of duplicate picking
Audit concerns
Checks Already Performed:
SMQ1 / SMQ2 checked
/SCWM/MON stock overview verified
No obvious short dump
Basic delivery status review done
Despite these checks, stock difference remains.
My Questions:
What are the most common reasons for stock mismatch between ERP and EWM?
Which integration points should be verified first?
How to safely reconcile stock in production?
When should correction be done in ERP vs EWM?
Are there standard correction reports available in EWM?
Looking for practical troubleshooting guidance based on real project experience.
Stock mismatch between ERP and EWM usually indicates an integration confirmation failure or interrupted goods movement processing.
If:
Goods Issue (GI) or Goods Receipt (GR) posted
Material document exists in ERP
No open WT visible
No immediate queue error
But stock differs between ERP and EWM, the issue is almost always in asynchronous integration processing.
Let’s troubleshoot systematically.
🔎 1️⃣ First Understand the Integration Flow
In Embedded EWM:
For Goods Issue:
WT confirmed in EWM
GI posted in EWM
Confirmation sent to ERP
ERP posts material document
Stock reduced in both systems
For Goods Receipt:
GR posted in ERP
Message sent to EWM
EWM updates stock
If any confirmation message fails → stock mismatch occurs.
🔍 2️⃣ Most Common Root Causes (Real Project Experience)
🔹 A. Queue Processed Partially (Most Common)
Even if SMQ1/SMQ2 looks clean now, the issue may have occurred earlier.
Check carefully:
Transaction:
SMQ1 (ERP outbound)
SMQ2 (EWM inbound)
Look for:
Previously failed LUWs
RETRY or SYSFAIL history
Manually deleted queues
If queue failed temporarily and was not reprocessed properly → inconsistency remains.
🔹 B. Manual Posting in ERP (Bypassing EWM)
If user posts:
GI directly in VL02N
GR directly in MIGO
Without EWM-driven process, ERP stock updates but EWM does not.
This is very common in production emergencies.
Always verify document flow.
🔹 C. Incomplete Posting Change
Sometimes:
Posting Change WT confirmed
But ERP confirmation failed
Result:
EWM stock type changes
ERP stock does not reflect change
Check:
/SCWM/MON → Posting Change Node
🔹 D. Delivery Closed in ERP Before EWM Update
If ERP document technically closed before EWM received confirmation, status sync may fail.
🔹 E. CIF / Integration Model Issue
If integration object temporarily inactive:
Confirmation not transferred
No visible immediate error
Verify:
Logical system
RFC destination (SM59)
Integration settings
🔹 F. Background Job Not Running
qRFC scheduler job may be inactive.
Check:
SM37 → Background jobs for qRFC processing
If scheduler stopped, messages stay unprocessed.
🔍 3️⃣ What to Check Immediately (Practical Sequence)
Follow this order:
✔ Step 1: Compare Stock Quantities
ERP:
MMBE
EWM:
/SCWM/MON → Stock Overview
Identify exact delta quantity.
✔ Step 2: Check Document Flow
Verify:
Was GI done from EWM or ERP?
Was GR triggered correctly?
✔ Step 3: Check Queues Again (Historical)
SMQ1
SMQ2
SM58
Look for failed or deleted LUWs.
✔ Step 4: Check Application Logs
SLG1
Object examples:
/SCWM/ERP_INT
/SCWM/DELIVERY
🛠 4️⃣ How to Safely Reconcile Stock in Production
⚠ Never adjust tables manually.
✅ Scenario A: ERP Updated, EWM Not Updated
Option:
Identify missing message
Reprocess queue
Use /SCWM/POST if allowed
If necessary:
Reverse GI in ERP (VL09) → Reprocess correctly.
✅ Scenario B: EWM Updated, ERP Not Updated
Check outbound queue in ERP
Reprocess LUW
Restart qRFC scheduler
Avoid manual ERP material document creation.
✅ Scenario C: Complete Mismatch
If integration history unclear:
Freeze material temporarily
Perform physical stock verification
Reverse incorrect document
Repost correctly through standard process
🧰 5️⃣ Standard Correction Reports in EWM
Useful transactions/programs:
/SCWM/CONS_CHECK (Consistency Check)
/SCWM/R_STOCK_CHECK
/SCWM/ERP_STOCK_CHECK
/SCWM/REPAIR_STOCK
⚠ Always test in QA before production usage.
🛡 When to Correct in ERP vs EWM?
Golden rule:
👉 Always fix the process, not just the stock.
📌 Real Project Scenario
In a live e-commerce warehouse:
Issue:
Stock in ERP reduced, but EWM still showed quantity.
Root Cause:
Outbound queue failed during network interruption.
Queue was manually deleted instead of reprocessed.
Fix:
Recreated delivery flow → Corrected stock via standard reversal → Reposted GI.
Lesson:
Never delete queue without full impact analysis.
🎯 Final Conclusion
Stock mismatch between ERP and EWM is usually caused by:
Queue processing interruption
Manual posting in ERP
Posting change failure
RFC communication issue
Background job inactive
The solution is:
Identify integration failure point
Reprocess or reverse correctly
Avoid manual stock adjustment
Use correction tools carefully
Structured troubleshooting prevents financial and audit risk.