Skip to Content
Former Member
Nov 23, 2012 at 05:51 AM

Multilevel leave workflow displaying inconsistent behaviour


As per business requirement , a modification was done in the leave workflow to handle multi level approval cases .

Steps know as

SET_STATUS Static Method Public Set the Leave Status in table 'PTREQ_HEADER'

SET_PROCESSOR Static Method Public Sets the Processor Status

CORRECT_NOTICE Static Method Public Correct the Notice Table 'PTREQ_NOTICE'

were added as activity steps in the leave workflow .

This helps change the status of request to SENT from APPROVED in the PTREQ_HEADER table

By default the entries in the header table are as :



These entries are changed and made as




in case the first level is not the final level of approval for the leave.

However after an upgrade to ECC6.0 it has been observed that the system behaves in an inconsistent manner (working fine for some cases ) .

It does not clone the entries as above keeping them in approved state, for a longer period of time , this in turns leads to the leaves getting posted by the PTREQPOST without the final approver.

The time it takes for the status change to reflect is variable , and sometimes too long.

What could be a reason for the inconsistent behavior is not evident ?