Performance Issues When Using Standard API's To Rebuild Gl_sl_link_id After Upgrade
(Doc ID 2453099.1)
Last updated on OCTOBER 01, 2018
Applies to:Oracle Cost Management - Version 12.2.5 and later
Information in this document applies to any platform.
In 11i MTA/WTA can be posted in summary to GL.
If the customer is posting the Sub-Ledger data to GL in summary mode, the gl_sl_link_id is populated as NULL in GL_IMPORT_REFERENCES & MTL_TRANSACTION_ACCOUNTS / WIP_TRANSACTION_ACCOUNTS.
When this summary data is upgraded to R12, the XLA data is also created with gl_sl_link_id as NULL, because of which the customer will not be able to drill down to MTA/WIP transactions.
Procedures cst_upd_gir_mta_wta.cst_sl_link_upg_mta, cst_upd_gir_mta_wta.cst_sl_link_upg_wta are used to rebuild the missing gl_sl_link _id column in GL_IMPORT_REFERENCES table for a particular GL_BATCH_ID.
Below solution aims to improve performance when using procedures cst_upd_gir_mta_wta.cst_sl_link_upg_mta and cst_upd_gir_mta_wta.cst_sl_link_upg_wta.
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