Results for “per_contact_extra_info_f”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PER_CONTACT_EXTRA_INFO_F is a Human Resources (PER) module table in the HR schema that stores extra information associated with a contact relationship. Within Oracle E-Business Suite 12.1.1 and 12.2.2, this table extends the core contact relationship model by capturing flexible, descriptive attributes that are not held on the parent relationship record itself. It is a date-tracked (effective-dated) table, as indicated by the "F" suffix convention and the presence of EFFECTIVE_START_DATE and EFFECTIVE_END_DATE in its primary key, allowing the same contact relationship to retain multiple historical or future-dated versions of its supplementary information.

From a Data Vault modeling perspective, the metadata's heuristic classification is link. This suggests the table functions primarily as an associative structure that connects a contact relationship to a defined information type, while carrying its own descriptive payload. Analysts building a Data Vault or dimensional model around PER should treat PER_CONTACT_EXTRA_INFO_F as a relationship/link artifact anchored on the parent contact relationship, rather than as an independent hub.

Key Information Stored

The table contains 67 documented columns, most of which are generic descriptive slots. The most significant columns are:

• CONTACT_EXTRA_INFO_ID — Surrogate identifier for the extra information record; the leading column of the composite primary key PER_CONTACT_EXTRA_INFO_PK.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — Effective-dating columns that, together with CONTACT_EXTRA_INFO_ID, form the unique business-key candidate PER_CONTACT_EXTRA_INFO_PK.
• CONTACT_RELATIONSHIP_ID — Foreign key to PER_CONTACT_RELATIONSHIPS, identifying the contact relationship to which this extra information belongs.
• INFORMATION_TYPE — Classifies the nature of the extra information, with a documented foreign key relationship (referencing the information type definition).
• CEI_INFORMATION_CATEGORY and CEI_INFORMATION1 through CEI_INFORMATION30 — Thirty descriptive information slots for the flexible, category-driven payload.
• CEI_ATTRIBUTE_CATEGORY and CEI_ATTRIBUTE1 through CEI_ATTRIBUTE20 — Twenty descriptive attribute slots supporting the standard Oracle descriptive flexfield (DFF) pattern.
• OBJECT_VERSION_NUMBER — Optimistic locking version control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns capturing the process that last modified the row.

Notably, the surrogate key structure (CONTACT_EXTRA_INFO_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE) is both the primary key and the sole documented unique index, making it the definitive business-key candidate for querying current or historical rows.

Common Use Cases and Queries

Typical uses include reporting on the supplementary detail recorded against a contact relationship, auditing changes over time using the effective dates, and extracting information-type-specific attributes for downstream integration. Because the descriptive payload is spread across generic INFORMATIONn and ATTRIBUTEn columns, reporting usually pivots on INFORMATION_TYPE or CEI_INFORMATION_CATEGORY.

A representative current-record query joining the parent relationship follows:

• SELECT cei.contact_relationship_id, cei.information_type, cei.cei_information_category, cei.cei_information1 FROM hr.per_contact_extra_info_f cei WHERE cei.contact_relationship_id = :p_relationship_id AND SYSDATE BETWEEN cei.effective_start_date AND NVL(cei.effective_end_date, SYSDATE);
• Historical versioning: order by EFFECTIVE_START_DATE DESC to retrieve the most recent row per relationship and information type.
• Audit reporting: filter on LAST_UPDATE_DATE and PROGRAM_ID to identify changes applied by a specific concurrent program.
• DFF extraction: select CEI_ATTRIBUTE_CATEGORY and CEI_ATTRIBUTE1..CEI_ATTRIBUTE20 to report descriptive flexfield content.

Related Objects

The following objects are most significant, based on the documented foreign key and primary key relationships and standard PER integration patterns:

• PER_CONTACT_RELATIONSHIPS — Parent table; joined via PER_CONTACT_EXTRA_INFO_F.CONTACT_RELATIONSHIP_ID.
• PER_CONTACT_EXTRA_INFO_F.INFORMATION_TYPE — Referenced lookup/definition for the information type classification.
• PER_CONTACT_EXTRA_INFO_PK — Primary key constraint and unique index on (CONTACT_EXTRA_INFO_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE).
• PER_CONTACTS / PER_PERSONS — Higher-level contact and person entities reached transitively through PER_CONTACT_RELATIONSHIPS.
• HR_ CONTACT APIs / PER_CONTACT_EXTRA_INFO_ API — Business-layer APIs that insert and maintain rows in this table (contact extra information maintenance).
• FND concurrency / WHO audit context — REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID referencing concurrent program execution for change tracking.

Together these relationships establish PER_CONTACT_EXTRA_INFO_F as the flexible-attribute satellite of the contact relationship model, effective-dated and audited for the PER Human Resources module.