BDF 8.1.2-AccountToCustomer Must Deal With Same ACCT/CUST ROLE Records In STG_PARTY_ACCOUNT_ROLE_MAP
(Doc ID 2906486.1)
Last updated on NOVEMBER 04, 2022
Applies to:
Oracle Financial Services Behavior Detection Platform - Version 8.1.1 and laterInformation in this document applies to any platform.
Goal
AccountToCustomer BDF Fails and no data is ingested into the CUST_ACCT table.
STG_PARTY_ACCOUNT_ROLE_MAP has the following primary keys:
FIC_MIS_DATE
V_ACCOUNT_NUMBER
V_PARTY_ID
D_ROLE_EFFECTIVE_DATE
V_ACCT_PARTY_ROLE
STG_PARTY_ACCOUNT_ROLE_MAP is used to populate the CUST_ACCT table. However the CUST_ACCT table has the following primary keys:
CUST_INTRL_ID
ACCT_INTRL_ID
CUST_ACCT_ROLE_CD
Because of entity resolution data in the STG_PARTY_ACCOUNT_ROLE_MAP where there are two records with different V_PARTY_ID, same V_ACCOUNT_NUMBER/FIC_MIS_DATE/V_ACCT_PARTY_ROLE, and different D_ROLE_EFFECTIVE_DATE. However due to Entity Resolution (ER), the V_PARTY_ID value, which originally contained two different customer IDs, is being replaced with the SAME ER Global ID. As a result, the BDF AccountToCustomer fails when this data scenario is encountered.
Solution
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
| Goal |
| Solution |
| References |