How to Prevent Possible General Ledger Balances Corruption Due to Incorrect Program Incompatibilities in Release 12
Last updated on APRIL 03, 2017
Applies to:Oracle General Ledger - Version 12.0 and later
Information in this document applies to any platform.
Note: for release 11i, please refer to <Document 300933.1> How to Prevent Possible General Ledger Balances Corruption Due to Incorrect Program Incompatibilities in 11.5.
The concurrent program definitions of Posting, Open Period, and Translation have been updated. Now the three programs can run in parallel for different ledgers. However, due to an AOL issue, the concurrent program incompatibility definitions may not have been updated correctly leading to balances corruption issues when the opening program runs simultaneously with the posting program.
If the concurrent program definitions were not updated correctly, then you might be allowed to post a journal while a period is being opened for the same ledger. In this case, the Open Period program isn't aware that the Posting program is running, so it doesn't consider the impact of the journals the Posting program is in the process of posting when calculating opening balances.
The same way, the Posting program is not aware that the Open Period program is running, so it does not roll the balances into the period that the Open Period program is in the process of opening. So the opening balance of the newly opened period is not equal to the closing balance of the period before it.
A test for the balances corruption is available in these Diagnostic scripts:
- For release 12.0 to 12.0.5: <Document 463519.1> R12.0 Oracle General Ledger Period Closing Setup Test
- For release 12.0.6 to 12.1: <Document 732156.1> R12.0.6+ Oracle General Ledger Period Closing Setup Test
They can show an error indicating that the opening balance of one period does not equal the closing balance of the previous period. Should data corruptions have occurred please log a service Request with Oracle Support to get a datafix to the GL balances. Make sure the solution on this note (patch) is applied before any datafix.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms