Oracle Customer Hub (UCM) Master Data Management Reference > Configuring Source Data History and Cross-Reference Functionality > Administering Source Data and Cross-Reference Functionality for Oracle Customer Hub (UCM) >

About Oracle Customer Hub (UCM) Data Management Services

Oracle Customer Hub (UCM) provides the following data-management services to cleanse, identify, and link incoming source data to the master data records:

• Account Data Management Service
• Contact Data Management Service

These services are invoked through the Siebel Enterprise Application Integration (Siebel EAI) interface and can process single or multiple records. Records updated directly within Oracle Customer Hub (UCM) also trigger similar data management services but do not trigger the survivorship rules. These services take an incoming account or contact record and do the following:

• Check the system privilege of the application submitting the record.
• Cross-reference the record if an external account ID is provided.
• Create the Universally Unique Identifier (UUID) for the record if the record is new.
• Call the Data Cleansing Engine to standardize and validate account or contact name and address.
• Perform an exact match process that is based on the configured parameter. The default value for account records is External Account ID, and the default value for contact records is External Contact ID.
• If an exact match is not found, call the Data Matching Engine to perform fuzzy matching to identify possible duplication. The default is Account Name for account records. The default is Contact first name and last name for contact records.

NOTE:  Oracle Customer Hub (UCM) provides an embedded data matching and cleansing solution. The Siebel Data Quality module is licensed separately from Oracle Customer Hub (UCM). See Data Quality Guide for Oracle Customer Hub (UCM) and your third-party data quality provider documentation for more information.

Depending on the matching score returned from the Data Matching Engine, Oracle Customer Hub (UCM) can create a new record, link to an existing record, or store the incoming record for further investigation by the data steward. By default, the Data Matching Engine returns two threshold scores, an auto threshold score (upper) and manual threshold scores (lower), numbered on a scale of 0-100. You can configure these threshold numbers using Siebel Tools. The matching score results in the following three possibilities:

• When the incoming record is matched above the upper threshold, Oracle Customer Hub (UCM) applies survivorship rules to merge the incoming record with an existing record in Oracle Customer Hub (UCM). For information on survivorship and on setting up the rules, see Process of Creating Survivorship Rules.
• When the incoming record is matched below the lower threshold, Oracle Customer Hub (UCM) creates a new record and publishes a new-record message to other external systems. For information on publishing and subscribing, see Configuring System Publish and Subscribe for Oracle Master Data Management Applications.
• When the incoming record is matched between the upper-threshold number and the lower-threshold number, Oracle Customer Hub (UCM) stores the record in the deduplication table (S_UCM_DEDUP) for further investigation. Data stewards can view the pending records in the Incoming Duplicates-Account or Contact screen.

  Configure your matching threshold and the Data Matching Engine rules based on your organization's data quality standards.