When an outbound delivery is successfully replicated to SAP EWM but Warehouse Tasks (WTs) are not created, the issue is usually related to status management, configuration gaps, or background action failures — even if everything appears correct at first glance.

Below is a real-project, systematic troubleshooting approach.

🔍 1. Check Delivery Status (Most Commonly Missed)

Go to /SCWM/MON → Outbound Delivery Order (ODO) and verify:

Important Status Fields:

• Warehouse Process Status

• Picking Status

• Overall Status

• Goods Issue Relevance

• WT Creation Relevance

👉 If delivery is not “Released for Picking”, WT will not be created.

Very often, the delivery exists but is not fully warehouse-relevant.

🔍 2. Check Whether Automatic WT Creation Is Triggered

WT creation may depend on:

• Manual creation

• Automatic creation via PPF

• Wave management

• Background job

✔ If PPF is used:

Check:

• PPF action profile assigned

• Action determination successful

• Action status processed without error

Missing or inactive PPF action = No automatic WT.

🔍 3. Verify Warehouse Process Type (WPT) Deeply

Even if WPT is “maintained”, check:

• Picking control indicator

• Stock removal rule

• Confirmation control

• Activity area assignment

👉 Incorrect picking control can silently prevent WT creation.

This is one of the top root causes.

🔍 4. Validate Storage Type Search & Stock Availability

Even with correct search sequence:

• Is stock actually available in correct stock type?

• Is stock blocked or in quality?

• Is batch determination failing?

• Is stock in different availability group?

Check:

• /SCWM/MON → Stock Overview

• Product warehouse view

👉 If no valid source bin is found, WT will not be created.

🔍 5. Check Wave Management (If Active)

If wave management is used:

• Delivery may require wave release

• WT is created only after wave release

• Check wave status

Many projects forget this dependency.

🔍 6. Queue & WOCR Validation

Even if queue exists:

• Is correct queue determined?

• Is resource assigned to that queue?

• Is WOCR restricting WT grouping?

Incorrect queue determination can prevent processing.

🔍 7. Check Application Logs (Very Important)

Go to SLG1 and check for:

• Object: /SCWM/DELIVERY

• Object: /SCWM/WAVE

• Object: /SCWM/WHSE_TASK

Often errors appear in logs but not on delivery UI.

🔍 8. Check qRFC Queues

Even if no visible errors:

• Check SMQ1 / SMQ2

• Look for stuck or temporary blocked entries

• Reprocess failed messages if needed

Queue issues can delay WT creation.

🔍 9. Confirm Delivery Is Not Blocked

Check:

• Credit block

• Incompletion log

• Delivery block indicators

• GI relevance

Blocked deliveries will not trigger picking.

🔍 10. Product & Warehouse Data Validation

Check in /SCWM/MAT1:

• Warehouse product maintained

• Activity area assigned

• Storage type indicators correct

• No inconsistent stock removal rule

Missing activity area assignment is a common hidden cause.

✅ Most Common Real Project Root Causes

From real implementations, WT not created is usually due to:

1. Delivery not fully released for picking

2. Missing or failed PPF action

3. Incorrect picking control in WPT

4. No valid source stock found

5. Wave not released

6. Activity area not assigned

7. Queue mismatch

8. Application log errors

✅ Recommended Troubleshooting Order (Production Safe)

Follow this sequence:

1️⃣ Check delivery status
2️⃣ Check PPF action
3️⃣ Check stock availability
4️⃣ Validate WPT
5️⃣ Review wave status
6️⃣ Check application logs
7️⃣ Check queues

This minimizes business impact and avoids unnecessary configuration changes.

🔑 Final Project Insight

In 80% of cases, the issue is not a system error, but:

• Status not properly triggered

• Automatic action not configured

• Warehouse process control misaligned

Always validate process flow sequence, not just configuration.