Search Results per_contact_extra_info_f

Overview

The PER_CONTACT_EXTRA_INFO_F table is a core data object within the Oracle E-Business Suite Human Resources (PER) module. It serves as the primary repository for storing supplemental, type-specific information related to a person's contact relationships. A contact relationship, as defined in the system, is an association between an employee, applicant, or other person and an external contact, such as a dependent, beneficiary, or emergency contact. This table's role is to extend the basic relationship data stored in PER_CONTACT_RELATIONSHIPS by holding additional, often legally or administratively required, details that vary by the type of information being captured.

Key Information Stored

The table is structured as an effective-dated (time-tracked) entity, a standard HRMS design pattern indicated by the '_F' suffix and the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns in its primary key. This allows for the maintenance of historical changes to the extra information. The key columns, as documented, include the unique identifier (CONTACT_EXTRA_INFO_ID), the foreign key to the base relationship (CONTACT_RELATIONSHIP_ID), and the INFORMATION_TYPE. The INFORMATION_TYPE column is critical; it determines the context and format of the additional data stored, which is typically held in attribute columns (not listed in the provided metadata but commonly named CEI_INFORMATION1 through CEI_INFORMATIONn). Examples of information types could be 'BENEFICIARY_DETAILS', 'DEPENDENT_TAX_INFO', or 'EMERGENCY_MEDICAL_NOTES'.

Common Use Cases and Queries

This table is central to processes requiring detailed contact data beyond a name and relationship. Common use cases include benefits enrollment (storing beneficiary percentages or dependent eligibility details), payroll reporting (for tax-related dependent information), and emergency contact management (storing multiple phone numbers or medical alerts). A typical reporting query would join this table to PER_CONTACT_RELATIONSHIPS and then to PER_ALL_PEOPLE_F to retrieve a person's contacts and their associated extra information for a given effective date. For example, to find all emergency medical notes for an employee's contacts, a query would filter on INFORMATION_TYPE and join via CONTACT_RELATIONSHIP_ID. Data is primarily created and maintained through the Oracle HRMS person forms or via the HR Contact and HR Benefits APIs.

Related Objects

The documented foreign key relationships explicitly define this table's dependencies. Its primary integration is with the PER_CONTACT_RELATIONSHIPS table, which holds the core definition of who the contact is and their basic relationship type. The join is performed on the CONTACT_RELATIONSHIP_ID column. This relationship is fundamental; every record in PER_CONTACT_EXTRA_INFO_F must correspond to a valid, existing contact relationship. While not listed in the provided excerpt, this table is also a key source for views such as PER_CONTACT_EXTRA_INFO (the latest effective date snapshot) and is referenced by various HR and Benefits APIs for data validation and processing.