<?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 trfc in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/trfc/m-p/3429062#M823684</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt; transactional  rfc are transferred with parameters data in byte streme using which protocol&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 24 Feb 2008 10:09:55 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-24T10:09:55Z</dc:date>
    <item>
      <title>trfc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/trfc/m-p/3429062#M823684</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt; transactional  rfc are transferred with parameters data in byte streme using which protocol&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 24 Feb 2008 10:09:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/trfc/m-p/3429062#M823684</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-24T10:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: trfc</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/trfc/m-p/3429063#M823685</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Transaction ID (TID) / tRFC (Transactional Remote Function Call) management for inbound events. SAP uses a transaction and its corresponding ID to frame an event, guaranteeing that each piece of data is delivered once and only once from SAP. SAP sends a Transaction ID (TID) with the event data. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: Because the adapter uses asynchronous communication, it cannot be used when cross-referencing is required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Protocol for ensuring that an RFC is executed successfully and executed only once on the target system. SAP Business Connector can handle both inbound and outbound tRFCs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TRFC protocol: Communications method that an SAP component uses to asynchronously invoke a function on a remote system and that a remote system uses to asynchronously invoke a function on an SAP component. The tRFC protocol ensures that an RFC is executed successfully and only once.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe it uses Simple Object Access [SOAP] protocol.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sekar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Feb 2008 20:10:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/trfc/m-p/3429063#M823685</guid>
      <dc:creator>former_member188594</dc:creator>
      <dc:date>2008-02-29T20:10:10Z</dc:date>
    </item>
  </channel>
</rss>

