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.

See less

Controlling Warehouse Task Creation Based on Product Shelf Life (SLED) in SAP EWM

In pharmaceutical and regulated industries, controlling remaining shelf life during WT creation is critical for compliance. While FEFO and sort rules help, they are not sufficient to fully enforce minimum SLED validation.

A robust design requires a combination of:

• Standard configuration

• Batch determination strategy

• Stock removal control

• Enhancement (if strict blocking is required)

Below is the recommended real-project approach.

---

🔹 1️⃣ Understand Standard System Behavior First

Standard SAP EWM supports:

✔ FEFO (First Expired First Out)
✔ Batch determination
✔ Shelf life relevance in product master
✔ Sort rules based on SLED

However:

❌ Standard FEFO does not block WT creation if minimum remaining shelf life is not met.
❌ It only sorts stock — it does not enforce business rule validation.

That is why configuration alone is often insufficient.

---

🔹 2️⃣ Outbound Picking – Best Practice Design

✔ Step 1: Maintain SLED & Minimum Remaining Shelf Life

In product master:

• Maintain shelf life expiration data

• Maintain minimum remaining shelf life

Ensure batch classification is correct.

---

✔ Step 2: Use FEFO + Sort Rule (First Level Control)

Configure:

• Stock removal strategy = FEFO

• Sort rule based on expiration date

• Batch determination active

This ensures:
👉 System proposes oldest valid stock first.

But this alone does not enforce 90-day rule strictly.

---

✔ Step 3: Enforce Hard Stop Using BAdI (Recommended for Pharma)

If business requires:

“Do not create WT if remaining SLED < 90 days”

Then enhancement is required.

Commonly Used BAdI in Real Projects:

or

These BAdIs allow you to:

• Validate remaining shelf life dynamically

• Compare SLED against current date

• Throw error message

• Prevent WT creation

This is the most reliable approach in regulated environments.

---

🔹 3️⃣ Inbound Putaway – Directing Short SLED to Fast-Pick Areas

For inbound control:

✔ Option 1: Storage Type Search Sequence

Define:

• Storage type determination based on:

  • Shelf life remaining

  • Stock type

  • Putaway control indicator

But this requires enhancement if dynamic logic is complex.

---

✔ Option 2 (More Flexible): BAdI for Storage Type Determination

Common BAdI used:

This allows:

• Reading SLED at GR

• Determining remaining days

• Assigning storage type dynamically

  • Short SLED → Fast picking area

  • Long SLED → Bulk storage

This is widely used in pharma implementations.

---

🔹 4️⃣ Recommended Overall Architecture

For strict pharma compliance:

✔ Configuration Layer

• FEFO strategy

• Sort rule

• Batch determination

• Minimum remaining shelf life in material master

✔ Validation Layer (Enhancement)

• BAdI to enforce minimum remaining SLED

• Hard error if criteria not met

✔ Putaway Optimization Layer

• Dynamic storage type determination via BAdI

This ensures:

• Compliance

• Audit readiness

• Controlled WT creation

---

🔹 5️⃣ Common Design Mistakes

❌ Relying only on FEFO
❌ Not validating remaining days dynamically
❌ Ignoring time zone/date calculation
❌ Allowing manual override without audit log
❌ Not testing edge cases (partial batch, mixed HU)

---

🔹 6️⃣ Real Project Recommendation

In pharmaceutical projects:

✔ Always implement enhancement for SLED validation
✔ Log validation messages for audit
✔ Prevent manual bypass
✔ Test year-end date transitions
✔ Document SLED logic in functional specification

Because in regulated industries:

Compliance requirement > Standard convenience.

---

🔑 Final Answer to Your Question

✔ Is configuration alone enough?

No — configuration handles sorting but not strict blocking.

✔ Is BAdI required?

Yes, if business requires minimum remaining shelf life enforcement.

✔ Which BAdIs are commonly used?

• /SCWM/EX_CORE_STOCK_REMOVAL

• /SCWM/EX_WHO_CREATE

• /SCWM/EX_CORE_PTS_DET (for putaway logic)

---

See less

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.

---

See less

Designing an Efficient & Audit-Compliant Physical Inventory Strategy in SAP EWM

Designing a Physical Inventory (PI) process in SAP EWM for large, 24/7 warehouses requires balancing audit compliance, system performance, and operational continuity. A well-designed PI strategy should minimize business disruption while ensuring full traceability of inventory adjustments.

Below are best-practice design principles used in real SAP EWM projects.

---

🔹 1. Full PI vs Continuous PI (Cycle Counting) – Recommended Approach

✔ Avoid Pure Annual Full PI

• Annual full PI in large warehouses causes:

  • Operational downtime

  • Performance issues

  • Increased error rates

• Use full PI only for audit reconciliation or exception handling

✔ Prefer Continuous PI (Cycle Counting)

Recommended approach:

• Use cycle counting as the primary PI method

• Schedule small, frequent PI documents

• Count bins/products based on risk and movement frequency

👉 This approach satisfies auditors while keeping operations running.

---

🔹 2. Designing PI Areas & Counting Intervals

✔ Define PI Areas Strategically

Create PI areas based on:

• Storage type (high rack, picking, bulk, VAS)

• Operational criticality

• Access restrictions

Example:

• High-rack storage → Quarterly PI

• Picking areas → Monthly PI

• Fast-moving SKUs → More frequent counts

---

✔ Use ABC Classification

• A-class products → Frequent PI

• B-class products → Medium frequency

• C-class products → Annual or semi-annual PI

👉 This reduces workload and improves accuracy where it matters most.

---

🔹 3. Controlling & Documenting Inventory Differences (Audit Focus)

✔ Enforce Difference Reason Codes

• Mandatory reason codes for all PI differences

• Separate codes for:

  • Damage

  • Theft

  • Process error

  • System issue

👉 Auditors expect clear business justification for every difference.

---

✔ Block Automatic Posting of Differences

Best practice:

• Do not allow direct difference posting

• Route differences through:

  • Supervisor review

  • Approval workflow

This ensures:

• Accountability

• Reduced incorrect postings

---

🔹 4. Authorization & Approval Design for Audit Compliance

✔ Segregation of Duties (SoD)

Design roles such that:

• Counter ≠ Approver ≠ Poster

• No single user can:

  • Count

  • Approve

  • Post differences

👉 This is a key audit requirement.

---

✔ Use Change Logs & Application Logs

• Activate change documents

• Use application logs for:

  • PI creation

  • Difference posting

  • Recount triggers

This provides:

• Full traceability

• “Who changed what and when”

---

🔹 5. Performance Best Practices for Large PI Volumes

✔ Avoid Large PI Documents

• Do not create PI documents for thousands of bins at once

• Split PI documents by:

  • Storage type

  • Area

  • Product group

---

✔ Schedule PI Jobs During Low Activity

• Create and process PI documents during:

  • Night shifts

  • Low-volume windows

• Avoid peak outbound periods

---

✔ Monitor System Load

• Track PI-related queues and logs

• Monitor background job runtime

👉 This prevents performance degradation in productive systems.

---

🔹 6. Recommended End-to-End PI Design (Summary)

✔ Continuous PI as primary strategy
✔ Risk-based counting (ABC analysis)
✔ Mandatory difference reasons
✔ Supervisor approval before posting
✔ Strict role segregation
✔ Small, controlled PI documents
✔ Regular audit reporting

---

See less