Tie Breaker For Data Survival Metadata in Studio
(Doc ID 2897770.1)
Last updated on SEPTEMBER 28, 2022
Applies to:Oracle Financial Services Compliance Studio - Version 8.1.1 and later
Information in this document applies to any platform.
ER raised as below
When there is a tie that occurs in Data Survival, when using the DS metadata, the system picks a winner randomly when the metadata attribute has the same precedence number.
Customer1 Occupation = 'Teacher'
Customer2 Occupation= 'Banker'
In the table fcc_m_er_attribute_prec, Occupations are defined as:
Teacher : n_precedence = 1
Banker : n_precedence = 1
If we merge Cust 1 & 2 and use a DS rule of 'Metadata', 'Maximum'. There is no way to predict which attribute will survive because ER will choose randomly.
we would like to introduce Tie Breaker logic for the metadata survival logic so that the results are no longer random when there is a tie.
Tie Breaker Logic:
- Choose the customer with the earliest add date (stg_party_master_pre.d_start_date)
- If both customers have the same start date then choose the attribute of the customer whose ID comes first alphabetically (stg_party_master_pre.v_party_id).
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