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

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
24 26-Nov-2021 10:22 6 KB kparrott to previous
23 26-Nov-2021 10:22 6 KB jmyers to previous | to last
22 26-Nov-2021 10:22 6 KB jmyers to previous | to last EMAIL_ADDRESS ==> EMAIL_ADDRESS(Disambiguation)
21 26-Nov-2021 10:22 6 KB jmyers to previous | to last

Page References

Incoming links Outgoing links
IVEPS
IVEPS

Version management

Difference between version and

At line 1 changed 2 lines
!!!Alias: [IVEPS]
(INF_CV_PERSONALS)
[{TableOfContents }]
!!!PERSONAL INTERFACE FILE
At line 4 changed one line
The INF_CV_PERSONALS table is used to import employee identity and personal information into the software data structures. Basic employee information is created through Identity and Personal tables.
The Personal Interface File screen is used to import personal records into the software data structures.
At line 6 changed 61 lines
Tables loaded:
*[P2K_HR_IDENTITIES] (first record for each employee only)
*[P2K_HR_PERSONALS] (first record and subsequent effective splits)
*[P2K_HR_ALIASES] (subsequent records only)
*[P2K_AM_USER_FIELD_VALUES] (one per user field specified)
!!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.
|[PERSON_CODE]|Varchar2(16)|Y|Validation: Must be a unique person code on the [P2K_HR_IDENTITIES] table.
|[USER_NAME]|Varchar2(30)| |Validation: Must be a valid user name defined on [P2K_AM_USERS].
|[GOVERNMENT_CODE]|Varchar2(16)| |This field is required if this record is the first [INF_CV_PERSONALS] record for this employee that will result in the creation of a [P2K_HR_IDENTITIES] record. It is not required if it is a subsequent record that will result in the “splitting” of the [P2K_HR_PERSONALS] record.
|[FIRST_NAME]|Varchar2(50)|Y|
|[LAST_NAME]|Varchar2(50)|Y|
|[BIRTH_DATE]|Date()| |
|[GENDER]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_GENDER]
|[LANGUAGE_CODE]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_LANGUAGE_CODE]
|[ETHNIC]|Varchar2(30)| |This field is required if this record is the first [INF_CV_PERSONALS] record for this employee that will result in the creation of a [P2K_HR_IDENTITIES] record. It is not required if it is a subsequent record that will result in the “splitting” of the [P2K_HR_PERSONALS] record. Validation: If provided, must be one of the fixed lexicon values from [X_ETHNIC]
|[MIDDLE_NAME]|Varchar2(50)| |
|[SALUTATION]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_SALUTATION]
|[RANK]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_RANK]
|[BIRTHPLACE]|Varchar2(50)| |
|[CHALLENGED]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_CHALLENGED]
|[VETERAN_STATUS]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_VETERAN_STATUS]
|[GOVT_CODE_VERIFIED]|Varchar2(4)| |
|[PHOTO_LOCATION]|Varchar2(50)| |
|[DRIVERS_LICENSE]|Varchar2(30)| |
|[ALT_LANGUAGE_CODE]|Varchar2(30)| |
|[GOVT_CODE_ORIGIN]|Varchar2(30)| |
|[EFFECTIVE]|Date()|Y|Validation: Must be a valid date format. Suggestion: If you are not loading multiple date-effective records for the same person 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 person 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]
|[GEO_CODE]|Varchar2(16)| |Validation: The GEO Code must be a valid GEO code on the [P2K_CM_TAX_JURISDICTIONS] table. If the [STATE_PROVINCE_CODE] is provided, then the [GEO_CODE] must be within that specific state, as well.
|[ADDRESS_LINE_1]|Varchar2(50)| |
|[ADDRESS_LINE_2]|Varchar2(50)| |
|[LOCALITY]|Varchar2(50)| |
|[STATE_PROVINCE_CODE]|Varchar2(16)| |Validation: Must be a valid state code or province code, for the [COUNTRY_CODE] indicated on [P2K_CM_STATE_PROVINCES].
|[COUNTRY_CODE]|Varchar2(16)| |Validation: Must be a valid country code on [P2K_CM_COUNTRIES]. If you provide a [STATE_PROVINCE_CODE], then you must provide a [COUNTRY_CODE].
|[ZIP_POSTAL]|Varchar2(16)| |Validation: Must be formatted in the correct format, for the country indicated.
|[MAIL_ADDRESS_LINE_1]|Varchar2(50)| |
|[MAIL_ADDRESS_LINE_2]|Varchar2(50)| |
|[MAIL_LOCALITY]|Varchar2(50)| |
|[MAIL_STATE_PROVINCE_CODE]|Varchar2(16)| |Validation: Must be a valid state code or province code, for the [COUNTRY_CODE] indicated on [P2K_CM_STATE_PROVINCES].
|[MAIL_COUNTRY_CODE]|Varchar2(16)| |Validation: Must be a valid country code on [P2K_CM_COUNTRIES].
|[MAIL_ZIP_POSTAL]|Varchar2(16)| |Validation: Must be formatted in the correct format, for the country indicated for the mailing address.
|[PHONE_UNLISTED]|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.
|[PHONE_NUMBER]|Varchar2(20)| |Validation: Must be formatted in the correct format, for the country indicated by the physical location
|[ALT_PHONE_NUMBER]|Varchar2(20)| |Validation: Must be formatted in the correct format, for the country indicated by the physical location.
|[CELLULAR_NUMBER]|Varchar2(20)| |Validation: Must be formatted in the correct format, for the country indicated by the physical location
|[FAX_NUMBER]|Varchar2(20)| |Validation: Must be formatted in the correct format, for the country indicated by the physical location.
|[EMAIL_ADDRESS]|Varchar2(50)| |
|[MARITAL_STATUS]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_MARITAL_STATUS]
|[MARRIED_DATE]|Date()| |Validation: Must be a valid date
|[NUMBER_DEPENDENTS]|Number(5)| |
|[YEARS_EDUCATION]|Number(5)| |
|[TRANSPORTATION]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_TRANSPORTATION]
|[BONDED_STATUS]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_BONDED]
|[CITIZEN_STATUS]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_CITIZEN_STATUS]
|[FOREIGN_CODE]|Varchar2(16)| |
|[CITIZENSHIP]|Varchar2(16)| |
|[SCHOOL_DISTRICT_CODE]|Varchar2(16)| |Validation: Must be a valid school district code defined on [P2K_CM_SCHOOL_DISTRICTS].
Personal Interface File data is maintained on the [INF_CV_PERSONALS] table.
;[ID|ID]:This field uniquely identifies the personal record within the data base.
;[|PERSON_CODE]:
;[|USER_NAME]:
;[|GOVERNMENT_CODE]:
;[|FIRST_NAME]:
;[|LAST_NAME]:
;[|BIRTH_DATE]:
;[|GENDER]:
;[|LANGUAGE_CODE]:
;[|ETHNIC]:
;[|MIDDLE_NAME]:
;[|SALUTATION]:
|[RANK]:
|[BIRTHPLACE]:
|[CHALLENGED]:
|[VETERAN_STATUS]:
|[GOVT_CODE_VERIFIED]:
|[PHOTO_LOCATION]:
|[DRIVERS_LICENSE]:
|[ALT_LANGUAGE_CODE]:
|[GOVT_CODE_ORIGIN]:
|[EFFECTIVE]:
|[EXPIRY]:
|[CHANGE_CODE]:
|[GEO_CODE]:
|[ADDRESS_LINE_1]:
|[ADDRESS_LINE_2]:
|[LOCALITY]:
|[STATE_PROVINCE_CODE]:
|[COUNTRY_CODE]:
|[ZIP_POSTAL]:
|[MAIL_ADDRESS_LINE_1]:
|[MAIL_ADDRESS_LINE_2]:
|[MAIL_LOCALITY]:
|[MAIL_STATE_PROVINCE_CODE]:
|[MAIL_COUNTRY_CODE]:
|[MAIL_ZIP_POSTAL]:
|[PHONE_UNLISTED]:
|[PHONE_NUMBER]:
|[ALT_PHONE_NUMBER]:
|[CELLULAR_NUMBER]:
|[FAX_NUMBER]:
|[EMAIL_ADDRESS]:
|[MARITAL_STATUS]:
|[MARRIED_DATE]:
|[NUMBER_DEPENDENTS]:
|[YEARS_EDUCATION]:
|[TRANSPORTATION]:
|[BONDED_STATUS]:
|[CITIZEN_STATUS]:
|[FOREIGN_CODE]:
|[CITIZENSHIP]:
|[SCHOOL_DISTRICT_CODE]:
This page (revision-24) was last changed on 26-Nov-2021 10:22 by kparrottTop