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 and 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 13 changed one line
''For example, a full-time systems developer in the computer department of a college teaches a evening programming class twice a week or a part-time clerk works in the human resources department two mornings a week, and in the payroll department three days every other week.''
''For example, a full-time systems developer in the computer department of a college teaches a evening programming class twice a week or a part-time clerk works in the human resources department two mornings a week and in the payroll department three days every other week.''
At line 33 changed one line
;[Status|ASSIGNMENT_STATUS]:Used for the ‘contract’ facility. Will default to ‘Ongoing’. Assignment_Status is an optional fixed lexicon ([X_ASSIGN_STATUS]) that you may use to look up the value.
;[Status|ASSIGNMENT_STATUS]:This field is used for the ‘contract’ facility. Will default to ‘Ongoing’. Assignment_Status is an optional fixed lexicon ([X_ASSIGN_STATUS]) that you may use to look up the value.
At line 53 changed one line
;[Job|JOB_CODE]:This field shows job that the employee is hired to perform. Job_Code from [IDJB] ([P2K_CM_JOBS]) is a 16-character alphanumeric mandatory field.
;[Job|JOB_CODE]:This field shows the job that the employee is hired to perform. Job_Code from [IDJB] ([P2K_CM_JOBS]) is a 16-character alphanumeric mandatory field.
At line 63 changed one line
;[Work Rule|WORK_RULE_CODE]:Work rules are used to determine standard payroll processing information required to create pay headers and transactions for an employee. This value is inherited from the position, group, department or job. but may be overridden. Work_Rule_Code from [IDWR] ([P2K_CM_WORK_RULES]) is a 16-character alphanumeric optional field.
;[Work Rule|WORK_RULE_CODE]:Work rules are used to determine the standard payroll processing information required to create pay headers and transactions for an employee. This value is inherited from the position, group, department or job. but may be overridden. Work_Rule_Code from [IDWR] ([P2K_CM_WORK_RULES]) is a 16-character alphanumeric optional field.
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 188 changed one line
;[Seq #|SPLIT_SEQUENCE]:This field defines the sequential order (or line number) of the distribution code for this assignment. You may define one or multiple distribution lines with splits. Split_Sequence from ([P2K_CM_DISTRIBUTIONS]) is a 5 digit mandatory.
;[Seq #|SPLIT_SEQUENCE]:This field defines the sequential order (or line number) of the distribution code for this assignment. You may define one or multiple distribution lines with splits. Split_Sequence from ([P2K_CM_DISTRIBUTIONS]) is a 5 digit mandatory field.
At line 198 changed one line
;[Amount $|SPLIT_AMOUNT]:If the split rule is ‘by amount’ then indicate the amount in this field. Split_Amount from ([P2K_CM_DISTRIBUTIONS]) is an 18 digit optional numeric field.
;[Amount $|SPLIT_AMOUNT]:If the split rule is ‘by amount’ then indicate the amount in this field. Split_Amount from ([P2K_CM_DISTRIBUTIONS]) is an 18-digit optional numeric field.
This page (revision-72) was last changed on 26-Jan-2023 13:31 by Kevin HiggsTop