11 processing wrap up
Processing Wrap-Up
Once the predecessor/successor pair have encountered all of the edits described, they will either be reported or bypassed on the one-to-one report, depending on whether they have failed one or more edits, and whether the all-relationships option has been selected. Tallies at the end of the report note the number of P/S pairs that failed each of the listed exception conditions.
In addition to the edits reported in Job 015D, there has also been an auxiliary report available to list the one-to-many and many-to-one predecessor/successor relationships (such as breakouts and consolidations in multi-unit families). This report is temporarily unavailable, however, due to the major processing changes enacted in Version 8.1. Hopefully, this report will be restored soon. These conditions are not edited by this job for any types of disparity, but the information can be helpful in resolving some of the anomalies flagged in multi-balance breakout and consolidation warning messages (Code 183 and Code 184 ), which were described earlier. Alignment of data in these transitions is an effective cleanup tool that should be utilized.
Micro Edit File records do not yet exist for predecessor/successor edit exceptions. They must be reviewed with the report in conjunction with either the ES2C or ES2G screen. However, predecessor/successor data consistency is an important aspect of cleaning up a quarter’s files to prepare to submit the quarterly EQUI deliverable. In fact, the growing value of wage records to identify predecessors and successors lends credence to the importance of these edits. Job 015D should be run as part of the normal quarterly cycle.
Related Links
