<?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: ALV Report performance &amp; export problem in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-report-performance-export-problem/m-p/2013029#M411069</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mallik,&lt;/P&gt;&lt;P&gt;     Already i faced this problem before. At that time i follow some precuations:&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; 1) Check the estimation cost for that report with the basis people.&lt;/P&gt;&lt;P&gt; 2) The selection fields mentionedin the select statement and fields order in the internal; table should match with order of Data base fields order.&lt;/P&gt;&lt;P&gt; 3) Define type statements and then refer internal table to that types.&lt;/P&gt;&lt;P&gt; 4) Define secondary indexes in the where condition properly.&lt;/P&gt;&lt;P&gt; 5) Add BINARY SEARCH to read table statement.&lt;/P&gt;&lt;P&gt; 6) if possible attach package size n to the select statement.&lt;/P&gt;&lt;P&gt; 7) Avoid nested loops and nested selects.&lt;/P&gt;&lt;P&gt; &lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt; After populating the final internal table free all the internal tables.&lt;/P&gt;&lt;P&gt; 9) check how much time taking for each select statemnt through SY05.&lt;/P&gt;&lt;P&gt;Hope this helps you. reply for queries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kumar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Mar 2007 09:52:17 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-03-16T09:52:17Z</dc:date>
    <item>
      <title>ALV Report performance &amp; export problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-report-performance-export-problem/m-p/2013026#M411066</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;We have developed an complex ALV report which accesses the data from FI Tables like BKPF, BSEG, BSAK etc.,   There are almost 100 lac records in BSEG and every day around 20000 records are getting added to that.  Eventhough I have used specific search criteria, system is taking lot of time.  Due to this I forced to run the report in background.  In background also it is taking around 4 - 6 hours.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) How can I improve the performance of the report.  Especially to access data from huge database table like BSEG with lot of conditions.  Any best practices&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) I want to have an option (at selection screen) to get the report directly saved in a Excel file at desired path.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Mallik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Mar 2007 07:23:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-report-performance-export-problem/m-p/2013026#M411066</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-16T07:23:27Z</dc:date>
    </item>
    <item>
      <title>Re: ALV Report performance &amp; export problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-report-performance-export-problem/m-p/2013027#M411067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi Mallik,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Refer these for performance tuning &lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm" target="test_blank"&gt;http://www.sap-img.com/abap/performance-tuning-for-data-selection-statement.htm&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Santosh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Mar 2007 08:06:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-report-performance-export-problem/m-p/2013027#M411067</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-16T08:06:57Z</dc:date>
    </item>
    <item>
      <title>Re: ALV Report performance &amp; export problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-report-performance-export-problem/m-p/2013028#M411068</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;refer to this link related to performance of FI tables:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/rob.burbank/blog/2006/02/07/performance-of-nested-loops&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;**reward if helpful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;madhumitha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Mar 2007 09:10:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-report-performance-export-problem/m-p/2013028#M411068</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-16T09:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: ALV Report performance &amp; export problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/alv-report-performance-export-problem/m-p/2013029#M411069</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mallik,&lt;/P&gt;&lt;P&gt;     Already i faced this problem before. At that time i follow some precuations:&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt; 1) Check the estimation cost for that report with the basis people.&lt;/P&gt;&lt;P&gt; 2) The selection fields mentionedin the select statement and fields order in the internal; table should match with order of Data base fields order.&lt;/P&gt;&lt;P&gt; 3) Define type statements and then refer internal table to that types.&lt;/P&gt;&lt;P&gt; 4) Define secondary indexes in the where condition properly.&lt;/P&gt;&lt;P&gt; 5) Add BINARY SEARCH to read table statement.&lt;/P&gt;&lt;P&gt; 6) if possible attach package size n to the select statement.&lt;/P&gt;&lt;P&gt; 7) Avoid nested loops and nested selects.&lt;/P&gt;&lt;P&gt; &lt;span class="lia-unicode-emoji" title=":smiling_face_with_sunglasses:"&gt;😎&lt;/span&gt; After populating the final internal table free all the internal tables.&lt;/P&gt;&lt;P&gt; 9) check how much time taking for each select statemnt through SY05.&lt;/P&gt;&lt;P&gt;Hope this helps you. reply for queries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Kumar.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Mar 2007 09:52:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/alv-report-performance-export-problem/m-p/2013029#M411069</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-16T09:52:17Z</dc:date>
    </item>
  </channel>
</rss>

