<?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: declaring internal tables in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983013#M1341171</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 reason for this being that is it not a good practice to declare internal tables with header lines , as they are not allowed in object oriented concept . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you declare an internal table with header line it results in the same name for two objects one the internal table and the other the work area , hence the practice to define separate data objects for table and the work area. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 14 Aug 2009 05:22:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-08-14T05:22:28Z</dc:date>
    <item>
      <title>declaring internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983012#M1341170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;why do we declare internal tables in this way &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES: BEGIN OF ty_t501t,&lt;/P&gt;&lt;P&gt;..&lt;/P&gt;&lt;P&gt;...   &lt;/P&gt;&lt;P&gt;       END OF ty_t501t.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: gt_list1 TYPE STANDARD TABLE OF ty_list1,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;why not this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF ITAB OCCURS 0,&lt;/P&gt;&lt;P&gt;         ....&lt;/P&gt;&lt;P&gt;....&lt;/P&gt;&lt;P&gt;.....&lt;/P&gt;&lt;P&gt;      END OF ITAB.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2009 05:18:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983012#M1341170</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-14T05:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: declaring internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983013#M1341171</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 reason for this being that is it not a good practice to declare internal tables with header lines , as they are not allowed in object oriented concept . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you declare an internal table with header line it results in the same name for two objects one the internal table and the other the work area , hence the practice to define separate data objects for table and the work area. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2009 05:22:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983013#M1341171</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-14T05:22:28Z</dc:date>
    </item>
    <item>
      <title>Re: declaring internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983014#M1341172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if at all if you need any changes if you make changes to Ty... will be enough...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and you can create many internal tables... using that TY with a single line code...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2009 05:23:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983014#M1341172</guid>
      <dc:creator>former_member156446</dc:creator>
      <dc:date>2009-08-14T05:23:22Z</dc:date>
    </item>
    <item>
      <title>Re: declaring internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983015#M1341173</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;Declaring internal table with a header line decreases performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its better to have internal table without header line and a work area to work with it.&lt;/P&gt;&lt;P&gt;Its improves performance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also wen u work with internal table with header line it creates confusion that whether ur working with the header line or body of the internal table.&lt;/P&gt;&lt;P&gt;Also declaring internal table with header line is obsolete one.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT ITAB----&lt;/P&gt;&lt;HR originaltext="------" /&gt;&lt;P&gt;&amp;gt;Working with header line.(Confusion whether ur referring header or body of internal table)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT ITAB INTO WA------&amp;gt;Working with internal table widout header line and an work area&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lakshman.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Lakshman N on Aug 14, 2009 7:25 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2009 05:25:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983015#M1341173</guid>
      <dc:creator>former_member209217</dc:creator>
      <dc:date>2009-08-14T05:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: declaring internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983016#M1341174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When we declare an internal table using &lt;STRONG&gt;DATA statement&lt;/STRONG&gt;, it creates an internal table with headerline.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Use of internal tables with header is not recommended&lt;/STRONG&gt;. Such internal tables can cause serious bugs&lt;/P&gt;&lt;P&gt;in the code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So normal we declare a type using &lt;STRONG&gt;TYPE statement&lt;/STRONG&gt; and then declare the internal table using the newly declared &lt;/P&gt;&lt;P&gt;type.&lt;/P&gt;&lt;P&gt;In this case we have to create a separate workarea to perform operations on the internal table.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Use of workarea makes our code easy to understand&lt;/STRONG&gt;. Also there are &lt;STRONG&gt;less chances of error&lt;/STRONG&gt; if we use workareas&lt;/P&gt;&lt;P&gt;rather than internal table with headerline and &lt;STRONG&gt;bebugging becomes simple&lt;/STRONG&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Aug 2009 05:27:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/declaring-internal-tables/m-p/5983016#M1341174</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-14T05:27:50Z</dc:date>
    </item>
  </channel>
</rss>

