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

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
68 26-Nov-2021 10:22 14 KB ihowie to previous
67 26-Nov-2021 10:22 14 KB rthiruppathy to previous | to last
66 26-Nov-2021 10:22 13 KB kparrott to previous | to last
65 26-Nov-2021 10:22 13 KB jescott to previous | to last
64 26-Nov-2021 10:22 13 KB jescott to previous | to last
63 26-Nov-2021 10:22 13 KB jescott to previous | to last Target Time Code Set ==> TARGET_TIME_CODE_SET
62 26-Nov-2021 10:22 13 KB jescott to previous | to last
61 26-Nov-2021 10:22 13 KB rforbes to previous | to last

Page References

Incoming links Outgoing links
IDWR
IDWR

Version management

Difference between version and

At line 1 changed 2 lines
!!!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.
[{TableOfContents }]
At line 4 changed one line
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.
!!!DEFINE WORK RULES
Work Rules contain all of the policies and factors that describe an employee’s work arrangement. Work rules are used to determine the standard processing information that is required to create time sheets, pay headers and payroll transactions for an employee. The IDWR function is used to define and maintain work rules and their associated information.
At line 6 changed 2 lines
Work Rules are created and maintained through the Define Work Rules (IDWR) form.
Work rule defaults can be set at the group, department, job, position or assignment level. When an employee is assigned to that group, department, job, position or assignment, the employee will inherit its work rule. Overriding a work rule can be done on the work assignment.
At line 9 removed 5 lines
*Groups
*Departments
*Jobs
*Positions
*Assignment
At line 15 changed one line
Time generation through the ‘Generate Pay Transactions’ process ([UPTG]) cannot take place unless basic information is completed.
*Groups(IDGR) under ‘Work Rules’ tab
*Departments (IDDP) under ‘Definition’ tab
*Jobs (IDJB) under ‘Compensation’ tab
*Positions (IDPS) under ‘Definition’ tab
*Assignment (IEAS) under ‘Definition’ tab
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.
At line 22 changed one line
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 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.
At line 24 changed one line
;[Work Rule|WORK_RULE_CODE]: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
;[Work Rule|WORK_RULE (Field)]:Work rules are used to determine standard processing information required in creating pay headers and transactions for a person.
At line 26 changed one line
;[Entity|ENTITY_CODE]:This field displays the entity to which the work rule belongs. Entity_Code from [P2K_CM_ENTITIES] is a 16-character alphanumeric mandatory field
;[Entity|DEN_ID]:This field displays the entity to which the work rule belongs.
At line 28 changed one line
;[Standing|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.
;[Standing|STANDING]:This field indicates whether this work rule is active, obsolete or frozen.
%%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.%%
At line 31 changed one line
!!Details
!!Details tab
At line 33 changed one line
;[Description|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.
;[Description|DESCRIPTION]:This field displays the description of the purpose and use of the work rule.
At line 35 changed one line
;[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. Work_Calendar_Code from [P2K_CM_WORK_CALENDARS] is an optional field.
;[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.
At line 37 changed one line
;[Holiday Calendar|HOLIDAY_CALENDAR_CODE]: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.
;[Holiday Calendar|DHC_ID]:This is the holiday calendar code to be used for this work rule, if applicable.
At line 39 changed one line
;[Float Days Allowed|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.
;[Float Days Allowed|FLOAT_DAYS_ALLOWED]:This field will indicate that if a contract is specified, whether or not float days allowed.
At line 41 changed one line
;[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. Work_Is_Scheduled is an optional toggle field.
;[Holidays Use Schedule Hrs|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.
At line 43 changed one line
;[Must Be Acknowledged|MUST_BE_ACKNOWLEDGED]:Must_Be_Acknowledged is an optional toggle field.
;[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.
At line 45 changed one line
;[Time Rounding Rule|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.
;[Must Be Acknowledged|MUST_BE_ACKNOWLEDGED]:
At line 47 changed one line
;[Time Rounding Factor|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.
;[Time Rounding Rule|TIME_ROUNDING_RULE]:This field indicates how the time an employee works should be rounded, if at all.
At line 49 changed one line
;[Pays Per Contract|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.
;[Time Rounding Factor|TIME_ROUNDING_FACTOR]:This field indicates to what decimal point the time should be rounded.
At line 51 changed one line
;[Start Date of Pay|PAY_STARTING_DATE]:This field identifies the day when the pay for this work rule will commence. Pay_Starting_Date is an optional date field.
;[Pays Per Contract|PAYS_PER_CONTRACT]:This field identifies how many pays will be covered in this contract.
At line 53 changed one line
;[Work in Restriction Rule|WORK_IN_RESTRICTION_RULE]:This field is not currently functioning.
;[Start Date of Pay|PAY_STARTING_DATE]:This field identifies the day when the pay for this work rule will commence.
At line 55 changed one line
;[First Day of Week|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_DAY_OF_WEEK]).
;[Work in Restriction Rule|WORK_IN_RESTRICTION_RULE]:This field specifies if the work is to be done in a specific department.
At line 57 changed one line
;[Pieces Per Day|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.
;[First Day of Week|FIRST_DAY_OF_WEEK]:The field shows the first day of the week the pay period begins.
At line 59 changed one line
;[Std Hours Per Day|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.
;[Pieces Per Day|PIECES_PER_DAY]:This field shows the standard number of pieces per day an employee produces. Example: A seamstress sews 14 shirts (pieces).
At line 61 changed one line
;[Std Hours Per Week|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 Day|STD_HOURS_PER_DAY]:This field shows the standard number of hours per day.
At line 63 changed one line
;[Std Hours Per Pay|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.
;[Std Hours Per Week|STD_HOURS_PER_WEEK]:This field shows the standard number of hours per week.
At line 65 changed one line
;[Weeks Per Year|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.
;[Std Hours Per Pay|STD_HOURS_PER_PAY]:This field shows the standard number of hours in a pay period.
At line 67 changed one line
;[Months Per Year|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.
;[Weeks Per Year|WEEKS_PER_YEAR]:This field shows the standard number of weeks in a year (default is 52).
At line 69 changed one line
;[FLSA Method|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.
;[Months Per Year|MONTHS_PER_YEAR]:This is the standard number of months in a year (default is 12).
At line 71 changed one line
;[Group Source|GROUP_SOURCE]:This is the group source for pay headers to be created. Group_Source is an optional fixed lexicon ([X_GROUP_SOURCE]) field which you may fill with a selection from the values provided.
;[FLSA Method|FLSA_METHOD]:For U.S. installations only: This field indicates the method by which [FLSA] must be calculated.
;[FLSA Hours|FLSA_HOURS]:This field shows the base hours after which the FLSA calculation will begin. Any time worked over the indicated hours within the calendar period (or seven days if no calendar is indicated) will be paid at the FLSA Factor rate.
;[FLSA Calendar|FLSA_CALENDAR]:If FLSA is to be calculated over more than 7 days, a calendar must be set up to define the cycle.
;[Group Source|GROUP_SOURCE]:This is the group source for pay headers to be created.
;[Track Work Punches|TRACK_WORK_PUNCHES]:If this toggle is on, work clock punches will be tracked.
;[Track Meal Punches|TRACK_MEAL_PUNCHES]:If this toggle is on, meal clock punches will be tracked.
At line 74 changed one line
!!Status Rules
!!Status Rules tab
At line 76 changed one line
;[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.) Status_Code from [P2K_CM_EMPLOYMENT_STATUSES] is a mandatory LOV field that you must fill with a selection from the values provided.
;[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.)
At line 78 changed one line
;[Regular Time Code|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.
;[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.
At line 80 changed one line
;[Salary $ Code|TIME_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.
;[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.
At line 82 changed one line
;[Time Generation Rule|TIME_GENERATION_RULE]: This field indicates the type of time transactions that must be generated for a person.
;[Into Time Code|TIME_CODE]: The time code that time is generated into
At line 84 changed 2 lines
;:__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.
;[Generate Salary As|TIME_CODE]: The time code that salary dollars are generated into
At line 87 changed 2 lines
;:__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.
;[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.
At line 90 changed 2 lines
;:__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.
;[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.
At line 93 changed 2 lines
;:__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.
;[Add 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.
At line 96 changed 2 lines
;:__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.
;[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.
At line 99 changed 13 lines
;:__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.
;[Accumulate Experience|ACCUMULATE_EXPERIENCE]:
At line 113 changed 7 lines
;[Time Gen. Destination|TIME_GENERATION_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
Time_Generation_Destination is an optional fixed lexicon ([X_TIME_GEN_DEST]) field which you may fill with a selection from the values provided.
;[Regular Time Code|TIME_CODE]:This field shows the time code that normal time is to be paid out under.
At line 121 changed one line
;[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. Timesheet_Required is an optional toggle field. Timesheet_Required is an optional toggle field.
;[Salary $ Code|TIME_CODE]:This field shows the time code that salaried employees are to be paid out under.
At line 123 changed one line
;[Generate 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. Generate_Headers is an optional toggle field.
;[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.
At line 125 changed 2 lines
;[Generate 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. Generate_Details is an optional toggle field.
;[Time Gen. Destination|TIME_GENERATION_DESTINATION]:This field allows you define where the programs are going to be run from.
At line 128 changed one line
;[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. Generate_Holidays is an optional toggle field.
;[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.
At line 130 changed one line
;[Accumulate Experience|ACCUMULATE_EXPERIENCE]:This toggle will be discussed more during Salary Administration training. Accumulate_Experience is an optional toggle field.
At line 133 changed one line
!!Time Codes
!!Time Codes tab
At line 137 changed one line
;[Seq#|TIME_CODE_SEQUENCE]:This field will specify the order of priority of the time codes previously indicated. Time_Code_Sequence is a mandatory numeric field.
;[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]:This field provides a description of the time code.
;[Time Type|TIME_TYPE]:This field identifies the type of time that this time code will store.
;[Reason for Time|REASON_FOR_TIME]:The reason for the time code is provided in this field.
;[Requires Authorization|REQUIRES_AUTHORIZATION]:If this toggle is checked, the time code requires authorization.
At line 139 changed one line
;[Time Code|TIME_CODE]:This field displays the time code previously indicated. Time_Code from [P2K_CM_TIME_CODES] is a mandatory field.
__For Time Rule Types Without Time Code Sets__
;[Daily OT|DAILY_OT_ELIGIBLE]:If this toggle is checked, daily overtime is allowed for this time code.
;[Daily Holiday OT|HOLIDAY_OT_ELIGIBLE]:If this toggle is checked, daily holiday overtime is allowed for this time code.
;[Weekly OT|WEEKLY_OT_ELIGIBLE]:If this toggle is checked, weekly overtime is allowed for this time code.
;[Extended OT|EXTENDED_OT_ELIGIBLE]:If this toggle is checked, extended overtime is allowed for this time code.
;[Consecutive OT|CONSECUTIVE_OT_ELIGIBLE]:If this toggle is checked, consecutive overtime is allowed for this time code.
;[Lunch OT|LUNCH_ELIGIBLE]:If this toggle is checked, lunch time is allowed for this time code.
;[Meal Allowance|MEAL_ALLOWANCE_ELIGIBLE]:If this toggle is checked, meal allowance is allowed for this time code.
;[Call In|CALL_IN_ELIGIBLE]:If this toggle is checked, call in is allowed for this time code.
;[Guaranteed Time|GUARANTEED_TIME_ELIGIBLE]:If this toggle is checked, guaranteed time is allowed for this time code.
;[Actual Time|ACTUAL_TIME_REQUIRED]:If this toggle is checked, actual time is required for this time code.
----
!!Shift Rules tab
;[Shift|SHIFT_CODE]:This field identifies the shift associated with the work rule.
;[Time Code|TIME_CODE]:The time code associated with the shift is identified in this field.
;[Premium|PREMIUM_CODE]:The premium associated with the shift is identified in this field.
----
!!Time Rules tab
;[Frequency]:
;[Cycle|CYCLE_NUMBER]:This field is used used to change the order of time rules of different frequencies.
;[Seq|PROCESSING_SEQUENCE]:This field allows you to change the order of time rules within the same frequency.
;[Time Rule Type|TIME_RULE_TYPE_CODE]:This field defines the time rule type.
;[Band|QUALIFYING_BAND]:This field is used as a threshold, for example used to hold a minimum number of hours before the employee qualifies for overtime.
__Banding Time Rules__
;[From|FROM_CLOCK_TIME]/[To|TO_CLOCK_TIME]:These fields define the to and from clock times for the banding time rules.
;[Value|TIME_RULE_VALUE]:The value associated with the banding rule is identified in this field.
;[Day|DAY_OF_WEEK]:The day of the week associated with this banding rule is identified in this field.
;[Time Code|TIME_CODE]:The time code associated with this banding rule is identified in this field.
;[Premium|PREMIUM_CODE]:The premium associated with this banding rule is identified in this field.
;[Disable|DISABLE_RULE]:This toggle is used to refrain the Time Rule engine from calling the time rule. This is typically used to help debug time rules.
;[Target Time Code Set|TARGET_TIME_CODE_SET]: This field is used to specify a time code set, a group of time codes, that qualify for the time rule.
;[Apply Time Code Set|APPLY_TIME_CODE_SET]:This field is used to specify a time code set (usually a subset of the Target Time Code Set) that the rule should actually be applied to. This is often used with time Daily or Weekly time rules.
;[Action|TIME_RULE_ACTION]:This field is used to indicate how the Time Rule engine is to apply the time rule.
;[Time Rule Text|TIME_RULE_TYPE_TEXT]:This field is used to display a pre-defined explanation of the Time Rule.
;[Message Text|MESSAGE_TEXT]:This field provides a system message for the time rule.
;[Generate Warning|GENERATE_WARNING]:If this toggle is ON, a warning will be generated to alert the user to apply the time rule type.
;[Trace|TRACE_LEVEL]:This field is used to indicate the level of trace (messages) that the calculation report should display when performing a trial calculation. This field is used for troubleshooting purposes. [TIME_RULE_TRACING]
;[Can Be Waived|CAN_BE_WAIVED]:This field allows you to flag that a time rule should not be applied. The toggle also allows you to turn on a currently disable time rule .
----
![Notes|Edit:Internal.IDWR]
[{InsertPage page='Internal.IDWR' default='Click to create a new notes page'}]
This page (revision-68) was last changed on 26-Nov-2021 10:22 by ihowieTop