|
|
||
|
|
|
|
|
Version 05.13.02.00.06, March 6, 2013 - addendum release |
|
|
Feature: |
DRS Transmittal File |
|
Issue #: |
246616 |
|
Change: |
The DRS Transmittal file process no longer includes future employment records. |
|
Reason: |
Eligibility dates that are effective after the reporting period of the transmittal are rejected by DRS. |
|
Menu: |
WH\PA\RE\DT OR HR\PA\RE\PA\RE\DT |
|
Version 05.13.02.00.05, March 2, 2013 - standard release |
|
|
Feature: |
Re-Create DRS Transmittal File |
|
Change: |
Changed the Re-Create DRS Transmittal program to create the correct output filename format. |
|
Reason: |
The Web Re-Create DRS Transmittal created incorrect transmittal filenames and extensions that were not acceptable to DRS. The correct filename format is OOOOMMMVV.PRD.FIX. OOOO = Organization, MMM = Month, VV = Version, PRD = Format Indicator, FIX = Extension. |
|
Menu: |
Human Resources\Employee\EP\RE\RE\RD OR Human Resources\Payroll\PA\RE\RE\RD |
|
Version 04.12.02.00.04, March 3, 2012 |
|
|
Feature: |
Retirement Transmittal (Retirement Adjustments “Do Not Report”) |
|
Issue #: |
237545 |
|
Change: |
The Retirement Transmittal process was modified to prevent the report period from being populated on retirement adjustments that are marked “Do Not Report to DRS”. Previously, retirement adjustments that were marked “Do Not Report to DRS” were being populated with a report period on the Retirement Adjustments screen even though they weren’t reported. The Retirement Adjustments Report was modified accordingly. Both the Retirement Adjustments screen and report were also modified to display the Check date associated with processed adjustments. |
|
Reason: |
Defect Correction |
|
Menu: |
HR\PR\WS\RT |
|
Version 04.11.06.00.05, August 13, 2011 |
|
|
Feature: |
WESPaC DRS Transmittal (Exceptions) |
|
Issue #: |
235545 |
|
Change: |
The DRS Transmittal was modified to include the following exceptions: If any employee shares a Social Security Number with another employee, this exception will be reported and no extract will be created. (Both employees will be listed on the exception report.) If an employee being reported has a blank birthdate in the NAME table and an M – Member Information record is being transmitted, this exception will be reported and no extract file will be created. If an employee being reported has a blank Social Security number, this exception will be reported and no extract file will be created. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PA\RE\PA\RE\DT HR\PR\WS\RE\WR\DT |
|
Version 04.10.12.02.12, July 9, 2011 |
|
|
Feature: |
WESPaC Retirement Transaction Report\DRS Transmittal |
|
Issue #: |
236057 |
|
Change: |
DRS record counts were restored to the Plan and System total pages of the Retirement History report. Removal of these counts made it difficult to determine which Retirement Plan and System the totals are listing when reporting by employee. Also, these totals may be useful when the History report selections include all the retirement systems and records reported for one reporting period. The totals in this case should then match the transmittal file’s original counts. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PA\RE\PA\RE\RT HR\PA\RE\PA\RE\DT |
|
Version 04.10.12.02.12, July 9, 2011 |
|
|
Feature: |
WESPaC Retirement Transaction Report\DRS Transmittal |
|
Issue #: |
233940, 230167 |
|
Change: |
The Retirement Transaction Report and DRS Transmittal were modified to include a maximum of one ‘M’ record per member per transmittal and send this record only when the employee’s name, address, birthdate, or gender has changed from the value previously transmitted, or if the employee’s member information was not reportable in the previous reporting period, due to ineligibility or member status as a retiree (Type 97, 98, 99). ‘M’ records, however, will only be sent when other record types are transmitting for the employee and the employee has a Retirement Member Profile active in the current reporting period. The Retirement Transaction and Transmittal reports now indicate those employees whose member information will transmit. A WA001DRSMember record is now only created when an M record is sent. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PA\RE\PA\RE\RT HR\PA\RE\PA\RE\DT |
|
Implementation Note: |
WSIPC ran a data manipulation with the July 09, 2011 SR that removed extraneous duplicate or unsent records from the WA001DRSMember table. |
|
Version 04.10.12.01.03, March 12, 2011 |
|
|
Feature: |
WESPaC Retirement Transaction Report\DRS Transmittal |
|
Issue #: |
234827 |
|
Change: |
The Retirement Transaction Report and DRS Transmittal were modified to appropriately create ‘B’ records in cases when ‘B’ records with different Type codes are needed for the same person, plan, and earning period. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PA\RE\PA\RE\RT HR\PA\RE\PA\RE\DT |
|
Version 04.10.12.00.04, February 5, 2011 |
|
|
Feature: |
WESPaC Retirement Transaction Report\DRS Transmittal |
|
Issue #: |
230167 |
|
Change: |
The Retirement Transaction Report and DRS Transmittal were modified to not send B or C records if plan 3 has a future eligibility date. Entering a future start date for a plan should not generate a B code for a month that plan is not yet in effect, or generate a zero amount defined contribution record if the future plan is plan 3. A member profile for a future earning period should not cause a B code or contribution record to be created for an earlier earning period. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PA\RE\PA\RE\RT HR\PA\RE\PA\RE\DT |
|
Version 04.10.12.00.04, February 5, 2011 |
|
|
Feature: |
WESPaC Retirement Transaction Report\DRS Transmittal |
|
Issue #: |
233850 |
|
Change: |
Retirement Adjustments with “do not report” were incorrectly included in the DRS transmittal. This happened because the program was reverted to the previous version, which used the old field “MiscLogical” instead of the new “DoNotReport” field, but the data had been moved to the new field. This issue was fixed with the 1\12 NSR With this release, WSIPC ran a query to identify any items that were reported that should not have been reported, then provided the list of items to affected School Districts, so they could correct them in WBET. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PA\RE\PA\RE\RT HR\PA\RE\PA\RE\DT |
|
Implementation Note: |
WSIPC ran a query to identify any items that were reported that should not have been reported, then provided the list of items to affected School Districts, so they could correct them in WBET. |
|
Version 04.10.06.02.08, December 28, 2010 NSR |
|
|
Feature: |
WESPaC DRS Transmittal |
|
Issue #: |
233431 |
|
Change: |
Retirement Transmittal File process, Retirement Transmittal Report, and Retirement Transaction Report – Reverting the DRS programs to prior to the December Standard Release so that employee addresses will not be incorrectly reported to DRS. Please refer to the Alert Message # 233431 dated December 22, 2010 for additional details. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PA\RE\DT HR\PA\RE\RT |
|
Version 04.10.06.02.08, December 4, 2010 |
|
|
Feature: |
WESPaC Retirement Transmittal (Annual Statement Sort) |
|
Issue #: |
229759 |
|
Change: |
The View Employer Information screen was modified to remove the “Annual Statement Sort” option. This option is invalid as DRS no longer mails statements to districts. |
|
Reason: |
Approved enhancement. |
|
Menu: |
HR\PR\WS\RE\WR\DT HR\PR\RE\PA\RE\DT |
|
Version 04.10.06.02.08, December 4, 2010 |
|
|
Feature: |
WESPaC Retirement Transmittal (Name\Address Changes) |
|
Issue #: |
231441 |
|
Change: |
The DRS Retirement Transmittal file was modified to include name, address, birthdate, and gender changes when no other information is reported for the employee. Previously, name, address, birthdate, and gender changes were not included in the Retirement Transmittal if there was no other data to report for the employee. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PR\WS\RE\PR\WR\DT HR\PA\RE\PA\RE\DT |
|
Version 04.10.06.02.08, December 4, 2010 |
|
|
Feature: |
WESPaC Retirement Transmittal and File (‘B’ Records) |
|
Issue #: |
230167 |
|
Change: |
The Retirement Transmittal Report and the DRS Transmittal File were modified to not create the following when there is a Retirement Member Profile with a future start date (future earning period):
When changing a retirement eligibility start date, the informational message now states: “You changed the Start Date. The system will create a DRS employee employment transaction on the next appropriate transmittal.” When changing a retirement eligibility end date, the informational message now states: “You changed the End Date. The system will create a DRS employee employment transaction on the next appropriate transmittal.” |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PR\WS\RE\PR\WR\DT HR\PA\RE\PA\RE\DT |
|
Version 04.10.06.02.03, November 6, 2010 |
|
|
Feature: |
WESPaC Retirement Transmittal Report and File (‘M’ Records) |
|
Issue #: |
230194 |
|
Change: |
The DRS Transmittal File was modified to exclude retiree name and address changes that shouldn’t be reported. Previously, the DRS Transmittal may have been out of balance because a retiree name or address change was reported on a Member record if the retiree’s Retirement Member Profile record had an Eligibility End Date, but was not included in the record count control total on the Summary record. This “M” record should not have been included, as changes to retirees should not be reported. The retirees should make name and address changes directly with DRS. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PR\WS\RE\PR\WR\DT HR\PA\RE\PA\RE\DT |
|
Version 04.10.06.01.16, October 9, 2010 |
|
|
Feature: |
WESPaC Retirement Transmittal Report |
|
Issue #: |
230221 |
|
Change: |
The DRS Transmittal File was modified to exclude member profile changes for retirees. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PR\WS\RE\PR\WR\DT HR\PA\RE\PA\RE\DT |
|
Version 04.10.06.01.08, September 11, 2010 |
|
|
Feature: |
WESPaC Retirement Transmittal Report and File |
|
Issue #: |
225595 |
|
Change: |
The Retirement Transmittal Report and the DRS Transmittal File was modified to exclude member profile changes that shouldn’t be reported, and to ensure the control totals on the summary record match the detail on the transmittal file. New warnings were added to identify any differences between the control totals and detail records, which would create a DRS status of Out-of-Balance. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PR\WS\RE\PR\WR\DT HR\PA\RE\PA\RE\DT |
|
Version 04.10.01.00.00, April 10, 2010 |
|
|
Feature: |
WESPaC DRS Transmittal File (Retirement End Dates) |
|
Issue #: |
223807 |
|
Change: |
The DRS Transmittal process was modified to prevent the continued transmittal of retirement end dates. Previously, if a duplicate end date record was inadvertently created, the process continued to send duplicate end dates. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PR\WS\RE\PR\WR\DT HR\PA\RE\PA\RE\DT |
|
Version 04.09.06.02.02, March 13, 2010 |
|
|
Feature: |
WESPaC Re-create Retirement Transmittal File Screen |
|
Issue #: |
215690 |
|
Change: |
The Re-create Retirement Transmittal File Screen was modified to reformat the report version field to “99” so the complete report version will display in the browse. Previously, the report version for the browse was formatted as “9” and only the leading 0 of the report version was displayed. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\PA\RE\PA\RE\RD |
|
Version 04.09.02.00.01, May 9, 2009 |
|
|
Feature: |
DRS Retirement Transmittal Enhancements and Corrections Unreported Payrolls |
|
Issue #: |
n\a |
|
Change: |
Each transmittal will now automatically pick up all unreported payrolls from previous months. Quick Voids and reissued payrolls that are done after the original transmittal is created will automatically be included in the next month’s transmittal. |
|
Reason: |
Previously only the current month’s payroll activity was included in the transmittal. |
|
Menu: |
HR\PA\RE\DT |
|
Implementation Notes: |
To determine what, if any, additional retirement information from previously unreported payrolls will be included with the file created in the first payroll run after the release, the client must run the Retirement Transaction Report for all Earning Periods, all Retirement Plans, and all Transaction Sources that are Paid not Reported.
This report must be run after the client has reported the last DRS transmittal file for the April payroll, but before the first payroll is run after the May standard release. |
|
Version 04.09.02.00.01, May 9, 2009 |
|
|
Feature: |
DRS Retirement Transmittal Enhancements and Corrections B code creation |
|
Issue #: |
206063 and 209588 |
|
Change: |
B codes will now only be generated for Plan 0 employees with type codes of 97 and 98 (retirees) and all Plan 1, Plan 2 and Plan 3 employees. |
|
Reason: |
DRS does not require B codes for substitutes. |
|
Menu: |
HR\PA\RE\DT |
|
Version 04.09.02.00.01, May 9, 2009 |
|
|
Feature: |
DRS Retirement Transmittal Enhancements and Corrections Transmittal file name change |
|
Issue #: |
3288 |
|
Change: |
The transmittal file name now ends with .prd.fix |
|
Reason: |
DRS requirement |
|
Menu: |
HR\PA\RE\DT |
|
Version 04.09.02.00.01, May 9, 2009 |
|
|
Feature: |
DRS Retirement Transmittal Enhancements and Corrections Duplicate SSN exception report |
|
Issue #: |
208940 |
|
Change: |
Duplicate SSN exception report now clearly indicates which employee’s member profile is generating the error message. In the rare occurrence of multiple employees with a member profile being assigned the same SSN, only the first employee will be indicated with an asterisk. |
|
Reason: |
Previously the report did not indicate which employee’s member profile generated the error message. |
|
Menu: |
HR\PA\RE\DT |
|
Version 04.09.02.00.01, May 9, 2009 |
|
|
Feature: |
DRS Retirement Transmittal Enhancements and Corrections Member Profile Records |
|
Issue #: |
207042 |
|
Change: |
Member Profile Records will now only be sent to DRS for new employees and those with address, name, and\or birthdate changes. |
|
Reason: |
DRS Requirement |
|
Menu: |
HR\PA\RE\DT |
|
Version 04.09.02.00.01, May 9, 2009 |
|
|
Feature: |
DRS Retirement Transmittal Enhancements and Corrections Transfers from Plan 2 to Plan 3 |
|
Issue #: |
203945 |
|
Change: |
The Employment Information Records with the start and end dates for Plans 2 & 3 will not be transmitted at all. Only the Plan Choice Record will be sent (with the choice date). |
|
Reason: |
Transactions were rejected by DRS |
|
Menu: |
HR\PA\RE\DT |
|
Version 03.07.02.01.04, July 14, 2007 |
|
|
Remedy Ticket: |
111833 |
|
Change: |
The transmittal process was modified to recognize the most current employee’s Retirement Profile. |
|
Reason: |
The system was recognizing the employee’s first Retirement Profile for a specific system and plan, rather than the most current. |
|
Menu: |
|
|
Version 03.07.02.00.00, April 7, 2007 |
|
|
Remedy Ticket: |
109421 |
|
Change: |
Fix the DRS transmittal program to write data to member Extension field instead of to member Suffix field. |
|
Reason: |
Member Profile data with Suffix populated with JR, SR, III, and etc. in WESPaC is transmitting data to DRS as Suffix. As per DRS definitions only Degrees earned are valid in the Suffix field |
|
Menu: |
|
|
Version 03.07.02.00.00, April 7, 2007 |
|
|
Remedy Ticket: |
109301 |
|
Change: |
Fix the DRS transmittal program so that the number of retirement records reported to DRS = number of records reported per DRS Transmittal Edit message. |
|
Reason: |
A change made to correct "B" code transaction creations introduced the out of balance condition. |
|
Menu: |
|
|
Version 03.06.06.01.04, November 4, 2006 |
|
|
Remedy Ticket: |
100274 |
|
Change: |
The DRS Transmittal process was corrected to properly create "B" transactions. |
|
Reason: |
"B" transactions were not being created when an employee had zero values for compensation, hours, or days in the reporting month. |
|
Menu: |
|
|
Version 03.06.06.01.04, November 4, 2006 |
|
|
Remedy Ticket: |
100508 |
|
Change: |
The DRS Transmittal process was updated to report employees who have an active or inactive status. |
|
Reason: |
Prior to this change, employees who were in an inactive status at the time the DRS transmittal was created were not reported. |
|
Menu: |
|
|
Note: |
WSIPC is gathering data to perform a data manipulation to report transactions that were not reported in the past. |
|
Version 02.05.06.1, September 10, 2005 |
|
|
Remedy Ticket: |
65733 |
|
Change: |
The process was changed to report the employee’s mailing address if it exists, and transmit the following name prefixes only: blank, "Rev.", or "Dr.". |
|
Reason: |
To include addresses in the transmittal and limit name prefixes. |
|
Menu: |
|
|
Version 02.05.06.1, August 13, 2005 |
|
|
Remedy Ticket: |
65851 |
|
Change: |
The DRS Transmittal will now send blank for the rate option and the investment manager fields for employees who have not yet chosen options. |
|
Reason: |
A zero value was being reported to DRS in the rate option and the investment manager fields. The values should be blank for employees who have not chosen a rate option or investment manager for plan 3. |
|
Menu: |
|
|
Version 02.05.01.2, April 9, 2005 |
|
|
Change: |
Added a check for duplicate social security numbers and an exception report to print if any are found. |
|
Reason: |
Duplicate Social Security Numbers cause significant problems with the transmittal because it is keyed on these numbers. |
|
Menu: |
|
|
Note: |
Changes were made to hr\6paret15.p |
