By Adriana-Oracle on Dec 29, 2015
Posting journal entries in General Ledger is the last step of the accounting cycle, transferring these entries in a final state to update GL balances and locking them for further updates. This is the main GL process that will afterwards support Reporting on the balances, Translation, Consolidation and other business specific processes. As Posting is very common activity in GL, it is very important that the concurrent requests run with reasonable performance.
Posting bad performance was reported after Database Upgrade to 126.96.36.199 or 188.8.131.52. A higher parse time than 11g may be seen in 12c for a complex query with a multi-table join with SQL plan directives enabled.
Database Patch 20807398 is now available to fix this for you!
Did you upgrade the Database to the mentioned versions recently?
Proactively review this document today, before the users get to report performance issues:
GLPPOS: After Database Upgrade to 184.108.40.206 or 220.127.116.11 Posting Has Poor Performance Due to SQL Plan Directives (Doc ID 2068068.1)