User manual BUSINESS OBJECTS GLOBAL MATCH 8.00C

[. . . ] Global Match User's Guide Global Match 8. 00c April 2009 Copyright information © 2009 SAP® BusinessObjectsTM. SAP BusinessObjects and its logos, BusinessObjects, Crystal Reports®, SAP BusinessObjects Rapid MartTM, SAP BusinessObjects Data InsightTM, SAP BusinessObjects Desktop IntelligenceTM, SAP BusinessObjects Rapid Marts®, SAP BusinessObjects Watchlist SecurityTM, SAP BusinessObjects Web Intelligence®, and Xcelsius® are trademarks or registered trademarks of Business Objects, an SAP company and/or affiliated companies in the United States and/or other countries. SAP® is a registered trademark of SAP AG in Germany and/or other countries. All other names mentioned herein may be trademarks of their respective owners. 2 Global Match User's Guide Introducing Global Match Global Match is a stand-alone product that you can use to find duplicates in Unicode-based text files. [. . . ] The following table specifies the possible values for the field type, which Global Match uses to normalize the data before forming a match key. Field type value Description name firm addr pc other Personal name data Firm name data Address data Post code data Use this value when no pre-processing or normalization for the matcher type is required. Edit the Match Keyfield configuration file To edit the Match Keyfield configuration file: 1. Open the Match Keyfield configuration file (gfirm_fld. cfg) in the \pw\ gmatch\samples directory. Set the options for the different keys on which you are matching. Specify the appropriate options like checking for abbreviations, checking for initials, transpositions, and so on. Refer to the documentation in the configuration file for details about each of the options. For those keys on which you do not specify any options, defaults will be used, as specified in the documentation in the file. 8 Global Match User's Guide Edit the Match General Configuration file To edit the Match General configuration file: 1. Open the Match General Configuration file (gfirm_gen. cfg) in the \pw\ gmatch\samples directory. Set the options appropriate for your job. Edit the Match Rule Definition configuration file To edit the Match Rule Definition configuration file: 1. Open the Match Rule Definition file (gfirm_rul. cfg) in the \pw\gmatch\ samples directory. Set the rules that the records should pass in order to be considered a match. Verify the results of the trial runs with settings in this file, and adjust them as necessary. Rule settings The following provides brief descriptions of the rule settings. However, you need to specify the matcher fields, which determine which matcher type to apply. For example: Matcher_Field: Country Code Map the matcher identifier input field values to the matcher type. The identifier text in the matcher field determines which matcher is to be applied. The format for mapping the match identifier is as follows: Matcher: "identifier-text", matcher_type For example: Matcher: "JPN", jp Specify one matcher field value per matcher entry. You can specify up to 32 matcher entries. Use one of the following matcher types: Chinese, Japanese, Korean, and Taiwanese. The table at right lists the values for each of the matcher types. Matcher type Value Japanese Korean jp ko If you know your data can be processed with a Chinese zh single matcher type, you can specify the tw Default_Matcher parameter. If you do not specify Taiwanese any default matcher, all the remaining records that cannot be associated with a particular matcher type specified above will be processed through the generic Unicode matcher. Run Global Match After you set up the input file, the DMT, and the configuration files, you are ready to run the job. Run Global Match in the installation directory as follows: flgmtc mygmtc. cfg Global Match verifies all of the configuration settings, issues any errors or warnings, and displays various informational and progress messages. Analyze the output Output file Global Match creates two types of output files: an output file and a report file. The output file has the same format as the input file, with the following fields appended to each record: Field Description Record Number Dupe Group ID This is the number of the record. All the records in one dupe group will have the same numeric ID. [. . . ] Every Match key must have an associated match key field. Refer to the Match Library Programmer's Reference for valid values of match key field names. You specified matcher values, but did not specify a matcher field. You can specify only 32 matcher values. Missing string value in Matcher Specifi- Matcher specification must contain a cation. [. . . ]