Aggregate to Ledger Does Not Aggregate Cost Correctly For Transactions Missing Parent Instrument Table Record
(Doc ID 2765840.1)
Last updated on APRIL 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)
Oracle Financial Services Enterprise Performance Management (EPM)
On PFT 188.8.131.52.0, there appears to be an issue with the Aggregate to Ledger option in the Output. When using a Dynamic Driver allocation, the aggregate cost is specifically allocated at Target Instrument Table even when matching records do not exist.
PFT rule is built on following requirement:
Source = Management Ledger
Driver = Transaction Summary Table
Output (Debit) = Instrument Table with Aggregate to Ledger
There is a scenario where some Customer ID_NUMBER are present in Transaction Summary Table, however are not present in the Instrument Table (Lets say 5% records are missing in IT). Therefore, a part of cost has not been written to the Instrument Table - as few records do not exist here (same 5%).
However, when 'Aggregate to Ledger' option is selected in Output tab - The rule is aggregating 100% of the Cost, instead of aggregating the amount written to the Instrument Table (i.e., 95%) - which is chosen in the Output Debit Tab.
It is expected that the missing records / amounts which are not matched in the Transaction Summary Table are not aggregated.
The issue can be reproduced at will with the following steps:
1. Create a Dynamic Driver allocation on Management Ledger
2. Driver is Transaction Summary Table
3. Distribution Type is Percent Distribution
4. Debit instrument table and select Aggregate to Ledger "Yes" and Credit is none
5. Run the allocation and check results.
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