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

Configuring Siebel Data Quality Matching Server Using SSA

Two processes are needed to configure the Siebel Data Quality Matching Server using SSA. These processes are documented as phases and further broken down into the following steps to make it easier for you to implement:

Phase 1: Associating SSA to a Business Component

In this phase, you associate SSA to a Siebel business component. For this example, the Account business component is used.

To associate SSA to a business component

  1. Log in to Siebel Tools.

    2. For more information about Siebel Tools, see Siebel Tools Reference.

  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.

      3. The value choices are:

      • Company_Mandatory
      • Company_Optional
      • Contact_Mandatory
      • Contact_Optional

        • 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 in the Siebel eBusiness Third-Party Bookshelf.

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

      2. CAUTION:  It is recommended that you contact Siebel Technical Support about key table creation.

    2. Create a new business component with this newly created key table.

      3. For information about how to create a new business component, see Siebel Tools Reference.

    3. Define the user properties for that business component.

      4. NOTE:  The Data Quality Matching Server requires a key table for each business component (whereas the Siebel Data Quality Universal Connector does not).

  5. 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.

      5. 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.

      6. 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.

Phase 2: Mapping SSA Fields to Fields in a Siebel Business Component

In this phase, you map SSA fields to fields in a Siebel business component. For this example, the Account business component is used.

  1. Log in to Siebel Tools.

    2. For more information about Siebel Tools, see Siebel Tools Reference.

  2. Define the deduplication field mappings user properties for the Account 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 Business Component User Prop.
    4. In the Business Component User Props list, query for SSA DeDuplication Field*, and enter values using the following syntax.

      5. Property Name
      Value
      SSA DeDuplication Field n, where n is a number starting from 1.
      "Vendor Input Field", "Siebel Field"

      NOTE:  You can have more than one field mapping.

TIP:  If you deactivate a field mapping, you may need to shift the remaining fields ahead so that your list of field mappings is sequential. For example, if you deactivate field 2, you may need to change field 3 to field 2, field 4 to field 3, and so on. If you do not shift the remaining fields, the Siebel application recognizes only one field mapping and cannot find field 2 or subsequent fields.

Table 29, Table 30, and Table 31 provide the user property values for the Account, Contact, and List Mgmt Prospective Contact business components, respectively. For information about configuring these properties, see Data Quality Configuration Options.

Table 29 provides the user properties for the Account business component.

Table 29.  Account Business Component User Properties
User Property Name
Value1
SSA DeDuplication Field 1
"C", "Name"
SSA DeDuplication Field 2
"Country", "Country"
SSA DeDuplication Field 3
"City", "City"
SSA DeDuplication Field 4
"State", "State"
SSA DeDuplication Field 5
"Z", "Postal Code"
SSA DeDuplication Field 6
"I", "DUNS Number"
SSA DeDuplication Field 7
"A", "Street Address"

1The syntax for the values is: "Vendor Input Field", "Siebel Field".

Table 30 provides the user properties for the Contact business component.

Table 30.  Contact Business Component User Properties
User Property Name
Value1
Property Name
Property Value
SSA DeDuplication Field 1
"Z", "Postal Code"
SSA DeDuplication Field 2
"T", "Work Phone #"
SSA DeDuplication Field 3
"T", "Cellular Phone #"
SSA DeDuplication Field 4
"I", "Social Security Number"
SSA DeDuplication Field 5
"E", "Email Address"
SSA DeDuplication Field 6
"A", "Street Address"
SSA DeDuplication Field 7
"T", "Home Phone #"
SSA DeDuplication Field 8
"C", "Account"
SSA DeDuplication Field 9
"Last", "Last Name"
SSA DeDuplication Field 10
"First", "First Name"
SSA DeDuplication Field 11
"Middle", "Middle Name"
SSA DeDuplication Field 12
"City", "City"
SSA DeDuplication Field 13
"State", "State"
SSA DeDuplication Field 14
"Country", "Country"

1The syntax for the values is: "Vendor Input Field", "Siebel Field".

Table 31 provides the user properties for the List Mgmt Propitiate Contact business component.

Table 31.  List Mgmt Prospective Contact Business Component User Properties
User Property Name
Value1
SSA DeDuplication Field 1
"Last", "Last Name"
SSA DeDuplication Field 2
"First", "First Name"
SSA DeDuplication Field 3
"Middle", "Middle Name"
SSA DeDuplication Field 4
"C", "Account"
SSA DeDuplication Field 5
"A", "Street Address"
SSA DeDuplication Field 6
"City", "City"
SSA DeDuplication Field 7
"State", "State"
SSA DeDuplication Field 8
"Z", "Postal Code"
SSA DeDuplication Field 9
"Country", "Country"
SSA DeDuplication Field 10
"T", "Work Phone #"
SSA DeDuplication Field 11
"T", "Cellular Phone #"
SSA DeDuplication Field 12
"I", "Social Security Number"
SSA DeDuplication Field 13
"E", "Email Address"
SSA DeDuplication Field 14
"T", "Home Phone #"

1The syntax for the values is: "Vendor Input Field", "Siebel Field."


 Siebel Data Quality Administration Guide 
 Published: 15 May 2003