When Warehouse Tasks (WT) are not created automatically in SAP EWM even though stock and documents exist, the issue is usually related to configuration determination logic or process settings rather than system errors.

Since:

• Stock is visible in the warehouse

• Delivery or GR document exists

• No queue errors

• No short dump

The system is most likely not able to determine the required parameters for automatic WT creation.

Let’s troubleshoot step by step.

---

🔎 1️⃣ Check Warehouse Process Type (WPT) Determination

The Warehouse Process Type (WPT) controls how Warehouse Tasks are created.

Check configuration in:

SPRO → EWM → Cross Process Settings → Warehouse Task → Determine Warehouse Process Type

Verify:

• Correct WPT maintained for process

• Activity area and document type mapped

• WPT allows automatic WT creation

If WPT cannot be determined, the system will not create the Warehouse Task.

This is one of the most common root causes.

---

🔎 2️⃣ Verify Storage Type Search Sequence

For putaway or picking, the system must determine the correct destination storage type.

Check configuration in:

SPRO → EWM → Goods Receipt Process → Strategies → Define Storage Type Search Sequence

Verify:

• Search sequence assigned to correct warehouse

• Storage types maintained correctly

• Storage type allows putaway or picking

If the system cannot determine a destination storage type, WT creation will fail.

---

🔎 3️⃣ Check Automatic WT Creation Indicator

For inbound or outbound processes, automatic WT creation must be enabled.

Check:

Inbound Delivery Type
or
Outbound Delivery Type configuration.

Path:

SPRO → EWM → Goods Receipt / Goods Issue Process → Delivery Processing

Ensure the automatic WT creation flag is active.

If this is disabled, WT must be created manually.

---

🔎 4️⃣ Verify Product Master Settings

Incorrect product master settings can prevent WT creation.

Check transaction:

/SCWM/MAT1

Verify:

• Storage type data maintained

• Putaway control indicator

• Removal control indicator

• Warehouse process type determination

Missing data here often prevents automatic WT creation.

---

🔎 5️⃣ Check Warehouse Monitor for Hidden Errors

Sometimes errors are not visible during processing.

Check in:

/SCWM/MON

Navigate to:

Warehouse Monitor → Documents → Warehouse Tasks

Also check:

• Delivery status

• Open warehouse requests

• Incomplete tasks

This often reveals process inconsistencies.

---

🔎 6️⃣ Check Application Logs

If configuration looks correct, check logs.

Transaction:

SLG1

Suggested objects:

• /SCWM/PUTAWAY

• /SCWM/DELIVERY

Logs may show determination errors that are not displayed on the screen.

---

🔎 7️⃣ Check Queue Processing

Although you mentioned SMQ2 is clean, it is still important to confirm:

SMQ1 – Outbound Queue (ERP)
SMQ2 – Inbound Queue (EWM)

If queue processing failed earlier, the delivery may not trigger WT creation correctly.

---

📌 Real Project Scenario

In one S/4HANA Embedded EWM project:

Issue:
Inbound delivery was created successfully, but putaway WT was not generated.

Root Cause:
Storage Type Search Sequence was maintained, but Putaway Control Indicator in product master was missing.

Fix:
After updating the product master data and reprocessing the delivery, the system created WT automatically.

---

🛠 Recommended Troubleshooting Sequence

When WT is not created automatically:

1. Check WPT determination

2. Verify Storage Type Search Sequence

3. Check automatic WT creation indicator

4. Validate product master warehouse data

5. Check /SCWM/MON for document status

6. Review SLG1 application logs

7. Verify queues in SMQ1 / SMQ2

This structured approach usually identifies the root cause quickly.

---

🎯 Final Conclusion

Automatic Warehouse Task creation in SAP EWM depends on several determination objects, mainly:

• Warehouse Process Type

• Storage Type Search Sequence

• Delivery type settings

• Product master warehouse data

• Queue processing

If any of these cannot be determined correctly, the system will not create the Warehouse Task automatically.

Careful review of configuration and master data will resolve the issue in most cases.

---

See less