Search Results per_periods_of_placement_pk

Overview

The PER_PERIODS_OF_PLACEMENT table is a Human Resources (PER) module object that stores periods of placement details for a non-payrolled worker. It resides in the HR schema and is classified under the PER - Human Resources product within Oracle E-Business Suite 12.1.1 and 12.2.2. The table captures the contiguous spans of time during which an individual occupies a placement relationship, along with projected and actual termination information and a substantial set of descriptive and descriptive-flexfield attributes. It is a foundational record for workforce placement tracking where the worker is not processed through the payroll stream, allowing organizations to maintain a distinct history of placement arrangements independent of payroll employment records.

From a Data Vault modeling perspective, the provided heuristic classification identifies this object as standalone. This suggests that, in a dimensional or Data Vault representation, PER_PERIODS_OF_PLACEMENT is best treated as an independent satellite-like structure rather than as a hub or link, because the mined foreign-key structure does not reveal strong dependency chains to other parent objects. The table can therefore be modeled as a self-contained history-bearing entity keyed by its own surrogate identifier.

Key Information Stored

The table contains 77 documented columns. The most significant are summarized below, distinguishing the surrogate primary key from the unique business-key candidates.

• PERIOD_OF_PLACEMENT_ID — the surrogate primary key, defined by the PER_PERIODS_OF_PLACEMENT_PK index. It uniquely identifies each placement period record.
• PERSON_ID — identifies the non-payrolled worker to whom the placement period belongs.
• DATE_START — the start date of the placement period. Together with PERSON_ID, this forms the unique business key PER_PERIODS_OF_PLACEMENT_UK1 (PERSON_ID, DATE_START).
• ACTUAL_TERMINATION_DATE — the date the placement actually ended.
• PROJECTED_TERMINATION_DATE — the anticipated end date of the placement.
• TERMINATION_REASON — the reason the placement period was terminated.
• BUSINESS_GROUP_ID — the business group partitioning the record.
• OBJECT_VERSION_NUMBER — the optimistic locking version counter used by the framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the descriptive flexfield columns holding user-defined placement attributes.
• INFORMATION_CATEGORY and INFORMATION1–INFORMATION30 — the additional information flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• FINAL_PROCESS_DATE and LAST_STANDARD_PROCESS_DATE — process control timestamps.

The distinction between the surrogate key and the business key is important: while PERIOD_OF_PLACEMENT_ID provides a stable technical identifier, the PERSON_ID and DATE_START combination enforces the natural uniqueness of a placement start for a given person.

Common Use Cases and Queries

Typical reporting scenarios include identifying active versus terminated placements for non-payrolled workers and reconstructing placement timelines for a given person.

The following query retrieves all placement periods for a person, ordered chronologically:

• SELECT period_of_placement_id, person_id, date_start, actual_termination_date, projected_termination_date, termination_reason FROM per_periods_of_placement WHERE person_id = :p_person_id ORDER BY date_start;

To identify placements that are currently open (no actual termination), the predicate actual_termination_date IS NULL is applied. To compare projected against actual outcomes for reporting on termination accuracy, both termination columns are projected together and the difference calculated.

Related Objects

The metadata classifies the table as standalone and documents only the primary and unique indexes rather than explicit foreign keys. The principal referenced objects derived from the documented key columns are:

• PER_ALL_PEOPLE_F — joined on PER_PERIODS_OF_PLACEMENT.PERSON_ID = PER_ALL_PEOPLE_F.PERSON_ID, providing the person identity details behind each placement.
• PER_ALL_ASSIGNMENTS_F — related through PERSON_ID to link placement periods with assignment records.
• HR_ALL_ORGANIZATION_UNITS — associated through the business group / organization context where relevant.

These relationships allow placement data to be reported alongside core HR person and assignment information, extending the standalone structure into a broader workforce reporting model.