I am working on an SAP EWM inbound process where the inbound delivery is successfully distributed from ERP to EWM and the warehouse request is visible.
However, when I try to create Warehouse Tasks (WT), the system does not create any tasks, even though configuration and master data appear to be correct.
Scenario:
-
Inbound delivery is visible in
/SCWM/MON -
Warehouse number is correctly assigned
-
Putaway strategy is maintained
-
Warehouse process type is determined
-
Storage type and bin determination look correct
-
No clear error message is displayed
Issue:
Despite everything looking correct, the warehouse task is not created for putaway.
My Question:
What are the most common configuration or master data issues that can cause warehouse task not to be created after inbound delivery in SAP EWM?
Which settings should be checked first in this scenario?

SAP EWM Warehouse Task Not Created After Inbound Delivery
When an inbound delivery is successfully distributed to SAP EWM but Warehouse Tasks (WTs) are not created, the issue is usually related to process configuration gaps or missing master data, even if everything appears correct at first glance.
Below is a systematic checklist based on real project experience.
🔍 1. Check Inbound Delivery Item Status
Go to /SCWM/MON
Navigate to the inbound delivery item
Verify the status:
“Putaway Relevance” must be active
Delivery item must be released for warehouse processing
👉 If the delivery is not released, WT creation will not trigger.
🔍 2. Verify Warehouse Process Type (WPT)
Check whether the correct Warehouse Process Type is determined:
Go to SPRO → EWM → Goods Receipt → Warehouse Task → Define Warehouse Process Type
Ensure:
Putaway relevance is active
Correct stock removal/placement control is set
Confirmation control is not blocking WT creation
👉 Wrong or incomplete WPT is one of the most common causes.
🔍 3. Check Putaway Strategy & Storage Type Search
Verify Putaway Strategy in:
Product master (warehouse view)
Storage type search sequence
Ensure:
At least one storage type is found
Storage type allows putaway
No capacity or bin restriction blocks WT creation
👉 If no valid storage type/bin is found, WT will not be created.
🔍 4. Check Product Master Data
In /SCWM/MAT1, confirm:
Putaway control indicator is maintained
Storage section / storage type indicators are correct
Handling Unit requirement matches the process
Batch/SLED settings (if applicable) are consistent
👉 Missing or incorrect product master data often blocks task creation silently.
🔍 5. Check Warehouse Task Creation Settings
Verify whether WT creation is:
Manual
Automatic
Triggered by PPF
If PPF is used:
Check PPF action status
Ensure action is processed successfully
👉 If WT creation is set to manual, system will not create tasks automatically.
🔍 6. Check Queue & Warehouse Order Settings
Ensure a valid queue is determined
Check:
Queue assignment
Warehouse Order Creation Rules (WOCR)
Incorrect queue determination may prevent WT processing.
🔍 7. Check Application Logs & Queues
Always check:
SLG1 – Application logs for hidden errors
SMQ1 / SMQ2 – qRFC queues for stuck messages
👉 Many WT creation issues are visible only in logs, not on the UI.
✅ Final Recommendation (Real Project Insight)
In most productive systems, WT not created after inbound delivery is caused by:
Incorrect or incomplete Warehouse Process Type
Missing putaway strategy or storage type
Product master data gaps
Delivery not released for warehouse processing
PPF or queue-related issues