User Guide for connecting to SAP Data Quality Management ...

CUSTOMER

SAP Data Quality Management, version for SAP SolutionsDocument Version: 4.0 SP09 – 2017-12-08

User Guide for connecting to SAP Data Quality Management, microservices for location dataConnecting to SAP Data Quality Management, microservices for location data

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Before You Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.3 Required SAP Notes for Your System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.1 Downloading Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.2 Installing the Add-Ons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing Packages for a New DQM for SAP Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Installing Support Packages for DQM for SAP Add-On FLDQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4 Required Post-Installation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.1 Configuring Communication with SAP Data Quality Management, microservices Using Client

Certificate Authentication/Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.2 Activating Business Configuration Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.3 Setting up Data Quality Management IMG Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Linking to SAP Reference IMG Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Locating the IMG Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18IMG: SAP Handshake With RFC Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19IMG: Activate Base BC Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21IMG: Activate Client Specific BC Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5 Optional Post-Installation Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.1 Optional IMG Activities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

IMG: Maintain Settings to Switch off the Address Reviewer Screen. . . . . . . . . . . . . . . . . . . . . . . . . 23IMG: Maintain Settings for Address Validation Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24IMG: Maintain Supported Countries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24IMG: Maintain Exception Table of Transaction Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25IMG: Activate SAP Postcode Check Before PV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26IMG: Maintain Operating Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26IMG: Maintain Fields for Address Reviewers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27IMG: Activate/Deactivate Postal Validation Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28IMG: Activate/Deactivate DES Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29IMG: Activate/Deactivate Standardization Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29IMG: Maintain Customer Address Reviewer Labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29IMG: Maintain Suggestion List Labels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2 C U S T O M E RUser Guide for connecting to SAP Data Quality Management, microservices for location data

Content

IMG: Maintain Suggestion List Fields to Display and Order to Display. . . . . . . . . . . . . . . . . . . . . . . .30IMG: Maintain Customer-Defined Standardization Reviewer Labels. . . . . . . . . . . . . . . . . . . . . . . . . 30IMG: Maintain Standardization Reviewer Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31IMG: Activate Duplicate Check and Determine Limit for BAPIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31IMG: Set Limit for Duplicate List in SAP Dialog Boxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5.2 Other Optional Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Installing and Configuring Into WebClient for CRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Configuring Geocoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Configuring Name and Organization Cleansing for MDG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Adding the PO Box Lobby Field. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Configuring the Use of Multiple Back-End Engines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6 Postal Address Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396.1 Interactive Address Cleansing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

A Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40A.1 Postal Validation Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40A.2 Region Code Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41A.3 Product Component Version Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41A.4 Customizing an Error Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41A.5 Diagnosing Problems That Cause Data Quality Processing to Cease. . . . . . . . . . . . . . . . . . . . . . . . . . . 42A.6 Enabling postal validation in MDG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

User Guide for connecting to SAP Data Quality Management, microservices for location dataContent C U S T O M E R 3

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 also describes connecting to the cloud-based SAP Data Quality Management, microservices for location data product for address cleansing, geocoding, and reverse geocoding.

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. See the appropriate SAP documentation or SAP Business User Support.

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%3A%2F%2Fservice.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 Protection and Privacy

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

Data protection is associated with numerous legal requirements and privacy concerns. In addition to compliance with applicable data privacy regulations, it is necessary to consider compliance with industry-specific legislation in different countries. SAP provides specific features and functions to support compliance with regards to relevant legal requirements, including data protection. SAP does not give any advice on whether these features and functions are the best method to support company, industry, regional, or country-specific requirements. Furthermore, this information does not give any advice or recommendation in regards to additional features that would be required in particular IT environments; decisions related to data protection must be made on a case-by-case basis, under consideration of the given system landscape and the applicable legal requirements.

NoteIn the majority of cases, compliance with applicable data protection and privacy laws will not be covered by a product feature. SAP software supports data protection compliance by providing security features and specific data protection-relevant functions, such as simplified blocking and deletion of personal data. SAP does not provide legal advice in any form. Definitions and other terms used in this document are not taken from any given legal source.

Be aware that the data you provide gets placed into trace logs, sample reports, and repositories (side-effect data), and so on. In other words, your data will find its way into places other than output files. It is your responsibility to delete this data.

While processing SAP Business Partner data, the Data Quality Management version for SAP Solutions application stores the data in internal tables, for the purpose of data processing only.

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.

User Guide for connecting to SAP Data Quality Management, microservices for location dataBefore You Install C U S T O M E R 5

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.

Communications between the ABAP application server and SAP Data Quality Management, microservices for location data is protected by X.509 authentication, which is configured in the RFC destination.

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

Table 2:

Component Authorizations

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.

Table 3:

Component Authorizations

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

Threat Modeling

While the risk of this happening is minimal, you should be aware of a potential risk of someone maliciously accessing your DQM microservices account, processing large numbers of transactions, and incurring large fees (billable to you).

The authentication measures in place minimize this risk. You should also monitor your usage information in DQM microservices to watch for abnormal volumes.

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.


Before You Install

https://help.sap.com/viewer/d95546360fea44988eb614718ff7e959/Cloud/en-US/1d378fd1404c4cf9897ee1602583da1c.html

https://help.sap.com/viewer/d95546360fea44988eb614718ff7e959/Cloud/en-US/d77b9869b4f240de86679d5565af47c4.html

2.2 System Requirements

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

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)

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

SAP Note Description

1276016 Improper informational message is shown.

2158324 Cleanse data before saving to master tables.

1695782 Unable to activate classic BAdI impl. with IMG activity.

User Guide for connecting to SAP Data Quality Management, microservices for location dataBefore You Install C U S T O M E R 7

3 Installation

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

3.1 Downloading Software

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

1. Navigate to: https://support.sap.com/swdc.2. Select Software Downloads.


Installation

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F

http://help.sap.com/disclaimer?site=https%3A%2F%2Fwiki.scn.sap.com%2Fwiki%2Fdisplay%2FSL%2FWhat%2Bis%2Ban%2BAttribute%2BChange%2BPackage%2Band%2BWhy%2Bis%2Bit%2BNeeded

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. Complete the download using the Download Basket. See the instructions available on the software download

site for details.

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

User Guide for connecting to SAP Data Quality Management, microservices for location dataInstallation C U S T O M E R 9

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

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 1875965 Installation/Delta upgrade FLDQ 440_740

Related Information

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

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


Installation

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

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 file . If the path is long and

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

Table 6:

SP .SAR File

09 SAPK-45106INFLDQ

10 SAPK-45107INFLDQ

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

Related Information

Activating Business Configuration Sets [page 15]

User Guide for connecting to SAP Data Quality Management, microservices for location dataInstallation C U S T O M E R 11


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.

4.1 Configuring Communication with SAP Data Quality Management, microservices Using Client Certificate Authentication/Authorization

After completing all download and installation steps, perform the following steps to enable connectivity to SAP Data Quality Management, microservices for location data (DQM microservices).

NoteAll links to NetWeaver documentation are specific to NW 7.50. Refer to “Transport Layer Security for AS ABAP” in the documentation for the NW version you are running on.

As of today, only Client Certificate Authentication is supported when DQM microservices is used with the AS ABAP platform. It is not possible to use alternative authentication methods supported by DQM microservices, such as OAuth.

To establish trust between the AS ABAP system and DQM microservices, a client certificate must be set up in the AS ABAP system and also imported into SAP Cloud Platform to enable DQM microservices to trust the certificate being sent by the AS ABAP system.

The following steps must be done to configure the AS ABAP server to be able to make an outbound HTTPS call to the DQM microservices running on SAP Cloud Platform. Each of these steps is explained in greater detail in the following sections.

● Step 1 – Create/Set up PSE (Personal Security Environment) for Client Certificate Authentication (Transaction STRUST)

● Step 2 – Set up PSE for SSL/TLS (Transaction STRUST)● Step 3 – Set up an RFC Destination (Transaction SM59)● Step 4 – Set up DQM microservices to trust the Client Certificate being sent by the AS ABAP system

Step 1 - Create/Set up PSE (Personal Security Environment) for Client Certificate Authentication

If you already have a client certificate signed by a certificate authority and set up in an existing PSE, you may reuse that. However, SAP Cloud Platform supports only a specific list of Certificate Authorities (CAs). To reuse what you


Required Post-Installation Setup

have, your certificate must be signed by one of the trusted CAs (see Trusted Certificate Authorities for Client Certificate Authentication).

RestrictionSelf-signed certificates are not supported.

If you plan to reuse an existing PSE/Certificate, then you will need to export that certificate so that you can later import it into SAP Cloud Platform for use with DQM microservices in Step 4. This can be done using the STRUST transaction and selecting the standard SSL Client PSE you want to reuse where there is an option to export the client certificate.

Learn more about maintaining the standard SSL Client PSEs.

If you need to set up a new client certificate for communication with DQM microservices on SAP Cloud Platform, then you will need to set up a new standard (not anonymous) SSL Client PSE. This involves requesting a new signed certificate from a CA supported by SAP Cloud Platform and importing that associated certificate into your NW system using STRUST. Learn more.

If you happen to have multiple outbound HTTPS requests that use different client certificates, then you can’t use the default standard Client SSL PSE and may need to create additional individual standard Client SSL PSEs. Learn more.

You will also need to export this certificate in order to accomplish Step 4.

Step 2 – Set up PSE for SSL/TLS

In this step, you set up the NW system to be able to access the server certificate from SAP Cloud Platform in order for the AS ABAP servers to establish SSL/TLS communication with DQM microservices.

1. Export the server certificate from SAP Cloud Platform:○ Navigate to your SAP Cloud Platform cockpit. This link was provided to you when you purchased DQM

microservices.○ Use your browser’s capabilities to export the certificate to a file. To do this with Firefox:

Table 7:

Task Description

Export SSL certificate of SAP Cloud Platform

To export the SSL certificate of SAP Cloud Platform navigate to your web application in a browser window, display the website identification, show the certifi-cate and export it to a file.

Navigate to your web application in a browser window

When you navigate to the application URL in a browser window there should be an error because of missing permissions (because the OAuth 2.0 authorization details were not included in the request).

Display the website identification Click the SSL symbol and display the website identification data. Select Further information.

Show the certificate information (Description for Firefox.)

The SAP Cloud Platform server SSL/TLS certificate should be loaded in the SSL Client PSE certificate list that you created or set up in Step 1.

User Guide for connecting to SAP Data Quality Management, microservices for location dataRequired Post-Installation Setup C U S T O M E R 13

https://help.hana.ondemand.com/help/frameset.htm?fe957070f9f7447cb886eb65e6a0543e.html

https://help.hana.ondemand.com/help/frameset.htm?fe957070f9f7447cb886eb65e6a0543e.html

https://help.sap.com/saphelp_nw75/helpdata/en/49/23501ebf5a1902e10000000a42189c/frameset.htm

https://help.sap.com/saphelp_nw75/helpdata/en/49/26ada239242583e10000000a421937/frameset.htm

https://help.sap.com/saphelp_nw75/helpdata/en/49/26af8339242583e10000000a421937/frameset.htm

https://help.sap.com/saphelp_nw75/helpdata/en/49/26af8339242583e10000000a421937/frameset.htm

Typically, a server SSL/TLS certificate would be loaded into the Anonymous SSL Client PSE but because you are using Client Certificate Authentication, load this server certificate into the certificate list of the SSL Client PSE you created or set up in Step 1.

2. Open the SSL Client PSE that you created or set up in Step 1, and in the Certificate section, select Import Certificate. Click Add to Certificate List after they load the certificate. Then click Save.

Learn more about doing this with the STRUST transaction.

Step 3 – Set up an RFC Destination

Next you will establish the detailed connection information to DQM microservices from the AS ABAP system including the URL to connect with and referencing the certificates setup for authentication and SSL/TLS in the previous two steps.

1. Create an RFC destination to connect to DQM microservices by going to transaction SM59 and clicking New. For details, see Defining RFC Destinations [page 19].

2. Enter a destination name.3. Choose connection type G : HTTP connection to an external server.4. Enter the Target Host and Path Prefix. .

You use what is referred to as an “application URL” for the DQM microservices service running on SAP Cloud Platform. This is the URL you use in this RFC Destination.

NoteWhen you subscribe to DQM microservices you will get a unique SAP Cloud platform account. The URL provided there is to log in to the SAP Cloud Platform Cockpit.

To get the application URL, log in to the SAP Cloud Platform Cockpit and navigate to information about DQM microservices by following these steps:1. Select Services in the menu on the left.2. Select Data Quality Services tile under the Business Services section.3. Select the link Application URL under Service Configuration.4. Use the URL after the label Application URL.

Learn more about the structure of the URL.The first part of the URL contains the target host information, and the second part of the URL contains the path prefix information. Use the URL you were given when you subscribed to DQM microservices.For example, if you received https://previewxb2f051b7-x21b8f5bc.neo.ondemand.com/dq, you would enter previewxb2f051b7-x21b8f5bc.neo.ondemand.com in the Target Host field and /dq/addressCleanse in the Path Prefix field.

5. In the Service No. field, enter 443 .6. If necessary, populate the fields in the HTTP Poxy Options section. If you don't know this information, contact

your IT department.7. Click the Logon & Security tab and choose the Do Not Use a User option under Logon with User.8. In the Security Options section, select Active for SSL.9. Choose the PSE that you set up in steps 1 and 2.10. Click the Special Options tab, and choose Yes (all) under HTTP Cookies.



https://help.sap.com/saphelp_nw75/helpdata/en/49/250a3467cd3895e10000000a421937/content.htm

https://help.sap.com/viewer/d95546360fea44988eb614718ff7e959/Cloud/en-US/68904115d138486aaa2e09eae46e78b1.html

11. Click Connection Test.

NoteWhen you see the HTTP 405 "Method not allowed" message, you have connected successfully. Although in most situations this error message indicates a problem, here it signifies that your configuration settings are correct.

Step 4 – Set up DQM microservices to Trust the Client Certificate Being Sent by the AS ABAP System

In order for SAP Cloud Platform and the DQM microservices service to accept the client certificate sent from the AS ABAP system to authenticate and authorize use, the client certificate must be imported and configured for DQM microservices.

For more information, see "Configuring Client Certificate Authentication" in the Data Quality Management, microservices for location data documentation.

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

CautionSee important information about activating BC Sets for SP 10 in SAP Note 2513615 .

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 8:

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


https://help.sap.com/viewer/d95546360fea44988eb614718ff7e959/Cloud/en-US

https://help.sap.com/viewer/d95546360fea44988eb614718ff7e959/Cloud/en-US

http://help.sap.com/disclaimer?site=https%3A%2F%2Flaunchpad.support.sap.com%2F%23%2Fnotes%2F2513615

BC Set Description Client

/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

/FLDQ/DQAAS_CD1 Used for SAP Data Quality Management microservices for location data.

In addition to /FLDQ/DQAAS_CD1, activate /FLDQ/BASE_CD1 on your non-000 clients.

Also activate /FLDQ/BASE_CI1 on your 000 client.

NoteActivating /FLDQ/DQAAS_CD1 adds records to the /FLDQ/DQ_ENGINES table, allowing the software to use SAP DQM, microservices for postal validation (PV) and geocoding (GEO).

If you are already using DQM for SAP, you may want to add additional entries to the /FLDQ/DQ_ENGINES table. For example, you might add entries if you want to use an on-premise solution for postal validation on most records and then use SAP DQM, microservices for only US addresses. Or, you might want to use an on-premise solution for Match, but SAP DQM, microservices for postal validation.

non-000

/FLDQ/HANA_CI1 Required activation for the 000 (administrator) client, includes client-independent HANA configurations. Activate /FLDQ/HANA_CI1 before you activate /FLDQ/HANA_CD1.

000

/FLDQ/HANA_CD1 Required activation for the target client,includes engine class name and client-dependent HANA configurations. Activate in each target (non-000) client after you have activated /FLDQ/HANA_CI1.

non-000

Activating BC Sets on the Administrator (000) Client

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

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.

Maintain table /FLDQ/DQAAS_CFG in transaction SM30 and add the name of the RFC destination you created earlier.

Related Information

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

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

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


4.3.1 Linking to SAP Reference IMG Structure

1. Log on to client 000 of your system.2. Type S_IMG_EXTENSION into the Command field and click Enter.

3. In the Edit IMG Structure window, 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. Click Enter and then click Save.14. In the Change Request window, click Create in the Change Request window.15. Enter a name for the change request and click Save.16. Click Enter to clear the task dialog.

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



Table 9:

Basis Version Path

7.40 SAP NetWeaver Application Server Basis Services Address Management

SAP Business Objects Data Quality Management

4.3.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.3.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 10:

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.


Field Data

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 11:

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



Field Data

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




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 12]Setting up Data Quality Management IMG Activities [page 17]

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 12:

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 Quality Management, microservices for location dataOptional Post-Installation Setup C U S T O M E R 23

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 13:

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 14:

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

Adding a Transaction Code to the Exception Table

CautionBesides its main purpose, this activity lets you disable postal validation 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 Dialog box to prevent suggestion lists from appearing in dialog boxes.6. Close the window to save the changes and return to the previous window.

TipYou can select and deselect the suppression option 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 15:

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_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_REVIEW_NEW_WIDTH 35 Width by number of characters of the validated address column in the Postal Validation – Review Changes



Parameter Default Value Description

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.

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.

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.

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 16:

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

Related Information

Postal Address Validation [page 39]



5.1.9 IMG: Activate/Deactivate DES Functionality

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.10 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.11 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.12 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 17:

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.13 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.14 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.15 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.1.16 IMG: Activate Duplicate Check and Determine Limit for BAPIs

Use this activity to activate the SAP index pool, to enable batch and transactional matching.

Use transaction SPRO to access the IMG structure. Then locate the following IMG transaction at one of the following, depending on which Basis version you use:

● SAP Web Application Server > Application Server > Basis Services > Address Management > Duplicate Check● SAP NetWeaver > Application Server > Basis Services > Address Management > Duplicate Check

1. Select Activate Duplicate Check and Determine Limit for BAPIs.2. For all index pools that you want active, select the Index Active checkbox.3. For all index pools that you want active,, type 90 (or other desired threshold) in the Threshold BAPIs field.

5.1.17 IMG: Set Limit for Duplicate List in SAP Dialog Boxes

Use this activity to set the desired threshold of duplicates displayed during matching.

Use transaction SPRO to access the IMG structure. Then locate the following IMG transaction at one of the following, depending on which Basis version you use:

● SAP Web Application Server > Application Server > Basis Services > Address Management > Duplicate Check● SAP NetWeaver > Application Server > Basis Services > Address Management > Duplicate Check

1. Select Set Limit for Duplicate List in SAP Dialog Boxes.2. For any tables for which you want to set a threshold, enter that maximum in the Threshold SAP Dialog Box

field.


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

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 15]Creating an Enhancement Set [page 32]Enhancing the Component [page 33]

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.

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 18:

Field Value

Source ID FLDQ

Class /FLDQ/CL_DQ_ENGINE_BASE

Function Module

Destination

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.

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 19:

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 20:

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 21:

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 22:

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 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 23:

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

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.5 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 24: 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 25: 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. In real time, this product validates and standardizes address data before the data is saved to the SAP database.

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 26:

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 27:

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 Quality Management, microservices for location dataPostal Address Validation C U S T O M E R 39

A Troubleshooting

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

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 28:

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.


Troubleshooting

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

A.2 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. The information below explains how regions are mapped to work with this product and how you can change those mappings.

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.

A.3 Product Component Version Report

To create a report showing the version numbers of the Add-On, 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.4 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

User Guide for connecting to SAP Data Quality Management, microservices for location dataTroubleshooting C U S T O M E R 41

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

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

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.


Troubleshooting

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.

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: https://help.sap.com/viewer/disclaimer).

User Guide for connecting to SAP Data Quality Management, microservices for location dataImportant Disclaimers and Legal Information C U S T O M E R 43

https://help.sap.com/viewer/disclaimer

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 https://www.sap.com/corporate/en/legal/copyright.html for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

https://www.sap.com/corporate/en/legal/copyright.html

User Guide for connecting to SAP Data Quality Management ...

Documents

Transcript of User Guide for connecting to SAP Data Quality Management ...