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

(1)

Data Quality Management, version for SAP Solutions XI 3.1 SP2 (12.1.2)

November 2009

SAP

®

BusinessObjects™ Data Quality

Management, version for SAP Solutions

User’s Guide

(2)

Notices

All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in

Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

(3)

Preface

About this guide This guide provides a general overview of SAP BusinessObjects Data Quality Management, version for SAP Solutions as well as specific information for installing and integrating this product into your SAP environment.

Access the latest

documentation In addition to the documentation installed on your computer during installation of this product, you can access all the supported SAP Business Objects documentation from the SAP Business Objects Customer Support site.

1. Go to http://help.sap.com. 2. Select the Business Objects tab.

3. In the SAP Business Objects Overview section, select All Products.

4. On the “Business Objects Product Guides” screen, navigate to the document that you want to view.

You can view the PDFs online or save them to your computer.

Conventions This document follows these conventions: Convention 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.

(10)

Assumed audience This guide assumes that the people responsible for integrating and using Data Quality for SAP are experienced administrators and users of SAP R/3®, SAP ERP Central Component (SAP ECC), and SAP Customer Relationship Management (SAP CRM) solutions. If you are implementing the CRM IC WebClient or CRM WebClient postal validation and search capabilities, this guide also assumes that you are aware of any settings and customizations you have made to your CRM IC WebClient or CRM WebClient configuration before installing this product.

This guide does not explain basic operation of the SAP environment. For questions about the SAP environment, consult the appropriate SAP documentation or SAP technical support.

Product naming

conventions For brevity, SAP BusinessObjects Data Quality Management, version for SAP Solutions is often in this guide called Data Quality for SAP. BusinessObjects Data Services XI Release 3.2 SP01 (12.2.1.1) is often in this guide called Data Services.

(11)

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.

(12)

Data quality overview

What is data quality? Data quality is a process of arranging customer information in a standardized, validated, and consistent order. The process also helps you to avoid duplicate data entries and adds value by creating a single and accurate view of your customers.

What steps are involved in data quality?

Generally, data quality requires these main steps: parsing

correction standardization duplicate matching

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

(13)

Standardization After correcting the data, this product can standardizethe 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, matchingshould 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.

(14)

What is SAP BusinessObjects Data Quality Management,

version for SAP Solutions?

SAP BusinessObjects Data Quality Management, version for SAP Solutions is software that enhances parts of your SAP installation. SAP can stand alone without having this product installed, but without it, you would not attain the benefits of data quality. This product takes care of the correction, standardization, and duplicate matching steps in the data quality process.

Components of this

product This product consists of these components:

BusinessObjects Data Services XI Release 3.2 SP01 (12.2.1.1) – Data Quality Management Premium license, which handles data quality processing tasks on the data it receives from the RFC Server.

Data Services Address Directories, which are downloaded separately from Data Services and installed with Data Services.

Data Services Component, which provides Data Quality Management functionality within Data Services that is specific to this product. The RFC Server, which receives and returns data sent from the SAP environment through TCP/IP.

Three Business Add-Ins (BAdI) that are integrated directly into the SAP environment for postal validation, duplicate check, and error tolerant search.

Postal validation

engine The postal validation engine of this product relies on the Data Services address directories compiled from global postal authorities around the world, such as the United States Post Office, to cleanse addresses from almost any location.

The postal validation engine is integrated into your SAP system through SAP’s Business Address Services

–

Postal Validation (PV) interface.

Match engine The match engine of this product brings sophisticated record-matching

technology to your SAP applications. The criteria for deciding which records are a potential match are controlled by business rules that you can customize to your needs. When you enter a record that is a potential duplicate, you have the option of choosing which of the duplicate records to keep.

The match engine is integrated into your SAP system through SAP’s Business Address Services (BAS)

–

Duplicate Check, Error Tolerant Search (DES) interface.

(15)

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

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.

(16)

(17)

Chapter 2:

Installing Data Quality for SAP

This section explains the requirements and procedures for installing SAP BusinessObjects Data Quality Management, version for SAP Solutions. The installation for Data Quality for SAP includes installing the following components:

SAP BusinessObjects Data Services - Data Quality Management Premium license, including the Data Services Address Directories

Data Quality for SAP Data Services Component Data Quality for SAP RFC server

Data Quality for SAP Business Add-Ins (BAdIs) Support Package The details of these steps vary depending on whether you have the previous version of this product already installed. For details on installation scenarios, see “Installation scenarios” on page 20.

(18)

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. For a list of SAP Notes related to the IC WebClient, see “Requirements for running in a WebClient profile” on page 137.

Requirements for the

RFC Server The RFC Server requires one of the following environments. Supported operating

systems HP-UX 11i v2 (11.23) (Itanium) (64-bit)

IBM AIX 5.2, 5.3, and 6.1 (64-bit)

Red Hat Linux Enterprise Server 4 and 5 (64-bit) Solaris 9 and 10 (64-bit)

SuSE Enterprise Server 9 SP3 and 10 (64-bit) Windows XP (32 bit)

Windows 2003 Server (32 bit)

RFC Server permissions

for Windows 2003 Server In Windows 2003 Server, the user account that runs the RFC Server must have _{full permissions to access the subdirectories that contain the address directories.} Java Runtime

Environment The machine on which you install the RFC Server must run the Java 2 Platform, Standard Edition (J2SE) version 1.6. You must acquire and install the J2SE independently of the installation and before the installation of the RFC Server.

SAP Java Connector The UNIX installation of this product is configured with the assumption that you will use the 64-bit Java runtime. If you instead use the 32-bit Java runtime environment you must use the 2.x, 32-bit version of the SAP Java Connector (JCo) and remove the –d64 option in the RFC Server startup scripts. The 32-bit JCo installer is available at http://service.sap.com.

SAP Note# Description

196958 Collective note: Errors in interface for duplicate check 1142279 BUPA_ADDRESS_CHANGE performs address save twice 1328170 Address assigning directly without providing suggestion list - Data

Quality Management for SAP/Data Services 3.1. Note that versions of Data Services XI 3.1 SP02 and higher already have resolved this issue.

(19)

Requirements for the

BAdIs This version requires that you have the BAdIs from the previous version of this product, Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1), installed. The BAdIs portion of this product upgrades the BAdIs from that version, and cannot be installed without.The BAdIs portion of this product requires one of the following SAP environment:

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

SAP R/3 v4.7, SAP ECC 5.0 (ERP2004), and ECC 6.0 SAP ERP 6.0 Enh Pack 4

SAP Banking Services 6.0

Interactive (real-time) postal address validation, and duplicate check and error-tolerant search are supported within these client user interfaces:

CRM WebClient and CRM IC WebClient: CRM 2007 and greater CRM versions.

SAP GUI and IC Web Client: CRM 5.0

(20)

Installation scenarios

This version is a Support Package upgrade to the previous version of this product, Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1). Your installation scenario depends one whether you have installed that previous version of this product, or whether you intend to install this version as a fresh installation.

Previous version

already installed If you have the previous version of this product already installed, your installation steps require care in properly uninstalling components of that previous version while preserving any customizations you have made so that those customizations can be manually applied to this version.

Upgrade Data Services You must upgrade your version of Data Services to Data Services XI 3.2 SP01, version 12.2.1.1 and install the version-specific Data Services Component portion of this product.

If you have made changes to the Data Services jobs, dataflows, or custom functions in your previous installation, before upgrading export the components to preserve text-file versions and rename the objects within Data Services so that you can compare old versions to the new versions that are installed by the Data Services Component. You can then manually recreate your customizations. See the Data Services documentation for information on preforming an upgrade of Data Services and using the tools that allow you to compare components from your customized versions to the new versions installed with this product.

For further information on installing Data Services and the Data Services Component of this product, see “Install Data Services” on page 22 and “Install the Data Services Component” on page 23.

Install a new version of

the RFC Server This version requires a new version of the RFC Server portion of this product. The RFC Server does not upgrade directly. You must uninstall the previous version and install the new. If you have made configuration changes to your previous version of the RFC Server, you must manually apply them to the new configuration from backup copies of the RFC Server configuration files. For further information on replacing a previous version of the RFC Server and installing this component for this version, see “Install the RFC Server” on page 30.

Install the new BAdIs The BAdIs used for this version are provided as a Support Package that install directly over the previous version of the BAdIs in your SAP system. For further information on applying the BAdIs Support Package, see “Install the BAdIs support package” on page 34.

Fresh installation Though this version is a Support Package upgrade to the previous version of this product, you can install this version without performing a full installation of the previous version. However, in addition to performing the installation tasks described in this chapter, you must also install the BAdI portion of the previous version of this product, and if desirable, activate the IC WebClient using that BAdI.

(21)

Steps in a fresh

installation The installation of Data Quality for SAP requires these tasks, which are detailed later in this section: Outside of your SAP system:

1. Install Data Services and the Address Directories. 2. Install Data Services Component.

3. Install the RFC Server. On your SAP system:

4. Install the BAdIs from the previous version of this product. 5. Install the BAdIs support package from this version.

6. Run the post-installation tasks required of a new installation of the BAdIs. 7. Activate the IC WebClient, if desired.

(22)

Install Data Services

This product relies on Data Services for performing data quality operations. For instructions on installing, configuring, and running Data Services, see the Data Services Installation Guide.

This section contains considerations to help you successfully install Data Services for use with this product.

Data Services install

machine You can install Data Services on the same machine as the RFC Server, on a different machine, or even on a machine with a different operating system than the one that contains your installation of the RFC Server. Information about the system requirements for the machine on which you install Data Services are included with the Data Services documentation.

Data Services previously

installed If you are already a Data Services customer (as a stand-alone product or because you are upgrading from a previous version of this product) and therefore have already installed a version of Data Services, you must upgrade to Data Services XI 3.2 SP01, version 12.2.1.1, which is provided as part of this software package. See the Data Services documentation for details of how to upgrade.

Running new version of

Data Services You can run this product with a version of Data Services higher than XI 3.2 SP01, as long as it is still XI 3.x. (You cannot run this product with a previous version.) See the Data Services documentation for information about updating the Data Services Component items shipped with this release to work with newer versions of the Data Services repository.

Install the Address

Directories For Data Services to perform data quality operations, you must install the Data Services Address Directories. The Address Directories are a separate download from the Data Services installation media. See the Data Services documentation for information on downloading and installing the Address Directories.

Data Services must be

running You must have Data Services running during the remaining installation procedures of this product, and during its operation. Start the Data

Services Address Server service

You must manually start the Data Services Address Server service on the machine that houses Data Services. By default, the Address Server service is set to manual, and does not start with the startup of the computer. For details on manually starting the Address Server service, or setting it to start automatically, see the Data Services documentation.

(23)

Install the Data Services Component

After you install the latest version of Data Services and the Address Directories, you install the Data Services Component that is specific to this product and then perform configuration tasks. The Data Services Component installation

configures network connection information, and then copies a .xml file and imports .atl files specific to the operation of this product into your Data Services configuration. This section describes installing the Data Services Component for both Windows and UNIX/Linux, and then the configuration steps required after the installation.

Data Services

Component Checklist The Data Services Component installation routine asks the following information about your configuration. You should prepare this information before beginning the installation.

Data Services Repository database type

Data Services Repository database connection parameters: user name and password

Database information for the creation of the staging tables Table Owner/Schema

TNS Name/Service User Name

Password

Install the Data Services Component for Windows Data Services configuration

Install the Data Services Component on the machine you installed the Data Services Designer. To install the Data Services Component for a Windows Data Services configuration:

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

2. In the Welcome screen, click Next.

3. If the installation routine cannot detect your version of Data Services, the Confirmation Requested window appears. If the window appears, click Yes to confirm that you have first installed Data Services.

4. Read the license agreement and, if you accept the license agreement terms, choose “I accept the terms of the license agreement” and click Next. 5. In the Choose Destination Locations window, accept the default installation

location or specify a different location. Click Next

! If you have previously installed this version or any past version of this _{product and made customizations to the Data Services job} Job_Realtime_DQ_SAP_Create_Break_Keys, installing the Data Services Component will overwrite the customized version of the file. You should back up or rename the job if you want to keep any customizations. You can then apply the customizations to the new version.

(24)

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.

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 on that Windows machine:

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

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

If you run the install on a machine that does not have the Data Services Designer, you will have to use the Designer later to set the DS_SAP_DS datastore password after importing the .atl files.

(25)

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.

The installation by default copies files to the directory [your_path]/Business Objects\Data Quality Mgmt for SAP Solutions\integration/. Use the files in this location for the remaining steps.

10. If the installation routine is unable to import the .atl files to the Data Services, you must import them manually according to the directions in the Data Services documentation. You must import the .atl files in the following order:

SAP_DS_STG_TBL.atl DQ_SAP_DS.atl

DQ_SAP_DS_SYS_CFG.atl DQ_SAP_DS_SUB_PARAM.atl

11. Copy the file SupportedCountriesList.xml to the /bin directory of the Data Services configuration on the UNIX/Linux server.

The Data Services Component is now installed to your Data Services system, but you must perform post-installation steps following in this section to configure Data Services.

Use global variables

to disable engines You must disable the address cleanse engines for countries for which you did not purchase the address directory. See the Data Services documentation for information on which countries’ address data is supported by which engine. The table below lists the country engine substitution parameters.

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

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

(26)

To disable address cleanse engines:

1. In the Data Services Designer, go to Tools > Substitution Parameter Configurations.

2. In the Substitution Parameter Editor, select one of the country engine substitution variables from the list that represents a country address cleanse engine that you did not purchase.

3. Set the parameter to NO to disable the engine for every address cleanse engine represented by a Data Services address directory that you have not purchased. You must perform this step for every configuration you use. If you did not purchase an address cleanse address directory, and the

corresponding value is set to YES or is blank, this product cannot function properly.

4. After you have set the appropriate value for all the Substitution Parameters, click OK.

Create the batch

RDBMS staging tables Next, you create batch processing staging tables, which this product uses in the transfer or data to and from Data Services.

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.

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

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

(27)

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

Configure jobs as

services When you install the Data Services Component, a group of Data Services jobs are copied to your Data Services installation. You must configure these jobs (.atl files) as services.

Sample input files Before configuring jobs as services, you may want to run the sample input files to test Data Services jobs. Though running the sample input files is not required as part of installation, the installation is now at a point in which the files can be run. For information on verifying the Data Quality jobs, see “Using the sample input files to test Jobs” on page 88. The remaining information in this section is required as part of the installation of this product.

List of jobs and their

service names Configure jobs as services for all of the jobs listed in the table by following the steps in “To configure jobs as services” on page 27.

To configure jobs as

services You must perform this procedure for each job listed in the preceding table.

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 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_With_Firstname Service_Realtime_DQ_SAP_Create_ Break_Keys_With_Firstname 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

Before configuring jobs as services, you must have configured a Data Services repository as part of the installation of Data Services. If you have not configured a repository, see the Data Services documentation for instructions.

(28)

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 Time Services from the file tree on the left and open the Real-Time Service Configuration tab on the right.

5. Click Add.

6. In the Service Configuration window click Browse Jobs.

7. Select a job name (listed in the preceding table). For example, select Job_Batch_DQ_SAP_Address_Cleanse. If the Management Console is connected to more than one repository, make sure you select the dataflows from the repository that contains the jobs imported in the previous steps. 8. Enter the service name for the job. For example, enter

Service_Batch_DQ_SAP_Address_Cleanse (exact case is required). 9. For most services, enter 800 for the Processing Timeout value and click

Apply. For the service

Service_Realtime_Batch_DQ_SAP_Name_And_Address_Match, enter a very large number (such as 2147483647) to prevent a very large batch match job from timing out during processing.

10. Under Service Provider, click Add and include the correct JobServer to run this service.

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

Enable or disable an

address engine If necessary (for example, to disable the engine responsible for running addresses for a country you did not purchase), you can enable or disable an address engine for a particular service in the Data Services Management Console.

1. In the Real-Time Service Configuration tab, the Add dialog, click Add Overridden Parameter

2. Select the override parameter for the engine that you want to enable or disable. For example, to enable or disable the Canada engine, select $$DQ_SAP_EngineCanada.

3. Type Yes to enable or No to disable the engine.

Changes to parameters cannot take effect until the services that uses the parameters are restarted. Therefore, you must restart the job for this change to take effect.

To configure Web Services You must next configure Web Services. To configure Web Services:

1. Keep the Data Services Management Console open from the previous steps, or open and login to the Data Services Management Console and click Administrator.

(29)

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.

If you configure Web Services for any features you did not purchase, such as geocoding or DPV, those Web Services will fail.

(30)

Install the RFC Server

After you install and configure Data Services, and install the Data Services Component, you install the RFC Server. Each installation of the RFC Server installs one instance for transactional processing and one instance for batch processing.

Installing the RFC Server as a Windows Service

During the installation of the RFC Server on Windows, the installation routine allows you to install the RFC Server as a Windows Service. The RFC Server functions the same whether you install it as a Windows Service or not, but installing the RFC Server as a Windows Service allows you to administer it through the Services console.

The first instance of the RFC Server has the Service name BusinessObjects DQM for SAP xxx 1 (where xxx is the System ID). Other instances of the RFC Server are named BusinessObjects DQM for SAP xxx 2, BusinessObjects DQM for SAP xxx 3, and so on. A dedicated RFC Server for batch duplicate search has the service name BusinessObjects DQM for SAP Batch xxx.

If you chose not to install the RFC Server as a Windows Service but want to add this functionality, you must run the installer again and select the additional Windows Services option.

Replacing a previous

RFC Server version You cannot install this version of the RFC Server over a previous version. If you intend to use a machine that has the RFC Server from a previous version of this product, you must uninstall the previous version. On Windows, run the

installation routine from the previous version of this product on a machine that holds the RFC Server. The installation routine gives the option to uninstall the instance of the RFC Server it finds. On UNIX/Linux, simply delete the files of the RFC Server to uninstall.

If you are upgrading from a previous version of this product and made

customizations to the RFC Server settings, before uninstalling you should make copies of the previous version’s files flrfcsrv.xml and regions.xml to use as a reference to those customizations. You must manually apply any customizations to this version of the product to reproduce those changes from the default settings. For information on the location and settings of these files, see “Configuring the RFC Server” on page 61.

RFC Server Checklist The RFC Server installation routine asks the following information about your configuration. You should prepare this information before beginning the installation.

The three-letter System ID of your SAP system Gateway Host of your SAP system

Gateway Service Name of your SAP system

Basis version of your SAP system, and whether it is a Unicode system You must install the RFC Server from a user account that has permissions to install software on the machine, and you can only have one instance of an RFC Server dedicated to batch processing active on a single gateway.

(31)

Data Services Host Name (chosen when you install Data Services for this product)

Data Services Port Number (chosen when you install Data Services for this product)

URL for Data Services Web Services (chosen when you install Data Services for this product)

The email Host of your email system, a sender email address, and recipient email address (in comma-delimited format), used by the RFC Server to send email notifications if it terminates

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

To install the RFC Server:

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

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 SAP System ID, Host Name, and Service of the SAP Gateway.

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

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.

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.

The SAP System ID is a maximum of three characters in length. For the Host Name, you can use either the name or IP address of the SAP central instance gateway. The Service of the SAP Gateway is typically

(32)

8. In the SAP Basis window, select the version of your SAP Basis system. (The installer uses different files depending on your Basis version.) Click Next. 9. In the Data Services Connection window, enter the Data Services Access

Server hostname and port number (default is 4000), and the URL of the Data Services Web server (default is http://<hostname>:28080/DataServices/ servlet/webservices?ver=2.0&wsdlxml). Click Next.

10. In the Email Server Connection Parameters window, provide the following information:

Email host. If you leave this field blank, the RFC Server does not send email notifications if the RFC Server terminates or the SAP gateway disconnects.

Email Port. The default email port is 25. Sender Email Address.

Recipient Email Addresses. Each of the recipient email addresses must be separated by a comma.

Click Next.

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

Start the RFC Server If you installed the RFC Server on Windows as a Windows Service, you can start the RFC Server as you would any Windows Service. The name of the Service for the first instance of the RFC Server, for example, is BusinessObjects DQM for SAP xxx 1 (where xxx is the System ID). You must start all instances of the RFC Server, interactive and batch, in this manner.

You can also use the configuration features available for any Service, such as the ability to automatically restart the Service after failure. For details on configuring Windows Services, see your Windows documentation.

If you did not install the RFC Server as a Windows Service, you can find the batch files to start the RFC Server in the install directory of the machine on which you installed the RFC Server.

If your system is Unicode compliant, the step “Run the initialization program” on page 42 has further configuration instructions on configuring Data Quality for SAP for Unicode systems.

The email transport protocol is SMTP. The installation routine does not validate the email addresses you provide. You can change these parameters later in the RFC Server configuration file. For more information, see “Configuring through flrfcsrv.xml” on page 62.

If you run the installer again on a system that already has the RFC Server installed, the installation routine detects the previous installation and offers steps to create additional Windows Services (for Windows only), configure a new SAP system, or uninstall. When you uninstall the RFC Server on Windows, the routine uninstalls all RFC Servers on the system.

(33)

For Windows:

install_directory\start_<systemID>_trans.bat

install_directory\start_<systemID>_batch.bat For UNIX/Linux:

install_directory/start_<systemID>_trans

install_directory/start_<systemID>_bat

Where <systemID> represents the SAP System ID specified at installation.

Stop the RFC Server If you installed the RFC Server on Windows as a Windows Service, you can stop the RFC Server as you would any Windows Service.

If you did not install the RFC Server as a Windows Service, you must on the machine that hosts the RFC server use Ctrl-C in the RFC Server console to terminate the RFC Server process. Note that this method may on rare occasion cause SAP to show a connection to the RFC Server after the RFC Server has stopped.

When the RFC Server starts, it looks for the SAP Gateway and your installation of Data Services. Therefore, you should have both the SAP Gateway and Data Services running before starting the RFC Server. Additionally, the RFC Server looks for the Java Runtime Environment. Therefore, the Java runtime must be installed relative to where the RFC Server startup script runs, or you must set the JAVA_HOME environment variable to where Java is installed so that the RFC Server can find it.

If you use transaction SMGW from within your SAP system in an attempt to stop the RFC Server, the RFC Server restarts and reconnects. Also, if you are running multiple RFC Servers with the same TP name, this method may simultaneously stop all RFC Servers with that TP name (for more

information, see SAP Note 923248). Further, if you use transaction SMGW to stop the RFC Server that has been installed as a Windows Service, and the RFC Server fails to restart properly, the Windows Services Console would not reflect that the RFC Server is not running until the Console is refreshed.

(34)

Install the BAdIs support package

Before you proceed with these steps, make sure that your SAP system complies with all of the prerequisites described in “System requirements” on page 18. This version requires that you have the BAdIs from the previous version of this product, Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1), installed. The BAdIs portion of this product upgrades the BAdIs from that version, and cannot be installed without.

To install the BAdIs on your system, you must complete these tasks:

“Step 1: Import the Data Quality Management support package on client 000” on page 34

“Step 2: Re-activate the Business Configuration Sets on each target client” on page 36

Step 1: Import the Data Quality

Management support package on client 000

You must have the previous version of this product, SAP BusinessObjects Data Quality Management, version for SAP Solutions XI 3.1 SP1 (12.1.1) installed, using the full installation instructions of the User’s Guide for that version.This release upgrades that previous version.

You must have the latest Support Package Manager (SPAM) update/patch installed on your SAP system. (For more information, see SAP Note 822379.) Choose an applicable .SAR package for your Basis version from the tables below, import the Data Quality Management package on the reference client (client 000), and then activate (or reactivate) BC Set /FLDQ/47U6X to import new

customizing data.

! If you are doing a fresh installation of this product, you must install the _{BAdIs portion of the previous version of this product, according to the} instruction found in “BAdI-only for fresh installation” on page 123, before proceeding with the installation of this BAdIs support package.

Because of the variety of SAP versions, the illustrations that we use throughout these procedures may differ from what you encounter while installing BAdIs on your specific version of SAP Solution. We assume that you have knowledge of SAP administration to help you successfully navigate through the installation. Even though the screens may differ from version to version, follow all steps in these processes.

The BAdIs support package is installed using the support pack manager SPAM.

Basis 6.20

SAR file Application Server

\6.20\DATA\SAPK-40A1HINFLDQ.SAR all

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

(35)

Importing the Data Quality Management package

To import the Data Quality for SAP Support package:

1. Enter the transaction SPAM to open the Support Package Manager window. 2. Click the Support Package menu and choose Load packages > From

Frontend. Basis 6.40

SAR file Application Server

\6.40\DATA\SAPK-40A1HINFLDQ.SAR all

Basis 7.00

\7.00\DATA\CRM50\SAPK-40B1HINFLDQ.SAR CRM 5.0 \7.00\DATA\CRM2007\SAPK-40B1HINFLDQ.SAR and \7.00\DATA\CRM2007\SAPK-40B2HINFLDQ.SAR CRM 2007 \7.00\DATA\ECC6\SAPK-40A1HINFLDQ.SAR ECC 6

Basis 7.00 users must have the SPAM 21 update/patch or greater to be able to load a .SAR package. (For more information, see SAP Note 822379.) Also, you must (re)activate BC Set /FLDQ/47U6X (and BSP BC Set /FLDQ/ BSP_PV, if applicable) to import new customizing data.

Basis 7.01

\7.01\DATA\CRM7\SAPK-40A1HINFLDQ.SAR CRM 7.0 \7.01\DATA\ERP6 EP4\SAPK-40A1HINFLDQ.SAR ERP 6 EP4

You must (re)activate BC Set (and BSP BC Set, if applicable) /FLDQ/47U6X to import new customizing data.

Also, you must (re)activate BC Set /FLDQ/47U6X (and BSP BC Set /FLDQ/ BSP_PV, if applicable) to import new customizing data.

Basis 7.10

SAR file Application Server

\7.10\DATA\SAPK-40A1HINFLDQ.SAR FSBP

(36)

3. In the Select CAR/SAR archive window, browse to the \DATAdirectory of the Data Quality for SAP SAP – PV and DES BAdIs installation media, and select the applicable .SAR file. If the path is long and the system generates an error, copy the file to a local directory location and load it from there. 4. Click Open and then click Yes to load the .SAR file. The contents of the

compressed .SAR file appears.

5. Click Decompress.

6. Continue with standard Support Package process for component /FLDQ/. (For further instructions on importing a Support Package, see the

documentation for your SPAM tool.) 7. Click Cancel to close the tool

Step 2: Re-activate the Business

Configuration Sets on each target client

Re-activate the Business Configuration Sets on each of the target clients (non-000 logon clients) that you want to configure for use with Data Quality for SAP. Repeat these steps for each target client that you want to configure for use with Data Quality for SAP.

1. From one of the target clients, use /nSCPR20 to navigate to the Business Configuration Sets : Activation transaction.

2. Type /FLDQ/47U6X in the BC Set input field and click Enter. The following Short text appears: Business Configuration Set for BusinessObjects 06-21-09. (The date varies.)

3. Click the Activate button or select Activate from the BC Set menu. 4. Create a new change request. (Click OK if a caution appears.)

5. In the Activation Options window click Continue Activation (Enter). An Activation completed message appears at the bottom of the window.

For IC WebClient,

re-activate the BSP BC Sets If you use the IC WebClient, you must also re-activate the BSP BC sets. To re-activate the BSP Business Configuration Sets, open the target client (the one that you want to configure for use with the Data Quality for SAP) and follow these steps:

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

(37)

1. Enter transaction /nSCPR20 in the target client to navigate to the Business Configuration Sets : Activate transaction.

2. Type /FLDQ/BSP_PV in the BC set input field and click Enter.

The following Short text appears: BC Set for BusinessObjects BSP_PV Product 07/08/09. (The date varies.)

3. Click Activate.

4. Create a new change request when the window appears. (Dismiss any caution that may appear.)

5. Click Continue Activation (Enter) in the Activation Options window. An Activation completed message appears at the bottom of the window. 6. Repeat these steps for each target client that you want to configure for use

(38)

Quarterly Adjustment Reports

SAP provides standard reports for Quarterly Adjustments, which allow you to validate all the addresses in your database in a three-step batch process. You may want to run Quarterly Adjustments other times after this installation on a regular, pre-determined schedule and you should run Quarterly Adjustments after installing new Data Services address directories from SAP Business Objects to validate data that may have changed due to the renaming of streets, the

development of new areas, and so on.

If you did not have Data Quality for SAP installed, to run a Quarterly Adjustment Report you would execute the defined SAP reports RSADRQU1, RSADRQU2, and RSADRQU3. Installing Data Quality for SAP allows you to substitute the second of these standard reports, RSADRQU2, with the custom report /FLDQ/ RSADRQU2, and take advantage of the postal validation capabilities provided by Data Quality for SAP.

The running of these reports exchanges records between SAP and the RFC Server. Then the validated and updated addresses are committed to the SAP database.

Report RSADRQU1 You use report RSADRQU1 to select the addresses that are to be cleansed. To run the report:

1. On a target (non-000) client, start the report RSADRQU1 by running the transaction code SA38.

The “ABAP Execute Program” window appears.

2. In the Program field, enter RSADRQU1 and click the Execute button (F8). The “Create an address index for the quarterly adjustment” window appears, presenting several options.

3. Specify the countries for which the quarterly adjustment is to be performed. This field is required by default.

4. Specify the cities within the selected country or countries for which the quarterly adjustment is to be performed. This field is optional.

5. Specify the postal code or range of postal codes for which the Quarterly Adjustment is to be performed. This field is optional.

6. Change the packet size only if you have experienced problems in running Quarterly Adjustment Reports previously.

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.

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.

(39)

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.

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.

A D record is a record that has its check status set to D. There are three possible check status values.

C = Postal or address data is known and does not contain any errors D = Postal or address data may have errors

“ ” = Postal Validation has not been run

If a record has a check status set to D, the address in that record has previously been checked and the user selected to save the address without cleansing it. Records with a check status of D may contain faulty address data as a result. When running report

/FLDQ/RSADRQU2, you may want to skip D records because a user has already made the decision to save the address without cleansing it.

(40)

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.

(41)

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 reco

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

Data Quality Management, version for SAP Solutions XI 3.1 SP2 (12.1.2)

Contents

Preface ... 9

Chapter 2: Installing Data Quality for SAP ... 17

Chapter 3: Configuring through the IMG ... 45

Chapter 4:

Chapter 5: Postal address validation ... 69

Chapter 7: Tips and troubleshooting ... 85

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

Appendix D: Databases for staging tables... 107

Appendix F:

Preface

Access the latest

Product naming

Chapter 1:

What steps are involved in data quality?

The results of data

What is SAP BusinessObjects Data Quality Management,

Components of this

Postal validation

Introduction to SAP BusinessObjects Data Services

Hub of data quality

Access Data Services documentation on Windows

Chapter 2:

System requirements

Required SAP Support

SAP Note# Description

Installation scenarios

Previous version

Install Data Services

Data Services install

Install the Address

Install the Data Services Component

Data Services

Install the Data Services Component for Windows Data Services configuration

Install the Data Services Component for UNIX/Linux Data Services configuration

SAP_DS_STG_TBL.atl DQ_SAP_DS.atl

Create the batch

Substitution parameter Description

Configure jobs as

Job Service name

Install the RFC Server

Installing the RFC Server as a Windows Service

install_directory\start_<systemID>_trans.bat

Install the BAdIs support package

Step 1: Import the Data Quality

Basis 6.20

SAR file Application Server

Basis 7.01

SAR file Application Server

Step 2: Re-activate the Business

Quarterly Adjustment Reports

Report

Quarterly Adjustment