1. Data Quality for Oracle Customer Hub Guide
  2. Configuring Business Components and Applets for Data Matching and Data Cleansing

Configuring Business Components and Applets for Data Matching and Data Cleansing

This topic describes how to configure business components and applets, whether existing ones or new ones you create, for data matching and data cleansing.

You can configure existing business components or create additional business components for data matching for the Matching Server and for data matching and data cleansing for the Universal Connector.

Typically, you configure existing business components; however, you can create your own business components to associate with connector definitions. For information about how to create new business components and define user properties for those components, see Configuring Siebel Business Applications.

Note: You must base new business components you create only on the CSSBCBase class to support data cleansing and data matching, or make sure that the business component uses a class whose parent is CSSBCBase. This class includes the specific logic to call the DeDuplication and Data Cleansing business services.

To configure business components for data matching and data cleansing, complete the steps in the following procedure. This topic is a step in Process of Configuring New Data Quality Connectors.

To configure business components for data matching and cleansing

  1. Associate the business component with a connector.

    This includes configuring the vendor parameters shown in the following table.

    Name Value

    For data matching

    Business_component_name DeDup Record Type

    Business_component_name

    For data matching

    Business_component_name Token Expression

    Consult the vendor for the value of this field.

    Note: Applies to the Universal Connector, where key generation is carried out by the Siebel application.

    For data matching

    Business_component_name Query Expression

    Consult the vendor for the value of this field.

    Note: Applies to the Universal Connector, where key generation is carried out by the Siebel application.

    For data matching

    Parameter 1

    "global", "iss-config-file", "ssadq_cfg.xml"

    Note: Applies to the Oracle Data Quality Matching Server only, where match keys are generated by the Oracle Data Quality Matching Server.

    For data cleansing

    Business_component_name DataCleanse Record Type

    Business_component_name

  2. Configure the field mappings for each business component and operation.

  3. Create a DeDuplication Results business component and add it to the Deduplication business object.

  4. Configure an applet as the DeDuplication Results List Applet.

  5. Configure Duplicate views and add them to the Administration - Data Quality screen.

  6. Add the business component user properties as shown in the following table.

    Property Value

    DeDuplication Results BusComp

    The buscomp that you created in Configuring Business Components and Applets for Data Matching and Data Cleansing.

    DeDuplication Results List Applet

    The applet that you created in Configuring Business Components and Applets for Data Matching and Data Cleansing.

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