The legacy landscape: where most organisations start
Most organisations migrating to S/4HANA today are running one of two warehouse management configurations in ECC. SAP Logistics Execution Warehouse Management (LE-WM) is the classical warehouse management component embedded in ECC — capable for straightforward warehousing operations, but architecturally limited. SAP has confirmed that LE-WM is not available in S/4HANA. Organisations running LE-WM must migrate to EWM.
SAP Extended Warehouse Management (SCM-based, decentralised) is a more capable platform that ran as a separate system, connected to ECC via ALE/IDocs. Many organisations in manufacturing, retail distribution, and third-party logistics operated decentralised EWM because it provided the warehouse complexity — multi-step putaway, task interleaving, RF-guided picking, yard management — that LE-WM could not deliver.
EWM on S/4HANA: embedded versus decentralised
Embedded EWM runs inside the S/4HANA system. Warehouse management processes execute in the same application instance as the ERP. There is no IDoc-based communication — stock postings, transfer orders, and goods movements are processed within the same system call. This simplifies the landscape, eliminates the latency of IDoc message exchange, and reduces infrastructure cost. It is the appropriate choice for organisations with moderate warehouse complexity, limited automation, and warehouses that do not require high-availability isolation from the ERP system.
Decentralised EWM on S/4HANA runs as a separate SAP system connected to the S/4HANA ERP via standard ALE distribution. This deployment is appropriate for organisations with highly complex warehouse operations, advanced automation (ASRS, goods-to-person robots, sorter integration), 24×7 operations where warehouse system availability must be isolated from ERP maintenance windows, or global distribution networks with dozens of warehouses that need independent scalability.
IOTEK’s earliest workstream in any supply chain migration is a warehouse complexity classification — grouping warehouses by process complexity, automation level, and downtime tolerance — that drives the deployment architecture decision before any configuration work begins.
Migration paths for LE-WM customers
The LE-WM to EWM migration involves both a functional expansion (EWM is significantly more capable than LE-WM) and a data migration challenge. Warehouse master data — storage locations, storage types, sections, and bins — must be recreated in EWM’s richer master data model. Open stock at cutover must be migrated cleanly using SAP’s S/4HANA Migration Cockpit tooling.
Custom code and RF transactions present a particular challenge. LE-WM implementations frequently contain custom RF screen programs, custom movement types, and custom transfer order creation logic. These do not migrate automatically. Each custom object must be assessed against the EWM ABAP Cloud model and, where necessary, redesigned as a BAdI-based extension rather than an ABAP modification.
The LE-WM to EWM migration is, in practice, closer to a new EWM implementation than a data conversion. Organisations that plan it as a simple technical migration typically discover this reality late — after go-live, when warehouse operators are working with a system that behaves differently from what they were trained on.
Migration paths for decentralised EWM customers
For organisations migrating from Business Suite decentralised EWM to decentralised EWM on S/4HANA, the existing EWM customising must be transferred using the cross-system customising viewer (transaction SCU0) to ensure consistency between the two landscapes during the transition period.
SAP’s guidance recommends maintaining the Business Suite EWM as the customising source system during the migration, with automated transport of customising changes to the S/4HANA EWM target, until the first warehouse goes live on S/4HANA. For organisations migrating multiple warehouses in waves over an extended period, this governance discipline requires strict change control across two parallel systems simultaneously.
SAP Transportation Management: embedded in S/4HANA
SAP TM in S/4HANA is embedded in the application. The key functional capabilities — freight order management, carrier selection, freight settlement, dangerous goods management, and customs — are available natively. The direct integration between embedded TM and embedded EWM within the same S/4HANA system eliminates the asynchronous messaging that was required in the Business Suite landscape.
For organisations that have not implemented TM and are managing transportation in LE-TE, the S/4HANA migration is the natural point to implement TM — replacing manual carrier booking, spreadsheet-based load planning, and unstructured freight accruals with a system that provides freight order management, carrier tendering via SAP Business Network, and automated freight settlement.
The cutover challenge in logistics migrations
The hardest operational moment in any logistics migration is the cutover. Warehouses do not stop. Goods are in transit, open transfer orders are in execution, inbound deliveries are on dock, outbound shipments are being picked.
IOTEK’s logistics migration practice includes a dedicated cutover design workstream that maps every in-flight process category — open transfer orders, open warehouse tasks, in-transit deliveries, open freight orders, open shipping notifications — to a cutover disposition. The inventory freeze period — the window during which no new warehouse transactions are permitted while stock is migrated — is designed to be as short as operationally feasible, typically 4–8 hours for a single warehouse, and is sequenced warehouse by warehouse in a wave approach for large multi-site operations.
The combination of EWM complexity, transportation integration, and the operational imperative of not stopping the warehouse makes logistics migration one of the highest-risk workstreams in an S/4HANA programme. It is also, when executed correctly, one of the most tangible value drivers — consolidating warehouse management, transportation execution, and ERP stock management into a single integrated S/4HANA logistics core.
To discuss how this applies to your programme, contact IOTEK.
Sources & References
- SAP Community — SAP EWM Migration to S/4HANA — community.sap.com/…/10-steps-for-migrating-to-sap-ewm-on-sap-s-4hana-platform
- SAP Community — EWM FAQ: Migration to S/4HANA EWM — community.sap.com/…/the-sap-extended-warehouse-management-faq-series-migration-to-s-4hana-ewm
SAP, S/4HANA, RISE with SAP, GROW with SAP, Joule, and SAP Business Technology Platform are trademarks of SAP SE. IOTEK CONSULTING LLC is an independent consultancy and is not affiliated with, endorsed by, or a certified partner of SAP SE unless stated in a current written partner agreement. Content is based on publicly available SAP documentation, SAP Community resources, and IOTEK’s independent practitioner experience.