Siebel Data Quality Administration Guide > Configuring Siebel Data Quality >

Example of Configuring Business Components for Data Matching Using Third-Party Software and Universal Connector

This topic gives one example of configuring a business component for data matching with Firstlogic. You may use this feature differently, depending on your business model.

The SDQ data matching functionality, also known as deduplication, is implemented by way of the DeDuplication business service.

The third-party software used as an example in this topic is Firstlogic, however the steps in the procedure are similar for other third-party software.

To configure a business component to support data matching for Firstlogic

  1. Start Siebel Tools.
  2. In the Object Explorer, select the Business Component object, and then select the business component of interest.

    NOTE:  Make sure the business component is based on the CSSBCBase class property to support real-time data matching, or make sure that the business component is based on a class whose parent is CSSBCBase. This class includes the specific logic to invoke the DeDuplication business service.

  3. In the Object Explorer, select Business Component User Prop.

    TIP:   If the Business Component User Prop object is not visible in the Object Explorer, you can enable it in the Development Tools Options dialog box (View > Options > Object Explorer).

  4. In the Business Component User Properties list, create a new record and complete the necessary fields.

    For example, the following table shows the preconfigured data matching connectors for the Account business component:

    User Property Name

    DeDuplication Connector - Firstlogic


    For data matching with Firstlogic applications.

    Properties deprecated after 7.8.2 release

    DeDuplication Connector - Vendor1


    For data matching with Firstlogic applications.

  5. Configure a user property to assign a Type to your business component.

    For example, a user property value for the predefined Account business component is:

    User Property Name

    Dedup Type


    Business component type for Firstlogic connector

    This user property is not required, however it does provide a way for the vendor DLL to recognize the type of records the Siebel application passes to it. Some vendors do require this type as a predefined keyword. If it is not required as a keyword, developers can instead make the type a unique word so that the DLL identifies the type change when switching from one type to another in Siebel Business Applications.

  6. Configure the following user properties:
    User Property

    Dedup Token Expression

    Contact the vendor for the appropriate value of this field.

    Dedup Query Expression

    Contact the vendor for the appropriate value of this field.

  7. Create the field mappings between the Siebel fields for which data matching is required and the field names recognized by the vendor.

    For more information, see Mapping Data Matching Connector Fields to Siebel Business Components.

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

    Dup Object Id


    Object Id


    Object Name


    Request Id


    Total Score


    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.

  9. Add the new DeDuplication Results business component to the DeDuplication business object.
  10. Add the new business component to the business object of the view where you want to enable real-time data matching.

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

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

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

    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.

  12. 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 11 in the value column.
  13. Configure Duplicate views and add them to the Administration - Data Quality screen.

    NOTE:  It is recommended you copy and rename the existing Account Duplicates View and the Account Duplicates Detail View as examples for configuring new views.

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

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

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

Siebel Data Quality Administration Guide Copyright © 2006, Oracle. All rights reserved.