Data Quality Guide for Oracle Customer Hub > Configuring Data Quality with Oracle Enterprise Data Quality > Process of Configuring Additional Child Entities for Deduplication >

Configuring Data Maps for Additional Child Entity Deduplication

This task is a step in Process of Configuring Additional Child Entities for Deduplication.

To use a new child entity for matching in Oracle Customer Hub (UCM) processes, you must add the new integration component and integration component fields to Oracle Customer Hub (UCM) integration objects (such as CIFContact, SwiPersonIO, or UCMContactSourceDataAndHistory). Additionally, to allow Oracle Customer Hub (UCM) to send the new fields to Oracle Enterprise Data Quality for matching, you must map the new fields from the Oracle Customer Hub (UCM) integration object to the Oracle Enterprise Data Quality integration object.

To perform the following steps you must have performed all preceding steps in this process to modify all required objects to include the new child integration component and integration component fields, and also the modified integration objects must have been redeployed to the Siebel run-time database.

Use this task to configure data maps for additional child entity deduplication.

To configure data maps for additional child entity deduplication

1. In Oracle Customer Hub (UCM), and navigate to Administration - Integration, then Data Map Editor.
2. In the Integration Object Map view, query for the required integration object map.

   For this example, use the following query: UCM Contact*DQ IO.

3. Modify the required maps.

   For this example, modify the following maps for Contact Deduplication:

   • UCM Contact CIF IO to DQ IO (used by the UCM Real-time Process).
   • UCM Contact SDH IO to DQ IO (used by the UCM Batch Process).
   • UCM Contact SOAP IO to DQ IO (used by the UCM Soap Process).
   • UCM Contact Match IO to DQ IO (used by the Person Match Web Service).
4. For each data map in this example, you must use the Integration Component Map view to add the Contact_Communication Address integration component. See the following table:

   Name	Source Component Name	Target Component Name	Source Search Specficiation
   Contact	Contact	Contact	Not applicable
   Contact_INS Personal Address	Contact INS Personal Address	Personal Address	Not applicable
   Contact Account	Contact Account	Contact	IsPrimaryMVG = 'Y'
   Contact_Communication Address	Contact Communication Address	Communication Address	Not applicable

5. Select the newly created integration component map, Contact_Communication Address, then in the Integration Field Map view add the mapping for an alternate email address using the following example:
   • Source Expression: [Alternate Email Address]
   • Target Field Name: Address
6. Repeat Step 4 and Step 5 for each additional data map.