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

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

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
6 26-Nov-2021 10:22 1 KB mmcfarland to previous
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 1 KB mmcfarland to previous | to last
2 26-Nov-2021 10:22 1 KB mmcfarland to previous | to last
1 26-Nov-2021 10:22 983 bytes tchau to last

Page References

Incoming links Outgoing links
TR_OCC_OUT_EARLY
TR_OCC_OUT_EARLY

Version management

Difference between version and

At line 1 changed one line
!!!TR_OCC_OUT_EARLY - Occurrence Out Early
!!!TR_OCC_OUT_EARLY
At line 4 changed one line
This time rule identifies if an employee clocks OUT before the end of the scheduled shift time. This time rule creates a new time code on the employee'€™s time sheet for the occurrence of a early clock OUT. This time rule is applied to the raw clock punch prior to any rounding, to determine if there is an occurrence or not.
The OCC_OUT_EARLY time rule identifies if an employee clocks out before the end of the scheduled shift time.
At line 6 changed 2 lines
!!Requirements / Features
*Time Rule Type Code: OCC OUT EARLY
This time rule creates a new time code on the employee’s time sheet for the occurrence of a early clock out.
At line 8 added 2 lines
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 changed 2 lines
*__This time rule requires the IMST Preference for GEN IN OUT OCC set to Y__
*__This time rule DOES NOT SUPPORT a Floating Lunch definition on [ITSS]__
• This time rule requires the IMST Preference GEN IN OUT OCC set to Y
At line 13 added one line
• Frequency predefined as Never
At line 14 changed one line
* Frequency predefined as Never
• The time rule should be set up in IDWR as shown below
At line 17 added 2 lines
• __This time rule DOES NOT SUPPORT a Floating Lunch definition on [ITSS]__
At line 17 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 19 changed 5 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|1800| |No|No|No|No|Allowed [1]|No|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.
[#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.
This page (revision-6) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop