Do DIM_INSTRUMENT_TYPE and FSI_INSTRUMENT_TYPE_CD Share a List of Values?
(Doc ID 2376640.1)
Last updated on MARCH 20, 2019
Applies to:Oracle Financial Services Data Foundation - Version 8.0.0 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Enterprise Performance Management (EPM)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Data Foundation (FSDF)
In the Staging product processor (PP) tables the column v_instrument_type_cd:
1. Maps to DIM_INSTRUMENT_TYPE in FSDF in T2T such as T2T_STG_LOANS_CAS when moving data from the PP table in Staging to FCT_COMMON_ACCOUNT_SUMMARY in Processing
2. Maps to FSI_INSTRUMENT_TYPE_CD in EPM processing in T2T such as T2T_LOAN_CONTRACTS
One could therefore expect DIM_INSTRUMENT_TYPE and FSI_INSTRUMENT_TYPE_CD to share a list of values.
This is not the case. In the values in v_instrument_type_cd meets the needs of FSDF, then it will not meet the needs of EPM, and vice versa.
Is this an issue or a misunderstanding?
Question 2: Column v_instrument_type_cd in product processors has two different references: one from FSDF and one from EPM, both having their own different list of values.
Reason for saying this is that same staging column (i.e. v_instrument_type_cd) was noticed to be used in both join conditions from FSDF's T2T_STG_LOANS_CAS (as in the latest FSDF 8.0.4 technical metadata) and ALM's T2T_MORTGAGES (in the latest ALM 8.0.4 technical metadata), albeit joining to different dimension tables.
As the common staging area is supposed to be "common", then the content of v_instrument_type_cd would be expected not to vary whether one is doing an FSDF or an ALM based implementation.
Please verify and if required, kindly have FSDF introduce a new column in product processors for their version of ‘Instrument Type’.
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