SCD type 2 changing latest record "latest record indicator" as 'N' while doing any backdated run
(Doc ID 2585033.1)
Last updated on MARCH 31, 2020
Applies to:Oracle Financial Services Basel Regulatory Capital Basic - Version 8.0.0 and later
Information in this document applies to any platform.
Problem with the Scd, type 2. If we insert rows for MIS date prior to current one (e.g. if we insert dimensions for 31.12.2017, but have data for dates 31.01. and 28.02. existing in the database), the Scd results with non-valid state of the rows, meaning we have more than one row valid for one date (more than one row per key for 31.12.2017. and non of the valid ones for 28.02.).
N_ACCT_SKEY V_EXPOSURE_ID F_LATEST_RECORD_INDICATOR D_RECORD_START_DATE D_RECORD_END_DATE
2370790 BG0000559F Y 31.12.2017. 31.12.9999.
2336653 BG0000559F N 31.01.2018. 30.12.2017.
2370790 is the latest record for mis date '31.12.2017'. Prior 2370790, there was 2336653 as current. So after SCD 2 run for mis date '31.12.2017', it will make 2336653 record "latest record indicator" as 'N' and 2370790 inserted record "latest record indicator" as '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