Since:

• Delivery exists in VL03N

• No short dump

• No visible queue error

• Integration worked earlier

The problem is usually in warehouse number determination, delivery relevance, or qRFC message triggering.

Let’s analyze step by step.

🔎 1️⃣ First Confirm: Is the Delivery EWM-Relevant?

Not every ERP delivery is automatically distributed to EWM.

Check in:

VL03N → Header → Warehouse Number field

If warehouse number is blank → Delivery is NOT EWM relevant.

Why Warehouse Number May Not Be Determined?

Check configuration:

SPRO → Enterprise Structure → Assignment → Logistics Execution → Assign Warehouse Number to Plant/Storage Location

Also verify:

• Shipping point determination

• Plant + storage location mapping

If warehouse is not correctly assigned, system will never trigger EWM distribution.

🔎 2️⃣ Check Delivery Type Mapping to EWM

Even if warehouse number exists, delivery type must be mapped.

Check:

SPRO → Integration with Other SAP Components → Extended Warehouse Management → Assign Delivery Type to EWM

Verify:

• Delivery type is mapped to correct warehouse

• Document category is marked EWM-relevant

If this mapping was removed or changed in transport, distribution stops silently.

This is a very common production issue.

🔎 3️⃣ Check Outbound Queue in ERP (SMQ1)

If configuration is correct, next step is:

Transaction: SMQ1

Check if outbound queue entry was created when delivery was saved.

Cases:

• No queue entry → Distribution not triggered (configuration issue)

• Queue exists but stuck → Communication issue

• Queue processed successfully → Check EWM inbound queue

Even if SMQ2 is empty, always check SMQ1 in ERP first.

🔎 4️⃣ Check Inbound Queue in EWM (SMQ2)

If outbound queue processed but delivery not created:

Check:

Transaction: SMQ2

Look for inbound queue errors like:

• SYSFAIL

• STOP

• RETRY

If found:

• Double-click LUW

• Display error text

• Fix root cause

• Reprocess queue

🔎 5️⃣ Check RFC Destination

Go to:

Transaction: SM59

Test RFC destination between ERP and EWM.

If connection fails or times out:

• Queue may not process

• Delivery distribution stops

Also verify qRFC scheduler job is active (SM37).

🔎 6️⃣ Check for Enhancement or BAdI Blocking Distribution

Many mature projects implement custom logic.

Check active BAdIs such as:

• /SCWM/EX_ERP_DLV_DISTRIBUTE

• LE_SHP_DELIVERY_PROC

Custom logic may suppress EWM distribution under specific conditions (e.g., special delivery types).

If issue occurs only for certain delivery types or plants, enhancement is likely cause.

🔎 7️⃣ Real Project Scenario

In one S/4HANA Embedded EWM project:

Issue:
Outbound delivery created but not visible in EWM.

Root Cause:
During recent transport, delivery type mapping to EWM warehouse was removed.

System did not consider delivery EWM-relevant.

Fix:
Re-maintained mapping → Recreated delivery → Distribution worked immediately.

No queue error involved.

🛡 Safe Troubleshooting Approach in Production

Follow this sequence:

1. Check warehouse number in VL03N

2. Verify delivery type relevance

3. Check SMQ1 (ERP outbound queue)

4. Check SMQ2 (EWM inbound queue)

5. Test RFC connection

6. Avoid manual ODO creation

If delivery must be recreated:

• Reverse delivery

• Fix configuration

• Create new delivery

Never update tables directly.

🎯 Final Conclusion

If delivery is not distributed to EWM after creation in S/4HANA, the most common causes are:

• Warehouse number not determined

• Delivery type not EWM-relevant

• Outbound queue not triggered

• RFC communication issue

• Enhancement logic blocking distribution

The key is to first confirm whether the integration message was triggered.

If no queue exists → Configuration issue.
If queue exists but not processed → Integration issue.

This structured approach prevents unnecessary configuration changes and saves troubleshooting time.

When an outbound delivery is created in ERP (VL01N/VL02N) but is not visible in EWM (/SCWM/PRDO), the issue is almost always related to integration trigger failure between ERP and EWM.

Since:

• Delivery exists in VL03N

• No short dump

• No visible queue error

• Integration worked earlier

This indicates the issue is likely related to distribution determination or message processing.

Let’s troubleshoot systematically.

1️⃣ Understand the Distribution Logic

In Embedded EWM:

1. Outbound Delivery is created in ERP

2. System determines warehouse number

3. Delivery relevance for EWM is checked

4. Delivery message is sent via qRFC

5. EWM creates Outbound Delivery Order (ODO)

If step 2, 3, or 4 fails → Delivery will not appear in EWM.

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

🔹 A. Warehouse Number Determination Failed (Very Common)

Check in ERP:

SPRO → Logistics Execution → Shipping → Basic Shipping Functions → Shipping Point and Goods Receiving Point Determination

Verify:

• Shipping point assigned correctly

• Plant + Storage location mapped to warehouse number

If warehouse number is not determined, delivery will not be EWM-relevant.

🔹 B. Delivery Type Not Relevant for EWM

Check:

SPRO → Integration with Other SAP Components → EWM → Assign Delivery Type to Warehouse Process

Ensure:

• Delivery type is mapped to EWM warehouse

• Document category relevant for distribution

If delivery type is not marked as EWM relevant, system will not send it.

🔹 C. Queue Not Created (Silent Failure)

Even if SMQ2 is empty, check:

Transaction:
SMQ1 (Outbound Queue in ERP)

If no queue entry exists, distribution was never triggered.

Possible reasons:

• qRFC scheduler not running

• RFC destination issue

• Logical system mismatch

🔹 D. User Exit / BAdI Blocking Distribution

Check if any enhancement is active for delivery creation.

Common BAdIs:

• LE_SHP_DELIVERY_PROC

• /SCWM/EX_ERP_DLV_DISTRIBUTE

Custom logic may suppress EWM distribution under certain conditions.

This is common in mature projects.

🔹 E. Incorrect Integration Model / Logical System

Verify:

• Logical system assigned correctly

• Warehouse linked to correct ERP system

• RFC destination working (SM59 test)

If RFC is inactive, delivery will not transfer.

3️⃣ What to Check Immediately (Practical Sequence)

Follow this order:

✔ Step 1: Check Warehouse Number in Delivery

In VL03N → Header → Check warehouse number determination

✔ Step 2: Check SMQ1 in ERP

See if outbound queue entry exists

✔ Step 3: Check SMQ2 in EWM

Ensure inbound queue processed

✔ Step 4: Check SM59

Test RFC connection

✔ Step 5: Check SLG1

Object: /SCWM/ERP_INT or DELIVERY

4️⃣ How to Safely Troubleshoot in Production

⚠ Do NOT manually create ODO in EWM.

Safe approach:

1. Identify if queue exists

2. If queue stuck → fix and reprocess

3. If no queue → check delivery relevance configuration

4. If necessary → reverse delivery and recreate after fix

Never adjust tables directly.

5️⃣ Critical Configuration Objects for Delivery Integration

✔ Warehouse number determination
✔ Delivery type mapping to EWM
✔ Document category relevance
✔ RFC destination
✔ Logical system assignment
✔ qRFC scheduler active
✔ Integration BAdI implementations

6️⃣ Real Project Scenario

In one S/4HANA Embedded EWM project:

Issue:
Delivery created in ERP but not visible in EWM.

Root Cause:
Delivery type mapping was removed during transport.

System did not consider delivery EWM-relevant.

Fix:
Re-maintained delivery type mapping → recreated delivery → Distribution worked immediately.

No queue issue involved.

7️⃣ Golden Rule

If delivery does not appear in EWM:

👉 First confirm whether distribution message was created.
👉 If message not created → Configuration issue.
👉 If message created but not processed → Queue issue.

This distinction saves hours of troubleshooting.

🎯 Final Conclusion

If Delivery is not distributed to EWM after creation in S/4HANA, it is usually due to:

• Warehouse number determination failure

• Delivery type not EWM relevant

• Outbound queue not triggered

• RFC communication issue

• Enhancement logic blocking distribution

Structured integration troubleshooting will resolve the issue safely without production risk.