-
In the EH extract file, the employee record is built by SSN, by Position Sequence and by Effective Date. So if an employee has data overflow, the missing data will be for the highest position sequence and/or most recent effective dates. For example: If an employee has 5 position sequences, you may get all transactions for position sequences 01-04, but have only the oldest transactions for position sequence 05.
-
In the PY extract file, the employee record is built by SSN, by Pay Period and by Position Number. So, if an employee has data overflow, the missing data is will be for the most recent Pay Period and/or the highest position number. For example, if an employee has excessive retroactivity in the last fiscal year, you may get all payments for the first 11 pay periods, but only payments for the lowest position number(s) for the last pay period.
-
Employees with data overflow in the PY extract file are summarized in the PH and PHS files. Refer to the topic: Summarized Record Criteria for more information.
-
An employee overflow condition is not the same as running out of file space. Check the status message for your extract job to determine if you exceeded your allocated file space.
-
For complete information on extract files, refer to the CIRS User Manual.
Last Updated: October 3, 2005