This page (revision-35) was last changed on 30-Mar-2022 16:14 by Karen Parrott

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

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
35 30-Mar-2022 16:14 6 KB Karen Parrott to previous
34 30-Mar-2022 15:49 6 KB Karen Parrott to previous | to last
33 26-Nov-2021 10:22 6 KB kparrott to previous | to last
32 26-Nov-2021 10:22 6 KB JMyers to previous | to last
31 26-Nov-2021 10:22 6 KB JMyers to previous | to last
30 26-Nov-2021 10:22 6 KB JMyers to previous | to last
29 26-Nov-2021 10:22 6 KB JMyers to previous | to last
28 26-Nov-2021 10:22 6 KB JMyers to previous | to last
27 26-Nov-2021 10:22 6 KB JMyers to previous | to last
26 26-Nov-2021 10:22 11 KB JMyers to previous | to last
25 26-Nov-2021 10:22 11 KB JMyers to previous | to last
24 26-Nov-2021 10:22 11 KB JMyers to previous | to last
23 26-Nov-2021 10:22 14 KB JMyers to previous | to last
22 26-Nov-2021 10:22 15 KB JMyers to previous | to last
21 26-Nov-2021 10:22 15 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
ISRS
ISRS

Version management

Difference between version and

At line 5 added 9 lines
!!!WAGE STEP RULES
[{$applicationname}] uses Wage Step Rules to define the criteria needed to move an employee through the steps within a scale, and to trigger this event, an increase (or decrease) in the employees’ wages. These rules are created for each applicable unit, and are assigned to theemployee through their group. Wage Step Rules are created and maintained through the Define Wage Step Rules (ISRS) form.
\\
\\
Wage Step Rules data is maintained on the [P2K_SA_WAGE_STEP_RULES] and
[P2K_SA_WAGE_STEP_LOGICS] tables.
\\
----
At line 12 removed 3 lines
Wage Step Rules data is maintained on the [P2K_SA_WAGE_STEP_RULES] and
[P2K_SA_WAGE_STEP_LOGICS] tables.
At line 59 added 23 lines
!!Wage Stepping Logic
;[Up to Seq|STEP_SEQUENCE]:The stepping logic is to be applied until the employee reaches this sequence on their scale/step. Step sequences are used rather than the descriptive step codes. This is up to and including the sequence indicated. Step_Sequence is a 4-character numeric mandatory field that you must manually entered.
;[Next Scale|SCALE_CODE]/[Step|STEP_CODE]:Once the employee meets the requirements that are defined in the “Base” and “Period” areas of this form, this field identifies next scale/step that the employee is to go, if they are NOT to automatically go to the next sequential step. For example, an employee completes Step1 and because of circumstances, they should continue on to Step 4, not Step 2. Scale_Code and Step_Code are combined into an alphanumeric mandatory code that is created in the ISWS form
;[Stepping Interval|STEPPING_INTERVAL]:This field displays the amount of time that will be added to the Step Base date to calculate the new effective date of the assignment record – the date when the employee will move up to the next sequence step in the scale. Stepping_Interval is a required, 12-character numeric field that must be manually updated.
;[Stepping Basis|PERIOD_BASIS]:This field defines the time period (hour, day, week, year) in which the stepping interval value is expressed. Period_Basis is a required, fixed lexicon ([X_PERIOD_BASIS]), which you may fill with a value from the LOV.
;[Pre Eligible Threshold (For experience tracking only)|PRE_ELIGIBLE_THRESHOLD]:A Pre Eligible Threshold can be used to further qualify employees for wage stepping. The“pre-eligible” time is checked when a calendar end date (in the calendar named in the heading) falls within the period being processed.\\__If ‘pre-eligible threshold’ is not indicated the calendar is ignored.\\__If ‘pre-eligible threshold’ is indicated the calendar must be supplied.\\Pre_Eligible_Threshold is an optional, 12-character numeric field that may be manually updated.
;[Step Method|STEP_METHOD]:This field indicates the method to be used for stepping. Step_Method is a required, fixed lexicon ([X_STEP_METHOD]) that may be chosen from the LOV.
;[Step Base Date|STEP_BASE_DATE]:This field displays the base date, from which the next date for stepping will be calculated. This field is used when it is necessary to step based on a specific date. Use “Not Specified” if the wage step rule is not date dependant. Step_Base_Date is an optional, fixed lexicon ([X_STEP_BASE_DATE]) that may be chosen from the LOV.
;[Step Date Rule|DATE_ADJUSTMENT_RULE]:When the new step date is calculated using the step method, period, and basis above, the date that is calculated may have to be adjusted to the 1st of the month or the start of the pay period. Date_Adjustment_Rule is a required, fixed lexicon ([X_DATE_ADJUSTMENT_RULE]) which you may fill with a selection from the values provided.
;[User Calc|USER_CALC]:If a date adjustment to be used is not included in the standard step date rules above, a [{$applicationname}] UserCalc function may be provided. UserCalc is an optional 16-character code which you may fill with a selection from the LOV.
\\
----
!!Experience Rules
__When setting up Wage Step Rules in ISRS for anniversary stepping, you must not enter anything in the experience rules section of the screen. If you do so, the USAS - wage step anniversary process assumes that the rule is coded for experience purposes only and will ignore it for anniversary step processing.__
\\
\\
;[Experience Type|EXPERIENCE_TYPE]:Wage stepping experience may be categorized by entity, unit, group, department, job or position. Experience_Type is an optional, fixed lexicon ([X_EXPERIENCE_TYPE]) that you may fill with a selection from the LOV.
;[Eligible Element|ELEMENT_CODE]:If experience stepping is being done, then this element contains the ‘Hours’ pay components that are counted towards eligible experience. Element_Code is an optional 16-character code that you may fill with a selection from the LOV.
;[Work Element|ELEMENT_CODE]:This field allows you to track the pay components that identify actual time worked. Element_Code is an optional 16-character code that you may fill with a selection from the LOV.
;[Absent Element|ELEMENT_CODE]:You may wish to track the pay components that identify absence time. Element_Code is an optional 16-character code that you may fill with a selection from the LOV.
;[Allow Wage Stepping|ALLOW_WAGE_STEPPING]:If the Allow Wage Stepping toggle is ON, an employee will be stepped based on the wage stepping rules defined. If the Allow Wage Stepping toggle is OFF, only experience will be tracked and no stepping will be done. Allow_Wage_Stepping is an optional toggle field.
;[No Carry Forward|NO_CARRY_FORWARD]:If the No Carry Forward toggle is ON, an employee who is being stepped based on this experience type will NOT carry any ‘left-over’ hours forward to the next step. If the No Carry Forward toggle is OFF, an employee who is being stepped based on this experience type will carry forward any hours ‘left-over’ to the next step. No_Carry_Forward is an optional toggle field.
This page (revision-35) was last changed on 30-Mar-2022 16:14 by Karen ParrottTop