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

[. . . ] Match/Consolidate Custom Programmer's Reference Match/Consolidate 7. 80c September 2007 Contact information Contact us on the Web at http://www. firstlogic. com/customer If you find any problem with this documentation, please report it to Business Objects in writing at documentation@businessobjects. com. Copyright Patents Copyright © 2007 Business Objects. 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. 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. [. . . ] 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 25 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. 26 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 27 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 28 Match/Consolidate Custom Programmer's Reference Setting up external operations You may perform group posting entirely outside of normal Match/Consolidate processing. We will call this an external group-posting operation. Job file Under this method, no Group Posting blocks are used in the job file. However, the job file should include a block for the group-posting report. And in the blocks for output file or purge, the Do Group Posting parameter must be set to Yes. To set up external operations, your main program (not an exit function) should call three functions in the Match/Consolidate Custom library: Call mpc_set_gpst_num_ops() to set the number of external operations to be performed. Call mpc_set_gpst_name() to name your external operation(s). This call has the same effect as the parameter Group Post Name in the Group Posting block. The name that you set is used on the group-posting report, simply to identify each operation. Operations will be listed in the order that you set their names. Call mpc_set_exit() to set up your exit function. Make sure that your exit function will be called at least in the process state, and perhaps in the init and term states as well. To repeat, your exit function will be called only if the user has set the Do Group Posting parameter in the Execution block of the job file to Yes. [. . . ] 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 26. [. . . ]