Show TOC

 Tracked Process Event Notification Locate this document in the navigation structure

 

Definition: A Tracked Process Event Notification is the reported information about an event that occurred in a business process that is to be tracked. Comment: Events can be of the type expected or unexpected. Usage: A Tracked Process Event Notification is usually created during the execution of a business process that is to be tracked.

Technical Data

Entity Type

Business Object

Software Component Version

ESM SCEMSRV 7.01

Technical Name

TrackedProcessEventNotification

Object Category

Business Process Object

Business Context and Use

The Tracked Process Event Notification business object enables events in a tracked process to be monitored and reported.

A tracked process enables the expected process and sequence of events that apply to a process or object to be defined.  The resulting tracked process can then be monitored, based on defined events.  Event information and processing rules are saved in the associated tracked process. Event notifications trigger follow-up activities like status changes, alerts, e-mail sending, updates to external systems, changes to dependant expected events, starting workflows and so on.  Each event is assigned a unique event code, location and partner data.

Within a supply chain process, employees and business partners confirm actual events; these events are based on the defined events for a tracked process. Events can be expected, unexpected, or overdue.

Expected events occur consistently for a business process. In a procurement scenario, expected events can include the following:

  • Purchase order creation

  • Order acknowledgement

  • Advanced shipping notification

  • Goods receipt

  • Evaluated receipt settlement (ERS) or invoice verification

  • Payment

Unexpected events do not occur consistently and are usually not desirable. However, unexpected events can feasibly occur and may have a significant impact on the business process. In a procurement scenario, unexpected events can include the following:

  • Acknowledgement received with changes

  • Shipment delay

  • Quantity change

  • Delivery quantity change

  • Due date change

  • Delivery date change

Events are reported as follows:

  • For expected events, the tracking ID, event code, location and partner data are used by the back-end system to find the corresponding expected event of the tracked process.  

  • For unexpected events, the tracking ID is used by the back-end system to find the corresponding tracked process.

Notes on SAP Implementation

The Tracked Process Event Notification business object represents the data and reference values that are used in SAP Event Management.  In particular, a tracked process event notification corresponds to an event message in SAP Event Management.This means that the master data and Customizing settings that relate to event messages affect the attributes and behavior of tracked process event notification within the Tracked Process Event Notification business object.

A tracked process event notification can only be created if all required Customizing activities have been completed in the back-end system. In the back-end system, the following prerequisites are required:

  • SAP Event Management is in use and all associated Customizing activities have been completed.

  • The relevant tracked process business object is available and active in SAP Event Management.

  • You have authorization to use event messages, and therefore can use the operations in this business object.

  • Other systems that are relevant to the business scenario are also in use. For example, in a procurement scenario, SAP ERP is required.

More Information

For more information about tracked process event notifications and their use, see the SAP Library documentation for SAP Event Management at http://help.sap.com .  Search for the topics Events and Event Handlers .For more information about tracked processes, see the Tracked Process business object.