Skip to Content

In the last blog of this series we learned more about the business aspects of SAP Extended Warehouse Management within the SAP S/4HANA 1610 release. This centralized version of SAP EWM is a full-fledged EWM system with clear to see business advantages, like the Fiori user experience and ability to leverage other SAP S/4HANA 1610 innovations without interface.

Now, let’s dive deeper into the advantages from a technical point of view. It is about 3 things: one system, reduction of data redundancy, and simplification.

One System

Having SAP Extended Warehouse Management brought into the core of SAP S/4HANA 1610 brings many technical benefits. Many customers are looking for simplification options of their SAP landscape, and this is possible with integrated extended warehouse management. Here are some concrete example of IT benefits.

With EWM in the core of S/4HANA 1610, the core interface (CIF) is no longer needed to transfer business partner data, material master data and batch master data from SAP ERP into SAP EWM. Now, there is a direct read of the business partner in EWM in S/4HANA instead of replication of the data across two systems. This facilitates a reduced DB footprint, reduced TCO (avoid replication & monitoring) and an overall simplified set-up and operations.

Another benefit is that companies can now leverage other enhancements from S/4HANA like the SAP Fiori user experience that has been harmonized with the 1610 version. The FIORI Launchpad is the single point of access for all applications, and all have the same look and feel with the new Belize theme. This UX provides a simple unified user experience across all UI technologies, giving the ability to merge transactions from different applications into one role. For instance, quality management functionalities and needed and available for warehouse managers with this 1610 release.

SAP Fiori app for Warehouse Monitoring

Another S/4HANA enhancement that EWM can now leverage without interface is the support of 40-digit material numbers, available since SAP S/4HANA 1511.

Reduction of Data Redundancy

Having SAP EWM in the core of SAP S/4HANA allows for end-to end insight and visibility while eliminating disparate systems and processes. The processes are leaner and there are less business documents required to perform the same tasks.

For example, in the integrated version of SAP EWM in SAP S/4HANA, there is no longer a need replicate the orders and create a Expected Goods Receipt. The inbound delivery gets information directly from the Purchase/Manufacturing Order.

Reduction of data redundancy in the inbound delivery process in SAP EWM in the core of S/4HANA

Similarly, warehouse request objects can now be skipped. You can process outbound delivery orders without using outbound-delivery requests; process inbound deliveries without having inbound-delivery notifications and process posting changes without using posting-change requests.

Across many areas, the same reduction of data tables can be seen, such as the elimination redundant customizing tables, redundant product valuation data, redundant accounting data and the replacement of project stock mapping table.

In the quality management process, the Quality Inspection Engine can be eliminated. Only one inspection document is maintained in SAP EWM in SAP S/4HANA instead of working with a quality inspection document and a quality management (QM) inspection lot. It is triggered by an inspection rule.

Simplification

SAP S/4HANA 1610 SAP offers two Warehouse Management Systems.

Simplicity is largely achieved by deactivating components and simplifying the stack.

Discover the full scope and benefits of SAP S/4HANA 1610

And follow me via @SDenecken to stay on top of the latest…

Here the link to Part 4a:

https://blogs.sap.com/2016/12/06/s4hana-1610-use-case-series-4a-warehouse-management-biz-view/

Link to the series:

https://blogs.sap.com/2016/11/09/s4hana-1610-use-case-series-intro/

 

To report this post you need to login first.

11 Comments

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

  1. Joachim Rees

    Hi Sven,

    a litte suggestion to help your readers navigate more easily:

    When you mention a blog, make it a link pointing there!

    In your initial sentence, “In the last blog of this series” you allready do link to the series, my suggestiosn is to also make the “last blog” part a link as well!

    best
    Joachim

    (0) 
  2. Ram Manohar Rebba

    Thanks Sven. This has given me some insight of EWM on S4Hana 1610. I have question.
    1. Do we still need to create a dummy logical system for EWM system or we can even eliminate this step.
    2. if the EWM is directly integrated with S4Hana 1610. Can’t we directly perform Goods Receipt.

    Thanks,
    Ram
    Ram259@gmail.com

    (0) 
  3. Suraj Tatpalliwar

    Hi Ram,

    we have removed data  Data Redundancy and CIF is removed. but we still have qrfc as we ware having earlier.. its is just like EWM add on option before. but now its embeded and also reduce duplicate transectinal documents.

    (0) 
  4. Ashim Chowdhury

    Hi Sven,

    My question is related to the Quality Management process where you have mentioned that in S/4 HANA 1610 we don’t need QIE for doing the inspection. So in EWM in S/4 HANA the inspection rule will have the material master inspection set-up (assigning relevant inspection type to material master) ? All the quality process like results recording, UD and stock posting can be with the single inspection document created in EWM and no need to have any inspection lot?

     

    Is there any document/blog where this explained in details including the config and data set-up?

     

    (0) 
  5. Sangeeta Majumdar

    Currently we have a SAP LE – TRM ( Task and Resource Management ) solution in my customer ECC system . In the Compatibility Pack scope – I do NOT see any mention of the sub module Task & Resource Management and also these configuration nodes do not exist in S4 HANA 1511 or 1610 SPRO. So does this mean that a customer who is using ECC LE Task & Resource Management will not be covered under the Compatibility Pack ??

    In such a case, the way forward for them on the S4 journey will be to move to SAP EWM only ?

    Customer is also using Cross Docking as part of LE-WM . So for this functionality to work in the S4 HANA box, he cannot use this as part of compatibity scope – is that correct ? and he will have to get a license for SAP EWM as well – as it is part of Advanced WM features .

     

    Please suggest. Thanks.

    (0) 
  6. shivakkumar Geetha venkatesan

    Hi Sven,

     

    I am having one Question related to WM/EWM. do SAP withdraw WM support ? means when ? will SAP EWM on S/4 HANA will easily communicate/Interact with DCS- Distributed control systems, SCADA – superviosry control and data Acquisition system. I know EWM can by default speak with PLC. but if my client wants to connect EWM to PLC- programmable logic controller then to DCS. where main control over the plant is through DCS and PLC is for field level control or specific device control..etc.. how can we achieve this.. please furnish details..

    Regards,

    G.V.Shivakkumar

    (0) 

Leave a Reply