Skip to Content
avatar image
Former Member

ABAP Runtime error !!! Timeout error

Hi friends,

This time i have an error in the production . The result of the error is becoz of the following short dump that occurs when a report is run . I would appreciate if you can give me some advice on how to overcome this issue . Sometime the report runs fine and fetches all the data from the table but sometimes it takes forever and results in a short dump.

Error analysis


After a certain length of time, the program is terminated. In the case of a work area, this means that

- endless loops(DO,WHILE, ...),

- database accesses producing an excessively large result set,

- database accesses without a suitable index (full table scan)

do not block the processing for too long.

The system profile "rdisp/max_wprun_time" contains the maximum runtime of a

program. The current setting is 600 seconds. Once this time limit has been exceeded,

the system tries to terminate any SQL statements that are currently

being executed and tells the ABAP processor to terminate the current

program. Then it waits for a maximum of 60 seconds. If the program is

still active, the work process is restarted.

In my SQL query i have used SELECT SINGLE ....INTO TABLE ... .

Should i use SELECT * .....INTO TABLE ????

Please let me know .


Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

6 Answers

  • Best Answer
    avatar image
    Former Member
    Apr 25, 2006 at 04:45 AM

    Hi !

    If it is not possible to tune up your programm you can run it in background as a "batch" programm.

    In the background there is no runtime limitation !



    Some Reward Points would be fine if this helps a bit...

    Add comment
    10|10000 characters needed characters exceeded

    • Hari,

      To my knowledge,even a background job will have some limitations in terms of runtime.There is an ample chance that this long running job will impact other critical jobs in Production.So better do the performance optimisation rather than brushing it under the carpet in the name of "program scheduled as a background job".


  • avatar image
    Former Member
    Apr 25, 2006 at 01:53 AM

    Hi Hari,

    This is coz of long running program. Try to performance tune the program.

    Remove all select statements from within the loop and use read statement with binary search. Try using sorted table where ever possible that should bring down your run time.

    Never use select * , only select the fields you are really going to use. Array fetch is always a better option then selecting data in a loop.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Rob is Right these internal tables should not be empty, you can include these codes before proceeding to your SQL statement:

      IF i_rsnum[] IS NOT INITIAL

      AND i_matnr[] IS NOT INITIAL.

      select rsnum





      These will somehow keep the SQL statement from returning volumes of data similar to an open search

  • avatar image
    Former Member
    Apr 25, 2006 at 03:39 AM


    I dont think the error is because of use of "select single..". In fact its far better than using "Select * ..".

    You need to performance tune your program.

    Adding to Vijay's suggestions, you also need to emphasis on "select single.." rather than "select ..upto 1 rows".

    Avoid nested loops.

    Avoid unecesary multiple database hits.

    Avoid select within a loop.

    Avoid using " select ...into corresponding fields..".

    The error might be due to some database accesses without a suitable index. If there is lot of data in the database, it may result in time out dump.



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 25, 2006 at 03:40 AM

    Hi Hari ,

    Your program is going to short dump due to lack of proper code optimization and performance issues as others have also stated.

    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.

    Thanks and Regards,



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Apr 25, 2006 at 05:10 AM


    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.


    Thanks & Regards

    Sreenivasu P

    Message was edited by: Sreenivasulu Ponnadi

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 09, 2007 at 01:04 AM

    Hi normally sertan time limit will be set by the basis people to run the abap programs in foreground

    I think in your case as mentioned below you fellow all the performense issues with select stmts and use secondary indexes

    and use the commit work immediateely after the database update explicitly in the program so that the run times will reset

    use the commit work in several places then let me it shoud work fine .


    srinu reddy.

    Add comment
    10|10000 characters needed characters exceeded