Search Results hr_all_positions




Overview
Explore in AI Chat

Overview

HR_ALL_POSITIONS is a date-effective, multilingual view owned by the APPS schema in Oracle E-Business Suite, defined under the PER (Human Resources) product. It presents position records as maintained in Oracle HRMS, exposing both date-tracked attributes and derived values that simplify reporting and integration. Because positions are date-effective entities, the view relies on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to describe the temporal validity of each row, and it is primarily intended to serve as a reporting and integration layer over the underlying position base table rather than as a transactional entry point.

The view is documented as VALID in ETRM for 12.1.1 and 12.2.2 and is commonly referenced when consumers need position information tied to grade, job, location, organization, and headcount planning. The user search term entry_grade_id maps directly to a column in this view, reflecting the frequent requirement to identify the grade associated with a position for compensation, progression, and budgeting analysis.

Underlying Base Objects

Per the documented ETRM metadata, HR_ALL_POSITIONS is defined over the following objects:

  • HR_ALL_POSITIONS_F (SYNONYM) — the core date-effective position table holding the authoritative position attributes.
  • FND_SESSIONS (SYNONYM) — the applications session table, used in conjunction with date-effective logic and language/session context.
  • HR_GENERAL (PACKAGE) — the HR utility package supplying derived values and decode functions embedded in the view text.

The view text itself demonstrates this dependency through calls such as HR_GENERAL.DECODE_LATEST_POSITION_DEF_ID, HR_GENERAL.GET_POSITION_DATE_END, and HR_GENERAL.DECODE_POSITION_LATEST_NAME. These functions resolve the latest position definition, compute the effective end date, and decode the position name, respectively, ensuring that consumers see normalized, date-appropriate results without writing their own date-effective logic.

Key Columns

The view exposes a broad set of columns. The most significant include:

Common Use Cases and Queries

A typical requirement is to retrieve current positions and their entry grades for a business group. Because the view is date-effective, queries should filter by SYSDATE between the effective dates.

SELECT position_id, entry_grade_id, job_id, organization_id
FROM apps.hr_all_positions
WHERE business_group_id = :p_bg_id
AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

To join to grade definitions for grade names, consumers typically link ENTRY_GRADE_ID to PER_GRADES. The view is also widely used for integration extracts feeding downstream scheduling, budgeting, and headcount reports, where the decoded position name and latest definition identifiers remove the burden of resolving date-effective changes at the source.