User manual BUSINESS OBJECTS MATCH-CONSOLIDATE 7.70C CUSTOM PROGRAMMERS REFERENCE

[. . . ] Match/Consolidate Custom Programmer's Reference Version 7. 70c July 2006 Introduction to Match/Consolidate Custom Writing exit functions Group posting Match/Consolidate Custom library functions 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. [. . . ] For this purpose, Match/Consolidate Custom offers several get functions to retrieve fields or whole records, or get information about the input file or fields. For details, see the "Table of exit-support functions by exit point" on page 28. 26 Match/Consolidate Custom Programmer's Reference parse() exit function This type of exit function is available only during the Read Records processing step. It is called while reading records when parsing is performed. In previous versions of the manual, we referred to this exit as name_address_parse(). Perform your own data parsing You can use the parse() exit function to populate specific fields with the data you want. For example, Match/Consolidate can parse United States addresses but not addresses from other countries. During the exit, you could parse the address data, put the data into the appropriate key fields, and reset the AP parse status fields--for example, you might set the status of the address data to OK. Support functions During the parse() exit, you might call these support functions: Function Description mpc_get_ap_field() Find the current parse status of the record. For example, if you were targeting non-U. S. records, you could check the MPG_AP_LL_ERROR field for the code E403, which indicates a non-U. S. Get the original data or key data. mpc_get_db_field() mpc_get_pw_field() mpc_get_key_field() mpc_put_db_field() mpc_put_key_field() mpc_set_ap_field() Put data into database fields or key fields. For example you might set a value in one of the parse-status fields: MPG_AP_NAME_ERROR, MPG_AP_FIRM_ERROR, MPG_AP_ADDR_ERROR, or MPG_AP_LL_ERROR. Do not call ACE or TrueName Do not call either ACE Library or TrueName Library from this parse exit. If either of those programs is initiated in the parse exit, their functions will conflict with Match/Consolidate's use of those same functions. If you feel you need to call either ACE or TrueName from the parse exit, consider using the extended parsing settings in the Match Options block of your Match/ Consolidate job, instead. You should be able to get the results you want through that approach. Chapter 2: Writing exit functions 27 Table of exit-support functions by exit point The following table shows which exit-support functions you can call from each type of exit function. Exit support function input_ proc comp_ before comp_ after_ dupe Exit function comp_ after_ nondupe dupe_ group dupe_ group_ post output _proc parse mpc_get_ap_field() mpc_get_db_field() mpc_get_error_info() mpc_get_exit_type() mpc_get_info_in_field() mpc_get_info_in_file() mpc_get_info_key_field() mpc_get_info_out_field() mpc_get_info_out_file() mpc_get_info_pw_field() mpc_get_job_step() mpc_get_key_field() mpc_get_num_current_rec() mpc_get_num_in_files() mpc_get_num_recs() mpc_get_pw_field() mpc_get_pw_field_id() mpc_get_record() mpc_put_db_field() mpc_put_key_field() mpc_put_record() mpc_set_ap_field() mpc_set_current_rec() mpc_set_dupes() mpc_set_gpst_result() mpc_set_group_pos() mpc_set_process() mpc_set_unique() simscore() P P Yes Yes Yes Yes Yes No No Yes Yes No 1 Yes 1 P P P P No P No 1 No No No P P Yes P P Yes Yes Yes Yes Yes No No Yes Yes P P Yes 2 P P P No No No No P P No No No No Yes P P Yes Yes Yes Yes Yes No No Yes Yes P P Yes 2 P P P No No No No P P No No No No Yes P P Yes Yes Yes Yes Yes No No Yes Yes P P Yes 2 P P P No No No No P P No No No No Yes P P Yes Yes Yes Yes Yes No No Yes Yes No P Yes P P P P No No No No P No No P No No Yes P P Yes Yes Yes Yes Yes No No Yes Yes No P Yes P P P P P No P No P No P No No No Yes P P Yes Yes Yes Yes Yes P P Yes Yes No P Yes 2 P P P P No P No P No No No P No Yes P P Yes Yes Yes Yes Yes P P Yes Yes No P Yes 1 P P P P P Yes P P No No No P No Yes Yes = You can call this support function when the exit function is in any of the three states. No = You cannot call this support function. P = You can call this support function only when the exit function is in the process state. 1 = You can call this support function, but it will always return a 1. 2 = You can call this support function, but it will always return a 2. 28 Match/Consolidate Custom Programmer's Reference Chapter 3: Group posting This chapter explains the available options for performing group posting in Match/Consolidate Custom. Chapter 3: Group posting 29 Group posting options You may perform group posting by any of three methods: Method Description Internal You may perform group posting entirely within the normal Match/Consolidate job, by using Group Posting blocks in your job file. We will call this an internal group-posting operation. You may perform group posting entirely outside of normal Match/Consolidate processing. We will call this an external group-posting operation. You may perform group posting both internally and externally. That is, the user may set up operations through the job file, and then your exit function may perform postprocessing or additional operations. External Both 30 Match/Consolidate Custom Programmer's Reference Setting up external operations You may perform group posting entirely outside of normal Match/Consolidate processing. [. . . ] After mpc_set_group_pos() returns, the same record is still the current record, but it has a new position in the dupe group, so mpc_get_num_current_rec() would yield a different result. Returns Returns MPC_OK if successful. A return value of MPC_ERROR indicates an error, and mpc_errno is set to one of the following values: Value Description MPC_ERR_UNINIT MPC_ERR_IGNORED mpc_init() was not called. Function was called from other than an exit function, or was called from an exit function of an invalid type or state. For more information, see the "Table of exitsupport functions by exit point" on page 28. [. . . ]