Duplicate Records in FSI_D_XXXXX Tables After Running T2T With Updated Accounts (Doc ID 2135750.1)

Last updated on AUGUST 14, 2017

Applies to:

Oracle Financial Services Asset Liability Management - Version 8.0.0 to 8.0.4 [Release 8]
Oracle Financial Services Funds Transfer Pricing - Version 8.0.0 to 8.0.4 [Release 8]
Oracle Financial Services Profitability Management - Version 8.0.0 to 8.0.4 [Release 8]
Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.0 to 8.0.4 [Release 8]
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Table to Table (T2T)
Data Management
Data Mapping
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Reveleus Liquidity Risk Management (LRM)
Slowly Changing Dimension (SCD)

Symptoms

On ALM/LRM 8.0.1, after running the SCD for DIM_ACCOUNT, it appears that there are now additional records in dim_account with F_LATEST_RECORD_INDICATOR=’Y’ and old one updated to F_LATEST_RECORD_INDICATOR=’N’ . This is triggering duplicate record issues after running the T2T which load the FSI_D_xxxxxxxx tables since the T2T does not have a filter for DIM_ACCOUNT.F_LATEST_RECORD_INDICATOR='Y'.

ACTUAL BEHAVIOR
Have recently updated one of the field (V_ORIGINAL_ACCOUNT_NUMBER in all stg_XXXXX (All instrument) tables), which has created one new record in dim_account with F_LATEST_RECORD_INDICATOR=’Y’ and old one updated to F_LATEST_RECORD_INDICATOR=’N’ .
However, the T2T`s which loads the data from stg_XXXXX by joining dim tables (one of them is Dim_aacount) into the FSI_D_XXXXX is not considering DIM_ACCOUNT.F_LATEST_RECORD_INDICATOR='Y'.
This is actually causing the issue of duplicate records.

EXPECTED BEHAVIOR
Expect that the seeded T2Ts filter by DIM_ACCOUNT.F_LATEST_RECORD_INDICATOR='Y'.

The issue can be reproduced at will with the following steps:
1. Run SCD for DIM_ACCOUNT
2. Run T2Ts for the instrument tables
3. Duplicate records are generated.

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