R12 Deleting Unposted Reversal Journal In Primary Ledger Deletes Posted Reversal Journal In Secondary Ledger
(Doc ID 1500805.1)
Last updated on APRIL 28, 2023
Applies to:
Oracle General Ledger - Version 12.1.3 and laterInformation in this document applies to any platform.
Executable:GLPPOS - Posting
Executable:GLPARV - Auto Reversal Program
Form:GLXJEENT.FMB - Enter Journals/Encumbrances
Symptoms
Create a manual journal entry in the Primary Ledger and post.
Posting the journal in the Primary Ledger automatically creates and posts the journal in the Secondary Ledger as per standard functionality.
Then reverse the original journal in the Primary Ledger (using the "Reverse botton" in the journal entry screen).
When reversing the Journal in the Primary Ledger, it automatically creates an "unposted" Reversal journal for both Primary and Secondary Ledgers as per standard functionality.
Run the Autopost program in the Secondary Ledger only. The reversal journal is still unposted in the Primary Ledger but posted in the Secondary Ledger only as Autopost was run only in the Secondary Ledger.
Delete the reversal journal in the Primary ledger, which is still in an unposted status, via the Journal /enter form.
Observe this deletes both the Primary Ledger reversal journal and also the Secondary Ledger reversal journal which is posted (NOT CORRECT) which causes a balance mismatch between journal and balances and most probably data corruption in balances for 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! |