GLXJEENT: Why Does the Journal Batch Show Original Approver Instead of Actual Approver Designated by Vacation Rule?
(Doc ID 2343521.1)
Last updated on OCTOBER 13, 2022
Applies to:Oracle General Ledger - Version 12.2 and later
Information in this document applies to any platform.
Employee A has supervisor B.
Employee A enters a manual journal and sends it for approval to supervisor B.
However, supervisor B is unavailable and has defined a vacation rule with the option of 'Transfer Notification Ownership' to director C.
Director C approves the journal.
When reviewing the journal, field approver_employee_id in gl_je_batches reflects supervisor B (the originally selected approver) not director C (who actually approved the journal).
Based on the scenario above, the following questions are addressed:
1. Why is supervisor B stored in the batch as the person who approved the journal?
A vacation rule with option 'Transfer Notification Ownership' to director C was created and director C actually approved the journal.
It is expected director C would be stored in the batch as the approver.
2. Is there any method to determine who actually approved the journal when using a vacation rule?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!