<?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: Packets in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/packets/m-p/959441#M67040</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nitin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally, the application server's memory can be considered to be virtually unlimited. However, it is the memory for the work process that will be limited. Even so, in most cases it would be capable of holding very huge volumes of data without any problem. It can even acquire additional space from the SAP Extended Memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The memory for a work process and the size of the Extended Memory can be configured using some profile parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you getting any errors / short dumps because of the volume of the data? Is there a scope to improvise the logic of the program ? For example, not all of these million records may be needed. The SELECT statements can be written with more restrictive where-clause etc.,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Further troubleshooting can be given if the exact nature of your problem is known.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Anand Mandalika.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 Jul 2005 16:15:22 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-07-11T16:15:22Z</dc:date>
    <item>
      <title>Packets</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/packets/m-p/959438#M67037</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 I am supposed to get say 1 Million records and if application server's memory is not sufficient how can u get the records into chunk of packets ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 10 Jul 2005 08:04:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/packets/m-p/959438#M67037</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-07-10T08:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: Packets</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/packets/m-p/959439#M67038</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You may use the following example.&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;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 10 Jul 2005 08:12:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/packets/m-p/959439#M67038</guid>
      <dc:creator>Vinod_Chandran</dc:creator>
      <dc:date>2005-07-10T08:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: Packets</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/packets/m-p/959440#M67039</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 you getting records using a select statement, then use the Cursor, Fetch statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kshitij&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jul 2005 15:27:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/packets/m-p/959440#M67039</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-07-11T15:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Packets</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/packets/m-p/959441#M67040</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nitin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Generally, the application server's memory can be considered to be virtually unlimited. However, it is the memory for the work process that will be limited. Even so, in most cases it would be capable of holding very huge volumes of data without any problem. It can even acquire additional space from the SAP Extended Memory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The memory for a work process and the size of the Extended Memory can be configured using some profile parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you getting any errors / short dumps because of the volume of the data? Is there a scope to improvise the logic of the program ? For example, not all of these million records may be needed. The SELECT statements can be written with more restrictive where-clause etc.,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Further troubleshooting can be given if the exact nature of your problem is known.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Anand Mandalika.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Jul 2005 16:15:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/packets/m-p/959441#M67040</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-07-11T16:15:22Z</dc:date>
    </item>
  </channel>
</rss>

