You may estimate salary increases through the Estimate Salary Increases Based on Performance (USPF) screen.
The USPF form allows the selection of EE’s (from selected parameter values i.e. Group, Unit, Department, Authorization area, and Location) who become eligible for salary increases based on their performance review and existing salary within its range.
Employees who are eligible for selection must not have an employment status of “Terminated”, ”Retired”, ”Lay Off”, “Deceased”, “Resigned” on the “EE as of date” parameter.
Employees may be disqualified from the PFP process for 5 reasons:
The selected EE’s are batched together by using the “Break by” parameter, giving the associated manager easy viewing of their projected wage totals on the ISPF screen.
Each EE is processed using the “Overall Rating” of their performance (from ISRV) and their existing compa ratio (EE’s Wage/Range Midpoint as seen in VEEP). These values are compared to the matrix associated to their salary range, which provides a suggested percentage of increase for their salary.
Reviews used in PFP must be of the type provided in the parameter “Include Review Type”, with a review date on or after the parameter “Reviews Effective As Of “ and have the same status as in the “Review Status” parameter. If more than one review qualifies under these conditions, the most recent review is used for PFP.
The new salary is stored as a personnel action with a status “In Progress”. If an employee does not receive a PFP increase, a PA is still produced to note the fact the EE was not over looked in the process.
Increases are limited to the “Compa ratio limit” defined in ISMX. If, however, the limit pushes the EE’s wage past the maximum for their range then their PA will also update the toggle “Out of Range” on the assignment record.
Wage Rounding – Rounding is done by two methods:
Report Parameters | |
---|---|
User | Mandatory, LOV available List created by USPF for used for batching EE are associated to this user. |
Review Type | Mandatory, LOV available This field supplies the Review type (one allowed) that will be considered for PFP. |
Review Status | Mandatory, LOV available This field ensures that reviews have the same status (one allowed). Suggested status is “Approved” |
Reviews Effective As of | Mandatory, Date, LOV available This field ensures that reviews must have occurred since this date. |
EE’s Hired As Of | Mandatory, Date, LOV available All employees must be have an Original Hire Date on their employment record as of this date in order to qualify for PFP regardless if they have a review completed. |
Relative Date | |
Proration | Optional, LOV available This field allows for selection of logic, which prorates (months since the last increase to the USPF PA effective date) the suggested % increase based on the last time a wage increase was given through PA’s. ’Latest Effective’ is custom and currently the only type supported. If “None” is selected the suggested % is direct from ISMX. |
Bring EE to Minimum | Optional, ON/OFF Toggle This field ensures that before an EE is processed for PFP that their wage is at least the minimum for the range they are associated. This can be used if a mass salary range adjustment has been given. The employee will be brought to the minimum wage for the range and then given the PFP increase if set to “Yes”. If “No” the EE will be given the PFP increase on their current salary. |
PA’s To Include in Proration | Optional, LOV available This field supplies PA’s that would qualify for the selected proration process. (Proration Type parameter.) |
USPF PA’s Effective | Mandatory, Date, LOV available This field supplies the date in which all PA’s generated will be effective. |
Break By | Optional, LOV available You may specify that the report pages break by department, units, etc. |
Trial | Optional, LOV available You may choose to run the report in a trial mode to see results |
Exception Level | Optional, LOV available, <0-Exceptions Only> This field supplies the level of messaging for the USPF that is required. Currently three levels are supported. |
User Comments | Optional, Text This field holds the user-supplied comment which will appear in the header of all pages of the report. |
Report List Filters | |
---|---|
Person Code | Optional, LOV available This field limits the report to employees with the “Person Codes” selected. |
Entity | Optional, LOV available This field limits the report to employees within the entity(s) selected. |
Location | Optional, LOV available This field limits the report to employees within the location(s) selected. |
Auth. Area | Optional, LOV available This field limits the report to employees within the authorization area(s) selected. |
Department | Optional, LOV available This field limits the report to employees within the department(s) selected. |
Org Level | Optional, LOV available This field limits the report to employees within the organization level(s) selected. |
Unit | Optional, LOV available This field limits the report to employees within the unit(s) selected. |
Group | Optional, LOV available This field limits the report to employees within the group(s) selected. |
Status Type | Optional, LOV available This field limits the report to employees within the employee status(es) selected. |
Screen captures are meant to be indicative of the concept being presented and may not reflect the current screen design.
If you have any comments or questions please email the Wiki Editor
All content © High Line Corporation