EWM – MES Direct Integration for Receiving HUs in EWM

SAP MES (Manufacturing Execution System) is a software solution that helps manufacturers plan, execute and monitor their production activities in real-time. It is designed to support the entire production process, from raw material sourcing and production planning to quality control and shipping.

SAP EWM (Extended Warehouse Management) and SAP MES can be directly integrated to support the information flow between the warehouse and the production field. One important aspect of EWM is the ability to receive and track handling units (HUs) as they enter the warehouse.

Benefits of integrating EWM with MES for receiving HUs

• One of the main benefits is improved accuracy and traceability. By integrating the two systems, it is possible to capture real-time data on HU movement and location, which can be used to track and trace HUs throughout the warehouse. This information is critical for ensuring that HUs are received and stored in the correct location, as well as for identifying and correcting any issues that may arise during the receiving process.
• Another benefit of EWM-MES integration is increased efficiency. By automating the HU receiving process, it is possible to reduce the number of manual steps involved, which can save time and reduce the risk of errors. In addition, integrating the two systems allows for real-time communication between the warehouse and the production floor, which can help to identify and resolve any issues that may impact the flow of goods.
• A third benefit is improved visibility. By integrating the two systems, it is possible to gain real-time visibility into the status of HUs as they move through the warehouse. This can help to identify bottlenecks and optimize the flow of goods, as well as to improve forecasting and planning.

Source

Ways to implement EWM - MES direct integration for receiving HUs

There are several ways to implement EWM - MES direct integration for receiving HUs in EWM. One common approach is to use an interface or middleware solution that connects the two systems and allows for data exchange. This can be done using APIs (Application Programming Interfaces) or other integration tools, such as an integration platform as a service (iPaaS).

SAP provides a range of APIs (Application Programming Interfaces) that can be used to integrate SAP MES with SAP EWM. Some of the important APIs provided by SAP for this purpose include:

• BAPI (Business Application Programming Interface): BAPIs are a set of predefined APIs that can be used to access and modify data in SAP systems. They can be used to exchange data between SAP MES and SAP EWM and to trigger specific business processes in the SAP systems.
• IDoc (Intermediate Document): IDocs are a standardized format for exchanging data between SAP systems and other systems. They can be used to transfer data such as material and inventory information, production orders, and quality control results between SAP MES and SAP EWM.
• RF (Radio Frequency) API: The RF API is a set of predefined APIs that can be used to access and modify data in SAP EWM using RF devices, such as RFID (Radio-Frequency Identification) scanners and handheld terminals. It can be used to support real-time data capture and material handling operations in the warehouse.
• OData (Open Data Protocol): OData is a standardized protocol for querying and updating data over the web. It can be used to expose SAP data as REST (Representational State Transfer) APIs, which can be accessed and consumed by other systems, such as SAP MES.
• Event-driven architecture (EDA): EDA is a design pattern that enables systems to communicate with each other by sending and receiving events. It can be used to set up real-time communication between SAP MES and SAP EWM and to trigger specific actions in response to specific events.

However; EWM MES integration can also be done with non-SAP systems. Some APIs provided by SAP for this situation are as follows;

• /SCWM/MFG_CONSUME_ITEMS_EXT   Consumption of Goods from Production
• /SCWM/MFG_READ_STOCK_EXT           Stock Information from Production
• /SCWM/MFG_RECEIVE_HUS_EXT          Receive HUs
• /SCWM/MFG_REVERSE_HUS_EXT         Reverse HUs
• /SCWM/MFG_REVERSE_ITEMS_EXT     Consumption Reversal from Production
• /SCWM/MFG_STAGE_EXT                       External Staging Request for Production

These are just a few examples of the APIs that can be used to integrate SAP MES and SAP EWM. The specific APIs that are used will depend on the specific integration requirements and the capabilities of the systems involved.

Another option is to use a pre-built integration solution, such as a pre-configured interface or connector. This can be a faster and simpler option, as it requires less customization and setup. However, it may not offer as much flexibility as a custom interface or middleware solution.

Source

To integrate EWM and MES for the purpose of receiving HUs (Handling Units) in EWM, the following steps may be involved:

1. Define the integration requirements: As with any integration, it is important to define the specific business processes and data flows that need to be supported by the integration. In this case, the requirements may include the ability to transfer HUs from MES to EWM, track the movement and status of HUs in the warehouse, and provide real-time visibility into warehouse operations.
2. Configure the EWM system: The next step is to configure the EWM system to support the integration. This may involve setting up integration points, such as middleware or API (Application Programming Interface) connectors, and configuring data mapping and transformation rules to ensure that data is correctly transferred between the systems.
3. Set up the MES system: The MES system will also need to be configured to support the integration. This could involve setting up work centers, defining production orders, and configuring routing and capacity planning rules.
4. Define the material flow: The material flow between the shop floor and the warehouse will need to be defined and configured in both EWM and MES. This may involve setting up material master records, defining storage locations and bin types, and configuring inventory management rules to ensure that the right materials are available at the right time on the shop floor.
5. Test the integration: After the systems have been configured, it is important to test the integration to ensure that it is functioning correctly. It might involve running test scenarios to verify that data is being transferred correctly and that the integration is meeting the requirements defined in the first step.
6. Go live: Once the integration has been tested and is functioning correctly, it can be deployed in a production environment. This may involve rolling out the integration to all relevant users and making any necessary changes to business processes to support the integration.
7. Monitor and maintain the integration: After the integration has gone live, it is important to monitor it to ensure that it is performing as expected and to identify and resolve any issues that may arise. Regular maintenance and updates may also be required to ensure that the integration continues to support business needs.