SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide Data Quality Management, version for SAP Solutions XI 3.1 SP2 (12.1.2) November 2009

Notices Copyright information Copyright 2009 SAP AG. All rights reserved. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. 2 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Contents Preface... 9 About this guide...9 Access the latest documentation...9 Conventions...9 Assumed audience...10 Product naming conventions...10 Chapter 1: Overview... 11 Data quality overview...12 What is data quality?...12 What steps are involved in data quality?...12 The results of data quality...13 What is SAP BusinessObjects Data Quality Management, version for SAP Solutions?...14 Components of this product...14 Postal validation engine...14 Match engine...14 Introduction to SAP BusinessObjects Data Services...15 Hub of data quality needs...15 Access Data Services documentation on Windows...15 Chapter 2: Installing Data Quality for SAP... 17 System requirements...18 Required SAP Support Notes for your system...18 Requirements for the RFC Server...18 Requirements for the BAdIs...19 Installation scenarios...20 Previous version already installed...20 Fresh installation...20 Install Data Services...22 Data Services install machine...22 Install the Address Directories...22 Data Services must be running...22 Start the Data Services Address Server service...22 Install the Data Services Component...23 Data Services Component Checklist...23 Install the Data Services Component for Windows Data Services configuration...23 Install the Data Services Component for UNIX/Linux Data Services configuration...24 Use global variables to disable engines...25 Create the batch RDBMS staging tables...26 Configure jobs as services...27 Install the RFC Server...30 Contents 3

Installing the RFC Server as a Windows Service... 30 Replacing a previous RFC Server version... 30 RFC Server Checklist... 30 Install the RFC Server... 31 Start the RFC Server... 32 Stop the RFC Server... 33 Install the BAdIs support package... 34 Step 1: Import the Data Quality Management support package on client 000... 34 Step 2: Re-activate the Business Configuration Sets on each target client... 36 Quarterly Adjustment Reports... 38 Report RSADRQU1... 38 Report /FLDQ/RSADRQU2... 39 Report RSADRQU3... 40 Quarterly Adjustment custom error report... 41 Run the initialization program... 42 Purpose of initial setup... 42 Performing batch match from the same window... 42 Run the initial setup... 42 Configure geocoding... 43 Configure the RFC Server for geocoding... 43 Register geocoding program in SAP... 43 Configure the country... 43 Designate fields to use for geocoding... 44 Chapter 3: Configuring through the IMG... 45 Locating the Data Quality for SAP IMG activities... 46 SAP handshake with RFC server... 47 Maintain Supported Countries... 48 Remove the country codes... 48 Maintain exception table of transaction codes... 49 Add a transaction code to the exception table... 49 Maintain table to activate SAP postal code check before postal validation.. 51 Add a country to the table... 51 Maintain fields for address reviewer... 52 Fields and order for standard street addresses... 52 Fields and order for P.O. Box addresses... 52 Make changes to the fields for the address reviewer... 52 Maintain fields for duplicate hit list display... 54 Fields and order for error tolerant search and duplicate search... 54 Make changes to the fields for the duplicate hit list display... 55 Maintain operating parameters... 56 Operating parameters... 56 Modify the parameters... 57 Map address types for Quarterly Adjustment... 59 Defining mappings... 59 Predefined mappings... 59 Add a mapping for an Address Type Code... 59 4 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Chapter 4: Configuring the RFC Server... 61 Configuring through flrfcsrv.xml...62 Location of flrfcsrv.xml...62 Editing flrfcsrv.xml...62 SAP settings and DQ Server settings...62 File settings...62 General settings...64 Dataflows...64 Reconnect Settings...65 Termination email settings...65 Overrides...66 Configuring through regions.xml...68 Adding U.S. military regions...68 Chapter 5: Postal address validation... 69 Interactive cleansing with Data Quality for SAP...70 Using interactive cleansing...70 Multiple suggestions...71 Batch cleansing with Quarterly Adjustment Reports...72 Chapter 6: Duplicate check and error tolerant search... 73 Understanding duplicate check and error tolerant search...74 Duplicate check...74 Error tolerant search...74 Break Keys...74 Understanding break keys and data fields...75 Changing the match code...76 Configuring the break key settings...76 Match on name data...79 Using duplicate check...80 Interactive mode...80 Batch mode...81 Using error tolerant search...83 The hit list...83 Fields displayed...84 Chapter 7: Tips and troubleshooting... 85 Installation troubleshooting...86 If the installation was unable to import the.atl files...86 Checking the RFC Server(s) connection...86 Connection to the RFC Server closed...86 Troubleshooting Unicode issues...87 Postal validation and duplicate check/error tolerant search troubleshooting.88 Using the sample input files to test Jobs...88 Inability to save addresses for which the postal code cannot be completed...88 Records created without break keys due to downtime of RFC Server...88 Records not stored in pending update table when search disabled...89 Understanding regions...89 Contents 5

Region code cannot be mapped to the region name... 90 Newfoundland region code for R/3 4.70... 91 RSMTCCODE program error message... 91 Include records with empty break keys... 91 Threshold values for duplicates... 92 Show Duplicates button inactive in WebClients... 92 Generating reports in Data Services... 92 DPV processing locked... 92 Diagnosing problems that cause data quality processing to cease... 93 RFC Server Troubleshooting... 94 Output manifest information... 94 Appendix A: Data Services Jobs and Options... 95 Data Services jobs... 95 Combine House Num and PMB option... 96 Appendix B: Error Codes... 99 Technical error codes... 99 Postal validation error codes... 102 Duplicate check error code... 103 Appendix C: External List Management... 105 Using Data Quality for SAP with ELM... 106 Cleansing the external list prior to loading via ELM... 106 ELM functionality for different versions of SAP CRM... 106 Records with only name data... 106 Appendix D: Databases for staging tables... 107 Oracle RDBMS inputs screen... 107 DB2 RDBMS inputs screen... 107 MS SQL RDBMS inputs screen... 108 MySQL 5.0 RDBMS inputs screen... 109 Appendix E: Using the Break Key Profiler... 111 Break Key Profiler job... 112 Concepts for break key profiler... 113 Noise words... 113 First and Last Name Selection... 113 Address only selection... 113 Installation... 115 Installing the dataflow with this product... 115 Installing the dataflow without this product... 115 Run the job... 116 Performance... 116 Interpret the Results... 117 The output files... 117 Settings that can be optimized based on the output... 118 Match Codes... 119 Creating Custom Match Codes... 121 6 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Appendix F: BAdI-only for fresh installation...123 Installing the BAdIs from the previous version...124 Step 1: Import the Data Quality Management package on client 000...124 Step 2: Insert the Data Quality Management IMG structure on client 000...127 Step 3: Activate the Business Configuration Sets on each target client 129 Activate region and country fields in TSAD10...130 SAP handshake with RFC Server...131 Purpose of the activity...131 Define the RFC destinations...131 Load supported country codes...134 Running the transaction and report...134 Activate duplicate check index pools...135 Activate the index pools...135 Install and configure Data Quality for SAP into the CRM IC WebClient or CRM WebClient...137 Requirements for running in a WebClient profile...137 Summary of configuration tasks...137 Activate the BSP BC Sets...137 Creating an Enhancement Set...138 Find the name of the Component to Enhance...138 Enhance the Component...139 Index... 141 Contents 7

8 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Preface About this guide This guide provides a general overview of SAP BusinessObjects Data Quality Management, version for SAP Solutions as well as specific information for installing and integrating this product into your SAP environment. Access the latest documentation In addition to the documentation installed on your computer during installation of this product, you can access all the supported SAP Business Objects documentation from the SAP Business Objects Customer Support site. 1. Go to http://help.sap.com. 2. Select the Business Objects tab. 3. In the SAP Business Objects Overview section, select All Products. 4. On the Business Objects Product Guides screen, navigate to the document that you want to view. You can view the PDFs online or save them to your computer. Conventions This document follows these conventions: Convention Bold Italics Menu commands! Description 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. 9

Assumed audience This guide assumes that the people responsible for integrating and using Data Quality for SAP are experienced administrators and users of SAP R/3, SAP ERP Central Component (SAP ECC), and SAP Customer Relationship Management (SAP CRM) solutions. If you are implementing the CRM IC WebClient or CRM WebClient postal validation and search capabilities, this guide also assumes that you are aware of any settings and customizations you have made to your CRM IC WebClient or CRM WebClient configuration before installing this product. This guide does not explain basic operation of the SAP environment. For questions about the SAP environment, consult the appropriate SAP documentation or SAP technical support. Product naming conventions For brevity, SAP BusinessObjects Data Quality Management, version for SAP Solutions is often in this guide called Data Quality for SAP. BusinessObjects Data Services XI Release 3.2 SP01 (12.2.1.1) is often in this guide called Data Services. 10 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Chapter 1: Overview Before using SAP BusinessObjects Data Quality Management, version for SAP Solutions, you should understand some of the concepts of data quality. A basic familiarity with these concepts helps you to understand what this product does, how it works with your existing SAP environment, and why your organization benefits from data quality. Chapter 1: Overview 11

Data quality overview What is data quality? Data quality is a process of arranging customer information in a standardized, validated, and consistent order. The process also helps you to avoid duplicate data entries and adds value by creating a single and accurate view of your customers. What steps are involved in data quality? Generally, data quality requires these main steps: parsing correction standardization duplicate matching Parsing Parsing involves checking the structure and content of each field of a contact s information. 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, street number and name, region, and postal code. Correction To correct data, this product uses secondary data sources, such as the U.S. Postal Service s National Directory or an international postal directory, to check and validate address information. Using these secondary sources, this product can check, for example, whether La Crosse, Wisconsin is associated with the ZIP Code 54601, whether Harbor Plaza is actually a valid street name in La Crosse, and whether 100 is a valid address for that street. 12 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Standardization After correcting the data, this product can standardize the data. Standardization works in conjunction with correction and parsing as it arranges customer information in a consistent and preferred format. 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. Duplicate Matching Once a standardized customer record exists, matching should become part of the data quality analysis to eliminate redundancies. During the matching step, the software searches existing customer data records in real time 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 the user is offered the opportunity to determine whether the newly entered record matches the suggested existing record. Duplicate matching technology even allows the user to search for records based on partial information. The results of data quality 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. Chapter 1: Overview 13

What is SAP BusinessObjects Data Quality Management, version for SAP Solutions? SAP BusinessObjects Data Quality Management, version for SAP Solutions is software that enhances parts of your SAP installation. SAP can stand alone without having this product installed, but without it, you would not attain the benefits of data quality. This product takes care of the correction, standardization, and duplicate matching steps in the data quality process. Components of this product This product consists of these components: BusinessObjects Data Services XI Release 3.2 SP01 (12.2.1.1) Data Quality Management Premium license, which handles data quality processing tasks on the data it receives from the RFC Server. Data Services Address Directories, which are downloaded separately from Data Services and installed with Data Services. Data Services Component, which provides Data Quality Management functionality within Data Services that is specific to this product. The RFC Server, which receives and returns data sent from the SAP environment through TCP/IP. Three Business Add-Ins (BAdI) that are integrated directly into the SAP environment for postal validation, duplicate check, and error tolerant search. Postal validation engine The postal validation engine of this product relies on the Data Services address directories compiled from global postal authorities around the world, such as the United States Post Office, to cleanse addresses from almost any location. The postal validation engine is integrated into your SAP system through SAP s Business Address Services Postal Validation (PV) interface. Match engine The match engine of this product brings sophisticated record-matching technology to your SAP applications. The criteria for deciding which records are a potential match are controlled by business rules that you can customize to your needs. When you enter a record that is a potential duplicate, you have the option of choosing which of the duplicate records to keep. The match engine is integrated into your SAP system through SAP s Business Address Services (BAS) Duplicate Check, Error Tolerant Search (DES) interface. 14 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Introduction to SAP BusinessObjects Data Services As a Data Quality for SAP user, you may be wondering what SAP Business Objects Data Services is and what it means to you. After installation and configuration, you can use Data Quality for SAP with little thought given to Data Services, because it handles the data quality processes behind the scenes. Details of installing and configuring Data Services are found in the Data Services documentation. This section provides a simple overview of what Data Services does, independent of its use within Data Quality for SAP, and tells you where you can find more information about Data Services. Hub of data quality needs Data Services is the next generation data quality platform that allows you to tie in all of your data quality needs to a single hub. Many customers of Data Quality for SAP 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 Data Services as the backbone for all of your data quality needs. With Data Services, you can centralize and standardize this processing through the following Data Services features. Centralized business rule repository All of the business rule definitions are stored in a single repository that can be shared by all applications that use Data Services. 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 Data Quality for SAP, your own custom application that incorporates Data Services, or direct batch processing through Data Services itself. This means that you can create data quality standards that are truly shared across your entire enterprise. Access Data Services documentation on Windows After installing Data Services, Windows users can access the documentation from shortcuts on the Start menu. Documentation is installed as a separate component. The documentation for Data Services is an optional installation component in most cases. If you don t install the documentation while installing Data Services, it won t be available on your system. To access the documentation: 1. Choose Start > Programs > SAP BusinessObjects XI 3.2 > SAP BusinessObjects Data Services > Data Services Documentation. 2. Click the appropriate shortcut for the documentation you want to view. Chapter 1: Overview 15

16 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Chapter 2: Installing Data Quality for SAP This section explains the requirements and procedures for installing SAP BusinessObjects Data Quality Management, version for SAP Solutions. The installation for Data Quality for SAP includes installing the following components: SAP BusinessObjects Data Services - Data Quality Management Premium license, including the Data Services Address Directories Data Quality for SAP Data Services Component Data Quality for SAP RFC server Data Quality for SAP Business Add-Ins (BAdIs) Support Package The details of these steps vary depending on whether you have the previous version of this product already installed. For details on installation scenarios, see Installation scenarios on page 20. Chapter 2: Installing Data Quality for SAP 17

System requirements This section contains the requirements for your SAP system, the RFC Server, and the BAdIs. Required SAP Support Notes for your system Before installing this product, review the following SAP Support Notes to determine which apply to your SAP configuration. SAP Note# Description 196958 Collective note: Errors in interface for duplicate check 1142279 BUPA_ADDRESS_CHANGE performs address save twice 1328170 Address assigning directly without providing suggestion list - Data Quality Management for SAP/Data Services 3.1. Note that versions of Data Services XI 3.1 SP02 and higher already have resolved this issue. In addition, you should review any other SAP Support Notes for any content related to Data Quality Management applicable to your SAP platform. For a list of SAP Notes related to the IC WebClient, see Requirements for running in a WebClient profile on page 137. Requirements for the RFC Server The RFC Server requires one of the following environments. Supported operating systems HP-UX 11i v2 (11.23) (Itanium) (64-bit) IBM AIX 5.2, 5.3, and 6.1 (64-bit) Red Hat Linux Enterprise Server 4 and 5 (64-bit) Solaris 9 and 10 (64-bit) SuSE Enterprise Server 9 SP3 and 10 (64-bit) Windows XP (32 bit) Windows 2003 Server (32 bit) RFC Server permissions for Windows 2003 Server In Windows 2003 Server, the user account that runs the RFC Server must have full permissions to access the subdirectories that contain the address directories. Java Runtime Environment The machine on which you install the RFC Server must run the Java 2 Platform, Standard Edition (J2SE) version 1.6. You must acquire and install the J2SE independently of the installation and before the installation of the RFC Server. SAP Java Connector The UNIX installation of this product is configured with the assumption that you will use the 64-bit Java runtime. If you instead use the 32-bit Java runtime environment you must use the 2.x, 32-bit version of the SAP Java Connector (JCo) and remove the d64 option in the RFC Server startup scripts. The 32-bit JCo installer is available at http://service.sap.com. 18 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Requirements for the BAdIs This version requires that you have the BAdIs from the previous version of this product, Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1), installed. The BAdIs portion of this product upgrades the BAdIs from that version, and cannot be installed without.the BAdIs portion of this product requires one of the following SAP environment: SAP Customer Relationship Management (SAP CRM) solutions 5.0, 2007, and 7.0 SAP R/3 v4.7, SAP ECC 5.0 (ERP2004), and ECC 6.0 SAP ERP 6.0 Enh Pack 4 SAP Banking Services 6.0 Interactive (real-time) postal address validation, and duplicate check and errortolerant search are supported within these client user interfaces: CRM WebClient and CRM IC WebClient: CRM 2007 and greater CRM versions. SAP GUI and IC Web Client: CRM 5.0 SAP GUI only: CRM 5.0, ERP 6, ERP 5, and R/3 4.7. Chapter 2: Installing Data Quality for SAP 19

Installation scenarios This version is a Support Package upgrade to the previous version of this product, Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1). Your installation scenario depends one whether you have installed that previous version of this product, or whether you intend to install this version as a fresh installation. Previous version already installed If you have the previous version of this product already installed, your installation steps require care in properly uninstalling components of that previous version while preserving any customizations you have made so that those customizations can be manually applied to this version. Upgrade Data Services You must upgrade your version of Data Services to Data Services XI 3.2 SP01, version 12.2.1.1 and install the version-specific Data Services Component portion of this product. If you have made changes to the Data Services jobs, dataflows, or custom functions in your previous installation, before upgrading export the components to preserve text-file versions and rename the objects within Data Services so that you can compare old versions to the new versions that are installed by the Data Services Component. You can then manually recreate your customizations. See the Data Services documentation for information on preforming an upgrade of Data Services and using the tools that allow you to compare components from your customized versions to the new versions installed with this product. For further information on installing Data Services and the Data Services Component of this product, see Install Data Services on page 22 and Install the Data Services Component on page 23. Install a new version of the RFC Server This version requires a new version of the RFC Server portion of this product. The RFC Server does not upgrade directly. You must uninstall the previous version and install the new. If you have made configuration changes to your previous version of the RFC Server, you must manually apply them to the new configuration from backup copies of the RFC Server configuration files. For further information on replacing a previous version of the RFC Server and installing this component for this version, see Install the RFC Server on page 30. Install the new BAdIs The BAdIs used for this version are provided as a Support Package that install directly over the previous version of the BAdIs in your SAP system. For further information on applying the BAdIs Support Package, see Install the BAdIs support package on page 34. Fresh installation Though this version is a Support Package upgrade to the previous version of this product, you can install this version without performing a full installation of the previous version. However, in addition to performing the installation tasks described in this chapter, you must also install the BAdI portion of the previous version of this product, and if desirable, activate the IC WebClient using that BAdI. 20 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Steps in a fresh installation The installation of Data Quality for SAP requires these tasks, which are detailed later in this section: Outside of your SAP system: 1. Install Data Services and the Address Directories. 2. Install Data Services Component. 3. Install the RFC Server. On your SAP system: 4. Install the BAdIs from the previous version of this product. 5. Install the BAdIs support package from this version. 6. Run the post-installation tasks required of a new installation of the BAdIs. 7. Activate the IC WebClient, if desired. Chapter 2: Installing Data Quality for SAP 21

Install Data Services This product relies on Data Services for performing data quality operations. For instructions on installing, configuring, and running Data Services, see the Data Services Installation Guide. This section contains considerations to help you successfully install Data Services for use with this product. Data Services install machine You can install Data Services on the same machine as the RFC Server, on a different machine, or even on a machine with a different operating system than the one that contains your installation of the RFC Server. Information about the system requirements for the machine on which you install Data Services are included with the Data Services documentation. Data Services previously installed If you are already a Data Services customer (as a stand-alone product or because you are upgrading from a previous version of this product) and therefore have already installed a version of Data Services, you must upgrade to Data Services XI 3.2 SP01, version 12.2.1.1, which is provided as part of this software package. See the Data Services documentation for details of how to upgrade. Running new version of Data Services You can run this product with a version of Data Services higher than XI 3.2 SP01, as long as it is still XI 3.x. (You cannot run this product with a previous version.) See the Data Services documentation for information about updating the Data Services Component items shipped with this release to work with newer versions of the Data Services repository. Install the Address Directories For Data Services to perform data quality operations, you must install the Data Services Address Directories. The Address Directories are a separate download from the Data Services installation media. See the Data Services documentation for information on downloading and installing the Address Directories. Data Services must be running You must have Data Services running during the remaining installation procedures of this product, and during its operation. Start the Data Services Address Server service You must manually start the Data Services Address Server service on the machine that houses Data Services. By default, the Address Server service is set to manual, and does not start with the startup of the computer. For details on manually starting the Address Server service, or setting it to start automatically, see the Data Services documentation. 22 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Install the Data Services Component After you install the latest version of Data Services and the Address Directories, you install the Data Services Component that is specific to this product and then perform configuration tasks. The Data Services Component installation configures network connection information, and then copies a.xml file and imports.atl files specific to the operation of this product into your Data Services configuration. This section describes installing the Data Services Component for both Windows and UNIX/Linux, and then the configuration steps required after the installation.! If you have previously installed this version or any past version of this product and made customizations to the Data Services job Job_Realtime_DQ_SAP_Create_Break_Keys, installing the Data Services Component will overwrite the customized version of the file. You should back up or rename the job if you want to keep any customizations. You can then apply the customizations to the new version. Data Services Component Checklist The Data Services Component installation routine asks the following information about your configuration. You should prepare this information before beginning the installation. Data Services Repository database type Data Services Repository database connection parameters: user name and password Database information for the creation of the staging tables Table Owner/Schema TNS Name/Service User Name Password Install the Data Services Component for Windows Data Services configuration Install the Data Services Component on the machine you installed the Data Services Designer. To install the Data Services Component for a Windows Data Services configuration: 1. Locate the SAP BusinessObjects Data Quality Management, version for SAP Solutions - Data Services Component media and launch setup.exe. 2. In the Welcome screen, click Next. 3. If the installation routine cannot detect your version of Data Services, the Confirmation Requested window appears. If the window appears, click Yes to confirm that you have first installed Data Services. 4. Read the license agreement and, if you accept the license agreement terms, choose I accept the terms of the license agreement and click Next. 5. In the Choose Destination Locations window, accept the default installation location or specify a different location. Click Next Chapter 2: Installing Data Quality for SAP 23

S Though you can use the Browse button to change the destination folder, SAP Business Objects recommends that you install to the default directory, and you must install to a path that finishes with [your_path]\ Business Objects\Data Quality Mgmt for SAP Solutions. 6. In the Repository Connection Parameters screen, enter the connection details. Click Next. 7. In the RDBMS Selection window, choose the database type you intend to use for the creation of staging tables, and click Next. The window that follows this step varies, depending on which database type you chose. Each database type requires different connection data. For reference information on databases supported for staging tables, see Databases for staging tables on page 107. 8. In the Connection Parameters window that appears for your database type, enter the database connection information and click Next. 9. In the Ready to Install the Program window, click Install. The windows update for each steps in the installation routine. 10. Click Finish when the installation has completed. The Data Services Component is now installed to your Data Services system, but you must perform post-installation steps following in this section to configure Data Services. Install the Data Services Component for UNIX/Linux Data Services configuration Install the Data Services Component on the machine you installed the Data Services Designer. Though you have a UNIX/LINUX Data Services configuration, the Designer is always installed on a Windows machine. If you run the install on a machine that does not have the Data Services Designer, you will have to use the Designer later to set the DS_SAP_DS datastore password after importing the.atl files. To install the Data Services Component for a UNIX/Linux Data Services configuration on that Windows machine: 1. Locate the SAP BusinessObjects Data Quality Management, version for SAP Solutions - Data Services Component media and launch setup.exe. 2. In the Welcome screen, click Next. 3. If the installation routine cannot detect your version of Data Services, the Confirmation Requested window appears. If the window appears, click Yes to confirm that you have first installed Data Services. 4. Read the license agreement and, if you accept the license agreement terms, choose I accept the terms of the license agreement and click Next. 5. In the Choose Destination Locations window, accept the default installation location or specify a different location. Click Next 24 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Though you can use the Browse button to change the destination folder, SAP Business Objects recommends that you install to the default directory, and you must install to a path that finishes with [your_path]/ Business Objects/Data Quality Mgmt for SAP Solutions. 6. In the RDBMS Selection window, choose the database type you intend to use for the creation of staging tables, and click Next. Keep in mind that the connection information you provide in this section is for your UNIX Data Services configuration. The window that follows this step varies, depending on which database type you chose. Each database type requires different connection data. For reference information on databases supported for staging tables, see Databases for staging tables on page 107. 7. In the Connection Parameters window that appears for your database type, enter the database connection information and click Next. 8. In the Ready to Install the Program window, click Install. The windows update for each steps in the installation routine. 9. Click Finish when the installation has completed. The installation by default copies files to the directory [your_path]/business Objects\Data Quality Mgmt for SAP Solutions\integration/. Use the files in this location for the remaining steps. 10. If the installation routine is unable to import the.atl files to the Data Services, you must import them manually according to the directions in the Data Services documentation. You must import the.atl files in the following order: SAP_DS_STG_TBL.atl DQ_SAP_DS.atl DQ_SAP_DS_SYS_CFG.atl DQ_SAP_DS_SUB_PARAM.atl For instructions on importing.atl files, see the Data Services documentation. 11. Copy the file SupportedCountriesList.xml to the /bin directory of the Data Services configuration on the UNIX/Linux server. The Data Services Component is now installed to your Data Services system, but you must perform post-installation steps following in this section to configure Data Services. Use global variables to disable engines You must disable the address cleanse engines for countries for which you did not purchase the address directory. See the Data Services documentation for information on which countries address data is supported by which engine. The table below lists the country engine substitution parameters. Chapter 2: Installing Data Quality for SAP 25

Substitution parameter $$DQ_SAP_EngineUsa $$DQ_SAP_EngineAustralia $$DQ_SAP_EngineCanada $$DQ_SAP_EngineEmea $$DQ_SAP_EngineGlobalAddress $$DQ_SAP_EngineJapan $$DQ_SAP_EngineMultiCountry Description Enable or disable the USA engine Enable or disable the Australia engine Enable or disable the Canada engine Enable or disable the EMEA engine Enable or disable the Global Address engine Enable or disable the Japan engine Enable or disable the Multi Country engine If you have created your own substitution parameter configurations, make sure that you include them in this process. You must perform the steps to disable unpurchased address cleanse engines for all the $$DQ_SAP_* substitution parameters in any configuration you use with this product. To disable address cleanse engines: 1. In the Data Services Designer, go to Tools > Substitution Parameter Configurations. 2. In the Substitution Parameter Editor, select one of the country engine substitution variables from the list that represents a country address cleanse engine that you did not purchase. 3. Set the parameter to NO to disable the engine for every address cleanse engine represented by a Data Services address directory that you have not purchased. You must perform this step for every configuration you use. If you did not purchase an address cleanse address directory, and the corresponding value is set to YES or is blank, this product cannot function properly. 4. After you have set the appropriate value for all the Substitution Parameters, click OK. Create the batch RDBMS staging tables Next, you create batch processing staging tables, which this product uses in the transfer or data to and from Data Services. You must have an appropriate database client installed and a connection (such as an Oracle TNS entry) to the database created. To create the Staging Table RDBMS tables: 1. In the Data Services Designer, go to the Jobs tab of the Local Object Library. In the Batch Jobs hierarchy, select the job DQCreateStageTables. The DQCreateStageTables is now visible in the Designer. 2. With the job DQCreateStageTables active, select Debug > Execute (or press F8) to execute the job. 26 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

3. In the Execution Properties window, select the appropriate configuration from the System configuration drop-down list. Configure jobs as services When you install the Data Services Component, a group of Data Services jobs are copied to your Data Services installation. You must configure these jobs (.atl files) as services. Sample input files Before configuring jobs as services, you may want to run the sample input files to test Data Services jobs. Though running the sample input files is not required as part of installation, the installation is now at a point in which the files can be run. For information on verifying the Data Quality jobs, see Using the sample input files to test Jobs on page 88. The remaining information in this section is required as part of the installation of this product. List of jobs and their service names Configure jobs as services for all of the jobs listed in the table by following the steps in To configure jobs as services on page 27. Job Job_Batch_DQ_SAP_Address_Cleanse Job_Realtime_Batch_DQ_SAP_Name_ And_Address_Match Job_Realtime_DQ_SAP_Address_ Cleanse Job_Realtime_DQ_SAP_Address_ Cleanse_Suggestions Job_Realtime_DQ_SAP_Address_GEO Job_Realtime_DQ_SAP_Create_Break_ Keys Job_Realtime_DQ_SAP_Create_Break_ Keys_With_Firstname Job_Realtime_DQ_SAP_Name_And_ Address_Match Job_Realtime_DQ_SAP_Retrieve_ Country_Purchased Job_Realtime_DQ_SAP_US_DPV_ Address_Cleanse_Suggestions Service name Service_Batch_DQ_SAP_Address_ Cleanse Service_Realtime_Batch_DQ_SAP_ Name_And_Address_Match Service_Realtime_DQ_SAP_Address_ Cleanse Service_Realtime_DQ_SAP_Address_ Cleanse_Suggestions Service_Realtime_DQ_SAP_Address_ GEO Service_Realtime_DQ_SAP_Create_ Break_Keys Service_Realtime_DQ_SAP_Create_ Break_Keys_With_Firstname Service_Realtime_DQ_SAP_Name_And_ Address_Match Service_Realtime_DQ_SAP_Retrieve_ Country_Purchased Service_Realtime_DQ_SAP_US_DPV_ Address_Cleanse_Suggestions To configure jobs as services You must perform this procedure for each job listed in the preceding table. Before configuring jobs as services, you must have configured a Data Services repository as part of the installation of Data Services. If you have not configured a repository, see the Data Services documentation for instructions. Chapter 2: Installing Data Quality for SAP 27

To configure jobs as services: 1. Open the Data Services Management Console and login. 2. Click Administrator. 3. In the file tree expand Real-Time and select the server that you set up when you installed Data Services. 4. Select Real-Time Services from the file tree on the left and open the Real- Time Service Configuration tab on the right. 5. Click Add. 6. In the Service Configuration window click Browse Jobs. 7. Select a job name (listed in the preceding table). For example, select Job_Batch_DQ_SAP_Address_Cleanse. If the Management Console is connected to more than one repository, make sure you select the dataflows from the repository that contains the jobs imported in the previous steps. 8. Enter the service name for the job. For example, enter Service_Batch_DQ_SAP_Address_Cleanse (exact case is required). 9. For most services, enter 800 for the Processing Timeout value and click Apply. For the service Service_Realtime_Batch_DQ_SAP_Name_And_Address_Match, enter a very large number (such as 2147483647) to prevent a very large batch match job from timing out during processing. 10. Under Service Provider, click Add and include the correct JobServer to run this service. 11. Repeat steps 4 through 10 for each of the Real-time job listed in the preceding table. Enable or disable an address engine If necessary (for example, to disable the engine responsible for running addresses for a country you did not purchase), you can enable or disable an address engine for a particular service in the Data Services Management Console. 1. In the Real-Time Service Configuration tab, the Add dialog, click Add Overridden Parameter 2. Select the override parameter for the engine that you want to enable or disable. For example, to enable or disable the Canada engine, select $$DQ_SAP_EngineCanada. 3. Type Yes to enable or No to disable the engine. Changes to parameters cannot take effect until the services that uses the parameters are restarted. Therefore, you must restart the job for this change to take effect. To configure Web Services You must next configure Web Services. To configure Web Services: 1. Keep the Data Services Management Console open from the previous steps, or open and login to the Data Services Management Console and click Administrator. 28 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

2. Select Web Services from the file tree at left and open the Web Services Configuration tab on the right. 3. Select Add Real-Time Service from the drop-down menu and click Apply. All of the service names that you entered in To configure jobs as services appear in the list. If you configure Web Services for any features you did not purchase, such as geocoding or DPV, those Web Services will fail. 4. Choose Select All and click Add. To start the services After you have configured both the jobs and Web Services, you must start the services. To start the services: 1. Keep the Data Services Management Console open from the previous steps, or open and login to the Data Services Management Console and click Administrator. 2. Select Real-Time Services from the file tree at left and open the Real-Time Services Status tab on the right. 3. Select all of the services that you created and click Start. It may take a few minutes for the services to start. If you are not certain the services started, check that the Business Objects Address Server is started. In Windows, look in the Services window to see the status of all services. After you have performed the automatic services start, you must shutdown and restart the services manually if you change the configurations. Chapter 2: Installing Data Quality for SAP 29

Install the RFC Server After you install and configure Data Services, and install the Data Services Component, you install the RFC Server. Each installation of the RFC Server installs one instance for transactional processing and one instance for batch processing. You must install the RFC Server from a user account that has permissions to install software on the machine, and you can only have one instance of an RFC Server dedicated to batch processing active on a single gateway. Installing the RFC Server as a Windows Service During the installation of the RFC Server on Windows, the installation routine allows you to install the RFC Server as a Windows Service. The RFC Server functions the same whether you install it as a Windows Service or not, but installing the RFC Server as a Windows Service allows you to administer it through the Services console. The first instance of the RFC Server has the Service name BusinessObjects DQM for SAP xxx 1 (where xxx is the System ID). Other instances of the RFC Server are named BusinessObjects DQM for SAP xxx 2, BusinessObjects DQM for SAP xxx 3, and so on. A dedicated RFC Server for batch duplicate search has the service name BusinessObjects DQM for SAP Batch xxx. If you chose not to install the RFC Server as a Windows Service but want to add this functionality, you must run the installer again and select the additional Windows Services option. Replacing a previous RFC Server version You cannot install this version of the RFC Server over a previous version. If you intend to use a machine that has the RFC Server from a previous version of this product, you must uninstall the previous version. On Windows, run the installation routine from the previous version of this product on a machine that holds the RFC Server. The installation routine gives the option to uninstall the instance of the RFC Server it finds. On UNIX/Linux, simply delete the files of the RFC Server to uninstall. If you are upgrading from a previous version of this product and made customizations to the RFC Server settings, before uninstalling you should make copies of the previous version s files flrfcsrv.xml and regions.xml to use as a reference to those customizations. You must manually apply any customizations to this version of the product to reproduce those changes from the default settings. For information on the location and settings of these files, see Configuring the RFC Server on page 61. RFC Server Checklist The RFC Server installation routine asks the following information about your configuration. You should prepare this information before beginning the installation. The three-letter System ID of your SAP system Gateway Host of your SAP system Gateway Service Name of your SAP system Basis version of your SAP system, and whether it is a Unicode system 30 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Data Services Host Name (chosen when you install Data Services for this product) Data Services Port Number (chosen when you install Data Services for this product) URL for Data Services Web Services (chosen when you install Data Services for this product) The email Host of your email system, a sender email address, and recipient email address (in comma-delimited format), used by the RFC Server to send email notifications if it terminates Install the RFC Server Install the RFC Server on a machine that meets the system requirements ( Requirements for the RFC Server on page 18). The procedure in this section is specific to Windows. Installing the RFC Server on UNIX or Linux requires you to input the same information, without any parallel to the step of installing the RFC Server as a Windows Service. To install the RFC Server: 1. Locate the SAP BusinessObjects Data Quality Management, version for SAP Solutions - RFC Server media and launch setup.exe. 2. In the Welcome screen, click Next. 3. Read the license agreement and, if you accept the license agreement terms, choose I accept the terms of the license agreement and click Next. 4. If you want to install the RFC Server as a Windows Service, click Yes, and in the next screen enter the number of Services you want to create for transactional processing. Otherwise, click No. 5. In the Choose Destination Locations window, accept the default installation location or specify a different location. Click Next. By default, the installation routine installs the RFC Server to the folder C:\Program Files\Business Objects\Data Quality Mgmt for SAP Solutions. Though you can use the Browse button to change the destination folder, SAP Business Objects recommends that you install to this default directory, and you must install to a path that finishes with [your_path]\business Objects\Data Quality Mgmt for SAP Solutions. 6. In the SAP Information window, enter the SAP System ID, Host Name, and Service of the SAP Gateway. The SAP System ID is a maximum of three characters in length. For the Host Name, you can use either the name or IP address of the SAP central instance gateway. The Service of the SAP Gateway is typically sapgwxx, where xx is the central instance number. 7. Select Yes or No to indicate whether your SAP system is Unicode compliant. Click Next. Chapter 2: Installing Data Quality for SAP 31

If your system is Unicode compliant, the step Run the initialization program on page 42 has further configuration instructions on configuring Data Quality for SAP for Unicode systems. 8. In the SAP Basis window, select the version of your SAP Basis system. (The installer uses different files depending on your Basis version.) Click Next. 9. In the Data Services Connection window, enter the Data Services Access Server hostname and port number (default is 4000), and the URL of the Data Services Web server (default is http://<hostname>:28080/dataservices/ servlet/webservices?ver=2.0&wsdlxml). Click Next. 10. In the Email Server Connection Parameters window, provide the following information: Email host. If you leave this field blank, the RFC Server does not send email notifications if the RFC Server terminates or the SAP gateway disconnects. Email Port. The default email port is 25. Sender Email Address. Recipient Email Addresses. Each of the recipient email addresses must be separated by a comma. Click Next. The email transport protocol is SMTP. The installation routine does not validate the email addresses you provide. You can change these parameters later in the RFC Server configuration file. For more information, see Configuring through flrfcsrv.xml on page 62. 11. In the Ready to Install the Program window, click Install. The installation proceeds 12. Click Finish when the installation has completed. If you run the installer again on a system that already has the RFC Server installed, the installation routine detects the previous installation and offers steps to create additional Windows Services (for Windows only), configure a new SAP system, or uninstall. When you uninstall the RFC Server on Windows, the routine uninstalls all RFC Servers on the system. Start the RFC Server If you installed the RFC Server on Windows as a Windows Service, you can start the RFC Server as you would any Windows Service. The name of the Service for the first instance of the RFC Server, for example, is BusinessObjects DQM for SAP xxx 1 (where xxx is the System ID). You must start all instances of the RFC Server, interactive and batch, in this manner. You can also use the configuration features available for any Service, such as the ability to automatically restart the Service after failure. For details on configuring Windows Services, see your Windows documentation. If you did not install the RFC Server as a Windows Service, you can find the batch files to start the RFC Server in the install directory of the machine on which you installed the RFC Server. 32 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

For Windows: install_directory\start_<systemid>_trans.bat install_directory\start_<systemid>_batch.bat For UNIX/Linux: install_directory/start_<systemid>_trans install_directory/start_<systemid>_bat Where <systemid> represents the SAP System ID specified at installation. When the RFC Server starts, it looks for the SAP Gateway and your installation of Data Services. Therefore, you should have both the SAP Gateway and Data Services running before starting the RFC Server. Additionally, the RFC Server looks for the Java Runtime Environment. Therefore, the Java runtime must be installed relative to where the RFC Server startup script runs, or you must set the JAVA_HOME environment variable to where Java is installed so that the RFC Server can find it. Stop the RFC Server If you installed the RFC Server on Windows as a Windows Service, you can stop the RFC Server as you would any Windows Service. If you did not install the RFC Server as a Windows Service, you must on the machine that hosts the RFC server use Ctrl-C in the RFC Server console to terminate the RFC Server process. Note that this method may on rare occasion cause SAP to show a connection to the RFC Server after the RFC Server has stopped. If you use transaction SMGW from within your SAP system in an attempt to stop the RFC Server, the RFC Server restarts and reconnects. Also, if you are running multiple RFC Servers with the same TP name, this method may simultaneously stop all RFC Servers with that TP name (for more information, see SAP Note 923248). Further, if you use transaction SMGW to stop the RFC Server that has been installed as a Windows Service, and the RFC Server fails to restart properly, the Windows Services Console would not reflect that the RFC Server is not running until the Console is refreshed. Chapter 2: Installing Data Quality for SAP 33

Install the BAdIs support package Before you proceed with these steps, make sure that your SAP system complies with all of the prerequisites described in System requirements on page 18. This version requires that you have the BAdIs from the previous version of this product, Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1), installed. The BAdIs portion of this product upgrades the BAdIs from that version, and cannot be installed without.! If you are doing a fresh installation of this product, you must install the BAdIs portion of the previous version of this product, according to the instruction found in BAdI-only for fresh installation on page 123, before proceeding with the installation of this BAdIs support package. Because of the variety of SAP versions, the illustrations that we use throughout these procedures may differ from what you encounter while installing BAdIs on your specific version of SAP Solution. We assume that you have knowledge of SAP administration to help you successfully navigate through the installation. Even though the screens may differ from version to version, follow all steps in these processes. To install the BAdIs on your system, you must complete these tasks: Step 1: Import the Data Quality Management support package on client 000 on page 34 Step 2: Re-activate the Business Configuration Sets on each target client on page 36 The BAdIs support package is installed using the support pack manager SPAM. Step 1: Import the Data Quality Management support package on client 000 You must have the previous version of this product, SAP BusinessObjects Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1) installed, using the full installation instructions of the User s Guide for that version.this release upgrades that previous version. You must have the latest Support Package Manager (SPAM) update/patch installed on your SAP system. (For more information, see SAP Note 822379.) Choose an applicable.sar package for your Basis version from the tables below, import the Data Quality Management package on the reference client (client 000), and then activate (or reactivate) BC Set /FLDQ/47U6X to import new customizing data. Basis 6.20 SAR file \6.20\DATA\SAPK-40A1HINFLDQ.SAR Application Server all You must (re)activate BC Set /FLDQ/47U6X to import new customizing data. 34 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Basis 6.40 SAR file \6.40\DATA\SAPK-40A1HINFLDQ.SAR Application Server all You must (re)activate BC Set /FLDQ/47U6X to import new customizing data. Basis 7.00 SAR file \7.00\DATA\CRM50\SAPK-40B1HINFLDQ.SAR CRM 5.0 \7.00\DATA\CRM2007\SAPK-40B1HINFLDQ.SAR and \7.00\DATA\CRM2007\SAPK-40B2HINFLDQ.SAR Application Server CRM 2007 \7.00\DATA\ECC6\SAPK-40A1HINFLDQ.SAR ECC 6 Basis 7.00 users must have the SPAM 21 update/patch or greater to be able to load a.sar package. (For more information, see SAP Note 822379.) Also, you must (re)activate BC Set /FLDQ/47U6X (and BSP BC Set /FLDQ/ BSP_PV, if applicable) to import new customizing data. Basis 7.01 SAR file \7.01\DATA\CRM7\SAPK-40A1HINFLDQ.SAR CRM 7.0 \7.01\DATA\ERP6 EP4\SAPK-40A1HINFLDQ.SAR Application Server ERP 6 EP4 You must (re)activate BC Set (and BSP BC Set, if applicable) /FLDQ/47U6X to import new customizing data. Also, you must (re)activate BC Set /FLDQ/47U6X (and BSP BC Set /FLDQ/ BSP_PV, if applicable) to import new customizing data. Basis 7.10 SAR file \7.10\DATA\SAPK-40A1HINFLDQ.SAR Application Server FSBP You must (re)activate BC Set /FLDQ/47U6X to import new customizing data. Importing the Data Quality Management package To import the Data Quality for SAP Support package: 1. Enter the transaction SPAM to open the Support Package Manager window. 2. Click the Support Package menu and choose Load packages > From Frontend. Chapter 2: Installing Data Quality for SAP 35

3. In the Select CAR/SAR archive window, browse to the \DATA directory of the Data Quality for SAP SAP PV and DES BAdIs installation media, and select the applicable.sar file. If the path is long and the system generates an error, copy the file to a local directory location and load it from there. 4. Click Open and then click Yes to load the.sar file. The contents of the compressed.sar file appears. 5. Click Decompress. 6. Continue with standard Support Package process for component /FLDQ/. (For further instructions on importing a Support Package, see the documentation for your SPAM tool.) 7. Click Cancel to close the tool Step 2: Re-activate the Business Configuration Sets on each target client Re-activate the Business Configuration Sets on each of the target clients (non-000 logon clients) that you want to configure for use with Data Quality for SAP. Repeat these steps for each target client that you want to configure for use with Data Quality for SAP. 1. From one of the target clients, use /nscpr20 to navigate to the Business Configuration Sets : Activation transaction. 2. Type /FLDQ/47U6X in the BC Set input field and click Enter. The following Short text appears: Business Configuration Set for BusinessObjects 06-21-09. (The date varies.) 3. Click the Activate button or select Activate from the BC Set menu. 4. Create a new change request. (Click OK if a caution appears.) 5. In the Activation Options window click Continue Activation (Enter). An Activation completed message appears at the bottom of the window. For IC WebClient, reactivate the BSP BC Sets If you use the IC WebClient, you must also re-activate the BSP BC sets. To reactivate the BSP Business Configuration Sets, open the target client (the one that you want to configure for use with the Data Quality for SAP) and follow these steps: If you are upgrading a current WebClient installation, delete the contents of the /FLDQ/AD_FORMMAP table prior to activating the BC set. 36 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

1. Enter transaction /nscpr20 in the target client to navigate to the Business Configuration Sets : Activate transaction. 2. Type /FLDQ/BSP_PV in the BC set input field and click Enter. The following Short text appears: BC Set for BusinessObjects BSP_PV Product 07/08/09. (The date varies.) 3. Click Activate. 4. Create a new change request when the window appears. (Dismiss any caution that may appear.) 5. Click Continue Activation (Enter) in the Activation Options window. An Activation completed message appears at the bottom of the window. 6. Repeat these steps for each target client that you want to configure for use with Data Quality for SAP. Chapter 2: Installing Data Quality for SAP 37

Quarterly Adjustment Reports SAP provides standard reports for Quarterly Adjustments, which allow you to validate all the addresses in your database in a three-step batch process. You may want to run Quarterly Adjustments other times after this installation on a regular, pre-determined schedule and you should run Quarterly Adjustments after installing new Data Services address directories from SAP Business Objects to validate data that may have changed due to the renaming of streets, the development of new areas, and so on. If you did not have Data Quality for SAP installed, to run a Quarterly Adjustment Report you would execute the defined SAP reports RSADRQU1, RSADRQU2, and RSADRQU3. Installing Data Quality for SAP allows you to substitute the second of these standard reports, RSADRQU2, with the custom report /FLDQ/ RSADRQU2, and take advantage of the postal validation capabilities provided by Data Quality for SAP. The running of these reports exchanges records between SAP and the RFC Server. Then the validated and updated addresses are committed to the SAP database. Report RSADRQU1 You use report RSADRQU1 to select the addresses that are to be cleansed. To run the report: 1. On a target (non-000) client, start the report RSADRQU1 by running the transaction code SA38. The ABAP Execute Program window appears. 2. In the Program field, enter RSADRQU1 and click the Execute button (F8). The Create an address index for the quarterly adjustment window appears, presenting several options. 3. Specify the countries for which the quarterly adjustment is to be performed. This field is required by default. 4. Specify the cities within the selected country or countries for which the quarterly adjustment is to be performed. This field is optional. 5. Specify the postal code or range of postal codes for which the Quarterly Adjustment is to be performed. This field is optional. 6. Change the packet size only if you have experienced problems in running Quarterly Adjustment Reports previously. SAP Business Objects recommends that you maintain the default setting for packet size of 1000 records. This number determines how many records are processed and stored at one time. All addresses that meet the selection conditions are read, regardless of the packet size. The setting should be adjusted only in response to performance issues previously encountered. 7. Select the radio button to exclude, check additionally, or check separately addresses that have not previously been subjected to postal validation. This setting is not relevant to Data Quality for SAP s functionality, so the setting will not affect the results of postal validation. 38 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

8. Select the appropriate radio button either to cancel the Quarterly Adjustment if INDX exists or to overwrite the existing INDX. Running RSADRQU1 creates a temporary table called INDX, which is used by the other two Quarterly Reports and deleted when the process completes successfully. If the Quarterly Adjustment Reports process did not complete successfully, the INDX table from the failed attempt may still be available. This option allows you to cancel the Quarterly Adjustment process rather than overwrite the existing data, or to proceed creating INDX with the current parameters. You must select Overwrite existing INDX if the Quarterly Adjustment is terminated for some reason and you want to start it again. 9. Click the Execute button (F8) to run RSADRQU1. A confirmation window appears. Report /FLDQ/RSADRQU2 Instead of the defined SAP report RSADRQU2, you next execute the report /FLDQ/RSADRQU2. You use this report to read the addresses stored temporarily in INDX and update INDX. 1. Start the report /FLDQ/RSADRQU2 by running the transaction code SA38. The ABAP Execute Program window appears. 2. In the Program field, enter /FLDQ/RSADRQU2 and click the Execute button (F8). The Check and update address data in quarterly adjustment window appears. 3. Check the Clear Previous Error Codes box to clear error codes from previous runs or uncheck the box to have the new error codes appended. Check the Skip D records during the Quarterly adjustment process box only if you want to run postal validation without checking D records. A D record is a record that has its check status set to D. There are three possible check status values. C = Postal or address data is known and does not contain any errors D = Postal or address data may have errors = Postal Validation has not been run If a record has a check status set to D, the address in that record has previously been checked and the user selected to save the address without cleansing it. Records with a check status of D may contain faulty address data as a result. When running report /FLDQ/RSADRQU2, you may want to skip D records because a user has already made the decision to save the address without cleansing it. A confirmation window appears. If any records failed during validation, those records are shown here. Postal Validation error logs from /FLDQ/ RSADRQU2 The system uses the Clear Previous Error Codes check box to determine whether the report saves validation errors logged from previous runs of the Quarterly Adjustments, or errors only from this run. Chapter 2: Installing Data Quality for SAP 39

The check box Clear Previous Error Codes affects the content of the report displayed as a result of running the custom error report /FLDQ/AD_REPT_DISP_QTRERRORLOG. It does not affect the content of the error log that appears automatically after you run the final Quarterly Adjustment Report. Report RSADRQU3 You use report RSADRQU3 to commit updates to the SAP database with the validations performed in /FLDQ/RSADRQU2.! If execution errors occur when you run the report /FLDQ/RSADRQU2, you must not run the report RSADRQU3 next. All three of the Quarterly Adjustment reports must be run successfully in sequence. Running RSADRQU3 on data resulting from a failed run of /FLDQ/RSADRQU2 can compromise the integrity of the data written back to the SAP system. To run the report: 1. Start the report RSADRQU3 by running the transaction code SA38. The ABAP Execute Program window appears. 2. In the Program field, enter RSADRQU3 and click the Execute button (F8). A confirmation window appears, indicating that the addresses have been removed from postal check and committed to the database. If the Quarterly Adjustment process finds that any records are incorrect, the window displays a list of those records. You should next run a Quarterly Adjustment custom error report, which provides you a hyperlink to each of these records so that you can directly edit each record as necessary. If the report terminates or is terminated prematurely for any reason, it can be started again at any time. When this report has finished, the system displays an error log of all addresses that could not be updated on this run of Quarterly Adjustments. Though report RSADRQU3 is an SAP report, you must have the RFC Server running to process records from the pending update table.! While RSADRQU3 is in process or not started, the Quarterly Adjustment remains active. If addresses are changed using other SAP business transactions while the quarterly adjustment is in process, these addresses can not be updated by report RSADRQU3. You must complete the Quarterly Adjustment process before making other changes to the postal address data if you want the new data included in the adjustments. 40 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Quarterly Adjustment custom error report Data Quality for SAP provides a custom error report, /FLDQ/AD_REPT_DISP_QTRERRORLOG, which you can use to display the address validation errors that occurred during all Quarterly Adjustment runs since the last time you cleared the previous error codes. To run the Quarterly Adjustment custom error report: 1. Start the report /FLDQ/AD_REPT_DISP_QTRERRORLOG by running the transaction code SA38. The ABAP Execute Program window appears. 2. In the Program field, enter /FLDQ/AD_REPT_DISP_QTRERRORLOG and click the Execute button (F8). The Display Address Errors generated during Quarterly Adjustment window appears. At this window you can set limits to filter and sort the displayed results. 3. Set any filters and click the Execute button (F8). An error log is displayed showing a list of records on which postal validation errors occurred. Each field item is a hyperlink to the record itself, which you can use to go to the record for direct editing. You must repeat the entire procedure for running Quarterly Adjustments for each target (non-000) client as part of the installation of Data Quality for SAP. Chapter 2: Installing Data Quality for SAP 41

Run the initialization program The last step to prepare this product for use is to run the initialization program on each target (non-000) client. This step is required for all installations of this product.! Before running the initial setup program, you must run Quarterly Adjustments to perform postal validation on the data that already exists in your SAP system. This process is required even if you are upgrading this product from a previous version. Purpose of initial setup The initial setup program prepares your existing data for matching with duplicate check and error tolerant search. You must run the initial setup program before using this product, and again if you make changes to the match expression that controls the parameters of duplicate check and error tolerant search. Performing batch match from the same window The window from which you execute the initialization program also contains the options to perform batch match. You need not perform batch match to prepare this product for use. You can optionally run batch match any time later. For information on running batch match, see Batch mode on page 81. Run the initial setup To run the initial setup program: 1. Invoke the transaction SA38 in the command box. The ABAP: Execute Program window appears. 2. In the Program field, enter /FLDQ/RSADRINI and click the Execute button (F8). The Initial Match Code (Index) Setup Program window appears. 3. Check the box for Perform Initialization and click the Execute button (F8). The program executes. Installation and setup are complete in this target (non- 000) client. 4. Repeat these steps on each target client that you want to configure for use with this product. You should execute the FLDQ/RSADRINI program only when users are not updating records in the system, such as during the initial setup. When users are working in the SAP system and updating records, use instead the /FLDQ/RSMTCCODE program (Match Code Creation Program). This program performs the same function as the RSADRINI program, but on only a subset of the data. This program simultaneously locks records as it runs so that you can run it while users are updating records in the system. 42 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Configure geocoding If you have purchased the geocoding option for this product, you can make configurations to return latitude, longitude, and relevant status information for a U.S. address record. To configure geocoding for your business partner records, you must perform the following actions described in this section. Configure the RFC Server for geocoding You must configure the RFC Server to handle geocoding. To configure the RFC Server, edit the main configuration file of the RFC Server, flrfcsrv.xml. You can find information on editing flrfcsrv.xml in Editing flrfcsrv.xml on page 62. In flrfcsrv.xml, remove the comment notation from the XML key <address_geo>. The line <!--address_geo>service_realtime_dq_sap_address_geo</address_geo--> is changed to <address_geo>service_realtime_dq_sap_address_geo</address_geo> Register geocoding program in SAP To register the geocoding program in your SAP system: 1. From the IMG, navigate to General Settings > Set Geo-Coding > Register Geo-Coding Program in the System. The Geo-Coder Mapping Table window appears. 2. Enter the following values for the fields: Field Source ID Class Function Module Destination Value SAP1 CL_GEOCODER_GENERIC_RFC ADDR_GEO FL_GDQC_SERVER The default value for the destination is FL_GDQC_SERVER. 3. Save the entry. Configure the country To configure the country for geocoding: 1. From the IMG, navigate to General Settings > Set Geo-Coding > Assign Geo- Coding Program to Countries. 2. Create a new line for the country US. 3. For the Source ID, enter SAP1. 4. Enter a value for the sequence. If a line already exists for US, select a number smaller than the existing line. 5. Set the exclusive flag. Chapter 2: Installing Data Quality for SAP 43

6. Save the entry. Designate fields to use for geocoding When attempting to determine the latitude and longitude of an address, the SAP system passes all address fields of the address record to the geocoding program. When a user makes a change to an address record, the new data is sent to the geocoding program. However, only certain fields of an address record are relevant to determining latitude and longitude. In this procedure, you designate the fields to use for geocoding, which allows the non-designated fields to be changed without re-sending data to the geocoding program. To designate default fields to use for geocoding: 1. From the IMG, navigate to General Settings > Set Geo-Coding > Assign Relevant Address Fields for Geo-Coding. 2. In the Address Fields Relevant for a Geo-Coder table, enter for the Source ID SAP1 and enter a field to use as a default field for geocoding (for example, COUNTRY). 3. Repeat to create other entries for any additional fields you want to use as a default field for geocoding (for example, REGION or STREET). 4. Save the entry. 44 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Chapter 3: Configuring through the IMG Now that you have installed all components of SAP BusinessObjects Data Quality Management, version for SAP Solutions, you can configure it to handle postal validation and duplicate searching with settings appropriate for your business. You can customize many aspects of Data Quality for SAP through the activities this product adds to the SAP Implementation Management Guide (IMG). This chapter explains those activities and the options you have for configuration. Chapter 3: Configuring through the IMG 45

Locating the Data Quality for SAP IMG activities You can find the Data Quality for SAP IMG activities within the IMG structure by following this process: 1. Use the transaction SPRO to access the Implementation Guide (IMG) structure. 2. Navigate to the BusinessObjects : Global Data Quality Connector node. The navigation to this node path depends on the Basis version that you use. Basis version Path 6.20 (R/3 4.7) SAP Web Application Server > Basis Services > Address Management 6.40 (ECC 5.0) SAP NetWeaver > SAP Web Application Server > Basis Services > Address Management 7.00 (ECC 6.0 and CRM 5.0) 7.01 (CRM 7.0 and ERP 6.0) 7.10 (Banking Services 6.0) SAP Web Application Server > Application Server > Basis Services > Address Management SAP NetWeaver > Application Server > Basis Services > Address Management SAP Web Application Server > Application Server > Basis Services > Address Management The Data Quality for SAP activities are the nodes at the bottom level of this structure. The remainder of this chapter is a description of these activities. 46 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

SAP handshake with RFC server This activity allows you to define the RFC destination and test whether the components of Data Quality for SAP are able to communicate by invoking a TCP/IP handshake. The activity is invoked for the first time during the installation and configuration of Data Quality for SAP. You can perform the activity again at any time. For details of performing this activity, see Run the initialization program on page 42. Chapter 3: Configuring through the IMG 47

Maintain Supported Countries This activity maintains the ISO country codes for the countries for which Data Quality for SAP provides postal validation by making changes to the table / FLDQ/AD_VAL_CNT. The list of countries that are supported depends on the postal directories that you have licensed from SAP Business Objects. If you did not purchase support for all countries or if you do not want postal validation enabled for some of the supported countries for which you purchased support, you can remove those ISO country codes from the filter using this activity. Remove the country codes When you click the Maintain supported countries activity, the table /FLDQ/AD_VAL_CNT is displayed, showing the list of supported countries. From this display, you can remove from the filter those ISO country codes for which you do not want postal validation enabled. To remove a country code: 1. Select the country code from the list of supported countries. 2. Click the Delete button. 3. Save the changes. 48 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Maintain exception table of transaction codes This activity allows you to disable suggestion lists, preventing them from being displayed for specific transactions, as well as control postal validation per transaction, search, and duplicate check. During postal validation, Data Quality for SAP takes ambiguous, incomplete, or inaccurate address data and offers the user a list of address data choices that fit the content of official postal directories. The list is called a suggestion list. The user must select the item from the suggestion list containing the appropriate address data in order for postal validation to continue. There may be some transactions for which you do not want the user to be presented with a suggestion list and you may disable suggestion lists for those transactions. By default, suggestion lists are enabled for all transactions. In the default window, there is a transaction code for DEFAULT that controls transactions but the check boxes are unmarked. By checking the Suppress Suggestions box for DEFAULT, you suppress suggestion lists for all transactions. You can instead add transaction codes and suppress suggestion lists only for that code. Add a transaction code to the exception table To add a transaction code to the exception table: 1. From the IMG, click on the activity Maintain exception table of transaction codes. The Maintain exception table of transaction codes window appears. 2. Click the New Entries button. The New Entries: Overview of Added Entries window appears. 3. Enter a Transaction code to specify the transactions for which you do not want suggestion lists to appear. 4. Check the Suppress Validation box if you want to prevent postal validation for that transaction (not recommended). 5. Check the Suppress Search box if you want to prevent both error tolerant search and duplicate checking for that transaction (not recommended). 6. Check the Suppress Dialog box to prevent suggestion lists from appearing in dialog boxes. 7. Exit the window to save the changes and return to the Maintain exception table of transaction codes window. Additionally, you can select and deselect the suppression check boxes directly from the Change View Maintain exception table of transaction codes : Overview window. Chapter 3: Configuring through the IMG 49

! Warning: This activity also lets you disable both postal validation and error tolerant search/duplicate check on a transaction basis. However, SAP Business Objects does not recommend disabling this capability because doing so would allow invalid address data and duplicates to be stored in your SAP system. Essentially, suppressing these capabilities turns off certain functionality of Data Quality for SAP without removing it from your SAP system. Suppressing only the suggestions without suppressing validation or searches ensures that invalid data is not stored. Additionally, suppressing error tolerant search/duplicate check will prevent records from being stored in the table /FLDQ/AD_PUPDATE, where updated records are held before being committed to the SAP database. In the following illustration, the transaction code XD01 has been added to the Change View Maintain exception table of transaction codes : Overview window. Check the appropriate boxes to suppress postal validation, duplicate searches, or duplicate suggestions. 50 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Maintain table to activate SAP postal code check before postal validation This activity lets you to define countries for which you want the SAP postal code check to be performed before Data Quality for SAP validates the rest of the address data. Data Quality for SAP can validate addresses even if they do not contain a postal code. Therefore, by default, Data Quality for SAP disables a postal code check that SAP normally performs on the address before Data Quality for SAP validates the rest of the address data. Disabling the SAP postal code check allows Data Quality for SAP to perform postal validation on the data as it was entered by the user. By default, this table is blank because there are no countries for which Data Quality for SAP needs a valid postal code before processing. You need to change this setting only if you want the SAP postal code check to be performed for a certain country. Add a country to the table To add a country to the table to activate SAP postal code check before postal validation: 1. From the IMG, select the activity Maintain table to activate SAP postal code check before postal validation. The Maintain table to activate SAP postal code check before postal validation window appears. 2. Click the New Entries button. The New Entries: Overview of Added Entries window appears. 3. Enter in the ISO Country code field the two-letter ISO code for the country for which you want a postal check performed before complete address validation occurs. 4. Save the changes and exit the window. The Maintain table to activate SAP postal code check before postal validation window returns. This activity exists only in case future versions of Data Quality for SAP support additional countries for which a postal check must occur for proper address validation. This activity does not assist this version in performing address validation. Chapter 3: Configuring through the IMG 51

Maintain fields for address reviewer This activity allows you to define which fields are displayed in the address reviewer dialog and the order of those fields. During postal validation, Data Quality for SAP may modify the address data to make the address data conform more completely to the data in official postal directories. If Data Quality for SAP modifies the address data, it displays a dialog containing both the original and modified address data. The user can choose either to keep the original data or to accept the modified data. Because standard street address data and P.O. Box data require different sets of fields for postal validation, you must define the fields for both address types. Fields and order for standard street addresses By default, the following fields are displayed for standard street addresses and given the following order: 1. BUILDING 2. HOUSE_NUM1 3. STREET 4. CITY 5. REGION 6. POST_CODE1 7. COUNTRY Fields and order for P.O. Box addresses By default, the following fields are displayed for P.O. Box addresses and given the following order: 1. PO_BOX 2. POST_CODE2 3. PO_BOX_LOC 4. CITY1 5. PO_BOX_REG 6. REGION 7. PO_BOX_CTY 8. COUNTRY Make changes to the fields for the address reviewer To make changes to the fields or the order of the fields displayed in the address reviewer: 1. From the IMG, select the activity Maintain fields for address reviewer. The Maintain fields for address reviewer window appears. 2. Check or uncheck boxes in the Display for Street Addr and Display for PO Box columns. Data Quality for SAP displays the fields checked in the address review dialog. 52 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

3. Type sequential numbers for all the checked fields in the Sequence Number fields to indicate the order of the fields for street address data and P.O. Box data. You must number both the street address data and P.O. Box data in sequence from 1 to the total number of displayed fields. 4. Save the changes and exit the window. Chapter 3: Configuring through the IMG 53

Maintain fields for duplicate hit list display In this activity, you can define which fields are displayed in the hit list and their order for error tolerant search or duplicate check. You must define the fields for both hit list types. SAP Basis 6.40 shows an additional window in this activity that other SAP versions do not show. This window is generated by SAP and not Data Quality for SAP, and therefore is not documented in this Guide. Fields and order for error tolerant search and duplicate search By default, the following fields are displayed in this order for the error tolerant search and duplicate search lists: Error tolerant search list 1. Score 2. Customer or Vendor or BusPartner 3. Name 4. Name2 5. Street 6. City 7. Region 8. Postal Code 9. Country Duplicate Hit List 1. Score 2. Last name 3. First name 4. House number 5. Street 6. City 7. Region 8. Postal Code 9. Customer 10. Vendor 11. BusPartner 54 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Make changes to the fields for the duplicate hit list display To make changes to the fields or the order of the fields in the duplicate hit list display: 1. From the IMG, click on the activity Maintain fields for duplicate hit list display. The Maintain fields for duplicate hit list display window appears. 2. Check or uncheck boxes in the Display Flag (Search) and Display Flag (Dup. Check) columns. The fields checked appear in the duplicate check or error tolerant search dialog. 3. Type sequential numbers for all the checked fields in the Sequence (Search) and Sequence (Dup. Check) fields to indicate the order of the fields for duplicate check or error tolerant search data. Both the duplicate check and error tolerant search data are to be numbered in sequence from 1 to the total number of displayed fields. 4. Save the changes and exit the window. Chapter 3: Configuring through the IMG 55

Maintain operating parameters In this activity, you can modify one of the several operating parameters that affect the behavior of Data Quality for SAP. Operating parameters The following table shows the operating parameters, the default values, and a description of each. Parameter Name Default Value Description ADD_REVIEW_FLAG X Flag to determine whether a dialog is displayed that allows the user to review the original and modified address during postal validation. Valid values are 'X' to receive this confirmation dialog or a space not to receive the dialog. AD_ADDRESS_ FINISHED_FUNC_NM AD_ADDRESS_SEARCH_ FUNC_NM AD_REVIEW_NEW_ WIDTH AD_REVIEW_ORIG_ WIDTH BATCH_MATCH_RFC_ DEST DRVR_ADDR_IGNORE_ NAME_MATCH_CODE none none Used to allow the creation of a custom function module, that can be called by the RFC Server when a match code is created to add data to the match code data structure. Used to allow the creation of a custom function module that can be called by the RFC Server during address search and duplicate checking to add data to the match code data structure. 35 Width by number of characters of the validated address column in the Postal Validation -- Review Changes window, allowing you to adjust the column size if addresses are too long to fit. 25 Width by number of characters of the original address column in the Postal Validation -- Review Changes window, allowing you to adjust the size of the column if addresses are too long to fit. FL_GDQC_BATCH X Dedicated RFC Server for handling duplicate search functionality in batch mode (called batch match). This value is also called the Program ID of the RFC Server. By default, this product ignores driver name match codes if the driver address is present. To reverse this behavior, make the Parameter Value blank. ENABLE_DES_FUN_NM none Administrator-specified function to enable/disable Data Quality for SAP duplicate error tolerant search (DES). A possible value is the name of a function module to call before executing Data Quality for SAP s DES. The interface for the function module specified here must have one EXPORT parameter named VALID of type FLAG pass by value. After the function call, if VALID is X, postal validation processing occurs using Data Quality for SAP. If VALID is space, then only SAP's standard DES checks occur. ENABLE_PV_FUNC_NM none Administrator-specified function to enable/disable Data Quality for SAP postal validation. A possible value is the name of a function module to call before executing Data Quality for SAP s postal validation. The interface for the function module specified here must have one EXPORT parameter named VALID of type FLAG pass by value. After the function call, if VALID is X, postal validation processing occurs using Data Quality for SAP. If VALID is space, then only SAP's standard address checks occur. 56 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Parameter Name Default Value Description MAX_ACT_DUPS 100 Maximum number of actual duplicates displayed to the user. MAX_ELP_TM_DUPS 5 seconds Maximum time allowed in seconds to find duplicates. The value must be 1 second or greater. MAX_REC_QU2 10000 Maximum number of records per package passed to the RFC Server during the quarterly adjustment report. MAX_UPD_PEND 100 Maximum number of records that may be pending for update to the RFC Server when the RFC Server is unavailable. If the number of records pending exceeds this maximum, then the records are not updated automatically and require the pending record update report to be run. For information on the pending update report, see the section Records created without break keys due to downtime of RFC Server on page 88. NON_DIALOG_ERR_MSG space Toggles whether system messages are to be displayed in non-dialog mode. Valid values are X to enable passing of system error messages in non-dialog mode for postal validation or a space not to receive the system message. PKG_SIZE_DUPS 1000 Package size for passing candidate duplicates to the RFC Server. RFC_DEST FL_GDQC_SERVER Name of the RFC Server contacted through a Remote Function Call. This name must correspond to a valid destination that describes a functioning RFC Server. TECH_ERR_FUNC_NM none Name of a user defined function module that is called whenever a technical error occurs. Operating parameters used only by the CRM IC WebClient or CRM WebClient configuration The following table shows the operating parameters, the default values, and a description of each for operating parameters used only by the CRM IC WebClient or CRM WebClient. Parameter Name Default Value Description BSP_DES_THRESHOLD 70 The threshold value for BSP duplicate error search. This parameter is not applicable to CRM 7 or CRM 2007 systems. Users of these systems can change the threshold in the Activate Duplicate Check and Determine Limit for BAPIs section of the IMG, under the Duplicate Check node. BSP_RANGE_HEIGHT 225 Height of child window for range queries in BSP Postal Validation. BSP_RANGE_WIDTH 400 Width of child window for range queries in BSP Postal Validation. BSP_REVIEW_HEIGHT 320 Height of address review BSP page. BSP_REVIEW_WIDTH 700 Width of address review BSP page. BSP_SUGG_LIST_HEIGHT 475 Height of child window for suggestion lists in BSP Postal Validation and Duplicate Check/Error tolerant Search. BSP_SUGG_LIST_WIDTH 700 Width of child window for suggestion lists in BSP Postal Validation and Duplicate Check/Error tolerant Search. Modify the parameters To make changes to operating parameters: Chapter 3: Configuring through the IMG 57

1. From the IMG, click on the activity Maintain operating parameters. The Maintain operating parameters window appears. 2. Change the Parameter Value field for any of the parameters. 3. Save the changes and exit the window. 58 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Map address types for Quarterly Adjustment Data Quality for SAP provides the custom error report /FLDQ/AD_REPT_DISP_QTRERRORLOG to log invalid addresses found by Data Quality for SAP during the execution of Quarterly Adjustment Reports. This activity allows you to make each item in the list of invalid addresses a hyperlink that takes the user directly to the appropriate transaction to edit the incorrect address. Allowing the user to access the transaction and address in this manner saves the user the effort of manually entering the transaction and locating each invalid address for editing. Defining mappings The report /FLDQ/AD_REPT_DISP_QTRERRORLOG lists the Address Type, Address Key, and Address Type Code for each address. The Address Key can serve as a hyperlink that calls the appropriate transaction to edit the address only if the Address Type Code and Parameter ID for this Address Type are defined in table /FLDQ/AD_QTR_OBJ. If the mapping for a particular Address Type does not exist in this table, clicking on the Address Key field has no effect. For each Address Type in the error report /FLDQ/AD_REPT_DISP_QTRERRORLOG, an edit transaction and the Parameter ID must be defined in order for the key field to serve as a hyperlink. Some of these mappings are predefined in Data Quality for SAP as shipped, but you must add mappings for all other Address Types for which you want to create hyperlinks. For example, when linking to a Customer record, for transaction XD02 you would define the Parameter ID as KUN. Predefined mappings Data Quality for SAP ships with transaction mappings for the following Address Types: KNA1 - Customer LFA1 - Vendor BUS0010 - Functional Location BUS1006 - Business Partner BUS1006001 - Business Partner Employee BUT052 - Person within Organization USRCOMPANY - Company You must perform the activity described in the following section to add a mapping for any other Address Types. Add a mapping for an Address Type Code To add a mapping for an Address Type Code: 1. Run the /FLDQ/AD_REPT_DISP_QTRERRLOG report. 2. Write down the Address details for an entry for which the hyperlink does not work, noting these three items: Address Type Chapter 3: Configuring through the IMG 59

Address Key Address Type Code 3. Use the Address Type and Address Key to determine which SAP transaction should be used to edit the address record. 4. Navigate to the Edit transaction. 5. Place your cursor in the Key field (for example, Customer in transaction XD02). 6. Press the F1 key. 7. Click the Technical Information button on the Performance Assistant dialog menu bar. 8. Note the Parameter ID value in the Field Data section. 9. Use the IMG Activity Map of Objects to transaction for Quarterly Error Report. 10. Click the New Entries button and fill in all three columns using the data you have collected: Enter the Address Type Code in the Object Type field. Enter the transaction Code in the Transaction for Edit field. Enter the Parameter ID in the Object Parameter ID field. 11. Save. 12. Repeat as necessary for each address that does not have a working hyperlink. 13. Create a Customizing Request. 60 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Chapter 4: Configuring the RFC Server Through the installation process, all of the necessary files on the RFC Server are configured to properly run SAP BusinessObjects Data Quality Management, version for SAP Solutions. You may, however, change items after installation. Chapter 4: Configuring the RFC Server 61

Configuring through flrfcsrv.xml The main configuration file of the RFC Server is flrfcsrv.xml. Through the parameters of this file, you control several aspects of Data Quality for SAP, such as how Data Quality for SAP handles logging and various performance-related settings. This section discusses certain critical settings of this configuration file.! You should not make changes to flrfcsrv.xml without a full understanding of the implications of those changes. Errors in this configuration file could disable Data Quality for SAP. Location of flrfcsrv.xml The file is located on your system at install_directory\config\flrfcsrv.xml. Editing flrfcsrv.xml Edit flrfcsrv.xml as you would any other XML file. If you have an XML editing program that you are familiar with, you can use that program. On Windows systems, we recommend that you do not use Notepad when editing the configuration files. If you do use Notepad, the data will display all in one line, making it difficult to read. When you edit a value in flrfcsrv.xml, make sure that you alter configurable values but do not change the structure or required parameters of the file. Be sure to make a backup of flrfcsrv.xml to preserve its original state in case you later want to discard your changes. SAP settings and DQ Server settings The settings under the commented headings <!--SAP settings --> and <!--DQ Server Settings --> are determined at the time of installation. If you want to run multiple instances of the RFC Server, you can override these settings by making new settings in the <override> tags, found beneath these settings in the file. See Overrides on page 66 for details on how to override these settings. File settings The following table shows the configurable settings and defaults in the section under the commented heading <!-- File Settings -->. All of these settings must have an entry. Setting Description Default log_level Provides two levels of logging. 1 - Only serious errors are logged 2 - Serious errors and any important warnings and information messages are logged. 2 62 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Setting Description Default uc_logging_flag uc_logging_file_dir uc_playback_flag uc_bytes_per_log_file uc_connect_timeout_ sec uc_retry_connect_ count Enables logging for the Universal Connector, which provides connection to Data Services. This setting is provided to allow customers to provide detailed information to customer support representatives. You should not change these values unless requested in a customer support situation. Sets the directory of the log file for the Universal Connector, which provides connection to Data Services. This setting is provided to allow customers to provide detailed information to customer support representatives. You should not change these values unless requested in a customer support situation. Enables the playback of data transfer feature of the Universal Connector, which provides connection to Data Services. This setting is provided to allow customers to provide detailed information to customer support representatives. You should not change these values unless requested in a customer support situation. The size, in bytes, that a log file is allowed to attain before an additional log file is created for logging, which provides connection to Data Services. This setting is provided to allow customers to provide detailed information to customer support representatives. You should not change these values unless requested in a customer support situation. Maximum amount of time in seconds the RFC Server should attempt to connect to Data Services. Must be greater than or equal to zero. A setting of zero indicates no timeout. Maximum number of times the RFC Server should attempt to retry to connect to Data Services. false <none> false 1000000 300 1 Chapter 4: Configuring the RFC Server 63

Setting Description Default uc_connect_delay_ between_retries enable_trace region_file fmt_file Amount of time to wait between attempts to communicate with the Data Services. Must be greater than or equal to zero. A setting of zero indicates that the RFC Server is to attempt continuously to connect to the Data Services and SAP Gateway without pausing between attempts. Determines whether the RFC Server should generate trace files. A trace file provides you with a history of transactions. Possible values are yes and no. Location and name of regions.xml, which sets regions for a specific country code. The path is relative to the installation of Data Quality for SAP Location and name of fmt.xml file, which is the format file., which specifies the format of tables that the gateway passes as arguments to the RFC Server. 0 yes config/regions.xml config/fmt.xml General settings The commented heading <!-- General Settings --> has only one setting. Setting Description Default max_sugg_items Maximum number of suggestion items the RFC server should return. Must be set to a minimum of 1. 99 Dataflows The settings under the commented headings <!--Dataflows --> correspond to the name of the dataflows that run each type of SAP request. If you change the name of the dataflow here, you must change it on your Data Services installation. For more information about dataflows, see the Data Services documentation that shipped with this package. Setting Description Default address_suggestion Defines the dataflow used for address suggestions. If you have purchased the DPV option for this product, installed the DPV directories in Data Services, and configured Job_Realtime_DQ_SAP_US_DPV_A ddress_cleanse_suggestions as a service, you can enable DPV address suggestions by changing the value of this key to Service_Realtime_DQ_SAP_US_DP V_Address_Cleanse_Suggestions. Service_Realtime_DQ_ SAP_Address_Cleanse_ Suggestions 64 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Setting Description Default address_geo This setting is not enabled by default. If you have purchased, installed, and configured geocoding, you should enable this setting. To enable geocoding, remove the comments from this key. Service_Realtime_DQ_ SAP_Address_GEO Reconnect Settings The following table shows the configurable settings and defaults in the section under the commented heading <!-- Reconnect Settings -->. Setting Description Default dq_server_sec_delay_ between_retries dq_server_retry_startup delay The delay in seconds between reconnect attempts. The delay in seconds to wait for the server to become stable before reattempting processing. 6 200 Termination email settings The following table shows the configurable settings and defaults in the section under the commented heading <!-- Termination email Settings -->. These settings are configured at installation, but you can change the settings of how the RFC Server sends out email notifications if it terminates. Setting Description Default email_host The name of the email server host. Set at installation email_port The port number of the email server. Set at installation email_sender The email address of the email sender. Set at installation email_recipient A list of all email recipients, separated by a comma. Set at installation Chapter 4: Configuring the RFC Server 65

Overrides You can override the settings in the other sections, which would be useful if you run more than one instance of the RFC Server. You can override only the following tags: sap_gwhost sap_gwserv sap_progid sap_unicode dq_type dq_host dq_port dq_web_server_url repository_path sub_options Create an override when RFC Server is not a Windows Service To create an override when the RFC Server is not a Windows Service: 1. Remove the comment tags from an override so that this section can be parsed by the RFC Server. 2. Fill in the value for the override name. <override name="my_new_override_name"> 3. Fill in the values for each tag that requires an override. If any tags are the same as the default setting, fill in the default setting value. 4. Set the override in the file install_directory\config\ start_<systemid>_trans.bat by indicating the name of the override. set OVERRIDE="my_new_override_name" 5. Save and close both files. When start_<systemid>_trans.bat runs, it looks for the named override in flrfcsrv.xml and executes those override settings. Create an override when RFC Server is a Windows Service If the RFC Server is a Windows Service, you must edit the Windows Registry to create an override. You should make a backup copy of the Registry before editing it. To create an override when the RFC Server is a Windows Service: 1. Remove the comment tags from an override so that this section can be parsed by the RFC Server. 2. Fill in the value for the override name. <override name="my_new_override_name"> 3. Fill in the values for each tag that requires an override. If any tags are the same as the default setting, fill in the default setting value. 4. In the Windows Registry Editor, navigate to My Computer > HKEY_LOCAL_MACHINE > SYSTEM > ControlSet001 > Services. Select the <service_name> that represents an instance of the RFC Server (for example, BusinessObjects DQM for SAP Batch xxx), right click on the 66 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

ImagePath of the service, and click Modify. At the end of the Value data, append the following tag: "-Dfl.links.sap.override=my_new_override_name" 5. Repeat the previous step for each instance of the RFC Server. 6. Save your changes and restart Windows. When start_<systemid>_trans.bat runs, it looks for the named override in flrfcsrv.xml and executes those override settings. Chapter 4: Configuring the RFC Server 67

Configuring through regions.xml The file regions.xml sets the regions for a specific country code, and correspond to the regions set in your SAP system using the Insert Regions IMG activity. Adding U.S. military regions This example describes adding U.S. military regions to regions.xml and your SAP system in order to enable this product to process addresses based on U.S. military regions. Add U.S military regions to the SAP system You must first add U.S. military regions to your SAP system, if these regions are not already enabled. See your SAP system documentation for information on how to insert regions through the IMG. You must make the following new entries in the Regions table: Country Region Description US AE Armed Forces Europe US AA Armed Forces America US AP Armed Forces Pacific Add U.S. military regions to regions.xml You must next add U.S. military regions to regions.xml to allow this product to process these regions. Edit regions.xml as you would any other XML file. If you have an XML editing program that you are familiar with, you can use that program. On Windows systems, we recommend that you do not use Notepad when editing the configuration files. If you do use Notepad, the data will display all in one line, making it difficult to read. Be sure to make a backup of regions.xml to preserve its original state in case you later want to discard your changes. To add U.S. military regions to regions.xml: 1. Open the file install_directory\config\regions.xml. 2. Add the following lines inside the <country code= US language= EN > section: <region code="aa" name="aa"/> <region code="ae" name="ae"/> <region code="ap" name="ap"/> <region code="ae" name="armed Forces Africa"/> <region code="ae" name="armed Forces Canada"/> <region code="ae" name="armed Forces Europe"/> <region code="ae" name="armed Forces Middle East"/> <region code="aa" name="armed Forces Americas"/> <region code="ap" name="armed Forces Pacific"/> 3. Save the file and restart the RFC Server. 68 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Chapter 5: Postal address validation This chapter describes the postal address validation features of SAP BusinessObjects Data Quality Management, version for SAP Solutions. Postal validation standardizes and corrects address data, protecting the integrity of that data in your SAP system. Postal address validation takes place in real time as users enter data and in a batch mode as part of the SAP Quarterly Adjustment Report. In real time, Data Quality for SAP validates and standardizes address data before the data is saved to the SAP database. During Quarterly Adjustment, this product replaces one of the SAP reports to standardize and correct the data that already exists. Chapter 5: Postal address validation 69

Interactive cleansing with Data Quality for SAP Data Quality for SAP s interactive, real-time postal address cleansing capability lets your SAP users cleanse address data at the point of entry and before the data is written into your SAP database. Using interactive cleansing For interactive address cleansing, the SAP user needs to take no unusual action. The data is cleansed automatically when the user saves the record or clicks the Check Address button. In this example, a user adds information for a new account. The data is not entered properly, and the ZIP Code was not entered. After the user attempts to save the record, the cleansing takes place in real time. The user is offered a window to review the changes that Data Quality for SAP made to the address. The user can accept the validated address, use the original address, or cancel the postal validation process. 70 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

At this window you have three button options: Button Accept Validated Address Use Original Address Cancel Action The previous window returns to focus with the corrected data populating the fields. The previous window returns to focus with the data as originally entered populating the fields. The previous window returns to focus and the process is cancelled. In this example, the following items were cleansed: The street name was corrected and properly cased. The city was spelled properly and properly cased. The state was cased properly. The ZIP+4 postal code was added. Multiple suggestions This illustration of the suggestion list (this time, as used in the IC Web Client) offers several addresses because the original provided address was ambiguous. In this window, the three button options are as follows: Button Select Use Original Address Cancel Action The previous window returns to focus with the data chosen here populating the fields. The previous window returns to focus with the data as originally entered populating the fields. The previous window returns to focus and the process is cancelled. Chapter 5: Postal address validation 71

Batch cleansing with Quarterly Adjustment Reports Data Quality for SAP accomplishes batch cleansing of postal addresses through Quarterly Adjustments. You first run Quarterly Adjustments with Data Quality for SAP s custom report as part of the installation and configuration steps. After installation, you may want to run Quarterly Adjustments on a regular, predetermined schedule. Also, you should run Quarterly Adjustments after installing new address directories from SAP Business Objects to validate data that may have changed due to the renaming of streets, the development of new areas, and so on. You may also want to further customize the display of the report by making each address listed in the report a hyperlink to the editable address entry. For information on this process, see Map address types for Quarterly Adjustment on page 59. 72 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Chapter 6: Duplicate check and error tolerant search This chapter describes the duplicate check and error tolerant search capabilities of SAP BusinessObjects Data Quality Management, version for SAP Solutions. These capabilities allow users to prevent the creation of duplicate customer records in the SAP database and also to search for customer records using information that may contain misspellings, omitted or transposed characters, and so on. Chapter 6: Duplicate check and error tolerant search 73

Understanding duplicate check and error tolerant search To help you understand the concepts of this chapter, this section briefly defines some of the terminology. Each of these concepts are explored in greater detail later in this chapter. Duplicate check Duplicate check is the process that assures that duplicate addresses are not entered into the SAP system when users create a new address record or update an existing one. During the check, if there are duplicates, the user is presented with the list of possible duplicates and allowed to select an existing customer and open that record, or to continue the process of adding the new customer, or to cancel the operation. Error tolerant search Error tolerant search allows users to find customer records using partial information. Based on the partial information provided by the user, Data Quality for SAP presents a list of possible matches to the user. The user then can choose to select a record from the search hit list of matches for further processing or can cancel out of the search hit list. Break Keys A break key is the search index for each record that this product uses for discovering similar, possibly matching, candidate records. A break key is made up of search terms that are arranged in a specific order. The search terms can be customized so that this product can determine that certain existing records have no realistic probability of being duplicates and should be ignored. In some previous versions of this product the term match code was used instead of break key. The decision to change this term to break key was made because break key is consistent with the terminology used for Data Services. 74 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Understanding break keys and data fields When given input data during duplicate check and error tolerant search, this product limits the number of records used in the search by determining a break key for the data. It then considers only stored records with the same break key value as the input data when searching for duplicates. This process is altered when Data Quality for SAP is configured to include records with empty break key values. For more information about the implications of configuring Data Quality for SAP to include records with empty break keys and the process to do so, see the section RSMTCCODE program error message on page 91. Included in this product are five best practices break keys that you can use to create the match codes to be used in finding similar records. You can change the match code to alter the matching results produced. Installing the Data Services Component of this product places in your Data Services installation the job DQ_SAP_Break_Key_Profiler. This job can process the data in your SAP system and recommend what match code would give the best results along with other configuration recommendations. For information about DQ_SAP_Break_Key_Profiler, see Using the Break Key Profiler on page 111. By default, this product uses a moderate break key that offers good performance and completeness of results for a wide set of data. The default break key uses the two character country code, the first five alphanumeric characters of the postal code and the first letter of the street field to generate the break key value. To improve the results during a search, this product requires data for the street and postal code fields so that the appropriate records can be used in the matching process. For example, to search for a customer who you know lives on Main Street in La Crosse, Wisconsin, you would enter the following information in the search window: Street: Main St Postal Code: 54601 The break key value for this input data is US54601M. The search process selects all of the records from the SAP system that have the break key value US54601M. The search process then compares the input data to each record selected using the matching rules set up on the RFC Server. To illustrate the importance of providing data in the two fields used by Data Quality for SAP to determine a break key, imagine that you entered the following information in the search window: Street: <blank> Postal Code: 54601 The break key value would be US54601 and only records with a break key value of US54601M would be selected for searching. This result would not include the record you were searching for because that record has a break key value of US54601M. Chapter 6: Duplicate check and error tolerant search 75

During duplicate search, this product performs postal validation on the input data before performing the search. If this example had been for duplicate search specifically, the postal code left blank, but street, city, and region data were complete, then Data Quality for SAP could validate the data and determine the postal code. The corrected data would then be assigned the appropriate break key of US54601M, even though you did not directly enter the postal code. Changing the match code You can change the match code to one of the others provided. To change the match code: 1. Open the Data Services Designer and select Tools > Substitution Parameter Configurations. The Substitutions Parameter Editor opens. 2. In the Substitution Parameter Editor, update substitution value $$DQ_SAP_Match_Function. Valid entries are the following. MatchCode1 MatchCode2 MatchCode3 MatchCode4 MatchCode5 MatchCodeCustom For a description of the match codes, see Match Codes on page 119. If you change the match code, you must run the initialization program to update the match code entries in this product s match code table. For information on running the initialization program, see Run the initial setup on page 42. Configuring the break key settings The regular break key settings can be configured in the Data Services job Job_Realtime_DQ_SAP_Create_Break_Keys. This job does not use first names in the creation of break keys, and is both the default and recommended method of creating break keys. It is set to run when you install this product. If you want to use this job with extra data fields, you can configure it to do so. This product provides an additional job that uses first names in the creation of break keys, Job_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName. Because first names are typically common, this job is suited only to special circumstances for duplicate check operations, probably using a smaller and more relevant candidate set than with the default job. Further, you can change the default break key calculation by using a custom function. For general information on configuring a Data Services job, see the Data Services documentation. Configure break key setting with extra fields You can use additional fields for matching by modifying the $$DQ_SAP_Match_Function substitution parameter to the value MatchCodeCustom. The custom match code has preconfigured logic to include 76 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

data such as telephone numbers, email addresses, and two other extra, customizable fields. To use the extra, customizable fields in Job_Realtime_DQ_SAP_Create_Break_Keys, you must create two function modules for your SAP system. The system calls the first function module when a match code is created for a new or updated record. This process allows you to put additional data into the table that is sent down to this product s GET_MATCH_CODES RFC Server method. Creating this module allows you to use the additional data in a match code. Also, since the data is saved in the match code table, the data can be used in formulating a match score. The system calls the second function module during address search and duplicate checking. This allows you to fill the additional data fields for the driver record during match. Both of these function modules must have one table parameter named im_driver with a structure of /FLDQ/AD_MTCCODE. The following code block shows how the function modules must be structured: FUNCTION Z_AD_FINISHED_EXAMPLE. *"--------------------------------------------------------------- *"*"Local interface: *" TABLES *" IM_DRIVER STRUCTURE /FLDQ/AD_MTCCODE *"--------------------------------------------------------------- data: wa_match_codes type /fldq/ad_mtccode. loop at im_driver into wa_match_codes. * * Here s where you put your own logic to get the additional data. * modify im_driver from wa_match_codes index sy-tabix. endloop. ENDFUNCTION. Finally, you must configure the names of these function modules in the IMG activity Maintain operating parameters, using the parameters AD_ADDRESS_FINISHED_FUNC_NM for the function module called when a match code is created, and AD_ADDRESS_SEARCH_FUNC_NM for the function module called during address search and duplicate checking. For information on the IMG activity Maintain operating parameters, see Maintain operating parameters on page 56. Create break keys using first names If you want to use first names in creating break keys, you must change the Data Services job from Job_Realtime_DQ_SAP_Create_Break_Keys to Job_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName. To change these jobs: 1. From the Data Services Management Console, click on Administrator. 2. Navigate to Real-time > <your machine name>. Chapter 6: Duplicate check and error tolerant search 77

3. Click on Real-Time Services and select the Real-Time Services configuration tab. 4. Check the box for Job_Realtime_DQ_SAP_Create_Break_Keys. 5. Click the Disable button. 6. Check the box for Job_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName. 7. Click the Enable button. 8. Select the Real-Time Services Status tab. 9. Check the box for Job_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName. 10. Click the Start button. Next, you must make changes to the RFC Server configuration. For detailed information about this configuration file, see Configuring through flrfcsrv.xml on page 62. 1. In the RFC Configuration file install_directory\config\flrfcsrv.xml, comment the following tag: <break_key>service_realtime_dq_sap_create_break_keys </break_key> to <!-- <break_key>service_realtime_dq_sap_create_break_keys </break_key> --> 2. Uncomment the following tag: <!--<break_key> Service_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName </break_key>--> to <break_key> Service_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName </break_key>. 3. Save your changes and restart the RFC Server. The method of restarting the RFC Server varies depending on your operating system and, within Windows, whether you run the RFC Server as a Windows Service. For information on how to restart the RFC Server for your configuration, see Configuring through flrfcsrv.xml on page 62. Change the default break key calculations with a custom function You can change the default break key calculations by modifying custom function CF_DQ_SAP_Calculate_Match_Code_Custom in the Data Services Designer. Within DF_Realtime_DQ_SAP_Create_Break_Keys, go to the Build_Address_Match_Codes transform, which is where the Match_Code1 is created. The function CF_DQ_SAP_Calculate_Match_Code_Custom is where the custom match code is calculated, and this function uses the extra five fields available to this data flow in its expression. The sample code below shows a scenario of changing the default break key calculations. This example uses six digits from telephone number, four digits 78 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

from the extension, and six characters of the domain name from the email address. It then sends the data through the double_metaphone function to get the output and combines the data to make the match code. In similar fashion, the extra1 and extra2 fields could instead be used to make the break key. # Sample logic to add telephone number, telephone extension, email # address, extra1, extra2 (extra1 & extra2 may be different fields # coming from SAP based on your business requirement). if (length(ltrim_blanks_ext(rtrim_blanks_ext($input_tel_number))) > 0) # take first 3 (long dist code) + next 3 (which identified region?) $tmpmatchcode = $tmpmatchcode substr($input_tel_number,1,6); if (length(ltrim_blanks_ext(rtrim_blanks_ext($input_tel_extens))) > 0) # take first 4 digits of extension $tmpmatchcode = $tmpmatchcode substr($input_tel_extens,1,4); if (length(ltrim_blanks_ext(rtrim_blanks_ext($input_smtp_addr))) > 0) # Take characters after @ and send it to through phonetic function # and get a 6 character code out of it. # This way misspelled domains length / short ones.com/.net will # have something in common $tmp_phonetic = double_metaphone(substr($input_smtp_addr,index($input_smtp_addr, '@',1)+1, length($input_smtp_addr)- index($input_smtp_addr,'@',1)),0,0); $tmpmatchcode = $tmpmatchcode $tmp_phonetic; # Add extra1 and extra2 logic if required. #End of sample to add additional fields for Creating break keys. if( ltrim_blanks_ext(rtrim_blanks_ext($tmpmatchcode)) = '') $tmpmatchcode = null; return $tmpmatchcode; Match on name data You can also perform a search with data from the name field. This product creates special break key values based on name information. This ability allows you to perform a name-only search. However, the name break keys are not configurable. If you enter data into both the name field and address fields, then both the name and address break key values are used to select records. Chapter 6: Duplicate check and error tolerant search 79

Using duplicate check You can use duplicate check in interactive mode and, for Business Partner data, in batch mode. Interactive mode When you create a new entry in the SAP database for a customer, vendor, or business partner, Data Quality for SAP performs postal validation on the entry to complete and standardize the data, then checks existing data to find records that might be duplicates of the new, validated entry. The hit list In response to your attempt to save a new record, Data Quality for SAP processes the data and, if it finds a record for which the new record may be a duplicate, presents a hit list of candidates from which you can select an entry. If one of the results on the hit list is a match of the record you are entering, select the record by clicking it. At this window you have three button options: Button Continue Select Duplicate Cancel Action The previous window returns to focus showing the current address that the user accepted from the previous address reviewer window. The previous window returns to focus with the data from the selected record populating the fields. The previous window returns to focus and the process is cancelled. SAP Basis 6.40 shows additional GUI elements in this window that other SAP versions do not show. These additional elements are created by SAP and not Data Quality for SAP, and therefore are not documented in this guide. The duplicate check hit list for the WebClient is shown here: 80 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

At this window you have two button options: Button Continue Cancel Action The previous window returns to focus and the record the user entered is saved. The previous window returns to focus and the process is cancelled. Fields displayed You can customize the data fields displayed in the SAP-GUI version of the duplicate check hit list, as well as the order of those fields. See Maintain fields for duplicate hit list display on page 54 for information about the default settings and the procedure for making changes to the fields displayed within the SAP GUI. Batch mode You can use duplicate search in batch mode (called batch match) to find duplicate records in your Business Partners database. To use duplicate search in batch mode: 1. Invoke the transaction SA38 in the command box. The ABAP: Execute Program window appears. 2. In the Program field, enter /FLDQ/RSADRINI and click the Execute button (F8). The Initial Match Code (Index) Setup Program window appears. 3. Check the box for the Program Option Perform Batch Match. The window displays fields for configuring batch match. Chapter 6: Duplicate check and error tolerant search 81

4. Set the threshold (a lower number produces more matches) and the packet size (defined as the number of records in a packet), and choose whether to use the SAP functionality to create a cleansing case to combine records. For more information about the functionality to create a cleansing case on your SAP platform, see the documentation for your SAP platform. 5. Click the Execute button (F8). The results appear after the system finishes processing. Cleaning the staging tables for batch mode To avoid erroneous results when using duplicate search in batch mode, you should periodically clean the staging tables. If you have previously run batch job that failed, there may be records remaining in the staging tables from that previous job. You can clean the staging tables in one of two ways: Execute an SQL query on the datastore. (For example, delete from DQ_SAP_BATCH_MATCH_RUN_INPUT.) Execute the sample input file SampleInputXMLFor_Realtime_DQ_SAP_Name_And_Address_Match_Cl eanup_request.xml in the batch match dataflow in the Data Services Designer For information about the sample input files, see Using the sample input files to test Jobs on page 88. 82 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Using error tolerant search When you perform a search for a customer, vendor, or business partner using SAP error tolerant search functionality (often called fuzzy search or rough search), Data Quality for SAP takes even partial data or erroneous data that you entered and provides a hit list of logical record matches between your search terms and existing data. A sample search window is shown here: The searches can take place on address fields or name fields. You can customize Data Quality for SAP to determine which fields are presented in the hit list to help you decide which record fulfills your search. The hit list In response to your search request, Data Quality for SAP processes the data, creates a list of possible matches, and presents a hit list of candidates from which you can select an entry. A sample error tolerant search hit list dialog is shown here. Chapter 6: Duplicate check and error tolerant search 83

If one of the results on the hit list is the desired record, select the record and click the Select button. At this window you have three button options. Button Select New Search Cancel Action A window appears that gives the customer number for confirmation. If this record is the desired record, you can accept it by clicking Enter. The previous window returns with the entered data populating the fields. The duplicate matches are discarded. The search window returns, populated by the data you entered. The standard SAP search window is displayed. Fields displayed You can customize the data fields displayed in the error tolerant search hit list, as well as the order of those fields. See Maintain fields for duplicate hit list display on page 54 for information on the default settings and the procedure for making changes to the fields displayed. 84 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Chapter 7: Tips and troubleshooting This chapter includes information on troubleshooting errors and known issues within SAP BusinessObjects Data Quality Management, version for SAP Solutions. It also includes tips for using the product. Chapter 7: Tips and troubleshooting 85

Installation troubleshooting If the installation was unable to import the.atl files If the Windows installation routine notifies you that was unable to import the.atl files and copy the.xml file, you must manually perform these operations. This installation routine by default copies the files to the directory [your_path]\ Business Objects\Data Quality Mgmt for SAP Solutions\integration\. To manually perform the file import and copy operations: 1. According to the directions in the Data Services documentation, import the.atl files through the Data Services Designer. You must import the.atl files in the following order: SAP_DS_STG_TBL.atl DQ_SAP_DS.atl DQ_SAP_DS_SYS_CFG.atl DQ_SAP_DS_SUB_PARAM.atl For instructions on importing.atl files, see the Data Services documentation. 2. Copy the file SupportedCountriesList.xml to the \bin directory of the Data Services configuration. Further, you must manually set the DS_SAP_DS datastore password after importing the.atl files. See the Data Services documentation for instructions on setting a datastore password. Checking the RFC Server(s) connection You can determine to which RFC Server(s) an SAP gateway is connected by using the SAP transaction SMGW. For information on the use and syntax of transaction SMGW, consult your SAP documentation. Connection to the RFC Server closed If the connection between your SAP system and the RFC Server closes or is not made during installation, the RFC Server log files contain the entry connection closed. The location and name of the RFC Server log files vary depending on whether you install the RFC Server as a Windows Service or not. The variable <sysid> the System ID. Type of log file Windows Service Transactional Windows Service Batch Non-service Transactional Non-service Batch Path and name \logs\businessobjects DQM for SAP <sysid> 1 log.txt \logs\businessobjects DQM for SAP Batch <sysid> log.txt \logs\<sysid>\flrfcsrv_log.txt \logs\<sysid>\flrfcsrv_batch_log.txt 86 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

A more descriptive explanation may exist in another log file or trace file on the RFC Server. Depending on the issue, the information may be in various files that have the extension.trc. If you experience failures due to closed connections to the RFC Server, you can search for those files with the wildcard search *.trc. Troubleshooting Unicode issues Data Quality for SAP has two settings that indicate whether your system processes Unicode characters, one in Data Quality for SAP s RFC Server configuration file and one in the RFC Destination. If you have problems related to Unicode characters, you should check and configure these two settings to make sure they are correct. Configure the RFC Server To configure the RFC Server to determine whether Data Quality for SAP works with either a Unicode or non-unicode system: In Data Quality for SAP s RFC Server configuration file (by default, install_directory\config\flrfcsrv.xml), set the sap_unicode key to yes if you have a Unicode system or no if you have a non-unicode system, as follows: <sap_unicode>yes</sap_unicode> or <sap_unicode>no</sap_unicode> Configure in the IMG To configure the IMG to determine whether Data Quality for SAP works with either a Unicode or non-unicode system: 1. Within the SAP client, enter the transaction SM59. The Display and Maintain RFC destinations window appears. 2. Select TCP/IP > FL_GDQC_SERVER. The RFC Destination FL_GDQC_SERVER window appears. 3. Select the Special Options tab. 4. In the Character Width in Target System field, select the Non-Unicode or Unicode button, as appropriate for your system. Unicode 5. Save the settings (Ctrl+S). Chapter 7: Tips and troubleshooting 87

Postal validation and duplicate check/error tolerant search troubleshooting Using the sample input files to test Jobs During the installation of the Data Services Component, the installation routine installs sample input files to your Data Services configuration at installpath\ Business Objects\Data Quality Mgmt for SAP Solutions\extrafiles\ SampleInputfiles. You can use these input data files as a template to run data through Data Quality for SAP. Before running sample files, set the sample directory path in the parameter $$DQ_SAP_Sample_WorkDir. To set the sample directory path: 1. In the Data Services Designer, go to Tools > Substitution Parameter Configurations. 2. In the Substitution Parameter Editor, select $$DQ_SAP_Sample_WorkDir. 3. Set the directory path to the location of the of the sample input files. 4. After you have set the appropriate directory, click OK. You can now run a sample job. For example, if you want to customize a job, you could send add records to a sample input file and send the data through the job to see if you receive the expected results. This process can help you make configurations to jobs. For instruction on how to run Jobs, see the Data Services documentation. Inability to save addresses for which the postal code cannot be completed If you were not running Data Quality for SAP on your SAP system and you entered an address without using the postal code, the SAP system would return a standard SAP error indicating that you need to enter a valid postal code. Because you are running Data Quality for SAP on your SAP system, Data Quality for SAP attempts to fill in the correct postal code based on the other address information you provided. If, however, Data Quality for SAP can not determine a postal code, Data Quality for SAP does not offer you an option to save the address without correcting. This restriction is necessary because if you attempted to save the address without the ZIP Code, the SAP system would return its standard error indicating that you need to enter a valid postal code. Therefore, instead of creating a scenario in which Data Quality for SAP allows you to save the address without the postal code only to have the SAP system disallow it, Data Quality for SAP instead gives an error and does not allow you to save the address. Records created without break keys due to downtime of RFC Server During any time that the RFC Server is not functioning, Data Quality for SAP can not give a break key to newly created records or changed records. When the RFC Server again functions and the first record is created or changed, Data Quality for SAP checks a list of pending records to determine which records have not been assigned break keys, and assigns break keys to those records. The size of that list is configurable through the IMG activity Maintain operating parameters. (For details, see Maintain operating parameters on page 56.) 88 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

If the number of pending records exceeds the size configured in that parameter, Data Quality for SAP cannot assign break keys to the records. Instead, you must run the custom report /FLDQ/AD_REPT_UPDATE_PEND_RECS. To run the report /FLDQ/AD_REPT_UPDATE_PEND_RECS: 1. Start the report /FLDQ/AD_REPT_UPDATE_PEND_RECS by running the transaction code SA38. The ABAP Execute Program window appears. 2. In the Program field, enter /FLDQ/AD_REPT_UPDATE_PEND_RECS and click the Execute button (F8). A confirmation window appears and Data Quality for SAP has assigned break keys to all records in the database. Records not stored in pending update table when search disabled As you add or change records, the records are normally stored in the table /FLDQ/AD_PUPDATE until they are committed to the SAP database. However, records are not stored in that table if the Suppress Search box is checked because with search functionality suppressed, Data Quality for SAP would never process the records in the table, and the table would grow endlessly. For information about the Suppress Search checkbox, see Add a transaction code to the exception table on page 49. Understanding regions Regions are data fields that could be states for U.S. addresses, provinces for Canadian addresses, and so on. You can edit the file regions.xml to control how Data Quality for SAP maps regions between the data format expected by SAP and the data format expected by Data Services. In particular, this section describes how the order of region maps in the file is significant. Consider this example. Each line of regions.xml specifies conversion values for both directions: SAP region code -> Data Services region name CA, PQ -> CA, QC CA, QC -> CA, PQ CA, QC -> CA, QC SAP region code <- Data Services region name CA, PQ <- CA, QC CA, QC <- CA, PQ CA, QC <- CA, QC When there are redundancies in the maps, as in this example, Data Quality for SAP uses the last defined map. Therefore, Data Quality for SAP converts the input region: CA, PQ -> CA, QC CA, QC -> CA, QC (note: QC->PQ was overwritten by QC->QC) And Data Quality for SAP converts the output region: CA, QC <- CA, PQ CA, QC <- CA, QC (note: PQ<-QC was overwritten by QC->QC) Chapter 7: Tips and troubleshooting 89

Therefore, if the order of these regions map is different, you get a different result that might be unexpected. Region code cannot be mapped to the region name If postal validation fails because the region code cannot be mapped to the full region name, you can change the manner in which region codes are returned by this product. The RFC Server configuration file regions.xml has both short and long region name mappings because region codes used by SAP systems and those used by Data Services are different. This product uses the settings in regions.xml to resolve that difference by mapping the region codes between the two components. If it does so undesirably, you can change the mapping. To change the region code mapping, you must modify the way that the Data Services Global Address Cleanse (GAC) transform returns region names, and then modify regions.xml to correspond to the changes in the GAC transform. To modify how the GAC transform returns region names, you must change the setting for the Region Style for each dataflow in the GAC transform. The Region Style specifies whether to abbreviate the region name. It provides the following options: Option Long Preserve Short Description Uses the fully spelled region name (for example, California or Ontario). Retains the style used in the input record. Abbreviates the region name (for example, CA or ON) To change the Region Style for each dataflow in the GAC transform: 1. In the Data Services Designer, double click on the GAC transform you want to modify and select the Options tab. 2. Under the Standardization Options, pull down the list for Region Style and change the value as you require (for example, from Short to Long). 3. Repeat these steps for each dataflow in the GAC transform. Next, this change must be reflected in the regions.xml file of the RFC Server. For more information about making changes to an RFC Server configuration file, see Configuring the RFC Server on page 61 To modify regions.xml: 1. Open the file install_directory\config\regions.xml. In the file, each <country> tag contains several <region> tags. 2. For each region, change the code attribute to match the Region Style naming convention you selected in the Data Services GAC transform. 3. Save the file and restart the RFC Server For example, in the following entry, the region code of WI would translate to the region name of wi. This is the value that would be returned by the RFC Server to the SAP system. 90 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

<country code="us" language="en"> <region code="wi" name="wi"/> </country> If you want to use the long region names returned from Data Services, you would modify this tag as follows: <country code="us" language="en"> <region code="wisconsin" name="wi"/> </country> If you are changing from Short to Long Region Styles, there must be a corresponding Long region code for every region tag in the file regions.xml. The RFC Server processes the first matching value found. Consequently, you should either remove any Region Styles not in use, or ensure that the Regions Style you use is the first in each country section. If you want to use a combination of region style naming conventions (perhaps because some dataflows use Short and some use Long for a Region Style), you must have a combination of both long and short region names in the regions.xml file. Newfoundland region code for R/3 4.70 If you have R/3 4.70 system, the SAP two character mapping code for the Canadian province Newfoundland is NF. For all other versions of SAP supported by Data Quality for SAP, the mapping code is NL. In the file regions.xml, the mapping code NL is used for Newfoundland. To assure correct postal validation, users of R/3 4.70 should change the line in regions.xml for country CA: <region code="nf" name="nl"/> to <region code="nf" name="nf"/> RSMTCCODE program error message When you run the program RSMTCCODE for a range of records but no record exists in that range, the system displays an error message that states, Report execution completed successfully. No updates done to break keys table. Include records with empty break keys A break key is the search index for each record that Data Quality for SAP uses for finding similar, possibly matching, candidate records. A break key consists of search terms that are arranged in a specific order. The search terms can be customized so that Data Quality for SAP can determine that certain existing records have no realistic probability of being duplicates and should be ignored. For more information on break keys and how they help Data Quality for SAP perform searches, see Understanding duplicate check and error tolerant search on page 74. Some records may not have a break key associated with them; that is, some records have an empty break key. Some may have break keys for name data but not address data, or vice versa. Chapter 7: Tips and troubleshooting 91

On one hand, including records that have empty break keys during postal validation or duplicate search slows the processing of Data Quality for SAP, because Data Quality for SAP has more records to examine. On the other hand, including records that have empty break keys helps Data Quality for SAP return appropriate records. Threshold values for duplicates For SAP Basis versions 640 and above, you must set threshold values in the IMG activity Set Limit for Duplicate List in SAP Dialog Boxes. For information on configuring this IMG activity, see your SAP documentation. Show Duplicates button inactive in WebClients If the Show Duplicates button is inactive after installation, make certain that you have followed all the instructions for in the section Activate duplicate check index pools on page 135 Generating reports in Data Services The generation of reports on data quality operations is handled within Data Services. When generating reports from a real-time job, you must first terminate the job in order to generate report logs on that data. For information on how to generate reports, see the Data Services documentation. DPV processing locked Data Quality for SAP provides available support for Delivery Point Validation (DPV) processing as a for sale add-on. If you run DPV and receive an error message that a record has locked DPV processing, you must obtain a DPV Unlock Code from customer support to unlock DPV functionality. See the Data Services documentation for information on DPV and DPV locking, as well as instructions to unlock DPV processing. 92 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Diagnosing problems that cause data quality processing to cease If this product ceases data quality processing for no obvious reason, consider the items below as tips to diagnose the problem. Verify whether the appropriate Data Services Web Services jobs are all still started and running within the Data Services Management Console. See the Data Services documentation for information about the Web Services jobs. Check the logs within the Data Services Management Console for any errors. See the Data Services documentation for information on the logs and responses to issues found there. Do not ignore the logs for a Data Services Service simply because the indicator light for that Service is green. Sometimes the Service indicator light shows green when in fact processing has actually stopped. Drill down into the individual logs under each Service, as the green indicator light may indicate only that the real time services is active. The cause of the problem with data quality processing may be found in the logs. Try running the individual real-time jobs from within the Data Services Designer if real-time services do not work from within this product.this test may reveal problems within Data Services. Ensure the sample data sets jobs have been set up correctly. Verify that the SAP Gateway RFC Server communication is still active by using the transaction SMGW. See the documentation for your SAP platform for more information about this transaction. If you are licensed for geocoding and get an error related to geocoding, ensure that in Data Services the GEO job has been set up as real-time Web Service. See the Data Services documentation for information about configuring jobs as a Web Service. Examples of the error messages include the following: An internal error occurred during geocoding or in a related geocoding program. Internal error in SAP1, US. RFC: Connection error Destination: FL_GDQC_SERVER Chapter 7: Tips and troubleshooting 93

RFC Server Troubleshooting RFC Server state toggles between START and STOP If after initialization the RFC Server state toggles between START and STOP, you may not have a valid gateway service ID in the configuration file flrfcsrv.xml. Check the value for the key <sap_gwserv> to ensure that the entry is correct. For instruction on editing flrfcsrv.xml, see Configuring through flrfcsrv.xml on page 62. Output manifest information Upon startup, the RFC Server console outputs the manifest information, which is the vendor s name, name of the product, and the version of the product. Then, after the log file is initialized, it writes this information to the log file. The format of this string is: <vendor> s <product> v<version> Here, <vendor> is the value assigned as the specification vendor in the manifest file, <product> is the value assigned as the specification title in the manifest file, and <version> is the value of the specification version in the manifest file. This information can be displayed only if the manifest information is available to the program. If this information cannot be loaded, the RFC Server displays the following warning: Warning: Unable to access the manifest file to display version and vendor information. The program continues processing normally after displaying this message to the console. 94 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Appendix A: Data Services Jobs and Options This section describes the Data Services jobs and options that are specific to SAP BusinessObjects Data Quality Management, version for SAP Solutions. Consult the Data Services documentation for general procedures for working with Data Services jobs and options. Data Services jobs These jobs are located in the Data Services Designer after you install the Data Services Component. Job Job_Batch_DQ_SAP_Address_Cleanse Job_Realtime_Batch_DQ_SAP_Name_ And_Address_Match Job_Realtime_DQ_SAP_Address_Cleanse Job_Realtime_DQ_SAP_Address_Cleanse_ Suggestions Job_Realtime_DQ_SAP_Address_GEO Description This job is used for quarterly adjustment reports and produces the same results as the results from the interactive address validation process. For more information about quarterly adjustment reports, see Quarterly Adjustment Reports on page 38. This job handles batch mode processing. It performs the following functions: Clears the records of a batch processing run from the staging tables (both input and output tables). Loads the staging tables with records from the RFC Server request for duplicate check in batch mode (batch match) processing. Processes records from input staging table for a specific BATCH_ID. The job matches driver record with candidate records to find potential duplicated names and addresses. It then loads the results into the output staging table. It uses the substitution parameter DQ_SAP_BATCH_ID to identify the records of a specific batch processing run and is passed from the RFC Server request by default. Fetches the duplicate check results in batch mode from the output staging table of a specific batch ID and sends back the results to the RFC Server. This job is used when the IMG setting is configured so that the Suggestion List is disabled during the Address Validation. For information about suggestion lists, see Maintain exception table of transaction codes on page 49. This job is used when the IMG setting is configured so that the Suggestion List is enabled during the Address Validation. For information about suggestion lists, see Maintain exception table of transaction codes on page 49. This job is used if you have purchased the geocoding option for this product. It processes latitude and longitude for US addresses. For information about activating geocoding functionality, see Configure geocoding on page 43. 95

Job Job_Realtime_DQ_SAP_Create_Break_Keys Job_Realtime_DQ_SAP_Create_Break_Keys_ With_Firstname Job_Realtime_DQ_SAP_Name_And_Address_ Match Job_Realtime_DQ_SAP_Retrieve_Country_ Purchased Job_Realtime_DQ_SAP_US_DPV_Address_ Cleanse_Suggestions DQ_SAP_Break_Key_Profiler Description This job is the default job for determining break keys. It does not use first names. For information on break keys, see Understanding break keys and data fields on page 75. This job uses first names for the creation of break keys. For information on break keys, see Understanding break keys and data fields on page 75. This job matches a driver record with candidate records to find potential duplicate names and addresses. It uses the Job-level Global Variable $SAP_MATCH_THRESHOLD as the default threshold if an invalid threshold is passed from the RFC Server request. This job retrieves the list of countries for which you can perform postal validation. This job processes US records through the URAC (US Regulatory Address Cleanse) transform and non-us records through the GAC (Global Address Cleanse) transform. If the collection contains multiple records (pending update case), all records must be of US origin to receive URAC DPV processing. This job generates statistics on Customer and Business Partner data to discover the best options to be set for this product. For more information about this job, see Using the Break Key Profiler on page 111. Combine House Num and PMB option The combine_house_num_and_pmb option of each job allows you to determine how Data Quality for SAP handles house number and PMB (postal mail box) data for that job. The following table explains the eight options that you can set for all address cleanse jobs to the global variable $gaddrcombineoption for each job. Option Explanation 1 (default) This option separates the house num1, house num2, and street data in the house num1, house num2, and street fields, respectively. It also appends the PMB data in the street supple2 field. 2 This option separates the house num1, house num2, and street data in the house num1, house num2, and street fields, respectively. It also appends the PMB data in the street field. 3 This option combines the house num1 and house num2 with street data in the street field and append the PMB data in the street suppl2 field. 4 This option combines the house num1, house num2, and PMB data with the street data in the street field. 5 This option combines the house num2 data with street data in the street field and appends the PMB data in the street suppl2 field. 6 This option combines the house num2 and PMB data with the street data in the street field. 7 This option combines the house num1 data with the street data in the street field and appends the PMB data in the street suppl2 field. 8 This option combines the house num1 and PMB data with the street data in the street field. 96 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

To set the option for how Data Quality for SAP handles house number and PMB data: 1. For any address cleanse job, choose Properties > Global Variables. 2. Change the value of $gaddrcombineoption from 1 to any value described in the preceding table. 3. Click Apply to activate your changes and then save the job. 4. Repeat these steps for any other jobs. 97

98 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Appendix B: Error Codes This section lists the error codes and provides a description of each code. Technical error codes Data Quality for SAP displays technical error codes in the Error Log Report, which you can access by running the custom report /FLDQ/ AD_REPT_DISPLAY_ERRLOG. To run the custom report /FLDQ/AD_REPT_DISPLAY_ERRLOG: 1. Start the report /FLDQ/AD_REPT_DISPLAY_ERRLOG by running the transaction code SA38. The ABAP Execute Program window appears. 2. In the Program field, enter AD_REPT_DISPLAY_ERRLOG and click the Execute button (F8). The Display Error Log Report appears. The following table lists the technical error codes: Technical Error T501 T502 T503 T504 T505 T506 T507 T508 T509 T510 Description An abnormal operation occurred during data processing. See the log files for details. This is the generic duplicate check and error-tolerant search error The IE_CH_ADDR table has a row of an invalid length because the length did not match the length specified in the format file. An incompatible Driver record length was found during duplicate check and error-tolerant search. An incompatible Candidate record length was found during duplicate check and error-tolerant search. An incompatible Match code record length was found during duplicate check and error-tolerant search. The table from SAP for adding the ISO country codes is not specified. The ISO country code table record length is invalid. There is not a record in the IE_CH_ADDR table for getting an input address during ADR_VALIDATE or ADR_VALIDATE_QTR call. The IE_CH_ADDR table for getting an input address is not specified during ADR_VALIDATE or ADR_VALIDATE_QTR call. 99

Technical Error T511 T512 T513 T514 T515 T516 T517 T518 T520 T521 T522 T524 T526 T527 T528 T529 T550 T600 T601 T602 T604 T701 T702 Description The EX_PROMPTS table for updating a suggestion prompt is not specified during ADR_VALIDATE call with a suggestion list option enabled. The EX_PROMPTS table record length is invalid. The IM_SUGGLIST table that is for adding the suggestion list is not specified during ADR_VALIDATE call with a suggestion list option enabled. The IM_SUGGLIST code table record length is invalid. The EX_DRIVER table for getting a driver record for matching is not specified during GET_MATCH_CODE call. The EX_DRIVER table record length is invalid. There is no record in the EX_DRIVER table for getting the driver record for matching. The IM_MATCH_CODES table for updating the match codes is not specified during GET_MATCH_CODE call. The IM_FIELD_LIST table for adding the fields for matching is not specified during GET_INDEXED_FIELD_LIST call. The IM_FIELD_LIST table record length is invalid. The EX_CANDIDATES table for getting the candidate records for matching is not specified during GET_POTENTIAL_MATCH call. The IM_MATCHES table for adding the matched records is not specified during GET_POTENTIAL_MATCH call. The search mode parameter (EX_SEARCH_MODE) passed is invalid (must be I, U, or S). The address type parameter (EX_CURRENT_ADDR_TYPE) passed is invalid (must be 1 or 2). The Data Quality process timed out. Error returned from Data Quality during process. Invalid function object. Unable to process Gateway request. Error occurred during ADR_VALIDATE or ADR_VALIDATE_QTR call. Error occurred when creating input data for the Suggestion List process during ADR_VALIDATE call. Error occurred when retrieving output data for Suggestion List process during ADR_VALIDATE call. The batch ADR_VALIDATE_QTR dataflow failed to initialize. An invalid address type was passed to the GET_INDEXED_FIELD_LIST function. Invalid parameter values found while processing a GET_INDEXED_FIELD_LIST request. 100 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Technical Error T703 T704 T705 T749 T750 T751 T752 T753 T802 T803 T804 T805 T806 T807 T809 T852 T853 T854 T855 T856 T898 T899 T900 T902 Description Unable to access stored person fields for a GET_INDEXED_FIELD_LIST request. Unable to access stored organization fields for a GET_INDEXED_FIELD_LIST request. Unable to access the list of temporary fields in order to create the indexed field list. An error occurred processing the GET_INDEXED_FIELD_LIST request. Error occurred during GET_ISO_COUNTRIES call. The system could not read the file SupportedCountries.txt on the Data Quality Server. The key file utility could not be found during GET_ISO_COUNTRIES call. The file SupportedCountries.txt could not be found during GET_ISO_COUNTRIES call. The file SupportedCountries.txt could not be opened for reading during a GET_ISO_COUNTRIES call. Invalid parameter values found while processing a GET_POTENTIAL_MATCHES request. Unable to locate the configuration file potential match setting for the specified table and field. Invalid response from the Data Quality server. Unable to access candidate record information. Unable to communicate with the Data Quality server. Unable to access driver record information. The BATCH_MATCH dataflow failed to initialize. Invalid parameter values found while processing a GET_POTENTIAL_BATCH_MATCHES request. Unable to locate the configuration file potential batch match setting for the specified table and field. Invalid response from the DQXI server. Unable to access candidate record information. Unable to communicate with the DQXI server. An error occurred processing the GET_POTENTIAL_MATCHES request. An error occurred processing the GET_POTENTIAL_MATCHES request. An error occurred getting the display function modules for the GUI type. Invalid parameter values found during GET_MATCH_CODES call. 101

Technical Error T903 T904 T905 T906 T907 T908 T909 T910 T911 T912 T913 T914 T915 T916 T999 Description Undefined application structure. Unable to access the application structure object. Unable to access the application structure object field. GetString method conversion exception on JCO Table. GetString method name does not exist exception on JCO Table. Driver record does not exist exception on JCO Table. Match record exists exception on JCO Table. Invalid socket table record index or record array not allocated exception. Insufficient or excess records for the reply tables returned from Data Quality. Undefined Data Quality response table. Dataflow error message returned from Data Quality. Dataflow status message returned from Data Quality. Unable to access the application input parameter list. Unable to access the application output parameter list. An error occurred processing the GET_MATCH_CODES request. Postal validation error codes Data Quality for SAP displays postal validation error codes within error message windows as the errors occur. The following table lists the postal validation error codes: Postal Validation Errors FZ01 FZ02 FZ03 FZ04 FZ05 FZ06 FZ07 FZ08 FZ09 FZ10 FZ11 Description There are more suggestions than the max suggestion set in the configuration file. The House number provided is blank. Invalid suggestion number is specified for Street record. The house number provided must be an odd number. The house number provided must be an even number. The PO Box number provided is blank. Invalid suggestion number is specified for PO Box record. The PO Box number provided must be an odd number. The PO Box number provided must be an even number. Invalid primary range is entered. The address is not a valid delivery point. 102 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Postal Validation Errors FZ12 FZ13 FZ14 FZ15 FZ16 FZ17 FZ18 Description The country is not defined. The address is not a valid delivery point. This record locked DPV processing. Consult the Data Quality documentation for the steps required to unlock DPV processing. The records primary range is a valid delivery point, but the secondary range is not valid in the DPV directory. The address is a confirmed delivery point, but the parsed secondary range is not available on input. DPV processing is currently unavailable. The secondary unit range provided was invalid. Duplicate check error code Data Quality for SAP displays a duplicate check error code within error message windows as the errors occur. There is only one duplicate check error code. Duplicate Check Error D001 Description The driver record to be matched is empty or data with all spaces. 103

104 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Appendix C: External List Management This section describes External List Management (ELM) features of SAP BusinessObjects Data Quality Management, version for SAP Solutions. ELM is SAP CRM functionality that allows users to import data into the SAP database from an external list. To prevent the creation of duplicate data in the database, SAP offers functionality that allows the external list to be matched against the SAP database so that duplicates can be identified. Data Quality for SAP further enhances this SAP functionality by providing the postal validation and matching capabilities of this product. You can use the Data Quality portion of this product to run postal validation and duplicate check on the data in the list itself prior to importing the list into your SAP database. Then upon import of the list, the ELM process uses the technology of Data Quality for SAP to perform postal validation and duplicate check of the list data against the SAP database. This product s postal validation and duplicate check capabilities are also available through SAP s LSM Workbench for data migration from legacy systems. 105

Using Data Quality for SAP with ELM To achieve optimal data quality when using ELM with SAP BusinessObjects Data Quality Management, version for SAP Solutions, users should do the following: 1. If you have a stand-alone version of Data Quality, cleanse (through postal validation) and de-duplicate the external list using Data Quality. For information on using Data Quality for these tasks, consult the Data Quality documentation. 2. Using the SAP ELM functionality, load the external list into the SAP system. The ELM process uses the technology of Data Quality for SAP to match the cleansed and de-duplicated list data against the SAP database. Duplicates in the list are marked as duplicates and are not imported. For information on using ELM within your SAP CRM system, consult the SAP documentation. Cleansing the external list prior to loading via ELM If the external list is not cleansed via Data Quality prior to being loaded via ELM, any records that SAP considers to be invalid postal addresses are automatically excluded from the de-duplication process and are not loaded into the database. Therefore, some records in the external list would be ignored. Examples of addresses that SAP considers to be invalid postal addresses are incomplete addresses or addresses that have the city, country, or region in lower case. Pre-cleansing the list using a stand-alone version of Data Quality corrects and standardizes postal data, allowing the data to become valid if enough information is included in the record. This process allows the user to get the most value from the external list. In addition, The SAP system does not check the list against itself for duplicates unless the records are B2B data. Records that are B2C data are not checked for duplicates within the list. If the list is de-duplicated against itself using a stand-alone version of Data Quality prior to being loaded via ELM, the SAP system then considers all records in the list for de-duplication, instead of only the B2B records. ELM functionality for different versions of SAP CRM In versions prior to SAP CRM 5, records that contained a P.O. Box address but no street address are not correctly compared against the database for de-duplication because the P.O. Box was excluded from the field mapping in ELM, causing the creation of an incorrect break key within this product. This issue has been fixed by SAP in CRM 5 and higher. Records with only name data In SAP s ELM implementation, records in the external list that contain only name data (no address data) are not compared against the database for de-duplication because SAP does not call duplicate check and error tolerant search (DES) if the phone number or postal code is blank. 106 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Appendix D: Databases for staging tables This section lists database types, guidelines, and sample values that you could use during the installation of the Data Services Component to choose a database type and provide connection data. Oracle RDBMS inputs screen The following are the Oracle Connection Parameters input screen specifications: Text Oracle Tables Owner/Schema Oracle TNS Name/Service Oracle User Oracle Password Guidelines Cannot be blank, no default Cannot be blank, no default Cannot be blank, default to Oracle Tables Owner/ Schema Cannot be blank. The following are the Oracle Connection Parameters sample values: Text Oracle Tables Owner/Schema Oracle TNS Name/Service Oracle User Oracle Password Sample value DBUSER MYDB.BYDBHOST.MYCOMPANY.NET or MYDB DBUSER DBPASS DB2 RDBMS inputs screen The following are the DB2 Connection Parameters input screen specifications: Text DB2 Tables Owner/Schema DB2 TNS Name DB2 User ID DB2 Password Guidelines Cannot be blank, no default Cannot be blank, no default Cannot be blank, no default Cannot be blank. The following are the DB2 Connection Parameters sample values: 107

Text Sample value DB2 Tables Owner/Schema DBUSER DB2 TNS Name/Service MYDB DB2 User ID dbuser DB2 Password dbpass MS SQL RDBMS inputs screen The following are the MS SQL Connection Parameters input screen specifications: Text Database Tables Owner Database Server Name Database Name User Name Password Windows Authentication Guidelines Cannot be blank, no default Cannot be blank, no default Cannot be blank, no default Cannot be blank unless Windows Authorization checkbox is checked Set to blank if the Windows Authentication checkbox is checked. Default is not checked The following are the MS SQL Connection Parameters sample values: Text Database Tables Owner Database Server Name Database Name User Name Password Sample value DBO \\myserver MYDB dbuser (or check the Windows Authorization checkbox) dbpass (or check the Windows Authorization checkbox) 108 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

MySQL 5.0 RDBMS inputs screen The following are the MySQL 5.0 Connection Parameters input screen specifications: Text Data Source Name (DSN) Database Tables Owner User Name Password Guidelines Cannot be blank, no default Cannot be blank, no default Cannot be blank, no default Cannot be blank, no default. The following are the MySQL 5.0 Connection Parameters sample values: Text Data Source Name (DSN) Database Tables Owner User Name Password Sample value DataServices dataservices dbuser dbpass 109

110 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Appendix E: Using the Break Key Profiler The Break Key Profiler dataflow allows you to show the performance of various settings for duplicate check (matching) within this product. You can then use the results to customize the options to best match the data in your system, finding the optimal balance between getting full results or the rapid response time that is needed. 111

Break Key Profiler job The Data Services job DQ_SAP_Break_Key_Profiler is installed as part of the Data Services Component portion of this product. It can be connected to the SAP system to generate statistics on Customer and Business Partner data to discover the best options to be set for this product. You can run this job immediately after installing the product or later to diagnose possible solutions to performance issues. This job can also be installed to Data Services before installing the rest of this product to predict performance. See the document installed with the job for a detailed description on how to run this job and interpreter the results. The document is in <Data Services install>\ Data Quality Mgmt for SAP Solutions\ extras. The job checks the SAP index pools BUT000 and KNA1. If you install the job to Data Services before installing the rest of this product, you must assure that you have activated these index pools before running the job. For information on activating the index pools, see Activate duplicate check index pools on page 135. Running this job provides the following benefits: Shows the different results for the five best practice match codes that are used for searching on address information. For information on the match codes, see Match Codes on page 119. Allows matching the best function to your unique data to get the best results and response time. Tests custom match codes that use extra fields against the best practice match codes supplied with this product. Finds noise words that can be removed from the matching process to get better matches. Compares certified name selection against last name only selection to decide what type of name selection process will be used. Compares address only selection to name and address selection to decide if address only selection should be activated. 112 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Concepts for break key profiler This section provides some information to help you understand the terms and techniques of the break key profiler. Noise words Noise words are words that are part of the organization name1 or name2 field that do not have any relevance. For example, words such as of, the, and Inc. are common words that, if used when processing matches, result in much larger candidate groups. Candidates selected on these noise words are of little use in matching. This product already has many common English noise words configured. You can add new words that you consider to be noise words in your data. By removing the noise words from the matching process, you can improve performance. You can remove noise words from your data prior to creating the break keys. First and Last Name Selection This product offers two types of dataflows to create break keys: Last name only First and last name. Last name candidates usually provide better matches, as matching with first name often leads to false positive results. However, for backwards compatibility, this product offers both types of matches. This dataflow shows the results for a random selection of records in the file DQ_SAP_LastNameCompare. The results show the difference in size that the last name only versus first and last name generate. Name Candidates are only one part of the selection. When optimizing, you should consider the address selection process to get full benefit. When looking at the data, keep in mind that this product can process roughly 1000 records per second. For example, for a candidate group of 2000 records the processing time will be roughly two seconds, meaning that the user must wait that long to see results. This product has a default five-second processing limit for each transaction. For groups over 5000 to 6000 records, there can be records that will not get processed and a five second response time. Address only selection You can select match candidates using address information only. With this option enabled, this product ignores name information when selecting match candidates. However, if address information is missing, normal selection with name information occurs. The matching process itself still uses name and address information. Only the selection of the records prior to matching is based on address information. The default matching setup for organizations and individuals are 70 percent based on addresses making this a valid way of selecting candidates. The output in file DQ_SAP_NameAddressCompare looks at a random selection of records from the data and compares the candidate groups based on selecting on address information, on only name information and on both address and name information. 113

This show the performance you would get based on the selection process that is used. When looking at the data, keep in mind that this product can process roughly 1000 records per second. For example, for a candidate group of 2000 records the processing time will be roughly two seconds, meaning that the user must wait that long to see results. This product has a default five-second processing limit for each transaction. For groups over 5000 to 6000 records, there can be records that will not get processed and a five second response time. 114 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Installation You must install and run this dataflow on Data Services 12.2.1.0 or higher. Installing the dataflow with this product The configuration dataflow, datastores, and options are installed when you install the Data Services Component portion of this product. After installation, the Data Services datastore DQ_SAP_BP_CONFIG is set to point to the SAP system that contains the Customers and Business Partners records from which to pull the data. Settings such as turning on or off address engines and configuring the DQ_SAP_DS datastore are configured during the installation. Installing the dataflow without this product You can also install this dataflow to your Data Services configuration without installing the rest of this product. To install the dataflow separately: 1. In the installation materials for the Data Services Component portion of this product, locate the file DQ_SAP_Break_Key_Profiler_Tool.zip. 2. Unzip this file in the location of your Data Services installation. 3. Open the Data Services Designer and import the file located at <Data Services install>\ Data Quality Mgmt for SAP Solutions\ Break_Key_Profiler.atl. 4. Open the data store tab and configure the DQ_SAP_DS and DQ_SAP_BP_CONFIG datastores. Use the Q_SAP_DS datastore to connect to a MSSQL, Oracle, MySQL, or DB2 database to store temporary files used by this Data Services job. Use DQ_SAP_Config to connect to the SAP system to pull the data that is to be processed. You must provide the application server, username, password, client number, and system number to connect. 5. Open Tools > Substitution Parameter Configurations, and enable the address engines that you have purchased for this product. Disable any that you have not purchased. The following are the substitution values to be modified. DQ_SAP_EngineUsa DQ_SAP_EngineAustralia DQ_SAP_EngineCanada DQ_SAP_EngineEmea DQ_SAP_EngineGlobalAddress DQ_SAP_EngineJapan DQ_SAP_EngineMultiCountry For detailed directions on disabling address engines, see Use global variables to disable engines on page 25. 115

Run the job There are two ways to run the job. Choose the method you prefer from these two options: Start the dataflow through the Data Services Designer. Navigate to Jobs > Batch Jobs, and select DQ_SAP_Break_Key_Profiler. Click the Execute button. In the Data Services Management Console select Administrator > Batch > Batch Job Configuration tab, and then select Execute for DQ_SAP_Break_Key_Profiler. You can leave all the settings as default in the Execution Options screen. Click the Execute button. Performance Having the dataflow perform address and name correction, along with generating statistics, is a CPU-intensive task. To alleviate the burden on a single CPU, this dataflow is configured under the assumption that your machine has two CPUs. If the machine on which you run Data Services is more capable than the assumed, two-cpu machine, you can change the Degree of Parallelism (DOP) setting to get better performance. To change the DOP setting: 1. Open the batch job DQ_SAP_Break_Key_Profiler and right click on DF_DQ_SAP_Create_Break_Keys. 2. Select Properties, and change the Degree of Parallelism (DOP) to better fit the number of CPU your machine runs. A machine with two CPUs works best with a setting 1-2 DOP. A machine with four CPUs works best with a setting of 3-4 DOP. A machine with six CPUs works best with a setting of 4-6 DOP. However, if the database server is also on the same machine, consider dropping the DOP by one or two settings to leave a resources for exclusive database processing. 116 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Interpret the Results This batch job is split into several dataflows and scripts. After the job runs, you can find the results in the final dataflow, DF_Generate_Statistics. Running the job also sends ten.csv output files to [your_path]\business Objects\ Data Quality Mgmt for SAP Solutions\extras\SampleInputFiles. You can view the first 1000 records from within the dataflow, but you must open the.csv output files to see the all the records. You may want to do so for any of the match codes (called DQ_SAP_Match_Code1 through DQ_SAP_Match_Code5) if you want to see all the records. However, the first few hundred records are the most important. You can graph the data from the match codes by opening the.csv file in a data reporting tool or a spreadsheet program and using its graphing capabilities. The output files The following sections provide descriptions for each of the output files. DQ_SAP_NOISE_WORDS The dataflow generates statistics on the words in the organization name fields The output contains a row for each word, along with the number of times it appears in the database and the percentage. The results are sorted so that the most common words are first. When you look through the results, look for words that occur frequently but do not add value. For example, the abbreviation Inc. appears in many organizations names but does not provide assistance with the matching process. You could add this word to the noise word list so that it is removed before generating the break keys for candidate selection. Adding words to the noise word list shrinks the candidate groups and limits the number of false positives that this product processes through the dataflows, thereby improving performance. The dataflow provides some noise words. To add noise words, in the Data Services Designer open the CF_DQ_SAP_REMOVE_ORG_NOISE_WORDS custom function and follow the instructions at the top of the function. DQ_SAP_LastNameComp are This output file shows the different candidate groups that are generated based on using the default break key dataflow or the secondary dataflow that incorporates first names in the selection. The first record in the output is the average of all the other records. The output contrasts the last name selection with the first and last name selection, and shows the difference in number between the groups and how many times larger one of the groups is compared to the other. For any but a very small database, you should use the last name only. Last name only generates much smaller candidate set groups because first names are typically common and add many false positives to the matching results. Using first names provides few new matches that would not be found by selecting only on last name. 117

DQ_SAP_NameAddressCo mplare This output file shows the differences among three methods for selecting candidates: address only, address and last name, and last name only. These three results are displayed to help contrast an option in this product that allows for address-only candidate selection when address data is available to improve performance. The first record in the output is the average of all the other records. Address fields comprise 70 percent of the matching process, so by basing the candidate selection on addresses (where available) results in high quality matches and improved performance. DQ_SAP_Match_Code1-5 In this output, there are six match group tables, numbered 1-5, and also a custom table. This product can generate five different best-practice match codes based on the address, along with a custom match code that can be developed for special requirements. Each of these tables allows you to see the match codes that are generated for the associated match code, along with a count and percent of the records in the database that have that match code. Use these fields to find the best match code function to be used on your data. For a description of these match codes, see Match Codes on page 119. DQ_SAP_MatchCodeStats This output shows an overview of all the match codes: the average group size, maximum group size, and median group size for the five best practice match codes and the custom match code. This product uses this output, along with the DQ_SAP_Match_Code1-5 outputs, for picking the best match code to implement. DQ_SAP_MatchGroupCom posite This output is a combination of DQ_SAP_Match_Code1-5 and the custom tables. The purpose of this combination is to allow you to easily compare the output. You can compare the largest match groups by examining the top 10 to 25 percent of the data. Settings that can be optimized based on the output The most important aspect in improving response time for data quality processing is to select the best match code for your data and the size of your database. Ideally, you find the match code that gives both the smallest average break group, but also has the best distribution. To help find that ideal, use the MATCH_GROUP tables and MATCH_GROUP_STATS to compare the results and pick the best one. The match codes are number 1-5 and described in the next section. You can look at the actual match codes and their size and percentage of all records, in the MATCH_GROUP1-5 tables. For larger tables, however, you should use the MATCH_GROUP_STATS tables. These tables show the average, median, number of match groups, and max fields. You can also find in the tables the median group size to help you better understand how the data is distributed, because the median group size data is not unduly influenced by the top and bottom few percent, which can skew the average value. By comparing the average and median, you can get a better understanding of how the data is arranged. For best performance, get the data to be spread as evenly as possible over the highest number of match codes. You should limit the number of match codes that are significantly larger. 118 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

If processing seems slow or you get incomplete results returned, you should use a different match code. If there is a problem with your data, such as missing or incomplete data in the fields that the match code is using, then cleanse and standardize the data with Data Services. Address information must be complete, as the break keys are generated off the postal code and street name data fields. Using tighter break keys results in smaller break groups, which increases the possibility of excluding a possible match. Picking the best match code requires you to balance response time versus the highest probability of finding all matches. As the data set increases in size, the tighter match groups must be used to keep performance within required boundaries. The five best practice fields are designed to handle the different sized data sets by giving a range of loose to tight match codes. Match Codes This product provides five best practice match codes. All match codes contain the country data field. Tighter match codes work well for address data. All address data are preprocessed through Global Address Cleanse transform that standardizes the information and places the data into the correct fields before generating the match codes. This limits misspellings, transposed letters, and invalid address components, which would require fuzzy matching to find all possible matches. There is also a custom match code that can be modified to select on extra fields such as email, phone numbers or other fields if required. Match Code 1 Match Code 1 has loose postcode and loose street name selection. It is created by using two-character ISO country code, plus the first three characters of the postcode, plus the first character of street name. For the United States and most other countries, the ISO country code and three characters of the postcode narrow the location to the sectional center facility. The first character of the street further limits the match code to streets with the same starting letter. This was the match code previously used by this product. It generates the most possible matches that will have to be processed through the matching process, and as a result is the slowest at processing, on average. Match Code 2 Match Codes 2 has loose postcode and tight street name selection. It is created by using the two-character ISO country code, plus the first three characters of postcode, plus the first three characters of street name. This match code is a modification of Match Code 1, with a tighter selection of the street field by using three characters instead of only one. This match code gives fast performance but still selects addresses in a larger postal area. Match Code 3 Match Code 3 has tight postcode and loose street name selection. It is created by using the two-character ISO country code, plus the first five characters of the postcode, plus the first character of street name. Using the first five characters of the postcode narrows the location to the area of the city or town for the United States, with similar accuracy for other countries. It uses the first character for the street, which results in small candidate groups and fast performance, but still allows for variance in the street name. This match code gives similar performance to Match Code 2. 119

Match Code 4 Match Code 4 has tight postcode and tight street name selection. It is created by using the two-character ISO country code, plus the first five characters of the postcode, plus the first 3 characters of street name. It has narrow postcode selection but increases the street tightness by using the first three characters of that field. In most data sets, this generates the smallest number of records to be sent to the matching process. This should result in the fastest response time for large databases, especially if the lower numbered match codes return too many false positives that have to be processed. Match Code 5 Match Code 5 has tight region, tight city, and tight street matching. It is created by using the two-character ISO country code, plus the two-character region code, plus the first then characters of city, plus the first three characters of the street name. Postcodes are only loosely tied to cities and do not truly represent geographical regions. They are artificial constructs. This match code uses region and city instead of postcode to offer a different logical way to group the addresses. This match code uses the three characters of the street to partition the larger cities. The city field is standardized so that matching on larger sets of data can help narrow the records selected to be matched against, but does not remove any records that have a chance to match. This match code should result in slightly slow response time compared to Match Code 4, but much faster than Match Code 2 or Match Code 3. Match Code Custom Match Code Custom is a placeholder. It is to be created for special cases in which the default match code based on the best practice address data does not result in the candidate groups that is needed. 120 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Creating Custom Match Codes You may find circumstances in which creating a custom match code provides a better solution that using the provided match codes. Special search cases such as searches on phone number, email address, or on an extra field that is not address information may make a custom match code a good solutions. The recommended way to create a custom match code is through updating our custom function CF_DQ_SAP_Calculate_Match_Code_Custom. This function already has most of the common fields that can be used for creating a match code, along with a few common ways of combining them into match codes. You can modify the function and test it within the DQ_SAP_Break_Key_Profiler job. If you have to modify the input to the CF_DQ_SAP_Calculate_Match_Code_Custom custom function, you must modify the transform Build_Address_Match_Codes in DF_DQ_SAP_Create_Break_Keys when testing and in the same transform in DF_Realtime_DQ_SAP_Create_Break_Key for production. After you have finished testing the custom function you will have to set the custom function to be used in the DF_Realtime_DQ_SAP_Create_Break_Key dataflow. To change what code is used for the break keys: 1. Open Data Services Designer and navigate to Tools > Substitution Parameter Configurations. 2. In the Substitution Parameter Editor, set the substitution value $$DQ_SAP_Match_Function to MatchCodeCustom. You must restart the Real-time job for the new break key to be used. For more information on changing break keys, see Configuring the break key settings on page 76. 121

122 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Appendix F: BAdI-only for fresh installation This section reprints from the previous version of this product s Users Guide in the installation instructions for the previous version s BAdIs. If you are performing a fresh (non-upgrade) installation, use these instructions to install and configure those BAdIs. 123

Installing the BAdIs from the previous version Because of the variety of SAP versions, the illustrations that we use throughout these procedures may differ from what you encounter while installing BAdIs on your specific version of SAP Solution. We assume that you have knowledge of SAP administration to help you successfully navigate through the installation. Even though the screens may differ from version to version, follow all steps in these processes. To install the BAdIs on your system, you must complete these tasks: Step 1: Import the Data Quality Management package on client 000 on page 124 Step 2: Insert the Data Quality Management IMG structure on client 000 on page 127 Step 3: Activate the Business Configuration Sets on each target client on page 129 The BAdIs are installed and upgraded using the Add-on Installation Tool, invoked by the transaction SAINT. Step 1: Import the Data Quality Management package on client 000 Choose an applicable.sar package for your Basis version from the tables below, import the Data Quality Management package on the reference client (client 000), and then activate (or reactivate) BC Set /FLDQ/47U6X to import new customizing data. Basis 6.20 SAR file \6.20\DATA\SAPK-40ACOINFLDQ.SAR \6.20\DATA\UPGRADE\SAPK-40ACHINFLDQ.SAR New install or upgrade New install Upgrade You must (re)activate BC Set /FLDQ/47U6X to import new customizing data. Basis 6.40 SAR file \6.40\DATA\SAPK-40ACOINFLDQ.SAR New install or upgrade New install \6.40\DATA\UPGRADE\SAPK-40ACHINFLDQ.SAR Upgrade (from 2.00c Rev 3 or above) You must (re)activate BC Set /FLDQ/47U6X to import new customizing data. 124 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Basis 7.00 SAR file \7.00\DATA\SAPK-40ACOINFLDQ.SAR \7.00\DATA\UPGRADE\SAPK-40ACHINFLDQ.SAR \7.00\DATA\CRM50\UPGRADE\SAPK- 40BCHINFLDQ.SAR \7.00\DATA\CRM2007\UPGRADE\SAPK- 40BCHINFLDQ.SAR New install or upgrade New install for all users Upgrade for ECC 6 users who installed version 39 of this file. New install and upgrade for CRM 5.0 users who installed version 39 of this file. New install and upgrade for CRM 2007 users who installed version 39 of this file. Basis 7.00 users must have the SPAM 21 update/patch or greater to be able to load a.sar package. (For more information, see SAP Note 822379.) Also, you must (re)activate BC Set /FLDQ/47U6X (and BSP BC Set /FLDQ/ BSP_PV, if applicable) to import new customizing data. Basis 7.01 SAR file \7.01\DATA\CRM7\SAPK-40ACOINFLDQ.SAR \7.01\DATA\ECC6 Enh Pack 4\SAPK- 40ACOINFLDQ.SAR \7.01\DATA\CRM7\UPGRADE\SAPK- 40ACHINFLDQ.SAR New install or upgrade New installation package for IC Web Client PV and DES Business Add-ins for CRM 7. New installation package for PV and DES Business Addins for ERP6 EP4. Upgrade for CRM 7 users who installed version 39 of this file. You must (re)activate BC Set /FLDQ/47U6X (and BSP BC Set /FLDQ/ BSP_PV, if applicable) to import new customizing data. Basis 7.10 SAR file \7.10\DATA\SAPK-40ACOINFLDQ.SAR New install or upgrade New install for all users You must (re)activate BC Set /FLDQ/47U6X to import new customizing data. Importing the Data Quality Management package To import the Data Quality for SAP package: 1. Enter the transaction SAINT to open the Add-On Installation Tool window. 125

2. Click the Installation packages menu and choose Load packages > From Frontend. 3. In the Select CAR/SAR archive window, browse to the \DATA directory of the Data Quality for SAP SAP PV and DES BAdIs installation media, and select the applicable.sar file. If the path is long and the system generates an error, copy the file to a local directory location and load it from there. 4. Click Open and then click Yes to load the.sar file. The contents of the compressed.sar file appears. 5. Click Decompress to view a list of Data Quality for SAP BAdIs in the Installable add-on and PCS Packages for your system table. 6. Click Continue. A confirmation window is displayed indicating that the Addon FLDQ will be installed. 7. Click Enter to confirm the installation. (This takes approximately five minutes.) 8. After the install completes, click Finish. Also, after the install completes, you can choose to view logs. 9. When you have installed all of the BAdIs, click Cancel to close the Add-on Installation tool. 126 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Step 2: Insert the Data Quality Management IMG structure on client 000 After you import the BAdIs, you link the Data Quality for SAP IMG (Implementation Management Guide) structure to your SAP Reference IMG structure. 1. Log on to client 000 of your system. 2. Type S_IMG_EXTENSION into the Command field and click Enter. 3. In the Edit IMG Structure window select the Possible Entries icon located next to the IMG Structure field. 4. In the Find Structure window, type Address Management for the Title and click Execute. A confirmation appears that the Address management structure exists. 5. Double-click the Address Management node to return to S_IMG_EXTENSION. 6. Click the Possible Entries icon in the Enhancement ID field and double-click /FLDQ/AD_IMG to open the Edit IMG Structure window. 7. Click Enhance Structure. One or possibly two Information dialogs appear. 127

8. Click Enter in each Information dialog to clear the dialog boxes. 9. Select the last of the Address Management sub nodes and choose Edit > Nodes > Insert IMG Structure > On Same Level. 10. Click Find in the Reference to a Structure window, and type BusinessObjects in the Title. Click Execute. 11. Double-click BusinessObjects : Global Data Quality Connector to open the Reference to a Structure window. 12. Copy the field in The node refers to the structure and paste it into the Node Name field. 13. Click Enter and then click Save. 14. Click Create in the Change Request window. 15. Enter a name for the change request and click Save. 16. Click Enter to clear the task dialog. Verify insertion To verify that the Data Quality for SAP IMG structure is correctly inserted into the SAP Reference IMG structure, follow these steps: 1. Enter transaction /nspro in the command box. 2. Click SAP Reference IMG and navigate to the path that corresponds to your Basis version. Basis version Path 6.20 (R/3 4.7) SAP Web Application Server > Basis Services > Address Management 128 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Basis version 6.40 (ECC 5.0) SAP NetWeaver > SAP Web Application Server > Basis Services > Address Management 7.00 (ECC 6.0 and CRM 5.0) 7.01 (CRM 7.0 and ERP 6.0) 7.10 (Banking Services 6.0) Path SAP Web Application Server > Application Server > Basis Services > Address Management SAP NetWeaver > Application Server > Basis Services > Address Management SAP Web Application Server > Application Server > Basis Services > Address Management You should now see the entry, BusinessObjects : Global Data Quality Connector, within the IMG structure. 3. Exit your SAP system. Step 3: Activate the Business Configuration Sets on each target client After you insert the BusinessObjects IMG structure into the SAP Reference IMG structure, activate the Business Configuration Sets on each of the target clients (non-000 logon clients) that you want to configure for use with Data Quality for SAP. Repeat these steps for each target client that you want to configure for use with Data Quality for SAP. 1. From one of the target clients, use /nscpr20 to navigate to the Business Configuration Sets : Activation transaction. 2. Type /FLDQ/47U6X in the BC Set input field and click Enter. The following Short text appears: Business Configuration Set for BusinessObjects AAK 06-21-07. (The date may vary.) 3. Click the Activate button or select Activate from the BC Set menu. 4. Create a new change request. (Click OK if a caution appears.) 5. In the Activation Options window click Continue Activation (Enter). An Activation completed message appears at the bottom of the window. 129

Activate region and country fields in TSAD10 This activity is a post-installation configuration for first-time installations of this product. It can be performed at any time necessary, but if you are upgrading from a full installation of the previous version of this product, this step would have been a part of the installation of that previous version. Users performing a fresh installation must perform this task. By default the region and country fields are available for use in the TSAD10 table. You must manually activate these fields for use. The following screen shows the values for the columns within the TSAD10 table (though the shown by transaction SM30 in the procedure below is different). To activate the fields: 1. Invoke transaction SM30. The Maintain Table Views window appears. 2. Enter table name TSAD10. 3. In the TSAD10 table, check the boxes for the fields region and country to activate them for use. 4. Save your changes. The region and country fields are now available for the data quality operations of this product. 130 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

SAP handshake with RFC Server This activity is a post-installation configuration for first-time installations of this product. It can be performed at any time necessary, but if you are upgrading from a full installation of the previous version of this product, this step would have been a part of the installation of that previous version. Users performing a fresh installation must perform this task. When performing this activity, you must do so on each target (non-000) client. To find this activity in the IMG structure, follow this process: 1. Use the transaction SPRO to access the IMG structure. 2. Navigate down the IMG structure to the location of this activity. On an R/3 system, the activity is in the following location: Implementation Guide for R/3 Customizing (IMG) > Basis Components > Basis Services > Address Management > BusinessObjects : Global Data Quality Connector > SAP handshake with the RFC server Purpose of the activity This activity allows you to define the RFC destination and test whether the components of Data Quality for SAP are able to communicate by invoking a TCP/IP handshake. The first time this activity is invoked, you must define the RFC destination. The RFC Server must be running in order to complete this activity. Define the RFC destinations The RFC Server is used to perform postal validation and duplicate check functions on data sent by the SAP system. To communicate with the RFC Server from within the IMG, you must define the RFC destinations for the server. Define FL_GDQC_SERVER To define the RFC destination FL_GDQC_SERVER: 1. From the IMG on a target (non-000) client, click on the activity named SAP handshake with the RFC server. The Display and Maintain RFC Destinations window appears. On SAP versions that use Basis 7.00, this window is named Configuration of RFC Connections. 2. Click Create. The RFC Destination window appears. 3. Fill in the fields of the RFC Destination window as follows: RFC Destination: FL_GDQC_SERVER Connection type: T Description: Connection to BusinessObjects GDQC RFC Server 131

By default, Data Quality for SAP expects the name of the RFC destination to be FL_GDQC_SERVER. If you choose not to use the name FL_GDQC_SERVER, you must go to the activity Maintain operating parameters on page 56 and ensure that the value of the RFC_DEST parameter is the name of the chosen RFC destination. 4. Press Ctrl+S to save the settings. 5. Click Registration (in R/3) or choose Registered Server Program (CRM) to make the Activation Type Registration. This setting is desired because the RFC Server is registered on the SAP gateway as an RFC server. 6. Type the Program ID as FLRFCSRV. By default, Data Quality for SAP expects the Program ID to be FLRFCSRV. If you choose not to use the Program ID FLRFCSRV, you must edit the <sap_progid> setting in the configuration file flrfcsrv.xml. For details on editing this configuration file, see Configuring through flrfcsrv.xml on page 62. 7. If you are installing Data Quality for SAP on a Unicode system, select the Special Options tab. On SAP versions that use Basis 7.00 and above, this tab is labeled MDMP & Unicode. 8. If you are installing Data Quality for SAP on a Unicode system, select Unicode in the Character Width in Target System field. 9. If you are installing Data Quality for SAP on a Unicode system, Press Ctrl+S to save the settings and exit the activity. The final steps of this procedure apply to all users. 10. Click the Connection Test button. If the RFC Server is running and the connection is successful, a confirmation appears. Click Back. 11. Press Ctrl+S to save the settings. Define FL_GDQC_BATCH To define the RFC destination FL_GDQC_BATCH: 1. From the IMG on a target (non-000) client, click on the activity named SAP handshake with the RFC server. The Display and Maintain RFC Destinations window appears. On SAP versions that use Basis 7.00, this window is named Configuration of RFC Connections. 2. Click Create. The RFC Destination window appears. 3. Fill in the fields of the RFC Destination window as follows: RFC Destination: FL_GDQC_BATCH Connection type: T Description: Connection to BusinessObjects GDQC Batch RFC Server 132 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

By default, Data Quality for SAP expects the name of the RFC destination to be FL_GDQC_BATCH. If you choose not to use the name FL_GDQC_BATCH, you must go to the activity Maintain operating parameters on page 56 and ensure that the value of the RFC_DEST parameter is the name of the chosen RFC destination. 4. Press Ctrl+S to save the settings. 5. Click Registration (in R/3) or choose Registered Server Program (CRM) to make the Activation Type Registration. This setting is desired because the RFC Server is registered on the SAP gateway as an RFC server. 6. Type the Program ID as FLRFCBTC. By default, Data Quality for SAP expects the Program ID to be FLRFCBTC. If you choose not to use the Program ID FLRFCBTC, you must edit the <sap_progid> setting in the configuration file flrfcsrv.xml. 7. If you are installing Data Quality for SAP on a Unicode system, select the Special Options tab. On SAP versions that use Basis 7.00 and above, this tab is labeled MDMP & Unicode. 8. If you are installing Data Quality for SAP on a Unicode system, select Unicode in the Character Width in Target System field. 9. If you are installing Data Quality for SAP on a Unicode system, Press Ctrl+S to save the settings and exit the activity. The final steps of this procedure apply to all users. 10. Click the Connection Test button. If the RFC Server is running and the connection is successful, a confirmation appears. Click Back. 11. Press Ctrl+S to save the settings. 133

Load supported country codes This activity is a post-installation configuration for first-time installations of this product. It can be performed at any time necessary, but if you are upgrading from a full installation of the previous version of this product, this step would have been a part of the installation of that previous version. Users performing a fresh installation must perform this task. When you perform this activity, you must load into each target (non-000) client the supported countries on which Data Quality for SAP can perform postal validation. Running the transaction and report To load supported country codes: 1. On a target (non-000) client, run transaction SA38. The ABAP: Execute Program window appears. 2. In the Program field, specify /FLDQ/AD_REPT_LOAD_COUNTRIES. 3. Click Execute. The supported countries are loaded into a table that you can maintain from the IMG activity Maintain Supported Countries. 4. Repeat these steps on each target client that you want to configure for use with Data Quality for SAP. After loading the country codes with this step, you can optionally configure Data Quality for SAP by removing country codes for which you have not purchased support by using the Maintain Supported Countries IMG activity. For details, see the section Maintain Supported Countries on page 48. 134 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Activate duplicate check index pools This activity is a post-installation configuration for first-time installations of this product. It can be performed at any time necessary, but if you are upgrading from a full installation of the previous version of this product, this step would have been a part of the installation of that previous version. Users performing a fresh installation must perform this task. When you run this activity, you must run it on each target (non-000) client. Though this activity is part of the standard SAP functionality and not added specifically by Data Quality for SAP, it is required for the proper functioning of Data Quality for SAP. You must perform this procedure on each target (non-000) client. Data Quality for SAP relies on these duplicate check index pools to perform its duplicate check processes. To find the Activate duplicate check index pools activity within the IMG structure, follow this process: 1. On a target (non-000) client, use the transaction SPRO to access the IMG structure. 2. Click the SAP Reference IMG button. 3. Navigate down the IMG structure to the location of this activity. On an R/3 system, the activity is in the following location: Implementation Guide for R/3 Customizing (IMG) > Basis Components > Basis Services > Address Management > Activate duplicate check index pools This IMG structure assumes you are running R/3. However, the IMG structure for a CRM or ECC system is similar. Whether you are running R/3 or CRM, the node is labeled as Activate duplicate check index pools. Purpose of this activity This activity creates the standard SAP index pools, KNA1 and BUT000, which are useful when Data Quality for SAP searches for duplicate data. Initially, the index pools are not active. Activate the index pools To activate the two standard SAP index pools, follow these steps: 1. In the IMG, click on the activity, Activate duplicate check index pools. The Customizing Settings For Logical Search Pools: Overview window appears. 2. Type 90 in the Threshold field for index pool BUT000, and select Index Active. A checked box activates the index pool. 3. R/3 only: Type 90 in the Threshold field for index pool KNA1, and select the Index Active box. A checked box activates the index pool. 135

4. Press Ctrl+S to save the settings. 5. Repeat the entire process for each target (non-000) client.! Warning: When you activate index pools in SAP CRM systems, you should not activate the index pool KNA1 ADRNR. If you have previously activated index pool KNA1 ADRNR in a SAP CRM system, you should deactivate it. This functionality is not supported in SAP CRM systems. 136 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Install and configure Data Quality for SAP into the CRM IC WebClient or CRM WebClient This section describes the requirements and procedures to install the functionality of Data Quality for SAP into your CRM IC WebClient or CRM WebClient environment. Requirements for running in a WebClient profile To run the functionality of Data Quality for SAP within your WebClient profiles, you must run SAP CRM 2007 or CRM 7.0. Refer to these SAP Support Notes to determine if additional configuration or support packages are necessary for your configuration. Note # Description 1250600 Postal Validation for Business Partner Address 1286002 CRM WEB UI: Country gets erased on saving 1299693 Postal Validation: Saving of correct address 1300236 CRM WebUI : Country gets erased on saving 1340952 Address validation: address not taken over from popup 1351582 Address validation: address not taken over from popup (regarding double save) 1356120 In the Account Identification, when trying to create and save a duplicate record, the save is not possible. A unique record, however, can be saved. 1359568 Account/Contact Creation: Address Validation + Direct Save 1384111 Exception saving related partner 1376561 Duplicate Check on Create Contact Person screen 1384877 At End: Database update failed. Rollback has been triggered. 1378301 Address validation & duplicate check on More Fields 1371528 Address Validation & Duplicate Check Summary of configuration tasks To install the functionality of Data Quality for SAP into your CRM IC WebClient or CRM WebClient environment, you must add a Component Usage to the Component to which you want to add Postal Validation. You add the Component Usages using the Enhancement Framework. Make sure that you have imported the correct.sar files provided as part of the installation of this product into your SAP system. For information on importing.sar files, see Installing the BAdIs from the previous version on page 124. Activate the BSP BC Sets To activate the BSP Business Configuration Sets, open the target client (the one that you want to configure for use with the Data Quality for SAP) and follow these steps: If you are upgrading a current WebClient installation, delete the contents of the /FLDQ/AD_FORMMAP table prior to activating the BC set. 137

1. Enter transaction /nscpr20 in the target client to navigate to the Business Configuration Sets : Activate transaction. 2. Type /FLDQ/BSP_PV in the BC set input field and click Enter. The following Short text appears: BC Set for BusinessObjects BSP_PV Product 02/08/08. (The date varies.) 3. Click Activate. 4. Create a new change request when the window appears. (Dismiss any caution that may appear.) 5. Click Continue Activation (Enter) in the Activation Options window. An Activation completed message appears at the bottom of the window. 6. Repeat these steps for each target client that you want to configure for use with Data Quality for SAP. Creating an Enhancement Set An SAP client can only have one Enhancement Set active at one time. If the SAP client does not already have an Enhancement, you can create an Enhancement Set by following this procedure. If the SAP client already has an Enhancement Set, you can skip this procedure. To create an Enhancement Set and assign it to a client: 1. Go to transaction SM34. The View Cluster Maintenance window appears. 2. Enter View Cluster name BSPWDVC_CMP_EXT. 3. Click the Maintain button. You may receive warnings from the SAP system but you can proceed with this procedure. 4. Click the New Entries button. The Change View Enhancement Set Definition window appears. 5. Enter an Enhancement Set name and a description for it. 6. Save the record. The SAP system requires that you perform the steps to create a new request. 7. Invoke transaction SM30. The Maintain Table Views window appears. 8. Enter table name BSPWDV_EHSET_ASG. 9. Click Maintain. 10. Click New Entries. 11. Enter the client number for which you want to create the Enhancement, and the Enhancement Set name that you created in this procedure. 12. Save the record. The SAP system requires that you perform the steps to create a new request. Find the name of the Component to Enhance When you enhance the Component to install the functionality of Data Quality for SAP into your CRM IC WebClient or CRM WebClient environment, you must know the name of the Component that you intend to enhance. If you do not already know the name of the Component, you can find the name with this procedure. 138 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

To find the name of the Component to enhance: 1. From any window in which you can enter address data, click one of the address fields to assign it focus. 2. Press F2 on your keyboard. A Technical Data window appears, which contains among its fields the component name used for addressing, UI_Component. Enhance the Component To enhance the Component: 1. Go to transaction BSP_WD_CMPWB. 2. Enter the names of the Component and the Enhancement Set. 3. Click Display. 4. Click on the Runtime Repository Editor tab. 5. Click Edit. 6. Expand the Component Usages menu item. 7. Click the change button. 8. Right click on Component Usages and select Add Component Usage. 9. In the Create Component Usage window, enter the following data: Field ID Used Component Interface View Value PostalValidation /FLDQ/DQXI_PV /FLDQ/DQXI_PV/DQXI_PV 10. Save and exit. 139

140 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide

Index Symbols /FLDQ/AD_PUPDATE table, 50, 89 /FLDQ/AD_REPT_DISP_QTRERRORLOG, 40 /FLDQ/AD_REPT_DISPLAY_ERRLOG error log, 99 /FLDQ/AD_REPT_LOAD_COUNTRIES, 134 /FLDQ/AD_REPT_UPDATE_PEND_RECS, 89 /FLDQ/AD_VAL_CNT table, 48 /FLDQ/RSADRINI, 42, 81 /FLDQ/RSADRQU2, 39 /FLDQ/RSMTCCODE, 42 A AD_REPT_UPDATE_PEND_RECS program, 89 address engine enable or disable, 28 B BAdIs installation, 34 installation requirements, 19 break key configure, 76 definition, 74 C check status D record, 39 combine_house_num_and_pmb option, 96 configuring IMG, 45 RFC Server, 61 correction, 12 CRM IC WebClient, 137 D D record, 39 data quality, 12 Data Quality Management for SAP overview, 11 Data Services documentation, 15 installation notes, 22 introduction to, 15 jobs, 95 dataflows, 64 deduplication. See also matching dialog suppressing, 49 documentation Data Services, 15 duplicate check, 73 definition, 74 using, 80 E error codes duplicate check, 103 postal validation, 102 technical, 99 error log, 99 error tolerant search, 73 definition, 74 suppressing, 49 using, 83 F fields address reviewer, 52 hit list, 54 FL_GDQC_SERVER, 132, 133 flrfcsrv.xml, 94 editing, 62 fmt.xml, 64 G geocoding, 43 error, 93 H hit list, 80, 83 I IMG configuration, 45 IMG activities Activate duplicate check index pools, 135 Maintain exception table of transaction codes, 49 Maintain fields for address reviewer, 52 Maintain fields for duplicate hit list display, 54 Maintain operating parameters, 56 Maintain supported countries, 48 Maintain table to activate SAP postal code check before postal validation, 51 SAP handshake with RFC Server, 47, 131 initial setup program /FLDQ/RSADRINI, 42, 81 installation, 17 BAdIs, 34 Data Services, 22 RFC Server, 30 connection closed, 86 troubleshooting, 86 Index 141

J Java requirements for RFC Server, 18 L log files RFC Server, 86 M Maintain exception table of transaction codes, 49 Maintain fields for duplicate hit list display, 54 Maintain operating parameters, 56 Maintain supported countries, 48 Maintain table to activate SAP postal code check before postal validation, 51 manifest information, 94 match engine, 14 matching, 13 name data, 79 military regions, 68 O operating parameters, 56 option combine_house_num_and_pmb, 96 overview correction, 12 data quality, 12 matching, 13 parsing, 12 standardization, 13 P P.O. Box addresses, 52 parsing, 12 postal validation, 69 engine, 14 interactive cleansing, 70 quarterly adjustment reports, 38 suppressing, 49 Q quarterly adjustment, 38 /FLDQ/RSADRQU2, 39 error log, 40 R regions military, 68 regions.xml, 64, 68 understanding regions, 89 requirements BAdIs, 19 RFC Server, 18 SAP Support Notes, 18 RFC Server checking connection, 86 configuring, 61 console, 94 flrfcsrv.xml, 62 overrides, 66 installation, 30 Java requirements, 18 Program ID, 56, 132, 133 requirements, 18 SAP handshake, 131 starting, 32 stopping, 33 troubleshooting, 94 RSMTCCODE program, 42, 91 S SAP Support Notes requirements, 18 search suppressing, 49 standardization, 13 suppress dialog, 49 suppress search, 49 suppress validation, 49 T table /FLDQ/AD_VAL_CNT, 48 transaction SA38, 39, 40, 42, 81, 89, 99, 134 SAINT, 124 SMGW, 33, 86, 93 SPRO, 46, 131, 135 U Unicode, 31 troubleshooting, 87 V validation suppressing, 49 W WebClient, 137 142 SAP BusinessObjects Data Quality Management, version for SAP Solutions User s Guide