sap users guide en

116
Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1) July 2009 SAP ® BusinessObjects™ Data Quality Management, version for SAP Solutions User’s Guide

Upload: rajesh-gumpena

Post on 12-Mar-2015

284 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: Sap Users Guide En

SAP® BusinessObjects™ Data Quality Management, version for SAP SolutionsUser’s Guide

Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1)

July 2009

Page 2: Sap Users Guide En

Notices

Copyright information © 2009 SAP, AG. All rights reserved. SAP Business Objects owns the following U.S. patents, which may cover products that are offered and licensed by Business Objects: 5,295,243; 5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742; 5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259; 6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409; 6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766; 7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130; 7,299,419; 7,320,122 and 7,356,779. Business Objects and its logos, BusinessObjects, Business Objects Crystal Vision, Business Process On Demand, BusinessQuery, Cartesis, Crystal Analysis, Crystal Applications, Crystal Decisions, Crystal Enterprise, Crystal Insider, Crystal Reports, Crystal Vision, Desktop Intelligence, Inxight and its logos, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let There Be Light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in the United States and/or other countries of Business Objects and/or affiliated companies. SAP is the trademark or registered trademark of SAP AG in Germany and in several other countries. All other names mentioned herein may be trademarks of their respective owners.

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

Page 3: Sap Users Guide En

Contents

Preface ............................................................................................................ 7About this guide.........................................................................................7Access the latest SAP Business Objects documentation ...........................7Conventions ...............................................................................................7Assumed audience .....................................................................................8Product naming conventions......................................................................8

Chapter 1:Overview ........................................................................................................ 9Data quality overview ....................................................................................10

What is data quality? ...............................................................................10What steps are involved in data quality? .................................................10The results of data quality........................................................................11

What is SAP BusinessObjects Data Quality Management, version for SAP Solutions? .......................................................................................................12

Components of this product.....................................................................12Postal validation engine...........................................................................12Match engine ...........................................................................................12

Introduction to SAP BusinessObjects Data Services .....................................13Hub of data quality needs ........................................................................13Access Data Services documentation on Windows.................................13

Chapter 2:Installing Data Quality for SAP................................................................. 15System requirements ......................................................................................16

Required SAP Support Notes for your system ........................................16Requirements for the RFC Server............................................................16Requirements for the BAdIs ....................................................................17

The installation process..................................................................................18Install Data Services.......................................................................................19

Data Services install machine..................................................................19Data Services must be running ................................................................19Start the Data Services Address Server service.......................................19

Install the Data Services Component .............................................................20Install the Data Services Component for Windows Data Services configuration............................................................................................20Install the Data Services Component for UNIX/Linux Data Services configuration............................................................................................21Edit DQ_SAP_DS datastore properties ...................................................22Use global variables to disable engines ...................................................22Create the batch RDBMS staging tables .................................................23Configure jobs as services .......................................................................23

Install the RFC Server ....................................................................................26Install a dedicated RFC Server for batch duplicate search ......................26Installing the RFC Server as a Windows Service....................................26Upgrading from a previous version .........................................................26

Contents 3

Page 4: Sap Users Guide En

Install the RFC Server ............................................................................. 26Start the RFC Server ............................................................................... 27Stop the RFC Server................................................................................ 28

Install the BAdIs ............................................................................................ 29Step 1: Import the Data Quality Management package on client 000 .... 29Step 2: Insert the Data Quality Management IMG structure on client 000 ................................................................................................. 32Step 3: Activate the Business Configuration Sets on each target client.. 34Postrequisite for ERP 6.0, CRM 7.0, and Banking Services 6.0 users ... 34

SAP handshake with RFC Server .................................................................. 35Purpose of the activity............................................................................. 35Define the RFC destinations ................................................................... 35

Load supported country codes ....................................................................... 38Running the transaction and report ......................................................... 38

Activate duplicate check index pools ............................................................ 39Activate the index pools.......................................................................... 39

Quarterly Adjustment Reports ....................................................................... 41Report RSADRQU1................................................................................ 41Report /FLDQ/RSADRQU2 ................................................................... 42Report RSADRQU3................................................................................ 43Quarterly Adjustment custom error report .............................................. 44

Run the initial setup program......................................................................... 45Purpose of initial setup............................................................................ 45Run the initial setup................................................................................. 45

Install and configure Data Quality for SAP into the CRM IC WebClient or CRM WebClient ............................................................................................ 46

Requirements for running in a WebClient profile................................... 46Summary of configuration tasks ............................................................. 46Activate the BSP BC Sets ....................................................................... 46Creating an Enhancement Set ................................................................. 47Find the name of the Component to Enhance ......................................... 47Enhance the Component.......................................................................... 48For CRM 5.0: Maintain exception table of transaction codes................. 48

Configure geocoding...................................................................................... 49Configure the RFC Server for geocoding ............................................... 49Register geocoding program in SAP....................................................... 49Configure the country.............................................................................. 49Designate fields to use for geocoding ..................................................... 50

Chapter 3:Configuring through the IMG................................................................... 51Locating the Data Quality for SAP IMG activities........................................ 52SAP handshake with RFC server................................................................... 53Maintain Supported Countries ....................................................................... 54

Remove the country codes ...................................................................... 54Maintain exception table of transaction codes............................................... 55

Add a transaction code to the exception table......................................... 55Maintain table to activate SAP postal code check before postal validation .. 57

Add a country to the table ....................................................................... 57Maintain fields for address reviewer ............................................................. 58

Fields and order for standard street addresses......................................... 58Fields and order for P.O. Box addresses ................................................. 58Make changes to the fields for the address reviewer .............................. 58

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

Page 5: Sap Users Guide En

Maintain fields for duplicate hit list display...................................................60Fields and order for error tolerant search and duplicate search...............60Make changes to the fields for the duplicate hit list display....................61

Maintain operating parameters.......................................................................62Operating parameters...............................................................................62Modify the parameters.............................................................................63

Map address types for Quarterly Adjustment ................................................64Defining mappings...................................................................................64Predefined mappings ...............................................................................64Add a mapping for an Address Type Code..............................................64

Chapter 4:Configuring the RFC Server ...................................................................... 67Configuring through flrfcsrv.xml...................................................................68

Location of flrfcsrv.xml ...........................................................................68Editing flrfcsrv.xml..................................................................................68SAP settings and DQ Server settings.......................................................68File settings..............................................................................................68General settings .......................................................................................70Dataflows.................................................................................................70Overrides..................................................................................................71

Chapter 5:Postal address validation ............................................................................ 73Interactive cleansing with Data Quality for SAP ...........................................74

Using interactive cleansing......................................................................74Multiple suggestions................................................................................75

Batch cleansing with Quarterly Adjustment Reports .....................................76

Chapter 6:Duplicate check and error tolerant search ............................................... 77Understanding duplicate check and error tolerant search ..............................78

Duplicate check .......................................................................................78Error tolerant search ................................................................................78Break Keys...............................................................................................78

Understanding break keys and data fields......................................................79How Data Services determines a break key ............................................79Configure the break key settings .............................................................80Match on name data.................................................................................81

Using duplicate check ....................................................................................83Interactive mode ......................................................................................83Batch mode ..............................................................................................84

Using error tolerant search .............................................................................86The hit list ................................................................................................86Fields displayed .......................................................................................87

Chapter 7:Tips and troubleshooting ............................................................................ 89Installation troubleshooting............................................................................90

If the installation was unable to import the .atl files................................90Checking the RFC Server(s) connection .................................................90Connection to the RFC Server closed......................................................90Troubleshooting Unicode issues..............................................................90

Postal validation and duplicate check/error tolerant search troubleshooting.92

Contents 5

Page 6: Sap Users Guide En

Using the sample input files to test Jobs ................................................. 92Inability to save addresses for which the postal code cannot be completed ................................................................................................ 92Records created without break keys due to downtime of RFC Server.... 92Records not stored in pending update table when search disabled ......... 93Understanding regions............................................................................. 93Newfoundland region code for R/3 4.70................................................. 94RSMTCCODE program error message................................................... 94Include records with empty break keys................................................... 94Threshold values for duplicates............................................................... 94Addresses do not validate/Error T528..................................................... 95Generating reports in Data Services........................................................ 95DPV processing locked ........................................................................... 95

RFC Server Troubleshooting ......................................................................... 96Output manifest information ................................................................... 96RFC Server stops because it could not find server function ‘ADDR_GEO’......................................................................................... 96

Appendix A:Data Services Jobs and Options ................................................................. 97

Data Services jobs ................................................................................... 97Combine House Num and PMB option................................................... 98

Appendix B:Error Codes ................................................................................................ 101

Technical error codes ............................................................................ 101Postal validation error codes ................................................................. 104Duplicate check error code.................................................................... 105

Appendix C:External List Management ....................................................................... 107Using Data Quality for SAP with ELM....................................................... 108

Cleansing the external list prior to loading via ELM............................ 108ELM functionality for different versions of SAP CRM........................ 108Records with only name data ................................................................ 108

Appendix D:Databases for staging tables...................................................................... 109

Oracle RDBMS inputs screen ............................................................... 109DB2 RDBMS inputs screen .................................................................. 109MS SQL RDBMS inputs screen............................................................ 110MySQL 5.0 RDBMS inputs screen....................................................... 110Sybase ASE RDBMS inputs screen ...................................................... 111

Index........................................................................................................... 113

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

Page 7: Sap Users Guide En

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 SAP Business Objects 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 Description

Bold We use bold type for file names, paths, emphasis, and text that you should type exactly as shown. For example, “Type cd\ dirs.”

Italics 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).”

Menu commands 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 poten-tial 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.

7

Page 8: Sap Users Guide En

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 ERC), 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 3.1 is often in this guide called Data Services.

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

Page 9: Sap Users Guide En

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 9

Page 10: Sap Users Guide En

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:

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

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

Page 11: Sap Users Guide En

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 11

Page 12: Sap Users Guide En

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.1 (12.1.1) - Data Quality Management Premium license, which handles data quality processing tasks on the data it receives from the RFC Server.Data Services Component, which provide 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/IPThree 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.

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

Page 13: Sap Users Guide En

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.

To access the documentation:

1. Choose Start > Programs > SAP BusinessObjects XI 3.1 > SAP BusinessObjects Data Services > Data Services Documentation.

2. Click the appropriate shortcut for the documentation you want to view.

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.

Chapter 1: Overview 13

Page 14: Sap Users Guide En

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

Page 15: Sap Users Guide En

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

Data Quality for SAP Data Services Component

Data Quality for SAP RFC server

Data Quality for SAP Business Add-Ins (BAdIs)

Chapter 2: Installing Data Quality for SAP 15

Page 16: Sap Users Guide En

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.

In addition, you should review any other SAP Support Notes for any content related to Data Quality Management applicable to your SAP platform.

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

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.

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 Data Ser-vices XI 3.1 SP02 and higher already have this issue resolved.

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

Page 17: Sap Users Guide En

Requirements for the BAdIs

The BAdIs portion of this product requires one of the following SAP environment:

SAP Customer Relationship Management (SAP CRM) solutions 5.0, 7.0, and 2007

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

Chapter 2: Installing Data Quality for SAP 17

Page 18: Sap Users Guide En

The installation process

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

2. Install Data Services Component

3. Install the RFC Server

4. Create the repository staging table

On your SAP system:

5. Install the Data Quality Management Business Add-Ins (BAdIs)

6. Perform the “SAP handshake with RFC server” IMG activity

7. Load the supported countries

8. Activate duplicate check index pools.

9. Run Quarterly Adjustments.

10. Run the initial setup program.

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

Page 19: Sap Users Guide En

Install Data Services

You must install Data Services before installing the RFC Server or BAdIs. 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 (prior to the installation of this product) and therefore have already installed a version of Data Services, you must upgrade to BusinessObjects Data Services XI 3.1, version 12.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 new version of Data Services XI 3.x. 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.

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.

Chapter 2: Installing Data Quality for SAP 19

Page 20: Sap Users Guide En

Install the Data Services Component

After you install Data Services, 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.

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

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.

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.

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.

For reference information on databases supported for staging tables, see “Databases for staging tables” on page 109.

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

Page 21: Sap Users Guide En

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. To install the Data Services Component for a UNIX/LINUX 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

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

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

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.

Keep in mind that the connection information you provide in this section is for your UNIX Data Services configuration.

For reference information on databases supported for staging tables, see “Databases for staging tables” on page 109.

Chapter 2: Installing Data Quality for SAP 21

Page 22: Sap Users Guide En

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.

Edit DQ_SAP_DS datastore properties

You must edit the DQ_SAP_DS datastore properties to set the password for the RDMBS user. To edit the DQ_SAP_DS datastore properties:

1. In the Data Services Designer, go to the datastores tab of the Local Object Library. Right-click on DQ_SAP_DS datastore and select Edit.

2. Set the password in the Edit datastore DQ_SAP_DS window for the RDMBS user. Click OK.

MySQL repository in Data Services

The installation routine of this product sets the value of the DQ_USER field in the DQ_SAP_DS datastore according to the user name of the repository database. For all supported databases except MySQL, the user name and schema are identical.

If your Data Services configuration uses MySQL as its repository database, you must ensure that the value of the DQ_USER field is same as the MySQL schema, even if the schema is different than the user name.

Use global variables to disable engines

You must disable the address cleanse engines for countries you did not purchase.

The table below lists the country engine substitution parameters.

To disable address cleanse engines:

For instructions on importing .atl files, see the Data Services documentation.

Substitution parameter Description

$$DQ_SAP_EngineUsa Enable or disable the USA engine

$$DQ_SAP_EngineAustralia Enable or disable the Australia engine

$$DQ_SAP_EngineCanada Enable or disable the Canada engine

$$DQ_SAP_EngineEmea Enable or disable the EMEA engine

$$DQ_SAP_EngineGlobalAddress Enable or disable the Global Address engine

$$DQ_SAP_EngineJapan Enable or disable the Japan engine

$$DQ_SAP_EngineMultiCountry 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 al the $$DQ_SAP_* substitution parameters in any configuration you use with this product.

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

Page 23: Sap Users Guide En

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 you have not purchased. You must perform this step for every configuration you use. If you did not purchase an address cleanse engine 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.

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.

3. In the Execution Properties window, select the appropriate configuration from the System configuration drop-down list.

The job executes. The system may produce a warning message due to the script job attempting to run a Drop Table command on a database table that does not exist. This message is expected and does not affect the successful configuration of this product.

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.

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

You must have an appropriate database client installed and a connection (such as an Oracle TNS entry) to the database created.

Job Service name

Job_Batch_DQ_SAP_Address_Cleanse Service_Batch_DQ_SAP_Address_Cleanse

Job_Realtime_Batch_DQ_SAP_Name_And_Address_Match

Service_Realtime_Batch_DQ_SAP_Name_And_Address_Match

Job_Realtime_DQ_SAP_Address_Cleanse

Service_Realtime_DQ_SAP_Address_Cleanse

Chapter 2: Installing Data Quality for SAP 23

Page 24: Sap Users Guide En

To configure jobs as services

You must perform this procedure for each job listed in the preceding table. 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.

8. Enter the service name for the job. For example, Service_Batch_DQ_SAP_Address_Cleanse (exact case is required) for the Service Name.

9. Enter 800 for the Processing Timeout value and click Apply.

10. Repeat steps 4 through 9 for each of the Real-time job listed in the preceding table.

Enable or disable an address engine

If necessary, 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.

Job_Realtime_DQ_SAP_Address_Cleanse_Suggestions

Service_Realtime_DQ_SAP_Address_Cleanse_Suggestions

Job_Realtime_DQ_SAP_Address_GEO Service_Realtime_DQ_SAP_Address_GEO

Job_Realtime_DQ_SAP_Create_Break_Keys

Service_Realtime_DQ_SAP_Create_Break_Keys

Job_Realtime_DQ_SAP_Create_Break_Keys_ExtraFlds

Service_Realtime_DQ_SAP_Create_Break_Key_ExtraFlds

Job_Realtime_DQ_SAP_Name_And_Address_Match

Service_Realtime_DQ_SAP_Name_And_Address_Match

Job_Realtime_DQ_SAP_Retrieve_Country_Purchased

Service_Realtime_DQ_SAP_Retrieve_Country_Purchased

Job_Realtime_DQ_SAP_US_DPV_Address_Cleanse_Suggestions

Service_Realtime_DQ_SAP_US_DPV_Address_Cleanse_Suggestions

Job Service name

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

Page 25: Sap Users Guide En

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.

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.

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 25

Page 26: Sap Users Guide En

Install the RFC Server

After you install and configure Data Services, and install the Data Services Component, you install the RFC Server. You can install more than one instance of the RFC Server.

Install a dedicated RFC Server for batch duplicate search

To run duplicate search functionality in batch mode (often called “batch match”), you must install and run a dedicated RFC Server, in addition to the RFC Server installed to run all other operations associated with Data Quality for SAP. Only one RFC Server dedicated to batch mode can be active on a gateway.

The configuration settings for this RFC Server are maintained in the configuration file flrfcbtc.xml. For more information about setting and configuring this dedicated RFC Server, see “Maintain operating parameters” on page 62.

For information about running duplicate search in batch mode, see “Batch mode” on page 84.

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 SAP1. Other instances of the RFC Server are named BusinessObjects DQM for SAP2, BusinessObjects DQM for SAP3, and so on. A dedicated RFC Server for batch duplicate search has the service name BusinessObjects DQM for SAP Batch.

Upgrading from a previous version

If you are upgrading from a previous version of this product and made customizations to the RFC Server settings, you should make copies of the previous version’s files flrfcsrv.xml, regions.xml, and tsad10.txt to use as a reference to those customizations. You must manually apply any customizations to this version of the product.

Install the RFC Server Install the RFC Server on a machine that meets the system requirements (“Requirements for the RFC Server” on page 16).

To install the RFC Server:

1. Locate the SAP BusinessObjects Data Quality Management, version for SAP Solutions - RFC Server media and launch setup.exe.

You must install the RFC Server from a user account that has permissions to install software on the machine.

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.

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

Page 27: Sap Users Guide En

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.

6. In the SAP Information window, enter the Host Name and Service of the SAP Gateway.

7. Select Yes or No to indicate whether your SAP system is Unicode compliant. Click Next.

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&amp;wsdlxml). Click Next.

10. In the Ready to Install the Program window, click Install. The installation proceeds

11. Click Finish when the installation has completed.

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

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.

You can use either the name or IP address of the SAP Gateway for the host name.

If your system is Unicode compliant, the step “SAP handshake with RFC Server” on page 35 has further configuration instructions on configuring Data Quality for SAP for Unicode systems.

Chapter 2: Installing Data Quality for SAP 27

Page 28: Sap Users Guide En

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.

For Windows:

install_directory\start_rfcserver.bat

install_directory\start_rfcserver_batch.bat

For UNIX/Linux:

install_directory/start_rfcserver

install_directory/start_rfcserver_batch

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, follow these steps to stop the RFC Server:

1. Use transaction SMGW. For information on the use and syntax of transaction SMGW, consult your SAP documentation.

Using transaction SMGW is the preferred method to stop the RFC Server if it is not installed as a Windows Service. However, 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, the Windows Services Console does not reflect the changed state until the Console is refreshed.

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

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. If the Data Services portion of this product is stopped for any reason, you must restart Data Services and then restart the RFC Server to reinitialize the Data Services dataflows.

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.

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

Page 29: Sap Users Guide En

Install the BAdIs

Before you proceed with these steps, make sure that your SAP system complies with all of the prerequisites described in “System requirements” on page 16.

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 29

“Step 2: Insert the Data Quality Management IMG structure on client 000” on page 32

“Step 3: Activate the Business Configuration Sets on each target client” on page 34

“Postrequisite for ERP 6.0, CRM 7.0, and Banking Services 6.0 users” on page 34

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.

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.

The BAdIs are installed and upgraded using the Add-on Installation Tool, invoked by the transaction SAINT.

Basis 6.20

SAR file New install or upgrade

\6.20\DATA\SAPK-40ACOINFLDQ.SAR New install

\6.20\DATA\UPGRADE\SAPK-40ACHINFLDQ.SAR Upgrade

You must (re)activate BC Set /FLDQ/47U6X to import new customizing data.

Basis 6.40

SAR file New install or upgrade

\6.40\DATA\SAPK-40ACOINFLDQ.SAR 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.

Chapter 2: Installing Data Quality for SAP 29

Page 30: Sap Users Guide En

Basis 7.00

SAR file New install or upgrade

\7.00\DATA\SAPK-40ACOINFLDQ.SAR New install for all users

\7.00\DATA\UPGRADE\SAPK-40ACHINFLDQ.SAR Upgrade for ECC 6 users who installed version 39 of this file.

\7.00\DATA\CRM50\SAPK-40BCOINFLDQ.SAR New installation package for IC Web Client PV and DES Business Add-ins for CRM 5.0.

\7.00\DATA\CRM2007\SAPK-40BCOINFLDQ.SAR New installation package for IC Web Client PV and DES Business Add-ins for CRM 2007.

\7.00\DATA\CRM50\UPGRADE\SAPK-40BCHINFLDQ.SAR

Upgrade for CRM 5.0 users who installed version 39 of this file.

\7.00\DATA\CRM2007\UPGRADE\SAPK-40BCHINFLDQ.SAR

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 to import new customizing data.

Basis 7.01

SAR file New install or upgrade

\7.01\DATA\CRM7\SAPK-40ACOINFLDQ.SAR New installation package for IC Web Client PV and DES Business Add-ins for CRM 7.

\7.01\DATA\ECC6 Enh Pack 4\SAPK-40ACOINFLDQ.SAR

New installation package for PV and DES Business Add-ins for ECC 6.

\7.01\DATA\CRM7\UPGRADE\SAPK-40ACHINFLDQ.SAR

Upgrade for CRM 7 users who installed version 39 of this file.

You must (re)activate BC Set /FLDQ/47U6X to import new customizing data.

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

Page 31: Sap Users Guide En

For information about the requirements and configuration procedures to use the functionality of this product within the CRM IC WebClient or CRM WebClient, see “Install and configure Data Quality for SAP into the CRM IC WebClient or CRM WebClient” on page 46.

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.

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 Add-on 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.

Basis 7.10

SAR file New install or upgrade

\7.10\DATA\SAPK-40ACOINFLDQ.SAR New install for all users

You must (re)activate BC Set /FLDQ/47U6X to import new customizing data.

Chapter 2: Installing Data Quality for SAP 31

Page 32: Sap Users Guide En

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.

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

Page 33: Sap Users Guide En

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

Chapter 2: Installing Data Quality for SAP 33

Page 34: Sap Users Guide En

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.

Postrequisite for ERP 6.0, CRM 7.0, and Banking Services 6.0 users

SAP ERP 6.0, CRM 7.0, and Banking Services 6.0 by default do not have the region and country fields made available for use in the TSAD10 table. You must manually activate these fields for use.

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.

6.40 (ECC 5.0) SAP NetWeaver > SAP Web Application Server > Basis Services > Address Management

7.00 (ECC 6.0 and CRM 5.0)

SAP Web Application Server > Application Server > Basis Services > Address Management

7.01 (CRM 7.0 and ERP 6.0)

SAP NetWeaver > Application Server > Basis Services > Address Management

7.10 (Banking Services 6.0)

SAP Web Application Server > Application Server > Basis Services > Address Management

Basis version Path

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

Page 35: Sap Users Guide En

SAP handshake with RFC Server

Now that you have installed the components of Data Quality for SAP, you must make some post-installation configurations on each target (non-000) client before you use Data Quality for SAP.

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.

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.

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

The RFC Server must be running in order to complete this activity.

On SAP versions that use Basis 7.00, this window is named Configuration of RFC Connections.

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 62 and ensure that the value of the RFC_DEST parameter is the name of the chosen RFC destination.

Chapter 2: Installing Data Quality for SAP 35

Page 36: Sap Users Guide En

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.

7. If you are installing Data Quality for SAP on a Unicode system, select the Special Options tab.

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.

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.

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

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

On SAP versions that use Basis 7.00 and above, this tab is labeled “MDMP & Unicode.”

The final steps of this procedure apply to all users.

On SAP versions that use Basis 7.00, this window is named Configuration of RFC Connections.

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 62 and ensure that the value of the RFC_DEST parameter is the name of the chosen RFC destination.

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

Page 37: Sap Users Guide En

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.

7. If you are installing Data Quality for SAP on a Unicode system, select the Special Options tab.

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.

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.

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 flrfcbtc.xml.

On SAP versions that use Basis 7.00 and above, this tab is labeled “MDMP & Unicode.”

The final steps of this procedure apply to all users.

Chapter 2: Installing Data Quality for SAP 37

Page 38: Sap Users Guide En

Load supported country codes

Now that you have connected your SAP system to the RFC Server, 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.

!Because of a known issue on AIX, the first time the user executes the FLDQ/AD_REPT_LOAD_COUNTRIES program, the RFC Server will fail (timeout). After this occurs, restart the RFC Server and run the program again.

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

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

Page 39: Sap Users Guide En

Activate duplicate check index pools

The next step in setting up Data Quality for SAP is to run the standard SAP IMG activity, Activate duplicate check index pools, on each target (non-000) client.

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

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.

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.

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.

Chapter 2: Installing Data Quality for SAP 39

Page 40: Sap Users Guide En

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.

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

Page 41: Sap Users Guide En

Quarterly Adjustment Reports

The next step in setting up Data Quality for SAP is to run Quarterly Adjustments. You must run Quarterly Adjustments on each target (non-000) as part of the installation and configuration process to perform postal validation on the existing data in your SAP system.

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.

Chapter 2: Installing Data Quality for SAP 41

Page 42: Sap Users Guide En

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.

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 confirmation window appears. If any records failed during validation, those records are shown here.

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 errorsD = 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.

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

Page 43: Sap Users Guide En

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.

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.

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.

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

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

Chapter 2: Installing Data Quality for SAP 43

Page 44: Sap Users Guide En

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.

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

Page 45: Sap Users Guide En

Run the initial setup program

The last step in setting up Data Quality for SAP is to run the initial setup program on each target (non-000) client.

Purpose of initial setup

The initial setup program prepares your existing data for matching with duplicate check and error tolerant search.

Run the initial setup To run the initial setup program:

1. Enter 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 program executes. Installation and setup are complete in this target (non-000) client.

3. Repeat steps 1-2 on each target client that you want to configure for use with Data Quality for SAP.

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

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.

Chapter 2: Installing Data Quality for SAP 45

Page 46: Sap Users Guide En

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 5.0 or higher.

If you are running 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.

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 “Install the BAdIs” on page 29.

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:

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.

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

If you are upgrading a current WebClient installation, delete the contents of the /FLDQ/AD_FORMMAP table prior to activating the BC set.

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

Page 47: Sap Users Guide En

The following Short text appears: BC Set for BusinessObjects BSP_PV Product 02/08/08. (The date may vary.)

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.

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.

Chapter 2: Installing Data Quality for SAP 47

Page 48: Sap Users Guide En

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:

10. Save and exit.

For CRM 5.0: Maintain exception table of transaction codes

Users of CRM 5.0 must navigate to the IMG activity “Maintain exception table for transaction codes” and perform a customization to enable the WebClient functionality of this product. For more information about navigating the IMG activities of this product, see “Configuring through the IMG” on page 51. For more information about this activity, see “Maintain exception table of transaction codes” on page 55.

For users of CRM 5.0, the importing the .SAR file for the WebClient creates in this IMG activity an additional column to specify the Program name.

Within the Program column, specify the Program name SAPMHTTP and check the boxes in that row to suppress validation, search, and suggestions.

Field Value

ID PostalValidation

Used Component /FLDQ/DQXI_PV

Interface View /FLDQ/DQXI_PV/DQXI_PV

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

Page 49: Sap Users Guide En

Chapter 2: Installing Data Quality for SAP 49

Page 50: Sap Users Guide En

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

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:

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.

Field Value

Source ID SAP1

Class CL_GEOCODER_GENERIC_RFC

Function Module ADDR_GEO

Destination FL_GDQC_SERVER

The default value for the destination is FL_GDQC_SERVER, but the value would be different if you chose a different RFC Destination in “Define the RFC destinations” on page 35.

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

Page 51: Sap Users Guide En

5. Set the exclusive flag.

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.

Chapter 2: Installing Data Quality for SAP 51

Page 52: Sap Users Guide En

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

Page 53: Sap Users Guide En

Chapter 3: Configuring through the IMG

Now that you have installed both 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 51

Page 54: Sap Users Guide En

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.

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.

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)

SAP Web Application Server > Application Server > Basis Services > Address Management

7.01 (CRM 7.0 and ERP 6.0)

SAP NetWeaver > Application Server > Basis Services > Address Management

7.10 (Banking Services 6.0)

SAP Web Application Server > Application Server > Basis Services > Address Management

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

Page 55: Sap Users Guide En

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 “SAP handshake with RFC Server” on page 35.

Chapter 3: Configuring through the IMG 53

Page 56: Sap Users Guide En

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.

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

Page 57: Sap Users Guide En

Maintain exception table of transaction codes

This activity allows you to disable suggestion lists, preventing them from being displayed for specific transactions.

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 55

Page 58: Sap Users Guide En

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.

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

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

Page 59: Sap Users Guide En

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 57

Page 60: Sap Users Guide En

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.

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

Page 61: Sap Users Guide En

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.

4. Save the changes and exit the window.

You must number both the street address data and P.O. Box data in sequence from 1 to the total number of displayed fields.

Chapter 3: Configuring through the IMG 59

Page 62: Sap Users Guide En

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.

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

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.

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

Page 63: Sap Users Guide En

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.

4. Save the changes and exit the window.

Both the duplicate check and error tolerant search data are to be numbered in sequence from 1 to the total number of displayed fields.

Chapter 3: Configuring through the IMG 61

Page 64: Sap Users Guide En

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

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.

AD_ADDRESS_SEARCH_FUNC_NM

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

AD_REVIEW_NEW_WIDTH

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.

AD_REVIEW_ORIG_WIDTH

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.

BATCH_MATCH_RFC_DEST

FL_GDQC_BATCH Dedicated RFC Server for handling duplicate search functional-ity in batch mode (also called “batch match”). This value is also called the Program ID of the RFC Server.

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 func-tion 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.

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.

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

Page 65: Sap Users Guide En

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.

Modify the parameters

To make changes to operating parameters:

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.

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 sec-tion “Records created without break keys due to downtime of RFC Server” on page 92.

NON_DIALOG_ERR_MSG space Toggles whether system messages are to be displayed in non-dia-log 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.

Parameter Name Default Value Description

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.

Chapter 3: Configuring through the IMG 63

Page 66: Sap Users Guide En

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

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

Page 67: Sap Users Guide En

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.

Chapter 3: Configuring through the IMG 65

Page 68: Sap Users Guide En

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

Page 69: Sap Users Guide En

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 67

Page 70: Sap Users Guide En

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.

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

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

One reason you might alter a setting in this section would be if you chose a Program ID other than FLRFCSRV during the activity “SAP handshake with RFC Server,” and now must edit the <sap_progid> setting to correspond to the correct Program ID. This step is mandatory if you have configured a dedicated RFC Server to support matching in batch mode.

Setting Description Default

log_level Provides two levels of logging. 1 - Only serious errors are logged2 - Serious errors and any important warnings and information messages are logged.

2

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

Page 71: Sap Users Guide En

uc_logging_flag Enables logging for the Universal Connector, which provides connection to Data Services.This setting is provided to allow cus-tomers to provide detailed information to customer support representatives. You should not change these values unless requested in a customer support situation.

false

uc_logging_file_dir Sets the directory of the log file for the Universal Connector, which provides connection to Data Services.This setting is provided to allow cus-tomers to provide detailed information to customer support representatives. You should not change these values unless requested in a customer support situation.

<none>

uc_playback_flag Enables the playback of data transfer feature of the Universal Connector, which provides connection to Data Services.This setting is provided to allow cus-tomers to provide detailed information to customer support representatives. You should not change these values unless requested in a customer support situation.

false

uc_bytes_per_log_file 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 cus-tomers to provide detailed information to customer support representatives. You should not change these values unless requested in a customer support situation.

1000000

uc_connect_timeout_sec

Maximum amount of time in seconds the RFC Server should attempt to con-nect to Data Services. Must be greater than or equal to zero. A setting of zero indicates no timeout.

300

uc_retry_connect_count

Maximum number of times the RFC Server should attempt to retry to con-nect to Data Services.

1

Setting Description Default

Chapter 4: Configuring the RFC Server 69

Page 72: Sap Users Guide En

General settings The following table shows the configurable settings and defaults in the section under the commented heading <!-- General Settings -->. All of these settings must have an entry.

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.

uc_connect_delay_between_retries

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 indi-cates that the RFC Server is to attempt continuously to connect to the Data Services and SAP Gateway without pausing between attempts.

0

enable_trace Determines whether the RFC Server should generate trace files. A trace file provides you with a history of transac-tions. Possible values are yes and no.

yes

tsad10_config Location and name of tsad10.txt, which is a file that stores valid match fields. The path is relative to the installation of this product.

config/tsad10.txt

region_file Location and name of regions.xml, which sets regions for a specific coun-try code. The path is relative to the installation of Data Quality for SAP

config/regions.xml

fmt_file Location and name of fmt.xml file, which is the format file., which speci-fies the format of tables that the gate-way passes as arguments to the RFC Server.

config/fmt.xml

Setting Description Default

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

include_empty_candidates_check

Determines whether to include empty candidates in address checks. Possible values are yes and no.

yes

include_empty_candidates_search

Determines whether to include empty candidates in address searches. This configuration setting is discussed in more detail in the section“RSMTC-CODE program error message” on page 94. Possible values are yes and no.

yes

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

Page 73: Sap Users Guide En

For more information about dataflows, see the Data Services documentation that shipped with this package.

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_rfcserver.bat by indicating the name of the override.

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_Address_Cleanse_Suggestions as a ser-vice, you can enable DPV address suggestions by changing the value of this key to Service_Realtime_DQ_SAP_US_DPV_Address_Cleanse_Suggestions.

Service_Realtime_DQ_SAP_Address_Cleanse_Suggestions

address_geo This setting is not enabled by default. To enable geocoding, remove the comments from this key.

Service_Realtime_DQ_SAP_Address_GEO

Chapter 4: Configuring the RFC Server 71

Page 74: Sap Users Guide En

set OVERRIDE="my_new_override_name"

5. Save and close both files. When start_rfcserver.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), right click on the 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_rfcserver.bat runs, it looks for the named override in flrfcsrv.xml and executes those override settings.

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

Page 75: Sap Users Guide En

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 73

Page 76: Sap Users Guide En

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.

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

Page 77: Sap Users Guide En

At this window you have three button options:

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 Action

Accept Validated Address

The previous window returns to focus with the corrected data popu-lating the fields.

Use Original Address

The previous window returns to focus with the data as originally entered populating the fields.

Cancel The previous window returns to focus and the process is cancelled.

Button Action

Select The previous window returns to focus with the data chosen here populating the fields.

Use Original Address

The previous window returns to focus with the data as originally entered populating the fields.

Cancel The previous window returns to focus and the process is cancelled.

Chapter 5: Postal address validation 75

Page 78: Sap Users Guide En

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, pre-determined 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.

For information about running Quarterly Adjustments, see “Quarterly Adjustment Reports” on page 41.

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

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

Page 79: Sap Users Guide En

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 77

Page 80: Sap Users Guide En

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.

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

Page 81: Sap Users Guide En

Understanding break keys and data fields

During duplicate check and error tolerant search, Data Quality for SAP uses break keys to limit the number of records used in duplicate searches. Once given input data, Data Quality for SAP determines a break key for the address and considers only stored records with the same break key value when searching for duplicates.

How Data Services determines a break key

By default, Data Quality for SAP uses the first three alphanumeric characters of the postal code and the first letter of the street field to generate the break key value. Therefore, in order to improve the results during a search, Data Quality for SAP 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 546M. The search process selects all of the records from the SAP system that have the break key value 546M. 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 546 and only records with a break key value of 546 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 546M.

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

During duplicate search, Data Quality for SAP 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 546M, even though you did not directly enter the postal code.

Chapter 6: Duplicate check and error tolerant search 79

Page 82: Sap Users Guide En

Configure the break key settings

The regular break key settings can be configured in the Data Services job Job_Realtime_DQ_SAP_Create_Break_Keys. For 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 instead using the job Job_Realtime_DQ_SAP_Create_Break_Keys_ExtraFlds, which has preconfigured logic to include data such as telephone numbers, email addresses, and two other extra, customizable fields. To use this job, you must change value of the key <break_keys> in flrfcsrv.xml to reflect that default job. For information on editing flrfcsrv.xml, see “Editing flrfcsrv.xml” on page 68.

To use the extra, customizable fields in Job_Realtime_DQ_SAP_Create_Break_Keys_ExtraFlds, 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 62.

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

Page 83: Sap Users Guide En

Change the default break key calculations

You can change the default break key calculations by modifying DF_Realtime_DQ_SAP_Create_Break_Keys_ExtraFlds in the Data Services Designer.

Within DF_Realtime_DQ_SAP_Create_Break_Keys_ExtraFlds, go to the BuildMatchCodeswithAddress transform, which is where the Match_code1 and Match_code2 are created. The function CF_DQ_SAP_CalculateMatchCode_ExtraFlds is where match codes are 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 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 81

Page 84: Sap Users Guide En

By default, Data Quality for SAP includes records with empty break keys when performing matches. In the file flrfcsrv.xml, the parameter for including records with empty break keys to find duplicates in postal validation is include_empty_candidates_check. The parameter for including records with empty break keys in duplicate search is include_empty_candidates_search. You can exclude records with empty break keys when performing matches by changing the default setting on each parameter from yes to no.

For more information on these settings and their values, see “General settings” on page 70.

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

Page 85: Sap Users Guide En

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:

The duplicate check hit list for the WebClient is shown here:

Button Action

Continue The previous window returns to focus showing the current address that the user accepted from the previous address reviewer window.

Select Duplicate The previous window returns to focus with the data from the selected record populating the fields.

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

Chapter 6: Duplicate check and error tolerant search 83

Page 86: Sap Users Guide En

At this window you have two button options:

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 60 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 (often called “batch match”) to find duplicate records in your Business Partners database.

To use duplicate search in batch mode:

1. Invoke transaction se38 to go to the ABAP editor screen.

2. In the ABAP editor screen, enter the program /FLDQ/RSBTCMTC. The Business Partner Batch Match screen appears.

Button Action

Continue The previous window returns to focus and the record the user entered is saved.

Cancel The previous window returns to focus and the process is cancelled.

To use duplicate search in batch mode, you must install a dedicated RFC Server to handle these tasks. For more information, see “Install a dedicated RFC Server for batch duplicate search” on page 26. You must also edit the the RFC Server configuration file flrfcbtc.xml on this dedicated RFC Server to reflect the proper Program ID (by default, FL_GDQC_BATCH) for the dedicated server.

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

Page 87: Sap Users Guide En

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

4. Execute the program.

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 Job_Realtime_DQ_SAP_Name_And_Address_Match_Cleanup in the Data Services Designer with the following structure in the input file of that Job: <DataSet><Record><BATCH_ID>*</BATCH_ID></Record></DataSet>

For information about the sample input files, see “Using the sample input files to test Jobs” on page 92.

For more information about the SAP functionality to create a cleansing case, see the SAP documentation.

Chapter 6: Duplicate check and error tolerant search 85

Page 88: Sap Users Guide En

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.

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

Page 89: Sap Users Guide En

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.

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 60 for information on the default settings and the procedure for making changes to the fields displayed.

Button Action

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

New Search The search window returns, populated by the data you entered.

Cancel The standard SAP search window is displayed.

Chapter 6: Duplicate check and error tolerant search 87

Page 90: Sap Users Guide En

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

Page 91: Sap Users Guide En

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 89

Page 92: Sap Users Guide En

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

2. Copy the file SupportedCountriesList.xml to the \bin directory of the Data Services configuration.

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.

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

For instructions on importing .atl files, see the Data Services documentation.

Type of log file Path and name

Windows Service Transactional \logs\BusinessObjects DQM for SAP#_log.txt

Windows Service Batch \logs\BusinessObjects DQM for SAP Batch_log.txt

Non-service Transactional \logs\flrfcsrv_log.txt

Non-service Batch \logs\BusinessObjects DQM for SAP Batch_log.txt

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

Page 93: Sap Users Guide En

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.

5. Save the settings (Ctrl+S).

Unicode

Chapter 7: Tips and troubleshooting 91

Page 94: Sap Users Guide En

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 62.)

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

Page 95: Sap Users Guide En

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

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 93

Page 96: Sap Users Guide En

Therefore, if the order of these regions map is different, you get a different result that might be unexpected.

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.

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.

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.

In the file flrfcsrv.xml, the parameter for including records with empty break keys to find duplicates in postal validation is include_empty_candidates_check. The parameter for including records with empty break keys in duplicate search is include_empty_candidates_search.

For more information on these settings and their values, see “General settings” on page 70.

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

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

Page 97: Sap Users Guide En

For information on configuring this IMG activity, see your SAP documentation.

Addresses do not validate/Error T528

If addresses do not validate and Error T528 is recorded in the RFC Server log files, the cause may be that the Data Services was stopped and restarted without restarting the RFC Server. For more information, see “Start the RFC Server” on page 27.

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.

Chapter 7: Tips and troubleshooting 95

Page 98: Sap Users Guide En

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

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.

RFC Server stops because it could not find server function ‘ADDR_GEO’

If geocoding is registered in your SAP system, but in the RFC Server configuration file, flrfcsrv.xml, the XML key <address_geo> is commented out, the RFC Server will shut down with the first record processed and the following error is reported in the flrfcsrv_log.txt file:

JCO. Server:could not find server function 'ADDR_GEO'

Because the key for geocoding in the RFC Server is not enabled, the RFC Server shuts down upon being sent a server function it is not configured to handle. You must uncomment the XML key <address_geo> to configure the RFC Server.

For more information, see “Configure geocoding” on page 49.

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

Page 99: Sap Users Guide En

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.

Data Services jobs These jobs are located in the Data Services Designer after you install the Data Services Component.

Consult the Data Services documentation for general procedures for working with Data Services jobs and options.

Job Description

Job_Batch_DQ_SAP_Address_Cleanse 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 41.

Job_Realtime_Batch_DQ_SAP_Name_And_Address_Match

This job handles batch mode processing. It performs the following func-tions:

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 poten-tial 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 pro-cessing 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.

Job_Realtime_DQ_SAP_Address_Cleanse This job is used when the IMG setting is configured so that the Sugges-tion List is disabled during the Address Validation. For information about suggestion lists, see “Maintain exception table of transaction codes” on page 55.

Job_Realtime_DQ_SAP_Address_Cleanse_Suggestions

This job is used when the IMG setting is configured so that the Sugges-tion List is enabled during the Address Validation. For information about suggestion lists, see “Maintain exception table of transaction codes” on page 55.

Job_Realtime_DQ_SAP_Address_GEO This job is used if you have purchased the geocoding option for this product. It processes latitude and longitude for US addresses. For infor-mation about activating geocoding functionality, see “Configure geoc-oding” on page 49.

97

Page 100: Sap Users Guide En

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.

Job_Realtime_DQ_SAP_Create_Break_Keys This job contains the settings for determining break keys. For informa-tion on break keys, see “Understanding break keys and data fields” on page 79.

Job_Realtime_DQ_SAP_Create_Break_Keys_ExtraFlds

This job contains the settings for determining break keys, with extra fields such as telephone number, email address, and so on. For informa-tion on break keys, see “Understanding break keys and data fields” on page 79.

Job_Realtime_DQ_SAP_Name_And_Address_Match

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.

Job_Realtime_DQ_SAP_Retrieve_Country_Purchased

This job retrieves the list of countries for which you can perform postal validation.

Job_Realtime_DQ_SAP_US_DPV_Address_Cleanse_Suggestions

This job processes US records through the URAC (US Regulatory Address Cleanse) transform and non-US records through the GAC (Glo-bal Address Cleanse) transform. If the collection contains multiple records (pending update case), all records must be of US origin to receive URAC DPV processing.

Job Description

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.

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

Page 101: Sap Users Guide En

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.

99

Page 102: Sap Users Guide En

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

Page 103: Sap Users Guide En

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 Description

T501 An abnormal operation occurred during data processing. See the log files for details.

T502 This is the generic duplicate check and error-tolerant search error

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

T504 An incompatible Driver record length was found during duplicate check and error-tolerant search.

T505 An incompatible Candidate record length was found during duplicate check and error-tolerant search.

T506 An incompatible Match code record length was found during duplicate check and error-tolerant search.

T507 The table from SAP for adding the ISO country codes is not specified.

T508 The ISO country code table record length is invalid.

T509 There is not a record in the IE_CH_ADDR table for getting an input address during ADR_VALIDATE or ADR_VALIDATE_QTR call.

T510 The IE_CH_ADDR table for getting an input address is not specified during ADR_VALIDATE or ADR_VALIDATE_QTR call.

101

Page 104: Sap Users Guide En

T511 The EX_PROMPTS table for updating a suggestion prompt is not specified during ADR_VALIDATE call with a suggestion list option enabled.

T512 The EX_PROMPTS table record length is invalid.

T513 The IM_SUGGLIST table that is for adding the suggestion list is not specified during ADR_VALIDATE call with a sug-gestion list option enabled.

T514 The IM_SUGGLIST code table record length is invalid.

T515 The EX_DRIVER table for getting a driver record for match-ing is not specified during GET_MATCH_CODE call.

T516 The EX_DRIVER table record length is invalid.

T517 There is no record in the EX_DRIVER table for getting the driver record for matching.

T518 The IM_MATCH_CODES table for updating the match codes is not specified during GET_MATCH_CODE call.

T520 The IM_FIELD_LIST table for adding the fields for matching is not specified during GET_INDEXED_FIELD_LIST call.

T521 The IM_FIELD_LIST table record length is invalid.

T522 The EX_CANDIDATES table for getting the candidate records for matching is not specified during GET_POTENTIAL_MATCH call.

T524 The IM_MATCHES table for adding the matched records is not specified during GET_POTENTIAL_MATCH call.

T526 The search mode parameter (EX_SEARCH_MODE) passed is invalid (must be I, U, or S).

T527 The address type parameter (EX_CURRENT_ADDR_TYPE) passed is invalid (must be 1 or 2).

T528 The Data Quality process timed out.

T529 Error returned from Data Quality during process.

T550 Invalid function object. Unable to process Gateway request.

T600 Error occurred during ADR_VALIDATE or ADR_VALIDATE_QTR call.

T601 Error occurred when creating input data for the Suggestion List process during ADR_VALIDATE call.

T602 Error occurred when retrieving output data for Suggestion List process during ADR_VALIDATE call.

T604 The batch ADR_VALIDATE_QTR dataflow failed to initialize.

T701 An invalid address type was passed to the GET_INDEXED_FIELD_LIST function.

T702 Invalid parameter values found while processing a GET_INDEXED_FIELD_LIST request.

Technical Error Description

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

Page 105: Sap Users Guide En

T703 Unable to access stored person fields for a GET_INDEXED_FIELD_LIST request.

T704 Unable to access stored organization fields for a GET_INDEXED_FIELD_LIST request.

T705 Unable to access the list of temporary fields in order to create the indexed field list.

T749 An error occurred processing the GET_INDEXED_FIELD_LIST request.

T750 Error occurred during GET_ISO_COUNTRIES call. The sys-tem could not read the file SupportedCountries.txt on the Data Quality Server.

T751 The key file utility could not be found during GET_ISO_COUNTRIES call.

T752 The file SupportedCountries.txt could not be found during GET_ISO_COUNTRIES call.

T753 The file SupportedCountries.txt could not be opened for reading during a GET_ISO_COUNTRIES call.

T802 Invalid parameter values found while processing a GET_POTENTIAL_MATCHES request.

T803 Unable to locate the configuration file potential match setting for the specified table and field.

T804 Invalid response from the Data Quality server.

T805 Unable to access candidate record information.

T806 Unable to communicate with the Data Quality server.

T807 Unable to access driver record information.

T809 The BATCH_MATCH dataflow failed to initialize.

T852 Invalid parameter values found while processing a GET_POTENTIAL_BATCH_MATCHES request.

T853 Unable to locate the configuration file potential batch match setting for the specified table and field.

T854 Invalid response from the DQXI server.

T855 Unable to access candidate record information.

T856 Unable to communicate with the DQXI server.

T898 An error occurred processing the GET_POTENTIAL_MATCHES request.

T899 An error occurred processing the GET_POTENTIAL_MATCHES request.

T900 An error occurred getting the display function modules for the GUI type.

T902 Invalid parameter values found during GET_MATCH_CODES call.

Technical Error Description

103

Page 106: Sap Users Guide En

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:

T903 Undefined application structure.

T904 Unable to access the application structure object.

T905 Unable to access the application structure object field.

T906 GetString method conversion exception on JCO Table.

T907 GetString method name does not exist exception on JCO Table.

T908 Driver record does not exist exception on JCO Table.

T909 Match record exists exception on JCO Table.

T910 Invalid socket table record index or record array not allocated exception.

T911 Insufficient or excess records for the reply tables returned from Data Quality.

T912 Undefined Data Quality response table.

T913 Dataflow error message returned from Data Quality.

T914 Dataflow status message returned from Data Quality.

T915 Unable to access the application input parameter list.

T916 Unable to access the application output parameter list.

T999 An error occurred processing the GET_MATCH_CODES request.

Technical Error Description

Postal Validation Errors

Description

FZ01 There are more suggestions than the max suggestion set in the configuration file.

FZ02 The House number provided is blank.

FZ03 Invalid suggestion number is specified for Street record.

FZ04 The house number provided must be an odd number.

FZ05 The house number provided must be an even number.

FZ06 The PO Box number provided is blank.

FZ07 Invalid suggestion number is specified for PO Box record.

FZ08 The PO Box number provided must be an odd number.

FZ09 The PO Box number provided must be an even number.

FZ10 Invalid primary range is entered.

FZ11 The address is not a valid delivery point.

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

Page 107: Sap Users Guide En

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.

FZ12 The country is not defined.

FZ13 The address is not a valid delivery point.

FZ14 This record locked DPV processing. Consult the Data Quality documentation for the steps required to unlock DPV process-ing.

FZ15 The records primary range is a valid delivery point, but the secondary range is not valid in the DPV directory.

FZ16 The address is a confirmed delivery point, but the parsed sec-ondary range is not available on input.

FZ17 DPV processing is currently unavailable.

FZ18 The secondary unit range provided was invalid.

Postal Validation Errors

Description

Duplicate Check Error

Description

D001 The driver record to be matched is empty or data with all spaces.

105

Page 108: Sap Users Guide En

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

Page 109: Sap Users Guide En

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.

107

Page 110: Sap Users Guide En

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.

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

Page 111: Sap Users Guide En

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:

The following are the Oracle Connection Parameters sample values:

DB2 RDBMS inputs screen

The following are the DB2 Connection Parameters input screen specifications:

The following are the DB2 Connection Parameters sample values:

Text Guidelines

Oracle Tables Owner/Schema Cannot be blank, no default

Oracle TNS Name/Service Cannot be blank, no default

Oracle User Cannot be blank, default to Oracle Tables Owner/Schema

Text Sample value

Oracle Tables Owner/Schema DBUSER

Oracle TNS Name/Service MYDB.BYDBHOST.MYCOMPANY.NET or MYDB

Oracle User DBUSER

Text Guidelines

DB2 Tables Owner/Schema Cannot be blank, no default

DB2 TNS Name Cannot be blank, no default

DB2 User ID Cannot be blank, no default

Text Sample value

DB2 Tables Owner/Schema DBUSER

DB2 TNS Name/Service MYDB

DB2 User ID dbuser

109

Page 112: Sap Users Guide En

MS SQL RDBMS inputs screen

The following are the MS SQL Connection Parameters input screen specifications:

The following are the MS SQL Connection Parameters sample values:

MySQL 5.0 RDBMS inputs screen

The following are the MySQL 5.0 Connection Parameters input screen specifications:

The following are the MySQL 5.0 Connection Parameters sample values:

Text Guidelines

Database Tables Owner Cannot be blank, no default

Database Server Name Cannot be blank, no default

Database Name Cannot be blank, no default

User Name Cannot be blank unless Windows Authorization checkbox is checked

Windows Authentication Default is not checked

Text Sample value

Database Tables Owner DBO

Database Server Name \\myserver

Database Name MYDB

User Name dbuser (or check the Windows Authorization checkbox)

Text Guidelines

Data Source Name (DSN) Cannot be blank, no default

Database Tables Owner Cannot be blank, no default

User Name Cannot be blank, no default

Text Sample value

Data Source Name (DSN) DataServices

Database Tables Owner dataservices

User Name dbuser

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

Page 113: Sap Users Guide En

Sybase ASE RDBMS inputs screen

The following are the Sybase ASE Connection Parameters input screen specifications:

The following are the Sybase ASE Connection Parameters sample values:

Text Guidelines

Database Tables Owner Cannot be blank, no default

Server Hostname Cannot be blank, no default

Database Name Cannot be blank, no default

User Name Cannot be blank, no default

Text Sample value

Database Tables Owner DBUSER

Server Hostname \\myserver

Database Name MYDB

User Name dbuser

111

Page 114: Sap Users Guide En

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

Page 115: Sap Users Guide En

Index

Symbols/FLDQ/AD_PUPDATE table, 56, 93/FLDQ/AD_REPT_DISP_QTRERRORLOG, 43/FLDQ/AD_REPT_DISPLAY_ERRLOG error log, 101/FLDQ/AD_REPT_LOAD_COUNTRIES, 38/FLDQ/AD_REPT_UPDATE_PEND_RECS, 93/FLDQ/AD_VAL_CNT table, 54/FLDQ/RSADRINI, 45/FLDQ/RSADRQU2, 42/FLDQ/RSMTCCODE, 45

AAD_REPT_UPDATE_PEND_RECS program, 93address engine

enable or disable, 24

BBAdIs

installation, 29installation requirements, 17

break keyconfigure, 80definition, 78

Ccheck status

D record, 42combine_house_num_and_pmb option, 98configuring

IMG, 51RFC Server, 67

correction, 10CRM IC WebClient, 46

DD record, 42data quality, 10Data Quality Management for SAP

overview, 9Data Services

documentation, 13installation notes, 19introduction to, 13jobs, 97

dataflows, 70deduplication. See also matchingdialog

suppressing, 55documentation

Data Services, 13duplicate check, 77

definition, 78using, 83

Eerror codes

duplicate check, 105postal validation, 104technical, 101

error log, 101error tolerant search, 77

definition, 78suppressing, 55using, 86

Ffields

address reviewer, 58hit list, 60

FL_GDQC_SERVER, 36, 37flrfcsrv.xml, 96

editing, 68fmt.xml, 70

Ggeocoding, 49

Hhit list, 83, 86

IIMG

configuration, 51IMG activities

Activate duplicate check index pools, 39Maintain exception table of transaction codes, 55Maintain fields for address reviewer, 58Maintain fields for duplicate hit list display, 60Maintain operating parameters, 62Maintain supported countries, 54Maintain table to activate SAP postal code check before

postal validation, 57SAP handshake with RFC Server, 35SAP handshake with RFC server, 53

initial setup program/FLDQ/RSADRINI, 45

installation, 15BAdIs, 29Data Services, 19RFC Server, 26

connection closed, 90troubleshooting, 90

Index 113

Page 116: Sap Users Guide En

JJava

requirements for RFC Server, 16

Llog files

RFC Server, 90

MMaintain exception table of transaction codes, 55Maintain fields for duplicate hit list display, 60Maintain operating parameters, 62Maintain supported countries, 54Maintain table to activate SAP postal code check before postal validation, 57manifest information, 96match

engine, 12matching, 11

name data, 81

Ooperating parameters, 62option

combine_house_num_and_pmb, 98overview

correction, 10data quality, 10matching, 11parsing, 10standardization, 11

PP.O. Box addresses, 58parsing, 10postal validation, 73

engine, 12interactive cleansing, 74quarterly adjustment reports, 41suppressing, 55

Qquarterly adjustment, 41

/FLDQ/RSADRQU2, 42error log, 43

Rregions.xml, 70

understanding regions, 93requirements

BAdIs, 17RFC Server, 16SAP Support Notes, 16

RFC Serverchecking connection, 90configuring, 67console, 96flrfcsrv.xml, 68

overrides, 71installation, 26Java requirements, 16Program ID, 36, 37, 62, 68, 84requirements, 16SAP handshake, 35starting, 27stopping, 28troubleshooting, 96

RSMTCCODE program, 45, 94

SSAP Support Notes

requirements, 16search

suppressing, 55standardization, 11suppress dialog, 55suppress search, 55suppress validation, 55

Ttable

/FLDQ/AD_VAL_CNT, 54transaction

SA38, 38, 42, 43, 45, 93, 101SAINT, 29SMGW, 28, 90SPRO, 35, 39, 52

tsad10.txt, 70

UUnicode, 27

troubleshooting, 90

Vvalidation

suppressing, 55

WWebClient, 46

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