Premature Escalation Of Task (Doc ID 2154459.1)

Last updated on DECEMBER 10, 2016

Applies to:

Oracle Fusion Global Human Resources Cloud Service - Version 11.1.10.0.0 and later
Information in this document applies to any platform.

Goal

Issue with Premature Escalation of Task

1) Transaction was first assigned to A. B. on March 8 at 5:40 p.m.
2) and it escalated to R. W. after 4 days, March 12. R. approved the transaction 2 days later on March 14 at 1:24 p.m.
3) After R. approved the transaction, the approval routed to V. W. on March 14.
4) V.'s approval was escalated 2 days later on March 16 but should not have escalated until March 18 (4 days from assignment to V.).

Client's escalations are set to 4 days with 2 maximum escalations. The first escalation occurred after 4 days. The approver to whom the approval was first escalated, R., would have had until March 16 before the transaction escalated again. She approved in 2 days and that approval was routed (not escalated) to V.

The expectation is that the expiration date-time would reset upon each movement from one person to the next. Approver #4 (V.) should have had 4 days to approve
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms