<?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: About RFC's in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073148#M429558</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;&amp;lt;b&amp;gt;RFC:&amp;lt;/b&amp;gt;Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Synchronous RFC:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&amp;lt;b&amp;gt;Transactional RFC (tRFC) and Queued RFC (qRFC&amp;lt;/b&amp;gt;).&amp;lt;/b&amp;gt; tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Transactional RFC:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call. &lt;/P&gt;&lt;P&gt;To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Queued RFC:&amp;lt;/b&amp;gt;When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more information on RFC, please go through the link.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bhanu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 Mar 2007 09:55:10 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-03-21T09:55:10Z</dc:date>
    <item>
      <title>About RFC's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073142#M429552</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 want to know more about RFC's .&lt;/P&gt;&lt;P&gt;     How to work on RFC's&lt;/P&gt;&lt;P&gt;     Examples on RFC's&lt;/P&gt;&lt;P&gt;     Doc's on RFC's&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please let me know all these&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;khanna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 09:37:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073142#M429552</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-21T09:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: About RFC's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073143#M429553</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use the SEARCH function. I assume that a lot of postings about RFC's are in this forum already.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 09:38:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073143#M429553</guid>
      <dc:creator>h_senden2</dc:creator>
      <dc:date>2007-03-21T09:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: About RFC's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073144#M429554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Refer this link:&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 09:40:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073144#M429554</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-21T09:40:58Z</dc:date>
    </item>
    <item>
      <title>Re: About RFC's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073145#M429555</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;there r TRFC(transactional RFC),ARFC(asynchronous RFC),QRFC(queued RFC).&lt;/P&gt;&lt;P&gt;rfc is for getting the data,moving the dta from client to client remotely.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if u  give me ur mail id i'll send u some basic examples with screen shots.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;bharat.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 09:43:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073145#M429555</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-21T09:43:01Z</dc:date>
    </item>
    <item>
      <title>Re: About RFC's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073146#M429556</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;&lt;/P&gt;&lt;P&gt;and you will be passing an Import parameter DESTINATION to it.&lt;/P&gt;&lt;P&gt;Other code and usage will be similar to any fun module;&lt;/P&gt;&lt;P&gt;Have a look at any fun module in SE37 to understand better about the different components of Fun modules;&lt;/P&gt;&lt;P&gt;reward if useful&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 09:43:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073146#M429556</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-21T09:43:08Z</dc:date>
    </item>
    <item>
      <title>Re: About RFC's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073147#M429557</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remote Function Call:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RFCs enable you to call and execute predefined functions in a remote system - or even in the same system. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RFCs manage the communication process, parameter transfer and error handling.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Priyanka.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 09:45:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073147#M429557</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-21T09:45:19Z</dc:date>
    </item>
    <item>
      <title>Re: About RFC's</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073148#M429558</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;&amp;lt;b&amp;gt;RFC:&amp;lt;/b&amp;gt;Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Synchronous RFC:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&amp;lt;b&amp;gt;Transactional RFC (tRFC) and Queued RFC (qRFC&amp;lt;/b&amp;gt;).&amp;lt;/b&amp;gt; tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Transactional RFC:&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call. &lt;/P&gt;&lt;P&gt;To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Queued RFC:&amp;lt;/b&amp;gt;When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more information on RFC, please go through the link.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bhanu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 Mar 2007 09:55:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/about-rfc-s/m-p/2073148#M429558</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-21T09:55:10Z</dc:date>
    </item>
  </channel>
</rss>

