Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

TIME_OUT error in back ground

0 Kudos

Hi All,

I have scheduled a program in background.But i am getting short dump as TIME_OUT.

I am getting the following dump.

********************************************************************

Runtime Errors TIME_OUT

Occurred on 04.12.2008 at 06:11:26

Time limit exceeded.

What happened?

The program "SAPLZ_PTI_FILE" has exceeded the maximum permitted runtime without

interruption, and has therefore been terminated.

002430 WHEN 'WA_INSTALL-ANLAGE'.

002440 DATA: c_anlage(10) TYPE n.

002450 c_anlage = lw_sdata-symvalue.

> SELECT SINGLE aklasse FROM eanlh INTO p_aklasse ---->dump occurs here

002470 WHERE anlage = c_anlage

002480 AND bis = '99991231'.

002490

002500 *- Sluitveld geeft einde van te verwerken IDOC-data

002510 WHEN 'GV_EINDVELD'.

*************************************************************************

This code is executing inside a loop.

Anybody has the solution for this?

Please help me, in solving this problem.

Thnaks

Taj

1 ACCEPTED SOLUTION

Former Member
0 Kudos

you need to SELECT aklasse FROM eanlh INTO internal_table for all entries(where you are currently looping.

then in loop insted of select single wite Read internal_table with key

3 REPLIES 3

Former Member
0 Kudos

you need to SELECT aklasse FROM eanlh INTO internal_table for all entries(where you are currently looping.

then in loop insted of select single wite Read internal_table with key

Former Member
0 Kudos

first of all using a select statement in the loop is not avisable.

use a read statement instead of loop.

thanks,

poonam.

Former Member
0 Kudos

Your Select statement has got nothing to do with the dump.

It is a TIME OUT dump which simply means that maximum allotted time was exceeded. Try to do some performance tuning on your report. Just walk through the report in debug mode to just check if it falling in some infinite loop. Or you could try to limit the amount of data being processed through your selection parameters.

If nothing above works. Request your basis to somehow increase the time limit further.

These are the only ways. Most importantly Do Performance Tuning. All The Best !

Try transaction se30. It will help.