User Guide for connecting to SAP Data Services · User Guide for connecting to SAP Data Services...

CUSTOMER

SAP Data Quality Management, version for SAP SolutionsDocument Version: 4.0 SP09 – 2017-09-26

User Guide for connecting to SAP Data ServicesConnecting to Data Services

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3 Required SAP Notes for Your System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.1 Downloading Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.2 Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.3 Installing Data Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Installing the Data Services Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Using the Sample Input Files to Test Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Configuring Jobs as Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Configuring Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Starting the Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

3.4 Installing the Add-Ons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Installing Packages for a New DQM for SAP Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Installing Support Packages for DQM for SAP Add-On FLDQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Applying SAP Notes After Installing SP 09. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.5 RFC Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Preparing to Install the RFC Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Assigning SAP Authorizations to the RFC User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Number of RFC Servers to Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Installing an RFC Server as a Windows Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Replacing a Previous RFC Server Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Installing the RFC Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Starting and Stopping the RFC Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Configuring the RFC Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4 Required Post-Installation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.1 Activating Business Configuration Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.2 Setting up Data Quality Management IMG Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Linking to SAP Reference IMG Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Locating the IMG Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44IMG: SAP Handshake With RFC Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44IMG: Activate Base BC Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47IMG: Activate Client Specific BC Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

2 C U S T O M E RUser Guide for connecting to SAP Data Services

Content

4.3 Prepare for Matching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5 Optional Post-Installation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.1 Optional IMG Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

IMG: Maintain Settings to Switch off the Address Reviewer Screen. . . . . . . . . . . . . . . . . . . . . . . . . 49IMG: Maintain Settings for Address Validation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50IMG: Maintain Supported Countries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50IMG: Maintain Exception Table of Transaction Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51IMG: Activate SAP Postcode Check Before PV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52IMG: Maintain Operating Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52IMG: Maintain Fields for Address Reviewers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55IMG: Maintain Fields for Duplicate Hit List Displays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56IMG: Map Objects for Quarterly Error Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57IMG: Activate/Deactivate Postal Validation Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59IMG: Activate/Deactivate DES Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59IMG: Activate/Deactivate Creation of Match Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60IMG: Activate/Deactivate Standardization Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60IMG: Identify Search Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60IMG: Maintain DQM Region Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60IMG: Maintain Customer Address Reviewer Labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62IMG: Maintain Suggestion List Labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62IMG: Maintain Suggestion List Fields to Display and Order to Display. . . . . . . . . . . . . . . . . . . . . . . . 63IMG: Maintain Customer-Defined Standardization Reviewer Labels. . . . . . . . . . . . . . . . . . . . . . . . . 63IMG: Maintain Standardization Reviewer Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

5.2 Other Optional Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Installing and Configuring Into WebClient for CRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Configuring Geocoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Configuring Name and Organization Cleansing for MDG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Configuring Address Output Field Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Adding the PO Box Lobby Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Configuring the Use of Multiple Back-End Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

6 Postal Address Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.1 Interactive Address Cleansing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.2 Batch Address Cleansing With Quarterly Adjustment Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Report RSADRQU1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Report /FLDQ/RSADRQU2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Report RSADRQU3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Batch Address Cleansing Reviewer (/FLDQ/RSADRRVW). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Quarterly Adjustment Custom Error Report (/FLDQ/AD_REPT_DISP_QTRERRORLOG). . . . . . . . . . .78

7 Duplicate Checking and Error-Tolerant Searching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

User Guide for connecting to SAP Data ServicesContent C U S T O M E R 3

7.1 Break Keys (Match Codes). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Changing the Break Keys (Match Codes). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Configuring Break Key Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Matching on Name Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7.2 Duplicate Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Interactive Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Batch Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7.3 Error-Tolerant Searching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917.4 Duplicate checking with SAP MDG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Setting the BAS-DES Duplicate Check for MDG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Preparing Data Services to Work With MDG for Generic Duplicate Check. . . . . . . . . . . . . . . . . . . . . 92

7.5 Matching on Birthdate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Populating Birthdate Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

8 Person and Organization Name Cleansing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008.1 Interactive Name Cleansing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008.2 Batch Name Cleansing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Build Results Report (/FLDQ/NC_BUILD_RESULTS ). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Review Commit Results Report (/FLDQ/NC_REVIEW_COMMIT_RESULTS). . . . . . . . . . . . . . . . . . 102

A Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104A.1 Installation Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104A.2 Postal Validation Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105A.3 Duplicate Check and Error-Tolerant Search Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107A.4 Region Code Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108A.5 RFC Server Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111A.6 Real-time Job Time-Out Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114A.7 Product Component Version Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115A.8 Customizing an Error Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115A.9 Diagnosing Problems That Cause Data Quality Processing to Cease. . . . . . . . . . . . . . . . . . . . . . . . . . 115A.10 Person and Organization Name Cleanse Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116A.11 Enabling postal validation in MDG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

B External List Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118B.1 External List Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Using This Product With ELM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Matching on the Marketing Attributes Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

C Break Key Profiler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122C.1 Break Key Profiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Installing the Break Key Profiler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Running the Break Key Profiler Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Performance of the Break Key Profiler Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125


Content

Interpreting the Break Key Profiler Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Creating Custom Match Codes (Break Keys). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

D Data Quality Administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131D.1 Using Data Quality Administration With This Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

E Staging Table Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132E.1 Data Services Component Installation: Staging Table Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132

User Guide for connecting to SAP Data ServicesContent C U S T O M E R 5

1 Introduction

About This Product

SAP Data Quality Management version for SAP Solutions (DQM for SAP) provides a prepackaged native integration of data quality best practices within the SAP Customer Relationship Management (SAP CRM), SAP Enterprise Resource Planning (SAP ERP), and SAP Master Data Governance (SAP MDG) environments.

When you enter a new customer, supplier, or partner record using SAP ERP, SAP CRM, or SAP MDG , DQM for SAP software corrects and/or validates the address based on referential data sources, and formats the address according to norms of the applicable country. DQM for SAP also helps prevent duplicate entities entering your SAP ERP, CRM, and MDG applications, and helps search and improve your existing data.

About This Guide

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

This guide assumes that people responsible for installing and configuring this product are experienced administrators and users of the SAP platform on which you are integrating it. If you are implementing the CRM IC WebClient or CRM WebClient postal validation and search capabilities, this guide assumes that you are aware of customizations made to the CRM IC WebClient or CRM WebClient configuration before installing this product.

This guide does not explain basic operation of the SAP environment or Data Services. See the appropriate SAP documentation or SAP Business User Support, or Data Services documentation.

SAP Information Resources

A global network of SAP technology experts provides customer support, education, and consulting to ensure maximum information management benefit to your business.

Table 1:

Resource Details

Customer Support, Consulting, and Education

Information about SAP Business User Support programs, and links to technical articles, downloads, and online forums. Consulting services provide information about how SAP can help maximize your information management investment. Education services provide information about training options and modules. From traditional classroom learning to targeted e-learning seminars, SAP can offer a training package to suit your learning needs and preferred learning style.

Documentation Documentation describing the software installation, functionality, and so on.


Introduction

http://help.sap.com/disclaimer?site=http://service.sap.com



http://help.sap.com/dqmsap

2 Before You Install

Before you install this product, there are several important topics that you need to be aware of:

● Security● System requirements● Required SAP Notes

2.1 Security

To best protect your data, follow these security recommendations and best practices.

Data Services Security Settings

You can configure the following security settings in Data Services:

● Access Server SSL communication● Web Service SSL communication● Session security

When you install the RFC Server, you are asked if you enabled these settings.

Unless you require encryption and session security, we recommend that you do not enable these options in your Data Services configuration. A preferred network security strategy is to have your Data Services installation and RFC Server behind a firewall.

Data Protection and Privacy

Data security requirements differ among organizations based on government or corporate policies and other factors.

This product has access only to firm/customer name and address information. It does not process or archive any associated financial or Social Security and Insurance Numbers identifiers. You may choose not to encrypt data transfers between the RFC Server and Data Services components for either of the following scenarios:

● Installation of the RFC Server and Data Services are on the same physical computer, meaning data moved between these two components does not move across a network

● The installation of this product is behind a secure firewall and you have no concerns with name and address information flowing unencrypted across the local network

User Guide for connecting to SAP Data ServicesBefore You Install C U S T O M E R 7

Security Information Specific to the RFC Server

Keep in mind the following security-related attributes of the RFC Server that are installed with this product.

● The RFC Server connects to the SAP Application Server to obtain table metadata (such as table structure definition). This connection requires that a connection user account be created on the SAP system. The RFC Server installation routine prompts the user for this password and encrypts it in the flrfcsrv.xml configuration file. A key file is also generated and written to the RFC Server configuration folder. Access to the RFC Server installation folder and its contents should be restricted by the operating system.

● The RFC Server should be behind a firewall to prevent unwanted remote access.● On Windows, the RFC Server can be executed as a Windows service. Windows services can be started/

stopped by anyone who has access to the system.● The RFC Server can be manually configured to log data as it flows between the system components. This

capability potentially exposes name and address information. This functionality is useful in troubleshooting problems related to data.

● The RFC Server does not implement roles or responsibility concepts. The RFC Server functions as a thin application transforming data formats between the SAP and Data Services systems.

● Configuration of the RFC Server is via the flrfcsrv.xml configuration file. Therefore, any user that can modify this configuration file can affect the behavior of this product. If your operating system supports file journaling, you can enable this capability and allow it to track any changes to flrfcsrv.xml.

Authorizations

To protect data in the system, this product offers the ability to assign authorization groups to Business Partners and Customers to prevent unauthorized users from viewing unauthorized duplicate records.

Authorizations for the components of this product are handled as follows.

Table 2:

Component Authorizations

RFC Server Authorizations and roles are configured by the operating system user access. The RFC Server does not implement an authorization or roles concept.

Data Services Components Authorizations and role administration are configured by the Data Services administration tools.

ABAP Component Authorizations and role administration are configured by the SAP platform's administration tools.

Logging

Security logging for the components of this product are handled as follows.


Before You Install

Table 3:

Component Authorizations

RFC Server The logging of security related events (for example, an invalid password) is performed in the SAP configuration ID log file. The RFC server does not provide the capability to analyze security related events.

Data Services Components Logging security-related events is configured by the Data Services administration tools.

ABAP Components Logging security-related events is configured by the SAP platform's administration tools.

Communication Interfaces

Data is transferred between components of this product using different communication interfaces. The following table shows the method or limitation of these communication interfaces.

Table 4:

Components Communication Interface

RFC Server and SAP gateway / Application Server (provided by packages installed with this product)

Uses the SAP Java Connectivity 3.0 (SAPJCO3) library. The data transmitted over this interface is not encrypted.

RFC Server and Data Services Uses these methods:

● RFC Server and SAP gateway / Application Server (provided byWeb service calls at startup from the RFC server to Data Services to obtain job schema information, such as the field names

● Realtime interface calls over a temporary socket to send data to be processed or to retrieve product version/job name information from the Data Services system

Network Setup

The following table shows options for a network setup between components of this product.

Table 5:

Components Communication Interface

RFC Server and SAP gateway / Application Server (provided by the package installed with this product)

Because data between these components cannot be encrypted, this communication channel should be placed behind a firewall.

RFC Server and Data Services Encryption can be configured during the installation of the RFC Server.


Network Ports

The following table identifies and describes the network ports used for communication between components of this product.

Table 6:

Components Description Port

RFC Server and SAP gateway / Application Server (provided by the packages installed with this product)

The port number uses the last two digits of the SAP gateway number to create the port number 33<xx>.

For example, the RFC Server uses port 3352 to communicate with sapgw52 (both end with 52).

RFC Server and Data Services via Web Services

This setting applies only for communication using Data Services Web Services.

Port 8080/8443.

RFC Server and Data Services via the real-time interface

This port must match the Data Services installed port number. If you did not accept the default, you must change the port number.

Port 4000, by default.

Data Storage

Data handled by this product is stored on the SAP platform in the SAP database /fldq/ namespace tables, included in the packages installed with this product.

Data is saved, accessed, or updated when the BAS interface invokes the functionality of this product or when one of the reports provided with this product is executed.

Related Information

Installing the RFC Server [page 33]Configuring the RFC Server [page 38]

2.2 System Requirements

Ensure that your landscape meets the following requirements before you begin installing this product.

You can run all of your Data Services and RFC server applications on a single computer or you can run it on multiple systems. This decision can be based off your customer’s daily transactional load, your time requirement to complete batch reports (INIBM, QU2, or Name Cleanse), and your available hardware. If the customer's daily transactional load is high for only a portion of the day (say 8AM to 8PM Monday through Friday) you may be able to use a single computer to handle transactional requests during this time and then execute your batch reports in the evening hours or weekends when the transactional load is greatly reduced. If you have a 24/7 hour transactional load or are unable to complete the background reports during a lull in transactional requests, then


Before You Install

you should have a second computer that can handle the batch reports and will not adversely affect your transactional load.

Requirements for the Data Services 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. However, installing Data Services and the RFC Server on the same machine reduces network traffic, slightly increases performance, and reduces the number of ports that must be exposed and enabled.

Using Data Services as part of this product requires greater system requirements for the machine than the minimums described in the Data Services documentation.

For this product:

● The machine must have a minimum of 8 CPU cores.● In addition to the RAM required for all the other software running—the operating system, Data Services (used

with this product or stand-alone), Information platform services, databases, database servers, and so on—the machine must have additional RAM free, depending on which jobs you want to run and the operating system.

● Data Services version 4.2 SP4. See Installing Data Services [page 16].

Operating System and Memory Requirements for the RFC Server

The RFC Server requires one of the following 64-bit operating systems.

● IBM AIX 6.1 TL5 and 7.1 TL2 SP1● Red Hat Linux Enterprise Server 5 Update 3, 6.5 and 7● Solaris 10 and 11 SPARC● SuSE Enterprise Server 11 SP3 x86_64● Windows Server 2008 SP2 x64● Windows Server 2008 R2 SP1 x64● Windows Server 2012 x64● Windows Server 2012 R2 x64

Each running RFC Server instance requires 200MB of RAM to execute. Running batch match code requires a minimum of three RFC Servers for transactional and three RFC Servers for batch.

Requirements for the ABAP Add-On

The ABAP Add-On portion of this product supports the following environments:

● SAP Customer Relationship Management (SAP CRM) solutions 2007 and 7.0 and higher● ECC 6.0● SAP ERP 6.0 Enh Pack 4 or greater


● SAP Banking Services 6.0● SAP Master Data Governance – Supplier – Add-on to ERP 6 Enh Pack 5 (Postal Validation only)● SAP Master Data Governance – Add-on to ERP 6 Enh Pack 6 (Supports Postal Validation for Supplier Data

Model and Matching for all data models)

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

● SAP CRM WebClient and CRM IC WebClient: CRM 2007 and higher CRM versions● SAP GUI only: ECC 6● SAP Master Data Governance – Supplier: ERP 6 Enh Pack 5 (Postal Validation only)● SAP Master Data Governance: ERP 6 Enh Pack 6 and Higher (Supports Postal Validation for Supplier Data

Model and Matching for all data models)

Related Information

Configuring Jobs as Services [page 20]

2.3 Required SAP Notes for Your System

Follow the instructions in the following SAP Notes as appropriate for your SAP system. Review other SAP Notes for content related to Data Quality Management applicable to your SAP platform.

Table 7:

SAP Note Description

196958 Collective note: Errors in interface for duplicate check.

1091535 During batch input in foreground pop ups will not occur.

1472502 Long time processing when executing CUSTOMER_GET_INDEX_EXCEPTIONS. This helps resolve a performance issue in the SAP function ADDR_EXTRACT_FOR_DUPL_INDEX, resulting in faster batch match processing.

1512042 Performance improvements on ADDR_EXTRACT_FOR_DUPL_INDEX. This helps resolve a performance issue in the SAP function ADDR_EXTRACT_FOR_DUPL_INDEX, resulting in faster batch match processing.

1677509 Running the report SIC_BAS_RSADRINI to index already existing Business Partners to begin work with checking duplicates, the report runs an endless loop and/or times out.

2024181 Index overwriting is incorrectly handled in RSADRQU1.

1276016 Improper informational message is shown.

2158324 Cleanse data before saving to master tables.


Before You Install

3 Installation

This chapter explains the steps required to install SAP Data Quality Management, version for SAP Solutions.

3.1 Downloading SoftwareInstallation for this product includes several components, which you can download from SAP Software Download Center or SAP Solution Manager.

Download Attribute Change Package First

Before you download the Data Quality Management software, you must download Attribute Change Package (ACP). If you do not have ACP installed, you may encounter the following errors when you install the FLDQ base component:

● Non-permitted release of add-on SAP installed and Component SAP_BASIS,740 has to be installed.● SAP_ABA 7.51 is not installed. In S4 HANA 1610 initial shipment stack, the SAP_ABA version is 75B.

To download ACP:

1. Go to https://launchpad.support.sap.com/ .2. From the menu at the top of the screen, choose Downloads.3. In the text box at the top of the screen, type Attribute Change Package for FLDQ and press Enter .4. Choose the appropriate version for your system (for example, FLDQ======440_740).5. Click the Download Basket icon to add the selected item to your Download Basket.6. Go to your Download Basket and complete the download.

Learn more about ACP .

Downloading Components for a DQM for SAP Installation or Upgrade

NoteThe steps below describe using SAP Software Download Center to download the various components needed for this software installation. You may choose to use SAP Solution Manager instead; in that case, you do not need to follow these instructions.

NoteThe Data Services download is separate from the DQM for SAP download. You must complete both. Refer to the Data Services Installation Guide and Installing Data Services [page 16]. The component to look for when

User Guide for connecting to SAP Data ServicesInstallation C U S T O M E R 13

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/

http://help.sap.com/disclaimer?site=https://wiki.scn.sap.com/wiki/display/SL/What+is+an+Attribute+Change+Package+and+Why+is+it+Needed

downloading is SAP Data Services - Data Quality Management Premium license, including the Data Services Address Directories for Postal Validation, version 4.2.4 or greater.

1. Navigate to: https://support.sap.com/swdc.2. Select Software Downloads.3. Search for SBOP DQM for SAP SOL. 4.0.4. Select Maintenance Product.

NoteSelect Installation Product only if you need to install an old version of the product. We recommend installing the latest version to gain access to the latest functionality and corrections.

5. Select Entry by Component.6. Select the ABAP Component that corresponds to your system.7. Select SBOP DQM FOR SAP 4.0 [system information].8. Click Support Packages.9. Select the packages for all support packages that you are installing, and click the shopping cart symbol to add

them to your Download Basket.10. In the navigational links that appear near the top of the screen, click ENTRY BY COMPONENT.11. Click DQM for SAP JAVA Components to access the RFC components.12. Click SBOP DQM for SAP 4.0 RFC SERV.13. Select your operating system from the drop-down list.14. Select the RFC Server for the version that you are installing, and add it to your download basket.

NoteBe sure to select the correct Support Package (SP) for your NetWeaver (NW) version. The SP number may not correspond with the number in the .SAR file name. See the table below for details.

15. In the navigational links that appear near the top of the screen, click ENTRY BY COMPONENT.16. Click DQM for SAP Data Services Comp.17. Click SBOP DQM for sap 4.0 DS COMP.18. Select the Data Services component for the version you are installing, and add it to your Download Basket.

NoteBe sure to select the correct Support Package (SP) for your NetWeaver (NW) version. The SP number may not correspond with the number in the .SAR file name. See the table below for details.

19. Complete the download using the Download Basket. See the instructions available on the software download site for details.

Table 8: .SAR Files for Each Support Package (SP)Find your Netweaver / Basis version, and select the support packages (SP) that you need.

SP.SAR Files Listed by Netweaver / Basis Release

NW 700/701 NW 702 NW 710 NW 731 NW 740/750

01 SAPK-44701INFLDQ SAPK-44801INFLDQ SAPK-44901INFLDQ SAPK-45001INFLDQ n/a


Installation


NW 700/701 NW 702 NW 710 NW 731 NW 740/750



04 SAPK-44704INFLDQ SAPK-44804INFLDQ SAPK-44904INFLDQ SAPK-45004INFLDQ SAPK-45101INFLDQ






3.2 Installation Checklist

Installing this software and everything it needs to become operational is a multi-step process. The steps you take depend on whether you are installing this product for the first time or you are installing over an older version of the product. See the checklists below learn about the installation steps for you to follow.

Installing This Product for the First Time

Table 9:

Step Reference Done?

Outside your SAP system:

1 Install Data Services 4.2.4 or higher and the Address Directories (for Postal Validation).

See Installing Data Services [page 16].

2 Install Data Services Components. See Installing the Data Services Components [page 18].

3 Install the RFC Server. See RFC Server [page 29].

Then, on your SAP system:

1 Install the packages from the 4.0 version of this product.

See Installing Packages for a New DQM for SAP Installation [page 26].

2 Install all of the 4.0 Support Packages of this product. See Installing Support Packages for DQM for SAP Add-On FLDQ [page 27].

3 Activate BC Sets See Activating Business Configuration Sets [page 41]



4 Activate the IC WebClient, CRM WebClient, and MDG WebClient, if desired.

See Installing and Configuring Into WebClient for CRM [page 64].

Installing Over a Previous Version of This Product

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.

Table 10:


1 Back up your current Data Services jobs and RFC Server configuration files.

To learn about backing up, see the Data Services Installation Guide.

2 Upgrade your version of Data Services to version 4.2.4 or higher.

To learn about upgrading Data Services and customizing jobs, see the Data Services Installation Guide.

To learn about installing Data Services for use with this product, see Installing Data Services [page 16] in this guide.

3 Uninstall and then Install the version-specific Data Services Components. Manually duplicate any customizations made to Data Services Components jobs from the previous version that you want to reproduce in this version.

See Installing the Data Services Components [page 18].

4 Install the support package of this version. If you are upgrading from an older version, you do not need to re-install the support packages from those previous versions.

See Installing Support Packages for DQM for SAP Add-On FLDQ [page 27].

5 Uninstall the previous version of the RFC Server and install the new.

See RFC Server [page 29].

6 If you have made configuration changes to your previous version of the RFC Server, manually apply those changes to the new configuration from backup copies of the RFC Server configuration files.

See RFC Server [page 29].

3.3 Installing Data Services

This product relies on Data Services for performing data quality operations, so you must install Data Services before installing the components of this product. For instructions on installing, configuring, and running Data Services, see the Data Services Installation Guide.


Installation

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

CautionBe aware that installing Data Services is a multi-step process that involves many components. You must read the Data Services documentation to fully understand and perform all of the required steps.

CautionYou must install the latest patch level for Data Services 4.2 SP4 for the latest version of Data Services.

You should take note of any customizations you have made to this product's components, as the upgrade requires that you manually recreate them in this version.

See the Data Services documentation for details of how to upgrade.

Installing the Address Directories

To perform Postal Validation operations, you must install the Data Services Address Directories. The Address Directories are a separate download. See the Data Services Installation Guide for information about downloading and installing the Address Directories.

Setting the Data Services Code Page to Work With Custom Functions

To use the custom functions provided with this product, use the Data Services Locale Selector to set the code page to UTF-8. For more information, see the Data Services Reference Guide.

NoteData Services must be running during the remaining installation procedures for this product, and during its operation.


3.3.1 Installing the Data Services Components

Before installing the Data Services Components, be sure that you have installed the correct version of Data Services for this product, including any Address Directories for the countries you have purchased. You must have the Data Services Job Server configured and running, and have an Access Server configured. On the machine on which you are performing this installation, you must have already logged in to the Data Services Designer that is connected to the Data Services Repository to be used, and connected to the Job Server.

The installation routine asks for the user name and password for the Data Services Repository database. Prepare this information before beginning the Data Services Components installation.

In addition, you must have a database prepared to use for the creation of batch RDBMS staging tables. This database may or may not be the same as used for the Data Services Repository database. The information required varies depending on the type of supported database used and whether on MS SQL you use Windows Authentication for security of the database. For details, see Data Services Component Installation: Staging Table Values [page 132].

Installing Components

After you install the latest version of Data Services and the Address Directories, you install the Data Services Components specific to this product and then perform configuration tasks. The Data Services Components installation configures database connection information. This section describes installing the Data Services Components for both Windows and UNIX/Linux, and then the configuration steps required after the installation.

CautionIf you previously installed this version or any past version of this product and made customizations to Data Services jobs, installing the Data Services Components will overwrite the customized version of the files. You should back up or rename the job or custom function if you want to keep any customizations, and any other jobs to which you have made customizations. You can then apply the customizations to the new version.

Install the Data Services Components on the machine you installed the Data Services Designer.

The Designer is a Windows-only install. Unix installations of the Data Services Components must be installed on the machine with the Designer.

If any previous or current version of the Data Services Components is already installed, you must uninstall it before conducting this installation. Save a backup of any customizations you have made to help you reproduce them after this installation.

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

2. In the Confirmation Requested window, click Yes to confirm that you have installed the correct version of Data Services.

3. In the Welcome window, click Next.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 Location window, accept the default installation location or specify a different

location. Click Next.


Installation

We recommend that you install to the default directory, and you must install to a path that ends with [your_path]\SAP BusinessObjects\Data Quality Mgmt for SAP Solutions. If you choose another location and run the Break Key Profiler job, you must manually change files within that job. See Installing the Break Key Profiler [page 124].

6. In the Address Engine Selection window, uncheck the box for any address engines for which you did not purchase referential data and click Next.

7. In the Data Services Repository Database Selection window, choose the database type you intend to use for the creation of the Data Services repository. Click Next to continue.If you chose Microsoft SQL Server, a confirmation message appears, asking if you want to use Windows Authentication.Enter the connection information and click Next.

8. In the Confirmation Requested screen, indicate whether you want to use the same information from the Data Services Repository Database Selection window to create the staging tables.

9. If necessary, in the Staging Tables Database Connection Parameters window that appears for your database type, enter the database connection information, and click Next.

10. In the Ready to Install the Program window, click Install to launch begin the installation.11. Click Finish after the installation has completed.

The Data Services Components are now installed to your Data Services system, but you must perform post-installation steps to configure Data Services jobs as services and to configure Web Services.

If error messages occurred during the installation process, you may have to run the installation routine again to uninstall and then attempt to reinstall, use the Designer to set the DQ_SAP_DS datastore password, or manually create the batch RDBMS staging tables.

During installation, the installer places four ATL files in <DS Install Drive>:\Program Files (x86)\SAP BusinessObjects\Data Quality Mgmt for SAP Solutions\integration. If the installation failed, go to that location and manually import the ATL files in order:

1. DQ_SAP_DS_STG_TBL_STEP_1.atl2. DQ_SAP_DS_STEP_2.atl3. DQ_SAP_DS_SYS_CFG_STEP_3.atl4. DQ_SAP_DS_SUB_PARAM_STEP_4.atl

Related Information

Installing the Break Key Profiler [page 124]

3.3.2 Using the Sample Input Files to Test Jobs

Before you move on to the next step (configuring jobs as services), run the Data Services jobs installed using the sample input files to test them. Though running the sample input files is not required as part of installation, the installation is now at a point in which the jobs can be run. This will help identify and eliminate any possible future issues.


During the installation of the Data Services Components, sample input files are installed to your Data Services configuration at <installpath>\SAP BusinessObjects\Data Quality Mgmt for SAP Solutions\extra\SampleInputfiles. You can use these input data files as a template to run data through this product.

For example, if you want to customize a job, you could 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 customize jobs.

For instruction on how to run jobs, see the Data Services documentation.

3.3.3 Configuring Jobs as Services

When you install the Data Services Components, a group of Data Services jobs that are specific to Data Quality Management for SAP are installed to your Data Services Repository.

You must configure these jobs as services. Before configuring jobs as services, you must have configured a Data Services Access Server as part of the installation of Data Services. If you have not configured an Access Server, see the Data Services documentation for instructions.

RestrictionDo not start services for functionality that you did not purchase.

Jobs and Their Service Names

Table 11: Required JobsConfigure jobs as services for all of the jobs listed in this table by following the steps below the table. This table also lists some of the values that you must enter for each service and the memory footprint for each job. The memory information can help you determine the number of instances you should use.

Job Name

Service Name

Description

Recycle Count

Max/Min Instances

Started Instances

Memory (MB)

Job_Realtime_Batch_DQ_SAP_Address_Cleanse

Service_Realtime_Batch_DQ_SAP_Address_Cleanse

This job is used for Quarterly Adjustment reports and produces the same results as those from the interactive address validation process.

1000 3 3 Win 2112

Unix 1875

Job_Realtime_DQ_SAP_Address_Cleanse

Service_Realtime_DQ_SAP_Address_Cleanse

This job is used when the IMG setting is configured so that the Suggestion List is disabled during Postal Validation.

4000 2 2 Win 612

Unix 610


Installation

Job Name

Service Name

Description

Recycle Count

Max/Min Instances

Started Instances

Memory (MB)

Job_Realtime_DQ_SAP_Address_Cleanse_Suggestions

Service_Realtime_DQ_SAP_Address_Cleanse_Suggestions

This job is used when the IMG setting is configured so that the Suggestion List is enabled during Postal Validation.

10000 3 3 Win 3336

Unix 3333

Job_Realtime_DQ_SAP_Create_Break_Keys

Service_Realtime_DQ_SAP_Create_Break_Keys

This is the default job for determining break keys. It does not use first names.

For this job, for optimal /FLDQ/RSADRINIBM performance, start two more batch RFC servers than you have Create Break Key services.

4000 4 (See description at left.)

4 Win 1296

Unix 1600

Job_Realtime_DQ_SAP_Name_And_Address_Match

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

10000 2 2 Win 270

Unix 320

Table 12: Optional JobsConfigure jobs as services for these jobs only if you need them. Setting up services for these jobs unnecessarily will consume memory that you could otherwise preserve.

For any optional jobs that you want to use, you must configure the jobs in Data Services and then restart the RFC servers before trying to execute the jobs from the SAP system.


Job Name Description

Job_Realtime_Batch_DQ_SAP_Name_And_Address_Match

Service_Realtime_Batch_DQ_SAP_Name_And_Address_MatchThis job handles batch mode processing:

● Clears the records of a batch processing run from the staging input and output tables.

● Loads the staging tables with records from the RFC Server request for batch match processing.

● Processes records from input staging table for a specific BATCH_ID. The job matches driver record with candidate records to find potentially duplicated names and addresses. It then loads the results into the output staging table. It uses the substitution parameter DQ_SAP_BATCH_ID to identify the records of a specific batch processing run and is passed from the RFC Server request by default.

● Fetches the duplicate check results in batch mode from the output staging table of a specific batch ID and sends back the results to the RFC Server.

Recycle count: 400

Max/Min instances: 3

Started instances: 1

Memory: Win 1476; Unix 2043

Job_Realtime_DQ_SAP_Data_Cleanse This job is used when the IMG setting is configured to perform person name and organization name standardization.

Job_Realtime_DQ_SAP_Get_Region_Data

Service_Realtime_DQ_SAP_Get_Region_DataThis job retrieves the list of all the possible regions that can be returned by Data Services and sends them to the SAP system. This is used during table maintenance of the /FLDQ/DQ_REGIONS table.

Recycle count: 10000





Installation


Job_Realtime_DQ_SAP_Name_And_Address_Ext_Match

Service_Realtime_DQ_SAP_Name_And_Address_Ext_MatchThis job matches a driver record with candidate records to find potential duplicate names and addresses for the External List Management (ELM) process. It contain five marketing attributes fields that can be dynamically set from the SAP system to be part of the match score, in addition to standard name and address matching criteria.


Max/Min instances: any value

Started instances: n/a

Memory: Win 93; Unix 115 (optional jobs not included in total)

Job_Realtime_DQ_SAP_Name_And_Address_Ext_Match_Weights

Service_Realtime_DQ_SAP_Name_And_Address_Ext_Match_Weights

This job retrieves the match weights that are set in Job_Realtime_DQ_SAP_Name_And_Address_Ext_Match. These values are used on the SAP system to set the marketing attribute values correctly.


Max/Min instances: any value

Started instances: n/a

Memory: Win 7; Unix 144; (optional jobs not included in total)

Job_Realtime_DQ_SAP_Product_Version

Service_Realtime_DQ_SAP_Product_VersionThis job retrieves the versions of the Data Services jobs that are installed and running.





Job_Realtime_DQ_SAP_MDG_Match This job allows duplicate check in an MDG system.

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

DQ_SAP_Break_Key_Profiler This job generates statistics on Customer and Business Partner data to discover the best options to be set for this product.



Job_Realtime_DQ_SAP_Address_Global_GEO This job is used if you have purchased the geocoding option for this product. It processes latitude and longitude for supported global country addresses.

Job_Realtime_DQ_SAP_Create_Break_Keys_With_Firstname This job uses first names for the creation of break keys.

Job_Realtime_DQ_SAP_MDG_Create_Match_Codes This job creates match codes (break keys) for duplicate check in an MDG system.

Table 13:The memory usage shown below is a guideline and will differ based on the concentration or dispersion of the address location data.

Batch job Recommended / default degree of parallelism

Total size (MB) per million records

Job_Batch_DQ_SAP_Name_And_Address_Match_Process 6 1000

Configuring Real-Time Services

Perform these steps for each job listed in the Required Jobs table and any optional jobs that you need.

1. Open the Data Services Management Console and log in.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). 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 (listed in the preceding table). Exact case is required.9. Enter a Processing timeout value of 800 for all services.10. Enter the Recycle count value, as shown in the preceding table.11. Under Service Provider, click Add and select the correct JobServer to run this service.12. Enter the same number for both the Max Instances and Min Instances for the service, as shown in the

preceding table.13. Click Apply.


Installation

3.3.4 Configuring Web Services

After configuring jobs as a service, you must configure Web Services by following the steps below.

Adding the Batch Job

1. Log in to the Data Services Management Console and click Administrator.2. Select Web Services from the file tree and open the Web Services Configuration tab.3. Select Add Batch Job... from the drop-down menu, and click Apply.4. Select job name Job_Batch_DQ_SAP_Name_And_Address_Match_Process, and click Add.

Adding the Real-Time Job

1. Log in to the Data Services Management Console and click Administrator.2. Select Web Services from the file tree and open the Web Services Configuration tab.3. Select Add Real-Time Service from the drop-down menu and click Apply.

All of the service names that you entered previously appear in the list.4. Choose Select All and click Add.

If you added the Data Quality Management, version for SAP Solutions Web Services without session security enabled, you must disable session security for the functions Get_RTService_List and Get_Batchjob_Status.

5. In the Web Service Configuration tab, select the functions Get_RTService_List and Get_Batchjob_Status, and from the drop-down, select Disable Session Security.

3.3.5 Starting the Services

After you have configured both the jobs and Web Services, you must 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 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.

After you have performed the automatic services start, you must shutdown and restart the services manually if you change the configurations.


3.4 Installing the Add-Ons

TipA Basis Administrator must perform the tasks described in this topic.

You install the appropriate Data Quality Management (DQM) for SAP packages to upgrade to the latest functionality.

If this is a new DQM for SAP installation for you, follow the instructions to install the Add-On for a new DQM for SAP installation.

After you install the 4.0 Add-On, proceed to install the support packages.

Before you can perform these steps, you must have the latest Support Package Manager (SPAM) update/patch installed on your SAP system. (For more information, see SAP Note 822379.)

3.4.1 Installing Packages for a New DQM for SAP Installation


Follow the instructions below to install DQM for SAP version 4.0.

To ensure that your SAP system complies with all requirements, see System Requirements.

Importing the DQM for SAP 4.0 Installation Package on Client 000

1. Enter the transaction SAINT to open the Add-On Installation Tool window.

2. Click the Installation Package menu and choose Load packages From Frontend .3. In the Select CAR/SAR archive window, browse to and select the applicable .SAR file for your Basis version. If

the path is long and the system generates an error, copy the file to a local directory location and load it from there.

Table 14:

NW / Basis Release

.SAR file for new installations .SAR file for SAPehpi/SAPup system upgrades

Note: Path is …\DATA_UNITS\…. File extension is .SAR.

NW 700/701

…\FLDQ_440_700_INST\DATA\K-447AGINFLDQ …\FLDQ_440_700_UPGR\DATA\K-447GGINFLDQ (NW 700 only)

NW 702 …\FLDQ_440_702_INST\DATA\K-448AGINFLDQ …\FLDQ_440_702_UPGR\DATA\K-448GGINFLDQ


Installation

NW / Basis Release

.SAR file for new installations .SAR file for SAPehpi/SAPup system upgrades

Note: Path is …\DATA_UNITS\…. File extension is .SAR.



NW 740/750

…\FLDQ_440_740_INST\DATA\K-451AGINFLDQ …\FLDQ_440_731_UPGR\DATA\K-450GGINFLDQ

4. Click Open and then click Yes to load the .SAR file.5. Click Decompress.6. Continue with standard Add-On Package process for component FLDQ. (For further instructions on importing

an Add-On Package, see the documentation for your SAINT tool.)7. Click Continue, and then Complete to close the tool.

Next you must install the DQM for SAP support packages add-on.

NoteSee the following for important information:

● SAP Note 1623439 Installation/Delta upgrade FLDQ 440_700● SAP Note 1613042 Installation/Delta upgrade FLDQ 440_702● SAP Note 1615470 Installation/Delta upgrade FLDQ 440_710● SAP Note 1729436 Installation/Delta upgrade FLDQ 440_731● SAP Note 1875965 Installation/Delta upgrade FLDQ 440_740

Related Information

System Requirements [page 10]Installing Support Packages for DQM for SAP Add-On FLDQ [page 27]Activating Business Configuration Sets [page 41]

3.4.2 Installing Support Packages for DQM for SAP Add-On FLDQ


After you install the packages for DQM for SAP 4.0, install packages for the latest support packages. If you are not caught up with the latest support package, be sure to install all support packages that are not installed.


http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/1623439





Importing the DQM for SAP Support Packages on Client 000

1. Enter the transaction SPAM to open the Support Package Manager window.

2. Click the Support Package menu and choose Load packages From Frontend .3. In the Select CAR/SAR archive window, browse to and select the applicable .SAR files for your Basis version

(see table below). If the path is long and the system generates an error, copy the file to a local directory location and load it from there.

Table 15: .SAR Files for Each Support Package (SP)Find your Netweaver / Basis version, and install the support packages (SP) that you need.


NW 700/701 NW 702 NW 710 NW 731 NW 740/750










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 Continue, and then Complete to close the tool.

NoteSee the following for important information about generation errors:

● SAP Note 1706715 - Support Package for Add-On FLDQ 440_700● SAP Note 1706716 - Support Package for Add-On FLDQ 440_702● SAP Note 1706717 - Support Package for Add-On FLDQ 440_710● SAP Note 1736208 - Support Package for Add-On FLDQ 440_731● SAP Note 1950970 - Support Package for Add-On FLDQ 440_740

Next you must activate (or reactivate) the applicable BC Sets to import new customizing data on the target clients and 000 reference clients.


Installation






Related Information

Activating Business Configuration Sets [page 41]

3.4.3 Applying SAP Notes After Installing SP 09

After updating to Data Quality Management version for SAP Solutions SP 09, you must apply the following SAP Notes.

SAP Note 2326588:

● /FLDQ/RSADRQU2 report may generate invalid SAP address regions. See: https://launchpad.support.sap.com/#/notes/2326588/E

SAP Note 2351601:

● /FLDQ/RSPRODVER does not handle all DQ engines properly. See: https://launchpad.support.sap.com/#/notes/2351601/E

SAP Note 2373062:

● Losing LANGU and other values when committing changes with /FLDQ/RSADRRVW during Quarterly Adjustments. See: https://launchpad.support.sap.com/#/notes/2373062/E

SAP Note 2403997:

● Ensure the Quarterly Index is completely cleared out before address validation occurs during Quarterly Adjustments. See: https://launchpad.support.sap.com/#/notes/2403997/E

SAP Note 2410703 (optional):

● Use DQ France subregion for SAP region mapping. See: https://launchpad.support.sap.com/#/notes/2410703/E

3.5 RFC Server

The Remote Function Call (RFC) Server is a server that allows third-party programs, including SAP Applications, to schedule and initiate Data Services jobs and return the results to Data Services.

At minimum, you must run one instance of the RFC Server for transactional processing to make this product operational, but you are encouraged to run more. In addition, performing batch processing requires one or more RFC Servers dedicated to batch processing. You can install the RFC Server on the same machine as Data Services, on a different machine, or even on a machine with a different operating system than the one that contains your installation of Data Services. However, installing Data Services and the RFC Server on the same machine reduces network traffic, slightly increases performance, and reduces the number of ports that must be exposed and enabled.

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


http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#/notes/2326588/E








3.5.1 Preparing to Install the RFC Server

Prepare for RFC Server installation by completing the following steps.

Table 16:

Step Reference

1 Assign SAP authorizations to allow the RFC User to interact with the ABAP stack of SAP systems.

See Assigning SAP Authorizations to the RFC User [page 30]

2 Gather the following information, which will be requested during RFC Server installation.

● Gateway Connection information of your SAP system: three-letter System ID, Gateway Server Host Name, Gateway Service ID, Transaction Program ID (FLRFCSRV), and Batch Program ID (FLRFCBTC)

● Application Server connection information: Host Name, System Number, Client, User Name, Password, and optional language

● Data Services security settings: path to the Data Services trusted certificate folder (if you enable Web Service SSL communication), and the CMS User Name, Password, system name, and authentication type (if you enable session security)

● Data Services Access Server connection information – Host Name, Port Number, and URL for the WSDL

● Your email system settings: Host, Port, a sender email address, and recipient email addresses (in comma-delimited format), used by the RFC Server to send email notifica-tions if it terminates Data Services Access Server connection information: Host Name, Port Number, and URL for the WSDL

● The BusinessObjects Enterprise (BOE) Central Management Service (CMS) username, password, system name, and authentication type (if you enable session security)

See Data Services Administrator's Guide

3 Confirm that the SAP system allows external RFC connections.

Define the SAP connection security strategy by setting the gw/acl_mode parameter or by configuring connection security settings in the gw/sec_info and gw/reg_info files. If the gw/sec_info and gw/reg_info files exist, their securityInstalling the RFC Servers requires this task of Basis configuration settings override the gw/acl_mode setting. administration, which is applicable to SAP systems at Kernel Release 720 and greater.

See 1480644 and 1069911

4 Ensure access to flrfcsrv_log.txt file.

On Windows 2008 Server and later systems that use the User Account Control (UAC), the RFC Server may not be able to run if that user does not have appropriate privileges. The error is caused by the inability to access the flrfcsrv_log.txt file. You must ensure that the user has privileges to access this file.

3.5.2 Assigning SAP Authorizations to the RFC User

Before installing the RFC Server, you must:

● Create an RFC user on the SAP ABAP target client in transaction SU01 or similar (for fresh installations).● Assign the new RFC User SAP authorizations to allow the RFC User to interact with the ABAP stack of your

SAP systems by using the role template provided with this installation.


Installation



Table 17: RFC User Name and Type

RFC User Name: We recommend combining the SID and COM to create the RFC User Name. For example, if you have a D22 system RFC Server, the name would be D22COM.

RFC User Type: Communications

Using the RFC Server Role Template

Use the provided Role Template to help ensure that proper updated security authorizations are used for the RFC Server user.

1. Invoke transaction PFCG.2. Enter /FLDQ/DQM_COMM_USER in Role.3. From the Role menu, click Copy (Shift + F11) and enter a new role name (such as ZDQM_COMM_USER)4. Click the Copy All button.

5. Click the pencil icon .6. Select the Authorizations tab and then click the Propose Profile Name button. The Profile Name is created.7. Click the Change Authorization Data button. If you are prompted, click Yes.8. Click the Generate button.9. Click the Back button.The Authorization tab indicator becomes green.10. Select the User tab and enter the RFC user you created into the User Assignments area.11. Click Save.12. Click the User Comparison button.13. Click Complete Comparison.14. Click Save.

The authorizations are now set.

Authorizations

This table shows the required authorizations that should now be set by using the role template.

Table 18:

Name Required authorizations

Activity Execute

Name of RFC to be protected /FLDQ/AD_GENERIC_FM, RFC1, SDIFRUNTIME, SYST, SYSU

Type of RFC object to be protected FUGR (Function group)

If you did not use the role template for any reason, you must manually set the authorizations, see your SAP system documentation for more information about assigning authorizations.


3.5.3 Number of RFC Servers to Install

You must minimally run one instance of the RFC Server. If you use duplicate search in batch mode (called batch match), you must run one or more instances of the RFC Server dedicated to batch match. Running more instances of the RFC Server can increase performance.

For real-time transactions, we recommend the following based on the number of concurrent users.

Table 19:

Number of concurrent users Number of RFC Server instances

50 3

100 6

200 13

300 19

400 25

500 31

If your transactional usage is predictable and consistent (no significant peak times of usage), we recommend the following based on the number of records your organization creates or modifies in a day.

Table 20:

Records Number of RFC server instances

12,000 2

24,000 3

48,000 6

96,000 13

144,000 19

192,000 25

240,000 31

A common scenario for the number of transactional RFC Servers is 6.

The resources footprint of an RFC Server instance is relatively small. Running additional instances of the RFC Server often increases performance.

3.5.4 Installing an RFC Server as a Windows Service

During an 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 SAP DQM xxx yyy 1 (where xxx is the System ID and yyy is the Program ID). Other instances of the RFC Server are named SAP DQM xxx yyy 2, SAP DQM xxx yyy 3, and so on.


Installation

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

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.

3.5.5 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 file flrfcsrv.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.

Related Information

Configuring the RFC Server [page 38]

3.5.6 Installing the RFC Server

Ensure that the machine that you intend to install the RFC Server on meets the system requirements.

The instructions below are specific to Windows, though versions of UNIX and Linux are supported. 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.

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

2. In the Welcome screen, click Next.3. Read the license agreement and, if you accept the license agreement terms, choose I accept the terms of the

license agreement and click Next.4. If you want to install the RFC Server as a Windows Service, click Yes and then in the next screen enter the

number of Services you want to create for Transactional and Batch processing, and click Next. Otherwise, click No.

5. In the Choose Destination Locations window, accept the default installation location or specify a different location. Click Next.


By default, the installation routine for Windows installs the RFC Server to the folder C:\Program Files\SAP BusinessObjects\Data Quality Mgmt for SAP Solutions. For UNIX or Linux, it installs by default to Business_Objects/Data_Quality_Mgmt_for_SAP_Solutions.

6. In the SAP Information windows, enter the following information and click Next:

These options appear in more than one window.

○ SAP System ID (a maximum of three characters in length)○ Gateway Server Host Name (use the name of the SAP central instance gateway)○ Gateway Service ID (typically “sapgw<xx>,” where <xx> is the central instance number)

Next,choose the metadata connection method. You can choose the Application Server or the Message Server. If you choose the Application Server Connection, enter the following:

○ Application Server Host Name○ Application Server System Number (a maximum of two numbers in length)○ Application Server Client Number (a maximum of three characters in length)○ Application Server User Name○ Application Server Password (entered twice for confirmation)

NoteEach SAP systems password is encrypted and stored in the configuration file flrfcsrv.xml. You can reset the password by executing the start_password_reset script from within a shell. The startup script is in the RFC Server installation folder. When run, it prompts for the SAP communication username and password.

○ SAP Router (optional)○ Client Language (optional)

If you choose the Message Server Connection, enter the following:○ Message Server Host Name○ Message Server Group○ Message Server Port (optional)○ Client Number○ Client User Name○ Client Password (entered twice for confirmation)○ SAP Router (optional)○ Client Language (optional)

7. If, during the Data Services installation, you enabled these settings, in the Data Communication Security Settings window check the Yes box before clicking Next:

Option Description

Is Access Server SSL communication enabled?

This setting is configured though the Data Services Access Server and uses a set of supplied certifi-cates for connection. Enabling this setting encrypts all data but does not authenticate the user. If you enable this feature, you must supply the path to the Data Services Certificate.

Is Web Service SSL Communication enabled?

This setting enables a SSL connection through the Web Service hosting the Data Services Management Console. This connection is controlled by the supported interface in the Web Service (for example, through a Web server, such a Tomcat). Enabling this setting encrypts all data but does not authenticate the user. If you enable this feature, you must supply the path to the Data Services Certificate.

Is session security enabled?

Session security is enabled by default. This setting applies to the Web Service. Leaving session security enabled forces most calls to the Web Service (except ping and login/logout) to log in with a valid


Installation

Option Description

BusinessObjects Enterprise (BOE) Central Management Service (CMS) username/password before accessing Web Service functions. It does not encrypt data. If you are not enabling session security you must disable the Data Services Web Service Configuration GetRTServie_List security via the Management Console. If enabled, you must supply the following information about the CMS system.○ CMS username○ CMS password (entered twice)○ CMS system name○ CMS authentication type

8. In the Data Services Connection window, enter the Data Services Access Server hostname, port number (default is 4000), and the URL of the Data Services Web server. Click Next.The default is either http://<hostname>:8080/DataServices/servlet/webservices?ver=2.0&wsdlxml or, if you use SSL, https://<hostname>:28080/DataServices/servlet/webservices?ver=2.0&wsdlxml.

9. 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 hibernates, or if 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.

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 the section Configuring through flrfcsrv.xml.

10. Click Next.11. In the Monitor Services Settings window, select which groups of services you want the RFC Server to monitor

(see below). Click Next.

Table 21:The RFC Server can monitor the services you configured as part of the installation of the Data Services Components. If one or more of those monitored services stops running, the RFC Server hibernates until it detects that those services are running again. If email notifications are enabled, the RFC Server sends a notification email to the designated recipients before hibernating.

Category Services

Postal Validation Real-Time Services

○ Service_Realtime_DQ_SAP_Address_Cleanse○ Service_Realtime_DQ_SAP_Address_Cleanse_Suggestions○ Service_Realtime_Batch_DQ_SAP_Address_Cleanse

Duplicate Check Real-Time Services

○ Service_Realtime_DQ_SAP_Create_Break_Keys○ Service_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName○ Service_Realtime_DQ_SAP_Create_Break_Keys_No_PV○ Service_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName_No_PV○ Service_Realtime_Batch_DQ_SAP_Name_And_Address_Match○ Service_Realtime_DQ_SAP_Name_And_Address_Match

Name Cleanse Real-Time Service

○ Service_Realtime_DQ_SAP_Data_Cleanse


Category Services

Extended Search Real-Time services (for CRM 7 Ehp1 or Greater)

○ Service_Realtime_DQ_SAP_Name_And_Address_Ext_Match○ Service_Realtime_DQ_SAP_Name_And_Address_Ext_Match_Weights

These services are optional for the installation of this product, even on CRM 7 Ehp1 or greater systems. Do not configure the RFC Server to monitor these services unless you have config-ured them.

Add-on Non-Essential Supportive Real-Time Services

○ Service_Realtime_DQ_SAP_Address_Global_GEO○ Service_Realtime_DQ_SAP_Product_Version○ Service_Realtime_DQ_SAP_Get_Region_Data

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

13. Click Finish when the installation is complete.

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.

A typical setup has one gateway server attached to multiple application servers and multiple RFC servers. When you run the RFC server installation a second (or third, etc.) time, you are given the option to proceed with that typical setup or to have multiple gateways, with each their own application server and RFC server. To configure your setup in this alternate way, with multiple gateways, use the New Config Based on Existing Gateway option during RFC installation.

RememberAfter installing the RFC Server, you must set up the SAP handshake with the RFC Server to test whether the components can communicate. See the IMG activity SAP Handshake With RFC Servers.


Installation

Related Information

System Requirements [page 10]IMG: SAP Handshake With RFC Servers [page 44]

3.5.7 Starting and Stopping the RFC Server

CautionBefore you start the RFC Server, ensure that the following steps have been completed:

● Install Data Services and the Data Services Components.● Install and activate Add-Ons.● Configure the RFC Server as a destination on the SAP side.● Ensure that your Data Services jobs are up and running as real-time services and deployed to the web

server.

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

Table 22:

Windows: <install_directory>\start_<SAP systemID>_<SAP programID>_trans.bat

<install_directory>\start_<SAP systemID>_<SAP programID>_batch.bat

UNIX/Linux: <install_directory>/start_<SAP systemID>_<SAP programID>_trans

<install_directory>/start_<SAP systemID>_<SAP programID>_batch

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

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


When the RFC Server starts, it displays status messages about its progress and any technologies (such as Extended Search or MDG) not supported by the SAP Basis version to which it connects.

Stopping 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, then, on the machine that hosts the RFC Server, you must use Ctrl-C in the RFC Server console to terminate the RFC Server process. This method may on rare occasion cause SAP to show a connection to the RFC Server after the RFC Server has stopped.

NoteIf you use transaction SMGW from within your SAP system to stop the RFC Server and 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). 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.

Related Information

Installing Data Services [page 16]Installing the Data Services Components [page 18]IMG: SAP Handshake With RFC Servers [page 44]Configuring Jobs as Services [page 20]Installing the Add-Ons [page 26]Defining RFC Destinations [page 45]

3.5.8 Configuring the RFC Server

During installation the RFC Servers for this product are created. By default, all of the necessary files on each RFC Server are configured to properly run this product. You may, however, change items after installation.

Editing flrfcsrv.xml

The main configuration file of the RFC Server is flrfcsrv.xml. Using parameters in this file, you control several features of this product, such as how it handles logging and various performance-related settings. This section discusses certain critical settings of this configuration file.

The file is located on your system at <install_directory>\config\flrfcsrv.xml.


Installation

CautionDo not edit flrfcsrv.xml unless you understand the implications of those changes. Errors in this configuration file could disable this product.

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.

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.

Enabling DPV

Within flrfcsrv.xml, <address_suggestion> defines the dataflow used for address suggestions. The default is Service_Realtime_DQ_SAP_Address_Cleanse_Suggestions.

If you have installed the Delivery Point Validation (DPV) directories in Data Services and configured Job_Realtime_DQ_SAP_US_DPV_Address_Cleanse_Suggestions as a service, you can enable DPV address suggestions by changing the value of <address_suggestion> to Service_Realtime_DQ_SAP_US_DPV_Address_Cleanse_Suggestions.

Enabling Geocoding

By default, the RFC Server is not configured to handle geocoding.

Within flrfcsrv.xml, <address_geo> defines the dataflow used for geocoding. If you have purchased, installed, and configured geocoding for US addresses, uncomment <address_geo> as described below.

Change the line:



to:

<address_geo>Service_Realtime_DQ_SAP_Address_Global_GEO</address_geo>

Save the file and restart the RFC Server for this change to take effect.

NoteAdditional steps are necessary to fully enable geocoding.


Related Information

Configuring Geocoding [page 66]


Installation

4 Required Post-Installation Setup

After installing the product and before you can begin using its features, you must perform these essential setup steps that are described in this chapter.

Some steps are related to this product's functionality. You can enable or disable various features and control how the features operate. Some of the essential setup steps are related to this product's interaction with the RFC Server.

4.1 Activating Business Configuration Sets

You must activate BC Sets to apply their settings to the client. This required step must be performed after installation and before this product's functionality is available for use.

Data Quality Management BC Sets

The following BC Sets are available for SAP Data Quality Management, version for SAP Solutions (DQM for SAP). Activate the appropriate BC Sets on your clients, as needed.

Table 23:

BC Set Description Client

/FLDQ/BASE_CI1 Required activation on client 000 for all DQM for SAP scenarios, includes client-independent configurations.

000

/FLDQ/BASE_CD1 Required activation on each target client where a DQM for SAP scenario will be used.

non-000

/FLDQ/EXT_SEARCH Used for CRM extended search capabilities only. Activate in each target (non-000) client that needs CRM extended search capabilities.

non-000

/FLDQ/BSP_PV Used for CRM WebClient installations only. Activate in each CRM WebClient target (non-000) client. Activating Business Server Pages (BSP) BC Sets is necessary only if you are enabling this product's functionality in a CRM IC WebClient or CRM WebClient environment.

non-000

/FLDQ/MDG_SDQ_MSG Used for SAP Master Data Governance – Supplier (MDG) installations only. Activate in each target MDG (non-000) client.

non-000

Activating BC Sets on the Administrator (000) Client

Activate the applicable BC Sets (see table above) by following the steps below.

User Guide for connecting to SAP Data ServicesRequired Post-Installation Setup C U S T O M E R 41

You must activate the base BC Sets first:

● BASE CI1● BASE CD1

1. From client 000, use /nSCPR20 to navigate to the Business Configuration Sets : Activation transaction.2. Type the name of the BC Set (for example, /FLDQ/BASE_CI1) in the BC Set input field and click Enter.

A confirmation message appears.3. Click Activate.4. Create a new change request. (Dismiss any caution message that appears.)5. In the Activation Options window, click Continue Activation (Enter).

An Activation complete message appears at the bottom of the window.6. Repeat steps 2-5 to activate additional BC Sets that you need.

Activating BC Sets on the Target Client

Activate the applicable BC Sets (see table above) by following the steps below. Repeat these steps for each target client (non-000 logon clients) that you want to configure for use with this product.

1. From the target client (a non-000 logon client), use /nSCPR20 to navigate to the Business Configuration Sets : Activation transaction.

2. Type the name of the BC Set (for example, /FLDQ/BASE_CD1) in the BC Set input field and click Enter.A confirmation message appears.

3. Click Activate.4. Create a new change request. (Dismiss any caution message that appears.)5. In the Activation Options window, click Continue Activation (Enter).6. Repeat steps 2-5 to activate additional BC Sets that you need on the current client.7. Repeat steps 1-6 on other target clients as needed.

Another method of activating BC Sets is using IMG activities.

Related Information

IMG: Activate Base BC Set [page 47]IMG: Activate Client Specific BC Set [page 47]

4.2 Setting up Data Quality Management IMG Activities

After you have installed all components of this product, you can configure it to perform postal validation, person and firm name cleansing, and/or duplicate searching with settings appropriate for your business.

You can customize many aspects of this product through the activities it adds to the SAP Implementation Management Guide (IMG).


Required Post-Installation Setup

NoteThe IMG activities described in this section must be configured before you can use this product. Other IMG activities are optional; see Optional Post-Installation Setup [page 49].

NoteIMG activities that are specific to Master Data Governance (MDG) and External List Management (ELM) are described elsewhere in this manual.

Related Information

Maintain Services for MDG Generic Duplicate Check [page 94]External List Management [page 118]

4.2.1 Linking to SAP Reference IMG Structure

After you import the Add-On, this product's IMG structure (/FLDQ/AD_IMG) is linked to the Reference IMG structure of your SAP system. You should verify that the added IMG structure is in place.

NoteUsers of MDG must perform this procedure to link the option /FLDQ/AD_IMGMDG. Users of CRM 7 EnhP1 or greater systems must perform this procedure to link the option /FLDQ/AD_IMGCRM. If you are not using MDG or CRM 7 EnhP1 or greater, skip this procedure.

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, click the Possible Entries icon located next to the IMG Structure field.4. In the Find Structure window, enter Address Management for the Title and click Execute.

A message tells you 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 the option you are linking:

○ /FLDQ/AD_IMGMDG (for MDG systems)○ /FLDQ/AD_IMGCRM (for CRM 7 EnhP1 or greater systems)

7. In the Edit IMG Structure window, click Enhance Structure.8. Click Enter to dismiss each Information window that appears.

9. Select the last Address Management subnode and then Edit Nodes Insert IMG Structure On Same Level .

10. Click Find in the Reference to a Structure window, and type in the Title either BusinessObjects (for MDG systems) or DQM (for CRM systems). Click Execute.


11. In the table of found options, double-click the option appropriate for your system:

○ BusinessObjects : Global Data Quality Connector : MDG Extension (for MDG systems)○ DQM : Global Data Quality Adapter : CRM7 Extension (for CRM 7 EnhP1 or greater systems)

12. Enter the text appropriate for your system to name the IMG node:

○ SAP Data Quality Management : MDG Extension (for MDG systems)○ SAP Data Quality Management : CRM Extension (for CRM 7 EnhP1 or greater systems)

13. In the Reference to a Structure window, copy the text from the The node refers to the structure field and paste it into the Node Name field.

14. Click Enter and then click Save.15. In the Change Request window, click Create in the Change Request window.16. Enter a name for the change request and click Save.17. Click Enter to clear the task dialog.

Users of MDG must perform this procedure a second time to link the option /FLDQ/AD_IMGMDG. Users of CRM 7 EnhP1 or greater systems must perform this procedure a second time to link the option /FLDQ/AD_IMGCRM.

4.2.2 Locating the IMG Activities

After installation, the IMG activities for this product are embedded within the IMG of your SAP application.

The fastest way to access the Data Quality Management node structure is to use transaction /N/FLDQ/DQMIMG. Or you can follow the steps below.

1. Use transaction SPRO to access the IMG structure.

2. Follow the path shown below. The navigation depends on the Basis version that you use.

Table 24:

Basis Version Path

7.00 (ECC 6.0 and CRM 2007)

7.10 (Banking Services 6.0)

SAP Web Application Server Application Server Basis Services Address

Management SAP Business Objects Data Quality Management

7.01 (CRM 7.0 and ERP 6.0)

7.02 (ERP 6.0 Enh Pack 5)

7.31

7.40

SAP NetWeaver Application Server Basis Services Address Management

SAP Business Objects Data Quality Management

4.2.3 IMG: SAP Handshake With RFC Servers

This activity is a post-installation configuration for first-time installations of this product. Users performing a fresh installation must perform this task. It can be performed at any time necessary.

If you are upgrading from a previous version of this product, this step was part of the installation of that previous version.



Use this activity to define the RFC destination and test whether the components of this product can communicate by invoking a TCP/IP handshake.

The first time this activity is invoked, you must define the RFC destination.

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

You must define the following RFC destinations:

● FL_GDQC_SERVER● FL_GDQC_BATCH

Defining the RFC destination FL_GDQC_SERVER

1. From the IMG on a target (non-000) client, click the activity SAP Handshake with RFC Servers.2. Click Create.3. Complete the fields in the RFC Destination window as follows:

Table 25:

Field Data

RFC Destination FL_GDQC_SERVER

If you choose not to use the default name FL_GDQC_SERVER, you must go to the activity Maintain operating parameters and ensure that the value of the RFC_DEST parameter is the name of the chosen RFC destination.

Connection type T

Description Connection to DQM for SAP - RFC Server on <machine name>

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 necessary because the RFC Server for this product is registered on the SAP gateway as an RFC Server.

6. Input the Program ID as FLRFCSRV.If you choose not to use the default Program ID FLRFCSRV, you must edit the <sap_progid> setting in the configuration file flrfcsrv.xml. For details, see the section Configuring through flrfcsrv.xml.

7. If necessary, specify a Gateway Host and service. This step is necessary only if you want to use RFC Servers connected to a different gateway server. If a gateway host/service name is provided, then you must also ensure that this system has the default gw/monitor system parameter set to 2 for this product to operate properly.

8. If you are installing this product on a Unicode system:1. On SAP versions that use Basis 7.00, select the MDMP & Unicode tab. On SAP versions that use versions

above Basis 7.00, select the Unicode tab.


2. Select the option Unicode in the Communcation Type with Target System section.3. Press Ctrl+S to save the settings and exit the activity.

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

9. Click the Connection Test button. If the RFC Server is running and the connection is successful, a confirmation appears.

10. Click Back.11. Press Ctrl+S to save the settings.

Defining the RFC destination FL_GDQC_BATCH

1. From the IMG on a target (non-000) client, click the activity named SAP handshake with RFC servers.2. Click Create.3. Fill in the fields of the RFC Destination window as follows:

Table 26:

Field Data

RFC Destination FL_GDQC_BATCH

If you choose not to use the default name (FL_GDQC_BATCH), you must go to the IMG activity Maintain Operating Parameters and ensure that the value of the RFC_DEST parameter is the name of the chosen RFC destination.

Connection type T

Description Connection to DQM for SAP - Batch RFC Server on <machine name>

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 necessary because the RFC Server for this product is registered on the SAP gateway as an RFC Server.

6. Input the Program ID as FLRFCBTC.If you choose not to use the default Program ID (FLRFCBTC), you must edit the <sap_progid> setting in the configuration file flrfcsrv.xml. For details, see the section Configuring through flrfcsrv.xml.

7. If necessary, specify a Gateway Host and service. This step is necessary only if you want to use RFC Servers connected to a different gateway server. If a gateway host/service name is provided, then you must also ensure that this system has the default gw/monitor system parameter set to 2 for this product to operate properly.

8. Press Ctrl+S to save the settings and exit the activity.

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

9. Click the Connection Test button. If the RFC Server is running and the connection is successful, a confirmation appears.



10. Click Back.11. Press Ctrl+S to save the settings.

4.2.4 IMG: Activate Base BC Set

You can use this activity to activate /FLDQ/BASE_CI1 on the SAP Client 000. Note, however, that it is necessary to activate multiple BC sets, and you can accomplish this more quickly and efficiently by using the SCPR20 transaction.

Related Information


4.2.5 IMG: Activate Client Specific BC Set

You can use this activity to activate /FLDQ/BASE_CD1 on each SAP Client that uses this product. Note, however, that it is necessary to activate multiple BC sets, and you can accomplish this more quickly and efficiently by using the SCPR20 transaction.

Related Information


4.3 Prepare for Matching

Before you can perform matching with this product, you must:

● Run the Quarterly Adjustment reports● Run the Initial Match Code (Index) Setup

Related Information

Batch Address Cleansing With Quarterly Adjustment Reports [page 74]


Initial Match Code (Index) Setup and Batch Match Report (/FLDQ/RSADRINIBM) [page 87]



5 Optional Post-Installation Setup

Additional setup may be necessary, depending on your needs and environment.

Follow the instructions in this chapter to enable or disable various features and control how the features operate.

Related Information

Required Post-Installation Setup [page 41]Setting up Data Quality Management IMG Activities [page 42]

5.1 Optional IMG Activities

5.1.1 IMG: Maintain Settings to Switch off the Address Reviewer Screen

Use this activity to control when the system displays the Address Reviewer screen, based on changes to an address's components. The default behavior is to display the Address Reviewer screen when an address is created or changed and one or more components of the address triggers postal validation and requires review.

You may not want the Address Reviewer screen to appear when users change certain components of an address. You can control this behavior by selecting the appropriate entries based on what part of an address has changed during postal validation and entering a country code.

ExampleDeactivating the Address Reviewer Screen

To suppress the Address Reviewer screen for changes to the postal code for U.S. addresses only, you would make the following entry:

Table 27:

Country Country, Postcode, Region, or Locality Corrections

Country, Postcode, Region, or Locality Corrections

Pre/Post Directionals, Primary Name, Type, and Range Corrections

Unit Description, Unit Number, Building, Stairwell, and Firm Name Corrections

US CORRECTED POSTAL CODE.

NO SIGNIFICANT DIFFERENCE BETWEEN THE INPUT DATA AND THE CORRECTED DATA.


User Guide for connecting to SAP Data ServicesOptional Post-Installation Setup C U S T O M E R 49

To suppress the Address Reviewer screen for changes to postal code for all addresses, regardless of the country, you would make the following entry:

Table 28:

Country Country, Postcode, Region, or Locality Corrections

Country, Postcode, Region, or Locality Corrections

Pre/Post Directionals, Primary Name, Type, and Range Corrections

Unit Description, Unit Number, Building, Stairwell, and Firm Name Corrections

<blank> CORRECTED POSTAL CODE.



5.1.2 IMG: Maintain Settings for Address Validation Control

Use this activity to configure address validation to require users to either accept the validated address or only use the address that was input. This can be configured per country.

To configure this option, enter a country code and choose to use the validated or original address:

Table 29:

Option Description

Use Validated Address Only Requires users to accept the address as corrected before it can be saved.

Use Original Address Only Requires users to accept the address as it was entered. It does not allow users to save using the corrected address.

5.1.3 IMG: Maintain Supported Countries

Use this activity to maintain the ISO country codes for the countries for which this product provides postal validation. The list of countries that are supported depends on the postal directories that you have licensed.

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.

Removing a Country Code

To remove a country from this list:

1. Select the country code from the list of supported countries.2. Click the Delete button.3. Save the changes.


Optional Post-Installation Setup

5.1.4 IMG: Maintain Exception Table of Transaction Codes

Use this activity to control postal validation per transaction, search, and duplicate check. You can also disable suggestion lists, preventing them from being displayed for specific transactions.

During postal validation, this product 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.

You can turn off postal validation or duplicate check by checking the appropriate box.

NoteOn systems running CRM 2007 (Basis version 7.00), you should uncheck the box for SAPHTTP—Suppress Validation, Suppress Search, Suppress Suggestions to allow postal validation in the CRM WebClient or CRM IC Web Client. On all other SAP platforms supported by this product, this setting should be active.

Adding a Transaction Code to the Exception Table

CautionBesides its main purpose, this activity lets you disable postal validation and error tolerant search/duplicate check on a transaction basis. However, we do 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 this product without removing it from your SAP system. Suppressing only the suggestions without suppressing validation or searches ensures that invalid data is not stored.

1. In the IMG, select 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 Validation5. Check the Suppress Search box box if you want to prevent if you want to prevent both error tolerant search and

duplicate checking for postal validation for that transaction (not recommended).6. Check the Suppress Dialog box to prevent suggestion lists from appearing in dialog boxes.7. Close the window to save the changes and return to the previous window.


TipYou can select and deselect the suppression options in the Change View ‘Maintain exception table of transaction codes’: Overview window.

5.1.5 IMG: Activate SAP Postcode Check Before PV

Use this activity to define countries for which you want the SAP postal code check to be performed before this product validates the rest of the address data.

This product can validate addresses even if the addresses do not contain a postal code. By default, this product disables a postal code check that SAP normally performs on the address before this product validates the rest of the address data. Disabling the SAP postal code check lets this product 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 this product needs a valid postal code before processing. Change this setting only if you want the SAP postal code check to be performed for a certain country.

1. In the Activate SAP Postcode Check Before Validation window, click the New Entries button.2. In the New Entries: Overview of Added Entries window, in the ISO Country Code Field, enter the two-letter ISO

code for the country for which you want a postal check performed before complete address validation occurs.3. Save the changes and exit the window.

5.1.6 IMG: Maintain Operating Parameters

Use this activity to modify operating parameters that affect the behavior of this product.

Operating Parameters

This table shows the operating parameters, the default values, and a description of each.

Table 30:

Parameter Default Value Description

ADD_REVIEW_FLAG X Flag to determine whether a window opens that lets the user review the original and modified address during postal validation. Valid values are X to receive this confirmation window or a space to not display the window.




AD_ADDRESS_FINISHED_FUNC_NM none Allows 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 Allows 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_BYPASS_DUP_AUT_CHECK none Allows bypassing the authorization group check for duplicate check results. “X” value activates this feature.

AD_BYPASS_SEARCH_AUT_CHECK none Allows bypassing the authorization group check for search results. “X” value activates this feature.

AD_CANDIDATE_FIELD_LIST_FUNC_N none Function module to execute during GET_CANDIDATES method. Used to add fields.

AD_REVIEW_NEW_WIDTH 35 Width by number of characters of the validated address column in the Postal Validation – Review Changes

AD_REVIEW_ORIG_WIDTH 25 Width by number of characters of the original address column in the Postal Validation – Review Changes window,letting you adjust the column size if addresses are too long to fit. window, letting you adjust the size of the column if addresses are too long to fit.

AD_SUPPORTED_COUNTRY_QTR X Determines whether to limit the quarterly update process to supported countries. Valid values are X or a space to remove this limit.

AD_USE_ADR2_ADR6_IN_MATCH_CODES none Determines whether to send ADR2 and ADR6 data to the Data Quality engine during batch match code generation. Valid values are X or a space to remove this limit.

BATCH_MATCH_RFC_DEST FL_GDQC_BATCH Dedicated RFC Server for handling duplicate search functionality in batch mode (called batch match). This value is also called the Program ID of the RFC Server.

DRVR_ADDR_IGNORE_NAME_MTC_CODE X By default, this product ignores driver name match codes if the driver address is present. To reverse this behavior, leave the parameter value blank.



ENABLE_DES_FUNC_NM none Administrator-specified function to enable or disable this product's duplicate error tolerant search (DES). A possible value is the name of a function module to call before executing this product’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 this product. If VALID is space, then only the SAP enterprise application's standard DES checks occur.

ENABLE_MATCH_CODE_FUNC_NM none Administrator-specified function to enable or disable this product's use of match codes. A possible value is the name of a function module to call before executing this product’s match codes. 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”

ENABLE_PV_FUNC_NM none Administrator-specified function to enable or disable this product's postal validation. A possible value is the name of a function module to call before executing this product’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 this product. If VALID is space, then only the SAP enterprise application's standard address checks occur.

MAX_ACT_DUPS 100 Maximum number of actual duplicates displayed to the user.

MAX_ELP_TM_DUPS 5 Maximum time allowed in seconds to find duplicates. The value must be 1 second or greater.

MAX_ELP_TM_DUPS_NON_DIALOG 10 Maximum time allowed in seconds to find duplicates in non-dialog mode. The value must be 1 second or greater.

MAX_REC_QU2 10000 Maximum number of records per package passed to the RFC Server during the quarterly adjustment report.




MAX_UPD_PEND 100 Maximum number of records that may be pending for update to the RFC Server when the RFC Server is unavailable. If the number of records pending exceeds this maximum, then the records are not updated automatically and require the pending record update report to be run.

NON_DIALOG_ERR_MSG space Toggles whether system messages are displayed in non-dialog mode. Valid values are “X” to enable passing of system error messages in non-dialog mode for postal validation or a space not to receive the system message.

PKG_SIZE_DUPS 1000 Package size for passing candidate duplicates to the RFC Server.

RFC_DEST FL_GDQC_SERVER Name of the RFC Server contacted through a Remote Function Call. This name must correspond to a valid destination that describes a functioning RFC Server.

STANDARDIZATION_REVIEW_FLAG none “X” indicates that standardization review screen will appear after processing.

TECH_ERR_FUNC_NM none Name of a user-defined function module that is called when a technical error occurs.

5.1.7 IMG: Maintain Fields for Address Reviewers

Use this activity to define the fields displayed in the address reviewer window and the order of those fields.

During postal validation, the system may modify address data to make it conform to the data in postal directories. If the system modifies the address data, it displays both the original and modified address data. The user can choose 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.


Default Fields

Table 31:

Street Addresses P.O. Box Addresses

By default, the following fields are displayed for standard street addresses, in this order:

1. HOUSE_NUM12. STREET3. CITY14. REGION5. POST_CODE16. COUNTRY

By default, the following fields are displayed for P.O. Box addresses, in this order:

1. PO_BOX2. POST_CODE23. PO_BOX_LOC4. CITY15. PO_BOX_REG6. REGION7. PO_BOX_CTY8. COUNTRY

Changing the Fields or Their Order

1. In the IMG, select Maintain Fields for Address Reviewer.The Maintain Fields for Address Reviewer window appears.

2. Select or de-select checkboxes in the Display for Street Addr and Display for PO Box columns.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.

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

4. Save the changes and exit the window.

5.1.8 IMG: Maintain Fields for Duplicate Hit List Displays

Use this activity to 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.



Default Fields

Table 32:

Error-Tolerant Search Duplicate Hit List

By default, the following fields are displayed in this order for error tolerant search.

1. Score2. Customer or Vendor or BusPartner3. Name4. Name25. Street6. City7. Region8. Postal Code9. Country

By default, the following fields are displayed in this order for duplicate hit list.

1. Score2. Last name3. First name4. House number5. Street6. City7. Region8. Postal Code9. Customer10. Vendor11. BusPartner

Changing the Error-Tolerant Search or Duplicate Hit List Display

1. In the IMG, select Maintain Fields for Duplicate Hit List Display.The Maintain fields for duplicate hit list display window appears.

2. Select or deselect checkboxes in the Display Flag (Search) and Display Flag (Dup.Check) columns.The fields checked appear in the duplicate check or error tolerant search window.

3. Type sequential numbers for all 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.

TipYou must number the fields in sequence from 1 to the total number of displayed fields.

4. Save the changes and exit the window.

5.1.9 IMG: Map Objects for Quarterly Error Report

This product provides the custom error report /FLDQ/AD_REPT_DISP_QTRERRORLOG to log invalid addresses found during the execution of Quarterly Adjustment Reports.

Use the Map Objects for Quarterly Error Report activity 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, saving the user the effort of finding each invalid address.


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 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 for the key field to serve as a hyperlink. Some of these mappings are predefined in this product 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

This product 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

Perform the steps described in the following section to add a mapping for any other address types.

Adding a Mapping

1. Run the /FLDQ/AD_REPT_DISP_QTRERRLOG report.2. Write down the following details for an entry for which the hyperlink does not work:

○ Address type○ 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 in the Performance Assistant window's menu bar.8. Note the Parameter ID value in the Field Data section.9. Use the IMG activity Map objects for Quarterly Error Report.



10. Click the New Entries button and fill in all three columns using the data you collected:

Table 33:

Entry Field

Address Type Code Object Type

Transaction Code Transaction for Edit

Parameter ID Object Parameter ID

11. Save.12. Repeat as necessary for each address that does not have a working hyperlink.13. Create a Customizing Request.

5.1.10 IMG: Activate/Deactivate Postal Validation Functionality

Use this activity to activate or deactivate the postal validation capabilities of this product for transactional processes. You may want to temporarily deactivate the postal validation capabilities for troubleshooting or maintenance.

TipWhen you run Quarterly Adjustment Reports, postal validation occurs even if you have deactivated postal validation functionality with this activity.

Related Information

Postal Address Validation [page 73]

5.1.11 IMG: Activate/Deactivate DES Functionality

Use this activity to activate or deactivate this product's duplicate check and error tolerant search (DES) capabilities. You may want to temporarily deactivate the duplicate check and error tolerant search capabilities for troubleshooting or maintenance.

In the IMG, select Activate/Deactivate DES Functionality. In the window that opens, read the message carefully, and select the appropriate action to activate or deactivate DES functionality.


5.1.12 IMG: Activate/Deactivate Creation of Match Codes

Use this activity to activate or deactivate the creation of match codes for this product. You may want to temporarily deactivate this feature for troubleshooting or maintenance.

5.1.13 IMG: Activate/Deactivate Standardization Functionality

Use this activity to activate or deactivate the client-specific name standardization capabilities of this product. You may want to temporarily deactivate these capabilities for troubleshooting or maintenance.

To select or deselect standardization for Organization Name or Person Name, check or uncheck that option's checkbox.

If you want to be able to review and accept or reject transactional suggested changes, then you will also need to enable the SAP BusinessObjects Data Quality Management IMG activity Maintain operating parameters STANDARDIZATION_REVIEW_FLAG value.

5.1.14 IMG: Identify Search Fields

Use this activity to identify the region and country fields to use for error tolerant search by making changes to the TSAD10 table.

1. From the IMG, select Identify Search Fields.The Indexable address fields for duplicate check window appears, showing the TSAD10 table.

2. Check all six (6) boxes for the fields Region and Country to activate them for use.3. Save your changes.

The region and country fields are now available for the data quality operations of this product.

5.1.15 IMG: Maintain DQM Region Mappings

Use this activity to maintain the region mappings for this product through the Region Mapping Table.

Regions are data fields that could be states for U.S. addresses, provinces for Canadian addresses, and so on.

The mappings between the SAP system and Data Services reside in the table /FLDQ/DQ_REGIONS. This table holds a default configuration that provides mappings for many regions of many countries, letting you reconcile differences between the SAP system’s region data and Data Service’s region data.

Region Mapping

A complete and correct region mapping consists of the following characteristics:



● For a specific country there is an entry in the T005S table for the country/region code.● There is a corresponding entry in the Regions table with the same country/region code.● The SAP system’s country/region code in the Regions table maps to the country/region code Data Services

provides.

A correct mapping is one in which the value of BLAND (Region code) in the T005S table has an equal value in the SAP_REGIONCODE field of the Regions table. In addition, the value of the ISO_COUNTRYCODE and ISO_REGIONCODE in the Regions table holds the correct corresponding Data Services value.

In the Regions table, each section consists of the following possible entries:

Table 34:

Entry Description

SAP_COUNTRYCODE 2-character ISO country code for the entry, according to the T005S table (T005S-LAND1).

SAP_REGIONCODE 2-character SAP region code for the entry, according to the T005S table (T005S-BLAND).

ISO_COUNTRYCODE Country code as it is known in Data Services.

ISO_REGIONCODE Region code as it is known to Data Services.

DQ_REGIONNAME Optional.

ExampleA complete mapping for the state of Wisconsin in the United States would have these elements.

In the T005S table, the entry would be similar to this example.

Table 35:

MANDT LAND1 BLAND FPRCD HERBL BEZEI

100 US WI 55 Wisconsin

The relevant fields for this table are:

● LAND1: Country● BLAND: Region Code

In the Regions table, the entry would be similar to this example.

Table 36:

SAP_COUNTRYCODE SAP_REGIONCODE ISO_COUNTRYCODE ISO_REGIONCODE

US WI US WI

NoteCasing of these entries is important. In some SAP systems, “wi” is not the same as “WI”.

All of the maintenance for region mappings occurs in these two tables. In all cases, either an entry is missing from one of these tables, or an entry must be corrected. Often, the choice depends on existing entries.

The report /FLDQ/RSREGIONRPT provides a description of where the entries exist and are not present for each section.


You must correct only the mappings for regions that are relevant to your business needs. For example, if your organization does not perform business with a region in a certain country, you do not need to correct the mappings regions in that country. The report displays a list of all possible regions that could be mapped for your system’s Support Countries.

5.1.16 IMG: Maintain Customer Address Reviewer Labels

Use this activity to customize the wording of the labels on the address reviewer screen.

Customized labels are maintained in the table /FLDQ/AD_RVW_CUS. In this table, you specify the following:

● Language● Table name● Field name● Medium field label

The standard labels are stored in the /FLDQ/AD_RVW_LBL table. You can look at this table to discover the table name and field name of the label you want to replace.

To determine which label to display, the system reads labels in the following order:

● Customized label from /FLDQ/AD_RVW_CUS in current logged on language● Customized label from /FLDQ/AD_RVW_CUS in the default language (English)● Standard label provided by default with this product as defined in the table /FLDQ/AD_RVW_LBL

5.1.17 IMG: Maintain Suggestion List Labels

Use this activity to change the text displayed for Suggestion Lists labels. Before making any modifications, you must identify the following fields:

Table 37:

Field Description

Address Either a postal address, a street address, or a dual address (both street and P.O. Box in one address).

Lang Language setting to which this field applies.

SuggListId The type of Suggestion List to which the label applies. Refer to /FLDQ/AD_SUGLIST for a description of each SUGG_LIST_ID.

Field Name The name of the Suggestion List to which the label applies.

Field Label The text to be displayed for a particular Lang, SuggListId, and Field Name combination.

Changing a Suggestion List Label

1. Locate the desired field to be changed for the Suggestion List type.



2. Change the Field Label field.3. Click Save.

5.1.18 IMG: Maintain Suggestion List Fields to Display and Order to Display

Use this activity to change the fields that are shown on Suggestion List screens and the fields' order.

In the Address Type field, select whether this is applicable for a street or P.O. Box address.

In the Suggestion List ID field, choose the appropriate type of suggestion list. See the list and table /FLDQ/AD_SUGLIST for description of possible entries.

For the remaining fields, select the fields that you want to display by clicking the Display checkbox and entering an ordinal value (left to right) for columns to display.

5.1.19 IMG: Maintain Customer-Defined Standardization Reviewer Labels

Use this activity to customize the wording of the labels on the name and organization reviewer screen.

Customized labels are maintained in the table /FLDQ/DC_RVW_CUS. In this table, you specify the following:

● Language● Table name● Field name● Medium field label

The standard labels are stored in the /FLDQ/DC_RVW_LBL table. You can look at this table to see the table name and field name of the label you want to replace.

The system reads labels in the following order to determine the label text to display:

● Customized label from /FLDQ/DC_RVW_CUS in current logged on language● Customized label from /FLDQ/DC_RVW_CUS in the default language (English)● Standard label provided by default with this product as defined in the table /FLDQ/DC_RVW_LBL

5.1.20 IMG: Maintain Standardization Reviewer Fields

Use this activity to choose the fields to display in the person and organization reviewer screens and the fields' order.

To select or deselect a field, check or uncheck that field's checkbox.

To change the order in which the fields are listed, change the number assigned in the far-right column. For example, 1 means that field is listed first on the screen.


5.2 Other Optional Setup

5.2.1 Installing and Configuring Into WebClient for CRM

Follow the instructions in this section to install the functionality of this product into a CRM IC WebClient or CRM WebClient environment, CRM version 7.0 or CRM 2007

Requirements for Running in a WebClient Profile

Refer to these SAP Support Notes to determine if additional configuration or support packages are necessary for your SAP CRM 2007 or CRM 7.0 configuration.

Table 38:

Note Description

1250600 Postal Validation for Business Partner Address.

1286002 CRM WEB UI: Country gets erased on saving.

1299693 Postal Validation: Saving of correct address.

1300236 CRM WebUI : Country gets erased on saving.

1340952 Address validation: address not taken over from popup.

1351582 Address validation: address not taken over from popup (regarding double save).

1356120 In the Account Identification, when trying to create and save a duplicate record, the save is not possible. A unique record, however, can be saved.

1359568 Account/Contact Creation: Address Validation + Direct Save.

1384111 Exception saving related partner.

1376561 Duplicate Check on Create Contact Person screen.

1384877 At End: Database update failed. Rollback has been triggered.

1378301 Address validation & duplicate check on More Fields.

1371528 Address Validation & Duplicate Check.

Configuration Procedures

To install the functionality of this product 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. You must complete the following procedures:

1. Activate the BSP-PV BC Sets on the target client. See Activating Business Configuration Sets.2. Create an Enhancement Set. See Creating an Enhancement Set.3. Enhance the component. See Enhancing the Component.



Related Information

Activating Business Configuration Sets [page 41]Creating an Enhancement Set [page 65]Enhancing the Component [page 65]

5.2.1.1 Creating an Enhancement Set

1. Go to transaction SM34.The View Cluster Maintenance window appears.

2. Enter View Cluster name BSPWDVC_CMP_EXT.

3. Click the Maintain button. (Dismiss any caution message that may appear.)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.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.

A new Enhancement Set is created and assigned to the client.

5.2.1.2 Enhancing the Component

To find the name of the Component, click an address field in any window in which you can enter address data, and press F2. In the window that opens, see UI_Component, the Component name used for addressing.

1. Go to transaction BSP_WD_CMPWB.2. Enter the names of the Component and the Enhancement Set.3. Click Display.4. Click the Runtime Repository Editor tab.5. Click Edit.6. Expand the Component Usages menu item.7. Click the Change button.8. Right-click Component Usages and select Add Component Usage.


9. In the Create Component Usage window, enter the following:

Field Value You Enter

ID PostalValidationUsed Component /FLDQ/DQXI_PVInterface View /FLDQ/DQXI_PV/DQXI_PV

10. Save and exit.

The Component is now enhanced.

5.2.2 Configuring Geocoding

If you purchased the Geocoding option and directories, you can configure this product to return latitude, longitude, and relevant status information for an address record.

To configure geocoding for your business partner records, follow the instructions in this section.

Configuring the Geocoding Job as a Service

In Data Services, you must configure the geocoding job as a service, as you did with the other jobs during installation of the Data Services components.

The geocoding job name is Job_Realtime_DQ_SAP_Address_Global_GEO.

Make the geocoding service name Service_Realtime_DQ_SAP_Address_Global_GEO.

For information about configuring a job as a service, see Configuring Jobs as Services.

Starting Real-Time Service for Geocoding

To use geocoding, you must configure and start the service in the Data Services Management Console.

1. 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 the geocoding service click Start.

NoteYou can also disable the geocoding service with this procedure if it is not needed. Select the geocoding service you want to disable and click Disable.



Configuring the RFC Server to Enable Geocoding

For information about enabling geocoding on the RFC Server, see Configuring the RFC Server [page 38].

Registering the Geocoding Program in the SAP System

You must 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. Click New Entries.3. Enter these values for the fields:

Table 39:

Field Value

Source ID FLDQ

Class /FLDQ/CL_DQ_ENGINE_BASE

Function Module ADDR_GEO

Destination FL_GDQC_SERVER (The default value for the Destination is FL_GDQC_SERVER.)

4. Save the entry.

Configuring Each Country for Geocoding

You must configure each country for geocoding.

1. From the IMG, navigate to General Settings Set Geo-Coding Assign Geo-Coding Program to Countries .

2. Click New Entries .3. Create a new line for the country (for example US).4. For the Source ID, enter SAP1.5. Enter a value for the sequence. If a line already exists for that country code, select a number smaller than the

existing line.6. Set the exclusive flag.7. Repeat for each country for which you want to configure geocoding.8. Save the entry.


Designating Fields to Use for GeoCoding

When trying 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 when determining latitude and longitude.

Follow the steps below to specify the fields to use for geocoding, which allows the non-designated fields to be changed without re-sending data to the geocoding program.

1. From the IMG, navigate to General Settings Set Geo-Coding Assign Relevant Address Fields for Geo-Coding .

2. Click New Entries .3. In the Address Fields Relevant for a Geo-Coder table, enter for the Source ID FLDQ and enter a field to use as a

default field for geocoding (for example, COUNTRY).4. Repeat to create other entries for any additional fields you want to use as a default field for geocoding (for

example, REGION or STREET).5. Save the entry.

Related Information


5.2.3 Configuring Name and Organization Cleansing for MDG

Several more steps are needed if you plan to perform name and organization cleansing in your MDG environment.

SAP Note

Refer to this SAP Note to perform additional required setup.

Table 40:

Note Description

2184328 You configured enrichments for MDG entities that run as part of the check cycle. The UI does not show the enriched value.




Define the Data Quality Enrichment Spots

NoteWhen you import the BAdl from the latest support package, these values should be populated. You can confirm this, or edit the values if necessary, by following the steps below.

1. Execute transaction MDGIMG.2. Under Master Data Governance > General Settings > Data Quality and Search > Validations and Enrichments,

execute Define Enrichment Spots.3. In the Change View "Enrichment Spot": Overview window, create a new Enrichment Spot as shown below, if it

does not already exist:

Table 41:

Enrichment Spot Enrichment Feeder Class Description

ENRICH_DATA_CLEANSE /FLDQ/CL_DQM_NAME_FEEDER DQM MDG Enrichment Spot

4. Navigate to the Enrichment Adapters View window, and create a new Enrichment Adapter as shown below, if it does not already exist:

Table 42:

Enrichment Adapter Enrichment Adapter Class UI Component Description

ENRICH_DATA_CLEANSE /FLDQ/CL_DQM_NAME_FEEDER /FLDQ/CL_DQM_NAME_UI DQM MDG Enrichment Adapter

5. Navigate to the Enrichment Adapters Assignment View window, and create a new Enrichment Adapter as shown below, if it does not already exist:

Table 43:

Enrichment Adapter

DATA_CLEANSE_ADAPTER

Configure the Change Request Step Properties

1. Execute transaction MDGIMG.2. Under Master Data Governance > General Settings > Process Modeling > Change Requests, execute Configure

Properties of Change Request Step.3. In the Display View "Type of Change Request": Overview highlight the type of change request to activate name

cleansing, such as SUPPL1P1.4. Right-click Change Request Step in the Dialog Stucture on the left side of the display, and choose Choose

Subdialog.5. Highlight 00 Submission.6. Right-click Enhancements and Checks per Change Request Step and choose Choose Subdialog.7. Set the Relevant checkbox to checked for DQM MDG Name/Title Enrichment.


5.2.4 Configuring Address Output Field Format

The combine_house_num option of each job allows you to determine how this product handles house number data for that job.

The following table lists the options that control how address line data (street data) is output to the fields of your SAP system for the substitution variable $$DQ_SAP_Output_Format_Address_Line.

The substitution variable $$DQ_SAP_Output_Format_Address_Line controls how address line data (street data) is output to the fields of your SAP system. The following table lists the options.

Table 44:

Option Description

1 (default) This option outputs data is put into separate fields. There is no combination of fields.

2 This option outputs all address data to the Street field.

3 This option combines primary name and secondary data and outputs to the street field.

4 This option combines primary range and primary name data and outputs to the street field. All other data is separated.

For all countries, all other extra address data that is not validated by this product is output STR_SUPPL2.

You must restart the service after changing this setting.

5.2.5 Adding the PO Box Lobby Field

Validated Canadian PO Box addresses may return a delivery installation that we will display in the SAP PO Box Lobby field. If you expand the BP transaction PO Box fields and do not see the “PO Box Lobby” field, follow these steps to display that field.

Steps to create a field group

1. Go to BUS2 transaction.2. Scroll down the list and find an available unused field group number (for example, 2128).3. Click New Entries.4. Complete the following:

Table 45:

Option Description

Field Group Enter the number you identified in step 2 above.

Description Enter Address:PO Box Lobby

FM for fld grouping Enter BUA_BUPA_EVENT_FMOD2



Option Description

Changes plannable Select this option.

5. Click Save.6. Go to BUS2 transaction.7. Click the Position button.8. Enter the field group number that you used in steps 2 and 4 above.9. Select the Row.10. Right-click Field Group->Fields, and select Choose Subdialog.11. Create new entries with following table name, field name, and input field checked:

○ Table Field name Input field ADDR1_DATA PO_BOX_LOBBY (checked)○ ADDR2_DATA PO_BOX_LOBBY (checked)

12. Click Save.13. If you see a “Field name doesn’t exist on subscreen” message, press Enter and ignore.

Steps to assign field group to a view

1. Go to BUS3 transaction.2. Select view “BUA100”(“ Address: Usages”).3. Right-click View->Field groups and select Choose Subdialog.4. Click New Entries.5. Give the created field group no.6. Click the Save button.

5.2.6 Configuring the Use of Multiple Back-End Engines

You can configure SAP Data Quality Management, version for SAP Solutions to handle certain types of processing or records from certain countries with a specific engine.

If you own or have the rights to use multiple engines (Data Services, HANA, and/or SAP Data Quality Management, microservices for location data), you may want to specify that certain types of processing be handled by one of those engines, and all other processing be handled by a different engine, for example.

Another likely scenario is that you have the Data Services or HANA engine perform postal validation for those countries for which you own reference data. And then have the cloud-based microservices product perform postal validation and geocode processing for those countries whose reference data you do not own.


Table 46: Data Quality Operations

DQ Operation Is This DQ Operation Supported by This Engine?

HANA Data Services Data Quality Management, microservices for location data

GEO (assign geocodes) yes yes yes

MATCH (identify matching records) yes yes no

NAME (person and organization name cleanse) yes yes no

PV (postal validation) yes yes yes

PV_BATCH (batch postal validation) yes yes no

To configure the use of multiple back-end engines, follow these steps:

1. Enter task sm30.2. Enter the table /FLDQ/DQ_ENGINES and click Maintain.

The engine listed with no country (Ctr) or data quality (DQ) operation specified is the default. This engine will handle processing for all countries and operations that are not otherwise specified in this table.

3. To set up country-specific processing, click New Entries, choose a country (Ctr), specify a data quality (DQ) operation, and press F4 to choose the engine. Save your change.

Table 47: Engines

SAP Data Quality Management, microservices for location data /FLDQ/CL_DQ_ENGINE_DQAAS

Data Services /FLDQ/CL_DQ_ENGINE_DS

HANA /FLDQ/CL_DQ_ENGINE_HANA_TASK

4. To set up operation-specific processing with no country associated, click New Entries, specify a data quality (DQ) operation, and press F4 to choose the engine. Save your change.

5. Set up all country-specific and operation-specific processing that you need, and save your changes.



6 Postal Address Validation

Postal address validation standardizes and corrects address data, protecting the quality 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, this product 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.

6.1 Interactive Address Cleansing

This product'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.

For interactive address cleansing, the SAP user needs to take no additional action. The data is cleansed automatically when the user saves the record or clicks the Check Address button.

When the user creates a record that contains invalid data and attempts to save the record, the cleansing takes place in real time.

If this product discovers one corrected address to suggest, the following options are presented:

Table 48:

Button Action

Accept Validated Address The previous window returns to focus with the corrected data populating the fields. Check status is set to C.

Use Original Address The previous window returns to focus with the data as originally entered populating the fields. Check status is set to D.

Cancel The previous window returns to focus and the process is cancelled. Check status is not changed.

If this product discovers two or more corrected addresses to suggest, the following options are presented:

Table 49:

Button Action

Select The Review Address Validation appears with the selected/validated fields, or another suggestion list window appears if further address components have more than one option.

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

Skip The Review Address Validation window shows address components that have been validated up to this step. This option is available only for addresses that are validated up to a primary or secondary range, and is not available for addresses that are input with a wildcard (*) character.

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

User Guide for connecting to SAP Data ServicesPostal Address Validation C U S T O M E R 73

6.2 Batch Address Cleansing With Quarterly Adjustment Reports

This product accomplishes batch cleansing of postal addresses through Quarterly Adjustments. You first run Quarterly Adjustments with this product’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 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 this product installed, to run a Quarterly Adjustment Report you would execute the defined SAP reports RSADRQU1, RSADRQU2, and RSADRQU3. Installing this product 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 this product.

Optionally, you can then run the report /FLDQ/RSADRRVW to view the differences between the original and validated records before committing to the changes through the RSADRQU3 report. Then the validated and updated addresses are committed to the SAP database.

You must repeat the entire procedure for running Quarterly Adjustments for each target (non-000) client as part of this installation.

Run the reports in this order:

1. RSADRQU12. /FLDQ/RSADRQU23. RSADRQU3 to accept or reject all changes or /FLDQ/RSADRRVW to display, review, and accept individual

changes

After you run Quarterly Adjustments, you should run the Initial Match Code (Index) Setup program.

6.2.1 Report RSADRQU1

You use report RSADRQU1 to select the addresses that are to be cleansed.

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. Use a packet size of 1000.

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.


Postal Address Validation

7. Select the radio button to Exclude, Check additionally, or Check separately addresses that have not previously been subjected to postal validation. This setting determines which records are included in postal validation processing.

8. Select the appropriate radio button either to Cancel the Quarterly Adjustment if INDX exists or to Overwrite the existing INDX. If the Quarterly Adjustment is terminated for some reason and you want to start it again, you must select Overwrite 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.

9. Click the Execute button (F8) to run RSADRQU1.

The report runs and a confirmation window appears.

6.2.2 Report /FLDQ/RSADRQU2

Before running this report, you must run report RSADRQU1.

Instead of running the 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.2. In the Program field, enter /FLDQ/RSADRQU2 and click the Execute button (F8).

3. Choose a processing mode:

Option Description

View Only Standard batch method of cleansing with all or nothing commit to address master data.

Approve/Reject Batch method of cleansing with enhanced ability to selectively approve or reject proposed address changes.

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

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.

5. Check the Skip D records during the Quarterly adjustment process box only if you want to run postal validation without checking D records.A D record is a record that has its check status set to D. There are three possible check status values.

Option Description

C Postal or address data is known and does not contain any error

D Postal or address data may have errors

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

6. Set up the multi-process options as needed:

Option Description

Available DQ Instances

The number of data quality processes available. This is equal to the number of RFC Servers attached to the SAP system.

Available Work Process

The number of work processes available for the program to use for parallel processing.

Maximum Concurrent Tasks

The maximum number of processes the program can use for parallel processing. It is the lesser between the number of RFC Servers and the number of work processes available on the application server.

A confirmation window appears. If any records failed during validation, those records are shown.

6.2.3 Report RSADRQU3

Before running RSADRQU3, you must run the reports RSADRQU1 and /FLDQ/RSADRQU2.

You use report RSADRQU3 to commit updates to the SAP database with the validations performed in the Quarterly Update report.

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

1. Start the report RSADRQU3 by running the transaction code SA38.2. In the Program field, enter RSADRQU3.3. Click the Execute button (F8).

A confirmation window indicates 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 (/FLDQ/AD_REPT_DISP_QTRERRORLOG), which provides you a hyperlink to each of these records so that you can directly edit each record as necessary.

If the report ends 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-system report, you must have the RFC Server running to process records from the pending update table.

CautionWhile 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



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

6.2.4 Batch Address Cleansing Reviewer (/FLDQ/RSADRRVW)

Review address changes proposed by Quarterly Adjustments.

Use the /FLDQ/RSADRRVW report to view address cleanse results and act on them.

1. Run transaction code SA38.2. In the Program field, enter /FLDQ/RSADRRVW and click the Execute button (F8).3. Set up filters and other options as needed:

Table 50:

Option Description

Address numbers to process Enter the range of address numbers to process. Leave blank to show all.

Country Enter range(s) of address country codes to process. Leave blank to show all.

Region Enter range(s) of address region (state/province) codes to process.

Status Code Enter range of address engine status codes to display Leave blank to show all.

Approved/Rejected By Enter logon user to limit display to (leave blank for all)

Do not show Approved proposals

Exclude records that the user already reviewed and approved.

Do not show Rejected proposals

Exclude records for which the user already reviewed and rejected the proposed address changes.

Page size Enter the number of records to show on a single screen.

At the bottom of the screen, you can see the available range of address numbers and the number of changes that will be displayed based on your filter and other option settings.

4. Click Update number of changes displayed to refresh the number of changes shown.5. Click the Execute button to display the interactive reviewer tool.

The reviewer tool shows all records that match your filters. For each record, you see the current and proposed data, and you can choose to approve or reject the changes, and navigate the records using the following options:

Table 51:

Option Description

Prev Page (up arrow) Displays the previous logical page from the DB table.

Next Page (down arrow) Displays the next logical page from the DB table.

Approve Sets the highlighted address to Approved.

Reject Sets the highlighted address to Rejected.

Approve Pg Sets all records on the page to Approved.

Reject Pg Sets all records on the page to Rejected.


Option Description

Commit Pg For each approved row on the screen, updates the master data with the proposed changes and then deletes this BP proposal from the review table.

Commit All For each approved row in the review DB table (not just on the current page), updates the master data with the proposed changes and then deletes this BP proposal from the review table.

Reject All For each approved row in the review DB table (not just on the current page), sets all proposed changes to Rejected.

Approve All For each approved row in the review DB table (not just on the current page), updates status to Approved.

Reset All For each approved row in the review DB table (not just on the current page), updates status to Initial. Once committed, the records are removed from the address change proposals table.

6.2.5 Quarterly Adjustment Custom Error Report (/FLDQ/AD_REPT_DISP_QTRERRORLOG)

This product provides a custom error report, /FLDQ/AD_REPT_DISP_QTRERRORLOG, which shows address validation errors that occurred during all Quarterly Adjustment runs since the last time you cleared the previous error codes.

1. Run 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 Quarterly Adjustment Error Log window appears. You can set limits to filter and sort the displayed results.

3. Set any filters and click the Execute button (F8).An error log shows a list of records on which postal validation errors occurred.

NoteYou can customize this report by making each address listed in the report a hyperlink to the editable address entry. This saves the effort of manually entering the transaction and locating each invalid address for editing. To do this, use the IMG activity Map Objects for Quarterly Error Report.

Related Information

IMG: Map Objects for Quarterly Error Report [page 57]



7 Duplicate Checking and Error-Tolerant Searching

This product's duplicate check and error tolerant search 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.

Duplicate check is the process that ensures 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 allows users to find customer records using partial information. Based on the partial information provided by the user, this product 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.

7.1 Break Keys (Match Codes)

A break key is the search index for each record that this product uses to search for similar, possibly matching, candidate records. A break key contains 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.

NoteIn some areas of this product, the term match code is used instead of break key. The terms are interchangeable in this product. Data Services always uses break key.

When given input data during duplicate check and error tolerant search, this product limits the number of records used in the search by determining a break key for the data. It then considers only stored records with the same break key value as the input data when searching for duplicates.

NoteThis process changes when this product is configured to include records with empty break key values. Some records may not have a break key associated with them (in other words, an empty break key). Some may have break keys for name data but not address data, or vice versa. On the one hand, including records that have empty break keys during postal validation or duplicate search slows processing because there are more records to examine. On the other hand, including records that have empty break keys helps this product return appropriate records.

Included in this product are five best practices break keys that you can use to create the match codes to be used in finding similar records. You can change the match code to alter the matching results produced.

User Guide for connecting to SAP Data ServicesDuplicate Checking and Error-Tolerant Searching C U S T O M E R 79

Installing the Data Services Components of this product places in your Data Services installation the job DQ_SAP_Break_Key_Profiler. This job can process the data in your SAP system and recommend what match code would give the best results along with other configuration recommendations. For information about DQ_SAP_Break_Key_Profiler, see the section Understanding the Break Key Profiler.

By default, this product uses a moderate break key that offers good performance and completeness of results for a wide set of data. The default break key uses the two character country code, the first five alphanumeric characters of the postal code and the first letter of the street field to generate the break key value. To improve the results during a search, this product requires data for the street and postal code fields so that the appropriate records can be used in the matching process.

For example, to search for a customer who you know lives on Main Street in La Crosse, Wisconsin, you would enter the following information in the search window:

Field Data

Street Main St

Postal Code 54601

The break key value for this input data is US54601M. The search process selects all of the records from the SAP system that have the break key value US54601M. The search process then compares the input data to each record selected using the matching rules set up on the RFC Server.

To illustrate the importance of providing data in the two fields used to determine a break key, imagine that you entered the following information in the search window:

Field Data

Street <blank>

Postal Code 54601

The break key value would be US54601 and only records with a break key value of US54601 would be selected for searching. This result would not include the record you were searching for because that record has a break key value of US54601M.

NoteDuring duplicate search, this product performs postal validation on the input data before performing the search. If this example had been for duplicate search specifically, the postal code left blank, but street, city, and region data were complete, then this product could validate the data and determine the postal code. The corrected data would then be assigned the appropriate break key of US54601M, even though you did not directly enter the postal code.

Related Information

Break Key Profiler [page 122]


Duplicate Checking and Error-Tolerant Searching

7.1.1 Changing the Break Keys (Match Codes)

You can change the match code to one of the others provided.

1. In the Data Services Designer, select Tools Substitution Parameter Configurations .The Substitutions Parameter Editor opens.

2. In the Substitution Parameter Editor, update substitution value $$DQ_SAP_Match_Function. Valid entries are the following.

○ MatchCode1○ MatchCode2○ MatchCode3○ MatchCode4○ MatchCode5○ MatchCodeCustom

For a description of these best practices match codes, see the section Best Practices Match Codes .

If you change the match code, you must run the initialization program to update the match code entries in this product’s match code table. For information on running the initialization program, see the section Run the Initial Match Code (Index) Setup program.

Related Information

Best Practices Match Codes (Break Keys) [page 128]

7.1.2 Configuring Break Key Settings

The regular break key settings can be configured in the Data Services job Job_Realtime_DQ_SAP_Create_Break_Keys. This job does not use first names in the creation of break keys, and is both the default and recommended method of creating break keys. It is set to run when you install this product. If you want to use this job with extra data fields, you can configure it to do so.

This product provides an additional job that uses first names in the creation of break keys, Job_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName. Because first names are typical, this job is suited only to special circumstances for duplicate check operations, probably using a smaller and more relevant candidate set than with the default job.

Further, you can change the default break key calculation by using a custom function.

For general information about configuring a Data Services job, see the Data Services documentation.


7.1.2.1 Substitute Jobs Without Postal Validation

If you did not purchase the postal validation capabilities of this product but intend to perform duplicate check and error-tolerant search, you must substitute the two standard Data Services jobs involving break keys with versions that are designed to be used in this scenario. If you use postal validation, you need not perform this substitution.

Substitute the following standard jobs involving break keys with these alternative versions.

Break key job with postal validation Alternative for no postal validation

Job_Realtime_DQ_SAP_Create_Break_ Keys Job_Realtime_DQ_SAP_Create_Break_ Keys_No_PV

Job_Realtime_DQ_SAP_Create_Break_ Keys_With_Firstname Job_Realtime_DQ_SAP_Create_Break_ Keys_With_Firstname_No_PV

You must map these jobs for customers that do not use postal validation to the same services normally used by the jobs they replace.

Job Service Name

Job_Realtime_DQ_SAP_Create_Break_ Keys_No_PV Service_Realtime_DQ_SAP_Create_ Break_Keys

Job_Realtime_DQ_SAP_Create_Break_ Keys_With_Firstname_No_PV

Service_Realtime_DQ_SAP_Create_ Break_Keys_With_Firstname

For the procedure to configure a Data Services job as a service, see the section Configure Jobs as Services.

7.1.2.2 Configuring Break Key Settings With Extra Fields

You can use additional fields for matching by modifying the $$DQ_SAP_Match_Function substitution parameter to the value MatchCodeCustom. The custom match code has preconfigured logic to include data such as telephone numbers, email addresses, and two other extra, customizable fields.

To use the extra, customizable fields in Job_Realtime_DQ_SAP_Create_Break_Keys, you must create two function modules for your SAP system.

The system calls the first function module when a match code is created for a new or updated record. This process allows you to put additional data into the table that is sent 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, because 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 lets you 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.

7.1.2.3 Creating Break Keys Using First Names: Changing the RFC Server Configuration

Next, you must change the RFC Server configuration. For detailed information about this configuration file, see the section Configuring through flrfcsrv.xml.

1. In the RFC Configuration file <install_directory>\config\flrfcsrv.xml, comment the tag <break_key>Service_Realtime_DQ_SAP_Create_Break_Keys </break_key>.The tag should now appear as follows: .

2. Uncomment the tag .The tag should now appear as follows: <break_key>Service_Realtime_DQ_SAP_Create_Break_Keys_With_FirstName</break_key>

3. Save your changes and restart the RFC Server.

The method of restarting the RFC Server varies depending on your operating system and, within Windows, whether you run the RFC Server as a Windows Service.

Related Information

Starting and Stopping the RFC Server [page 37]

7.1.2.4 Changing Default Break Key Calculations With a Custom Function

You can change the default break key calculations by modifying custom function CF_DQ_SAP_Calculate_Match_Code_Custom in the Data Services Designer.

Within DF_Realtime_DQ_SAP_Create_Break_Keys, go to the Build_Address_Match_Codes transform, which is where the Match_Code1 is created. The function CF_DQ_SAP_Calculate_Match_Code_Custom is where the custom match code is calculated, and this function uses the extra five fields available to this dataflow 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;

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

7.2 Duplicate Check

You can use duplicate check in interactive mode and, for Business Partner data, in batch mode.

7.2.1 Interactive Mode

When you create a new entry in the SAP database for a customer, vendor, or business partner, this product 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.



In response to your attempt to save a new record, this product 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. You can then choose from these options:

Table 52:

Option Description

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

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

Display Partner Shows the master record, but keeps the duplicate hit list.

Cleansing Case (SAP GUI only) Creates a cleansing case for any of the duplicates identified and flags the record for saving.


The window for the IC WebClient presents these options:

Table 53:

Option Description

Choose Chooses the selected duplicate record.

Merge (CRM WebClients only) Calls a new window to allow you to merge the duplicate record with the master record.

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


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 the section Maintain fields for duplicate hit list display for information about the default settings and the procedure for making changes to the fields displayed within the SAP GUI.

7.2.2 Batch Mode

If you are running one or more batch RFC Servers, you can use duplicate search in batch mode (called batch match) to find duplicate records in your Business Partners database. The default configuration of this product is suited to run a single batch RFC Server, but running multiple batch RFC Servers allows you to take advantage of multithreading for increased performance.

Running multiple batch RFC Servers requires adjustments to the default configuration.

7.2.2.1 Configuration Settings for Multiple Batch RFC Servers

Configuring a system with multiple batch RFC Servers for optimal performance requires making decisions regarding some other settings.


For however many batch RFC Servers you run, you ideally should run a larger number of work processes in the SAP system. Also, use the PARALLEL_PROCESS_ GROUP configuration option to specify the work process group to use. For more information about the PARALLEL_PROCESS_ GROUP configuration option, see IMG: Maintain Operating Parameters.

In Data Services, setting the maximum instances for Service_Realtime_DQ_SAP_Create_Break_Keys to the number of batch RFC Servers often provides optimal performance. However, the higher the number of work processes and maximum instances you allow, the more computing resources are consumed on those systems. Finding the optimal balance among these configuration settings may require some testing.

For example, consider these sample results from one series of tests. (Your results will vary depending on your system and configuration).

Table 54:

Batch RFC servers

Work processes Service maximum instances

Performance results

3 4 1 Data Services is where the performance bottleneck is located because it can process only one instance.

1 4 3 Batch RFC Server is where the performance bottleneck is located because only one server must handle all processing.

3 1 3 Not enough work processes, causing the performance bottleneck. One work process is sending information to three different batch RFC Servers.

Each of these options produces a performance bottleneck because one of the components can only process one packet at a time, giving little performance increase.

Instead, you might try three batch RFC Servers and five work processes. A good estimate would probably be to use three maximum instances for Service_Realtime_DQ_SAP_Create_Break_Keys. The best result can be found only by testing.

You can also increase the maximum instances in Service_Realtime_Batch_DQ_SAP_Name_And_Address_Match from the default of one to two if you have ample resources on the Data Services machine. Doing so would give limited performance increases if you have running the batch match option in this job.

In addition to these settings, you must also decide how to set the maximum concurrent tasks on the SAP system. The maximum concurrent taks defines the limit on how many work processes this match report can use. The report sets the highest value that can be supported, but you can change that value if you prefer to reduce the demands on the system (perhaps because there are other processes that have to share these resources).

TipYou must ensure that the RFC Servers are dedicated to the proper SAP Gateway for batch mode to work.

Related Information

IMG: Maintain Operating Parameters [page 52]



7.2.2.2 Preparing Data Services to Work With Multiple Batch RFC Servers

For Data Services to operate in a configuration of multiple batch RFC Servers, you must increase the number of minimum and maximum instances of the break key service, Service_Realtime_DQ_SAP_Create_Break_Keys to equal the number of batch RFC servers. To set this option:

1. In the Data Services Administrator, navigate to Real-Time <[machine name]> Real-Time Services .

2. Select the Real-Time Services Configuration tab.3. Select Service_Realtime_DQ_SAP_Create_Break_Keys.4. Set the minimum instances and maximum instances values to the number of batch RFC Servers you intend to

run.

When you save the configuration, the services restarts. You must adjust this setting each time you change the number of batch RFC Servers.

7.2.2.3 Initial Match Code (Index) Setup and Batch Match Report (/FLDQ/RSADRINIBM)

The /FLDQ/RSADRINIBM program is used both to run batch match and also to run the initial match code setup.

The following instructions explain both scenarios -- initial match code setup and batch match. You simply select different options, depending on whether you're performing match code setup or batch match.

NoteThe Initial Match Code Setup report provided in previous releases, /FLDQ/RSADRINI, is now deprecated and should no longer be used. Use /FLDQ/RSADRINIBM instead. /FLDQ/RSADRINI is still available for those cases where Enhancement Spots have been implemented to modify the report’s functionality. In all other cases, use the new report as described below.

● Run the Initial Match Code (Index) Setup program on each target (non-000) client.● Initial Match Code Setup is required for all installations of this product that use Duplicate Check — Error

Tolerant search.● Initial Match Code Setup prepares your existing data for matching with duplicate check and error tolerant

search.● Once you have run initial match code setup, you need not run it again unless you have made changes to your

match code configuration.● Before running the Initial Match Code Setup, you must run Quarterly Adjustments to perform postal validation

on the data that already exists in your SAP system. This process is required even if you are upgrading this product from a previous version because having correct address data increases the effectiveness of finding duplicate data.

NoteCreating match codes while users are on the system: You can perform batch match or create match codes, and commit Match independently. This allows you to run batch match and create match codes without locking


users out of the system during the process. When the process is complete, you can then lock users out and commit the match codes at an appropriate time. When match codes have been created, but not committed, new match codes continue to be created. When they are committed, pending match codes are then committed also. In addition, when you run this report and match codes have been previously created but not committed, this state is reported on the screen.

1. Invoke the transaction SA38.

2. In the Program field, enter /FLDQ/RSADRINIBM and click Execute (F8).The Initial Match Code (Index) Setup and Batch Match Report window appears.

Your choices, among the options in this window, will depend on whether you are setting up initial match codes or performing batch match.

3. Select from the following options, as applicable::

Table 55:

Option Description Initial Match Code Setup

Batch Match

Available DQ Instances

Number currently running.

Available Work Processes

How many work processes on the SAP system are available.

You must have more available work processes than available batch RFC Servers because the pool of work processes is used to make each RFC Server call. You should have a few additional work processes that can be used by other ABAP processes.

Maximum Concurrent Tasks

Sets the limit on how many work processes this report can use. Lowering the number can hinder performance but conserve resources.

Packet Size The number of records in a packet.

Build the Index

Must be run before any other options are used. It populates the necessary database staging tables with (Business Partners, etc.) information from your SAP system. This option requires no RFC Servers (BATCH or TRANSACTIONAL) and does not require users to be locked out of the system. It can be run during any business hours appropriate for your business needs. Before executing the report, the Index Pools that have been activated on your system are shown in the Active Index Pools(s) section. Review this section before executing the report to verify that the required Index Pools have been activated. If an Index Pool correction needs to be made, make the correction and then re-run this report. After this option has been run, it only needs to be re-run in the following cases:○ When many contacts have been added to your system. This ensures that

those contacts are included in Batch Match.○ After Batch Match has been successfully completed.



Option Description Initial Match Code Setup

Batch Match

Create Match Codes

Creates the match codes needed for the Duplicate Check and Batch Match functionality. This option requires at least one BATCH RFC Server. It does not use TRANSACTIONAL RFC Servers. See the recommendations in this User Guide for the number of RFC Servers you should use in your environment. If you are unsure, three (3) is a good choice. This option does not require users to be locked out of the system. The time required to complete this operation is dependent upon many factors, including the amount of data, memory size, and work processes. It can be run during any business hours appropriate for your business needs.

Commit Dup Check Match Codes

Makes the match codes created as a result of the Create Match Codes option (above) active on your system and usable by our Transactional Duplicate Check functionality. This options requires no RFC Servers (BATCH or TRANSACTIONAL). Users must be locked out of the system while the new match codes are transferred to our database tables.

Perform Batch Match

Uses the data generated by the Build the Index optoin and the Create Match Codes option to find duplicate Business Partners, Contacts, etc. on your SAP system. It does not require users to be locked out of the system. It requires only one (1) BATCH RFC Server. If required, the Data Flow on Data Services can be scaled by setting the Degree of Parallelism (DOP). Please see the relevant documentation in this User Guide for more information. This option can be run during any business hours appropriate for your business needs. The behavior of this option depends on whether match codes have previously been created. If match codes have been previously created, this option performs batch match. If match codes have not been previously created, this option creates match codes and then performs batch match.

Threshold A lower number produces more potential matches.

Create BUT000 Cleansing Case

Indicates cleansing cases should be created for duplicates found in the BUT000 (Business Partner) index pool during the batch match process. For more information about creating a cleansing case on your SAP platform, see the documentation for your SAP platform.

This option appears only after you select the Perform Batch Match option.

4. Click the Execute button (F8).

If you have run Batch Match, after the system finishes processing, the number of matches are shown. To see the results of Batch Match processing, run the report /FLDQ/AD_DISPL_BATCH_MATCH.

Related Information

Viewing the Batch Match Results (/FLDQ/AD_DISPL_BATCH_MATCH) [page 90]


7.2.2.4 Viewing the Batch Match Results (/FLDQ/AD_DISPL_BATCH_MATCH)

This report has three criteria that you can use to filter the results of batch match and allow a smaller subset of data to be displayed. These criteria are cumulative.

NoteTo configure the Birthdate field to be displayed in the results screen of this report, add the Birthdate field to the layout via Settings -> Layout -> Change.

1. Invoke the transaction SA38 in the command box.

2. In the Program field, enter /FLDQ/AD_DISPL_BATCH_MATCH and click the Execute button (F8).

3. If you want to use Program Options to filter the report, configure these options:

Table 56:

Option Description

Index Pool This drop-down list shows Index Pools that are available in the batch match results (for example, BUT000 or KNA1).

Country This drop-down list shows countries present in the batch match report, filtered by the Index Pool selection. If no Index Pool was selected, then all available countries are displayed.

Group IDs Filters the report by Match Group IDs.

Number of Entries Shows the number of duplicates that will be displayed based on the criteria selected.

4. Click the Execute button (F8).

Matching records are displayed. Note that only default fields are shown. You can choose other fields to display at Settings Layout Change .

The following fields are available for display in this table, but are not enabled by default:

○ STR_SUPPL1 (Street Suppl1)○ STR_SUPPL2 (Street Suppl2)○ FLOOR (Floor)○ HOUSE_NUM2 (House Suppl)○ SMTP_ADDR (Email Address)○ TEL_NUMBER (Telephone_no.)○ BIRTHDT (Birthdate)

The fields STR_SUPPL1, STR_SUPPL2, FLOOR, and HOUSE_NUM2 must first be activated in the TSAD10 table for them to be populated with data. For information about activating fields in the TSAD10 table, see IMG: Identify Search Fields.

Related Information

IMG: Identify Search Fields [page 60]



7.3 Error-Tolerant Searching

When users perform a search for a customer, vendor, or business partner using SAP error-tolerant search functionality (often called fuzzy search or rough search), this product 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.

The searches can take place on address fields or name fields. You can customize this product 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 a search request, this product processes the data, creates a list of possible matches, and presents a hit list of candidates from which you can select an entry.

A hit list window gives these options.

Table 57:

Option Description

Select A window appears that gives the data 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.

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 IMG: Maintain Fields for Duplicate Hit List Display for information about the default settings and how to change the fields displayed.

Related Information

IMG: Maintain Fields for Duplicate Hit List Displays [page 56]

7.4 Duplicate checking with SAP MDG

This section describes how to configure this product to provide duplicate check with SAP Master Data Governance (MDG).


MDG supports different search applications. One is the Address Search based on BAS-DES (Business Service Address) for MDG-S/C/BP data models that uses the best practice Data Quality Management match capability, such SAP ERP/SAP CRM. Another type of duplicate check you could use is the generic duplicate check. Depending on the needs, you can choose between one of the duplicate check methods you want to setup to use with this product.

MDG generic duplicate check is only applicable to ECC 6.0 Ehp6 and later systems.

7.4.1 Setting the BAS-DES Duplicate Check for MDG

This method is applicable for the MDG C/S/BP data models. Assuming all the necessary install steps for this product are performed already, you must set the following to enable the BAS-DES based dupe check.

1. Use the t-code MDGIMG and navigate to the following highlighted and execute Define Search Applications and for the AD Search Mode and Enable the flags.

2. Go back to the IMG options and select Configure Duplicate Check for Entity Types. Set the Search Mode to AD and fill the Threshold parameters as per the MDG documentation.

7.4.2 Preparing Data Services to Work With MDG for Generic Duplicate Check

CautionUse this duplicate check method only if you did not use the method for setting the BAS-DES based duplicate check for MDG.

MDG generic duplicate check is only applicable to ECC 6.0 Ehp6 and later systems and applicable for all data models of MDG. If you want to use the BAS-DES based duplicate check for your MDG-C/S/BP data models you must not use this method.

If you want to use this duplicate check as part of installation of this product, you must configure the Data Services jobs that are installed by this product’s Data Services Components as services.For information on the procedure of configuring jobs as services, see Configuring Jobs as Services.

Related Information




7.4.2.1 Configuring MDG Jobs as Services

In addition to the jobs listed in Configuring Jobs as Services, you must configure these two jobs as services to use this product to provide generic duplicate check with MDG:

● Job_Realtime_DQ_SAP_MDG_Match● Job_Realtime_DQ_SAP_MDG_Create_Match_Codes

You must create multiple services for each job to accomodate each data model on which you intend to use this product’s search capability.

To distinguish the jobs and services, append to the name the data model ID to avoid having multiple data models sharing a service.

For example, you could name the match services Service_Realtime_DQ_SAP_MDG_Match_BP, Service_Realtime_DQ_SAP_MDG_Match_MM, and so on. You could name the create match code services Service_Realtime_DQ_SAP_MDG_Create_Match_Codes_BP, Service_Realtime_DQ_SAP_MDG_Create_Match_Codes_MM, and so on.

NoteNo matter what data model ID you append to the name of the service, you must use the prefixes Service_Realtime_DQ_SAP_MDG_Match and Service_Realtime_DQ_SAP_MDG_Create_Match_Codes with no variation.

Related Information


7.4.2.2 Specifying the Work Processes to Use

Use the PARALLEL_PROCESS_ GROUP configuration option to specify the work process group to use. For more information about the PARALLEL_PROCESS_ GROUP configuration option, see IMG: Maintain Operating Parameters.

Related Information



7.4.2.3 Disabling Session Security for Get_RTService_List

For the Data Services function Get_RTService_List, you must disable session security. Having session security enabled (which is the default) produces an error and causes session validation to fail.

1. In the Data Services Administrator, navigate to the Web Services Web Services Configuration .2. Select Get_RTService_List, and then from the drop-down list, select Disable session security.3. Click Apply to make the change.

7.4.2.4 Maintain Services for MDG Generic Duplicate Check

Maintaining services for MDG generic duplicate check requires several steps described in this section involving the IMG activity Maintain services for MDG generic duplicate check. For general information about the IMG activities used by this product, see the section Setting up Data Quality Management IMG Activities.

CautionWhen you perform the tasks in this section and save the generic duplicate check configuration, the process recreates the search index for the data model. Therefore, these procedures should be done during a system maintenance window, if possible.

7.4.2.4.1 Setting /FLDQ/ Namespace to Modifiable

Before configuring generic duplicate check on the SAP MDG system, you must set this product’s namespace to Modifiable.

1. Go to the option SE03 Set System Change and set /FLDQ/ to Modifiable in both lower panes.2. Save the change.

7.4.2.4.2 Assigning the Services

Next, you must assign the services.

1. From the IMG, click the Maintain services for MDG generic duplicate check.The Determine Work Area Entry window appears.

2. Enter the data model for which you want to configure duplicate check.The Service Assignment: Overview screen appears.

3. Assign a Duplicate Check Service and a Match Code Service to the data model by selecting one service from the selection list for both the Duplicate Check Service Name and Match Code Service Name selection lists.For example, you could assign a Data Services service called ServiceRealtime_DQ_SAP_MDG_Match1 to the Duplicate Check Service and a Data Services service called ServiceRealtime_DQ_SAP_MatchCode1 to the Match Code Service for the Materials Data Model.



Each service can be assigned to only one data model. This procedure can be used to create additional Match and Match Code services.

7.4.2.4.3 Configuring Fields for Duplicate Check

After assigning the services, you next configure which fields to use for duplicate check. Data models are made up of several Entity Types. Each Entity Type can have several attributes and each is assigned a weight for matching. You configure the fields one-by-one with this procedure, repeating the steps on the New Entries screen as necessary.

1. In the Service Assignment screen, select the data model line.2. Double-click the Fields for duplicate check folder in the dialog structure pane.

The New Entries screen appears. Here you can choose an Entity Type and Attributes for those Entity Types, as well as specifying other conditions.

3. Select the Entity Type field.The Entity Type screen appears.

4. Select the Entity Type, and then continue.The Attribute screen appears.

5. Select an Attribute for that Entity Type, and then continue.The Entity Type and Attribute populate the New Entries screen.

6. Type a number in the Weight field to assign priority of this Entity Type and Attribute when finding matches.

NoteThe weights of the various Entity Types and Attributes are compared to each other to set priorities in finding duplicates.

7. If desired, check the boxes in the fields Remove Noise Words, Remove Punctuation, and Remove Diacriticals to prevent those items from consideration during duplicate check.

8. If desired, check the box in the Mandatory field to make this Entity Type and Attribute mandatory for consideration in matching.

7.4.2.4.4 Defining Match Code Fields

Next, define the Match Code Fields. For each field, you must choose the type of corresponding match code.

This product provides the following match code (break key) functions within Data Services, each with these configurable options:

Table 58:

Match Code Function

Option 1 Option 2

Soundex None None


Match Code Function

Option 1 Option 2

Phonetic A flag to control how encoded strings are returned. When input as 0, return the primary encoding. If there is no primary encoding, then return null or the input string, depending on how Option2 is set.

When the input is not 0, return the alternate encoding. If there is no alternate encoding, then return null or the input string, depending on how Option2 is set.

A flag to determine whether to return null or the input string when there is no encoding. When input as 0, return null. Otherwise, return the input string when there is no encoding. When the parameter is null or invalid (non-numeric), it is defaulted to 1.

When input is empty, there is no primary or secondary encodings. When Option2 =0, then return null. When Option2 =1, then return the empty string.

Substring Start: The position of the first character in the new string. The function counts characters from the beginning of input_string . In normal dataflows, the first character is position number 1. If start is 0, the new string begins with the first character (position 1).

If start is negative, the function counts characters from the end of input_string . The new string begins with the character in that position from the end of the string.

If start is greater than the number of characters in input_string, the function returns an empty string.

Length: The number of characters in the resulting string. If length is 0 or negative, the function returns an empty string. If length is greater than the number of characters remaining in input_string after start , the function returns only the remaining characters.

The function keeps the trailing blanks in the remaining input_string after start .

1. In the Service Assignment screen, select the data model line.2. Double-click the Match Code Fields folder in the dialog structure pane.3. Select the Entity Type field.4. Select the Entity Type, and then continue.5. Select an Attribute for that Entity Type, and then continue. The Entity Type and Attribute populate the New

Entries screen.6. Select the Data Services Function Name field. The screen listing the Data Services Function Names appears.7. Select the Data Services function to assign, and continue. The function populates the Data Services Function

Name field.8. Supply the options in the Option 1 and Option 2 fields for that Data Services function.9. If desired, check the boxes in the fields Remove Noise Words, Remove Punctuation, and Remove Diacriticals to

prevent those items from consideration during maching.

When you save the configuration, the values are sent to the Date Services jobs and the jobs are restarted. The match code (break key) tables for this data model are created dynamically and each table is initialized with records already in the data model.

Related Information

Changing Default Break Key Calculations With a Custom Function [page 83]



7.4.2.4.5 Configuring MDG to Use This Product for Duplicate Checking

Next, you must configure MDG to use this product for duplicate checking.

1. Within the SAP client, invoke transaction SM30.2. Edit the V_USMD204c. Table View.3. Create an entry with the following values.

Table 59:

Field Value

Find Z1

Access Class /FLDQ/CL_MDG_DUPL_CHECK

Free Text Checked

Fuzzy Checked

Description DQM Implementation

4. Edit the V_USMD_DPCHK_MOD Table View.5. Enter a Threshold value for each Data Model/Entity Type with a find of Z1.

After these changes are saved, users of this MDG system have a Duplicate Check button on their screen. When a duplicate is found, the user is presented a list of duplicates. When a record is saved or updated within MDG, a record in the match code table is created or updated.

7.4.2.5 Adding a Custom Match Code Function

In addition to the match code (break key) functions provided with this product (soundex, phonetic, and substring), you can create and add a custom function that will be available when you define the Match Code Fields. Creating a custom function requires configuration on the MDG system and in Data Services.

Creating the Function in Data Services

For full instructions on creating functions in Data Services, see the Data Services documentation.

1. In the Data Services Designer, create a new custom function that will generate the break key. You can view the custom function CF_DQ_SAP_MDG_Phonetic_Match_Code_Metaphone as an example.

2. Open the custom function CF_DQ_SAP_MDG_Match_Code_Controller. Inside this function are instructions on how to add a new function. The name you give the function must be exactly the same as the name you will enter in the SAP view /fldq/ad_funcs.

3. Save the function and restart the Real-Time Service Service_Realtime_DQ_SAP_MDG_Create_Match_Codes.

The custom function will be available when you define the Match Code Fields in MDG.


Configuring the MDG System for Custom Functions

1. From the IMG, click the activity Maintain Data Services Custom Functions.

NoteThe table that appears stores the valid match code (break key) functions that can be used in the MDG Match Code Fields screen. It is used to link the available match code (break key) functions in Data Services to the items the SAP match code field screen allows the user to enter. The first column of the table is the Function field that is passed down to Data Services and used by the CF_DQ_SAP_MDG_Match_Code_Controller function to route data to the correct custom function for generating match codes (break keys).This name must be identical to the one used in that function.

The validate_func field is used to associate an ABAP function that validates two options that can be used for each break key function. This function is run when the data on the MDG Match Code Fields screen is saved to verify that the options are valid for that break key function.

2. Add a new row in this table for your new custom break key function. For an example of a validate_func, examine the function /FLDQ/VALIDATE_SUBSTRING_OPT.

This function will be available for selection on the SAP Data Model setup screen. The field validate_func is the ABAP function that validates options for the function.

TipFor an example of a configuration, examine the function /FLDQ/VALIDATE_SUBSTRING_OPT.

7.5 Matching on Birthdate

Populating Birthdate Values

To populate the birthdate values to be included in the matching process:

1. Enter transaction SPRO.

2. Click SAP Reference IMG and navigate to the following node: SAP NetWeaver ->Application Server ->Basis Services ->Address Management -> SAP BusinessObjects Data Quality Management.

3. Open the IMG activity Identify Search Fields.4. To enable birthdate values to be included in the input to the batch match processing, click New Entry and then

enter the following values for the new entry:○ DD table = BUT000○ DD field = BIRTHDT○ Check the last 3 checkboxes.

5. Save and exit the activity.

The /FLDQ/AD_DISPL_BATCH_MATCH allows the BIRTHDATE values to be displayed along with the match results.



Related Information

Viewing the Batch Match Results (/FLDQ/AD_DISPL_BATCH_MATCH) [page 90]


8 Person and Organization Name Cleansing

Person name cleansing standardizes various components related to a person's name. Organization cleansing standardizes the names of firms, companies, and organizations.

Person name and organization name cleansing takes place in real time as users enter data and in a batch mode using the Build Results report and Review Commit Results report.

Person and organization name cleansing is disabled by default. You can enable it, per client, using the IMG activity Activate/Deactivate Standardization Functionality.

Fields cleansed during person name cleansing:

● Title● First name● Last name● Middle name● Academic title

NoteIf a title was not provided on input, one may be assigned, depending on the person’s first name.

Field cleansed during organization name cleansing:

● Firm name

Related Information

Configuring Name and Organization Cleansing for MDG [page 68]IMG: Activate/Deactivate Standardization Functionality [page 60]

8.1 Interactive Name Cleansing

Interactive, real-time person and organization name cleansing lets SAP users cleanse person and organization name data at the point of entry, before data is written to the SAP database.

The person and organization name data is cleansed automatically when the user saves the record, clicks the Check button, or presses the Enter key.

When the user creates a record that contains invalid or unparsed person name data or invalid organization name data and attempts to save the record, the cleansing takes place in real time.

If this product discovers person or organization name data that needs to be cleansed, a window opens, revealing the suggested improvements. The user can choose to keep or discard the changes.


Person and Organization Name Cleansing

Table 60:

Button Action

Accept Cleansed The previous window returns to focus with the corrected data populating the fields.

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


8.2 Batch Name Cleansing

This product's batch person and organization name cleansing capability lets SAP users cleanse and review person and organization name data in groups of records.

Use the following two reports to perform batch name cleansing:

● /FLDQ/NC_BUILD_RESULTS● /FLDQ/NC_REVIEW_COMMIT_RESULTS

8.2.1 Build Results Report (/FLDQ/NC_BUILD_RESULTS )

Use the Build Results report to select the names or organizations that are to be cleansed.

This report lets you stage the selected name and organization data for later review.

1. Run transaction code SA38.The ABAP Execute Program window appears.

2. In the Program field, enter /FLDQ/NC_BUILD_RESULTS and click the Execute button (F8).3. Set up filters and other options as needed:

Table 61:

Option Description

BP numbers to process Enter the range of record numbers to process.

BP creation username Enter the name of the user who created the object.

BP creation date Enter the date on which the object was created.

Name Country (formatting) Enter the country whose style is followed for name and organization formatting.

Person (last) or Org Name Enter a range of names.

Process Person Name BPs Includes person name data in the cleansing.

Process Organization Name BPs

Includes organization name in the cleansing.

Packet size Determines how many records are processed and stored at one time. All addresses that meet the criteria are read, regardless of the packet size. Change this setting only in response to performance issues encountered.

4. Click the Execute button to generate the report.

User Guide for connecting to SAP Data ServicesPerson and Organization Name Cleansing C U S T O M E R 101

The report shows the following processing statistics:

● Start time● Completion time● Elapsed time in seconds

Use /FLDQ/NC_REVIEW_COMMIT_RESULTS to see results. If the results are acceptable, you can again run the process on a larger data set.

Related Information

Review Commit Results Report (/FLDQ/NC_REVIEW_COMMIT_RESULTS) [page 102]

8.2.2 Review Commit Results Report (/FLDQ/NC_REVIEW_COMMIT_RESULTS)

Use the Review Commit Results report to view cleanse results and act on them.

This report lets you view the cleansed name and organization data before and after cleansing.

1. Run transaction code SA38.The ABAP Execute Program window appears.

2. In the Program field, enter /FLDQ/NC_REVIEW_COMMIT_RESULTS and click the Execute button (F8).3. Set up filters and other options as needed:

Table 62:

Option Description

BP numbers to process Enter the range of record numbers to process.

Name Country (formatting) Enter the country whose style is followed for name and organization formatting.

Person (last) or Org name Enter a range of names.

Show Person BPs Include records with proposed person-name cleansing.

Show Organization BPs Include records with proposed organization-name cleansing.

Do not show approved proposals Exclude records that the user already reviewed and approved.

Do not show rejected proposals Exclude records with a CHKSTATUS of D, meaning that the user already reviewed this record's proposed name changes, and declined them.

Page size Enter the number of records to show on a single screen.

4. At the bottom of the screen, you can see the available range of BP numbers and the number of changes that will be displayed based on your filter and other option settings. Click Update number of changes displayed to refresh the latter number.

5. Click the Execute button to generate the report.


Person and Organization Name Cleansing

The report shows all records that match your filters. For each record, you see the original and the cleansed data, and you can choose to approve or reject the changes, and navigate the records using the following options:

Table 63:

Option Description

Approve Marks the selected record as approved.

Reject Marks the selected rec ord as rejected.

Approve Pg Sets all records on screen to approved and Checkstatus to “C”.

Reject Pg Sets all records on the page to a Rejected status. Sets Review table Checkstatus to “D”.

First Page, Previous Page, Next Page, Last Page

Use these buttons to navigate through the records.

Commit Pg For each approved row on the screen, updates the master data with the proposed changes and then deletes this BP proposal from the review table.

Commit All For each approved row in the review DB table (not just on the current screen), updates the master data with the proposed changes and then deletes this BP proposal from the review table.

Reject All In the review DB table, sets all review table records to not approve. Sets Review table Checkstatus to “D”.

Reset All Returns all records on this screen to their original status, before your changes.

Approve? (checkbox) Sets the selected record's changes to approved.

Once committed, the records are removed from the proposals table.

User Guide for connecting to SAP Data ServicesPerson and Organization Name Cleansing C U S T O M E R 103

A Troubleshooting

A.1 Installation Troubleshooting

Read tips and troubleshooting solutions related to the installation of this product.

Enabling and Disabling Address Cleanse Engine

By default, all address cleanse engines are enabled. Any unpurchased address engines should be disabled.

1. In the Data Services Management Console, navigate to the Real-Time Service Configuration tab, select the appropriate Service, and then navigate to the Add screen. 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.

Disabling Address Cleanse Engines Using Global Variables

During installation, you specified which address engines were purchased. You can change this setting manually to disable the address cleanse engines for countries for which you did not purchase the address directory. See the Data Services documentation for information about which countries’ address data is supported by which engine.

This table lists the country engine substitution parameters.

Table 64:

Substitution parameter Description

$$DQ_SAP_EngineUsa Enable or disable the USA engine

$$DQ_SAP_EngineCanada Enable or disable the Canada engine

$$DQ_SAP_EngineGlobalAddress Enable or disable the Global Address 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.

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.


Troubleshooting

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.

Error While Executing Batch Job DQCreateStageTables

During the installation of the Data Services Components, the installation routine attempts to run the DQCreateStageTables job to automatically create the RDBMS staging tables. If the installation was unable to create the staging tables, you must run the job manually in the Data Services Designer to create them.

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

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 job DQCreateStageTables is now visible in the Designer.

2. With the job DQCreateStageTables active, select Execute (or press F8) to execute the job, and then accept the default settings in the Execution Properties confirmation window.

This error is typically the result of incorrect database connection information provided during installation. To see this information, open the DQ_SAP_DS datastore and verify the connection information. When you close the window, Data Services validates the connection. See the Data Services documentation for instructions on setting a datastore's connection information.

A.2 Postal Validation Troubleshooting

Read troubleshooting tips for postal-validation-related issues.

Inability to Save Addresses for Which the Postal Code Cannot Be Completed

If you were not running this product 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.

This product attempts to fill in the correct postal code based on the other address information you provided. If, however, this product cannot determine a postal code, it 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 postal 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 this product allows you to save the address without the postal code only to have the SAP system disallow it, this product does not allow you to save the address.

User Guide for connecting to SAP Data ServicesTroubleshooting C U S T O M E R 105

Suggestion List Configuration

The configuration of suggestion lists is held in tables integrated into your SAP system by the installation of this product. Through these tables, you can changes to the appearance and content of suggestion lists.

You can edit these tables to configure suggestion lists.

Table 65:

Table Description

/FLDQ/AD_SCR_SUG This table configures which fields are displayed on a suggestion list and in what order. Use the DQM IMG nodes to configure this table. Look for the activity "Maintain Suggestion List Fields to display and order to display."

/FLDQ/AD_SUGLBL This table assigns labels to the suggestion list fields. The suggestion lists first tries to find records using the language of the user who is logged in. If the system is not able to use that language, it next tries to find records with the system's back-up language. If the system is not able to use that language either, it uses English. Use the transaction SM30 or DQM IMG to configure this table.

Postal Code: PO Box or Street Address

If you see error #3000 while performing postal validation on a record with a PO Box address, check that the address has the postal code entered in the PO Box post code field (POST_CODE2), not the street address post code field (POST_CODE1).

DPV Processing Locked

Delivery Point Validation (DPV) processing is provided as a for sale add-on to this product. If you run DPV and receive an error message that a record has locked DPV processing, you must obtain a DPV Unlock Code from SAP Business User 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.


Troubleshooting

A.3 Duplicate Check and Error-Tolerant Search Troubleshooting

Read troubleshooting tips for issues related to this product's duplicate check and error-tolerant search capabilities.

Records Created Without Break Keys (Match Codes) Due to Downtime of RFC Server

During any time that the RFC Server is not functioning, this product cannot 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, this product 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.

If the number of pending records exceeds the size configured in that parameter, this product cannot assign break keys to the records. Instead, you must run the custom report /FLDQ/AD_REPT_UPDATE_PEND_RECS.

Problems with CRM 7.0 EHP1 and Fuzzy Search

If fuzzy search is not working properly on a CRM 7.0 EHP1 system, see SAP Knowledge Base Article 1710840 for instructions to resolve the issue.

Duplicate Check and Substitution Parameter $$DQ_SAP_Match_Engine

Duplicate checking occurs in the following Data Services match transforms:

● Job_Realtime_Batch_DQ_SAP_Name_And_Address_Match● Job_Realtime_DQ_SAP_Name_And_Address_Ext_Match● Job_Realtime_DQ_SAP_Name_And_Address_Match● Job_Realtime_DQ_SAP_MDG_Match

These transforms use the substitution parameter $$DQ_SAP_Match_Engine. The default setting is JAPANESE, because the JAPANESE setting provides the same latin1 data matching as the other settings, and includes additional Unicode character matching and special Japanese character search/replace/standardization. Therefore, we recommend that you leave this setting to JAPANESE.

For information about the Data Services match engine and its substitution parameters, see the Data Services documentation.


Related Information


A.4 Region Code Troubleshooting

If you find when running postal validation the region code is incorrect or missing, you can try to correct this problem by reconciling any differences between the mappings of regions between the SAP system and Data Services. The information below explains how regions are mapped to work with this product and how you can change those mappings.

Displaying Missing Region Data

During postal validation, when a record has missing region data, the record is logged.

You can display the details of these missing regions by running the report /FLDQ/AD_REPT_DISPLAY_ERRLOG. Look at the details of the records in the display with the External ID of FZ23. Each missing entry displays the information it has, as well as what it was missing.

Details of an entry might be similar to the following:

Sample Code“COUNTRY: <countryname> - <countrycode>”

“Add, or correct an entry in the /FLDQ/DQ_REGIONS table.”

“<list of SAP region codes that are not in the /FLDQ/DQ_REGIONS table>”

“The list of SAP region codes are currently not mapped to Data Quality region codes.”

Reconciling Regions

To reconcile region differences between your SAP installation and those of Data Services, run the following reports in this order:

1. /FLDQ/AD_MAP_REGIONS2. /FLDQ/RSREGIONRPT


Troubleshooting

/FLDQ/AD_MAP_REGIONS

Before running this job, ensure that the results have no extraneous data that has no relevance to your business needs. For details, see IMG: Maintain Supported Countries [page 50].

The report /FLDQ/AD_MAP_REGIONS populates the tables.

TipThis job may take a long time to complete, resulting in one transactional RFC Server being busy until the completion of this job. You should run this job when this potential resource usage has minimal effect.

1. Invoke SAP transaction SE38.2. In the ABAP Editor: Initial Screen window, in the Program field, enter /FLDQ/AD_MAP_REGIONS.3. Click the Execute button.

At the conclusion of this job, the database tables needed for reconciliation are populated.

/FLDQ/RSREGIONRPT

The report /FLDQ/RSREGIONRPT indicates differences between the region data of the SAP system and that of Data Services.

1. Invoke SAP transaction SE38.2. In the ABAP Editor: Initial Screen window, in the Program field, enter /FLDQ/RSREGIONRPT .3. Click the Execute button.

The initial selection screen appears.4. Click the matchcode object (or press F4).

The list of countries that have region differences between your SAP system and Data Services appears.

NoteYou can select multiple countries by selecting the check box next to each country that you want displayed. If you want to display the report for all countries with region differences, you can leave the field blank, or select ALL COUNTRIES from the matchcode object.

5. Click Execute.

A report showing region differences is displayed. The differences are grouped by country and the type of difference. In each country section, and for new difference types within a country, the report displays a short description of the action required to map each section’s regions.

TipThis report sometimes shows a large amount of information. You could print the report and use it as a reference.


Example: Region Exists Only in SAP System

In this example, you see the following message after displaying the missing region data.

“These entries only exist in /FLDQ/DQ_REGIONS and T005S tables. These entries do not exist in Data Services. Add, or correct, an entry in the /FLDQ/DQ_REGIONS table.”

This message indicates that there are no entries for these regions for the country specified in Data Services. Therefore, Data Services can not return these entries during postal validation. This could be because a region has changed names or been consolidated into another region.

You must now add or correct a region entry in the /FLDQ/DQ_REGIONS table.

Determining the Cause of the Error

1. Invoke the IMG activity to insert regions. See the documentation specific to your SAP system for instructions.2. Look for an existing entry.3. If an entry exists, ensure that the region Code matches that of the region report and note the Region code

used.4. If there is not an existing entry, follow the instructions in your SAP system documentation to add the region.

Ensure that the region Code matches that of the region report and note the Region code you used.5. Use the SAP transaction code SM30 to invoke the Maintain Table Views: Initial Screen.6. In the Table/View field, enter /FLDQ/DQ_REGIONS and click the Maintain button.

You may see the warning “Caution: The table is cross-client.” If so, click Continue.

The Change View Maintenance View for DQ_REGIONS table: Overview is displayed.

Adding New Entries to the /FLDQ/DQ_REGIONS Table

If needed, in the Change View Maintenance View for DQ_REGIONS table: Overview, you can add new entries.

1. Click the COUNTRY CODE field.2. Use Request Help to invoke a list of SAP Country codes.3. Select the appropriate entry.4. Click the SAP REGION CODE field.5. Use Request Help to invoke the Search Help.6. Enter the applicable Country Code and SAP REGION CODE if you know it. Otherwise, click Continue to display

a list of SAP REGION CODES for the country.7. Select the appropriate entry.8. Click the DQ LONG REGION NAME field.9. Use Request Help to invoke the Search Help.10. Enter the applicable Country Code and DQ Long Region Name if you know it. Otherwise, click Continue to

display a list of DQ Long Region Name for the country.11. Click the DQ SCRIPT field.12. Enter the applicable Country Code and DQ Long Region Name and click Continue.


Troubleshooting

A list of Scripts for that name is displayed. (In most cases, LATN is the value used for this field.)13. Select the appropriate entry that maps to the DQ Long Region Name you entered earlier.14. Save the entries.

You may be prompted to create a change request, which could be used to transport these changes to other systems, if needed.

Modifying an Entry in the /FLDQ/DQ_REGIONS Table

If needed, in the Change View Maintenance View for DQ_REGIONS table: Overview, you can modify an entry.

1. Click the field to be changed.2. Determine the appropriate entry, using the instructions in this section.3. Select the appropriate entry.4. Save the entries.

Related Information

IMG: Maintain DQM Region Mappings [page 60]

A.5 RFC Server Troubleshooting

Read troubleshooting tips relating to the RFC Server.

Removing a Windows Service for an RFC Server

If you installed the RFC Server as a Windows service, you can use the tool remove_rfc_service.bat to remove any RFC Server services that are no longer used on that Windows system. The tool is at <install_path>\bin.

Start the tool from a Windows command prompt with Administrator privileges. When the program has started, you are asked for the SAP System ID used by the RFC Server, and then you can choose to remove Batch or Transactional RFC services, or both.

RFC Server Fails to Start: Partner Not Reached

If the RFC Server fails to start and displays the message “Partner not reached – Connection refused,” verify that the RFC Server’s network port 33<xx> is open (where <xx> is the central instance number). Having this port closed is often the cause of this error.


RFC Server Fails to Start: Cannot Find the Log File

On Windows 2008 Server and later systems that use the User Account Control (UAC), the RFC Server may not be able to run if that user does not have appropriate privileges. The error is caused by the inability to access the flrfcsrv_log.txt log file. Ensure that the user has appropriate privileges to access the log file.

This error may produce the following message:

Error: Unable to locate the Log file (%2). Please check the command line, configuration file options, and account privileges, with %2 being the log path similar to C:\Program Files (x86)\SAP BusinessObjects\Data Quality Mgmt for SAP Solutions\logs\flrfcsrv_log.txt .

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 product's version. 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>

Table 66:

Field Description

<vendor> The value assigned as the specification vendor in the manifest file.

<product> The value assigned as the specification title in the manifest file.

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

Understanding High Availability for the RFC Server for Network Outage

If a network outage occurs between the RFC Server and the SAP Gateway, then the RFC Server automatically reconnects to the SAP Gateway with a new connection when the outage has been resolved.

By default, the previous, inactive connection remains present on the SAP Gateway for 300 seconds. After 300 seconds, the SAP Gateway pings this connection. Because the connection is invalid, the SAP Gateway removes this inactive connection.

If, during that time, a call is made to that connection from this product, an error results and the connection is removed from the SAP Gateway.

You can set a different interval via SAP transaction code RZ10. Set the gw/reg_keepalive parameter value. Note that the value entered results in a ping to all registered programs on the SAP Gateway. For example, if you have 10


Troubleshooting

registered programs connected to the SAP Gateway, and set the gw/reg_keepalive parameter to 30, The result is 10 pings every 30 seconds.

See your SAP system documentation for more information about transaction code RZ10 and the gw/reg_keepalive parameter.

Java OutofMemoryError

If you receive the error “java.lang.OutOfMemoryError: Java heap space” while running the RFC Server, you have two options:

1. Increase the value of the maximum heap size (“-Xmx”). The RFC Server is pre-configured to use a maximum heap size of 256 MB of memory to conserve system resources.

2. Remove the “–Xmx” parameter. If system memory resources are not an issue, you can remove this.

The procedure to modify the “–Xmx” parameter depends on whether the RFC Server is being run from the batch file or as a Windows service:

Table 67:

Method Procedure

Modifying the parameter when running the RFC Server as a batch file

1. Locate this line in the appropriate batch file: %JAVA_EXE% -Xmx256m -classpath %FL_CLASSPATH%

2. Modify the –Xmx parameter. For example, to increase the maximum heap size to 512 MB the new parameter would read: -“Xmx512m”.

Modifying the parameter when running the RFC Server as a Windows service

You must modify the Windows Registry.

1. Locate the appropriate RFC Server service located in the Registry node HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\

2. Double-click the ImagePath value.3. Modify the value of the “–Xmx256m” parameter to the required value. (You could also re

move it and allow the memory footprint to grow without limit.)4. Click OK.

Startup Status Messages

During startup, the console shows startup status messages, indicating the steps of the process. The following messages appear only if their functionality is not supported by your Basis version:

● Extended Search functionality is not available on this system● MDG functionality is not available on this system


Data Services Managment Console

The Data Services Management Console allows for configuration of connected RFC Servers. This product does not use this capability, and attempting to configure the RFC Server for this product through Data Services can cause errors.

All configuration of the RFC Server for this product is described in this document.

If you have configured the RFC Server for this product in Data Services, use the Management Console’s SAP Connections window to delete the interface with this product’s RFC Server.

PC Power Management Software

Allowing a machine hosting an RFC Server to be put to sleep by PC power management software can cause the RFC Server to fail to reinitialize properly. You should not enable PC power management software on a machine that hosts an RFC Server.

RFC Server Termination

The RFC Server is designed to continue running regardless of the operational status of the Data Services or SAP application/gateway servers. However, the RFC Server terminates when you close the SAP gateway connection to the RFC Server via transaction SMGW or the same signal is sent from the gateway server. When this occurs you must manually restart the RFC Server.

If the RFC Servers are running as Window services, they can be configured to automatically restart based on the Window Services Recovery setting.

Related Information

Installing an RFC Server as a Windows Service [page 32]

A.6 Real-time Job Time-Out Troubleshooting

If, during the use of Data Quality Management for SAP Solutions, you find that our Data Services real-time job services are timing out, adjust the following items:

● In Data Services Management Console, adjust the Processing Timeout of the job in question by 50 percent. This should give the job the necessary time to finish.

● In the RFC Server’s flrfcsrv.xml file, change the uc_connect_timeout_sec setting to be 10 more than the entry you used above in the Real-time Service configuration. For example, if you increased the Real-time


Troubleshooting

Service Processing Timeout to 1200, you would change the uc_connect_timeout_sec in the flrfcsrv.xml file to 1210.

Restart both the Realtime Service and the RFC Server after making these changes.

A.7 Product Component Version Report

To create a report showing the version numbers of the Add-On, RFC Server, and Data Services jobs, run /FLDQ/RSPRODVER.

This report is intended to provide SAP Business User Support the ability to verify that all of the components of this product are the same or identify possible incompatibilities caused by version mismatches. Running this report is not otherwise required.

A.8 Customizing an Error Message

When an error is produced, the system reads error messages in the following order to determine the text to display:

1. Customized message for the language of the current login2. Customized message in the default language (English)3. Standard error message provided by default with this product

To customize an error message, follow these instructions:

1. Use the SAP transaction code SM30 to invoke the Maintain Table Views: Initial Screen.2. Enter table name /FLDQ/AD_ERRCUST.

3. Click the Maintain link in the Maintain Table Views window.4. Click New Entries (F5) in the Change View Customer defined error messages: Overview window.5. Specify an error code number, a language code (for example, EN for English), and the text of the message to

be displayed with that error.If the error occurs, the text represents how the error is logged.

6. Save your changes.

A.9 Diagnosing Problems That Cause Data Quality Processing to Cease

If this product ceases data quality processing, consider these tips to diagnose the problem.

● To check the error log for this product, run the report /FLDQ/AD_REPT_DISPLAY_ERRLOG.


● Verify whether the appropriate Data Services Web Services jobs are started and running within the Data Services Management Console. See the Data Services documentation for information about Web Services jobs.

● Check the logs within the Data Services Management Console for any errors. See the Data Services documentation for information on the logs and responses to issues found there.

● Do not ignore the logs for a Data Services service simply because the indicator light for that service is green. Sometimes the service indicator light is green even though processing has stopped. Examine the individual logs under each service, as the green indicator light may indicate only that the real-time services are active. The cause of the problem with data quality processing may be found in the logs.

● Try running the individual real-time jobs from within the Data Services Designer if real-time services do not work from within this product. This test may reveal problems within Data Services.

● Verify that the communication between the SAP Gateway and the RFC Server is active by using the transaction SMGW. See the documentation for your SAP platform for more information about this transaction.

● If you are licensed for geocoding and get an error related to geocoding, ensure that in Data Services the GEO job has been set up as a real-time Web Service. See the Data Services documentation for information about configuring jobs as a Web Service. Examples of the error messages include the following:○ An internal error occurred during geocoding or in a related geocoding program○ Internal error in SAP1, US. RFC: Connection error Destination: FL_GDQC_SERVER

● If you are licensed for geocoding and the RFC Server fails, the system still allows the address to be saved but logs an error that can be viewed in the /FLDQ/AD_REPT_DISPLAY_ERRLOG report.

Related Information

Configuring Geocoding [page 66]

A.10 Person and Organization Name Cleanse Troubleshooting

If you encounter incorrect person and organization name parsing issues, you will need to purchase and install SAP Information Steward and use its Cleansing Package Builder to update the dictionary parsing rules so that it parses names as you expect.

A.11 Enabling postal validation in MDG

If postal validation is not activated in Master Data Governance (MDG), ensure that Address Enrichment is set to Relevant in the appropriate MDG Change Request Step.

1. Enter transaction code MDGIMG.

2. Choose General Settings Process Modeling Change Requests Configure Properties of Change Request Step .


Troubleshooting

3. Choose your change request in the right pane.4. Double-click Change Request Step in the left pane.5. Choose the step where you want to enable postal validation.6. Double-click Enhancements and Checks per Change Request Step.7. For the Address Enrichment setting, enable the Relevant checkbox.


B External List Management

B.1 External List Management

External List Management (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.

This product further enhances this standard 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 this technology to perform postal validation and duplicate check of the list data against the SAP database.

B.1.1 Using This Product With ELM

To achieve optimal data quality when using ELM with this product, users should do the following.

● If you have a stand-alone version of Data Services, cleanse (through postal validation) and de-duplicate the external list using Data Services. For information on using Data Quality for these tasks, see the Data Services documentation.

● Using the SAP ELM functionality, load the external list into the SAP system. The ELM process uses the technology of this product 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 system documentation.

Specifying the Work Processes to Use

Use the PARALLEL_PROCESS_ GROUP configuration option to specify the work process group to use. For more information about the PARALLEL_PROCESS_ GROUP configuration option, see IMG: Maintain Operating Parameters.

Cleansing the Extermal List Before Loading

If the external list is not cleansed by Data Services prior to being loaded through 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.


External List Management

Pre-cleansing the list using a stand-alone version of Data Services 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.

If the list is de-duplicated against itself using a stand-alone version of Data Services prior to being loaded through ELM, the SAP system then considers all records in the list for de-duplication, instead of only the B2B records.

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.

Error: Index Pool BUT000 PARTNER Not Set up Completely

If there are any records in the pending updates table, the system may generate the following error message: Search index for index pool BUT000 PARTNER not set up completely. If you encounter this error, make sure you do not have any records in the pending updates table /FLDQ/AD_PUPDATE. If there are records in the pending update table, run the pending updates report /FLDQ/AD_REPT_UPDATE_PEND_RECS.

Related Information


B.1.2 Matching on the Marketing Attributes Field

This product supports the use of Marketing Attributes fields in matching, and allows you to make customizations to enable matching on other fields. You configure this product to perform this task through the IMG activity Maintain Matching on Marketing Attributes.

For general information about the IMG activities used by this product, see Setting up Data Quality Management IMG Activities.

Platform Requirement for Matching on the Marketing Attributes Field

To use matching on Marketing Attributes fields, you must use SAP CRM 7.0, Enhancement Pack 1 or later.

User Guide for connecting to SAP Data ServicesExternal List Management C U S T O M E R 119

Configuring ELM Jobs as Services

In addition to the jobs listed in Configuring Jobs as Services, you must configure these two jobs as services to use this product to work with ELM extended search on marketing attributes fields:

● Job_Realtime_DQ_SAP_Name_And_Address_Ext_Match● Job_Realtime_DQ_SAP_Name_And_Address_Ext_Match_Weights

Name the services:

● Service_Realtime_DQ_SAP_Name_And_Address_Ext_Match● Service_Realtime_DQ_SAP_Name_And_Address_Ext_Match_Weights

IMG: Activate/Deactivate Extended Search Functionality

This IMG activity allows you to activate or deactivate the Extended Search BAdI for ELM. You must activate extended search functionality if you are using the extended search ELM jobs.

IMG: Maintain Matching on Marketing Attributes

This IMG activity allows you to configure matching on Marketing Attributes fields. After configuration, the CRM business user can run ELM and invoke the data matching capabilities of this product on Marketing Attributes fields.

Configuring Matching on Marketing Attributes Fields

1. From the IMG, click the activity Maintain Matching on Marketing Attributes. The Marketing Attributes for Use During Duplicate Check screen appears.

2. Click the New Entries button. A drop-down list shows the available Marketing Attributes fields.3. Choose from the list the Marketing Attributes field on which you want to perform matching.4. Repeat this process for up to five different Marketing Attributes fields. By default, this product accepts a

maximum of five fields.5. For each Marketing Attributes field, assign a Weight percentage. The Weight percentages must add to 100,

regardless of the number of Marketing Attributes fields.

NoteBy default, the weight of 100% for Marketing Attributes fields represents 20% of the total weight of fields used in performing matching operations. This 20% or total figure can be changed, as described below.

6. Save your changes.

Saving the changes automates a request to the RFC Server. When the request from the SAP system reaches the RFC Server, the RFC Server restarts the Data Services match Job, creating in the Job new substitution parameter values to reflect the changes you made in the SAP system.


External List Management

Customizing the Number and Weights of Fields

To increase the number of available Marketing Attributes fields from the default five, you must change the following within Data Services.

NoteConsult the Data Services documentation for further details about how to edit dataflows.

Adding a new marketing attribute field:

1. In Data Services Designer, open the dataflow DF_Realtime_DQ_SAP_Name_And_Address_Ext_Match.2. In the transform RowsToColumns, add a new field GenericField<x> (where <x> is the next sequential number).3. Copy the function call from the GenericField5 field and replace the 5 with the <x> value that is the next

sequential number. The function has this sytax: CF_DQ_SAP_Get_Generic_Field([$$DQ_SAP_ATTR<x>],MA4. Create the following new substitution parameters:

○ $$DQ_SA_ATTR<x>○ $$DQ_SAP_WT<x> (where <x> is the same number as above)

Adding a generic field to the input of the matching transform:

After you have added a new marketing attribute field, you can add the GenericField<x> to the input of the matching transform

1. Create a new Match Criteria called Market_attrib_<x>.2. Copy the options from Market_attrib_5 and replace the substitution parameter $$DQ_SAP_WT5 with $

$DQ_SAP_WT<x>. Make sure that both fields’ blank score is set to 0.

By default the marketing attributes are set to 20% of the match score. You can change this level by altering the substitution parameter fields that end with _WT (but not DQ_SAP_WT<x> ). This product then recalculates the percent for the marketing attributes by adding the _WT fields (standard match fields like name, address, and so on) together and subtracting that sum from 100.

Adjusting the weight of an existing substitution parameter:

1. In the Substitution Parameter Editor window, double-click the field that contains the weight value for the substitution parameter you want to change

2. Change the integer to the desired weight value.3. Click OK to save the changes and close the Substitution Parameter Editor.

For each additional transform and corresponding substitution parameter, you can choose in your SAP system an additional Marketing Attribute field in the Marketing Attributes for Use During Duplicate Check screen.

Related Information

Setting up Data Quality Management IMG Activities [page 42]Configuring Jobs as Services [page 20]

User Guide for connecting to SAP Data ServicesExternal List Management C U S T O M E R 121

C Break Key Profiler

C.1 Break Key Profiler

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

Break Key Profiler Job

The Data Services job DQ_SAP_Break_Key_Profiler is installed as part of the Data Services Components portion of this product. It can be connected to the SAP system to generate statistics on Customer and Business Partner data to discover the best options to be set for this product. You can run this job immediately after installing the product or later to diagnose possible solutions to performance issues.

This job can also be installed to Data Services before installing the rest of this product to predict performance.

The job checks the SAP index pools BUT000 and KNA1. If you install the job to Data Services before installing the rest of this product, you must assure that you have activated these index pools before running the job.

Running this job provides the following benefits:

● Shows the different results for the five best practice match codes that are used for searching on address information.

● Allows matching the best function to your unique data to get the best results and response time.● Tests custom match codes that use extra fields against the best practice match codes supplied with this

product.● Finds noise words that can be removed from the matching process to get better matches.● Compares certified name selection against last name only selection to decide what type of name selection

process will be used.● Compares address only selection to name and address selection to decide if address only selection should be

activated.

Noise Words

Noise words are words that are part of the organization name1 or name2 field that do not have any relevance. For example, words such as “of,” “the,” and “Inc.” are common words that, if used when processing matches, result in much larger candidate groups.


Break Key Profiler

Candidates selected on these noise words are of little use in matching. This product already has many common English noise words configured. You can add new words that you consider to be noise words in your data. By removing the noise words from the matching process, you can improve performance.

If possible, you can improve the quality of matching results by removing noise words from your data prior to creating the break keys.

First and Last Name Selection

This product offers two types of dataflows to create break keys:

● Last name only● First and last name

Last name candidates usually provide better matches, as matching with first name often leads to false positive results. However, for backwards compatibility, this product offers both types of matches.

This dataflow shows the results for a random selection of records in the file DQ_SAP_LastNameCompare. The results show the difference in size that the last name only versus first and last name generate.

Name Candidates are only one part of the selection. When optimizing, you should consider the address selection process to get better results. When looking at the data, keep in mind that this product can process approximately 1000 records per second. For example, for a candidate group of 2000 records the processing time will be roughly two seconds, meaning that the user must wait that long to see results.

There is a default five-second processing limit for each transaction. For groups over 5000 to 6000 records, there can be records that do not get processed and a five second response time.

Address Only Selection

You can select match candidates using address information only. With this option enabled, the software ignores name information when selecting match candidates. However, if address information is missing, normal selection with name information occurs instead.

The matching process itself still uses name and address information. Only the selection of the records prior to matching is based on address information.

The default matching setup for organizations and individuals are 70 percent based on addresses making this a valid way of selecting candidates. The output in file DQ_SAP_NameAddressCompare looks at a random selection of records from the data and compares the candidate groups based on selecting on address information, on only name information and on both address and name information.

This show the performance you would get based on the selection process that is used. When looking at the data, keep in mind that this product can process roughly 1000 records per second. For example, for a candidate group of 2000 records the processing time will be roughly two seconds, meaning that the user must wait that long to see results.

This product has a default five-second processing limit for each transaction. For groups over 5000 to 6000 records, there can be records that will not get processed and a five second response time.

User Guide for connecting to SAP Data ServicesBreak Key Profiler C U S T O M E R 123

C.1.1 Installing the Break Key Profiler

The configuration dataflow, datastores, and options are installed when you install the Data Services Components portion of this product.

After installation, the Data Services datastore DQ_SAP_BP_CONFIG is set to point to the SAP system that contains the Customers and Business Partners records from which to pull the data. Settings such as turning on or off address engines and configuring the DQ_SAP_DS datastore are configured during the installation.

If you did not install the Data Services Components to the default location, you must make changes to operate the Break Key Profiler. The flat files in the dataflow DF_Generate_Statistics_sql assume a root directory based on the default location of the Data Services Components installation. If you did not install to that default location, you must update those files with the correct root directory information before running the DQ_SAP_Break_Key_Profiler job.

You must update the following flat files:

● DQ_SAP_NoiseWords● DQ_SAP_NameAddressCompare● DQ_SAP_LastNameCompare● DQ_SAP_MatchGroupComposite● DQ_SAP_MatchCodeStats● DQ_SAP_MatchCode1● DQ_SAP_MatchCode2● DQ_SAP_MatchCode3● DQ_SAP_MatchCode4● DQ_SAP_MatchCode5● DQ_SAP_MatchCodeCustom● DQ_SAP_MatchCode_PO_BOX

C.1.1.1 Installing the Dataflow Without This Product

You can install this dataflow to a Data Services configuration without installing the rest of this product, perhaps because you want to install the dataflow to a separate Data Services configuration.

1. In the installation materials for the Data Services Components portion of this product, locate the file DQ_SAP_Break_Key_Profiler_Tool.zip.

2. Unzip this file in a location accessible to your Data Services installation.3. Open the Data Services Designer and import the file <Data Services install>\Data Quality Mgmt

for SAP Solutions\integration\Break_Key_Profiler.atl.

NoteWhen you import the file, the system prompts for a passphrase.The passphrase is DQMSAP. If you receive a warning message, dismiss it as this is the expected behavior.

4. Open the data store tab and configure the DQ_SAP_DS and DQ_SAP_BP_CONFIG datastores.a. Use the DQ_SAP_DS datastore to connect to a MSSQL, Oracle, MySQL, DB2, or Sybase database to store

temporary files used by this Data Services job.


Break Key Profiler

b. Use DQ_SAP_BP_Config to connect to the SAP system to pull the data that is to be processed. You must provide the application server, username, password, client number, and system number to connect.

5. Open Tools Substitution Parameter Configurations , and enable the address engines that you have purchased for this product. Disable any that you have not purchased. The following are the substitution values to be modified.

○ DQ_SAP_EngineUsa○ DQ_SAP_EngineCanada○ DQ_SAP_EngineGlobalAddress

You can now run the Batch Key Profiler on this Data Services system.

C.1.2 Running the Break Key Profiler Job

There are two ways to run the job:

● Start the dataflow through the Data Services Designer as you would any dataflow. Navigate to Jobs Batch Jobs , and select DQ_SAP_Break_Key_Profiler. Click the Execute button.

● In the Data Services Management Console, select Administrator Batch Batch Job Configuration tab, and then select Execute for DQ_SAP_Break_Key_Profiler. You can leave all the settings as default in the Execution Options screen. Click the Execute button.

NoteIf you are running the Break Key Profiler on a Sybase database, the Sybase configuration setting “ddl in tran” must be set to true.

C.1.3 Performance of the Break Key Profiler Job

Having the dataflow perform address and name correction, along with generating statistics, is a CPU-intensive task. Because a single CPU would not perform well under these tasks, this dataflow is configured under the assumption that your machine has two CPUs.

This section offers suggestions for improving performance when you run the Break Key Profiler job.

Changing the Degree of Parallelism Setting

If the machine on which you run Data Services has more than two CPUs, you can change the Degree of Parallelism (DOP) setting to get better performance of the Break Key Profiler job.

Based on the number of CPUs of your machine, set the DOP in this range.


CPUs Recommended DOP setting

2 1 to 2

4 3 to 4

6 4 to 6

1. Open the batch job DQ_SAP_Break_Key_Profiler and right-click DF_DQ_SAP_Create_Break_Keys.2. Select Properties, and then change the Degree of Parallelism (DOP) to the recommended setting (see

preceding table)

TipIf the database server is also on the same machine, you might improve performance by dropping the DOP one or two levels to leave CPU resources for exclusive database processing

Disabling Noise Word Generation

Disabling noise word generation increases performance of the Break Key Profiler job

1. Open Data Services Designer and navigate to Tolls Substitution Parameter Configurations .2. In the Substitution Parameter Editor, set to NO the the substitution value $$DQ_SAP_Profiler_Noise_Words.

The value should now be $$DQ_SAP_Profiler_Noise_Words = NO. You must restart the Real-time job for the new setting to be used.

C.1.4 Interpreting the Break Key Profiler Results

This batch job is split into several dataflows and scripts. After the job runs, you can find the results in the final dataflow, DF_Generate_Statistics.

Running the job also sends ten .csv output files to <[install_path]>\SAP BusinessObjects\Data Quality Mgmt for SAP Solutions\extras\SampleInputFiles.

You can view the first 1000 records from within the dataflow, but you must open the .csv output files to see the all the records. You may want to do so for any of the match codes (called DQ_SAP_Match_Code1 through DQ_SAP_Match_Code5) if you want to see all the records. However, the first few hundred records are the most important.

NoteYou can graph the data from the match codes by opening the .csv file in a data reporting tool or a spreadsheet program and using its graphing capabilities.


Break Key Profiler

C.1.4.1 Break Key Profiler Output Files

Table 68:

File Description

DQ_SAP_NOISE_WORDS The dataflow generates statistics on the words in the organization name fields The output contains a row for each word, along with the number of times it appears in the database and the percentage. The results are sorted so that the most common words are first.

When you look through the results, look for words that occur frequently but do not add value. For example, the abbreviation “Inc.” appears in many organizations’ names but does not provide assistance with the matching process. You could add this word to the noise word list so that it is removed before generating the break keys for candidate selection.

Adding words to the noise word list shrinks the candidate groups and limits the number of false positives that this product processes through the dataflows, thereby improving performance.

The dataflow provides some noise words. To add noise words, in the Data Services Designer open the CF_DQ_SAP_REMOVE_ORG_NOISE_WORDS custom function and follow the instructions at the top of the function.

DQ_SAP_LastNameCompare This output file shows the different candidate groups that are generated based on using the default break key dataflow or the secondary dataflow that incorporates first names in the selection. The first record in the output is the average of all the other records.

The output contrasts the last name selection with the first and last name selection, and shows the difference in number between the groups and how many times larger one of the groups is compared to the other.

For any but a very small database, you should use the last name only. Last name only generates much smaller candidate set groups because first names are typically common and add many false positives to the matching results. Using first names provides few new matches that would not be found by selecting only on last name.

DQ_SAP_NameAddressCompare

This output file shows the differences among three methods for selecting candidates: address only, address and last name, and last name only. These three results are displayed to help contrast an option in this product that allows for address-only candidate selection when address data is available to improve performance. The first record in the output is the average of all the other records.

Address fields comprise 70 percent of the matching process. Basing the candidate selection on addresses (where available) results in high quality matches and improved performance.

DQ_SAP_Match_Code1-5 In this output, there are six match group tables, numbered 1-5, and also a custom table. This product can generate five different best-practice match codes based on the address, along with a custom match code that can be developed for special requirements.

Each of these tables allows you to see the match codes that are generated for the associated match code, along with a count and percent of the records in the database that have that match code. Use these fields to find the best match code function to be used on your data.

DQ_SAP_MatchCodeStats This output shows an overview of all the match codes: the average group size, maximum group size, and median group size for the five best practice match codes and the custom match code. This product uses this output, along with the DQ_SAP_Match_Code1-5 outputs, for picking the best match code to implement.


File Description

DQ_SAP_MatchGroupComposite

This output is a combination of DQ_SAP_Match_Code1-5 and the custom tables. The purpose of this combination is to allow you to easily compare the output.

You can compare the largest match groups by examining the top 10 to 25 percent of the data.

C.1.4.2 Settings Optimized Based on Output

The most important aspect in improving response time for data quality processing is to select the best match code for your data and the size of your database. Ideally, you find the match code that gives both the smallest average break group, but also has the best distribution.

To help find that ideal, use the MATCH_GROUP tables and MATCH_GROUP_STATS to compare the results and pick the best one. The match codes are numbered 1-5.

The following tips can also help you use the output to optimize break key settings:

● You can look at the actual match codes, their size, and percentage of all records in the MATCH_GROUP1-5 tables. For larger tables, however, you should use the MATCH_GROUP_STATS tables. These tables show the average, median, number of match groups, and max fields. You can also find in the tables the median group size to help you better understand how the data is distributed, because the median group size data is not unduly influenced by the top and bottom few percent, which can skew the average value.

● By comparing the average and median, you can get a better understanding of how the data is arranged. For best performance, strive for results in which the data is spread as evenly as possible over the highest number of match codes. You should limit the number of match codes that are significantly larger.

● If processing seems slow or you get incomplete results returned, you should use a different match code.● If there is a problem with your data, such as missing or incomplete data in the fields that the match code is

using, then cleanse and standardize the data with Data Services. Address information must be complete, as the break keys are generated off the postal code and street name data fields.

● Using tighter break keys results in smaller break groups, which increases the possibility of excluding a possible match. Picking the best match code requires you to balance response time versus the highest probability of finding all matches. As the data set increases in size, the tighter match groups must be used to keep performance within required boundaries. The five best practice fields are designed to handle the different sized data sets by giving a range of loose to tight match codes.

C.1.4.3 Best Practices Match Codes (Break Keys)

This product provides five best practice match codes. All match codes contain the country data field.

Tighter match codes work well for address data. All address data are pre-processed through Global Address Cleanse transform that standardizes the information and places the data into the correct fields before generating the match codes. This limits misspellings, transposed letters, and invalid address components, which would require fuzzy matching to find all possible matches.

There is also a custom match code that can be modified to select on extra fields such as email, phone numbers or other fields if required.


Break Key Profiler

Table 69:

Match code Description

Match Code 1 This has loose postcode and loose street name selection. It is created by using two-character ISO country code, plus the first three characters of the postcode, plus the first character of street name.

For the United States and most other countries, the ISO country code and three characters of the postcode narrow the location to the sectional center facility. The first character of the street further limits the match code to streets with the same starting letter. This was the match code previously used by this product. It generates the most possible matches that will have to be processed through the matching process, and as a result is the slowest at processing, on average.

Match Code 2 This has loose postcode and tight street name selection. It is created by using the two-character ISO country code, plus the first three characters of postcode, plus the first three characters of street name. This match code is a modification of Match Code 1, with a tighter selection of the street field by using three characters instead of only one. This match code gives fast performance but still selects addresses in a larger postal area.

Match Code 3 This has tight postcode and loose street name selection. It is created by using the two-character ISO country code, plus the first five characters of the postcode, plus the first character of street name.

Using the first five characters of the postcode narrows the location to the area of the city or town for the United States, with similar accuracy for other countries. It uses the first character for the street, which results in small candidate groups and fast performance, but still allows for variance in the street name. This match code gives similar performance to Match Code 2.

Match Code 4 This has tight postcode and tight street name selection. It is created by using the two-character ISO country code, plus the first five characters of the postcode, plus the first 3 characters of street name.

It has narrow postcode selection but increases the street tightness by using the first three characters of that field. In most data sets, this generates the smallest number of records to be sent to the matching process. This should result in the fastest response time for large databases, especially if the lower numbered match codes return too many false positives that have to be processed.

Match Code 5 This has tight region, tight city, and tight street matching. It is created by using the two-character ISO country code, plus the two-character region code, plus the first ten characters of city, plus the first three characters of the street name.

Postcodes are only loosely tied to cities and do not truly represent geographical regions. They are artificial constructs. This match code uses region and city instead of postcode to offer a different logical way to group the addresses.

This match code uses the three characters of the street to partition the larger cities. The city field is standardized so that matching on larger sets of data can help narrow the records selected to be matched against, but does not remove any records that have a chance to match. This match code should result in slightly slow response time compared to Match Code 4, but much faster than Match Code 2 or Match Code 3.

Match Code Custom

This is a placeholder. It is to be created for special cases in which the default match code based on the best practice address data does not result in the candidate groups that is needed.

C.1.5 Creating Custom Match Codes (Break Keys)If you have special search cases (such as searches on phone number, email address, or on an extra field that is not address information ), you may prefer to create a custom match code rather than use the provided best practices match codes.


The best method to create a custom match code is by updating the provided custom function CF_DQ_SAP_Calculate_Match_Code_Custom. This function already has most of the common fields that can be used for creating a match code, along with a few common ways of combining them into match codes. You can modify the function and test it within the DQ_SAP_Break_Key_Profiler job.

If you have to modify the input to the CF_DQ_SAP_Calculate_Match_Code_Custom custom function, you must modify the transform Build_Address_Match_Codes in DF_DQ_SAP_Create_Break_Keys when testing and in the same transform in DF_Realtime_DQ_SAP_Create_Break_Key for production.

After you have finished testing the custom function, you must set the custom function to be used in the DF_Realtime_DQ_SAP_Create_Break_Key dataflow.

C.1.5.1 Changing the Code Used for Match Codes (Break Keys)

1. Open Data Services Designer and navigate to Tools Substitution Parameter Configurations .2. In the Substitution Parameter Editor, set the substitution value $$DQ_SAP_Match_Function to

MatchCodeCustom.

You must restart the Real-time job for the new match code (break key) to be used.

For more information on changing break keys, see Configuring Break Key Settings.

Related Information

Configuring Break Key Settings [page 81]


Break Key Profiler

D Data Quality Administration

D.1 Using Data Quality Administration With This Product

Data Quality Administration (DQA) is an SAP framework designed to eliminate duplicate data records and ensure a high standard of Data Quality. This product further enhances this framework when the default task Internal Duplicate Check is executed, evoking the deduplication process of this product.

The following tasks are supported by default by the framework, and work on a predefined validation group, such as a profile or target group.

Integrated Duplicate Check by default has these steps:

1. Identify Duplicates Internally, which evokes this product's deduplication process to get potential matches. That is, it gathers candidate records inside and outside of target group.

2. Create Cleansing Cases, which creates cleansing cases from duplicates created in the first step.3. Merge Business Partner (BP) records, which merges BPs from the cleansing cases created in the second step.

The other three default tasks are External Postal Address Validation, External Content Validation, and External Duplicate Check. These tasks allow a user to export data from a validation group to an external location, do external processing (for example, validation or deduplication) on the data, and re-import the file, where any changes will then be updated. SAP Data Services, for example, could be used for the external processing.

Customization settings and activities and further documentation about the tasks are found at the following IMG activity location: Customer Relationship Management > Master Data > Business Partner > Data Quality Administration. DQA tasks and processing are found in CRM — Master Data activities.

For more information, see the SAP documentation for DQA tasks and also SAP Note 1140790 for details about customizing and enhancements.

User Guide for connecting to SAP Data ServicesData Quality Administration C U S T O M E R 131

E Staging Table Values

E.1 Data Services Component Installation: Staging Table Values

Here are the database types, guidelines, and sample values that you could use during the installation of the Data Services Components to choose a database type and provide connection information.

Table 70: Sybase RDBMS staging tableSybase Connection Parameters input screen specifications and sample values:

Text Guidelines Sample Value

Database Tables Owner No default DBO

Database Server Name Cannot be blank, no default \\myserver

Database Name Cannot be blank, no default MYDB

User Name Cannot be blank, no default dbuser

Password Cannot be blank, no default dbpass

Table 71: Oracle RDBMS staging tableOracle Connection Parameters input screen specifications and sample values:


Oracle Tables Owner/Schema No default DBUSER

Oracle TNS Name/Service Cannot be blank, no default MYDB.MYDBHOST.MYCOMPANY.NET or MYDB

Oracle User Name Cannot be blank, no default DBUSER

Oracle User Password Cannot be blank, no default DBPASS

Table 72: DB2 RDBMS staging tableDB2 Connection Parameters input screen specifications and sample values:


DB2 Tables Owner/Schema No default DBUSER


DB2 User ID Cannot be blank, no default dbuser

DB2 User Password Cannot be blank, no default dbpass

Table 73: MS SQL Server RDBMS staging tableMS SQL Server Connection Parameters input screen specifications and sample values:


Staging Table Values


Database Tables Owner No default DBO

Database Server Name Cannot be blank, no default \\myserver


User Name Cannot be blank, no default (shown if Windows Authentication is not used)

dbuser

User Password Cannot be blank, no default (shown if Windows Authentication is not used)

dbpass

Table 74: MySQL 5.0 RDBMS staging tableMySQL 5.0 Connection Parameters input screen specifications and sample values:


Database Source Name (DSN) Cannot be blank, no default DataServices

Database Tables Owner No default dataservices

User Name Cannot be blank, no default dbuser

User Password Cannot be blank, no default dbpass

Related Information

Installing the Data Services Components [page 18]

User Guide for connecting to SAP Data ServicesStaging Table Values C U S T O M E R 133

Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).


Important Disclaimers and Legal Information

http://help.sap.com/disclaimer/

User Guide for connecting to SAP Data ServicesImportant Disclaimers and Legal Information C U S T O M E R 135

go.sap.com/registration/contact.html

© 2017 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company 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.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Date post:	02-May-2018
Category:	Documents
Upload:	lamkiet
View:	320 times
Download:	8 times

User Guide for connecting to SAP Data Services · User Guide for connecting to SAP Data Services...

Documents