This page (revision-72) was last changed on 26-Jan-2023 13:31 by Kevin Higgs

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
72 26-Jan-2023 13:31 23 KB Kevin Higgs to previous
71 26-Nov-2021 10:22 23 KB Karen Parrott to previous | to last
70 26-Nov-2021 10:22 24 KB Karen Parrott to previous | to last
69 26-Nov-2021 10:22 24 KB Karen Parrott to previous | to last
68 26-Nov-2021 10:22 24 KB Meg McFarland to previous | to last
67 26-Nov-2021 10:22 24 KB khiggs to previous | to last
66 26-Nov-2021 10:22 24 KB khiggs to previous | to last
65 26-Nov-2021 10:22 24 KB kparrott to previous | to last
64 26-Nov-2021 10:22 24 KB kparrott to previous | to last
63 26-Nov-2021 10:22 24 KB rforbes to previous | to last
62 26-Nov-2021 10:22 23 KB kparrott to previous | to last
61 26-Nov-2021 10:22 22 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
IEAS
IEAS

Version management

Difference between version and

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 40 changed one line
;[Wage Progress Date|WAGE_PROGRESSION_DATE ]:If the assignment’s wage is to increase on a specific date, that date is indicated in this field. See [Wage Progression Processes|WAGE PROGRESSION] for full details.
;[Wage Progress Date|WAGE_PROGRESSION_DATE ]:If the assignment'€™s wage is to increase on a specific date, that date is indicated in this field. See [Wage Progression Processes|WAGE PROGRESSION] for full details.
At line 44 changed one line
;[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 75 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]).
At line 77 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]).
;[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 79 changed one line
;[Supervisory|SUPERVISORY]:This toggle indicates if the position is to be reported as ‘Supervisory’ 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]).
At line 81 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 83 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 91 changed one line
;[Job Profile|JOB_PROFILE_CODE]:This field is the ‘job posting’ information that is linked to the recruitment application.
;[Job Profile|JOB_PROFILE_CODE]:This field is the '€˜job posting'€™ information that is linked to the recruitment application.
At line 145 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.
Note: Focus-change is a desirable by product of the ability to do a drill-into from any given field (for example, position, job, unit, etc.). This is accomplished by providing (in IMFDH) a LOV query that allows look up and translation of IDs.
At line 147 added 11 lines
As a result, the Location tab's First manager and Supervised By fields have LOVs defined to provide the translation of the ID that is on the record (otherwise you would not see the name of the manager).
This means that if you are on the Location tab of IEAS where these lookup/translations are made, and then go to another screen for employees, you will re-focus on this different employee.
There are several options that the customer has, as this will not be changed within the product:
1. Remove these fields from IEAS definition using IMFOS
2. Place these fields on their own tab instead of the Location tab, so that the change-in-focus will only occur when you go to this explicit tab.
;[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 149 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 157 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 171 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 200 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 204 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 207 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 213 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 215 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 218 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-72) was last changed on 26-Jan-2023 13:31 by Kevin HiggsTop