Data Quality Managment for SAP CRM/ERP

Transcription

BusinessObjects™ Data Quality
Management for SAP® CRM/ERP Solutions
User’s Guide
BusinessObjects Data Quality Management for SAP CRM/ERP Solutions 12.0.0
April 2008
1RWLFHV
&RQWDFWLQIRUPDWLRQ
Contact us on the Web at http://www.businessobjects.com/support
If you find any problem with this documentation, please report it to Business Objects
in writing at [email protected].
If your issue concerns a Business Objects product and not the documentation, please
contact our Customer Support experts.
&RS\ULJKW
Copyright © 2008 Business Objects. All rights reserved.
3DWHQWV
Business Objects owns the following U.S. patents, which may cover products that are
offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2,
6,490,593 and 6,289,352.
7UDGHPDUNV
Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise
are trademarks or registered trademarks of Business Objects SA or its affiliated
companies in the United States and other countries. All other names mentioned herein
may be trademarks of their respective owners.
7KLUGSDUW\FRQWULEXWRUV
Business Objects products in this release may contain redistributions of software
licensed from third-party contributors. Some of these individual components may
also be available under alternative licenses. A partial listing of third-party
contributors that have requested or permitted acknowledgments, as well as required
notices, can be found at: http://www.businessobjects.com/thirdparty
%XVLQHVV2EMHFWV'DWD4XDOLW\0DQDJHPHQWIRU6$3&50(536ROXWLRQV8VHU¶V*XLGH
&RQWHQWV
Preface ............................................................................................................ 7
About this guide.........................................................................................7
Don’t miss emails from us .........................................................................7
Access the latest documentation ................................................................7
Conventions ...............................................................................................7
Assumed audience .....................................................................................8
Chapter 1:
Overview ........................................................................................................ 9
Data quality overview ....................................................................................10
What is data quality? ...............................................................................10
What steps are involved in data quality? .................................................10
The results of data quality........................................................................11
What is Data Quality Management for SAP Solutions? ................................12
Components of Data Quality Management for SAP Solutions ...............12
Postal validation engine...........................................................................12
Match engine ...........................................................................................12
Introduction to BusinessObjects Data Services .............................................13
Hub of data quality needs ........................................................................13
Access Data Services documentation on Windows .................................13
Chapter 2:
Installing Data Quality Management for SAP Solutions......................... 15
System requirements ......................................................................................16
Required OSS Notes for your SAP system..............................................16
Requirements for the RFC Server............................................................16
Requirements for the BAdIs ....................................................................16
The installation process..................................................................................17
Install BusinessObjects Data Services ...........................................................18
BusinessObjects Data Services install machine ......................................18
BusinessObjects Data Services must be running.....................................18
Install the Data Services Component .............................................................19
Install the Data Services Component.......................................................19
Edit DQ_SAP_DS Datastore properties ..................................................19
Use global variables to disable engines ...................................................20
Create the batch RDBMS staging tables .................................................20
Configure jobs as services .......................................................................21
Install the RFC Server ....................................................................................24
Install a dedicated RFC Server for batch duplicate search ......................24
Install the RFC Server .............................................................................24
Start the RFC Server................................................................................25
Stop the RFC Server ................................................................................25
Install the BAdIs.............................................................................................26
Step 1: Import the Data Quality Management package on client 000.....26
Step 2: Insert the Data Quality Management IMG structure on client
000 ...........................................................................................................29
&RQWHQWV
Step 3: Activate the Business Configuration Sets on each target client.. 30
SAP handshake with RFC Server .................................................................. 32
Purpose of the activity............................................................................. 32
Define the RFC destination ..................................................................... 32
Load supported country codes ....................................................................... 34
Running the transaction and report ......................................................... 34
Activate duplicate check index pools ............................................................ 35
Activate the index pools.......................................................................... 35
Quarterly Adjustment Reports ....................................................................... 37
Report RSADRQU1................................................................................ 37
Report /FLDQ/RSADRQU2 ................................................................... 38
Report RSADRQU3................................................................................ 39
Quarterly Adjustment custom error report .............................................. 40
Run the initial setup program......................................................................... 41
Purpose of initial setup............................................................................ 41
Run the initial setup................................................................................. 41
Install and configure Data Quality Management into the IC WebClient ...... 42
Requirements for running in an IC WebClient profile............................ 42
Postal validation with the IC WebClient................................................. 42
Summary of configuration tasks ............................................................. 42
Activate the BSP BC Sets ....................................................................... 42
Configure IC WebClients to use Data Quality Management views and
controllers................................................................................................ 43
Activate the /FLDQ/BSP_DQ service..................................................... 44
Add postal validation functionality to other IC WebClient views .......... 44
Disable the Postal Validation BAdI for the IC WebClient ..................... 46
To create new address records ................................................................ 46
Chapter 3:
Configuring through the IMG ................................................................... 47
Locating the Data Quality Management for SAP Solutions IMG activities.. 48
SAP handshake with RFC server................................................................... 49
Maintain Supported Countries ....................................................................... 50
Remove the country codes ...................................................................... 50
Maintain exception table of transaction codes............................................... 51
Add a transaction code to the exception table......................................... 51
Maintain table to activate SAP postal code check before postal validation .. 54
Add a country to the table ....................................................................... 54
Maintain fields for address reviewer ............................................................. 55
Fields and order for standard street addresses......................................... 55
Fields and order for P.O. Box addresses ................................................. 55
Make changes to the fields for the address reviewer .............................. 55
Maintain fields for duplicate hit list display .................................................. 57
Fields and order for error tolerant search and duplicate search .............. 57
Make changes to the fields for the duplicate hit list display ................... 58
Maintain operating parameters ...................................................................... 59
Operating parameters .............................................................................. 59
Modify the parameters ............................................................................ 60
Map address types for Quarterly Adjustment ................................................ 61
Defining mappings .................................................................................. 61
Predefined mappings ............................................................................... 61
Add a mapping for an Address Type Code ............................................. 61
%XVLQHVV2EMHFWV'DWD4XDOLW\;,IRU6$36ROXWLRQV8VHU¶V*XLGH
Chapter 4:
Configuring the RFC Server ...................................................................... 63
Configuring through flrfcsrv.xml...................................................................64
Location of flrfcsrv.xml ...........................................................................64
Editing flrfcsrv.xml..................................................................................64
SAP settings and DQ Server settings.......................................................64
File settings..............................................................................................64
General settings .......................................................................................66
Dataflows.................................................................................................67
Overrides..................................................................................................67
Chapter 5:
Postal address validation ............................................................................ 69
Interactive cleansing with Data Quality Management for SAP Solutions .....70
Using interactive cleansing......................................................................70
Multiple suggestions................................................................................71
Batch cleansing with Quarterly Adjustment Reports.....................................72
Chapter 6:
Duplicate check and error tolerant search ............................................... 73
Understanding duplicate check and error tolerant search ..............................74
Duplicate check .......................................................................................74
Error tolerant search ................................................................................74
Break Keys...............................................................................................74
Understanding break keys and data fields......................................................75
How BusinessObjects Data Services determines a break key .................75
Configure the break key settings .............................................................76
Match on name data.................................................................................76
Using duplicate check ....................................................................................77
Interactive mode ......................................................................................77
Batch mode ..............................................................................................78
Using error tolerant search .............................................................................80
The hit list ................................................................................................80
Fields displayed .......................................................................................81
Chapter 7:
Tips and troubleshooting ............................................................................ 83
Installation troubleshooting............................................................................84
Checking the RFC Server(s) connection .................................................84
Connection to the RFC Server closed......................................................84
Troubleshooting Unicode issues..............................................................84
Postal validation and duplicate check/error tolerant search troubleshooting .86
Using the sample input files to test Jobs..................................................86
Inability to save addresses for which the postal code cannot be
completed.................................................................................................86
Records created without break keys due to downtime of RFC Server ....86
Records not stored in pending update table when search disabled..........87
Understanding regions .............................................................................87
Newfoundland region code for R/3 4.60 and 4.70...................................87
RSMTCCODE program error message ...................................................88
Include records with empty break keys ...................................................88
Duplicate hit list not appearing as expected ............................................88
Threshold values for duplicates ...............................................................88
&RQWHQWV
Addresses do not validate/Error T528..................................................... 89
DPV processing locked ........................................................................... 89
RFC Server Troubleshooting ......................................................................... 90
Output manifest information ................................................................... 90
Appendix A:
BusinessObjects Data Services Jobs and Options..................................... 91
BusinessObjects Data Services jobs........................................................ 91
Combine House Num and PMB option................................................... 92
Appendix B:
Error Codes .................................................................................................. 95
Technical error codes .............................................................................. 95
Postal validation error codes ................................................................... 98
Duplicate check error code...................................................................... 99
Appendix C:
External List Management ....................................................................... 101
Using Data Quality Management for SAP Solutions with ELM................. 102
Cleansing the external list prior to loading via ELM ............................ 102
ELM functionality for different versions of SAP CRM........................ 102
Records with only name data ................................................................ 102
Index........................................................................................................... 103
%XVLQHVV2EMHFWV'DWD4XDOLW\;,IRU6$36ROXWLRQV8VHU¶V*XLGH
3UHIDFH
$ERXWWKLVJXLGH
This guide provides a general overview of BusinessObjects Data Quality
Management for SAP CRM/ERP Solutions as well as specific information for
installing and integrating this product into your SAP environment.
'RQ
WPLVVHPDLOV
IURPXV
Email messages concerning this product come from a different address now. Ever
since Business Objects purchased Firstlogic, Inc. in April 2006, email messages
from us have come from a businessobjects.com email address. Make sure that
your email system does not unintentionally filter these messages to a spam, trash,
or quarantine area where you might miss them. We don’t want any important
news about your product to not reach you.
$FFHVVWKHODWHVW
GRFXPHQWDWLRQ
In addition to the documentation installed on your computer during installation of
this product, you can access all the supported Business Objects documentation
from the Business Objects Customer Support site.
1. Go to http://www.businessobjects.com.
2. From the “Support” pull-down menu, choose Documentation.
3. On the “Documentation” screen, choose Product Guides and navigate to the
document that you want to view.
You can view the PDFs online or save them to your computer.
&RQYHQWLRQV
This document follows these conventions:
&RQYHQWLRQ
'HVFULSWLRQ
Bold
We use bold type for file names, paths, emphasis, and text that you
should type exactly as shown. For example, “Type cd\ dirs.”
Italics
We use italics for emphasis and text for which you should substitute
your own data or values. For example, “Type a name for your file,
and the .txt extension (testfile.txt).”
Menu commands We indicate commands that you choose from menus in the following
format: Menu Name > Command Name. For example, “Choose File
> New.”
We use this symbol to alert you to important information and potential problems.
We use this symbol to point out special cases that you should know
about.
We use this symbol to draw your attention to tips that may be useful
to you.
$VVXPHGDXGLHQFH
This guide assumes that the people responsible for integrating and using Data
Quality for SAP Solutions are experienced administrators and users of SAP R/3®,
SAP ERP Central Component (SAP ERC), and SAP Customer Relationship
Management (SAP CRM) solutions. If you are implementing the IC WebClient
postal validation and search capabilities, this guide also assumes that you are
aware of any settings and customizations you have made to your IC WebClient
configuration before installing this product.
This guide does not explain basic operation of the SAP environment. For
questions about the SAP environment, consult the appropriate SAP
documentation or SAP technical support.
This guide also does not explain the operation of the Data Quality server or
Project Architect. For specific questions about Data Quality, consult the Data
Quality documentation that is included in this package.
&KDSWHU
2YHUYLHZ
Before using BusinessObjects Data Quality Management for SAP CRM/ERP
Solutions, you should understand some of the concepts of data quality. A basic
familiarity with these concepts helps you to understand what Data Quality
Management for SAP Solutions does, how it works with your existing SAP
environment, and why your organization benefits from data quality.
&KDSWHU2YHUYLHZ
'DWDTXDOLW\RYHUYLHZ
:KDWLVGDWDTXDOLW\"
Data quality is a process of arranging customer information in a standardized,
validated, and consistent order. The process also helps you to avoid duplicate data
entries and adds value by creating a single and accurate view of your customers.
:KDWVWHSVDUH
LQYROYHGLQGDWD
TXDOLW\"
Generally, data quality requires these main steps:
3DUVLQJ
Parsinginvolves checking the structure and content of each field of a contact’s
information. During parsing, checks ensure that data appears where it belongs; an
address does not appear in a name field, for example. Some of the more common
elements to search for in a record during parsing include first and last name, street
number and name, region, and postal code.
&RUUHFWLRQ
To correct data, Data Quality Management for SAP Solutions uses secondary data
sources, such as the U.S. Postal Service’s National Directory or an international
postal directory, to check and validate address information. Using these
secondary sources, Data Quality Management for SAP Solutions can check, for
example, whether La Crosse, Wisconsin is associated with the ZIP Code 54601,
whether Harbor Plaza is actually a valid street name in La Crosse, and whether
100 is a valid address for that street.

parsing
correction
standardization
duplicate matching
6WDQGDUGL]DWLRQ
After correcting the data, Data Quality Management for SAP Solutions can
standardize the data. Standardization works in conjunction with correction and
parsing as it arranges customer information in a consistent and preferred format.
Examples of standardization include removal of dashes from a phone number or
Social Security number, use of a common abbreviation such as DEPT for
department number, or common representations of title such as Mr., Ms., Mrs.,
and Jr. It also includes the application of standard address elements such as
converting Street to St and converting South West to SW.
'XSOLFDWH0DWFKLQJ
Once a standardized customer record exists, matching should become part of the
data quality analysis to eliminate redundancies. During the matching step, the
software searches existing customer data records in real time using specific
business-defined criteria to look for similar records. If no match is found, the data
quality process is complete. If a match is found, however, then the user is offered
the opportunity to determine whether the newly entered record matches the
suggested existing record.
Duplicate matching technology even allows the user to search for records based
on partial information.
7KHUHVXOWVRIGDWD
TXDOLW\
These data quality concepts provide a foundation that helps a business to develop
a clear picture of the customer, which can improve both efficiency and
effectiveness. Because there are so many touch points for customer data in an
organization, this activity has far-reaching implications in how you conduct
business on a day-to-day basis.
&KDSWHU2YHUYLHZ
:KDWLV'DWD4XDOLW\0DQDJHPHQWIRU6$36ROXWLRQV"
Data Quality Management for SAP Solutions is software that enhances parts of
your SAP installation. SAP can stand alone without having Data Quality
Management for SAP Solutions installed. But without Data Quality Management
for SAP Solutions, you would not attain the benefits of data quality. Data Quality
Management for SAP Solutions takes care of the correction, standardization, and
duplicate matching steps in the data quality process.
&RPSRQHQWVRI'DWD
4XDOLW\0DQDJHPHQW
IRU6$36ROXWLRQV
Data Quality Management for SAP Solutions consists of these components:

3RVWDOYDOLGDWLRQ
HQJLQH
BusinessObjects Data Services XI Release 3.0, which handles data quality
processing tasks on the data it receives from the RFC Server.
Data Services Component, which provide functionality in BusinessObjects
Data Services that is specific to this product.
The RFC Server, which receives and returns data sent from the SAP
environment through TCP/IP.
Three Business Add-Ins (BAdI) that are integrated directly into the SAP
environment for postal validation, duplicate check, and error tolerant search.
The postal validation engine of Data Quality Management for SAP Solutions
relies on the BusinessObjects Data Services address directories compiled from
postal authorities such as the United States Post Office. Data Quality
Management for SAP Solutions can cleanse both U.S. and global addresses.
The postal validation engine is integrated into your SAP system through SAP’s
Business Address Services–Postal Validation (PV) interface.
0DWFKHQJLQH
The match engine of Data Quality Management for SAP Solutions brings
sophisticated record-matching technology to your SAP applications. The criteria
for deciding which records are a potential match are controlled by business rules
that you can customize to your needs. When you enter a record that is a potential
duplicate, you have the option of choosing which of the duplicate records to keep.
The match engine is integrated into your SAP system through SAP’s Business
Address Services (BAS)–Duplicate Check, Error Tolerant Search (DES)
interface.
,QWURGXFWLRQWR%XVLQHVV2EMHFWV'DWD6HUYLFHV
As a Data Quality Management for SAP Solutions user, you may be wondering
what BusinessObjects Data Services is and what it means to you.
After installation, you can use Data Quality Management for SAP Solutions with
little thought given to BusinessObjects Data Services, because it handles the data
quality processes behind the scenes. The version of BusinessObjects Data
Services shipped as part of Data Quality Management for SAP Solutions is
customized to run only as part of Data Quality Management for SAP Solutions,
but the technology of BusinessObjects Data Services offers other potential
solutions to your enterprise’s data quality needs. This section provides an
overview of what BusinessObjects Data Services does, independent of its use
within Data Quality Management for SAP Solutions, and tells you where you can
find more information about BusinessObjects Data Services.
+XERIGDWDTXDOLW\
QHHGV
BusinessObjects Data Services is the next generation data quality platform that
allows you to tie in all of your data quality needs to a single “hub.” Many
customers of Data Quality Management for SAP Solutions also have data quality
needs in other applications or other areas of their enterprise. Instead of having
many disparate solutions for each area of your enterprise, you can use
BusinessObjects Data Services as the backbone for all of your data quality needs.
With BusinessObjects Data Services, you can centralize and standardize this
processing through the following BusinessObjects Data Services features.
&HQWUDOL]HGEXVLQHVVUXOH
UHSRVLWRU\
All of the business rule definitions are stored in a single repository that can be
shared by all applications that use BusinessObjects Data Services. You can
organize business rules into reusable objects that can be shared to meet your
enterprise requirements.
You can use the same objects in a project for Data Quality Management for SAP
Solutions, your own custom application that incorporates BusinessObjects Data
Services, or direct batch processing through BusinessObjects Data Services itself.
This means that you can create data quality standards that are truly shared across
your entire enterprise.
$FFHVV'DWD6HUYLFHV
GRFXPHQWDWLRQRQ
:LQGRZV
After installing BusinessObjects Data Services, Windows users can access the
documentation from shortcuts on the Start menu.
Documentation is installed as a separate component. The documentation
for BusinessObjects Data Services is an optional installation component in
most cases. If you don’t install the documentation while installing
BusinessObjects Data Services, it won’t be available on your system.
To access the documentation:
1. Choose Start > Programs > BusinessObjects XI 3.0 >
BusinessObjects Data Services > Data Services Documentation.
2. Click the appropriate shortcut for the documentation you want to view.
&KDSWHU2YHUYLHZ
&KDSWHU
,QVWDOOLQJ'DWD4XDOLW\0DQDJHPHQWIRU
6$36ROXWLRQV
This section explains the requirements and procedures for installing
BusinessObjects Data Quality Management for SAP CRM/ERP Solutions.
Access the Business Objects Electronic Software Download (ESD) site at https://
businessobjects.subscribenet.com/control/bobj/login. After you log in, select
Products - Purchased to see a list of available downloads.
The installation for Data Quality Management for SAP Solutions includes
installing the following components:
BusinessObjects Data Services
Data Quality Management for SAP Solutions Data Services Component
Data Quality Management for SAP Solutions RFC server
Data Quality Management for SAP Solutions Business Add-Ins (BAdIs)
&KDSWHU,QVWDOOLQJ'DWD4XDOLW\0DQDJHPHQWIRU6$36ROXWLRQV
6\VWHPUHTXLUHPHQWV
This section contains the requirements for your SAP system, the RFC Server, and
the BAdIs.
5HTXLUHG2661RWHV
IRU\RXU6$3V\VWHP
You must have installed the following Online Service System (OSS) Notes on
your SAP system.
2661RWH
'HVFULSWLRQ
196958
Collective note: Errors in interface for duplicate check
197217
Composite note: Various errors in quarterly adjustment
197803
Composite note: Error with interface for address check
710565
Termination with AM897 when calling
ADDR_PERSONAL_GET_ARRAY
5HTXLUHPHQWVIRUWKH
5)&6HUYHU
The RFC Server requires the following environments.
6XSSRUWHG:LQGRZV
RSHUDWLQJV\VWHPV
Windows XP (32 bit)
5)&6HUYHUSHUPLVVLRQV
IRU:LQGRZV6HUYHU
In Windows 2003 Server, the user account that runs the RFC Server must have
full permissions to access the subdirectories that contain the address directories.
-DYD5XQWLPH
(QYLURQPHQW
The machine on which you install Data Quality for SAP Solutions must run the
32-bit version of the Java 2 Platform, Standard Edition (J2SE) version 1.5 or
higher.
Windows 2003 Server (32 bit)
An installable version of the J2SE is not included in this software package. You
must acquire, install, and run the J2SE independently of the installation and
before the installation of Data Quality Management for SAP Solutions.
5HTXLUHPHQWVIRUWKH
%$G,V
The BAdIs portion of Data Quality Management for SAP Solutions requires the
following environment:
SAP Customer Relationship Management (SAP CRM) solutions v4.0 (with
Basis/ABAP SP 39) and higher.
SAP R/3 v4.6 (with Basis/ABAP SP 46) and higher.
ECC 5.0 (ERP2004) and higher.
7KHLQVWDOODWLRQSURFHVV
The installation of Data Quality Management for SAP Solutions requires these
tasks:
Outside of your SAP system:
1. Install BusinessObjects Data Services
2. Install Data Services Component
3. Install the RFC Server
4. Create the repository staging table
On your SAP system:
5. Install the Data Quality Management Business Add-Ins (BAdIs)
6. Perform the “SAP handshake with RFC server” IMG activity
7. Load the supported countries
8. Activate duplicate check index pools.
9. Run Quarterly Adjustments.
10. Run the initial setup program.
,QVWDOO%XVLQHVV2EMHFWV'DWD6HUYLFHV
You must install BusinessObjects Data Services before installing the RFC Server
or BAdIs. Find instructions for installing, configuring, and running
BusinessObjects Data Services in the Data Services Installation Guide.
This section contains considerations to help you successfully install
BusinessObjects Data Services for use with this product.
%XVLQHVV2EMHFWV'DWD
6HUYLFHVLQVWDOO
PDFKLQH
You can install BusinessObjects Data Services on the same machine as the RFC
Server, on a different machine, or even on a machine with a different operating
system than the one that contains your installation of the RFC Server. Information
about the system requirements for the machine on which you install
BusinessObjects Data Services are included with the Data Services
documentation.
%XVLQHVV2EMHFWV'DWD
6HUYLFHVPXVWEH
UXQQLQJ
You must have BusinessObjects Data Services running during the remaining
installation procedures of this product, and during its operation.
,QVWDOOWKH'DWD6HUYLFHV&RPSRQHQW
After you install BusinessObjects Data Services, you install the Data Services
Component that is specific to this product and then perform configuration tasks.
This section describes installing and configuring the Data Services Component.
,QVWDOOWKH'DWD
6HUYLFHV&RPSRQHQW
Install the Data Services Component on the machine you installed
BusinessObjects Data Services. To install the Data Services Component:
1. Locate the BusinessObjects Data Quality Management for SAP CRM/ERP
Solutions - Data Services Component media and launch setup.exe.
2. In the Welcome screen, click Next.
3. If the installation routine cannot detect your version of BusinessObjects Data
Services, the Confirmation Requested window appears. If the window
appears, click Yes to confirm that you have first installed BusinessObjects
Data Services.
4. Read the license agreement and, if you accept the license agreement terms,
choose “I accept the terms of the license agreement” and click Next.
5. In the Choose Destination Locations window, accept the default installation
location or specify a different location. Click Next
Though you can use the Browse button to change the destination folder,
Business Objects recommends that you install to the default directory,
and you must install to a path that finishes with [your_path]\
BusinessObjects\DataQuality_for_SAP.
6. In the RDBMS Selection window, choose the database type you intend to use
for the creation of staging tables, and click Next.
The window that follows this step varies, depending on which database type
you chose. Each database type requires different connection data.
7. In the Connection Parameters window that appears for your database type,
enter the database connection information and click Next.
8. In the Ready to Install the Program window, click Install. The windows
update for each steps in the installation routine.
9. Click Finish when the installation has completed.
The Data Services Component is now installed to your BusinessObjects Data
Services system, but you must perform post-installation steps to configure
BusinessObjects Data Services.
(GLW'4B6$3B'6
'DWDVWRUHSURSHUWLHV
You muse edit the DQ_SAP_DS Datastore properties to set the password for the
RDMBS user. To edit the DQ_SAP_DS Datastore properties:
1. In the Data Services Designer, go to the Datastores tab of the Local Object
Library. Right-click on DQ_SAP_DS Datastore and select Edit.
2. Set the password in the Edit Datastore DQ_SAP_DS window for the
RDMBS user. Click OK.
8VHJOREDOYDULDEOHV
WRGLVDEOHHQJLQHV
For this product to function properly, you must disable the address cleanse
engines for countries you did not purchase.
The table below lists the Data Quality Management for SAP Solutions country
engine substitution parameters.
6XEVWLWXWLRQSDUDPHWHU
'HVFULSWLRQ
$$DQ_SAP_EngineUsa
Enable or disable the USA engine
$$DQ_SAP_EngineAustralia
Enable or disable the Australia engine
$$DQ_SAP_EngineCanada
Enable or disable the Canada engine
$$DQ_SAP_EngineEmea
Enable or disable the EMEA engine
$$DQ_SAP_EngineGlobalAddress
Enable or disable the Global Address
engine
$$DQ_SAP_EngineJapan
Enable or disable the Japan engine
$$DQ_SAP_EngineMultiCountry
Enable or disable the Multi Country
engine
If you have created your own substitution parameter configurations, make
sure that you include them in this process. You must perform the steps to
disable unpurchased address cleanse engines for al the $$DQ_SAP_*
substitution parameters in any configuration you use with this product.
To disable address cleanse engines:
1. In the Data Services Designer, go to Tools > Substitution Parameter
Configurations.
2. In the Substitution Parameter Editor, select one of the country engine
substitution variables from the list that represents a country address cleanse
engine that you did not purchase.
3. Set the parameter to NO to disable the engine for every address cleanse
engine you have not purchased. You must perform this step for every
configuration you use. If you did not purchase an address cleanse engine and
the corresponding value is set to YES or is blank, this product cannot
function properly.
4. After you have set the appropriate value for all the Substitution Parameters,
click OK.
&UHDWHWKHEDWFK
5'%06VWDJLQJWDEOHV
Next, you create batch processing staging tables, which this product uses in the
transfer or data to and from BusinessObjects Data Services.
You must have an appropriate database client installed and a connection
(such as an Oracle TNS entry) to the database created.
To create the Staging Table RDBMS tables:
1. In the Data Services Designer, go to the Jobs tab of the Local Object Library.
In the Batch Jobs hierarchy, select the job DQCreateStageTables. The
DQCreateStageTables is now visible in the Designer.
2. With the job DQCreateStageTables active, select Debug > Execute (or press
F8) to execute the job.
3. In the Execution Properties window, select the appropriate configuration
from the System configuration drop-down list.
The job executes. The system may produce a warning message due to the script
job attempting to run a Drop Table command on a database table that does not
exist. This message is expected and does not affect the successful configuration
of this product.
&RQILJXUHMREVDV
VHUYLFHV
After you install the Data Services Component, you must publish the Data
Quality Management for SAP Solutions jobs (.atl files) as services.
/LVWRIMREVDQGWKHLU
VHUYLFHQDPHV
Configure jobs as services for all of the jobs listed in the table by following the
steps in “To configure jobs as services” on page 21.
-RE
6HUYLFHQDPH
Job_Batch_DQ_SAP_Address_Cleanse
Service_Batch_DQ_SAP_Address_
Cleanse
Job_Realtime_DQ_SAP_Address_
Cleanse
Service_Realtime_DQ_SAP_Address_
Cleanse
Job_Realtime_DQ_SAP_Address_
Cleanse_Suggestions
Service_Realtime_DQ_SAP_Address_
Cleanse_Suggestions
Job_Realtime_DQ_SAP_Create_Break_
Keys
Service_Realtime_DQ_SAP_Create_
Break_Keys
Job_Realtime_DQ_SAP_Name_And_
Address_Match
Service_Realtime_DQ_SAP_Name_And_
Address_Match
Address_Match_Cleanup
Address_Match_Cleanup
Address_Match_Load
Address_Match_Load
Address_Match_Results
Address_Match_Results
Job_Realtime_DQ_SAP_Retrieve_
Country_Purchased
Service_Realtime_DQ_SAP_Retrieve_
Country_Purchased
Job_Realtime_DQ_SAP_US_DPV_
Address_Cleanse_Suggestions
Service_Realtime_DQ_SAP_US_DPV_
Address_Cleanse_Suggestions
Job_Realtime_DQ_UC_Init_Batch_Match Service_Realtime_DQ_UC_Init_Batch_
Match
Job_Realtime_DQ_UC_Update_Batch_
Status
7RFRQILJXUHMREVDV
VHUYLFHV
Service_Realtime_DQ_UC_Update_
Batch_Status
You must perform this procedure for each job listed in the preceding table. To
configure jobs as services:
1. Open the Data Services Management Console and login.
2. Click Administrator.
3. In the file tree expand Real-Time and select the server that you set up when
you installed BusinessObjects Data Services.
4. Select Real-Time Service from the file tree on the left and open the RealTime Service Configuration tab on the right.
5. Click Add.
6. In the Service Configuration window click Browse Jobs.
7. Select a job name (listed in the preceding table). For example, select
Job_Batch_DQ_SAP_Address_Cleanse.
8. Enter the service name for the job. For example,
Service_Batch_DQ_SAP_Address_Cleanse (exact case is required) for the
Service Name.
9. Enter 800 for the Processing Timeout value and click Apply.
10. Repeat steps 4 through 9 for each of the Real-time job listed in the preceding
table.
(QDEOHRUGLVDEOHDQ
DGGUHVVHQJLQH
If necessary, you can enable or disable an address engine for a particular service
in the Data Services Management Console.
1. In the Real-Time Service Configuration tab, the Add dialog, click Add
Overridden Parameter
2. Select the override parameter for the engine that you want to enable or
disable. For example, to enable or disable the Canada engine, select
$$DQ_SAP_EngineCanada.
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.
7RFRQILJXUH:HE6HUYLFHV
You must next configure Web Services. To configure Web Services:
1. Keep the Data Services Management Console open from the previous steps,
or open and login to the Data Services Management Console and click
Administrator.
2. Select Web Services from the file tree at left and open the Web Services
Configuration tab on the right.
3. Select Add Real-Time Service from the drop-down menu and click Apply.
All of the service names that you entered in To configure jobs as services
appear in the list.
4. Choose Select All and click Add.
7RVWDUWWKHVHUYLFHV
After you have configured both the jobs and Web Services, you must start the
services. To start the services:
1. Keep the Data Services Management Console open from the previous steps,
or open and login to the Data Services Management Console and click
Administrator.
2. Select Real-Time Services from the file tree at left and open the Real-Time
Services Status tab on the right.
3. Select all of the services that you created and click Start.
It may take a few minutes for the services to start. If you are not certain the
services started, check that the Business Objects Address Server is started. In
Windows, look in the Services window to see the status of all services.
After you have performed the automatic services start, you must shutdown and
restart the services manually if you change the configurations.
,QVWDOOWKH5)&6HUYHU
After you install and configure BusinessObjects Data Services, and install the
Data Services Component, you install the RFC Server. This section describes
installing and running the RFC server.
You must install the RFC Server from a user account that has permissions to
install software on the machine.
,QVWDOODGHGLFDWHG
5)&6HUYHUIRUEDWFK
GXSOLFDWHVHDUFK
To run duplicate search functionality in batch mode (often called “batch match”),
you must install and run a dedicated RFC Server, in addition to the RFC Server
installed to run all other operations associated with Data Quality Management for
SAP Solutions.
For more information about setting and configuring this dedicated RFC Server,
see “Maintain operating parameters” on page 59.
For information about running duplicate search in batch mode, see “Batch mode”
on page 78.
,QVWDOOWKH5)&6HUYHU
Install the RFC Server on a machine that meets the system requirements
(“Requirements for the RFC Server” on page 16). To install the RFC Server:
1. Locate the BusinessObjects Data Quality Management for SAP CRM/ERP
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. In the Choose Destination Locations window, accept the default installation
location or specify a different location. Click Next
By default, the installation routine installs the RFC Server to the folder
C:\Program Files\BusinessObjects\DataQuality_for_SAP. Though
you can use the Browse button to change the destination folder, Business
Objects recommends that you install to this default directory, and you
must install to a path that finishes with [your_path]\BusinessObjects\
DataQuality_for_SAP.
5. In the SAP Information window, enter the Host Name and Service of the SAP
Gateway.
You can use either the name or IP address of the SAP Gateway for the
host name.
6. Select Yes or No to indicate whether your SAP system is Unicode compliant.
Click Next.
If your system is Unicode compliant, the step “SAP handshake with
RFC Server” on page 32 has further configuration instructions on
configuring Data Quality Management for SAP Solutions for Unicode
systems.
7. In the SAP Basis window select the version of your SAP Basis. (The installer
uses different files depending on your Basis version.) Click Next.
8. In the Data Services Connection window, enter the Data Services hostname,
port number (default is 4000), and the URL of the Data Services Web server
(default is http://<hostname>:28080/DataServices/servlet/
webservices?ver=2.0&wsdlxml). Click Next.
9. In the Ready to Install the Program window, click Install. The installation
proceeds
10. Click Finish when the installation has completed.
6WDUWWKH5)&6HUYHU
You can find the batch file to start the RFC Server in the install directory of the
machine on which you installed the RFC Server.
install_directory\start_rfcserver.bat
You can launch this file from the command line or in Windows by doubleclicking the file in the Windows Explorer.
When the RFC Server starts, it looks for the SAP Gateway and your
installation of BusinessObjects Data Services. Therefore, you should have
both the SAP Gateway and BusinessObjects Data Services running before
starting the RFC Server. If the BusinessObjects Data Services portion of this
product is stopped for any reason, you must restart BusinessObjects Data
Services and then restart the RFC Server to reinitialize the Data Services
dataflows.
Additionally, the RFC Server looks for the Java Runtime Environment.
Therefore, the Java runtime must be installed relative to where the RFC
Server startup script runs, or you must set the JAVA_HOME environment
variable to where Java is installed so that the RFC Server can find it.
6WRSWKH5)&6HUYHU
Follow these steps to stop the RFC Server:
1. Use transaction SMGW. For information on the use and syntax of transaction
SMGW, consult your SAP documentation.
Using transaction SMGW is the preferred method to stop the RFC Server.
However, if you are running multiple RFC Servers with the same TP name,
this method may simultaneously stop all RFC Servers with that TP name (for
more information, see SAP Note 923248).
2. On the machine that hosts the RFC server, use Ctrl-C in the RFC Server
console to terminate the RFC Server process. Note that this method may on
rare occasion cause SAP to show a connection to the RFC Server after the
RFC Server has stopped.
,QVWDOOWKH%$G,V
The RFC Server must be running to install the Data Quality Management for SAP
Solutions Business Add-Ins (BAdIs).
Before you proceed with these steps, make sure that your SAP system complies
with all of the prerequisites described in “System requirements” on page 16.
Because of the variety of SAP versions, the illustrations that we use
throughout these procedures may differ from what you encounter while
installing BAdIs on your specific version of SAP Solution. We assume that
you have knowledge of SAP administration to help you successfully
navigate through the installation. Even though the screens may differ from
version to version, follow all steps in these processes.
To install the BAdIs on your system, you must complete these tasks:
“Step 1: Import the Data Quality Management package on client 000” on page 26
“Step 2: Insert the Data Quality Management IMG structure on client 000” on
page 29
“Step 3: Activate the Business Configuration Sets on each target client” on
page 30
The BAdIs are installed and upgraded using the Add-on Installation Tool,
invoked by the transaction SAINT.
6WHS,PSRUWWKH
'DWD4XDOLW\
0DQDJHPHQWSDFNDJH
RQFOLHQW
The reference client (client 000) is the Data Quality Management for SAP
Solutions package that you import using the SAP Add-on Installation Tool. Make
sure that the contents of Data Quality Management for SAP Solutions PV and
DES BAdIs file is located on a disk or network drive.
Choose an applicable .SAR package from the tables below.
%DVLVF
6$5ILOH
1HZLQVWDOORUXSJUDGH
\4.6\DATA\SAPK-39ACOINFLDQ.SAR
New install
\4.6\DATA\UPGRADE\SAPK-39ACHINFLDQ.SAR
Upgrade
You must (re)activate BC Set /FLDQ/AAK25 to import new customizing
data.
%DVLV
6$5ILOH
1HZLQVWDOORUXSJUDGH
New install
Upgrade
You must (re)activate BC Set /FLDQ/47U6X to import new customizing
data.
%DVLV
6$5ILOH
1HZLQVWDOORUXSJUDGH
New install
Upgrade (from 2.00c Rev 3
or above)
You must (re)activate BC Set /FLDQ/47U6X to import new customizing
data.
%DVLV
6$5ILOH
1HZLQVWDOORUXSJUDGH
New install
Upgrade from 2.00c Rev
3 or above
Basis 7.00 users must have the SPAM 21 update/patch or greater to be able
to load the .SAR package. (For more information, see SAP Note 822379.)
Also, you must (re)activate BC Set /FLDQ/47U6X to import new
customizing data.
3DFNDJHIRUXVHZLWKWKH
,&:HE&OLHQW
Basis 6.20 and 7.00 users: If you intend to use the functionality of Data Quality
Management for SAP Solutions within the IC WebClient, you must import a
second .SAR file, SAPK-39DCHINFLDQ.SAR.
For information about the requirements and configuration procedures to use the
functionality of Data Quality Management for SAP Solutions within the IC
WebClient, see “Install and configure Data Quality Management into the IC
WebClient” on page 42.
,PSRUWLQJWKH'DWD
4XDOLW\0DQDJHPHQW
SDFNDJH
To import the Data Quality Management for SAP Solutions package:
1. Enter the transaction SAINT to open the Add-On Installation Tool window.
2. Click the Installation packages menu and choose Load packages > From
Frontend.
3. In the Select CAR/SAR archive window, browse to the \DATA directory of
the Data Quality Management for SAP Solutions SAP – PV and DES BAdIs
installation media, and select the applicable .SAR file.
4. Click Open and then click Yes to load the .SAR file. The contents of the
compressed .SAR file appears.
5. Click Decompress to view a list of Data Quality Management for SAP
Solutions BAdIs in the Installable add-on and PCS Packages for your system
table.
6. Click Continue. A confirmation window is displayed indicating that the Addon FLDQ will be installed.
7. Click Enter to confirm the installation. (This takes approximately five
minutes.)
8. After the install completes, click Finish. Also, after the install completes, you
can choose to view logs.
9. When you have installed all of the BAdIs, click Cancel to close the Add-on
Installation tool.
6WHS,QVHUWWKH
'DWD4XDOLW\
0DQDJHPHQW,0*
VWUXFWXUHRQFOLHQW
After you import the BAdIs, you link the Data Quality Management for SAP
Solutions IMG (Implementation Management Guide) structure to your SAP
Reference IMG structure.
1. Log on to client 000 of your system.
2. Type S_IMG_EXTENSION into the Command field and click Enter.
3. In the Edit IMG Structure window select the Possible Entries icon located
next to the IMG Structure field.
4. In the Find Structure window, type Address Management for the Title and
click Execute.
A confirmation appears that the Address management structure exists.
5. Double-click the Address Management node to return to
S_IMG_EXTENSION.
6. Click the Possible Entries icon in the Enhancement ID field and double-click
/FLDQ/AD_IMG to open the Edit IMG Structure window.
7. Click Enhance Structure. One or possibly two Information dialogs appear.
8. Click Enter in each Information dialog to clear the dialog boxes.
9. Select the last of the Address Management sub nodes and choose Edit >
Nodes > Insert IMG Structure > On Same Level.
10. Click Find in the Reference to a Structure window, and type BusinessObjects
in the Title. Click Execute.
11. Double-click BusinessObjects : Global Data Quality Connector to open the
Reference to a Structure window.
12. Copy the field in “The node refers to the structure” and paste it into the Node
Name field.
13. Click Enter and then click Save.
14. Click Create in the Change Request window.
15. Enter a name for the change request and click Save.
16. Click Enter to clear the task dialog.
9HULI\LQVHUWLRQ
To verify that the Data Quality Management for SAP Solutions IMG structure is
correctly inserted into the SAP Reference IMG structure, follow these steps:
1. Enter transaction /nSPRO in the command box.
2. Click SAP Reference IMG and navigate to the path that corresponds to your
Basis version.
%DVLVYHUVLRQ
3DWK
46c (R/3 4.6)
Basis Components > Basis Services > Address Management
620 (R/3 4.7 and
CRM 4.0)
SAP Web Application Server > Basis Services >
Address Management
640 (ECC 5.0)
SAP NetWeaver > SAP Web Application Server > Basis Services > Address Management
700 (ECC 6.0
and CRM 5.0)
SAP Web Application Server > Application Server >
Basis Services > Address Management
You should now see the entry, BusinessObjects : Global Data Quality
Connector, within the IMG structure.
3. Exit your SAP system.
6WHS$FWLYDWHWKH
%XVLQHVV
&RQILJXUDWLRQ6HWVRQ
HDFKWDUJHWFOLHQW
After you insert the BusinessObjects IMG structure into the SAP Reference IMG
structure, activate the Business Configuration Sets on each of the target clients
(non-000 logon clients) that you want to configure for use with Data Quality
Management for SAP Solutions.
Repeat these steps for each target client that you want to configure for use with
Data Quality Management for SAP Solutions.
1. From one of the target clients, use /nSCPR20 to navigate to the Business
Configuration Sets : Activation transaction.
2. Type /FLDQ/AAK25 (for R/3 v. 4.6) or /FLDQ/47U6X (for all other Basis
versions) in the BC Set input field and click Enter.
The following Short text appears: Business Configuration Set for
BusinessObjects AAK 06-21-07. (The date may vary.)
3. Click the Activate button or select Activate from the BC Set menu.
4. Create a new change request. (Click OK if a caution appears.)
5. In the Activation Options window click Continue Activation (Enter). An
Activation completed message appears at the bottom of the window.
6$3KDQGVKDNHZLWK5)&6HUYHU
Now that you have installed the components of Data Quality Management for
SAP Solutions, you must make some post-installation configurations on each
target (non-000) client before you use Data Quality Management for SAP
Solutions.
To find this activity in the IMG structure, follow this process:
1. Use the transaction SPRO to access the Implementation Guide for R/3®
Customizing (IMG) structure.
2. Navigate down the structure to the following location:
Implementation Guide for R/3® Customizing (IMG)
> Basis Components
> Basis Services
> Address Management
> BusinessObjects : Global Data Quality Connector
> SAP handshake with the RFC server
3XUSRVHRIWKHDFWLYLW\
This activity allows you to define the RFC destination and test whether the
components of Data Quality Management for SAP Solutions are able to
communicate by invoking a TCP/IP handshake.
The first time this activity is invoked, you must define the RFC destination.
'HILQHWKH5)&
GHVWLQDWLRQ
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 destination for the server.
To define the RFC destination, follow these steps:
1. From the IMG on a target (non-000) client, click on the activity named “SAP
handshake with the RFC server.” The Display and Maintain RFC
Destinations window appears.
On SAP versions that use Basis 7.00, this window is named Configuration of
RFC Connections.
2. Click Create. The RFC Destination window appears.
3. Fill in the fields of the RFC Destination window as follows:
RFC Destination: FL_GDQC_SERVER
Connection type: T
Description: Connection to BusinessObjects GDQC RFC Server
By default, Data Quality Management for SAP Solutions expects the name
of the RFC destination to be FL_GDQC_SERVER. If you choose not to use
the name FL_GDQC_SERVER, you must go to the activity “Maintain
operating parameters” on page 59 and ensure that the value of the
RFC_DEST parameter is the name of the chosen RFC destination.
4. Press Ctrl+S to save the settings.
5. Click Registration (in R/3) or choose Registered Server Program (CRM) to
make the Activation Type Registration. This setting is desired because the
RFC Server is registered on the SAP gateway as an RFC server.
6. Type the Program ID as FLRFCSRV.
By default, Data Quality Management for SAP Solutions expects the
Program ID to be FLRFCSRV. If you choose not to use the Program ID
FLRFCSRV, you must edit the <sap_progid> setting in the configuration
file flrfcsrv.xml. For details on editing this configuration file, see
“Configuring through flrfcsrv.xml” on page 64.
7. Click the Test Connection button.
If the RFC Server is running and the connection is successful, a confirmation
appears.
If you are installing Data Quality Management for SAP Solutions on
Unicode system, you must perform steps 9-11.
9. If you are installing Data Quality Management for SAP Solutions on a
Unicode system: select the Special Options tab.
On SAP versions that use Basis 7.00, this tab is labeled “MDMP &
Unicode.”
10. If you are installing Data Quality Management for SAP Solutions on a
Unicode system, select Unicode in the Character Width in Target System
field.
/RDGVXSSRUWHGFRXQWU\FRGHV
Now that you have connected your SAP system to the RFC Server, you must load
into each target (non-000) client the supported countries on which Data Quality
Management for SAP Solutions can perform postal validation.
5XQQLQJWKH
WUDQVDFWLRQDQGUHSRUW
Because of a known issue on AIX, the first time the user executes the
FLDQ/AD_REPT_LOAD_COUNTRIES program, the RFC Server will fail
(timeout). After this occurs, restart the RFC Server and run the program
again.
To load supported country codes:
1. On a target (non-000) client, run transaction SA38. The ABAP: Execute
Program window appears.
2. In the Program field, specify /FLDQ/AD_REPT_LOAD_COUNTRIES.
3. Click Execute.
The supported countries are loaded into a table that you can maintain from
the IMG activity Maintain Supported Countries.
4. Repeat these steps on each target client that you want to configure for use
with Data Quality Management for SAP Solutions.
After loading the country codes with this step, you can optionally configure
Data Quality Management for SAP Solutions by removing country codes for
which you have not purchased support by using the Maintain Supported
Countries IMG activity.
For details, see the section “Maintain Supported Countries” on page 50.
$FWLYDWHGXSOLFDWHFKHFNLQGH[SRROV
The next step in setting up Data Quality Management for SAP Solutions is to run
the standard SAP IMG activity, Activate duplicate check index pools, on each
target (non-000) client.
Though this activity is part of the standard SAP functionality and not added
specifically by Data Quality Management for SAP Solutions, it is required
for the proper functioning of Data Quality Management for SAP Solutions.
You must perform this procedure on each target (non-000) client. Data
Quality Management for SAP Solutions relies on these duplicate check
index pools to perform its duplicate check processes.
To find the Activate duplicate check index pools activity within the IMG
structure, follow this process:
1. On a target (non-000) client, use the transaction SPRO to access the IMG
structure.
2. Navigate down the structure to the following location:
Implementation Guide for R/3® Customizing (IMG)
> Basis Components
> Basis Services
> Address Management
> Activate duplicate check index pools
This IMG structure assumes you are running R/3. However, the IMG
structure for a CRM or ECC system is similar. Whether you are running R/3
or CRM, the node is labeled as Activate duplicate check index pools.
3XUSRVHRIWKLV
DFWLYLW\
This activity creates the standard SAP index pools, KNA1 and BUT000, which
are useful when Data Quality Management for SAP Solutions searches for
duplicate data. Initially, the index pools are not active.
$FWLYDWHWKHLQGH[
SRROV
To activate the two standard SAP index pools, follow these steps:
1. In the IMG, click on the activity, Activate duplicate check index pools. The
Customizing Settings For Logical Search Pools: Overview window appears.
2. Type 90 in the Threshold field for index pool BUT000, and select Index
Active. A checked box activates the index pool.
3. R/3 only: Type 90 in the Threshold field for index pool KNA1, and select the
Index Active box. A checked box activates the index pool.
5. Repeat the entire process for each target (non-000) client.
Warning: When you activate index pools in SAP CRM systems, you
should not activate the index pool KNA1 ADRNR. If you have previously
activated index pool KNA1 ADRNR in a SAP CRM system, you should
deactivate it. This functionality is not supported in SAP CRM systems.
4XDUWHUO\$GMXVWPHQW5HSRUWV
The next step in setting up Data Quality Management for SAP Solutions is to run
Quarterly Adjustments. You must run Quarterly Adjustments on each target (non000) as part of the installation and configuration process to perform postal
validation on the existing data in your SAP system.
SAP provides standard reports for Quarterly Adjustments, which allow you to
validate all the addresses in your database in a three-step batch process. You may
want to run Quarterly Adjustments other times after this installation on a regular,
pre-determined schedule and you should run Quarterly Adjustments after
installing new Data Services address directories from Business Objects to
validate data that may have changed due to the renaming of streets, the
development of new areas, and so on.
If you did not have Data Quality Management for SAP Solutions installed, to run
a Quarterly Adjustment Report, you would execute the defined SAP reports
RSADRQU1, RSADRQU2, and RSADRQU3. Installing Data Quality
Management for SAP Solutions allows you to substitute the second of these
standard reports, RSADRQU2, with the custom report /FLDQ/RSADRQU2, and
take advantage of the postal validation capabilities provided by Data Quality
The running of these reports exchanges records between SAP and the RFC
Server. Then the validated and updated addresses are committed to the SAP
database.
5HSRUW56$'548
You use report RSADRQU1 to select the addresses that are to be cleansed. To run
the report:
1. On a target (non-000) client, start the report RSADRQU1 by running the
transaction code SA38.
The “ABAP Execute Program” window appears.
2. In the Program field, enter RSADRQU1 and click the Execute button (F8).
The “Create an address index for the quarterly adjustment” window appears,
presenting several options.
3. Specify the countries for which the quarterly adjustment is to be performed.
This field is required by default.
4. Specify the cities within the selected country or countries for which the
quarterly adjustment is to be performed. This field is optional.
5. Specify the postal code or range of postal codes for which the Quarterly
Adjustment is to be performed. This field is optional.
6. Change the packet size only if you have experienced problems in running
Quarterly Adjustment Reports previously.
Business Objects recommends that you maintain the default setting for
packet size of 1000 records. This number determines how many records
are processed and stored at one time. All addresses that meet the
selection conditions are read, regardless of the packet size. The setting
should be adjusted only in response to performance issues previously
encountered.
7. Select the radio button to exclude, check additionally, or check separately
addresses that have not previously been subjected to postal validation. This
setting is not relevant to Data Quality Management for SAP Solutions’s
functionality, so the setting will not affect the results of postal validation.
8. Select the appropriate radio button either to cancel the Quarterly Adjustment
if INDX exists or to overwrite the existing INDX.
Running RSADRQU1 creates a temporary table called INDX, which is used
by the other two Quarterly Reports and deleted when the process completes
successfully. If the Quarterly Adjustment Reports process did not complete
successfully, the INDX table from the failed attempt may still be available.
This option allows you to cancel the Quarterly Adjustment process rather
than overwrite the existing data, or to proceed creating INDX with the
current parameters.
You must select “Overwrite existing INDX” if the Quarterly Adjustment is
terminated for some reason and you want to start it again.
9. Click the Execute button (F8) to run RSADRQU1.
A confirmation window appears.
5HSRUW
)/'456$'548
Instead of the defined SAP report RSADRQU2, you next execute the report
/FLDQ/RSADRQU2. You use this report to read the addresses stored temporarily
in INDX and update INDX.
1. Start the report /FLDQ/RSADRQU2 by running the transaction code SA38.
2. In the Program field, enter /FLDQ/RSADRQU2 and click the Execute button
(F8).
The “Check and update address data in quarterly adjustment” window
appears.
3. Check the “Clear Previous Error Codes” box to clear error codes from
previous runs or uncheck the box to have the new error codes appended.
Check the “Skip D records during the Quarterly adjustment process” box
only if you want to run postal validation without checking D records.
A D record is a record that has its check status set to D. There are three
possible check status values.

C = Postal or address data is known and does not contain any errors
D = Postal or address data may have errors
“ ” = Postal Validation has not been run
If a record has a check status set to D, the address in that record has
previously been checked and the user selected to save the address
without cleansing it. Records with a check status of D may contain
faulty address data as a result. When running report
/FLDQ/RSADRQU2, you may want to skip D records because a user
has already made the decision to save the address without cleansing it.
A confirmation window appears. If any records failed during validation,
those records are shown here.
3RVWDO9DOLGDWLRQHUURU
ORJVIURP)/'4
56$'548
The system uses the “Clear Previous Error Codes” check box to determine
whether the report saves validation errors logged from previous runs of the
Quarterly Adjustments, or errors only from this run.
The check box “Clear Previous Error Codes” affects the content of the report
displayed as a result of running the custom error report
/FLDQ/AD_REPT_DISP_QTRERRORLOG. It does not affect the content of the
error log that appears automatically after you run the final Quarterly Adjustment
Report.
5HSRUW56$'548
You use report RSADRQU3 to commit updates to the SAP database with the
validations performed in /FLDQ/RSADRQU2.
If execution errors occur when you run the report /FLDQ/RSADRQU2, you
must not run the report RSADRQU3 next. All three of the Quarterly
Adjustment reports must be run successfully in sequence. Running
RSADRQU3 on data resulting from a failed run of
/FLDQ/RSADRQU2 can compromise the integrity of the data written back
to the SAP system.
To run the report:
1. Start the report RSADRQU3 by running the transaction code SA38.
2. In the Program field, enter RSADRQU3 and click the Execute button (F8).
A confirmation window appears, indicating that the addresses have been
removed from postal check and committed to the database. If the Quarterly
Adjustment process finds that any records are incorrect, the window displays
a list of those records. You should next run a Quarterly Adjustment custom
error report, which provides you a hyperlink to each of these records so that
you can directly edit each record as necessary.
If the report terminates or is terminated prematurely for any reason, it can be
started again at any time. When this report has finished, the system displays an
error log of all addresses that could not be updated on this run of Quarterly
Adjustments.
Though report RSADRQU3 is an SAP report, you must have the RFC Server
running to process records from the pending update table.
While RSADRQU3 is in process or not started, the Quarterly Adjustment
remains active. If addresses are changed using other SAP business
transactions while the quarterly adjustment is in process, these addresses can
not be updated by report RSADRQU3. You must complete the Quarterly
Adjustment process before making other changes to the postal address data if
you want the new data included in the adjustments.
4XDUWHUO\$GMXVWPHQW
FXVWRPHUURUUHSRUW
Data Quality Management for SAP Solutions provides a custom error report,
/FLDQ/AD_REPT_DISP_QTRERRORLOG, which you can use to display the
address validation errors that occurred during all Quarterly Adjustment runs since
the last time you cleared the previous error codes.
To run the Quarterly Adjustment custom error report:
1. Start the report /FLDQ/AD_REPT_DISP_QTRERRORLOG by running the
The ABAP Execute Program window appears.
2. In the Program field, enter /FLDQ/AD_REPT_DISP_QTRERRORLOG and
click the Execute button (F8).
The Display Address Errors generated during Quarterly Adjustment window
appears. At this window you can set limits to filter and sort the displayed
results.
3. Set any filters and click the Execute button (F8).
An error log is displayed showing a list of records on which postal validation
errors occurred. Each field item is a hyperlink to the record itself, which you
can use to go to the record for direct editing.
You must repeat the entire procedure for running Quarterly Adjustments for
each target (non-000) client as part of the installation of Data Quality
5XQWKHLQLWLDOVHWXSSURJUDP
The last step in setting up Data Quality Management for SAP Solutions is to run
the initial setup program on each target (non-000) client.
Before running the initial setup program, you must run Quarterly
Adjustments to perform postal validation on the data that already exists in
your SAP system.
3XUSRVHRILQLWLDO
VHWXS
The initial setup program prepares your existing data for matching with duplicate
check and error tolerant search.
5XQWKHLQLWLDOVHWXS
To run the initial setup program:
1. Enter transaction SA38 in the command box.
2. In the “Program” field, enter /FLDQ/RSADRINI and click the Execute
button (F8).
The program executes. Installation and setup are complete in this target (non000) client.
3. Repeat steps 1-2 on each target client that you want to configure for use with
Data Quality Management for SAP Solutions.
You should execute the FLDQ/RSADRINI program only when users are not
updating records in the system, such as during the initial setup.
When users are working in the SAP system and updating records, use instead
the /FLDQ/RSMTCCODE program (Match Code Creation Program). This
program performs the same function as the RSADRINI program, but on only
a subset of the data. This program simultaneously locks records as it runs so
that you can run it while users are updating records in the system.
,QVWDOODQGFRQILJXUH'DWD4XDOLW\0DQDJHPHQWLQWRWKH,&
:HE&OLHQW
This section describes the requirements and procedures to install the functionality
of Data Quality Management for SAP Solutions into your IC WebClient
environment.
5HTXLUHPHQWVIRU
UXQQLQJLQDQ,&
:HE&OLHQWSURILOH
To run the functionality of Data Quality Management for SAP Solutions within
your IC WebClient profiles, you must meet the following minimum requirements
in your SAP system.
)XQFWLRQDOLW\
6$3YHUVLRQ
Postal Validation
SAP CRM 4.0 and above
Duplicate Check/Error-Tolerant Search SAP CRM 5.0 and above
3RVWDOYDOLGDWLRQZLWK
WKH,&:HE&OLHQW
SAP has provided a mechanism for customers to replace SAP’s IC WebClient
views and controllers with third party views and controllers. Data Quality
Management for SAP Solutions contains enhanced versions of the Business
Partner Create (BuPaCreate) view and controller. If you are currently using the
SAP-provided version of these objects, you can use the instructions in this section
to configure your system to use the version shipped with Data Quality
Management for SAP Solutions. If you are currently using an already modified
version of these objects, you can use the instructions in this section to add the
postal validation functionality to your modified objects. These instructions can
also be used to add postal validation functionality to additional views within your
environment.
6XPPDU\RI
FRQILJXUDWLRQWDVNV
All users of the IC WebClient have a unique profile. To run the functionality of
Data Quality Management for SAP Solutions into your IC WebClient profiles, a
Basis Administrator must configure the profile by replacing the BuPa controller
of each profile with the BuPa controller provided by this product. The
configuration is manually performed because overwriting the existing BuPa
controller with the BuPa controller provided with this product would also
overwrite any customizations that have been performed prior to the installation of
this product.
The configuration tasks described in this section are specific to configuring
the IC Web Client to use Data Quality Management for SAP Solutions. If
you want to add this product’s postal validation, duplicate check, and errortolerant search capabilities to other processes, you can use these instructions
as a template of how to perform such customizations.
Make sure that you have imported the .SAR file provided as part of the
installation of this product into your SAP system. For information on importing
.SAR files, see “Install the BAdIs” on page 26.
$FWLYDWHWKH%63%&
6HWV
To activate the BSP Business Configuration Sets, open the target client (the one
that you want to configure for use with the Data Quality Management for SAP
Solutions) and follow these steps:
If you are upgrading a current IC WebClient installation, delete the contents
of the /FDLQ/AD_FORMMAP table prior to activating the BC set.
1. Enter transaction /nSCPR20 in the target client to navigate to the Business
Configuration Sets : Activate transaction.
2. Type /FLDQ/BSP_PV in the BC set input field and click Enter.
The following Short text appears: BC Set for BusinessObjects BSP_PV
Product 02/08/08. (The date may vary.)
3. Click Activate.
4. Create a new change request when the window appears. (Dismiss any caution
that may appear.)
5. Click Continue Activation (Enter) in the Activation Options window.
An Activation completed message appears at the bottom of the window.
6. Repeat these steps for each target client that you want to configure for use
with Data Quality Management for SAP Solutions.
&RQILJXUH,&
:HE&OLHQWVWRXVH
'DWD4XDOLW\
0DQDJHPHQWYLHZV
DQGFRQWUROOHUV
The steps to configure IC WebClients to use the functionality of this product vary
depending on if you use Basis 620 or Basis 700.
For the steps that state “For either Basis version,” keep track of the applicable
version(s).
1. For either Basis version, use transaction SPRO and navigate to Customer
Relationship Management > Interaction Center WebClient > CustomerSpecific System Modifications.
2. For either Basis version, run Define IC WebClient Runtime Framework
Profiles.
3. For either Basis version, select the correct profile.
4. For Basis 620 click Execute, and then add the following XML markup within
the <ControllerReplacements>
</ControllerReplacements> tags.
<ControllerReplacement>
<ReplacedController>BuPaCreate</ReplacedController>
<ReplacingController>
/fldq/BSP_DQ/BOBJ_BuPaCreate
</ReplacingController>
</ControllerReplacement>
The result in your SAP system is as follows.
<ControllerReplacements>
<ControllerReplacement>
<ReplacedController>BuPaCreate</ReplacedController>
<ReplacingController>
/FLDQ/BSP_DQ/BOBJ_BuPaCreate
</ReplacingController>
</ControllerReplacement>
</ControllerReplacements>
5. For Basis 700, double-click Controller Substitutes on the left side of the
Dialog Structure panel, and add the following values to the Controller
Substitutes grid on the right side:
%63$SSOLFDWLRQ
5HSODFHG
&RQWUROOHU
%63$SSOLFDWLRQ
5HSODFHPHQW
&RQWUROOHU
CRM_IC
BuPaCreate
/FLDQ/BSP_DQ
BOBJ_BuPaCreate
6. For either Basis version, save and exit.
$FWLYDWHWKH
)/'4%63B'4
VHUYLFH
Next, you must activate the /FLDQ/BSP_DQ service.
To activate the /FLDQ/BSP_DQ service:
1. Enter transaction SICF. The Maintain Services window appears.
2. For Basis 700 only, assure that the value for Hierarchy Type is SERVICE.
Click Execute.
3. Navigate through the services hierarchy to default host > sap > bc > bsp >
FLDQ.
4. Right-click on FLDQ, and select Activate Service from the context-sensitive
menu.
5. Click the recursive Yes button to activate the service.
6. Exit the window.
If you click the regular Yes button instead of the recursive Yes, the service
will not be activated.
$GGSRVWDOYDOLGDWLRQ
IXQFWLRQDOLW\WRRWKHU
,&:HE&OLHQWYLHZV
The enhancement to the BuPaCreate view was designed with portability in mind.
You can add postal validation functionality to other views within the IC
WebClient by copying the enhanced code from the BuPaCreate view to the
destination view and configuring the form values postal validation should use.
$GGWKHSRVWDOYDOLGDWLRQ
FRGHWRWKHGHVWLQDWLRQ
YLHZ
To add postal validation code to the destination view:
1. Use transaction SE80 to open the destination BSP application and view in the
SAP Web Application Builder.
2. Create a new session.
3. In the SAP Web Application Builder, open the BSP application
/FLDQ/BSP_DQ.
4. Open the BOBJ_BuPaCreate.htm view in the layout tab.
5. Find the beginning of the enhanced code by searching for “Beginning of
changes for adding Business Objects BSP_PV Functionality”. This text
marks the beginning of the enhanced code.
6. Find the end of the enhanced code by searching for “End of changes for
adding Business Objects BSP_PV Functionality”.
7. Copy the enhanced code and insert it into the destination view.
8. Add the following attribute to the Save CRMIC:Button tag at the bottom of
the destination view.
RQ&OLHQW&OLFN LIRQ6DYH&OLFN^KWPOEHYHQWFDQFHO6XEPLW
WUXH`HOVH^KWPOEHYHQWFDQFHO6XEPLW IDOVH`
9. Replace all occurrences of BOBJ_BuPaCreate.htm within the inserted code
with the name of the destination view.
10. Activate the view and fix any syntax errors.
11. Before continuing to the form configuration section, view the destination
form within the IC WebClient to ensure it still displays correctly.
&RQILJXUHIRUPYDOXHVIRU
SRVWDOYDOLGDWLRQ
To configure form values for postal validation:
1. Add a record to the /FLDQ/AD_FORMMAP table for each form field you
want to map to the ADRC_STRUC record. The values of the fields are the
following:
)LHOG
9DOXHGHVFULSWLRQ
VIEW NAME
The name of the view to which you are adding postal validation functionality.
FORM ID
The ID value of the <crmic:inputField> tag of the form element you are mapping.
ADRC STRUC FIELD
The name of the field you want to populate.
2. Save the changes to the /FLDQ/AD_FORMMAP table.
3. Repeat these steps for every IC WebClient profile.
$FWLYDWHVHDUFK
IXQFWLRQDOLW\ZLWKLQ,&
:HE&OLHQWRQ&50
V\VWHP
To activate search functionality within the IC WebClient on a CRM 5.0 system:
1. Navigate down the IMG structure to the following location:
Customer Relationship Management
> CRM Cross-Application Components
> Generic Interaction Layer/Object Layer
> Component-Specific Settings
> Extend Object Model for Business Partner
2. In the New Entries: Overview of Added Entries screen, select the
Implementation Class Definition folder.
3. For the Implementation Class Definition, add the following values:
)LHOG
9DOXH
External Object Name
BuilHeader
Implementation Class
/FLDQ/CL_BOBJ_BUIL_HEADER
'LVDEOHWKH3RVWDO
9DOLGDWLRQ%$G,IRU
WKH,&:HE&OLHQW
To use Postal Validation within your IC WebClient environment, you must
disable the standard Business Objects Postal Validation BAdI through the IMG
activity “Maintain exception table of transaction codes.”
You must add the Program SAPMHTTP and suppress validation, search, and
suggestions for it, as shown in this figure.
For information about adding this program to the exception table, see “Add a
transaction code to the exception table” on page 51.
7RFUHDWHQHZDGGUHVV
UHFRUGV
When creating new address records through the IC WebClient using this product,
you must create the records using these steps:
1. Click the Create button.
2. Enter the address Data.
3. Click the Save button to save the record.
If you create address records with any other procedure, postal validation may not
launch as expected.
&KDSWHU
&RQILJXULQJWKURXJKWKH,0*
Now that you have installed both components of BusinessObjects Data Quality
Management for SAP CRM/ERP Solutions, you can configure it to handle postal
validation and duplicate searching with settings appropriate for your business.
You can customize many aspects of Data Quality Management for SAP Solutions
through the activities this product adds to the SAP Implementation Management
Guide (IMG).
This chapter explains those activities and the options you have for configuration.
&KDSWHU&RQILJXULQJWKURXJKWKH,0*
/RFDWLQJWKH'DWD4XDOLW\0DQDJHPHQWIRU6$36ROXWLRQV,0*
DFWLYLWLHV
You can find the Data Quality Management for SAP Solutions IMG activities
within the IMG structure by following this process:
1. Use the transaction SPRO to access the Implementation Guide (IMG)
structure.
2. Navigate to the BusinessObjects : Global Data Quality Connector node. The
navigation to this node path depends on the Basis version that you use.
%DVLVYHUVLRQ
3DWK
46c (R/3 4.6)
Basis Components > Basis Services > Address Management
620 (R/3 4.7 and
CRM 4.0)
SAP Web Application Server > Basis Services >
Address Management
640 (ECC 5.0)
SAP NetWeaver > SAP Web Application Server > Basis Services >
Address Management
700 (ECC 6.0
and CRM 5.0)
SAP Web Application Server > Application Server >
Basis Services > Address Management
The Data Quality Management for SAP Solutions activities are the nodes at the
bottom level of this structure. The remainder of this chapter is a description of
these activities.
6$3KDQGVKDNHZLWK5)&VHUYHU
This activity allows you to define the RFC destination and test whether the
components of Data Quality Management for SAP Solutions are able to
communicate by invoking a TCP/IP handshake.
The activity is invoked for the first time during the installation and configuration
of Data Quality Management for SAP Solutions. You can perform the activity
again at any time.
For details of performing this activity, see page 32.
0DLQWDLQ6XSSRUWHG&RXQWULHV
This activity maintains the ISO country codes for the countries for which Data
Quality Management for SAP Solutions provides postal validation by making
changes to the table /FLDQ/AD_VAL_CNT. The list of countries that are
supported depends on the postal directories that you have licensed from Business
Objects.
If you did not purchase support for all countries or if you do not want postal
validation enabled for some of the supported countries for which you purchased
support, you can remove those ISO country codes from the filter using this
activity.
5HPRYHWKHFRXQWU\
FRGHV
When you click the “Maintain supported countries” activity, the table
/FLDQ/AD_VAL_CNT is displayed, showing the list of supported countries.
From this display, you can remove from the filter those ISO country codes for
which you do not want postal validation enabled.
To remove a country code:
1. Select the country code from the list of supported countries.
2. Click the Delete button.
3. Save the changes.
0DLQWDLQH[FHSWLRQWDEOHRIWUDQVDFWLRQFRGHV
This activity allows you to disable suggestion lists, preventing them from being
displayed for specific transactions.
During postal validation, Data Quality Management for SAP Solutions 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.
$GGDWUDQVDFWLRQ
FRGHWRWKHH[FHSWLRQ
WDEOH
To add a transaction code to the exception table:
1. From the IMG, click on the activity “Maintain exception table of transaction
codes.” The “Maintain exception table of transaction codes” window
appears.
2. Click the New Entries button.
The “New Entries: Overview of Added Entries” window appears.
3. Enter a Transaction code to specify the transactions for which you do not
want suggestion lists to appear.
4. Check the Suppress Validation box if you want to prevent postal validation
for that transaction (not recommended).
5. Check the Suppress Search box if you want to prevent both error tolerant
search and duplicate checking for that transaction (not recommended).
6. Check the Suppress Dialog box to prevent suggestion lists from appearing in
dialog boxes.
7. Exit the window to save the changes and return to the “Maintain exception
table of transaction codes” window.
Additionally, you can select and deselect the suppression check boxes
directly from the “Change View ‘Maintain exception table of transaction
codes’: Overview” window.
Warning: This activity also lets you disable both postal validation and
error tolerant search/duplicate check on a transaction basis. However,
Business Objects does not recommend disabling this capability because
doing so would allow invalid address data and duplicates to be stored in
your SAP system. Essentially, suppressing these capabilities turns off
certain functionality of Data Quality Management for SAP Solutions
without removing it from your SAP system. Suppressing only the
suggestions without suppressing validation or searches ensures that
invalid data is not stored.
Additionally, suppressing error tolerant search/duplicate check will
prevent records from being stored in the table /FLDQ/AD_PUPDATE,
where updated records are held before being committed to the SAP
database.
In the following illustration, the transaction code XD01 has been added to the
“Change View ‘Maintain exception table of transaction codes’: Overview”
window. Check the appropriate boxes to suppress postal validation, duplicate
searches, or duplicate suggestions.
In the following illustration, the table has a column to specify the Program name.
This column is created as a result of importing the .SAR file for the IC
WebClient.
For more information, see “Package for use with the IC WebClient” on page 27.
To suppress validation, search, or suggestions in the IC WebClient, specify the
Program name SAPMHTTP and check the appropriate boxes in that row.
0DLQWDLQWDEOHWRDFWLYDWH6$3SRVWDOFRGHFKHFNEHIRUHSRVWDO
YDOLGDWLRQ
This activity lets you to define countries for which you want the SAP postal code
check to be performed before Data Quality Management for SAP Solutions
validates the rest of the address data.
Data Quality Management for SAP Solutions can validate addresses even if they
do not contain a postal code. Therefore, by default, Data Quality Management for
SAP Solutions disables a postal code check that SAP normally performs on the
address before Data Quality Management for SAP Solutions validates the rest of
the address data. Disabling the SAP postal code check allows Data Quality
Management for SAP Solutions to perform postal validation on the data as it was
entered by the user.
By default, this table is blank because there are no countries for which Data
Quality Management for SAP Solutions needs a valid postal code before
processing. You need to change this setting only if you want the SAP postal code
check to be performed for a certain country.
$GGDFRXQWU\WRWKH
WDEOH
To add a country to the table to activate SAP postal code check before postal
validation:
1. From the IMG, select the activity “Maintain table to activate SAP postal code
check before postal validation.” The “Maintain table to activate SAP postal
code check before postal validation” window appears.
2. Click the New Entries button.
The “New Entries: Overview of Added Entries” window appears.
3. Enter in the ISO Country code field the two-letter ISO code for the country
for which you want a postal check performed before complete address
validation occurs.
4. Save the changes and exit the window. The “Maintain table to activate SAP
postal code check before postal validation” window returns.
This activity exists only in case future versions of Data Quality
Management for SAP Solutions support additional countries for which a
postal check must occur for proper address validation. This activity does
not assist this version in performing address validation.
0DLQWDLQILHOGVIRUDGGUHVVUHYLHZHU
This activity allows you to define which fields are displayed in the address
reviewer dialog and the order of those fields.
During postal validation, Data Quality Management for SAP Solutions may
modify the address data to make the address data conform more completely to the
data in official postal directories. If Data Quality Management for SAP Solutions
modifies the address data, it displays a dialog containing both the original and
modified address data. The user can choose either to keep the original data or to
accept the modified data.
Because standard street address data and P.O. Box data require different sets of
fields for postal validation, you must define the fields for both address types.
)LHOGVDQGRUGHUIRU
VWDQGDUGVWUHHW
DGGUHVVHV
By default, the following fields are displayed for standard street addresses and
given the following order:
1. BUILDING
2. HOUSE_NUM1
3. STREET
4. CITY
5. REGION
6. POST_CODE1
7. COUNTRY
)LHOGVDQGRUGHUIRU
32%R[DGGUHVVHV
By default, the following fields are displayed for P.O. Box addresses and given
the following order:
1. PO_BOX
2. POST_CODE2
3. PO_BOX_LOC
4. CITY1
5. PO_BOX_REG
6. REGION
7. PO_BOX_CTY
8. COUNTRY
0DNHFKDQJHVWRWKH
ILHOGVIRUWKHDGGUHVV
UHYLHZHU
To make changes to the fields or the order of the fields displayed in the address
reviewer:
1. From the IMG, select the activity “Maintain fields for address reviewer.” The
“Maintain fields for address reviewer” window appears.
2. Check or uncheck boxes in the Display for Street Addr and Display for PO
Box columns.
Data Quality Management for SAP Solutions displays the fields checked in
the address review dialog.
3. Type sequential numbers for all the checked fields in the Sequence Number
fields to indicate the order of the fields for street address data and P.O. Box
data.
You must number both the street address data and P.O. Box data in
sequence from 1 to the total number of displayed fields.
4. Save the changes and exit the window.
0DLQWDLQILHOGVIRUGXSOLFDWHKLWOLVWGLVSOD\
In this activity, you can define which fields are displayed in the hit list and their
order for error tolerant search or duplicate check. You must define the fields for
both hit list types.
SAP Basis 6.40 shows an additional window in this activity that other SAP
versions do not show. This window is generated by SAP and not Data
Quality Management for SAP Solutions, and therefore is not documented in
this Guide.
)LHOGVDQGRUGHUIRU
HUURUWROHUDQWVHDUFK
DQGGXSOLFDWHVHDUFK
By default, the following fields are displayed in this order for the error tolerant
search and duplicate search lists:
(UURUWROHUDQWVHDUFKOLVW
1. Score
2. Customer or Vendor or BusPartner
3. Name
4. Name2
5. Street
6. City
7. Region
8. Postal Code
9. Country
'XSOLFDWH+LW/LVW
1. Score
2. Last name
3. First name
4. House number
5. Street
6. City
7. Region
8. Postal Code
9. Customer
10. Vendor
11. BusPartner
0DNHFKDQJHVWRWKH
ILHOGVIRUWKHGXSOLFDWH
KLWOLVWGLVSOD\
To make changes to the fields or the order of the fields in the duplicate hit list
display:
1. From the IMG, click on the activity “Maintain fields for duplicate hit list
display.” The “Maintain fields for duplicate hit list display” window appears.
2. Check or uncheck boxes in the Display Flag (Search) and Display Flag (Dup.
Check) columns.
The fields checked appear in the duplicate check or error tolerant search
dialog.
3. Type sequential numbers for all the checked fields in the Sequence (Search)
and Sequence (Dup. Check) fields to indicate the order of the fields for
duplicate check or error tolerant search data.
Both the duplicate check and error tolerant search data are to be
numbered in sequence from 1 to the total number of displayed fields.
0DLQWDLQRSHUDWLQJSDUDPHWHUV
In this activity, you can modify one of the several operating parameters that affect
the behavior of Data Quality Management for SAP Solutions.
2SHUDWLQJSDUDPHWHUV
The following table shows the operating parameters, the default values, and a
description of each.
3DUDPHWHU1DPH
'HIDXOW9DOXH
'HVFULSWLRQ
ADD_REVIEW_FLAG
X
Flag to determine whether a dialog is displayed that allows the user
to review the original and modified address during postal validation.
Valid values are ’X’ to receive this confirmation dialog or a space
not to receive the dialog.
AD_REVIEW_NEW_
WIDTH
35
Width by number of characters of the validated address column
in the Postal Validation -- Review Changes window, allowing
you to adjust the size of the column if addresses are too long to
fit.
AD_REVIEW_ORIG_
WIDTH
25
Width by number of characters of the original address column in
the Postal Validation -- Review Changes window, allowing you
to adjust the size of the column if addresses are too long to fit.
BATCH_MATCH_RFC_
DEST
FL_GDQC_
BATCH_RFC
Dedicated RFC Server for handling duplicate search functionality in batch mode (also called “batch match”). This value is also
called the Program ID of the RFC Server.
ENABLE_DES_FUN_NM
none
Administrator-specified function to enable/disable Data Quality
Management for SAP Solutions duplicate error tolerant search
(DES). A possible value is the name of a function module to call
before executing Data Quality Management for SAP Solutions’s
DES. The interface for the function module specified here must
have one EXPORT parameter named VALID of type FLAG
“pass by value.” After the function call, if VALID is “X,” postal
validation processing occurs using Data Quality Management
for SAP Solutions. If VALID is space, then only SAP's standard
DES checks occur.
ENABLE_PV_FUNC_NM
none
Administrator-specified function to enable/disable Data Quality
Management for SAP Solutions postal validation. A possible
value is the name of a function module to call before executing
Data Quality Management for SAP Solutions’s postal validation.
The interface for the function module specified here must have
one EXPORT parameter named VALID of type FLAG “pass by
value.” After the function call, if VALID is “X,” postal validation processing occurs using Data Quality Management for SAP
Solutions. If VALID is space, then only SAP's standard address
checks occur.
MAX_ACT_DUPS
100
Maximum number of actual duplicates displayed to the user.
MAX_ELP_TM_DUPS
5 seconds
Maximum time allowed in seconds to find duplicates. The value
must be 1 second or greater.
MAX_REC_QU2
10000
Maximum number of records per package passed to the RFC Server
during the quarterly adjustment report.
3DUDPHWHU1DPH
'HIDXOW9DOXH
'HVFULSWLRQ
MAX_UPD_PEND
100
Maximum number of records that may be pending for update to the
RFC Server when the RFC Server is unavailable. If the number of
records pending exceeds this maximum, then the records are not
updated automatically and require the pending record update report
to be run. For information on the pending update report, see the section “Records created without break keys due to downtime of RFC
Server” on page 86.
NON_DIALOG_ERR_MSG space
Toggles whether system messages are to be displayed in nondialog 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 used for passing candidate duplicates to the RFC
Server.
RFC_DEST
FL_GDQC_SERVER
Name of the RFC Server contacted through a Remote Function Call.
This name must correspond to a valid destination that describes a
functioning RFC Server.
TECH_ERR_FUNC_NM
none
Name of a user defined function module that is called whenever a
technical error occurs.
2SHUDWLQJSDUDPHWHUV
XVHGRQO\E\WKH,&
:HE&OLHQWFRQILJXUDWLRQ
The following table shows the operating parameters, the default values, and a
description of each for operating parameters used only by the IC WebClient.
3DUDPHWHU1DPH
'HIDXOW9DOXH
'HVFULSWLRQ
BSP_RANGE_HEIGHT
225
Height of child window for range queries in BSP Postal Validation.
BSP_RANGE_WIDTH
400
Width of child window for range queries in BSP Postal Validation.
BSP_REVIEW_HEIGHT
320
Height of address review BSP page.
BSP_REVIEW_WIDTH
700
Width of address review BSP page.
BSP_SUGG_LIST_HEIGHT
475
Height of child window for suggestion lists in BSP Postal Validation and Duplicate Check/Error tolerant Search.
BSP_SUGG_LIST_WIDTH
700
Width of child window for suggestion lists in BSP Postal Validation
and Duplicate Check/Error tolerant Search.
0RGLI\WKH
SDUDPHWHUV
To make changes to operating parameters:
1. From the IMG, click on the activity “Maintain operating parameters.” The
“Maintain operating parameters” window appears.
2. Change the Parameter Value field for any of the parameters.
0DSDGGUHVVW\SHVIRU4XDUWHUO\$GMXVWPHQW
Data Quality Management for SAP Solutions provides the custom error report
/FLDQ/AD_REPT_DISP_QTRERRORLOG to log invalid addresses found by
Data Quality Management for SAP Solutions during the execution of Quarterly
Adjustment Reports.
This activity allows you to make each item in the list of invalid addresses a
hyperlink that takes the user directly to the appropriate transaction to edit the
incorrect address. Allowing the user to access the transaction and address in this
manner saves the user the effort of manually entering the transaction and locating
each invalid address for editing.
'HILQLQJPDSSLQJV
The report /FLDQ/AD_REPT_DISP_QTRERRORLOG lists the Address Type,
Address Key, and Address Type Code for each address.
The Address Key can serve as a hyperlink that calls the appropriate transaction to
edit the address only if the Address Type Code and Parameter ID for this Address
Type are defined in table /FLDQ/AD_QTR_OBJ. If the mapping for a particular
Address Type does not exist in this table, clicking on the Address Key field has
no effect.
For each Address Type in the error report
/FLDQ/AD_REPT_DISP_QTRERRORLOG, an edit transaction and the
Parameter ID must be defined in order for the key field to serve as a hyperlink.
Some of these mappings are predefined in Data Quality Management for SAP
Solutions 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.
3UHGHILQHGPDSSLQJV
Data Quality Management for SAP Solutions ships with transaction mappings for
the following Address Types:
KNA1 - Customer
LFA1 - Vendor
BUS0010 - Functional Location
BUS1006 - Business Partner
BUS1006001 - Business Partner Employee
USRCOMPANY - Company
You must perform the activity described in the following section to add a
mapping for any other Address Types.
$GGDPDSSLQJIRUDQ
$GGUHVV7\SH&RGH
To add a mapping for an Address Type Code:
1. Run the /FLDQ/AD_REPT_DISP_QTRERRLOG report.
2. Write down the Address details for an entry for which the hyperlink does not
work, noting these three items:

Address Type

Address Key

Address Type Code
3. Use the Address Type and Address Key to determine which SAP transaction
should be used to edit the address record.
4. Navigate to the Edit transaction.
5. Place your cursor in the Key field (for example, Customer in transaction
XD02).
6. Press the F1 key.
7. Click the Technical Information button on the Performance Assistant dialog
menu bar.
8.
Note the Parameter ID value in the Field Data section.
9. Use the IMG Activity Map of Objects to transaction for Quarterly Error
Report.
10. Click the New Entries button and fill in all three columns using the data you
have collected:

Enter the Address Type Code in the Object Type field.

Enter the transaction Code in the Transaction for Edit field.

Enter the Parameter ID in the Object Parameter ID field.
11. Save.
12. Repeat as necessary for each address that does not have a working hyperlink.
13. Create a Customizing Request.
&KDSWHU
&RQILJXULQJWKH5)&6HUYHU
Through the installation process, all of the necessary files on the RFC Server are
configured to properly run BusinessObjects Data Quality Management for SAP
CRM/ERP Solutions. You may, however, change items after installation.
&KDSWHU&RQILJXULQJWKH5)&6HUYHU
&RQILJXULQJWKURXJKIOUIFVUY[PO
The main configuration file of the RFC Server is flrfcsrv.xml. Through the
parameters of this file, you control several aspects of Data Quality Management
for SAP Solutions, such as how Data Quality Management for SAP Solutions
handles logging and various performance-related settings. This section discusses
certain critical settings of this configuration file.
You should not make changes to flrfcsrv.xml without a full understanding of
the implications of those changes. Errors in this configuration file could
disable Data Quality Management for SAP Solutions.
/RFDWLRQRI
IOUIFVUY[PO
The file is located on your system at install_directory\config\flrfcsrv.xml.
(GLWLQJIOUIFVUY[PO
Edit flrfcsrv.xml as you would any other XML file. If you have an XML editing
program that you are familiar with, you can use that program.
On Windows systems, we recommend that you do not use Notepad when editing
the configuration files. If you do use Notepad, the data will display all in one line,
making it difficult to read.
When you edit a value in flrfcsrv.xml, make sure that you alter configurable
values but do not change the structure or required parameters of the file. Be sure
to make a backup of flrfcsrv.xml to preserve its original state in case you later
want to discard your changes.
6$3VHWWLQJVDQG'4
6HUYHUVHWWLQJV
The settings under the commented headings  and
 are determined at the time of installation.
One reason you might alter a setting in this section would be if you chose a
Program ID other than FLRFCSRV during the activity “SAP handshake with
RFC Server,” and now must edit the <sap_progid> setting to correspond to
the correct Program ID. This step is mandatory if you have configured a
dedicated RFC Server to support matching in batch mode.
If you want to run multiple instances of the RFC Server, you can override these
settings by making new settings in the <override> tags, found beneath these
settings in the file. See “Overrides” on page 67 for details on how to override
these settings.
)LOHVHWWLQJV
The following table shows the configurable settings and defaults in the section
under the commented heading . All of these settings
must have an entry.
6HWWLQJ
'HVFULSWLRQ
'HIDXOW
log_level
Provides two levels of logging.
1 - Only serious errors are logged
2 - Serious errors and any important
warnings and information messages
are logged.
2
uc_logging_flag
false
Enables logging for the Universal
Connector, which provides connection
to BusinessObjects Data Services.
This setting is provided to allow customers to provide detailed information
to customer support representatives.
You should not change these values
unless requested in a customer support
situation.
uc_logging_file_dir
Sets the directory of the log file for the <none>
Universal Connector, which provides
connection to BusinessObjects Data
Services.
situation.
uc_playback_flag
Enables the playback of data transfer false
feature of the Universal Connector,
which provides connection to BusinessObjects Data Services.
situation.
uc_bytes_per_log_file
1000000
The size, in bytes, that a log file is
allowed to attain before an additional
log file is created for logging, which
provides connection to BusinessObjects Data Services.
situation.
enable_trace
Determines whether the RFC Server
yes
should generate trace files. A trace file
provides you with a history of transactions. Possible values are yes and no.
*HQHUDOVHWWLQJV
6HWWLQJ
'HVFULSWLRQ
'HIDXOW
tsad10_config
Location and name of tsad10.txt,
which is a file that stores valid match
fields. The path is relative to the
installation of Data Quality Management for SAP Solutions.
config/tsad10.txt
region_file
Location and name of regions.xml,
config/regions.xml
which sets regions for a specific country code. The path is relative to the
installation of Data Quality Management for SAP Solutions
fmt_file
Location and name of fmt.xml file,
which is the format file., which specifies the format of tables that the gateway passes as arguments to the RFC
Server.
config/fmt.xml
The following table shows the configurable settings and defaults in the section
under the commented heading . All of these
settings must have an entry.
6HWWLQJ
'HVFULSWLRQ
'HIDXOW
max_sugg_items
Maximum number of suggestion
items the RFC server should return.
Must be set to a minimum of 1.
99
connect_timeout
Maximum amount of time in millisec- 20000
onds the RFC server should attempt to
connect to Data Services. Must be
greater than or equal to zero. A setting
of zero indicates no timeout.
connect_delay
Amount of time to wait between
attempts to communicate with the
Data Services. Must be greater than or
equal to zero. A setting of zero indicates that the RFC server is to attempt
continuously to connect to the Data
Services and SAP Gateway without
pausing between attempts.
5000
include_empty_
candidates_check
Determines whether to include empty
candidates in address checks. Possible
values are yes and no.
yes
include_empty_
candidates_search
Determines whether to include empty
candidates in address searches. This
configuration setting is discussed in
more detail in the section“RSMTCCODE program error message” on
page 88. Possible values are yes and
no.
yes
'DWDIORZV
The settings under the commented headings  correspond to
the name of the dataflows that run each type of SAP request. If you change the
name of the dataflow here, you must change it on your Data Services installation.
For more information about dataflows, see the Data Services documentation that
shipped with this package.
2YHUULGHV
You can override the settings in the other sections, which would be useful if you
run more than one instance of the RFC Server.
You can override only the following tags:
sap_gwhost
sap_gwserv
sap_progid
sap_unicode
dq_type
dq_host
dq_port
dq_web_server_url
repository_path
sub_options
&UHDWHDQRYHUULGH
To create an override:
1. Remove the comment tags from an override so that this section can be parsed
by the RFC Server.
2. Fill in the value for the override name.
<override name="my_new_override_name">
3. Fill in the values for each tag that requires an override. If any tags are the
same as the default setting, fill in the default setting value.
4. Set the override in the file install_directory\config\start_rfcserver.bat by
indicating the name of the override.
set OVERRIDE="my_new_override_name"
5. Save and close both files. When start_rfcserver.bat runs, it looks for the
named override in flrfcsrv.xml and executes those override settings.
&KDSWHU
3RVWDODGGUHVVYDOLGDWLRQ
This chapter describes the postal address validation features of BusinessObjects
Data Quality Management for SAP CRM/ERP Solutions. Postal validation
standardizes and corrects address data, protecting the integrity of that data in your
SAP system.
Postal address validation takes place in real time as users enter data and in a batch
mode as part of the SAP Quarterly Adjustment Report. In real time, Data Quality
Management for SAP Solutions 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.
&KDSWHU3RVWDODGGUHVVYDOLGDWLRQ
,QWHUDFWLYHFOHDQVLQJZLWK'DWD4XDOLW\0DQDJHPHQWIRU6$3
6ROXWLRQV
Data Quality Management for SAP Solutions’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.
8VLQJLQWHUDFWLYH
FOHDQVLQJ
For interactive address cleansing, the SAP user needs to take no unusual action.
The data is cleansed automatically when the user saves the record or clicks the
Check Address button. In this example, a user adds information for a new
account. The data is not entered properly, and the ZIP Code was not entered.
After the user attempts to save the record, the cleansing takes place in real time.
The user is offered a window to review the changes that Data Quality
Management for SAP Solutions made to the address. The user can accept the
validated address, use the original address, or cancel the postal validation process.
At this window you have three button options:
%XWWRQ
$FWLRQ
Accept Validated
Address
The previous window returns to focus with the corrected data populating the fields.
Use Original
Address
The previous window returns to focus with the data as originally
entered populating the fields.
Cancel
The previous window returns to focus and the process is cancelled.
In this example, the following items were cleansed:
The street name was corrected and properly cased.
The city was spelled properly and properly cased.
The state was cased properly.
The ZIP+4 postal code was added.
0XOWLSOHVXJJHVWLRQV
This illustration of the suggestion list (this time, as used in the IC Web Client)
offers several addresses because the original provided address was ambiguous.
In this window, the three button options are as follows:
%XWWRQ
$FWLRQ
Select
The previous window returns to focus with the data chosen here
populating the fields.
Use Original
Address
The previous window returns to focus with the data as originally
entered populating the fields.
Cancel
&KDSWHU3RVWDODGGUHVVYDOLGDWLRQ
%DWFKFOHDQVLQJZLWK4XDUWHUO\$GMXVWPHQW5HSRUWV
Data Quality Management for SAP Solutions accomplishes batch cleansing of
postal addresses through Quarterly Adjustments. You first run Quarterly
Adjustments with Data Quality Management for SAP Solutions’s custom report
as part of the installation and configuration steps.
After installation, you may want to run Quarterly Adjustments on a regular, predetermined schedule. Also, you should run Quarterly Adjustments after installing
new address directories from Business Objects to validate data that may have
changed due to the renaming of streets, the development of new areas, and so on.
For information about running Quarterly Adjustments, see “Quarterly
Adjustment Reports” on page 37.
You may also want to further customize the display of the report by making each
address listed in the report a hyperlink to the editable address entry. For
information on this process, see “Map address types for Quarterly Adjustment”
on page 61.
&KDSWHU
'XSOLFDWHFKHFNDQGHUURUWROHUDQWVHDUFK
This chapter describes the duplicate check and error tolerant search capabilities of
These capabilities allow users to prevent the creation of duplicate customer
records in the SAP database and also to search for customer records using
information that may contain misspellings, omitted or transposed characters, and
so on.
&KDSWHU'XSOLFDWHFKHFNDQGHUURUWROHUDQWVHDUFK
8QGHUVWDQGLQJGXSOLFDWHFKHFNDQGHUURUWROHUDQWVHDUFK
To help you understand the concepts of this chapter, this section briefly defines
some of the terminology. Each of these concepts are explored in greater detail
later in this chapter.
'XSOLFDWHFKHFN
Duplicate check is the process that assures that duplicate addresses are not
entered into the SAP system when users create a new address record or update an
existing one. During the check, if there are duplicates, the user is presented with
the list of possible duplicates and allowed to select an existing customer and open
that record, or to continue the process of adding the new customer, or to cancel
the operation.
(UURUWROHUDQWVHDUFK
Error tolerant search allows users to find customer records using partial
information. Based on the partial information provided by the user, Data Quality
Management for SAP Solutions 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.
%UHDN.H\V
A break key is the search index for each record that Data Quality Management for
SAP Solutions uses for discovering similar, possibly matching, candidate records.
A break key is made up of search terms that are arranged in a specific order. The
search terms can be customized so that Data Quality Management for SAP
Solutions can determine that certain existing records have no realistic probability
of being duplicates and should be ignored.
In some previous versions of this product the term “match code” was used
instead of break key. The decision to change this term to “break key” was
made because “break key” is consistent with the terminology used for
BusinessObjects Data Services.
8QGHUVWDQGLQJEUHDNNH\VDQGGDWDILHOGV
During duplicate check and error tolerant search, Data Quality Management for
SAP Solutions uses break keys to limit the number of records used in duplicate
searches. Once given input data, Data Quality Management for SAP Solutions
determines a break key for the address and considers only stored records with the
same break key value when searching for duplicates.
This process is altered when Data Quality Management for SAP Solutions is
configured to include records with empty break key values. For more
information about the implications of configuring Data Quality Management
for SAP Solutions to include records with empty break keys and the process
to do so, see the section “RSMTCCODE program error message” on
page 88.
+RZ%XVLQHVV2EMHFWV
'DWD6HUYLFHV
GHWHUPLQHVDEUHDN
NH\
By default, Data Quality Management for SAP Solutions uses the first three
alphanumeric characters of the postal code and the first letter of the street field to
generate the break key value. Therefore, in order to improve the results during a
search, Data Quality Management for SAP Solutions requires data for the street
and postal code fields so that the appropriate records can be used in the matching
process.
For example, to search for a customer who you know lives on Main Street in La
Crosse, Wisconsin, you would enter the following information in the search
window:
Street: Main St
Postal Code: 54601
The break key value for this input data is 546M. The search process selects all of
the records from the SAP system that have the break key value 546M. The search
process then compares the input data to each record selected using the matching
rules set up on the RFC Server.
To illustrate the importance of providing data in the two fields used by Data
Quality Management for SAP Solutions to determine a break key, imagine that
you entered the following information in the search window:
Street: <blank>
Postal Code: 54601
The break key value would be 546 and only records with a break key value of 546
would be selected for searching. This result would not include the record you
were searching for because that record has a break key value of 546M.
During duplicate search, Data Quality Management for SAP Solutions
performs postal validation on the input data before performing the search. If
this example had been for duplicate search specifically, the postal code left
blank, but street, city, and region data were complete, then Data Quality
Management for SAP Solutions could validate the data and determine the
postal code. The corrected data would then be assigned the appropriate break
key of 546M, even though you did not directly enter the postal code.
&RQILJXUHWKHEUHDN
NH\VHWWLQJV
The break key settings are configurable and specified in the BusinessObjects
Data Services transform transactional_create_break_keys. If you want to change
the break key, then Business Objects recommends that you contact Customer
Care. For contact information, see “Contact information” on page 2.
0DWFKRQQDPHGDWD
You can also perform a search with data from the name field. Data Quality
Management for SAP Solutions 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.
By default, Data Quality Management for SAP Solutions includes records
with empty break keys when performing matches. In the file flrfcsrv.xml,
the parameter for including records with empty break keys to find duplicates
in postal validation is include_empty_candidates_check. The parameter
for including records with empty break keys in duplicate search is
include_empty_candidates_search. You can exclude records with empty
break keys when performing matches by changing the default setting on each
parameter from yes to no.
For more information on these settings and their values, see “General
settings” on page 66.
8VLQJGXSOLFDWHFKHFN
You can use duplicate check in interactive mode and, for Business Partner data, in
batch mode.
,QWHUDFWLYHPRGH
When you create a new entry in the SAP database for a customer, vendor, or
business partner, Data Quality Management for SAP Solutions 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.
7KHKLWOLVW
In response to your attempt to save a new record, Data Quality Management for
SAP Solutions processes the data and, if it finds a record for which the new
record may be a duplicate, presents a hit list of candidates from which you can
select an entry.
If one of the results on the hit list is a match of the record you are entering, select
the record by clicking it.
At this window you have three button options:
%XWWRQ
$FWLRQ
Continue
The previous window returns to focus showing the current address
that the user accepted from the previous address reviewer window.
Select Duplicate
The previous window returns to focus with the data from the selected
record populating the fields.
Cancel
SAP Basis 6.40 shows additional GUI elements in this window that other
SAP versions do not show. These additional elements are created by SAP
and not Data Quality Management for SAP Solutions, and therefore are not
documented in this guide.
The duplicate check hit list for the IC WebClient is shown here:
At this window you have two button options:
%XWWRQ
$FWLRQ
Continue
The previous window returns to focus and the record the user entered
is saved.
Cancel
)LHOGVGLVSOD\HG
You can customize the data fields displayed in the SAP-GUI version of the
duplicate check hit list, as well as the order of those fields. See “Maintain fields
for duplicate hit list display” on page 57 for information about the default settings
and the procedure for making changes to the fields displayed within the SAP
GUI.
%DWFKPRGH
You can use duplicate search in batch mode (often called “batch match”) to find
duplicate records in your Business Partners database.
To use duplicate search in batch mode, you must install a dedicated RFC
Server to handle these tasks. For more information, see “Install a dedicated
RFC Server for batch duplicate search” on page 24. You must also edit the
the RFC Server configuration file flrfcsrv.xml on this dedicated RFC Server
to reflect the proper Program ID (by default, FL_GDQC_BATCH_RFC) for
the dedicated server. For information on editing flrfcsrv.xml, see
“Configuring through flrfcsrv.xml” on page 64.
To use duplicate search in batch mode:
1. Invoke transaction se38 to go to the ABAP editor screen.
2. In the ABAP editor screen, enter the program /FLDQ/RSBTCMTC. The
Business Partner Batch Match screen appears.
3. Set the threshold (a lower number produces more matches) and the packet
size (defined as the number of records in a packet), and choose whether to
use the SAP functionality to create a cleansing case to combine records. (R/3
4.6 systems do not have an option to create a cleansing case.)
For more information about the SAP functionality to create a cleansing case,
see the SAP documentation.
4. Execute the program.
The results appear after the system finishes processing.
&OHDQLQJWKHVWDJLQJ
WDEOHVIRUEDWFKPRGH
To avoid erroneous results when using duplicate search in batch mode, you
should periodically clean the staging tables. If you have previously run batch job
that failed, there may be records remaining in the staging tables from that
previous job.
You can clean the staging tables in one of two ways:
Execute an SQL query on the Datastore. (For example, delete from
DQ_SAP_BATCH_MATCH_RUN_INPUT.)
Execute the sample input file
Job_Realtime_DQ_SAP_Name_And_Address_Match_Cleanup in the Data
Services Designer with the following structure in the input file of that Job:
<DataSet><Record><BATCH_ID>*</BATCH_ID></Record></DataSet>
For information about the sample input files, see “Using the sample input files to
test Jobs” on page 86.
8VLQJHUURUWROHUDQWVHDUFK
When you perform a search for a customer, vendor, or business partner using SAP
error tolerant search functionality (often called fuzzy search or rough search),
Data Quality Management for SAP Solutions takes even partial data or erroneous
data that you entered and provides a hit list of logical record matches between
your search terms and existing data.
A sample search window is shown here:
The searches can take place on address fields or name fields. You can customize
Data Quality Management for SAP Solutions to determine which fields are
presented in the hit list to help you decide which record fulfills your search.
7KHKLWOLVW
In response to your search request, Data Quality Management for SAP Solutions
processes the data, creates a list of possible matches, and presents a hit list of
candidates from which you can select an entry.
A sample error tolerant search hit list dialog is shown here.
If one of the results on the hit list is the desired record, select the record and click
the Select button.
At this window you have three button options.
)LHOGVGLVSOD\HG
%XWWRQ
$FWLRQ
Select
A window appears that gives the customer number for confirmation. If
this record is the desired record, you can accept it by clicking Enter. The
previous window returns with the entered data populating the fields.
The duplicate matches are discarded.
New Search
The search window returns, populated by the data you entered.
Cancel
The standard SAP search window is displayed.
You can customize the data fields displayed in the error tolerant search hit list, as
well as the order of those fields.
See “Maintain fields for duplicate hit list display” on page 57 for information on
the default settings and the procedure for making changes to the fields displayed.
&KDSWHU
7LSVDQGWURXEOHVKRRWLQJ
This chapter includes information on troubleshooting errors and known issues
within BusinessObjects Data Quality Management for SAP CRM/ERP Solutions.
It also includes tips for using the product.
&KDSWHU7LSVDQGWURXEOHVKRRWLQJ
,QVWDOODWLRQWURXEOHVKRRWLQJ
&KHFNLQJWKH5)&
6HUYHUVFRQQHFWLRQ
You can determine to which RFC Server(s) an SAP gateway is connected by
using the SAP transaction SMGW. For information on the use and syntax of
transaction SMGW, consult your SAP documentation.
&RQQHFWLRQWRWKH5)&
6HUYHUFORVHG
If the connection between your SAP system and the RFC Server closes or is not
made during installation, the RFC Server log file flrfcsrv_log.txt contains the
entry “connection closed.”
A more descriptive explanation may exist in another log file or trace file on the
RFC Server. Depending on the issue, the information may be in various files that
have the extension .trc. If you experience failures due to closed connections to
the RFC Server, you can search for those files with the wildcard search *.trc.
7URXEOHVKRRWLQJ
8QLFRGHLVVXHV
Data Quality Management for SAP Solutions has two settings that indicate
whether your system processes Unicode characters, one in Data Quality
Management for SAP Solutions’s RFC Server configuration file and one in the
RFC Destination. If you have problems related to Unicode characters, you should
check and configure these two settings to make sure they are correct.
&RQILJXUHWKH5)&6HUYHU
To configure the RFC Server to determine whether Data Quality Management for
SAP Solutions works with either a Unicode or non-Unicode system:
In Data Quality Management for SAP Solutions’s RFC Server configuration file
(by default, install_directory\config\flrfcsrv.xml), set the sap_unicode key to
yes if you have a Unicode system or no if you have a non-Unicode system, as
follows:
<sap_unicode>yes</sap_unicode>
or
<sap_unicode>no</sap_unicode>
&RQILJXUHLQWKH,0*
To configure the IMG to determine whether Data Quality Management for SAP
Solutions works with either a Unicode or non-Unicode system:
1. Within the SAP client, enter the transaction SM59. The Display and Maintain
RFC destinations window appears.
2. Select TCP/IP -> FL_GDQC_SERVER. The RFC Destination
FL_GDQC_SERVER window appears.
3. Select the Special Options tab.
4. In the Character Width in Target System field, select the Non-Unicode or
Unicode button, as appropriate for your system.
1RQ8QLFRGH
8QLFRGH
5. Save the settings (Ctrl+S).
3RVWDOYDOLGDWLRQDQGGXSOLFDWHFKHFNHUURUWROHUDQWVHDUFK
WURXEOHVKRRWLQJ
8VLQJWKHVDPSOH
LQSXWILOHVWRWHVW-REV
During the installation of the Data Services Component, the installation routine
installs sample input files to your BusinessObjects Data Services configuration at
installpath\BusinessObjects\DataQuality_for_SAP\extrafiles\
SampleInputfiles. You can use these input data files as a template to run data
through Data Quality Management for SAP Solutions.
For example, if you want to customize a Job, you could send add records to a
sample input file and send the data through the Job to see if you receive the
expected results. This process can help you make configurations to Jobs.
For instruction on how to run Jobs, see the Data Services documentation.
,QDELOLW\WRVDYH
DGGUHVVHVIRUZKLFK
WKHSRVWDOFRGH
FDQQRWEHFRPSOHWHG
If you were not running Data Quality Management for SAP Solutions on your
SAP system and you entered an address without using the postal code, the SAP
system would return a standard SAP error indicating that you need to enter a valid
postal code.
Because you are running Data Quality Management for SAP Solutions on your
SAP system, Data Quality Management for SAP Solutions attempts to fill in the
correct postal code based on the other address information you provided. If,
however, Data Quality Management for SAP Solutions can not determine a postal
code, Data Quality Management for SAP Solutions does not offer you an option
to save the address without correcting. This restriction is necessary because if you
attempted to save the address without the ZIP Code, the SAP system would return
its standard error indicating that you need to enter a valid postal code.
Therefore, instead of creating a scenario in which Data Quality Management for
SAP Solutions allows you to save the address without the postal code only to
have the SAP system disallow it, Data Quality Management for SAP Solutions
instead gives an error and does not allow you to save the address.
5HFRUGVFUHDWHG
ZLWKRXWEUHDNNH\V
GXHWRGRZQWLPHRI
5)&6HUYHU
During any time that the RFC Server is not functioning, Data Quality
Management for SAP Solutions can not give a break key to newly created records
or changed records.
When the RFC Server again functions and the first record is created or changed,
Data Quality Management for SAP Solutions checks a list of pending records to
determine which records have not been assigned break keys, and assigns break
keys to those records. The size of that list is configurable through the IMG
activity “Maintain operating parameters.” (For details, see “Maintain operating
parameters” on page 59.)
If the number of pending records exceeds the size configured in that parameter,
Data Quality Management for SAP Solutions cannot assign break keys to the
records. Instead, you must run the custom report /FLDQ/
AD_REPT_UPDATE_PEND_RECS.
To run the report /FLDQ/AD_REPT_UPDATE_PEND_RECS:
1. Start the report /FLDQ/AD_REPT_UPDATE_PEND_RECS by running the
2. In the Program field, enter /FLDQ/AD_REPT_UPDATE_PEND_RECS and
click the Execute button (F8).
A confirmation window appears and Data Quality Management for SAP
Solutions has assigned break keys to all records in the database.
5HFRUGVQRWVWRUHGLQ
SHQGLQJXSGDWHWDEOH
ZKHQVHDUFKGLVDEOHG
As you add or change records, the records are normally stored in the table
/FLDQ/AD_PUPDATE until they are committed to the SAP database. However,
records are not stored in that table if the Suppress Search box is checked because
with search functionality suppressed, Data Quality Management for SAP
Solutions would never process the records in the table, and the table would grow
endlessly.
For information about the Suppress Search checkbox, see “Add a transaction
code to the exception table” on page 51.
8QGHUVWDQGLQJ
UHJLRQV
Regions are data fields that could be states for U.S. addresses, provinces for
Canadian addresses, and so on. You can edit the file regions.xml to control how
Data Quality Management for SAP Solutions maps regions between the data
format expected by SAP and the data format expected by BusinessObjects Data
Services (and its Address Cleanse transform). In particular, this section describes
how the order of region maps in the file is significant. Consider this example.
Each line of regions.xml specifies conversion values for both directions:
SAP region code -> Data Services region name
CA, PQ -> CA, QC
CA, QC -> CA, PQ
CA, QC -> CA, QC
SAP region code <- Data Services region name
CA, PQ <- CA, QC
CA, QC <- CA, PQ
CA, QC <- CA, QC
When there are redundancies in the maps, as in this example, Data Quality
Management for SAP Solutions uses the last defined map.
Therefore, Data Quality Management for SAP Solutions converts the input
region:
CA, PQ -> CA, QC
CA, QC -> CA, QC (note: QC->PQ was overwritten by QC->QC)
And Data Quality Management for SAP Solutions converts the output region:
CA, QC <- CA, PQ
CA, QC <- CA, QC (note: PQ<-QC was overwritten by QC->QC)
Therefore, if the order of these regions map is different, you get a different result
that might be unexpected.
1HZIRXQGODQGUHJLRQ
FRGHIRU5DQG
If you have R/3 4.60 or 4.70 system, the SAP two character mapping code for the
Canadian province Newfoundland is NF. For all other versions of SAP supported
by Data Quality Management for SAP Solutions, the mapping code is NL. In the
file regions.xml, the mapping code NL is used for Newfoundland. To assure
correct postal validation, users of R/3 4.60 and 4.70 should change the line in
regions.xml for country CA:
<region code="NF" name="NL"/>
to
<region code="NF" name="NF"/>
5607&&2'(SURJUDP
HUURUPHVVDJH
When you run the program RSMTCCODE for a range of records but no record
exists in that range, the system displays an error message that states, “Report
execution completed successfully. No updates done to break keys table.”
,QFOXGHUHFRUGVZLWK
HPSW\EUHDNNH\V
A break key is the search index for each record that Data Quality Management for
SAP Solutions uses for finding similar, possibly matching, candidate records. A
break key consists of search terms that are arranged in a specific order. The search
terms can be customized so that Data Quality Management for SAP Solutions can
determine that certain existing records have no realistic probability of being
duplicates and should be ignored.
For more information on break keys and how they help Data Quality
Management for SAP Solutions perform searches, see “Understanding
duplicate check and error tolerant search” on page 74.
Some records may not have a break key associated with them; that is, some
records have an empty break key. Some may have break keys for name data but
not address data, or vice versa.
On one hand, including records that have empty break keys during postal
validation or duplicate search slows the processing of Data Quality Management
for SAP Solutions, because Data Quality Management for SAP Solutions has
more records to examine. On the other hand, including records that have empty
break keys helps Data Quality Management for SAP Solutions return appropriate
records.
In the file flrfcsrv.xml, the parameter for including records with empty break
keys to find duplicates in postal validation is
include_empty_candidates_check. The parameter for including records with
empty break keys in duplicate search is include_empty_candidates_search.
For more information on these settings and their values, see “General settings” on
page 66.
'XSOLFDWHKLWOLVWQRW
DSSHDULQJDV
H[SHFWHG
If the duplicate hit list screen fails to appear as expected, the problem may exist in
the field SAP_MATCH_THRESHOLD of the Data Services transform
transactional_name_and_address_match. This field must not be blank. For more
information about transactional_name_and_address_match, see
“BusinessObjects Data Services jobs” on page 91.
7KUHVKROGYDOXHVIRU
GXSOLFDWHV
The Data Services transform address_validate_suggestion contains the values to
set the threshold for candidate records to be presented in a suggestion list.
However, because of changes in SAP Basis versions 640 and above, the threshold
values from address_validate_suggestion are ignored by the SAP system.
Instead, for SAP Basis versions 640 and above, you must set threshold values in
the IMG activity “Set Limit for Duplicate List in SAP Dialog Boxes.”
For information on configuring this IMG activity, see your SAP documentation.
$GGUHVVHVGRQRW
YDOLGDWH(UURU7
If addresses do not validate and Error T528 is recorded in the RFC Server log
files, the cause may be that the BusinessObjects Data Services was stopped and
restarted without restarting the RFC Server. For more information, see “Start the
RFC Server” on page 25.
'39SURFHVVLQJ
ORFNHG
Data Quality Management for SAP Solutions provides available support for
Delivery Point Validation (DPV) processing as a for sale add-on. If you run DPV
and receive an error message that a record has locked DPV processing, you must
obtain a DPV Unlock Code from customer support to unlock DPV functionality.
See the Data Services documentation for information on DPV and DPV locking,
as well as instructions to unlock DPV processing.
5)&6HUYHU7URXEOHVKRRWLQJ
5)&6HUYHUVWDWH
WRJJOHVEHWZHHQ
67$57DQG6723
If after initialization the RFC Server state toggles between START and STOP, you
may not have a valid gateway service ID in the configuration file flrfcsrv.xml.
Check the value for the key <sap_gwserv> to ensure that the entry is correct.
For instruction on editing flrfcsrv.xml, see “Configuring through flrfcsrv.xml” on
page 64.
2XWSXWPDQLIHVW
LQIRUPDWLRQ
Upon startup, the RFC Server console outputs the manifest information, which is
the vendor’s name, name of the product, and the version of the product. Then,
after the log file is initialized, it writes this information to the log file.
The format of this string is:
<vendor>’s <product> v<version>
Here, <vendor> is the value assigned as the specification vendor in the manifest
file, <product> is the value assigned as the specification title in the manifest file,
and <version> is the value of the specification version in the manifest file.
This information can be displayed only if the manifest information is available to
the program. If this information cannot be loaded, the RFC Server displays the
following warning:
Warning: Unable to access the manifest file to display version and vendor
information.
The program continues processing normally after displaying this message to the
console.
$SSHQGL[$
%XVLQHVV2EMHFWV'DWD6HUYLFHV-REVDQG
2SWLRQV
This section describes the BusinessObjects Data Services jobs and options that
are specific to BusinessObjects Data Quality Management for SAP CRM/ERP
Solutions.
Consult the BusinessObjects Data Services documentation for general
procedures for working with BusinessObjects Data Services jobs and
options.
%XVLQHVV2EMHFWV'DWD
6HUYLFHVMREV
These jobs are located in the Data Services Designer after you install the Data
Services Component.
-RE
'HVFULSWLRQ
Job_Batch_DQ_SAP_Address_Cleanse
This job is used for quarterly adjustment reports and produces the same
results as the results from the interactive address validation process. For
more information about quarterly adjustment reports, see “Quarterly
Adjustment Reports” on page 37.
Job_Realtime_DQ_SAP_Address_Cleanse
This job is used when the IMG setting is configured so that the Suggestion List is disabled during the Address Validation. For information
about suggestion lists, see “Maintain exception table of transaction
codes” on page 51.
Job_Realtime_DQ_SAP_Address_Cleanse_
Suggestions
This job is used when the IMG setting is configured so that the Suggestion List is enabled during the Address Validation. For information
about suggestion lists, see “Maintain exception table of transaction
codes” on page 51.
Job_Realtime_DQ_SAP_Create_Break_Keys
This job contains the settings for determining break keys. For information on break keys, see “Understanding break keys and data fields” on
page 75.
Job_Batch_DQ_SAP_Name_And_Address_
Match_Run
This job processes records from input staging table (populated by
Job_Realtime_DQ_SAP_Name_And_Address_Match_Load) for a specific BATCH_ID. The job matches driver record with candidate records
to find potential duplicated names and addresses. It then loads the
results into the output staging table. It uses the substitution parameter
DQ_SAP_BATCH_ID to identify the records of a specific batch processing run and is passed from the RFC Server request by default.
Job_Realtime_DQ_SAP_Name_And_Address_
Match
This job matches a driver record with candidate records to find potential
duplicate names and addresses. It uses the Job-level Global Variable
“$SAP_MATCH_THRESHOLD” as the default threshold if an invalid
threshold is passed from the RFC Server request.
-RE
'HVFULSWLRQ
Match_Load
This job loads the staging tables with records from the RFC Server
request for duplicate check in batch mode (“batch match”) processing.
Match_Results
This job fetches the duplicate check results in batch mode (“batch
match”) from the output staging table of a specific batch ID and sends
back the results to the RFC Server.
Match_Cleanup
This job clears the records of a batch processing run from the staging
tables (both input and output tables).
Job_Realtime_DQ_SAP_Retrieve_Country_
Purchased
This job retrieves the list of countries for which you can perform postal
validation.
Job_Realtime_DQ_SAP_US_DPV_Address_
Cleanse_Suggestions
This job processes US records through the URAC (US Regulatory
Address Cleanse) transform and non-US records through the GAC (Global Address Cleanse) transform. If the collection contains multiple
records (pending update case), all records must be of US origin to
receive URAC DPV processing.
Job_Realtime_DQ_UC_Init_Batch_Match
This job generates a unique Batch ID and creates a log record entry in
the UCBatchJob table
Job_Realtime_DQ_UC_Update_Batch_Status
This job generates log record in the UCBatchJob table. Used multiple
times as a duplicate check batch mode job (“batch match”), it processes
from one state to the next.
&RPELQH+RXVH1XP
DQG30%RSWLRQ
The combine_house_num_and_pmb option of each job allows you to determine
how Data Quality Management for SAP Solutions handles house number and
PMB (postal mail box) data for that job. The following table explains the eight
options that you can set for all address cleanse jobs to the global variable
$gAddrCombineOption for each job.
2SWLRQ
([SODQDWLRQ
1 (default)
This option separates the house num1, house num2, and street data in
the house num1, house num2, and street fields, respectively. It also
appends the PMB data in the street supple2 field.
2
This option separates the house num1, house num2, and street data in
the house num1, house num2, and street fields, respectively. It also
appends the PMB data in the street field.
3
This option combines the house num1 and house num2 with street data
in the street field and append the PMB data in the street suppl2 field.
4
This option combines the house num1, house num2, and PMB data
with the street data in the street field.
5
This option combines the house num2 data with street data in the street
field and appends the PMB data in the street suppl2 field.
6
This option combines the house num2 and PMB data with the street
data in the street field.
7
This option combines the house num1 data with the street data in the
street field and appends the PMB data in the street suppl2 field.
8
This option combines the house num1 and PMB data with the street
data in the street field.
To set the option for how Data Quality Management for SAP Solutions handles
house number and PMB data:
1. For any address cleanse job, choose Properties > Global Variables.
2. Change the value of $gAddrCombineOption from 1 to any value described in
the preceding table.
3. Click Apply to activate your changes and then save the job.
4. Repeat these steps for any other jobs.
$SSHQGL[%
(UURU&RGHV
This section lists the error codes and provides a description of each code.
7HFKQLFDOHUURUFRGHV
Data Quality Management for SAP Solutions displays technical error codes in the
Error Log Report, which you can access by running the custom report /FLDQ/
AD_REPT_DISPLAY_ERRLOG.
To run the custom report /FLDQ/AD_REPT_DISPLAY_ERRLOG:
1. Start the report /FLDQ/AD_REPT_DISPLAY_ERRLOG by running the
transaction code SA38. The “ABAP Execute Program” window appears.
2. In the Program field, enter AD_REPT_DISPLAY_ERRLOG and click the
Execute button (F8). The Display Error Log Report appears.
The following table lists the technical error codes:
7HFKQLFDO(UURU
'HVFULSWLRQ
T501
An abnormal operation occurred during data processing. See
the log files for details.
T502
This is the generic duplicate check and error-tolerant search
error
T503
The IE_CH_ADDR table has a row of an invalid length
because the length did not match the length specified in the
format file.
T504
An incompatible Driver record length was found during
duplicate check and error-tolerant search.
T505
An incompatible Candidate record length was found during
T506
An incompatible Match code record length was found during
T507
The table from SAP for adding the ISO country codes is not
specified.
T508
The ISO country code table record length is invalid.
T509
There is not a record in the IE_CH_ADDR table for getting
an input address during ADR_VALIDATE or
ADR_VALIDATE_QTR call.
T510
The IE_CH_ADDR table for getting an input address is not
specified during ADR_VALIDATE or
7HFKQLFDO(UURU
'HVFULSWLRQ
T511
The EX_PROMPTS table for updating a suggestion prompt is
not specified during ADR_VALIDATE call with a suggestion
list option enabled.
T512
The EX_PROMPTS table record length is invalid.
T513
The IM_SUGGLIST table that is for adding the suggestion
list is not specified during ADR_VALIDATE call with a suggestion list option enabled.
T514
The IM_SUGGLIST code table record length is invalid.
T515
The EX_DRIVER table for getting a driver record for matching is not specified during GET_MATCH_CODE call.
T516
The EX_DRIVER table record length is invalid.
T517
There is no record in the EX_DRIVER table for getting the
driver record for matching.
T518
The IM_MATCH_CODES table for updating the match codes
is not specified during GET_MATCH_CODE call.
T520
The IM_FIELD_LIST table for adding the fields for matching
is not specified during GET_INDEXED_FIELD_LIST call.
T521
The IM_FIELD_LIST table record length is invalid.
T522
The EX_CANDIDATES table for getting the candidate
records for matching is not specified during
GET_POTENTIAL_MATCH call.
T524
The IM_MATCHES table for adding the matched records is
not specified during GET_POTENTIAL_MATCH call.
T526
The search mode parameter (EX_SEARCH_MODE) passed
is invalid (must be I, U, or S).
T527
The address type parameter (EX_CURRENT_ADDR_TYPE)
passed is invalid (must be 1 or 2).
T528
The Data Quality process timed out.
T529
Error returned from Data Quality during process.
T550
Invalid function object. Unable to process Gateway request.
T600
Error occurred during ADR_VALIDATE or
T601
Error occurred when creating input data for the Suggestion
List process during ADR_VALIDATE call.
T602
Error occurred when retrieving output data for Suggestion
List process during ADR_VALIDATE call.
T604
The batch ADR_VALIDATE_QTR dataflow failed to
initialize.
T701
An invalid address type was passed to the
GET_INDEXED_FIELD_LIST function.
T702
Invalid parameter values found while processing a
GET_INDEXED_FIELD_LIST request.
7HFKQLFDO(UURU
'HVFULSWLRQ
T703
Unable to access stored person fields for a
T704
Unable to access stored organization fields for a
T705
Unable to access the list of temporary fields in order to create
the indexed field list.
T749
An error occurred processing the
T750
Error occurred during GET_ISO_COUNTRIES call. The system could not read the file SupportedCountries.txt on the
Data Quality Server.
T751
The key file utility could not be found during
GET_ISO_COUNTRIES call.
T752
The file SupportedCountries.txt could not be found during
GET_ISO_COUNTRIES call.
T753
The file SupportedCountries.txt could not be opened for
reading during a GET_ISO_COUNTRIES call.
T802
GET_POTENTIAL_MATCHES request.
T803
Unable to locate the configuration file potential match setting
for the specified table and field.
T804
Invalid response from the Data Quality server.
T805
Unable to access candidate record information.
T806
Unable to communicate with the Data Quality server.
T807
Unable to access driver record information.
T809
The BATCH_MATCH dataflow failed to initialize.
T852
GET_POTENTIAL_BATCH_MATCHES request.
T853
Unable to locate the configuration file potential batch match
setting for the specified table and field.
T854
Invalid response from the DQXI server.
T855
Unable to access candidate record information.
T856
Unable to communicate with the DQXI server.
T898
T899
T900
An error occurred getting the display function modules for the
GUI type.
T902
Invalid parameter values found during
GET_MATCH_CODES call.
3RVWDOYDOLGDWLRQHUURU
FRGHV
7HFKQLFDO(UURU
'HVFULSWLRQ
T903
Undefined application structure.
T904
Unable to access the application structure object.
T905
Unable to access the application structure object field.
T906
GetString method conversion exception on JCO Table.
T907
GetString method name does not exist exception on JCO
Table.
T908
Driver record does not exist exception on JCO Table.
T909
Match record exists exception on JCO Table.
T910
Invalid socket table record index or record array not allocated
exception.
T911
Insufficient or excess records for the reply tables returned
from Data Quality.
T912
Undefined Data Quality response table.
T913
Dataflow error message returned from Data Quality.
T914
Dataflow status message returned from Data Quality.
T915
Unable to access the application input parameter list.
T916
Unable to access the application output parameter list.
T999
An error occurred processing the GET_MATCH_CODES
request.
Data Quality Management for SAP Solutions displays postal validation error
codes within error message windows as the errors occur.
The following table lists the postal validation error codes:
3RVWDO9DOLGDWLRQ
(UURUV
'HVFULSWLRQ
FZ01
There are more suggestions than the max suggestion set in the
configuration file.
FZ02
The House number provided is blank.
FZ03
Invalid suggestion number is specified for Street record.
FZ04
The house number provided must be an odd number.
FZ05
The house number provided must be an even number.
FZ06
The PO Box number provided is blank.
FZ07
Invalid suggestion number is specified for PO Box record.
FZ08
The PO Box number provided must be an odd number.
FZ09
The PO Box number provided must be an even number.
FZ10
Invalid primary range is entered.
FZ11
The address is not a valid delivery point.
'XSOLFDWHFKHFNHUURU
FRGH
3RVWDO9DOLGDWLRQ
(UURUV
'HVFULSWLRQ
FZ12
The country is not defined.
FZ13
The address is not a valid delivery point.
FZ14
This record locked DPV processing. Consult the Data Quality
documentation for the steps required to unlock DPV processing.
FZ15
The records primary range is a valid delivery point, but the
secondary range is not valid in the DPV directory.
FZ16
The address is a confirmed delivery point, but the parsed secondary range is not available on input.
FZ17
DPV processing is currently unavailable.
FZ18
The secondary unit range provided was invalid.
Data Quality Management for SAP Solutions displays a duplicate check error
code within error message windows as the errors occur.
There is only one duplicate check error code.
'XSOLFDWH&KHFN
(UURU
'HVFULSWLRQ
D001
The driver record to be matched is empty or data with all
spaces.
$SSHQGL[&
([WHUQDO/LVW0DQDJHPHQW
This section describes External List Management (ELM) features of
ELM is SAP CRM functionality that allows users to import data into the SAP
database from an external list. To prevent the creation of duplicate data in the
database, SAP offers functionality that allows the external list to be matched
against the SAP database so that duplicates can be identified.
Data Quality Management for SAP Solutions further enhances this SAP
functionality by providing the postal validation and matching capabilities of this
product. You can use the Data Quality portion of this product to run postal
validation and duplicate check on the data in the list itself prior to importing the
list into your SAP database. Then upon import of the list, the ELM process uses
the technology of Data Quality Management for SAP Solutions to perform postal
validation and duplicate check of the list data against the SAP database.
This product’s postal validation and duplicate check capabilities are also
available through SAP’s LSM Workbench for data migration from legacy
systems.
8VLQJ'DWD4XDOLW\0DQDJHPHQWIRU6$36ROXWLRQVZLWK(/0
To achieve optimal data quality when using ELM with BusinessObjects Data
Quality Management for SAP CRM/ERP Solutions, users should do the
following:
1. If you have a stand-alone version of Data Quality, cleanse (through postal
validation) and de-duplicate the external list using Data Quality. For
information on using Data Quality for these tasks, consult the Data Quality
documentation.
2. Using the SAP ELM functionality, load the external list into the SAP system.
The ELM process uses the technology of Data Quality Management for SAP
Solutions to match the cleansed and de-duplicated list data against the SAP
database. Duplicates in the list are marked as duplicates and are not imported.
For information on using ELM within your SAP CRM system, consult the
SAP documentation.
&OHDQVLQJWKHH[WHUQDO
OLVWSULRUWRORDGLQJ
YLD(/0
If the external list is not cleansed via Data Quality prior to being loaded via ELM,
any records that SAP considers to be invalid postal addresses are automatically
excluded from the de-duplication process and are not loaded into the database.
Therefore, some records in the external list would be ignored. Examples of
addresses that SAP considers to be invalid postal addresses are incomplete
addresses or addresses that have the city, country, or region in lower case.
Pre-cleansing the list using a stand-alone version of Data Quality corrects and
standardizes postal data, allowing the data to become valid if enough information
is included in the record. This process allows the user to get the most value from
the external list.
In addition, The SAP system does not check the list against itself for duplicates
unless the records are B2B data. Records that are B2C data are not checked for
duplicates within the list.
If the list is de-duplicated against itself using a stand-alone version of Data
Quality prior to being loaded via ELM, the SAP system then considers all records
in the list for de-duplication, instead of only the B2B records.
(/0IXQFWLRQDOLW\IRU
GLIIHUHQWYHUVLRQVRI
6$3&50
In versions prior to SAP CRM 5, records that contained a P.O. Box address but no
street address are not correctly compared against the database for de-duplication
because the P.O. Box was excluded from the field mapping in ELM, causing the
creation of an incorrect break key within this product. This issue has been fixed
by SAP in CRM 5 and higher.
5HFRUGVZLWKRQO\
QDPHGDWD
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.
,QGH[
6\PEROV
/FLDQ/AD_PUPDATE table, 52, 87
/FLDQ/AD_REPT_DISP_QTRERRORLOG, 39
/FLDQ/AD_REPT_DISPLAY_ERRLOG error log, 95
/FLDQ/AD_REPT_LOAD_COUNTRIES, 34
/FLDQ/AD_REPT_UPDATE_PEND_RECS, 86
/FLDQ/AD_VAL_CNT table, 50
/FLDQ/RSADRINI, 41
/FLDQ/RSADRQU2, 38
/FLDQ/RSMTCCODE, 41
$
AD_REPT_UPDATE_PEND_RECS program, 86
address engine
enable or disable, 22
%
BAdIs
installation, 26
installation requirements, 16
break key
configure, 76
definition, 74
Business Objects Electronic Software Download, 15
BusinessObjects Data Services
documentation, 13
installation notes, 18
introduction to, 13
jobs, 91
&
check status
D record, 38
combine_house_num_and_pmb option, 92
configuring
IMG, 47
RFC Server, 63
correction, 10
'
D record, 38
data quality, 10
Data Quality Management for SAP
overview, 9
dataflows, 67
deduplication. See also matching
dialog
suppressing, 51
documentation
accessing from Web, 7
BusinessObjects Data Services, 13
duplicate check, 73
definition, 74
using, 77
(
error codes
duplicate check, 99
postal validation, 98
technical, 95
error log, 95
error tolerant search, 73
definition, 74
suppressing, 51
using, 80
)
fields
address reviewer, 55
hit list, 57
FL_GDQC_SERVER, 32
flrfcsrv.xml, 90
editing, 64
fmt.xml, 66
+
hit list, 77, 80
,
IMG
configuration, 47
IMG activities
Activate duplicate check index pools, 35
Maintain exception table of transaction codes, 51
Maintain fields for address reviewer, 55
Maintain fields for duplicate hit list display, 57
Maintain operating parameters, 59
Maintain supported countries, 50
Maintain table to activate SAP postal code check before
SAP handshake with RFC Server, 32
SAP handshake with RFC server, 49
initial setup program
/FLDQ/RSADRINI, 41
installation, 15
BAdIs, 26
BusinessObjects Data Services, 18
RFC Server, 24
connection closed, 84
troubleshooting, 84
Java
requirements for RFC Server, 16
,QGH[
/
log file
flrfcsrv_log.txt, 84
0
Maintain exception table of transaction codes, 51
Maintain fields for duplicate hit list display, 57
Maintain operating parameters, 59
Maintain supported countries, 50
Maintain table to activate SAP postal code check before postal
validation, 54
manifest information, 90
match
engine, 12
matching, 11
name data, 76
2
operating parameters, 59
option
combine_house_num_and_pmb, 92
OSS Notes
requirements, 16
overview
correction, 10
data quality, 10
matching, 11
parsing, 10
standardization, 11
3
P.O. Box addresses, 55
parsing, 10
engine, 12
interactive cleansing, 70
quarterly adjustment reports, 37
suppressing, 51
requirements
BAdIs, 16
OSS Notes, 16
RFC Server, 16
RFC Server
checking connection, 84
configuring, 63
console, 90
flrfcsrv.xml, 64
overrides, 67
installation, 24
Java requirements, 16
Program ID, 33, 59, 64, 78
requirements, 16
SAP handshake, 32
starting, 25
stopping, 25
troubleshooting, 90
RSMTCCODE program, 41, 88
6
search
suppressing, 51
standardization, 11
suppress dialog, 51
suppress search, 51
suppress validation, 51
7
table
/FLDQ/AD_VAL_CNT, 50
TCP/IP, 12
transaction
SA38, 34, 38, 39, 41, 86, 95
SAINT, 26
SMGW, 25, 84
SPRO, 32, 35, 48
tsad10.txt, 66
8
4
quarterly adjustment, 37
/FLDQ/RSADRQU2, 38
error log, 39
Unicode, 24
troubleshooting, 84
9
validation
suppressing, 51
5
regions.xml, 66
understanding regions, 87