Enabling and Disabling Data Matching and Data Cleansing

This chapter describes how to enable data matching and data cleansing, and describes the data quality settings that you can apply for Siebel CRM and Oracle Customer Hub. Data cleansing and data matching must be enabled before you perform data quality tasks. This chapter includes the following topics:

Levels of Enabling and Disabling Data Cleansing and Data Matching

In Siebel Business Applications, there are various levels at which you can enable or disable data cleansing and data matching as summarized in the following table. In some of these views you can also specify the vendor used for data cleansing or data matching (the type). The table also shows who is most likely to set the parameters in each view.

Table Levels of Enabling and Disabling Data Matching and Cleansing

Screen and View	Setting or Parameter	Value	Parameters Set By
Values set at the enterprise level
Administration - Server Configuration, Enterprises, Data Quality	Enable button Disable button	Not applicable	Application administrator
Administration - Server Configuration, Enterprises, Parameters	DeDuplication Data Type Data Cleansing Type	Data Matching Vendor Name Data Cleansing Vendor Name	Application administrator
Values set for Data Quality Settings Note: These settings affect all the servers.
Administration - Data Quality, Data Quality Settings	Enable DataCleansing Enable DeDuplication	Yes or No	Data administrator
Values set at the object manager level
Administration - Server Configuration, Servers, select component Data Quality Manager, then click the Parameters tab	Data Cleansing Enable Flag Data Cleansing Type DedDuplication Enable Flag DeDuplication Data Type	True or False Data Cleansing Vendor Name True or False Data Matching Vendor Name	Data administrator
Administration - Server Configuration, Servers, select Object manager of application (for example, Sales Object Manager (ENU)), then click the Parameters tab	Data Cleansing Enable Flag Data Cleansing Type DedDuplication Enable Flag DeDuplication Data Type	True or False Data Cleansing Vendor Name True or False Data Matching Vendor Name	Data administrator
Values set at the user level
Tools, User Preferences, Data Quality	Enable DataCleansing Enable DeDuplication	Yes or No	Data steward and end users Note: A data steward monitors the quality of incoming and outgoing data for an organization.

The values of parameters at the user level override the values at the object manager level. In turn, the values at the in the object manager level override the settings specified at the enterprise level. This allows administrators to enable data matching or cleansing for one application but not another and allows users to disable data matching or cleansing for their own login even if data matching or cleansing is enabled for their application.

However, data matching or data cleansing cannot be enabled for a user login if data matching or data cleansing are not enabled at the object manager level.

Even if data cleansing and data matching are enabled, cleansing and matching are only triggered for business components as defined in Siebel Tools and in the Data Quality - Administration views.

For more information, see the following topics:

Enabling Data Quality at the Enterprise Level

Before performing any batch data matching or date cleansing tasks, you must first enable the Data Quality Manager server component for the enterprise. Data Quality Manager is the preconfigured component in the Data Quality component group that you use to run your data quality tasks.

There are three possible ways to enable the Data Quality component group:

When you install a Siebel Server, you can specify the Data Quality component group in the list of component groups that you want to enable.
If you do not choose to enable the Data Quality component group during installation, you can enable it later using the Siebel Server Manager. For more information about enabling component groups using the Siebel Server Manager, see Siebel System Administration Guide.
You can enable the Data Quality component group from your Siebel application, as described in this topic.

Note: If you use Siebel Server Manager (srvrmgr) to list component groups, groups that were enabled from the Siebel application are not listed.

The enterprise parameters DeDuplication Data Type and Data Cleansing Type specify respectively the type of software used for data matching and data cleansing. These parameters are automatically set according to what you choose for data matching at Siebel Server installation time. However, it is recommended that you check the values for these parameters to make sure they are appropriately set for the enterprise.

Use the following procedures to enable and disable Data Quality Manager and to configure the enterprise parameter settings for data matching and data cleansing.

To enable data quality at the enterprise level

Log in to the Siebel application with administrator responsibilities.
Navigate to the Administration - Server Configuration screen, then Enterprises view.
Click the Component Groups view tab.
In the Component Groups list, select Data Quality, and then click the Enable button.
Data quality is now enabled at the enterprise level for data matching and data cleansing.
Restart the Siebel Server.

Use the following procedure to configure data matching and data cleansing settings at the enterprise level.

Configuring Data Matching and Data Cleansing Settings at the Enterprise Level

Use the following task to configure data matching and data cleansing settings at the enterprise level.

To configure data matching and data cleansing settings at the enterprise level

Log in to the Siebel application with administrator responsibilities.
Navigate to the Administration - Server Configuration screen, then Enterprises view.
Click the Parameters view tab.
In the Parameter field in the Enterprise Parameters list, query and review the settings for each of the following parameters:
- DeDuplication Data Type
- Data Cleansing Type
The Value field can be set as follows:
- CHANGE_ME. Indicates that you chose None when you installed the Siebel Server.
- name of third-party server. Indicates the name of the third-party server that is being used for data matching and (or) data cleansing.
  For example:
  - ISS. Indicates that Oracle Data Quality Matching Server is used for data matching.
  - ASM. Indicates that Oracle Data Quality Address Validation Server is used for data cleansing.
If necessary, enter any corrections in the Value field.
The value you choose for Data Cleansing Type can differ from the value you choose for DeDuplication Data Type, provided that you have the appropriate vendor software available.

Note: The values set in the Value field in the Enterprise Parameters list also appear in the Value fields for the corresponding parameters in the Component Parameters and Server Parameters views.
If you change an enterprise parameter in Step 4 (or if you change any value of a server component such as Data Quality Manager), restart the server component so that the new settings take effect.
For more information about restarting server components, see Siebel System Administration Guide.

Specifying Data Quality Settings

Before performing any data matching or cleansing tasks, you must make sure that the appropriate data quality setting parameters are specified. Use the following procedure to specify the data quality settings for the enterprise.

To specify data quality settings

Navigate to the Administration - Data Quality screen, then the Data Quality Settings view.
In the Value field for each parameter, apply the appropriate settings.
The parameters applicable to all data quality products are described in the following table.
Log out of the application and log back in for the changes to take effect.

Note: You do not have to restart the Siebel Server.

The following table describes the parameters that apply to all data quality products.

Table Data Quality Settings Applicable to Data Quality Products

Parameter	Description
Enable DataCleansing	Determines whether real-time data cleansing is enabled for the Siebel Server the administrator is currently logged into. The default value is Yes. Other values you set for data quality can override this setting. For more information about this, see Levels of Enabling and Disabling Data Cleansing and Data Matching.
Enable DeDuplication	Determines whether real-time data matching is enabled for the Siebel Server the administrator is currently logged into. The default value is Yes. Other values you set for data quality can override this setting. For more information about this, see Levels of Enabling and Disabling Data Cleansing and Data Matching.
Force User Dedupe - Account	Determines whether duplicate records are displayed in a window when a user saves a new account record. The user can then merge duplicates. If set to No, duplicates are not displayed in a window, but the user can merge duplicates in the Duplicate Accounts view. The default value is Yes. For more information about window configuration, see Configuring the Windows Displayed in Real-Time Data Matching.
Force User DeDupe - Contact	Determines whether duplicate records are displayed in a window when a user saves a new contact record. The user can then merge duplicates. If set to No, duplicates are not displayed in a window, but the user can merge duplicates in the Duplicate Contacts view. The default value is Yes. For more information about window configuration, see Configuring the Windows Displayed in Real-Time Data Matching.
Force User DeDupe - List Mgmt	Determines whether duplicate records are displayed in a window when a user saves a new prospect record. The user can then merge duplicates. If set to No, duplicates are not displayed in a window, but the user can merge duplicates in the Duplicate Prospects view. The default value is Yes. For more information about window configuration, see Configuring the Windows Displayed in Real-Time Data Matching.
Fuzzy Query Enabled	Determines whether fuzzy query, an advanced search feature, is enabled. The default value is no. For more information about fuzzy query, see Enabling and Disabling Fuzzy Query.
Fuzzy Query - Max Returned	Specifies the maximum number of records returned when a fuzzy query is performed. The default value is 500. For more information about fuzzy query, see Enabling and Disabling Fuzzy Query.
Account Match Against Note: This parameter applies to the Oracle Data Quality Matching Server only.	If set to Primary Address, then only the primary address associated with an account is considered for deduplication. If set to All Address, then all addresses associated with an account are considered for deduplication. The default value is Primary Address.
Contact Match Against Note: This parameter applies to the Oracle Data Quality Matching Server only.	If set to Primary Address, then only the primary address associated with a contact is considered for deduplication. If set to All Address, then all addresses associated with a contact are considered for deduplication. The default value is Primary Address.
Match Threshold	Specifies a threshold above which any record with a match score is considered a match. Higher scores indicate closer matches. A perfect match is equal to 100. Possible values are: 50-100.
Enable DQ Multiple Addresses Note: This parameter applies to the Oracle Data Quality Matching Server only.	Set to Yes if configuring deduplication against multiple addresses. The default value is No. For more information, see Configuring Deduplication Against Multiple Addresses.
Enable DQ Multiple Languages Note: This parameter applies to the Oracle Data Quality Matching Server only.	Set to Yes if configuring multiple language support for data matching. The default value is No. For more information, see Configuring Multiple Language Support for Data Matching.
Enable DQ Sync Note: This parameter applies to the Oracle Data Quality Matching Server only.	Set to Yes if configuring data synchronization between the Siebel application and the Oracle Data Quality Matching Server using the new synchronizer process. The new synchronizer process uses the DQ Sync Services business service to insert synchronized messages directly into the Oracle Data Quality Matching Server (Informatica Identity Resolution) NSA table, and is triggered by the DQ Sync* action sets in Siebel CRM. The default value is Yes. For the new synchronizer process to work, you must also: Configure the EBC table. For more information, see Process of Configuring Data Synchronization Between Siebel and Oracle Data Quality Matching Server. Activate the DQ Sync Action Sets. Note: The old synchronizer uses workflows to send XML messages to the Oracle Data Quality Matching Server XS Server (XML Sync Server), and is triggered by the ISSSYNC action sets in Siebel CRM.
Sort Match Web Service Results	Set to Yes to enable the sort filter for the results in the Data Quality Web Services. The default is No.

Disabling Data Matching and Cleansing Without Restarting the Siebel Server

If you enabled data matching or cleansing from the Administration - Server Configuration screen, you can disable one or both from the Data Quality Settings view without restarting the Siebel Server.

After you disable data matching or data cleansing, log out and then log in to the application again for the new settings to take effect. The settings apply to all the object managers in your Siebel Server, whether or not they have been enabled in the Administration - Server Configuration screen.

Enabling Data Quality at the Object Manager Level

In real-time mode, data quality is called when a new or modified record is saved. Real-time data matching and cleansing is supported only for employee-facing applications. By specifying data matching and cleansing parameters at the object manager level in the Siebel application, you can enable data matching or cleansing for one application and disable it for another application. However, you cannot enable data matching for both the Matching Server and the Universal Connector for the same application.

To enable data matching and data cleansing for real-time processing at the object manager level, you must enable certain parameters for the object manager that the application uses. You enable real-time processing for data matching and cleansing using either the graphical user interface (GUI) of the Siebel application or the command-line interface of the Siebel Server Manager.

Note: The command-line interface of the Siebel Server Manager is the srvrmgr program. For more information about using the command-line interface, see Siebel System Administration Guide.

Use the following procedures to enable data matching and cleansing for real-time processing:

These procedures require that data quality is already enabled at the enterprise level. For information about enabling data quality at the enterprise level, see Enabling Data Quality at the Enterprise Level.

Enabling Data Quality Using the GUI

To enable data quality at the object manager level using the GUI, complete the steps in the following procedure.

To enable data quality at the object manager level using the GUI

Log in to the Siebel application with administrator responsibilities.
Navigate to the Administration - Server Configuration screen, then the Servers view.
In the Components list, select an object manager where end users enter and modify customer data.
For example, select the Call Center Object Manager (ENU) if you want to enable or disable real-time data matching or cleansing for that object manager.
Click the Parameters subview tab.

In the Parameters field in the Component Parameters list, apply the appropriate settings to the parameters listed in the following table to enable or disable data matching or cleansing.

Field	Description
Data Cleansing Enable Flag	Indicates whether real-time data cleansing is enabled for a specific object manager, such as Call Center Object Manager (ENU). This parameter allows you to set different data cleansing values in different object managers. By default, all values for this parameter are set to False.
DeDuplication Enable Flag	Indicates whether real-time data matching is enabled for a specific object manager, such as Call Center Object Manager (ENU). This parameter allows you to set different data matching values in different object managers. By default, all values for this parameter are set to False.
Data Cleansing Type	Indicates the third-party vendor software that is used for data cleansing.
DeDuplication Data Type	Indicates the third-party vendor software that is used for data matching.

Note: The settings at this object manager level override the enterprise-level settings.

After the component parameters are set, restart the object manager either by using srvrmgr or by completing the following sub-steps:
1. Navigate to the Administration - Server Management screen, then the Servers view.
2. Click the Components Groups view tab (if not already active).
3. In the Servers list (upper applet), select the appropriate Siebel Server (if you have more than one in your enterprise).
4. In the Components Groups list (middle applet), select the component of your object manager, and use the Startup and Shutdown buttons to restart the component.

For information about restarting server components, see Siebel System Administration Guide.

Enabling Data Quality Using the Command-Line Interface

Use the following procedure to enable data quality at the object manager level using the Siebel Server Manager command-line interface.

To enable data quality at the object manager level using the Siebel Server Manager command-line interface

Start the Siebel Server Manager command-line interface (srvrmgr) using the user name and password of a Siebel application administrator account such as SADMIN. For more information, see Siebel System Administration Guide.

Note: You must have Siebel CRM administrator responsibility to start or run Siebel Server tasks using the Siebel Server Manager command-line interface.
Execute commands similar to the following examples to enable or disable data matching or data cleansing.
The examples are for the Call Center English application (where SSCObjmgr_enu is the alias name of the English Call Center object manager of the Call Center application.) Use the appropriate alias_name for the application component name to which you want the change applied:
- To enable data matching if you are using Universal Connector third-party software:
```
change parameter DedDupTypeEnable=True, DeDupTypeType=ISS for component 
SCCObjMgr_enu
```
- To enable data cleansing if you are using Universal Connector third-party software:
```
change parameter DataCleansingEnable=True, DataCleansingType=ASM for component 
SCCObjMgr_enu
```

To disable data matching or data cleansing, execute commands like these examples with the DeDupTypeEnable or DataCleansingEnable parameters set to False. For more information about using the command-line interface, see Siebel System Administration Guide.

Enabling Data Quality at the User Level

Users can disable data matching, data cleansing, or fuzzy query for their own logins by setting user preferences even if these features are enabled for their application. The values in the User Preferences view are applicable to real-time processing.

The User Profile screen, Data Quality view displays many of the same options that are set in the Administration - Data Quality Settings screen. However, a choice to disable a feature in the user preference settings takes priority (for the current user) over a choice to enable it in the Data Quality Settings view. The reverse is not true: if a feature is disabled in the Data Quality Settings view, you cannot override that disabling by enabling the feature in the user preferences settings.

Use the following procedure to set user preferences and enable data quality at the user level.

To enable data quality at the user level

Log in to your Siebel application as the user.
Navigate to the User Profile screen, then the Data Quality view.

In the Data Quality form, set the parameters for that user.

The following table describes the fields.

Field	Description
Enable Data Cleansing	Select Yes to enable data cleansing for the current user. Otherwise, select No to disable data cleansing.
Enable DeDuplication	Select Yes to enable data matching for the current user. Otherwise select No to disable data matching.
Fuzzy Query Enabled	Select Yes to use a fuzzy query for the current user. Select No to disable fuzzy queries for the current user. Fuzzy query only works if certain conditions are met; see Enabling and Disabling Fuzzy Query.
Fuzzy Query - Max Matches Returned	Specify the maximum number of query result records you want data quality to return to you. Valid values are 10 to 500. The default value is 100.
Match Threshold	Applicable for Universal Connector. Select a threshold above which any record with a match score is considered a match. Higher scores indicate closer matches (a perfect match is equal to 100). Possible values are: 50-100. If no threshold value is supplied in any of the data quality settings, the default value of 50 is used by the Siebel application.

Log out of the application and log back in as the user to initialize the new settings.
Do not to restart the Siebel Server.

Disabling Data Cleansing for Specific Records

You can disable data cleansing for accounts, contacts, and prospects on a record-by-record basis for both real-time and batch mode processing.

To disable data cleansing for a record

Drill down on the record for which you want to disable cleansing, and then click the More Info view tab.
In the More Info form, select the Disable Cleansing check box.

Note: The Disable Cleansing check box is cleared (that is, cleansing enabled) by default for new records.

Enabling and Disabling Fuzzy Query

Data Quality provides an advanced query feature, known as fuzzy query, that makes searching more intuitive and effective. For general information about fuzzy query functionality, see Fuzzy Query.

When all of the following conditions are satisfied, the Siebel application uses fuzzy query mode automatically, regardless of which data quality product you are using. However, if any of the conditions are not satisfied, the Siebel application uses the standard query mode:

Data matching must be enabled in the Administration - Data Quality Settings view, see Specifying Data Quality Settings.
Data matching must not be disabled for the current user in the User Preferences - Data Quality view, see Enabling Data Quality at the User Level.
Fuzzy query must be enabled in the Administration - Data Quality Settings view; Fuzzy Query Enabled must be set to Yes.
Fuzzy query must be enabled for the current user in the User Preferences - Data Quality view; Fuzzy Query Enabled must be set to Yes.
The query must not use wildcards.
The query must specify values in fields designated as fuzzy query mandatory fields. For information about identifying the mandatory fields, see Identifying Mandatory Fields for Fuzzy Query.
The query must leave optional fields blank.

The following procedures describe how to enable and disable fuzzy query in the Data Quality Settings. If wildcards (*) or quotation marks (") are used in a fuzzy query, then that fuzzy query will not be effective. Also, if mandatory fuzzy query fields are missing, then fuzzy query is disabled for that particular query.

Enabling Fuzzy Query

Use the following procedure to enable fuzzy query.

To enable fuzzy query

Navigate to the Administration - Data Quality screen, then the Data Quality Settings view.
Click New to create a new record:
1. In the Name field, choose Fuzzy Query Enabled.
2. In the Value field, choose Yes.
(Optional) If you want to set a maximum number of returned records, click New to create a new record:
1. In the Name field, choose Fuzzy Query - Max Returned.
2. In the Value field, enter a number from 10 to 500.

Disabling Fuzzy Query

Use the following procedure to disable fuzzy query.

To disable fuzzy query

Navigate to the Administration - Data Quality screen, then the Data Quality Settings view.
In the Data Quality Settings list, select Fuzzy Query Enabled, and in the Value field, choose No.

Identifying Mandatory Fields for Fuzzy Query

You might want to provide users with information about mandatory fields (query fields that must include values for the Siebel application to use fuzzy query mode). The following table shows the preconfigured mandatory fields that Oracle provides.

If you want to identify the current mandatory fields for your own Siebel CRM implementation, use the procedure that follows.

Table Mandatory Fields for Fuzzy Query, by Business Component

Business Component	Mandatory Fields for Fuzzy Query
Account	Name
Contact	First Name, Last Name
List Mgmt Prospective Contact	First Name, Last Name

To identify fields that are mandatory for fuzzy query

Login to Web Tools.
In the Object Explorer, expand Business Component and then select the business component of interest in the Business Components pane.
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). If this is necessary, you must repeat Step 2 of this procedure.
In the Business Component User Properties pane, select Fuzzy Query Mandatory Fields, and inspect the field names listed in the Value column.
Repeat Step 2 through Step 4 for other business components, as needed.

4Enabling and Disabling Data Matching and Data Cleansing