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 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 ([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.
At line 57 changed one line
;[Department|DEPARTMENT_CODE]:This is the department to which the employee is assigned. Department_Code from [IDDP] [(P2K_CM_DEPARTMENTS)] is a 16-character alphanumeric mandatory field.
;[Department|DEPARTMENT_CODE]:This is the department to which the employee is assigned. Department_Code from [IDDP] ([P2K_CM_DEPARTMENTS]) is a 16-character alphanumeric mandatory field.
At line 59 changed one line
;[Group|GROUP_CODE]:This is the group code that determines the policy rules under which the employee must be processed. Group_Code from [IDGR] [(P2K_CM_GROUPS)] is a 16-character alphanumeric mandatory field.
;[Group|GROUP_CODE]:This is the group code that determines the policy rules under which the employee must be processed. Group_Code from [IDGR] ([P2K_CM_GROUPS]) is a 16-character alphanumeric mandatory field.
At line 80 changed one line
;[Leave Reason|LEAVE_REASON]:A reason for the leave of absence may be entered here. Leave_Reason is an optional fixed lexicon [(X_LEAVE_REASON)].
;[Leave Reason|LEAVE_REASON]:A reason for the leave of absence may be entered here. Leave_Reason is an optional fixed lexicon ([X_LEAVE_REASON]).
At line 119 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). Rate_Basis is a mandatory fixed lexicon [(X_RATE_BASIS)].
;[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). Rate_Basis is a mandatory fixed lexicon ([X_RATE_BASIS]).
At line 138 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 is a fixed lexicon [(X_RESPONSIBILITY_LEVEL)] that you may complete with a value from the LOV (F9) provided.
;[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 is a fixed lexicon ([X_RESPONSIBILITY_LEVEL]) that you may complete with a value from the LOV (F9) provided.
At line 140 changed one line
;[Service Rating|SERVICE_RATING]:This field indicates an employee is on a probationary status for service or seniority purposes. Service_Rating is an optional fixed lexicon [(X_SERVICE_RATING)] you may use to look up the value.
;[Service Rating|SERVICE_RATING]:This field indicates an employee is on a probationary status for service or seniority purposes. Service_Rating is an optional fixed lexicon ([X_SERVICE_RATING]) you may use to look up the value.
At line 144 changed one line
;[Work Type|WORK_TYPE]: Work type is an assignment classification. Work_Type is an optional fixed lexicon [(X_WORK_TYPE)].
;[Work Type|WORK_TYPE]: Work type is an assignment classification. Work_Type is an optional fixed lexicon ([X_WORK_TYPE]).
At line 146 changed one line
;[WC Class|WCB_CLASS]:Workers’ Compensation is a user-definable code. WCB_Class is an optional user-defined lexicon [(X_WCB_CLASS)].
;[WC Class|WCB_CLASS]:Workers’ Compensation is a user-definable code. WCB_Class is an optional user-defined lexicon ([X_WCB_CLASS]).
At line 148 changed one line
;[Burden Method|BURDEN_METHOD]: This field specifies the burden method to be used for this in the Journalize Labor [(UPGL)] process. If this field is not specified, the burden method defined on the IDGR will be used. Burden_Method is an optional fixed lexicon [(X_BURDEN_METHOD)].
;[Burden Method|BURDEN_METHOD]: This field specifies the burden method to be used for this in the Journalize Labor ([UPGL]) process. If this field is not specified, the burden method defined on the IDGR will be used. Burden_Method is an optional fixed lexicon ([X_BURDEN_METHOD]).
At line 183 changed one line
;[O/R Basis|RATE_BASIS]:This field is used in conjunction with the O/R Rate to indicate the unit of measure for this premium, when the rate is overridden. Rate_Basis from [ISPM] ([P2K_SA_PREMIUM_USAGES]) is an optional fixed lexicon [(X_RATE_BASIS)] you may use to override the default rate basis.
;[O/R Basis|RATE_BASIS]:This field is used in conjunction with the O/R Rate to indicate the unit of measure for this premium, when the rate is overridden. Rate_Basis from [ISPM] ([P2K_SA_PREMIUM_USAGES]) is an optional fixed lexicon ([X_RATE_BASIS]) you may use to override the default rate basis.
At line 192 changed one line
;[Split Rule|SPLIT_RULE]:The distribution split rule indicates whether the distribution is being split by a percentage, by flat amount or by the Distribution pick list of authorized assignments. Split_Rule from ([P2K_CM_DISTRIBUTIONS]) is an optional fixed lexicon [(X_SPLIT_RULE)].
;[Split Rule|SPLIT_RULE]:The distribution split rule indicates whether the distribution is being split by a percentage, by flat amount or by the Distribution pick list of authorized assignments. Split_Rule from ([P2K_CM_DISTRIBUTIONS]) is an optional fixed lexicon ([X_SPLIT_RULE]).
This page (revision-72) was last changed on 26-Jan-2023 13:31 by Kevin HiggsTop