SAP EWM Consultant Topics Checklist

(Fundamental → Advanced)
Below is a structured list of key SAP Extended Warehouse Management (EWM) topics for a functional
consultant. Topics are ordered from fundamentals to advanced, with Priority (High/Med/Low),
Dependencies, and Integration flags (MM, SD, QM, TM, etc.) indicated. Differences between S/4HANA
(Embedded) and ECC (Decentralized) EWM are noted where relevant. This checklist can guide learning and
ensure coverage of all critical areas for an EWM role.

EWM Overview & Architecture

• EWM Fundamentals & Benefits (High; Deps: none; Intg: –): EWM is an advanced warehouse
management solution that “enhances and extends” traditional WM by providing advanced
inventory management, order fulfillment and resource optimization 1 . It offers real-time
visibility, supports high-volume processes, and improves transparency and efficiency in
warehousing. (Basic understanding of standard WM concepts is assumed.)
• SAP WM vs EWM (High; Deps: none; Intg: –): Unlike classic SAP WM, EWM supports complex, high-
throughput operations. EWM adds native features such as labor management, slotting/
rearrangement, warehouse monitoring, and advanced integration (e.g. with TM/GTT) that
standard WM lacks 2 3 . (EWM is generally preferred for large/automated warehouses, whereas
WM served smaller operations.)
• Deployment Models: Embedded vs Decentralized (High; Deps: EWM Fundamentals; Intg: –):
Understand Embedded EWM (part of S/4HANA) vs Decentralized EWM (on a separate SCM/ECC
system). Embedded EWM (SAP S/4HANA 1610+) includes a “Basic” version (supplanting old WM) and
an optional “Advanced” add-on (wave management, kitting, slotting, labor mgmt., etc.) 4 .
Decentralized EWM runs on a separate SAP SCM/ECC server and communicates via RFC/CIF 5 . Key
differences: Embedded EWM shares the S/4 database (no replication of master data) and simplifies
integration (e.g. no “Expected GR” document) 6 , whereas Decentralized EWM supports multiple
ERP links and offers independent availability (helpful for 24×7, high-volume sites) 7 8 .
(Knowledge of both models is essential; focus on the model used by your client.)
• Data Model (Warehouse Tasks & Quants) (High; Deps: Org Structure; Intg: –): In EWM, stock is
managed as quants (quantities at specific bins) and Warehouse Tasks (WTs) trigger movements. A
warehouse number contains storage types/sections/bins with quants that represent actual inventory
9 . Unlike WM’s Transfer Orders, EWM creates WTs for all internal moves (putaway, picking,

replenishment). All operations (put-away, stock removal) occur within a warehouse number 10 .
(Prerequisite for learning processes: understand that EWM tracks stock by quantity per bin, and how
WTs drive movements.)
• Integration Architecture (Med; Deps: Deployment Models; Intg: MM, SD, QM, TM): Understand
how EWM links with ERP. In Decentralized EWM, master and transaction data replicate via CIF/ALE
(IDocs) to EWM. (For example, purchase orders/stock transfers in ECC generate EWM inbound
deliveries via CIF.) In Embedded EWM, data is shared natively (no replication); this eliminates artifacts
like the “Expected GR” document 11 . Know the basic CIF setup and RFC communication (for

1
 decentral) and the S/4 integration (for embed). This is needed before tackling process flows and
interface customizing.

Organizational Structure & Master Data

• Warehouse Number (High; Deps: none; Intg: –): The top-level EWM org unit. A warehouse number
maps to a physical warehouse complex 10 . All storage types, sections and bins belong to a
warehouse number. (A warehouse number has no address; it groups all lower-level structures 12 .)
Priority: High (foundation for every process).
• Storage Types / Sections / Bins (High; Deps: Warehouse Number; Intg: –): Define the layout of the
warehouse. A Storage Type (e.g. High-Rack, Bulk, Picking area) is a physical zone within a warehouse
13 . Each storage type can be subdivided into Storage Sections, which further contain Storage

Bins. These control how materials are put away and picked. (E.g. bulk vs fixed-bin, high-rack vs floor
storage.) Priority: High (basis for all putaway/retrieval).
• Storage Control (Open vs Actual Bins) (High; Deps: Storage Types/Bins; Intg: –): Learn the concept
of bin management. Bins can be opened (stock is calculated) or closed (bin doesn’t track stock; an
order must open it first). Storage control settings (inbound/outbound control) determine whether a
storage type is “open” or “actual.” (Prereq: Storage types/bins.)
• Putaway & Removal Strategies (High; Deps: Storage Types/Bins; Intg: –): Configuration of where
and how to put away or pick stock. Putaway strategies (e.g. next empty bin, fixed bin, weight-based)
and removal strategies (e.g. FIFO, LIFO, NEU) are defined per storage type. These depend on having
a correct structure in place. Priority: High (drives automatic bin determination).
• Packaging and Handling Units (HU) (High; Deps: Warehouse Number; Intg: –): Understand HU
management. HU Types define packaging structures (pallets, cartons) and packaging
specifications define how materials are packed into HUs. EWM uses HUs extensively for putaway,
picking, shipping and inventory. Configuring HU types, pack specifications, pack proposals and split
criteria is critical. (Cite: EWM “enables management of handling units” for shipping/receiving 14 .)
• Material Master (EWM-specific fields) (Med; Deps: –; Intg: MM): Know key EWM-relevant material
master settings (base UoM, weight/volume for capacity checks, stock placement indicators, etc.). In
Embedded EWM, the S/4 material master carries these fields; in Decentralized EWM, material data is
replicated via CIF. Integration: SAP MM (materials/procurement).
• Business Partner / Vendors / Customers (Med; Deps: –; Intg: MM, SD): EWM uses SAP Business
Partners for vendors/customers (in S/4HANA) or vendors/customers (in ECC). Embedded EWM
shares BP data with S/4 (no replication) 6 , whereas decentralized EWM requires master data
replication. Integration: SAP MM (vendors), SD (customers).
• Work Centers & Resources (Med; Deps: Org Structure; Intg: –): Define resources (forklift, worker,
etc.) and work centers in EWM master data. These are used in labor management and task
execution. (EWM’s Labor Management uses work centers to calculate performance 15 .) Priority:
Medium (critical if labor mgmt or RF scanning is used).
• Packaging Materials (Med; Deps: HU Types; Intg: –): Master data for secondary packaging (films,
shrink-wrap). Define packaging materials if EWM packing functionality is used. Priority: Medium
(project-specific).
• EWM Organizational Mapping (Plant, Storage Location) (High; Deps: Org Structure; Intg: MM, SD):
Map the EWM warehouse number to S/4 storage locations and plants. In Embedded EWM, the S/4
plant/storage location can be integrated with the EWM warehouse number (via availability groups)
16 . In Decentralized EWM, set up CIF to link EWM warehouse to ECC plant/storage location. Priority:

High (enables ERP↔EWM integration).

2
Inbound Processes
• Procurement Receipt (Purchase Order to GR) (High; Deps: Org Structure, Master Data; Intg: MM,
QM): Inbound starts when a Purchase Order is issued. In ERP (MM), an inbound delivery is created
(either manually or via MRP/STO). In Decentralized EWM, this delivery is transferred (via CIF/IDoc) to
EWM; in Embedded EWM it’s directly available. The EWM system then generates a Goods Receipt
(GR) Warehouse Task for receiving the goods. The process includes registration of arrival and
unloading. EWM “registers the arrival of the product” and confirms receipt for inbound deliveries
17 . Integration: SAP MM (PO and delivery); optionally QM (for inbound inspection). Dependencies:

Must know storage types/bins and putaway strategies.

• Putaway (Storing Goods) (High; Deps: Inbound GR, Org Structure; Intg: –): Once goods are received,
configure how they are placed into storage. EWM handles unloading and directs putaway into
determined bins. This uses the storage types, putaway strategies, and HU management. (EWM
“manages unloading and facilitates placement of goods into pre-determined storage locations” 18 .)
Priority: High.
• Quality Inspection (Inbound) (Med; Deps: Inbound Receipt; Intg: QM): If QA is active, incoming
goods can trigger inspection lots in QM. EWM can hold goods in a quality inspection area until
release. (The module “handles the quality control processes for incoming products” 19 .) Integration:
SAP QM. Dependencies: Inbound delivery setup, QM integration.
• Deconsolidation / Repackaging (Med; Deps: Inbound Receipt; Intg: –): For received pallets or
containers, EWM supports deconsolidation (splitting into smaller units) or repackaging (changing pack
configurations). E.g. breaking down a large HU into multiple HUs. This follows inbound receipt and
uses HU functions. (EWM “dividing larger shipments into individual items” describes deconsolidation
20 .) Priority: Medium (important in warehouses that use mix pallets or multi-level handling).
• Handling Unit Management (Inbound) (High; Deps: HU Master Data; Intg: –): EWM manages HUs
from the point of receipt. You learn to pack/unpack items into HUs on inbound, and maintain HU
hierarchies. This includes using pack specifications to automatically build HUs. (EWM “enables the
management of handling units” for inbound/outbound processes 14 .) Priority: High (core to most
EWM processes).
• Cross-Docking (Inbound) (Med; Deps: Inbound/Outbound Setup; Intg: SD): EWM supports cross-
docking, immediately using inbound goods for outgoing orders without putaway. Two types:
opportunistic (unplanned) or planned (warehouse tasks are auto-created for direct shipping) 21 .
Integration: SAP SD (sales/stock transfer orders). Priority: Medium (accelerates flow; project-specific if
used).
• Returns Processing (Vendor Returns) (Med; Deps: Inbound GR; Intg: MM, SD): Handling vendor
returns (reverse logistics) from EWM perspective. This often uses a WM Goods Issue via EWM.
Integration: SAP MM (credit memo processing) and SD (refund). Priority: Medium (covers complete
procure-to-pay cycle).

Outbound Processes
• Outbound Delivery & Order Fulfillment (High; Deps: Inbound Processes, Org Structure; Intg: SD,
TM): Outbound starts with an order (typically an SD Sales Order or a Delivery Order for STO). ERP
creates an outbound delivery (sales or stock transport). Decentralized EWM receives this via CIF/
IDoc; Embedded EWM uses the shared S/4 data. The EWM delivery generates Warehouse Tasks for
picking. (EWM “Outbound order processing:… receipt of outbound orders from SAP SD or other
modules” 22 .) Priority: High (key EWM process).

3
 • Stock Confirmation & Availability (High; Deps: Outbound Delivery; Intg: SD): EWM confirms stock
availability and allocates stock for the outbound order. The system checks bin stock (quants) and
creates tasks to fulfill the delivery. (This is implied in order confirmation in [27] 23 .) Priority: High.
• Picking (Various Strategies) (High; Deps: Outbound Delivery; Intg: –): Execute picking of goods
from storage. EWM supports multiple strategies (wave picking, cluster picking, zone picking, etc.) to
optimize throughput 24 . It creates tasks by strategy. (For example, wave picking batches orders;
zone picking assigns pickers to zones.) Priority: High (crucial for efficiency).
• Kitting & Value-Added Services (VAS) (Medium; Deps: Outbound Picking; Intg: –): If products need
assembly or configuration, EWM can create kits or perform VAS (e.g. repacking, labeling) before
shipping. (EWM supports “value-added services (VAS), kitting” in outbound processing 25 .) Priority:
Medium (important in manufacturing industries).
• Packing & HU Consolidation (Outbound) (High; Deps: Picking; Intg: –): After picking, items are
packed into HUs (pallets/cartons) per the packaging specifications. EWM proposes packings and
allows manual adjustments. Handling Unit management ensures items are correctly grouped 26 .
Priority: High.
• Staging & Loading (High; Deps: Packing; Intg: TM): Packed HUs/orders are moved to staging areas
for loading onto vehicles. EWM can advise on loading sequences and truck assignments 27 .
Integration: SAP TM/carrier systems for transportation planning and yard management. Priority:
High.
• Goods Issue & Shipment Execution (High; Deps: All Outbound Steps; Intg: SD, FI): Finalize the
outbound delivery with a Goods Issue (GI). Stock is removed from inventory, and an FI posting is
generated (in ERP). In Embedded EWM, this directly updates the delivery in S/4; in Decentralized, a GI
IDoc goes back to ERP. Priority: High.
• Returns Processing (Customer Returns) (Medium; Deps: Outbound Delivery; Intg: SD, QM): Process
returned goods from customers. A return delivery (inbound to warehouse) is handled similarly to
inbound, often integrated with SD returns orders. Integration: SAP SD returns flow, possibly QM for
re-inspection. Priority: Medium (completes order-to-cash loop).

Internal Warehouse Processes

• Internal Stock Transfers & Replenishment (High; Deps: Org Structure; Intg: –): Manage internal
movements (replenishments) within the warehouse. For example, automatically or manually move
stock from bulk to forward-pick areas. EWM uses Warehouse Tasks for all bin-to-bin moves. Priority:
High (keeps pick faces stocked).
• Warehouse Task (WT) Management (High; Deps: All Processes; Intg: –): Every internal movement is
executed via a Warehouse Task. Understanding how WTs are created, prioritized, and confirmed is
crucial. (Unlike WM’s TO, EWM’s WT is key.) Priority: High.
• Putaway & Removal (within Warehouse) (High; Deps: WTs; Intg: –): EWM can trigger internal
putaway or removal tasks (e.g. after picking, return putaway, or revoking wrong bin). These use the
same logic as inbound/outbound putaway. Priority: High.
• Short-Dumps & Exceptions (Med; Deps: –; Intg: –): Handling exceptional events like short-dumping
(placing goods in interim bins) or corrections. Priority: Medium.
• Scrapping & Special Stock (Med; Deps: QM, Org Structure; Intg: QM, FI): Manage scrap in
warehouse (write-offs) and special stock types. EWM can handle scrap directly at bin level. Priority:
Medium (project-specific).

4
 • Lot & Serial Number Handling (Medium; Deps: Master Data; Intg: MM, SD, QM): EWM fully supports
batch/lot and serial tracking. Learn how EWM manages batches/serials during all movements
(inbound, storage, picking, outbound). Priority: Medium (if your scenario uses batches/serials).
• Deconsolidation (Internal) (Med; Deps: –; Intg: –): Splitting HUs at storage, if needed. Priority:
Medium. (Often done as part of inbound or internal process.)

Physical Inventory Processes

• Inventory Count Procedures (High; Deps: Org Structure; Intg: FI): EWM supports cycle counting and
full physical inventory. Staff count quantities in selected bins and record counts in EWM. The system
“counts and verifies the actual stock level” 28 . Priority: High (ensures inventory accuracy).
• Count & Control (Med; Deps: Inventory Counts; Intg: –): Use EWM’s Count and Control process to
handle discrepancies. Bins are classified (A/B/C) and counted at different intervals. If counts differ,
EWM provides reports for recount/adjustment. Priority: Medium.
• Adjustments & Reconciliation (Med; Deps: Inventory Counts; Intg: FI): Differences between
counted and system stock generate adjustment postings. Learn how to process invent differences
and post FI documents for them. Priority: Medium.
• Continuous vs Periodic Inventory (Med; Deps: Inventory Counts; Intg: –): Understand options:
continuous counting (rotating counts) vs scheduled (annual/periodic) counts. Priority: Medium.

Advanced Functions
• Slotting & Rearrangement (Med; Deps: Org Structure, Inventory History; Intg: –): EWM’s slotting
automatically suggests optimal bin assignments based on demand patterns, handling units, etc. It
“optimizes material storage based on demand patterns” 29 , reducing travel time. Priority: Medium
(valuable in complex warehouses).
• Value-Added Services (VAS) (Med; Deps: Inbound/Outbound; Intg: –): Configure VAS in EWM to
perform value-add tasks (e.g. kitting, labeling, inspections) on receipt or prior to shipment. (EWM
supports “value-added services (VAS)” in advanced inbound/outbound 25 .) Priority: Medium.
• Kitting & De-Kitting (Med; Deps: Outbound Picking; Intg: –): EWM can build kits of components to
fulfill an order (outbound kitting) or break kits into components. Priority: Medium.
• Cross-Docking (Advanced) (Med; Deps: Inbound & Outbound; Intg: –): Beyond basic cross-docking,
EWM supports planned (e.g. inbound for a specific sales order) or opportunistic cross-docking.
Priority: Medium.
• Wave Management (Medium; Deps: Outbound Process; Intg: –): Group warehouse tasks into waves
for scheduling (e.g. specific work shifts or delivery dates). Used in Advanced Embedded EWM.
Priority: Medium (improves throughput).
• Labor Management (Med; Deps: Work Centers; Intg: –): EWM Labor Management tracks workforce
productivity (planned vs actual hours, quotas). It uses resources/work centers and task information
to calculate efficiency 15 . Priority: Medium (growing expectation in large warehouses).
• Material Flow System (MFS) (Medium; Deps: Hardware Setup; Intg: –): For automated warehouses
with conveyors/ASRS, EWM’s MFS connects to PLCs. Learn the concept (EWM creates tasks which can
trigger MFS to move goods). EWM’s advanced tasks mgmt and MFS are linked 30 . Priority: Medium
(in automation projects).
• Yard Management (Low; Deps: TM Integration; Intg: TM): Advanced Warehouse (and SAP TM)
integration for tracking vehicles in the yard (gate-in/gate-out, dock assignment). Priority: Low-Med (if
yard mgmt is in scope).

5
 • Monitoring & Analytics (Low; Deps: –; Intg: –): EWM offers tools like the Warehouse Monitor and
Warehouse Cockpit, plus SAP HANA/BI reports for KPIs. (These “warehouse monitoring and
analytics tools” provide real-time visibility 31 .) Priority: Low (nice-to-have).
• Extended Integration (Low; Deps: –; Intg: TM, GTT, eWM Mobile): EWM integrates with SAP TM
(transport planning), GTT (track & trace), and SAP Fiori/Business Technology Platform. Basic
awareness of these integrations is useful 32 . Priority: Low (awareness only).

Configuration / Implementation Tasks

(Throughout learning, understand how to configure the above topics in IMG / SPRO.)
- Basic Settings (High): Create Warehouse Number(s) and assign to S/4 plant/storage loc. Define Storage
Types, Sections, Bins 33 . Set up Storage Control and Activity Areas (for grouping bins and tasks).
- Process Configuration (High): Define Process Types and Movement Types for inbound/outbound/internal
flows. Map ERP movement types (e.g. 101 goods receipt) to EWM process types. Configure Putaway/
Removal Strategies per storage type. Define Storage Type Search Sequences (e.g. for putaway).
- Document Types & Master Data (High): Assign EWM document types for Inbound Deliveries, Outbound
Deliveries, HUs, etc. Configure HU types, pack specs, and packaging material masters. Set up resource/work
center master records.
- Integration Settings (High): For Decentralized EWM, configure CIF/Middleware (define transfer rules for
material, BP, inventory). For Embedded EWM, activate the EWM scope item and assign process steps to
warehouse process (via availability group mapping) 16 . Configure ERP<->EWM link (GW quality usage
decision, GI interfaces).
- Warehouse Management Process (WMP) (High): Activate/deactivate advanced processes (e.g. cross-
docking, blocking, replenishment) via customizing. Define storage type search sequences, slotting
heuristics, wave settings if needed.
- RF / UI Configuration (Med): (If using RF) Set up RF menus and hard keys. (If using Fiori) Enable Fiori apps
for EWM tasks. Priority: Medium (dependent on tech stack).
- Master Data Load/Migrations (High): Plan migration of key masters (pack spec, HU types, resources). Use
LSMW/ETL for large data.
- Testing & Validation (High): Prepare test scenarios for each process; test inbound, internal, outbound
flows end-to-end. Document results.
- Cutover Activities (High): Understand cutover steps (e.g. lock WM postings, migrate stock to EWM via
stock transfer, open final tasks, complete PI). Create conversion documents (WM->EWM where applicable).

Integration with Other Modules

• Materials Management (MM) (High): EWM inbound is tightly integrated with MM. Purchase orders
and stock transport orders in ERP trigger EWM inbound deliveries 34 . Goods Receipt in EWM posts
GR in ERP (stock is updated in MM). Stock movements (e.g. transfers, reservations) flow between
modules. Key: Grasp the PO→Delivery→EWM process.
• Sales & Distribution (SD) (High): SAP SD (Order-to-Cash) integrates for outbound processes. Sales
orders generate ERP deliveries which create EWM outbound tasks 22 . EWM confirms picking/
packing and posts Goods Issue back to SD (updating billing status). Understand the integration of
delivery document types and status flows.
• Quality Management (QM) (Medium): QM integrates mainly at goods receipt and final inspection.
EWM can hand off received goods to QM for inspection, and hold stock based on inspection results.
Likewise, returns may trigger inspection lots. (EWM “handles the quality control processes for

6
 incoming products” 19 .) Key: Know how inspection lots are triggered and usage decisions are
processed.
• Transportation Management (TM) (Medium): SAP TM (or Logistics Execution Yard) can schedule
and optimize outbound shipments coming from EWM. Yard Management (part of TM) often goes
hand-in-hand with EWM docking. (EWM “integrated with carriers and shipping services” 27 .) Key:
Learn how to hand over delivery details to TM.
• Logistics Execution (LE-WM) (Low): In S/4HANA Embedded EWM, traditional LE-WM is replaced. For
ECC/Decentralized, EWM replaces LE-WM in processes. Understand how legacy WM inventory can be
converted to EWM. Priority: Low (historical awareness).
• Production Planning (PP) / Manufacturing (Low): EWM can stage components for production
(Stock to Production). Also, EWM can capture produced finished goods (Production-inbound).
Integration: SAP PP (production orders). Priority: Low (if implementing with MII/PP).
• Finance (FI/CO) (Low): Inventory postings in EWM ultimately affect FI via integration with MM/SD.
Understand basic FI impact (goods movements, FI documents) but no specialized EWM finance
config. Priority: Low (conceptual).

Technical Enhancements (Basic)

• BAdIs and User-Exits (Low): Familiarize with key enhancement spots in EWM for custom logic (e.g. /
SCWM/EX_RANGESPUT for putaway rules). Priority: Low (functional consultants should know basics,
rely on developers for details).
• CIF / IDoc Interfaces (Low): In Decentralized EWM, know the basic flows of relevant IDocs (e.g. /
SCWM/CRTO for creation of outbound delivery, /SCWM/ASCM for stock transfers). Priority: Low
(understand concept).
• Fiori and RF UI (Low): Learn the standard Fiori apps for EWM (warehouse monitor, inbound/
outbound tasks) and classic RF menu names (e.g. /SCWM/PRDI for picking). Priority: Low (overview
only).
• SAP UI & Reporting (Low): EWM provides the Warehouse Monitor, Cockpit, and standard SAP GUI
transactions (e.g. /SCWM/WMTO, /SCWM/MON). Know how to navigate basic screens. Priority: Low.

Project Documentation and Cutover

• Blueprinting & Fit/Gap (High): Document business requirements vs standard EWM. Prepare process
flows and determine needed customizations. Priority: High (foundation of any project).
• Data Migration (High): Migrate all necessary master data (bin structure, pack specs, opening stock if
converting from WM). Plan archival of old WM data or its conversion (SAP provides tools for
WM→EWM stock transfer). Priority: High.
• System Configuration Documentation (High): Keep detailed documentation of all IMG/customizing
steps. Generate SAP solution documentation (SCN, Jira tickets, etc.). Priority: High.
• Testing and Training (High): Prepare unit/integration test scripts covering all processes. Plan end-
user training on new EWM transactions and mobile apps. Priority: High.
• Cutover and Go-Live (High): Steps include final stock count, lock legacy WM transactions, perform
stock transfer to EWM, activate EWM processes, and validate opening stock. Post-go-live support
(hypercare) planning. Priority: High.

Sources: SAP documentation and expert guides for EWM processes 35 22 28 25 36 10 6 provide
details on many of the above concepts and integrations.

7
 1 14 17 18 19 20 21 22 23 24 26 27 28 34 35 Overview of the SAP Extended Warehouse
Management (EWM) module
[Link]

2 3 15 25 29 30 31 32 36 SAP S/4 HANA Warehouse Management / EWM / WMS Module Overview

[Link]

4 5 6 7 8 11 SAP EWM Decentralized vs Embedded | Pillir

[Link]

9 10 12 13 33 EWM Warehouse Organization Structure Q&A

[Link]

16 SAP Best Practices for Embedded EWM

[Link]