LOAD_EVENT does not update standard statuses

[petra_just]

hi experts,

when posting the Standard Event LOAD_END using Fm /SAPTRX/BAPI_EH_ADDEVENTMSG_02,, the Event is posted correctly against the expected Event in the FU, but the execution Status is not updated. Also, the Event is not propagated to the related freight order.

[petra_just · Accepted solution]

have run the Trigger Report /SCMTMS/PROCESS_TRIGGER_BGD, but no effect. But, when I select the same Event and choose "Report Event", all updates happen as they should be.

What field in the BAPI do I have to fill, so that this "Report Event" is done in Background while posting automatically?

[former_member186607 · Accepted solution]

Hi Petra,

for me this sounds as if the propagation from EM to TM did not happen. In this case you will still be able to see "green status" for the expected event in TM execution tab - but the execution info is read from SAP EM and not persisted in SAP TM. Can you check this? -> field "Source of Exec. Information" on the TM execution tab.

If this is the case this can have several root causes. have you already checked the TM inbound queues starting with EM*? Please check the troubleshooting guide for more info, on what could be the root cause: http://scn.sap.com/docs/DOC-61452

Best regards, Daniel

[petra_just · Accepted solution]

Daniel,

yes, have checked the Queue. No entries for this FU. The source of the info is propagated from SAP EM. The Event info is persisted correctly into the EXECUTIONINFORMATION_TR Node. Have checked that as advised in your guide. When I post "Report Event" manually, all Status updates happen and the Propagation to the FO too. It seems I must have Chosen a wrong entry in the BAPI. Have set it as synchronous. Is that ok?

[petra_just · Accepted solution]

Daniel,

I am using BAPI /SAPTRX/BAPI_EH_ADDEVENTMSG_02 to post the events. We are using TM and EM on the same machine. Have read your guide and checked all the customizing and the rest of the tips. But, the customizing is as described in your guide. The event looks correct on the exec tab and the node is there. But, the Status updates do not happen without pressing "Report Event".

Regards

Petra

[petra_just · Accepted solution]

Daniel,

have attached the coding. Please let me know what is wrong.

[former_member186607 · Accepted solution]

Hi,

you have mentioned above that "The Event info is persisted correctly into the EXECUTIONINFORMATION_TR" -> this is a transient node, so nothing will be persisted here. Please check node EXECUTIONINFORMATION (you can reach it via association EXEC) instead.

Can you please explain in more detail, when/how this coding is executed. Maybe the COMMIT is missing? Is this only used for test purposes? How is it called?

Best regards, Daniel

[petra_just · Accepted solution]

Hi Daniel,

Have checked the FU and node EXEC and indeed there is nothing in node EXEC. This report is used to set events to loaded automatically when a certain time is reached. We use it in a first phase to have the load events and the related statuses updated as loaded on the same time as they were planned in the schedule. Maybe, the commit is missing. Which coding would I have to add to it to test this idea. the developper will only work tomorrow morning, but I can change the coding to test if this works. We are already live and this has to work "yesterday".

Thanks so much for your on-going help.

Regards

Petra

[petra_just · Accepted solution]

Daniel,

have seen another thread about the same issue. Do I have to fill the structure TRACKEEMODIFY?

If yes, which fields?

EVTCNT same as header, EVTID LOAD_END, LOCID1.Which date fields?

[petra_just · Accepted solution]

Daniel,

yes, the commit was missing. Thanks so much for your help. Have attached an extract of your document "How the Standard Integration can be tested between SAP EM and SAP TM" and it explains clearly that the 2nd BAPI BAPI-TRANSACTION_COMMIT must be done after the BAPI call.

Best greetings!!

[former_member524998 · Accepted solution]

Hello Daniel,

I would like to go through the trouble shooting document you have prepared for a similar issue and it seems the document has been archived and unable to open it. Could you please help me with accessing it?