|
|
||
|
|
|
|
|
Version 05.12.10.00.12, December 8, 2012 - standard release |
|
|
Feature: |
SPI Salary Exhibit Report |
|
Change: |
The Exception Report now displays Name Key when the Exception Message is “High Classified Hourly Rate has a null value or overflow format error.” |
|
Reason: |
Previously, the Name Key did not display on the Exception Report. |
|
Menu: |
Human Resources\Federal/State Reporting\SR\WA\SS |
|
Version 05.12.10.00.12, December 8, 2012 - standard release |
|
|
Feature: |
SPI Salary Exhibit Report |
|
Issue #: |
247782 |
|
Change: |
Updated the report and the F-195 and F-200 extract so that salary figures are rounded to the nearest dollar amount. |
|
Reason: |
The SPI Exhibit Salary Report program is dropping off cents from the salary amounts. |
|
Menu: |
Human Resources\Federal/State Reporting\SR\WA\SS |
|
Version 04.10.06.00.00, August 14, 2010 |
|
|
Feature: |
WESPaC SPI Salary Exhibit Exception Report (Null value\Format Error) |
|
Issue #: |
222821 |
|
Change: |
The SPI Salary Exhibit Exception Report was modified to generate an overflow data error if extremely large benefit amounts (values too large to be displayed) are encountered in the Salary Negotiation Plan. Previously, an exception was not generated when extremely large benefit amounts existed in the SN Plan. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\SN\WS\SR\SS HR\PR\WS\RE\SR\SS |
|
Version 04.09.06.02.01, December 5, 2009 |
|
|
Feature: |
SPI Salary Exhibit Report (Correct Classified Hours and FTE) |
|
Issue #: |
218035 |
|
Change: |
The Salary Exhibit Report was modified to display the correct hours and FTE for classified employees when the ‘Do not use calendar to find Calc FTE’ box or ‘Use FTE instead of Calc FTE to calculate pay amounts’ box is checked. Previously, classified hours, which were reported on the Salary Exhibit, were calculated by multiplying the assignment Total Hours & Minutes (as displayed on the screen) by the calculated or entered F.T.E. (as displayed on the screen).
This logic is appropriate when the calendar is used to derive Calc FTE, and the screen that displayed F.T.E. is an adjustment factor calculated as the Assignment Hours Per Day\Assignment Calendar Hours Per Day.
The logic is incorrect if the 'Do Not Use Calendar' box or 'Use FTE instead of Calc FTE' box is checked. The assignment Total Hours & Minutes should be reported as-is. When the classified reported hours are wrong, FTE is reported incorrectly since it is calculated as Hours\2080. Consequently, the Hourly Rate of Pay is also reported incorrectly when hours are wrong. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\SN\WS\SR\SS HR\PR\WS\RE\SR\SS |
|
Version 04.09.06.00.01, September 12, 2009 |
|
|
Feature: |
WESPaC Salary Exhibit Exception Report (Format Error) |
|
Issue #: |
216283 |
|
Change: |
The Salary Exhibit Exception Report was modified to provide detailed information about any missing data or data that is too big for a field. Previously, this type of erroneous data was omitted, and it was difficult to identify what was missing. Now, if null or oversized values are encountered, details about the incorrect data are reported to help identify the source of the error.
When there is no data in a field, sometimes a "null" value is stored in that field, causing errors when it is referenced. Null values are represented in WESPaC by a single question mark: “?”. A field most often contains a null value when its value is the result of a faulty calculation, such as when a field required for the calculation is missing or cannot be determined. For instance, if the calendar on the SN Plan Position Control and the calendar on the assignment do not match, the WC benefit calculation might result in a null value since there would be a discrepancy in the number of days needed for the calculation. In this case, a “?” would be displayed in the WC ded\ben Amt\Pct field on the Assignment Payroll Information screen.
Oversized data, or data values that are bigger than the field length, are represented in WESPaC by multiple question marks: “?????”. A field may contain an oversized value when its value is based on bad data. For instance, uncharacteristically large values in FTE or hours fields might result in calculated amounts that are too big for the field format in WESPaC, or on reports, or on the export file. Oversized data is represented on the report by a large negative number such as 999,999.999-. |
|
Reason: |
Defect correction. |
|
Menu: |
HR\SN\WS\SR\SS |
|
Implementation Notes: |
Previously, the Salary Exhibit – Certificated Employees section of the report printed first and the SPI Salary Exhibit Null Exception Report printed last. Now, if there are exceptions, the enhanced SPI Salary Exhibit Exception Report prints before the Salary Exhibit – Certificated Employees section and provides detailed information about null and oversized data (format) errors. |
|
Version 04.08.10.00.03, March 7, 2009 |
|
|
Feature: |
Salary Negotiations – WESPaC State Reports |
|
Issue #: |
211005 |
|
Change: |
Checks for null or over-sized data values are added to the following reports & extracts: S-275, Mix Factor & SPI Salary Exhibit. |
|
Reason: |
These checks help ensure accurate reporting and successful extract file load and edit at OSPI. |
|
Menu: |
HR\SN\WA icon\MF, SR & SS |
|
Version 03.07.10.01.04, August 16, 2008 |
|
|
Change: |
Remove message box after Copy SPI Code to Asn Brk utility runs |
|
Reason: |
Streamline process – remove a click. |
|
Menu: |
HR\PR\RE\SN\SR\SS HR\PR\WS\RE\SR\SS HR\SN\WS\SR\SS |
|
Version 03.06.01.5, June 3, 2006 |
|
|
Remedy Ticket: |
88163 |
|
Change: |
Program was changed to reference the proper data field in the file. |
|
Reason: |
The report was not properly displaying the minimum and maximum hourly rate. |
|
Menu: |
Human Resources\Salary Negotiations\ |
|
Version 02.05.06.2, November 5, 2005 |
|
|
Remedy Ticket: |
72923 |
|
Change: |
Correct the calculation for determining FTE. |
|
Reason: |
The report’s calculation of FTE was overstated. Consequently the calculation of low, average, and high salaries were understated. |
|
Menu: |
Human Resources\Salary Negotiations\ |
|
Version 02.05.01.3, May 23, 2005 |
|
|
Change: |
The program had assumed just one version of each code in the program, activity and duty (group) code tables. The reports will now collapse dollars for identical program\activity\duty combinations based on the state code within each table. The descriptions for program and activity are now coming from FFAMAD-ACCT-DESCS table. The duty description will be the first duty code used within the program\activity combination. The benefit report will now collapse benefit dollars for identical program\activity\duty combinations when used by both classified and certificated. |
|
Menu: |
Human Resources\Salary Negotiations\ |
|
Note: |
Hr\6pmrpt06.p |
|
Version 02.05.01.3, May 7, 2005 |
|
|
Change: |
Gpmrpt02.w |
|
Reason: |
Corrected problem when run was attempted before plan was generated. Added message window and aborted run when this was the case. |
|
Menu: |
Human Resources\Salary Negotiations\ |
