PLP--Crosscheck Redirection §

In PLP, incoming records that match database records on a primary key, but fail specfied crosschecks are output to an XCFail file where they can be reviewed using the MCU. The purpose of the crosscheck redirection rules (XCRR) is to decrease the number of XCFail groups that need human review in MCU.  

This is achieved by identifying common patterns when reviewing the XCFails in MCU, and then creating a rule in the PLP configuration that will 'redirect' these records1), the next time the program is run, from the XCFail file into an additional 'NoMatch' or 'Match' file.  

PLP consults the XCRR after all of the crosschecks have been evaluated. If, at this time, the record is destined to be output to the XCFail file, the redirection rules will then be checked. If the record matches one of these rules, it is removed from the XCFail queue and redirected to a different output file.: 

There are two forms in PLP that are used to setup the redirection rules: 

  • a table view that shows all of the rules at a glance, and  
  • a workform, that is used to add new rules to the table. 

Please Note 

The use of crosscheck redirection rules assumes that a fairly standard set of PLP match rules is in place. Since the XCRR is a new feature in PLP, its possible that many of your existing configs have made use of other parameters to achieve similar results (i.e., a reduced number of crosschecks, the use of the MaxHits or MaxXcFails options, etc.). For this reason, before embarking upon a major XCRR project, it may be a good idea to also start with a new set of Match Rules based on the TMQ defaults. 

1) and remove them from the XCFail stream
plp/redirection.txt · Last modified: 2013/04/27 09:09 (external edit)
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
Driven by DokuWiki Recent changes RSS feed