cancel
Showing results for 
Search instead for 
Did you mean: 

EM is down.

Former Member
0 Kudos

Everyone,

In the current ECC -> EM Setup for PO and ASN. If for some reason, EM is down then all related POs and IDNs that are created during down time will be in QRFC Outbound Queue (SMQ1). Once the system is up, we will release from SMQ1 and everything is working fine.

My Question is:

For Invoice creation, it is through the 3rd Party , where they will Post Invoice in Cockpit in ECC, then through the Process will trigger and creates the Invoice EH (through RFC) in EM. Process is working fine.

If EM is down, then the 3rd Party still posts the Invoice in the Cockpit in ECC, but there is no Invoice EH due to EM is down ( No RFC Connection). I don't see this record in SMQ1 like PO and IDN. Any thoughts how I should push this records into Q.

Please let me know if I am missing any configuration.

Thank you in advance.

Susheel

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member583013
Active Contributor
0 Kudos

Answered in the thread

former_member583013
Active Contributor
0 Kudos

Steffen is correct. Since you are manually calling the EH_POST BAPI you should consider calling it using the qRFC method as described at [http://www.erpgenie.com/sap-event-management/sap-event-management-working-with-queued-rfc|http://www.erpgenie.com/sap-event-management/sap-event-management-working-with-queued-rfc]

former_member190756
Active Contributor
0 Kudos

Hello Susheel

if the process is going through the standard BADI implementation for MM Invoice EM Integration /SAPTRX/MM_INVOICE and EM connection is setup as asynchron in transaction /SAPTRX/ASC0TS it should work as for the other documents.

You could set a breakpoint in include /SAPTRX/LASC2F01 and check how the BAPI /SAPTRX/BAPI_EH_POST is called in the Invoice case.

Best regards,

Steffen