The SAP Extended Warehouse Management FAQ Series: System Architecture
In today’s blog post, I will try to answer some of the frequently asked questions that we receive regarding the options available to set-up your SAP Extended Warehouse Management systems, some integration options available, as well as some additional information sources which serve as guidance for your implementations.
Which Questions will be answered in this Blog Post:
- Which deployment options are available?
- How can we harmonize material numbers if we have multiple ERP systems connected to the same decentral EWM on SAP S/4HANA?
- Can we connect Decentral SAP EWM on SAP S/4HANA to SAP S/4HANA Cloud?
- Can we run the new Advanced Shipping & Receiving with decentral SAP EWM?
- Are there any plans for an integration with Global Trade Services via SAP Transportation Management?
- Can we use SAP Transportation Management (SAP TM) and Decentral SAP Extended Warehouse Management (SAP EWM) on the same SAP S/4HANA system and client?
- Can we run other applications as well on the same system as decentral SAP EWM?
- Is there a source for guides or best practices documents for SAP Extended Warehouse Management?
Which deployment options are available?
When talking about deployment options first thing we need to distinguish between the On Premise and the Cloud deployments. Before we breakdown what each option entails, it is important to note that we will only refer to options available on SAP S/4HANA, as the old NetWeaver deployments (i.e. Business Suite SAP EWM 9.5 and lower) will not be supported any longer after 2027.
On Premise implies that you deploy the warehouse management system in your own data centre with the options to customize and extend the suite with complete control over your environment. This option allows users to optimize their warehouse capacities towards various specializations.
For On Premise deployments there are two options available:
- Embedded EWM on SAP S/4HANA – in this scenario, the warehouse management system is installed on the same client as the central ERP system and the integration between the two is seamless. Embedded EWM is available in two versions
- Basic Warehouse Management
- Extended Warehouse Management (which provides additional features)
- Decentralized EWM on SAP S/4HANA – with this option, the warehouse management system is installed on a separate system and can work independently from the central ERP system. This allows warehouse operations to continue working even in cases when the ERP system is not available or going through maintenance. Additionally, this option is also more scalable, able to process warehouse operations in high-volume, high-intensity environments. This option also supports integration with multiple ERP systems, which would allow a logistic service provider to use a single warehouse to serve the logistical needs of several different business or corporate entities. Furthermore, opting for a Decentralized EWM on SAP S/4HANA approach opens the possibility of connecting it with SAP S/4HANA Cloud Private edition, which is explained below
SAP S/4HANA Cloud Warehouse Management on the other hand, is deployed with powerful cloud hyperscalers, where SAP manages the IT infrastructure. Like most Cloud pricing models, this is a subscription service, where users can experience new innovations via continuous feature deliveries, fast time to value and lower total costs of ownership (TCO). As with the On Premise version, the SAP S/4HANA Cloud deployment also supports two versions:
- SAP S/4HANA Cloud, Private edition – with this option, a decentral as well as an embedded deployment of SAP EWM on SAP S/4HANA is possible, with the benefit of receiving the same functionalities as in the On Premise scenarios. The service is hosted on a private server where SAP manages the technical maintenance, and customers have the option to choose whether to upgrade to a newer version
- SAP S/4HANA Cloud, Public edition – in this option, cloud Warehouse Management is embedded in SAP S/4HANA Cloud and is a version of Extended Warehouse Management which offers a scope of warehousing activities suitable for cloud
For a summarized look at all these options, please refer to the following figure.
The release information and restriction notes for Embedded EWM and Decentralized EWM on SAP S/4HANA provide conceptual and functional comparisons between the deployments of the latest versions for SAP EWM as well as comparison to SAP EWM 9.5.
Note 3080846 “SAP S/4HANA 2021: Release information and restrictions for EWM in SAP S/4HANA” – this SAP Note contains release information and restrictions when using embedded SAP Extended Warehouse Management (EWM) in SAP S/4HANA, on-premise edition 2021 FPS00.
Note 3080907 “Release information and restrictions of Decentralized EWM on SAP S/4HANA 2021” – This SAP Note contains release information and restrictions when using SAP Extended Warehouse Management (EWM) on a separate decentralized SAP S/4HANA system, on-premise edition 2021 FPS00.
Is there a simple way to integrate non-SAP ERP systems with Decentralized EWM on SAP S/4HANA?
In some cases, users would prefer to use their non-SAP ERP system together with a Decentralized EWM on SAP S/4HANA. To reduce complexity in this process, we took steps to minimize the integration that should take place. To do this, we have re-introduced IDoc integration, which previously was only available for integrating non-SAP ERP systems with Business Suite EWM 9.5. This integration method uses a reduced set of messages and integration steps.
For a guide on how to implement this integration, I encourage you to read SAP Note 3140478 “IDOC Integration for non-SAP ERP systems and decentralized EWM in S/4 HANA”.
How can we handle non-harmonized material numbers from multiple ERP systems connected to the same decentral EWM on SAP S/4HANA?
In some cases, it may happen that customers are using decentral EWM on SAP S/4HANA on the latest On Premise release, which is connected to multiple enterprise management systems with non-harmonized material numbers (e.g. ERP1: MAT1, ERP2: MAT1) that represent different products in the warehouse. Users want to be able to clearly identify the product in the warehouse when document communication for the material takes place between an ERP System and SAP EWM, e.g. an Inbound Delivery is created. Therefore, it is necessary to use different material numbers in EWM for the non-harmonized material numbers in ERP. These material numbers must be correctly mapped during transactional processing (inbound and outbound) in EWM.
Before we answer the question on how to do the mapping, I would like to point out that there are two distinct scenarios we must consider first.
In the first scenario, we must assume that only SAP EWM is running in the side-by-side system, and no other application is running on that same system. In that case, you can consider option 2 from SAP Note 3109532 “Handling of Non-Harmonized Material from multiple ERPs in SAP S/4HANA Decentral EWM” as it provides a very easy way (with less custom developer skills required) to map multiple non-harmonized ERP system material master records to the material master record which is used in SAP EWM.
In the second scenario however, we must assume that SAP EWM is running with other applications on the same decentral system (e.g. SAP TM). In that case, This is the standard SAP approach for using UKMS mapping data, however it requires more developer skills because the UKMS interfaces have to be used in custom code BAdI implementations.
Can we connect Decentral SAP EWM on SAP S/4HANA to SAP S/4HANA
For several years now, it is possible to connect a decentral EWM 9.5 system (based on NetWeaver) to an SAP S/4HANA Cloud ERP system. However, a decentral EWM on SAP S/4HANA integration with S/4HANA Cloud is so far not possible, because the integration scenario is tailored for the Core Interface (CIF) Remote Function Call (RFC) based master data replication.
Our goal is to provide in the future an integration scenario which allows to integrate decentral SAP EWM on SAP S/4HANA On Premise (or private Cloud) with SAP S/4HANA Public Cloud.
Can we run the new Advanced Shipping & Receiving with decentral SAP EWM?
Advanced Shipping & Receiving currently is only possible in an embedded deployment, as it uses the Transportation Management Freight Order as a central object, which is not possible in a Decentral set-up. However, we plan to make ASR available for decentral in 2023 and beyond.
Are there any plans for an integration with Global Trade Services via SAP Transportation Management?
SAP Extended Warehouse Management has the option to directly integrate with Global Trade Services in non-ASR scenarios. However, with the SAP S/4HANA 2021 FPS01 release you can now also use Advanced Shipping and Receiving to manage communication between SAP S/4HANA components and SAP Global Trade Services (GTS). For SAP S/4HANA, this involves the SAP TM and SAP EWM components connecting with an external GTS system. With this integration, you can do compliance-relevant checks for, e.g., embargos or sanction party lists, and obtain clearances such as unloading permits and customs clearance after approval of the export declaration.
Can we use SAP Transportation Management (SAP TM) and Decentral SAP Extended Warehouse Management (SAP EWM) on the same SAP S/4HANA system and client?
To achieve a seamless logistical process, companies put more focus on integrating SAP EWM with SAP TM. While the most typical integration scenario is having both SAP TM and SAP EWM embedded in SAP S/4HANA, there are other possible scenarios. The scenario in this paragraph pertains to those users who would prefer to use decentralized Extended Warehouse Management on SAP S/4HANA and then intend to use the same SAP S/4HANA system and client for SAP Transportation Management. Such a set-up is released as SAP standard functionality only under specific boundary conditions, such as minimum version required, UKMS mappings, and others. For a detailed look into these boundary conditions, I recommend you read the SAP Note 2812981 “Transportation Management and decentralized EWM in same SAP S/4HANA system and client”.
Can we run other applications as well on the same system as decentral SAP EWM?
As was stated above in the case of running SAP TM on the same system as decentral SAP EWM, there are certain scenarios where it may be possible. Also, since the SAP S/4HANA 2021 release, we also support using SAP Yard Logistics (on SAP S/4HANA stack) and SAP EWM in the same system client. However, an easier approach you may consider is to keep your decentralized SAP EWM application running on a system separate from other applications.
If you are interested in a modular approach when designing and implementing your Digital Supply Chain, you can also check out SAP Digital Supply Chain Management, edition for SAP S/4HANA. It offers a composable package of SAP S/4HANA solutions and includes the cluster of market leading SAP Digital Logistics components.
Is there a source for guides or best practices documents for SAP Extended Warehouse Management?
Indeed there is. If you are setting up a new deployment of SAP Extended Warehouse Management, and you would like to follow some guides for different deployments of SAP Extended Warehouse Management, I recommend you check out SAP Note 2782080 “Overview of Guides or Best Practices Documents for Extended Warehouse Management”.
FIND OUT MORE!
For more information about SAP Extended Warehouse Management, please follow us on social media, our YouTube channel or our community pages:
SAP EWM topic page:
SAP Digital Supply Chain channel:
SAP EWM LinkedIn group:
Release information and restrictions of embedded EWM on SAP S/4HANA 2021:
Release note for EWM in S/4HANA 2021
Release information and restrictions of Decentralized EWM on SAP S/4HANA 2021:
Release note for Decentralized EWM in S/4HANA 2021
For a complete list of Q&A about SAP EWM within the community, please access this link:
In case you do not find your specific question there, feel free to post your question via the following form:
Fantastic blog one question for nonERP integration using IDOC guess, middleware like SAP PO is still required.
Just to clarify, are you asking if middleware (such as SAP PO) is required for integrating decentralized SAP EWM on SAP S/4HANA with non-SAP ERPs via IDOCs?
Yes, is middleware still required?
Apologies for the late reply, I had to double check with some colleagues, but the answer is that no middleware is required for the integration.
Thanks for the excellent summary and update on EWM System Architecture.
At this moment we have a customer with SAP ECC 6 where we are working with them on an possible SAP EWM Decentral PCE implementation.
For mobile warehousing, our customer wants to confirm if ITS mobile + RF devices are still the way forward, being the SAP recommendation for this scenario.
He’s doubts came from the document presented at SAPPHIRE in 2019: ASUG84117 - SAP Strategy for Mobile Warehousing in S4HANA.
Being this document from May 2019, would you know if there are any developments in this topic?
Thanks in advance!
thank you very much for this great blog!
Regarding your answer to the question: Can we connect Decentral SAP EWM on SAP S/4HANA to SAP S/4HANA?
Is there any SAP note with additional information or roadmap you can share with us?
That would be very helpful.
Thank you very much, Ralf
Apologies for the late reply. Unfortunately the Product Management team does not have any more information we can share at the moment regarding this integration topic. We will update this topic as soon as we have a solid roadmap plan.
thank you very much for this concise blog. ASR with decentral EWM is in the Roadmap for Q4 2023. Does this imply that Inbound Cargo Registration will then be available with decentral EWM, too?