Search Results date_effective_name




Overview
Explore in AI Chat

Overview

APPS.HR_POSITIONS is a reportable, security-enabled view over the Oracle E-Business Suite Human Resources position–definition model. In EBS 12.1.1 and 12.2.2 it exposes one row per position-version as defined in the HR_POSITIONS_F datetracked entity, resolving the effective-date context (effective start/end, current and historical versions) through the HR_GENERAL package and the session context established by FND_PROFILE and FND_SESSIONS. It is the primary read interface used by HRMS reports, position hierarchies, headcount and establishment reporting, iRecruitment vacancy display, and downstream integrations that need position attributes without touching the datetracked base table directly. The view also enforces HR security (HR_SECURITY) where position-level security is enabled in the business group, so query results are automatically filtered by the accessing responsibility and user's security profile. Because it is a view rather than a table, it carries no physical storage and is subject to the same datetrack semantics as the underlying entity.

Underlying Base Objects

The documented dependencies are HR_POSITIONS_F (view), HR_GENERAL (package), HR_SECURITY (package), FND_PROFILE (package) and FND_SESSIONS (synonym). HR_POSITIONS_F is the datetracked position definition view that supplies the effective-dated attribute rows — POSITION_ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, NAME, STATUS and the descriptive attributes. HR_GENERAL contributes the derived date columns: the view calls HR_GENERAL.GET_POSITION_DATE_END(position_id) to populate DATE_END, which is the effective end date of the current version. FND_PROFILE and FND_SESSIONS resolve the business group, date-track session date, and access context used to determine which datetrack row qualifies as "current" for the querying session. HR_SECURITY applies position and organization security filtering so that users only see positions permitted by their security profile.

Key Columns

Common Use Cases and Queries

Typical uses include current-position listings, vacancy and requisition validation, position hierarchy extraction, and point-in-time reporting of historical position names using date_effective_name. A current-position query filtered to the session date:

  • SELECT p.position_id, p.name, p.date_effective_name, p.organization_id, p.job_id, p.status FROM apps.hr_positions p WHERE p.business_group_id = :p_bg AND TRUNC(SYSDATE) BETWEEN p.effective_start_date AND NVL(p.effective_end_date, HR_GENERAL.GET_POSITION_DATE_END(p.position_id)+1);
  • SELECT p.supervisor_position_id, p.name FROM apps.hr_positions p WHERE p.date_effective = :l_date AND p.business_group_id = :p_bg — as-of reporting using date_effective and date_effective_name.
  • SELECT COUNT(*) FROM apps.hr_positions p WHERE p.organization_id = :org AND p.permit_recruitment_flag = 'Y'; — recruitment-eligible positions.

Because security is applied within the view, integrations should connect as the appropriate APPS responsibility or grant explicit position security rather than querying HR_POSITIONS_F directly.