<?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: What are nested Internal tables in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-nested-internal-tables/m-p/2422826#M541010</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;&lt;/P&gt;&lt;P&gt;When storing data in internal tables, you often use one internal table for each database you read.&lt;/P&gt;&lt;P&gt;Each one contains some or all columns of the relevant database table. It is up to you whether&lt;/P&gt;&lt;P&gt;you create an internal table with a flat structure for each database table or if you create, for&lt;/P&gt;&lt;P&gt;example, internal tables with nested structures. If you have several tables, each one with a flat&lt;/P&gt;&lt;P&gt;structure, you have to work with redundant key fields to link the tables. If, on the other hand, you&lt;/P&gt;&lt;P&gt;use nested internal tables, you can store the data from the database tables hierarchically.&lt;/P&gt;&lt;P&gt;Saving and processing very large amounts of data in internal tables has disadvantages. If you&lt;/P&gt;&lt;P&gt;divide up the data into different internal tables, processing it can be very runtime-intensive, since&lt;/P&gt;&lt;P&gt;the tables have to be processed individually. Furthermore, it requires a lot of storage space,&lt;/P&gt;&lt;P&gt;since internal tables are not stored in compressed form. The system may even need to store the&lt;/P&gt;&lt;P&gt;dataset outside of its working memory. This means that processing it takes even longer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An example of nested internal table:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assume the following program is linked to the logical database [Page 1163] F1S.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT DEMO.&lt;/P&gt;&lt;P&gt;DATA: SUM TYPE I, CNT TYPE I.&lt;/P&gt;&lt;P&gt;NODES: SPFLI, SFLIGHT, SBOOK.&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF WA_SBOOK,&lt;/P&gt;&lt;P&gt;BOOKID TYPE SBOOK-BOOKID,&lt;/P&gt;&lt;P&gt;SMOKER TYPE SBOOK-SMOKER,&lt;/P&gt;&lt;P&gt;CLASS TYPE SBOOK-CLASS,&lt;/P&gt;&lt;P&gt;LUGGWEIGHT TYPE SBOOK-LUGGWEIGHT,&lt;/P&gt;&lt;P&gt;WUNIT TYPE SBOOK-WUNIT,&lt;/P&gt;&lt;P&gt;END OF WA_SBOOK.&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF WA_SFLIGHT,&lt;/P&gt;&lt;P&gt;FLDATE TYPE SFLIGHT-FLDATE,&lt;/P&gt;&lt;P&gt;SBOOK LIKE TABLE OF WA_SBOOK,&lt;/P&gt;&lt;P&gt;END OF WA_SFLIGHT.&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF WA_SPFLI,&lt;/P&gt;&lt;P&gt;CARRID TYPE SPFLI-CARRID,&lt;/P&gt;&lt;P&gt;CONNID TYPE SPFLI-CONNID,&lt;/P&gt;&lt;P&gt;CITYFROM TYPE SPFLI-CITYFROM,&lt;/P&gt;&lt;P&gt;CITYTO TYPE SPFLI-CITYTO,&lt;/P&gt;&lt;P&gt;SFLIGHT LIKE TABLE OF WA_SFLIGHT,&lt;/P&gt;&lt;P&gt;END OF WA_SPFLI.&lt;/P&gt;&lt;P&gt;DATA TAB_SPFLI LIKE TABLE OF WA_SPFLI.&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;GET SPFLI.&lt;/P&gt;&lt;P&gt;REFRESH WA_SPFLI-SFLIGHT.&lt;/P&gt;&lt;P&gt;GET SFLIGHT.&lt;/P&gt;&lt;P&gt;REFRESH WA_SFLIGHT-SBOOK.&lt;/P&gt;&lt;P&gt;GET SBOOK.&lt;/P&gt;&lt;P&gt;MOVE-CORRESPONDING SBOOK TO WA_SBOOK.&lt;/P&gt;&lt;P&gt;APPEND WA_SBOOK TO WA_SFLIGHT-SBOOK.&lt;/P&gt;&lt;P&gt;GET SFLIGHT LATE.&lt;/P&gt;&lt;P&gt;MOVE-CORRESPONDING SFLIGHT TO WA_SFLIGHT.&lt;/P&gt;&lt;P&gt;APPEND WA_SFLIGHT TO WA_SPFLI-SFLIGHT.&lt;/P&gt;&lt;P&gt;GET SPFLI LATE.&lt;/P&gt;&lt;P&gt;MOVE-CORRESPONDING SPFLI TO WA_SPFLI.&lt;/P&gt;&lt;P&gt;APPEND WA_SPFLI TO TAB_SPFLI.&lt;/P&gt;&lt;P&gt;END-OF-SELECTION.&lt;/P&gt;&lt;P&gt;SORT TAB_SPFLI BY CITYFROM CITYTO CONNID.&lt;/P&gt;&lt;P&gt;LOOP AT TAB_SPFLI INTO WA_SPFLI.&lt;/P&gt;&lt;P&gt;SKIP.&lt;/P&gt;&lt;P&gt;WRITE: / WA_SPFLI-CARRID,&lt;/P&gt;&lt;P&gt;WA_SPFLI-CONNID,&lt;/P&gt;&lt;P&gt;'from', (15) WA_SPFLI-CITYFROM,&lt;/P&gt;&lt;P&gt;'to', (15) WA_SPFLI-CITYTO.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;SORT WA_SPFLI-SFLIGHT BY FLDATE.&lt;/P&gt;&lt;P&gt;LOOP AT WA_SPFLI-SFLIGHT INTO WA_SFLIGHT.&lt;/P&gt;&lt;P&gt;SKIP.&lt;/P&gt;&lt;P&gt;WRITE: / 'Date:', WA_SFLIGHT-FLDATE.&lt;/P&gt;&lt;P&gt;WRITE: 20 'Book-ID', 40 'Smoker', 50 'Class'.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;SORT WA_SFLIGHT-SBOOK BY CLASS SMOKER BOOKID.&lt;/P&gt;&lt;P&gt;SUM = 0.&lt;/P&gt;&lt;P&gt;CNT = 0.&lt;/P&gt;&lt;P&gt;LOOP AT WA_SFLIGHT-SBOOK INTO WA_SBOOK.&lt;/P&gt;&lt;P&gt;WRITE: / WA_SBOOK-BOOKID UNDER 'Book-ID',&lt;/P&gt;&lt;P&gt;WA_SBOOK-SMOKER UNDER 'Smoker',&lt;/P&gt;&lt;P&gt;WA_SBOOK-CLASS UNDER 'Class'.&lt;/P&gt;&lt;P&gt;SUM = SUM + WA_SBOOK-LUGGWEIGHT.&lt;/P&gt;&lt;P&gt;CNT = CNT + 1.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;WRITE: 'Number of bookings: ', (3) CNT,&lt;/P&gt;&lt;P&gt;/ 'Total luggage weight:',&lt;/P&gt;&lt;P&gt;(3) SUM, WA_SBOOK-WUNIT.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Jun 2007 04:55:11 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-27T04:55:11Z</dc:date>
    <item>
      <title>What are nested Internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-nested-internal-tables/m-p/2422825#M541009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Guru's,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am new to ABAP ...just trying to learn things.Can you please explain me what are nested internal tables and what is the purpose of nested internal table?where can it be used and why a header line is not written in a Nested Internal table...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kindly explain it (scenario where nested internal tables are used) with an example it will be helpful.&lt;/P&gt;&lt;P&gt; &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Priyanka&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jun 2007 04:52:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-nested-internal-tables/m-p/2422825#M541009</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-27T04:52:55Z</dc:date>
    </item>
    <item>
      <title>Re: What are nested Internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-nested-internal-tables/m-p/2422826#M541010</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;&lt;/P&gt;&lt;P&gt;When storing data in internal tables, you often use one internal table for each database you read.&lt;/P&gt;&lt;P&gt;Each one contains some or all columns of the relevant database table. It is up to you whether&lt;/P&gt;&lt;P&gt;you create an internal table with a flat structure for each database table or if you create, for&lt;/P&gt;&lt;P&gt;example, internal tables with nested structures. If you have several tables, each one with a flat&lt;/P&gt;&lt;P&gt;structure, you have to work with redundant key fields to link the tables. If, on the other hand, you&lt;/P&gt;&lt;P&gt;use nested internal tables, you can store the data from the database tables hierarchically.&lt;/P&gt;&lt;P&gt;Saving and processing very large amounts of data in internal tables has disadvantages. If you&lt;/P&gt;&lt;P&gt;divide up the data into different internal tables, processing it can be very runtime-intensive, since&lt;/P&gt;&lt;P&gt;the tables have to be processed individually. Furthermore, it requires a lot of storage space,&lt;/P&gt;&lt;P&gt;since internal tables are not stored in compressed form. The system may even need to store the&lt;/P&gt;&lt;P&gt;dataset outside of its working memory. This means that processing it takes even longer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An example of nested internal table:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assume the following program is linked to the logical database [Page 1163] F1S.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT DEMO.&lt;/P&gt;&lt;P&gt;DATA: SUM TYPE I, CNT TYPE I.&lt;/P&gt;&lt;P&gt;NODES: SPFLI, SFLIGHT, SBOOK.&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF WA_SBOOK,&lt;/P&gt;&lt;P&gt;BOOKID TYPE SBOOK-BOOKID,&lt;/P&gt;&lt;P&gt;SMOKER TYPE SBOOK-SMOKER,&lt;/P&gt;&lt;P&gt;CLASS TYPE SBOOK-CLASS,&lt;/P&gt;&lt;P&gt;LUGGWEIGHT TYPE SBOOK-LUGGWEIGHT,&lt;/P&gt;&lt;P&gt;WUNIT TYPE SBOOK-WUNIT,&lt;/P&gt;&lt;P&gt;END OF WA_SBOOK.&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF WA_SFLIGHT,&lt;/P&gt;&lt;P&gt;FLDATE TYPE SFLIGHT-FLDATE,&lt;/P&gt;&lt;P&gt;SBOOK LIKE TABLE OF WA_SBOOK,&lt;/P&gt;&lt;P&gt;END OF WA_SFLIGHT.&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF WA_SPFLI,&lt;/P&gt;&lt;P&gt;CARRID TYPE SPFLI-CARRID,&lt;/P&gt;&lt;P&gt;CONNID TYPE SPFLI-CONNID,&lt;/P&gt;&lt;P&gt;CITYFROM TYPE SPFLI-CITYFROM,&lt;/P&gt;&lt;P&gt;CITYTO TYPE SPFLI-CITYTO,&lt;/P&gt;&lt;P&gt;SFLIGHT LIKE TABLE OF WA_SFLIGHT,&lt;/P&gt;&lt;P&gt;END OF WA_SPFLI.&lt;/P&gt;&lt;P&gt;DATA TAB_SPFLI LIKE TABLE OF WA_SPFLI.&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;GET SPFLI.&lt;/P&gt;&lt;P&gt;REFRESH WA_SPFLI-SFLIGHT.&lt;/P&gt;&lt;P&gt;GET SFLIGHT.&lt;/P&gt;&lt;P&gt;REFRESH WA_SFLIGHT-SBOOK.&lt;/P&gt;&lt;P&gt;GET SBOOK.&lt;/P&gt;&lt;P&gt;MOVE-CORRESPONDING SBOOK TO WA_SBOOK.&lt;/P&gt;&lt;P&gt;APPEND WA_SBOOK TO WA_SFLIGHT-SBOOK.&lt;/P&gt;&lt;P&gt;GET SFLIGHT LATE.&lt;/P&gt;&lt;P&gt;MOVE-CORRESPONDING SFLIGHT TO WA_SFLIGHT.&lt;/P&gt;&lt;P&gt;APPEND WA_SFLIGHT TO WA_SPFLI-SFLIGHT.&lt;/P&gt;&lt;P&gt;GET SPFLI LATE.&lt;/P&gt;&lt;P&gt;MOVE-CORRESPONDING SPFLI TO WA_SPFLI.&lt;/P&gt;&lt;P&gt;APPEND WA_SPFLI TO TAB_SPFLI.&lt;/P&gt;&lt;P&gt;END-OF-SELECTION.&lt;/P&gt;&lt;P&gt;SORT TAB_SPFLI BY CITYFROM CITYTO CONNID.&lt;/P&gt;&lt;P&gt;LOOP AT TAB_SPFLI INTO WA_SPFLI.&lt;/P&gt;&lt;P&gt;SKIP.&lt;/P&gt;&lt;P&gt;WRITE: / WA_SPFLI-CARRID,&lt;/P&gt;&lt;P&gt;WA_SPFLI-CONNID,&lt;/P&gt;&lt;P&gt;'from', (15) WA_SPFLI-CITYFROM,&lt;/P&gt;&lt;P&gt;'to', (15) WA_SPFLI-CITYTO.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;SORT WA_SPFLI-SFLIGHT BY FLDATE.&lt;/P&gt;&lt;P&gt;LOOP AT WA_SPFLI-SFLIGHT INTO WA_SFLIGHT.&lt;/P&gt;&lt;P&gt;SKIP.&lt;/P&gt;&lt;P&gt;WRITE: / 'Date:', WA_SFLIGHT-FLDATE.&lt;/P&gt;&lt;P&gt;WRITE: 20 'Book-ID', 40 'Smoker', 50 'Class'.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;SORT WA_SFLIGHT-SBOOK BY CLASS SMOKER BOOKID.&lt;/P&gt;&lt;P&gt;SUM = 0.&lt;/P&gt;&lt;P&gt;CNT = 0.&lt;/P&gt;&lt;P&gt;LOOP AT WA_SFLIGHT-SBOOK INTO WA_SBOOK.&lt;/P&gt;&lt;P&gt;WRITE: / WA_SBOOK-BOOKID UNDER 'Book-ID',&lt;/P&gt;&lt;P&gt;WA_SBOOK-SMOKER UNDER 'Smoker',&lt;/P&gt;&lt;P&gt;WA_SBOOK-CLASS UNDER 'Class'.&lt;/P&gt;&lt;P&gt;SUM = SUM + WA_SBOOK-LUGGWEIGHT.&lt;/P&gt;&lt;P&gt;CNT = CNT + 1.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;ULINE.&lt;/P&gt;&lt;P&gt;WRITE: 'Number of bookings: ', (3) CNT,&lt;/P&gt;&lt;P&gt;/ 'Total luggage weight:',&lt;/P&gt;&lt;P&gt;(3) SUM, WA_SBOOK-WUNIT.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jun 2007 04:55:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-nested-internal-tables/m-p/2422826#M541010</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-27T04:55:11Z</dc:date>
    </item>
    <item>
      <title>Re: What are nested Internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-nested-internal-tables/m-p/2422827#M541011</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;Nested internal tables are when you make a field which is TYPED with a TABLE TYPE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is one of your strucutre field is a TABLE TYPE so when you create a INTENRAL TABLE of this Strucutre this internal table field containes one of its field as another INTERNAL table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They are also concidered DEEP STRUCUTRES as we will not the size of the internal table at the decleration time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: begin of NES_STRUCT,&lt;/P&gt;&lt;P&gt;field1(10) type C,&lt;/P&gt;&lt;P&gt;nested_tab type table of SPFLI,&lt;/P&gt;&lt;P&gt;end of NES_STRUCT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now NES_STRUCT is a strcutre which has an internal table in it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now &lt;/P&gt;&lt;P&gt;DATA: IT_NES_STRUCT LIKE TABLE OF NES_STRUCT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now IT_NES_STRUCT is an intenral table with each record of it having a field with name "nested_tab" which is an internal table itself.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sesh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jun 2007 04:55:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-nested-internal-tables/m-p/2422827#M541011</guid>
      <dc:creator>seshatalpasai_madala</dc:creator>
      <dc:date>2007-06-27T04:55:55Z</dc:date>
    </item>
    <item>
      <title>Re: What are nested Internal tables</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-nested-internal-tables/m-p/2422828#M541012</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;structures containing internal tables as components or&lt;/P&gt;&lt;P&gt;Internal table containing Structure as components are called Deep Internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please check this link for reading a deep structure. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="212928"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;TYPES: BEGIN OF TYPE_DEEP,&lt;/P&gt;&lt;P&gt;              MATNR TYPE MATNR,               &lt;/P&gt;&lt;P&gt;              T_MARC TYPE MARC OCCURS 0,&lt;/P&gt;&lt;P&gt;            END OF TYPE_DEEP.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;DATA: T_DEEP     TYPE STANDARD TABLE OF TYPE_DEEP.&lt;/P&gt;&lt;P&gt;DATA: WA_DEEP TYPE TYPE_DEEP.&lt;/P&gt;&lt;P&gt;DATA: T_MARC    TYPE TABLE OF MARC.&lt;/P&gt;&lt;P&gt;DATA: S_MARC    TYPE MARC.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Populating data.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;WA_DEEP-MATNR = 'TEST'.&lt;/P&gt;&lt;P&gt;S_MARC-MATNR = 'TEST'.&lt;/P&gt;&lt;P&gt;S_MARC-WERKS = '9090'.&lt;/P&gt;&lt;P&gt;APPEND S_MARC TO T_MARC.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Append second level internal table.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;WA_DEEP-T_MARC[] = T_MARC[].&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Append.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;APPEND WA_DEEP TO T_DEEP.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Process the internal table.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;LOOP AT T_DEEP INTO WA_DEEP.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  WRITE: / WA_DEEP-MATNR.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;PROCESS the second level internal table.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;   LOOP AT WA_DEEP-T_MARC INTO S_MARC.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;    WRITE: S_MARC-WERKS.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;   ENDLOOP. &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points for useful Answers&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anji&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Jun 2007 04:56:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-nested-internal-tables/m-p/2422828#M541012</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-27T04:56:36Z</dc:date>
    </item>
  </channel>
</rss>

