Highlighted in previous blogs http://scn.sap.com/community/s4hana/blog/2015/11/05/hana-journey-and-features-of-scm-products-in-s4-hana-simple-logistics and http://scn.sap.com/community/s4hana/blog/2015/11/19/sap-s-road-map-for-supply-chain-solution-with-s4-hana-and-its-expected-benefits on the advantages and SCM applications being natively integrated in digital core of S/4 HANA (S4H). This blog is very specific to EWM integration with S4H.

It appears from below SAP slide (though stated as Labs preview) that EWM will be embedded in digital core of S4H in On-premise edition of 1610 release i.e functionalities of EWM will be made available in digital core and there is no need for running EWM as a separate application.


Advantages will be

  • Master data and transaction data need not be transferred between the systems and CIF and q RFC connections are not needed (Reducing TCO , inconsistency and downtime of systems)
  • Material master , business partners stored only in one system (thus reducing the data footprint )
  • Customizing objects like HU types need not be transferred to EWM  (thus reducing data footprint , inconsistency and complexity of the systems)
  • There will be no duplication of business documents ( Presently ECC delivery document are replicated as separate document numbers , thus reducing data redundancy and time spent in matching the documents numbers in reports etc)
  • Common maintenance / down time

Now , the question is whether this native integration of EWM with S4H will be relevant / beneficial for all customers or scenarios ? Answer is NOT as

One of the main USP of SAP EWM is its capability to operate in decentralized mode i.e both ERP (ECC or S4H) and EWM can run independent of each other i.e all Goods receipt (GR) , Goods issue (GI) and other warehouse activities like VAS etc can be performed in EWM even if the connection with ERP (ECC) is broken. All these transactions / documents get transferred / updated to ECC once the connection is restored.

So, the stand alone deployment of EWM will continue for

  • Business critical warehouse operations 
  • Risk mitigation (during migration to S4H etc)
  • Scalability for large warehouses

Hence, if the warehouse operations are de-centralized, then it needs to be ascertained  whether the option of native integration of EWM with S4H core should be chosen or not.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Panaya Panaya

    While this blog post clearly states that EWM will no longer be required, The most updated simplification document of 1610 (p. 222) states:
    “ Required and Recommended Action(s) The Warehouse Management (LE-WM) and the other components described above is not the target architecture within SAP S/4HANA. The (already available) alternative functionality is Extended Warehouse Management (SAP EWM) and a customer could start introducing EWM upfront to the SAP S/4HANA installation. ”

    So, is it or is it not a part of S4?

  2. E. Roelofs

    We are an e-commerce seller and have an existing SAP landscape with SAP ECC and embedded WM. For our new warehouse we have planned to implement SAP EWM and we are thinking of what system setup would be the best for us.

    Current situation: SAP ECC 6.0 (SQL Database)

    New situation SAP ECC 6.0 (SQL Database) connected with SAP EWM (on a HANA database)

    Within the SAP EWM solution, next to material master data and business partners, we need other master data like Bill Of Material and plant specific material master data which is not standard available in EWM.

    Question: is there a possibility to implement SAP EWM within S4HANA as a decentralized system, connected to SAP ECC and what are the advantages/disadvantages of this solution?


Leave a Reply