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 removed 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 32 changed one line
;[Status|ASSIGNMENT_STATUS]:This field is used for the ‘contract’ facility. Will default to ‘Ongoing’.
;[Status|ASSIGNMENT_STATUS]:This field is used for the ‘contract’ facility. Will default to ‘Ongoing’.
At line 29 added 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 added 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 39 changed 2 lines
;[Renew Contract| ]:This button allows you to renew the employee’s contract.
\\
;[Renew Contract| ]:This button allows you to renew the employee’s contract.
\\ \\
At line 43 changed one line
!Definition
At line 60 changed one line
;[ACA Category|ACA_CATEGORY]:This field indicates the ACA Category for this group.
;[ACA Category|ACA_CATEGORY]:
At line 68 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]).
;[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]).
;[Provide Internal Service|PROVIDE_INTERNAL_SERVICE]:
At line 70 changed 6 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]).
;[Supervisory|SUPERVISORY]:This toggle indicates if the position is to be reported as ‘Supervisory’ on specific government reports (e.g. Official Language Report - [REOLA]).
;[Job Profile|JOB_PROFILE_CODE]:This field is the 'job posting' information that is linked to the recruitment application.
;[Supervisory|SUPERVISORY]:This toggle indicates if the position is to be reported as ‘Supervisory’ on specific government reports (e.g. Official Language Report - [REOLA]).
;[Job Code|JOB_CODE]:
At line 78 changed one line
;[Employment Status|STATUS_CODE]:This field indicates an individual’s employment status as pending approval, active, on a leave of some type or terminated.
;[Employment Status|STATUS_CODE]:This field indicates an individual’s employment status as pending approval, active, on a leave of some type or terminated.
At line 80 changed one line
;[Leave Date|LEAVE_DATE]:This field shows the date the employee’s leave commences.
;[Leave Date|LEAVE_DATE]:This field shows the date the employee’s leave commences.
At line 88 changed 9 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 117 changed one line
;[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.
;[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.
At line 145 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 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.
;[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.
At line 147 changed one line
\\
\\ \\
At line 150 changed one line
;[First Manager|EID_ID_FIRST_MANAGER]: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.
;[First Manager|EID_ID_FIRST_MANAGER]: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 154 changed one line
;[Responsibility Level|RESPONSIBILITY_LEVEL]:‘Responsibility Level’ is a security access feature and is defined on the Assign User Security Rights ([IMSV]) form. A user may only access information on an employee who’s assignment responsibility is lower than, or equal to that defined for user access on [IMSV]. The data for this field is inherited from the position, but it may be overridden.
;[Responsibility Level|RESPONSIBILITY_LEVEL]:‘Responsibility Level’ is a security access feature and is defined on the Assign User Security Rights ([IMSV]) form. A user may only access information on an employee who’s assignment responsibility is lower than, or equal to that defined for user access on [IMSV]. The data for this field is inherited from the position, but it may be overridden.
At line 162 changed one line
;[WC Class|WCB_CLASS]:Workers’ Compensation is a user-definable code.
;[WC Class|WCB_CLASS]:Workers’ Compensation is a user-definable code.
At line 168 changed 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.
;[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 187 changed one line
\\
At line 202 changed 2 lines
;:%%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.
\\
;[Unit|UNIT_CODE]:The unit associated with this premium will be displayed in this field.
\\ \\
At line 208 changed one line
;[Distribution Code|DISTRIBUTION_CODE]:This field shows the distribution code receiving the portion of costs. This is normally the distribution of the wages associated with the assignment.\\ \\The Distribution Editor button 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 complete distribution will be shown at the top of the form. When you are satisfied with the distribution created, press OK. 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 distribution code to be returned to the previous form, press ‘Cancel’.
;[Distribution Code|DISTRIBUTION_CODE]:This field shows the distribution code receiving the portion of costs. This is normally the distribution of the wages associated with the assignment.\\ \\The Distribution Editor button 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 complete distribution will be shown at the top of the form. When you are satisfied with the distribution created, press OK. 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 distribution code to be returned to the previous form, press ‘Cancel’.
At line 212 changed one line
;:__Not Specified__:If ‘Not Specified’ is selected, there is no need to define percentage or amounts, the system will post the entire 100% to the distribution code.
;:__Not Specified__:If ‘Not Specified’ is selected, there is no need to define percentage or amounts, the system will post the entire 100% to the distribution code.
At line 215 changed one line
;:__Distr. Pick List__:Within the Distribution tab of IEAS, sequences are created with the split rule ‘Dist. Pick List’ with the start and end dates identified. You MUST complete both the start and end date fields within IEAS. The pick list will be applied to either a pay transaction ([IPTR]) or pay line ([IPPH]) through the following procedure:
;:__Distr. Pick List__:Within the Distribution tab of IEAS, sequences are created with the split rule ‘Dist. Pick List’ with the start and end dates identified. You MUST complete both the start and end date fields within IEAS. The pick list will be applied to either a pay transaction ([IPTR]) or pay line ([IPPH]) through the following procedure:
At line 222 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
;[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
At line 224 changed one line
;[User %|USER_PERCENT]: If you have selected ‘Split By Percent’ as the split rule, then you will indicate the User percentage in this field. After the Distr % is entered, the User % is defaulted with the Distr %. This defaulted value may be overridden.
;[User %|USER_PERCENT]: If you have selected ‘Split By Percent’ as the split rule, then you will indicate the User percentage in this field. After the Distr % is entered, the User % is defaulted with the Distr %. This defaulted value may be overridden.
At line 227 changed one line
;[Amount $|SPLIT_AMOUNT]:If you have selected ‘Split By Flat Amount’ as the split rule, then you will indicate the amount to be given to the distribution code in this field. When the ‘Split By Flat Amount’ is used, the distribution code will be posted with the exact amount as specified. The last sequential split line will be adjusted positively or negatively.Only one split rule should be used on a single distribution tab. You may however, set up separate split rules for different assignments, positions or jobs.
;[Amount $|SPLIT_AMOUNT]:If you have selected ‘Split By Flat Amount’ as the split rule, then you will indicate the amount to be given to the distribution code in this field. When the ‘Split By Flat Amount’ is used, the distribution code will be posted with the exact amount as specified. The last sequential split line will be adjusted positively or negatively.Only one split rule should be used on a single distribution tab. You may however, set up separate split rules for different assignments, positions or jobs.
This page (revision-53) was last changed on 26-Nov-2021 10:22 by Karen ParrottTop