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 3 removed one line
[{Image src='IDUN.JPG' width='360' align='right' link='attach/IDUN.JPG'}]
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, and jobs. They may be used to determine[benefit schedules and leave schedules.
At line 9 changed one line
Units are subdivided into [groups], which reflect policy variations within the unit. The job definitions, [salary ranges|Salary Range], wage scales and steps, holiday calendar, benefit plan eligibility, attendance policies, work rules, and other policies are defined at the group level.
Units are subdivided into [groups|GROUPS], which reflect policy variations within the unit. The job definitions, [salary ranges|SALARIES_SALARY RANGES], wage scales and steps, holiday calendar, benefit plan eligibility, attendance policies, work rules, and other policies are defined at the group level.
At line 15 removed 2 lines
%%information This function is [date sensitive] and changes made in these areas below the [date navigator] may be split with a new effective date.%%
At line 19 changed 3 lines
;[Unit|UNIT_CODE]:This field is a user-defined code that uniquely identifies the unit being defined. [Unit_Code] is a mandatory 16-character alphanumeric field you must manually enter.
;[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].
;[Standing|STANDING]:This field displays the standing of the unit. Standing is an optional field you must fill from the fixed lexicon [X_STANDING].
;[Unit|UNIT_CODE]:This field is a user-defined code that uniquely identifies the unit being defined.
;[Entity|ENTITY_CODE]:This field identifies the entity associated with the defined unit.
;[Standing|STANDING]:This field displays the standing of the unit.
At line 20 added 2 lines
%%information This function is [date sensitive|DATE SENSITIVE] and changes made in these areas below the [date navigator|DATE SENSITIVE NAVIGATOR] may be split with a new effective date.%%
\\
At line 24 changed 2 lines
[{Image src='IDUN_Details.JPG' width='360' align='right' link='attach/IDUN/IDUN_Details.JPG'}]
!!Define Units (IDUN) - Details
!!Details tab
At line 27 changed 2 lines
;[Status|UNIT_STATUS]: This field displays status of the unit. Unit_Status is a mandatory fixed lexicon [X_UNIT_STATUS] you may use to look up the value. Active will default
;[Description|DESCRIPTION]: This field holds a detailed description or name for the unit. Description is a 50-character alphanumeric optional field you may manually enter.
;[Status|UNIT_STATUS]: This field displays status of the unit.
;[Description|DESCRIPTION]: This field holds a detailed description or name for the unit.
At line 30 changed 5 lines
Agreement_Start_Date and Agreement_End_Date is an optional date field you may manually enter or by using the calendar function (F9).
;[Unit Name|UNIT_NAME]: This field holds the name of the unit. Unit_Name is an optional 50-character alphanumeric field you may fill manually.
;[Unit Local|UNIT_LOCAL]: This field holds the name of the unit local. Unit_Local is an optional 50-character alphanumeric field you enter may manually.
;[Unit Sub Local|UNIT_SUB_LOCAL]: This field holds the name of the unit sub-local. Unit_Sub_Local is a 50-character alphanumeric optional field you may manually enter.
;[Unit Name|UNIT_NAME]: This field holds the name of the unit.
;[Unit Local|UNIT_LOCAL]: This field holds the name of the unit local.
;[Unit Sub Local|UNIT_SUB_LOCAL]: This field holds the name of the unit sub-local.
\\
At line 36 changed 2 lines
[{Image src='IDUN_UnionContract.JPG' width='360' align='right' link='attach/IDUN/IDUN_UnionContract.JPG'}]
!!Define Units (IDUN) - Union Contract (LR)
!!Union Contract (LR) tab
At line 40 changed one line
\\
At line 42 changed 2 lines
[{Image src='IDUN_Groups.JPG' width='360' align='right' link='attach/IDUN/IDUN_Groups.JPG'}]
!!Define Units (IDUN) - Groups
!!Groups tab
%%warning This tab is for viewing purposes only; you may not edit the data.%%
At line 45 changed 2 lines
This Groups tab is for viewing only; groups cannot be added directly to this screen. Once the unit has been defined and the IDUN screen saved, you may associate the unit to the group through the [IDGR] screen. Once association has been made, the group will then automatically appear in this area of the IDUN form
This tab is for viewing only; groups cannot be added directly to this screen. Once the unit has been defined and the IDUN screen saved, you may associate the unit to the group through the [IDGR] screen. Once association has been made, the group will then automatically appear in this area of the IDUN form.\\
\\
At line 48 changed 2 lines
[{Image src='IDUN_Contacts.JPG' width='360' align='right' link='attach/IDUN/IDUN_Contacts.JPG'}]
!!Define Units (IDUN) - Contacts (LR)
!!Contacts (LR) tab
At line 51 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 53 changed 6 lines
;[Unit Contact Type|UNIT_CONTACT_TYPE]: This field will display the type of contact being defined. For example, shop stewards, union representatives, union administrative representatives or union officials. Unit_Contact_Type is an optional field you may fill from the fixed lexicon [X_UNIT_CONTACT_TYPE]
;[Unit Contact Title|UNIT_CONTACT_TITLE]: This field displays the official title of the unit contact. Unit_Contact_Title is a mandatory 50-character alphanumeric field you must enter manually.
;[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.
;[Unit Contact Type|UNIT_CONTACT_TYPE]: This field will display the type of contact being defined. For example, shop stewards, union representatives, union administrative representatives or union officials.
At line 50 added 11 lines
;[Unit Contact Title|UNIT_CONTACT_TITLE]: This field displays the official title of the unit contact.
;Employee Name OR Contact Name: These fields display the identity of the unit contact.
;:%%information You may only complete one of these fields.%%
;:* For internal contacts, use the Employee Name field. The link to [IEID] ([P2K_HR_IDENTITIES]) is made through the [foreign key] [EID_ID].
;:* For external contacts, use the Contact Name field. The link to [IECI] ([P2K_HR_CONTACTS]) is made through the [foreign key] [ECT_ID].
;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 61 changed 2 lines
[{Image src='IDUN_Elements.JPG' width='360' align='right' link='attach/IDUN/IDUN_Elements.JPG'}]
!!Define Units (IDUN) - Elements
!!Elements tab
At line 66 changed 4 lines
;[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].
;[Description]:This field offers a short description of the element. Description is a 50-character alphanumeric optional field you may manually enter.
;[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.
;[Unit Element Typ|UNIT_ELEMENT_TYPE]: This field identifies the unit [element|PAY ELEMENTS] type.
;[Description|DESCRIPTION]:This field offers a short description of the [element|PAY ELEMENTS].
;[Element|ELEMENT_CODE]: This field provides the name of the [element|PAY ELEMENTS] for the unit.
\\
At line 71 changed 2 lines
[{Image src='IDUN_GrievanceRules.JPG' width='360' align='right' link='attach/IDUN/IDUN_GrievanceRules.JPG'}]
!!Define Units (IDUN) - Grievance Unit Rules (LR)
!!Grievance Unit Rules (LR) tab
At line 74 changed 2 lines
;[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.
;[Description]: A short description of this rule and how it is associated to this unit may be provided here. Description is a mandatory 50-character alphanumeric field you must fill.
;[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.
;[Description|DESCRIPTION]: A short description of this rule and how it is associated to this unit may be provided here.
----
![Notes|Edit:Internal.IDUN]
[{InsertPage page='Internal.IDUN' default='Click to create a new notes page'}]
This page (revision-28) was last changed on 26-Nov-2021 10:22 by JMyersTop