SAP S/4HANA Extended Warehouse Management Architecture

1. The Urgent LE-WM Sunset Mandate

Classic SAP Logistics Execution - Warehouse Management (LE-WM, transactions LT01, LT03, LT12, tables LTAK/LTAP) is part of the S/4HANA Compatibility Pack, which reaches official end-of-use rights by end of 2025/2026. Continuing to run classic LE-WM creates immense architectural compliance risk and blocks Clean Core upgrades.

SAP S/4HANA Extended Warehouse Management (EWM) is the strategic, long-term solution. However, architects face a critical decision: Which deployment model fits their operational scale and resilience requirements?

2. Deployment Model Decision Matrix: Embedded vs. Decentralized

Evaluation Dimension	Embedded EWM Basic	Embedded EWM Advanced	Decentralized EWM on S/4HANA
Licensing	Included in standard S/4HANA Enterprise Management license	Requires additional EWM Advanced license metric	Requires dedicated S/4HANA instance + EWM licensing
System Landscape	Same client and HANA database as S/4HANA ERP	Same client and HANA database as S/4HANA ERP	Dedicated separate server/tenant for warehouse operations
ERP Downtime Resilience	Warehouse stops during ERP maintenance/upgrades	Warehouse stops during ERP maintenance/upgrades	24/7 Zero Downtime: Warehouse continues operating during ERP offline
High-Volume Automation	Manual and simple RF handling	Wave management, slotting, labor mgmt, MFS	Automated Guided Vehicles (AGV), high-bay MFS, mega hubs
Integration Latency	Direct memory call (Zero qRFC serialization)	Direct memory call (Zero qRFC serialization)	qRFC / BGRFC / CloudEvents over network

3. Clean Core Extensibility in S/4HANA EWM

In classic LE-WM, custom logic was implemented via user exits (e.g. MWMTO001) or raw modifications to function module L_TO_CREATE_TR. In S/4HANA EWM, Clean Core requires:

• Released Warehouse Task BAdIs: Use /SCWM/EX_CORE_CR_POST for confirmation actions and /SCWM/EX_CORE_CR_INT for determination without touching standard delivery code.
• Decoupled Asynchronous Events: Trigger outbound stock status changes via SAP Advanced Event Mesh (CloudEvents) rather than direct synchronous table updates on LIKP/LIPS.
• Released CDS Projections: Query warehouse inventory and task execution via released CDS view entities such as /SCWM/I_WarehouseTask.

4. Modernizing ITSmobile & RF Scanning

Classic RF terminals relied on ITSmobile (HTML-wrapped SAP GUI dynpros in transaction /SCWM/RFUI). For Clean Core modernization:

1. SAP Mobile Start & Fiori Warehouse Apps: Deploy mobile-optimized Fiori apps for Picking, Putaway, and Physical Inventory.
2. Headless Barcode Scanning APIs: Implement RAP OData v4 query services consumed by lightweight Android/iOS scanning ruggedized devices (Zebra, Honeywell).

5. Interactive Architecture Generator

Model your warehouse throughput profile, evaluate deployment topologies, and generate clean core BAdI code with Tool #103:

🚛 Launch Tool #103: S/4HANA EWM Clean Core Architect →