Goods Issue Posted in ERP but Not Updated in SAP EWM – How to Fix Status Mismatch

This issue indicates a synchronization failure between ERP and EWM during the outbound integration process.

Since:

• GI is posted in ERP

• Material document is created

• EWM delivery still shows “Not GI Posted”

• Stock still visible in EWM

The problem is almost always related to queue processing or integration message failure from ERP to EWM.

Let’s troubleshoot step by step.

---

1️⃣ Understand the Integration Logic

In Embedded EWM:

1. GI is posted

2. ERP sends confirmation message to EWM

3. EWM updates delivery status

4. Stock is reduced in EWM

If step 2 fails → Status mismatch occurs.

This is NOT a picking issue — it is an integration confirmation issue.

---

2️⃣ Most Common Root Causes (Real Project Experience)

---

🔹 A. Inbound Queue Stuck in EWM (Most Common Cause)

Check:

Transaction:
SMQ2 (Inbound Queue in EWM)

Look for queue related to delivery number.

Possible statuses:

• SYSFAIL

• RETRY

• STOP

If queue is stuck, EWM never receives GI confirmation.

👉 Fix the root cause and reprocess LUW.

---

🔹 B. Outbound Queue Not Processed in ERP

Check:

SMQ1 (Outbound Queue in ERP)

If message not sent to EWM, EWM status will not update.

Sometimes queue is in READY but scheduler job is not running.

Check background job for qRFC processing.

---

🔹 C. CIF / Delivery Integration Issue

Verify:

• Logical system assignment

• Warehouse number mapping

• Integration model active

If integration object is inactive or incorrectly mapped, confirmation message fails silently.

---

🔹 D. Delivery Already Closed in ERP Before EWM Update

In rare cases:

If delivery is technically closed in ERP before EWM confirmation, status may not sync properly.

Check document flow carefully.

---

🔹 E. Manual GI Posted in ERP (Bypassing EWM Process)

If someone posts GI directly in ERP using VL02N instead of EWM-driven GI:

ERP updates stock, but EWM is not informed properly.

This is a common root cause in production.

---

3️⃣ What to Check Immediately

Follow this sequence:

✔ Step 1: Check SMQ2 in EWM

Look for inbound delivery queue

✔ Step 2: Check SMQ1 in ERP

Ensure outbound confirmation message processed

✔ Step 3: Check SM58

Look for tRFC errors

✔ Step 4: Check SLG1

Object: /SCWM/ERP_INT or /SCWM/DELIVERY

---

4️⃣ How to Safely Re-Synchronize Status in Production

⚠ Never change tables manually.

Safe options:

---

✅ Option 1: Reprocess Queue (Preferred)

If queue exists:

• Fix error

• Execute LUW again

• Monitor status update

---

✅ Option 2: Use EWM Correction Transaction

Transaction:
/SCWM/POST

If GI already posted in ERP, system may allow synchronization update.

---

✅ Option 3: Cancel & Repost GI (If Business Allows)

If integration completely failed:

1. Reverse GI in ERP (VL09)

2. Ensure queue working

3. Post GI again from EWM

⚠ Only after business approval.

---

5️⃣ When to Correct in ERP vs EWM?

Golden Rule:

👉 Never adjust stock manually in EWM to fix ERP mistake.

Always fix integration.

---

6️⃣ Real Project Scenario

In one S/4HANA Embedded EWM project:

Issue:
GI posted in ERP but EWM still showed open delivery.

Root Cause:
Outbound queue in ERP was stuck due to temporary RFC destination issue.

Queue was in READY state but background job was inactive.

Fix:
Activated qRFC scheduler → Reprocessed queue → Status synchronized automatically.

No manual correction needed.

---

7️⃣ Practical Troubleshooting Flow

1. Check ERP GI document

2. Check SMQ1 in ERP

3. Check SMQ2 in EWM

4. Check SM58

5. Reprocess queue

6. Monitor delivery status in /SCWM/PRDO

Avoid direct stock adjustment.

---

🎯 Final Conclusion

If Goods Issue is posted in ERP but not updated in SAP EWM, it is usually caused by:

• Inbound queue stuck in EWM

• Outbound queue not processed in ERP

• RFC communication issue

• Manual GI in ERP

• Integration model misconfiguration

This is an integration confirmation failure — not a warehouse issue.

Proper queue monitoring and controlled reprocessing will resolve the inconsistency safely.

See less

When RF transaction screen flow is incorrect in SAP S/4HANA Embedded EWM, and GUI transactions work correctly, the issue is usually related to RF Framework configuration or screen flow control logic, not warehouse process configuration.

Since:

• RF transaction starts correctly

• Initial screen appears

• GUI works fine

• No dump or application error

The issue is most likely in RF screen sequencing configuration or custom enhancement logic.

Let’s troubleshoot systematically.

---

1️⃣ Check Logical Transaction & Presentation Profile

Go to:

Transaction:
/SCWM/RFUI

Then check configuration in SPRO:

EWM → Mobile Data Entry → RF Framework → Define Logical Transactions

Verify:

• Logical transaction assigned correctly

• Correct step sequence maintained

• Presentation profile assigned

If incorrect logical transaction is assigned, wrong screen sequence will appear.

---

2️⃣ Check Screen Flow Configuration

Path:

SPRO → EWM → Mobile Data Entry → RF Framework → Define Screen Flow Logic

Key checks:

• Screen sequence numbers

• Foreground/Background step indicator

• Verification profile

• Function code assignments

If sequence numbers are incorrect or step type is misconfigured, screens may:

• Skip steps

• Jump to wrong screen

• Not prompt mandatory fields

This is one of the most common issues.

---

3️⃣ Check Verification Profile

If mandatory fields are not prompted:

Check:

SPRO → EWM → Mobile Data Entry → RF Framework → Define Verification Profile

Verify:

• Required fields marked properly

• Field control active

• Profile assigned to logical transaction

If verification profile is missing or wrongly assigned, RF will skip mandatory input.

---

4️⃣ Check Warehouse Process Type (WPT) Influence

Although WPT is correct, check:

• Is WPT configured for background processing?

• Is auto-confirmation active?

• Is automatic WT confirmation enabled?

If auto-confirmation is active, RF may skip confirmation screens.

This is often mistaken as screen flow error.

---

5️⃣ Check BAdI or Custom Enhancements (Very Common in Real Projects)

Many projects enhance RF using:

BAdI:
/SCWM/EX_RFUI_EXTEND

or related RF framework enhancement spots.

Custom logic may:

• Skip screens intentionally

• Change next screen dynamically

• Suppress input fields

If issue exists only in certain warehouse or process type, enhancement is highly likely.

Always check:

SE19 → Active implementations for RF BAdIs

---

6️⃣ How to Debug RF Issues Safely

In QA or DEV:

1. Activate external breakpoint in RF function module

2. Use user-specific debugging

3. Test using /SCWM/RFUI

In Production (safe approach):

• Avoid hard debugging

• Use SLG1 (Application Log)

• Check RF logs

• Compare working vs non-working warehouse configuration

---

7️⃣ Check Presentation Device Settings

Sometimes issue occurs only on certain RF devices.

Check:

• Presentation profile

• Display profile

• Device template settings

Different device templates may suppress fields.

---

🔎 Real Project Scenario

In one Embedded EWM project:

Issue:
During picking, confirmation screen was skipped.

Root Cause:
Custom BAdI implementation dynamically changed next screen based on WPT.

Fix:
Adjusted enhancement logic and tested in QA.

After transport, RF flow worked correctly.

No standard config issue.

---

🛡 Practical Troubleshooting Sequence

Follow this order:

1. Verify Logical Transaction

2. Check Screen Sequence configuration

3. Verify Verification Profile

4. Check WPT auto-confirm settings

5. Review BAdI implementations

6. Compare working warehouse vs failing warehouse

Never change screen flow directly in production without testing.

---

🎯 Final Conclusion

Incorrect RF screen sequence in SAP EWM is usually caused by:

• Wrong logical transaction assignment

• Incorrect screen flow configuration

• Missing verification profile

• Auto-confirm settings in WPT

• Custom BAdI enhancement logic

GUI working fine confirms that the issue is RF framework-specific.

Systematic review of RF configuration and enhancements will resolve the issue safely.

See less

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