Skip to end of metadata
Go to start of metadata

The Integration of External Warehouse Management System ES bundle addresses the exchange of logistics data between SAP ERP and a third-party warehouse management system that resides within the company's system landscape.

This ES bundle enables the exchange of logistics-relevant information like inbound and outbound deliveries and data related to the movement of goods within a tracking system and also offers replication of product, customer, and supplier master data from SAP ERP to the external warehouse management system.
The Integration of External Warehouse Management System ES bundle leverages enterprise SOA by deploying key enterprise service operations to allow SAP ERP to communicate with an external warehouse management system.

Audience

Managers, clerks and system administrators in enterprises with warehouse operations will find this ES bundle of value for direct interaction with installed external warehouse management systems.

For details on Service Operations, Business Objects and Process Components, please check the ES Workplace.


Integration of External Warehouse Management System (click to enlarge)





How To Use This ES Bundle

The Integration of External Warehouse Management System ES bundle provides straightforward communications between SAP ERP and an external warehouse management system using standards-based enterprise services. Besides choreographing the flow of delivery-based messages, users may also incorporate this bundle to exchange information affecting master data and planning data, as well as communicate critical error-handling data.

In the past, organizations have integrated SAP ERP with their external warehouse management systems using older integration methods such as iDocs. Using enterprise service provides an easier and more straightforward method of integration than was previously available. Furthermore, upgrades to SAP ERP or the external warehouse management system will not disturb the integration, something that cannot be said of earlier integration methods.

The following series of use cases for the Integration of External Warehouse Management System ES bundle show how different outcomes can be achieved by using the enterprise services in different combinations. While these examples illustrate a few of the ways that this ES bundle could be used, the intention is to show the flexibility and reusability of these business objects and enterprise service operations so that you will have a clearer understanding of how to best deploy them in your own environment. This wiki is also a space for you to share knowledge and collaborate with others who are implementing the Integration of External Warehouse Management System ES bundle.

Use Case 1: Master Data Replication

Keeping master data up to date is vital in any enterprise. This use case involves replicating data from SAP ERP to the external warehouse management system. A warehouse manager (or other central responsible person for master data management) wants to replicate warehouse-specific product master data, such as product, or general master data, such as customer, or supplier master data, from SAP ERP to an external warehouse management system for further logistics purposes like inbound or outbound processes.

Master Data Replication (click to enlarge)


When the person in charge of changing the product master data (warehouse-specific view) in SAP ERP finishes making the changes, in the background, SAP ERP invokes the Request Material Warehouse Management View Replication enterprise service operation, which uses the Material business object. If the changes relate to a classified packing material (such as a palette), the service operation Request Logistic Unit Basic Data Replication can be invoked instead.

When anyone makes a change to customer master data in SAP ERP, the system automatically invokes the Request Customer Replication enterprise service. Similarly, when supplier master data is added or changed, the system invokes Request Supplier Replication. The data transfer is executed automatically, and the receiver gets an XML file to import into their external warehouse management system.

Step

Enterprise Service Invoked

Step 1: The user replicate product master data from the SAP system to an external system

Request Material Warehouse Management View Replication

Step 2: If the changes relate to a classified packing material, the user replicate logistic unit basic data from the SAP system to an external system

Request Logistic Unit Basic Data Replication

Step 3: The user replicate customer master data from the SAP system to an external system

Request Customer Replication

Step 4: The user replicate supplier master data from the SAP system to an external system

Request Supplier Replication

Use Case 2: Inbound Delivery Processing

An Inbound Delivery is created when all pre-processes are done (in terms of purchasing activities in your enterprise) and the supplier has sent out an Advanced Shipping Notification (ASN) to SAP ERP. SAP ERP replicates the Inbound Delivery business object to an external WMS by invoking Request Inbound Delivery so that the responsible warehouse clerk can compare the physical goods that arrive at the unloading station to a purchase request or other appropriate data.

Inbound Delivery Processing (click to enlarge)


The external warehousing system can send out a confirmation message to confirm the status of handling the received inbound deliveries by using the Change Inbound Delivery based on Inbound Delivery Confirmation Cancel Request enterprise service operation.
If the supplier communicates any changes about inbound deliveries to SAP ERP, this information can be forwarded to the warehouse system by invoking Request Inbound Delivery Change or Request Inbound Delivery Cancellation depending on whether a change or cancellation has been sent.



For more information about additional capabilities related to this use case, please see the connectivity kit for this ES bundle.

Use Case 3: Outbound Delivery Processing

In SAP CRM, once a sales order has been created, SAP CRM tells SAP ERP to create an outbound delivery. This outbound delivery is then communicated to another system for further processing. In general , this system would be SAP SCM (Supply Chain Management). But in this use case, the system to which SAP ERP will pass the outbound delivery is the external warehouse management system, which will then initiate warehouse processes that will result in the delivery of the goods the customer ordered. To pass the Outbound Delivery business object to the external warehouse management system, SAP ERP invokes Request Outbound Delivery, triggering the creation of the outbound delivery in the external WMS for further warehouse-specific tasks like physical picking, packing, and loading. The WMS receives the proper messages and can process them as designed in its system. The external warehouse management system then invokes the Confirm Outbound Delivery based on Outbound Delivery Confirmation Create Request enterprise service operation to send back confirmation that it created and executed the outbound delivery as requested by SAP ERP.

Outbound Delivery Processing (click to enlarge)


For more information about additional capabilities related to this use case, please see the connectivity kit for this ES bundle.

Use Case 4: Goods Movement Processing for Stock Category Transfers

An enterprise needs to perform a stock transfer from one stock category to another, for example, moving some stock to safety stock. A warehouse clerk triggers this action in the WMS system, which creates a goods movement and posts it. When the goods movement is posted, the WMS system invokes Create Goods Movement to send the information about the stock category transfer to SAP ERP. The event can be cancelled by using the cancellation message Cancel Goods Movement instead.

Goods Movement Processing (click to enlarge)

Use Case 5: Preview of Expected Warehouse Volume

Warehouse personnel can better plan their schedule if they have a view into what's coming down the pipeline. What orders will be processed to go out of the warehouse in the near future? What orders will be coming in to the warehouse? The specific details about the orders are less important than the overall volume of incoming and outgoing orders, which is helpful for warehouse personnel to know about to plan their schedules.

Preview of Expected Warehouse Volume (click to enlarge)


In SAP ERP, the enterprise service Notify of Purchase Order Logistics Planning View can be invoked to send information to the external warehouse management system about orders that will be coming into the warehouse. Similarly, the Notify of Sales Order Logistics Planning View sends data about orders that warehouse personnel must fulfill.



Connectivity Kit

Connectivity Kit Available!

A Connectivity Kit is available to help administrators with the details of implementing this ES bundle. See the Connectivity Kits wiki for more information.

System Requirements

End-to-end Processes Where This ES Bundle Is Used

SOA Homepage on SDN

4 Comments

  1. Unknown User (smczise)

    Hello Experts,

    This wiki is really helpful to us as we are exporing the possibilities of integration of external WMS system with our local ECC system. However, I have hit a road block and would appreciate any help from you guys.

    I am trying the Outbound Delivery processing, so after an Outbound Delivery document is created on SAP side, I am hoping to process this Outbound Delivery (OD) in ext WMS system. After the WMS system has processed the OD, it invokes an ES on the ECC system to notify the completion of processing of OD. The ES that I am making use of is OutboundDeliveryERPChangeRequestConfirmation_In which is present on SAP's HU2 ECC system. While trying to test this ES from WebService Navigator, I am getting the following error:

     CX_GDT_CONVERSION:Exception CX_SOAP_ROOT occurred (program: CL_SOAP_RUNTIME_ROOT==========CP, include: CL_SOAP_RUNTIME_ROOT==========CM004, line: 110)..An exception with the type CX_GDT_CONVERSION occurred, but was neither handled locally, nor declared in a RAISING clause.An error occurred during conversion between XML format and the SAP internal format

    Because of the above error I am unable to proceed with my scenario, if any one has any idea of how to resolve the above problem then please share.

    Regards,

    Shailesh

  2. Former Member

    Dear Shailesh,

     The error description above points to a conversion error in the SOAP runtime, i.e. some input parameters do not follow the schema restrictions. This could be the case e.g. if mandatory fields are omitted or the corresponding data types as described in the Global Data Type (GDT) catalog are not followed. If the problem persists, please open a OSS ticket. The OSS would be the right platform to continue the error analysis.

    Best regards,

    Claudius

  3. Unknown User (ua6gqt4)

    Hello,

    The details provided in the bundle are very helpful.

    However could you please give more information in the scenario where external warehouse management systems are not sophisticated enough to communicate with Webservicesexposed by PI are there any connectivity kits which can be deployed at external warehouse systems to enable this or how exactly this kit can be leveraged in the scenario mentioned above.

    Regards,

    Girish

  4. Hello

    anybody who can share experiences with the ES Bundle Integration of External Warehouse Management Systemand the usage of its Enterprise Services "Confirm Goods Movement_V1" or "Confirm Goods Movement" ?

    As far as I understood these ES can be used for goods movements out of the ERP System.
    Is it really possible to use these ES while creating an goods movement with Transaction MIGO ??

    As far as I know it is only possible to send Transport Orders with WMTORD IDOCS out of SAP to externa Systems (!!) without any custom coding (!!) . Using instead an WMBXY message type (IDOC WMBIDO02) is only for inbound IDOC processing. If using this Standard IDOC for outbound IDOC processing the only way is implementing the BADI called while perfoming the TA MIGO. Correct?

    Any experiences either with the ES Bundle or the IDOC goods movement out of SAP ERP are welcome.

    Kind regards,
    Dries