Results for “hr_person_deployments”

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

Overview

HR.HR_PERSON_DEPLOYMENTS is a Human Resources table within the PER (People) product family of Oracle E-Business Suite, available in both the 12.1.1 and 12.2.2 releases. It stores the record of cross-business group periods of work for an employee, capturing the movement of a person from a source business group to a destination business group for a defined interval. In global or multi-legal-entity implementations, this table provides the transactional backbone for tracking deployments, transfers, and international assignments where the employing entity, payroll, and statutory reporting responsibilities change during the deployment window.

From a data modeling perspective, the ETRM heuristic Data Vault classification for this table is standalone. This implies that, when viewed through a Data Vault lens, the object can be treated as a self-contained satellite-style record rather than a classical hub or link, since the mined foreign key structure does not place it at the center of an associative relationship. This classification is a modeling suggestion only; in practice the table functions as an operational transaction record with defined outbound references to surrounding reference objects.

Key Information Stored

The documented physical schema contains 70 columns. The most significant are summarized below.

• PERSON_DEPLOYMENT_ID — the surrogate primary key uniquely identifying each deployment record.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications framework for concurrent update control.
• FROM_BUSINESS_GROUP_ID and TO_BUSINESS_GROUP_ID — the source and destination business groups between which the deployment occurs.
• FROM_PERSON_ID and TO_PERSON_ID — the person record identifiers on each side of the deployment.
• PERSON_TYPE_ID — the person type assigned for the deployment; LEAVING_PERSON_TYPE_ID captures the type on exit.
• START_DATE and END_DATE — the effective period of the deployment.
• DEPLOYMENT_REASON and LEAVING_REASON — coded explanations for initiation and termination.
• EMPLOYEE_NUMBER — the business identifier for the deployed employee, a natural candidate key alongside the surrogate.
• STATUS, STATUS_CHANGE_REASON, and STATUS_CHANGE_DATE — lifecycle state tracking.
• ORGANIZATION_ID, LOCATION_ID, JOB_ID, POSITION_ID, and GRADE_ID — the core assignment attributes in effect during deployment.
• SUPERVISOR_ID and RETAIN_DIRECT_REPORTS — supervisory relationship and reporting-line retention flag.
• PAY_BASIS_ID, PAYROLL_ID, PEOPLE_GROUP_ID, and PROPOSED_SALARY — payroll and compensation context.
• PER_INFORMATION1 through PER_INFORMATION30 — descriptive flexfield (DFF) storage for installation-specific attributes.

Foreign keys documented include PAY_BASIS_ID → PER_PAY_BASES, PEOPLE_GROUP_ID → PAY_PEOPLE_GROUPS, SOFT_CODING_KEYFLEX_ID → HR_SOFT_CODING_KEYFLEX, and ASSIGNMENT_STATUS_TYPE_ID → PER_ASSIGNMENT_STATUS_TYPES. Business-key candidates are typically formed from the deployment identifier combined with the employee number and effective dates.

Common Use Cases and Queries

Typical reporting scenarios include active deployment rosters, cross-business-group transfer audits, and payroll reconciliation for employees working outside their home entity.

• Listing active deployments for a business group for a given date range.
• Auditing deployment reasons against leaving reasons for turnover analysis.
• Reconciling deployed employees to payroll and people group assignments.
• Tracking assignment status transitions during deployment.

A representative query pattern:

• SELECT person_deployment_id, employee_number, from_business_group_id, to_business_group_id, start_date, end_date, status
• FROM hr.hr_person_deployments
• WHERE to_business_group_id = :p_bg_id
• AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);

Related Objects

The following objects are referenced by or depend upon HR_PERSON_DEPLOYMENTS, based on the documented foreign key structure.

• PER_PAY_BASES — joined via PAY_BASIS_ID to resolve pay basis definitions.
• PAY_PEOPLE_GROUPS — joined via PEOPLE_GROUP_ID for payroll grouping.
• HR_SOFT_CODING_KEYFLEX — joined via SOFT_CODING_KEYFLEX_ID for soft coding distributions.
• PER_ASSIGNMENT_STATUS_TYPES — joined via ASSIGNMENT_STATUS_TYPE_ID to decode status values.
• PER_BUSINESS_GROUPS and PER_ALL_PEOPLE_F — referenced by the business group and person identifier columns for contextual resolution.
• PER_ALL_ASSIGNMENTS_F — the assignment history that the deployment ultimately materializes into.

Deployments are generally driven through the Oracle HRMS deployment and transfer function of the People Management module, with the table acting as the persistent record behind those transactional forms.