In my first blog on the topic we described the SAP Event Management (EM) Application Interface in SAP TM - This provides the ability to configure the EM interface from within SAP TM. In this blog we will show the SAP TM components that require some configuration in order to trigger the SAP EM Application Interface.
After the DOA, BPT, AOT and Event Type configuration is in place (see part 1) the SAP TM Application Interface with SAP EM is complete. The integration will still not be functional until the following SAP EM related configuration is completed in the standard SAP TM configuration objects.
Freight Unit Type
In the IMG select: SAP Transportation Management > Transportation Management > Planning > Freight Unit > Define Freight Unit Types
Select the applicable Freight Unit Type to be tracked with SAP EM and verify that the “Execution Tracking Relevance” setting is set to “Execution Tracking with External Event Management” (See above figure).
Select either “Standard Propagation” or “Enhanced Propagation” for Execution Propagation Mode. If Execution Propagation Mode is set to "Enhanced Propagation” instead of “Standard Propagation,” and several freight units are part of the freight order or forwarding order, the system will wait until the event is posted on the last freight unit before populating the freight order or forwarding order. For example, several rail cars will comprise a shipment to one customer. The rail cars will be loaded with methane one at a time. The event, LOADING END, indicates the first rail car is full and is being moved to another track. When this event updates the status of the freight unit, and Execution Propagation Mode is set to “Standard Propagation,” the freight unit and freight order will both be updated with the event. If Execution Propagation Mode is set to “Enhanced Propagation,” the freight unit of each rail car will be populated with LOADING END as each car is filled. Not until the last rail car leaves the loading position will the freight order be populated with the event LOADING END.
If the checkbox “Propagate Execution Info” in the Customizing activities for Defining Freight Order Types, Freight Booking Types and Transportation Unit Types has been set, note that this will not propagate execution events to predecessor documents. Set the propagation mode to the same value for all freight documents that are related to each other in execution tracking.
Set the entry “Application Object Type” to ODT30_FU as shown in the above figure.
Ensure the entry “Last Expected Event” has the relevant event code that denotes the last event in your execution process. This is typically UNLOAD_END as shown in the above figure.
Freight Order Type
In the IMG select: SAP Transportation Management > Transportation Management > Freight Order Management > Freight Order > Define Freight Order Types
Select the applicable freight order type to be tracked with SAP Event Management and ensure that the “Execution Tracking Relevance” setting is set to “Execution Tracking with External Event Management”
Check “Propagate Execution Info” if the event that is reported for a freight order needs to also propagate the predecessor document (a freight unit in the visibility process).
Ensure the entry “Application Object Type” is set to ODT40_TO.
Ensure the entry “Last Expected Event” has the relevant event code that denotes the last event in the execution process. The last event is typically UNLOAD_END.
Freight Booking Type
In the IMG, select: SAP Transportation Management > Transportation Management > Freight Order Management > Freight Booking > Define Freight Booking Types
Select the applicable Freight Booking Type to be tracked with SAP EM and ensure that the “Execution Tracking Relevance” setting is set to “Execution Tracking with External Event Management.”
Check “Propagate Execution Info” if you want an event that is reported for a freight order propagated to the predecessor document (a freight unit in the visibility process).
Ensure the entry “Application Object Type” is set to ODT40_TO.
Ensure the entry “Last Expected Event” has the relevant event code that denotes the last event in your execution process. The last event is typically UNLOAD_END.
Transportation Unit Type
In the IMG, select: Transportation Management > Planning > Transportation Unit > Define Transportation Unit Types
Select the applicable Transportation Unit Type to be tracked with SAP EM and ensure that the “Execution Tracking Relevance” setting is set to “Execution Tracking with External Event Management”
Check “Propagate Execution Info” if you want an event that is reported for a freight order propagated to the predecessor document (a freight unit in the visibility process).
Ensure the entry “Application Object Type” is set to ODT30_TU.
Ensure the entry “Last Expected Event” has the relevant event code that denotes the last event in your execution process, e.g. DECOUPLING.
Output Management
The Post Processing Framework (PPF) is used to trigger the communication from SAP Transportation Management to SAP Event Management. The output management adapter needs to be maintained for this communication to work. This procedure covers the configuration required for objects freight unit, transportation unit, transportation order and booking order:
In the IMG, go to node Cross-Application Components > Processes and Tools for Enterprise Applications > Reusable Objects and Functions for BOPF Environment > PPF Adapter for Output Management > Maintain Output Management Adapter Settings
Choose the dialog structure Direct Output Agents (w/o PPF & w/o History).
For the Transportation Order (Freight Unit / Order, Booking Order): Select the following entry and enable it:
Business object: /SCMTMS/TOR
Node: ROOT
Agent name: SEND_EM_DATA_FROM_TOR
Output type: Recommended output type is “Has Uncritical o/p Process after Commit (background)”
Choose the dialog structure “Nodes for Before Image”
Create entries for the following sub nodes of node ROOT of Business Object /SCMTMS/TOR: EXECUTIONINFORMATION, ITEM_TR, STOP
For the Instruction: Select the following entry and enable it:
Business object: /SCMTMS/INSTRUCTION
Node: INSTRUCTIONS
Agent name: EM_DATA_FROM_INS
Output type: Recommended output type is “Has Uncritical o/p Process after Commit (background)”
Change Notification Agent (CNA)
For Resource Tracking Visibility, the Resource Master data is extracted using the Change Notification Agent (CNA) functionality within SAP Transportation Management.
To maintain the CNA, perform the following IMG activities:
Choose: SAP Transportation Management > SCM Basis > Master Data > Change Notification Agent > Maintain Change Notification Agent
Select Applications and App. ID “TM_EM_RES”
Navigate to “Assign Applications to Objects”
Check the Active / Inactive Box for the “TM_EM_RES” Application and Object ID “RES_H.”
Ensure that the following are checked: New, Deleted, BIMG Relevant
Note: Only resources where the “Relevant for Event Management” flag is set, are considered.
Cross-Reference between TM and EM
Table /SAPTRX/AOTREF is available in SAP Transportation Management. This table stores the relationship between the SAP Transportation Management object (application object identified by the application object ID) and the corresponding SAP Event Management event handler GUID.
In my next blog I'll be running through SAP TM operations as it relates to the integration with SAP EM.