Siebel Data Quality Administration Guide > Configuring Siebel Data Quality >

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

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

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 cleansing

  1. Start Siebel Tools.
  2. In the Object Explorer, expand Business Component, 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 predefined data cleansing connector for the Account business component:

    User Property Name

    DataCleansing Connector - Firstlogic


    For data cleansing with Firstlogic applications.

    Properties deprecated after 7.8.2 release

    DataCleansing Connector - Vendor1


    For data cleansing 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

    DataCleanse Type


    Business component type for Firstlogic applications.

  6. Create the field mappings between the Siebel fields that you want to cleanse and the field names of the external software.

    For more information, see Mapping of Connector Fields to Business Component Fields.

  7. (Optional) If you want to prevent data cleansing on a selected record, perform the following:
    1. Add an extension column to the base table and map it to a business component field called Disable DataCleansing.
      For example, the fields used in the Business Address business component are:

      Field Name

      Disable DataCleansing



      Predefault value


      Text Length




  1. Expose this flag on the applet to allow you to disable data cleansing for certain records from the user interface.
    (Optional) Configure a field called Last Clnse Date so that the Data Cleansing business service can mark the last date and time that data cleansing was run on a particular record.

    Field Name

    Last Clnse Date



    Object Name. Column






    After a record is cleansed, the Data Cleansing business service attempts to update the Last Clnse Date business component field to the current date and time. This field is useful for future batch data cleansing, because you can use an Object WHERE Clause to cleanse only records that have changed since the last cleanse date. For example, the following values appear in the Account business component:

    Object Where Clause: [Last Clnse Date] < [Updated]

  • (Optional) Use a DataCleansing Conflict Id Field user property to specify the conflict Id field for a business component.

    In most implementations, user keys are defined in the database schema for each table. These user keys make sure that no more than one record has the same set of values in specific fields. For example, the S_ORG_EXT table used by the Account business component uses columns NAME, LOC (Location), and BU_ID (organization id) in the user keys. Before you run data cleansing against your database, you may have similar, but not exactly the same records, in your database.

    After these records are cleansed, they can cause user key violations because the cleansed values become exactly the same value. You can use the Conflict Id field to resolve this issue. Add the CONFLICT_ID system column (given this table column exists in the database schema) to the user keys and then configure a user property called DataCleansing Conflict Id Field in that business component. The following example is for the Account business component:

    User Property: DataCleansing Conflict Id Field
    Property Value: S_ORG_EXT.Conflict Id

    If a user key violation occurs when the Siebel application writes the cleansed records to the database, the application tries to update the Conflict Id field to the record's row Id to make the record unique and bypass the user key violation. After the entire database is cleansed, you can perform data matching to catch these records and resolve them.

    CAUTION:  Before modifying user keys, contact Oracle's Siebel Technical Support.

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