Journal Approval Workflow Delegation Unexpected Behavior
(Doc ID 422264.1)
Last updated on OCTOBER 10, 2022
Applies to:
Oracle General Ledger - Version 11.5.9 to 12.0.4 [Release 11.5.9 to 12.0]Information in this document applies to any platform.
FORM:GLXJEENT.FMB - Enter Journals/Encumbrances
Symptoms
The issue is related to Delegation functionality in Journal Approval.
The person to whom the approval is delegated, does not have the required Authorizing Limits to approve a Journal.
The standard documented behavior is that the Authorizing limits of the Supervisor are carried forward to the delegated user, even if it is not a supervisor, however this is not happening.
Steps to Reproduce
- User C creates a journal and sends it for approval
- Manager M receives the notification. He has enough Authorization Limits to approve the journal, but he delegates the approval to another person P using the Delegate responsibility option. P does not have enough Authorization Limits and may not be a manager.
- P receives the notification and tries to approve the journal. But the journal does not get approved by P because the Authorization limit is less. However since this was Delegation, Authorization limits of M should have been considered.
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 |
| Still Have Questions? |
| References |