This page (revision-10) 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
10 26-Nov-2021 10:22 4 KB JMyers to previous
9 26-Nov-2021 10:22 4 KB JMyers to previous | to last
8 26-Nov-2021 10:22 4 KB JMyers to previous | to last
7 26-Nov-2021 10:22 4 KB JEscott to previous | to last
6 26-Nov-2021 10:22 4 KB JEscott to previous | to last
5 26-Nov-2021 10:22 4 KB JEscott to previous | to last
4 26-Nov-2021 10:22 4 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_ENROLLMENTS
INF_CV_ENROLLMENTS

Version management

Difference between version and

At line 1 changed 2 lines
!!!Alias: IVBEN
The INF_CV_ENROLLMENTS table is used to import the list of benefit plans and coverage’s that an employee has elected to participate in into the software data structures. The Plan, Coverage and Benefit Components must be defined in the benefit module before loading in ENROLLMENT records
!!!Alias: [IVBEN]
(INF_CV_ENROLLMENTS)
The INF_CV_ENROLLMENTS table is used to import the list of benefit plans and coverages that an employee has elected to participate in into the software data structures. The [Plan|PLAN_CODE], [Coverage|COVERAGE_CODE] and [Benefit Components|BENEFIT COMPONENTS] must be defined in the benefit module before loading in ENROLLMENT records.
Tables loaded:
*[P2K_BE_ENROLLMENTS]
*[P2K_BE_ENROLLMENT_DETAILS]
*[P2K_BE_ENROLLMENT_COMPONENTS]
At line 5 changed 31 lines
||Column name||Data Type / Size||Domain||Mand.||Notes
|[ID]|Number(10)|[ID]| |
|[ENTITY_CODE]|Varchar2(16)|[CODE]|Y|
|[PERSON_CODE]|Varchar2(16)|[CODE]|Y|
|[EMPLOYMENT_TYPE]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[HIRE_DATE]|Date()|[DATE]| |
|[PLAN_CODE]|Varchar2(16)|[CODE]|Y|
|[EFFECTIVE]|Date()|[EFFECTIVE]|Y|
|[EXPIRY]|Date()|[EXPIRY]|Y|
|[CHANGE_CODE]|Varchar2(16)|[CODE]| |
|[COVERAGE_CODE]|Varchar2(16)|[CODE]| |
|[FREQUENCY_CODE]|Varchar2(16)|[CODE]| |
|[PARTICIPATION_RULE]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[COVERAGE_STEP_CODE]|Varchar2(16)|[CODE]| |
|[DESCRIPTION]|Varchar2(50)|[DESCRIPTION]| |
|[UNOFFICIAL]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[ENROLLMENT_STATUS]|Varchar2(30)|[VARCHAR30|VARCHARnn]| |
|[ELIGIBILITY_START_DATE]|Date()|[DATE]| |
|[ELIGIBILITY_END_DATE]|Date()|[DATE]| |
|[PREMIUM_START_DATE]|Date()|[DATE]| |
|[PREMIUM_END_DATE]|Date()|[DATE]| |
|[PLAN_REG_NUMBER]|Varchar2(50)|[VARCHAR50|VARCHARnn]| |
|[EVIDENCE_OF_INSURANCE]|Varchar2(4)|[VARCHAR4|VARCHARnn]| |
|[PERCENTAGE]|Number(5)|[PERCENT]| |
|[BC_CODE]|Varchar2(16)|[CODE]| |
|[AMOUNT]|Number(18)|[AMT12V6|AMTnn]| |
|[AMOUNT_OVERRIDE]|Number(18)|[AMT12V6|AMTnn]| |
|[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|Not moved to the software data structures, but used for validation of the employment record. Validation: The Entity Code provided must be defined on [P2K_CM_ENTITIES]
|[PERSON_CODE]|Varchar2(16)|Y|Destination: Not moved to the software data structures, but used for validation of the employment record. Validation: Must be a valid [PERSON_CODE] already defined on the [P2K_HR_IDENTITIES] table.
|[EMPLOYMENT_TYPE]|Varchar2(30)| |Not moved to the software data structures, but used for validation of the employment record. Validation: The employee must have an active employment record for this employment type. Must be one of the fixed lexicon values from [X_EMPLOYMENT_TYPE]. Derivation: If you do not provide an employment type value, the conversion application will look for any [P2K_HR_EMPLOYMENTS] record that matches the other criteria. Suggestion: If you are loading employees, you can set this field to a fixed value of ‘01’
|[HIRE_DATE]|Date()| |Validation: Must be a valid date. Derivation: If you do not provide a hire date, the conversion application will look for any [P2K_HR_EMPLOYMENTS] record that matches the other criteria.
|[PLAN_CODE]|Varchar2(16)|Y|
|[EFFECTIVE]|Date()|Y|Validation: The [EFFECTIVE] date in the interface file must fall between the [EFFECTIVE] and [EXPIRY] date of the Coverage Detail record.
|[EXPIRY]|Date()|Y|Validation: Must be equal to, or greater than the [EFFECTIVE] date
|[CHANGE_CODE]|Varchar2(16)| |Validation: The Change Code provided must be defined on [P2K_CM_CHANGE_REASONS]. Suggestion: Set this value to CONVERSION to identify these records in the future.
|[COVERAGE_CODE]|Varchar2(16)| |Validation: The coverage code must match exactly to the coverage name defined in the [IBPN] screen.
|[FREQUENCY_CODE]|Varchar2(16)| |Validation: Validated against the frequency code in the [IPPF] screen
|[PARTICIPATION_RULE]|Varchar2(30)| |Validation: Validated against the [Participation Rule|X_PARTICIPATION_RULE] lexicon. Suggestion: Leave NULL and allow to derive. Derivation: Derived from the Participation Rule defined for the Plan.
|[COVERAGE_STEP_CODE]|Varchar2(16)| |
|[DESCRIPTION]|Varchar2(50)| |
|[UNOFFICIAL]|Varchar2(30)| |Validation: Validated against the [UNOFFICIAL|X_UNOFFICIAL] lexicon. Defaults: This will default to a value of ‘1’, to indicate an official record.
|[ENROLLMENT_STATUS]|Varchar2(30)| |Must be one of the fixed lexicon values from [X_ENROLLMENT_STATUS].
|[ELIGIBILITY_START_DATE]|Date()| |Validation: No validation performed, must be a valid date. Suggestion: 01-Jan-0001
|[ELIGIBILITY_END_DATE]|Date()| |Validation: No validation performed, must be a valid date. Suggestion: 31-Dec-3999
|[PREMIUM_START_DATE]|Date()| |Validation: No validation performed, must be a valid date. Suggestion: 01-Jan-0001
|[PREMIUM_END_DATE]|Date()| |Validation: No validation performed, must be a valid date. Suggestion: 31-Dec-3999
|[PLAN_REG_NUMBER]|Varchar2(50)| |
|[EVIDENCE_OF_INSURANCE]|Varchar2(4)| |Validation: NULL, '0', 'N' or 'NO' will set this to false, all other values will set to true
|[PERCENTAGE]|Number(5)| |
|[BC_CODE]|Varchar2(16)| |
|[AMOUNT]|Number(18)| |
|[AMOUNT_OVERRIDE]|Number(18)| |
|[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_ENROLLMENTS]
[{InsertPage page='Internal.INF_CV_ENROLLMENTS' default='Click to create a new notes page'}]
This page (revision-10) was last changed on 26-Nov-2021 10:22 by JMyersTop