on 2020 Oct 23 1:36 AM
Hi there,
At our end, we are seeing cases where when an event is reported for a freight unit in EM, it shows up twice on the FU in TM.(Same for freight orders and freight bookings as well). For the FU in TM, in the 'Execution' tab, we see one line saying source of execution information as 'Propagated from SAP EM' and the other line for the same event says 'Read from SAP EM'. Why might this be happening? How should we resolve this so that we only see the reported event in EM only once in TM and not twice? How should we avoid this event duplication?
I checked the meaning of 'Read from SAP EM' and couldn't find much except that it shows when the event is available in EM but not in TM. But in our case, we have it available in both TM and EM.
Thanks in advance!
Akshat
Request clarification before answering.
Also look at Freight Unit Type and setting in "Execution Track. Relevance" - set to be tracked with SAP EM and verify that the “Execution Tracking Relevance” setting is set to “Execution Tracking with External Event Management”
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes - that is the setting
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a fundamental misalignment with your SAP TM / EM approach. You either:
1) Leverage EM to capture events in which case TM uses "Read from SAP EM" - i.e. no EM events are propagated to TM but TM "reads" the events and displays them in the execution tab
2) Leverage TM to house events in which case TM uses "Propagated from SAP EM" - i.e. Any events captured in TM will be sent to SAP EM and any events captured in SAP EM will be "propagated" / sent to TM via the rule set
This is approach is configured in the FU / FO type so make sure that you choose 1 and then synch up the needed behavior in EM to reflect either sending / propagating events to TM or not.
Make sense?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Akshat ,
Assuming that you are able to see only 1 event message "In Transit" in EM WebUI & 2 event message "In Transit" at FU level.
Can you confirm if both the messages are same , I mean no difference of partners or location for both these messages which is seen at FU in TM. If there is no difference ideally message will be overwritten & not duplicated.
Any multiple tracking ID configuration that is done at EM to report event at multiple event handler?
Can you try to check the object class CL_TOR_A_PROP_EXEC_INF for the method PROPAGATE_EXEC_FROM_SUCC or PROPAGATE_EXEC_FROM_PRED as to why the event is getting duplicated?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Akshat ,
Standard SAP behavior when you report an event at freight booking is that it will be propagated to the corresponding freight units as well or vice versa but there will not be any duplication. If you don't want the propagation to happen to predecessor or successor documents then, there is a configuration at freight booking/order document type which has the - Display Mode for Execution Tab, you can set the actual events & expected events from EM , this can help as propagation between TM document will stop.
In case you are reporting event from TM , then check if the event type is configured to sent the reported event from TM to EM.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Arun,
The duplication happens when events are reported on FUs/FOs/FBs in EM. Say for example, I report "In Transit" on a FU in EM, it is duplicated on the FU in TM--One saying "Propagated from SAP EM" and the other saying "Read from SAP EM". I don't want the propagation of events between documents to stop. I want the duplication seen on the FUs/FOs/FBs in TM when events are reported in EM to stop.
| User | Count |
|---|---|
| 17 | |
| 16 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.