DQ Xi Seiebel Ucm - User Guide

BusinessObjects Data Quality Management for Oracles Siebel UCM 8.
0 Users Guide
Data Quality for Oracles Siebel UCM 11.7.0.0 April 2008
&RQWDFW LQIRUPDWLRQ
Contact us on the Web at http://www.businessobjects.com/support If you find any problem with this documentation, please report it to Business Objects in writing at documentation@businessobjects.com. If your issue concerns a Business Objects product and not the documentation, please contact our Customer Support experts.
&RS\ULJKW 3DWHQWV
Copyright 2008 Business Objects. All rights reserved. Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352. Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. Business Objects products in this release may contain redistributions of software licensed from third-party contributors. Some of these individual components may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty
7UDGHPDUNV
7KLUGSDUW\ FRQWULEXWRUV
7vrPiwrp9hhRhyvHhhtrrsPhpyrTvriryV8H'VrBvqr
&RQWHQWV
Preface .............................................................................................................7 About this guide.........................................................................................7 Conventions ...............................................................................................7 Assumed audience .....................................................................................7 Naming conventions ..................................................................................7 About versions ...........................................................................................7 Access the latest Business objects documentation ....................................8 Chapter 1: Overview ........................................................................................................ 9 Data quality overview ....................................................................................10 What is data quality? ...............................................................................10 What steps are involved in data quality? .................................................10 What is Data Quality for Oracles Siebel UCM? ...........................................13 Who updates Data Quality for Oracles Siebel UCM?............................13 Siebel Data Quality Universal Connector license and documentation....13 Firstlogic ..................................................................................................13 Address-cleansing transforms..................................................................13 Parsing and standardization-transforms...................................................13 Match transforms .....................................................................................13 Flexible business rules and configuration................................................13 Introduction to BusinessObjects Data Quality XI..........................................14 Data quality hub.......................................................................................14 More information about BusinessObjects Data Quality XI.....................14 Access BusinessObjects Data Quality XI documentation .......................15 Chapter 2: Installation ................................................................................................... 17 System requirements on your Siebel systems ................................................18 Operating system requirements ...............................................................18 Installation scenarios ......................................................................................19 System with Windows server ..................................................................19 The installation process..................................................................................20 Prerequisite: Siebel Data Quality Universal Connector ..........................20 Step 1: Install BusinessObjects Data Quality XI, copy the dataflows, and disable unused address engines ...............................................................20 Step 2: Install the Data Quality for Oracles Siebel UCM software........20 Step 3: Application Administration setup................................................20 BusinessObjects Data Quality XI installation notes and procedures .............21 Install BusinessObjects Data Quality XI .................................................21 Copy dataflows and transforms to BusinessObjects Data Quality XI installation................................................................................................21 Disable unused address cleanse engines..................................................22 Installing Data Quality for Oracles Siebel UCM on your Siebel system .....24 Install your Data Quality for Oracles Siebel UCM software .................24 Manual updates to configuration .............................................................24
8r
Start the BusinessObjects Data Quality XI Server.................................. 24 Administrative setup ...................................................................................... 26 Change the third-party DLL name .......................................................... 26 Edit the Siebel configuration file (for clients)......................................... 26 Enabling data quality through the Siebel application.............................. 26 Chapter 3: Configuring Data Quality for Oracles Siebel UCM ............................... 29 The client configuration file .......................................................................... 30 Format of the file..................................................................................... 30 Editing the file......................................................................................... 30 File parameters ........................................................................................ 30 Default Siebel configuration supported ......................................................... 31 Business components supported by default ............................................ 31 UCM batch object supported................................................................... 31 Siebel fields supported by default ........................................................... 31 Chapter 4: Using Data Quality for Oracles Siebel UCM .......................................... 35 Interactive cleansing with Data Quality for Oracles Siebel UCM ............... 36 Using interactive cleansing ..................................................................... 36 Interactive matching and consolidation with Data Quality for Oracles Siebel UCM ................................................................................................... 37 Populate the match key value.................................................................. 37 Identify duplicate records........................................................................ 37 Remove duplicate records ....................................................................... 37 Batch processing ............................................................................................ 39 Setting the Where Clause ........................................................................ 39 Batch option components ........................................................................ 39 Creating a new batch job ......................................................................... 40 Running a batch job................................................................................. 41 Running the batch process from the command line ................................ 41 Incremental Data Matching jobs ............................................................. 42 Batch jobs with the UCM Batch Manager .............................................. 42 Batch job considerations................................................................................ 44 Cleansing business components in proper order ..................................... 44 Running batch processes simultaneously................................................ 44 Avoid cleansing the siebel administrator record ................................. 44 Consolidation after batch match .................................................................... 45 Viewing duplicate records....................................................................... 45 Merge duplicate records .......................................................................... 45 For UCM Batch Manager........................................................................ 45 Chapter 5: Concepts for customized applications....................................................... 47 Master configuration...................................................................................... 48 Configuration options.............................................................................. 49 Dataflow input/output field names ................................................................ 52 Add a new field ....................................................................................... 52 Remove a field ........................................................................................ 52 Example: adding new fields for cleansing/matching ..................................... 53 Working with address-cleansing errors ......................................................... 55 Posting address errors to your Siebel database ....................................... 55
7vrPiwrp9hhRhyvYDsPhpyrTvriry8SH&&hqPhpyrTvriry8SH&'VrBvqr
Customizing and suppressing error messages .........................................55 Chapter 6: Tips and troubleshooting ............................................................................ 57 Parsing and standardization............................................................................58 Error on M/M field ..................................................................................58 BusinessObjects Data Quality XI...................................................................59 BusinessObjects Data Quality XI connection troubles............................59 Logging....................................................................................................59 Crash on DQXI service............................................................................59 Address cleanse transform change me setting .....................................60 Transaction dataflows..............................................................................60 Address cleansing...........................................................................................61 1030 error.................................................................................................61 Error on State or Country fields...............................................................61 Match/consolidate ..........................................................................................62 Interactive matching seems unusually slow ............................................62 Batch processing errors ..................................................................................63 Problems processing large record sets .....................................................63 Match Key Generation.............................................................................63 Client and server issues ..................................................................................64 Client hangs .............................................................................................64 Client hangs/Data Quality Server windows Service not started automatically............................................................................................64 Appendix A: Reference.......................................................................................................65 Business component and dataflow reference...........................................65 Index ..............................................................................................................67
8r
7vrPiwrp9hhRhyvYDsPhpyrTvriry8SH&&hqPhpyrTvriry8SH&'VrBvqr
3UHIDFH
$ERXW WKLV JXLGH
This guide provides a general overview of BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0, as well as specific information for installing and integrating this product into your Siebel environment. This document follows these conventions:
&RQYHQWLRQV
&RQYHQWLRQ
Bold
'HVFULSWLRQ
We use bold type for file names, paths, emphasis, and text that you should type exactly as shown. For example, Type cd\ dirs. We use italics for emphasis and text for which you should substitute your own data or values. For example, Type a name for your file, and the .txt extension (testfile.txt). We indicate commands that you choose from menus in the following format: Menu Name > Command Name. For example, Choose File > New. We use this symbol to alert you to important information and potential problems. We use this symbol to point out special cases that you should know about. We use this symbol to draw your attention to tips that may be useful to you.
Italics
Menu commands
$VVXPHG DXGLHQFH
This manual assumes that the people responsible for integrating BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0 are experienced users of Siebel UCM and that the Siebel system has been fully configured to work with this product. This manual does not explain basic operation of Siebel UCM. For questions about Siebel UCM, consult the appropriate Siebel documentation or Siebel technical support.
1DPLQJ FRQYHQWLRQV
For brevity, BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0 is often in this guide called Data Quality for Oracles Siebel UCM. BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0 supports only version 8.0 of Oracles Siebel UCM.
$ERXW YHUVLRQV
$FFHVV WKH ODWHVW %XVLQHVV REMHFWV GRFXPHQWDWLRQ
In addition to the documentation installed on your computer during installation of this product, you can access all the supported Business Objects documentation from the Business Objects Customer Support site. 1. Go to http://www.businessobjects.com. 2. From the Support pull-down menu, choose Documentation. 3. On the Documentation screen, choose Product Guides and navigate to the document that you want to view. You can view the PDFs online or save them to your computer.
&KDSWHU 2YHUYLHZ
Before using BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0, you should understand some data quality concepts. A basic familiarity with these concepts will help you to understand what Data Quality for Oracles Siebel UCM does, and why your company benefits from data quality.
8uhr )Prvr
'DWD TXDOLW\ RYHUYLHZ

:KDW LV GDWD TXDOLW\"
Data quality is a process of arranging customer information in a logical and consistent order while cleansing, standardizing, and enhancing the data. The process then combines related records to avoid duplicate entries. This process adds value by creating a single view of your customers. Generally, data quality requires five main steps: This version of Data Quality for Oracles Siebel UCM fulfills these steps of the data quality process:
parsing correction standardization matching consolidation
:KDW VWHSV DUH LQYROYHG LQ GDWD TXDOLW\"
3DUVLQJ
Parsinginvolves checking the structure and content of each field of a contacts information, for example. During parsing, checks ensure that data appears where it belongs; an address does not appear in a name field, for example. Some of the more common elements to search for in a record during parsing include first and last name, title, company name, business versus personal mailing address, e-mail address, phone number (business, cell, fax), and social security number. Data in Siebel is often entered in discrete fields, and doesnt need to be parsed. However, you may configure your application to accept a multiline input that is parsed.
&RUUHFWLRQ
Correction can begin after parsing is complete and data resides in the proper fields. In order to correct data, it becomes necessary to use secondary data sources, such as the U.S. Postal Services National Directory or an international postal directory, to check and validate address information. Using these secondary sources, a program can check, for example, whether La Crosse, Wisconsin is associated with the ZIP code 54601, whether Harborview Plaza is actually a valid street name in La Crosse, and whether 100 is a valid address for that street.

6WDQGDUGL]DWLRQ
After correcting the data, it is important to standardize the data. Standardization works in conjunction with correction and parsing as it arranges customer information in a consistent and preferred format. This facilitates successful matching and consolidation of data elements. Examples of standardization include removal of dashes from a phone number or social security number, use of a common abbreviation such as DEPT for department number, or common representations of title such as Mr., Ms., Mrs., and Jr. It also includes the application of standard address elements such as converting Street to St and converting South West to SW. Once a quality customer record exists, matching should become part of the data quality analysis to eliminate redundancies. During the matching step, software searches existing customer data records using specific business-defined criteria to look for similar records. If no match is found, the data quality process is complete. If a match is found, however, then there is one final step required.
0DWFKLQJ
8uhr )Prvr

&RQVROLGDWLRQ
When a match is found, simply identifying all of the related records in the database is not enough to create a single view of the customer. Consolidation uses the data found during matching to combine all of the similar data into a single consolidated view of each customer. In Data Quality for Oracles Siebel UCM, consolidation is accomplished by eliminating inferior records, or by merging the matching records through Siebels merge process.
These data quality concepts provide a foundation that helps a business to develop a clear picture of the customer, which can improve both efficiency and effectiveness. Because there are so many touch points for customer data in an organization, this activity has far-reaching implications in how you conduct business on a day-to-day basis.

:KDW LV 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0"

Data Quality for Oracles Siebel UCM is software that provides the correction and standardization steps in the data quality process.
:KR XSGDWHV 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0" 6LHEHO 'DWD 4XDOLW\ 8QLYHUVDO &RQQHFWRU OLFHQVH DQG GRFXPHQWDWLRQ
Data Quality for Oracles Siebel UCM is created and maintained by Business Objects, an SAP Company.
To install and use Data Quality for Oracles Siebel UCM, you must have a software license for the Siebel Data Quality Universal Connector as part of your Siebel configuration. The Siebel Data Quality Universal Connector is licensed separately from Siebel UCM 8.0. The functionality of the Siebel Data Quality Universal Connector used by this product is documented in the Oracle publication, Siebel Data Quality Administration Guide, Version 8.0.
)LUVWORJLF
Within the GUI of Data Quality for Oracles Siebel UCM and in the document Siebel Data Quality Administration Guide, Version 8.0, the term Firstlogic is mentioned as a setting, technology, and as a software vendor. Since the creation of the Siebel Data Quality Universal Connector, Firstlogic has been acquired by Business Objects and the technologies or settings referred to as Firstlogic are used by this product. In short, when you see the word Firstlogic, it applies to this product. The address-cleansing transforms use address directories compiled from postal authorities such as the United States Post Office, and other sources. Depending on the country transforms you purchase, Data Quality for Oracles Siebel UCM can cleanse both domestic (U.S.) and global addresses. The parsing and standardization transforms use name dictionaries to find and, if necessary, add or fix name and firm (business name) information from your source data. For example, based on the name dictionary information, you can add to your data other name-related components, such as gender, titles, and so on. The match transforms bring sophisticated record-matching and consolidation technology to your Siebel applications. Siebel administrators can fine-tune the results of Data Quality for Oracles Siebel UCM by making changes to the BusinessObjects Data Quality XI dataflows that are provided with the program. For information about modifying dataflows, see the BusinessObjects Data Quality XI documentation. You can integrate Data Quality for Oracles Siebel UCM no matter how youve customized your Siebel application. For information about how to configure Data Quality for Oracles Siebel UCM for a customized Siebel application, see Concepts for customized applications on page 47.
$GGUHVVFOHDQVLQJ WUDQVIRUPV
3DUVLQJ DQG VWDQGDUGL]DWLRQ WUDQVIRUPV
0DWFK WUDQVIRUPV
)OH[LEOH EXVLQHVV UXOHV DQG FRQILJXUDWLRQ
8uhr )Prvr

,QWURGXFWLRQ WR %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;,

As a Data Quality for Oracles Siebel UCM user, you may wonder what BusinessObjects Data Quality XI is and what it means to you. After installation, you can use Data Quality for Oracles Siebel UCM with little thought given to BusinessObjects Data Quality XI, because it handles the data quality processes behind the scenes. The version of BusinessObjects Data Quality XI shipped as part of the Data Quality for Oracles Siebel UCM is customized to run only as part of the Data Quality for Oracles Siebel UCM, but the technology of BusinessObjects Data Quality XI offers other potential solutions to your enterprises data quality needs. This section provides an overview of what BusinessObjects Data Quality XI does, independent of its use within the Data Quality for Oracles Siebel UCM, and tells you where you can find more information about BusinessObjects Data Quality XI.
'DWD TXDOLW\ KXE
BusinessObjects Data Quality XI is the next generation data quality platform that allows you to tie in all of your data quality needs to a single hub. Many users of Data Quality for Oracles Siebel UCM also have data quality needs in other applications or other areas of their enterprise. Instead of having many disparate solutions for each area of your enterprise, you can use BusinessObjects Data Quality XI as the backbone for all of your data quality needs. With BusinessObjects Data Quality XI, you can centralize and standardize this processing through the following features. All of the business rule definitions are stored in a single repository that can be shared by all applications that use BusinessObjects Data Quality XI. You can organize business rules into reusable objects that can be shared to meet your enterprise requirements. You can use the same objects in a project for the Data Quality for Oracles Siebel UCM, your own custom application that incorporates BusinessObjects Data Quality XI, or direct batch processing through BusinessObjects Data Quality XI itself. This means that you can create data quality standards that are truly shared across your entire enterprise.
&HQWUDOL]HG EXVLQHVV UXOH UHSRVLWRU\
6HUYLFHRULHQWHG DUFKLWHFWXUH
BusinessObjects Data Quality XI is built on service-oriented architecture principles. That means that BusinessObjects Data Quality XI is a service that can work with your other applications. You can set up any number of instances of the BusinessObjects Data Quality XI Server software, and your applications (including Data Quality for Oracles Siebel UCM) can communicate with that server directly, or via a web server using the BusinessObjects Data Quality XI web service. This means that all of your data quality processing can happen in one centralized area.
0RUH LQIRUPDWLRQ DERXW %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;,
For more information about BusinessObjects Data Quality XI, see the BusinessObjects Data Quality XI documentation. The documentation is available in electronic format, both in a printable PDF file and an online help format.

$FFHVV %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, GRFXPHQWDWLRQ
After installing BusinessObjects Data Quality XI, you can access the documentation from shortcuts on the Start menu. To access the documentation: 1. Choose Start > Programs > BusinessObjects XI Release 2 > Data Quality 11.7 > Documentation. 2. Click the appropriate shortcut for the documentation you want to view. Documentation is installed as a separate component. The documentation for BusinessObjects Data Quality XI is an optional installation component in most cases. If you dont install the documentation while installing BusinessObjects Data Quality XI, it wont be available on your system.
8uhr )Prvr

&KDSWHU ,QVWDOODWLRQ
This chapter explains the requirements and procedures for installing the BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0.
8uhr!)Dhyyhv

6\VWHP UHTXLUHPHQWV RQ \RXU 6LHEHO V\VWHPV

In some cases the requirements for servers or thick clients that use Data Quality for Oracles Siebel UCM exceed those of regular Siebel servers or thick clients. These requirements are documented in the following sections. This section does not discuss the system requirements for running the BusinessObjects Data Quality XI portion of BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0. For that information, see the BusinessObjects Data Quality XI documentation that is included in this software package.
2SHUDWLQJ V\VWHP UHTXLUHPHQWV
6XSSRUWHG VHUYHU RSHUDWLQJ V\VWHPV
This section describes which operating systems are supported for this product.
Windows 2000 Windows 2003 Windows 2000 Windows XP
6XSSRUWHG FOLHQW RSHUDWLQJ V\VWHPV

,QVWDOODWLRQ VFHQDULRV
As you integrate Data Quality for Oracles Siebel UCM, you must consider that a computer running Siebel software might be used as a server, a connected thick client, a mobile thick client or a zero-footprint client.
6\VWHP ZLWK :LQGRZV VHUYHU
&RQQHFWHG WKLFN FOLHQWV
Data Quality for Oracles Siebel UCM is run on either a Siebel server computer, a thick (mobile) client computer, or a zero-footprint client computer.
The term connected thick client refers to a thick client computer that always has access to a Siebel server computer. These types of thick clients require some setup to be able to run Data Quality for Oracles Siebel UCM, but only require a very small amount of disk space for Data Quality for Oracles Siebel UCMrelated files (approximately 1 MB). If you want to use the Siebel Simulator to test UCM workflows before publishing, you may be using this scenario. The term mobile thick client refers to a thick client computer that may be used remotely and isnt always connected to a Siebel server computer. These clients can be set up to access a remote Data Quality for Oracles Siebel UCM server (one available via the network) or you can install an additional Data Quality for Oracles Siebel UCM server directly to the remote client. If you want to use the Siebel Simulator to test UCM workflows before publishing, you may be using this scenario.
0RELOH WKLFN FOLHQWV
=HURIRRWSULQW FOLHQWV
You can configure Data Quality for Oracles Siebel UCM to operate on zero-footprint (thin) clients. In this scenario, no files are installed on the client computer, but are instead installed to a server computer.
8uhr!)Dhyyhv

7KH LQVWDOODWLRQ SURFHVV

This section explains the high-level installation steps and tells you where to look for more detailed steps.
3UHUHTXLVLWH 6LHEHO 'DWD 4XDOLW\ 8QLYHUVDO &RQQHFWRU
To install and use Data Quality for Oracles Siebel UCM, you must have a software license for the Siebel Data Quality Universal Connector as part of your Siebel configuration. The Siebel Data Quality Universal Connector is licensed separately from Siebel UCM 8.0. Your first step is to install BusinessObjects Data Quality XI, copy the dataflows that are used for Data Quality for Oracles Siebel UCM, and disable the unused address engines. For instructions on installing BusinessObjects Data Quality XI, see the BusinessObjects Data Quality XI documentation, but for instruction on copying the dataflows and other additional and necessary details, see BusinessObjects Data Quality XI installation notes and procedures on page 21. Your next step is to install the software that powers the Data Quality for Oracles Siebel UCM. This software allows your Siebel application to interact with the BusinessObjects Data Quality XI Server you install in Step 1. You can install it to the same computer that houses the Siebel server, or to any computer that is available to the Siebel server and Siebel clients via the network. For details on this installation step, see Installing Data Quality for Oracles Siebel UCM on your Siebel system on page 24.
6WHS ,QVWDOO %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, FRS\ WKH GDWDIORZV DQG GLVDEOH XQXVHG DGGUHVV HQJLQHV
6WHS ,QVWDOO WKH 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0 VRIWZDUH
6WHS $SSOLFDWLRQ $GPLQLVWUDWLRQ VHWXS
You must change the DLL name for Data Quality for Oracles Siebel UCM. You do this through the Application Administration screens of your Siebel application. For details on this step, see Administrative setup on page 26.

%XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, LQVWDOODWLRQ QRWHV DQG SURFHGXUHV

This section describes issues unique to installing BusinessObjects Data Quality XI as part of Data Quality for Oracles Siebel UCM, including a procedure to copy the Data Quality for Oracles Siebel UCM dataflows and transforms from the BusinessObjects Data Quality Integration Studio Dataflows installation media and disabling unused address cleanse engines. You must complete the installation and configuration of BusinessObjects Data Quality XI before proceeding to the rest of the installation of Data Quality for Oracles Siebel UCM.
,QVWDOO %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;,
You must install BusinessObjects Data Quality XI before installing the other components of Data Quality for Oracles Siebel UCM. You can find instructions for installing, configuring, and running BusinessObjects Data Quality XI in the BusinessObjects Data Quality XI documentation. You can install BusinessObjects Data Quality XI on the same machine as the Siebel server, on a different machine, or even on a machine with a different operating system than the one that contains your installation of Siebel. Business Objects strongly recommends that you create a new database instance (depending on your database) for the BusinessObjects Data Quality XI Metadata Repository and Global Parsing Option dictionaries. Information about the system requirements for the machine on which you install BusinessObjects Data Quality XI and the recommendations provided here are included with the BusinessObjects Data Quality XI documentation.
%XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, LQVWDOO PDFKLQH
%XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, SUHYLRXVO\ LQVWDOOHG
If you are already a BusinessObjects Data Quality XI customer (prior to the installation of this product) and therefore have already installed a version of BusinessObjects Data Quality XI, you must upgrade to BusinessObjects Data Quality XI 11.7.1.0, which is provided as part of this software package. See the BusinessObjects Data Quality XI documentation for details of how to upgrade.
&RS\ GDWDIORZV DQG WUDQVIRUPV WR %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, LQVWDOODWLRQ
The BusinessObjects Data Quality Integration Studio Dataflows installation media that ships with this product contains dataflows and transforms in the form of .xml files that are specific to the functionality of the Data Quality for Oracles Siebel UCM. You must copy the dataflows and transforms from the installation media to your BusinessObjects Data Quality XI installation. If you have a previous installation of BusinessObjects Data Quality XI and you have customized any dataflows or transforms, copying the dataflows and transforms from the installation media will overwrite the existing files and therefore overwrite any customizations you have made. Before copying the dataflows and transforms to your BusinessObjects Data Quality XI installation, you should make a backup copy of all the files in the DataQualityinstall\repository\ folder, where DataQualityinstall is the location of your BusinessObjects Data Quality XI installation (by default, c:\ dqxi\11_7).
8uhr!)Dhyyhv

To copy the dataflows and transforms to your BusinessObjects Data Quality XI installation: 1. From the BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0 UCM Dataflows installation media, copy the folder repository (and all the folders and files within) to the folder DataQualityinstall\, where DataQualityinstall is the location of your BusinessObjects Data Quality XI installation (by default, c:\dqxi\11_7). 2. When prompted for permission to overwrite files, choose Yes to all. The files are copied to their correct locations in subdirectories of the folder DataQualityinstall\repository\. 3. Restart the BusinessObjects Data Quality XI Server.
'LVDEOH XQXVHG DGGUHVV FOHDQVH HQJLQHV
After installing BusinessObjects Data Quality XI and copying the additional dataflows and transforms, you must disable in BusinessObjects Data Quality XI the country-based address cleanse engines that you did not purchase in order for this product to work properly. The following is the list of BusinessObjects Data Quality XI address engines that you can disable:
Australia Plugin Canada Plugin Global Address Cleanse Japan (for Japanese Unicode data) Japan Plugin Multi Country Plugin USA Plugin
These address engines are configured with the assumption that you purchased all of the address technology engines, so each engine is enabled upon installation. If you purchased only a subset of the address processing engines, you must manually disable the unused address cleanse engines. You may also want to disable individual address cleanse engines to allow you to test only a certain address cleanse engine in isolation from others, or for any other purposes. However, you must disable address cleanse engines that are not purchased and used.
for
To disable unused address cleanse engines: 1. In the BusinessObjects Data Quality XI Project Architect, go to projects/ blueprints/siebel/transactional_business_address_datacleanse. 2. Right-click any address cleanse engine you want to disable, and select Disable from the context-sensitive menu. Disabled engines are displayed as gray and indicated with the symbol 7 in the upper-left corner. 3. Select the transform Global Suggest Lists Global. 4. For Global Suggest Lists Global, in the Option Group Name, select ENGINES.

5. In the Options pane, change the Value to NO for any engine you want to disable, if the engine is available in the list. 6. Click the menu button Verify Project to make sure the dataflow is free of errors. 7. Repeat the steps for other dataflows that use address cleanse transforms.
8uhr!)Dhyyhv

,QVWDOOLQJ 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0 RQ \RXU 6LHEHO V\VWHP
After you have installed and configured BusinessObjects Data Quality XI according to the instructions in the BusinessObjects Data Quality XI documentation, the next step is to install Data Quality for Oracles Siebel UCM on your Siebel system.
,QVWDOO \RXU 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0 VRIWZDUH
Usually you install this software to the same computer that houses your Siebel server. To install the software for the Data Quality for Oracles Siebel UCM: 1. From the Data Quality for Oracles Siebel UCM, run setup.exe. 2. After you accept the license agreement, follow the on-screen installation instructions to install your software. During the installation, you are prompted for various information about your system and Siebel server. The installation attempts to automatically identify some of this information. Be prepared to supply the following items, if necessary:
BusinessObjects Data Quality XI Server IP address and bootstrap file location (by default, the bootstrap file is located in DataQualityinstall\ repository\configuration_rules\) Destination folder location Path to the Siebel root location directory (for example, c:\sba8\siebsrvr)
3. Reboot your system after the installation is complete. If you chose the default location, setup installs files into the c:\Program Files\BusinessObjects\DQ_for_Siebel folder and copies files to the Siebelroot\bin and Siebelroot\SDQConnector folders. This Users Guide refers to this path as the installation path. If you choose a different path for installation, you must note this change when the document refers to the default path.
0DQXDO XSGDWHV WR FRQILJXUDWLRQ
You can make manual changes to the configuration information obtained at installation. The configuration information is stored in the file Siebelroot\SDQConnector\DQClient.xml. If the setup routine could not connect to BusinessObjects Data Quality XI and automatically update DQClient.xml, you must make these changes in order to provide the information necessary for the Siebel server to communicate with the BusinessObjects Data Quality XI Server. You must also make changes to this file if the information about your BusinessObjects Data Quality XI Server changes. For instruction on making changes to DQClient.xml, see The client configuration file on page 30.
6WDUW WKH %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, 6HUYHU
After you have installed Data Quality for Oracles Siebel UCM, you must start the BusinessObjects Data Quality XI Server (if it is not already running), before this product can run data quality operations. For details on starting and stopping

the BusinessObjects Data Quality XI Server, see the BusinessObjects Data Quality XI documentation. Before executing the UCM process with data quality enabled, you must have completed all setup procedures for your Siebel system, as described in the Siebel UCM documentation.
8uhr!)Dhyyhv

$GPLQLVWUDWLYH VHWXS
There is some further administrative setup to perform. Before you can use Data Quality for Oracles Siebel UCM, you must change the third-party DLL name in the Application Administration screens, edit the Siebel configuration file, and enable data quality through the Siebel application.
&KDQJH WKH WKLUG SDUW\ '// QDPH
To change the third-party DLL name: 1. Open the Site Map in the Siebel application. 2. Under Administration - Data Quality, click Data Quality Settings. 3. Click Third Party Administration. 4. For the Name Firstlogic, change the DLL Name from FirstlogicConnector to DQClient. For more information about using the administration screens, see the Siebel Data Quality Administration Guide, Version 8.0.
(GLW WKH 6LHEHO FRQILJXUDWLRQ ILOH IRU FOLHQWV
To enable data cleansing and deduplication, you must first set some parameters in your Siebel configuration file. This is necessary only for your clients, not your server. For UCM, this is necessary if you intend to run the Siebel Simulator to test your UCM workflows. 1. Open your Siebel configuration file (siebel.cfg for example). 2. Locate the [DataCleansing] section. 3. For the value of the Enable parameter, enter True. 4. For the value of the Type parameter, enter Firstlogic. This section of your configuration file might look like this:
[DataCleansing] Enable Type = True = Firstlogic
5. Save and close the configuration file. Note: You can repeat these steps for the [DeDuplication] section also.You can enable the Data Cleansing and Deduplication options independently; the two dont need to be the same value. Restart your Siebel Server after making changes to the configuration files in order to activate the changes.
(QDEOLQJ GDWD TXDOLW\ WKURXJK WKH 6LHEHO DSSOLFDWLRQ
)RU EDWFK SURFHVVLQJ
After setting up your configuration file, there are some additional steps you must take to enable data cleansing and deduplication in your client/server architecture. To enable batch processing via your clients: 1. From your Siebel application, choose Administration - Server Configuration > Servers > Components.

2. Choose Data Quality Manager from the list. 3. Click the Component Parameters tab. 4. To enable batch data cleansing, set the Data Cleansing Enable Flag to True. 5. Enter Firstlogic as the Data Cleansing Type. 6. To enable batch deduplication, set the Deduplication Enable Flag to True. 7. Enter Firstlogic as the Deduplication Data Type. 8. Restart your Siebel Server to enable the change.
)RU LQWHUDFWLYH SURFHVVLQJ
To enable interactive data cleansing and deduplication, follow these steps. 1. Navigate to Administration - Server Configuration > Enterprise > Component Definitions. 2. Select the appropriate component (for example, Sales Object manager). 3. To enable interactive cleansing, set the Data Cleansing Enable Flag to True. 4. Enter Firstlogic as the Data Cleansing Type. 5. To enable interactive deduplication, enter Firstlogic as the Deduplication Data Type. 6. Set the Deduplication Enable Flag to True. 7. Restart your Siebel Server to enable the change.
If you are licensed to use List Import, repeat the previous steps on the following components:
List Import Service Manager Workflow Process Batch Manager Workflow Process Manager
8uhr!)Dhyyhv

If you intend to use the UCM Batch Manager to execute CDM workflows, repeat the previous steps on the UCM Batch Manager component. If you want to use the interactive and batch process on regular CRM data of UCM, you must also configure the UCM Object Manager. For more information, see your Siebel UCM documentation and the Siebel Data Quality Administration, Version 8.0.

&KDSWHU &RQILJXULQJ 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0
Through the installation process, all of the necessary files are configured to properly run BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0. You may, however, change items after installation. If you change settings, refer to this chapter to reconfigure them properly.
8uhr")8svtvt9hhRhyvsPhpyrTvriryV8H

7KH FOLHQW FRQILJXUDWLRQ ILOH

During the installation process, you install the client configuration file (DQClient.xml) to each of the thick clients and to the Siebel server. If your configuration requires any variations from the default settings, you must edit this file.
)RUPDW RI WKH ILOH
DQClient.xml is an XML file. Here are the files contents:
<businessobjects> <DQXI_SERVER_IP>dqxiserver1</DQXI_SERVER_IP> <DQXI_SERVER_PORT>20004</DQXI_SERVER_PORT> <DQXI_INITIALIZATION_DATAFLOW_NAME> projects\blueprints\siebel\read_configuration_file.xml </DQXI_INITIALIZATION_DATAFLOW_NAME> <DQXI_REPOSITORY_PATH>c:\dqxi\11_7\repository\ configuration_rules </DQXI_REPOSITORY_PATH> <DQXI_SUBSTITUTION_FILE>dqxiserver1_substitutions.xml </DQXI_SUBSTITUTION_FILE> </businessobjects>
(GLWLQJ WKH ILOH )LOH SDUDPHWHUV
To edit the file, change the value between the opening and closing parameter tags. The following table explains the parameters and valid values in this file.
Qhhrr
DQXI_SERVER_IP DQXI_SERVER_PORT DQXI_INITIALIZATION _DATAFLOW_NAME
9rpvv
The IP address of the BusinessObjects Data Quality XI Server. The port number of the BusinessObjects Data Quality XI Server. The name and path of the dataflow file that contains the initialization settings for BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0. By default, this setting is projects\blueprints\siebel\read_configuration_file.xml The path to the location of the BusinessObjects Data Quality XI repository folder. The name of the file that contains the BusinessObjects Data Quality XI substitutions for data fields. By default the file is dqxiserver1_substitutions.xml.
DQXI_REPOSITORY _PATH DQXI_SUBSTITUTION _FILE

'HIDXOW 6LHEHO FRQILJXUDWLRQ VXSSRUWHG

Data Quality for Oracles Siebel UCM is designed to work out of the box with Siebels default configuration. However, some Siebel users have customized applications that use specialized Business Components or fields. Siebel Industry Applications usually require some additional configuration. This section explains which business components and fields are supported by default. If your Siebel configuration matches the configuration below, you can move on to Using Data Quality for Oracles Siebel UCM on page 35. If your configuration differs, you will need to perform some additional setup. See Concepts for customized applications on page 47 for further details.
%XVLQHVV FRPSRQHQWV VXSSRUWHG E\ GHIDXOW
The following business components are supported with the default configuration of Data Quality for Oracles Siebel UCM.
Account Business Address Contact List Management Prospective Contact CUT Address (for Vertical) Personal Address (for Horizontal)
8&0 EDWFK REMHFW VXSSRUWHG
The ability to run UCM batch jobs on the following object types is supported with the default configuration of Data Quality for Oracles Siebel UCM.
Account Contact
6LHEHO ILHOGV VXSSRUWHG E\ GHIDXOW
This section discusses fields that are supported with the default configuration of Data Quality for Oracles Siebel UCM. For information on how data quality fields are mapped to Siebel Business Component fields, see the Siebel Data Quality Administration Guide, Version 8.0. If any of the default settings are missing from your configuration, you may need to enter them in the Third Party Administration Field Mappings section for the Business Components and their operations. For example, the Contact Deduplication BC Operation may not include the Primary State and Primary Street Address Field Mappings. If these mappings do not exist, you must add them. For information on adding Field Mappings, see the Siebel Data Quality Administration Guide, Version 8.0.
3DUVLQJ DQG VWDQGDUGL]DWLRQ
Parsing and standardization occurs on the following Siebel fields, by default.

7vrpr
Account
Avryq
Name Location
Contact
Last Name First Name Middle Name Job Title
List Mgmt Prospective Contact
Last Name First Name Middle Name Job Title Account Primary Account Location
$GGUHVV FOHDQVLQJ
Address cleansing occurs on the following Siebel fields, by default.
7vrpr
Business Address CUT Address Personal Address List Mgmt Prospective Contact
Avryq
Street Address Street Address 2 City State Postal Code Country
0DWFKLQJ DQG FRQVROLGDWLRQ
Matching and consolidation occurs on the following Siebel fields, by default.
7vrpr
Account
Avryq
Primary Account Street Address Primary Account City Primary Account State Primary Account Postal Code Primary Account Country Name Location Dedup Token Id

7vrpr
Contact
Avryq
First Name Middle Name Last Name Primary Account Name Account Location Primary Street Address Primary City Primary State Primary Postal Code Primary Country Dedup Token Id
List Mgmt Prospective Contact
First Name Middle Name Last Name Account Primary Account Location Street Address City State Postal Code Country Dedup Token Id

&KDSWHU 8VLQJ 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0
Now that you have finished setting up BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0, you can use its capabilities. For example, you can run a batch session to cleanse all of the records that exist in your database already. Data Quality for Oracles Siebel UCM also includes real-time, interactive processing so you can be sure that new records are properly cleansed on their way in to your Siebel database. This section serves as a supplement to the information found in the Siebel Data Quality Administration Guide, Version 8.0 about running interactive and batch data quality jobs. For detailed, step-by-step instructions on the data quality functionality and running jobs within your Siebel application, see the Siebel documentation.
8uhr#)Vvt9hhRhyvsPhpyrTvriryV8H

,QWHUDFWLYH FOHDQVLQJ ZLWK 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0

Data Quality for Oracles Siebel UCMs interactive or real-time cleansing capability lets your Siebel users cleanse the data at the point of entry into your Siebel database. You can cleanse both name and address data in interactive mode.
8VLQJ LQWHUDFWLYH FOHDQVLQJ
For interactive name and address cleansing, Siebel users need to take no further action. The data is cleansed automatically when they save the record, select another record, or attempt to exit the program. In this example, one of your users adds information for a new account. The data isnt entered properly, and the ZIP code is left blank.
After the user steps off the record or saves the record, the cleansing takes place. When the user returns to the original record, the data is cleansed.
The actual cleansing that takes place varies based on the Siebel screen youre working in and based on any customizations you performed to Data Quality for Oracles Siebel UCM. In this example, the following items were cleansed.
The street name was corrected and properly cased. The city was spelled properly and cased properly. The state was cased properly. The ZIP code was added. The country was spelled out and properly cased.

,QWHUDFWLYH PDWFKLQJ DQG FRQVROLGDWLRQ ZLWK 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0
Data Quality for Oracles Siebel UCMs interactive (or real-time) match/consolidate capability notifies your Siebel users when they enter a record that might already exist in your Siebel database.
3RSXODWH WKH PDWFK NH\ YDOXH
The match key is used during the matching process to help narrow the candidates for potential matches. This makes for quicker matching. This field is automatically populated on records you create after installing Data Quality for Oracles Siebel UCM. To populate the match key value for records in your database prior to installing Data Quality for Oracles Siebel UCM, run an initial match key generation batch job. For information on running an initial match key generation batch job, see the Siebel Data Quality Administration Guide, Version 8.0. The match key value is used only during interactive processing.
,GHQWLI\ GXSOLFDWH UHFRUGV
To identify potentially duplicate records, your Siebel users need to take no extra steps. The potential matches are identified automatically when they save the record, select another record, or attempt to exit the program. To resolve the duplicate, however, your users take an active role. The user can select a matching record to which the current entered record will be merged.
5HPRYH GXSOLFDWH UHFRUGV
After you enter a potentially matching record, the Possible Matching Accounts screen appears.
Uurrpqw rrrqvpvqrrq urhrhqu urr
Qviyrhpuvtrpqhr uurr

To eliminate unwanted duplicate records: 1. To consolidate/merge the record you just created, click Pick. 2. To keep all records shown, click Ignore All. 3. If you keep all records, you can click the hyperlink of the record in the Accounts List, and then click the Duplicate Accounts tab in the bottom section. The potential matching records are shown there. Click Pick to merge the records.

%DWFK SURFHVVLQJ
Batch processing uses jobs to process records within a business component. You can process all the records in a business component or you can select a subset of the available records.
6HWWLQJ WKH :KHUH &ODXVH
The Where Clause option allows you to selectively process records for Data Quality for Oracles Siebel UCM. For example, you can choose to process only records that were updated on or after a certain day. This decision could save processing time, because you wouldnt be processing records that you may have already cleansed. The Where Clause option is set up to operate the same way that the Where Clauses within Siebel server Tasks operate. For more information on clauses and running batch jobs in Siebel, see the Siebel Data Quality Administration Guide, Version 8.0.
%DWFK RSWLRQ FRPSRQHQWV
You can customize the Data Quality Manager batch option components by entering values in the Administration - Server Management > Jobs screen for the following job parameters:
Buscomp Name Business Object Name Data Quality Setting Operation Type
Also, you can create a Where Clause, if necessary.

The following table shows configuration settings for creating Data Quality Manager batch option components for this product.
7pIhrhq 9hhRhyvTrvt 7vrPiwrp Ihr

Accounts: Account Account "",Yes,account_datacleanse.xml" "",Yes,account_match.xml"
Prhv Ur
Data Cleansing DeDuplication
Address datacleanse for horizontal applications: Business Address Personal Address "",Yes,business_address_datacleanse.xml" "",Yes,business_address_datacleanse.xml" Data Cleansing Data Cleansing
Address datacleanse for vertical applications: CUT Address Prospects: List Mgmt Prospective Contact List Mgmt Prospective Contact Contacts: Contact Contact "",Yes,contact_datacleanse.xml" "",Yes,contact_match.xml" Data Cleansing DeDuplication "",Yes,prospect_datacleanse.xml" "",Yes,prospect_match.xml" Data Cleansing DeDuplication "",Yes,business_address_datacleanse.xml" Data Cleansing
Incremental match for Accounts, Prospects, and Contacts: Account List Mgmt Prospective Contact Contact "",No,account_incremental_match.xml" "",No,prospect_incremental_match.xml" "",No,contact_incremental_match.xml" DeDuplication DeDuplication DeDuplication
The syntax of a Data Quality Setting must be precise. Any error in the syntax could cause inaccurate results or cause a batch job to fail.
&UHDWLQJ D QHZ EDWFK MRE
To create a new batch job: 1. From your Siebel application, navigate to Administration - Server Management > Jobs.
From here you can create new batch jobs or view the results of a previous batch run.
2. In the Jobs screen, click the New button to create a new job. 3. From the Component/Job field of your new job, select Data Quality Manager.
4. In the Job Parameters frame, click New to create a new job parameter. 5. For the Name field, select the following parameters: Buscomp Name Business Object Name Operation Type Data Quality Setting
6. In the Value field for each Name field parameter, enter an appropriate value for the component you want to create.
5XQQLQJ D EDWFK MRE
If you just created a new batch job and are already in the Jobs screen with the current job is selected, click Submit Job to run your batch job. If you are not currently in the Jobs screen, follow this procedure.
To run a batch job: 1. From your Siebel application, choose Administration - Server Configuration. 2. Access the Job Detail menu. 3. Select the job you want to run. 4. Click Submit Job to start the batch process.
You can refresh the view to check the jobs status.
5XQQLQJ WKH EDWFK SURFHVV IURP WKH FRPPDQG OLQH
You can also run a batch process request from the command line. To run a batch process from the command line, enter the following commands and enter information appropriate for your system in place of the italicized items. 1. Go to the /bin subdirectory beneath the Siebel installation location on your Siebel Server. 2. Enter the following command: srvrmgr /g gateway server name /e enterprise server name /u username /p password /s Siebel Server name /l language (ENU for English) 3. For each batch task, type the following: run task for comp DQMgr with BCName = Buscomp Name, BobjName = Business Object Name, OpType = Operation Type, ObjWhereClause= Object Where Clause, ObjSortClause = Object Sorting Clause, ConnectStr = Connect String, DQSetting = Data Quality Value

,QFUHPHQWDO 'DWD 0DWFKLQJ MREV
Incremental Data Matching jobs can be performed if you want to perform matching for a subset of records in the database. For example, if you want to perform matching on just the records that have been updated today, you could include the Object Where Clause job parameter with the following value:
[Updated] = Today()
This job parameter requires all of the records that were updated today to be used as master records. The job run then searches the entire database for potential duplicates to the master records (including duplicates within the restrictions of the Where Clause; in this instance, those updated today are compared against each other as possible duplicates). Because of this Object Where Clause, the job run does not check the records that existed before today to find potential duplicates for them. It compares only preexisting records to find duplicates to the master records. Presumably, records that existed before today have already been processed for duplicates, and in this job you want to process only the new records, providing an efficiently smaller group to be processed. In this example, the Data Quality setting would be different than those listed in Batch option components on page 39. You would use a *_incremental_*.xml dataflow and the setting No instead of Yes as the second value.
%DWFK MREV ZLWK WKH 8&0 %DWFK 0DQDJHU
Siebel UCM offers a Batch Manager for the execution of batch jobs. The capability of Data Quality for Oracles Siebel UCM can be employed to provide data quality operations on your UCM data management operations. This section discusses the Batch Manager as used with Data Quality functionality. For specific details in running jobs with the UCM Batch Manager, see the documentation for Siebel Universal Customer Master at the Siebel Bookshelf. For example, through the UCM load process you might have incomplete or inaccurate records to upload to a Siebel database. You can run the UCM Batch Manager with the necessary UCM parameters to cleanse the incoming data and perform a match against the existing data. In this example, the UCM job is run for Account UCM on all the records that are Queued-Insert.

When the UCM Batch Manager operation completes successfully, the data from the SDH table is successfully cleansed and consolidated to give the best record, as per the UCM process. Some records from the SDH table require manual intervention to create the best version of the record. To understand the consolidation of records that may be matches, see Consolidation after batch match on page 45.

%DWFK MRE FRQVLGHUDWLRQV

When running batch jobs, you should consider the following issues.
&OHDQVLQJ EXVLQHVV FRPSRQHQWV LQ SURSHU RUGHU
You should always perform address cleansing before parsing and standardization. Before running batch match/consolidate for the first time, you must run batch address cleansing and parsing and standardization. If you plan to cleanse both the Contact and Account Business Components, you must cleanse Account first. Contact uses a calculated value to determine its internally stored Match Candidate Token. This calculation uses data from the account that the contact is associated with. Therefore, to keep this field up to date, Account must be cleansed before Contact.
5XQQLQJ EDWFK SURFHVVHV VLPXOWDQHRXVO\ $YRLG FOHDQVLQJ WKH VLHEHO DGPLQLVWUDWRU UHFRUG
You cannot run more than one batch process simultaneously.
The read-only siebel administrator record must not be subjected to cleansing. Since this record is dated January 1, 1980, a simple method to exclude this record from the batch process would be to set a Where Clause that allows only records that take place after this date to be processed. For example:
[Created] >= 1/2/80
This syntax requires that only records with a creation date on or after 1/2/80 are processed. Any date after 1/1/80 but before the earliest creation date of other records would produce the same result.

&RQVROLGDWLRQ DIWHU EDWFK PDWFK

By consolidating records, you get to choose which master record to keep. This section explains how to consolidate your records by viewing the records and merging duplicate records.
9LHZLQJ GXSOLFDWH UHFRUGV
After running the batch matching process, you can view the records that were identified as matches. Choose Navigate > Site Map > Administration - Data Quality.
0HUJH GXSOLFDWH UHFRUGV
To merge duplicate records in either the Duplicate Accounts, Duplicate Contacts, or Duplicate Prospects screen: 1. Click the hyperlink of a record. A Duplicate Resolution screen appears. 2. In the Sequence field, enter the sequence number for the record. Enter 1 for the master record, or the record you want to keep. Enter 2 (or 3, 4, and so on) for the subordinate records that will be merged into the main record. 3. Highlight all of the records in the group you want to merge. 4. Click Merge. The master record (that is, the record you assigned 1 in the Sequence field) is retained, with any missing fields in the record populated by data from the other records in the order of sequence.
)RU 8&0 %DWFK 0DQDJHU
During the UCM batch process, any records that require manual intervention are queued in the Incoming Duplicates view in the Administration - Universal Customer Master screen. You can manually review and resolve the duplicates that are identified in the UCM batch process. For details on this process, see the Siebel UCM documentation.

&KDSWHU &RQFHSWV IRU FXVWRPL]HG DSSOLFDWLRQV
BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0 is designed to work with Siebels default configuration, but users who have custom fields or business components may need to perform some individual configuration. If you have a Siebel application in which you have renamed or added a Business Component or field, there are some concepts with which you should become familiar.
%XVLQHVV 2EMHFWV *OREDO 6HUYLFHV
Some customizations to the default configuration can be problematic. Before proceeding on your own with far-reaching customizations, you should contact Business Objects Global Services. Contact your Account Manager or Business Objects Customer Service to find out more about Business Objects Global Services.
8uhr$)8prspvrqhyvphv

0DVWHU FRQILJXUDWLRQ
The basic configuration of Data Quality for Oracles Siebel UCM is handled in the BusinessObjects Data Quality XI Project Architect. In the Project Architect, open configuration_rules\dataflow_objects\shared_options\ siebel_connector_base.
Once selected, siebel_connector_base appears in the Option Explorer and Option Editor.
From here, you make the master configurations to Data Quality for Oracles Siebel UCM. The configuration settings are recorded in the file DQinstall\repository\ configuration_rules\dataflow_objects\shared_options\ siebel_connector_base.xml. You should back up the file before making any changes. The major sections in these options group settings are the following: configurations settings, Business Components, and substitution list settings.

&RQILJXUDWLRQ RSWLRQV
Within the configuration options, you can make changes to the basic configuration, business components, and substitution values. This section details the configuration options available. This table lists the settings for the SIEBEL_CONNECTOR option.
6,(%(/B&211(&725
Pv
VERSION_NUMBER REVISION_NUMBER SIEBEL_MAJOR_VERSION SIEBEL_MINOR_VERSION LOG_LEVEL
Whyvqhyr
11.7.0 1 8 0 1-5
9rpvv
Version number of this product. Revision number of this product. Siebel major version number. Siebel minor version number (reserved for future use). Level of detail to be written to log files. A higher number gives a higher level of detail. Level 2 is the minimum to log errors and warnings. The default is Level 3. Directory in which log files are created. Log files by default are created in the siebsrvr\log directory. The number of log files to keep before the oldest log file is deleted. Maximum number of KB for a single log file. After maximum is reached, a new log file is created. The number of initialization log files to keep before the oldest log file is deleted. The number of seconds the connection to the BusinessObjects Data Quality XI Server is kept open with no data traffic. Range of ports the BusinessObjects Data Quality XI Server uses to communicate back to the portion of this product integrated within your Siebel software. This is the minimum range. If the port is busy it will look for an open port until it reaches maximum range defined. Range of ports the BusinessObjects Data Quality XI Server uses to communicate back to the portion of this product integrated within your Siebel software. This is the maximum range. If the port is busy, the Siebel application looks for an open port until it reaches maximum range defined. The number of records that can be queued in memory waiting for transmission over the network to the BusinessObjects Data Quality XI Server. The number of seconds to sleep before checking if the number of records in memory has dwindled below the BATCH_MATCH_RECORDS_TO_QUEUE limit. The minimum number of seconds between launching batch jobs.
LOG_DIRECTORY LOGS_TO_KEEP LOG_SIZE NUMBER_OF_INITIALIZATION_ LOG_MESSAGES_TO_KEEP CONNECTION_TIMEOUT
Any valid directory Any valid integer Any valid integer (KB) Any valid integer Any valid integer (seconds)
BATCH_LOW_PORT
A valid port number
BATCH_HIGH_PORT
A valid port number
BATCH_MAX_RECORDS_TO_ QUEUE BATCH_CHECK_QUEUE_SIZE_ INTERVAL MIN_INTERVAL_BETWEEN_ BATCHES
A valid integer
A valid integer (seconds)
A valid integer (seconds)

Pv
Whyvqhyr
9rpvv
Determines if an address warning is returned to the user when an address is unable to be thoroughly cleansed. The behavior is different depending on whether you run Siebel UCM or Siebel CRM. On CRM systems, setting to True allows a message to be displayed to the user when an invalid address is entered transactionally. It does not affect CRM batch processes. For UCM systems, this value must be set to False. Otherwise, the UCM upload process fails, as Siebels UCM upload process is unable to accept any warnings and continue. Even if you are using the UCM upload process in combination with Siebel CRM, this value must be set to False. In all cases, when the log level is set accordingly, users still see any address fault code in the logs within the <DQ.FaultCode> tag, as the record is returned from BusinessObjects Data Quality XI.
DISPLAY_ADDRESS_WARNING_ True or False MESSAGES
%XVLQHVV FRPSRQHQW RSWLRQV
The Business Component (BC) settings include details about each business component you want to cleanse or deduplicate. These settings are primarily useful in interactive data quality, because they indicate which dataflow is used for the current business component. Each BC entry has the following settings to define the name of the BC and the Business Object to which the BC belongs. BC_NAMEName of the Business Component. BO_NAMEName of the Business Object (to which the BC belongs). If you want to do interactive data cleansing on a given BC, then add the <INTERACTIVE_DATA_CLEANSE> section to the file. If you want to do interactive matching on a given BC, then add the <INTERACTIVE_MATCH> section to the file. If you do not want to do these operations, then do not add the relevant section (or remove it if it already exists). There are no configuration options required to do batch processing on a given BC; therefore, no entries are required here. The options for each section are as follows. INTERACTIVE_DATA_CLEANSEThis section sets the dataflow and options used during an interactive data cleanse for the BC.
Pv
DATAFLOW_NAME
9rpvv
Name of the dataflow with relative path from the projects folder.
INTERACTIVE_MATCHThis section sets the dataflow and options used during an interactive data matching for BC. The option used by this product is listed in following table. Any other options visible in the interface are not used in this product.

Pv
DATAFLOW_NAME
9rpvv
Name of the dataflow with relative path from the projects folder.
6XEVWLWXWLRQ OLVW RSWLRQV
The substitution list allows you to substitute or translate the spaces and special characters used in a BC Name or Field Name. This solution is required because Siebel allows spaces and special characters in BC names and Field names, but XML and BusinessObjects Data Quality XI do not. BusinessObjects Data Quality XI uses the INPUT_FIELD_NAME to define the BC Name and Field Name in which a dataflow operates. Therefore, you must define any BC Name and Field Name with spaces or special characters here with a substituted name. BC_SUBSTITUTIONThis section has two options for business component name substitutions.
Pv
SIEBEL_BC_NAME IQ8_BC_NAME
9rpvv
Actual BC name as it appears in Siebel Tools. Note that any space character must be replaced by _spc. Substituted BC NAME that is be used in the Dataflows INPUT_FIELD_NAME option instead of using the Actual Siebel BC name. This allows BusinessObjects Data Quality XI to avoid all special characters and spaces that are not permitted in XML notation.
FIELD_SUBSTITUTIONThis section has two options for business component name substitutions.
Pv
9rpvv
SIEBEL_FIELD_NAME Actual field name as it appears in Siebel Tools. Note that any space character must be replaced by _spc. IQ8_FIELD_NAME Substituted field name that is be used in the Dataflows INPUT_FIELD_NAME option instead of using the Actual Siebel field name. This allows BusinessObjects Data Quality XI to avoid all special characters and spaces that are not permitted in XML notation.
You need to create only one entry of field name, even though the field name might appear in different Business component field names. You should add substituted names only as they are needed.

'DWDIORZ LQSXWRXWSXW ILHOG QDPHV

The BusinessObjects Data Quality XI Server uses input fields and output fields to process data that it receives from or sends to Siebel. When you have Siebel fields that youve customized, youll need to edit the input field names/output field names, or add new ones.
$GG D QHZ ILHOG
The procedure for adding a field is documented in the BusinessObjects Data Quality XI Data Cleanse Modifiers Guide. This section describes issues unique to adding a field for Data Quality for Oracles Siebel UCM. A field name for Data Quality for Oracles Siebel UCM has the following naming structure:
[BC_name].[field_name]
For example, an input for the account_datacleanse dataflow is Account.Name. Here, Account is the Business Component name and Name is the field name. When you add a new field, you must use this naming convention, as it corresponds with the structure of field names in Siebel. If a field does not correspond to a Siebel Business Component name (that is, it is used internally by BusinessObjects Data Quality XI, it is give the BC_name DQ. If you add a field name to BusinessObjects Data Quality XI that includes spaces or special characters, you must also make an entry in the substitution list. For more information on the substitution list, see Substitution list options on page 51.
5HPRYH D ILHOG
To remove a field from a dataflow, simply delete the field within the BusinessObjects Data Quality XI Project Architect.

([DPSOH DGGLQJ QHZ ILHOGV IRU FOHDQVLQJPDWFKLQJ

This section provides a sample procedure for adding new fields for cleansing or matching. This sample procedure adds a field for Email Address to a Contact Business Component. This sample is for reference purposes only. Before adding new fields to your Siebel application, consult the Siebel Data Quality Administration Guide, Version 8.0. To add a field for Email Address to a Contact Business Component: 1. From your Siebel application, navigate to Administration - Data Quality > Third Party Administration. 2. Highlight the Firstlogic/DQClient Vendor record. 3. Highlight the Contact/Data Cleansing record in the BC Vendor Field Mapping section. 4. In the Field Mappings section, add a new record for Email Address.
5. Restart the Siebel server. The Siebel server is now able to send the value of the Contacts Email Address field to BusinessObjects Data Quality XI, where data quality operations can be performed on the data. However, you must configure BusinessObjects Data Quality XI to work with this data. For thorough procedures for configuring BusinessObjects Data Quality XI, see the documentation that ships with that portion of this product. 6. In BusinessObjects Data Quality XI, open the Project Architect and navigate to projects > blueprints > siebel. Select the dataflow transactional_contact_datacleanse. For reference information about the dataflows installed with this product, see Business component and dataflow reference on page 65.

7. Add the email address field to the reader, writer, and datacleanse dataflows. Whenever you use any spaces or special characters with added fields, you must also update siebel_connector_base.xml. In this example, the field Email Address uses a space. You must also make this change in the substitutions list. 8. Add a substitution in siebel_connector_base.xml. (For details, see Substitution list options on page 51.) Siebels naming convention requires that you replace a space character with _spc. The Siebel Contact Business Component and the BusinessObjects Data Quality XI dataflow transactional_contact_datacleanse are now capable of working with an Email Address field.

:RUNLQJ ZLWK DGGUHVVFOHDQVLQJ HUURUV

With Data Quality for Oracles Siebel UCM, you have some flexibility for how address-cleansing errors are handled. For example, you can return an error code to a Siebel field or you can suppress which errors are returned in interactive mode. This section explains how to handle these situations. The handling of address-cleansing errors differs in Siebel UCM and Siebel CRM during transactional processing. If an address-cleansing error occurs in a Siebel CRM system, the system can display an error message. The system does not display an error message in Siebel UCM.
3RVWLQJ DGGUHVV HUURUV WR \RXU 6LHEHO GDWDEDVH
In batch mode, you can return address-cleansing error codes or descriptions directly to a field in your Siebel database. This can be useful if you want to run a query and find all of the records in your Siebel database that contain some sort of address error. To post address errors to your Siebel database, follow these steps. 1. Add a new field to your Siebel business component that will contain these address errors (Address Error Message, for example) 2. In the BusinessObjects Data Quality XI Project Architect, open the appropriate dataflow (for example, business_address_datacleanse). 3. In the Writer transform, copy the gen.err_message output field and paste to the transform. 4. In the new output entry, change the OUTPUT_FIELD_NAME option to the field name you added to your Siebel business component. (The name must be in the format business_component.field_name.) 5. Save your changes. After following these steps, when you run a batch process of Data Quality for Oracles Siebel UCM, any address-cleansing error messages will be written to this field.
&XVWRPL]LQJ DQG VXSSUHVVLQJ HUURU PHVVDJHV
You can customize the error messages that appear during batch or interactive cleansing, or even suppress an error message to prevent BusinessObjects Data Quality XI from skipping the cleansing process on a record that produced the error. To customize or suppress error messages, you must use the BusinessObjects Data Quality XI Python Editor. For information on the Python Editor, see the BusinessObjects Data Quality XI documentation. In the Python editor, open the transform Frmt Errorcode in a dataflow. The transform lists the error code and message. From here, you can directly edit an error message, or suppress an error by commenting out the error code and message.

&KDSWHU 7LSV DQG WURXEOHVKRRWLQJ
This chapter includes information on troubleshooting errors and known issues within BusinessObjects Data Quality Management for Oracles Siebel UCM 8.0. It also includes tips for using this product.
8uhr%)Uvhqiyruvt

3DUVLQJ DQG VWDQGDUGL]DWLRQ

The following tips and troubleshooting suggestions apply only to the parsing and standardization data cleansing transform of Data Quality for Oracles Siebel UCM.
(UURU RQ 00 ILHOG
If you set your dataflows to standardize data to all upper, or all lower case, you may receive errors in your M/M (Mr./Ms.) field. This error occurs because the value in the field will not match the value in the Pick List M/M. To resolve this issue, you can add the appropriately-cased values to your list of values for the M/M field. Alternatively, if your business process allows, you can instead unbind the Picklist M/M pick lists through Siebel Tools.

%XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;,

The following tips and troubleshooting suggestions apply to the BusinessObjects Data Quality XI portion of this problem. For additional information about BusinessObjects Data Quality XI, see the BusinessObjects Data Quality XI documentation.
%XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, FRQQHFWLRQ WURXEOHV
If you having trouble connecting to BusinessObjects Data Quality XI (for example, you are unable to log in or data is not getting cleansed), check your connection to BusinessObjects Data Quality XI. To verify that the BusinessObjects Data Quality XI Server is running, open a command prompt and navigate to \siebsrvr\bin. Run DQTestConnect.exe. This program uses the connectivity options in DQClient.xml to attempt to connect to the BusinessObjects Data Quality XI Server. Use DQTestConnect.exe with the following argument: DQTestConnect [configuration_file_path] The argument [configuration_file_path] is optional. If this argument is not supplied, the default path ./DQClient.xml is used.
/RJJLQJ
If you have trouble with BusinessObjects Data Quality XI, set the configuration option for <LOG_LEVEL> to the value of 5 in the siebel_connector_base shared options. This setting allows the highest level of logging. For more information, see Master configuration on page 48. Log files are generated in the siebsrvr/log directory in the form DQ_Log_*.xml. The log files DQ_Log_Init_*.xml contains the initialization log messages. The first DQ_Log_Init_*.xml is generated, filling up a number of messages specified by the setting <NUMBER_OF_INITIALIZATION_LOG_MESSAGES_TO_KEEP>, then the next DQ_Log_*.xml files is created. If the portion of this product installed on your Siebel system can not initialize properly (and potentially can not open a normal DQ_Log_*.xml type log file), the system then generates DQ_Error_*.log files in .../siebsrvr/bin. The log files in the siebsrvr/log directory may also direct you to check the BusinessObjects Data Quality XI logs files. If your address directories expire (for example), the error is recorded in the BusinessObjects Data Quality XI log files. For more information about BusinessObjects Data Quality XI log files, consult the BusinessObjects Data Quality XI documentation.
&UDVK RQ '4;, VHUYLFH
If you receive a message that the DQXI service has crashed, then your BusinessObjects Data Quality XI Server has crashed. This crash can happen during interactive data cleanse or matching. It can be caused by the use of invalid postal directories or by using an invalid path to the postal directories. You should check the substitution settings on your dataflow to make sure the path to the postal directories is specified and correct. If your postal directories are located on a different machine than the BusinessObjects Data Quality XI Server, make sure your Data Quality Windows
8uhr%)Uvhqiyruvt

service account is set to a local system account and that the path in the substitution setting is a UNC path, rather than a mapped network directory.
$GGUHVV FOHDQVH WUDQVIRUP FKDQJH PH VHWWLQJ
When viewing an address cleanse transform in the BusinessObjects Data Quality XI Project Architect to see which transforms are enabled, you might see that some transforms report change me as the setting. This is a known issue with the BusinessObjects Data Quality XI Project Architect. Change the value to Yes or No and the value will be saved. The next time you open the Project Architect, the value again appears as change me. However, the value last set (Yes or No) remains intact the application functions according to that value, despite the display in the Project Architect.
7UDQVDFWLRQ GDWDIORZV
All transactional dataflows must contain the Determine Data Last Modified transform. All transactional dataflows included in the installation contain this transform. Any transactional dataflows that you create must use this transform. This requirement is specific to Siebel. It does not apply to dataflows used outside of Siebel.

$GGUHVV FOHDQVLQJ
The following tips and troubleshooting suggestions apply only to the addresscleansing transforms of Data Quality for Oracles Siebel UCM.
HUURU
If you regularly receive 1030 errors (No country found by Country ID or no country set for the record) through the address-cleansing transforms, be sure that you are entering a country with your address. The address-cleansing transforms requires that the country is present. To help avoid this, set a default country for your country field or be sure to make this a required field so it isnt skipped during data entry.
(UURU RQ 6WDWH RU &RXQWU\ ILHOGV
If your addresses are consistently not cleansed, or if you receive errors on the SetFieldValue() function for the State and Country fields, you likely need to add some values to your list of values for those fields. You will most likely receive the errors on the State field if you have international addresses and the appropriate states for those addresses are not in your list of values. To eliminate errors, add the appropriate states, provinces, and so on. For the Country field, be sure to add United States to your list of values. (Siebel has only USA by default.) You have two alternatives. First, if your business process allows, you can instead unbind the Picklist State and Picklist Country pick lists through Siebel Tools. (See your Siebel documentation for instructions of using Siebel Tools.) Second, you could change the address cleanse dataflow to return USA instead of United States. The following is an example of Python code in the business address and prospect datacleanse transforms (for example, the Format Address Fields transform in business_address_datacleanse.xml) which you could modify if you use bounded picklists for country values. The code changes the input of United States (as well as Puerto Rico, Guam, and Virgin Islands) to the output of USA. It makes similar changes to output Ireland and Hong King when receiving slightly different inputs.
# populate country temp_country = INPUT_GEN_COUNTRY.strip() if temp_country == United States or temp_country == Puerto Rico or temp_country == Guam or temp_country == Virgin Islands (us): OUTPUT_COUNTRY = USA elif temp_country == Irish Republic: OUTPUT_COUNTRY = Ireland elif temp_country == Hong Kong, China: OUTPUT_COUNTRY = Hong Kong elif len(temp_country.strip()) == 0: OUTPUT_COUNTRY = INPUT_COUNTRY else: OUTPUT_COUNTRY = INPUT_GEN_COUNTRY
8uhr%)Uvhqiyruvt

0DWFKFRQVROLGDWH
The following tips and troubleshooting suggestions apply only to the match/ consolidate transforms of Data Quality for Oracles Siebel UCM.
,QWHUDFWLYH PDWFKLQJ VHHPV XQXVXDOO\ VORZ
If interactive matching seems to be running unusually slow, one place to check is your siebel.cfg file. Look for the CaseInsensitive parameter. If this is set to True, this will cause multiple unindexed queries to the database for each (normal) query. For further details, consult your Siebel Applications Administration Guide in your Siebel Bookshelf.

%DWFK SURFHVVLQJ HUURUV

Here are some solutions to batch-processing errors you might encounter.
3UREOHPV SURFHVVLQJ ODUJH UHFRUG VHWV
If your object manager returns this error message: There were more rows than could be returned. Please refine your query to bring back fewer rows, you may have encountered Siebels 10,000 record restriction. To remove the 10,000 record restriction, set the following parameter in the data source section of the relevant configuration file for the data source.
MaxFetchArraySize = -1
For the connected Web Client, navigate to Server Administration > Enterprise Configuration > Enterprise Profile Configuration > Component Profiles > ServerDataSrc. Set the DSMaxFetchArraySize parameter to -1.
0DWFK .H\ *HQHUDWLRQ
Match key generation is handled within the Siebel system. To understand when and how the keys for data matching are generated, and how to generate and refresh the keys used for matching, see the Siebel Data Quality Administration Guide, Version 8.0.
8uhr%)Uvhqiyruvt

&OLHQW DQG VHUYHU LVVXHV

The following item applies to situations that arise with client and server communication.
&OLHQW KDQJV
If your client seems to hang or freeze when you start it up, check to see if your Data Quality for Oracles Siebel UCM server is running. If the server isnt running, the client waits a while to see if the server gets started. Eventually, this process times out and returns an error message. Before time-out, however, it may seem as if your client is hanging. The BusinessObjects Data Quality XI Server hangs when it attempts to connect to the relational database on startup, but the database server is not running before the BusinessObjects Data Quality XI Server. You can remedy this problem by setting up a dependency between services in Windows so that the BusinessObjects Data Quality XI Server does not attempt to start until your database server (also running as a service) has started. To configure the service dependency, open the Registry Editor and open the key HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Services\ ServiceName, where ServiceName is the service you want to delay. By default, the installer calls it dqxiserver1. However, when you install, you may choose a different name, so you must use whatever name you chose for the service. Add a REG_MULTI_SZ value named DependOnService to the key, then edit the value of DependOnService to add the service name of the service you want started before the selected service. If you use SQL Server, the name is MSSQLSERVER. For Oracle and DB2, you should be able to do the same. After rebooting the machine, the dqxiserver1 service (if you have named your BusinessObjects Data Quality XI Server dqxiserver1 or accepted default setting while installing the BusinessObjects Data Quality XI Server) starts correctly, as long as it was set up to start automatically.
&OLHQW KDQJV'DWD 4XDOLW\ 6HUYHU ZLQGRZV 6HUYLFH QRW VWDUWHG DXWRPDWLFDOO\

$SSHQGL[ $ 5HIHUHQFH
%XVLQHVV FRPSRQHQW DQG GDWDIORZ UHIHUHQFH
This table explains the dataflows associated with each business component, along with its type and purpose. It can be used as reference while editing an existing dataflow, while adding fields for cleansing/matching, to make a new dataflow, and so on. After you properly install this product, all the dataflows listed here are available in the BusinessObjects Data Quality XI Project Architect at Configuration_Rules > projects > blueprints > siebel.
7vr 8r
-
9hhsy
read_configuration_file
Ur
Qr
Interactive This is the initialization dataflow that reads the configuration settings in siebel_connector_base (in shared_options) and sends the settings to Siebel. It is the first dataflow called by Siebel. Batch Batch Use this dataflow to cleanse name/firm on the Account Business Component. Use this dataflow to find matches on Account Records. Results are stored in s_dedup_result table for manual review and resolving the records one at a time. It uses the Account Business Component. Use this dataflow as you would account_match, except it allows you to define a more limited set of records for which to find duplicates.
Account Account
account_datacleanse account_match
Account
account_incremental_match
Batch
Account
transactional_account_datacleanse Interactive Use this dataflow to cleanse name/firm when data are entered interactively. It uses the Account Business Component. It is used for UCM Account cleansing. transactional_account_match Interactive Use this dataflow to find the matching accounts while data are entered interactively. It uses the Account Business Component. It is used for UCM Account matching. Interactive Use this dataflow to cleanse Address when data is entered interactively. This dataflow uses the Business Address Business Component. It is used for Siebel Horizontal Applications. It is used for UCM Address cleansing. Batch Use this dataflow to cleanse address on the Business Address Business Component. This dataflow is used for Siebel Horizontal Applications. Use this dataflow to cleanse name/firm on the Contact Business Component.
Account
Business Address
transactional_business_address _datacleanse
Business Address Contact
business_address_datacleanse
contact_datacleanse
Batch

7vr 8r
Contact
9hhsy
contact_match
Ur
Batch
Qr
Use this dataflow to find matches on Contact Records. Results are stored in the s_dedup_result table for manual review and resolving the records one at a time. It uses the Contact Business Component. Use this dataflow as you would contact_match, except it allows you to define a more limited set of records for which to find duplicates.
Contact
contact_incremental_match
Batch
Contact
transactional_contact_datacleanse
Interactive Use this dataflow to cleanse name/firm when data are entered interactively. This dataflow uses the Contact Business Component. It is used for UCM Contact cleansing. Interactive Use this dataflow to find the matching Contacts while data are entered interactively. This dataflow uses the Contact Business Component. It is used for UCM Contact matching. Interactive Use this dataflow to cleanse Address when data is entered interactively. This dataflow uses the CUT Address Business Component. It is used for Siebel Industry Solutions Applications. It is used for UCM Address Cleansing. Batch Use this dataflow to cleanse Address on CUT Address Business Component. It is used for Siebel Industry Solutions Applications. Use this dataflow to cleanse name/firm on the List Mgmt Prospective Contact Business Component. Use this dataflow to find matches on the List Mgmt Prospective Contact Records. Results are stored in the s_dedup_result table for manual review and resolving the records one at a time. By default, this dataflow uses Siebels List Mgmt Prospect Contact Business Component. Use this dataflow as you would prospect_match, except it allows you to define a more limited set of records for which to find duplicates.
Contact
transactional_contact_match
CUT Address
transactional_business_address _datacleanse
CUT Address
business_address_datacleanse
List Mgmt Prospective Contact List Mgmt Prospective Contact
prospect_datacleanse
Batch
prospect_match
Batch
List Mgmt Prospective Contact List Mgmt Prospective Contact List Mgmt Prospective Contact Personal Address Personal Address
prospect_incremental_match
Batch
transactional_prospect _datacleanse transactional_prospect_match
Interactive Use this dataflow to cleanse name/firm when data is entered interactively. This dataflow uses the List Mgmt Prospective Contact Business Component. Interactive Use this dataflow to find the matching List Mgmt Prospective Contacts while data are entered interactively. This dataflow uses the List Mgmt Prospective Contact Business Component. Interactive Use this dataflow to cleanse addresses when data is entered interactively through the Personal Address BC. This BC is applicable for Horizontal Applications only. Batch Use this dataflow to cleanse addresses in batch mode through the Personal Address BC. This BC is applicable for Horizontal Applications only.
transactional_business_address _datacleanse business_address_datacleanse

,QGH[
$
Account business component, 31 address cleansing, 32, 36 disable unused engines, 22 overview, 13 address-cleansing errors, 55 audience, 7
consolidation of records, 12 Contact business component, 31 customized application, 47 CUT Address Buscomp name, 40 business component, 31
'
Data Cleansing Enable Flag, 27 Data Cleansing Type, 27 data quality enable in Siebel, 26 Data Quality Manager batch option components, 40 dataflows copy to BusinessObjects Data Quality XI, 21 input/output field names, 52 reference, 65 transational, 60 Deduplication Data Type, 27 deduplication. See also matching duplicate records removing, 37 viewing, 45
%
batch option components, 39 batch processing, 39 considerations, 44 errors, 63 match/consolidate, 45 simultaneously, 44 Business Address business component, 31 business component options, 50 reference, 65 supported, 31 business rules, 13 BusinessObjects Data Quality XI add/remove dataflow fields, 52 after installing, 22 dataflows, 21 documentation, 15 installation, 21 introduction to, 14 Project Architect, 48 siebel_connector_base, 48
(
error messages, 55
)
fields Siebel, 31 Firstlogic, 13
&
client, 19 command line batch process, 41 configuration default, 31 Siebel, 31 supported, 31 configuration file DQClient.xml, 30 Siebel, 26 configuration options SIEBEL_CONNECTOR, 49 consolidation manual, 45
,
Incremental Data Matching, 42 installation BusinessObjects Data Quality XI, 21 process overview, 20 scenario, 19 to Siebel system, 22 interactive cleansing, 36 match/consolidate, 37
/
List Management Prospective Contact business component, 31
Dqr

0
match key generation, 63 value, 37 match/consolidate, 32 interactive, 37 matching, 11 merge batch, 45 merge. See also consolidation of records
requirements operating system, 18
6
server DQ Link, 20 Siebel configuration file, 26 Siebel Data Quality Universal Connector, 13 siebel_connector_base, 48 standardization, 11 substitution list, 51 options, 51
2
overview, 9 data quality, 10 matching, 11 parsing, 10 standardization, 11
7
thick client connected, 19 remote, 19 thin client, 19
3
parsing, 10 parsing and standardization, 31, 36 overview, 13 Personal Address business component, 31 Preface, 7 Project Architect, 48
9
versions Siebel, 7
:
Where Clause, 39
5
reference dataflows, 65
=
zero-footprint client, 19


DQ Xi Seiebel Ucm - User Guide

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

DQ Xi Seiebel Ucm - User Guide

Загружено:

Авторское право:

Доступные форматы

BusinessObjects Data Quality Management for Oracles Siebel UCM 8.

Data Quality for Oracles Siebel UCM 11.7.0.0 April 2008

$ERXW WKLV JXLGH

$FFHVV WKH ODWHVW %XVLQHVV REMHFWV GRFXPHQWDWLRQ

'DWD TXDOLW\ RYHUYLHZ

:KDW VWHSV DUH LQYROYHG LQ GDWD TXDOLW\"

:KDW LV 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0"

3DUVLQJ DQG VWDQGDUGL]DWLRQ WUDQVIRUPV

)OH[LEOH EXVLQHVV UXOHV DQG FRQILJXUDWLRQ

,QWURGXFWLRQ WR %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;,

&HQWUDOL]HG EXVLQHVV UXOH UHSRVLWRU\

0RUH LQIRUPDWLRQ DERXW %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;,

$FFHVV %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, GRFXPHQWDWLRQ

6\VWHP UHTXLUHPHQWV RQ \RXU 6LHEHO V\VWHPV

Windows 2000 Windows 2003 Windows 2000 Windows XP

6XSSRUWHG FOLHQW RSHUDWLQJ V\VWHPV

0RELOH WKLFN FOLHQWV

7KH LQVWDOODWLRQ SURFHVV

6WHS  $SSOLFDWLRQ $GPLQLVWUDWLRQ VHWXS

%XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, LQVWDOODWLRQ QRWHV DQG SURFHGXUHV

%XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, LQVWDOO PDFKLQH

%XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, SUHYLRXVO\ LQVWDOOHG

&RS\ GDWDIORZV DQG WUDQVIRUPV WR %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, LQVWDOODWLRQ

6WDUW WKH %XVLQHVV2EMHFWV 'DWD 4XDOLW\ ;, 6HUYHU

(GLW WKH 6LHEHO FRQILJXUDWLRQ ILOH IRU FOLHQWV

)RU LQWHUDFWLYH SURFHVVLQJ

&KDSWHU  &RQILJXULQJ 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0

7KH FOLHQW FRQILJXUDWLRQ ILOH

DQClient.xml is an XML file. Here are the files contents:

(GLWLQJ WKH ILOH )LOH SDUDPHWHUV

DQXI_REPOSITORY _PATH DQXI_SUBSTITUTION _FILE

'HIDXOW 6LHEHO FRQILJXUDWLRQ VXSSRUWHG

8&0 EDWFK REMHFW VXSSRUWHG

6LHEHO ILHOGV VXSSRUWHG E\ GHIDXOW

3DUVLQJ DQG VWDQGDUGL]DWLRQ

Parsing and standardization occurs on the following Siebel fields, by default.

Last Name First Name Middle Name Job Title

List Mgmt Prospective Contact

Address cleansing occurs on the following Siebel fields, by default.

0DWFKLQJ DQG FRQVROLGDWLRQ

Matching and consolidation occurs on the following Siebel fields, by default.

List Mgmt Prospective Contact

&KDSWHU  8VLQJ 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0

,QWHUDFWLYH FOHDQVLQJ ZLWK 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0

,GHQWLI\ GXSOLFDWH UHFRUGV

5HPRYH GXSOLFDWH UHFRUGV

Uurrpqw rrrqvpvqrrq urhrhqu urr

%DWFK RSWLRQ FRPSRQHQWV

Also, you can create a Where Clause, if necessary.

7pIhrhq 9hhRhyvTrvt 7vrPiwrp Ihr

Data Cleansing DeDuplication

&UHDWLQJ D QHZ EDWFK MRE

,QFUHPHQWDO 'DWD 0DWFKLQJ MREV

%DWFK MRE FRQVLGHUDWLRQV

You cannot run more than one batch process simultaneously.

&RQVROLGDWLRQ DIWHU EDWFK PDWFK

0HUJH GXSOLFDWH UHFRUGV

)RU 8&0 %DWFK 0DQDJHU

&KDSWHU  &RQFHSWV IRU FXVWRPL]HG DSSOLFDWLRQV

LOG_DIRECTORY LOGS_TO_KEEP LOG_SIZE NUMBER_OF_INITIALIZATION_ LOG_MESSAGES_TO_KEEP CONNECTION_TIMEOUT

A valid port number

A valid port number

3DUVLQJ DQG VWDQGDUGL]DWLRQ WUDQVIRUPV

6WHS $SSOLFDWLRQ $GPLQLVWUDWLRQ VHWXS

&KDSWHU &RQILJXULQJ 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0

&KDSWHU 8VLQJ 'DWD 4XDOLW\ IRU 2UDFOHV 6LHEHO 8&0

Uurrpqw rrrqvpvqrrq urhrhqu urr

&KDSWHU &RQFHSWV IRU FXVWRPL]HG DSSOLFDWLRQV

'DWDIORZ LQSXWRXWSXW ILHOG QDPHV

([DPSOH DGGLQJ QHZ ILHOGV IRU FOHDQVLQJPDWFKLQJ

:RUNLQJ ZLWK DGGUHVVFOHDQVLQJ HUURUV

&KDSWHU 7LSV DQG WURXEOHVKRRWLQJ

&OLHQW KDQJV'DWD 4XDOLW\ 6HUYHU ZLQGRZV 6HUYLFH QRW VWDUWHG DXWRPDWLFDOO\