05 adding new micro edit record
Adding a New Micro Edit Record
It is rare that you would manually need to add a record to the micro edits, since the exceptions are almost universally found in the batch edits, to be reviewed on-line. However, there may be a time when changes to a record have been made on ES2C (or on another screen), and the data look peculiar (perhaps with a non-seasonal employment shift). You can always know immediately from any of the ES2C screens whether the displayed account is on the Micro Edit File based on whether the ES2E (Shift-F4) description on the bottom of the screen displays in pink. Transferring to ES2E from any ES2C screen with the Shift-F4 key combination will edit the record, even if it is not currently on the edit file. If it turns out that this record fails one or more edits, the establishment is added to the Micro Edit File, the exceptions are flagged and highlighted, and you will be directed to the first exception field for action. Then, if you go back to the ES2C screen, using the Shift-F4 combination, you will see the description of the ES2E screen transfer in pink, rather than blue.
As a record is added to the micro edits, its sort key must be established so it will appear in the proper placement. Part of that placement is where it would have appeared in the printed report, had this condition existed at the time of the last micro edits. The page number field is assigned to a newly added record based on the next record on file after its placement. So, if the next micro edit record would have been on page 179, the same page number will be listed for the new account. However, the page number will be displayed in pink to signal that it doesn’t actually appear on the printed output, but signals where it belongs in the grand scheme of the edits. This same pink coloring is used for all non-printed edit exceptions (those that have no crucial-level conditions, but have had no data changes from one edit run to the next).
There are certain cases when the files (Micro and Micro Edit) are out of synchronization, primarily when corrections are made externally to ES2E, such as in the ES2C screen. For instance, let’s say an establishment had originally shown an invalid county code (such as zeroes), and a tax rate disparity (e.g., 0.3% listed, but 0.7% calculated from contributions divided by taxable wages). A correction of the county code on ES2C would not remove the error code 013 (invalid county) from the MEXR data, since the edits performed by ES2E would not recognize that the problem had been there previously. This is also noted often in the 018D (A-list errors) and 008S (Faster Fester report) batch jobs, since they both use obsolete micro edit data in preparing their output.
Related Links
