GLPPOS: When Posting a Reversal Journal in Primary Ledger it is Automatically Posted in Reporting (ALC) Ledger But in Secondary Ledger it is Not Automatically Posted
(Doc ID 1530980.1)
Last updated on AUGUST 01, 2023
Applies to:
Oracle General Ledger - Version 12.1.3 and laterInformation in this document applies to any platform.
Executable:GLPREV - Reverse Journals
Executable:GLPPOS - Posting
Symptoms
When a reversed journal is posted in the Primary Ledger it gets posted in the Reporting Ledger (ALC), but the reversal journals are not posted automatically in the Secondary ledgers.
When journal approval is enabled and a reversal journal in primary ledger is created, approved and posted, the reversing journal in secondary ledger is also created but is not automatically approved and posted. This results in an unposted reversing journal in the secondary ledger that needs to be sent through workflow for approval. This requires the user to have to initial the journal workflow approval in both the ledgers for the same reversal journal. As the journal does not get posted there is also a risk that the reversing journal can be deleted from the secondary ledger.
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 |