Fusion Global HR: Document Of Records Approval Routing Is Incorrect When Requestor Has Multiple Roles
(Doc ID 2898280.1)
Last updated on MAY 18, 2023
Applies to:
Oracle Fusion Global Human Resources Cloud Service - Version 11.13.22.04.0 and laterInformation in this document applies to any platform.
Symptoms
On : 11.13.22.04.0 version, Global Human Resources
ACTUAL BEHAVIOR
-----------------------
Approval rule conditions depending on the requestor's role for Document of Records is not working when a requestor has both roles
Approval rule is configured as follows:
1. if Line Manager initiates the transaction > then route to HR Specialist for approval
2. if HR Specialist initiates the transaction > then should be auto-approved
3. if the initiator has both roles > then the transaction should be auto-approved > but instead it follows both above rule conditions, for Line Manager and for HR Specialist
EXPECTED BEHAVIOR
-----------------------
Approval should work as per the setup
STEPS
-----------------------
1. when user with Line Manager role initiates the transaction > it routes to HR Specialist for approval
2. when user with HR Specialist role initiates the transaction > it is auto-approved
3. when user with both roles initiates the transaction > it follows both above rule conditions, for Line Manager and for HR Specialist, instead of just being auto-approved
Changes
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 |
Changes |
Cause |
Solution |
References |