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

This page was created on 26-Nov-2021 10:22 by UnknownAuthor

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
53 26-Nov-2021 10:22 22 KB Karen Parrott to previous
52 26-Nov-2021 10:22 21 KB kparrott to previous | to last
51 26-Nov-2021 10:22 21 KB kparrott to previous | to last
50 26-Nov-2021 10:22 21 KB kparrott to previous | to last
49 26-Nov-2021 10:22 21 KB kparrott to previous | to last
48 26-Nov-2021 10:22 21 KB kparrott to previous | to last
47 26-Nov-2021 10:22 21 KB lurtan to previous | to last
46 26-Nov-2021 10:22 21 KB kparrott to previous | to last
45 26-Nov-2021 10:22 21 KB kparrott to previous | to last
44 26-Nov-2021 10:22 21 KB kparrott to previous | to last
43 26-Nov-2021 10:22 20 KB kparrott to previous | to last
42 26-Nov-2021 10:22 21 KB kparrott to previous | to last
41 26-Nov-2021 10:22 20 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
PEAS
PEAS

Version management

Difference between version and

At line 5 added 12 lines
The Maintain Assignment Information (PEAS) form allows you to view information related to an employee's assignment.
Maintain Assignment Information data is stored in the [P2K_HR_ASSIGNMENTS], [P2K_SA_PERSONNEL_ACTIONS], [P2K_HR_ASSIGNMENT_DETAILS], [P2K_SA_PREMIUM_USAGES] and [P2K_CM_DISTRIBUTIONS] tables.
Handling of Distributions and Premiums
*Defaulting will be carried forward to future records when in context. Defaulting of the distribution can come from the Job / Position, and will be done.
*Manual overrides will not be carried forward (Message will be issued.) Changes to distribution made directly on the DISTRIBUTION tab will be applied on current record, but will not be carried forward to future records.
*PAs with an effective date that fall on a past effective split record where a premium was added without changing assignment information, will receive the future update warning message. Premium(s) will only be applied to future record when none exist on future records.
**If 1 or more premiums exist, the message will be given to the user to manually adjust future records.
\\
At line 6 changed 7 lines
;[PA#|PA_NUMBER]:
;[Change Reason|CHANGE_CODE]:
;[Takes Effect|]:
;[PA Expiry Date|]:
;[New Effective|]:
;[Initiate PA|]:
;[Cancel PA|]:
;[PA#|PA_NUMBER]:This field identifies a personal action associated with the assignment.
;[Change Reason|CHANGE_CODE]:This field allows you to track why information has been created or changed as of an effective date.
;[Takes Effect|PA_EFFECTIVE_DATE]:The date the personal action becomes effective is displayed in this field.
;[PA Expiry Date|PA_EXPIRY_DATE]:The date the personal action ends is displayed in this field.
;[New Effective|PA_EXPIRY_DATE]:This field displays an optional date field which shows the last date the PA is effective.
;[Initiate PA|ACT_INITIATE_PA]:This is an action button which allows the user to initiate a [Personnel Action|PERSONNEL ACTION] for the employee in focus.
;:By pressing the Initiate PA button, the [Create Personnel Action|MSCPA] dialog box will appear requesting initial information for the [PA|PERSONNEL ACTION].
;[Cancel PA|ACT_CANCEL_PA]:The PA may be canceled by pressing this button, once pressed the status will change to 'Cancelled'.
At line 36 added 3 lines
;[Wage Progress Date|WAGE PROGRESSION]:The Wage Progress Date field can be used in conjunction with the lexicon option Wage Progression Date in the Step_Base_Date field in ISRS to manage employee wage/scale stepping.
At line 24 changed one line
\\ \\
\\
At line 27 removed 2 lines
!Definition
;[Position|POSITION_CODE]:This is the position to which the employee is assigned. Position_Code from [IDPS]
At line 44 added 2 lines
;[Position|POSITION_CODE]:This is the position to which the employee is assigned.
At line 42 changed one line
;[Work Rule|WORK_RULE_CODE]:Work rules are used to determine the standard payroll processing information required to create pay headers and transactions for an employee. This value is inherited from the position, group, department or job. but may be overridden.
;[Work Rule|WORK_RULE (Field)]:Work rules are used to determine the standard payroll processing information required to create pay headers and transactions for an employee. This value is inherited from the position, group, department or job. but may be overridden.
At line 44 changed one line
;[Long Term Assignment|LONG_TERM_ASSIGNMENT]:This field is used for certain custom calculation functions and may be secured from view.
;[ACA Category|ACA_CATEGORY]:This field indicates the ACA Category for this group.
At line 46 changed one line
;[Requires Time Sheet|REQUIRES_TIME_SHEET]:This toggle indicates that the employee must complete a time sheet for their position. This toggle controls whether UEGTS will create a separate timesheet (IPTS) for this assignment based on the option on the Work Rule Status. Only used for secondary assignments.
;[Bypass Org Chart|BYPASS_ORG_CHART]:
At line 64 added one line
;[Long Term Assignment|LONG_TERM_ASSIGNMENT]:This field is used for certain custom calculation functions and may be secured from view.
At line 49 changed one line
!Status
;[Requires Timesheet|REQUIRES_TIME_SHEET]:This toggle indicates that the employee must complete a time sheet for their position. This toggle controls whether UEGTS will create a separate timesheet (IPTS) for this assignment based on the option on the Work Rule Status. Only used for secondary assignments.
At line 70 added 2 lines
;[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]).
At line 74 added 4 lines
;[Job Profile|JOB_PROFILE_CODE]:This field is the 'job posting' information that is linked to the recruitment application.
;[Org Record Type|ORG_RECORD_TYPE]:
At line 64 changed 2 lines
;[Job Profile|JOB_PROFILE_CODE]:This field is the ‘job posting’ information that is linked to the recruitment application.
\\ \\
\\
;[View Open PA Summary| ]
\\
;[Submit PA|ACT_SUBMIT_PA]
;:[{InsertPage page='ACT_SUBMIT_PA'}]
;[Process PA|ACT_PROCESS_PA]:This is an action button which will update the employee's records with the changed detail of the PA. The status of the PA will be updated to 'Completed'.
\\
At line 99 added 2 lines
!Compensation Information
At line 78 changed one line
The following 5 fields Contract Days, School Days, Contract Limit, Periods Elected and Pay Starting are used exclusively for the control of contract processing.
;[Start Date of Pay|PAY_STARTING_DATE]:For contract assignment only: This field displays the date upon which the employee is to begin being paid. This may be different than the hire date.
At line 80 changed one line
;[Contract Days|CONTRACT_DAYS]:If this is a contract assignment, this field shows the number of days within the contract.
;[Range|RANGE_CODE]:Salary range provides minimum and maximum guidelines for the salary payable for the job, with which an employee's salary may be compared. This range is inherited from the position or job, however, it may be overridden.
At line 82 changed one line
;[School Days|SCHOOL_DAYS]:If this is a contract assignment, this field shows the number of school days within the contract.
;[Scale Step|SCALE_CODE] [Step|STEP_CODE]:The Wage Scale and Step fields determine the wage that is derived from the wage scale table. Scale/Step is inherited from the position or job, and may be overridden.
At line 84 changed one line
;[Contract Limit|CONTRACT_LIMIT]:If this is a contract assignment, this field displays the wage limit for the contract period.
;[Scale Rate|DRV_SCALE_RATE]:This field displays the rate the employee is receiving from the scale/step table. This field will be automatically filled once the scale/step has been selected.
At line 86 changed one line
;[Periods Elected|PERIODS_ELECTED]:If this is a contract assignment, this field shows the number of pay periods that the wage is to be paid over for the contract period.
;[Wage Rate|WAGE_RATE]: The employee's wage rate, expressed in terms of the rate basis, below. On this screen, there is an [in line calculator|WAGE_RATE CALCULATOR] for ease of wage changes.
At line 88 changed one line
;[Start Date of Pay|PAY_STARTING_DATE]:For contract assignment only: This field displays the date upon which the employee is to begin being paid. This may be different than the hire date.
;[Basis|RATE_BASIS]:The rate basis is the unit of measure that the associate wage rate is being stored or displayed in. It is either inherited from the position (or job), or defaulted from the wage scale and step. This basis may, however, be overridden (i.e. hourly, weekly, biweekly, semi-monthly, monthly or annually).
At line 90 changed one line
;[Range|RANGE_CODE]:Salary range provides minimum and maximum guidelines for the salary payable for the job, with which an employee's salary may be compared. This range is inherited from the position or job, however, it may be overridden.
!Miscellaneous Information
At line 92 changed one line
;[Scale|SCALE_CODE] [Step|STEP_CODE]:The Wage Scale and Step fields determine the wage that is derived from the wage scale table. Scale/Step is inherited from the position or job, and may be overridden.
The following 5 fields Contract Days, School Days, Contract Limit, Periods Elected and Pay Starting are used exclusively for the control of contract processing.
At line 94 changed one line
;[Scale|SCALE_CODE] [Step|STEP_CODE]:The Wage Scale and Step fields determine the wage that is derived from the wage scale table. Scale/Step is inherited from the position or job, and may be overridden.
;[Contract Days|CONTRACT_DAYS]:If this is a contract assignment, this field shows the number of days within the contract.
At line 96 changed one line
;[Wage Rate|WAGE_RATE]: The employee's wage rate, expressed in terms of the rate basis, below. On this screen, there is an [in line calculator|WAGE_RATE CALCULATOR] for ease of wage changes.
;[School Days|SCHOOL_DAYS]:If this is a contract assignment, this field shows the number of school days within the contract.
At line 98 changed one line
;[Basis|RATE_BASIS]:The rate basis is the unit of measure that the associate wage rate is being stored or displayed in. It is either inherited from the position (or job), or defaulted from the wage scale and step. This basis may, however, be overridden (i.e. hourly, weekly, biweekly, semi-monthly, monthly or annually).
;[Contract Limit|CONTRACT_LIMIT]:If this is a contract assignment, this field displays the wage limit for the contract period.
At line 133 added 4 lines
;[Periods Elected|PERIODS_ELECTED]:If this is a contract assignment, this field shows the number of pay periods that the wage is to be paid over for the contract period.
At line 104 changed one line
;[Scale Overriden|SCALE_OVERRIDE]:If the toggle is ON, the displayed wage rate has been keyed manually, and is different from the rate on the scale step. If the toggle is OFF, either the wage rate has not been overridden or else the scale step is not being used. This toggle is automatically turned on when the salary is overridden from the salary provided by the scale/step code selected. To reset this toggle, re-enter the wage rate to be the same as the scale rate.
;[Scale Overriden|SCALE_OVERRIDDEN]:If the toggle is ON, the displayed wage rate has been keyed manually, and is different from the rate on the scale step. If the toggle is OFF, either the wage rate has not been overridden or else the scale step is not being used. This toggle is automatically turned on when the salary is overridden from the salary provided by the scale/step code selected. To reset this toggle, re-enter the wage rate to be the same as the scale rate.
At line 108 changed one line
;[MNC Test (NL)|]:
;[Trigger BE Pay|TRIGGER_BE_RETRO]:If this toggle is ON, this assignment record may be specifically included in an execution of [UBRETRO] for retroactive wage benefit changes resulting from wage increases. If this toggle is OFF, the [UBRETRO] program will not pick up any retro benefits to be processed. A "To Be Audited" pay with starting and ending dates that fall within the effective and expiry dates must also exist for [UBRETRO] to process.
At line 110 changed 2 lines
;[MNC Test (UDF)|]:
\\ \\
\\
At line 168 added 5 lines
;[Send Pays To Location|LOCATION_CODE]:This field identifies the location where an employee's pay checks or deposit slips should be sent. This field may be left blank if the pays are to be sent to the employee’s ‘work out of’ location. This field may be used in the sorting of checks and deposits. If this field is left blank, checks and deposits may also be sorted by department or work location.
;[Web Pay Stub Only|WEB_PAY_STUB_ONLY]:If this toggle is on, the Information that can be used by the UPSTUB programs as a bypass. If on the UPSTUB can be made to not print for this person.
At line 140 removed one line
;[Send Pays To Location|LOCATION_CODE]:This field identifies the location where an employee's pay checks or deposit slips should be sent. This field may be left blank if the pays are to be sent to the employee’s ‘work out of’ location. This field may be used in the sorting of checks and deposits. If this field is left blank, checks and deposits may also be sorted by department or work location.
At line 142 removed 2 lines
;[Web Pay Stub Only|WEB_PAY_STUB_ONLY]:If this toggle is on, the Information that can be used by the [UPSTUB] programs as a bypass. If on the [UPSTUB] can be made to not print for this person.
At line 148 changed 3 lines
;[Email|EMAIL_ADDRESS]:This field holds the employee's work email address. This value is inherited from the locations, however, it may be overridden.
;[Work Cell Phone #|]:
\\ \\
;[Email|EMAIL_ADDRESS(Field)]:This field holds the employee's work email address. This value is inherited from the locations, however, it may be overridden.
\\
At line 165 changed 2 lines
;[Unit|]:
\\ \\
;:%%information Note that PAs with an effective date that falls on a past effective split record where a premium was added without changing assignment information, will receive the future update warning message.\\*Premium(s) will only be applied to future record when none exist on future records. \\*If 1 or more premiums exist, the message will be given to the user to manually adjust furture records.\\*A warning message will be displayed telling users that the premium values have not been updated on future records and they need to verify the values.
\\
At line 192 removed 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.
At line 194 removed 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.
At line 196 removed 8 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.
;[Submit PA|]:
;[Process PA|]:
[{If var='loginstatus' contains 'authenticated'
At line 205 changed 4 lines
![Discussion|Edit:Internal.PEAS]
[{InsertPage page='Internal.PEAS' default='Click to create a new discussion page'}]
}]
![Notes|Edit:Internal.PEAS]
[{InsertPage page='Internal.PEAS' default='Click to create a new notes page'}]
This page (revision-53) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop