Work Rules#
Work Rules are used to determine the standard processing information that is required in order to create 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.
Work Rules are created and maintained through the Define Work Rules (IDWR) form.
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’ process (UPTG) 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, and P2K_CM_WORK_RULE_TIME_CODES tables.
- Work Rule
- Work rules are used to determine standard processing information required in creating pay headers and transactions for a person. Work_Rule_Code is a 16-character alphanumeric mandatory field you must manually enter
- Entity
- This field displays the entity to which the work rule belongs. Entity_Code from P2K_CM_ENTITIES is a 16-character alphanumeric mandatory field
- Standing
- This field indicates whether this work rule is active, obsolete or frozen. Standing is an optional fixed lexicon (X_STANDING) you may use to look up the value.
Details#
- Description
- This field displays the description of the purpose and use of the work rule. Description is an optional 50-character alphanumeric field you must manually enter.
- 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. Work_Calendar_Code from P2K_CM_WORK_CALENDARS is an optional field.
- Holiday Calendar
- This is the holiday calendar code to be used for this work rule, if applicable. Holiday_Calendar_Code from P2K_CM_HOLIDAY_CALENDARS is an optional field.
- Float Days Allowed
- This field will indicate that if a contract is specified, whether or not float days allowed. Float_Days_Allowed is an optional 5-digit numeric field you may manually enter.
- 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. Work_Is_Scheduled is an optional toggle field.
- Must Be Acknowledged
- Must_Be_Acknowledged is an optional toggle field.
- Time Rounding Rule
- This field indicates how the time an employee works should be rounded, if at all. Time_Rounding_Rule is an optional fixed lexicon (X_TIME_ROUNDING_RULE) field that you may fill with a selection from the values provided.
- Time Rounding Factor
- This field indicates to what decimal point the time should be rounded. Time_Rounding_Factor is an optional 9-character numeric value you may manually enter.
- Pays Per Contract
- This field identifies how many pays will be covered in this contract. Pays_Per_Contract is an optional 5-character numeric field you may manually enter.
- Start Date of Pay
- This field identifies the day when the pay for this work rule will commence. Pay_Starting_Date is an optional date field.
- 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. First_Day_Of_Week is an optional fixed lexicon (X_FIRST_DAY_OF_WEEK).
- Pieces Per Day
- This field shows the standard number of pieces per day an employee produces. Example: A seamstress sews 14 shirts (pieces). Pieces_Per_Day is an optional numeric field you must manually enter.
- Std Hours Per Day
- This field shows the standard number of hours per day. Hours_Per_Day is an optional numeric field you must manually enter.
- Std Hours Per Week
- This field shows the standard number of hours per week. Hours_Per_Week is an optional numeric field you must manually enter.
- Std Hours Per Pay
- This field shows the standard number of hours in a pay period. Hours_Per_Pay is an optional numeric field you must manually enter.
- Weeks Per Year
- This field shows the standard number of weeks in a year (default is 52). Weeks_Per_Year is an optional numeric field you must manually enter.
- Months Per Year
- This is the standard number of months in a year (default is 12). Months_Per_Year is an optional numeric field you must manually enter.
- FLSA Method
- For U.S. installations only: This field indicates the method by which FLSA must be calculated. FLSA_Method is an optional fixed lexicon (X_FLSA_CALC_METHOD) field which you may fill with a selection from the values provided.
- Group Source
- This is the group source for pay headers to be created. This field indicates the source for time creation for example: Not Specified, Prime Assignment, Posn/Prime Assign or Job Only Group_Source is an optional fixed lexicon (X_GROUP_SOURCE) field which you may fill with a selection from the values provided.
Status Rules#
- Status
- This field shows the employment status code that may be indicated on an employee’s record. (ACTIVE should be defined as the default.) Status_Code from P2K_CM_EMPLOYMENT_STATUSES is a mandatory LOV field that you must fill with a selection from the values provided.
- Regular Time Code
- This field shows the time code that normal time is to be paid out under. Time_Code from P2K_CM_TIME_CODES is a mandatory field.
- Salary $ Code
- This field shows the time code that salaried employees are to be paid out under. Time_Code from P2K_CM_TIME_CODES is an optional field.
- Time Generation Rule
- This field indicates the type of time transactions that must be generated for a person.
- By Day with Time
- For a biweekly payroll this would create ten daily transactions, with hours under the pay component attached to the time code indicated.
- By Week with Time
- For a monthly payroll this would create four to six transactions, each breaking as of the Friday of each week during the month, with hours under the pay component attached to the time code indicated.
- By Period with Time
- This will create one transaction regardless of the payroll cycle, with hours under the pay component attached to the time code indicated.
- By Day w/o Time
- For a biweekly payroll this would create ten daily transactions for the pay component attached to the time code indicated with no hours.
- By Week w/o Time
- For a monthly payroll this would create four to six transactions, each breaking as of the Friday of each week during the month for the pay component attached to the time code indicated with no hours.
- By Period w/o Time
- This will create one transaction regardless of the payroll cycle for the pay component attached to the time code indicated with no hours.
- There are three additional Time Generation rules:
- *Pick List by Day
- *Pick List by Week
- *Pick List by Period
- *Holidays ONLY
- Choosing one of these 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 timesheets. 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_Generation_Rule is an optional fixed lexicon (X_TIME_GENERATION_RULE) field which you may fill with a selection from the values provided.
- Time Gen. Destination
- This field allows you define where the programs are going to be run from.
| TS (Time Scheduling) | - Shift Pattern |
| TS (Time Scheduling) | - Event Schedule |
| TM (Time Management) | - Shift Calendar |
| TM (Time Management) | - Hours Calendar |
| PR (Payroll) | - Calendar |
- 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. Timesheet_Required is an optional toggle field. Timesheet_Required is an optional toggle field.
- 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. Generate_Headers is an optional toggle field.
- Generate Details
- If the Generate Details toggle is ON, then details will be attached to the header generated.
- 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. Generate_Holidays is an optional toggle field.
- Accumulate Experience
- This toggle will be discussed more during Salary Administration training. Accumulate_Experience is an optional toggle field.
Time Codes#
This screen is used to indicate the order of processing for the time codes indicated.
- Seq#
- This field will specify the order of priority of the time codes previously indicated. Time_Code_Sequence is a mandatory numeric field.
- Time Code
- This field displays the time code previously indicated. Time_Code from P2K_CM_TIME_CODES is a mandatory field.
