Marco Freischlag wrote a great article entitled “SAP Event Management – How to use Multiple Tracking IDs” (Marco Freischlag, 2013). His article describes how to post an event using several Tracking IDs. Until SP4 for SAP Event Management 9.0, (or by implementing OSS note 1917245), it was only possibly to post an event to a single tracking ID.
There are alternative ways to achieve the same outcome but this option is now available for architects of SAP Event Management solutions to use. The most common way is to leverage different tracking IDs across the event handlers in order to have the events post to the needed EHs. Putting together the SAP EM Interface Diagram (a part of our Reveal oVo(C) Implementation Methodology for SAP EM) is critical to the understanding of how the various EHs relate to, and interact with the different EHs. An example of the Reveal SAP EM Interface Diagram is shown below.
An example application of the functionality described in Marco’s document is summarized below for reference:
- A SAP Transportation Management freight order has several railcars assigned to it
- When the ARRIVAL event comes in for the freight order it needs to be propagated to all the associated railcars so that they, too, may receive the ARRIVAL event
In order to achieve this, using this technique, we would send an ARRIVAL event using TRXID = <dummy value> with an entry in the ‘Further References’ table for each of the related railcars filling in REFID = Railcar TRXID and REFUSAGE = ‘M’.
Note: If the Resource Tracking Scenario is used, consider the following SAP Note: 1930447 – Table Index for /SAPTRX/EVM_REF for Resource Tracking in order to avoid performance issues. For the details around configuring this functionality please refer to Marco’s document.
 Document: SAP EM – How to use Multiple Tracking IDs written by Marco Freischlag (11/2/2013)