User manual BUSINESS OBJECTS EDATAQUALITY SUITE 7.60C RELEASE 4

[. . . ] eDataQuality Suite User's Guide Version 7. 60cR4 April 2006 eDataQuality overview How to set up your server How to set up your clients API and field reference Notices Published in the United States of America by Firstlogic, Inc. , 100 Harborview Plaza, La Crosse, Wisconsin 54601-4071. Customer Care Technical help is free for customers who are current on their ESP. When you call, have at hand the user's manual and the version number of the product you are using. Call from a location where you can operate your software while speaking on the phone. [. . . ] ACE uses this information 2 to assign a ZIP Code. You cannot use the discrete fields City and State if: 1) You store city and state together in a combined field, or 2) You use state abbreviations other than those set by the U. S. 3 Although ACE assigns them from a postal database, County numbers are not really "postal" codes used in mail handling (except in Periodicals Class). If you have a field specifically for the ordinary, 5-digit ZIP Code, then present it to ACE through the ZIP field. ACE uses this information to confirm, or perhaps to complete, the city and state data. ZIP4 codes are required for Postnet barcoding. They are also important for the GeoCensus Option. Notice that the proper field name does not include the plus sign (+). If you have a combined field for ZIP and ZIP+4, present it through the ZIP10 field instead. For input, it doesn't matter whether or not you have a hyphen between the codes. If you set up ACE to automatically update this field, it will insert a hyphen intelligently. Street address ace. input. address ace. input. suite ace. input. urb City State ace. input. city ace. input. state County ace. input. county ZIP Code ace. input. zip 5 ace. input. zip4 4 ace. input. zip10 10 122 eDataQuality User's Guide ACE U. S. input fields Type of data Field name Length Description Address lines ace. input. lastline up to 60 There are some situations in which you should use the ACE field Last Line instead of the separate City, State, and ZIP fields: If you have a combined city-state-ZIP field, well, that's exactly what ACE calls Last Line. For example, your mapping might be: ace. input. lastline = City_ST_ZIP. Perhaps you have a combined city-state field, but a separate field for ZIP. In that situation you have to set up the Last Line field to include (concatenate) both of your fields; for example, ace. input. lastline = City_State & ZIP. You do not have to physically merge your fields. If your State field contains full spellings or abbreviations other than those set by the U. S. Postal Service, do not use the discrete State field. Instead, present your city, state, and ZIP fields together through the Last Line field. For example: ace. input. lastline = City & State & ZIP up to 60 Some companies store name-address data in an open format of four or more lines. We call this type of record format a multiline format. ACE can accept two to twelve lines of multiline input. [. . . ] For example, the parser previously identified Hewlett Packard as a personal name, so we added Hewlett Packard to the dictionary as a firm name. Overview of creating a dictionary To create a custom parsing dictionary, follow these basic steps: User-Modifiable Dictionaries (UMD) 207 1. Use UMD Show to query our base parsing dictionary. Look for existing entries for the words you wish to add or change. Put your custom entries in a transaction file. [. . . ]