Tracked Process 
A Tracked Process is a representation of a business process that is to be tracked.
Technical Data
Entity Type |
Business Object |
Software Component Version |
ESM SCEMSRV 7.01 |
TrackedProcess |
Business Context and Use
The Tracked Process business object enables business processes or objects to be tracked. A tracked process can represent the following:
A business process, such as a purchasing, logistics, or supply change process
A real or logical business object, such as a parcel that is posted or a purchase order that is created
A tracked process enables the expected process and sequence of events that apply to the process or object to be defined. The resulting tracked process can then be monitored, based on defined events.
A tracked process is defined by a unique identifier called an application object ID. In a purchasing scenario, a purchase order number, or a combination of purchase order and line item number, is identified by a tracking ID. A supplementary tracking ID can also be used.
In order to create and update a tracked process, a range of reference data must be defined in the back-end system as follows:
Scenarios
Events
Event profiles
Attributes
Tracking data
Status
Scenarios
The expected rules and events for the tracked process are established and defined in a business scenario, which represents the actual business process. For example, a purchasing, sales, or supply chain process.
EventsEvents depend on the business scenario and can be expected (regular), unexpected or overdue. For example, in a purchasing 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
Each event in a tracked process is uniquely identified by an event code, location and partner data. Location and partner data are also needed as the same event code can be used several times in a process.
Event profilesWhen a tracked process is created, due dates or times of expected events are determined based on the expected event profile in the back-end system. For example, an event profile defines that an order acknowledgement is expected five working days after the purchase order creation date.
AttributesEvents
Events depend on the business scenario and can be expected (regular), unexpected or overdue. For example, in a purchasing 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
Each event in a tracked process is uniquely identified by an event code, location and partner data. Location and partner data are also needed as the same event code can be used several times in a process.
Event profilesWhen a tracked process is created, due dates or times of expected events are determined based on the expected event profile in the back-end system. For example, an event profile defines that an order acknowledgement is expected five working days after the purchase order creation date.
AttributesAttributes are used to control events in the tracked process or simply to provide information. Attributes can include details such as reference numbers, order numbers, supplier and delivery address information, e-mail addresses, URLs and so on.
Tracking dataTracking data is required to report on events and are created with the tracked process. For example, in a procurement process, tracking data can refer to the purchase order number or a combination of purchase order and line item number.
Event profiles
When a tracked process is created, due dates or times of expected events are determined based on the expected event profile in the back-end system. For example, an event profile defines that an order acknowledgement is expected five working days after the purchase order creation date.
AttributesAttributes are used to control events in the tracked process or simply to provide information. Attributes can include details such as reference numbers, order numbers, supplier and delivery address information, e-mail addresses, URLs and so on.
Tracking dataTracking data is required to report on events and are created with the tracked process. For example, in a procurement process, tracking data can refer to the purchase order number or a combination of purchase order and line item number.
Attributes
Attributes are used to control events in the tracked process or simply to provide information. Attributes can include details such as reference numbers, order numbers, supplier and delivery address information, e-mail addresses, URLs and so on.
Tracking dataTracking data is required to report on events and are created with the tracked process. For example, in a procurement process, tracking data can refer to the purchase order number or a combination of purchase order and line item number.
Tracking data
Tracking data is required to report on events and are created with the tracked process. For example, in a procurement process, tracking data can refer to the purchase order number or a combination of purchase order and line item number.
Notes on SAP Implementation
The Tracked Process business object represents the data and reference values that are used in SAP Event Management. In particular, a tracked process corresponds to an event-handler in SAP Event Management.
This means that the master data and Customizing settings that relate to event-handlers affect the attributes and behaviour of tracked processes within the Tracked Processes business object.
A tracked process 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.
You have authorization to use the event-handler, 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.
In order to create and update a tracked process, a range of reference data must be defined in SAP Event Management, including the following:
Scenarios
Events
Event profiles
Attributes
Tracking data
Status
When this reference data is in place, tracked processes can be created, investigated, changed, and monitored.
Before implementing the Tracked Process business object, we strongly recommend that you are familiar with the process being tracked and the associated Customizing settings in SAP Event Management.
More Information
For more information about tracked processes and their use, see the SAP Library documentation for SAP Event Management at http://help.sap.com . Search for the topics Event Handler , Event , Tracking ID , Application Object , and SAP Event Management Infrastructure .For more information about monitoring events in a tracked process, see Tracked Process Event Notification business object.