This page (revision-5) was last changed on 26-Nov-2021 10:22 by Lilia Urtan

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
5 26-Nov-2021 10:22 3 KB Lilia Urtan to previous
4 26-Nov-2021 10:22 3 KB Lilia Urtan to previous | to last
3 26-Nov-2021 10:22 3 KB JMyers to previous | to last
2 26-Nov-2021 10:22 3 KB JMyers to previous | to last
1 26-Nov-2021 10:22 3 KB JMyers to last

Page References

Incoming links Outgoing links
UFSTEP
UFSTEP

Version management

Difference between version and

At line 3 changed one line
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.
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.
At line 9 changed 2 lines
*It is possible for a budget seat to be stepped more than once during the budget timeframe.
*The derived step date must fall within the budget timeframe.
*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.
At line 17 added one line
*There must be a value entered in the Wage Progress Date field on IEAS for the budget seat. Value cannot be NULL.
At line 21 changed 34 lines
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.
‘Apply Wage Stepping for Budget Seats’ Field Descriptions
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
*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
----
![Notes|Edit:Internal.UFSTEP]
[{InsertPage page='Internal.UFSTEP' default='Click to create a new notes page'}]
This page (revision-5) was last changed on 26-Nov-2021 10:22 by Lilia UrtanTop