runtime exceeded error

[Former Member]

i have developed the report, i tested that report in development ,it gives output,

but i transported that report into production ,but i got the error msg

runtime exceeded.

Regards

raja

[Former Member]

Try to optimize the report or run it in the background.

Manoj

[Former Member]

Hi raja,

Your program is going to short dump due to lack of proper code optimization and performance issues.

You will have to tune your program so that it doesn't take so much time to execute, <b>there will be a limit set by the BASIS team for each program to execute</b>. Check you SELECT statemenets / loops to decrease the execution time.

In addition to do the runtime analysis , you can make use of following also:

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.

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.

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.

4. Avoid using nested select statements and nested loops as far as possible.

Hope these points help you analyze your program in a better way and give you a certain solution to optimize your code.

Updation of the timeout limit is task of BASIS.

In Tcode : RZ10, you can maintain systme parameters.

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.

Make sure about your system before changing that.

ALSO CHECK OUT WITH THESE LINKS

http://sap.ittoolbox.com/groups/technical-functional/SAP-R3-DEV/timeout-in-abap-debugger-560635

http://sap.ittoolbox.com/groups/technical-functional/SAP-R3-DEV/timeout-in-abap-debugger-560756

REgards,

pankaj singh

<b>*** reward if helpful</b>

[Former Member]

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.

Rob

[Former Member]

Hi Raja

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)

use The runtime analysis (SE30),The performance database.

Thanks and Regards

Ramamurthy