Wiki: IDWR

This is version . It is not the current version, and thus it cannot be edited.

Back to current version Restore this version

DEFINE WORK RULES
Details tab
Status Rules tab
Time Codes tab
Shift Rules tab
Time Rules tab

DEFINE WORK RULES#

Work Rules are used to determine the standard processing information that is required in order to create time sheets, pay headers and payroll transactions for an employee.

Work rule defaults can be set at the job, position or group level. When an employee is assigned to that job, position or group, the employee will inherit its work rule. You may override this information on the work assignment.

Once defined, work rules may be placed on the following forms to allow for defaulting:

Groups
Departments
Jobs
Positions
Assignment

Time generation through the ‘Generate Pay Transactions’ (UPTG) process or through the 'Generate Scheduled Shifts and Time Sheets' (UEGTS) process cannot take place unless basic information is completed.

The ‘Standard Hours Per Day’ field will define the default hours per day.

This is used as a default if no ‘Hours Per Day’ is entered in the Work Calendar (IDWC). If ‘Hours per Day’ are entered in the Work Calendar (IDWC) and they are less than the ‘Standard Hours Per Day’ on IDWR, the work calendar hours are pro-rated against the work rule hours.

Work Rule data is stored in the P2K_CM_WORK_RULES,P2K_CM_WORK_RULE_DETAILS, P2K_CM_WORK_TIME_RULES, P2K_CM_WORK_RULE_TIME_CODES, P2K_TS_SHIFT_RULES, P2K_TS_TIME_RULES, P2K_TS_TIME_RULE_TYPES, P2K_HR_ASSIGNMENT_DETAILS and P2K_CM_POSITION_DETAILS tables.

Work Rule: Work rules are used to determine standard processing information required in creating pay headers and transactions for a person.

Entity: This field displays the entity to which the work rule belongs.

Standing: This field indicates whether this work rule is active, obsolete or frozen.

This function is date sensitive and changes made in these areas below the date navigator may be split with a new effective date.

Details tab#

Description: This field displays the description of the purpose and use of the work rule.

Work Calendar: 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: This is the holiday calendar code to be used for this work rule, if applicable.

Float Days Allowed: This field will indicate that if a contract is specified, whether or not float days allowed.

Holidays Use Schedule Hrs

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

Time Rounding Rule: This field indicates how the time an employee works should be rounded, if at all.

Time Rounding Factor: This field indicates to what decimal point the time should be rounded.

Pays Per Contract: This field identifies how many pays will be covered in this contract.

Start Date of Pay: This field identifies the day when the pay for this work rule will commence.

Work in Restriction Rule: This field is not currently functioning.

First Day of Week: The field shows the first day of the week the pay period begins.

Pieces Per Day: This field shows the standard number of pieces per day an employee produces. Example: A seamstress sews 14 shirts (pieces).

Std Hours Per Day: This field shows the standard number of hours per day.

Std Hours Per Week: This field shows the standard number of hours per week.

Std Hours Per Pay: This field shows the standard number of hours in a pay period.

Weeks Per Year: This field shows the standard number of weeks in a year (default is 52).

Months Per Year: This is the standard number of months in a year (default is 12).

FLSA Method: For U.S. installations only: This field indicates the method by which FLSA must be calculated.

FLSA Hours

FLSA Calendar

Group Source: This is the group source for pay headers to be created.

Track Work Punches

Track Meal Punches

Status Rules tab#

Status: 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

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.

Into Time Code

Generate Salary As

Create 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

Add Holidays

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

Regular Time Code: This field shows the time code that normal time is to be paid out under.

Salary $ Code: This field shows the time code that salaried employees are to be paid out under.

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: This field allows you define where the programs are going to be run from.

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.