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

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 Kevin Higgs to previous
7 26-Nov-2021 10:22 1 KB Kevin Higgs 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 987 bytes ihowie to previous | to last
2 26-Nov-2021 10:22 985 bytes ihowie to previous | to last
1 26-Nov-2021 10:22 984 bytes ihowie to last

Page References

Incoming links Outgoing links
TR_OCC_IN_LATE_ON_T
TR_OCC_IN_LATE_ON_T

Version management

Difference between version and

At line 4 changed one line
The OCC_IN_LATE_ON_T time rule identifies if an employee clocks in on or after the start of the scheduled shift time.
This time rule identifies if an employee clocks IN on or after the start of the scheduled shift time.
At line 6 changed one line
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 creates a new time code on the employee’s time sheet for the occurrence of a late clock IN.
At line 8 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 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 requires the IMST Preference GEN IN OUT OCC set to Y
* This time rule requires the IMST Preference GEN IN OUT OCC set to Y
At line 13 changed one line
• Frequency predefined as Never
* Frequency predefined as Never
At line 15 changed one line
• The time rule should be set up in IDWR as shown below
* The time rule should be set up in IDWR as shown below
At line 17 changed one line
• __This time rule DOES NOT SUPPORT a Floating Lunch definition on [ITSS]__
* __This time rule DOES NOT SUPPORT a Floating Lunch definition on [ITSS]__
At line 20 changed 3 lines
||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
[#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.
||[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|1820| |No|No|No|No|Allowed [1]|No|No|No|No|Add
At line 23 added one line
[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 statistics.
At line 25 added 7 lines
----
![Notes|Edit:Internal.TR_MAX_BREAK_TIME]
[{InsertPage page='Internal.TR_MAX_BREAK_TIME' default='Click to create a new notes page'}]
This page (revision-8) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop