You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Please confirm if there is a 2nd Oracle Bug relating to the issue with GL Journal Action Log

in General Ledger & Intercompany 10 comments

Please confirm if there is a 2nd Oracle Bug relating to the issue with GL Journal Action Log.

We have become aware of bugs in Oracle Fusion Cloud ERP, which relate to the GL Journal Entry Action Log. At the application front end, the Action Log displays the history of actions on each journal batch, such as journal entry creation, update, approval, rejection, and posting. These actions are stored in the standard Oracle table GL_JE_ACTION_LOG.

Impact of the Bugs: The Oracle 24C quarterly release from July 2024 introduced bugs causing the Journal Entry Action Log and table GL_JE_ACTION_LOG to not capture certain journal approval information. Specifically, when a journal entry was approved through the journal approval workflow, the records associated with the action “Approved” may be omitted from the Action Log and the standard Oracle table. ‘HALO for Journals’ uses this table GL_JE_ACTION_LOG to determine journal entry approver(s) and approval date(s), and impacted journals may have empty values in fields “Approver ID” and “Approval Date” within ‘HALO for Journals’.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!