<?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: internal table in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168685#M753938</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; by default occurs 0 means 8 kb will allocate .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; if u want more memory means u can give as occurs n,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; so here u can increase memory dynamically as per u r requirement .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; But among all of them occurs 0 is better as for performance wise &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THX&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Dec 2007 06:20:13 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-12-21T06:20:13Z</dc:date>
    <item>
      <title>internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168682#M753935</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;could u plz tell if i write occurs 0 /how much size it wil take?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Dec 2007 06:03:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168682#M753935</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-21T06:03:43Z</dc:date>
    </item>
    <item>
      <title>Re: internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168683#M753936</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if u write occurs 0 then it takes 8KB memory...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward points if useful....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Dec 2007 06:04:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168683#M753936</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-21T06:04:24Z</dc:date>
    </item>
    <item>
      <title>Re: internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168684#M753937</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;STRONG&gt;Srinath&lt;/STRONG&gt;,&lt;/P&gt;&lt;P&gt;  It takes 64 bytes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Plzz Reward if Useful,&lt;/P&gt;&lt;P&gt;Mahi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Dec 2007 06:06:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168684#M753937</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-21T06:06:25Z</dc:date>
    </item>
    <item>
      <title>Re: internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168685#M753938</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; by default occurs 0 means 8 kb will allocate .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; if u want more memory means u can give as occurs n,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; so here u can increase memory dynamically as per u r requirement .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; But among all of them occurs 0 is better as for performance wise &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;THX&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Dec 2007 06:20:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168685#M753938</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-21T06:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168686#M753939</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;Before Release 3.0, internal tables all had header lines and a flat-structured line type. There were no independent table types. You could only create a table object using the OCCURS&lt;/P&gt;&lt;P&gt;addition in the DATA statement, followed by a declaration of a flat structure:&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF &amp;lt;itab&amp;gt; OCCURS &amp;lt;n&amp;gt;,&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;&amp;lt;fi&amp;gt; ...,&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;END OF &amp;lt;itab&amp;gt;.&lt;/P&gt;&lt;P&gt;This statement declared an internal table &amp;lt;itab&amp;gt; with the line type defined following the OCCURS addition. Furthermore, all internal tables had header lines.&lt;/P&gt;&lt;P&gt;The number &amp;lt;n&amp;gt; in the OCCURS addition had the same meaning as in the INITIAL SIZE addition from Release 4.0. Entering &amp;#145;0&amp;#146; had the same effect as omitting the INITIAL SIZE addition. In this case, the initial size of the table is determined by the system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above statement is still possible in Release 4.0, and has roughly the same function as the following statements:&lt;/P&gt;&lt;P&gt;TYPES: BEGIN OF &amp;lt;itab&amp;gt;,&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;&amp;lt;fi&amp;gt; ...,&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;END OF &amp;lt;itab&amp;gt;.&lt;/P&gt;&lt;P&gt;DATA &amp;lt;itab&amp;gt; TYPE STANDARD TABLE OF &amp;lt;itab&amp;gt;&lt;/P&gt;&lt;P&gt;WITH NON-UNIQUE DEFAULT KEY&lt;/P&gt;&lt;P&gt;INITIAL SIZE &amp;lt;n&amp;gt;&lt;/P&gt;&lt;P&gt;WITH HEADER LINE.&lt;/P&gt;&lt;P&gt;In the original statement, no independent data type &amp;lt;itab&amp;gt; is created. Instead, the line type only exists as an attribute of the data object &amp;lt;itab&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The effect of the OCCURS addition is to construct a standard table with the data type &amp;lt;linetype&amp;gt;. The line type can be any data type. The number &amp;lt;n&amp;gt; in the OCCURS addition has the same meaning as before Release 3.0. Before Release 4.0, the key of an internal table was always the default key, that is, all non-numeric fields that were not themselves internal tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bhaskar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Dec 2007 09:08:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table/m-p/3168686#M753939</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-21T09:08:36Z</dc:date>
    </item>
  </channel>
</rss>

