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 1 changed 2 lines
[{TableOfContents }]
!!!UNIT INTERFACE FILE
!!!Alias: [IVDUN]
(INF_CV_UNITS)
At line 4 changed one line
The Unit Interface File screen is used to import unit codes into the software data structures.
The INF_CV_UNITS table is used to import unit codes and their attendant data into the software data structures. A unit is a union, a bargaining unit, or a business sector of the organization that has a common set of employment rules and options. A unit normally has some kind of publication, such as a union contract, an employee handbook, or a policy and procedures manual detailing the employment rules that apply to the unit.
At line 6 changed one line
Unit Interface File data is maintained on the [INF_CV_UNITS] table.
Typical organization units are Salaried, Hourly or Union ABC.
At line 8 changed 13 lines
;[ID|ID]:This field uniquely identifies the unit record within the data base.
;[Entity|ENTITY_CODE]:This field identifies the entity associated with the unit.
;[Unit|UNIT_CODE]:This field is a user-defined code that uniquely identifies the unit being defined.
;[Standing|STANDING]:This field displays the standing of the unit.
;[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.
;[Description|DESCRIPTION]:This field holds a detailed description or name for the unit.
;[|UNIT_STATUS]:This field displays status of the unit.
;[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.
;[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.
;[Unit Text|UNIT_TEXT]:This field allows you to supply important information about the union contract.
Tables loaded:
*[P2K_CM_UNITS] (first record for each unit code only)
*[P2K_CM_UNIT_DETAILS] (first record and subsequent effective splits)
!!Table Columns
\\
||Column name||Data Type / Size||Mand.||Notes
|[ID]|Number(10)| |Used internally to define a unique identification for the record. This field would not be loaded.
|[ENTITY_CODE]|Varchar2(16)|Y|Validation: Must be a valid entity code defined on [P2K_CM_ENTITIES].
|[UNIT_CODE]|Varchar2(16)|Y|Validation: Must be a unique unit code for the entity provided.
|[STANDING]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_STANDING]. Suggestion: Normally, you would only load active units, so you could populate this field with a constant value of “A”.
|[EFFECTIVE]|Date()|Y|Validation: Must be a valid date format. Suggestion: If you are not loading multiple date-effective records for the same unit code, then populate this field with a constant ‘01-Jan-0001’ which represents the beginning of time.
|[EXPIRY]|Date()| |Validation: Must be a valid date format, with a date after the effective date. Suggestion: If you are not loading multiple date-effective records for the same unit code, then populate this field with a constant ‘31-Dec-3999’ which represents the end of time.
|[CHANGE_CODE]|Varchar2(16)| |Validation: The Change Code provided must be defined on [P2K_CM_CHANGE_REASONS]
|[DESCRIPTION]|Varchar2(50)|Y|
|[UNIT_STATUS]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_UNIT_STATUS]. Suggestion: Normally, you would only load active units, so you could populate this field with a constant value of “A”.
|[AGREEMENT_START_DATE]|Date()| |Validation: Must be a valid date.
|[AGREEMENT_END_DATE]|Date()| |Validation: Must be a valid date, with a date after the agreement start date.
|[UNIT_NAME]|Varchar2(50)| |
|[UNIT_LOCAL]|Varchar2(50)| |
|[UNIT_SUB_LOCAL]|Varchar2(50)| |
|[UNIT_TEXT]|Varchar2(4000)| |
|[CREATE_DATE]|Date()| |This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
|[CREATE_USER]|Varchar2(30)| |This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
|[CHANGE_DATE]|Date()| |This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
|[CHANGE_USER]|Varchar2(30)| | This field used internally only to provide audit information for the creation/updating of records. This field would not be loaded.
[{If var='loginstatus' contains 'authenticated'
At line 22 changed 2 lines
![Notes|Edit:Internal.IVDUN]
[{InsertPage page='Internal.IVDUN' default='Click to create a new notes page'}]
![Discussion|Edit:Internal.IVDUN]
[{InsertPage page='Internal.IVDUN' default='Click to create a new discussion page'}]
At line 42 added one line
}]
This page (revision-7) was last changed on 26-Nov-2021 10:22 by JMyersTop