<?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 performance in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749257#M324870</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;system calculates the size by rowlength * occurs that is how much memoryu you want for declaring the itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if your row length is big enough it may allocate 8kb also...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rowlength * no. of occurs &amp;gt; or eq 8 kb it will allocate the memory in system page area and if it is less it will be allocated in program roll area.&lt;/P&gt;&lt;P&gt;access to program roll area memory is faster than system page area.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so it depends on the size of your internal table.&lt;/P&gt;&lt;P&gt;if your internal table contains occurs 1 and row length * 1 less than 8kb then it will allocate memory in program roll area for the first time but if your itab size crosses 8 kb limit it will allocate at system page area .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;shiba dutta&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 02 Jan 2007 10:19:12 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-02T10:19:12Z</dc:date>
    <item>
      <title>internal table performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749251#M324864</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I wanted to know what is the difference between occurs 0 &amp;amp; occurs 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Which one is prefferable &amp;amp; why??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 09:33:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749251#M324864</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T09:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: internal table performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749252#M324865</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Neha,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If u decalre the tab as occurs 0 then the 8kb memory will be allocated for that table.&lt;/P&gt;&lt;P&gt;If u decalre the tab as occurs 1 then the memory will be reallocated as the data is filled in that table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if the data the table is holding is more then go for occurs 0 additon. If it is less u can declare it with occurs 100.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If useful reward.&lt;/P&gt;&lt;P&gt;Vasanth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 09:36:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749252#M324865</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T09:36:05Z</dc:date>
    </item>
    <item>
      <title>Re: internal table performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749253#M324866</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Neha,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If u declare table with OCCURS 0 ---&amp;gt; defaultly an 8KB memory is assinged to table. Eventhogh the table infromation is not that much, So memory is wated if the informaion is less.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Declaration of table by using OCCURS 1, Means it will assign a memory space which will sufficant to fint for one record first. depending upon the usage the consiqutive memory is assinged.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if u know the amount of information that need to be place in table, it is better to give mount.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sunil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 09:42:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749253#M324866</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T09:42:09Z</dc:date>
    </item>
    <item>
      <title>Re: internal table performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749254#M324867</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;occurs 0 addition will allocate large memory space and it is advisable 2 go for occurs 0 when u r not sure of the amount of the data 2 be stored.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;however if u need 2 store only limited amount of data, u can go for occurs 100. This will help in improving performance as unwanted memory allocation is avoided.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards, &lt;/P&gt;&lt;P&gt;Sandeep&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*pls award points if u find this useful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 09:47:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749254#M324867</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T09:47:41Z</dc:date>
    </item>
    <item>
      <title>Re: internal table performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749255#M324868</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 know that if we specify occours 0 it will allocate 8kb of memory by default.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is like if i write occurs 1 it will only hold only one row or more than 1 row.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Similarly occurs 2 then it will hold only two rows or anything else.&lt;/P&gt;&lt;P&gt;While occurs 100 what happened??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls let me know asap.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 10:12:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749255#M324868</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T10:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: internal table performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749256#M324869</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Neha,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For occurs 1, when one row is filled, then more memory is allocated. It can have more than one row as memory will be dynamically allocated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so for occurs 2 or occurs 100, you will be able to append more records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Navneet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 10:16:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749256#M324869</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T10:16:19Z</dc:date>
    </item>
    <item>
      <title>Re: internal table performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749257#M324870</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;system calculates the size by rowlength * occurs that is how much memoryu you want for declaring the itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if your row length is big enough it may allocate 8kb also...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rowlength * no. of occurs &amp;gt; or eq 8 kb it will allocate the memory in system page area and if it is less it will be allocated in program roll area.&lt;/P&gt;&lt;P&gt;access to program roll area memory is faster than system page area.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so it depends on the size of your internal table.&lt;/P&gt;&lt;P&gt;if your internal table contains occurs 1 and row length * 1 less than 8kb then it will allocate memory in program roll area for the first time but if your itab size crosses 8 kb limit it will allocate at system page area .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;shiba dutta&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 10:19:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749257#M324870</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T10:19:12Z</dc:date>
    </item>
    <item>
      <title>Re: internal table performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749258#M324871</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;If u use occurs 1, initially, only 1 row will be allotted and depending on the usage, memory will be reallocated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Sandeep&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 10:20:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749258#M324871</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T10:20:06Z</dc:date>
    </item>
    <item>
      <title>Re: internal table performance</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749259#M324872</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;It will hold more than one record, but initially it will assigne memory for one record only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While u r appending records it will assign memory...!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regrds,&lt;/P&gt;&lt;P&gt;Sunil&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 10:27:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-table-performance/m-p/1749259#M324872</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T10:27:18Z</dc:date>
    </item>
  </channel>
</rss>

