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

XI and RFC adapter

Hi

The RFC Adapter configuration has been done successfully and the adapter starts up successfully.

In our scenario, we attempt to receive an xml message from my local machine through a file adapter, and pass this along to the RFC Outbound adapter to execute a RFC on the CRM box.

The following error message is encountered in the XI monitoring tool.

==============================================================================================================

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Inbound Message

-->

- http://sap.com/exchange/MessageFormat">

<SAP:Context />

<SAP:Code p1="connection closed (no data)" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>

<SAP:Text language="EN">System error when calling the outbound RFC adapter (connection closed (no data))</SAP:Text>

</SAP:ErrorHeader>

===================================================================================================

I then stop the RFC adapter and attempt the scenario again. I get the following error message in XI monitoring tool.

================================================================================================================

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Inbound Message

-->

- http://sap.com/exchange/MessageFormat">

<SAP:Context />

<SAP:Code p1="Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n" p2="" p3="" p4="">RFC_ADAPTER.SYSTEM_FAILURE_OUTBOUND</SAP:Code>

<SAP:Text language="EN">System error when calling the outbound RFC adapter (Exception in handleRequest of server Xmb2RfcService: java.lang.Exception: Bean n)</SAP:Text>

</SAP:ErrorHeader>

==================================================================================================================

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 16, 2004 at 04:59 PM

    Hi Emile,

    An messages via the file adapter is normally an asynchronous interface and a RFC connection via the RFC adapter is synchronous interface. It is not possible to connect those two interfaces without an ccBPM in the middle.

    Cheers,

    Frank

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 17, 2004 at 06:05 AM

    You may or may not know, I am totally new to SAP XI and hence would like to ask you what ccBPM is and how to define it or where I can read to do the above?

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Emile,

      ccBPM is Cross Component Business Process Management, it is a separate component running on SAP XI.

      You can read the details SAP XI Help under

      this section

      SAP XI ->Design and Configuration Time ->Design -> Designing Cross Component Business Processes

      Cheers

      Senthil

  • author's profile photo Former Member
    Former Member
    Posted on Nov 17, 2004 at 09:03 AM

    I am having difficulty finding the following:

    You can read the details SAP XI Help under

    this section

    SAP XI ->Design and Configuration Time ->Design -> Designing Cross Component Business Processes

    Please Help

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      I guess you go from

      File -> XI -> RFC

      This should work even so the RFC is sync. The other way around you have to use the Sync to Async Bridge.

      Without a ccBPM you would not get the RFC response back but the call still would go to the R3 system. We had to do this in XI 2.0 before we had 3.0.

      If you depend of the response message then only ccBPM is the solution.

      Stefan

  • author's profile photo Former Member
    Former Member
    Posted on Nov 17, 2004 at 10:16 AM

    You are correct, we are going from FILE --> XI ---> R3 but our file does not arrive on the R3 system.

    The file adapter have configured with QOS = BE.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi KP,

      call transaction SXMB_ADM and click on Integration Engine Configuration. In there enter RUNTIME and click on specific settings. The drop down and help tells you the correct parameter spelling but use:

      TRACE_LEVEL = 3

      LOGGING = 1

      LOGGING_SYNC = 1

      LOGGING_PROPGATION = 1

      TRACE_LEVEL_PROPGATION = 1

      I forgot that your scenario is inbound RFC to R/3. When the tracing is set you should be able to see in each step (before mapping, after mapping) what you payload looks like. If the payload is empty when it calls the adapter then there is a problem with the mapping. XI is very picky with namespaces and names.

      Use ST01 to set a system trace for RFC Calls and see if that helps if the payload is correct once you it calls the adapter.

      We have the exact scenario too, our file adapter is EO not BE since the file adapter cannot handle ackwnoledgments.

      I hope this will help to come closer to the problem.

      Stefan

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.