Wiki: IVDUN

UNIT INTERFACE FILE
Units Definition
Details tab
Union Contract (LR) tab
Groups tab
Contacts (LR) tab
Elements tab
Grievance Unit Rules (LR) tab

UNIT INTERFACE FILE#

The Unit Interface File screen is used to import unit codes into the software data structures.

Unit Interface File data is maintained on the INF_CV_UNITS table.

ID

Entity: This field identifies the entity associated with the unit.

Unit: This field is a user-defined code that uniquely identifies the unit being defined.

Standing: This field displays the standing of the unit.

Effective As Of/Expires On: If the group is temporary, these fields will define the dates the group is effective.

Change Reason: 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.

Description: This field holds a detailed description or name for the unit.

: This field displays status of the unit.

Agreement Start Date/Agreement End Date: For units with agreements or contracts, these fields will display the first and last dates of the agreement.

Unit Name: This field holds the name of the unit.

Unit Local: This field holds the name of the unit local.

Unit Sub Local: This field holds the name of the unit sub-local.

Unit Text: This field allows you to supply important information about the union contract.

Units Definition#

The definition data for the Maintain Units screen is maintained on the P2K_CM_UNITS and P2K_CM_UNIT_DETAILS tables.

Unit: 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: 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: This field displays the standing of the unit. Standing is an optional field you must fill from the fixed lexicon X_STANDING.

This function is date sensitive and changes made in these areas below the date navigator may be split with a new effective date.

Details tab#

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: 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 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: This field holds the name of the unit. Unit_Name is an optional 50-character alphanumeric field you may fill manually.

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: 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: 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#

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: 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: 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.

: 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: 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.

Grievance Unit Rules (LR) tab#

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.

Table of Contents