Allocation Rule Performance - Global Temporary Table Created For Entire FISCAL_YEAR Instead of FISCAL_MONTH
(Doc ID 2689973.1)
Last updated on AUGUST 24, 2021
Applies to:Oracle Financial Services Profitability Management - Version 8.0.4 and later
Information in this document applies to any platform.
Oracle Financial Services Enterprise Performance Management (EPM)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
On PFT 8.0.5 while analyzing allocation rules that seem to be taking lot of time to complete, the number of records on which these rules run are in millions, one key observation is that when the allocation engine creates the global temporary table based on FSI_D_MANAGEMENT_LEDGER, it only filters based on FISCAL_YEAR and not on FISCAL_MONTH.
With the row based structure presented by Management Ledger table, there should be no reason whatsoever for the Global temporary table to be pulling all the records for a particular FE, through the entire year.
This can be summarized to particular scenario where there are 20+ million records for a FE per month. When running the allocation for a month(ie November) of any Fiscal Year, though the interest is for the 20 million records, the Global temp table is created for 11*20 i.e. 220 million records, which is not relevant for the current fiscal_month.
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