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

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

Page References

Incoming links Outgoing links
TERMINOLOGY-TS
TERMINOLOGY-TS

Version management

Difference between version and

At line 62 changed one line
;Field Prompt:This is the ‘label’ that the user will see for the GL segment being entered ([IDGS]) and the approval level needed ([IDAP])
;Field Prompt:This is the ‘label’ that the user will see for the GL segment being entered (IDGS) and the approval level needed (IDAP)
At line 66 changed one line
;FLSA Method:For U.S. installations only: Indicates the method by which [FLSA] must be calculated. FLSA_Method is an optional fixed lexicon [X_FLSA_CALC_METHOD].
;FLSA Method:For U.S. installations only: Indicates the method by which FLSA must be calculated. FLSA_Method is an optional fixed lexicon [X_FLSA_CALC_METHOD].
At line 119 changed one line
;Mandatory: If the toggle is ON, then the segment must be completed at all distribution levels. This means no masking is allowed. If the toggle is OFF, then the segment may be completed, wild carded or left blank.
;Mandatory: If the toggle is ON, then the segment must be completed at all distribution levels. This means no masking is allowed.
If the toggle is OFF, then the segment may be completed, wild carded or left blank.
At line 124 changed one line
;Minimum Hours Off: This field indicates the minimum hours that an employee in that work area must be off before they can be scheduled for another shift. The format for this field is xx,xxx.xx
;Minimum Hours Off: This field indicates the minimum hours that an employee in that work area must be off before they can be scheduled for another shift.The format for this field is xx,xxx.xx
At line 150 changed one line
;Pay Period:Pay periods are numbered by the year, followed by the week # of the year. All weeks in the year must be defined, although not all week must be pay periods.
;Pay Period:Pay periods are numbered by the year, followed by the week # of the year. All weeks in the year must be defined,
although not all week must be pay periods.
At line 168 removed 44 lines
;Rank:This field indicates the order in which the replacement job being defined will fill the position. If a job is ranked as ‘1’ it will be chosen as the first to fill this position, etc.
;Rate:Standard Rate is the rate used for this premium.
;Rate Basis:The rate basis is the unit of measure the associated rate is being stored or displayed in; for example: hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate_Basis is a fixed lexicon [X_RATE_BASIS]
;Raw time:The total time worked, normally shown in hours and minutes of the day.
;Reason for Time:This field displays an explanation for the time code. Reason for time entered. May be a reason for a leave, or a reason for overtime. Defaults from the [IDWR] Time Codes tab for the Time Code being entered. Reason_for_Time is an optional field that users may fill with a value selected from the user defined lexicon [X_REASON_FOR_TIME].
;Reference ID:This field allows the user to identify the approval for later reference.
;Reference Info:This field allows the user to provide any additional reference information about the approval.
;Reference Match:If an approval type has multiple sub categories, this field is used to identify those subcategories.
;Refusal:A record of an employee's refusal of a work assignment, shift or overtime offer, also know as a decline.
;Relative Day #:This field assigns a day number, relative to the starting date of the work calendar, to each defined calendar date.
;Rel. Start Date:This field indicates which day of predefined shift a team would begin with. For instance, on August 22, one team may start on the 1st day (Aug 22) of an 8-day shift pattern while another team would start on the 3rd (Aug 24) day of that same pattern.
;Replacement Jobs:A list of jobs related to another job that can be used as alternates in the search for qualified employees to fill vacant posts.
;Replacement Rule:If the job in the station post is vacant and must be replaced, the replacement rule is designed to give the user detailed information regarding how to make the replacement. A field the user may fill using the fixed lexicon [X_REPLACEMENT_RULE].
;Required WSE:The ‘Required Work Shift Equivalent (WSE)’ is the measure of work to be done in a station post in one shift. If the post requires a full-time person the WSE will be 1. If the post requires a person only half time, the WSE will be .5
;Reserve List:List of the spare employees who may be called in to work on short notice, Call In List, Reserve, Casual or Float Pool.
;Restriction Type:If the employee has any preferences or restrictions for this job, that type of restriction is indicated here.
;Rounding Rules:Rounding Rules are associated with the conversion of raw times to elapsed time.
\\
!![S|#19]
----
;Sched. Time:If time was generated on the pay transaction then the amount that was generated will be indicated here. This will be used to ensure that the day, week or period scheduled time will always added up to the generated time.
;Schedule Deadline:This field identifies the day of the week used as the deadline day for time scheduling. Schedule_Deadline is an optional field that the user may fill using the fixed lexicon [X_DAY_OF_WEEK].
;Scheduling:A method for bringing together work requirements and the people resources that are needed to complete them within the required time frame, may be referred to as work scheduling, shift scheduling, personnel/staff scheduling, manpower loading.
;Segment:This is the sequential order of the segments. Maximum of ten segments may be defined numbered between 1 through 10.
;Seniority Date:This field shows the date that the employee will gain seniority in this assignment
;Sequence:The order that the data must be displayed or processed
;Shift:A time period within a day during which work is done. In certain industries a system of shifts is required to keep operations running effectively. A shift is described by when it occurs (e.g. day, afternoon, night, graveyard, or swing shift). The rules determining the start, stop, meal, and break times etc. vary by shift. Shifts sometimes need to be divided into a smaller number of periods called time slots. The name of the shift.
;Shift Differential:An amount of money that is earned in addition to an employee's regular wage for working a particular shift; it is given to employees as a premium.
;Shift Letter: This field identifies whether the shift is ‘D’-Day, ‘E’-Evening, or ‘N’-Night (defined in [ITSS]). A field the user may fill with the user-defined lexicon [X_SHIFT_LETTER].
;Shift Pattern: Specifies a daily sequence of shifts worked and "off" days, repeating every "n" days. Shift patterns are used in establishing work team shift rotations. This field displays the user defined code that uniquely identifies the shift pattern.
;Shift Rotation: Specifies the day by day shift pattern that occurs for a given work team. Rotations are used in a shift environment to cycle workers through the different shifts fairly ensuring that the work stations are properly filled.
;Shift Status:Status is used to indicate whether an area is active at a SPECIFIC point in time, which is different from the standing of an area. For example, while a lifeguard station may have ongoing active standing (not obsolete or frozen), the station may only be active 9 months of the year. For remaining three months of the year, the area’s status is non-active.
;Standing: This field is used to indicate whether the record is ‘active’, ‘frozen’ or ‘obsolete’. Standing is a field the user may fill using the fixed lexicon [X_STANDING].
;Start At: This is the starting position of the segment. This is not the VALUE in that position. It does not count ‘-’ or ‘.’ as a position
;Start Date: The beginning date of a time frame for this data. A date field the user must either manually enter or choose a value from the calendar icon (F9).
;Start Time:This field defines the start time of the shift.
;Start Time of Day:When shifts are scheduled for this work division, this field will identify the daily start time for the schedule week.
;Starting Date:This field identifies the first date the work calendar begins. This field will be used to populate the details
;Station Post:A list of jobs required within a work station ranked in the order they must be filled (based on level of responsibility, skill and pay), also known as a promotion line or line of progression. A station post is a job done by an individual person; it may be full-time or part time, mandatory or optional. This user-defined value is used as a ‘line of progression’ to rank the jobs necessary to fill a workstation. Rank may be used during call-in or replacement situations as well as scheduling to move employees up/down the line of progression for the workstation.
;Status: Status is used to indicate whether an area is active at a SPECIFIC point in time, which is different from the standing of an area. For example, while a lifeguard station may have ongoing active standing (not obsolete or frozen), the station may only be active 9 months of the year. For remaining three months of the year, the area’s status is non-active.
;Std Hours Per Day: This is the standard number of hours per day
;Std Hours Per Pay:This field holds the standard number of hours in a pay period for this work arrangement.
;Std Hours Per Week:This field holds the standard number of hours per week for this work arrangement.
;Stop Time:This field defines the ending time of the shift.
At line 213 removed 91 lines
\\
!![T|#20]
----
;Tardiness: Occurs when a defined late tolerance is exceeded and for which a penalty or consequence is usually applied.
;Team Post:A specific station post on a specific work team. A team post may be filled or vacant at any point in time.
;Text:This screen provides additional information about the time rule in this screen, For example, a short description of the usage and purpose of the time rule.
;Time Basis: This field indicates the basis in which the time code is kept. Time_Basis is a mandatory fixed lexicon [X_TIME_BASIS].
;Time Code: A user-defined code used during scheduling and time entry that breaks down time work, leave time or other entries. Time codes are classified by time code types. Time codes are transformed into pay components upon entry into payroll system. This field displays the user-defined time code that uniquely identifies a type of time. This is the time code to be used by the time entry, work scheduling and pay generation processes to link with payroll. Time Code to be used to create transaction detail. More than one time code can exist per [IPTR] line.
;Time Code (toggle):If this toggle is ON, the user will be able to associate a time code to this time rule in other screens.
;Time Exception:A condition that must be highlighted or a situation that requires attention.
;Time Format:This field identifies the format that will be used when scheduling work divisions. Time_Format is a mandatory field that the user must fill using the fixed lexicon [X_TIME_FORMAT].
;Time Rounding Factor:This field identifies the factor by which the time is rounded, either up or down.
;Time Rounding Rule: This field defines how the time should be rounded. Time_Rounding_Rule is an optional field that the user may fill with a value from the fixed lexicon [X_ROUND_RULE] provided.
;Time Rule Action: The ‘Time Rule Action’ field is used to indicate whether the time rule is to ‘add’, or ‘replace’. Time_Rule_Action is a mandatory field the user may fill with the fixed lexicon [X_TIME_RULE_ACTION] provided.
;Time Rule Type:This field identifies the category of time rule.
;Time Rule Value:Time_Rule_Value is an optional 18-character numeric field the user may fill manually.
;Time Sheet Required (info only):If the Time Sheet Required toggle is ON, employees are required to submit some kind of record (paper or electronic) of their work and/or attendance.
;Time Slot: A subdivision of a shift identified by a start and stop time. Time slots may be for time worked, time off, breaks or lunches.
;Time Slot Type:This field describes the employee’s activity during the specified time. Time_Slot_Type is a mandatory field the user must fill with the fixed lexicon [X_TIME_SLOT_TYPE] provided.
;Time Sheet:A paper or electronic form that records employee work and absentee time, also knows as a Time Card, Time Entry or Worksheet.
;Time Type:This field categorizes the time code as a time type. Time_Type is a mandatory field the user must fill either manually or with the fixed lexicon [X_TIME_TYPE].
;To Clock Time: This field displays the end time of any time rule applicable to a certain time of day.
;Tolerance:The amount of time granted to employees before being considered late for a shift.
;Total Hours:This field shows the total hours for this employee in this batch.
\\
!![U|#21]
----
;Unit:A subdivision of an entity that rules and policies are established by, may be a union, a bargaining unit, a contract group or a set of employees governed by the same rules
;Up to Approval:If this toggle is ON, the employee may approve all employees beneath him/her (up to and including themselves) in one action.
;Updated By:Displays the execution id (MEX_ID) of the function that changed/updated the transaction
;User Calc: If this toggle is ON, the user will be able to associate a usercalc to this time rule in other screens.
;User Calc Code:This field will display any user calc code associated with the time rule.
;User Name:This field displays the name of actual user give approval rights.
\\
!![V|#22]
----
;Vacancy List:Lists any vacancies to be filled after all eligible employees have received their assignments, also know as Shortage List.
;Validate Unit:This is the sequential order of the segments. These segments should be numbered 11 and greater in order to keep the separate from the original G/L segments.
;Validation Name: This field provides the name of the segment combination.
;Value:Amount of time entered on the pay line.
;Value (toggle):If this toggle is ON, the user will be able to associate a value (e.g. hours paid, number of meals) to this time rule in other screens.
;Value Prompt:This field shows the descriptive name of the value associated with the time rule.
;Variance:A deviation from the standard or expected measure or amount that has been defined.
\\
!![W|#23]
----
;Wage Rate:Standard wage rate from primary assignment.
;Weeks per Year:This field holds the standard number of weeks in a year for this work arrangement (default is 52).
;Work Area:A subdivision of a [work division|WORK DIVISIONS] where work is performed such as a plant location, production line, process, product, cost center, floor, ward or department, managed by a supervisor, pit boss or foreman who may be responsible for more than one work area. A [work area|WORK AREAS] is generally subdivided into work stations based on activities, machinery, equipment or processes. Quite often, a [work area|WORK AREAS] consists of a single work station. This field is a user-defined code that uniquely identifies the [work area|WORK AREAS], a subdivision within a [work division|WORK DIVISIONS].
;Work Area Status: Status is used to indicate whether an area is active at a SPECIFIC point in time, which is different from the standing of an area. For example, while a lifeguard station may have ongoing active standing (not obsolete or frozen), the station may only be active 9 months of the year. For remaining three months of the year, the area’s status is non-active. A field the user may fill using the fixed lexicon [X_WORK_AREA_STATUS].
;Work Area Type: The ‘Work Area Type’ field allows the user to categorize [work areas|WORK AREAS]. Work_Area_Type is an optional field the user may fill using the user-defined lexicon [X_WORK_AREA_TYPE].
;Work Calendar: A day by day picture of days worked and days off that may repeat every "n" days. The field displays the work calendar code to be used for this work rule, if applicable. If no calendar is supplied, assume MON-FRI workweek
;Work Calendar Code:This field holds a user -defined time code that uniquely identifies the work calendar.
;Work Calendar Type: Indicates the type of work calendar. Work_Calendar_Type is a mandatory field the user must fill manually or through the fixed lexicon [X_WORK_CALENDAR_TYPE].
;Work Day Type: This field indicates the workday type this calendar date is. Work_Day_Type is a mandatory fixed lexicon [X_WORK_DAY_TYPE].
;Work Division: A subdivision of an operational entity in a physical location such as a plant, factory, mill, store, restaurant, theater, casino, police force, fire service, treatment plant, hospital, school or campus, overseen by a manager or director of operations. A [work division|WORK DIVISIONS] is generally subdivided into a number of work areas where work is performed. This field is a user defined code that uniquely identifies the [work division|WORK DIVISIONS], a subdivision within an entity.
;Work Division Status: Status is used to indicate whether an area is active at a SPECIFIC point in time, which is different from the standing. For example, while a lifeguard station may have ongoing active standing (not obsolete or frozen), the station may only be active 9 months of the year. For remaining three months of the year, the area’s status is non-active. Work_Division_Status is tied to the fixed lexicon [X_WORK_DIVISION_STATUS].
;Work In Progress: If the Work in Progress toggle is ON, this pay line is considered a WIP transaction, which will be journalized to the Work in Progress account of the general ledger, instead of the payroll clearing account. If the toggle is OFF, the pay line is a not journalized as work in progress.
;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.
;Work Order: An order for a quantity of work to be done, handled as special cost centers.
;Work Preference:Records any shift or work related employee preferences.
;Work Restrictions:A list of employee constraints that must be taken into consideration during scheduling.
;Work Rule:This is a user-defined time code that uniquely identifies the work rule.
;Work Station: A place within a work area that must be filled by a person or a team of people; usually based on machinery, equipment, posts or processes. This field is a user-defined code that uniquely identifies the workstation, a subdivision within a work area.
;Work Station Status: Status is used to indicate whether an area is active at a SPECIFIC point in time, which is different from the standing. For example, while a lifeguard station may have ongoing active standing (not obsolete or frozen), the station may only be active 9 months of the year. For remaining three months of the year, the area’s status is non-active. A field the user may fill using the fixed lexicon [X_WORK_STATION_STATUS].
;Work Station Type: The ‘Work Station Type’ field is used to let the user categorize workstations. Work_Station_Type is an optional field the user may fill using the user-defined lexicon [X_WORK_STATION_TYPE].
;Work Team: A set of employees that work together in a work station on the same shift rotation, often led by a team leader or lead hand, may be referred to as a crew, a squad, a work station complement. In a shift environment, each work station has its own work team for each shift. This field is a user-defined code that uniquely identifies the ‘Work Team’ employed in the Work Station or associated to the Team Post.
;WSE: The measure of full-time or part-time work to be done in a station post on one shift. This field will indicate the Work Shift Equivalent for this assignment.
\\
!![X|#24]
----
''No Terminology''
\\
!![Y|#25]
----
''No Terminology''
\\
!![Z|#26]
----
''No Terminology''\\
----
![Notes|Edit:Internal.TERMINOLOGY-TS]
[{InsertPage page='Internal.TERMINOLOGY-TS' default='Click to create a new notes page'}]
This page (revision-9) was last changed on 26-Nov-2021 10:22 by JEscottTop