<?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 Re: RFC communction failure in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739737#M1111963</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try adding something like this to your RFC call:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;      EXCEPTIONS&lt;/P&gt;&lt;P&gt;        system_failure        = 1  MESSAGE mess&lt;/P&gt;&lt;P&gt;        communication_failure = 2  MESSAGE mess&lt;/P&gt;&lt;P&gt;        resource_failure      = 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mário&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Nov 2008 16:47:35 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-11-12T16:47:35Z</dc:date>
    <item>
      <title>RFC communction failure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739735#M1111961</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am calling an RFC function module (Target sytem A). In case there is a communction failure, how can I know it and handling exception in the calling program. Are there any constriants that I have to take while creating an RFC (like creating exceptions)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;lt;&amp;lt;removed_by_moderator&amp;gt;&amp;gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Nov 2008 16:34:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739735#M1111961</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-11-12T16:34:48Z</dc:date>
    </item>
    <item>
      <title>Re: RFC communction failure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739736#M1111962</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please don't offer rewards, and find your answer in SAP online help, this topic is explained there very well.&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Nov 2008 16:36:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739736#M1111962</guid>
      <dc:creator>ThomasZloch</dc:creator>
      <dc:date>2008-11-12T16:36:47Z</dc:date>
    </item>
    <item>
      <title>Re: RFC communction failure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739737#M1111963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try adding something like this to your RFC call:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;      EXCEPTIONS&lt;/P&gt;&lt;P&gt;        system_failure        = 1  MESSAGE mess&lt;/P&gt;&lt;P&gt;        communication_failure = 2  MESSAGE mess&lt;/P&gt;&lt;P&gt;        resource_failure      = 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mário&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Nov 2008 16:47:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739737#M1111963</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-11-12T16:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: RFC communction failure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739738#M1111964</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here´s a nice blog about RFC_VERIFY_DESTINATION by Craig Cmehil:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Nov 2008 20:11:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739738#M1111964</guid>
      <dc:creator>former_member182371</dc:creator>
      <dc:date>2008-11-12T20:11:28Z</dc:date>
    </item>
    <item>
      <title>Re: RFC communction failure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739739#M1111965</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Priyanka,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is your call to the RFC from another system (i.e. are you using a remote-enabled RFC)?  We faced this issue and handle the exception trapping at that end (a java-based app).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is also something called RFC_PING.  I found additional info: "The problem with RFC_PING is that it doesn't test authorizations. I don't know if RFC_VERIFY_DESTINATION does or not. However if you are using Trusted RFC, this test of authorization to logon is very important."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Good luck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SL&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Nov 2008 20:42:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc-communction-failure/m-p/4739739#M1111965</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-11-12T20:42:34Z</dc:date>
    </item>
  </channel>
</rss>

