This issue indicates a synchronization failure between ERP and EWM during the outbound integration process.

Since:

• GI is posted in ERP

• Material document is created

• EWM delivery still shows “Not GI Posted”

• Stock still visible in EWM

The problem is almost always related to queue processing or integration message failure from ERP to EWM.

Let’s troubleshoot step by step.

1️⃣ Understand the Integration Logic

In Embedded EWM:

1. GI is posted

2. ERP sends confirmation message to EWM

3. EWM updates delivery status

4. Stock is reduced in EWM

If step 2 fails → Status mismatch occurs.

This is NOT a picking issue — it is an integration confirmation issue.

2️⃣ Most Common Root Causes (Real Project Experience)

🔹 A. Inbound Queue Stuck in EWM (Most Common Cause)

Check:

Transaction:
SMQ2 (Inbound Queue in EWM)

Look for queue related to delivery number.

Possible statuses:

• SYSFAIL

• RETRY

• STOP

If queue is stuck, EWM never receives GI confirmation.

👉 Fix the root cause and reprocess LUW.

🔹 B. Outbound Queue Not Processed in ERP

Check:

SMQ1 (Outbound Queue in ERP)

If message not sent to EWM, EWM status will not update.

Sometimes queue is in READY but scheduler job is not running.

Check background job for qRFC processing.

🔹 C. CIF / Delivery Integration Issue

Verify:

• Logical system assignment

• Warehouse number mapping

• Integration model active

If integration object is inactive or incorrectly mapped, confirmation message fails silently.

🔹 D. Delivery Already Closed in ERP Before EWM Update

In rare cases:

If delivery is technically closed in ERP before EWM confirmation, status may not sync properly.

Check document flow carefully.

🔹 E. Manual GI Posted in ERP (Bypassing EWM Process)

If someone posts GI directly in ERP using VL02N instead of EWM-driven GI:

ERP updates stock, but EWM is not informed properly.

This is a common root cause in production.

3️⃣ What to Check Immediately

Follow this sequence:

✔ Step 1: Check SMQ2 in EWM

Look for inbound delivery queue

✔ Step 2: Check SMQ1 in ERP

Ensure outbound confirmation message processed

✔ Step 3: Check SM58

Look for tRFC errors

✔ Step 4: Check SLG1

Object: /SCWM/ERP_INT or /SCWM/DELIVERY

4️⃣ How to Safely Re-Synchronize Status in Production

⚠ Never change tables manually.

Safe options:

✅ Option 1: Reprocess Queue (Preferred)

If queue exists:

• Fix error

• Execute LUW again

• Monitor status update

✅ Option 2: Use EWM Correction Transaction

Transaction:
/SCWM/POST

If GI already posted in ERP, system may allow synchronization update.

✅ Option 3: Cancel & Repost GI (If Business Allows)

If integration completely failed:

1. Reverse GI in ERP (VL09)

2. Ensure queue working

3. Post GI again from EWM

⚠ Only after business approval.

5️⃣ When to Correct in ERP vs EWM?

Golden Rule:

👉 Never adjust stock manually in EWM to fix ERP mistake.

Always fix integration.

6️⃣ Real Project Scenario

In one S/4HANA Embedded EWM project:

Issue:
GI posted in ERP but EWM still showed open delivery.

Root Cause:
Outbound queue in ERP was stuck due to temporary RFC destination issue.

Queue was in READY state but background job was inactive.

Fix:
Activated qRFC scheduler → Reprocessed queue → Status synchronized automatically.

No manual correction needed.

7️⃣ Practical Troubleshooting Flow

1. Check ERP GI document

2. Check SMQ1 in ERP

3. Check SMQ2 in EWM

4. Check SM58

5. Reprocess queue

6. Monitor delivery status in /SCWM/PRDO

Avoid direct stock adjustment.

🎯 Final Conclusion

If Goods Issue is posted in ERP but not updated in SAP EWM, it is usually caused by:

• Inbound queue stuck in EWM

• Outbound queue not processed in ERP

• RFC communication issue

• Manual GI in ERP

• Integration model misconfiguration

This is an integration confirmation failure — not a warehouse issue.

Proper queue monitoring and controlled reprocessing will resolve the inconsistency safely.