Results for “person_extra_info_id”

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

Overview

HR.HR_PERSON_DEPLYMT_EITS is a Human Resources (PER) module table in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store "extra information to recreate in a new business group for deployed employees." In practice, the table acts as a bridging construct between a person's deployment record and the extra information types (EITs) that must be carried forward when a deployed employee is re-created or re-homed into a new business group. This supports global deployment and business-group migration flows, where legislative or descriptive EIT data attached to a person must be preserved across organizational boundaries.

The table is owned by the HR schema and holds 9 documented columns with primary key constraint HR_PERSON_DEPLYMT_EITS_PK on PERSON_DEPLYMT_EIT_ID. The mined Data Vault classification is "standalone," but the single foreign key to PER_PEOPLE_EXTRA_INFO indicates a dependent relationship. A reasonable modeling suggestion is to treat this as a satellite-like table attached to the person extra information hub/link, since it records association metadata rather than independent business entities.

Key Information Stored

• PERSON_DEPLYMT_EIT_ID — Surrogate primary key (HR_PERSON_DEPLYMT_EITS_PK); uniquely identifies each deployment EIT row.
• PERSON_DEPLOYMENT_ID — Identifies the deployment record to which the EIT association belongs; a key business-link candidate.
• PERSON_EXTRA_INFO_ID — Foreign key referencing PER_PEOPLE_EXTRA_INFO; ties the row to the underlying EIT instance for the person.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard WHO audit columns recording the most recent updater and timestamp.
• LAST_UPDATE_LOGIN — Login context of the last updating session, used for audit and concurrency diagnostics.

The only documented unique index is the primary key; PERSON_DEPLOYMENT_ID and PERSON_EXTRA_INFO_ID are business-key candidates but are not documented as uniquely constrained.

Common Use Cases and Queries

Typical scenarios include auditing which EITs are staged for re-creation during deployment, reconciling deployment EIT rows against live person extra information, and reporting on migration completeness.

• List EITs staged for a given deployment:
  SELECT e.person_deploymt_eit_id, e.person_extra_info_id FROM hr.hr_person_deploymt_eits e WHERE e.person_deployment_id = :deployment_id;
• Join to the source EIT to inspect values:
  SELECT e.person_deployment_id, p.extra_info_id, p.information_type FROM hr.hr_person_deploymt_eits e JOIN per_people_extra_info p ON p.extra_info_id = e.person_extra_info_id;
• Audit-based reporting on recent changes:
  SELECT * FROM hr.hr_person_deploymt_eits WHERE last_update_date >= :since;
• Orphan detection (EIT referenced but no deployment):
  SELECT e.* FROM hr.hr_person_deploymt_eits e LEFT JOIN per_people_extra_info p ON p.extra_info_id = e.person_extra_info_id WHERE p.extra_info_id IS NULL;

Related Objects

• PER_PEOPLE_EXTRA_INFO — Referenced via PERSON_EXTRA_INFO_ID; holds the actual EIT instances.
• PER_PERSON_DEPLOYMENTS (PER deployment entity) — Logical parent implied by PERSON_DEPLOYMENT_ID.
• PER_BUSINESS_GROUPS — Target group for re-creation; drives the deployment scope.
• PER_PERSON_TYPES / PER_PEOPLE_F — Person identity context for deployed employees.
• Public APIs such as HR_PERSON_DEPLOYMENT_API and the EIT maintenance APIs that populate or consume these rows.