<?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: Using Table types in RFC in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306045#M1223635</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;are you asking whether you can use Sorted or Hashed tables as parameters?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, you can. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And it will have no effects on the RFC but positive effects on the processing&lt;/P&gt;&lt;P&gt;in the RFC-function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Siegfried&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 18 Mar 2009 09:31:29 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-03-18T09:31:29Z</dc:date>
    <item>
      <title>Using Table types in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306043#M1223633</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to create one RFC. But in that RFC, I wish to use Table types as import and export parameters completly avoiding Tables tab. Will that effect the performance of RFC if I use Table types. If Yes, Please give clear clarification where it effects the performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also please let me know how the performance of the RFC is effected if we use Tables tab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ravee..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 06:19:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306043#M1223633</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-18T06:19:10Z</dc:date>
    </item>
    <item>
      <title>Re: Using Table types in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306044#M1223634</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Ravee&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since TABLES parameters are obsolete you should always use table types for "itab" parameters.&lt;/P&gt;&lt;P&gt;The system will always show you a warning about possible performance problems which you can ignore.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And if you ever really run into a performance problem with these table type parameters you could do a transformation within the RFC-fm (itab -&amp;gt; XML binary stream) and make the re-transformation (XML binary stream -&amp;gt; itab) in your calling program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Uwe&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 06:49:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306044#M1223634</guid>
      <dc:creator>uwe_schieferstein</dc:creator>
      <dc:date>2009-03-18T06:49:14Z</dc:date>
    </item>
    <item>
      <title>Re: Using Table types in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306045#M1223635</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;are you asking whether you can use Sorted or Hashed tables as parameters?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, you can. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And it will have no effects on the RFC but positive effects on the processing&lt;/P&gt;&lt;P&gt;in the RFC-function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Siegfried&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 09:31:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306045#M1223635</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-18T09:31:29Z</dc:date>
    </item>
    <item>
      <title>Re: Using Table types in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306046#M1223636</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt; The performance is effected as the response time of the FM depends on the amount of data that you are trying to get from the remote system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have TABLE TYPES in your import and export paramteres the amount of data that needs to be sent and receive is decided only at the run time. Where as for normal types the amount of data is always constant. For table types its depends how many records of data you want to send to the FM and how many records you want to read from the FM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The performance in case where you have table types depends on the amount of data and the bandwidth of you network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 09:51:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306046#M1223636</guid>
      <dc:creator>seshatalpasai_madala</dc:creator>
      <dc:date>2009-03-18T09:51:53Z</dc:date>
    </item>
    <item>
      <title>Re: Using Table types in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306047#M1223637</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;Now using of table parameter is obsolete, an example can be found in latest release like Ecc 6.0 onwards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Shashi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2009 10:06:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306047#M1223637</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-18T10:06:25Z</dc:date>
    </item>
    <item>
      <title>Re: Using Table types in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306048#M1223638</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"I wish to use Table types as import and export parameters completly avoiding Tables tab."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  I'm not sure if Tables can be avoided, if just using regular ABAP. I know that the Importing tab would not work when I tried it (under vrs 4.6b).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  Because you are launching separate processes, in separate memory areas: any parameter you use in RFC has to be known by the calling and the callee functions/programs. This means that you need a common reference. If you have more than one function module in a function group, you can use the TOP file and a 'Z' data dictionary structure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope that this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan Perecky&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 May 2009 21:27:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/using-table-types-in-rfc/m-p/5306048#M1223638</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-26T21:27:42Z</dc:date>
    </item>
  </channel>
</rss>

