This page (revision-12) 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
12 26-Nov-2021 10:22 1 KB mmcfarland to previous
11 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
10 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
9 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
8 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
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 963 bytes ihowie to previous | to last
3 26-Nov-2021 10:22 961 bytes ihowie to previous | to last
2 26-Nov-2021 10:22 955 bytes ihowie to previous | to last
1 26-Nov-2021 10:22 845 bytes ihowie to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 changed 2 lines
!!!TR_OCC_IN_EARLY - Occurrence In Early
!!Time Rule Overview
!!!TR_OCC_IN_EARLY
At line 4 changed one line
This rule identifies if an employee clocks IN prior to the scheduled shift time. This time rule creates a new time code on the employee’s time sheet for the occurrence of an early clock IN.
The OCC_IN_EARLY time rule identifies if an employee clocks in prior to the scheduled shift time.
At line 6 changed one line
This time rule is applied to the raw clock punch prior to any rounding, to determine if there is an occurrence or not.
This time rule creates a new time code on the employee’s time sheet for the occurrence of an early clock in.
At line 8 changed 2 lines
!!Additional Info
*__This time rule requires the IMST Preference for GEN IN OUT OCC set to Y__
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 11 changed one line
*__This time rule DOES NOT SUPPORT a Floating Lunch definition on [ITSS]__
Set Up
• This time rule requires the IMST Preference GEN IN OUT OCC set to Y
• Frequency is predefined as Never
• The time rule should be set up in IDWR as shown below
At line 13 removed 4 lines
*Frequency is predefined as Never
At line 18 changed one line
*The time rule should be set up in IDWR as shown below
||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 20 changed 8 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
[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_EARLY]
[{InsertPage page='Internal.TR_OCC_IN_EARLY' 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.