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

Version management

Difference between version and

At line 5 changed one line
There must be a primary assignment corresponding to every employment relationship that an employee has with no gap between dates. The initial primary assignment is automatically created by either the Establish Personnel Profiles ([IEHR]) or Quick Hire ([IEQH]) form. When an employee has more than one employment relationship, (for example, they are a former employee, a current retiree or a current contractor) there will be a primary assignment record for each of these three relationships.
There must be a primary assignment corresponding to every employment relationship that an employee has with no gap between dates. The initial primary assignment is automatically created by either the Establish Personnel Profiles ([IEHR]) or Quick Hire ([IEQ]) form. When an employee has more than one employment relationship, (for example, they are a former employee, a current retiree or a current contractor) there will be a primary assignment record for each of these three relationships.
At line 117 changed one line
;[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]: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 134 changed one line
;[First Manager|]:This is a derived field based on hierarchal 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]:This is a derived field based on hierarchal 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 196 changed one line
;[User %|]: This value in this field is for display purposes only and is defaulted once the Dist % is completed.
;[User %]: This value in this field is for display purposes only and is defaulted once the Dist % is completed.