Siebel Data Quality Administration Guide > Configuring Siebel Data Quality >

Example of Configuring a Business Component for Data Matching Using SSA-NAME3

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

To configure a business component for data matching with SSA

1. Start Siebel Tools.
2. In the Object Explorer, double-click the Business Component object to expand it, and then select the business component of interest.
3. In the Object Explorer, click 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 new records with the properties and values provided in the following table.

   Property	Value	Comments
   Deduplication Connector - SSA	"SSA"
   SSA Match Purpose	Enter one of the following values: Company_Mandatory Company_Optional Contact_Mandatory Contact_Optional NOTE:  By default, the Account business component is set to Company_Optional, and the Contact and List Mgmt Prospective Contact 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. SDQ supports only these four Match Purpose values. For more information about match purpose, see Match Purpose.

5. Configure a DeDuplication Key business component and user properties to specify the business component for your key table.

   NOTE:  Due to the complexity of creating database tables, it is recommended that you contact your database administrator for key table creation.

   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

        For example, the Account business component uses the S_ORG_DEDUP_KEY key table.

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

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

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

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

        For example, the Account business component uses DeDuplication - SSA Account Key.

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

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

      Business Component name/DeDuplication - SSA Business Component name Key

      For example, the link for the Account business component is: 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 5 with the properties and values provided in the following table.

      Property	Value
      Name	DeDuplication - SSA Business Component name Key
      Destination Link	Business Component name/DeDuplication - SSA Business Component name Key
      Destination Business Component	DeDuplication - SSA Business Component name Key

      For example, the properties and values for the Account business component 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 5 with the properties and values provided in the following table.

      Property	Value
      Name	Algorithm Type
      Multivalue Link	DeDuplication - SSA Business Component name Key

      For example, the multivalue link for the Account business component is: DeDuplication - SSA Account Key.

      For more information about links and multivalue links, see Configuring Siebel Business Applications.

7. Configure the DeDup Key Modification Date and DeDup Last Match Date fields for your business component:
   1. In the Object Explorer, double-click the Business Component object to expand it, and then select the business component you created in Step 5.
   2. In the Object Explorer, click Field.
   3. In the Fields list, create two new records with the properties and values provided in the following table.

      	Value
      Property	Join	Column	Type
      DeDup Key Modification Date	Base table for the business component	DEDUP_KEY_UPD_DT	DTYPE_UTCDATETIME
      DeDup Last Match Date	Base table for the business component	DEDUP_LAST_MTCH_DT	DTYPE_UTCDATETIME

      For example, the values for the Account business component are listed in the following table:

      	Value
      Property	Join	Column	Type
      DeDup Key Modification Date	S_ORG_EXT	DEDUP_KEY_UPD_DT	DTYPE_UTCDATETIME
      DeDup Last Match Date	S_ORG_EXT	DEDUP_LAST_MTCH_DT	DTYPE_UTCDATETIME

      After a record is processed during key generation, the DeDuplication business service updates the following fields to the current date and time:

      DeDup Key Modification Date. This is useful for future batch generations because you can run a key refresh instead of a more time-consuming key generation.

      DeDup Last Match Date. This is useful for future batch data matching because you can set an Object WHERE Clause to process records that have not changed since the last match date.

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

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

   Field	Value
   Dup Object Id	DUP_OBJ_ID
   Object Id	OBJ_ID
   Object Name	OBJ_NAME
   Request Id	DEDUP_REQ_ID
   Total Score	TOT_SCORE_VAL

   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.

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.

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