This page (revision-8) was last changed on 26-Nov-2021 10:22 by mmcfarland

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

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
8 26-Nov-2021 10:22 1 KB mmcfarland to previous
7 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
6 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
5 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
4 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
3 26-Nov-2021 10:22 960 bytes mmcfarland to previous | to last
2 26-Nov-2021 10:22 967 bytes ihowie to previous | to last
1 26-Nov-2021 10:22 963 bytes ihowie to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed one line
!!!TR_OCC_IN_LATE - Occurrence In Late
!!!TR_OCC_IN_LATE
At line 4 changed one line
This ime rule identifies if an employee clocks IN after the start of the scheduled shift time. This time rule creates a new time code on the employee’s time sheet for the occurrence of a late clock IN. This time rule is applied to the raw clock punch prior to any rounding, to determine if there is an occurrence or not.
This ime rule identifies if an employee clocks IN after the start of the scheduled shift time.
At line 6 changed 2 lines
!!Additional Info
*__This time rule requires the IMST Preference for GEN IN OUT OCC set to Y__
This time rule creates a new time code on the employee’s time sheet for the occurrence of a late clock IN.
At line 9 changed one line
*__This time rule DOES NOT SUPPORT a Floating Lunch definition on [ITSS]__
This time rule is applied to the raw clock punch prior to any rounding, to determine if there is an occurrence or not.
At line 10 added 3 lines
!!Additional Info
*This time rule requires the IMST Preference GEN IN OUT OCC to be set to Y
At line 15 added one line
*__This time rule DOES NOT SUPPORT a Floating Lunch definition on [ITSS]__
At line 14 removed one line
At line 19 changed 2 lines
||[Cycle|CYCLE_NUMBER]||[Frequency|FREQUENCY]||[Seq|SEQUENCE]||[Time Rule Type|TIME_RULE_TYPE_TEXT]||[Band|QUALIFYING_BAND]||[From|FROM_CLOCK_TIME]||[To|TO_CLOCK_TIME]||[Value|VALUE]||[Day|DAY_OF_WEEK]||[Time Code|TIME_CODE_VALUE]||[Premium|PREMIUM_CODE]||[Target Time Code Set|TARGET_TIME_CODE_SET]|| [Apply Time Code Set|APPLY_TIME_CODE_SET]||[Action|TIME_RULE_ACTION]
| |Never|1790| |No|No|No|No|No|Allowed [1]|No|No|No|Add
||Band||From||To||Value||Day Of Week||Time Code||Premium||Action||Targeted Time Code Sets||Apply Time Code Sets
|#|No|No|No|Allowed[1]|No|Add|No|No
At line 22 changed 6 lines
[1] A Time Code is allowed in the definition and can map to a pay component for future action in a payroll UserCalc, for items such as statistics.
![Notes|Edit:Internal.TR_OCC_IN_LATE]
[{InsertPage page='Internal.TR_OCC_IN_LATE' default='Click to create a new notes page'}]
[#1] Time code is allowed in the definition and can map to a pay component for future action in a payroll UserCalc, for items such as stats.