Results for “contact_relationship_id”

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

Overview

HR_PERSON_DEPLYMT_CONTACTS is a Human Resources (PER) module table within the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. Its documented purpose is to hold contacts that must be recreated in a new business group for employees whose records are being deployed (copied or migrated) between business groups. During business group deployment, Oracle HRMS must transfer dependent person-level data from the source business group to the target business group; this table acts as a staging or reference store for the contact records associated with each deployed employee's deployment process.

The table resides in the HR schema and is documented as VALID, with a physical schema of nine columns in ETRM 12.2.2. The Data Vault classification mined heuristically from the foreign-key structure is standalone. In modeling terms, this suggests HR_PERSON_DEPLYMT_CONTACTS behaves as an independent table rather than as a classic hub, link, or satellite. Although it carries a surrogate primary key and one foreign-key reference, the heuristic classification indicates that, for Data Vault purposes, it can be modeled independently, with its relationship to PER_CONTACT_RELATIONSHIPS handled as a soft or derived association rather than a mandatory parent-child integration point.

Key Information Stored

The table is defined by the primary key constraint HR_PERSON_DEPLYMT_CONTACTS_PK, which is enforced on the column PERSON_DEPLYMT_CONTACT_ID. This surrogate identifier uniquely distinguishes each deployment contact row and should not be treated as a business key.

• PERSON_DEPLYMT_CONTACT_ID — surrogate primary key, uniquely identifying each contact-to-recreate record.
• PERSON_DEPLOYMENT_ID — identifies the person deployment (business group transfer) to which the contact record belongs; the effective parent context for the row even though no foreign key is documented against it.
• CONTACT_RELATIONSHIP_ID — foreign key to PER_CONTACT_RELATIONSHIPS, supplying the relationship definition (for example, emergency contact or dependent relationship type) that must be recreated in the new business group.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle HRMS framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE — standard WHO audit columns recording the user and timestamp of row insertion.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording the most recent modification, its user, and the login session.

No unique indexes beyond the primary key are documented in the ETRM metadata, so PERSON_DEPLOYMENT_ID in combination with CONTACT_RELATIONSHIP_ID is best regarded as a potential business-key candidate for reconciliation purposes rather than a documented constraint.

Common Use Cases and Queries

The principal use case is validating and reconciling contacts carried across business group deployment. Typical SQL patterns join the table to its deployment parent and to the contact relationship definition:

• Enumerating all contacts staged for a given deployment: SELECT * FROM hr.hr_person_deplymt_contacts WHERE person_deployment_id = :deployment_id;
• Decoding relationship types: SELECT c.person_deplymt_contact_id, r.contact_relationship_id FROM hr.hr_person_deplymt_contacts c, per.per_contact_relationships r WHERE c.contact_relationship_id = r.contact_relationship_id;
• Audit and troubleshooting of deployment runs using CREATION_DATE, CREATED_BY, and LAST_UPDATE_DATE to confirm when contact records were staged.

Reporting use cases include pre-deployment readiness checks, post-deployment verification that every expected contact was recreated, and data-quality audits of duplicate CONTACT_RELATIONSHIP_ID values within a single PERSON_DEPLOYMENT_ID.

Related Objects

• PER_CONTACT_RELATIONSHIPS — referenced via CONTACT_RELATIONSHIP_ID; provides the contact relationship definition.
• HR_PERSON_DEPLYMT_CONTACTS_PK — primary key constraint on PERSON_DEPLYMT_CONTACT_ID.
• PER_PERSON_DEPLOYMENTS / person deployment APIs — the deployment process that populates and consumes PERSON_DEPLOYMENT_ID.
• PER_ALL_PEOPLE_F — the person records ultimately affected by business group deployment.
• PER_CONTACT_RELATIONSHIPS_TL — translated relationship names for reporting.
• HR_PERSON_DEPLOYMENTS and related HR deployment tables — companion staging tables populated during the same deployment run.