― Extended Warehouse Management ―
Embedded / Decentralized / Inbound-Outbound & RF / MFS Automation / Labor, Wave & Yard Management
July 2026
This paper provides a systematic overview of SAP EWM (Extended Warehouse Management), SAP’s strategic warehouse management solution, covering deployment options, organizational structure, functionality, automation integration, and key migration considerations. It is intended primarily for enterprises considering migration from the legacy WM (LE-WM) and for manufacturing/logistics practitioners pursuing advanced warehouse automation.
Chapter 1 What Is SAP EWM
SAP EWM is SAP’s warehouse management solution that provides advanced management of all in-warehouse processes from goods receipt through goods issue. Compared with the legacy WM (LE-WM), it offers far broader functionality, including labor management, slotting, value-added services, cross-docking, yard management, and automated warehouse integration (MFS). As of 2026 it is the only strategic WMS that SAP continues to actively develop, while WM is being phased out (compatibility pack, supported until around 2030).
Chapter 2 Deployment Options ― Embedded / Decentralized / Stock Room
| Deployment | Placement | Licensing | Best Suited For |
|---|---|---|---|
| Embedded | Co-resident within S/4HANA | Included in the S/4HANA license | Small to mid-large scale; wants tight ERP integration |
| Decentralized | Independent system on a separate server | Requires a separate platform/server | Large scale, high throughput; wants isolation from ERP downtime |
| Stock Room Management | Lightweight inventory management within S/4HANA | Core | Small warehouses; a lightweight alternative where EWM would be too heavy |
• Embedded: Runs in the same system as S/4HANA, with real-time, tightly coupled integration to inventory, production, and shipping. Simple to implement and operate
• Decentralized: Ensures high availability and high throughput as an independent system. Less affected by ERP downtime or updates, and can consolidate warehouses from multiple ERP systems
• Stock Room Management: Lightweight inventory management equivalent to legacy WM, suited to small sites that do not need EWM’s advanced functions
• Key selection point: Embedded is the standard choice for mid-size operations wanting tight ERP integration, while decentralized is the standard for 24-hour large DCs and automated warehouses. Choose with future automation expansion and throughput requirements in mind.
Chapter 3 Organizational Structure and Master Data
EWM models the warehouse as a hierarchy of “warehouse number → storage type → storage section → storage bin,” managing inventory precisely at the bin level. The organizational structure and master data defined here form the basis for the process control described later (Chapter 4).
3-1 Warehouse Hierarchy
| Level | Meaning | What It Enables |
| Warehouse Number | The top level of a warehouse complex managed by EWM; maps to a plant × storage location in S/4HANA | Centralized management of one physical warehouse as a single warehouse number |
| Storage Type | Area classification such as high-bay racking, floor storage, picking, inbound/outbound zones, or automated storage | Different putaway/allocation rules per area |
| Storage Section | Subdivision within a storage type (fast movers/cold storage/hazardous materials, etc.) | Separates putaway destinations by characteristic |
| Storage Bin | The actual storage location (address); has a bin type and access type | Manages inventory, capacity, and travel paths at the bin level |
| Activity Area | A logical unit grouping tasks such as picking and physical inventory | Used as the unit for assigning and sequencing work |
| Quant | A block of stock in one bin sharing the same product, batch, and stock type | Identifies stock within a bin by attribute |
3-2 Master Data Around Inbound/Outbound
• Staging Area / Warehouse Door: Temporary holding areas and truck doors for inbound/outbound; can be assigned automatically via door determination groups
• Means of Transport / Transportation Mode: Defines the vehicles and transportation modes used for inbound/outbound and links to shipment planning
• Work Resources / Resource Groups: Defines resources such as workers and forklifts, and assigns work to them
3-3 Units That Represent Stock (Stock Type / HU)
• Stock Type and Availability Group: Distinguishes available stock, stock under quality inspection, blocked stock, etc., and controls whether it can be allocated; mapped to ECC stock types
• Handling Unit (HU): Physical packaging such as pallets, cases, and containers. Inventory, movements, and shipments are managed at the HU level, and nested structures can also be represented
• Lot/Batch, Serial Number, Expiration Date: Tracking at the lot/serial level, with allocation via FEFO (First-Expired-First-Out)
3-4 Product Master (Warehouse View)
By maintaining EWM-specific warehouse views on top of the S/4HANA product master, putaway, allocation, and slotting behavior can be controlled per product.
• Warehouse Data / Storage Type Data: Inbound/outbound control, storage type assignment, and quantity classification per product
• Slotting Data: Inputs for optimal bin placement based on shipping frequency, weight, and dimensions
• Packaging Data: Default settings related to packaging materials, HU types, and quantities per package
• The source of EWM’s precision lies in managing inventory by bin and HU. Because it can track in real time which HU is in which bin, and how many units exist by stock type, batch, and expiration date, putaway, allocation, physical inventory, and traceability all operate accurately at the bin and package level.
Chapter 4 Functional Details
This chapter explains in detail what EWM can do, following the process from goods receipt through goods issue. Each process is controlled by the master data from Chapter 3 together with the warehouse process types (WPT) and storage control described below.
4-1 Inbound / Goods Receipt (Inbound)
• ASN Integration: Generates inbound deliveries from purchase orders/advance shipping notices and reconciles planned versus actual receipts
• Goods Receipt and Inspection: Quantity inspection, routing to quality inspection (QM integration), and damage checks; pass/fail branches to putaway or hold
• Deconsolidation: Re-sorts mixed HUs by storage destination or process step
• Putaway Strategy: Automatically determines the optimal bin based on product characteristics, bin availability, capacity, temperature zone, and turnover rate (choosing strategies such as fixed, open, near-picking, or bulk)
• Putaway Execution: Distributed as warehouse tasks (WT) to RF devices/automated equipment, putting away stock into bins at the HU level
4-2 Storage and Inventory Management
• Real-Time Inventory: Immediate visibility of stock by bin, HU, lot, serial number, stock type, and expiration date
• Internal Movements and Replenishment: Automatically replenishes picking areas from storage areas (based on reorder point, planned, or confirmed quantities)
• Physical Inventory: Cycle counting and full physical inventory, with discrepancy recording and stock adjustment
• Stock Blocking/Release and Quality Decisions: Manages stock status such as under inspection, on hold, or available for shipment
4-3 Outbound / Picking (Outbound)
• Outbound Delivery Order (ODO): Generates outbound delivery orders from sales orders/shipping instructions
• Wave Management: Bundles multiple outbound orders into waves and processes them in batches to match travel paths, resources, and shipping schedules
• Picking Strategies: FEFO/FIFO, shortest-path routing, total picking (bulk picking) / wave-and-pick (sorting) methods
• Picking Support: RF handheld devices, voice (Pick-by-Voice), Pick/Put-to-Light, picking carts, and automation (GTP)
• Packing and Shipment Inspection: Packing, weight/dimension checks, and issuance of shipping labels and delivery notes
• Shipping and Dock Operations: Shipping door assignment, loading, truck loading, and integration with TM (Transportation Management)
4-4 Mechanisms That Control Processes (WPT / Storage Control)
How work is determined in EWM is governed by warehouse process types (WPT) and storage control. This is what makes EWM not merely an inventory ledger but a precise work-design tool.
• Warehouse Process Type (WPT): Defines HU control, storage processes, and confirmation procedures for each type of process such as putaway, stock removal, or movement; automatically determined via control indicators
• Process-Oriented Storage Control (POSC): Routes work through multiple steps in sequence, such as goods receipt → inspection → VAS → putaway
• Layout-Oriented Storage Control (LOSC): Routes work through physical layout waypoints (e.g., transfer points on conveyance equipment)
• Warehouse Order (WO) Creation Rules: Bundles warehouse tasks into work packages (WOs) distributed to workers, optimizing travel paths and workload
4-5 Advanced Functions (EWM Advanced)
| Function | What It Enables |
| Labor Management | Setting engineered labor standards, measuring actual performance, productivity analysis, staff planning, and incentive calculation |
| Slotting & Rearrangement | Automatic proposals and periodic re-slotting of optimal bin placement based on shipping frequency (ABC), weight, and size |
| Value-Added Services (VAS) | Manages in-warehouse processing such as labeling, kitting, assembly, and repackaging as formal process steps |
| Cross-Docking | Routes inbound goods directly to outbound without storage, reducing storage costs and lead time |
| Yard Management | Manages the placement and movement of trailers, vehicles, and docks on the premises |
| Billing | Charges for warehouse services based on storage and labor volume, for 3PL operations |
| Returns | Return receipt, inspection, and restock/scrap decisions (reverse logistics) |
| Production Integration (PP Integration) | EWM executes material supply to manufacturing (PSA) and finished goods receipt |
4-6 Visibility ― Warehouse Monitor and Work Management
• Warehouse Monitor: Provides real-time, single-screen monitoring of inventory, tasks (WT/WO), resources, and exceptions within the warehouse, and allows direct actions (priority changes, reassignment, exception handling) from that screen
• EWM KPIs / Analytics: Visualizes productivity, shipping accuracy, inventory accuracy, throughput, and bin utilization, feeding back into labor management and slotting
• Dynamic Work Redistribution: Dynamically reassigns work in response to busy periods, delays, or staff shortages
4-7 MFS (Material Flow System) ― Direct Control of Automated Warehouses
EWM’s biggest differentiator is MFS (Material Flow System). It allows EWM to directly control automated warehouse equipment without an additional Warehouse Control Unit/System (WCU/WCS).
• Connected Equipment: Automated storage/retrieval systems (AS/RS), conveyors, sorters, automated transport such as AGVs/AMRs, and Goods-to-Person (GTP)
• Direct Control: EWM directly executes transport instructions, route control, and exception handling via telegram communication with PLCs (no intermediate WCS required)
• Benefits: Simplified architecture through elimination of the WCS layer, and real-time, unified management together with inventory and work
• MFS makes it possible to consolidate the “two layers of WMS (EWM) and WCS (equipment control)” into a single layer. For warehouses investing in automation, this consolidation greatly improves operational simplicity and visibility.
Chapter 5 Automation, Robotics, and AI Integration
• Robotics Integration: Connects AMRs, picking robots, and Goods-to-Person (GTP) via MFS or standard APIs
• EWM + Automation Orchestration: Integrates and controls robots from multiple vendors using solutions such as SAP Warehouse Robotics
• Use of AI: AI-driven advances in warehouse operations are progressing, including slotting optimization, demand-linked work planning, and anomaly detection
Chapter 6 Migrating from WM to EWM
• Background: Legacy WM (LE-WM) is treated as a compatibility pack in S/4HANA, with limited support until around 2030. New implementations are expected to use EWM
• Migration Approach: A greenfield build aligned with EWM best practices is the general approach, involving redesign of organizational structure and strategy
• Phased Rollout: First renew key warehouses with embedded EWM, then expand large DCs to decentralized deployment and automation (MFS)
⚠ Migration Caution: Moving from WM to EWM is not a simple version upgrade but a substantial rebuild that recreates bins, strategies, and work design. Rather than carrying over current operations as-is, success depends on redesigning operations around EWM capabilities such as slotting, wave management, and labor management.
Chapter 7 Configuration (Detailed Setup Steps)
This chapter organizes the concrete configuration steps for building EWM, following the structure of the SAP EWM Configuration Playbook (assuming embedded EWM on S/4HANA; menu paths refer to IMG = SPRO; transactions are reached by navigating from SPRO to IMG). Configuration proceeds in the order: “① S/4HANA ↔ EWM integration → ② organizational structure → ③ warehouse master structure → ④ process control → ⑤ documents/number ranges.”
Figure: Overview of EWM Functionality (Source: quoted from SAP EWM materials, EWM-Processos p4)
7-1 S/4HANA ↔ EWM Integration (Basic Settings)
Even with embedded deployment, S/4HANA and EWM communicate via queues (qRFC). The integration foundation must be established first.
• Logical System Definition and Client Assignment: IMG → SCM Extended Warehouse Management → SCM Basis → Integration → Basic Settings for Setting Up the System Landscape
• RFC Destination / Business System Group: Configures target systems/queue types and monitoring settings for qRFC (QIN/QOUT schedulers)
• Distribution Model Generation: Generates the transfer model for master and transactional data to EWM
※ Note: Even though embedded EWM runs within the same system, queue settings and business system group definitions are still required for delivery and inventory integration. For decentralized EWM, RFC/queue monitoring carries even greater weight.
7-2 Organizational Structure Settings (S/4HANA Side / EWM Side)
| Area | Setting | IMG Menu Path (Summary) |
| S/4HANA | Plant, storage location, shipping point, ERP warehouse number | Enterprise Structure / Logistics Execution |
| S/4HANA | Assignment of warehouse number ↔ plant/storage location | Logistics Execution → Warehouse Mgmt |
| EWM | Definition of warehouse number | SCM EWM → EWM → Master Data → Define Warehouse Numbers |
| EWM | Supply Chain Unit (SCU) and business partner assignment | Master Data → Define/Assign Supply Chain Unit |
| EWM | Mapping of EWM warehouse ↔ ERP warehouse | Interfaces → ERP Integration → General Settings |
7-3 Warehouse Master Structure Settings
Defines the physical and logical structure of the warehouse hierarchically, from stock types down to bins.
Figure: EWM Warehouse Organization and Master Data Configuration Screen (Source: quoted from the SAP EWM Configuration Playbook, p30)
• Availability Group / Stock Type: Definition and mapping of availability groups and ECC/EWM stock types
• Storage Type / Storage Section / Storage Type Group: High-bay racking, floor storage, picking, inbound/outbound zones, etc.
• Storage Bin: Bin type, access type, and bin structure (mass-generated via Storage Bin Structure)
• Staging Area / Warehouse Door: Staging area, door determination group, and door assignment
• Activity Area: Generates the logical unit that groups tasks such as picking
• Product Master (EWM View): Maintains warehouse data, storage type data, slotting, and packaging data views
• HU / Batch: Packaging material type, HU type, and batch management (activation of LOG_LE_INTEGRATION, number ranges)
7-4 Process Control (WPT / WO / Storage Control)
Warehouse process types, warehouse orders, and storage control govern how work is determined within the warehouse.
Figure: Warehouse Process Type (WPT) Settings (Source: quoted from the SAP EWM Configuration Playbook, p77)
• Warehouse Process Type (WPT): Controls putaway and stock removal, HU control, storage processes, and warehouse request settings; determines WPT via control indicators and assigns it to the product master
• Warehouse Order (WO): Defines number ranges, creation rules, item/subtotal filters, and search sequences by activity area, optimizing the work packages distributed to workers
Figure: Storage Control (POSC/LOSC) Settings (Source: quoted from the SAP EWM Configuration Playbook, p100)
• Storage Control: Process-oriented (POSC — sequences such as goods receipt → inspection → putaway) and layout-oriented (LOSC — physical layout waypoints). Configures storage process steps, storage process definitions, and WPT determination
• Delivery Processing Profile: Profiles for text, date/time, status, field control, incompletion checks, etc., and ERP integration (mapping of document, item, and date types)
7-5 Configuration Sequence (Practical Order)
• Order: Integration foundation → organizational structure → master structure (storage types/bins/areas) → process control (WPT/WO/storage control) → documents/number ranges
• Settle First: Consistency of number ranges and ERP ↔ EWM mapping (warehouse number, document type, stock type). If this is misaligned, every downstream step breaks down
⚠ Edition Differences: In S/4HANA Public Cloud, configuration is done in a Fiori-based configuration environment rather than SPRO. Private/on-premise editions use SPRO (IMG). The menu paths in this chapter assume on-premise/private edition.
Chapter 8 Customer Case Studies (Public Cases)
EWM delivers results not merely by digitizing simple warehouse tasks, but through large-scale warehouse transformations combined with automation and robotics. This section introduces representative publicly disclosed case studies.
8-1 Hasco Vision (Automotive Lighting) ― The World’s First EWM-Based Mobile Robot Warehouse
• Overview: Built a warehouse integrating mobile robots (AMRs) on an EWM foundation (implemented by Westernacher)
• Results: 100% accuracy in production supply, approximately 30% improvement in storage bin utilization, and roughly a one-third reduction in labor costs
Figure: EWM Outbound Process (reference; Source: quoted from SAP EWM materials, EWM-Processos p5)
[Key Takeaway] EWM’s integration with MFS/robotics can simultaneously improve accuracy, space efficiency, and labor costs. In automation-driven warehouses, the degree to which EWM also handles equipment control determines the results achieved.
8-2 DAW (Paints) ― Direct EWM Integration of a High-Bay Warehouse and AutoStore
• Overview: Built a state-of-the-art distribution center directly integrating a high-bay (automated high-rise) warehouse and AutoStore with EWM
• Results: Improved product stock availability and process stability, enhancing delivery service to customers
8-3 Global Automotive Aftermarket Retailer ― Productivity Gains Through RF Automation
• Overview: Rolled out automated warehouse processes based on mobile RF scanning across multiple distribution centers in India and China in under two years
• Results: Approximately 30% improvement in warehouse staff productivity
8-4 Typical Benefit Levels
| Metric | Improvement (Based on Public Case Studies) |
| Material handling costs | Approx. -20% |
| Putaway speed | Approx. +50% |
| Picking time | Approx. -25% |
| Storage bin utilization | +30% (automation cases) |
• A common thread across these cases is that EWM is used not as a “warehouse activity recording system” but as an “integrated platform that optimizes together with automation equipment (AS/RS, AutoStore, AMR).” The configuration described in the previous chapter (WPT, storage control, MFS) provides the foundation that makes this integration possible.
Chapter 9 Conclusion
SAP EWM is the only strategic WMS that SAP continues to actively develop, consistently covering everything from the basics of inbound/outbound operations, inventory, and RF, through labor management, slotting, cross-docking, and yard management, to the direct control of automated warehouses via MFS. The key is to select the deployment option (embedded / decentralized / Stock Room) according to requirements and to design with future automation expansion in mind.
• Final message: The value of EWM lies not in “digitizing warehouse work,” but in "optimizing the WMS, equipment control (MFS), and labor together as one." In the age of automation, this degree of integration is what determines a warehouse’s productivity and throughput.
(This paper was prepared based on publicly available SAP information on SAP EWM/MFS/deployment options and literature from 2025–2026. The scope of functionality varies by edition and release.)
Have a question about this article?
Ask the author directly — no sales pitch, just an answer.