ABAP Proxy asynchronous outbound persistency

[suwandi_cahyadi]

Dear Experts,

I'm curious about the ABAP proxy persistency at the ECC side (outbound message from SAP ECC to PI)

in case of IDoc, once the IDoc is created it will be persisted in a standard table, there are also tcodes to check outbound IDoc status. Even, when the connection is down or the SAP PI is down, we can still monitor at Outbound tRFC tcode (SM58).

in case of asynchronous outbound ABAP proxy messages, does this has the same persistency level? AFAIK, we can monitor ABAP proxy messages in SXMB_MONI. In case of connection down, will the message still be persisted? or will it just gone?

Thank you,

Suwandi C.

[Former Member · Accepted solution]

Hi Suwandi

If the ABAP program for the proxy executed successfully then the message will be available in ECC moni. Now if the PI server is down at that time, then the message will be failed in ECC moni and will be available for  resend when the PI server is up.

The same message will come to PI moni once it successfully processed in ECC Moni.

Sometime you will see that, no message is available in ECC moni itself...in those cases you have to monitor the JOB which is running the abap program for the proxy.

Thanks,

Indrajit

[engswee]

Hi Suwandi,

On the ECC side, the messages are sent out via qRFC (as opposed to tRFC for IDocs.) These are persisted, and you can similarly view any LUW with connection related issues via SMQ1 (or go the long way via SMQR.) Once the connection issue is resolved, you can reexecute the LUW from SMQ1 to resend - very similar behaviour with SM58.

There is also a link to the outbound queue status from the corresponding message in SXMB_MONI.

Rgds

Eng Swee