When an Outbound Delivery Order (ODO) is not created in SAP EWM after creating the delivery in ERP, the problem is usually related to delivery relevance determination or integration message processing between ERP and EWM.

Even if the delivery exists in VL03N, the system must still determine that the delivery is EWM relevant and trigger the qRFC integration message.

Below is the step-by-step troubleshooting approach used in real SAP EWM projects.

 First Check: Is the Delivery EWM-Relevant?

Not every ERP delivery is automatically distributed to EWM.

Open the delivery in VL03N and verify:

• Warehouse Number field

• Shipping point

• Plant and storage location

If warehouse number is missing, the system will not trigger EWM distribution.

Configuration to check

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

If this mapping is missing, the delivery will remain in ERP only.

 Check Delivery Type Mapping to EWM

The delivery type must be configured as EWM relevant.

Check configuration:

SPRO → Integration with Other SAP Components → Extended Warehouse Management → Delivery Processing

Verify:

• Delivery type is mapped to the warehouse

• Document category is relevant for EWM

If the delivery type is not mapped, the system will not create the ODO.

This is one of the most common root causes in projects.

Check Outbound Queue in ERP (SMQ1)

If configuration is correct, the next step is to verify whether the integration message was triggered.

Go to transaction:

SMQ1 – Outbound Queue

Check if a queue entry was created for the delivery.

Possible situations:

If no queue exists, the problem is usually configuration related.

 Check Inbound Queue in EWM (SMQ2)

If the ERP queue was created successfully but the ODO is still not created, check the inbound queue in EWM.

Transaction:

SMQ2

Look for statuses such as:

• SYSFAIL

• RETRY

• STOP

If a queue is stuck:

1. Open the LUW

2. Check error message

3. Fix the root cause

4. Reprocess the queue

 Check RFC Communication

Integration between ERP and EWM depends on RFC communication.

Go to:

SM59 – RFC Destination

Test the connection between ERP and EWM.

If RFC connection fails:

• Queue messages will not be processed

• Delivery distribution will stop

Also verify that qRFC scheduler jobs are active.

 Check Enhancement or BAdI Logic

In some projects, custom logic may block delivery distribution.

Common enhancement spots include:

• /SCWM/EX_ERP_DLV_DISTRIBUTE

• LE_SHP_DELIVERY_PROC

Custom logic may suppress distribution for specific delivery types, plants, or storage locations.

If the issue occurs only for certain scenarios, enhancement logic should be checked.

 Verify Delivery Status and Document Flow

Sometimes ODO creation fails because the delivery is not fully relevant for warehouse processing.

Check in VL03N:

• Delivery status

• Document flow

• Goods movement status

If the delivery is already processed or blocked, ODO creation may not occur.

 Real Project Example

In one S/4HANA Embedded EWM implementation:

Outbound deliveries were created in ERP but ODO was not created in EWM.

Root cause:

Delivery type mapping to EWM warehouse was accidentally removed during a transport.

Fix:

The configuration was corrected and the delivery was recreated.

Result:

ODO was created automatically in EWM.

🛠 Recommended Troubleshooting Sequence

When ODO is not created:

1️⃣ Check warehouse number in VL03N
2️⃣ Verify delivery type mapping to EWM
3️⃣ Check outbound queue in SMQ1
4️⃣ Check inbound queue in SMQ2
5️⃣ Test RFC connection in SM59
6️⃣ Check enhancements or BAdIs

This structured approach usually identifies the root cause quickly.

 Final Conclusion

If the Outbound Delivery Order is not created in SAP EWM, the most common reasons are:

• Warehouse number not determined

• Delivery type not configured as EWM relevant

• Outbound queue not triggered

• Inbound queue failure

• RFC communication issue

• Custom enhancement blocking distribution

Identifying whether the integration message was triggered is the key first step in troubleshooting.