<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RFC issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113772#M983552</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;in RFC when the destination server is not available then it will give dump can we able to avoid the dump or can we able to catch the dump in the table and use it or is there any oss notes which will stop dumping.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Jul 2008 13:35:27 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-07-09T13:35:27Z</dc:date>
    <item>
      <title>RFC issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113772#M983552</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;in RFC when the destination server is not available then it will give dump can we able to avoid the dump or can we able to catch the dump in the table and use it or is there any oss notes which will stop dumping.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jul 2008 13:35:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113772#M983552</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-09T13:35:27Z</dc:date>
    </item>
    <item>
      <title>Re: RFC issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113773#M983553</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;you can use this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;try.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;call RFC......&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;catch CX_SY_REMOTE_CALL_ERROR.&lt;/P&gt;&lt;P&gt;endtry.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jul 2008 13:41:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113773#M983553</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-09T13:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: RFC issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113774#M983554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Before calling your RFC call try to use fm RFC_PING and also please check program RSRFCPIN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;a®&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jul 2008 13:43:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113774#M983554</guid>
      <dc:creator>former_member194669</dc:creator>
      <dc:date>2008-07-09T13:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: RFC issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113775#M983555</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try adding these lines to your RFC call:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION&lt;/P&gt;&lt;P&gt;    EXPORTING&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;....&lt;/P&gt;&lt;P&gt;    EXCEPTIONS&lt;/P&gt;&lt;P&gt;        SYSTEM_FAILURE = 1&lt;/P&gt;&lt;P&gt;        COMMUNICATION_FAILURE = 2.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jul 2008 13:51:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113775#M983555</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-09T13:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: RFC issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113776#M983556</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try this, you can display the error message also&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  DATA l_oref TYPE REF TO cx_root.&lt;/P&gt;&lt;P&gt;  data p_text type string.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  TRY.&lt;/P&gt;&lt;P&gt;    CALL FUNCTION '----&lt;/P&gt;&lt;HR originaltext="---" /&gt;&lt;P&gt;'.  " remote function call&lt;/P&gt;&lt;P&gt;    CATCH CX_SY_REMOTE_CALL_ERROR INTO l_oref.&lt;/P&gt;&lt;P&gt;      p_text = l_oref-&amp;gt;get_text( ).&lt;/P&gt;&lt;P&gt;  ENDTRY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Look at the dump which you got and ig it is not having the exception CX_SY_REMOTE_CALL_ERROR, replace that exception in catch.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;P_text contains the exception description&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Jul 2008 14:04:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-issue/m-p/4113776#M983556</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-09T14:04:36Z</dc:date>
    </item>
  </channel>
</rss>

