Search Results hr_position_name




Overview

APPS.HR_POSITIONS_F is a reporting and integration view in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that exposes position definition data from Oracle HRMS. It presents the effective-dated position records — the "F" suffix denotes the date-tracked (datetrack) entity — together with the translated position name and a wide set of descriptive, financial, and descriptive-flexfield attributes. Because it joins the base position table to its translation table, it resolves the position name in the session's language, returning a single denormalized row per position per effective date range.

The view is the standard access point for reporting on positions without re-implementing the multi-table translation join or the security predicates applied by Oracle HRMS. It is widely used in custom reports, concurrent programs, interfaces, and data extracts where a position name is required alongside its definition.

Underlying Base Objects

The documented referenced base objects are:

  • HR_ALL_POSITIONS_F (synonym) — the effective-dated position definition table holding the physical columns (position_id, effective dates, job_id, organization_id, fte, status, and so on).
  • HR_ALL_POSITIONS_F_TL (synonym) — the translation table supplying the language-specific name and related text.
  • HR_GENERAL (package) — the HRMS utility package used for date-tracked logic and language/date handling.
  • HR_SECURITY (package) — applies security profile filtering so the caller sees only authorized business groups and organizations.
  • FND_PROFILE (package) — supplies profile option values such as session language and business group context.

Consequently the view is a security- and translation-aware projection of HR_ALL_POSITIONS_F rather than a simple one-to-one table alias. It inherits datetrack semantics (effective_start_date, effective_end_date) and the standard HRMS row-level security model.

Key Columns

  • position_id — primary key of the position; effective_start_date / effective_end_date — datetrack interval boundaries.
  • name — the translated position name from HR_ALL_POSITIONS_F_TL; date_effective_name — the date the current name took effect. A search for "hr_position_name" normally resolves to this column.
  • business_group_id, organization_id, location_id — organizational placement used for filtering and joins to HR_ORGANIZATION_UNITS and HR_LOCATIONS_ALL.
  • job_id, entry_grade_id, entry_step_id, pay_basis_id, pay_freq_payroll_id — the job/grade/step and payroll linkage that drives compensation defaults.
  • fte, max_persons, working_hours, frequency, probation_period, permanent_temporary_flag, seasonal_flag, position_type, status — capacity, classification, and lifecycle attributes.
  • supervisor_position_id, prior_position_id, successor_position_id, relief_position_id, supervisor_id — the position hierarchy and succession structure.
  • attribute1..attribute18 and information1..information30 — descriptive flexfield and extra-information segments.

Common Use Cases and Queries

Typical uses include listing current open positions by organization, extracting position-to-job mappings for interfaces, and reporting FTE or headcount capacity by business group. Because the view is effective-dated, most queries filter to the current date.

Sample query returning current position names for a business group:

SELECT position_id, name, job_id, organization_id, fte, status
FROM apps.hr_positions_f
WHERE business_group_id = :p_business_group_id
  AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date
  AND NVL(status,'X') <> 'INACTIVE';

Joining to the job table for a descriptive listing:

SELECT p.name position_name, j.name job_name, p.fte
FROM apps.hr_positions_f p, apps.hr_all_jobs j
WHERE p.job_id = j.job_id
  AND TRUNC(SYSDATE) BETWEEN p.effective_start_date AND p.effective_end_date;

For historical or "as-of" reporting, replace SYSDATE with the required date and restrict the effective interval accordingly. Note that row visibility is governed by HR_SECURITY through the session's security profile, so results are filtered to the organizations and business groups the reporting responsibility is permitted to access.