EFPA: Incorrect Signage for Certain Reporting Lines

(Doc ID 2010911.1)

Last updated on JULY 17, 2015

Applies to:

Oracle Financial Services Enterprise Financial Performance Analytics - Version 6.1.1 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Data Foundation (FSDF) previously known as Oracle Financial Services Data Warehouse (FSDW)
Oracle Business Intelligence Enterprise Edition (OBIEE)


On EFPA 8.0.0, it appears that the signage is incorrect for certain reporting lines.

EFPA reports use the reporting line dimension as the basis for the income statement and balance sheet dashboard reports. In the income statement, there is a reporting line 107302 - Net Interest Income. This is mapped from Financial Element 420 (Interest). FE 420 is a seeded FE which is used for both interest income as well as interest expense. When natural signage is used as the signage method, balances with FE 420 in Ledger Stat are positive irrespective of whether the balance is interest income or interest expense - it is the Common COA ID that determines whether the row corresponds to income or expense. (COA ID of 4000 is Interest Income and 4500 is Interest Expense).

Now, coming to EFPA, the parent node "Net Interest Revenue" (rep line id 85000) contains, in addition to other members, reporting line FTP Income/Expense (mapped to FE 450) and Net Interest Income.
For a liability product, it is expected that FTP Income/Expense and Net Interest Income will net out so that the parent "Net Interest Revenue" is a difference of the two, not a sum.

This can happen by transforming Net Interest Income to be a negative number in EFPA (since it is expense inside a revenue parent).

Similarly, for an asset product, it is expected that FTP Income/Expense needs to have its sign changed (since it becomes an expense), so that the parent Net Interest Revenue shows a net difference between the two.

Expect the reports to show correct signage based on the mapped Common COA ID.

The issue can be reproduced at will with the following steps:
1. Run the Income Statement Detail in RCY in EFPA and validate against Ledger Stat numbers


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