Results for “hr_positions_x”

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

Overview

HR_POSITIONS_X is a date-effective, secured view owned by the APPS schema in Oracle E-Business Suite, belonging to the PER (Human Resources) product family. It is defined over HR_POSITIONS_F, the foundational date-tracked table that stores the full history of position definitions, and it layers date-effective resolution and row-level security on top of that data. Where HR_POSITIONS_F exposes every dated row for a position, HR_POSITIONS_X resolves the effective record for a given point in time and applies the security profile of the connecting user, returning only the positions that user is entitled to see.

The view is primarily consumed for reporting, integration, and downstream processing where a stable, security-aware, point-in-time picture of positions is required. Because it is date-effective, the view reflects the position as it stood on a specific date rather than its most recent state alone, making it suitable for historical analysis, headcount reconciliation, and workforce planning extracts.

Underlying Base Objects

According to the ETRM metadata, HR_POSITIONS_X references the following documented base objects:

• HR_POSITIONS_F (VIEW) — the primary date-tracked source supplying position attributes and their effective date ranges.
• HR_SECURITY (PACKAGE) — applies the security profile logic that restricts rows to the positions a user may access.
• HR_GENERAL (PACKAGE) — provides helper functions used within the view text, such as DECODE_LATEST_POSITION_DEF_ID, GET_POSITION_DATE_END, and DECODE_POSITION_LATEST_NAME.
• FND_PROFILE (PACKAGE) — used to resolve profile option settings that influence date-effective and security behavior.

The view therefore inherits its business data from HR_POSITIONS_F while deferring security enforcement and date resolution to the HR_SECURITY and HR_GENERAL packages. Callers benefit from these transformations without needing to reproduce the security or effective-dating logic themselves.

Key Columns

The view exposes the core position definition columns together with several date and status attributes relevant to reporting. The column REPLACEMENT_REQUIRED_FLAG, which prompted the search, indicates whether a replacement is required for the position, typically used in recruitment and succession planning. Other notable columns include:

• POSITION_ID — the unique identifier for the position.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effective boundaries of the record.
• JOB_ID, ORGANIZATION_ID, LOCATION_ID — the job, organization, and location assigned to the position.
• PERMANENT_TEMPORARY_FLAG, POSITION_TYPE — classify the nature and duration of the position.
• PERMIT_RECRUITMENT_FLAG — indicates whether the position may be recruited against.
• REVIEW_FLAG, SEASONAL_FLAG — additional position characteristics.
• STATUS — the current status of the position record.
• ATTRIBUTE1 through ATTRIBUTE30 — descriptive flexfield segments.

These columns, combined with the date-effective range, enable precise historical and current-state queries.

Common Use Cases and Queries

Typical scenarios include listing all positions requiring replacement, extracting recruiting-eligible positions for a given organization, and reconciling position headcount as of a specific date. A representative query for the searched flag is:

SELECT position_id, effective_start_date, effective_end_date, position_type, replacement_required_flag FROM apps.hr_positions_x WHERE replacement_required_flag = 'Y' AND SYSDATE BETWEEN effective_start_date AND effective_end_date ORDER BY position_id;

Because the view enforces HR security automatically, results are limited to positions the querying user is authorized to view, making it safe for ad hoc reporting by line managers and HR analysts alike.