<?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 tables in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119379#M443967</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi mrudula,&lt;/P&gt;&lt;P&gt;    Long life data are stored in the database table. We can't afford to lose data from the database table. Hence v need of a intermediate table where v can put in all our datas and work with that, thus avoiding accidental loss of data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This intermediate tables are nothing but called as internal tables, which are created during runtime and reserves no memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are 3 types of internal tables.&lt;/P&gt;&lt;P&gt;1)standard&lt;/P&gt;&lt;P&gt;2)sorted&lt;/P&gt;&lt;P&gt;3)hashed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Arun.&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>Thu, 19 Apr 2007 12:24:02 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-04-19T12:24:02Z</dc:date>
    <item>
      <title>internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119370#M443958</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the purpose of using internal tables ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 11:57:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119370#M443958</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T11:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119371#M443959</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;   Internal tables are used 2 store humongous amount of data. they are the substitues for arrays in abap.Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;kiran kumar k&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        kiran kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 11:59:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119371#M443959</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T11:59:34Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119372#M443960</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In a nutshell, internal tables are used to temporarily store data from the database for you to work on within your programs.  They are populated by using SQL syntax - either native SQL (eg ORacle, MS) or Open SQL (SAP specific).  Open SQL is the preferred option as is platform independant.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;andy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:00:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119372#M443960</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:00:25Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119373#M443961</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;The main purpose of using internal tables is to take out the burden on database..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See let us suppose 10 persons are using MARA table and modifying it or fetching data from it or doing some manupulations..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So if they are not using internal table , all of them together are hitting the mara table and thus the performance of data from database will become very low and reports etc will run very slowly..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If they are using internal table by fetching data from the MARA and doing manupulation in there system , It is specific to that system performance and thus the peroformance of DATABASE will be finally good is using internal tables..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rewards points if useful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;nazeer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:03:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119373#M443961</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:03:01Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119374#M443962</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;Please go through this link to have more idea on internal tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/ab009.htm" target="test_blank"&gt;http://www.sap-img.com/ab009.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;Preeti&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:03:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119374#M443962</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:03:34Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119375#M443963</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;Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt; Sudheer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:05:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119375#M443963</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:05:13Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119376#M443964</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;Internal tables are basically structures, which are used to store data.&lt;/P&gt;&lt;P&gt;The data,which is needed to be displayed, say, in the form of a report output, &lt;/P&gt;&lt;P&gt;is fetched first in the internal table, from the database table, and is then displayed.&lt;/P&gt;&lt;P&gt;Using internal tables decreases the number of hits to the actual database, and in this way, increases the performance of the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg. of an internal table:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Types:begin of itab_struct,&lt;/P&gt;&lt;P&gt;..... "Data declarations&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;end of itab_struct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data:itab type table of itab_struct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data:wa_itab like line of itab_struct.   "Workarea.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thnaks and regards,&lt;/P&gt;&lt;P&gt;Prerna&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:18:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119376#M443964</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:18:46Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119377#M443965</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;While adding or retrieving records to / from internal table we have to keep the record temporarily. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The area where this record is kept is called as work area for the internal table.  The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header line is a implicit work area for the internal table.  It depends on how the internal table is declared that the itab will have the header line or not. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Declaration of internal table:&lt;/P&gt;&lt;P&gt;e.g. &lt;/P&gt;&lt;P&gt;data: begin of itab occurs 10, &lt;/P&gt;&lt;P&gt;           ab type c, &lt;/P&gt;&lt;P&gt;           cd type i, &lt;/P&gt;&lt;P&gt;        end of itab.  " this table will have the header line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Subashini.J&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:21:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119377#M443965</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:21:42Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119378#M443966</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naga Mrudula,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internal tables &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects A data type is the abstract description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The data type is also an attribute of an existing data object. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internal Tables as Data Types&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internal tables and structures are the two structured data types in ABAP. The data type of an internal table is fully specified by its line type, key, and table type. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Line type&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the structure is a column in the internal table. However, the line type may also be elementary or another internal table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this resolves your query.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all the helpful answers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:23:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119378#M443966</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:23:15Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119379#M443967</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi mrudula,&lt;/P&gt;&lt;P&gt;    Long life data are stored in the database table. We can't afford to lose data from the database table. Hence v need of a intermediate table where v can put in all our datas and work with that, thus avoiding accidental loss of data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This intermediate tables are nothing but called as internal tables, which are created during runtime and reserves no memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are 3 types of internal tables.&lt;/P&gt;&lt;P&gt;1)standard&lt;/P&gt;&lt;P&gt;2)sorted&lt;/P&gt;&lt;P&gt;3)hashed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Arun.&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>Thu, 19 Apr 2007 12:24:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119379#M443967</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:24:02Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119380#M443968</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;why we will loose data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:30:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119380#M443968</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119381#M443969</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;SAP R/3 is working on application server, it does not have its own database.&lt;/P&gt;&lt;P&gt;It fetches data from database through native SQL (as per database like oracle, DB2, sybase etc)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This data it stores in INTERNAL TABLES just like a buffer withn the application server. The data manipulation is done on application server by playing with INTERNAL TABLES.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally the end output ITAB is stored back to DB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Sandeep&lt;/P&gt;&lt;P&gt;Reward if helpful&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:35:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119381#M443969</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:35:27Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119382#M443970</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naga mrudula,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internal tables are a very important concept of ABAP. &lt;/P&gt;&lt;P&gt;They are use to store the data of database tables temporarily. &lt;/P&gt;&lt;P&gt;This is done to ensure that the Database is not accessed continuously.&lt;/P&gt;&lt;P&gt;You can do any processing on the data in the internal tables and finally save the processed data from the internal table to the database table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ABAP doesn't support arrays.&lt;/P&gt;&lt;P&gt;Internal table is like multi dimensional arrays where you can store data in &lt;/P&gt;&lt;P&gt;rows and columns.&lt;/P&gt;&lt;P&gt;It contains header line.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header line is nothing but a work area of the table.&lt;/P&gt;&lt;P&gt;Either you can have header line in the internal table or you can declare a work area separately.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HEADER &amp;amp; BODY: Every table(be it internal or transparent)contains two sections: Header and Body.&lt;/P&gt;&lt;P&gt;Header is a workarea of the table which acts as an interface for the table. Header can have only one record at a time&lt;/P&gt;&lt;P&gt;Body is the entire table containing the data or records. Body is a collection of records.&lt;/P&gt;&lt;P&gt;Structure of header and body are same for a particular table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;internal table.&lt;/P&gt;&lt;P&gt;data: begin of itab occurs 0,&lt;/P&gt;&lt;P&gt;matnr like mara-matnr,&lt;/P&gt;&lt;P&gt;maktx like makt-maktx,&lt;/P&gt;&lt;P&gt;end of itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Archana Suresh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:44:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119382#M443970</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119383#M443971</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;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;Internal tables&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1)Internal tables means of taking data from a fixed structure and storing it in working memory in ABAP. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) The data is stored&amp;lt;b&amp;gt; line by line in memory&amp;lt;/b&amp;gt;, and each line has the same structure. In ABAP, internal tables fulfill the &amp;lt;b&amp;gt;function of arrays&amp;lt;/b&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) An internal table is a run time instance.  It get created when program starts execution. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4)It get destroyed when program terminates. it has two different parts.  HeaderLine(optional) &amp;amp; Body(Compulsory). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5)Any value that comes to or goes from interanal table , that travels through headerline. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;A related program is .&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;*declaration.&amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: begin of inernaltable occurs 0, &lt;/P&gt;&lt;P&gt;         x type c, &lt;/P&gt;&lt;P&gt;         y type i, &lt;/P&gt;&lt;P&gt;      end of itab. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;*initializing headerline&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   internaltable-x = 'd'. &lt;/P&gt;&lt;P&gt;   internaltable-y = 34. &lt;/P&gt;&lt;P&gt;   &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;*storing value into internal table&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appene internaltable .  &lt;/P&gt;&lt;P&gt;appene internaltable . &lt;/P&gt;&lt;P&gt;appene internaltable . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;*reading internal table&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;loop at itab . &lt;/P&gt;&lt;P&gt;   write: / internaltable-x, internaltable-y.  &amp;lt;b&amp;gt;"writes to output list&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;endloop. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps u,&lt;/P&gt;&lt;P&gt;reward points if useful&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ginni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 19 Apr 2007 12:49:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-tables/m-p/2119383#M443971</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-19T12:49:30Z</dc:date>
    </item>
  </channel>
</rss>

