Timed out running standard code

[Former Member]

Hi All,

We have a customized function module to process idoc to create materials.

Last week it was running fine for even 76000 segments, which processed in 90 minutes.

But when i tried to reprocess the same idoc in this week, it is timed out in 10 minutes. When i checked,

the control itself is not coming to my function module before which its executing a loop in standard code and

getting timed out there. Below is the code from standard program

Its inside the inlcude MSED7F03

* build data records
 LOOP AT t_nodes_in WHERE type <> c_node_type_h.
   CLEAR l_sdata.
* get data from background table
   PERFORM data_from_node_get
                           USING
                              t_nodes_in-hide
                              t_data_records_in-sdata.

   t_data_records_in-segnam = t_nodes_in-name.
   APPEND t_data_records_in.
 ENDLOOP.

I did a dump analysis and found out that the setting is done in the transaction RZ11, where we provide u201Crdisp/max_wprun_timeu201D as input parameter. Now the time limit is provided as 600 seconds.

But changing this is not a solution I feel as this is just temperory, once after the server is restarted the values will be set to the default.

Waiting for the valubale suggestions

[Former Member]

Hi,

I am not sure what changes you have made and how you are running the program.

it will be always good to run the programs in back ground which takes more than 3 mintues in dialog mode !

Suresh

[Former Member]

Hi,

I am re-processing an idoc in WE19 where I select the option run in background only.

I would like to know whether there is any other settings for running time of background jobs because when I checked a dump happened for program run in background for more than 10 hours, it says the settings is only for 600 seconds.

If it is only 600 seconds that time, then how the program ran for more than 10 hours then and not now.

Please help.

Edited by: vinraaj on Jul 2, 2010 6:06 AM

[Former Member]

run time limits apply to foreground execution only, if I remember correctly...that's why we use background for anything that is going to be lengthy.

[ThomasZloch]

Sounds like parallel processing is active when you process your IDocs, and dialog processes are being used in this case, so the runtime limit does apply. Maybe there is a few "big" IDocs that cause the runtime to exceed 10 minutes?

Since SAP standard code is involved, did you check for SAP notes?

Thomas

[Former Member]

closed