Last updated on FEBRUARY 03, 2017
Applies to:Oracle Fusion General Ledger Cloud Service - Version 18.104.22.168.0 and later
Oracle Fusion General Ledger - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Journal approval is enabled and when the users try to delegate or reassign the task to a different user then the functionality works in the same way.
The expectation is that when the task is re-assigned to a new user the final approver name should be that of the new user.
When the journal is delegated the final approver name stamp of the journal should still be the original user to whom the task was assigned.
The result observed is that regardless of using reassignment or delegation the final approver is the new user:
Original Approver FINUSER1 -> Reassign to FINUSER2 -> FINUSER2 approves -> Final approval will be FINUSER2
Original Approver FINUSER1 -> Delegate to FINUSER2 -> FINUSER2 approves -> Final approval will be FINUSER2
What is the difference between reassignment and delegation of journal approval notifications?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms