How to deactivate timeout (rdisp/max_wprun_time) for special transaction ?

[Former Member]

Hi,

We are using transactions S_ALR_xxxx for closing period and some times during the month. In 46C, these transactions wasn't kill by the timeout (rdisp/max_wprun_time). We have upgraded to ECC6 and with exactly the same procedure these transaction are killed after 600s (the value of our timeout). These transactions are interactives so we can't use the backgroung mode. In 46C, these transactions taked 2 000s but we don't want to set a very high value for the timeout.

Is there a way to disabled the timeout for a special transaction in sending by RFC the execution on a BTC workprocess or in .... ?

Thanks

Thierry

[Former Member]

Hi Thierry,

The parameter is applicable to all the work process and is an instance level parameter, so it cannot affect a specific transaction.

The best way to work around your issue is to run the job as background job where there is no time out limitation.

Hope this helps.

Thank you,

Kind regards,

Zaheer Shaikh

[Former Member]

Thierry,

1. You cannot exclude few transactions because max_wprun_time will be applicable to all the transactions.

2. This will be applicable to only dialog work processes and you can run reports in background without having effect of above parameter.

Hope this helps.

Manoj

[JPReyes]

rdisp/max_wprun_time is a dynamic parameter meaning you can change the value without restarting the system... you can change the paremeter via RZ11 and set it back when the job is finished.

Regards

Juan

[Former Member]

Thierry,

How was it set up in 46C? Can it not be done the same?

If not, maybe this will help:

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a4dcf62d-0a01-0010-afa5-e8edcecb...