OFSAA PFT Questions on the Requirements for New User Defined Instrument Tables and the Required Super Class Entities and Columns

(Doc ID 2345815.1)

Last updated on JANUARY 05, 2018

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)
Data Model

Goal

Currently planning to create a new instrument table.  The user guide says for any new instrument table they need to be added to the below super classes entity tables. If there are any new dimensions to be added, those need to be added to the LEAF_COLUMNS super class.

BASIC_INSTRUMENT_REQ
LEAF_COLUMNS
MULTI_CUR_REQ
PORTFOLIO

There are new key dimensions which need to be added to the new instrument table like Card Product, Merchant Size, Client Size, etc. These dimensions are going to part of management ledger and also part of instrument table. These are key dimensions.

Questions:

1. By adding all the above super classes, all the unwanted columns which will not be used are inherited in the new instrument table. Is there any way to avoid all the unwanted columns ?
2. Any dimension column added to LEAF_COLUMNS will add those dimension columns to all of the instrument tables. Is there any way to avoid this? There are new dimension columns which need to be only in the custom instrument table and management ledger.
3. Is it supported to create a new super class entity having similar properties to LEAF_COLUMNS super class ? It is intended to add the new user defined key dimensions to the custom super class entities and relate these to the desired custom instrument tables.

Solution

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