Join Condition for DIM_DAY_COUNT_IND is Incorrectly Mapped to V_data_origin Column in T2T
(Doc ID 2463451.1)
Last updated on AUGUST 12, 2020
Applies to:Oracle Financial Services Data Foundation - Version 8.0.2 to 8.0.7 [Release 8]
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Data Foundation (FSDF)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Data Management Tools (DMT)
Table to Table (T2T) Mapping
On FSDF 8.0.2, the join condition for DIM_DAY_COUNT_IND is incorrectly mapped to v_data_origin column in the 3 T2Ts - T2T_STG_BORROWINGS_CAS, T2T_STG_INVESTMENTS_CAS, T2T_STG_MUTUAL_FUNDS_CAS and requires correction
For example T2T_STG_INVESTMENTS_CAS contains ''LEFT OUTER JOIN
ON STG_INVESTMENTS.V_DATA_ORIGIN =
AND DIM_DAY_COUNT_IND.F_LATEST_RECORD_INDICATOR = 'Y' ''
The expected mapping should be with the column STG_INVESTMENTS.V_DAY_COUNT_IND and not column STG_INVESTMENTS.V_DATA_ORIGIN. The expected mapping is shown below:
The issue was noticed in v.802 but also verified to be present in the v.8061 technical metadata documentation.
Correct Mapping > LEFT OUTER JOIN DIM_DAY_COUNT_IND ON STG_INVESTMENTS.V_DAY_COUNT_IND = DIM_DAY_COUNT_IND.V_DAY_COUNT_IND_CODE AND DIM_DAY_COUNT_IND.F_LATEST_RECORD_INDICATOR = 'Y'
Incorrect Mapping > LEFT OUTER JOIN DIM_DAY_COUNT_IND ON STG_INVESTMENTS.V_DATA_ORIGIN = DIM_DAY_COUNT_IND.V_DAY_COUNT_IND_CODE AND DIM_DAY_COUNT_IND.F_LATEST_RECORD_INDICATOR = 'Y'
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