On Requisitions, First Responder Wins Is Not Working With Multiple Approver Groups
(Doc ID 1923403.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle Purchasing - Version 12.2.3 and laterInformation in this document applies to any platform.
Symptoms
Approval Management Engine (AME) First Responder wins is not working leaving the Requisition in IN PROCESS status. This occurs with multiple approver groups and approval group members and the issue is best described in an example:
Two static approver groups with 2 approvers each, for example:
AG1 (1.1, 1.2)
AG2 (2.1, 2.2)
The action type of the actions in the applicable rule is 'approval-group chain of authority'
Requirements are the following:
(1). The members of AG1 and AG2 must get the approval notifications in parallel, for example:
1.1, 1.2, 2.1 and 2.1 must all get it at the same time
(2). The voting regime within each approver group must be First Responder Wins, but only WITHIN the approver group, for example:
the transaction is only approved if approver 1.1 OR 1.2 in AG1 approves AND approver 2.1 OR approver 2.2 in AG2 approves.
AG1 (1.1, 1.2)
AG2 (2.1, 2.2)
The action type of the actions in the applicable rule is 'approval-group chain of authority'
Requirements are the following:
(1). The members of AG1 and AG2 must get the approval notifications in parallel, for example:
1.1, 1.2, 2.1 and 2.1 must all get it at the same time
(2). The voting regime within each approver group must be First Responder Wins, but only WITHIN the approver group, for example:
the transaction is only approved if approver 1.1 OR 1.2 in AG1 approves AND approver 2.1 OR approver 2.2 in AG2 approves.
The problem is once one approver approves, then the other approvers' notifications are cancelled with No Action Taken recorded, and the Requisition remains in IN PROCESS status
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |