FSI_PARTY_ID_CHANGE_DTLS Table Usage In RRS Reporting
(Doc ID 2807150.1)
Last updated on SEPTEMBER 21, 2021
Applies to:Oracle Financial Services - Regulatory Reporting for US Federal Reserve - Lombard Risk Integration Pack - Version 8.0.8 and later
Information in this document applies to any platform.
On : 8.0.8 version, Metadata
FSI_PARTY_ID_CHANGE_DTLS table usage in RRS reporting
1. The primary key constraint on this table is on (V_CURR_PARTY_ID, D_PARTY_ID_CHANGE_DATE). As indicated in the example below, if more than one counterparties get merged into a party on the same day, the constraint will get violated.
A bank 888 holds their deposits with Customer and has opened up 2 new branches. With new branch, new parties are created. Since these two parties are under one bank, they are merged to 888. Since the primary key constraint on this table is on (V_CURR_PARTY_ID, D_PARTY_ID_CHANGE_DATE, the constraint will be violated since they were merged on the same day.
V_PREV_PARTY_ID V_CURR_PARTY_ID D_PARTY_ID_CHANGE_DATE Notes
123 888 10/20/2019 Merge Operation - Branch 123 merged into 888 Bank
456 888 10/20/2019 Merge Operation - Branch 456 merged into 888 Bank
2. There’s also a scenario noticed in EPIC, where a party is un-merged from another party. As indicated in the example below,
a. Customer A and Customer B have same last name of XXX.
b. Customer A has a Social Security Number of 1114. Customer B has a Social Security Number of 1115. Both very similar.
c. Two party ID’s were created:
i. Customer A: 123
ii. Customer B: 456
d. Due to the various similarities in identifiers, EPIC has identified and merged the two parties, believing they are related parties.
i. Party 123 was merged into Party 888 on 9/30
ii. Party 456 was also merged into Party 888 on 9/30
e. EPIC does regular reviews of data quality reviews and notices that Customer A and Customer B are two different entities.
f. On 12/31, 123 was unmerged from 888. As per the current table design, it will appear that 888 is no longer an active party. However, that’s’ not the case. Only 123 was unmerged. Both Customer A and B still have active accounts.
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