<?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: Package size in Select query.. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224161#M768975</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dhanush,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What's the purpose of using PACKAGE SIZE in select statement?  &lt;/P&gt;&lt;P&gt;Package size can be used if you for example only want to finish processing a limited amount of data at a time due to lack of memory. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The example below  read 50 records at a time from VBAK into an internal table, and selects the corresponding entries from vbap into an internal table. Then the two internal tables can be processed, and the next 50 records from VBAk can be read. Remember to reinitialize tha tables before the next read.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT  z_test. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES: &lt;/P&gt;&lt;P&gt;  BEGIN OF t_vbak, &lt;/P&gt;&lt;P&gt;    vbeln LIKE vbak-vbeln, &lt;/P&gt;&lt;P&gt;    erdat LIKE vbak-erdat, &lt;/P&gt;&lt;P&gt;  END OF t_vbak, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  BEGIN OF t_vbap, &lt;/P&gt;&lt;P&gt;    posnr  LIKE vbap-posnr, &lt;/P&gt;&lt;P&gt;    matnr  LIKE vbap-matnr, &lt;/P&gt;&lt;P&gt;    meins  LIKE vbap-meins, &lt;/P&gt;&lt;P&gt;  END OF t_vbap, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  BEGIN OF t_report, &lt;/P&gt;&lt;P&gt;    vbeln LIKE vbak-vbeln, &lt;/P&gt;&lt;P&gt;    erdat LIKE vbak-erdat, &lt;/P&gt;&lt;P&gt;    posnr  LIKE vbap-posnr, &lt;/P&gt;&lt;P&gt;    matnr  LIKE vbap-matnr, &lt;/P&gt;&lt;P&gt;    meins  LIKE vbap-meins, &lt;/P&gt;&lt;P&gt;  END OF t_report. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: &lt;/P&gt;&lt;P&gt;  li_vbak   TYPE t_vbak OCCURS 0, &lt;/P&gt;&lt;P&gt;  l_vbak    TYPE  t_vbak, &lt;/P&gt;&lt;P&gt;  li_vbap   TYPE t_vbap OCCURS 0, &lt;/P&gt;&lt;P&gt;  l_vbap    TYPE t_vbap, &lt;/P&gt;&lt;P&gt;  li_report TYPE t_report OCCURS 0, &lt;/P&gt;&lt;P&gt;  l_report  TYPE t_report. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION. &lt;/P&gt;&lt;P&gt;  SELECT vbeln erdat &lt;/P&gt;&lt;P&gt;    FROM vbak &lt;/P&gt;&lt;P&gt;    INTO TABLE li_vbak PACKAGE SIZE 50. &lt;/P&gt;&lt;P&gt;    SELECT posnr matnr meins &lt;/P&gt;&lt;P&gt;      FROM vbap &lt;/P&gt;&lt;P&gt;      INTO TABLE li_vbap &lt;/P&gt;&lt;P&gt;      FOR ALL ENTRIES IN li_vbak &lt;/P&gt;&lt;P&gt;      WHERE vbeln = li_vbak-vbeln. &lt;/P&gt;&lt;P&gt;    IF sy-subrc = 0. &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  Now you have the two internal tables li_vbak and li_vbap filled &lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  with data. &lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  Do something with the data - remember to reinitialize internal &lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  tables &lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    ENDIF. &lt;/P&gt;&lt;P&gt;  ENDSELECT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*-- End of Program &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This specifies a quantity of data records from the archiving object master table that is clearly defined by package limits. A package is an indivisible unit (in terms of the distribution between parallel jobs) used for the parallel processing of mass data, meaning that it is processed by precisely one job.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package limits: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These specify the quantity of data contained in a package. Package limits consist of one upper and one lower restrictive value for the package formation attributes. They are used as selection criteria for the data retrieval of the process phases that have run in parallel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package size:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This specifies the number of data records in a package.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package formation attributes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These specify one or more fields from the archiving object master table, used by the system to define package limits. Check which fields you select as package formation attributes in the Archiving Workbench step Create External Parallel Processing Key. For more information, refer to the documentation on this activity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package profile:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This specifies a quantity of package limits formed by the system during the pre-step process. The package profile is used to divide up the whole value range of package formation attributes. Package limits must never overlap.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package formation strategy: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the algorithm used to form package profiles. The aim of this algorithm is to form a package profile in such a way that the parallel processing tool can form packages of an approximately equal size. The Archiving Workbench does not set the characteristic values of this algorithm; you or your customer must do this. The decision as to which algorithm is the most suitable depends on the conditions of the archiving object in question. The algorithm must be implemented by a function module registered by a corresponding Customizing entry for the archiving object in IMG activity Maintain Global Control of Archiving.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &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;&lt;/P&gt;&lt;P&gt;reward if useful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks and regards&lt;/P&gt;&lt;P&gt;suma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 10 Jan 2008 09:59:17 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-10T09:59:17Z</dc:date>
    <item>
      <title>Package size in Select query..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224154#M768968</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Friend,&lt;/P&gt;&lt;P&gt;              I have doubts in Package Size using select query..Could u tell me What is the use of it nad y we r using...Plz suggest me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dhanush.S.T&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 09:41:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224154#M768968</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T09:41:01Z</dc:date>
    </item>
    <item>
      <title>Re: Package size in Select query..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224155#M768969</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dhanush,&lt;/P&gt;&lt;P&gt;Here is brief explanation of packet size..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package size can be used to retreive a spcific number of records at a time. This can be used if you for example only want tofinish processing a limited amount of data at a time due to lack of memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The exampel below read 50 records at a time from VBAK into an internal table, and selects the corresponding entries from vbap into an internal table. Then the two internal tables can be processed, and the next 50 records from VBAk can be read. remeber to reinitialize tha tables before the next read.&lt;/P&gt;&lt;P&gt;PACKAGE SIZE n &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Works like ... INTO wa, except that the selected data is not placed in the internal table itab line by line, but in packets of n lines. The old contents of itab are overwritten. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;n &amp;lt;= 0 causes a runtime error. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internally, n is placed in a type I field. Here, the usual conversion rules apply (see MOVE). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After leaving the processing loop, the contents of the internal table itab are undefined. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the result of the selection is a table, the data is retrieved in a processing loop introduced by SELECT and concluded by ENDSELECT. The processing passes through the loop once for each line read. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT z_test .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES:BEGIN OF t_vbak,&lt;/P&gt;&lt;P&gt;               vbeln LIKE vbak-vbeln,&lt;/P&gt;&lt;P&gt;              erdat LIKE vbak-erdat, &lt;/P&gt;&lt;P&gt;            END OF t_vbak, &lt;/P&gt;&lt;P&gt;            BEGIN OF t_vbap,&lt;/P&gt;&lt;P&gt;              posnr LIKE vbap-posnr, &lt;/P&gt;&lt;P&gt;              matnr LIKE vbap-matnr,&lt;/P&gt;&lt;P&gt;              meins LIKE vbap-meins,&lt;/P&gt;&lt;P&gt;           END OF t_vbap, &lt;/P&gt;&lt;P&gt;           BEGIN OF t_report,&lt;/P&gt;&lt;P&gt;              vbeln LIKE vbak-vbeln,&lt;/P&gt;&lt;P&gt;              erdat LIKE vbak-erdat,&lt;/P&gt;&lt;P&gt;              posnr LIKE vbap-posnr,&lt;/P&gt;&lt;P&gt;             matnr LIKE vbap-matnr, &lt;/P&gt;&lt;P&gt;             meins LIKE vbap-meins,&lt;/P&gt;&lt;P&gt;         END OF t_report. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA:li_vbak TYPE t_vbak OCCURS 0,&lt;/P&gt;&lt;P&gt;            l_vbak TYPE t_vbak,&lt;/P&gt;&lt;P&gt;           li_vbap TYPE t_vbap OCCURS 0,&lt;/P&gt;&lt;P&gt;            l_vbap TYPE t_vbap,&lt;/P&gt;&lt;P&gt;           li_report TYPE t_report OCCURS 0,&lt;/P&gt;&lt;P&gt;            l_report TYPE t_report. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT vbeln erdat FROM vbak INTO TABLE li_vbak &lt;STRONG&gt;PACKAGE SIZE 50.&lt;/STRONG&gt; &lt;/P&gt;&lt;P&gt;SELECT posnr matnr meins FROM vbap INTO TABLE li_vbap FOR ALL ENTRIES IN li_vbak WHERE vbeln = li_vbak-vbeln.&lt;/P&gt;&lt;P&gt;IF sy-subrc = 0. &lt;/P&gt;&lt;P&gt;. Now you have the two internal tables li_vbak and li_vbap filled &lt;/P&gt;&lt;P&gt;with data. &lt;/P&gt;&lt;P&gt;. Do something with the data - remember to reinitialize internal &lt;/P&gt;&lt;P&gt;tables &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ENDIF. &lt;/P&gt;&lt;P&gt;ENDSELECT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Reward if helpful.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thankyou,&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 09:43:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224155#M768969</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T09:43:00Z</dc:date>
    </item>
    <item>
      <title>Re: Package size in Select query..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224156#M768970</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dhanush,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you use the PACKAGE SIZE addition, the lines of the selection are not written into the internal table at once, but in packets. You can define packets of &amp;lt;n&amp;gt; lines that are written one after the other into the internal table. If you use INTO, each packet replaces the preceding one. If you use APPENDING, the packets are inserted one after the other. This is only possible in a loop that ends with ENDSELECT. Outside the SELECT loop, the contents of the internal table are undetermined. You must process the selected lines within the loop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EX; Suppose you are extracting 100000 records from a table which is going dump because of long time(say 60 minutes.) extraction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assume basis person setted seeion time 15 minutes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when extraction crosses 15 minutes it will go dump.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That situation use package size&lt;/P&gt;&lt;P&gt;assume  15000 which takes 14 min.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select records package 15000 into appending internal table.&lt;/P&gt;&lt;P&gt;till 15000 records comes statement exexutes and append the internal table.Like wise you can extract data without dump..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Don't forget to reward if useful....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 09:53:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224156#M768970</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T09:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: Package size in Select query..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224157#M768971</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PACKAGE SIZE in the Select Query is used to fix the number of records we want to fetch from the Table for each Iteration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have to use it with SELECT .. ENDSELECT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;awrd points if useful&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bhupal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 09:53:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224157#M768971</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T09:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: Package size in Select query..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224158#M768972</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dhanush,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package size is used when you have to process a large chunk of records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you will use package size in your select command, the select command will process that much of records in lots that your are passing in package size. For example if you have mentioned 10000 in package size then the select command will process 10000 records in lots.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case you will not get run time error due to time limit exceed error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;mukesh kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 09:54:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224158#M768972</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T09:54:03Z</dc:date>
    </item>
    <item>
      <title>Re: Package size in Select query..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224159#M768973</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PACKAGE SIZE n &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Works like ... INTO wa, except that the selected data is not placed in the internal table itab line by line, but in packets of n lines. The old contents of itab are overwritten. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;n &amp;lt;= 0 causes a runtime error. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internally, n is placed in a type I field. Here, the usual conversion rules apply (see MOVE). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After leaving the processing loop, the contents of the internal table itab are undefined. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the result of the selection is a table, the data is retrieved in a processing loop introduced by SELECT and concluded by ENDSELECT. The processing passes through the loop once for each line read. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example &lt;/P&gt;&lt;P&gt;Output a list of all airlines (with short description and name): &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: itab TYPE STANDARD TABLE OF SCARR WITH NON-UNIQUE &lt;/P&gt;&lt;P&gt;DEFAULT KEY INITIAL SIZE 10. &lt;/P&gt;&lt;P&gt;FIELD-SYMBOLS: &amp;lt;FS&amp;gt; TYPE scarr. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SELECT * INTO TABLE itab PACKAGE SIZE 20 FROM scarr. &lt;/P&gt;&lt;P&gt;LOOP AT itab ASSIGNING &amp;lt;FS&amp;gt;. &lt;/P&gt;&lt;P&gt;WRITE: / &amp;lt;FS&amp;gt;-carrid, &amp;lt;FS&amp;gt;-carrname. &lt;/P&gt;&lt;P&gt;ENDLOOP. &lt;/P&gt;&lt;P&gt;ENDSELECT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example 2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package size can be used if you for example only want to finish processing a limited amount of data at a time due to lack of memory. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The example below read 50 records at a time from VBAK into an internal table, and selects the corresponding entries from vbap into an internal table. Then the two internal tables can be processed, and the next 50 records from VBAk can be read. Remember to reinitialize tha tables before the next read. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT z_test. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES: &lt;/P&gt;&lt;P&gt;BEGIN OF t_vbak, &lt;/P&gt;&lt;P&gt;vbeln LIKE vbak-vbeln, &lt;/P&gt;&lt;P&gt;erdat LIKE vbak-erdat, &lt;/P&gt;&lt;P&gt;END OF t_vbak, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BEGIN OF t_vbap, &lt;/P&gt;&lt;P&gt;posnr LIKE vbap-posnr, &lt;/P&gt;&lt;P&gt;matnr LIKE vbap-matnr, &lt;/P&gt;&lt;P&gt;meins LIKE vbap-meins, &lt;/P&gt;&lt;P&gt;END OF t_vbap, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BEGIN OF t_report, &lt;/P&gt;&lt;P&gt;vbeln LIKE vbak-vbeln, &lt;/P&gt;&lt;P&gt;erdat LIKE vbak-erdat, &lt;/P&gt;&lt;P&gt;posnr LIKE vbap-posnr, &lt;/P&gt;&lt;P&gt;matnr LIKE vbap-matnr, &lt;/P&gt;&lt;P&gt;meins LIKE vbap-meins, &lt;/P&gt;&lt;P&gt;END OF t_report. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: &lt;/P&gt;&lt;P&gt;li_vbak TYPE t_vbak OCCURS 0, &lt;/P&gt;&lt;P&gt;l_vbak TYPE t_vbak, &lt;/P&gt;&lt;P&gt;li_vbap TYPE t_vbap OCCURS 0, &lt;/P&gt;&lt;P&gt;l_vbap TYPE t_vbap, &lt;/P&gt;&lt;P&gt;li_report TYPE t_report OCCURS 0, &lt;/P&gt;&lt;P&gt;l_report TYPE t_report. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION. &lt;/P&gt;&lt;P&gt;SELECT vbeln erdat &lt;/P&gt;&lt;P&gt;FROM vbak &lt;/P&gt;&lt;P&gt;INTO TABLE li_vbak PACKAGE SIZE 50. &lt;/P&gt;&lt;P&gt;SELECT posnr matnr meins &lt;/P&gt;&lt;P&gt;FROM vbap &lt;/P&gt;&lt;P&gt;INTO TABLE li_vbap &lt;/P&gt;&lt;P&gt;FOR ALL ENTRIES IN li_vbak &lt;/P&gt;&lt;P&gt;WHERE vbeln = li_vbak-vbeln. &lt;/P&gt;&lt;P&gt;IF sy-subrc = 0. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now you have the two internal tables li_vbak and li_vbap filled &lt;/P&gt;&lt;P&gt;with data. &lt;/P&gt;&lt;P&gt;Do something with the data - remember to reinitialize internal &lt;/P&gt;&lt;P&gt;tables &lt;/P&gt;&lt;P&gt;ENDIF. &lt;/P&gt;&lt;P&gt;ENDSELECT.&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, 10 Jan 2008 09:54:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224159#M768973</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T09:54:45Z</dc:date>
    </item>
    <item>
      <title>Re: Package size in Select query..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224160#M768974</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; Package Size&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to process messages with quality of service EO (Exactly Once) in packages, you must specify a package size. This specifies the number of messages above which a package is to be scheduled for processing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once the specified package size is reached, a package can be processed immediately. If you want to do this, specify this in the corresponding field.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message packages can only be sent to a unique receiver. This must be either an IDoc receiver or an IDoc system as a receiver of ALE audits that are returned as acknowledgments by an IDoc receiver.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Due to performance reasons, you can only process small messages in packages. Therefore, you must also specify a corresponding message size.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Renjith Michael.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 09:54:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224160#M768974</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T09:54:48Z</dc:date>
    </item>
    <item>
      <title>Re: Package size in Select query..</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224161#M768975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dhanush,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What's the purpose of using PACKAGE SIZE in select statement?  &lt;/P&gt;&lt;P&gt;Package size can be used if you for example only want to finish processing a limited amount of data at a time due to lack of memory. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The example below  read 50 records at a time from VBAK into an internal table, and selects the corresponding entries from vbap into an internal table. Then the two internal tables can be processed, and the next 50 records from VBAk can be read. Remember to reinitialize tha tables before the next read.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT  z_test. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES: &lt;/P&gt;&lt;P&gt;  BEGIN OF t_vbak, &lt;/P&gt;&lt;P&gt;    vbeln LIKE vbak-vbeln, &lt;/P&gt;&lt;P&gt;    erdat LIKE vbak-erdat, &lt;/P&gt;&lt;P&gt;  END OF t_vbak, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  BEGIN OF t_vbap, &lt;/P&gt;&lt;P&gt;    posnr  LIKE vbap-posnr, &lt;/P&gt;&lt;P&gt;    matnr  LIKE vbap-matnr, &lt;/P&gt;&lt;P&gt;    meins  LIKE vbap-meins, &lt;/P&gt;&lt;P&gt;  END OF t_vbap, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  BEGIN OF t_report, &lt;/P&gt;&lt;P&gt;    vbeln LIKE vbak-vbeln, &lt;/P&gt;&lt;P&gt;    erdat LIKE vbak-erdat, &lt;/P&gt;&lt;P&gt;    posnr  LIKE vbap-posnr, &lt;/P&gt;&lt;P&gt;    matnr  LIKE vbap-matnr, &lt;/P&gt;&lt;P&gt;    meins  LIKE vbap-meins, &lt;/P&gt;&lt;P&gt;  END OF t_report. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: &lt;/P&gt;&lt;P&gt;  li_vbak   TYPE t_vbak OCCURS 0, &lt;/P&gt;&lt;P&gt;  l_vbak    TYPE  t_vbak, &lt;/P&gt;&lt;P&gt;  li_vbap   TYPE t_vbap OCCURS 0, &lt;/P&gt;&lt;P&gt;  l_vbap    TYPE t_vbap, &lt;/P&gt;&lt;P&gt;  li_report TYPE t_report OCCURS 0, &lt;/P&gt;&lt;P&gt;  l_report  TYPE t_report. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;START-OF-SELECTION. &lt;/P&gt;&lt;P&gt;  SELECT vbeln erdat &lt;/P&gt;&lt;P&gt;    FROM vbak &lt;/P&gt;&lt;P&gt;    INTO TABLE li_vbak PACKAGE SIZE 50. &lt;/P&gt;&lt;P&gt;    SELECT posnr matnr meins &lt;/P&gt;&lt;P&gt;      FROM vbap &lt;/P&gt;&lt;P&gt;      INTO TABLE li_vbap &lt;/P&gt;&lt;P&gt;      FOR ALL ENTRIES IN li_vbak &lt;/P&gt;&lt;P&gt;      WHERE vbeln = li_vbak-vbeln. &lt;/P&gt;&lt;P&gt;    IF sy-subrc = 0. &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  Now you have the two internal tables li_vbak and li_vbap filled &lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  with data. &lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  Do something with the data - remember to reinitialize internal &lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  tables &lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;    ENDIF. &lt;/P&gt;&lt;P&gt;  ENDSELECT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*-- End of Program &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This specifies a quantity of data records from the archiving object master table that is clearly defined by package limits. A package is an indivisible unit (in terms of the distribution between parallel jobs) used for the parallel processing of mass data, meaning that it is processed by precisely one job.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package limits: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These specify the quantity of data contained in a package. Package limits consist of one upper and one lower restrictive value for the package formation attributes. They are used as selection criteria for the data retrieval of the process phases that have run in parallel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package size:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This specifies the number of data records in a package.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package formation attributes:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;These specify one or more fields from the archiving object master table, used by the system to define package limits. Check which fields you select as package formation attributes in the Archiving Workbench step Create External Parallel Processing Key. For more information, refer to the documentation on this activity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package profile:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This specifies a quantity of package limits formed by the system during the pre-step process. The package profile is used to divide up the whole value range of package formation attributes. Package limits must never overlap.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Package formation strategy: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the algorithm used to form package profiles. The aim of this algorithm is to form a package profile in such a way that the parallel processing tool can form packages of an approximately equal size. The Archiving Workbench does not set the characteristic values of this algorithm; you or your customer must do this. The decision as to which algorithm is the most suitable depends on the conditions of the archiving object in question. The algorithm must be implemented by a function module registered by a corresponding Customizing entry for the archiving object in IMG activity Maintain Global Control of Archiving.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &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;&lt;/P&gt;&lt;P&gt;reward if useful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks and regards&lt;/P&gt;&lt;P&gt;suma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Jan 2008 09:59:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/package-size-in-select-query/m-p/3224161#M768975</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-10T09:59:17Z</dc:date>
    </item>
  </channel>
</rss>

