cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Transportation Management Events link

0 Likes
551

Dear all

We are trying to make a report to show the events expected and reported and unexpected.
We are facing a problem with some events that supposily are expected and reported, but the join we are using is not working and as a consequence, appear unexpected.
What we are doing is:
joining "/SAPTRX/EH_EXPEV" and "/SAPTRX/EH_EVMSG"
by EH_GUID, EVENT_CODE and MSG_GUID
The ones we are not able to match have these 2 differences:
- the field MATCHED_EE is blank
- the field NOT_RELEVANT is X Do you know if we are doing anything wrong?
Do you know how this not_relevant field can be populated as X? Thanks!

Accepted Solutions (0)

Answers (3)

Answers (3)

butschbacher
Explorer
0 Likes

Hello Juan,

i have no TM system to check this. Did you sent the Events from TM? I'm not sure if they really check the status from EM. Best would be to open a ticket at SAP and ask why the display is different.

Best regards,

Steffen

0 Likes

Thank you so much for your answers Steffen, they have been really of great help, we know why the events are flagged as not relevant now and will take action on this.

Have a nice day and thanks again,

Juan

butschbacher
Explorer
0 Likes

Hello Juan,

do you check Location, Partner or Data Code Set for your EEs?

If then e.g. the Location in the Event does not match the Location in the EE the event is not processed and would also get irrelevant.


Best regards,
Steffen

0 Likes

Dear Stephen, thanks a lot, I really appreciate your help. You are right, the location was different, and that is why the events are marked as not relevant. But in the application, if we go to the FO - Execution tab, we can see that the event has a green bullet on the left.

Does it mean that even if all events are not-relevant, the event can appear as reported?

butschbacher
Explorer
0 Likes

Hello Juan,

not relevant means that the Event was not processed.

This happens e.g. if you send an Event for an EE twice. The second one is then ignored and marked as not relevant. You can customize your EE profile to allow processing multiple events for an EE.

Best regards,

Steffen

0 Likes

Thanks so much Steffen.

This explains cases when there are more then one occurrence for same event and one of them is set as irrelevant.

But... what happens if all the reported events for one PO/expected event are marked as not relevant?

We have cases like this in our DB. In those cases joining "/SAPTRX/EH_EXPEV" and "/SAPTRX/EH_EVMSG" by EH_GUID, EVENT_CODE and MSG_GUID is not feasible since MSG_GUID is empty in "/SAPTRX/EH_EXPEV".