<?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: OOP ALV report custom control performance problem in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/oop-alv-report-custom-control-performance-problem/m-p/4929493#M1150048</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;timeout is not an alv problem. If you try to display a "huge" amount of data, any display technology will fail. Even sap programs fail, their wise solution is to ask user to restrict data to be displayed. Or reduce database selection time, or display amount. Or propose the user to download data as a spool, or output to a file on server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise, read some advices about how to handle timeout in [Note 25528 - Parameter rdisp/max_wprun_time|http://service.sap.com/sap/support/notes/25528].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About your question, if you still want to try, look at [example code with alv class cl_salv_table for simple display|http://help.sap.com/saphelp_nw2004s/helpdata/en/f9/1ab54099de3726e10000000a1550b0/frameset.htm]&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 27 Dec 2008 13:30:36 GMT</pubDate>
    <dc:creator>Sandra_Rossi</dc:creator>
    <dc:date>2008-12-27T13:30:36Z</dc:date>
    <item>
      <title>OOP ALV report custom control performance problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oop-alv-report-custom-control-performance-problem/m-p/4929492#M1150047</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;how to write OOP ALV report without custom control.. Actually with custom control which taking long time... and time out happens for huge selection of data..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Roops.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Dec 2008 07:35:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oop-alv-report-custom-control-performance-problem/m-p/4929492#M1150047</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-27T07:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: OOP ALV report custom control performance problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/oop-alv-report-custom-control-performance-problem/m-p/4929493#M1150048</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;timeout is not an alv problem. If you try to display a "huge" amount of data, any display technology will fail. Even sap programs fail, their wise solution is to ask user to restrict data to be displayed. Or reduce database selection time, or display amount. Or propose the user to download data as a spool, or output to a file on server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise, read some advices about how to handle timeout in [Note 25528 - Parameter rdisp/max_wprun_time|http://service.sap.com/sap/support/notes/25528].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About your question, if you still want to try, look at [example code with alv class cl_salv_table for simple display|http://help.sap.com/saphelp_nw2004s/helpdata/en/f9/1ab54099de3726e10000000a1550b0/frameset.htm]&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Dec 2008 13:30:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/oop-alv-report-custom-control-performance-problem/m-p/4929493#M1150048</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2008-12-27T13:30:36Z</dc:date>
    </item>
  </channel>
</rss>

