Duplicate event

[petra_just]

Hi experts,

this morning, we tested the Z-READY-FOR-PU Event. It is posting duplicate events with the app and ist posting one event with the sequence testing of BAPI /SAPTRX/BAPI_EH_ADDEVENTMSG_02 and BAPI_TRANSACTION_COMMIT. See screenshots. The difference with the app is that the "second" Event has no Location. What could be the reason that the Location is blank when posting with the app (2nd time)?

WRONG (with app)

CORRECT with test sequence

Thanks so much in advance. Its highly appreciated. Points will be rewarded quickly.

Petra

[Former Member · Accepted solution]

Hi Petra,

this structure of the BAPI must be filled for Location when you send the message via the app:

At least these two fields depending on your EE:

EVTCNT is the reference to the header entry.

Best regards,

Steffen

[Former Member]

Hi Petra,

I am guessing duplicate is being generated from "Event Type" config on Application System side ( TM ).

When you post an event on EM, it is propagated to TM which again hits the Event Types config. If there are no checks to handle the propagated events from EM, this event will be sent to EM.

To make sure if this assumption is correct, check the SNDNAM field in /SAPTRX/EVM_HDR and see if one is from your APP and one from TM.

If it's true, then make sure your event type has some checks to avoid this scenario.

Maybe some thing like if <fs_tor_execinfo>-execinfo_source eq 'A' then send events to EM. 'A' means directly reported on TM.

Thanks,

Vish

[petra_just]

Vishnu,

thx for your advise and sorry for the late reply. I have checked the Header table and found that there is only one message with Sender id for the Pick-up Event.

I have asked our app developper to fill the SNDID systematically. The other Event Z-CREATE-FO has several Messages, but I think, they all stem from the app. I will mark your advise as usefull as it helps to fill the Sender id.

For the time being, I am not sure how I can Change the Event type customizing. I open other Messages for this as it is not really related to this one.

Thanks a lot again. Your help is appreciated.

Petra

[Former Member]

Hi Petra,

It's SNDNAM field. You can use SNDID as well but use the same field in ruleset for TM check.

Thanks,

Vishnu

[Former Member]

Hi Petra,

Go to this link http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80348432-1282-3210-c2b7-f9339d8db...

Page12- you can directly debug SAP TM function module /SAPTRX/TMS_CHANGE_EXEC_INF "lv_in_background"“ in the debugger from ‘X’ to ‘ ‘ to have a direct synchronous call to the TM system.

Can you tell me what you mean "app"? Is it from SAP EM to SAP TM? or Third party application to SAP EM -> SAP TM.

Regards

GGOPII

[petra_just]

3rd Party application (mobile app) that Posts em Events.

[Former Member]

I think you should compare the messages (send with the app and directly with the BAPI) in transaction /SAPTRX/EVM_STATUS.

Compare the header especially Sender Name, ID etc. and the Location Fields.

If there are any difference we can check what went different in the system.

Best regards,

Steffen

[petra_just]

Steffen,

thx for the advise. we have added the Sender to the message as "APP" and now we can see in Transaction /SAPTRX/EVM_STATUS where the message is coming from. But, we receive only one message. For ready for Pick-up, we fill the Location and now we have only one message (thx, this was ur previous advise). For message load-end, we still have 2 Messages, one propagated from EM, one read from EM (although I have changed the customizing).

[Former Member]

Hi Petra,

according to your screenshots Load_End was first reported in EM and the 4 seconds later in TM.

The second one is not propagated from EM but Reported Directly for this Document. So this looks different then the case with the Pick_Up.

Are these Events Expected or Unexpected Events?

Best regards,

Steffen

[petra_just]

These are unexpected Events.