Allocation Creating Invalid Credit Entries with Fewer Rows than Debit for Out of Balance Result

(Doc ID 2311392.1)

Last updated on OCTOBER 03, 2017

Applies to:

Oracle Financial Services Profitability Management - Version 8.0.4 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

In Oracle Financial Services Profitability Management (PFT) 8.0.4, when you run a Dynamic Driver, Percent Distribution Allocation that contains "<Same As Driver>" output definitions in both the Debit and Credit screens, you expect to get the same amount of records output for the Debit and Credit.  You expect the records to offset each other.  However, there are more records being output to the Debit than to the Credit.  For example, in the test, 7 records are output by the Debit while only 3 records are output by the Credit.  You expect the quantity of Debit and Credit records to match.

In the Allocation setup, the Debit and Credit screens both output to [Current_Amount] on Management Ledger.

Debit has the following setup:

Financial Element: 23000
Organizational Unit: <Same As Driver>
General Ledger Account: 204983
Common Chart of Accounts: <Same As Driver>
Product: <Same As Driver>
Legal Entity: <Same As Driver>
LOB ID: <Same As Source>

Credit has the following setup:

Financial Element: 23000
Organizational Unit: <Same As Source>
General Ledger Account: 204469
Common Chart of Accounts: <Same As Source>
Product: <Same As Source>
Legal Entity: <Same As Source>
LOB ID: <Same As Driver>

In the Credit, you wanted to set the same dimensions to <Same As Driver> as in the Debit but the Allocation user interface does not allow this setup.  You get the following error:

Error ID: 1109
Error Description: Please select appropriate Macros/Values for the dimension

As a result, you have to choose different dimensions for the <Same As Driver> setting in the Debit and Credit.  And, in the results output, the Credit rows are not offsetting the Debit rows correctly because fewer Credit rows are output.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms