6Configuring Data Quality

Configuring Data Quality

This chapter describes the data quality configuration that you can perform for Siebel CRM and Oracle Customer Hub. It covers the following topics:

• Data Quality Configuration Overview

• Process of Configuring New Data Quality Connectors

• Configuring Vendor Parameters

• Mapping of Vendor Fields to Business Component Fields

• Example Configurations for Data Quality

• Configuring a New Field for Real-Time Data Matching

• Incremental Data Load

• Process of Configuring Data Synchronization Between Siebel and Oracle Data Quality Matching Server

• Configuring Deduplication Against Multiple Addresses

• Configuring Multiple Language Support for Data Matching

• Configuring Multiple Mode Support for Data Matching

• Configuring the Windows Displayed in Real-Time Data Matching

• Configuring the Mandatory Fields for Fuzzy Query

• Data Quality User Properties

Note: You must be familiar with Siebel Tools before performing some of the data quality configuration tasks. For more information about Siebel Tools, see Using Siebel Tools and Configuring Siebel Business Applications.

Data Quality Configuration Overview

The following table summarizes the data quality configuration that you can perform for Siebel CRM and Oracle Customer Hub.

Type	Configuration	See...
Generic data quality configuration for all data quality products	Configure new connectors for data matching and data cleansing for the Universal Connector	Process of Configuring New Data Quality Connectors
	Configure vendor parameters. You can configure the parameters for each of the software vendors.	Configuring Vendor Parameters
	Configure field mappings for business components. You can change or add field mappings.	Mapping of Vendor Fields to Business Component Fields
	Configure the windows displayed in real-time data matching	Configuring the Windows Displayed in Real-Time Data Matching
	Configure the mandatory fields for fuzzy search.	Configuring the Mandatory Fields for Fuzzy Query
Oracle Data Quality Matching Server Configuration	Data Matching	Configuring Data Quality for Oracle Data Quality Matching Server
		Configuring a New Field for Real-Time Data Matching
		Incremental Data Load
Oracle Data Quality Address Validation Server Configuration	Data Cleansing	Configuring Siebel CRM for the Oracle Data Quality Address Validation Server

Process of Configuring New Data Quality Connectors

You can define your own connectors for data matching and data cleansing for the Universal Connector. To configure new data quality connectors, perform the following tasks:

1. Registering New Data Quality Connectors

2. Configuring Business Components and Applets for Data Matching and Data Cleansing

Note: These processes do not cover vendor-specific configuration. You must work with Oracle-certified alliance partners to enhance data quality features for your applications.

Registering New Data Quality Connectors

Data Quality connector definitions are configured in the Third Party Administration view. You can specify one external application for data matching and a different application for data cleansing for the Universal Connector. You do this by setting the correct input values for each external application.

Note: The vendor parameters in the Siebel application are specifically designed to support multiple vendors in the Universal Connector architecture without the need for additional code. The values of these parameters must be provided by third-party vendors. Typically, these values cannot be changed because specific values are required by each software vendor. For more information about the values to use, see the installation documentation provided by your third-party vendor.

The Deduplication and Data Cleansing business services include a generalized adapter that communicates with the external data quality application through a set of dynamic-link library (DLL) or shared library files.

The DLL Name setting in the Third Party Administration view tells the Siebel application how to load the DLL or shared library. The names of the libraries are vendor-specific, but must follow naming conventions as described in Vendor Libraries. The Siebel application loads the libraries from the locations described in Universal Connector Libraries.

Use the following procedure to register a data quality connector. This topic is a step in Process of Configuring New Data Quality Connectors.

To register a data quality connector

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, create a new record and complete the necessary fields, as shown in the following table.

Name	Library Name
The name of the vendor. For a data matching connector, the name must match the value specified in the server parameter DeDuplication Data Type. For a data cleansing connector, the name must match the value specified in the server parameter Data Cleansing Type.	The name of the vendor DLL or shared library.

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 Step 3.
   DeDuplication Results List Applet	The applet that you created in Step 4.

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

Configuring Vendor Parameters

For each of the third-party software vendors that data quality uses for data cleansing or data matching, you can configure the vendor parameters that the Siebel application passes to the vendor software. You configure the vendor parameters in the Administration - Data Quality screen, Third Party Administration view, which also contains the DLL or shared library name for each vendor.

There are preconfigured vendor parameters for the Universal Connector with Oracle Data Quality Matching Server and Oracle Data Quality Address Validation Server as examples.

To configure vendor parameters

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, select the record for the required vendor.

3. Click the Vendor Parameters view tab.

4. In the Vendor Parameters List, create new records as required, or configure the values of existing vendor parameters.

Related Topic

Examples of Parameter and Field Mapping Values for Universal Connector

Mapping of Vendor Fields to Business Component Fields

For each vendor who supports data cleansing or data matching, there are field mappings that specify:

• The fields that are used in data cleansing and data matching

• The mapping between the Siebel application field names and the corresponding vendor field names.

There are mappings for each supported business component and data quality operation (DeDuplication and Data Cleansing). There are preconfigured field mappings for the Oracle Data Quality Matching Server Connector, see Preconfigured Field Mappings for Oracle Data Quality Matching Server.

You can configure the field mappings for a business component to include new fields or modify them to map to different fields. There might also be additional configuration required for particular third-party software.

Note: You must contact the specific vendor for the list of fields they support for data cleansing and data matching and to understand the effect of changing field mappings.

Related Topics

Mapping Data Matching Vendor Fields to Siebel Business Components

Adding a Field Mapping for Data Matching

Mapping Data Cleansing Vendor Fields to Siebel Business Component Fields

Mapping Data Matching Vendor Fields to Siebel Business Components

This topic explains how to map data matching vendor fields to Siebel business component fields.

To map a data matching vendor field to a Siebel business component field

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, select the record for the required vendor.

3. Click the BC Vendor Field Mapping view tab.

4. In the BC Operation list, select the record for the required business component and the DeDuplication operation. The field mappings are displayed in the Field Mapping list.

5. In the Field Mapping list enter the required values for Business Component Field and Mapped Field.

Adding a Field Mapping for Data Matching

In addition to the preconfigured fields that are used in data matching, you can configure your data quality implementation to inspect certain additional fields during data matching, such as a date of birth field for Contacts, or a D-U-N-S number field for Accounts.

For the Universal Connector, if the key token expression changes, you must regenerate match keys. Therefore, if you are adding a new field and the new field is added to the token expression, you must generate the match keys.

The following procedure describes how to add a field mapping.

To add a field mapping for data matching

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, select the record for the required vendor.

3. Click the BC Vendor Field Mapping view tab.

4. In the BC Operation list, select the record for the required business component and operation.

   • For example, to include a date of birth as a matching criterion, select the record for Contact and DeDuplication.

   • For example, to include a D-U-N-S number as a matching criterion, select the record for Account and DeDuplication.

   The field mappings are displayed in the Field Mapping list.

5. In the Field Mapping list, create a new record and complete the necessary fields as in the example shown in the following table.

   Business Component Field	Mapped Field
   Birth Date	Contact.Birth Date
   DUNS Number	Account.DUNS Number

6. If required, modify the corresponding real-time and batch mode data flows to incorporate the new field so that data quality considers the new field during data matching comparisons.

Mapping Data Cleansing Vendor Fields to Siebel Business Component Fields

Data cleansing is triggered when a record is saved after a field that is defined as an active data cleansing field is updated.

Default settings are preconfigured for the Account, Contact, Prospect, and Business Address business components to support integration with Oracle Data Quality Address Validation Server, but you can configure the mappings to your requirements or to support integration to other vendors.

Note: For Siebel Industry Applications, the CUT Address business component is enabled for data cleansing rather than the Business Address business component.

For example the following are active data cleansing fields for the Contact business component:

• Last Name

• First Name

• Middle Name

• Job Title

Tip: Only fields that are preconfigured as data cleansing fields in the vendor properties trigger real-time data cleansing when they are modified.

To map a data cleansing vendor field to a Siebel business component field

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.

2. In the Vendor List, select the record for the required vendor.

3. Click the BC Vendor Field Mapping view tab.

4. In the BC Operation list, select the record for the required business component and Data Cleansing operation.

   The field mappings are displayed in the Field Mapping list.

5. In the Field Mapping list enter the required values for Business Component Field and Mapped Field.

Example Configurations for Data Quality

The following table lists some example configurations for the different data quality products.

Data Quality Product	See...
Oracle Data Quality Matching Server: Data Matching	Configuring Data Quality for Oracle Data Quality Matching Server
Oracle Data Quality Matching Server: Data Matching	Configuring a New Field for Real-Time Data Matching
Oracle Data Quality Address Validation Server: Data Cleansing	Configuring Siebel CRM for the Oracle Data Quality Address Validation Server

Configuring Data Quality for Oracle Data Quality Matching Server

Configuring data quality for Oracle Data Quality Matching Server involves enabling deduplication on all object managers, specifying data quality settings, and setting up preconfigured vendor parameters and field mapping values for Oracle Data Quality Matching Server.

Use the following procedure to set up real-time deduplication for Oracle Data Quality Matching Server. This task is a step in Process of Installing the Oracle Data Quality Matching Server.

To configure data quality for Oracle Data Quality Matching Server

1. Enable data quality at the object manager level as described in Enabling Data Quality at the Object Manager Level.

2. Change the DeDuplication Data Type setting to ISS on all object managers as described in Enabling Data Quality at the Enterprise Level.

   This parameter can be set at the Enterprise, Siebel Server, or component level. For example, srvrmgr commands similar to the following can be used to set the parameters:

   Change param DeDupTypeType =ISS 
   Change param DeDupTypeEnable =True, DeDupTypeType =ISS for comp DQMgr 
   Change param DeDupTypeEnable =True, DeDupTypeType =ISS for comp SCCObjMgr_enu 
   Change param DeDupTypeEnable =True, DeDupTypeType =ISS for comp UCMObjMgr_enu 
   

   Note: You must change the DeDuplication Data Type setting to ISS on all object managers for deduplication with Oracle Data Quality Matching Server to be active.

3. Set data quality settings as described in Specifying Data Quality Settings.

   Make sure that the following parameters are set to Yes:

   Enable DeDuplication
   Force User DeDupe - Account
   Force User DeDupe - Contact
   Force User DeDupe - List Mgmt
   

4. Verify that the preconfigured vendor parameter and field mapping values are set up as listed in Universal Connector Parameter and Field Mapping Values for Oracle Data Quality Matching Server.

5. Modify the ssadq_cfg.xml file as described in Modifying Configuration Parameters for Oracle Data Quality Matching Server.

For more information about Siebel Server configuration and management, see Siebel System Administration Guide.

Configuring Siebel CRM for the Oracle Data Quality Address Validation Server

Configuring Siebel CRM for the Oracle Data Quality Address Validation Server involves enabling cleansing on all object managers, specifying data cleansing settings, and setting up preconfigured vendor parameters and field mapping values for the Oracle Data Quality Address Validation Server.

Use the following procedure to configure Siebel CRM for the Oracle Data Quality Address Validation Server. This task is a step in Process of Installing the Oracle Data Quality Address Validation Server.

To configure Siebel CRM for the Oracle Data Quality Address Validation Server

1. Open the uagent.cfg file in a text editor, and modify the [DataCleansing] section of the file to include the following:

   [DataCleansing]
   Enable=TRUE
   Type=ASM
   

   The uagent.cfg file is located in the Siebel/bin/w32u/enu directory.

2. In your Siebel application, enable data cleansing to use the Oracle Data Quality Address Validation Server as described in Enabling and Disabling Data Matching and Data Cleansing.

   For example, enable data cleansing at the object manager level, enterprise level, user level, and set the data quality settings (for data cleansing). Note that the Data Cleansing Type parameter must be set to ASM as shown in the following table.

   Parameter Name	Value
   Data Cleansing Enable Flag	True
   Data Cleansing Type	ASM

   1. Configure the ASM vendor applet (Oracle Data Quality Address Validation Server vendor applet) as shown in the following table by navigating to the Administration - Data Quality screen, then the Third Party Administration view.

      Vendor Applet Parameter Name	Vendor Applet Parameter Value
      Name	ASM
      DLL Name	ssadqasm

   2. Verify that the preconfigured ASM vendor parameter and field mapping values are set up as listed in Universal Connector Parameter and Field Mapping Values for Oracle Data Quality Address Validation Server.

   3. For better control over the data returned by ASM, add the following vendor parameters for Oracle Data Quality Address Validation Server:

      Vendor Parameter Name	Description
      ASM Country Database Return Code	Specifies the ASM return codes under this vendor parameter for which any error messages returned are ignored and processing continues if the country database is not found. List return codes, separated by a comma. For example, if the customer is using Informatica Address Doctor Version 5 and the country database is not licensed, then specify the vendor parameter as follows: ASM Country Database Return Code: 25,26
      ASM High Deliverability Return Code	Specifies the ASM return codes under this vendor parameter for which addresses returned by the ASM Engine override the input address. If the ASM return code matches a return code defined within this vendor parameter, then the validated address sent by the ASM Engine is cleansed. In all other cases, the input address is retained. List return codes, separated by a comma. For example: ASM High Deliverability Return Code: 0,1,2,3,4,5,6,7,8 This vendor parameter applies only if the DQ Cleanse High Deliverable Address vendor parameter is set to Yes.

3. Modify the ssadq_cfgasm.xml file as described in Modifying Configuration Parameters for Oracle Data Quality Address Validation Server.

Configuring a New Field for Real-Time Data Matching

When using the Oracle Data Quality Matching Server for data matching, there are a number of steps involved in configuring a new field for real-time data matching. Use the following procedure to configure a new field for data matching. This procedure shows how to add a new field called Position when matching Contacts.

To configure a new field for real-time data matching

1. In your Siebel application, navigate to the Administration - Data Quality screen, then the Third Party Administration view, and add the vendor field mappings for the new business components. For example:

   1. Select the Vendor shown in the following table:

      Vendor Name	DLL Name
      ISS	ssadqsea

   2. Select the business component operation shown in the following table:

      Business Component Name	Operation
      Contact	DeDuplication

   3. Add the field mapping shown in the following table:

      Business Component Field	Mapped Field
      Position	MyPosition

2. Configure the integration object.

   1. If using the old synchronizer, modify the Identity Search Server synchronization Integration Object by adding the new fields to it. In this example, you must modify the ISS_Contact to add the new Integration Component Field as shown in the following table:

      Name	Data Type	Length	External Name	XML Tag
      Position	DTYPE_TEXT	50	Position	MyPosition

      Note: For a Contact, you must modify the ISS_Contact integration object. For an Account, you must modify the ISS_Account integration object. For a Prospect, you must modify the ISS_List_Mgmt_Prospective_Contact integration object.

   2. If using the new synchronizer, then do the following:

      • Add the new field to the Synchronize Integration Object. In this case, 'SyncContact' IO. For the contact address field, add it to the 'Contact_INS Personal Address' Integration Component.

      • Add the new field to the 'DQ Sync Services' user property. In this case, 'Contact_DeDupFlds'. For the contact address field, add it to the 'Contact_INS Personal Address_DeDupFlds' user property.

      • Add the new field length to one or both of the following 'DQ Sync Services' user properties:

        'Contact_ExtLen' 
        'Contact_INS Personal Address_ExtLen'
        

        Note: It is mandatory that you maintain the same sequence that is detailed in the sdf file. Also make sure that the address fields are grouped together at the end of the sdf file.

      • Enter the new record length into the 'Contact Record Length' user property. This user property holds a total of all the field lengths in 'Contact_ExtLen' and 'Contact_INS Personal Address_ExtLen'.

        Note: ISSDataSrc must be added to the OM - Named Data Source component parameter for the UCM object manager and EAI object manager components.

3. Modify the SDF file (SiebelDQ.sdf):

   1. Add the new fields to the IDT table in IIR:

      In the following example for the old synchronizer, you must add the new Position field to the IDT_Contact. For example:

      create_idt
                IDT_CONTACT
      SOURCED_FROM      FLAT_FILE
                          BirthDate                    w(60),
                          CellularPhone                w(60),
                          EmailAddress                 w(60),
                          NAME                         w(100),
                          HomePhone                    w(60),
                          MiddleName                   w(100),
                          Account                      w(100),
                          City                         w(60),
                          Country                      w(20),
                          PrimaryPostalCode            w(20),
                          State                        w(20),
                          StreetAddress                w(100),
                          RowId                        w(30)
                          SocialSecurityNumber         w(60)
                          MyPosition                   w(60)
                          WorkPhone                    w(60)
      SYNC_REPLACE_DUPLICATE_PK
      TXN-SOURCE NSA
      ;
      

      In the following example for the new synchronizer, you must add the new Position field to the IDT_Contact.

      create_idt IDT_CONTACT
      sourced_from odb:15:ssa_src/ssa_src@ISS_DSN
      INIT_LOAD_ALL_CONTACTS.BIRTHDATE            BirthDate             V(60),
      INIT_LOAD_ALL_CONTACTS.CELLULARPHONE        CellularPhone         V(60),
      INIT_LOAD_ALL_CONTACTS.EMAILADDRESS         EmailAddress          V(60),
      INIT_LOAD_ALL_CONTACTS.NAME                 NAME                  V(100),
      INIT_LOAD_ALL_CONTACTS.HOMEPHONE            HomePhone             V(60),
      INIT_LOAD_ALL_CONTACTS.MIDDLE_NAME          MiddleName            V(100),
      INIT_LOAD_ALL_CONTACTS.ACCOUNT              Account               V(100),
      INIT_LOAD_ALL_CONTACTS.CONTACT_ID  (pk1)    RowId                 C(30),
      INIT_LOAD_ALL_CONTACTS.SOCIALSECURITYNUMBER SocialSecurityNumber  V(60),
      INIT_LOAD_ALL_CONTACTS.MYPOSITION           MyPosition            V(60),
      INIT_LOAD_ALL_CONTACTS.WORKPHONE            WorkPhone             V(60),
      INIT_LOAD_ALL_CONTACTS.CITY                 City                  V(60),
      INIT_LOAD_ALL_CONTACTS.COUNTRY              Country               V(20),
      INIT_LOAD_ALL_CONTACTS.POSTAL_CODE          PrimaryPostalCode     V(20),
      INIT_LOAD_ALL_CONTACTS.STATE                State                 V(20),
      INIT_LOAD_ALL_CONTACTS.STREETADDRESS        StreetAddress         V(100),
      INIT_LOAD_ALL_CONTACTS.ADDRESS_ID  (pk2)    ContactAddressID      C(60)
      SYNC REPLACE_DUPLICATE_PK 
      TXN-SOURCE NSA
      ;
      

   2. Modify SCORE-LOGIC in the IIR search definition:

      A set of field types are provided that are supported by Match Purpose. For Contact Match Purpose, the required and optional field types are shown in the following table:

      Field	Required
      Person_Name	Yes
      Organization_Name	Yes
      Address_Part1	Yes
      Address_Part2	No
      Posal_Area	No
      Telephone_Number	No
      ID	No
      Date	No
      Attribute1	No
      Attribute2	No

      If you want the new field to contribute to the match score, add it to the SCORE-LOGIC section in IIR search definition. For example:

      search-definition
      ==================
      NAME=           "search-person-name"
      IDX=            IDX_CONTACT_NAME
      COMMENT=        "Use this to search and score on person"
      KEY-LOGIC=      SSA,
                      System(default),
                      Population(usa),
                      Controls("FIELD=Person_Name 
                                SEARCH_LEVEL=Typical UNICODE_ENCODING=6",
                      Field(Name)
      SCORE-LOGIC=    SSA,
                      System(default),
                      Population(usa),
                      Controls("Purpose=Person_Name 
                                MATCH_LEVEL=Typical UNICODE_ENCODING=6",
                      Matching-Fields
      ("Name:Person_Name,StreetAddress:Address_Part1,City:Address_part2,State:Attr
      ibute1,PrimaryPostalCode:Postal_area,MyPosition:Attribute2")
      

4. Delete the existing system in IIR, and then create a new system using the new SiebelDQ.sdf file.

5. Reload the IIR system as described in Initial Loading of Siebel Data into Oracle Data Quality Matching Server Tables.

Incremental Data Load

When loading Siebel application data into Informatica Identity Resolution tables, rather than generating keys for the entire data set in one go, the incremental data load feature provides the functionality to divide the total load into smaller batches of configurable size and load them incrementally. Use the following procedure to configure a new field for data matching.

To incrementally load Siebel application data into Informatica Identity Resolution tables

1. Start the Informatica Identity Resolution server in Configure Mode.

2. Start the Informatica Identity Resolution Console client in Admin Mode.

3. Select System (if already created), otherwise create a new system using the required sdf file.

4. Run the IDS_IDT_<ENTITY TO BE LOADED>_STG.sql script to take a snapshot of records in the Siebel application.

   For example, execute the following script from the SQL command line prompt for account initial load using your appropriate login credentials:

   IDS_IDT_ACCOUNT_STG.sql
   

   The following sample SQL scripts can be used to capture snapshots of the data:

   • IDS_IDT_ACCOUNT_STG.SQL

   • IDS_IDT_CONTACT_STG.SQL

   • IDS_IDT_PROSPECT_STG.SQL

   For more information about these example scripts, see Sample SQL Scripts.

5. While creating a snapshot using the example scripts listed in the previous step, users are prompted to enter a batch size. Depending on the value entered, the entire snapshot is grouped into batches of the specified batch size.

   For example, run the following SQL script to create the database table to store the current batch number being loaded (this value is usually 1 for the first time):

   IDS_IDT_CURRENT_BATCH.sql 
   

6. Run the IDS_IDT_CURRENT_BATCH_<ENTITY TO BE LOADED>.sql script to create the dynamic view to load the snapshot for the staging table created in the previous step.

   For example, execute the following script from the command line:

   IDS_IDT_CURRENT_BATCH_ACCOUNT.sql
   

   The following sample SQL scripts can be used to create the views to process the records in a given batch:

   • IDS_IDT_CURRENT_BATCH_ACCOUNT.SQL

   • IDS_IDT_CURRENT_BATCH_CONTACT.SQL

   • IDS_IDT_CURRENT_BATCH_PROSPECT.SQL

   For more information about these example scripts, see Sample SQL Scripts.

7. Open the Informatica Identity Resolution client and perform a Load IDT.

   Load the remaining batches of data through the ISS batch Utility. Open a command window and navigate to the directory where the initial scripts for loading have been copied. Execute the initial load process by entering the following command at the command line:

   IDS_IDT_LOAD_ANY_ENTITY.CMD <Entity> <Work Directory> 
   

   For example, execute the following script from the command line for account initial load:

   IDS_IDT_LOAD_ANY_ENTITY.CMD Account c:/initialLoad/logs
   

8. The following files contain the parameters used by the batch load utility; you must update these files to reflect your installation:

   • idt_Account_load.txt

   • idt_Contact_load.txt

   • idt_Prospect_load.txt

   Note: Certain SQL and shell scripts are required to create materialized views and to load data incrementally. Some sample SQL and shell scripts are provided in Sample Configuration and Script Files Depending on customer requirements, you can fine tune these sample files during implementation.

9. Incrementally load the failed batches individually using the following script from the command line:

   IDS_IDT_LOADBATCH_ANY_ENTITY <Entity> <Work Directory> <Batch Number>
   

   For example, execute the following script from the command line to load batch 33 of account:

   IDS_IDT_LOADBATCH_ANY_ENTITY.CMD Account c:/initialLoad/logs 33
   

   Examine the log files and error files to ensure that all batches have successfully loaded. In the case of errors, use the information in the log and error files to determine the root cause for the failure and fix the underlying issue; repeat the load process as necessary.

Process of Configuring Data Synchronization Between Siebel and Oracle Data Quality Matching Server

When configuring data synchronization between the Siebel application and Oracle Data Quality Matching Server, perform the following tasks:

1. Configure the data source, see Configuring the Data Source.

2. Configure the DQ Sync Services Business Service to Use Informatica Identity Resolution 9.01, see Upgrading to Informatica Identity Resolution 9.01 (Step 1).

3. Configuring Object Managers for ISS Data Source.

Configuring the Data Source

Use the following procedure to configure the data source definition (or EBC table) required to synchronize data between the Siebel application and Oracle Data Quality Matching Server. This task is a step in Process of Configuring Data Synchronization Between Siebel and Oracle Data Quality Matching Server.

To configure the data source definition

1. In your Siebel application, navigate to Administration - Server Configuration, Enterprises, and then Profile Configuration view.

2. Copy an existing InfraDatasources named subsystem type.

3. Change the Profile and Alias properties to the Data Source name (ISSDataSrc) configured in Siebel Tools.

4. Update the profile parameters to correspond to the external RDBMS:

   • DSConnectString: This is the data source connect string.

     For the Microsoft SQL Server or the IBM DB2 databases, create an ODBC or equivalent connection and input the name of the connection in the parameter. For an Oracle RDBMS, specify the TNS name associated with the database, and not an ODBC or other entry.

   • DSSSQLStyle: This is the database SQL type.

   • DSDLLName: This is the DLL Name corresponding to the SQL type.

   • DSTableOwner: This is the data source table owner.

   • DSUsername: This is the default user name used for connections (Optional).

   • DSPassword: This is the default password used for connections (Optional).

Configuring Object Managers for ISS Data Source

Use the following procedure to configure object managers for the ISS Data Source. This task is a step in Process of Configuring Data Synchronization Between Siebel and Oracle Data Quality Matching Server.

To configure object managers for ISS Data Source

1. Navigate to Administration - Server Configuration, Enterprises, and then Component Definitions view.

2. Query for the components used with UCM, such as, the following:

   • EAI

   • UCM

   • Data Quality

   • Workflow

3. Select a component, and then select Start Reconfiguration from the main menu.

4. In the lower applet, query for the following parameter: OM - Named Data Source.

   Note: The value for this parameter is similar to the following: ServerDataSrc,GatewayDataSrc.

5. Add a comma after the last data source, then add the ISS data source you created in Configuring the Data Source. The default data source name is ISSDataSrc.

6. Save the record, then select Commit Reconfiguration from the main menu.

7. Repeat Step 3 through Step 6 for all required Object Managers.

   For example, add ISSDataSrc to the following components:

   • EAI Object Manager: OM - Named Data Source name

   • UCM Object Manager: OM - Named Data Source name

   • UCM Batch Manager: OM - Named Data Source name

   • Data Quality Manager

   • Workflow Process Batch Manager

   • Workflow Process Manager

8. Click Synchronize to save the changes to the Gateway Configuration file.

9. Start the Gateway Server and the Siebel Server.

Configuring Deduplication Against Multiple Addresses

When using the Oracle Data Quality Matching Server for data matching, you can configure deduplication against either the primary address or all address entities. When Oracle Data Quality is configured to carry out deduplication against all address entities, this helps identify duplicates between records that have similar non primary addresses. Previous to this release, deduplication was carried out on the primary address only.

• For account, you must use the Account Match Against parameter to specify whether to match using one of the following:

  • All Address

  • Primary Address

• For contact, you must use the Contact Match Against parameter to specify whether to match using one of the following:

  • All Address

  • Primary Address

  Note: You cannot perform deduplication against both All Address and Primary Address. Only one option can be used for deduplication. Choosing to carry out deduplication against all addresses is performance intensive.

  The following procedure describes how to configure deduplication against multiple addresses. Once configured, deduplication against multiple addresses applies in real-time, Universal Customer Master (UCM) or Enterprise Application Integration (EAI) insertion, and batch match processing modes.

To configure deduplication against multiple addresses

1. In your Siebel application, navigate to the Administration - Data Quality screen, then the Third Party Administration view, select the ISS Vendor Name (DLL Name: ssadqsea) and:

   1. In the BC Vendor Field Mapping, configure the business component operation shown in the following table:

      Business Component Field	Operation
      CUT Address	DeDuplication

   2. In the Vendor Parameter, configure the value shown in the following table:

      Name	Value
      CUT Address DeDup Record Type	CUT Address

   3. In the field mapping for CUT Address, enter the values shown in the following table:

      Business Component Field	Mapped Field
      PositionCity	PAccountCity
      Country	PAccountCountry
      Postal Code	PAccountPostalCode
      Row Id	PAccountAddressID
      State	PAccountState
      Street Address	AccountStrAddress

2. In your Siebel application, navigate to the Administration - Data Quality screen, then the Data Quality Settings view, and:

   1. In the Value field for the parameters shown in the following table, specify the appropriate settings.

   2. Log out of the application and log back in for the changes to take effect (you do not have to restart the Siebel Server).

      Parameter	Description
      Account Match Against	Set to one of the following: All Address to consider all addresses associated with an account for deduplication. Primary Address (the default value). If set to Primary Address, then only the primary address associated with an account is considered for deduplication.
      Contact Match Against	Set to one of the following: All Address to consider all addresses associated with a contact for deduplication. Primary Address (default value). If set to Primary Address, then only the primary address associated with a contact is considered for deduplication.
      Enable DQ Multiple Addresses	Set the value of this property Yes.
      Enable DQ Sync	Set the value of this property to Yes.

Configuring Multiple Language Support for Data Matching

When using Oracle Data Quality Matching Server for data matching, you can configure different match rules for different languages. This is useful when you have multiple geographical implementations, and for each implementation, you want to use country-specific match rules.

The solution involves creating multiple systems in Informatica Identity Resolution, where each system corresponds to a specific country or language. Records with a specific language or country are routed to the corresponding system. Because each system is linked to a population, the respective country-specific population rules are used for matching the records. To use this feature, add the Append BC Record Type Field x vendor parameter for UI entry and the Batch Append BC Record Type Field x vendor parameter for batch mode. This vendor parameters is used to specify a field in the BC, which has the country or language information. The BC name can be Account, Contact, or Prospect where x represents the sequence number. For example: Batch Append Account Record Type Field 1.

You must add similar vendor parameters to the Business Service User Property of the ISS System Services business service to represent the IDT number corresponding to the Language. When you create multiple systems in Informatica Identity Resolution, you must specify a unique database number for each system which is used as part of the unique IDT table name in Informatica Identity Resolution. You must enter this same number into the Business Service User Property of the ISS System Services business service for each system. The name of the user property is the same as the name of the system created in Informatica Identity Resolution, and the value of the user property is the database number (for example, see the following figure).

Note: In order to pick up all the records that belong to the same country when running a data quality batch processing task, it is mandatory to define a search specification (to pick up the records belonging to the same country). You can define a search specification by navigating to the Administration - Server Management screen, then the Jobs view.

This feature can be extended as follows:

• Extended to have different match rules depending on the source of data (for example the Siebel application or other application).

• Extended to have different match rules depending on the mode of data entry (for example, real-time or batch processing mode). The procedure in Configuring Multiple Mode Support for Data Matching describes how to configure multiple mode support for data matching when using the Oracle Data Quality Matching Server for data matching.

Use the following procedure to configure multiple language support for data matching when using the Oracle Data Quality Matching Server for data matching.

To configure the Siebel Server for Informatica Identity Resolution multiple language support

1. Create systems on the Informatica Identity Resolution server.

   1. Create separate SDF files for each Country (Population). Informatica provides Standard Populations for most of the countries. Standard Populations are distributed as part of SSA-NAME3 installation and can be copied separately if not selected when installing NAME3 server.

   2. Once all populations are in place, check and note the filename of each population, as this is the same name that is used in the SDF file.

      You can change System Name and System ID within the system definition file as follows:

      system-definition
      *=================
      NAME= siebeldq_XXXX
      ID= sYY
      

      Replace XXXX with Country, and YY with any number between and including 02 and 99. System ID 01 is reserved for Default System. For example, for Japanese population:

      filename : siebeldq_Japan.sdf
      Population files :
      japan.ysp
      

      Changes to SDF file:

      system-definition
      *=================
      NAME= siebeldq_Japan
      ID= s05
      

      System ID 01 is reserved for Default System

      Replace all occurrences of Population(usa) to Population(japan).

      Similar changes are required for each sdf file.

2. Configure the ssadq_cfg.xml configuration file in the <siebsrvr>/SDQConnector folder.

   For example, add the following parameter to the ssadq_cfg.xml file:

   <Parameter>
       <Record_Type>
           <Name>Account_Japan</Name>
           <System>siebeldq_Japan</System>
           <Search>search-org</Search>
           <no_of_sessions>25</no_of_sessions>
       </Record_Type>
   </Parameter>
   

   For a sample ssadq_cfg.xml file, see Sample Configuration and Script Files.

3. In your Siebel application, navigate to the Administration - Data Quality screen, then the Data Quality Settings view and in the value field for the parameter shown in the following table, specify the following setting:

   Parameter Name	Value
   Enable DQ Multiple Languages	Yes

4. Enable multiple language support for real-time flow:

   1. Navigate to Administration - Data Quality screen, then Third Party Administration view in your Siebel application.

   2. Select ISS as the third party vendor.

   3. Add the vendor parameters shown in the following table:

      Name	Value
      Append Account Record Type Field 1	Primary Account Country
      Append Contact Record Type Field 1	Primary Personal Country

5. Enable multiple language support for batch flow:

   1. Navigate to Administration - Data Quality screen, then Third Party Administration view in your Siebel application.

   2. Select ISS as the third-party vendor.

   3. Add the vendor parameters shown in the following table:

      Name	Value
      Batch Append Account Record Type Field 1	Country
      Batch Append Contact Record Type Field 1	Primary Personal Country

6. Add the user property to the ISS System Services business service.

   The user property that you add must correspond to the system name created in Informatica Identity Resolution for the respective country. For example, if the system created for Japan is siebeldq_Japan and the ID is set to 5, then the user property name must be siebeldq_Japan and the value 05, as shown in the following table.

   User Property Name	Value
   siebeldq_Japan	05

Configuring Multiple Mode Support for Data Matching

When using Oracle Data Quality Matching Server for data matching, you can configure different match rules for data matching depending on:

• Mode of operation (real-time or batch mode)

• Source of data (Siebel CRM or other application, such as, eBiz)

As a prerequisite to configuring multiple mode support for data matching, multiple language support for data matching must be configured as described in Configuring Multiple Language Support for Data Matching.

Follow the steps in the following procedure in order to use different match rules on a custom parameter (Source System). Using this procedure, the match rules that apply to data from source system 1 (EBIZ) will be different to the match rules that apply to data from source system 2 (SIEBEL).

To configure multiple mode support for data matching

1. Define separate match rules for each source system.

2. Create systems corresponding to each source system, where each source system points to a separate SDF file. For example:

   • Siebeldq_ebiz

   • Siebeldq_siebel

   The SDF file contains the IDT Layout Definition, Key Definition Logic, Match Fields considered for scoring records, the population to be used, and the Match purpose.

   Note: You must contact Informatica Technical Support in order to fine tune the SDF file.

3. Apply changes to the ssadq_cfg.xml file.

   For each system that you create in IIR, add the following parameters. There must be two entries, one for each source system (EBIZ and SIEBEL).

       <Record_Type>
           <Name>BCNAME_SOURCEFIELDVALUE</Name>
           <System>SYSTEM_NAME</System>
           <Search>SEARCH_CRITERIA</Search>
           <no_of_sessions>100</no_of_sessions>
       </Record_Type>
   

   The following example assumes that the source field is within the Account Business Component.

   <Parameter>
       <Record_Type>
           <Name>Account_EBIZ</Name>
           <System>SiebelDQ_EBIZ</System>
           <Search>search-org</Search>
           <no_of_sessions>100</no_of_sessions>
       </Record_Type>
   </Parameter>
   

   <Parameter>
       <Record_Type>
           <Name>Account_SIEBEL</Name>
           <System>SiebelDQ_SIEBEL</System>
           <Search>search-org</Search>
           <no_of_sessions>100</no_of_sessions>
       </Record_Type>
   </Parameter>
   

4. Navigate to the Administration - Data Quality screen, then the Third Party Administration view, and add the new vendor parameter for ISS as shown in the following table (this example assumes that Account is the Business Component Name, and Source is the Field):

   Parameter Name	Value
   Append Account Record Type Field 1	Source (this the business component field name where the source information is stored).

Configuring the Windows Displayed in Real-Time Data Matching

In real-time data matching when the user saves a new account, contact, or prospect record, the Siebel application displays the duplicate records in a window.

You can change the name of the windows that are displayed, and you can specify that a window is displayed for some other applets. This can be a similar applet to the Contact List, Account List, or List Mgmt Prospective Contact List applet or a customized applet. Both list and detail applets are supported, as long as they are not child applets.

For more information about configuring the windows displayed in real-time data matching, see the following procedures:

• Changing a Window Name

• Adding a Deduplication Window for an Applet

• Configuring a Real-Time Deduplication Window for Child Applets

Changing a Window Name

Use the following procedure to change the name of a window displayed.

To change the name of the window displayed

1. Login to Web Tools, open the workspace.

2. In the Object Explorer, select the Applet, and then select the applet of interest, for example, Contact List Applet.

3. In the Object Explorer, select Applet User Prop.

4. Select the DeDuplication Results Applet user property and change its value as required.

5. Save the changes and submit the workspace for delivery.

Adding a Deduplication Window for an Applet

Use the following procedure to add a Deduplication Window for an applet.

To add a Deduplication Window for an applet

1. Login to Web Tools, open the workspace.

2. In the Object Explorer, select the Applet object, and then select the applet of interest, for example, Account Form Applet

3. In the Object Explorer, select Applet User Prop.

4. Add a new record with the following settings:

   • Name. DeDuplication Results Applet

   • Value. DeDuplication Results (Account) List Applet

5. Save the changes and submit the workspace for delivery.

Configuring a Real-Time Deduplication Window for Child Applets

Configuration changes are required in Siebel Tools to set up the real-time Deduplication Window on child applets.

To configure the real-time Deduplication Window for a child applet, an applet user property must be added to the respective applet where the Deduplication Window is required. For example, to generate a window from the Account Contact view, add the applet user property to Account Contact List Applet, as described in the following procedure.

To configure the real-time Deduplication Window for a child applet (Account Contact view)

1. In Web Tools, open the workspace, query for the following applet:

   Account Contact List Applet

2. Add the following user property to this applet:

   • Name. DeDuplication Results Applet

   • Value. DeDuplication Results (Contact) List Applet

Configuring the Mandatory Fields for Fuzzy Query

For a business component you can configure the mandatory fields for fuzzy query - query fields that must include values for the Siebel application to use fuzzy query mode. Identifying Mandatory Fields for Fuzzy Query shows the preconfigured mandatory fields that Oracle Corporation provides.

Use the following procedure to configure the mandatory fields for a business component.

To configure the fields that are mandatory for fuzzy query

1. Login to Web Tools, open the workspace.

2. In the Object Explorer, expand Business Component and then select the business component of interest in the Business Components pane.

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

4. In the Business Component User Properties pane, select Fuzzy Query Mandatory Fields, and enter the required field names in the Value column.

Data Quality User Properties

This topic provides information about data quality user properties, including deduplication and data cleansing business service user properties. Information about the following is included in this topic:

• Account - Business Component User Properties

• Contact - Business Component User Properties

• List Mgmt Prospective Contact - Business Component User Properties

• DeDuplication - Business Service User Properties

• Data Cleansing - Business Service User Properties

• DQ Sync Services - Business Service User Properties

• ISS System Services - Business Services User Properties 

Account - Business Component User Properties

Data quality uses the Account business component user properties listed in the following table.

Name	Value	Comment
DQ Business Object	DQ Vendor	These business component user properties for Account specify the business object and business component used in the data quality Administration views in Siebel CRM.
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Mapping Config BC	DQ Mapping Config
DQ Vendor Info BC	DQ Vendor Info
DQ Key BusComp	Account Key	For the Universal Connector, DQ Key BusComp is used to specify the Name of the buscomp that stored the deduplication key generated in Siebel.
DeDuplication Key BusComp	DeDuplication - SSA Account Key	For SDQ Matching Server, DeDuplication Key BusComp is used to specify the Name of the buscomp that stored the dedup key generated by SSA.
DeDuplication Results BusComp	DeDuplication Results (Account)	Specifies the Name of the buscomp that will store the returned duplicated record data.
DeDuplication Results List Applet	DeDuplication Results (Account) List Applet	Specifies the Name of the pick applet used to prompt the user to resolve duplicates.
Fuzzy Query Mandatory Fields	"Name"	Specifies the mandatory fields for Fuzzy Query; that is, the query fields that must include values so that the Siebel application can use the fuzzy query mode.
DQ Associate BC 1	CUT Address: Address Id	Specifies the Name of the child MVG buscomp, and the field in the parent buscomp that comes from this MVG. This business component applies to the data quality Multiple Address Deduplication feature. Note: MVG stands for multiple value group.

For each field used in Multiple Address Deduplication that comes from the child MVG buscomp, a field user property is specified to map it to the child business component field, as shown in the following table.

Field	Name	Value
Primary Account City	DQ Associate BC Map	DQ Associate BC 1: City
Primary Account Country	DQ Associate BC Map	DQ Associate BC 1: Country
Primary Account Postal Code	DQ Associate BC Map	DQ Associate BC 1: Postal Code
Primary Account State	DQ Associate BC Map	DQ Associate BC 1: State
Primary Account Street Address	DQ Associate BC Map	DQ Associate BC 1: Street Address

Contact - Business Component User Properties

Data quality uses the Contact business component user properties listed in the following table.

Name	Value	Comment
DQ Business Object	DQ Vendor	These business component user properties for Contact specify the business object and business component used in the data quality Administration views in Siebel CRM.
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Mapping Config BC	DQ Mapping Config
DQ Vendor Info BC	DQ Vendor Info
DQ Key BusComp	Contact Key	For the Universal Connector, DQ Key BusComp is used to specify the Name of the buscomp that stored the deduplication key generated in Siebel.
DeDuplication Key BusComp	DeDuplication - SSA Contact Key	For SDQ Matching Server, DeDuplication Key BusComp is used to specify the Name of the buscomp that stored the dedup key generated by SSA.
DeDuplication Results BusComp	DeDuplication Results (Contact)	Specifies the Name of the buscomp that will store the returned duplicated record data.
DeDuplication Results List Applet	DeDuplication Results (Contact) List Applet	Specifies the Name of the pick applet used to prompt the user to resolve duplicates.
Fuzzy Query Mandatory Fields	"Last Name", "First Name"	Specifies the mandatory fields for Fuzzy Query; that is, the query fields that must include values so that the Siebel application can use the fuzzy query mode.
DQ Associate BC 1	CUT Address: Personal Address Id	Specifies the Name of the child MVG buscomp, and the field in the parent buscomp that comes from this MVG. This business component applies to the data quality Multiple Address Deduplication feature. Note: MVG stands for multiple value group.

For each field used in Multiple Address Deduplication that comes from the child MVG buscomp, a field user property is specified to map it to the child business component field, as shown in the following table.

Field	Name	Value
Primary Personal City	DQ Associate BC Map	DQ Associate BC 1: City
Primary Personal Country	DQ Associate BC Map	DQ Associate BC 1: Country
Primary Personal Postal Code	DQ Associate BC Map	DQ Associate BC 1: Postal Code
Primary Personal State	DQ Associate BC Map	DQ Associate BC 1: State
Primary Personal Street Address	DQ Associate BC Map	DQ Associate BC 1: Street Address

List Mgmt Prospective Contact - Business Component User Properties

Data quality uses the List Mgmt Prospective Contact business component user properties listed in the following table.

Name	Value	Comment
DQ Business Object	DQ Vendor	These business component user properties for List Mgmt Prospective Contact specify the business object and business component used in the data quality Administration views in Siebel CRM.
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Mapping Config BC	DQ Mapping Config
DQ Vendor Info BC	DQ Vendor Info
DQ Key BusComp	Prospect Key	For the Universal Connector, DQ Key BusComp is used to specify the Name of the buscomp that stored the deduplication key generated in Siebel.
DeDuplication Key BusComp	DeDuplication - SSA Prospect Key	For SDQ Matching Server, DQ Key BusComp is used to specify the Name of the buscomp that stored the dedup key generated by SSA.
DeDuplication Results BusComp	DeDuplication Results (Prospect)	Specifies the Name of the buscomp that will store the returned duplicated record data.
DeDuplication Results List Applet	DeDuplication Results (Prospect) List Applet	Specifies the Name of the pick applet used to prompt the user to resolve duplicates.
Fuzzy Query Mandatory Fields	"Last Name", "First Name"	Specifies the mandatory fields for Fuzzy Query; that is, the query fields that must include values so that the Siebel application can use the fuzzy query mode.

DeDuplication - Business Service User Properties

Data quality uses the DeDuplication business service user properties listed in the following table.

Name	Value	Comment
DQ Vendor BO	DQ Vendor	These business service user properties for DeDuplication specify the business object and business component used in the data quality Administration views in Siebel CRM.
DQ Vendor BC	DQ Vendor Info
DQ Mapping Config BC	DQ Mapping Config
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Vendor Param BC	DQ Vendor Parameter

Data Cleansing - Business Service User Properties

Data quality uses the Data Cleansing business service user properties listed in the following table.

Name	Value	Comment
DQ Vendor BO	DQ Vendor	These business service user properties for Data Cleansing specify the business object and business component used in the data quality Administration views in Siebel CRM.
DQ Vendor BC	DQ Vendor Info
DQ Mapping Config BC	DQ Mapping Config
DQ Field Mapping Info BC	DQ Field Mapping Info
DQ Vendor Param BC	DQ Vendor Parameter

DQ Sync Services - Business Service User Properties

The DQ Sync Services business service is used when synchronizing data between the Siebel application and Oracle Data Quality Matching Server (Informatica Identity Resolution). The Siebel application uses it to insert records into the NSA table belonging to the Oracle Data Quality Matching Server.

Data quality uses the DQ Sync Services business service user properties listed in the following table.

Name	Value	Comment
Account Integration Object Name	SyncAccount	These business service user properties specify the Integration Objects and Components used by the Siebel application to synchronize with Oracle Data Quality Matching Server (Informatica Identity Resolution).
Account Address Component Name	Account_Business Address
Contact Integration Object Name	SyncContact
Contact Address Component Name	Contact_INS Personal Address
Prospect Integration Object Name	SyncProspect
ISS System Name	siebeldq	These business service user properties specify the default Informatica Identity Resolution system name and IDT table names.
Account IDT Name	IDS_01_IDT_ACCOUNT
Contact IDT Name	IDS_01_IDT_CONTACT
Prospect IDT Name	IDS_01_IDT_PROSPECT
Account Record Length	1090	These business service user properties specify the Account record fields, data type, and length.
Account_DeDupFlds	Name|DUNS Number|Id
Account_DataType	W|W|C
Account_ExtLen	200|120|30
Contact Record Length	1850	These business service user properties specify the Contact record fields, data type, and length.
Contact_DeDupFlds	Birth Date|Cellular Phone #|Email Address|First Name Last Name|Home Phone #|Middle Name|Account|Id|Social Security Number|Work Phone #
Contact_DataType	W|W|W|W|W|W|W|C|W|W
Contact_ExtLen	120|120|120|200|120|200|200|30|120|120
Prospect Record Length	1770	These business service user properties specify the Prospect record fields, data type, and length.
Prospect_DeDupFlds	Account|Cellular Phone #|City|Country|Email Address|First Name Last Name|Home Phone #|Middle Name|Postal Code|Social Security Number|State|Street Address|Work Phone #|Id
Prospect_DataType	W|W|W|W|W|W|W|W|W|W|W|W|W|C
Prospect_ExtLen	200|120|120|60|120|200|120|200|40|120|40|200|200|30
Account_Business Address_DeDupFlds	City|Country|Postal Code|State|Street Address|Address Id	These business service user properties specify the Account Business Address record fields, data type, and length.
Account_Business Address_DataType	W|W|W|W|W|C
Account_Business Address_ExtLen	200|120|120|40|200|60
Contact_INS Personal Address_DeDupFlds	INS Personal City|INS Personal Country|INS Personal Postal Code|INS Personal State|INS Personal Street Address|INS Personal Address Id	These business service user properties specify the Contact INS Personal Address record fields, data type, and length.
Contact_INS Personal Address_DataType	W|W|W|W|W|C
Contact_INS Personal Address_ExtLen	120|40|40|40|200|60
Filter Characters	<Enter characters separated by a single space> Note: ^ (code separator) | (code separator) \r (carriage return)\n (new line) \t (horizontal tab)\f (form feed)	This business service user property is used to specify any special characters that need to be removed from data sent to the Oracle Data Quality Matching Server. Note: Enter all filter characters separated by a single space. For control characters, enter the ASCII code in the following format: ^nnn (where nnn is the code in decimal).
IIR Server on Little Endian Operating System	Yes	This business service user property is used to specify the Endian of the Operating System where the Oracle Data Quality Matching Server is installed.

ISS System Services - Business Services User Properties

When synchronizing data in Multiple Languages Support mode between the Siebel application and Oracle Data Quality Matching Server (Informatica Identity Resolution), the ISS System Services Business Service is used to specify the system name and database number in Informatica Identity Resolution, where each system corresponds to a specific country or language.

Data quality uses the ISS System Services business service user properties listed in the following table.

Name	Value	Comment
Account Default System	siebeldq	These business service user properties specify the default Informatica Identity Resolution system name for each support object.
Contact Default System	siebeldq
Prospect Default System	siebeldq
siebeldq	01	These are sample business service user properties. You must enter the actual Informatica Identity Resolution system name and corresponding database number. The default system has a database number of 01.
siebeldq_Denmark	02
siebeldq_UNITED_STATES	03

Related Topic

Configuring Multiple Language Support for Data Matching