Search Results hr_positions_f




Overview
Explore in AI Chat

Overview

HR_POSITIONS_F is an APPS-owned secure view within the PER (Human Resources) product family in Oracle E-Business Suite. As documented in the ETRM metadata, it serves as a security-filtered projection over the corresponding _ALL table, HR_ALL_POSITIONS_F. Its principal purpose is to expose position definition data—including the full date-tracked (datetracked) history of each position—while automatically restricting rows according to the security profile of the querying session. Because the view filters through HR_SECURITY, it is the recommended access point for custom reports, concurrent programs, and integration extracts that must respect organization-level and position-level security.

The view is particularly relevant to the search term successor_position_id, since the column SUCCESSOR_POSITION_ID is exposed directly by this view. This column identifies the position that succeeds the current position, typically used for succession planning and continuity-of-role modeling.

Underlying Base Objects

The ETRM documentation lists the following referenced base objects:

  • HR_ALL_POSITIONS_F (SYNONYM) — the primary _ALL date-tracked table holding position definition rows.
  • HR_ALL_POSITIONS_F_TL (SYNONYM) — the translation table providing language-specific position names.
  • HR_GENERAL (PACKAGE) — supplies decoding functions such as DECODE_LATEST_POSITION_DEF_ID, GET_POSITION_DATE_END, and DECODE_POSITION_LATEST_NAME, which the view invokes inline.
  • HR_SECURITY (PACKAGE) — performs the row-level security filtering that distinguishes the secure view from the base table.
  • FND_PROFILE (PACKAGE) — provides profile option values used in the security predicate.

The view is a thin wrapper: it selects the business columns from HR_ALL_POSITIONS_F and adds derived columns through HR_GENERAL. The datetracked columns EFFECTIVE_START_DATE and EFFECTIVE_END_DATE control row visibility, so queries must account for row dating.

Key Columns

Common Use Cases and Queries

Typical scenarios include succession-planning reports, position hierarchy extracts, organization headcount reporting, and integration feeds that must honor security. The following query retrieves current successor relationships:

  • Succession lookup:
SELECT p.position_id,
       p.name,
       p.successor_position_id
FROM   apps.hr_positions_f p
WHERE  p.successor_position_id IS NOT NULL
AND    TRUNC(SYSDATE) BETWEEN p.effective_start_date
                          AND p.effective_end_date;
  • Position with supervisor and job: join HR_POSITIONS_F to HR_ALL_POSITIONS_F_TL for localized names, filtering by business group.
  • Security-aware headcount: aggregate FTE and MAX_PERSONS by organization, relying on the view's built-in HR_SECURITY filter rather than querying the _ALL table directly.

Because the view enforces security and applies HR_GENERAL decoding, it should be preferred over HR_ALL_POSITIONS_F in all custom SQL unless unrestricted access is explicitly required.