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 9 added 8 lines
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 29 removed one line
;[Submit PA|ACT_SUBMIT_PA]:This is an action button which allows you to submit the PA for review. When pressed a dialog will appear asking you to verify the changes by pressing OK or Cancel. The status of the PA will then change to 'Submitted'.
At line 31 removed 3 lines
;[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 36 changed one line
\\ \\
\\
At line 39 changed one line
!Definition
At line 56 changed one line
;[ACA Category|ACA_CATEGORY]:
;[ACA Category|ACA_CATEGORY]:This field indicates the ACA Category for this group.
At line 65 removed one line
;[Provide Internal Service|PROVIDE_INTERNAL_SERVICE]:
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 68 changed one line
;[Job Code|JOB_CODE]:
;[Job Profile|JOB_PROFILE_CODE]:This field is the 'job posting' information that is linked to the recruitment application.
At line 81 changed 2 lines
\\ \\
\\
;[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 103 changed one line
;[Scale Rate|STEP_RATE]: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.
;[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 131 changed one line
;[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 BE increases. If this toggle is OFF, the [UBRETRO] program will use other criteria for selecting qualified retroactive BE changes.
;[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 133 changed 2 lines
\\ \\
\\
At line 174 changed one line
\\
At line 189 changed 2 lines
;[Unit|UNIT_CODE]:The unit associated with this premium will be displayed in this field.
\\ \\
;:%%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.
\\
This page (revision-53) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop