Data Quality Guide for Oracle Customer Hub > Configuring Data Quality with Oracle Enterprise Data Quality >

Overview of Configuring Oracle Enterprise Data Quality for Deduplication of Child Entities

Oracle Enterprise Data Quality (EDQ) can be configured to support the deduplication of a parent object's child entities. The steps to do this depend on the complexity of the child entity you want to use. When multiple child entity matching is enabled hierarchical data from Siebel CRM is transformed by the Siebel Connector into a flat record structure so that EDQ can match parent records (such as Contacts, Prospects, or Accounts) using the details of the child records (such as Names, Addresses, Email Addresses, Alternative Phone Numbers, and so on). Siebel Connector can be configured to handle child entities either as scalar (single field) or non-scalar (multi-field) objects.

Scalar groups are used for Siebel business components comprising one field, or for which only one field is mapped in the Data Quality field mappings in the Siebel database. The connector prepares the values for such groups into a simple delimited list of values in a single input attribute for EDQ.

Non-scalar groups are used for more complex child entities comprising multiple fields, such as names and addresses. In this case, the connector prepares multiple records for the same parent to submit to EDQ for matching purposes, each with different child data.

The following is an overview of the steps required to configure Enterprise Data Quality to process additional child entity types. For more information about extending the matching configuration, see Oracle® Enterprise Data Quality Customer Data Services Pack Customization Guide 11g Release 1 (11.1.1.7) on Oracle Technology Network (OTN).

To extend the matching configuration in Oracle Data Quality (EDQ)

1. In Oracle Data Quality (EDQ), extend the EDQ-CDS project to provide configuration logic to implement deduplication for the child entity type as follows:
   1. Edit the Web service definition (corresponding to the appropriate parent object type) to include the new attributes for the child entity type.
   2. Edit the candidates snapshot to include the new attributes.
   3. Edit the candidates data interface to include the new attributes.
   4. Edit the data interface mapping for the snapshot to include mappings for the new attributes.
   5. Edit the data interface mapping for the Web service to include mappings for the new attributes.
   6. Edit the cluster process to implement any new cluster key generation logic required for the child entity type.
   7. Edit the match process to implement the new matching logic for the child entity type.
2. Modify EDQ Siebel Connector dnd.properties file as follows:
   1. Edit the Multiple child entity groupings section to define the child entity as either a scalar or non-scalar group as appropriate.
   2. Restart the Siebel Server to apply the changes.