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

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

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
10 26-Nov-2021 10:22 3 KB jmyers to previous WORK_RULE_CODE ==> WORK_RULE (Field)
9 26-Nov-2021 10:22 3 KB jmyers to previous | to last
8 26-Nov-2021 10:22 3 KB JMyers to previous | to last
7 26-Nov-2021 10:22 11 KB JMyers to previous | to last
6 26-Nov-2021 10:22 11 KB JMyers to previous | to last
5 26-Nov-2021 10:22 10 KB JMyers to previous | to last
4 26-Nov-2021 10:22 10 KB JMyers to previous | to last
3 26-Nov-2021 10:22 10 KB JMyers to previous | to last
2 26-Nov-2021 10:22 1 KB JMyers to previous | to last
1 26-Nov-2021 10:22 2 KB JMyers to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 9 changed 2 lines
;[Entity|ENTITY_CODE]:This field displays the entity to which the work rule belongs.
;[Work Rule|WORK_RULE (Field)]:Work rules are used to determine standard processing information required in creating pay headers and transactions for a person.
;[Entity|ENTITY_CODE]:
;[Work Rule|WORK_RULE_CODE]:
;[Standing|STANDING]:
;[Effeci|EFFECTIVE]:
;[|EXPIRY]:
;[|CHANGE_CODE]:
;[Work Calendar|WORK_CALENDAR_CODE]:
;[|HOLIDAY_CALENDAR_CODE]:
;[|DESCRIPTION]:
;[First Day of Week|FIRST_DAY_OF_WEEK]:
;[Pieces Per Day|PIECES_PER_DAY]:
;[Std Hours Per Day|STD_HOURS_PER_DAY]:
;[Std Hours Per Week|STD_HOURS_PER_WEEK]:
;[Std Hours Per Pay|STD_HOURS_PER_PAY]:
;[Weeks Per Year|WEEKS_PER_YEAR]:
;[|MONTHS_PER_YEAR]:
;[|PAYS_PER_CONTRACT]:
;[|FLSA_METHOD]:
;[|FLOAT_DAYS_ALLOWED]:
;[|WORK_IS_SCHEDULED]:
;[|MUST_BE_ACKNOWLEDGED]:
;[|TIME_ROUNDING_RULE]:
;[|TIME_ROUNDING_FACTOR]:
;[|PAY_STARTING_DATE]:
;[|GROUP_SOURCE]:
;[|WORK_IN_RESTRICTION_RULE]:
;[|STATUS_CODE]:
;[|TIME_CODE_REGULAR]:
;[|TIME_CODE_SALARY]:
;[|TIME_CODE_OVERTIME]:
;[|TIMESHEET_REQUIRED]:
;[|TIME_GENERATION_RULE]:
;[|GENERATE_HEADERS]:
;[|GENERATE_DETAILS]:
;[|GENERATE_HOLIDAYS]:
;[|ACCUMULATE_EXPERIENCE]:
;[|SIGN_OFF_TYPE]:
;[|TIME_GENERATION_DESTINATION]:
[{If var='loginstatus' contains 'authenticated'
----
![Discussion|Edit:Internal.IVDWR]
[{InsertPage page='Internal.IVDWR' default='Click to create a new discussion page'}]
}]
;[Work Rule|WORK_RULE_CODE]:Work rules are used to determine standard processing information required in creating pay headers and transactions for a person.
;[Entity|DEN_ID]:This field displays the entity to which the work rule belongs.
At line 12 changed 3 lines
;[Effective As Of|EFFECTIVE]/[Expires On|EXPIRY]:If the group is temporary, these fields will define the dates the work rule is effective.
;[Change Reason|CHANGE_CODE]:This field displays the ‘Change Reason’ code, which provides the rationale as to why information has been created or changed as of an effective date.
;[Work Calendar|WORK_CALENDAR_CODE]:This is the work calendar code to be used for this work rule, if applicable. If no calendar is supplied, the system will assume MON-FRI workweek.
%%information This function is [date sensitive|DATE SENSITIVE] and changes made in these areas below the [date navigator|DATE SENSITIVE NAVIGATOR] may be split with a new effective date.%%
\\
----
!!Details tab
;[Description|DESCRIPTION]:This field displays the description of the purpose and use of the work rule.
;[Work Calendar|DWC_ID]:This is the work calendar code to be used for this work rule, if applicable. If no calendar is supplied, the system will assume MON-FRI workweek.
;[Holiday Calendar|DHC_ID]:This is the holiday calendar code to be used for this work rule, if applicable.
;[Float Days Allowed|FLOAT_DAYS_ALLOWED]:This field will indicate that if a contract is specified, whether or not float days allowed.
;[Holidays Use Schedule Hrs|]:This toggle indicates whether the Work Schedule dictates the holiday hours. The "Holidays Use Schedule Hrs" toggle only applies to the hours generated for the Holiday time code. It does not extend to the Worked time code.
;[Work Is Scheduled|WORK_IS_SCHEDULED]:If this toggle is ON, then transactions generated through the Transaction Generator ([UPTG]) into Pay Transactions ([IPTR]) must always be equivalent to the time scheduled. This means if an 8.00 hour regular hour day is generated and 4.00 hours of vacation are entered for the same day then the regular time will be reduced to 4.00 hours as to not exceed the 8.00 scheduled hours.
;[Must Be Acknowledged|MUST_BE_ACKNOWLEDGED]:
;[Time Rounding Rule|TIME_ROUNDING_RULE]:This field indicates how the time an employee works should be rounded, if at all.
;[Time Rounding Factor|TIME_ROUNDING_FACTOR]:This field indicates to what decimal point the time should be rounded.
;[Pays Per Contract|PAYS_PER_CONTRACT]:This field identifies how many pays will be covered in this contract.
;[Start Date of Pay|PAY_STARTING_DATE]:This field identifies the day when the pay for this work rule will commence.
;[Work in Restriction Rule|WORK_IN_RESTRICTION_RULE]:This field is not currently functioning.
At line 93 added one line
At line 95 added one line
At line 97 added one line
At line 99 added one line
At line 101 added one line
At line 103 added one line
At line 22 changed 6 lines
;[Pays Per Contract|PAYS_PER_CONTRACT]:This field identifies how many pays will be covered in this contract.
;[Work Is Scheduled|WORK_IS_SCHEDULED]:This field indicates that the transactions generated through the Transaction Generator ([UPTG]) into Pay Transactions ([IPTR]) must always be equivalent to the time scheduled.
;[Must Be Acknowledged|MUST_BE_ACKNOWLEDGED]:
;[Time Rounding Rule|TIME_ROUNDING_RULE]:This field indicates how the time an employee works should be rounded, if at all.
;[Time Rounding Factor|TIME_ROUNDING_FACTOR]:This field indicates to what decimal point the time should be rounded.
;[Pay Starting Date|PAY_STARTING_DATE]:This field identifies the day when the pay for this work rule will commence.
;[FLSA Method|FLSA_METHOD]:For U.S. installations only: This field indicates the method by which [FLSA] must be calculated.
;[FLSA Hours|FLSA_HOURS]:
;[FLSA Calendar|]:
At line 29 changed 5 lines
;[Work In Restriction Rule|WORK_IN_RESTRICTION_RULE]:This field specifies if the work is to be done in a specific department.
;[Overtime Time Code|TIME_CODE_OVERTIME]:This field allows you to provide a unique code to identify the overtime being recorded.
;[Time Sheet Required|TIMESHEET_REQUIRED]:This field indicates if the employees are required to submit some kind of record (paper or electronic) of their work and/or attendance.
;[Time Generation Rule|TIME_GENERATION_RULE]:This field indicates the type of time transactions that must be generated for a person.
;[Generate Headers|GENERATE_HEADERS]:This field indicates if pay headers will be generated for all employees who have this work rule.
;[Track Work Punches|TRACK_WORK_PUNCHES]:
;[Track Meal Punches|TRACK_MEAL_PUNCHES]:
\\
At line 35 changed 2 lines
![Notes|Edit:Internal.IVDWR]
[{InsertPage page='Internal.IVDWR' default='Click to create a new notes page'}]
!!Status Rules tab
At line 122 added 114 lines
;[Status|STATUS_CODE]:This field shows the employment status code that may be indicated on an employee’s record. (ACTIVE should be defined as the default.)
;[Obtain Details From|TIME_GENERATION_DESTINATION]:This field is used by [UEGTS] and [UPTG] to determine where the time may be generated from. For example, the time details may be based on a shift calendar, hours calendar, event schedule, shift pattern or payroll calendar. This field is tied to the lexicon [X_TIME_GEN_DEST].
;[Generate Details|TIME_GENERATION_RULE]: This field indicates how the [UEGTS] and [UPTG] are to generate the time. For example, does the time get generated by day with time, by day without time, by week with time etc. This field is tied to the [X_TIME_GENERATION_RULE] lexicon.
;[Into Time Code|]:
;[Generate Salary As|]:
;[Create Headers|GENERATE_HEADERS]:If the Generate Headers toggle is ON, the pay headers will be generated for all employees who have this work rule. If this toggle is OFF, no pay headers will be generated.
;[Add Details|GENERATE_DETAILS]:If the Generate Details toggle is ON, then details will be attached to the header generated. If this toggle is OFF, no detail will be generated.
;[Add Holidays|]:
;[Timesheet Required|TIMESHEET_REQUIRED]:If the Timesheet Required toggle is ON, employees are required to submit some kind of record (paper or electronic) of their work and/or attendance. The payroll application exceptions will report employees whose information is unconfirmed, and manual data entry forms will prompt the user to confirm that they have received the employee's timesheet record. If the Timesheet Required toggle is OFF, the user will not see any confirmation checking, reporting, or prompting.
;[Accumulate Experience|ACCUMULATE_EXPERIENCE]:
\\ \\
;[Regular Time Code|TIME_CODE]:This field shows the time code that normal time is to be paid out under.
;[Salary $ Code|TIME_CODE]:This field shows the time code that salaried employees are to be paid out under.
;[Time Generation Rule|TIME_GENERATION_RULE]: This field indicates the type of time transactions that must be generated for a person.
;:Choosing one of the time transactions will insert separate transactions for each distribution code attached to the assignment that has a split rule of 'Pick List'.
;:All PTR records created will have ZERO time and this logic is invoked ONLY for a pay type of 'Hourly'
;:When [UPTG] generates the pay transactions, the system will generate one transaction per assignment per distribution code on the list. The pay transaction will be overridden with the proper rate and complete GL distribution code.
;:For example, if [UPTG] is run for an employee with three assignments and each assignment has three distribution records defined on [IEAS], we would expect to see nine transaction records in [IPTR] per week, or eighteen records per pay period.
;:Employees can work in multiple locations (GL Distributions) at multiple rates of pay on multiple time sheets. These enhancements are required to accurately record the time and pay the employee.
;:‘Create by Period’ will still be split into more than one transaction when the period crosses over the end of a month or a holiday is generated.
;[Time Gen. Destination|TIME_GENERATION_DESTINATION]:This field allows you define where the programs are going to be run from.
;[Generate Holidays|GENERATE_HOLIDAYS]:If the Generate Holidays toggle is ON, holiday hours will be generated. If the toggle is OFF, no holiday hours will be generated.
\\
----
!!Time Codes tab
This screen is used to indicate the order of processing for the time codes indicated.
;[Seq#|TIME_CODE_SEQUENCE]:This field will specify the order of priority of the time codes previously indicated.
;[Time Code|DTC_ID]:This field displays the time code previously indicated.
;[Description|DESCRIPTION]:
;[Time Type|]:
;[Reason for Time|REASON_FOR_TIME]:
;[Requires Authorization|REQUIRES_AUTHORIZATION]:
__For Time Rule Types Without Time Code Sets__
;[Daily OT|DAILY_OT_ELIGIBLE]:
;[Daily Holiday OT|HOLIDAY_OT_ELIGIBLE]:
;[Weekly OT|WEEKLY_OT_ELIGIBLE]:
;[Extended OT|EXTENDED_OT_ELIGIBLE]:
;[Consecutive OT|CONSECUTIVE_OT_ELIGIBLE]:
;[Lunch OT|LUNCH_ELIGIBLE]:
;[Meal Allowance|MEAL_ALLOWANCE_ELIGIBLE]:
;[Call In|CALL_IN_ELIGIBLE]:
;[Guaranteed Time|GUARANTEED_TIME_ELIGIBLE]:
;[Actual Time|ACTUAL_TIME_REQUIRED]:
----
!!Shift Rules tab
;[Shift|TSS_ID]:
;[Time Code|DTC_ID]:
;[Premium|SPM_ID]:
----
!!Time Rules tab
;[Frequency|]:
;[Cycle|CYCLE_NUMBER]:
;[Seq|PROCESSING_SEQUENCE]:
;[Time Rule Type|TRT_ID]:
;[Band|QUALIFYING_BAND]:
;[From|ACTUAL_TIME_REQUIRED]:
;[Actual Time|FROM_CLOCK_TIME]:
;[To|TO_CLOCK_TIME]:
;[Value|TIME_RULE_VALUE]:
;[Day|DAY_OF_WEEK]:
;[Time Code|DTC_ID]:
;[Premium|SPM_ID]:
;[Disable|DISABLE_RULE]:
;[Target Time Code Set|]:
;[Apply Time Code Set|]:
;[Action|TIME_RULE_ACTION]:
;[Time Rule Text|]:
;[Message Text|MESSAGE_TEXT]:
;[Generate Warning|GENERATE_WARNING]:
;[Trace|TRACE_LEVEL]:
;[Can Be Waived|CAN_BE_WAIVED]: