This page (revision-8) 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
8 26-Nov-2021 10:22 3 KB JMyers to previous
7 26-Nov-2021 10:22 3 KB JEscott to previous | to last
6 26-Nov-2021 10:22 3 KB JEscott to previous | to last
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 1 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 1 KB JEscott to last

Page References

Incoming links Outgoing links
INF_CV_PREMIUMS
INF_CV_PREMIUMS

Version management

Difference between version and

At line 1 changed 2 lines
!!!Alias: IVSPM
The INF_CV_PREMIUMS table is used to import premium codes and their attendant data into the software data structures. Premiums are additional or supplementary pay amounts that are made to employees over and above their base pay. Premiums are determined by unit
!!!Alias: [IVSPM]
(INF_CV_PREMIUMS)
At line 4 added 5 lines
The INF_CV_PREMIUMS table is used to import [premium|PREMIUMS] data into the software data structures. [Premiums|PREMIUMS] are additional or supplementary pay amounts that are made to employees over and above their base pay. [Premiums|PREMIUMS] are determined by unit
Tables loaded:
*[P2K_SA_PREMIUMS] (first record for each premium code only)
*[P2K_SA_PREMIUM_DETAILS] (first record and subsequent effective splits)
At line 6 changed 29 lines
||Column name||Data Type / Size||Domain||Mand.||Notes
|[ID]|Number(10)|[ID]| |
|[ENTITY_CODE]|Varchar2(16)|[CODE]|Y|
|[UNIT_CODE]|Varchar2(16)|[CODE]|Y|
|[PREMIUM_CODE]|Varchar2(16)|[CODE]|Y|
|[DESCRIPTION]|Varchar2(50)|[DESCRIPTION]| |
|[PREMIUM_TYPE_CODE]|Varchar2(16)|[CODE]| |
|[PREMIUM_TYPE_SEQUENCE]|Number(5)|[NUMBER5|NUMBERn]| |
|[EFFECTIVE]|Date()|[EFFECTIVE]|Y|
|[EXPIRY]|Date()|[EXPIRY]| |
|[CHANGE_CODE]|Varchar2(16)|[CODE]| |
|[PC_CODE_DOLLARS]|Number(4)|[CODE NUMERIC]| |
|[PC_CODE_TIME]|Number(4)|[CODE NUMERIC]| |
|[PREMIUM_CALC_RULE]|Varchar2(30)|[VARCHAR30|VARCHARnn]|Y|
|[RATE_BASIS]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[PREMIUM_RATE]|Number(18)|[AMT12V6|AMTnn]| |
|[PREMIUM_PRORATED]|Varchar2(4)|[VARCHAR4|VARCHARnn]| |
|[FREQUENCY_CODE]|Varchar2(16)|[CODE]| |
|[PAY_POINT_TYPE]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[PAY_POINT_SEQUENCE]|Number(5)|[NUMBER5|NUMBERn]| |
|[REPLACEMENT_OPTION]|Varchar2(4)|[VARCHAR4|VARCHARnn]| |
|[HIGHEST_RATE_OF_DAY]|Varchar2(4)|[VARCHAR4|VARCHARnn]| |
|[PREMIUM_WAGE_SOURCE]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[USER_VARIABLE_CODE]|Varchar2(16)|[CODE]| |
|[CUSTOM_PREMIUM_LOGIC]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[CREATE_DATE]|Date()|[DATE]| |
|[CREATE_USER]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[CHANGE_DATE]|Date()|[DATE]| |
|[CHANGE_USER]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
||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 valid unit code defined on [P2K_CM_UNITS].
|[PREMIUM_CODE]|Varchar2(16)|Y|Validation: Must be a unique premium code for the unit.
|[DESCRIPTION]|Varchar2(50)| |
|[PREMIUM_TYPE_CODE]|Varchar2(16)| |Validation: Must be a valid premium type code defined on [P2K_SA_PREMIUM_TYPES].
|[PREMIUM_TYPE_SEQUENCE]|Number(5)| |
|[EFFECTIVE]|Date()|Y|Validation: Must be a valid date format. Suggestion: If you are not loading multiple date-effective records for the same premium 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 premium 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].
|[PC_CODE_DOLLARS]|Number(4)| |Validation: Must be a valid pay component already defined on [P2K_PR_PAY_COMPONENTS].
|[PC_CODE_TIME]|Number(4)| |Validation: Must be a valid pay component already defined on [P2K_PR_PAY_COMPONENTS].
|[PREMIUM_CALC_RULE]|Varchar2(30)|Y|Validation: If provided, must be one of the fixed lexicon values from [X_PREMIUM_CALC_RULE]
|[RATE_BASIS]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_RATE_BASIS].
|[PREMIUM_RATE]|Number(18)| |
|[PREMIUM_PRORATED]|Varchar2(4)| |Validation: This field is a “toggle” field. The value will be translated as False if the value is left NULL, set to “N”, “NO” or “0”. All other values will translate to True.
|[FREQUENCY_CODE]|Varchar2(16)| |
|[PAY_POINT_TYPE]|Varchar2(30)| |
|[PAY_POINT_SEQUENCE]|Number(5)| |
|[REPLACEMENT_OPTION]|Varchar2(4)| |
|[HIGHEST_RATE_OF_DAY]|Varchar2(4)| |
|[PREMIUM_WAGE_SOURCE]|Varchar2(30)| |
|[USER_VARIABLE_CODE]|Varchar2(16)| |
|[CUSTOM_PREMIUM_LOGIC]|Varchar2(30)| |
|[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_PREMIUMS]
[{InsertPage page='Internal.INF_CV_PREMIUMS' default='Click to create a new notes page'}]
This page (revision-8) was last changed on 26-Nov-2021 10:22 by JMyersTop