Warehouse Order Created but Not Assigned to Resource in SAP EWM – Root Cause & Fix

When Warehouse Orders (WO) are created but not assigned automatically to a resource in SAP EWM, the issue is usually related to queue configuration, resource setup, or activity area mismatch.

Even if WT creation, WOCR, and queue determination appear correct, automatic assignment will not work unless all assignment conditions are fulfilled.

Below is a step-by-step troubleshooting guide based on real project experience.

🔎 What Controls WO-to-Resource Assignment?

Automatic WO assignment depends on:

• Queue determination

• Resource assignment to queue

• Resource group configuration

• Activity area mapping

• Warehouse Order Creation Rule (WOCR)

• Resource type and activity

If any link is missing, WO remains unassigned.

🛑 Most Common Root Causes

1️⃣ Resource Not Assigned to Correct Queue (Most Common)

Check:

• /SCWM/RSRC → Display Resource

• Verify assigned queue

If the WO queue is Q_PICK_01 but the resource is assigned to Q_PICK_02, automatic assignment will not occur.

👉 This is the #1 real-world cause.

2️⃣ Resource Group Not Linked Properly

Verify:

• Resource group assigned to resource

• Resource group allowed for correct activity

Mismatch between WOCR and resource group prevents assignment.

3️⃣ Activity Area Mismatch

If WO is created for Activity Area A1, but resource is configured for Activity Area A2:

→ Assignment will fail silently.

Check:

• Activity area in WO

• Activity area allowed for resource

4️⃣ Resource Type Incorrect

Ensure resource type supports:

• Picking activity

• Correct warehouse number

Sometimes resource is created but not configured for required activity.

5️⃣ Automatic Assignment Not Activated

Check:

• Queue configuration allows automatic assignment

• WOCR settings do not restrict assignment

• No capacity restrictions blocking assignment

If capacity limit reached, WO may remain open.

🧪 Step-by-Step Troubleshooting Guide (Production Safe)

Follow this order:

Step 1

Check queue assigned to WO in /SCWM/MON.

Step 2

Check resource assignment to same queue in /SCWM/RSRC.

Step 3

Verify activity area in WO matches resource configuration.

Step 4

Review resource group mapping.

Step 5

Check WOCR for grouping restrictions.

Step 6

Review application logs (SLG1) for hidden assignment messages.

This structured approach avoids random configuration changes.

⚠ Common Configuration Mistakes

• Resource assigned to wrong warehouse number

• Resource active but not logged into correct queue

• Queue created but not linked to resource group

• Activity area copied but not updated

• Capacity check blocking assignment

• Testing done with different resource than configured

These small gaps commonly block automatic assignment.

📊 How Queue, Resource Group & Activity Area Impact Assignment

All four must align for automatic assignment to work.

✅ Final Recommendation

In most productive systems, automatic WO assignment fails because:

• Resource not assigned to correct queue

• Activity area mismatch

• Resource group configuration incomplete

Always start troubleshooting from queue alignment, then validate resource configuration.

Once queue + activity + resource mapping are aligned, automatic assignment works immediately.