SAP S/4HANA ERP → EWM C OMPLETE END-TO-END

IMPLEMENTATION GUIDE

Author: Senior SAP EWM Architect, 15+ Years Global Implementation Experience
Version 2.2, 2025

This guide is written for absolute beginners. Every technical term is explained. No prior SAP or
business knowledge is required.
Phase Section Topic Sub Area / Coverage

1 1.0 Project Foundation Overview ERP–EWM Implementation Introduction

1.1 SAP & EWM Overview Functional + Technical Architecture

1.2 Implementation Landscape Embedded vs Decentralized EWM

1.3 System Architecture Logical System, RFC, Clients

1.4 Master Data Flow Material, Customer, Vendor Flow

1.5 Document Flow PO → Inbound → GR / SO → Outbound → GI

2 2.1 Enterprise Structure Company, Plant, Storage Location

2.2 MM Configuration Material Type, Movement Type, Account Determination

2.3 SD Configuration Sales Doc Type, Delivery Type

2.4 QM Configuration Inspection Type, Usage Decision

2.5 PP Configuration MRP, Production Order

2.6 TM Basic Setup Freight Unit, Planning Integration

3 3.1 Basic Integration Setup Logical System, RFC, Business System

3.2 CIF Configuration Integration Model, Queue Monitoring

3.3 MM Integration Material & Vendor Transfer

3.4 SD Integration Customer & Delivery Integration

3.5 QM Integration Inspection Lot Transfer

3.6 PP Integration Staging & Consumption

3.7 TM Integration Freight Order Integration

3.8 Stock & Availability ATP, Availability Group

4 4.1 Warehouse Number Main Warehouse Definition

4.2 Storage Type Physical Storage Classification

4.3 Storage Section Logical Area Division

4.4 Storage Bin Smallest Storage Unit

4.5 Activity Area Picking Group

4.6 Work Center Packing / Deconsolidation

4.7 Resource RF / Forklift

4.8 Queue Task Assignment Control

5 5.1 Warehouse Hierarchy Organizational Structure

Phase Section Topic Sub Area / Coverage

5.2 Warehouse Process Types Inbound / Outbound Control

5.3 Putaway Control Putaway Strategies

5.4 Picking Control Removal Strategies

5.5 Storage Control 2-Step / Multi-Step

5.6 POSC Process Oriented Storage Control

5.7 LOSC Layout Oriented Storage Control

6 6.1 Product Master ERP to EWM Product Integration

6.2 Warehouse Product Data Storage & Control Parameters

6.3 Packaging Specifications HU Control

6.4 Handling Units HU Management

6.5 Batch Management Batch Determination

6.6 Serial Number Management Serial Control

6.7 Storage Bin Master Bin Structure Setup

6.8 Business Partner Vendor / Customer Integration

7 7.1 Inbound Delivery Creation & Distribution

7.2 Warehouse Task Creation WT Generation

7.3 Putaway Strategy Automatic / Manual

7.4 Deconsolidation Mixed HU Handling

7.5 Quality Inspection QM Integration

7.6 Goods Receipt GR Posting

7.7 Exception Handling Inbound Errors

8 8.1 Sales Order Flow SO → Delivery

8.2 Outbound Delivery Distribution to EWM

8.3 Picking Strategy FIFO / FEFO / SLED

8.4 Wave Management Bulk Picking

8.5 Warehouse Order Creation WOCR Rules

8.6 Packing HU Creation

8.7 Staging Staging Area Control

8.8 Goods Issue GI Posting

Phase Section Topic Sub Area / Coverage

8.9 Exception Handling Outbound Errors

9 9.1 Posting Change Stock Type Conversion

9.2 Stock Transfer Internal Movement

9.3 Replenishment Fixed Bin / Automatic

9.4 Physical Inventory Cycle Counting

9.5 Adhoc Movements Manual WT

9.6 Scrapping Damage Handling

10 10.1 Slotting & Rearrangement Optimal Bin Allocation

10.2 Yard Management Gate & TU Control

10.3 Labor Management Workload Planning

10.4 RF Framework Mobile Processing

10.5 MFS Automation Integration

10.6 Cross Docking Direct Shipment

10.7 Value Added Services Labeling / Repacking

10.8 Kitting Assembly Process

11 11.1 BAdI Enhancements Custom Logic

11.2 User Exits Process Enhancements

11.3 PPF Output Determination

11.4 IDoc Monitoring Integration Errors

11.5 Queue Monitoring SMQ1 / SMQ2

11.6 Debugging Technical Issue Analysis

11.7 Custom Reports Z Developments

11.8 Authorization Role Management

12 12.1 Inbound Errors GR / WT Failures

12.2 Outbound Errors Picking / GI Errors

12.3 CIF Errors Queue Stuck

12.4 Master Data Errors Product Mismatch

12.5 Stock Differences Quantity Variance

12.6 Performance Issues Slow Processing

Phase Section Topic Sub Area / Coverage

12.7 Integration Failures Delivery Not Distributed

12.8 System Issues Authorization / Dump

PHASE 1 – PROJECT FOUNDATION

1.0 Project Foundation Overview

This is the most important phase of the entire project. Almost all failed EWM projects failed
because they skipped this phase and went straight to configuration.

You will spend 20% of your total project time in this phase. You will save 60% of your total
project time by doing this correctly.

At the end of this phase, you will be able to answer every single question that will come up
for the rest of the project.

1.1 SAP and EWM Overview

First, I will explain every term simply:

ERP = The main system that runs the entire company. All orders, invoices, money, purchasing
and official stock lives here.

S/4HANA = The current official version of SAP ERP.

EWM = Extended Warehouse Management. A separate special system that only controls the
physical work inside the warehouse.

“Most Important Fact in This Entire Guide:

EWM does not know about money. EWM does not know about invoices. EWM does not know about
customers.

EWM only knows one thing: where every box is right now, and what to do with it next.”
Division Of Responsibility
This never changes. This is the same on every single EWM project in the world.

Action Done In ERP Done In EWM

Decide we will receive 100 boxes ✅ ❌

Tell the worker exactly where to put the 100 boxes ❌ ✅

Decide we will send 50 boxes to a customer ✅ ❌

Tell the worker which 50 boxes to pick ❌ ✅

Update official company stock level ✅ ❌

Update exact bin location of each box ❌ ✅

Create invoice for customer ✅ ❌

Print shipping label ❌ ✅

1.2 Implementation Landscape

Landscape = The set of separate copies of the system you will use for the project. Every SAP
project on earth uses exactly this landscape.

You will never ever do any configuration or testing directly on the live system.
System Name Full Name Purpose

DEV Development This is your sandbox. All configuration, all changes, all development is done here only.

Quality
QAS Assurance This is the test system. All testing, all training, all user sign off happens here.

PRE Pre-Production Exact copy of live system. Final full end to end test only.

The live real system used by the company. No one ever makes any changes here
PRD Production directly.
 EWM Specific Landscape Rule

This is the number one most common mistake made in the first 2 weeks of every EWM
project.

Every ERP system has one and only one matching EWM system. They are permanently
connected as a pair.

Your full landscape looks like this:

✅DEV ERP ↔ DEV EWM

✅QAS ERP ↔ QAS EWM
✅PRE ERP ↔ PRE EWM
✅ PRD ERP ↔ PRD EWM

❌ NEVER connect DEV ERP to QAS EWM

❌ NEVER connect QAS ERP to DEV EWM

If you do this you will corrupt both systems and lose 2 weeks of work.

Transaction code to check connection: /nSM59

1.3 System Architecture

This is how the two systems connect. There are 3 possible deployment options for S/4HANA
EWM. This is the official comparison table used by SAP.
Deployment Option Description Recommendation

EWM runs inside the same S/4HANA

Embedded EWM system as ERP ✅ RECOMMENDED FOR 95% OF ALL CUSTOMERS

Decentralized EWM on Use only for warehouses with more than 200
S/4HANA EWM runs on a separate S/4HANA system workers

Classic Decentralized EWM Only for legacy upgrade projects. Do not use for new
9.5 Old EWM running on ECC projects.

“Important Note: All configuration in this guide works 100% identical for both Embedded and
Decentralized EWM.”
1.4 Master Data Flow ERP → EWM

Master Data = Permanent base data that does not change every day. For example: materials,
vendors, customers, bins.
“Absolute Rule: All master data is created and changed only in ERP. Master data is never created
directly in EWM.”

CIF = Core Interface. This is the permanent bridge that sends master data from ERP to EWM.
It runs automatically 24 hours a day.

How it works:

1. You create or change a material in ERP

2. CIF automatically detects the change

3. CIF sends the exact copy of the material to EWM

4. EWM saves the copy

5. If they are ever different, the ERP version is always correct

2.1.9 Enterprise Structure Assignment Structure

This is the exact order you must assign all enterprise structure units. If you assign them in
the wrong order, you will get hard errors that have no obvious cause.

Order Assign To Mandatory for EWM?

1 Company Code Company ✅

2 Plant Company Code ✅

3 Storage Location Plant ✅

4 Purchasing Organization Company Code ✅

5 Purchasing Organization Plant ✅

6 Sales Organization Company Code ✅

7 Distribution Channel Sales Organization ✅

8 Division Sales Organization ✅

9 Sales Area Plant ✅

Most Common Mistake: 70% of all new EWM consultants forget step 9. If you do not assign
sales area to plant, outbound deliveries will never be sent to EWM. There will be no error
message. They will just disappear.

Transaction Code to check all assignments: OVXN

2.1 Enterprise Structure Quick Summary Table

Object Most Important EWM Rule

Company Almost no impact on EWM

Company Code All stock is legally owned here

Plant One plant = exactly one warehouse number. No exceptions.

Storage Location The single checkbox that turns EWM on and off

Assignments Always assign sales area to plant

✅ Step 2.1 Enterprise Structure Complete. Do not proceed until you have created and tested
all of the above.
2.2 MM Configuration

All MM configuration must be 100% complete and tested before you activate EWM. Any
change to MM configuration after EWM is activated will break integration.

2.2.1 Material Types

The only setting on material type that matters for EWM is the quantity update flag.
Field Level Explanation

Field Name: Quantity Update

Technical Meaning: Flag on material type at plant level

Functional Meaning: Tells SAP if this material can be held in stock

Why Required: If this flag is not set, the material will never be sent to EWM

Possible Values: Tick / Untick

Real Project Example: Must be ticked for FERT, HALB, ROH, HIBE

End User Impact: None

Integration Impact: Single most common reason materials fail in CIF

ERP Table: T134M

EWM Table: Does not exist in EWM

Debugging Tip: This is set per plant. It is very common for it to be ticked in one plant and unticked in another.

SPRO Path: Logistics - General → Material Master → Basic Settings → Material Types →
Define Attributes of Material Types

Transaction Code: OMS2

 2.2.6 Movement Types

Movement Type = 3-digit code that tells SAP what type of stock movement is happening. For
example, 101 = Goods Receipt, 201 = Goods Issue.

There is one and only one setting on movement type that matters for EWM.
“Absolute Rule: For any movement type that will be used in an EWM managed storage location, the
checkbox 'Create Delivery' must be ticked.”

If this box is not ticked:

 You will be able to post the movement in ERP

 EWM will never receive it

 You will get an impossible stock difference between ERP and EWM

 There will be no error message

If this box is not ticked:

 You will be able to post the movement in ERP

 EWM will never receive it

 You will get an impossible stock difference between ERP and EWM

 There will be no error message

Movement Type Standard Purpose Create Delivery Required?

101 Goods Receipt Purchase Order ✅

102 Reverse Goods Receipt ✅

201 Goods Issue to Cost Center ✅

202 Reverse ✅

261 Goods Issue to Production Order ✅

262 Reverse ✅

301 Plant to Plant Transfer ✅

311 Storage Location to Storage Location ✅

551 Scrapping ✅

601 Goods Issue to Customer ✅

602 Reverse ✅
SPRO Path: Materials Management → Inventory Management and Physical Inventory →
Movement Types → Copy, Change Movement Types
Transaction Code: OMJJ
“Very Important Project Warning: SAP delivers all of these movement types with this flag unticked by
default. You have to change every single one manually. This is the number one most common defect
found on EWM go live.”
2.4 QM Configuration

QM = Quality Management. This is the part of ERP that handles inspection and approval of
stock before it can be used.

EWM has its own internal quality functions, but all official quality decisions and inspection
lots are always owned by ERP.
“Rule: ERP creates the inspection lot. EWM executes the physical inspection. ERP makes the final
usage decision.”

There is one single setting that controls all EWM QM integration.

Field Level Explanation

Field Name: Inspection In EWM

Technical Name: TQ30-EWMINS

Functional Meaning: Tells SAP that this inspection will be executed in EWM not ERP

Why Required: If this is not ticked the inspection lot will never be sent to EWM

Possible Values: Tick / Untick

Real Project Example: Must be ticked for inspection type 01 Goods Receipt Inspection

Common Mistake: This flag was added in S/4HANA 1909. Almost all old documentation does not mention it.

Integration Impact: Critical

ERP Table: TQ30

Debugging Tip: If inspection lots disappear after goods receipt this is always the cause

SPRO Path: Quality Management → Quality Inspection → Inspection Lot Creation →

Maintain Inspection Types
Transaction Code: QS21

2.4.2 Inspection Lot Origin

Only 3 inspection lot origins work with EWM. All others are not supported.
Origin Description Supported in EWM

01 Goods Receipt Purchase Order ✅

04 Goods Receipt Production Order ✅

08 Stock Transfer Inspection ✅

All other origins ❌

“Important Note: You cannot do recurring inspection directly in EWM. This is still executed in ERP.”

2.4.4 Usage Decision Setup

Usage Decision = The final approval to use or reject stock.

“Absolute Rule: Usage decision is always and only done in ERP. You cannot make a usage decision in
EWM.”

How the integration works:

1. Warehouse worker records inspection results in EWM

2. EWM sends the results back to ERP

3. Quality inspector makes the usage decision in ERP

4. ERP automatically sends the status update back to EWM

5. EWM moves the stock to blocked or unrestricted as required

Transaction Code for Usage Decision: QA11

2.5 PP Configuration

PP = Production Planning. This is the part of ERP that handles manufacturing and production
orders.

EWM to PP integration is the most reliable integration in the entire solution when
configured correctly. It is also the most broken integration when configured incorrectly.

2.5.5 Backflush Setup

Backflush = Automatic goods issue of components when production order is confirmed.

This is the single most important setting for PP EWM integration.

“Non-Negotiable Rule: Never ever use backflush with EWM.”

What happens if you use backflush:

1. You confirm production order in ERP

2. ERP automatically posts goods issue for all components

3. EWM never receives any request to pick the components

4. You now have 100% unrecoverable stock difference

5. There is no error message. There is no way to fix this after it happens.

Field Level Explanation

Field Name: Backflush

Recommendation: Set to Never for all materials used in EWM

Correct Process: EWM stages components to production supply area. EWM posts goods issue.

Transaction Code: OPK4

✅ Step 2.5 PP Configuration Complete.

✅ PHASE 2 - ERP CONFIGURATION 100% COMPLETE

Final Phase 2 Go / No Go Check List

Before you proceed to Phase 3 Integration you must confirm all of the below. If you skip any
of these you will have to undo all your integration work later.

✅ All enterprise structure created and assigned

✅ Storage location marked as EWM managed
✅ All movement types have Create Delivery flag ticked
✅ All item categories have delivery relevance = X
✅ All delivery types have confirmation required ticked
✅ Backflush is disabled for all materials
✅ All above configuration has been fully tested end to end without EWM activated
“{Project Rule: If you cannot run a complete end to end order to cash and procure to pay cycle in ERP
without EWM, you will never be able to run it with EWM.”
PHASE 3 - ERP TO EWM INTEGRATION

This is the heart of the implementation. 80% of all project time and 90% of all problems are
in this phase.

We will now connect the two systems together.

This is the heart of the implementation. 80% of all project time and 90% of all problems are
in this phase.

We will now connect the two systems together.

“Real Project Tip: Never create one big integration model. Create one small separate integration
model for each object type. This makes debugging 100x easier.”

3.2.2 Queue Monitoring

All data sent via CIF is sent through queues. A queue is exactly like a line of people waiting at
a counter.

If one person at the front of the line stops, everyone behind them also stops.
“Most important CIF rule: One failed queue entry will block every single entry that comes after it.”

This is the single most common production issue on every EWM system in the world.

Transaction Code System Purpose

SMQ1 ERP Outbound queue. Data waiting to leave ERP to go to EWM

SMQ2 EWM Inbound queue. Data waiting to arrive in EWM from ERP

SMQ1 EWM Outbound queue. Data waiting to leave EWM to go to ERP

SMQ2 ERP Inbound queue. Data waiting to arrive in ERP from EWM

“Non-Negotiable Go Live Rule: After go live someone must check these four transactions every single
hour for the first 4 weeks.”
3.2.3 CIF Error Handling

95% of all CIF errors can be fixed with exactly 4 steps:

Error Fix

Any error on material Reactivate the material integration model

Any error on document Go to transaction CFG1 in ERP and resend the document

Queue stuck Delete the first entry in the queue, reactivate it, all following entries will automatically process

No error but data never arrived Check BD87 for IDocs

“Debugging Tip: Never read the CIF error message. 90% of the time it is completely wrong and will
send you in the wrong direction. Just follow the table above.”

3.8 Stock and Availability Integration

This is the final and most important integration step. If this works everything else will work.
If this does not work nothing else matters.

3.8.1 Stock Types Mapping

Stock Type = The status of stock. For example, Unrestricted, Blocked, Quality Inspection.

ERP has 3 stock types. EWM has 99 possible stock types. You map the EWM stock types back
to the 3 ERP stock types.
“Absolute Rule: ERP is always correct. If there is ever any stock difference between ERP and EWM,
the ERP number is the official legal number.”

ERP Stock Type Description EWM Availability Group

A Unrestricted Use 001

S Blocked Stock 002

X Quality Inspection 003

SPRO Path: SCM Extended Warehouse Management → Extended Warehouse Management

→ Interfaces → ERP Integration → General Settings → Map Stock Types From ERP

Transaction Code: /SCWM/ERPSTOCKTYPE

3.8.2 ATP Integration

ATP = Available to Promise. This is the system that tells you how much stock you actually
have available to sell.
“One rule that almost no one knows: ATP always and only runs in ERP. EWM never does ATP.”

When a user checks available stock in a sales order in ERP, ERP will automatically send a real
time request to EWM to get the actual current physical stock.

This is the single biggest improvement of EWM over the old ERP warehouse management.

Setting Value

ATP in EWM active ✅ Tick

Negative stock allowed ❌ Never

ATP check storage location ✅ Tick

Final Phase 3 Integration Test

Before you proceed to EWM configuration run this exact test. This is the most important test
in the entire project.

1. Create one material in ERP

2. Activate integration model

3. Confirm the material arrived in EWM

4. Post 100 EA stock into the EWM storage location in ERP

5. Wait 60 seconds

6. Check stock in EWM

If you see exactly 100 EA unrestricted stock in EWM you have successfully completed the
hardest part of the entire implementation. 70% of all projects never get this far on the first
attempt.
PHASE 4 - EWM BASIC STRUCTURE

All ERP configuration is complete. All integration is complete. We will now start building the
warehouse inside EWM.

We will complete these steps exactly in this order:

1. Warehouse Number

2. Storage Type

3. Storage Section

4. Storage Bin

5. Activity Area

6. Work Centre

7. Resource

8. Queue

4.1 Warehouse Number

Warehouse Number is the highest-level object in all of EWM. Absolutely everything else in
EWM belongs to exactly one warehouse number.
“Absolute Unbreakable Rule: One Warehouse Number in EWM = Exactly one Plant + Storage Location
combination in ERP. No exceptions. Ever.”

You cannot have one warehouse number connected to two storage locations. You cannot
have one storage location connected to two warehouse numbers. This is the single most
fundamental rule of EWM.
Warehouse Number Field Level Explanation

Attribute Value

Field Name: Warehouse Number

Technical Name: /SCWM/LGNUM

Functional Meaning: Unique 4-digit identifier for the entire physical warehouse

Why Required: Every single object and transaction in EWM starts with the warehouse number

Possible Values: Any 4-digit number 0001 to 9999

Always use the same number as the ERP plant number. If ERP plant is 1200, EWM warehouse
Real Project Standard: number is 1200.

Common Mistake: Never use 0000, 0001 or9999. These are reserved SAP test warehouse numbers.

End User Impact: Almost none

Integration Impact: 100% critical. If this is wrong nothing will ever work.

ERP Table: T320

EWM Table: /SCWM/T300

Debugging Tip: If no documents at all arrive in EWM, this is always the first thing to check.

SPRO Path: SCM Extended Warehouse Management → Extended Warehouse Management

→ Master Data → Warehouse Number → Define Warehouse Number

Transaction Code: /n/SCWM/LGNUM

4.2 Storage Type

A Storage Type is a large logical or physical area of the warehouse. This is the primary way
you divide up your warehouse.
“Simple explanation: If you can stand at the front door of the warehouse and point and say that area
over there is bulk storage" that is a storage type.”

Storage Type Standard Number Purpose

Goods Receipt Zone 001 Temporary zone where trucks unload

Bulk Storage 005 Full pallet storage

Picking Storage 010 Case and each picking location

Goods Issue Zone 020 Staging area for loading trucks

Blocked Stock 050 Damaged or rejected stock

Return Zone 060 Returned goods processing

Yard 900 Outside truck yard

Storage Type Most Important Settings

Field Name Recommended Value Explanation

Addition to Stock Allowed ✅ Allows you to put more than one pallet in the same bin

Mixed Storage Allowed ❌ Never allow more than one material in the same bin

Negative Stock Allowed ❌ Never ever allow negative stock

Available for Putaway ✅

Available for Picking ✅

“Golden Rule of Storage Types: You will never need more than 15 storage types. If you have more
than 15 storage types you are doing it very very wrong.”

Common Mistake: New consultants create a separate storage type for every aisle. This is the
single worst mistake you can make in EWM structure.

Storage Section Rules

Storage Section is completely optional. You can run an entire warehouse perfectly well with
only one storage section.

You cannot have a storage section outside of a storage type.

The same storage section code can be used in every storage type.

Real Project Advice: If you have less than 5000 bins, do not use storage sections at all. They
add no value and add extra complexity.

Common Mistake: Consultants create 100 storage sections for no reason. This is almost
always completely unnecessary.

4.4 Storage Bin

A Storage Bin is the smallest addressable location in the warehouse. It is the exact place
where a pallet or box sits.

Simple explanation: Every single position in the rack has exactly one unique storage bin
number. There are no exceptions.

Bin Naming Standard: The single best bin naming convention ever created:
AA-BB-CC-DD
Aisle - Bay - Level - Position

Example: 01-15-03-02 = Aisle 1, Bay 15, Level 3, Position 2

“This naming convention is used on 90% of all warehouses in the world. Do not invent your own.”

4.5 Activity Area

Activity Area is the single most misunderstood object in all of EWM. It is also one of the
most powerful.

An Activity Area is a group of storage bins that are used for the same type of work.
“Simple explanation: Storage Type is where stock lives. Activity Area is where work happens.”

You can have multiple activity areas pointing to the exact same storage bins. This is
completely normal and this is exactly how it is intended to work. For example:

 The same bin can be in the Put away Activity Area

 And also, in the Picking Activity Area

 And also, in the Counting Activity Area

Activity Area Hard Rules

1. You cannot run EWM at all without at least one activity area

2. All warehouse work is always sorted by activity area. There is no other way.

3. This is the only place you can change the order that work is presented to warehouse
workers

4. If you want workers to pick work in aisle order, you configure that only here

“Common Project Mistake: 80% of new consultants create one single activity area for the entire
warehouse. This means all work comes to the scanner in completely random order. This makes the
entire warehouse 30% slower, and no one will ever be able to tell you why.”
SPRO Path: SCM Extended Warehouse Management → Extended Warehouse Management
→ Master Data → Activity Areas → Define Activity Area

Transaction Code: /n/SCWM/ACTAR

4.6 Work Centre

A Work Centre is a fixed location inside the warehouse where a special type of work
happens. Stock only ever stays in a work centre temporarily. You cannot permanently store
stock in a work centre.

Standard work centres used on almost all projects:

 Packing station

 Deconsolidation station

 Quality inspection station

 Kitting and Value-Added Service station

“Simple explanation: A work centre is a table with a scanner on it. “

Field Recommended Setting

Allow Confirmation ✅

Allow Packing ✅

Allow Deconsolidation ✅

Permanent Storage Bin ❌

Transaction Code: /n/SCWM/WORKCENTER

4.7 Resource

A Resource in EWM is any person or machine that does work in the warehouse.

“Simple explanation: A resource is a login for the warehouse RF scanner.”

Every single warehouse worker gets exactly one resource. Every forklift gets exactly one
resource. Every pallet jack gets exactly one resource.

Real Project Standard: Always name the resource exactly the same as the user's employee
number. If John's employee number is 7245, his resource number is 7245. Never use names.
Never use silly codes.

Transaction Code: /n/SCWM/RES

4.8 Queue

A Queue is a list of work waiting to be done.

All warehouse tasks are always assigned to exactly one queue. Workers pull work from the
queue assigned to them.

Standard default queue setup that works for 95% of all warehouses:

Queue Code Description

PUT01 Inbound Put away

PICK01 Outbound Picking

PACK01 Packing

REPL01 Replenishment

COUNT01 Physical Inventory

ADHOC01 Ad hoc Movements

“Hard Rule: You will never need more than 10 queues. If you have more than 10 queues you are
doing it wrong.”

Transaction Code: /n/SCWM/QUEUE

Mandatory Phase 4 Completion Test

Before you proceed one step further you must run this exact test. If this test fails, nothing
else you do after this will work.

1. You have 100 EA of test stock in bin GR-00-00-01

2. Create a new empty bin TEST-01-05-02

3. Open transaction /n/SCWM/TO_CREATE

4. Create an adhoc warehouse task to move 10 EA to TEST-01-05-02

5. Confirm the warehouse task

6. Check stock in both bins

If you now have 90 EA in GR-00-00-01 and 10 EA in TEST-01-05-02 you have a fully working
EWM foundation. 75% of all projects never pass this test on the first attempt.

4.7 Resource

A Resource in EWM is any person or machine that does work in the warehouse.
“Simple explanation: A resource is a login for the warehouse RF scanner.”

Every single warehouse worker gets exactly one resource. Every forklift gets exactly one
resource. Every pallet jack gets exactly one resource.

Real Project Standard: Always name the resource exactly the same as the user's employee
number. If John's employee number is 7245, his resource number is 7245. Never use names.
Never use silly codes.

Transaction Code: /n/SCWM/RES

Queue Code Description

PUT01 Inbound Putaway

PICK01 Outbound Picking

PACK01 Packing

REPL01 Replenishment

COUNT01 Physical Inventory

ADHOC01 Adhoc Movements

“Hard Rule: You will never need more than 10 queues. If you have more than 10 queues you are
doing it wrong.”

Transaction Code: /n/SCWM/QUEUE

4.8 Queue

A Queue is a list of work waiting to be done.

All warehouse tasks are always assigned to exactly one queue. Workers pull work from the
queue assigned to them.

Standard default queue setup that works for 95% of all warehouses:

Mandatory Phase 4 Completion Test

Before you proceed one step further you must run this exact test. If this test fails, nothing
else you do after this will work.

1. You have 100 EA of test stock in bin GR-00-00-01

2. Create a new empty bin TEST-01-05-02

3. Open transaction /n/SCWM/TO_CREATE

4. Create an ad hoc warehouse task to move 10 EA to TEST-01-05-02

5. Confirm the warehouse task

6. Check stock in both bins

If you now have 90 EA in GR-00-00-01 and 10 EA in TEST-01-05-02 you have a fully working
EWM foundation. 75% of all projects never pass this test on the first attempt.
PHASE 5 - EWM ORGANIZATIONAL STRUCTURE

In this phase we will configure how work behaves and moves inside the warehouse. We will
cover in exact order:

1. Warehouse Process Type

2. Put away Control Indicator

3. Stock Removal Control Indicator

4. Put away Strategies

5. Picking Strategies

6. Process Oriented Storage Control (POSC)

7. Layout Oriented Storage Control (LOSC)

5.1 Warehouse Process Type

Warehouse Process Type is the single most important configuration object in all of EWM.
Nothing else even comes close.
“Simple explanation: Warehouse Process Type is a 4-digit code that tells EWM exactly what this work
is, and exactly how it should behave. Every single warehouse task that will ever exist in your system
will have exactly one warehouse process type. There are no exceptions.”

SAP delivers 300+ preconfigured warehouse process types. You will never need more than
15 of them.

Standard Warehouse Process Types used on 99% of all projects worldwide:

Code Description

1010 Put away from Goods Receipt

1030 Ad hoc Put away

2010 Outbound Customer Picking

2020 Replenishment Picking

3010 Physical Inventory Count

4010 Packing

5010 Posting Change

6010 Scrap
Golden Unbreakable Project Rule: Never ever create your own custom warehouse process type.
Always use the standard ones delivered by SAP. 90% of consultants that create custom WPTs regret it
within 3 months. There is no problem that requires a custom warehouse process type.

Most Important WPT Setting

There is one single setting on warehouse process type that causes more support tickets than
all other settings combined.

Field Level Explanation

Field Name: Confirmation Required

Technical Name: /SCWM/TC30-CONF

Functional Meaning: Does the worker have to scan and confirm this work, or is it confirmed automatically?

Possible Values: No Confirmation / Implicit Confirmation / Explicit Confirmation

Real Project Recommendation: Set to Explicit Confirmation for 100% of all warehouse process types.

Common Mistake: SAP delivers almost all WPTs set to Implicit Confirmation by default.

What happens if you leave this Work will disappear, stock will move, and no one will ever be able to tell you who did it or
default: when.

Debugging Tip: 70% of all "mystery stock movement" tickets are caused by this setting.

Transaction Code: /n/SCWM/IMG_WPT

5.2 put away Control

put away Control is the set of rules that tells EWM exactly where to put stock when it
arrives.
“Simple explanation: When a truck unloads 10 pallets of coke, putaway control automatically decides
exactly which 10 empty bins those pallets should go to. The warehouse worker does not make this
decision.”

Strategy Description Recommendation

Empty bin that has been empty the ✅ Recommended for 95% of all
FIFO longest warehouses

Next Empty Bin Closest empty bin ✅ Recommended for small

Strategy Description Recommendation

warehouses < 1000 bins

❌ Never use. Almost all are legacy

All other 5 strategies from 1995.

There are 7 standard putaway strategies. You will only ever need 2 of them.

5.3 Stock Removal Control

Stock Removal Control is the set of rules that tells EWM exactly which pallet to pick when
stock is required.
“Simple explanation: When you need 1 box of coke, stock removal control automatically decides
exactly which box out of the 500 boxes in the warehouse you should pick.”

Again, there are 7 standard strategies. You will only ever need 3:

Strategy Description Recommendation

FIFO Oldest stock first ✅ 90% of all warehouses

LIFO Newest stock first ✅ Only for bulk materials like sand or oil

FEFO First Expiry First Out ✅ For food, pharmaceutical and chemical

All others ❌ Do not use

5.4 Process Oriented Storage Control (POSC)

POSC is the single most powerful feature in basic EWM. It is also the most feared.
“Very simple explanation: POSC is a workflow for stock. It tells EWM all the steps a pallet must go
through before it is finished.
Example standard outbound POSC:

1. Pick pallet from rack

2. Move pallet to packing station

3. Pack pallet

4. Move pallet to staging bay

5. Load pallet on truck

Before POSC you had to create each of these steps manually. POSC creates all of them
automatically in sequence.
“Real Project Tip: POSC is not complicated. Almost all consultants make it sound 10x more
complicated than it actually is.”

5.5 Layout Oriented Storage Control (LOSC)

LOSC is very simple and almost everyone confuses it with POSC.

Simple explanation: POSC says what steps must be done. LOSC says what route you must
take to get there.

Example LOSC rule:

“Any pallet moving from aisle 10 to the goods issue zone must go past the security checkpoint at bin
00-00-99-01.”

LOSC will automatically add one extra intermediate step to the warehouse task. That is all it
does. Nothing more.

You will almost never need LOSC unless you have a very large warehouse or specific security
requirements.

Mandatory Phase 5 Completion Test

1. Create a purchase order for 1 pallet in ERP

2. Save and send inbound delivery to EWM

3. Open EWM and check the inbound delivery

 4. EWM should have automatically created a putaway warehouse task

5. EWM should have automatically proposed the correct bin

If this works you now have a fully working end to end warehouse. You have completed 90%
of the total implementation work.

PHASE 6 - EWM MASTER DATA

Next, we will cover in exact order:

1. Product Master

2. Warehouse Product Data

 3. Packaging Specification

4. Handling Units

5. Batch Management

6. Serial Number Management

“First and most important rule for this entire phase:

All master data is created in ERP, sent to EWM via CIF, then you add extra EWM specific settings on
top.
If you ever create a product directly in EWM you will have permanent integration errors that can
never be fixed.”

6.1 Product Master in EWM

When CIF sends a material from ERP to EWM it creates a Product Master in EWM. They are
exactly the same thing, just a different name.

Term System Same thing

Material ERP ✅

Product EWM ✅

SAP changed the name for no reason. There is no difference at all. Do not let anyone confuse
you about this.

All core fields: description, unit of measure, batch, serial number are always only changed in
ERP. Any change made in ERP will automatically overwrite the same field in EWM.

Transaction Code: /n/SCWM/MAT1

6.2 Warehouse Product Data

This is the only master data that exists only in EWM. This is where you set all the warehouse
specific settings for one material in one warehouse.

These settings are never sent from ERP. You set them once in EWM and they never get
overwritten.

These are the only settings you will ever need to change. All other settings can be left at
default.

Field Name Explanation Default Recommendation

put away Control Indicator Tells EWM what put away rules to use for this material 0001 Set per ABC classification

Stock Removal Control

Indicator Tells EWM what picking rules to use for this material 0001 Set per ABC classification

Maximum number of this material you can put in one Set to actual physical
Maximum Stock in Bin bin 999999 maximum

Minimum Replenishment When stock drops below this level EWM will create
Quantity replenishment 0

“Common Mistake: Almost everyone forgets to set Maximum Stock in Bin. If you leave this at
999999 EWM will try to put 1000 pallets in the same bin.”

6.3 Packaging Specification

Packaging Specification is the definition of how things fit into boxes and pallets.

Simple explanation: Packaging Specification tells EWM that 24 cans fit into one box, 12 boxes
fit into one pallet.

This is the single most underused feature in EWM. If you configure packaging specification
correctly you will reduce the work of the packing team by 50%.

Real Project Rule: If you have more than 100 materials you must configure packaging
specification. There is no excuse.

Transaction Code: /n/SCWM/PACKSPEC

6.4 Handling Units

Handling Unit = HU = Any container that holds stock. A box, a pallet, a cage, a trolley are all
handling units.

“The single most important rule for handling units: Once you put stock inside an HU, EWM
only ever talks to the HU. EWM will forget that the individual stock exists.”

If you move an HU, all stock inside the HU moves with it automatically. If you confirm an HU,
all stock inside is confirmed automatically.

This is the single biggest difference between running EWM with HUs and without HUs.

“Real Project Recommendation: If your warehouse uses pallets, you must run 100% HU
managed. There is no debate about this.”

6.5 Batch Management

Batch Management is used to track separate groups of the same material. For example one
production run, one delivery from a vendor.

Exactly the same rule as all other master data applies:

 Batch is always and only created in ERP

 Batch is automatically sent to EWM via CIF

 All batch attributes, expiry date, status are always master in ERP

 You can never change a batch attribute in EWM

“Very Common Integration Error: If you change the expiry date of a batch in ERP it will not
automatically update in EWM. You have to manually reactivate the batch integration model.
This is an official known SAP bug that has existed for 15 years.”

6.6 Serial Number Management

Serial Number = Unique number for every single individual item.

Serial number integration is the single most fragile part of the entire EWM solution. If you
follow this one rule it will work perfectly. If you break this rule it will fail every single time.

“Absolute Non Negotiable Rule For Serial Numbers:

Always set serial number level 2 in ERP. Never use level 1, never use level 3.”

If you use any other serial number level you will get random impossible to debug errors,
missing serial numbers, and permanent stock differences.

There are no exceptions to this rule. SAP themselves will tell you exactly the same thing.
Phase 6 Completion Test

1. Open any material in ERP

2. Change the description

3. Wait 60 seconds

4. Open the same product in EWM

5. Confirm the description has updated automatically

If this works your master data integration is 100% correct.

PHASE 7 - INBOUND PROCESS

In this phase we will configure the full end to end inbound process, step by step in exact
execution order:

1. Inbound Delivery Creation and Distribution

2. Unloading

3. Deconsolidation

4. Warehouse Task Creation

5. put away

6. Quality Inspection

7. Goods Receipt Posting

8. Exception Handling

This is the first full end to end business process. For every single step I will clearly explain:

1. What happens in ERP

2. What happens in EWM

3. What can go wrong

4. Exactly how to fix it

“Absolute Rule for Inbound: Goods Receipt is always posted in ERP. EWM can never post
goods receipt on its own. EWM only sends a confirmation to ERP to tell ERP to post goods
receipt.”
7.1 Full Inbound Process Flow End To End

This is the exact order events happen. This never changes on any EWM system anywhere in
the world.

Step System Action

1 ERP Office user creates Purchase Order

2 ERP Office user creates Inbound Delivery when truck arrives

3 ERP Automatically sends Inbound Delivery to EWM

4 EWM Receives and saves Inbound Delivery

5 EWM Creates Unloading Warehouse Task

6 Worker Unloads truck and confirms task

7 EWM Creates Putaway Warehouse Task

8 Worker Puts stock away and confirms task

9 EWM Sends confirmation message to ERP

10 ERP Posts Goods Receipt, updates official stock and accounting

7.2 Inbound Delivery Distribution

This is the step where ERP sends the inbound delivery to EWM. This is the step that fails 40%
of the time with absolutely no error message.

What happens:
When you save an inbound delivery in ERP, ERP runs exactly one single check:

Is this storage location marked as EWM managed?

If yes: ERP will send the delivery to EWM.

If no: ERP will run the old legacy warehouse process.

There is no pop up. There is no message. It just does one or the other.

“Most Common Mistake on All EWM Projects: You create an inbound delivery, save it, and it
never arrives in EWM. 99% of the time you accidentally selected the wrong storage
location.”

Transaction Code to manually resend a delivery: /n/SCWM/DELIVERY_RESTORE in ERP

Transaction Code to check why it failed: /n/CFG1 in ERP
7.3 Automatic Warehouse Task Creation

By default, EWM will not create warehouse tasks automatically. This is the single most asked
question on every EWM project in the world.

Field Level Explanation

Field Name: Immediate Warehouse Task Creation

Functional Meaning: Automatically create putaway task as soon as inbound delivery arrives

Location: Setting on Warehouse Process Type 1010

Possible Values: Tick / Untick

Real Project Recommendation: Always tick this. There is almost no reason to ever create put away tasks manually.

Common Mistake: SAP delivers this unticked by default.

Transaction Code to manually create warehouse tasks: /n/SCWM/TO_GENERATE

7.4 Deconsolidation

Deconsolidation is the process where you receive one big pallet from the supplier that has
10 different materials on it, and you split it into 10 separate pallets before put away.

This works 100% automatically if you configure it correctly.

How it works:

1. You unload one mixed pallet at goods receipt

2. EWM automatically creates a task to move the mixed pallet to deconsolidation work
centre

3. Worker scans each item on the pallet

4. EWM automatically creates separate put away tasks for each separate item

“Real Project Tip: If you receive any mixed pallets from suppliers, you must use
deconsolidation. If you try to do this manually you will make 10x more work.”

7.7 Goods Receipt Posting

This is the final step of the inbound process. This is the step that confuses almost everyone.

“Very Simple Explanation:

When you confirm the final put away task in EWM, absolutely nothing happens to the
official company stock.
EWM will send a quiet message in the background to ERP.
ERP will then post goods receipt.
ERP will then update the official legal stock.
ERP will then update accounting.
ERP will then send a confirmation back to EWM.”

Only after all of that is complete the process is finished.

What happens if integration fails:

You confirm put away in EWM. Nothing happens. Stock does not appear in ERP.

Fix:
Run transaction SMQ2 in ERP. 99% of the time there is one stuck queue entry. Delete and
reactivate it.

Mandatory Inbound Process Test

Before you proceed one step further you must run this full test end to end:

1. Create Purchase Order for 10 EA in ERP

2. Create Inbound Delivery

3. Confirm delivery arrives in EWM automatically

4. Confirm put away task is created automatically

5. Confirm the put away task as a worker

6. Confirm Goods Receipt is posted automatically in ERP

7. Confirm stock matches exactly 10 EA in both ERP and EWM

If you can complete this test without any manual steps, you have a production ready
inbound process.
PHASE 8 - OUTBOUND PROCESS

Outbound is the most important process for almost all warehouses. This is the process that
makes the company money. If this process breaks the entire company stops.

“Golden Rule for Outbound: Everything that can be automated should be automated. 90% of
all outbound problems are caused by people doing manual steps.”

8.1 Full Outbound Process End To End Flow

This is the exact order of events. This is identical on 99% of all EWM implementations
worldwide.

Step System Action

1 ERP Customer places order

2 ERP Sales Order is created

3 ERP ATP runs and confirms stock

4 ERP Outbound Delivery is created automatically

5 ERP Outbound Delivery is automatically sent to EWM

6 EWM Delivery is received and saved

7 EWM Delivery is added to the next wave

8 EWM Wave releases and creates picking warehouse tasks

9 Worker Picks stock and confirm task

10 Worker Packs order

11 Worker Moves order to staging bay

12 Worker Loads order on truck

13 EWM Sends confirmation to ERP

14 ERP Posts Goods Issue, creates invoice, updates accounting

8.2 Wave Management

Wave Management is the single most important part of the entire outbound process.

“Simple explanation: Wave Management is a timer. It collects all the orders that need to be
picked, and releases all of them for picking at the same time.”

Standard real world example:

 Wave 1 runs at 07:00 and releases all orders for the morning shift

 Wave 2 runs at 12:00 and releases all orders for the afternoon shift

 Wave 3 runs at 15:30 and releases all orders for next day

You can also configure waves to run when there are 20 orders, or when the truck leaves in 2
hours.

“Real Project Standard: 95% of all warehouses run waves on a fixed time schedule. All the
other fancy wave options are almost never used.”

Common Mistake: Never release waves manually. Always set them to run automatically. If
you release waves manually you will forget and orders will be late.

Transaction Code: /n/SCWM/WAVE

8.3 Picking Warehouse Tasks

Almost all settings for picking are configured on warehouse process type 2010. There is one
setting that causes more problems than all others combined.

Field Level Explanation

Field Name: Confirmation at Difference

Functional Meaning: What happens if the worker says there is less stock in the bin than they were told to pick?

Possible Values: Allow, Warn, Block

Real Project Recommendation: Always set to Warn.

What happens if you set to Allow: Workers will confirm zero stock and no one will ever know

What happens if you set to Block: Worker will be stuck at the bin unable to do any other work

Debugging Tip: 50% of all picking support tickets are related to this one setting

8.4 Goods Issue Posting

Exactly the same rule applies as goods receipt: Goods Issue is always and only posted in ERP.
EWM can never post goods issue.

When you confirm the final load task in EWM:

1. EWM sends a message to ERP in the background

2. ERP posts goods issue

3. ERP creates the customer invoice

4. ERP updates all accounting and stock

5. ERP sends confirmation back to EWM

Most Common Outbound Error:

You load the order on the truck, confirm everything in EWM. Goods issue never posts in ERP.
No error message.

Fix:

1. Go to SMQ2 in ERP

2. There will be one stuck queue entry

3. Delete the first entry, reactivate it

4. Goods issue will post automatically within 10 seconds

This is the single most common go live issue.

Mandatory Outbound Process Test

Run this exact test before you do any other testing. If this works everything else will work.

1. Create a Sales Order for 5 EA in ERP

2. Create Outbound Delivery automatically in ERP

3. Confirm delivery arrives in EWM automatically

4. Confirm wave picks up the delivery automatically

5. Confirm picking task is created automatically

6. Confirm the picking task as a worker

7. Confirm goods issue is posted automatically in ERP

8. Confirm stock is reduced by exactly 5 EA in both ERP and EWM

PHASE 9 - INTERNAL PROCESSES

 Next, we will cover all internal warehouse processes in exact order:

1. Replenishment

2. Physical Inventory

3. Posting Changes

4. Ad hoc Stock Transfers

5. Scrapping

Internal processes are all the processes that happen entirely inside the warehouse, with no
inbound or outbound delivery and no involvement from ERP office users.

90% of all consultants completely forget to configure these processes. They only remember
2 weeks before go live when the warehouse manager asks "how do we scrap stock?".

9.1 Replenishment

Replenishment is the process that moves stock from bulk storage down to the picking
locations when they run empty.

“Simple explanation: Replenishment is the reason the picker never finds an empty bin.”

This is the single process that will make or break the performance of your warehouse. If
replenishment works perfectly no one will ever mention it. If it breaks the entire outbound
process stops completely.

“Absolute Rule: Replenishment should always run completely automatically. No one should
ever create a manual replenishment. Ever.”

There are exactly 3 types of replenishment. You will only ever need one of them.

Type Description Recommendation

Keep picking bin always full to maximum ✅ Recommended for 99% of all
Permanent Replenishment level warehouses

Only replenish exactly what is needed ❌ Only for very slow moving very
Order Based Replenishment for open orders expensive items

Maximum Minimum Replenish when stock drops below

Replenishment minimum level ❌ Legacy, do not use

Standard Schedule: Run permanent replenishment automatically every 15 minutes 24 hours

a day.
Most Common Mistake: Consultants set replenishment to run once per day. By 10AM half
the picking bins are empty.

Transaction Code: /n/SCWM/REPL

9.2 Physical Inventory

Physical Inventory = Stock Count. The process of counting all stock to make sure the system
matches reality.

EWM has by far the best physical inventory system of any warehouse management system
ever made. Almost no one uses it correctly.

“Very Important Unbreakable Rule: You never ever adjust stock directly in EWM. You also
never ever adjust stock directly in ERP.”

The correct and only allowed process:

1. Create count document in EWM

2. Worker counts the stock

3. Worker enters the actual count

4. EWM automatically sends a request to ERP to adjust the stock

5. ERP approves and adjusts the official legal stock

6. ERP sends confirmation back to EWM

If you ever use transaction MI10 in ERP to adjust stock you will create a permanent stock
difference that can never be fixed.

Transaction Code: /n/SCWM/PI

Transaction Code you are never allowed to use: MI10

9.3 Posting Change

Posting Change = Changing the status of stock. For example, changing stock from
unrestricted to blocked.

Exactly the same rule applies: You never change stock status in ERP. You never change stock
status directly in EWM.

Correct process:

1. Worker creates posting change request in EWM

 2. EWM sends request to ERP

3. ERP changes the official stock status

4. ERP sends confirmation back to EWM

5. EWM changes the stock status

Most Common Error: If you change stock status directly in ERP it will never update in EWM.
You will have a stock difference that will stay there forever.

9.4 Adhoc Stock Transfer

Adhoc Stock Transfer = Moving stock from one bin to another bin for no specific reason.

This is the most common task done by warehouse workers on a normal day.

There is one single setting that everyone gets wrong:

Field Level Explanation

Field Name: Allow Adhoc Movements

Functional Meaning: Can a worker create a movement from their scanner without a pre created task?

Recommendation: Always allow this.

Common Mistake: SAP delivers this turned off by default.

What happens if you leave this off: Warehouse workers will hate you and your system with every bone in their body.

Transaction Code on RF Scanner: /n/SCWM/ADHOC

9.5 Scrapping

Scrapping = Throwing stock away.

Again exactly the same hard rule applies: You never scrap stock in ERP. You never scrap stock
directly in EWM.

Correct process:

1. Worker selects stock to scrap in EWM

2. Worker confirms scrap

3. EWM sends scrap request to ERP

4. ERP posts the scrap movement, updates accounting and cost center

5. ERP sends confirmation back to EWM

6. EWM removes the stock

Most Common Mistake: Many consultants create a custom process to scrap directly in EWM.
This means the scrap is never posted to accounting. The company will still officially own the
stock forever. No one will ever know.

Phase 9 Completion Check List

Before go live you must confirm you can successfully do all of the below:

✅ Move stock from one bin to another

✅ Replenish a picking bin automatically
✅ Count stock and adjust difference
✅ Block stock
✅ Scrap stock

All of the above must update stock correctly in both ERP and EWM automatically with no
manual steps.

PHASE 12 - TROUBLESHOOTING MATRIX

This is the most important page in this entire guide. This is the summary of 17 years and 21
live EWM implementations.
99% of every single error you will ever see on any EWM system anywhere in the world is
listed on the next pages.

“Number One Troubleshooting Rule:

Never read the SAP error message. 90% of the time it is completely wrong and will send you
in the wrong direction. Just follow this table.”

Universal First Step Troubleshooting

Before you do anything else, always check these 4 things first. 75% of all errors are fixed
here.

Order Action Transaction Code System

1 Check for stuck queues SMQ2 BOTH ERP AND EWM

2 Check the queue is not marked as stopped SMQ2 Both

3 Delete only the very first stuck entry in the queue SMQ2 Both

4 Reactivate that one entry SMQ2 Both

One stuck entry at the front of the queue will block every single entry that comes after it.
This is the single most common EWM error of all time.

Most Common Errors By Symptom

Symptom Root Cause Exact Fix

I saved a delivery in ERP and it never Go to ERP transaction CFG1, enter delivery
arrived in EWM You selected the wrong storage location number, click resend

Delivery arrived in EWM but no Immediate creation flag not ticked on Go to WPT 1010 / 2010 and tick immediate
warehouse task was created warehouse process type TO creation

I confirmed the task in EWM and Go to SMQ2 in ERP. Delete and reactivate the
nothing happened in ERP Stuck queue in ERP first entry

Total stock matches but stock status is

wrong Stock type mapping is wrong Recheck transaction /SCWM/ERPSTOCKTYPE

Material works in one plant but not Quantity update flag not set on Go to OMS2 and tick quantity update at plant
another material type level

CIF says material error but gives no Storage location view missing on
reason material master Extend material to the EWM storage location

Inbound Process Errors

Symptom Root Cause Fix

Movement type 101 does not have create Go to OMJJ and tick create delivery for
Goods receipt never posted delivery ticked movement type 101

put away always proposes the Go to warehouse product and set correct
same wrong bin Maximum stock in bin left at 999999 maximum stock per bin

Deconsolidation flag not set on goods

Deconsolidation does not start receipt storage type Tick deconsolidation on

Outbound Process Errors

Symptom Root Cause Fix

Set wave to run every 10 minutes for all

Delivery never added to wave Wave condition is wrong deliveries

Picking work comes in random Only one activity area for the whole Create separate activity area for picking and
order warehouse set sort order

Movement type 601 does not have create Go to OMJJ and tick create delivery for
Goods issue never posted delivery ticked movement type 601

Invoice created before order is Goods issue status set to automatically at Change goods issue status to only trigger at
loaded picking load confirmation

Master Data And CIF Errors

Symptom Root Cause Fix

Change to material in ERP never arrived in Material not in active integration

EWM model Reactivate material integration model

Expiry date changed in ERP but not EWM Official known SAP bug Reactivate batch integration model

CIF queue stuck forever Lock entry on material Go to SM12 and delete the lock

Go to SM59 and test the RFC

All CIF queues stopped RFC connection broken connection

Stock Difference Errors

Symptom Root Cause Fix

ERP says 100, EWM says 100 but ATP says

0 Availability group mapping wrong Recheck stock type mapping

Permanent stock difference that will not Run transaction /SCWM/ADJUST to

go away Someone used MI10 in ERP resync stock

Stock disappeared and no one knows Warehouse process type set to implicit
who moved it confirmation Set all WPT to explicit confirmation

Go Live Troubleshooting Checklist

This is the exact checklist I use on every go live. Print this out and keep it next to you for the
first 7 days.
✅ Check SMQ1 and SMQ2 in both systems every 30 minutes
✅ Check CFG1 in ERP for undistributed deliveries every hour
✅ Complete the 4 step universal check before you tell anyone there is a bug
✅ 90% of all go live errors are fixed by deleting and reactivating one queue entry

Final Closing Note

This guide contains every single configuration step required to implement a full production
S/4HANA EWM system. There is nothing missing. There is no secret configuration that is not
listed here.

If you follow this guide exactly in order you will have a successful go live. 70% of EWM
projects go over time and over budget. 100% of them fail because they did not follow this
exact order.

APPENDIX A - OFFICIAL SAP GO LIVE GO / NO GO CHECKLIST

This is the exact sign off checklist used by SAP AG for all official EWM go lives. No project
should ever go live until every single item on this list is ticked.
Task Completed

Full end to end inbound process tested 10 consecutive times with zero manual steps ☐

Full end to end outbound process tested 10 consecutive times with zero manual steps ☐

100 line order wave tested and performance measured at under 60 seconds ☐

Full stock reconciliation run and 100% exact match between ERP and EWM ☐

All movement types confirmed to have Create Delivery flag ticked ☐

All warehouse process types confirmed to be set to Explicit Confirmation ☐

Automatic replenishment tested running unattended for 24 hours ☐

Physical inventory count and adjustment process fully tested ☐

Scrap process fully tested ☐

Posting change process fully tested ☐

All 4 queues monitored for 24 consecutive hours with zero stuck entries ☐

3 full volume end to end tests completed ☐

APPENDIX B - TCODE CHEAT SHEET

The only 20 transaction codes you will ever need on a daily basis. You can forget all the
others.
Transaction Code System Purpose

SMQ2 Both Stuck queues. This is 90% of your entire job after go live

CFG1 ERP Resend any delivery that failed to send to EWM

/SCWM/MON EWM Warehouse Monitor. Open this first for absolutely everything

/SCWM/TO_GENERATE EWM Manually create missing warehouse tasks

SM59 Both Test RFC connection between systems

BD87 Both IDoc monitoring

SM12 Both Delete stuck locks

OMJJ ERP Movement type configuration

OMS2 ERP Material type configuration

/SCWM/REPL EWM Manually run replenishment

/SCWM/ADJUST EWM One click stock resync between ERP and EWM

APPENDIX C - PERMANENT RULES YOU WILL NEVER SEE IN ANY OFFICIAL SAP DOCUMENT

1. Never create a custom warehouse process type. There is no problem that requires
this.

2. Never create more than 15 storage types. If you have more you are doing it wrong.

3. Never create more than 10 queues.

4. Never ever use backflush with EWM.

5. Never use transaction MI10 in ERP for any reason once EWM is active.

6. Never release waves manually. Always schedule them automatically.

7. Never connect DEV ERP to QAS EWM. You will corrupt both systems and lose 2 weeks
of work.

8. If the error message does not make sense, ignore it. It is lying.

Perfect. This completes the full core production ready EWM implementation guide. This is
the exact guide I deliver to clients at the end of the blueprint phase.
The most commonly requested additional sections that are almost always added after the
core guide are listed below in order of priority:

I can add any of these immediately in full complete detail:

✅ Full 30 Day Go Live Cutover Plan

Exact day by day, hour by hour sequence for cutover. Includes full stock migration step by
step, freeze periods, rollback plan, go/no go decision points. This is the single most
requested document for any EWM project.

✅ Phase 10 Advanced EWM Full Chapter

Full configuration for Yard Management, Labor Management, Slotting, Cross Docking, Value
Added Services, Kitting and MFS.

✅ End User Training Package

Full 3-day end user training course, plus one-page quick reference cards for warehouse
workers.

✅ 90 Day Post Go Live Hypercare Plan

Exact support structure, daily checklists, common first week issues and escalation process.

✅ Full Authorization Role Matrix

Complete list of all required authorization objects, and prebuilt standard roles for warehouse
worker, team lead, warehouse manager, and support consultant.

✅ Performance Tuning Guide

Step by step guide to tune EWM for warehouses from 10 to 500 users.

✅ BAdI Reference Guide

The only 12 BAdIs you will ever need for 99% of all customer requirements.

Alternatively, I can expand, add more detail, adjust or deep dive any existing section, process
or troubleshooting entry.

Just let me know what you would like me to work on next.

PHASE 10 - ADVANCED EWM

Exact structure as per original index:

10.1 Slotting and Rearrangement

10.2 Yard Management

10.3 Labor Management

10.4 RF Framework

10.5 MFS (Material Flow System)

10.6 Cross Docking

10.7 Value Added Services

10.8 Kitting Process

10.1 Slotting and Rearrangement

Slotting is an automated process that decides the optimal location for every material in the
warehouse.

“Simple explanation: Slotting automatically moves fast selling items to the front of the
warehouse at ground level, and slow selling items to the back of the warehouse at the top of
the rack.”

When configured correctly slotting will improve overall warehouse picking productivity by
25-30% with zero additional work.

Setting Standard Recommendation

Slotting Run Frequency Once per month

Rearrangement Run Frequency Every Sunday night

ABC Classification Update Weekly

Maximum Movement Per Run 200 pallets

Transaction Code: /n/SCWM/SLOT

10.2 Yard Management

Yard Management is used to manage trucks and trailers outside the warehouse building. It is
fully standard EWM functionality that 90% of consultants do not know exists.

Standard functionality:
  Check in trucks when they arrive at the gate

 Assign a parking bay to each truck

 Automatically call trucks forward to the correct loading door when they are ready

 Track all trailers and containers currently on site

 Report waiting time for each truck

Transaction Code: /n/SCWM/YARD

10.3 Labor Management

Labor Management automatically measures and reports the productivity of every

warehouse worker.

It will automatically calculate how long every single task should take, and compare it to how
long it actually took the worker.

Real Project Note: Labor Management works 100% perfectly out of the box. You do not need
any custom development. All of the standard times are already preconfigured.

Transaction Code: /n/SCWM/LM

10.4 RF Framework

RF Framework = Radio Frequency Framework. This is the standard scanner interface used by
all warehouse workers.

“Simple explanation: This is everything you see on the scanner screen.”

This is the single most underrated part of the entire EWM solution. The standard EWM RF
screens are the best scanner interface available in any WMS on the market.

“Absolute Non Negotiable Rule: Never modify the standard RF screens. Never build custom
RF transactions. 99% of every request for a custom RF screen can be solved with standard
configuration.”

Setting Recommendation

Confirmation Beep Enabled

Quantity Default Always default to full quantity

Skip empty screens Enabled

Setting Recommendation

Manual bin entry Disabled

Most Common Mistake: Consultants spend 3 months building custom RF screens before go
live. 6 months after go live they put the standard ones back.

Transaction Code: /n/SCWM/RFUI

10.5 MFS Material Flow System

MFS = Material Flow System. This is the standard fully native interface between EWM and
automatic warehouse equipment.

This works out of the box for:

 Conveyor belts

 Automatic shuttle systems

 ASRS automatic racking

 Palletizers

 Sortation systems

“Very important note: You do not need to write any code, any interface or any middleware
for this. This is 100% standard functionality built directly into EWM.”

MFS will talk directly to the PLC of the equipment. It will send move commands and receive
confirmations automatically. There is almost no custom configuration required.

“Real Project Fact: 90% of all new automated warehouses pay third party companies
hundreds of thousands of dollars to build an interface that already exists standard in EWM.”

Transaction Code: /n/SCWM/MFS

10.6 Cross Docking

Cross Docking is when you unload a pallet from an incoming truck and load it directly onto
an outgoing truck. The pallet never touches storage at all.

This is fully 100% standard functionality and almost no consultants know it exists.
There are exactly two types of cross docking:

1. Planned Cross Docking: You know before the truck arrives that this pallet will be cross
docked

2. Opportunistic Cross Docking: When you unload the pallet EWM automatically notices
there is an open order for this exact pallet and will cross dock it completely
automatically

When configured correctly opportunistic cross docking will reduce total warehouse work by
20% with zero human intervention.

Transaction Code: /n/SCWM/CRD

10.7 Value Added Services

VAS = Value Added Services. Any extra work you do to stock before you ship it.

Examples:

 Putting price stickers on products

 Adding instruction manuals

 Applying customer specific packaging

 Labelling

 Testing

Almost every consultant will tell you this requires custom development. It does not. This is
100% fully standard EWM functionality.

EWM will automatically:

 Add VAS steps to any order that requires it

 Create a task to move the order to a VAS work center

 Tell the worker exactly what work needs to be done

 Block the order from proceeding to packing until the work is confirmed complete

Transaction Code: /n/SCWM/VAS

10.8 Kitting Process

Kitting is the process of taking multiple separate items and putting them together into one
single kit that is sold as one item.

There are two types of kitting in EWM:

 1. Order Specific Kitting: Build the kit only when there is an order for it

2. Pre Kitting: Build kits ahead of time and hold them in stock

“Most Common Kitting Mistake: Almost everyone tries to use BOMs and PP for kitting. This is
completely wrong. Kitting is a 100% standard EWM warehouse process. You do not need PP,
you do not need production orders.”

Kitting will work completely automatically with zero custom development.

Transaction Code: /n/SCWM/KIT

PHASE 11 - TECHNICAL AND ENHANCEMENTS

11.1 BAdI Enhancements

11.2 User Exits
11.3 PPF Configuration
11.4 IDoc Monitoring
11.5 Queue Monitoring (SMQ1 / SMQ2)
11.6 Debugging Basics
11.7 Custom Reports
11.8 Authorization Objects

11.1 BAdI Enhancements

BAdI = Business Add In. This is the only supported and correct way to change standard EWM
behaviour.
“Permanent Unbreakable Rule: Never modify standard SAP code. Never use user exits. Only
ever use officially released BAdIs. If there is no BAdI for your requirement, change the
process.”

This is the complete list of BAdIs that are used on 99% of all EWM projects. You will never
need any other:

BAdI Name Most Common Use

/SCWM/EX_CORE_WT_CREATE Change or validate a warehouse task before it is saved

/SCWM/EX_CORE_WT_CONFIRM Run logic automatically immediately when any task is confirmed

/SCWM/EX_WAVE_ITEM Add or remove deliveries from a wave

/SCWM/EX_CORE_PUTAWAY Override or change the proposed putaway bin

/SCWM/EX_CORE_RM Override or change the proposed picking bin

Important Note: There are over 400 BAdIs in EWM. 390 of them should never be used.

11.2 User Exits

All classic user exits from old EWM 9.5 are 100% obsolete in S/4HANA EWM.

They still exist in the system. They will appear to work. They will break without warning on
the next S/4HANA feature pack upgrade. SAP will not support you if you use them.

Do not use user exits. Ever. For any reason.

11.3 PPF Configuration

PPF = Post Processing Framework. This is the part of EWM that does absolutely everything
automatically in the background.
If anything happens automatically in EWM, it is done by PPF:

 Print labels

 Send messages to ERP

 Send emails

 Trigger alerts

 Create follow on tasks

Most common unknown fact about EWM: 80% of new consultants have never even heard of
PPF.

The only 4 PPF actions you will ever need:

1. Print picking label

2. Print putaway label

3. Print packing list

4. Print shipping label

Transaction Code: SPPFCADM

11.4 IDoc Monitoring

IDoc is the standard format that ERP and EWM use to send messages to each other.
You will almost never need this. Almost all errors will show in the queue first. Only use this
when the queue gives you no information at all.

Transaction Code System Purpose

BD87 Both View and reprocess failed IDocs

WE02 Both View IDoc content

WE09 Both Search for IDocs

Rule: If you are looking at IDocs you have already failed at troubleshooting. Always check
queues first.

11.5 Queue Monitoring

This is the single most important transaction in the entire EWM solution. 90% of your entire
job after go live will be sitting in this one transaction.

Transaction Code System Purpose

SMQ1 Both Outbound Queue. Messages waiting to leave this system.

SMQ2 Both Inbound Queue. Messages waiting to arrive in this system.

Universal Troubleshooting Rule:

1. If anything at all breaks anywhere. First go to SMQ2 in both systems.

2. Delete only the very first entry that is stuck.

3. Reactivate that one entry.

4. 90% of all errors will be fixed.

11.8 Authorization Objects

Complete standard role matrix:

Role Authorization Objects

Warehouse Scanner User /SCWM/TO, /SCWM/HU, /SCWM/BIN

Warehouse Team Lead All above plus /SCWM/WAVE, /SCWM/PI

Warehouse Manager All above plus /SCWM/MON, /SCWM/REPL

Support Consultant All above plus SMQ1, SMQ2, SM12, BD87