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

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
7 26-Nov-2021 10:22 1 KB JMyers to previous
6 26-Nov-2021 10:22 1 KB JMyers to previous | to last
5 26-Nov-2021 10:22 7 KB JMyers to previous | to last
4 26-Nov-2021 10:22 6 KB JMyers to previous | to last
3 26-Nov-2021 10:22 6 KB JMyers to previous | to last
2 26-Nov-2021 10:22 670 bytes JMyers to previous | to last
1 26-Nov-2021 10:22 3 KB JMyers to last

Page References

Incoming links Outgoing links
IVDUN
IVDUN

Version management

Difference between version and

At line 8 changed 2 lines
;[ID|ID]:
;[ID|ID]:This field uniquely identifies the unit record within the data base.
At line 13 changed 3 lines
;[Effective|EFFECTIVE]:
;[|EXPIRY]:
;[|CHANGE_CODE]:
;[Effective As Of|EFFECTIVE]/[Expires On|EXPIRY]:If the group is temporary, these fields will define the dates the group is effective.
;[Change Reason|CHANGE_CODE]:This field displays the ‘Change Reason’ code, which provides the rationale as to why information has been created or changed as of an effective date.
At line 23 removed 2 lines
[{If var='loginstatus' contains 'authenticated'
At line 26 changed 2 lines
![Discussion|Edit:Internal.IVDUN]
[{InsertPage page='Internal.IVDUN' default='Click to create a new discussion page'}]
![Notes|Edit:Internal.IVDUN]
[{InsertPage page='Internal.IVDUN' default='Click to create a new notes page'}]
At line 29 removed 66 lines
}]
!!Units Definition
The definition data for the Maintain Units screen is maintained on the [P2K_CM_UNITS] and [P2K_CM_UNIT_DETAILS] tables.
;[Unit|UNIT_CODE]:This field is a user-defined code that uniquely identifies the unit being defined. [Unit_Code|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.
%%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.%%
\\
----
!!Details tab
;[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.
;[Agreement Start Date|AGREEMENT_START_DATE] / [Agreement End Date|AGREEMENT_END_DATE]:For units with agreements or contracts, these fields will display the first and last dates of the agreement.
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.
\\
----
!!Union Contract (LR) tab
;[Contract Text|UNIT_TEXT]: This field allows you to supply important information about the union contract. Unit_Text is an optional 4000-character alphanumeric field you may fill manually.
\\
----
!!Groups tab
%%warning This tab is for viewing purposes only; you may not edit the data.%%
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.\\
\\
----
!!Contacts (LR) tab
The Contacts tab will identify the contacts associated with this unit. Contacts may be internal or external.
;[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. This is a mandatory field you may fill manually or retrieve from the LOV provided.
;:%%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.
\\
----
!!Elements tab
The data on this screen is maintained on the [P2K_LR_UNIT_ELEMENTS] table as a related child of [P2K_CM_UNIT_DETAILS].
;[Unit Element Typ|UNIT_ELEMENT_TYPE]: This field identifies the unit [element|PAY ELEMENTS] 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|PAY ELEMENTS]. Description is a 50-character alphanumeric optional field you may manually enter.
;[Element|ELEMENT_CODE]: This field provides the name of the [element|PAY ELEMENTS] 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.
\\
----
!!Grievance Unit Rules (LR) tab
;[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.
;[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.
This page (revision-7) was last changed on 26-Nov-2021 10:22 by JMyersTop