Comments on: Stock Difference Between ERP and EWM After Goods Movement – How to Identify and Fix? https://www.sapewmhelp.com/question/stock-difference-between-erp-and-ewm-after-goods-movement-how-to-identify-and-fix/ SAP EWM questions answered by experts β€” ABAP, S/4HANA, warehouse management Mon, 02 Mar 2026 10:38:31 +0000 hourly 1 https://wordpress.org/?v=7.0.2 By: PrafulAnand https://www.sapewmhelp.com/question/stock-difference-between-erp-and-ewm-after-goods-movement-how-to-identify-and-fix/#comment-256 Mon, 02 Mar 2026 10:38:31 +0000 https://www.sapewmhelp.com/?question=stock-difference-between-erp-and-ewm-after-goods-movement-how-to-identify-and-fix#comment-256 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:

  1. WT confirmed in EWM

  2. GI posted in EWM

  3. Confirmation sent to ERP

  4. ERP posts material document

  5. Stock reduced in both systems

For Goods Receipt:

  1. GR posted in ERP

  2. Message sent to EWM

  3. 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:

  1. Freeze material temporarily

  2. Perform physical stock verification

  3. Reverse incorrect document

  4. 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?

Situation Action
GI manually posted in ERP Reverse in ERP
Queue failure Fix integration & reprocess
EWM-only error Correct in EWM
Physical stock mismatch Perform inventory adjustment

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:

  1. Identify integration failure point

  2. Reprocess or reverse correctly

  3. Avoid manual stock adjustment

  4. Use correction tools carefully

Structured troubleshooting prevents financial and audit risk.

]]>