Consolidation Journal Posted Twice Causing Balance Corruption
(Doc ID 1922615.1)
Last updated on AUGUST 13, 2021
Applies to:Oracle General Ledger - Version 12.0.0 and later
Information in this document applies to any platform.
Executable:GLCCON - Consolidation Transfer
Executable:GLPPOS - Posting
Balance corruption has been found in GL_BALANCES due to the double posting of a Consolidation source journal.
Specific circumstance (timing) of submissions that is allowing this to occur.
1. Submit a consolidation transfer with Run Journal Import and Autopost selected.
2. Have Autopost scheduled to run for this source.
3. After the import was run the Autopost was submitted for this source. It completed, but before Posting (GLPPOS) concurrent request started for Autopost the Posting request from the consolidation was submitted, resulting in two posting program requests running at the same time for the same batch.
4. Both posting program execute with success and update gl_balances table for impacted Code combinations, resulting in double posting amounts to the balance of these accounts.
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