Oracle Customer Hub (UCM) Master Data Management Reference > Configuring the Survivorship Settings for Oracle Customer Hub (UCM) > Administering Survivorship for Oracle Customer Hub (UCM) >

Considerations When Using Child Survivorship Rules

This example demonstrates Source and Recent Rule of Entity Survivorship with the Personal Address Child object.

Rules of Execution

• During an Insert operation Entity Survivorship rules are not applied, but attribute data is captured.
• The default criteria for user key-based matches are used to eliminate the losing record in case of a user key-based match.
• Internal Resolution between child records is performed either within the existing master record or with the incoming match record using the default criteria.
• When using Field Value Based rules, the rule executed on the child record whose field value matches those defined, the record with the lowest sequence number has the highest rank.
• If you are using the Same Field Value Based rule, and the Comparison Field Value provided is empty then the Entity Survivorship engine looks for an Exact Value match child record to apply the comparison rule. This is typically used on FINCORP Loan, or deposit account objects to apply the rule to obtain an exact account number.

Setup

Use the Personal Address child object of the Contact parent object with the Default Criteria set to Recent. Table 38 lists the comparison rule details.

Note the additional information shown in Table 39:

Execution Examples

1. Oracle Customer Hub (UCM) receives a Contact record (C1) from the system Ebiz01 with following three Personal Addresses:
   • Personal Address Record A1: INSPersonalAddressType = Value 1
   • Personal Address Record A2: INSPersonalAddressType = Value 2
   • Personal Address Record A3: INSPersonalAddressType = Value 2

     The result is that attribute data from the Contact record is inserted with three personal address records.

2. Oracle Customer Hub (UCM) receives a Contact record (C2) from the system Siebel01 with three different Personal Addresses:
   • Personal Address Record A4: INSPersonalAddressType = Value 1
   • Personal Address Record A5: INSPersonalAddressType = Value 2
   • Personal Address Record A6: INSPersonalAddressType = Value 2

     As Contact record C2 is similar to C1 from the match result, the Survivorship engine is invoked to generate the surviving record with resultant children records.

Now the user key based matches are identified and default criteria is applied to eliminate the losing child record. The contact record C1 has the Address A1 attribute and the contact record C2 has the Address attribute A4, and both have the same user keys, and the default criteria of Recent is applied the Address A4 of Contact Record C2, being the most recent record, prevails.

Now two contact records' child records are subjected to field value based rules:

• Since Address Type = Value 1 has already been resolved using the user key based match Contact Record C2's A4 will be part of final surviving record.
• Since Address Type = Value 2 has the Source comparison rule, but before the rule can be applied the child records are run through the Internal Resolution process as explained below:

  If EntityInternalProcess_PersonalAddress is set to True, the Contact C1 record undergoes internal resolution for addresses A2 and A3 which have the same INSPersonalAddressType of Value 2. Since the default criteria is set to Recent the most recent of the two versions prevails, in this case, A3. The A2 record's end date column is updated with the current date and time.

  Also, if EntityInternalProcess_PersonalAddress is set to True, the Contact C2 record undergoes internal resolution for addresses A5 and A6 which have the same INSPersonalAddressType of Value 2. Since the default criteria is set to Recent the most recent of the two versions prevails, in this case, A6. The A5 record's end date column is updated with current date and time.

• Applying the Field Value based rule (which is set to Source) for INSPersonalAddressType = <Value 2> the source confidence of System = Siebel01(80) is greater than Ebiz01(70) so the A6 record prevails over the A3 record. The A3 record's end date column is updated with the current date and time.

So, the result is that Contact (C12) with five Personal Address records (and A4 and the A1 records with the same user key, INSPersonalAddressType = Value 1) prevailed and the A6 record with INSPersonalAddressType = Value 2 prevailed while the A2, A3 and A5 address records are end dated.

The attribute data is also inserted for new address records and updated for the previously existing address records accordingly.