!!!Apply Wage Stepping for Budget Seats

If automatic wage stepping is required, the Apply Wage Stepping (UFSTEP) form should be run immediately after the Create Initial Budget UFBDGT form before any assumptions are processed.

The Apply Wage Stepping (UFSTEP) process will NOT work on the “base” scenario.

!Wage Step Logic
*The UFSTEP process performs wage stepping logic for each budget seat that qualifies for wage stepping.
*It is possible for a budget seat to be stepped more than once during the budget time frame.
*The derived step date must fall within the budget time frame.
*The budget seat must NOT be terminated as of the step date.
*The budget seat must be in the same unit/group as of the step date.
*The budget seat must be on the same scale/step as of the step date.
*Budget seats must have a Scale/Step and the Scale Override toggle must be “off”.\\If the Scale Override toggle is “on”, it means that the budget seat is “red lined” or “red circled” and no automatic stepping should occur.  An exception message will be issued.
*There must be a wage step rule defined on the associated scale or group.\\A wage step rule on the scale overrides a wage step rule on the group.
*If the budget seat is already at the top of the scale no wage stepping logic is done.
*If the budget seat is for a vacant position, one of the following dates will be substituted for the step base date:
|Position Approved Date|If supplied and later than the budget start date, otherwise
|Position Effective Date|If position is “budgeted” after budget start date, otherwise
|Budget Start Date|If position is “budgeted” from the beginning of the Budget
*When budget seats are stepped, a new date sensitive record is cut and the wage rate and basis is re-derived based on the new step.
*Internal assumption records and assumption logs are created for each record stepped to provide an audit trail of the changes that have been made to the budget seats.
*An exception message will be issued for each budget seat that is stepped and it should state the budget seat code, the step date, the scale code and the old and new step.
*Experience records are not physically touched by UFSTEP.

||Report Parameters||
|Budget|Mandatory, LOV available\\The user-defined name of the budget to be stepped
|From| Date, Mandatory, LOV available\\The start date of the stepping period
|To|Date, Mandatory, LOV available\\The end date of the stepping period
|Exception Level|Mandatory, LOV available\\Do you need to see ‘trace’ information? \\Exceptions Only, User Trace, Legislation, UserCalc Trace, Program Trace or Utility Trace?
|Trial|	Mandatory, LOV available, <NO>\\Run in update mode (No) or in Trial (Yes)

||Report Filters||
|Budget Area|Mandatory, Multiple selections, LOV available\\Name of the budget area(s) to be stepped
|Scenario|Mandatory, Multiple selections, LOV available\\Name of the scenario(s) to be stepped
|Budget Seat|Mandatory, Multiple selections, LOV available, <ALL>\\Specific Budgets Seat(s) may be stepped\\Limits the budget to the entity indicated
|Unit|Mandatory, Multiple selections, LOV available,<ALL>\\Limits stepping to the unit indicated
|Group|Mandatory, Multiple selections, LOV available, <ALL>\\Limits stepping to the Group indicated
|Department|Mandatory, Multiple selections, LOV available, <ALL>\\Limits stepping to the Department indicated
|Auth Area|Mandatory, Multiple selections, LOV available, <ALL>\\Limits stepping to the Auth Area indicated
|Location|Mandatory, Multiple selections, LOV available, <ALL>\\Limits stepping to the Location indicated