PFT Allocation Undo Performance Questions
(Doc ID 2463425.1)
Last updated on FEBRUARY 05, 2021
Applies to:Oracle Financial Services Profitability Management - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)
Extensively using PFT for Cost Allocation. There are typically over 250 million records monthly in Management Ledger (ML), given the number of key dimensions on ML table.
Question 1: When running Undo for the allocations on the table, it seems to plainly fire deletes for the Undo which seem to be problematic for performance reasons:
A. Takes ages to complete and is not scalable
B. Uses tons of UNDO segment space and is not efficient
Is there anything which can be done to avoid the above issue for the large scale record Undo allocations?
Question 2: Does PFT offer any options to make the delete more efficient, by passing hints setting degree of parallelism (DOP) etc?
Question 3: Is there an alternative to the plain Delete, i.e. a truncate partition/sub partition?
Question 4: Does OFSAA recommend any out of the box partitioning strategy for ML tables like AS_OF_DATE/Financial Element composite partitioning to allow users to have more control over the Undo operation?
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