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

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

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
9 26-Nov-2021 10:22 2 KB mmcfarland to previous
8 26-Nov-2021 10:22 2 KB mmcfarland to previous | to last
7 26-Nov-2021 10:22 2 KB mmcfarland to previous | to last
6 26-Nov-2021 10:22 2 KB mmcfarland to previous | to last
5 26-Nov-2021 10:22 2 KB mmcfarland to previous | to last
4 26-Nov-2021 10:22 2 KB mmcfarland to previous | to last
3 26-Nov-2021 10:22 2 KB mmcfarland to previous | to last
2 26-Nov-2021 10:22 1 KB jmyers to previous | to last
1 26-Nov-2021 10:22 1 KB JEscott to last

Page References

Incoming links Outgoing links
TR_OFFSET_BFR_GAP
TR_OFFSET_BFR_GAP

Version management

Difference between version and

At line 4 added one line
This time rule will ensure employees are not entitled to any compensation for periods of overtime, if less than the number of minutes per day, defined in the Band.
At line 5 changed one line
A negative entry for the value of the transaction entered is created in the Time Code Sets. This rule will create offset records if the time is less than the value defined on the time rule band. Any gap in time will reset the calculation. This rule will solve the need where employees are not entitled to any compensation for periods of overtime of less than X min per day. This rule works in conjunction with TOP UP AFT GAP.
This rule will create offset records if the time is less then the value defined in the Band. Any gap in time will reset the calculation.
At line 7 changed one line
%%information Note that with this type of off set transactions, the 'From and 'To' times will match the entered times. The limit on the number of minutes that a transaction was produced up to is provided in the Band field. This time rule works with the time prior to the time used in the Time Rule TOP UP AFT GAP.%%
This rule works in conjunction with TOP_UP_AFT_GAP.
At line 9 changed one line
%%information In case the time codes that are offset by this rule, are also used by other time rules, it is recommended that this rule be the last one to fire (change the order using sequence and/or cycle) so the offset records will not have any impact on other time rule calculations.%%
A negative entry for the value of the transaction entered is created in the Time Code Sets.
At line 11 changed one line
The Apply Time Code Set needs to be defined only when not all of the records that contribute to the calculation should be offset.
This rule will create offset records if the time is less than the value defined on the time rule Band. Any gap in time will reset the calculation. This rule will solve the need where employees are not entitled to any compensation for periods of overtime of less than X min per day. This rule works in conjunction with TOP UP AFT GAP.
%%information Note: With this type of offset transactions, the From and To times will match the entered times. The limit on the number of minutes that a transaction was produced up to is defined in the Band. This time rule works with the time prior to the time used in the Time Rule TOP_UP_AFT_GAP.%%
%%information In case the time codes that are offset by this rule are also used by other time rules, it is recommended that this rule be the last one to fire (change the order using sequence and/or cycle) so the offset records will not have any impact on other time rule calculations.%%
The Apply Time Code Set needs to be defined _only_ when not all of the records that contribute to the calculation should be offset.
At line 13 changed one line
*e.g. Travel time should not be offset, so "target" will contain Travel and OT time codes and "apply" will contain only OT time codes.
*Example: Travel time should not be offset, so Target Time Code Set should contain Travel and OT time codes. The Apply Time Code Set should contain only the OT time codes.
At line 16 changed 2 lines
*[Frequency|FREQUENCY]
**predefined as Daily
*[Frequency|FREQUENCY] predefined as Daily
At line 20 changed 3 lines
||[Band|QUALIFYING_BAND]||[From|FROM_CLOCK_TIME]||[To|TO_CLOCK_TIME] ||[Value|TIME_RULE_VALUE]||[Day Of Week |DAY_OF_WEEK]||[Time Code|TIME_CODE]||[Premium |PREMIUM_CODE]||[Action|TIME_RULE_ACTION]||Target Time Code Set||Apply Time Code Set
|Disqualify limit (minutes)|No|No| |Yes|No|No|Add|Allowed|Allowed
||[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]
| |Daily|1510| |Disqualify limit, in minutes|No|No| |Allowed|No|No|Allowed|Allowed|Add
This page (revision-9) was last changed on 26-Nov-2021 10:22 by mmcfarlandTop