05 miscellaneous editing issues
Miscellaneous Editing Issues
The “R” sort parameter can allow the lowest numbered error code to be selected as a sort sequence. However, this doesn’t mean that the most severe errors will control the sequence of accounts. An error code 024 (reactivation date format problem) is a fairly low number, but is considered a “C” level condition (according to the BLS A-B-C prioritization scheme). Alternative prioritization can be selected according to the A-B-C list (using the “G” sort code), or the highest score values can be viewed first (with the “F” sort option). Even with all of these options, however, these sort parameters in themselves may be insufficient for certain types of review. For example, sometimes the QCEW analyst will want to see all new employers with a large initial employment (flagged with code 139). Since this is one of the lowest-classified micro exceptions, the error-based sort will likely miss many of these employers. To target specific error codes, it is necessary to use the error code/year-quarter entry fields; however, these will appear strictly by SESA ID, which may cross the boundaries of an individual’s area of responsibility.
One caveat should be mentioned regarding the error-based perusal of micro edit data. This browsing is based on the most recent editing data available (i.e., from the latest batch edit job run, or the latest updates from the ES2E screen). When micro records are updated through other CICS screens, such as ES2C, ES2R, or ES2V, the edits are not rerun, as they are with this screen; so the editing cross-reference information can become obsolete. Even ES2E will not always remove the error-based MEXR records from the file, giving obsolete error code references to the screen. When a particular error code had been present for an account, but the error was later reconciled elsewhere, the account will still be displayed in the error-code-based browse, unless there is no longer a Micro Edit record to be found. Then the program will continue on to the next record and delete the obsolete error code record.
Edit exceptions related to wage data are sometimes difficult to recognize visually, especially when the employment and total wage levels are high. The wage edit (codes 092 and 127) are actually composed of checks for total wage changes and average quarterly wage (AQW) shifts between quarters. Since the AQW is found by dividing total wages by the average monthly employment, a relatively stable total wage field may look fine even though employment may fluctuate. To help with the analysis of wage edits, the F6 key is available. This key replaces the contributions column with the AQW values for each quarter. This sheds new light on what the micro edits are concerned about. A decrease in employment with an increase in total wages will compound the difference in the AQW value. To return to contributions, press F6 again.
The macro edit key display is primarily for utilitarian purposes. When a particular employer has been associated with the integrated portion of the edit, the macro key (i.e., the county, 1-digit ownership and NAICS code) is displayed as “MAED” instead of the SORT key.
There will often be times when some of the fields that are used to sort the record within the micro edits will change. If the edits are in error-code sequence, but the most severe edit has been removed due to a data correction, the account should no longer be listed with that group of accounts. In such cases, the sort key will be adjusted, and a new placement for the record will be found. Simultaneously, another record at the same location in the edits will be inspected, donating its page number to the account being repositioned.
A potential problem could occur by the repositioning of a record into another part of the micro edits. You wouldn’t want to be “stuck” in another part of the edits when you have methodically been progressing through the edits under your purview. If an account is suddenly moved from page 21 to page 163, you will still need to get back to page 21 to look at the next record. Fortunately, the ES2E screen uses the original placement of an account for paging from account to account (with the F7 and F8 keys), rather than any new placements. Hence, once you’ve finished with the account that has been moved to page 163, advancing to the next record will bring you to the next account on page 21.
ES2E shares one feature with ES2C as well. Administrators (with an “A” security level) can update all micro data, even if locks have been set with the ES2I screen. This is helpful when there are still typographic or other correctable conditions present for accounts, but the quarter in which they occur is locked. This same update override feature is also available in ES2H, ES2V, EARC, etc.
Related Links
