Informatica Data Quality for SAP Point of Entry (Version 9.5.1) Installation and Configuration Guide

Transcription

1 Informatica Data Quality for SAP Point of Entry (Version 9.5.1) Installation and Configuration Guide

2 Informatica Data Quality for SAP Point of Entry Installation and Configuration Guide Version October 2014 Copyright (c) Informatica Corporation. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS (a) and (a) (1995), DFARS (1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights reserved.copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems Incorporated. All rights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All rights reserved. Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights reserved. Copyright Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights reserved. Copyright Information Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright International Organization for Standardization All rights reserved. Copyright ejtechnologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. All rights reserved. Copyright is International Business Machines Corporation. All rights reserved. Copyright yworks GmbH. All rights reserved. Copyright Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved. Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright MicroQuill Software Publishing, Inc. All rights reserved. Copyright PassMark Software Pty Ltd. All rights reserved. Copyright LogiXML, Inc. All rights reserved. Copyright Lorenzi Davide, All rights reserved. Copyright Red Hat, Inc. All rights reserved. Copyright The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved. Copyright Jinfonet Software. All rights reserved. Copyright Apple Inc. All rights reserved. Copyright Telerik Inc. All rights reserved. Copyright BEA Systems. All rights reserved. Copyright PDFlib GmbH. All rights reserved. Copyright Orientation in Objects GmbH. All rights reserved. Copyright Tanuki Software, Ltd. All rights reserved. Copyright Ricebridge. All rights reserved. Copyright Sencha, Inc. All rights reserved. Copyright Scalable Systems, Inc. All rights reserved. This product includes software developed by the Apache Software Foundation ( and/or other software which is licensed under various versions of the Apache License (the "License"). You may obtain a copy of these Licenses at Unless required by applicable law or agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses. This product includes software which was developed by Mozilla ( software copyright The JBoss Group, LLC, all rights reserved; software copyright by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License Agreement, which may be found at The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright ( ) , all rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at and This product includes Curl software which is Copyright , Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. The product includes software copyright ( ) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at license.html. The product includes software copyright , The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at kawa/software-license.html. This product includes OSSP UUID software which is Copyright 2002 Ralf S. Engelschall, Copyright 2002 The OSSP Project Copyright 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by Boost ( or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at / This product includes software copyright University of Cambridge. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at and at This product includes software licensed under the terms at license.html, asm.ow2.org/license.html, httpunit.sourceforge.net/doc/ license.html,

3 license.html, license-agreement; /copyright-software ; forge.ow2.org/projects/javaservice/, license.html; protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; current/doc/mitk5license.html; blob/master/license; and This product includes software licensed under the Academic Free License ( the Common Development and Distribution License ( the Common Public License ( the Sun Binary Code License Agreement Supplemental License Terms, the BSD License ( the new BSD License ( licenses/bsd-3-clause), the MIT License ( the Artistic License ( and the Initial Developer s Public License Version 1.0 ( This product includes software copyright Joe WaInes, XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by the Indiana University Extreme! Lab. For further information please visit This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject to terms of the MIT license. This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422; 7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460; 8,453,159; 8,458,230; and RE44,478, International Patents and other Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: DQ-SAP

4 Table of Contents Preface.... iv Informatica Resources.... iv Informatica My Support Portal.... iv Informatica Documentation.... iv Informatica Web Site.... iv Informatica How-To Library.... v Informatica Knowledge Base.... v Informatica Support YouTube Channel.... v Informatica Marketplace.... v Informatica Velocity.... v Informatica Global Customer Support.... v Chapter 1: Introduction to Data Quality for SAP Point of Entry Data Quality for SAP Point of Entry Overview SAP and PowerCenter Communication Physical Architecture Informatica Components SAP Components SAP Application Code Informatica Data Quality Integration with PowerCenter Informatica Data Quality Components Address Validation and Duplicate Analysis Data Flows Address Validation in Real Time Duplicate Analysis in Real Time Address Search in Real Time Manual Address Validation Operations Installation Prerequisites Chapter 2: Installing and Configuring Informatica Components Informatica Component Installation and Configuration Overview Updating the Informatica Domain Address Reference Data Installation Address Reference Data Properties Index Table Creation Configuring the Index Table Character Encoding Requirements PowerCenter Workflow Configuration Importing Workflows to the PowerCenter Repository Post-Import Workflow Tasks Associating a Workflow with a PowerCenter Integration Service Table of Contents i

5 Parameter File Configuration Copying the Parameter File to PowerCenter Verifying the Index Database Type Verifying the Relational Connection Name Verifying Database Connection Details Chapter 3: Installing and Configuring SAP Components SAP Component Installation and Configuration Overview SAP Support File Configuration Copying the Support Files to the SAP System Loading the Support Files to the Application Server Enabling HTTP Communication between SAP and PowerCenter Informatica Table Setup Creating the SCREEN Table Creating the WEBSVC Table Informatica Table Data Population Address Validation Web Service Values Updating the Values in the WEBSVC Table Error-Tolerant Search and Duplicate Analysis Configuration Color Classifications Minimum Score Values Configuring the Score Settings for Duplicate Searches Troubleshooting Duplicate Check Issues Address Search Configuration Address Type 1 Structure Address Type 2 Structure Address Search Activation Adding a Country Field to the Search Screen Verifying Error-Tolerant Search Capability Configuring the Address Types Index Pools Activating Index Pools SAP Index Population Loading Data to the SAP Index Updating the SAP Index Chapter 4: PowerCenter Repository Objects PowerCenter Repository Objects Overview Web Services POE_Encrypt_Password POE_Quarterly_Adjustment POE_Search_Index POE_Update_Index ii Table of Contents

6 POE_Validate_Address Workflows Mappings Mappings That Read a Single Record Mappings That Read the SAP Index Appendix A: ABAP Functions ABAP Function Definitions Table of Contents iii

7 Preface The Data Quality for SAP Point of Entry Installation and Configuration Guide describes the steps to install and configure the Data Quality for SAP Point of Entry file package. The files include SAP application code and Informatica repository objects. You use the files to integrate PowerCenter and SAP applications. The guide is written for SAP and Informatica administrators who install and configure the Data Quality for SAP Point of Entry files in the SAP environment. The guide assumes that readers are familiar with Informatica and SAP applications and products, including Informatica application services, web services, workflows, and mappings. Informatica Resources Informatica My Support Portal As an Informatica customer, you can access the Informatica My Support Portal at The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, Informatica Product Documentation, and access to the Informatica user community. Informatica Documentation The Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from Informatica Web Site You can access the Informatica corporate web site at The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. iv

8 Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks. Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through at KB_Feedback@informatica.com. Informatica Support YouTube Channel You can access the Informatica Support YouTube channel at The Informatica Support YouTube channel includes videos about solutions that guide you through performing specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel, contact the Support YouTube team through at supportvideos@informatica.com or send a tweet Informatica Marketplace The Informatica Marketplace is a forum where developers and partners can share solutions that augment, extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions available on the Marketplace, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at Informatica Velocity You can access Informatica Velocity at Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions. If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at ips@informatica.com. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at Preface v

9 C H A P T E R 1 Introduction to Data Quality for SAP Point of Entry This chapter includes the following topics: Data Quality for SAP Point of Entry Overview, 1 SAP and PowerCenter Communication, 2 Physical Architecture, 2 Informatica Data Quality Integration with PowerCenter, 5 Address Validation and Duplicate Analysis Data Flows, 6 Installation Prerequisites, 8 Data Quality for SAP Point of Entry Overview Data Quality for SAP Point of Entry is a file package that contains application code, data files, and PowerCenter repository objects. You install the contents of the file package to integrate PowerCenter and SAP application functionality. SAP uses the files that you install to improve the quality and usability of the address data in the SAP database. You install the application code on the machine that hosts the SAP server applications. You install the data files on the machine that hosts the Informatica services. You import the repository objects to the PowerCenter repository. You configure the SAP and PowerCenter applications to use the files and objects. When you install and configure the file package, you can use SAP to perform the following operations at the point of data entry: Validate an address record When a user enters an address in a data entry application, SAP runs in the background to validate the address. The SAP application calls a PowerCenter workflow that contains an address validation mapping. The mapping compares the input address to address reference data files, and it returns a list of valid addresses to the SAP system. SAP displays the list of addresses to the end user in the data entry application. Search the system for an address When a user enters a partial address in a data entry application, SAP runs in the background to determine if the database stores a complete version of the address. The SAP application calls a PowerCenter workflow that contains a duplicate analysis mapping. The mapping searches an index of the SAP database for the input address data, and it returns any similar address to the SAP system. 1

10 SAP also performs the search operation when a user saves an address following address validation. SAP uses the results of the search operation to ensure that a duplicate address does not enter the database. You can also verify that all address records in the SAP index contain current and complete postal information. You can verify the records in the SAP index at any time. SAP and PowerCenter Communication SAP and PowerCenter applications use the Simple Object Access Protocol (SOAP) to communicate. PowerCenter uses web services to implement the SOAP calls from SAP. SAP applications use Business Add-Ins to call the PowerCenter web services. Each PowerCenter web service identifies one or more mappings. The mappings define the address validation logic and duplicate analysis logic that the PowerCenter Integration Service uses to analyze the SAP data. An address validation mapping compares the SAP address data with the contents of a reference data set. You install the address reference data to the PowerCenter Integration Service machine. Physical Architecture You install and configure the files in the Data Quality for SAP Point of Entry file package on SAP and PowerCenter machines. Informatica Components The PowerCenter installation includes application services, client applications, and address reference data files. Data Quality for SAP Point of Entry is compatible with PowerCenter 9.1 and You install and configure the following components for PowerCenter: PowerCenter client applications Client applications for PowerCenter version 9.1 or PowerCenter repository The database that stores PowerCenter workflow, session, and mapping objects. PowerCenter repository objects Metadata objects that you import to the PowerCenter repository. The objects include the workflows, sessions, and mappings that perform address validation and duplicate search operations on SAP data. Data Quality for SAP Point of Entry includes XML files that define the objects. Import one of the following XML files to the PowerCenter repository: SAPPOE_91.xml. Contains repository objects for PowerCenter 9.1. SAPPOE_951.xml. Contains repository objects for PowerCenter PowerCenter Integration Service The application service that runs PowerCenter sessions. 2 Chapter 1: Introduction to Data Quality for SAP Point of Entry

11 PowerCenter Repository Service The application service that manages the PowerCenter repository. PowerCenter Web Services Hub The PowerCenter Web Services Hub connects external applications to PowerCenter. The external applications use web services to access PowerCenter functionality. The Web Services Hub and the web services that it hosts comprise the Web Services Provider. Address reference data files Files that contain current address data for all mailboxes in a country. The address validation mappings read the reference data files. You install the address reference data files on the machine that hosts the PowerCenter Integration Service. SAP Components The SAP system includes the SAP server, Business Address Services, and SAP application code. You install and configure the following components for SAP: SAP server SAP ECC 6.0 Enhancement Package 4 with Web Application Server. The server application includes the SAP database. Business Address Services The operations that you define with Data Quality for SAP Point of Entry use the following Business Address Services: BC-BAS-PV. Postal validation interface. BC-BAS-DES. Duplicate record and error-tolerant search interface. Data quality namespace When you configure the Data Quality for SAP Point of Entry files, you add the /INFADQPE/ namespace to the SAP system. The namespace stores all objects that SAP requires to communicate with PowerCenter, including the ABAP code. SAP index database The SAP index is a copy of the SAP database. When an SAP application writes or updates a record in the SAP database, the application writes or updates the same record in the index. The PowerCenter Integration Service performs all address validation and duplicate analysis operations on the index data. SAP Application Code Data Quality for SAP Point of Entry uses Advanced Business Application Programming (ABAP) code to define operations on the SAP system. The ABAP code performs the following operations in SAP: It activates the Business Add-Ins that run the address validation, address search, and address update tasks. It creates the functions that process the address logic and run the web service calls. It creates the SAP data entry screens. It creates the system tables and implements system recovery. Physical Architecture 3

12 It handles errors and security issues. Business Add-Ins SAP applications use Business Add-Ins (BAdIs) to communicate with Informatica applications. You add the BAdIs to the SAP environment. The BAdIs connect to the Business Address Services that manage address validation and duplicate analysis. Data Quality for SAP Point of Entry adds BAdI code to the following transaction exit points in an SAP application: ADDRESS_CHECK The ADDRESS_CHECK exit point sends data to the web services that validate an input address. ADDRESS_UPDATE The ADDRESS_UPDATE exit point sends data to the web services that check the SAP index database for copies of an input address. The code can also update the address data in the index. ADDRESS_SEARCH The ADDRESS_SEARCH exit point sends data to the web services that search the SAP index for an address. Use transport requests to import the BAdIs to the SAP system. The BAdIs start when the Data Quality for SAP Point of Entry components are active in the SAP system. BAdIs communicate with web services through ABAP functions. Data Entry Screens Data Quality for SAP Point of Entry adds custom data entry screens to the end user application. The screens display the results of the address validation and duplicate search operations. System Tables The SAP database includes system tables that contain information about database objects and database connections. Data Quality for SAP Point of Entry adds the following system tables to the SAP database: Table /INFADQPE/WEBSVC The WEBSVC table sets up the web service call. The fields in the table include the URL, service name, web service name, and relevant XML tags. The table contains an entry for each web service. The function INFADQPE/SUBMIT_WEBSERVICE reads the table. Table /INFADQPE/ERRLOG The ERRLOG table contains the error log data that the web services generate. Set the error logging property to Y in the ERRLOG table for each web service that will write error log data to the table. If an outbound or inbound error occurs, the table stores the related error code. The table also contains fields to hold the ID of the user who runs the SAP transaction, the date and time of the system activity, and the web service called. Table /INFADQPE/SCREEN The SCREEN table controls the screens that display side-by-side address information during address validation. The table can display country-specific data screens. 4 Chapter 1: Introduction to Data Quality for SAP Point of Entry

13 Table /INFADQPE/UPDATE The UPDATE table stores address data for the UpdateIndex web service when the web service is unavailable. Informatica Data Quality Integration with PowerCenter If you are an Informatica Data Quality user, you can create and update mappings in Informatica Developer and export the mappings to the PowerCenter repository. The Data Quality for SAP Point of Entry file package includes address validation and duplicate analysis mappings that you can import to the Model repository and review in the Developer tool. The mappings contain the same address validation and duplicate analysis logic that the PowerCenter mappings contain. You can update a mapping in the Developer tool and export it to replace the equivalent mapping in the PowerCenter repository. Note: Informatica Data Quality is an optional component. The Data Quality for SAP Point of Entry files do not integrate Informatica Data Quality and SAP applications. Data Quality for SAP Point of Entry includes all the PowerCenter workflows, sessions, and mappings that you need to validate address records and identify duplicate records. Informatica Data Quality Components All Informatica Data Quality components are optional. You can install and configure the following objects and files for Informatica Data Quality in the domain: Model repository The database that stores the data quality mapping objects. Model repository objects Mapping objects that you can import to the Model repository. The mappings correspond to the mappings that you import to the PowerCenter repository in the SAPPOE_91.xml and SAPPOE_951.xml files. You can import one of the following files to the Model repository: DQ_91_Mappings.xml. Contains mapping objects for Informatica Data Quality 9.1. DQ_951_Mappings.xml. Contains repository objects for Informatica Data Quality Model Repository Service The application service that manages the Model repository. Data Integration Service The application service that runs mappings. Content Management Service The application service that manages reference data. Address reference data files Files that contain current address data for all mailboxes in a country. The address validation mappings read the reference data files. You install the address reference data files on the machine that hosts the Data Integration Service. Informatica Data Quality Integration with PowerCenter 5

14 Address Validation and Duplicate Analysis Data Flows When an end user enters an address record in the data entry application, SAP passes the record to PowerCenter for analysis. PowerCenter return the results to SAP, and SAP displays the results to the end user. The address validation and duplicate analysis operations run on an index copy of the SAP database. The PowerCenter Integration Service reads and updates the addresses in the index. To update the SAP database, use a database tool to synchronize the database with the index. Address Validation in Real Time When an end user enters an address to a data entry application, SAP sends the address to PowerCenter to validate the address quality. The following process describes the outward data flow from SAP to PowerCenter and the return data flow from PowerCenter to SAP and to the data entry application: 1. The end user enters an address to the data entry application. 2. The SAP application calls a Business Address Service to process the address data. 3. The process request, including the address data, passes to the ADDRESS_CHECK Business Add-In. 4. The Business Add-In passes the process request to the PowerCenter Web Services Hub in a SOAP envelope. 5. The PowerCenter Web Services Hub passes the address data to a PowerCenter workflow. The workflow includes an address validation mapping. 6. The PowerCenter Integration Service validates the address data according to criteria that the mapping defines. The mapping compares the data with the address reference data. It returns a list of valid addresses that match the input data. 7. The workflow returns the mapping results to the PowerCenter Web Services Hub. 8. The PowerCenter Web Services Hub returns the results to the Business Add-In in a web service response. 9. The data entry user reviews the results of the process. The user can select the original address or select an address that the validation process proposes. Duplicate Analysis in Real Time When an end user saves a valid address to the SAP database, SAP sends the address to PowerCenter to determine if the SAP database stores a version of the address. The following process describes the outward data flow from SAP to PowerCenter and the return data flow from PowerCenter to SAP and the data entry application: 1. The end user selects an address for addition to the SAP database. 2. The SAP application calls a Business Address Service to process the address details. 3. The process request, including the address data, passes to the ADDRESS_SEARCH Business Add-In. 4. The Business Add-In passes the process request to the PowerCenter Web Services Hub in a SOAP envelope. 5. The PowerCenter Web Services Hub passes the address data to a PowerCenter workflow. The workflow includes a duplicate analysis mapping. 6 Chapter 1: Introduction to Data Quality for SAP Point of Entry

15 6. The PowerCenter Integration Service runs the mapping on the SAP index. The mapping compares the address with every address record in the index. The mapping returns the input address and any address that demonstrates a high degree of similarity to the input address. 7. The workflow returns the mapping results to the PowerCenter Web Services Hub. 8. The PowerCenter Web Services Hub returns the records to the Business Add-In in a web service response. 9. The user reviews the results of the process. The user adds the input address to the database, or the user identifies the address as a duplicate of an address in the SAP index. Note: The real-time address search and real-time duplicate analysis processes use the same SAP Business Add-In and the same PowerCenter workflow. Address Search in Real Time An end user can submit an incomplete address and search the SAP database for similar addresses. If the user finds an address that matches the incomplete address, the user can update the input address with the address in the database. The following process describe the outward data flow from SAP to PowerCenter and the return data flow from PowerCenter to SAP and to the data entry application: 1. The end user opens the Search screen in the data entry application and enters partial address data. The address data must include a two-letter ISO country code. 2. The SAP application calls a Business Address Service to read the address data. 3. The process request, including the address data, passes to the ADDRESS_SEARCH Business Add-In. 4. The Business Add-In passes the process request to the PowerCenter Web Services Hub in a SOAP envelope. 5. The PowerCenter Web Services Hub passes the address data to a PowerCenter workflow. The workflow includes a duplicate analysis mapping. 6. The PowerCenter Integration Service runs the mapping on the SAP index. The mapping compares the incomplete address data with every address record in the index. The mapping returns any record that demonstrates a high degree of similarity to the incomplete address. 7. The workflow returns the mapping results to the PowerCenter Web Services Hub. 8. The PowerCenter Web Services Hub returns the records to the Business Add-In in a web service response. 9. The user reviews the results of the process. The user might decide to use one of the suggested addresses as the complete address. Note: The real-time address search and real-time duplicate analysis processes use the same SAP Business Add-In and the same PowerCenter workflow. Manual Address Validation Operations If you are an SAP administrator, you can use the ADDRESS_UPDATE Business Add-In to call a PowerCenter workflow that validates the address records in the database. You can use an SAP transaction to filter the address records by the date of entry. You can call the address validation workflow at any time. The workflow performs the following tasks: 1. Analyzes the address records that you specify. 2. Determines if the address data in the records is correct and complete. Address Validation and Duplicate Analysis Data Flows 7

16 3. Fixes errors in the address records. 4. Completes any record that is incomplete 5. Reports on the deliverable status of each address. Note: Before you validate the addresses, copy the address records to the SAP database index. The PowerCenter Integration Service updates the addresses in the index. Installation Prerequisites You install and configure Data Quality for SAP Point of Entry components into an environment that comprises SAP and Informatica applications. Before you install and configure the components, verify that the SAP and Informatica applications are installed and fully operational. 8 Chapter 1: Introduction to Data Quality for SAP Point of Entry

17 C H A P T E R 2 Installing and Configuring Informatica Components This chapter includes the following topics: Informatica Component Installation and Configuration Overview, 9 Updating the Informatica Domain, 10 Address Reference Data Installation, 10 Index Table Creation, 11 PowerCenter Workflow Configuration, 12 Parameter File Configuration, 13 Informatica Component Installation and Configuration Overview You install and configure the Informatica components before you install and configure the SAP components. To install and configure the Informatica components, complete the following steps: 1. Update the Informatica domain. 2. Copy the address reference data files to the PowerCenter Integration Service machine. 3. Create the SAP index database. 4. Import the PowerCenter objects to the PowerCenter repository. 5. Copy the POE.param file to the PowerCenter Integration Service machine. 9

18 Updating the Informatica Domain Update properties on the PowerCenter Integration Service and on the node where the PowerCenter Integration Service runs. Use the Administrator tool to update the properties. Stop the PowerCenter Integration Service before you update the service properties. Restart the service after you update the properties. 1. Set the maximum number of processes that the PowerCenter Integration Service node can run to Set the DataMovementMode property on the PowerCenter Integration Service to Unicode. 3. Add the following file paths to the Java SDK ClassPath on the PowerCenter Integration Service: PowerCenter Version PowerCenter 9.1 PowerCenter File Paths <PowerCenter_installation_directory>/tomcat/common/lib/dworacle.jar <PowerCenter_installation_directory>/tomcat/common/lib/dwsqlserver.jar <PowerCenter_installation_directory>/tomcat/common/lib/dwdb2.jar <PowerCenter_installation_directory>\9.5.1\services\shared\jars \thirdparty>com.informatica.datadirect-dwdb hf1.jar <PowerCenter_installation_directory>\9.5.1\services\shared\jars \thirdparty>com.informatica.datadirect-dworacle-5.0.1hf1.jar <PowerCenter_installation_directory>\9.5.1\services\shared\jars \thirdparty>com.informatica.datadirect-dwsqlserver-5.0.1hf1.jar Use the full path to each file. Use a semicolon to separate the entries. Address Reference Data Installation You download address reference data files from Informatica in a compressed file format. Extract and copy the files to the PowerCenter Integration Service machine. The following table describes the types of address reference data that the Data Quality for SAP Point of Entry mappings can read: Type of Reference Data Batch Suggestion list When To Use Use for general address validation operations. Use for real-time address validation operations. You can extract the address reference data files and copy the files manually to the PowerCenter Integration Service machine. Or, you can use the Data Quality Content Installer to extract and copy the files. Data Quality Content Installer The Data Quality Content Installer is a file utility that you download from Informatica. The Content Installer extracts the compressed address reference data files and copies the files to the PowerCenter directory structure. Run the Content Installer on the PowerCenter Integration Service machine. 10 Chapter 2: Installing and Configuring Informatica Components

19 The Content Installer creates an /av/ directory in the PowerCenter directory structure. The Content Installer writes the address reference data to the /av/ directory. Address Reference Data Properties The PowerCenter Integration Service reads address reference data properties from the AD50.cfg configuration file. After you copy the address reference data files to the PowerCenter Integration Service machine, verify the AD50.cfg file properties. The PowerCenter installer writes the AD50.cfg file to the following directory: <PowerCenter_installation_directory>/server/bin Verify or update the following properties in the AD50.cfg file: Verify the path to the address reference data files in the ReferenceDataLocation property. Verify the license key data in the LicenseKey property. You download the license key from Informatica. If you have more than one license key, enter the licenses in a comma-separated string. Verify that the file includes at least one country abbreviation as a preload value for each type of address reference data that you install. Enter ALL to apply a preload setting for all countries. You can optionally edit other properties in the AD50.cfg file. Index Table Creation The PowerCenter Integration Service performs address validation and duplicate analysis operations on an index of the SAP database. The index contains a single table that you create and configure. Configuring the Index Table You can configure an index table in a Microsoft SQL Server, Oracle, or IBM DB2 database. The Data Quality for SAP Point of Entry installation files include data definition language (DDL) files for the index table. Use the files to create a user and schema for the index table on the database server. 1. Install or verify the database client on the PowerCenter Integration Service machine. For an IBM DB2 database, verify that the database client catalog includes the database. For an Oracle database, verify that the tnsnames.ora file contains a reference to the index database. 2. Create a user account and schema on the database server that stores the index database. 3. Use the DDL file for the database type to create the index database structure. Select from the following files: DB2-ddl.txt MSSQL-ddl.txt Oracle-ddl.txt 4. Use the PowerCenter Workflow Manager to create a relational connection object for the index database. 5. Verify the database name in the POE.param parameter file for Data Quality for SAP Point of Entry. The default database name is POE_Oracle. If you use a different database type or name, update the POE.param file with the correct name. Index Table Creation 11

20 Character Encoding Requirements The index database stores characters in the UTF-8 format. The default index database type is Oracle. Oracle reads the character format from the NLS_LANG registry entry on Windows and from the locale environment variable on UNIX. On an Oracle database client, set NLS_LANG to the locale that the database client and server can use with the user account you created. For example, set NLS_LANG to american_america.utf8. You must also configure the Oracle database client on the PowerCenter Integration Service machine to use Unicode characters. PowerCenter Workflow Configuration The Data Quality for SAP Point of Entry file set includes workflows that you import to the PowerCenter repository. After you import the workflows, associate each workflow with a PowerCenter Integration Service. Importing Workflows to the PowerCenter Repository Use the PowerCenter Repository Manager to import the object XML file to the repository. Import the XML file for the version of PowerCenter that you use: To import workflows for PowerCenter 9.1, select SAPPOE_91.xml. To import workflows for PowerCenter 9.5.1, select SAPPOE_951.xml. Post-Import Workflow Tasks After you import the PowerCenter workflows, you configure the PowerCenter and SAP systems to use the workflows. Complete the following tasks: 1. Associate each workflow with a PowerCenter Integration Service. 2. Verify that the endpoints for the web service mappings are exposed. 3. Create a relational connection in Workflow Manager to the index database table. 4. Add the POE.param parameter file to the PowerCenter Integration Service machine. 5. Populate the index table. Associating a Workflow with a PowerCenter Integration Service Use the PowerCenter Workflow Manager to associate each workflow that you import with a PowerCenter Integration Service. 1. Start Workflow Manager. 2. From the Workflow Manager menu, select Service > Assign Integration Service. The Assign Integration Service dialog box opens. 3. Select the repository folder that contains the workflows that you imported. 12 Chapter 2: Installing and Configuring Informatica Components

21 4. Select a PowerCenter Integration Service. 5. Select the workflows to assign to the PowerCenter Integration Service. To select all workflows in the folder, choose Select all displayed workflows. 6. Click Assign. After you associate the workflows with the PowerCenter Integration Service, restart the PowerCenter Web Services Hub. Parameter File Configuration The Data Quality for SAP Point of Entry file set contains a parameter file named POE.param. POE.param sets the following values: The database type for the index database and quarterly adjustment database. The connection name for the index database. The database connection details, including an encrypted password. Review the file settings, and edit the settings if required. Copying the Parameter File to PowerCenter To use the POE.param file, copy the file to the PowerCenter services host machine. 1. Find POE.param in the Data Quality for SAP Point of Entry installation file set. 2. Create a directory named param in the PowerCenter directory structure. Create the directory at the following path: <PowerCenter_Installation_Directory>/server/infa_shared/param 3. Copy POE.param to the param directory. Verifying the Index Database Type The POE.param file contains $$DATABASE_TYPE parameters for Oracle, Microsoft SQL Server, and IBM DB2. Update the file to specify the index database type. The POE.param file contains the following database type parameters: $$DATABASE_TYPE=Oracle #$$DATABASE_TYPE=Microsoft SQL Server #$$DATABASE_TYPE=DB2 The default database type is Oracle. Complete the following steps to change the database type: 1. Delete the # character from the index database type parameter. 2. Add the # character to other database parameters. Parameter File Configuration 13

22 Verifying the Relational Connection Name The POE.param file contains $$DBCONNECTION parameters for Oracle, Microsoft SQL Server, and IBM DB2. Update the file to specify the connection name for the index database. The POE.param file contains the following connection parameters: $DBConnection_POE=POE_Oracle #$DBConnection_POE=POE_MSSQL #$DBConnection_POE=POE_DB2 The default connection is Oracle. Complete the following steps to set the connection name: 1. Delete the # character from the index database connection name. 2. Add the # character to other connection parameters. Verifying Database Connection Details The POE.param file contains database connection parameters. PowerCenter mappings use the connection parameters to search the SAP index. The POE.param file contains the following connection parameters: $$DBHostName= $$DBPortNumber= $$DBUserName= $$DBPassword= $$DBOracleSID= $$DBDatabaseName= Complete the following steps to set the connection parameters: 1. Add the host name, port number, user name, and password that PowerCenter can use to access the database. Use an encrypted $$DBPassword value. 2. Add a database name or a database ID: Add a $$DBOracleSID for an Oracle database. Add a $$DBDatabaseName for a Microsoft SQL Server or IBM DB2 database. Note: To use an encrypted $$DBPassword value, you define a password encryption key in PowerCenter. Defining the Encryption Key Use the PowerCenter Transformation Developer to define the encryption key. 1. Start the PowerCenter Designer. 2. Open the Transformation Developer and connect to the PowerCenter repository. 3. Open the project folder that contains the SAP Point of Entry transformations. 4. Browse to the EXP_Encryption_Key transformation. Drag the transformation to the editor. 5. Select the Ports tab on the transformation. 6. Edit the EncryptionKey expression to create a custom key. 7. Save the transformation. Keep the key secret. Use the key to encrypt and decrypt the password that you store in the POE.param parameter file. 14 Chapter 2: Installing and Configuring Informatica Components

23 Creating an Encrypted Password Use the PowerCenter Web Services Hub to create an encrypted password. 1. Log in to PowerCenter Web Services Hub Console. The Web Services Hub URL has the following format: The default port number is In the left-hand pane, click Valid WebService. 3. In the right-hand pane, select the POE_Encrypt_Password service. Click Try-It. 4. In the left-hand pane, select the POE_Encrypt_PasswordOperation web service operation. Note: The operation might take a few moments to appear. 5. In the right-hand pane, select the HTML Request Form tab. 6. Enter the database password in the Input form field, and click Send. 7. Copy the text of the EncryptedPassword element from the SOAP response to the parameter file. If you change the PowerCenter Integration Service that runs the workflows, re-encrypt the password and update the POE.param file. Parameter File Configuration 15

24 C H A P T E R 3 Installing and Configuring SAP Components This chapter includes the following topics: SAP Component Installation and Configuration Overview, 16 SAP Support File Configuration, 17 Enabling HTTP Communication between SAP and PowerCenter, 18 Informatica Table Setup, 18 Informatica Table Data Population, 19 Error-Tolerant Search and Duplicate Analysis Configuration, 21 Address Search Configuration, 22 Address Search Activation, 25 Index Pools, 26 SAP Index Population, 27 SAP Component Installation and Configuration Overview You install and configure the SAP components after you install and configure the Informatica components. To install and configure the SAP components, complete the following steps: 1. Import the SAP support files. 2. Enable HTTP communication between SAP and PowerCenter. 3. Configure the SCREEN and WEBSVC tables in the /INFADQPE/ namespace. 4. Configure the error-tolerant and duplicate search functionality. 5. Configure the address search functionality. 6. Activate index pooling on the index table. 7. Populate the index with the SAP database records. 16

25 SAP Support File Configuration Data Quality for SAP Point of Entry delivers the SAP table configuration settings in support files. You import the files to the SAP system. Data Quality for SAP Point of Entry includes the following support files: DE _ PAT. Adds the Postal Validation Business Address Service (BC-BAS-PV) to the SAP system. DE _ PAT. Adds the Duplicate Check and Error Tolerant Search Business Address Service (BC-BAS-DES) to the SAP system. DE _ PAT. Adds BC-BAS-PV and BC-BAS-DES to the SAP system. Copying the Support Files to the SAP System Before you configure the SAP system to call PowerCenter web services, copy the SAP support files to the SAP system. u Copy the PAT files to the following location: /usr/sap/trans/eps/in Loading the Support Files to the Application Server Use SAP Easy Access to load the support files. 1. Open SAP Easy Access. Enter the following transaction code in the toolbar window: SAINT 2. Click the check-mark button, or press Enter. 3. Open the Installation Package menu. Select Load Packages > From Application Server. SAP displays the list of PAT files on the system. 4. Select the support files. The following table lists the files that you can select for each Business Address Service: Business Address Service File Name BC-BAS-PV BC-BAS-DES DE _ PAT or DE _ PAT DE _ PAT or DE _ PAT Note: Select the DE _ PAT support file to add the BC-BAS-PV service and the BC-BAS-DES service to the SAP system. 5. Press F3 to return to the to the Add-On Installation Tool view. 6. Click Start. Note: You can use the Filter option to show the installable and noninstallable PAT files. 7. In the Add-On/PCS column, select INFADQPE. 8. Click Continue to accept the next steps. SAP Support File Configuration 17

26 9. On the Installation Queue screen, select SAPK-170COININFADQPE. Click Continue. 10. When prompted to add modification adjustment transports to the installation queue, click No. 11. Enter the following support file password: 8897D44CDE Click Go. The installation process begins. 12. Click Finish to complete the PAT file installation. Enabling HTTP Communication between SAP and PowerCenter SAP and PowerCenter use the Simple Object Access Protocol (SOAP) to communicate. In the Data Quality for SAP Point of Entry environment, SOAP communication uses the Hypertext Transfer Protocol (HTTP). 1. On the SAP system, go to transaction SPRO. 2. Browse to the Define Proxy Configuration setting. Use the following path: SAP Customizing Implementation Code > SAP Netweaver > Application Server > Basis Services > Communication interfaces > Communication interfaces > Proxy configuration for HTTP Communication. 3. Update the Define Proxy Configuration setting with HTTP proxy information. Note: Deactivate the proxy if you do not use one. 4. Go to transaction SICF. 5. Press Execute. 6. Select Client > Proxy Settings. 7. Update the proxy setting with the proxy information. Note: Deactivate the proxy if you do not use one. 8. Got to transaction SMICM. 9. Select ICM from the Administration menu. 10. Select Exit Soft and then select Local. 11. On transaction SMICM, select Goto from the menu. 12. Select Hostname Buffer, and select Reset. Informatica Table Setup You add application configuration tables to the SAP system. The /INFADQPE/SCREEN table defines the structure of the data screens in the data entry application. The /INFADQPE/WEBSVC table defines the interaction between SAP and PowerCenter applications. 18 Chapter 3: Installing and Configuring SAP Components

27 Creating the SCREEN Table Use SAP Easy Access to create the SCREEN table. 1. Open SAP Easy Access. Enter the following transaction code in the toolbar window: /INFADQPE/SCREEN_INS 2. Click the check-mark button, or press Enter. SAP adds the values to the SCREEN table. When the process ends, SAP displays the following message: Six entries are created successfully in table /INFADQPE/SCREEN 3. Click the check-mark button, or press Enter. Note: Run the /INFADQPE/SCREEN_INS transaction once. If you run the transaction again, SAP replaces the Informatica values with default system values. Creating the WEBSVC Table Use SAP Easy Access to create the WEBSVC table. 1. Open SAP Easy Access. Enter the following transaction code in the toolbar window: /INFADQPE/WEBSVC_INS 2. Click the check-mark button, or press Enter. 3. Select the web service functionality that you want to enable. You can select one of the following options: Postal validation Duplicate check Both postal validation and duplicate check 4. Click the check-mark button above the list of options. SAP adds the values to the WEBSVC table. SAP displays a confirmation message when the process ends. Informatica Table Data Population After you configure the /INFADQPE/WEBSVC table, you update the data in the table. Note: You do not perform any task to update the /INFADQPE/SCREEN table. Informatica Table Data Population 19

28 Address Validation Web Service Values Update the URL, Service, and WebService fields for each web service in the /INFADQPE/WEBSVC table. The following table describes the values that you enter in each field: Web Service Name URL Field Service Field WebService Field POE_Search_Index [machine name on the network] [Port number. Default is 7333.] name]:[port number]/wsh/services/realtime/ POE_Search_Index POE_Quarterly_Adjustment [machine name on the network] [Port number. Default is 7333.] name]:[port number]/wsh/services/realtime/ POE_Quarterly_Adjustment/ POE_Search_Index [machine name on the network] [Port number. Default is 7333.] name]:[port number]/wsh/services/realtime/ POE_Search_Index POE_Update_Index [machine name on the network] [Port number. Default is 7333.] name]:[port number]/wsh/services/realtime/ POE_Update_Index POE_Validate_Address [machine name on the network] [Port number. Default is 7333.] name]:[port number]/wsh/services/realtime/ POE_Validate_Address Updating the Values in the WEBSVC Table Use SAP Easy Access to update the table values. 1. Open SAP Easy Access. 2. Enter the following transaction code in the toolbar window: SPRO 3. Click the check-mark button, or press Enter. 4. Select SAP Reference IMG. The SAP Customizing Implementation Guide opens. 5. Browse to the following location in the guide: SAP NetWeaver > Application Server > Basis Services > Address Management > Webservice Values Activity. 6. Click the check-mark beside Webservice Values. SAP Easy Access opens the following table: IDQ: Webservices for Address Validation 7. Add the address validation web service values to the table. You must provide the following values for each web service: URL Service WebService 8. Click Save. 20 Chapter 3: Installing and Configuring SAP Components

29 Error-Tolerant Search and Duplicate Analysis Configuration SAP can call a duplicate analysis workflow in different real-time scenarios. If a data entry user enters a partial address to the SAP system, SAP calls a workflow to search the index for similar addresses. The PowerCenter Integration Service performs an error-tolerant search on the index and returns all similar addresses to the SAP system. The end user can select an address to use for the transaction. If a data entry user saves a valid record following address validation, SAP calls a workflow to verify that the index does not store a copy of the record. The PowerCenter Integration Service searches the index for duplicate records and returns all potential duplicates to SAP. The end user selects one of the duplicate addresses or updates the current address. The PowerCenter Integration Service runs the same workflow in each case. The web service that starts the workflow determines the level of similarity that the PowerCenter Integration Service looks for in the index records. You can update the thresholds that the PowerCenter Integration Service uses in each case. Color Classifications The PowerCenter Integration Service uses colors to classify the levels of similarity between an input record and the index records. The following colors indicate the different classifications: Green indicates that the input record is a close match with a record in the index. Yellow indicates that the input record is a partial match with a record in the index. Red indicates that the input record is a poor match with a record in the index. You can specify the score thresholds that define the color classifications. For example, you can assign a green status to any index record that matches an input record with a score of 90% or higher. The following table lists the default threshold values: Color Score Threshold Green 85 Yellow 55 Red 0 Minimum Score Values The PowerCenter Integration Service uses a minimum score value to filter the results of a duplicate record search. The search operation does not return any index record that matches an input record with a score below the minimum score. The default minimum score is 40%. You can edit the minimum score value. Error-Tolerant Search and Duplicate Analysis Configuration 21

30 Configuring the Score Settings for Duplicate Searches Configure the color classification scores and the minimum score thresholds. The SEARCH value defines the threshold for an error-tolerant search. The DUPLICATE value defines the threshold for duplicate analysis when a data entry user saves a record. 1. Open SAP Easy Access. 2. Enter the following transaction code in the toolbar window: SPRO 3. Click the check-mark button. 4. Select SAP Reference IMG. The SAP Customizing Implementation Guide opens. 5. Browse to the following location in the guide: SAP NetWeaver > Application Server > Basis Services > Address Management > Maintain Informatica Data > Webservice Values Activity. 6. Click the check-mark button beside Webservice Values Activity. SAP displays the name, the service key value, and the active status of the web services that you enabled. 7. Use the left and right arrows below the WebService Name column to select the following column: Green Traffic Light Review the DUPLICATE and SEARCH score thresholds. Optionally, update the threshold values. 8. Use the left and right arrows to select the following column: Yellow Traffic Light Review the DUPLICATE and SEARCH score thresholds. Optionally, update the threshold values. 9. Use the left and right column to select the following column: Red Traffic Light Review the DUPLICATE and SEARCH score thresholds. Optionally, update the threshold values. 10. Click Save. Troubleshooting Duplicate Check Issues If a data entry user enters person data to the SAP system but does not enter address data, the duplicate check operation can fail. SAP publishes note for users who experience the issue. If you expect an end user to enter person name data without a related address, follow the steps in note Address Search Configuration SAP can accept an input address in different formats. You define the input address formats that the SAP application passes to PowerCenter. Use the SAP table maintenance generator to define the formats. The SAP table maintenance generator lists the address fields that you can use to define an input address. Define the address format for SAP Address Type 1 and Address Type Chapter 3: Installing and Configuring SAP Components

31 Address Type 1 Structure Define an address structure for Address Type 1 and Address Type 2. The following table lists the fields to select for Address Type 1: Table ADCP ADCP Field BUILDING FLOOR CITY1 COUNTRY HOUSE_NUM1 LOCATION NAME1 NAME2 NAME3 NAME4 POST_CODE1 POST_CODE2 PO_BOX REGION ROOMNUMBER STREET STR_SUPPL1 STR_SUPPL2 STR_SUPPL3 Address Search Configuration 23

32 Address Type 2 Structure Define an address structure for Address Type 1 and Address Type 2. The following table lists the fields to select for Address Type 2: Table ADCP ADCP ADRP ADRP Field BUILDING FLOOR CITY1 COUNTRY HOUSE_NUM1 LOCATION NAME3 NAME4 POST_CODE1 POST_CODE2 PO_BOX REGION ROOMNUMBER STREET STR_SUPPL1 STR_SUPPL2 STR_SUPPL3 NAME_FIRST NAME_LAST 24 Chapter 3: Installing and Configuring SAP Components

33 Address Search Activation Activate the index and add a country field to the search screen to enable search options for partial address records. Adding a Country Field to the Search Screen Add the countries that the input address records identify. 1. Go to SAP transaction SE Enter table name TSAD Select Create entries. 4. Click OK to move through the steps in the wizard. 5. Find the -COUNTRY field. Select the check boxes in the fourth and fifth columns. 6. Save the settings. Verifying Error-Tolerant Search Capability When a data entry user enters an incomplete address, The PowerCenter Integration Service can search the SAP index for similar addresses. 1. Verify that the index database tables are initialized. 2. Go to SAP transaction SPRO. 3. Browse to the Address Management item at the following location: SAP Web Application Server > Basis Service > Address Management. 4. Run Activate duplicate check index pool. 5. Verify that KNA1-ADRNR is active. 6. Save the settings. Configuring the Address Types Use SAP Easy Access to define the formats of Address Type 1 and Address Type Open SAP Easy Access. 2. Enter the following transaction code in the toolbar window: SM30 3. Click the check-mark button. 4. In the Table/View field, enter the following table identifier: TSAD10 5. Click Maintain. If SAP displays information messages, click the check symbol to close the message boxes. 6. SAP displays the fields that define Address Type 1 and Address Type 2. The field lists appear under the following heading: Indexable address fields for duplicate check Select or clear the fields for each address type. Address Search Activation 25

34 The following image shows the table view: Use the fourth column for Address Type 1. Use the fifth column for Address Type Click Save. SAP saves the updates as a user request before it commits the updates to the database. Select a current SAP request, or create an SAP request for the updates that you specified. To create a request, click Own Request. 8. Click the check symbol to store the request. SAP stores the request but does not commit the updates to the database. 9. Click the check symbol to run the request and save the updates to the database. Index Pools SAP can store multiple address data values in a single field. Data that SAP stores in a single field is known as pooled data. You must configure the index table to store data in the same way. Activating Index Pools Use SAP Easy Access to configure the index database table to store pooled data. 1. Open SAP Easy Access. 2. Enter the following transaction code in the text field on the toolbar: SPRO 3. Click the check-mark button. 4. Select SAP Reference IMG. The SAP Customizing Implementation Guide opens. 5. Browse to the following location in the guide: 26 Chapter 3: Installing and Configuring SAP Components