SAP Basis Tech Supports

Symptom
A work process can exceed the maximum runtime (specified by the “rdisp/max_wprun_time” profile parameter) without being cancelled.
Other terms
COMMIT WORK, TH_REDISPATCH, maximum runtime, WP_HOLD
Reason and Prerequisites
The reason for this is that the maximum runtime of a work process is not only reset to the value of rdisp/max_wprun_time if a new user (or more generally: a new task) is dispatched into the work process, but also if the current user performs actions that are associated with communication with the message server.
This is the case with enqueue operations, for example.
Solution
As of the patch level mentioned below, there is a profile parameter for Releases 46D, 620 and 640 that you can use to change the behavior of the timer in these cases: If you set the “rdisp/hold_keeps_time_slice” profile parameter to the “TRUE” value, then, after communication with the message server, the timer is set to the value rdisp/max_wprun_timeminusthe time that the process consumed for this task up to now. This solves the problem in most cases.
However, since the explosion of the measurement of time is in the area of seconds, operations that occur between message server operations and require less than one second may lead to an extension of the overall runtime.
ParametersValuesDefaultrdisp/hold_keeps_time_sliceFALSE, TRUEFALSE

As of Basis Release 7.0, the behavior described above is standard behavior and can no longer be changed. The parameter exists in other releases with the following patch levels:
46D: 1848
620: 1502
640: 18