Skip to end of metadata
Go to start of metadata

The Business Event Handling for Process Tracking ES bundle can be used to create, update and retrieve detailed information about tracked processes in SAP Event Management (SAP EM) and thus allows tracking and monitoring of collaborative supply chain processes.

A service is available for creating Tracked Process Event Notifications and sending them to SAP EM to change the state of a tracked process.

Customizations in SAP EM define which business processes and/or real-world or logical objects are tracked and which events can occur during the execution of those business processes or the lifetime of a real-world or logical object.


The Handling of Business Events for Process Tracking ES bundle can be deployed in virtually all business scenarios involving an SCEM product for providing visibility and tracking.

This ES bundle is valuable to all businesses interested in simplifying or extending the usage of SAP EM, for example, using custom-made user interfaces or by connecting the application with other software. Partners and customers could take advantage of the enterprise services in building scenarios with less effort and time.

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

How to Use This ES Bundle

Customers planning to deploy this ES bundle will easily be able to integrate the services into an existing interface or create a new one using SAP NetWeaver Process Integration (SAP NetWeaver PI) or similar tools.

This section will explore a series of use cases for the Business Event Handling for Process Tracking ES bundle. Each scenario will show how different outcomes can be achieved by using the enterprise services in different combinations. While these examples illustrate some 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. The use cases sometimes refer to users in various roles using enterprise services and business objects. The use cases are written this way to illustrate the logical flow of the services; in actuality, end users access the enterprise services through an interface and the business objects and enterprise services are working behind the scenes. Please note that this wiki is also a space for you to share knowledge and collaborate with others who are implementing the ES bundle, so please come back and share your experiences with this bundle after implementing it.

Use Case 1: Mobile UI for Truck Driver

An automotive supplier wants to keep track of the fulfillment of his deliveries to customers. Therefore, his logistics service provider has agreed to report some significant milestones when shipping the goods. The truck drivers have been equipped with mobile devices allowing for online connections to the supplier's SAP EM system. For each shipment to be tracked, the supplier application system requests the creation of process to be tracked in the SAP EM system by calling the enterprise service Maintain Tracked Process. By using the enterprise service Find Tracked Process by Elements in combination with enterprise service Read Tracked Process, details on those shipments that are assigned to the specific truck driver can be retrieved and put together in a work list. The truck driver can select the current one at a loading point and report the loading event with the help of enterprise service Create Tracked Process Event Notification.

Use Case 2: Batch Recall Scenario

A supplier finds out that there is a serious quality issue with a specific batch he had produced and already shipped to a customer. He informs his customer via a phone call that the batch needs to be recalled. In the supplier system landscape, the status of all deliveries is monitored with the help of enterprise service Maintain Tracked Process and enterprise service Create Tracked Process Event Notification, which had been reported by the involved parties. The customer's material manager checks in his ERP system to identify the defective batch (production, stock, or direct delivery). For those deliveries that are affected either directly or indirectly, the material manager can find out the status and location of the deliveries using the enterprise service Find Tracked Process by Elements in combination with enterprise service Read Tracked Process. Based on that, he can get in touch with the appropriate people to further drive the batch recall.

Future Directions

Future enterprise service development in the Business Event Handling for Process Tracking ES bundle could provide more options for configuring the tracked processes in the Supply Chain.


You can help improve this ES bundle by adding details about connectivity.

System Requirements

The services described in this bundle are available with any of the systems mentioned below:

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

SOA Homepage on SDN