<?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: Passing 3 internal tables as using parameter in subroutine in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020704#M1897890</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;I think if you are not passing huge tables by value, it's not a problem.&lt;/P&gt;&lt;P&gt;But as far as PERFORMs are obsolete now you can use local classes for your program. Defining these 3 tables as class attributes will let you forget about USING parameters.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 09 Apr 2015 09:36:51 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2015-04-09T09:36:51Z</dc:date>
    <item>
      <title>Passing 3 internal tables as using parameter in subroutine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020702#M1897888</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 passing three internal tables as using parameters in a subroutine in my program. I am little confused if it is recommended to pass so many tables as parameters.&lt;/P&gt;&lt;P&gt;Could you please let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2015 07:12:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020702#M1897888</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-04-09T07:12:13Z</dc:date>
    </item>
    <item>
      <title>Re: Passing 3 internal tables as using parameter in subroutine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020703#M1897889</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;I was also curious to know if it is recommended to pass these many tables in the perform.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The F1 help also does not gives any such information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If your table are globally defined you dont have to pass them in using parameters, but depending on your requirement, you can use USING and CHANGING parameters of the perform apropriately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would like other Gurus also to comment/share their views on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2015 07:45:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020703#M1897889</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-04-09T07:45:18Z</dc:date>
    </item>
    <item>
      <title>Re: Passing 3 internal tables as using parameter in subroutine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020704#M1897890</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;I think if you are not passing huge tables by value, it's not a problem.&lt;/P&gt;&lt;P&gt;But as far as PERFORMs are obsolete now you can use local classes for your program. Defining these 3 tables as class attributes will let you forget about USING parameters.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2015 09:36:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020704#M1897890</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-04-09T09:36:51Z</dc:date>
    </item>
    <item>
      <title>Re: Passing 3 internal tables as using parameter in subroutine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020705#M1897891</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tiki,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Previously i was thinking like Gaurav, but some days back, i read one document that SAP never recommended to define the data variable at global level.&lt;/P&gt;&lt;P&gt;Because when the program load SAP collect all the data object into Stack memory global objects always remain same till that program is in memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if we can define the data at local level it will automatically clear from memory when the scope of the blocks end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Nishant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2015 09:40:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020705#M1897891</guid>
      <dc:creator>nishantbansal91</dc:creator>
      <dc:date>2015-04-09T09:40:02Z</dc:date>
    </item>
    <item>
      <title>Re: Passing 3 internal tables as using parameter in subroutine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020706#M1897892</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you all for your valuable responses.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Apr 2015 13:03:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/passing-3-internal-tables-as-using-parameter-in-subroutine/m-p/11020706#M1897892</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2015-04-09T13:03:01Z</dc:date>
    </item>
  </channel>
</rss>

