!!!Alias: IVSPM (INF_CV_PREMIUMS) 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) !!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 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. [{If var='loginstatus' contains 'authenticated' ---- ![Discussion|Edit:Internal.INF_CV_PREMIUMS] [{InsertPage page='Internal.INF_CV_PREMIUMS' default='Click to create a new discussion page'}] }]