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

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
31 26-Nov-2021 10:22 8 KB lurtan to previous
30 26-Nov-2021 10:22 8 KB rforbes to previous | to last
29 26-Nov-2021 10:22 8 KB klawler to previous | to last
28 26-Nov-2021 10:22 8 KB jmyers to previous | to last WORK_RULE_CODE ==> WORK_RULE (Field)
27 26-Nov-2021 10:22 8 KB jmyers to previous | to last
26 26-Nov-2021 10:22 8 KB jmyers to previous | to last
25 26-Nov-2021 10:22 8 KB jmyers to previous | to last
24 26-Nov-2021 10:22 8 KB JMyers to previous | to last
23 26-Nov-2021 10:22 8 KB JMyers to previous | to last
22 26-Nov-2021 10:22 8 KB JMyers to previous | to last
21 26-Nov-2021 10:22 22 KB JMyers to previous | to last

Page References

Incoming links Outgoing links
IVDPS
IVDPS

Version management

Difference between version and

At line 3 changed 23 lines
Tables loaded:
*[P2K_CM_POSITIONS] (first record for each position code only)
*[P2K_CM_POSITION_DETAILS] (first record and subsequent effective splits)
*[P2K_SA_PREMIUM_USAGES] (one record for each premium code defined)
*[P2K_CM_DISTRIBUTIONS] (one record for each distribution split defined)
!!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]
|[POSITION_CODE]|Varchar2(16)|Y|Validation: Must be a unique position code for the entity specified
|[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 positions, so you could populate this field with a constant value of “A”.
|[GENERIC_CODE]|Varchar2(4)| |
|[POSITION_CODE_GROUPING]|Varchar2(16)| |
|[EFFECTIVE]|Date()|Y|Validation: Must be a valid date format. Suggestion: If you are not loading multiple date-effective records for the same position 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 position 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]
|[UNIT_CODE]|Varchar2(16)| |Validation: Must be a valid entity code defined on [P2K_CM_UNITS].
|[DEPARTMENT_CODE]|Varchar2(16)| |Validation: Must be a valid position code defined on [P2K_CM_DEPARTMENTS].
|[LOCATION_CODE]|Varchar2(16)| |Validation: Must be a valid LOCATION_CODE defined on [P2K_CM_LOCATIONS]. Derivation: This field is derived from the [LOCATION_CODE] on the [P2K_CM_DEPARTMENT_DETAILS] table for the [DEPARTMENT_CODE] specified.
|[GROUP_CODE]|Varchar2(16)| |Validation: Must be a valid [GROUP_CODE] defined on [P2K_CM_GROUPS]
|[JOB_CODE]|Varchar2(16)| |Validation: Must be a valid [JOB_CODE] defined on [P2K_CM_JOBS]
|[PERSON_CODE]|Varchar2(16)| |Validation: The [PERSON_CODE] must be for a valid employee currently entered on [P2K_HR_IDENTITIES].
;[|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]
;[|POSITION_CODE]|Varchar2(16)|Y|Validation: Must be a unique position code for the entity specified
;[|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 positions, so you could populate this field with a constant value of “A”.
;[|GENERIC_CODE]|Varchar2(4)| |
;[|POSITION_CODE_GROUPING]|Varchar2(16)| |
;[|EFFECTIVE]|Date()|Y|Validation: Must be a valid date format. Suggestion: If you are not loading multiple date-effective records for the same position 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 position 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]
;[|UNIT_CODE]|Varchar2(16)| |Validation: Must be a valid entity code defined on [P2K_CM_UNITS].
;[|DEPARTMENT_CODE]|Varchar2(16)| |Validation: Must be a valid position code defined on [P2K_CM_DEPARTMENTS].
;[|LOCATION_CODE]
;[|GROUP_CODE]|Varchar2(16)| |Validation: Must be a valid [GROUP_CODE] defined on [P2K_CM_GROUPS]
;[|JOB_CODE]|Varchar2(16)| |Validation: Must be a valid [JOB_CODE] defined on [P2K_CM_JOBS]
;[|PERSON_CODE]
This page (revision-31) was last changed on 26-Nov-2021 10:22 by lurtanTop