05 deleting micro record
Deleting a Micro Record
When there is a need to remove a micro record from the file, you have two options. If a record was added by accident, typing in an end-of-liability (EOL) date that is identical to the initial liability date will signal a record deletion in the next micro edit process (Job 028D, 001Q, 002D, etc.). If you want to immediately remove the record, however, you can type “*D” at the beginning of the NEXT-SESA-ID area. The combination of the asterisk and the letter “D” is an EXPO/EARS standard for deletion of a record or a set of records. After you have signaled the record deletion, the program will prompt you to confirm the deletion. The following message signals that you are a keystroke away from deleting the record:
If you are sure you want to delete the record, press the Enter key. If you have decided to let it remain on the file, press a function key, such as F1, F3, or F5.
Deleting a record requires that there will be no damage to locked quarters of the micro record. For instance, if the immediate prior quarter has been locked on the ES2I screen (denoted by a ‘3’ in the “FILE LOCKED” list of codes), but the employer was active (status ‘1’) in that quarter, it is not feasible to delete this establishment, since the finalized data in the prior quarter would be altered by the removal of this record. Similarly, if the administrative data have been locked, the record can’t be deleted, since there can be no change to the addresses, phone numbers, etc., associated with any account. When locked data prevent the deletion, the following message notes the reason for the prohibition:
Either the quarters and/or administrative data need to be unlocked in the ES2I screen (available only to those with administrator-level access), or there will be no deletion of the micro record in question. If all quarters and the administrative data are locked, the alternate message appears instead:
When the Micro record is deleted, Administrative and Quarterly Transaction File records list the contents of the micro record at the time of its removal. Simultaneously, most of the associated records on other files are removed as well. A mailing address on the MOA File will be removed, as will an associated Refiling record (if the employer had been slated for refiling during the current cycle). Both of these files have their own transaction files as well (the MOA Transaction File and the Refiling Transaction File). Therefore, records are written to these transaction files as the MOA and Refiling records are removed.
An interesting, if perhaps perplexing, effect can occur when going through the various update modes of this screen. When some (but not all) of the data lock switches have been set in ES2I, it causes those associated fields to be non-updateable on the screen. However, some of the update modes are set up specifically to handle those fields. As an example, the physical location/geocoding data lock switch prevents the physical location address block from receiving any updates, even when the update mode is set up exclusively for this block of data in the upper left-hand portion of the screen. So it appears that the screen is in inquiry-only mode in such instances.
Related Links
