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

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

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

Page References

Incoming links Outgoing links
INF_CV_UNITS
INF_CV_UNITS

Version management

Difference between version and

At line 1 changed one line
!!!Alias: [IVDUN]
!!!Alias: IVDUN
At line 3 added 2 lines
\\
Contract specific information.
At line 4 removed 8 lines
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.
Typical organization units are Salaried, Hourly or Union ABC.
Tables loaded:
*[P2K_CM_UNITS] (first record for each unit code only)
*[P2K_CM_UNIT_DETAILS] (first record and subsequent effective splits)
At line 14 changed 25 lines
||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.
----
![Notes|Edit:Internal.INF_CV_UNITS]
[{InsertPage page='Internal.INF_CV_UNITS' default='Click to create a new notes page'}]
||Column name||Data Type / Size||Domain||Mand.||Notes
|[ID]|Number(10)|[ID]| |
|[ENTITY_CODE]|Varchar2(16)|[CODE]|Y|
|[UNIT_CODE]|Varchar2(16)|[CODE]|Y|
|[STANDING]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[EFFECTIVE]|Date()|[EFFECTIVE]|Y|
|[EXPIRY]|Date()|[EXPIRY]| |
|[CHANGE_CODE]|Varchar2(16)|[CODE]| |
|[DESCRIPTION]|Varchar2(50)|[DESCRIPTION]|Y|
|[UNIT_STATUS]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[AGREEMENT_START_DATE]|Date()|[DATE]| |
|[AGREEMENT_END_DATE]|Date()|[DATE]| |
|[UNIT_NAME]|Varchar2(50)|[DESCRIPTION]| |
|[UNIT_LOCAL]|Varchar2(50)|[DESCRIPTION]| |
|[UNIT_SUB_LOCAL]|Varchar2(50)|[DESCRIPTION]| |
|[UNIT_TEXT]|Varchar2(4000)|[VARCHAR4000|VARCHARnn]| |
|[CREATE_DATE]|Date()|[DATE]| |
|[CREATE_USER]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[CHANGE_DATE]|Date()|[DATE]| |
|[CHANGE_USER]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
This page (revision-6) was last changed on 26-Nov-2021 10:22 by JMyersTop