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.
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/
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/4HANASimilarly, 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.
- SAP Warehouse Management (WM) application, which was first introduced as a submodule of the Materials Management application within SAP R/3, that is part of the compatibility scope (check note 2269324 - Compatibility Scope Matrix for SAP S/4HANA, on-premise edition and simplification list)
- SAP Extended Warehouse Management (EWM), which was developed as a component of SAP Supply Chain Management and now comes integrated in SAP S/4HANA
Simplicity is largely achieved by deactivating components and simplifying the stack.
Discover the full scope and benefits of SAP S/4HANA 1610
- SAP S/4HANA 1610 Release Highlights Brochure
- SAP S/4HANA 1610 Release Information
- Discover SAP S/4HANA
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/
- SAP Managed Tags:
11 Comments
