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 3 changed one line
!!!Wage Step Rules
!!!WAGE STEP RULES
At line 7 changed 5 lines
Wage Step Rules data is maintained on the [P2K_SA_WAGE_STEP_RULES] and
[P2K_SA_WAGE_STEP_LOGICS] tables.
\\
----
!!Stepping Methods
Wage Step Rules data is maintained on the [P2K_SA_WAGE_STEP_RULES],[P2K_SA_WAGE_STEP_LOGICS] and [P2K_SA_EXPERIENCE_RULES] tables.
\\ \\
;[Wage Step Rule|WAGE_STEP_RULE_CODE]:The name of the stepping rule is entered here. For one unit, there may be one or many step rules. These rules are then assigned to different groups within the unit. The employee, through the group chosen for them, is assigned a step rule. This step rule applies to their assignment scale/step, which defaults from job/position. The Wage Step rule may also be attached to a specific wage scale, in which case it will override the rule on the group.
At line 13 changed one line
;[Anniversary Date|ANNIVERSARY_DATE]:With this method, stepping occurs each year on the anniversary of the Step Base date.
;[Unit|UNIT_CODE]:Wage steps, and wage step rules, must be associated with a unit. You must either enter the unit/union name or use the LOV in this field to identify the associated unit.
At line 15 changed one line
;[Absolute Interval|ABSOLUTE_INTERVAL]:In this method, stepping occurs after the elapsed time specified in the Stepping Interval and Stepping Basis fields has passed since the Step Base date.
;[Entity|ENTITY_CODE]:Step rules must be associated with an entity. You may either enter the company name or use the LOV in this field to identify the associated entity.
At line 17 changed one line
;[Relative Interval|RELATIVE_INTERVAL]:Stepping occurs after the elapsed time specified in the Stepping Interval and Stepping Basis fields has passed since the date last stepped. The “date last stepped” is the effective date of the first date sensitive record that contains the current step.
;[Minimum Step Days|MINIMUM_STEP_DAYS]:This field shows the minimum number of days that must pass between movements from one step to another. This situation may apply when an employee reaches the qualifications for stepping very quickly (i.e. if a certification is received only a few days after hire). The minimum step days would prevent this employee from moving up the scale more quickly than allowed. In addition, stepping may be done on a particular day of the year (Jan. 1, or Sept. 1), in which case it may be necessary to stop recently hired employees from getting a step increase too early. A blank entry here is considered “0 days”.
At line 19 changed one line
;[Eligible Experience|ELIGIBLE_EXPERIENCE]:Stepping occurs when the experience eligible hours reaches the stepping interval. No Step Base date is required. The date that stepping should occur is predicted based on the pay period hours and varies depending on the FTE.__This is only applicable for weekly and biweekly payrolls__
;[Change Reason|CHANGE_CODE]:This field displays the reason for a change to a wage step rule.
At line 21 changed one line
;[Wage Step Rule|WAGE_END_RULE_CODE]:The name of the stepping rule is entered here. For one unit, there may be one or many step rules. These rules are then assigned to different groups within the unit. The employee, through the group chosen for them, is assigned a step rule. This step rule applies to their assignment scale/step, which defaults from job/position. The Wage Step rule may also be attached to a specific wage scale, in which case it will override the rule on the group. Wage_Step_Rule is a 16-character alphanumeric mandatory field that you must manually enter.
;[Calendar (For Experience Tracking only)|CALENDAR_CODE]:The calendar to be used to trigger “pre-eligible” threshold checking in wage stepping may be supplied in this field. (Calendar dates must coincide with pay period end dates in order to ensure that all transactions are accounted for.)
At line 23 changed one line
;[Unit|UNIT_CODE]:Wage steps, and wage step rules, must be associated with a unit. You must either enter the unit/union name or use the LOV in this field to identify the associated unit. Unit is a 16-character alphanumeric mandatory field that you may select from the list of values created in the Define Units (IDUN) form.
;[Retro PC Code (For Experience Tracking only)|PPC_ID]:If the evaluation of the wage stepping is done ‘after-the-fact’, then a [pay component|PAY COMPONENTS] must be specified to hold the retroactive amount calculated. This information is only needed when a calendar is specified.
At line 25 changed one line
;[Entity|ENTITY_CODE]:Step rules must be associated with an entity. You may either enter the company name or use the LOV in this field to identify the associated entity. Entity is defaulted in once you select the Unit.
;[Abbrev.|PC_ABBREVIATION]:This field displays the abbreviated description of the Retro PC Code selected above. The data for this field will default in once the Retro PC Code has been selected.
At line 27 changed one line
;[Minimum Step Days|MINIMUM_STEP_DAYS]:This field shows the minimum number of days that must pass between movements from one step to another. This situation may apply when an employee reaches the qualifications for stepping very quickly (i.e. if a certification is received only a few days after hire). The minimum step days would prevent this employee from moving up the scale more quickly than allowed. In addition, stepping may be done on a particular day of the year (Jan. 1, or Sept. 1), in which case it may be necessary to stop recently hired employees from getting a step increase too early. Minimum_Step_Days is an optional 4-character numeric amount that may be manually entered. A blank entry here is considered “0 days”.
;[PA Status|PA_STATUS]:Wage stepping through Experience [USEP] or Anniversary [USAS] will create a Personnel Action form. This field indicates the status of the Personnel Action (PA) created.\\See Track Experience and Step Rate [USEP], Step Wages Based on Anniversary [USAS], or Apply General Wage Changes [USSC] for details on setting up PA types.\\If PA Status is not entered, then the USEP will create any new PA with status 'Pending'.
At line 29 changed one line
;[Change Reason|CHANGE_CODE]:This field displays the reason for a change to a wage step rule. Change_Reason is an optional, semi-fixed lexicon ([X_CHNAGE_REASON]) that may be chosen from the LOV.
;[Description|DESCRIPTION]:This field displays the description of the Wage Step rule being created.
At line 31 changed one line
;[Calendar (For Experience Tracking only)|CALENDAR_CODE]:The calendar to be used to trigger “pre-eligible” threshold checking in wage stepping may be supplied in this field. (Calendar dates must coincide with pay period end dates in order to ensure that all transactions are accounted for.) Calendar_Code is an optional 4-character numeric amount that may be manually entered.
;[Up to Seq|UP_TO_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.
At line 33 changed one line
;[Retro PC Code (For Experience Tracking only)|PAY_COMPONENT]:If the evaluation of the wage stepping is done ‘after-the-fact’, then a pay component must be specified to hold the retroactive amount calculated. This information is only needed when a calendar is specified. Pay_Component is an optional 4-character numeric code that may be entered by the user or retrieved from the LOV.
;[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.
At line 35 changed one line
;[Abbrev.|ABBREVIATION]:This field displays the abbreviated description of the Retro PC Code selected above. The data for this field will default in once the Retro PC Code has been selected.
;[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.
At line 37 changed 9 lines
;[PA Status|PA_STATUS]:Wage stepping through Experience [USEP] or Anniversary [USAS] will create a Personnel Action form. This field indicates the status of the Personnel Action (PA) created. PA_Status is a required, fixed lexicon (X_PA_STATUS) that may be chosen from the LOV.
\\
__See Track Experience and Step Rate [USEP], Step Wages Based on Anniversary[USAS], or Apply General Wage Changes [USSC] for details on setting up PA types.__
\\
;[Description|DESCRIPTION]:This field displays the description of the Wage Step rule being created. Description is an optional 50-character alphanumeric field that may be manually entered.
\\
----
!!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.
;[Stepping Basis|PERIOD_BASIS]:This field defines the time period (hour, day, week, year) in which the stepping interval value is expressed.
At line 47 changed one line
;[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
;[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.
At line 49 changed one line
;[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.
;[Step Method|STEP_METHOD]:This field indicates the method to be used for stepping. This can be used in conjunction with the Step Base Date
At line 51 changed one line
;[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.
;[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 dependent.
At line 53 changed one line
;[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 Date Rule|STEP_DATE_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.
At line 55 changed one line
;[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.
%%information 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.%%
At line 57 changed one line
;[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.
;[Experience Type|EXPERIENCE_TYPE]:Wage stepping experience may be categorized by entity, unit, group, department, job or position.
At line 59 changed one line
;[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.
;[Eligible Element|PEL_ID_ELIGIBLE]:If experience stepping is being done, then this element contains the ‘Hours’ pay components that are counted towards eligible experience.
At line 61 changed 4 lines
;[User Calc|USER_CALC_CODE]: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
;[Work Element|PEL_ID_WORKED]:This field allows you to track the [pay components|PAY COMPONENTS] that identify actual time worked.
At line 66 changed 4 lines
__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.
;[Absent Element|PEL_ID_ABSENT]:You may wish to track the pay components that identify absence time.
At line 71 changed one line
;[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.
;[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.
At line 73 changed one line
;[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.
;[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.
At line 75 removed one line
;[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.
At line 77 removed one line
;[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.
At line 79 removed 2 lines
;[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.
\\
At line 82 changed 36 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.
![Notes|Edit:Internal.ISRS]
[{InsertPage page='Internal.ISRS' default='Click to create a new notes page'}]
This page (revision-35) was last changed on 30-Mar-2022 16:14 by Karen ParrottTop