Summary
Standard propagation of events from freight booking or freight order to relevant freight units can only happen for events – with STOP category specified as inbound or outbound. For events which can not be categorized as Inbound or Outbound, needs to be manually propagated to relevant freight units if required.
This document gives approach to handle manual propagation of events to predecessor documents in this case.
Add parameter FU (Freight Unit) to FB (Freight Booking) / FO (Freight Order) event handler.
Step 1 – Enhance Parameter extractors
It is required to get data of related FU for Freight Booking / Freight Order event handler.
Below coding can guide for specific approach.
CALL METHOD lr_srvmgr_tor->retrieve_by_association
EXPORTING
iv_node_key = /scmtms/if_tor_c=>sc_node-root
it_key = li_root_key
iv_association = /scmtms/if_tor_c=>sc_association-root-assigned_fus
iv_fill_data = abap_true
IMPORTING
et_data = li_fu.
Step 2 – Complete parameter setting in SAP EM.
Please note that parameter name is to be used as ‘Tracking ID Code set’. So, it should be same as FU tracking ID code set.
Also, map this parameter name to the parameter coming from TM system.
With this setting, when you assign FUs to FB/FO, this parameter will be automatically extracted and sent to corresponding TM system.
Add rule set assigned to FB/FO event handler
To route event to another event handler (FU in our case), SAP has provided two options as below.
FU /SAPTRX/RESEND
____________________________________________________
Short Text
Resend an Event Message to another Event Handler
Functionality
This function module resends an event message with a different tracking ID/tracking ID code set, that is, those that you specify in parameter-1 and parameter-2. If you want to resend the event message with a different internal event code, specify this code in parameter-3. Note that the system takes all information about an event, for example, event time, from the current event handler.
Parameter-1: Tracking ID code set. Enter a value or a metadata tag.
Parameter-2: Tracking ID. Enter a value or a metadata tag.
Parameter-3: Internal event code. Enter a value or a metadata tag.
Return code:
0 - Event message was resent successfully
2 - Event message could not be sent
3 - Event message was previously sent to the tracking ID code set/ tracking ID specified in the parameters
4 - One or more parameters are missing
FU /SAPTRX/RESEND_MULTIPLE
____________________________________________________
Short Text
Resend an Event Message to Multiple Event Handlers
Functionality
This function module resends an event message to multiple event handlers on the basis of the control or info parameter data contained in the current event handler. You must ensure that the control or info parameter data that you want to resend to other event handlers is stored in the current event handler with the same tracking ID code set as the event handlers to which you want to resend the event message.
If you want to resend the event message with a different internal event code, specify this code in parameter-3. Note that the system takes all information about an event, for example, event time, from the current event handler.
This function module can only be used in rule activities.
Parameter-1: Parameter name (the tracking ID code set of the event handlers to which you want to resend the event message). Enter a value or a metadata tag.
Parameter-2: Enter the parameter type, choosing one of the following:
C - Control parameter
I - Info parameter
Parameter-3: Internal event code. Enter a value or a metadata tag.
Return code:
0 - Event message was resent successfully
2 - Control or info parameter data not available
4 - One or more parameters are missing
We should use FU /SAPTRX/RESEND_MULTIPLE, since there will be multiple FUs assigned to single FB/FO.
Add rule set task with parameters as below.
Parameter name – FU will be replace tracking ID code set.
Parameter type – C will indicate that event handler details to be extracted from control parameter mentioned in event handler.
Internal event code – can be same or different, based on business requirement.
Conclusion
So, whenever specific event is reported for freight order/freight booking, it gets propagated to all freight units assigned to it.
