<?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: Batch Job Performance Issue. in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-performance-issue/m-p/5957595#M1337131</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;As you said you can split the records as packages. ( as teh issue is related to low memory of internal table ) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select ....package size...&lt;/P&gt;&lt;P&gt;*-- program logic&lt;/P&gt;&lt;P&gt;endslect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Naveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Aug 2009 08:57:42 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-08-19T08:57:42Z</dc:date>
    <item>
      <title>Batch Job Performance Issue.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-performance-issue/m-p/5957594#M1337130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am facing a performance issue in a background job, on a selection screen it contains month start date,  end date and also effective date as 01/01/2008. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Client executing this report once in every month. Since the effective date is constant, the database contains large volume of data i.e. more than 3 lakh records Presently. Finally the job gets cancelled. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please suggest what should be done in this scenario? Is there any concept like splitting the records as batches like multiples of 20 thousands.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards,&lt;/P&gt;&lt;P&gt;Stanly&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Aug 2009 08:50:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-performance-issue/m-p/5957594#M1337130</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-19T08:50:36Z</dc:date>
    </item>
    <item>
      <title>Re: Batch Job Performance Issue.</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-performance-issue/m-p/5957595#M1337131</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;As you said you can split the records as packages. ( as teh issue is related to low memory of internal table ) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select ....package size...&lt;/P&gt;&lt;P&gt;*-- program logic&lt;/P&gt;&lt;P&gt;endslect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Naveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Aug 2009 08:57:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/batch-job-performance-issue/m-p/5957595#M1337131</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-08-19T08:57:42Z</dc:date>
    </item>
  </channel>
</rss>

