XLABABUP Sublegder Accounting Balances Update Never Finish Subledger Accounting Balances Update If There Are Journal Entries in Future Enterable Periods
Last updated on AUGUST 05, 2016
Applies to:Oracle Receivables - Version 12.0.0 to 12.0.7 [Release 12.0]
Information in this document applies to any platform.
If there are some transactions in a future enterable period, and the total number of transactions to be accounted is greater than the BATCH_COMMIT_SIZE, then all the transactions which are in the Open, Closed and Pending periods are processed.
The transactions in future enterable periods are not processed as a result of the balance_flag (analytical_balance_flag/control_balance_flag) for these transactions remain in 'P'.
The current code logic shows the total load is split up into chucks of size defined by BATCH_COMMIT_SIZE. In every commit cycle, the transactions are selected and processed. This is repeated until there is no transaction to be processed.
Now consider a case where there are few transactions in future enterable periods. In that case, these transactions will be selected but balances will not be calculated.
In the next Commit cycle, the same transactions will be picked up but not processed.
This will repeat infinitely.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms