Skip to Content

Strategy and roadmap for SAP S/4HANA and SAP Extended Warehouse Management (SAP EWM)

What is the road map for SAP EWM in combination with SAP S/4HANA?

We plan to deliver SAP EWM in combination with the on-premise edition of SAP S/4HANA in two sequential approaches to two separate customer options for product integration on the SAP HANA platform.

In the short term, SAP EWM is planned to be connected to SAP S/4HANA using a sidecar approach based on the same technology employed for communication with SAP ERP. The sidecar approach as an option for integration with SAP S/4HANA supports business scenarios and processes of complex and automated warehouse and distribution centers. The two deployment options are SAP EWM as part of SCM Server or deployed on SAP NetWeaver.


In the long term, SAP EWM is planned to be an embedded application component within SAP S/4HANA. The longer-term goal is to have basic warehousing and extended warehouse management running on a common code base embedded in SAP S/4HANA. The embedded approach as a deployment option within SAP S/4HANA supports less complex or non-high throughput warehouses with a simplified integration to S/4HANA business processes.

We will soon make available to you more details once we have finished with a thorough evaluation.

Will different functions be provided in the two options?

Our goal is to provide the same functions when using either option. This question remains to be answered until after we have finished with our aforementioned evaluation.

Is the SAP EWM sidecar option a temporary solution?

Our plan is to make available to you the option of SAP EWM sidecar to SAP S/4HANA as a long-term solution for sound business reasons, among which:

  • A decentralized deployment solution provides proven customer value, such as high volume data processing, risk mitigation, and scalability for large distribution centers.
  • This solution safeguards SAP EWM data when existing SAP ERP+EWM customers decide to migrate their ERP system to SAP S/4HANA.
  • This deployment also allows for connection to multiple ERP or S/4 systems.

A Frequently_Asked_Question document was complied to provide more details on the SAP S/4HANA and SAP Extended Warehouse Management. Please visit us on FAQ SAP EWM and SAP S/4HANA

You must be Logged on to comment or reply to a post.
  • Hi Emma,

    Is there a possibility of another landscape option. A decentralized S/4Hana with EWM connected to S/4 Hana with ERP.

    EWM(on S/4 Hana) <--> ERP(on S/4 Hana)

    Thanks for the info.



      • Hi Emma ,

        Apolgies if am wrong ,

        From your post i can understand that EWM can be on HANA , We also understand ERP can be on HANA . Cant both be on HANA and communicate as how srinivasa have questioned ??

        Please suggest.


        Jinoy Joshy

        • Hi Jinoy,

          As to ERP on Hana, I understood that you mean SAP ECC (R3) on Hana, then it's definately possible that EWM on Hana <-> SAP ECC on Hana, and this is the classic deployment that has been offered in market.

          While in this post, it's about EWM communicating with SAP S/4 Hana (the new ERP solution), and up to now the followings are possible:

          Decentral EWM <->SAP S/4 Hana

          and very soon, EWM will become one embedded module on SAP S/4 Hana.

          Srinivasa's question is valid, but we don't have any plan yet.



  • Emma, you seem to imply that right now, there is no EWM-Option for S/4-Customers at all?

    ("short term, SAP EWM is planned to be connected" + "long term, SAP EWM is planned to be an embedded").

    I was under the impression that you could connect an existing EWM to an S/4HANA on premise 1511, just like you can connect it to an ECC-System (is that the "sidecar approach" you mention?)

    Can you please elaborate on that?



    • Hi Joachim,

      You are absolutely right. When this was posted (in September 2015), the EWM<->S/4 was not yet released, that's why we used the "planned to be" wording. So yes, EWM sidecar approach have already been available since S/4 1511.

      And we're working on the "long-term" approach, as well as the new version of the FAQ document. We'll publish it ASAP. Thanks.



      • Hi Emma,

        I was not paying attention to the creation date this time (I usually do!), I just saw it in some stream and assumed it to be a new post....

        So thanks very much for clarifying and sorry for the confusion!



    • Hi Bruno,

      We can't provide the exact date at this point of time, but it's coming soon. I'll update you ASAP. Thank you for understanding.



      • Dear Emma,

        Thanks for this blog. I have two questions :

        (1) Where can we find the "expected" functional scope of S/4HANA Enterprise Management OP 1610  ?

        (2) Is Co-Deployment of SAP EWM & SAP S/4HANA a possible roadmap ?  or will EWM functionalities become an integrated part of S/4HANA CORE ?

        Request clarity on this aspect please.

        Thanks in anticipation.


        • Hi Monika,

          I can't answer the first question as it's not in my area.

          As to the second question, the answer is yes for both. Please download the attached FAQ of the blog  for details.



  • Hi Experts,

    what could be the reason to not continue with CIF and instead use ALE/idoc?

    “There are some differences in transfer of master data from ERP to new decentralized EWM on S/4HANA as captured in below image. In present (or classic) decentralized EWM on NW or SCM , master data (Material , customer, vendor etc) is transferred to decentralized EWM through Core Interface (CIF), however ALE / IDOC or web service needs to be used to transfer material , batch , customer , vendor etc .”


    Does ALE/Idoc provide more flexibility to select which fields are copied to De-central EWM (HANA)?

    Thanks for the response.

    Manish Bhavsar

    • Hello,

      the reason that CIF is not used anymore is purely because of the S/4HANA system as decentralized EWM. EWM in this system uses the same master data as an embedded EWM. That means it needs business partner, materials, batches, etc. in the "ERP" part of the S/4HANA system. And these can not be created by CIF.