Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

RFC of one R/3 - RFC of other R/3 communication through PI

To PI Experts,

      WE have designed and configured an RFC -PI -RFC scenario. It is for transfering data from R/3 server in one landscape to R/3 server in other landscape. Whe we execute the report from the sender side RFC, the scenario is perfectly executed without any problem. In SXMB_MONI i am getting a succesful transaction as processed successfully. Also when I check throug RWB, I am checking for the Sender RFC channel and receiver RFC channel.  The sender channel and the receiver channel both are showing Green LED and are without error. In the sender channel log it is showing me as follows:

Audit Log for Message: c986e950-559b-11e2-b0f9-00096beb7359

Jan 3, 2013 5:20:36 PMInformationThe application tries to send an XI message asynchronously using connection RFC_http://sap.com/xi/XI/System.
Jan 3, 2013 5:20:36 PMInformationTrying to put the message into the send queue.
Jan 3, 2013 5:20:36 PMInformationThe response message for message c93016c0-559b-11e2-9628-00096beb7359(INBOUND) was successfully passed to the waiting "request" thread.
Jan 3, 2013 5:20:36 PMInformationThe message status was set to DLVD.
Jan 3, 2013 5:20:36 PMInformationThe application sent the message asynchronously using connection RFC_http://sap.com/xi/XI/System. Returning to application.
Jan 3, 2013 5:20:36 PMInformationUsing connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
Jan 3, 2013 5:20:36 PMInformationThe return message for message c93016c0-559b-11e2-9628-00096beb7359(OUTBOUND) was successfully passed to the waiting "call" thread.
Jan 3, 2013 5:20:36 PMInformationThe message status was set to DLVD.

The result is though the transaction is executed and processed successfully with proper payload ,the data is not getting transferred in the receiver RFC and internal Table in the R/3. Where could be the problem ? Can any one guide me on this....

Regards

Sonia Singh

replied

Dear All,

   The problem is solved. The problem was with ABAP report written to get the data retrived from the RFC. The correction was made in the ABAP and the problem was solved.

Thanks to everyone for their contribution...

Regards

Sonia

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question