<?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: runtime exceeded error in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802938#M344680</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the development system, there is usually a lot less data and poorly optimized code tends to run there much more quickly than in a QA or production system. You can use transaction ST05 to find inefficient portions of your code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Dec 2006 17:14:43 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-12-29T17:14:43Z</dc:date>
    <item>
      <title>runtime exceeded error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802935#M344677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i have developed the report, i tested that report in development ,it gives output,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; but i transported that report into production ,but i got the error msg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;runtime exceeded.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;raja&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 05:22:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802935#M344677</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T05:22:40Z</dc:date>
    </item>
    <item>
      <title>Re: runtime exceeded error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802936#M344678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try to optimize the report or run it in the background.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Manoj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 05:23:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802936#M344678</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T05:23:38Z</dc:date>
    </item>
    <item>
      <title>Re: runtime exceeded error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802937#M344679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi raja,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your program is going to short dump due to lack of proper code optimization and performance issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will have to tune your program so that it doesn't take so much time to execute, &amp;lt;b&amp;gt;there will be a limit set by the BASIS team for each program to execute&amp;lt;/b&amp;gt;. Check you SELECT statemenets / loops to decrease the execution time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In addition to do the runtime analysis , you can make use of following also:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. You can make use of SAP Code Inspector ( transaction code : SCI) to check your program. It will give you an idea how to optimize your select queries and detailed analysis of other errors/ warnings whihc will help you to fine tune your program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. The runtime analysis is also a good option because it will tell you which table is highly being used and then accordingly you can optimize your code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Select single is always a better option than using select *. Moreover if you know which data actuallu to retreive , you should use obly those fields yto retreive.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Avoid using nested select statements and nested loops as far as possible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope these points help you analyze your program in a better way and give you a certain solution to optimize your code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Updation of the timeout limit is task of BASIS.&lt;/P&gt;&lt;P&gt;In Tcode : RZ10, you can maintain systme parameters.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The parameter name is rdisp/max_wprun_time. If it not maintained in the profile it will be default 10 mins(600 seconds) as SAP has recommended.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Make sure about your system before changing that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ALSO CHECK OUT WITH THESE LINKS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://sap.ittoolbox.com/groups/technical-functional/SAP-R3-DEV/timeout-in-abap-debugger-560635" target="test_blank"&gt;http://sap.ittoolbox.com/groups/technical-functional/SAP-R3-DEV/timeout-in-abap-debugger-560635&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://sap.ittoolbox.com/groups/technical-functional/SAP-R3-DEV/timeout-in-abap-debugger-560756" target="test_blank"&gt;http://sap.ittoolbox.com/groups/technical-functional/SAP-R3-DEV/timeout-in-abap-debugger-560756&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REgards,&lt;/P&gt;&lt;P&gt;pankaj singh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;*** reward if helpful&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 05:27:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802937#M344679</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T05:27:19Z</dc:date>
    </item>
    <item>
      <title>Re: runtime exceeded error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802938#M344680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In the development system, there is usually a lot less data and poorly optimized code tends to run there much more quickly than in a QA or production system. You can use transaction ST05 to find inefficient portions of your code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Dec 2006 17:14:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802938#M344680</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-12-29T17:14:43Z</dc:date>
    </item>
    <item>
      <title>Re: runtime exceeded error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802939#M344681</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Raja&lt;/P&gt;&lt;P&gt;As Rob Burbank  said In the development system, there is usually a lot less data and poorly optimized code. In addition to the SQL Trace (ST05)&lt;/P&gt;&lt;P&gt;use The runtime analysis (SE30),The performance database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;P&gt;Ramamurthy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jan 2007 13:07:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/runtime-exceeded-error/m-p/1802939#M344681</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-01-02T13:07:48Z</dc:date>
    </item>
  </channel>
</rss>

