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

About Oracle Customer Hub (UCM) Survivorship Settings

Survivorship is the process of creating a best version record, known as a surviving record. When multiple systems attempt to contribute information about a customer, survivorship rules are used to govern how to construct a best version record, the surviving record, for the specific data object. Each rule is applicable to only one data object, and within each rule, multiple attribute group sets can be associated. Survivorship algorithms enable you to have greater control over the survivorship rules applied to the update and merge transactions. You can include conditions, such as Completion of Group, which designates the most complete combination of the Name and Main Phone Number fields is the retained Account record.

From Siebel CRM, Version 8.1.1.9 on, you can define survivorship rules for any child entity of the Account, Contact or Household object. You define survivorship rules for child entities in the UCM Entity Rule Set View.

From Siebel Innovation Pack 2014, you can define survivorship rules for Contact Social Media Profile as child entity of the Contact object.

Additionally, you might use the Master Wins and Slave Wins survivorship rules. The Master Wins rule stipulates that the values stored in Oracle Customer Hub (UCM) always win over the incoming record, or in the case of a merge operation, the surviving record's value always wins over the victim's value. The Slave Wins rule stipulates that the values sent by an external application to Oracle Customer Hub (UCM) always win over the values in the existing best version record, or in the case of a merge operation, the victim record's values will be retained over the surviving record's value.

Survivorship rules govern how the best version record can be constructed for the specific data object. Each rule is applicable to only one data object. Within each rule, though, there can be multiple attribute group sets associated with the rule.

Attribute group rule intersection objects are in specific survivorship rules. These objects are used to govern how the specific attribute group functions within the given rule when evaluated by the UCM Survivorship Engine. For information on configuring UCM Survivorship Engine properties, see Configuring UCM Transaction Manager for Data Management and Survivorship.

Definitions of Survivorship Terms

This topic describes terms used in the implementation of survivorship.

• Cross-Reference. Tables within Oracle Customer Hub (UCM) to link the Unique Id (UID) within Oracle Customer Hub (UCM) to the Source Id from each subscribed application.
• Data Consolidation. The process of consolidating incoming records contributed by source systems with matching best version records within Oracle Customer Hub (UCM), while applying survivorship to govern the update of fields.
• Merge. The process of combining two or more duplicate best version records into a single surviving record. During the merge process, survivorship is applied, and appropriate audit trail information is recorded.
• Data Recovery. The process of reverting to historical versions of the best version record from an erroneous update or merge operation.
• Victim Record. The record that is merged into another record during the merge process. This record is usually not retrievable after a merge.
• Surviving Record. The record into which another record or records are merged during a merge process. This record remains in Oracle Customer Hub (UCM) after a merge.
• Source Confidence Level. The level of confidence on the validity of given attribute group field values from a specific source. Even though the source confidence level is specified in numbers, the importance is the relative value among sources, not the absolute value.