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

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
43 26-Nov-2021 10:22 20 KB Karen Parrott to previous
42 26-Nov-2021 10:22 20 KB Karen Parrott to previous | to last
41 26-Nov-2021 10:22 20 KB Karen Parrott to previous | to last

Page References

Incoming links Outgoing links
IDPS
IDPS

Version management

Difference between version and

At line 1 changed 2 lines
!!!Positions
Positions are the building blocks of an organization chart that may be budgeted, filled and scheduled for work. These components define the structure required to run the organization’s operation. Positions are owned by an entity and associated with a department. They identify the need for a specific job to be done in a particular place in the organization, and the reporting relationships, requirements, work and pay rules, etc.
[{TableOfContents }]
At line 4 changed one line
Positions are optional; employees may be hired using job codes only. There are, however, a number of functions of the system that are based on position codes and budgets, therefore, it is recommended that positions be defined.
!!! DEFINE POSITIONS
At line 6 changed one line
Employees may be assigned to a position, either permanently through a work assignment record, or temporarily through a payroll transaction. An employee may hold one primary position and may also be authorized to perform the duties of other positions. An employee is hired into a position and the employee will inherit all the definitions from the position and job records.
Positions are the building blocks of an organization chart that may be budgeted, filled and scheduled for work. These components define the structure required to run the organization’s operation. Positions are owned by an entity and associated with a department. They identify the need for a specific job to be done in a particular place in the organization, and the reporting relationships, requirements, work and pay rules, etc.
At line 8 changed one line
One employee usually fills one position, whether it’s a full-time or part-time position. An employee may fill more than one position at a time (i.e. one-to-many). Sometimes two or more employees fill a single position, which may be known as job sharing (i.e. many-to-one).
Positions are optional; employees may be hired using job codes only. There are, however, a number of functions of the system that are based on position codes and budgets, therefore, it is recommended that positions be defined.
At line 10 changed one line
Occasionally, many employees fill a single position where the FTE (full time equivalent) total of the position is greater than one. This type of generic position is known as a pooled position. It is only used when the position's FTE requirements vary frequently (i.e. on a daily, weekly, seasonal or semester basis), making it infeasible to maintain such fluctuating requirements on an individual position per employee basis. In this situation, the FTE factor may be ignored entirely.
Employees may be assigned to a position, either permanently through a work assignment record, or temporarily through a payroll transaction. An employee may hold one primary position and may also be authorized to perform the duties of other positions. An employee is hired into a position and the employee will inherit all the definitions from the position and job records.
At line 11 added 4 lines
One employee usually fills one position, whether it’s a full-time or part-time position. An employee may fill more than one position at a time (i.e. one-to-many). Sometimes two or more employees fill a single position, which may be known as job sharing (i.e. many-to-one).
Occasionally, many employees fill a single position where the FTE (full time equivalent) total of the position is greater than one. This type of generic position is known as a pooled position. It is only used when the position's FTE requirements vary frequently (i.e. on a daily, weekly, seasonal or semester basis), making it infeasible to maintain such fluctuating requirements on an individual position per employee basis. In this situation, the FTE factor may be ignored entirely.
At line 14 changed one line
A position’s FTE factor is normally calculated by dividing the number of weekly hours scheduled for the position by the standard number of full-time weekly hours. An FTE factor of 1.0 indicates an employee is required to work full time to perform the responsibilities of that position. An FTE factor of less than 1.0 indicates an employee is only required to work part time to fulfill those responsibilities.
A position’s FTE factor is normally calculated by dividing the number of weekly hours scheduled for the position by the standard number of full-time weekly hours. An FTE factor of 1.0 indicates an employee is required to work full time to perform the responsibilities of that position. An FTE factor of less than 1.0 indicates an employee is only required to work part time to fulfill those responsibilities.
At line 16 changed one line
A vacant position may be considered to be a posting, a job opportunity or an opening within a department. A position is a potential commitment of resources by the organization, even if a budget has not been allocated or the position is still vacant.
A vacant position may be considered to be a posting, a job opportunity or an opening within a department. A position is a potential commitment of resources by the organization, even if a budget has not been allocated or the position is still vacant.
At line 18 changed one line
Position details are date sensitive. This means that as position information changes over time, a complete history of the position may be kept.
Position details are date sensitive. This means that as position information changes over time, a complete history of the position may be kept. Position records can be modified or deleted as necessary. If there is only one position record the Delete capability is removed.
At line 20 changed 2 lines
Position codes and names may be changed at any time and the effect of the changes will be seen immediately throughout the system.
Choosing a numbering scheme for position codes helps to minimize position changes when positions are upgraded, reclassified, or transferred to a different department, or when a whole department is moved to a different place in the organization chart due to restructuring.
Position codes and names may be changed at any time and the effect of the changes will be seen immediately throughout the system. Choosing a numbering scheme for position codes helps to minimize position changes when positions are upgraded, reclassified, or transferred to a different department, or when a whole department is moved to a different place in the organization chart due to restructuring.
At line 23 changed one line
You may build a structure within the position code but it is recommended to keep the structure as generic as possible. ''For example, do not include the department code in the position code structure. If there is a reorganization and a position is reclassified to another department, you will have to change the position code and the position history will be lost since it is associated to the “old” position code. ''
You may build a structure within the position code but it is recommended to keep the structure as generic as possible. ''For example, do not include the department code in the position code structure. If there is a reorganization and a position is reclassified to another department, you will have to change the position code and the position history will be lost since it is associated to the “old” position code. ''
At line 25 changed one line
Position codes may be automatically numbered through the sequence function or manually assigned by the user.
Position codes may be automatically numbered through the sequence function or manually assigned by the user.
At line 27 changed one line
;[Define Code Sequences|CODE_SEQUENCES]:A sequence is a process that allows the users to have the system automatically assign codes to various records. Code sequences are defined on the Define Code Sequences [(IMCS)] form.
If a user defined field(UDF) is established on a the position details table [P2K_CM_POSITION_DETAILS] and a matching user defined field is established on the work assignment details table [P2K_HR_ASSIGNMENT_DETAILS], then values stored in the UDF on the position table will default into the UDF on the work assignment table when employees are hired or transferred.
At line 29 changed 13 lines
The employee code and position code, among other codes, may be defined as system generated. \\
\\
If a sequence record exists for the field, a code will be assigned by the system. If there is no sequence record defined, the user will have to specify the code. \\
\\
Manually assigned numbers may be used with sequences. The manually assigned number must be within the start/end range and less than the last system assigned number.\\
\\
If this is an option that you would like to pursue then please make a note to bring it up during the System Administration training.\\
\\
!‘Maintain Positions’ Usage and Examples\\
\\
Position data is stored in the [P2K_CM_POSITIONS] and ]P2K_CM_POSITION_DETAILS] tables.
\\
;[Position|POSITION_CODE]:The position code is the number, reference code or abbreviation that uniquely identifies this position within the organization. Position_Code is a 16-character alphanumeric mandatory field you must manually enter or may be auto-generated by HHRMePersonality.
! Define Code Sequences:
At line 43 changed one line
;[Part Of Position|POSITION_CODE]:For experience tracking purposes, a position may be part of another generic position code. Position_Code is a 16-character alphanumeric mandatory field you must manually enter or may be auto-generated by HHRMePersonality.
A sequence is a process that allows the users to have the system automatically assign codes to various records. Code sequences are defined on the Define Code Sequences (
At line 45 changed one line
;[Entity|ENTITY_CODE]:This field displays the entity to which the position belongs. Entity_Code from [IDEN][(P2K_CM_ENTITIES)] is a 16-character alphanumeric mandatory field.
[IMCS]) form. The employee code and position code, among other codes, may be defined as system generated. If a sequence record exists for the field, a code will be assigned by the system. If there is no sequence record defined, the user will have to specify the code. Manually assigned numbers may be used with sequences. The manually assigned number must be within the start/end range and less than the last system assigned number.
At line 47 changed one line
;[Standing|STANDING]:Standing is used to indicate whether the record is active, frozen or obsolete. Active will default. Standing is an optional fixed lexicon [(X_STANDING)].
Position data is stored in the [P2K_CM_POSITIONS] and [P2K_CM_POSITION_DETAILS] tables.
At line 49 changed 3 lines
!!Define Positions (IDPS) - Definition
;[Title|POSITION_TITLE]:This field displays the official or formal title of the position, defaulted from the job title.
Position_Title is a 50-character alphanumeric mandatory field.
;[Position|POSITION_CODE]:The position code is the number, reference code or abbreviation that uniquely identifies this position within the organization.
At line 41 added 14 lines
;[Part Of Position|POSITION_CODE]:For experience tracking purposes, a position may be part of another generic position code.
;[Entity|ENTITY_CODE]:This field displays the entity to which the position belongs.
;[Standing]:Standing is used to indicate whether the record is active, frozen or obsolete. Active will default.
 
----
!! Definition tab
;[Title|POSITION_TITLE]:This field displays the official or formal title of the position, defaulted from the job title.
At line 54 removed one line
Description_1 is a 50-character alphanumeric optional field.
At line 56 changed one line
;[Description 2|DESCRIPTION_2]:This field provides a further description of the position. Description_2 is a 50-character alphanumeric optional field.
;[Description 2|DESCRIPTION_2]:This field provides a further description of the position.
At line 58 changed one line
;[Provide Public Service|PROVIDE_PUBLIC_SERVICE]:This toggle indicates if the position is to be reported as ‘Provide Public Service’ on specific government reports (e.g. Official Language Report - REOLA). If this toggle is checked on IEAS, it will be checked on this screen. Provide_Public_Service is an optional toggle field.
;[Provide Public Service|PROVIDE_PUBLIC_SERVICE]:This toggle indicates if the position is to be reported as ‘Provide Public Service’ on specific government reports (e.g. Official Language Report - REOLA). If this toggle is checked on [IEAS], it will be checked on this screen.
At line 60 changed one line
;[Provide Internal Service|PROVIDE_INTERNAL_SERVICE]:This toggle indicates if the position is to be reported as ‘Provide Internal Service’ on specific government reports (e.g. Official Language Report - REOLA). If this toggle is checked on IEAS, it will be checked on this screen. Provide_Internal_Service is an optional toggle field.
;[Provide Internal Service|PROVIDE_INTERNAL_SERVICE]:This toggle indicates if the position is to be reported as ‘Provide Internal Service’ on specific government reports (e.g. Official Language Report - REOLA). If this toggle is checked on [IEAS], it will be checked on this screen.
At line 62 changed 2 lines
;[Supervisory|PROVIDE_PUBLIC_SERVICE]:This toggle indicates if the position is to be reported as ‘Supervisory’ on specific government reports (e.g. Official Language Report - REOLA). If this toggle is checked on IEAS, it will be checked on this screen.
Supervisory is an optional toggle field.
;[Supervisory]:This toggle indicates if the position is to be reported as ‘Supervisory’ on specific government reports (e.g. Official Language Report - REOLA). If this toggle is checked on [IEAS], it will be checked on this screen.
At line 65 changed 2 lines
!Definition
;[Unit|UNIT_CODE]:This field displays the name of the unit to which this position belongs. Unit_Code from [IDUN] [(P2K_CM_UNITS)] is a 16-character alphanumeric mandatory field you must manually enter or retrieve from the LOV.
! Definition
At line 68 changed one line
;[Job|JOB_CODE]:This field displays the job on which the position is based. Job_Code from [IDJB] [(P2K_CM_JOBS)] is a 16-character alphanumeric mandatory field.
;[Unit|UNIT_CODE]:This field displays the name of the unit to which this position belongs. \\ \\%%information Please note that information for the Unit field will not default in when the Job field is filled in./%
At line 70 changed one line
;[Department|DEPARTMENT_CODE]:This field displays the department in which the tasks take place. Department_Code from [IDDP] [(P2K_CM_DEPARTMENTS)] is a 16-character alphanumeric mandatory field.
;[Job|JOB_CODE]:This field displays the job on which the position is based.
At line 72 changed one line
;[Group|GROUP_CODE]:This field displays the group to which the position belongs. Group_Code from [IDGR] [(P2K_CM_GROUPS)] is a 16-character alphanumeric mandatory field.
;[Department|DEPARTMENT_CODE]:This field displays the department in which the tasks take place.
At line 74 changed one line
;[Work Rule|WORK_RULE_CODE]:Work rules are used to determine standard payroll processing information required to create pay headers and transactions for an employee. The value in this field is inherited from the job, department or group in that order. The value may, however, be overridden. Work_Rule_Code from [IDWR] [(P2K_CM_WORK_RULES)] is a 16-character alphanumeric optional field.
;[Group|GROUP_CODE]:This field displays the group to which the position belongs.
At line 76 changed one line
;[Auth Area|AUTHORIZATION_CODE]:The authorization area is a security feature that enables an organization to control access to information for this position. Authorization_Code from [IDAA] [(P2K_AUTHORIZATION_AREAS)] is a 16-character alphanumeric optional field.
;[Work Rule|WORK_RULE (Field)]:Work rules are used to determine standard payroll processing information required to create pay headers and transactions for an employee. The value in this field is inherited from the job, department or group in that order. The value may, however, be overridden.
At line 78 changed one line
;[Location|LOCATION_CODE]:This is the location where the tasks are being performed. Location_Code from [IDLN][(P2K_CM_LOCATIONS)] is a 16-character alphanumeric mandatory field.
;[Auth Area|AUTHORIZATION_CODE]:The authorization area is a security feature that enables an organization to control access to information for this position.
At line 80 changed one line
;[Send Pays To|LOCATION]:This field identifies the location where an employee's pay checks should be sent. May be left blank if the pays are to be sent to the employee’s ‘work out of’ location. This field may be used for sorting pay advices by location. Location from [IDLN] [(P2K_CM_LOCATIONS)] is a 16-character alphanumeric optional field.
;[Location|LOCATION_CODE]:This is the location where the tasks are being performed.
At line 82 changed one line
;[Job Family|JOB_FAMILY]:Job Family is a grouping of jobs used to aid the flex positions functionality. This field allows you to limit the values of the Job LOV on the assignment details to those jobs that matched the identifiers attached to the position that has been assigned to the employee. Job_Family is an optional 200 alphanumeric character field.
;[Send Pays To|LOCATION_CODE]:This field identifies the location where an employee's pay checks should be sent. May be left blank if the pays are to be sent to the employee’s ‘work out of’ location. This field may be used for sorting pay advices by location.
At line 84 changed 2 lines
!Classification
;[Manager|PERSON_CODE]:This is the employee to whom this position reports. This field may need to be completed after employees have been entered into the system. Person_Code from [IEID] [(P2K_HR_IDENTITIES)] is a 16-character alphanumeric optional field.
;[Job Family|JOB_FAMILY]:Job Family is a grouping of jobs used to aid the flex positions functionality. This field allows you to limit the values of the Job LOV on the assignment details to those jobs that matched the identifiers attached to the position that has been assigned to the employee.
At line 87 changed one line
;[Reports To Position|POSITION_CODE]:This is the position to which this position reports. This field may be defaulted from the position identified as the department manager's position, but may be overridden Position_Code from [IDPS] [(P2K_CM_POSITIONS)] is a 16-character alphanumeric optional field.
! Classification
At line 89 changed one line
;[First Manager|PERSON_CODE]:This is a derived field based on hierarchical information in the system to show the user what the system will use when the "First Manager" option is chosen in approvals. The order of determination starts with what is entered as the ‘Reports To’ person on the assignment itself.
;[Manager|PERSON_CODE]:This is the employee to whom this position reports. This field may need to be completed after employees have been entered into the system.
At line 91 changed one line
;[Org Chart Level|ORG_CHART_LEVEL]:Level or tier of the organization chart on which this position should appear. This level is used to control the layout within Organization Charting software, such as Aquire Org Publisher, and is returned as "Level Number" in the Org Publisher views. Org_Chart_Level is an optional user-defined lexicon [(X_ORG_CHART_LEVEL)].
;[Reports To Position|POSITION_CODE]:This is the position to which this position reports. This field may be defaulted from the position identified as the department manager's position, but may be overridden
At line 93 changed one line
;[Responsibility Level|RESPONSIBILITY_LEVEL]:Responsibility level is a security feature used to control access to an employee's information. When an employee is hired or transferred, the responsibility level is inherited from the position, but the user may override it. Only a user whose responsibility access matches or is higher than the responsibility level on the employee's assignment record will be able to access that employee. The hierarchy of the responsibility levels is based on the saved value in the lexicon [(X_RESPONSIBILITY_LEVEL)]. Responsibility_Level is an optional fixed lexicon [(X_RESPONSIBILITY_LEVEL)].
;[First Manager|DRV_FIRST_MANAGER_EID]:This is a derived field based on hierarchical information in the system to show the user what the system will use when the "First Manager" option is chosen in approvals. The order of determination starts with what is entered as the ‘Reports To’ person on the assignment itself.
At line 93 added 4 lines
;[Org Chart Level|ORG_CHART_LEVEL]:Level or tier of the organization chart on which this position should appear. This level is used to control the layout within Organization Charting software, such as Aquire Org Publisher, and is returned as "Level Number" in the Org Publisher views.
;[Responsibility Level|RESPONSIBILITY_LEVEL]:Responsibility level is a security feature used to control access to an employee's information. When an employee is hired or transferred, the responsibility level is inherited from the position, but the user may override it. Only a user whose responsibility access matches or is higher than the responsibility level on the employee's assignment record will be able to access that employee. The hierarchy of the responsibility levels is based on the saved value in the lexicon ([X_RESPONSIBILITY_LEVEL]).
At line 96 removed one line
Language_Class is an optional user-defined lexicon [(X_LANGUAGE_CLASS)].
At line 98 changed one line
;[Industry|INDUSTRY_CODE]:This field displays the user-defined industry code. Industry_Code from [IDIN] [(P2K_CM_INDUSTRIES)] is a 16-character optional alphanumeric field.
;[Industry|INDUSTRY_CODE]:This field displays the user-defined industry code.
At line 100 changed one line
;[Occupation|OCCUPATION_CODE]:Occupation is a user-definable occupation code which is defined in the IDOC form. Occupation_Code from [IDOC] [(P2K_CM_OCCUPATIONS)] is an optional user-defined table.
;[Occupation|OCCUPATION_CODE]:This field displays the user-defined occupation code.
At line 102 changed 2 lines
[Job Profile|JOB_PROFILE_CODE]:Job Profiles is the ‘job posting’ information that is linked to the Recruitment application.
Job_Profile_Code from [IDJB] [(P2K_RE_JOB_PROFILES)] is an optional user-defined table.
;[Job Profile|JOB_PROFILE_CODE]:[Job Profiles] is the ‘job posting’ information that is linked to the Recruitment application.
At line 105 changed 5 lines
!!Define Positions (IDPS) - Compensation
!Work Arrangement
;[Authorized FTE|AUTHORIZED_FTE]:This field displays the number of full time equivalent positions for which a commitment has been made by the organization. Used by the Forecasting and Costing application to determine the total number of individuals needed.
This field is also used by position control logic to ensure that you do not exceed the employee count, based upon the FTE Override rule chosen. Authorized_FTE is an optional numeric field.
 
At line 111 changed 2 lines
;[Default FTE|DEFAULT_FTE]:This is the default full time equivalence of positions for which a commitment has been made by the organization. Used by the Forecasting and Costing application to determine the FTE value of an individual budget seat.
This field is also used in the creation of postings for the RE module, and used as the default FTE value to be applied if an employee is placed into this position. Default_FTE is an optional numeric field.
----
At line 109 added 8 lines
!! Compensation tab
! Work Arrangement
;[Authorized FTE|AUTHORIZED_FTE]:This field displays the number of full time equivalent positions for which a commitment has been made by the organization. This field is used by the Forecasting and Costing application to determine the total number of individuals needed. This field is also used by position control logic to ensure that you do not exceed the employee count, based upon the FTE Override rule chosen.
;[Default FTE|DEFAULT_FTE]:This is the default full time equivalence of positions for which a commitment has been made by the organization. This field is used by the Forecasting and Costing application to determine the FTE value of an individual budget seat. This field is also used in the creation of postings for the Recruiting module, and used as the default FTE value to be applied if an employee is placed into this position.
At line 115 removed 3 lines
*May not exceed FTE
*Warn if FTE exceeded
*May exceed FTE\\FTE_ Override_ Rule is an optional fixed lexicon [(X_FTE_OVERRIDE_RULE)].
At line 119 changed one line
;[Std Hrs/Week|STD_HOURS_PER_WEEK]:This field shows the standard hours per week required for this position. The hours are inherited from the work rule, group or job in that order. The value may, however, be overridden. Std_Hours_Per_Week is an optional numeric field.
;[Std Hrs/Week|STD_HOURS_PER_WEEK]:This field shows the standard hours per week required for this position. The hours are inherited from the work rule, group or job in that order. The value may, however, be overridden.
At line 121 changed one line
;[Std Hrs/Day|STD_HOURS_PER_DAY]:This field shows the standard hours per day required for this position. The hours are inherited from the work rule, group or job in that order. The value may, however, be overridden. Std_Hours_Per_Day is an optional numeric field.
;[Std Hrs/Day|STD_HOURS_PER_DAY]:This field shows the standard hours per day required for this position. The hours are inherited from the work rule, group or job in that order. The value may, however, be overridden.
At line 123 changed one line
;[Std Hrs/Pay|STD_HOURS_PER_PAY]:This field shows the standard hours per pay period required for this position. The hours are inherited from the work rule, group or job in that order. The value may, however, be overridden. Std_Hours_Per_Pay is an optional numeric field.
;[Std Hrs/Pay|STD_HOURS_PER_PAY]:This field shows the standard hours per pay period required for this position. The hours are inherited from the work rule, group or job in that order. The value may, however, be overridden.
At line 125 changed 2 lines
!Position Control
;[Suspended|SUSPENDED_DATE]:This date field indicates when the position was suspended. Suspended_Date is an optional date field.
! Position Control
At line 128 changed one line
;[Abolished|ABOLISHED_DATE]:This date field indicates when the position was abolished. Abolished_Date is an optional date field.
;[Status|POSITION_STATUS]:This field indicates whether the position is approved, not approved or obsolete.
At line 130 changed one line
;[Budget Rule|BUDGET_RULE]:This field indicates whether the position is budgeted, not budgeted or encumbered. Budget_Rule is an optional date field.
;[Approved On|APPROVED_DATE]:The date the approval was given is indicated in this field.
At line 132 changed 2 lines
!Compensation
;[Salary Range|RANGE_CODE}]: This field displays the salary or wage range that will be used to default to an employee’s assignment record. Salary range is defaulted from the Job definition, however, it may be overridden. Range_Code from [ISSR] [(P2K_SA_SALARY_RANGES)]is a 16-character alphanumeric optional field.
;[Approved By|APPROVED_BY]:This field indicates who gave the approval.
At line 135 changed one line
;[Scale|SCALE_CODE] [Step|STEP_CODE]:This field displays the scale/step code that will be used to default to an employee's assignment record. Scale Code and Step Code are defaulted from the Job definition, and may be overridden. Scale_Code and Step_Code from [ISSR][(P2K_SA_WAGE_SCALES)] and [(P2K_SA_WAGE_SCALE_STEPS)] is a combined 16-character alphanumeric optional field.
;[Suspended|SUSPENDED_DATE]:This date field indicates when the position was suspended.
At line 137 changed one line
;[Wage Rate|WAGE_RATE]:This field shows the standard salary or wage amount allocated for this position. It is usually the starting salary or wage that is entered, or the currently budgeted rate, rather than the amount that employee who fills the position is receiving. Wage Rate is defaulted from the Scale/Step definition, if provided or from the job definition. This value, however, may be overridden. Wage_Rate is an optional numeric field.
;[Abolished|ABOLISHED_DATE]:This date field indicates when the position was abolished.
At line 139 changed one line
;[Rate Basis|RATE_BASIS]:The rate basis is the unit of measure in which the associate wage rate is being stored or displayed (i.e.hourly, weekly, biweekly, semi-monthly, monthly or annually). Rate Basis is defaulted from the Scale/Step definition, if provided or from the job or salary range definition. Rate_Basis is a mandatory fixed lexicon [(X_RATE_BASIS)].
;[Budget Rule|BUDGET_RULE]:This field indicates whether the position is budgeted, not budgeted or encumbered.
At line 141 changed one line
;[Fulltime Wage|USE_FTE_WAGES]:If the FTE indicated in the Work Arrangement area is less than 1.00, this toggle will indicate if the displayed salary or wage should be converted to a Full Time Equivalent factor (FTE). This value is defaulted from the group definition. Suppose an employee has an FTE of 0.5 and the wage rate indicated is $4,000. If the toggle is OFF, this means that the employee will actually receive the full $4,000. If the toggle is turned ON, the displayed salary or wage is the 1.00 Full Time Equivalent amount. This means that in this case, where the FTE is 0.5, the employee will receive $2,000. Use_FTE_Wages is an optional toggle field.
! Compensation
At line 143 changed one line
;[Overtime Exempt|OVERTIME_EXEMPT]:If the toggle is ON, overtime is NOT payable for this position. If the toggle is OFF, overtime is payable for this position. Overtime Exempt is defaulted from the job definition. This field is for documentation purposes only and the information displayed will not be used for processing. Overtime_Exempt is an optional toggle field.
;[Salary Range|RANGE_CODE]: This field displays the salary or wage range that will be used to default to an employee’s assignment record. Salary range is defaulted from the Job definition, however, it may be overridden.
At line 145 changed 2 lines
!Review
;[Position Type|POSITION_TYPE]:This field shows the type (i.e. executive, management, supervisory, etc.) of position being defined. This field is used in several legislated reports for the categorization of employees (EMIS, TWC) Position_Type is an optional user-defined lexicon [(X_POSITION_TYPE)].
;[Scale|SCALE_CODE] [Step|STEP_CODE]:This field displays the scale/step code that will be used to default to an employee's assignment record. Scale Code and Step Code are defaulted from the Job definition, and may be overridden.
At line 148 changed one line
;[WC Class|WCB_CLASS]:This field shows the Workers’ Compensation classification used to determine the WC category for reporting and WC contribution. This field is defaulted in from the job definition. WC registrations and rates are defined by WCB_CLASS on the Maintain Workers Compensation Information (IPWC) form. This field is defaulted from the job definition. WCB_Class is an optional user-defined lexicon [(X_WCB_CLASS)].
;[Wage Rate|WAGE_RATE]:This field shows the standard salary or wage amount allocated for this position. It is usually the starting salary or wage that is entered, or the currently budgeted rate, rather than the amount that employee who fills the position is receiving. Wage Rate is defaulted from the Scale/Step definition, if provided or from the job definition. This value, however, may be overridden.\\ \\The Preference 'DEFAULT_RANGE_MIDPOINT', when set to Y, will cause the Wage Rate to be set to the Midpoint value from the Salary Range on the Job.
At line 150 changed one line
;[Last Review|LAST_REVIEW_DATE]:This date field indicates the last time the position was reviewed. Last_Review_Date is an optional date.
;[Rate Basis|RATE_BASIS]:The rate basis is the unit of measure in which the associate wage rate is being stored or displayed (i.e.hourly, weekly, biweekly, semi-monthly, monthly or annually). Rate Basis is defaulted from the Scale/Step definition, if provided or from the job or salary range definition.
At line 152 changed one line
;[Points|POSITION_POINTS]:For the purposes of using salary ranges ‘by formula’, position points may be assigned. Position_Points is an optional field you may manually enter.
;[Fulltime Wage|USE_FTE_WAGES]:If the FTE indicated in the Work Arrangement area is less than 1.00, this toggle will indicate if the displayed salary or wage should be converted to a Full Time Equivalent factor (FTE). This value is defaulted from the group definition. Suppose an employee has an FTE of 0.5 and the wage rate indicated is $4,000. If the toggle is OFF, this means that the employee will actually receive the full $4,000. If the toggle is turned ON, the displayed salary or wage is the 1.00 Full Time Equivalent amount. This means that in this case, where the FTE is 0.5, the employee will receive $2,000.
At line 154 changed one line
;[Evaluation Points| ]:This field displays the amount of evaluation points awarded to this position in order determine a salary range.
;[Overtime Exempt|OVERTIME_EXEMPT]:If the toggle is ON, overtime is NOT payable for this position. If the toggle is OFF, overtime is payable for this position. Overtime Exempt is defaulted from the job definition. This field is for documentation purposes only and the information displayed will not be used for processing.
At line 156 changed 2 lines
;[Assignment Required|ASSIGNMENT_REQUIRED]:If the toggle is ON, an employee must have a work assignment record (i.e. an authorization) that permits them to work in this position. Without one, the system will not allow their hours to be keyed against the position. If the toggle is OFF, an employee does not need an assignment record to be able to work in this position.
Assignment Required is defaulted from the job definition. Assignment_Required is an optional toggle field.
! Review
At line 159 changed 2 lines
!!Define Positions (IDPS) - Premiums
;[Premium|PREMIUM_CODE]: This field holds the user-defined premium code that uniquely identifies this premium within the organization. Premium_Code from [ISPM] [(P2K_SA_PREMIUMS)]is a mandatory LOV field.
;[Position Type|POSITION_TYPE]:This field shows the type (i.e. executive, management, supervisory, etc.) of position being defined. This field is used in several legislated reports for the categorization of employees (EMIS, TWC).
At line 162 changed one line
;[Premium Rate|[PREMIUM_RATE]:This field shows the premium rate that is defaulted from this premium. Premium_Rate from [ISPM] [(P2K_SA_PREMIUM_DETAILS)] is an optional field.
;[WC Class|WCB_CLASS]:This field shows the Workers’ Compensation classification used to determine the WC category for reporting and WC contribution. This field is defaulted in from the job definition. WC registrations and rates are defined by WCB_CLASS on the Maintain Workers Compensation Information ([IPWC]) form. This field is defaulted from the job definition.
At line 164 changed one line
;[Basis|RATE_BASIS]:The rate basis is the unit of measure in which the associated rate is being stored or displayed for the defaulted premium rate. For example: hourly, weekly, biweekly, semi-monthly, monthly, or annual. Rate_Basis from [ISPM] [(P2K_SA_PREMIUM_DETAILS)] is an optional fixed lexicon [(X_RATE_BASIS)].
;[Review Type|REVIEW_TYPE_CODE]:This field will define the type of review (e.g. Yearly, Merit, Bonus, etc.) being performed.
At line 166 changed one line
;[Override Rate|PREMIUM_RATE]:The user may enter the override rate that applies to this premium. Premium_Rate from [ISPM] [(P2K_SA_PREMIUM_USAGES)] is an optional field you may use to override the defaulted premium rate.
;[Last Review|LAST_REVIEW_DATE]:This date field indicates the last time the position was reviewed.
At line 168 changed one line
;[Override Rate Basis|RATE_BASIS]:The rate basis is the unit of measure in which the associated rate is being stored or displayed for the overridden rate. Rate_Basis from [ISPM] [(P2K_SA_PREMIUM_USAGES)] is an optional fixed lexicon [(X_RATE_BASIS)] you may use to override the overridden rate basis.
;[Points|POSITION_POINTS]:For the purposes of using salary ranges ‘by formula’, position points may be assigned.
At line 170 changed one line
!!Define Positions (IDPS) - Distributions
;%%( text-decoration: underline; )Evaluation Points/%:This field displays the amount of evaluation points awarded to this position in order determine a salary range.
At line 172 changed one line
;[Sequence #|SPLIT_SEQUENCE]:This field defines the sequential order of the distribution codes for this position . The user may define one or multiple distribution codes with splits. Split_Sequence from [(P2K_CM_DISTRIBUTIONS)] is a 5 digit mandatory field.
;[Assignment Required|ASSIGNMENT_REQUIRED]:If the toggle is ON, an employee must have a work assignment record (i.e. an authorization) that permits them to work in this position. Without one, the system will not allow their hours to be keyed against the position. If the toggle is OFF, an employee does not need an assignment record to be able to work in this position. Assignment Required is defaulted from the job definition.
At line 174 changed 2 lines
;[Distribution Code|DISTRIBUTION_CODE]:This field shows part or all of the distribution code receiving the portion of costs. This is normally the distribution of the wages associated with the position. Distribution_Code from [(P2K_CM_DISTRIBUTION)] is a 50 character alphanumeric mandatory field.\\The Distribution Editor button in the Distribution tab form on position provides an editor to aid in the creation of the correct distribution code. The information displayed in the Distribution Editor is based on the set up in the G/L Segments form. If segment values are completed for a segment and the ‘Must Validate’ toggle is on, then an LOV will be provided. As each segment is chosen the segments will be concatenated in a display at the bottom of the form.
When you are satisfied with the distribution created, choose ‘Return Code’. This will take the full or partial distribution and place it back on the previous form in the Distribution field. If you do not want the newly created distribution to be returned to the previous form then they may choose ‘Cancel Edit’.
 
At line 177 changed one line
;[Split Rule|SPLIT_RULE]:The distribution split rule indicates whether the distribution is being split by a percentage, by flat amount or by a Distribution pick list of authorized assignments. There are several choices that may be made, although all these values are specifically used for defaulting down to lower levels. Split_Rule from [(P2K_CM_DISTIRBUTIONS)] is an optional fixed lexicon [(X_SPLIT_RULE)] you may use to look up the value.
----
At line 179 changed one line
;[Dist %|SPLIT_PERCENT]:If the split rule is ‘by percent’ then indicate the percent in this field. You must enter the percentage has a whole number, not a decimal. For example, to indicate 6% you would enter 6, not .06 Split_Percent from [(P2K_CM_DISTRIBUTIONS)] is a 5-digit optional percentage field.
!! Premiums tab
At line 181 changed one line
;[User%|USER_PERCENT]:This value in this field is for display purposes only and is defaulted once the Dist % is complete. User_Percent from [(P2K_CM_DISTRIBUTIONS)] is a 5-digit optional percentage field.
;[Premium|PREMIUM_CODE]: This field holds the user-defined premium code that uniquely identifies this premium within the organization.
At line 183 changed one line
;[Amount|SPLIT_AMOUNT]:If the split rule is ‘by amount’ then indicate the amount in this field. Split_Amount from [(P2K_CM_DISTRIBUTIONS)] is an 18 digit optional numeric field.
;[Premium Rate|PREMIUM_RATE]:This field shows the premium rate that is defaulted from this premium.
At line 185 changed one line
;[Start Date|START_DATE]:For Distribution Pick Lists, this is the start date from this distribution may be used. For Funds, this is the start date that the fund becomes available. Start_Date from [(P2K_CM_DISTRIBUTIONS)]is an 18 digit optional numeric field.
;[Basis|RATE_BASIS]:The rate basis is the unit of measure in which the associated rate is being stored or displayed for the defaulted premium rate. For example: hourly, weekly, biweekly, semi-monthly, monthly, or annual.
At line 187 changed one line
;[End Date|END_DATE]:For Distribution Pick Lists, this is the last date that this distribution mat be used. For funds, this is the end of that fund's availability. End_Date from [(P2K_CM_DISTRIBUTIONS)]is an 18 digit optional numeric field.
;[Override Rate|PREMIUM_RATE]:The user may enter the override rate that applies to this premium.
At line 189 changed 3 lines
;[Fund|] / [Description|] / [Program|] /[Responsible Person| ]
These fields are used in Fund processing.
They are defaulted from the fund definition and may not be changed.
;[Override Rate Basis|RATE_BASIS]:The rate basis is the unit of measure in which the associated rate is being stored or displayed for the overridden rate.
 
----
!! Distributions tab
;[Sequence #|SPLIT_SEQUENCE]:This field defines the sequential order of the distribution codes for this position . The user may define one or multiple distribution codes with splits.
;[Distribution Code|DISTRIBUTION_CODE]:This field shows part or all of the distribution code receiving the portion of costs. This is normally the distribution of the wages associated with the position. The Distribution Editor button in the Distribution tab form on position provides an editor to aid in the creation of the correct distribution code. The information displayed in the Distribution Editor is based on the set up in the G/L Segments form. If segment values are completed for a segment and the ‘Must Validate’ toggle is on, then an LOV will be provided. As each segment is chosen the segments will be concatenated in a display at the bottom of the form. When you are satisfied with the distribution created, choose ‘Return Code’. This will take the full or partial distribution and place it back on the previous form in the Distribution field. If you do not want the newly created distribution to be returned to the previous form then they may choose ‘Cancel Edit’.
;[Split Rule|SPLIT_RULE]:The distribution split rule indicates whether the distribution is being split by a percentage, by flat amount or by a Distribution pick list of authorized assignments. There are several choices that may be made, although all these values are specifically used for defaulting down to lower levels.
;[Dist %|SPLIT_PERCENT]:If the split rule is ‘by percent’ then indicate the percent in this field. You must enter the percentage has a whole number, not a decimal. For example, to indicate 6% you would enter 6, not .06
;[User%|USER_PERCENT]:This value in this field is for display purposes only and is defaulted once the Dist % is complete.
;[Amount|SPLIT_AMOUNT]:If the split rule is ‘by amount’ then indicate the amount in this field.
;[Start Date|START_DATE]:For Distribution Pick Lists, this is the start date from this distribution may be used. For Funds, this is the start date that the fund becomes available.
;[End Date|END_DATE]:For Distribution Pick Lists, this is the last date that this distribution mat be used. For funds, this is the end of that fund's availability.
;[Fund|GL_FUND_CODE] / [Description] / [Program|PROGRAM_CODE] /[Responsible Person|PERSON_CODE]
These fields are used in Fund processing. They are defaulted from the fund definition and may not be changed.
 
----
!! Budget tab
This tab is currently not being populated or used.
 
----
!! Manager tab
This is where the employee may define the manager of this position. The manager is definable by either specifying a person or a position it reports to. The incumbent of that position is the manager. Entities where a 1 to 1 relationship (position to employee) exist will be obvious who the first manager is. Entities with multiple people in the managing position will have the most senior employee derived from their assignment start date and will be listed as the first manager. All active incumbents will be listed in the table on the lower half of this tab.
 
----
! [Notes|Edit:Internal.IDPS]
[{InsertPage page='Internal.IDPS' default='Click to create a new notes page'}]
This page (revision-43) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop