[Mveca_usps] FW: Payroll updates available in OECN_OOPS

[Deb Dinnen]

Hello,

The following patch was installed affecting the SERSHIRE and STRSHIRE programs:



*         RETIRE/SERSHIRE & STRSHIRE:  Allow up to 6 months for a new employee to be reported

o   Both SERSHIRE and STRSHIRE were looking at jobs that had a position start date within 60 days of the current date.  Because substitutes and supplementals are not always paid within 60 days we have modified SERSHIRE and STRSHIRE.  It will now first look at the 400 or 450 DEDSCN new employee flag.  If the new employee flag is set to "Y", it will then see if any jobs with a retire code of 400 or 450 has a position start date within 6 months (183 days).  If more than 1 job falls within the 6 month timeframe, the most recent job will be reported for that start date.

*         RETIRE/SERSHIRE & STRSHIRE:  Add reports to PAYROLLCD

o   Added both the SERSHIRE and STRSHIRE reports to PAYROLLCD when running in the ACTUAL mode.  The SERSHIRE reports will be under Number 13_SERSHIRE and the STRSHIRE reports will be under Number 14_STRSHIRE.  The current date will also be part of the name in PAYROLLCD, along with the sequence number.  For example, SERSHIRE_20140612_1.TXT;1 is the SERSHIRE report that was run on 2014/06/12 for the first actual run of the day (sequence number).

*         RETIRE/SERSHIRE & STRSHIRE:  Fix problem with all 1's record in both SERSHIRE & STRSHIRE

o   If a district is not using an employee id of 111111111, the program was trying to validate, report and put the dummy record in the csv file.  Both the SERSHIRE and STRSHIRE will also look at the true ssn (which is always all 1's for the dummy record) in case the employee id is not all 1's.  The dummy record will not be validated or reported.

*         RETIRE/SERSHIRE & STRSHIRE:  Fix unending loop problem in both SERSHIRE and STRSHIRE

o   If the very last record in the deduction file (DEDSCN) has the new employee flag set to "Y" on the 400 or 450, the SERSHIRE or STRSHIRE would not complete because it was in an unending loop.  This has been fixed.


Let me know if you have any questions.

Deb Dinnen
937-767-1468 x 3113
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listserv.mveca.org/pipermail/mveca_usps/attachments/20140723/3755de4e/attachment.htm>