Skip to Content
author's profile photo Former Member
Former Member

RFC Message not visible in SXMB_MONI

Dear Experts,

I have a issue in a scenario where XI receives the file and sends to RFC.

Message in XI is successful ( both in Integration Engine and Adapter Engine ) . In the receiver RFC Communication channel message status shows delivered.. But i could not find any message in receiver system in SXMB_MONI.

There is no failures in SM58, No dump in ST22 and SE13.

So What could be the issue and how to resolve this. Where can i see the message in Receiver. How do i confirm if the message reached Receiver system?

In my case, receiver system is SAP BW .


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on May 13, 2015 at 05:55 AM

    Hi Ruben,

    RFC messages cannot be monitored via SXI_MONITOR transaction in receiver system, only proxy messages are monitored in SXI_MONITOR transaction.

    This is the problem with RFC that is why i prefer to use proxy instead of RFC.Check below blog.

    Stop using RFC in PI © - Get better monitoring and error-handling features

    You need to check actual data is updated or not, if you creating the customer for example you can check actual customer created or not in the system.



    Add a comment
    10|10000 characters needed characters exceeded

    • >>>How do i confirm if the message reached Receiver system?

      If the audit log confirm that the message has been successfully processed by AE, then your RFC has been called and message has been executed.

      >>>So is there no way i can see the data what entered in to ECC after running the scenarion.

      You can find the xml content in adapter engine right?(post mapping payload). You can't see this xml in ECC and it is being procesed by your functin module.

      If you would like to know where is your data and what is happening during RFC execution, you have to debug the RFC by supplying the payload directly in ECC.

  • author's profile photo Former Member
    Former Member
    Posted on May 13, 2015 at 05:42 AM


    Not sure what the problem is. Because you said that the message is successful in Integration and Adapter Engine. Integration Engine would be the ABAP stack and that is where you see the message normally in SXMB_MONI. But you say it is not there. So I am guessing that you saw it on the Java side under RWB.

    So I would suggest that you just double check your time and if you can see it on the java stack(RWB). Take the message ID and copy into the advanced function in SXMB_MONI.

    But like you said you can see it is successful on the RFC Communication channel. That means it was successful.

    So the last question is confusion because like you yourself said it is successful on the Receiver channel.

    Can you please maybe just clear it up please?


    Jannus Botha

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on May 13, 2015 at 06:03 AM

    Hi Ruban,

    I agree with Praveen you can't use sxi_monitor in ECC with RFC communication, the only way that you have to debug your communication if you want to use a RFC is to do a Z table and in the first step of the RFC store all the data, another way is to do an external breakpoint with the same use that you have set in the RFC communication channel, then when you test the breakpoint will be raised.


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.