Hey Sandeep,
In general the application object type (AOT) determines the data that is handed over to SAP Event Management (planned events, parameters, IDs), when the data is sent to SAP EM and the SAP EM system where the Event Handler is created.
The AOT number identifies this application object. So as an example it can be the number of a purchase order if you want to track on purchase order header level or a concatenated number of purchase order header and purchase order item number if you want to track on item level. Other examples are e.g. sales orders, shipments or parcel numbers.
Furthermore the AOT number together with the application object type and the application system provide a unique identification for an event handler.
Tracking IDs (and tracking ID code sets) are used for sending Event Messages and identifying all Event Handlers the Event Messages belongs to. So in some cases this can be the same number as the AOT number. But you can also add multiple Tracking IDs to an Event Handler.
Just a few examples:
- Ten Event Handlers are created on Purchase Order item level (meaning you have ten items). As tracking ID the Purchase Order header number and the concatenated header and item number are used. Now a relevant event is reported which happens on header level and is
therefore relevant for all your Event Handlers. So instead of sending ten Event Messages you just send one Event Messages using the Purchase Order header number - For this Purchase Order an Inbound Delivery is created. So you want also track this document. So you can easily add the Tracking ID to an Event Handler using an Event Message and activities in the rule set. Now you can also report relevant events against this Event Handler from your Inbound Delivery
Hope this makes it clear for you
Best regards
Berthold
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.