This page (revision-28) was last changed on 26-Nov-2021 10:22 by JMyers

This page was created on 26-Nov-2021 10:22 by 192.168.200.17

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
28 26-Nov-2021 10:22 5 KB JMyers to previous
27 26-Nov-2021 10:22 6 KB RForbes to previous | to last
26 26-Nov-2021 10:22 6 KB JMyers to previous | to last
25 26-Nov-2021 10:22 7 KB JEscott to previous | to last
24 26-Nov-2021 10:22 7 KB JEscott to previous | to last
23 26-Nov-2021 10:22 7 KB JEscott to previous | to last
22 26-Nov-2021 10:22 7 KB RForbes to previous | to last
21 26-Nov-2021 10:22 7 KB Administrator to previous | to last

Page References

Incoming links Outgoing links
IDUN
IDUN

Version management

Difference between version and

At line 7 changed one line
Units belong to an [entity] and own [contract calendars], [salary] wage and [premium schedules|Premium Schedule], and [jobs]. They may be used to determine [benefit|Benefit Schedule] and [leave schedules|Leave Schedule].
Units belong to an entity and own contract calendars, salary wage and [premium schedules|Premium Schedule], and jobs. They may be used to determine [benefit schedules|Benefit Schedule] and [leave schedules|Leave Schedule].
At line 18 changed one line
;[Entity|ENTITY_CODE]:This field identifies the entity associated with the defined unit. Entity from [IDEN] ([P2K_CM_ENTITIES]) is a mandatory field you must fill through the [LOV].
;[Entity|ENTITY_CODE]:This field identifies the entity associated with the defined unit. Entity from [IDEN] ([P2K_CM_ENTITIES]) is a mandatory field you must fill through the LOV.
At line 52 changed one line
The Contacts tab will identify the contacts associated with this [unit]. Contacts may be internal or external.
The Contacts tab will identify the contacts associated with this unit. Contacts may be internal or external.
At line 56 changed 4 lines
;[Employee Name] OR [Contact Name]: These fields display the identity of the unit contact. You may only complete one of these fields. For internal contacts, use the Employee Name field and for external contacts, use the Contact Name field. Identity is derived from both the [IEID] ([P2K_HR_IDENTITIES]) and [IECT] ([P2K_HR_CONTACTS]) tables. This is a mandatory field you may fill manually or retrieve from the LOV provided.
;[Type|CONTACT_TYPE]: If the contact name is drawn from the contacts tables, this field will display the ‘contact type’ defined in the [IECI] screen. You cannot edit this field; the information will default once the contact name has been selected.
;[Address]: This field displays the contact’s address. You cannot edit this field; the information will default once the contact name has been selected.
;[Phone]: This field displays the contact’s phone number. You cannot edit this field; the information will default once the contact name has been selected.
;Employee Name OR Contact Name: These fields display the identity of the unit contact. %%(color:red;)You may only complete one of these fields.%% For internal contacts, use the Employee Name field and for external contacts, use the Contact Name field. Identity is derived from both the [IEID] ([P2K_HR_IDENTITIES]) and [IECT] ([P2K_HR_CONTACTS]) tables. This is a mandatory field you may fill manually or retrieve from the LOV provided.
;Type: If the contact name is drawn from the contacts tables, this field will display the ‘contact type’ defined in the [IECI] screen. You cannot edit this field; the information will default once the contact name has been selected.
;Address: This field displays the contact’s address. You cannot edit this field; the information will default once the contact name has been selected.
;Phone: This field displays the contact’s phone number. You cannot edit this field; the information will default once the contact name has been selected.
At line 67 changed one line
;[Unit Element Type]: This field identifies the unit element type. Unit_Element_Type is a mandatory field you will select from the fixed lexicon X_UNIT_ELEMENT_TYPE.
;[Unit Element Typ|UNIT_ELEMENT_TYPE]: This field identifies the unit element type. Unit_Element_Type is a mandatory field you will select from the fixed lexicon X_UNIT_ELEMENT_TYPE.
At line 69 changed one line
;[Element]: This field provides the name of the element for the unit. Element from [IPPE] ([P2K_PR_ELEMENTS]) is a mandatory 16-character alphanumeric field you must manually enter or retrieve from the LOV provided.
;[Element|ELEMENT_CODE]: This field provides the name of the element for the unit. Element from [IPPE] ([P2K_PR_ELEMENTS]) is a mandatory 16-character alphanumeric field you must manually enter or retrieve from the LOV provided.
At line 75 changed one line
;[Grievance_Rule]: If there are grievance rules directly associated with this unit, the name of those rules will appear in this screen. Grievance_Rule from [ILGR] ([P2K_LR_GRIEVANCE_RULES]) is a mandatory field you must fill either manually or through the LOV provided.
;[Grievance_Rule|GRIEVANCE_RULE_CODE]: If there are grievance rules directly associated with this unit, the name of those rules will appear in this screen. Grievance_Rule from [ILGR] ([P2K_LR_GRIEVANCE_RULES]) is a mandatory field you must fill either manually or through the LOV provided.
This page (revision-28) was last changed on 26-Nov-2021 10:22 by JMyersTop