Results for “hr_all_positions_f”

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

Overview

HR_ALL_POSITIONS_F is the core datable that stores position definition information within the Oracle E-Business Suite Human Resources (PER) module. In EBS 12.1.1 and 12.2.2, a position represents a specific occurrence of a job within an organization, defined independently of the person who occupies it. This distinction is fundamental to Oracle HRMS: jobs describe generic work categories, while positions bind that work to a particular organization, location, grade, and headcount allocation. The table is date-tracked, carrying EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns that support the DateTrack facility used throughout Oracle HRMS.

Based on the documented foreign key structure, the Data Vault classification for this object is a link. It connects independent business entities — jobs, organizations, locations, grades, and position definitions — into a single dated association. This heuristic reflects the table's role as a junction between reference hubs rather than as a standalone hub or satellite.

Key Information Stored

The table carries 136 documented columns. The most significant operational columns are:

• POSITION_ID — surrogate identifier for the position; part of the composite primary key HR_ALL_POSITIONS_F_PK along with the two DateTrack columns. Taken alone, POSITION_ID is the logical reference used by downstream tables.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — DateTrack boundary columns and members of the primary key.
• NAME — the user-facing position name.
• BUSINESS_GROUP_ID — the enterprise business group that owns the position; foreign key to HR_ALL_ORGANIZATION_UNITS.
• ORGANIZATION_ID — the organization unit where the position resides.
• JOB_ID — the job the position instantiates; foreign key to PER_JOBS.
• POSITION_DEFINITION_ID — the reusable position definition template; foreign key to PER_POSITION_DEFINITIONS.
• LOCATION_ID — foreign key to HR_LOCATIONS_ALL.
• ENTRY_GRADE_ID — default grade; foreign key to PER_GRADES.
• PAY_BASIS_ID — foreign key to PER_PAY_BASES.
• AVAILABILITY_STATUS_ID — foreign key to PER_SHARED_TYPES.
• FTE and MAX_PERSONS — headcount and full-time-equivalent capacity.
• SUPERVISOR_ID and SUPERVISOR_POSITION_ID — reporting hierarchy references.
• STATUS and PERMANENT_TEMPORARY_FLAG — lifecycle and type indicators.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 — descriptive flexfield storage.

The unique index HR_ALL_POSITIONS_F_PK (POSITION_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE) represents the business-key candidate for uniqueness; the remaining columns provide descriptive and control context.

Common Use Cases and Queries

Typical reporting scenarios include listing all current positions in a given organization, retrieving the grade and location for a position, and reconciling headcount. A representative query resolves the current datetracked row:

• SELECT position_id, name, job_id, organization_id, fte FROM hr_all_positions_f WHERE organization_id = :org AND SYSDATE BETWEEN effective_start_date AND effective_end_date;
• Joining to PER_JOBS and HR_LOCATIONS_ALL to produce a position register with job title and location.
• Joining PER_ALL_ASSIGNMENTS_F on POSITION_ID to identify incumbents versus vacant positions (MAX_PERSONS compared with assignment count).
• Feeding position hierarchy extracts via SUPERVISOR_POSITION_ID for organizational chart reporting.

Because of the DateTrack model, reports must always anchor on the effective date range rather than assuming a single row per POSITION_ID.

Related Objects

The foreign key metadata identifies the principal related objects and join columns:

• PER_JOBS — joined on HR_ALL_POSITIONS_F.JOB_ID.
• PER_POSITION_DEFINITIONS — joined on POSITION_DEFINITION_ID.
• HR_ALL_ORGANIZATION_UNITS — joined on both BUSINESS_GROUP_ID and ORGANIZATION_ID.
• HR_LOCATIONS_ALL — joined on LOCATION_ID.
• PER_GRADES — joined on ENTRY_GRADE_ID.
• PER_PAY_BASES — joined on PAY_BASIS_ID.
• PER_SHARED_TYPES — joined on AVAILABILITY_STATUS_ID.
• PER_ALL_ASSIGNMENTS_F — dependent child referencing POSITION_ID for incumbents.

Together these objects form the position management model used by Oracle HRMS and Oracle Payroll.