Skip to Content
avatar image
Former Member

Getting Run-time error "TIME_OUT" occurred

Hello Everybody,

In my Solution manager Development system every day when I check ABAP Runtime errors using ST22 transaction code I am getting a runtime error of TIME_OUT.I has also searched the SAP notes but I am not getting a proper solution to my issue of TIME_OUT.Please suggest solutions to overcome of my above mentioned issue.Below is the log for runtime error"TIME_OUT" :

Short text

Time limit exceeded.

What happened?

The program "/BDL/SAPLBDL4" has exceeded the maximum permitted runtime without

interruption and has therefore been terminated.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system


Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

After a specific time, the program is terminated to make the work area

available to other users who may be waiting.

This is to prevent a work area being blocked unnecessarily long by, for


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

- Database accesses with a large result set

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

The maximum runtime of a program is limited by the system profile

parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this

time limit is

exceeded, the system attempts to cancel any running SQL statement or

signals the ABAP processor to stop the running program. Then the system

waits another 60 seconds maximum. If the program is then still active,

the work process is restarted.

to correct the error

Programs with long runtime should generally be started as background

jobs. If this is not possible, you can increase the system profile

parameter "rdisp/max_wprun_time".

Depending on the cause of the error, you may have to take one of the

following measures:

- Endless loop: Correct program;

- Dataset resulting from database access is too large:

Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table

(for example);

- Database has unsuitable index: Check index generation.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following


"TIME_OUT" " "



If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File


2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File


3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More


4. Details about the conditions under which the error occurred or which

actions and input led to the error.

System environment

SAP-Release 700

Application server... "sapsm4dev"

Network address...... ""

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "2x Intel 80686"

Character length.... 8 Bits

Pointer length....... 32 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "SAPSM4DEV"

Database type..... "ORACLE"

Database name..... "SMD"

Database user ID.. "SAPSR3"

Char.set.... "English_United State"

SAP kernel....... 700

created (date)... "Oct 23 2007 00:57:10"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "OCI_10201_SHARE ( "

Patch level. 133

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 8112

EM...... 2090592

Heap.... 0

Page.... 16384

MM Used. 1516976

MM Free. 572168

Thanks and Regards,

Ashish Thakkar.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jun 17, 2008 at 02:56 PM


    Maximum work process runtime exceeded, due to which this runtime error occurs.

    Check for all the background jobs which got cancelled during the period of dump.

    You will get the clue of error.


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      Check the SM21 entries at the time when runtime error occurs. Try figure out what activity starts or ends at that time. You might get some useful information from log entries.


  • avatar image
    Former Member
    Jun 16, 2015 at 04:51 AM

    In SAP, there is a parameter rdisp/max_wprun_time which limits the maximum permitted runtime without interruption. By default this value is set to 600 seconds. However, if you are frequently encountering more dumps in SAP system due to this, you can consider increasing this value to 3600 seconds to avoid this issue.

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 05, 2016 at 05:38 AM

    Hi Everyone, Although it's an old thread but I would like to share the info which helped us. We have increased the size of the parameter abap/shared_objects_size_MB from by default_vale 250 to 400 MB. Thanks and Regards Anurag Das

    Add comment
    10|10000 characters needed characters exceeded