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

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
12 26-Nov-2021 10:22 5 KB khiggs to previous
11 26-Nov-2021 10:22 5 KB jmyers to previous | to last
10 26-Nov-2021 10:22 5 KB jmyers to previous | to last EMAIL_ADDRESS ==> EMAIL_ADDRESS(Disambiguation)
9 26-Nov-2021 10:22 5 KB JMyers to previous | to last
8 26-Nov-2021 10:22 5 KB JEscott to previous | to last
7 26-Nov-2021 10:22 5 KB JEscott to previous | to last
6 26-Nov-2021 10:22 5 KB JEscott to previous | to last
5 26-Nov-2021 10:22 2 KB JEscott to previous | to last
4 26-Nov-2021 10:22 2 KB JEscott to previous | to last
3 26-Nov-2021 10:22 2 KB JEscott to previous | to last
2 26-Nov-2021 10:22 2 KB JEscott to previous | to last
1 26-Nov-2021 10:22 2 KB JEscott to last

Page References

Incoming links Outgoing links
INF_CV_CONTACTS
INF_CV_CONTACTS

Version management

Difference between version and

At line 1 changed one line
!!!Alias: IVECT
!!!Alias: [IVECT]
(INF_CV_CONTACTS)
At line 4 changed one line
Each INF_CV_CONTACTS record will result in the creation of a P2K_HR_CONTACTS record and a P2K_HR_CONTACT_ROLES record. Subsequent records for the same contact, but different contact types will result in only a P2K_HR_CONTACT_ROLES record being created. Contacts are determined to be the same contact through the combination of USER_NAME or PERSON_CODE, FIRST_NAME, LAST_NAME, RELATION and EMPLOYER.
Each INF_CV_CONTACTS record will result in the creation of a [P2K_HR_CONTACTS] record and a [P2K_HR_CONTACT_ROLES] record. Subsequent records for the same contact, but different contact types will result in only a [P2K_HR_CONTACT_ROLES] record being created. Contacts are determined to be the same contact through the combination of [USER_NAME] or [PERSON_CODE], [FIRST_NAME], [LAST_NAME], [RELATION] and [EMPLOYER]. When running the [UVCONTACTS] process the fields [FIRST_NAME] and [LAST_NAME] [MIDDLE_NAME] are case sensitive (ie, "JOHN SMITH" is considered to be a different record than "John Smith").
At line 8 changed one line
|[ID]|Number(10)|[ID]| |
|[ID]|Number(10)| |Used internally to define a unique identification for the record. This field would not be loaded.
At line 11 changed 3 lines
|[USER_NAME]|Varchar2(30)| |
|[PERSON_CODE]|Varchar2(16)| |
|[RELATION]|Varchar2(30)| |
|[USER_NAME]|Varchar2(30)| |Validation: Must be a valid user name defined on [P2K_AM_USERS].
|[PERSON_CODE]|Varchar2(16)| |Validation: Must be a valid [PERSON_CODE] already defined on the [P2K_HR_IDENTITIES] table.
|[RELATION]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_RELATION]
At line 15 changed one line
|[GENDER]|Varchar2(30)| |
|[GENDER]|Varchar2(30)| |Validation: If provided, must be one of the fixed lexicon values from [X_GENDER]
At line 17 changed 2 lines
|[BIRTH_DATE]|Date()|[DATE]| |
|[LANGUAGE_CODE]|Varchar2(30)| |
|[BIRTH_DATE]|Date()| |
|[LANGUAGE_CODE]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_LANGUAGE_CODE]
At line 20 changed 2 lines
|[SALUTATION]|Varchar2(30)| |
|[RANK]|Varchar2(30)| |
|[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]
At line 25 changed 3 lines
|[STATE_PROVINCE_CODE]|Varchar2(16)| |
|[COUNTRY_CODE]|Varchar2(16)| |
|[ZIP_POSTAL]|Varchar2(16)| |
|[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.
At line 31 changed 4 lines
|[MAIL_STATE_PROVINCE_CODE]|Varchar2(16)| |
|[MAIL_COUNTRY_CODE]|Varchar2(16)|[CODE]| |
|[MAIL_ZIP_POSTAL]|Varchar2(16)| |
|[PHONE_NUMBER]|Varchar2(20)| |
|[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]. If you provide a [STATE_PROVINCE_CODE], then you must provide a [COUNTRY_CODE].
|[MAIL_ZIP_POSTAL]|Varchar2(16)| |Validation: Must be formatted in the correct format, for the country indicated
|[PHONE_NUMBER]|Varchar2(20)| |Validation: Must be formatted in the correct format, for the country indicated by the physical location
At line 36 changed one line
|[ALT_PHONE_NUMBER]|Varchar2(20)| |
|[ALT_PHONE_NUMBER]|Varchar2(20)| |Validation: Must be formatted in the correct format, for the country indicated by the physical location.
At line 38 changed 5 lines
|[CELLULAR_NUMBER]|Varchar2(20)| |
|[FAX_NUMBER]|Varchar2(20)| |
|[EMAIL_ADDRESS]|Varchar2(50)| |
|[SECURITY_LEVEL]|Varchar2(30)| |
|[PRIVATE_ITEM]|Varchar2(4)| |
|[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(Field)]|Varchar2(50)| |
|[SECURITY_LEVEL]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_SECURITY_LEVEL]
|[PRIVATE_ITEM]|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
At line 45 changed 5 lines
|[CONTACT_TYPE]|Varchar2(30)| |
|[CREATE_DATE]|Date()| |
|[CREATE_USER]|Varchar2(30)| |
|[CHANGE_DATE]|Date()| |
|[CHANGE_USER]|Varchar2(30)| |
|[CONTACT_TYPE]|Varchar2(30)| |Validation: Must be either a valid lexicon code, or a valid lexicon description from [X_CONTACT_TYPE]
|[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_CONTACTS]
[{InsertPage page='Internal.INF_CV_CONTACTS' default='Click to create a new notes page'}]
This page (revision-12) was last changed on 26-Nov-2021 10:22 by khiggsTop