Results for “position_availability_status”

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

Overview

APPS.PER_POSITIONS_LOV_V2 is a predefined Oracle E-Business Suite view that supplies a filtered list of valid positions for use as a List of Values (LOV) source. In Oracle EBS 12.1.1 and 12.2.2 the view is owned by the APPS schema and is typically referenced by forms, concurrent programs, and custom reports that require position selection. The view returns only the columns needed to populate an LOV — position name, position identifier, organization, job, and business group — rather than exposing the full HR_ALL_POSITIONS_F record.

Because the view filters on date-effective status, language, business group, and security, it returns only positions the current session is authorized to see. A user searching on position_id in an EBS form or ad hoc query will commonly find this view as the driving source, since POSITION_ID is the primary key through which position records are joined to other HR objects.

Underlying Base Objects

The ETRM 12.2.2 metadata lists the following base objects, referenced through synonyms in the APPS schema:

• HR_ALL_POSITIONS_F — the date-effective position table holding POSITION_ID, ORGANIZATION_ID, JOB_ID, BUSINESS_GROUP_ID, AVAILABILITY_STATUS_ID, STATUS, and effective dates.
• HR_ALL_POSITIONS_F_TL — the translation table supplying the language-specific position NAME.
• PER_SHARED_TYPES — the shared lookup table restricting results to availability statuses of lookup type POSITION_AVAILABILITY_STATUS.
• FND_SESSIONS — the session table used to derive the current effective date via FND_SESSIONS.EFFECTIVE_DATE.
• HR_GENERAL (package) — provides get_business_group_id and get_xbg_profile for business group determination.
• HR_SECURITY (package) — supplies VIEW_ALL and SHOW_RECORD to enforce row-level security on positions and organizations.

The view joins HR_ALL_POSITIONS_F to its translation row on POSITION_ID and language, to PER_SHARED_TYPES on availability status, and to FND_SESSIONS on SESSION_ID, producing a denormalized, security-filtered projection.

Key Columns

• NAME — the translated position name from HR_ALL_POSITIONS_F_TL, matching the user's session language (USERENV('LANG')).
• POSITION_ID — the unique identifier of the position; this is the value most users search on and the key that other HR tables reference.
• ORGANIZATION_ID — the organization to which the position belongs, subject to HR_SECURITY checks on HR_ALL_ORGANIZATION_UNITS.
• JOB_ID — the job associated with the position, useful for grouping or filtering by job.
• BUSINESS_GROUP_ID — the business group owning the position, constrained by the XBG profile or current business group.

Note that the view exposes no STATUS column; validity is enforced internally through the STATUS = 'VALID' (or NULL) predicate, so only usable positions are returned.

Common Use Cases and Queries

The most frequent scenario is resolving a position name from a known position_id, or listing positions for validation before inserting into an interface table. The view is also used in fast formulas, BIP data models, and custom concurrent programs that require a security-aware position LOV.

Resolving a name by identifier:

• SELECT position_id, name, organization_id, job_id, business_group_id FROM apps.per_positions_lov_v2 WHERE position_id = :p_position_id;

Filtering by business group and name pattern:

• SELECT position_id, name FROM apps.per_positions_lov_v2 WHERE business_group_id = :p_bg_id AND name LIKE :p_name||'%';

Because results depend on USERENV('LANG'), USERENV('SESSIONID'), and HR_SECURITY, queries should be executed from a connected EBS session rather than through a direct SQL*Plus connection maintaining only the APPS schema, to ensure correct language and security filtering.