Siebel Data Quality Administration Guide > Configuring Siebel Data Quality Matching Server Using SSA >

Example of Associating SSA to a Business Component

This topic provides a sample configuration using the Account business component as an example. Use the following procedure as an example to associate SSA to a Siebel business component.

NOTE:  This procedure is provided only as an example—the Account business component is already enabled for DeDuplication. Use a similar procedure to enable deduplication for business components other than the default components, which are Account, Contact, List Mgmt/List Mgmt Prospective Contact.

To associate SSA with a business component

1. Log in to Siebel Tools.

   For more information about Siebel Tools, see Using Siebel Tools.

2. Set the DeDuplication Connector - SSA business component user property value to SSA.
   1. In the Object Explorer, expand the Business Component object.
   2. In the Business Components list, select Account.
   3. In the Object Explorer, click Business Component User Prop.
   4. In the Business Component User Props list, query for DeDuplication Connector - SSA.
   5. In the Value field, enter "SSA".
3. Assign a type name to your business component.
   1. With the Account business component selected, in the Business Component User Properties list, query for SSA Match Purpose.
   2. In the value field, enter Company_Mandatory.

      The value choices for the Account business component are: Company_Mandatory and Company_Optional. The value choices for the Contact business component are: Contact_Mandatory and Contact_Optional.

      NOTE:  The preceeding four choices are the only Match Purpose values supported by Siebel Data Quality (SDQ).

      By default, the Account business component is set to Company_Mandatory, and the Contact and Prospect business components are set to Contact_Optional. If a value is marked mandatory, it implies that the value counts against the total score. Values marked Optional do not count toward the total score.

      NOTE:  SSA supports two types of deduplication: company and contact. For more information, see the SSA-NAME3 documentation that is included on the Siebel eBusiness Third-Party Bookshelf.

4. Configure the DeDuplication Key business component user property to specify the business component for your key table.
   1. Create a key table.

      A key table is a database table that stores the SSA keys used for matching. You can use one of the following existing key tables as a model:

      • S_ORG_DEDUP_KEY
      • S_PER_DEDUP_KEY
      • S_PRSP_DEDUPKEY

        In this example for the Account business component, the S_ORG_DEDUP_KEY key table is used.

        NOTE:  The Data Quality Matching Server requires a key table for each business component (whereas the Siebel Data Quality Universal Connector does not). Due to the complexity of creating database tables, it is recommended you contact your database administrator for key table creation.

   2. Create a new business component based on the key table you created in Step a.

      You can use one of the following existing key business components as a model:

      • DeDuplication - SSA Account Key
      • DeDuplication - SSA Contact Key
      • DeDuplication - SSA Prospect Key

        In this example for the Account business component, the DeDuplication - SSA Account Key business component is used.

   3. Define the user properties for the business component you created in Step b.

      You can use the existing user properties for the following business components as a model:

      • DeDuplication - SSA Account Key
      • DeDuplication - SSA Contact Key
      • DeDuplication - SSA Prospect Key

        In this example for the Account business component, the DeDuplication - SSA Account Key business component is used.

        For information about how to create business components and define user properties, see Configuring Siebel eBusiness Applications.

5. Create a link and the Algorithm Type field for the business component and the key business component you created in Step 4.
   1. Create a link using the following syntax:

      <Business Component name>/DeDuplication - SSA <Business Component name> Key

      In this example for the Account business component, the link is called:
      Account/DeDuplication - SSA Account Key.

   2. Navigate to the Business Component object type and create a multi-value link for the business component you created in Step 4 using the following properties:
      • Name = DeDuplication - SSA <Business Component name> Key
      • Destination Link = <Business Component name>/DeDuplication - SSA <Business Component> Key
      • Destination Business Component = DeDuplication - SSA <Business Component name> Key.

        In this example for the Account business component, the values are:

      • Name = DeDuplication - SSA Account Key
      • Destination Link = Account/DeDuplication - SSA Account Key
      • Destination Business Component = DeDuplication - SSA Account Key
   3. Navigate to the Field object type and create a new field for the business component you created in Step 4 with the following properties:
      • Name = Algorithm Type
      • Multivalue Link = DeDuplication - SSA <Business Component name> Key

        In this example for the Account business component, the multi-value link is
        DeDuplication - SSA Account Key.

        For more information about links and multi-value links, see Configuring Siebel eBusiness Applications.

6. Configure the DeDup Key Modification Date and DeDup Last Match Date fields for your business component.
   1. In the Object Explorer, expand the Business Component object.
   2. In the Business Components list, select Account.
   3. In the Object Explorer, click Field.
   4. In the Fields list, query for DeDup Key Modification Date, and enter values.

      The following are values for the Account business component:

      Field Name:	DeDup Key Modification Date
      Join:	S_ORG_EXT
      Column:	DEDUP_KEY_UPD_DT
      Type:	DTYPE_UTCDATETIME

      TIP:   After a record is processed during key generation, the DeDuplication business service updates the DeDup Key Modification Date field to the current date and time. This is useful for future batch generations because you can run a key refresh instead of a more time consuming key generation.

   5. In the Fields list, query for DeDup Last Match Date, and enter values.

      The following are values for the Account business component:

      Field Name:	DeDup Last Match Date
      Join:	S_ORG_EXT
      Column:	DEDUP_LAST_MTCH_DT
      Type:	DTYPE_UTCDATETIME

      TIP:   After a record is processed during deduplication, the DeDuplication business service updates the DeDup Last Match Date field to the current date and time. This is useful for future batch deduplication because you can set an Object WHERE Clause to process records that have not changed since the last match date.