Siebel Data Quality Administration Guide > Data Quality Configuration Options >

Configuring Business Components to Support Data Matching (Deduplication)

The matching functionality is implemented into a DeDuplication business service. For you to use the DeDuplication business service with a new Siebel business component, use the following procedure.

To configure a business component to support data matching (deduplication)

  1. Base the business component on the CSSBCBase class property to support real-time data matching.

    2. NOTE:  This class includes the specific logic to invoke the DeDuplication business services.

  2. Associate the business component to a connector using user properties for the business component.

    3. For example, add a new user property to the DeDuplication Connector - VendorName business component. For more information, see Configuring the Siebel Data Quality Universal Connector.

  3. Create the field mappings between the Siebel fields that you want to cleanse and the field names recognized by the external vendor.

    4. For more information, see Configuring the Siebel Data Quality Universal Connector.

  4. Configure a DeDuplication Results business component based on the S_DEDUP_RESULT table with the following field values:

    5. Dup Object Id. Column:
    DUP_OBJ_ID
    Object Id. Column:
    OBJ_ID
    Object Name. Column:
    OBJ_NAME
    Request Id, Column:
    DEDUP_REQ_ID
    Total Score. Column:
    TOT_SCORE_VAL

    The Siebel DeDuplication business service stores the ROW_ID of the matched pairs in the OBJ_ID and DEDUP_OBJ_ID columns. You can use these columns to join your business component to the primary data table to expose more information of the matched records.

    NOTE:  The Siebel matching process uses the S_DEDUP_RESULT table to store the matched pairs with a weighted score. The DeDuplication Results business component is required to insert matched pairs into the S_DEDUP_RESULT table as well as display the duplicate records in a DeDuplication Results list applet to users.

  5. Add the new DeDuplication Result business component to the DeDuplication business object.
  6. Add the new business component to the business object of the view where you want to enable real-time deduplication.

    7. In your primary business component, add a user property called DeDuplication Results BusComp and specify the DeDuplication Results business component that you just configured.

  7. Configure an applet as your DeDuplication Results List Applet based on the business component you configured in Step 4.

    8. This applet is used to display the duplicate records for real-time mode.

    TIP:  It is recommended you make a copy of an existing applet, such as the DeDuplication Results (Account) List Applet, and then make changes to the values (applet title, business component, and list columns). You may want to add join tables and fields to your DeDuplication Results business component and map these fields to your list applet so that you can see the duplicate records rather than their row Ids.

  8. For you to trigger real-time matching, perform the following:
    1. Modify the applet in which users enter or modify the customer data and base it on the CSSFrameListBase for a list applet or CSSFrameBase for a form applet.
    2. Add a user property called DeDuplication Results Applet and specify the DeDuplication Results List Applet you configured in Step 7 in the value column.
  9. For Siebel Data Quality Matching Server only. Create a match key table in the database and configure a match key business component.

    10. For more information. see Configuring Siebel Data Quality Matching Server Using SSA.

  10. Configure duplicate resolution views and add them to the Data Administration screen.

    11. It is recommended you use the Account Duplicates View and the Account Duplicates Detail View as your examples to learn how to configure new views.

  11. Add a field called Merge Sequence Number to the business component and a user property called Merge Sequence Number Field.

    12. This configuration is used for sequenced merges. For more information, see Merging Duplicate Records.

    TIP:  You do not need to map field Merge Sequence Number to a database column. Instead, set the Calculated attribute for that field.


 Siebel Data Quality Administration Guide 
 Published: 15 May 2003