<?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: Frusterating report time out problems... in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/frusterating-report-time-out-problems/m-p/1845202#M358689</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yea...there is a default set for planning scenario. The problem is there might be 30,000+ materials associated with a stock segment...and I have to iterate over the API to collect the data for each material. The API is incredibly slow. Other developers must have similar problems with this API...how do you overcome this issue? Can I display just part of the data while waiting for the API to finish running against all of materials? How about a view? Can I build a view using the API that will be populated with data and stored in the db...just waiting for me to filter and display? How do you guys deal with these performance issues? Waiting ten minutes for a report to display data because the API takes all that time to process a few thousand records is crazy? Come on...what's the secret?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 31 Jan 2007 19:51:20 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-01-31T19:51:20Z</dc:date>
    <item>
      <title>Frusterating report time out problems...</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/frusterating-report-time-out-problems/m-p/1845200#M358687</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I have designed a supply/demand report using the MD_MRP_LIST_API. I filter the record set by user select options date, MRP controller, stock segment, responsible person...etc. and display the result in a ALV grid. Problem is the report times out if not run in batch. Other programmers are resolving this issue by creating a set of variants to use as input to execute this job in batch once every hour...outputting the result to a series of flat files. I can then create a set of shells of the original program...applying a subset of the user select options to the various flat files...and then displaying the result. That all seems so hokey tho? I feel like I'm doing something wrong...I come from a JAVA background and I don't understand why this is so difficult. First of all...the API takes for ever to collect the data!! What's with that? Can't SAP provide an API that is more efficient? Second...can I create a view of the data using the API that is already stored in the DB, just waiting for me to grab it, manipulate and display? Third...can't I page? You know...display a subset of the data set while the rest of the program is working to collect more data. Straighten me out here guys...I want to learn how to do this right!!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 17:18:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/frusterating-report-time-out-problems/m-p/1845200#M358687</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-31T17:18:01Z</dc:date>
    </item>
    <item>
      <title>Re: Frusterating report time out problems...</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/frusterating-report-time-out-problems/m-p/1845201#M358688</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Do you pass the planning senarion (PLSCN)?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 17:28:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/frusterating-report-time-out-problems/m-p/1845201#M358688</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-31T17:28:08Z</dc:date>
    </item>
    <item>
      <title>Re: Frusterating report time out problems...</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/frusterating-report-time-out-problems/m-p/1845202#M358689</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yea...there is a default set for planning scenario. The problem is there might be 30,000+ materials associated with a stock segment...and I have to iterate over the API to collect the data for each material. The API is incredibly slow. Other developers must have similar problems with this API...how do you overcome this issue? Can I display just part of the data while waiting for the API to finish running against all of materials? How about a view? Can I build a view using the API that will be populated with data and stored in the db...just waiting for me to filter and display? How do you guys deal with these performance issues? Waiting ten minutes for a report to display data because the API takes all that time to process a few thousand records is crazy? Come on...what's the secret?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mat&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Jan 2007 19:51:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/frusterating-report-time-out-problems/m-p/1845202#M358689</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-31T19:51:20Z</dc:date>
    </item>
  </channel>
</rss>

