Results for “per_contact_relationships”

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

Overview

PER_CONTACT_RELATIONSHIPS is a Human Resources (PER) table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the contact and relationship details that link a person to a related contact person, capturing categories such as dependents, beneficiaries, emergency contacts, and parents. Each row represents a single relationship between an employee or primary person and a designated contact, together with the classification, effective dating, and descriptive flexfield context that qualify that relationship.

From a data-modeling perspective, the ETRM metadata provides a heuristic Data Vault classification of this object as hub-leaning. This should be treated as a modeling suggestion rather than a prescribed design: the table behaves primarily as a source of relationship entities keyed by a surrogate identifier, with a limited number of foreign-key dependencies outward. The single documented foreign key pointing to HR_ALL_ORGANIZATION_UNITS confirms the multi-tenant (business group) orientation typical of HR tables, while the several inbound foreign keys demonstrate that this table functions as a reference point for benefits and contact-related child entities.

Key Information Stored

The table contains 71 documented columns in the 12.2.2 physical schema. The most operationally significant are the following:

• CONTACT_RELATIONSHIP_ID — surrogate primary key, enforced by the unique index PER_CONTACT_RELATIONSHIPS_PK. This is the single documented unique business-key candidate and the column referenced by dependent tables.
• BUSINESS_GROUP_ID — identifies the business group (HR_ALL_ORGANIZATION_UNITS) that owns the relationship record.
• PERSON_ID — the primary person for whom the contact relationship is defined.
• CONTACT_PERSON_ID — the related person or contact being described.
• CONTACT_TYPE and PRIMARY_CONTACT_FLAG — classify the nature of the relationship and indicate whether it is the primary contact.
• DATE_START, START_LIFE_REASON_ID, DATE_END, and END_LIFE_REASON_ID — effective-dating and reason codes governing the active life of the relationship.
• DEPENDENT_FLAG, BENEFICIARY_FLAG, THIRD_PARTY_PAY_FLAG, BONDHOLDER_FLAG, and PERSONAL_FLAG — status flags that drive eligibility and payroll or benefits processing.
• RLTD_PER_RSDS_W_DSGNTR_FLAG and SEQUENCE_NUMBER — indicator and ordering attributes for the related person designation.
• PARTY_ID — links the relationship to the TCA party model where applicable.
• CONT_ATTRIBUTE1..20 and CONT_ATTRIBUTE_CATEGORY — descriptive flexfield columns for customer-specific contact attributes.
• CONT_INFORMATION1..20 and CONT_INFORMATION_CATEGORY — additional flexfield information captured against the contact.
• Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, OBJECT_VERSION_NUMBER, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) support auditability and concurrent program traceability.

A SYS_IL index appears in the documented unique index list; this is the system-managed index associated with a LOB column (COMMENTS) rather than a business-key constraint. The surrogate key CONTACT_RELATIONSHIP_ID, not a composite natural key, is therefore the primary business-key candidate.

Common Use Cases and Queries

Typical use cases include dependent and beneficiary maintenance, emergency contact reporting, and benefits eligibility analysis. A common query pattern joins the relationship record to the dependent and beneficiary child tables using CONTACT_RELATIONSHIP_ID:

• Listing all dependents for a person by filtering on DEPENDENT_FLAG and current effective dates between DATE_START and DATE_END.
• Reporting beneficiaries linked to benefits enrollments through BEN_COVERED_DEPENDENTS_F.
• Identifying COBRA participants via PER_COBRA_COV_ENROLLMENTS and PER_COBRA_DEPENDENTS_F.
• Extracting contact flexfield segments (CONT_ATTRIBUTE1..20) for organizational reporting.
• Populating deployment or reimbursement processes through HR_PERSON_DEPLYMT_CONTACTS and BEN_PRTT_REIMBMT_RQST_F.

Queries should always constrain on BUSINESS_GROUP_ID in multi-organization deployments, and generally filter DATE_END IS NULL or DATE_END > SYSDATE to retrieve currently active relationships. Because CONTACT_PERSON_ID references the person model, joins to PER_ALL_PEOPLE_F on both PERSON_ID and CONTACT_PERSON_ID are standard for resolving names and person numbers.

Related Objects

The documented foreign-key relationships identify the following significant dependent objects:

• HR_ALL_ORGANIZATION_UNITS — referenced via PER_CONTACT_RELATIONSHIPS.BUSINESS_GROUP_ID.
• BEN_COVERED_DEPENDENTS_F — joins on CONTACT_RELATIONSHIP_ID.
• PER_COBRA_COV_ENROLLMENTS — joins on CONTACT_RELATIONSHIP_ID.
• PER_COBRA_DEPENDENTS_F — joins on CONTACT_RELATIONSHIP_ID.
• PER_CONTACT_EXTRA_INFO_F — joins on CONTACT_RELATIONSHIP_ID.
• HR_PERSON_DEPLYMT_CONTACTS — joins on CONTACT_RELATIONSHIP_ID.
• BEN_PRTT_REIMBMT_RQST_F — joins on CONTACT_RELATIONSHIP_ID.

These inbound references confirm that the table acts as a central relationship hub for benefits administration, COBRA processing, deployment, and participant reimbursement within the Oracle EBS HR and Benefits modules.