This page (revision-11) 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
11 26-Nov-2021 10:22 3 KB JMyers to previous
10 26-Nov-2021 10:22 3 KB JMyers to previous | to last
9 26-Nov-2021 10:22 3 KB JMyers to previous | to last
8 26-Nov-2021 10:22 3 KB JMyers to previous | to last
7 26-Nov-2021 10:22 2 KB JMyers to previous | to last
6 26-Nov-2021 10:22 2 KB JMyers to previous | to last
5 26-Nov-2021 10:22 11 KB JMyers to previous | to last
4 26-Nov-2021 10:22 15 KB JMyers to previous | to last
3 26-Nov-2021 10:22 1 KB JMyers to previous | to last
2 26-Nov-2021 10:22 997 bytes JMyers to previous | to last
1 26-Nov-2021 10:22 2 KB JMyers to last

Page References

Incoming links Outgoing links
IVSPM
IVSPM

Version management

Difference between version and

At line 1 changed 2 lines
!!!Alias: [IVSPM]
(INF_CV_PREMIUMS)
[{TableOfContents }]
!!!PREMIUM INTERFACE FILE
At line 4 changed one line
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
The Premium Interface File screen is used to import [premium|PREMIUMS] data into the software data structures.
At line 6 changed 30 lines
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)| |
Premium Interface File data is maintained on the [INF_CV_PREMIUMS] table.
At line 37 changed one line
[{If var='loginstatus' contains 'authenticated'
;[ID|ID]:This field identifies the premium record within the data base.
;[Entity|ENTITY_CODE]:Premiums are associated with the entity identified in this field.
;[Unit|UNIT_CODE]:Each premium must be associated with a unit which may be identified in this field.
;[Premium|PREMIUM_CODE]:The name of the premium is identified in this field.
;[Description|DESCRIPTION]:This field holds a description of the premium code.
;[Premium Type|PREMIUM_TYPE_CODE]:In this field, the premium is categorized into one of the premium types created in the [ISPT] form.
;[Premium Type Sequence|PREMIUM_TYPE_SEQUENCE]:The sequence field is used to determine an order of priority for premiums.
;[Effective as of|EFFECTIVE]/[Expires On|EXPIRY]:If the premium is time limited, these field define that time period.
;[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.
;[Pay Component Dollars|PC_CODE_DOLLARS]:This field specifies the pay component code to which dollar amounts are associated with the premium.
;[Pay Component Time|PC_CODE_TIME]:This field specifies specifies the pay component code to which time amounts are associated with the premium.
;[Calculation Rule|PREMIUM_CALC_RULE]:Premium Calc rule is the rule that will be used to calculate the premium.
;[Rate Basis|RATE_BASIS]:This field defines the time period (hour, day, week, year) used with the premium rate value provided.
;[Rate|PREMIUM_RATE]:This is the rate that will be used when the Premium Calc rule includes “premium rate” in the formula.
;[Premium Prorated|PREMIUM_PRORATED]:This field will indicate if the premium paid will be prorated based on the employee’s FTE value.
;[Frequency|FREQUENCY_CODE]:This field will indicate how often the payroll item (deduction, benefit, attendance policy etc.) is processed.
;[Pay Point Type|PAY_POINT_TYPE]:This field displays the point in the payroll cycle when the premium should be processed.
;[Pay Point Sequence|PAY_POINT_SEQUENCE]:This field defines the sequential order of each step taken within a pay point.
;[Replacement Options|REPLACEMENT_OPTION]:This field indicates if the hours and/or earnings will be replaced by the new hours and/or earnings (including premium) calculated when the pay line is generated. The premium will remain attached to the pay line for audit purposes.
;[Highest Rate of Day|HIGHEST_RATE_OF_DAY]:This field indicates if the toggle is ON it provides the ability to apply the highest rate of pay received on that day worked including premiums.
;[Premium Wage Source|PREMIUM_WAGE_SOURCE]:This field defines the source of the premium, either from the pay line or from the highest scale/step rate on the position rec
;[User Variable|USER_VARIABLE_CODE]:This field displays a specific user variable for a premium rather than relying on the user variable associated with the pay component.
;[Custom Premium Logic|CUSTOM_PREMIUM_LOGIC]:If you require custom premium logic, contact your consultant.
At line 40 changed 2 lines
![Discussion|Edit:Internal.IVSPM]
[{InsertPage page='Internal.IVSPM' default='Click to create a new discussion page'}]
![Notes|Edit:Internal.IVSPM]
[{InsertPage page='Internal.IVSPM' default='Click to create a new notes page'}]
At line 43 changed one line
}]
This page (revision-11) was last changed on 26-Nov-2021 10:22 by JMyersTop