<?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 in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc/m-p/2632728#M605455</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 a call to a function module running in a different system.Programmatically ,you can call the RFC enabled function module&lt;/P&gt;&lt;P&gt;using the "CALL FUNCTION Destination" statement.&lt;/P&gt;&lt;P&gt;There are 3 types of RFC's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Synchronous RFC: With this call,the calling program stops processing until the control is returned back to the called function&lt;/P&gt;&lt;P&gt;2.Transactional RFC (tRFC)&lt;/P&gt;&lt;P&gt;Transactional RFC (known as asynchronous RFC) is an asynchronous communication method that executes the called function module in the RFC server only once. &lt;/P&gt;&lt;P&gt;3.Queued RFC: LUWs are processed in the order specified by the application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding the Gateway Host of RFC scenario, you need to go to trnx SM59, select the TCP/IP Connections and follow the Michal's Blog for further steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For IDOC Scenarios you need to do the ALE Configuration First.For the ALE Configuration you can look into this Blog:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will know waht is Partner profiles&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Jul 2007 07:36:20 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-30T07:36:20Z</dc:date>
    <item>
      <title>RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc/m-p/2632726#M605453</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is RFC? what is relation between idoc and rfc, which is better?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;swathi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jul 2007 07:31:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc/m-p/2632726#M605453</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-30T07:31:22Z</dc:date>
    </item>
    <item>
      <title>Re: RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc/m-p/2632727#M605454</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;u&amp;gt;Remote Function Call:&amp;lt;/u&amp;gt;&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;How to create it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;goto Se37 create a Function module.&lt;/P&gt;&lt;P&gt;in the attribute tab select remote function enabled radio button.&lt;/P&gt;&lt;P&gt;in Sm59 create a destination, select type 3 for R/3 system&lt;/P&gt;&lt;P&gt;specify the ip address of the target system &amp;amp; save it.then click the button test connection to check the connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in Function module specify ur import export parameters. it must be pass by value so tick the check box.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;write ur code &amp;amp; save it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a look at this link.&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf" target="test_blank"&gt;http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf&lt;/A&gt;&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;&amp;lt;u&amp;gt;IDOC&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC is a intermediate document to exchange data between two SAP Systems.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*IDocs are structured ASCII files (or a virtual equivalent). &lt;/P&gt;&lt;P&gt;*Electronic Interchange Document&lt;/P&gt;&lt;P&gt;*They are the file format used by SAP R/3 to exchange data with foreign systems.&lt;/P&gt;&lt;P&gt;*Data Is transmitted in ASCII format, i.e. human readable form&lt;/P&gt;&lt;P&gt;*IDocs exchange messages&lt;/P&gt;&lt;P&gt;*IDocs are used like classical interface files&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;IDOC types are templates for specific message types depending on what is the business document, you want to exchange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;WE30 - you can create a IDOC type.&lt;/P&gt;&lt;P&gt;An IDOC with data, will have to be triggered by the application that is trying to send out the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FOr testing you can use WE19.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;how to create idoc?&lt;/P&gt;&lt;P&gt;*WE30 - you can create a IDOC type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more information in details on the same along with the examples can be viewed on:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404" target="test_blank"&gt;http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sappoint.com/presentation.html" target="test_blank"&gt;http://www.sappoint.com/presentation.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.allsaplinks.com/idoc_search.html" target="test_blank"&gt;http://www.allsaplinks.com/idoc_search.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sapgenie.com/sapedi/idoc_abap.htm" target="test_blank"&gt;http://www.sapgenie.com/sapedi/idoc_abap.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;Reshma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jul 2007 07:32:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc/m-p/2632727#M605454</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-30T07:32:56Z</dc:date>
    </item>
    <item>
      <title>Re: RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/rfc/m-p/2632728#M605455</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 a call to a function module running in a different system.Programmatically ,you can call the RFC enabled function module&lt;/P&gt;&lt;P&gt;using the "CALL FUNCTION Destination" statement.&lt;/P&gt;&lt;P&gt;There are 3 types of RFC's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.Synchronous RFC: With this call,the calling program stops processing until the control is returned back to the called function&lt;/P&gt;&lt;P&gt;2.Transactional RFC (tRFC)&lt;/P&gt;&lt;P&gt;Transactional RFC (known as asynchronous RFC) is an asynchronous communication method that executes the called function module in the RFC server only once. &lt;/P&gt;&lt;P&gt;3.Queued RFC: LUWs are processed in the order specified by the application, tRFC can be serialized using queues (inbound and outbound queues). This type of RFC is called queued RFC (qRFC). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding the Gateway Host of RFC scenario, you need to go to trnx SM59, select the TCP/IP Connections and follow the Michal's Blog for further steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For IDOC Scenarios you need to do the ALE Configuration First.For the ALE Configuration you can look into this Blog:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will know waht is Partner profiles&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jul 2007 07:36:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/rfc/m-p/2632728#M605455</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-30T07:36:20Z</dc:date>
    </item>
  </channel>
</rss>

