Results for “per_positions_v”

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

Overview

PER_POSITIONS_V is a database view owned by the APPS schema in Oracle E-Business Suite, registered under the PER (Human Resources) product family. In both release 12.1.1 and 12.2.2, its documented purpose is to support the user interface of the Position Management and related HR forms rather than to serve as a standalone reporting entity. The view is a denormalized, presentation-oriented projection that joins the base positions tables to their corresponding translation, organization, job, location, and lookup sources, resolving coded values into user-readable descriptions.

Because the view surfaces descriptive text (job names, organization names, lookup meanings) alongside the underlying foreign keys and the standard WHO/attribute columns, it is frequently leveraged as a convenient starting point for ad hoc reporting, data extracts, and integration queries that need a single row per position enriched with human-readable labels. It should be treated as a UI-support object: the column set and join logic are dictated by form requirements and may evolve between patch levels.

Underlying Base Objects

The documented base objects for the view are:

• PER_POSITIONS (view) — the primary driving source of position rows.
• PER_ALL_POSITIONS (synonym) — referenced in the view text for position identity and successor/relief resolution.
• HR_ALL_POSITIONS_F_TL (synonym) — the translated position name source for successor and relief positions.
• HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL (synonyms) — supply organization identity and the translated organization name.
• PER_JOBS_TL (synonym) — supplies the translated job name, joined on the session language via USERENV('LANG').
• HR_LOCATIONS (view) — supplies the location code.
• HR_LOOKUPS (view) — resolves Frequency, Replacement Required Flag, Probation Period Units, and Status into their meanings.
• HR_API, HR_GENERAL, and HR_SECURITY (packages) — support the view's underlying security and utility logic.

Outer joins (denoted by the (+) operator) are applied to the location and lookup sources so that positions lacking a location or a particular coded attribute are still returned. The lookup joins are constrained by lookup type, mapping the stored code to its meaning.

Key Columns

• POSITION_ID — primary identifier of the position.
• BUSINESS_GROUP_ID — the business group that owns the position row.
• NAME — the position name; the column named NAME also carries translated job, successor, and relief names in the view text.
• JOB_ID — foreign key to the job; paired with the translated job name.
• ORGANIZATION_ID — the organization to which the position belongs, with its translated name.
• LOCATION_ID / LOCATION_CODE — assigned work location and its code.
• SUCCESSOR_POSITION_ID and RELIEF_POSITION_ID — positions designated for succession and relief, each with a resolved name.
• DATE_EFFECTIVE / DATE_END — the validity window of the position definition.
• FREQUENCY, PROBATION_PERIOD, PROBATION_PERIOD_UNITS, REPLACEMENT_REQUIRED_FLAG, STATUS — coded attributes exposed with their lookup meanings.
• TIME_NORMAL_START, TIME_NORMAL_FINISH, WORKING_HOURS — standard working-time attributes.
• ATTRIBUTE1–ATTRIBUTE20, ATTRIBUTE_CATEGORY — descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns; REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE record the concurrent program that last touched the row.
• ROWID — exposed for UI row identification.

Common Use Cases and Queries

Typical scenarios include listing positions for a business group with their job, organization, and location descriptions; auditing successor and relief assignments; and extracting positions for integration or interface loads. A representative query follows.

SELECT pos.position_id,
       pos.name            AS position_name,
       pos.job_id,
       pos.organization_id,
       pos.location_code,
       pos.status,
       pos.date_effective,
       pos.date_end
  FROM apps.per_positions_v pos
 WHERE pos.business_group_id = :p_business_group_id
   AND (pos.date_end IS NULL OR pos.date_end >= TRUNC(SYSDATE))
 ORDER BY pos.name;

To report lookup-resolved attributes, select the meaning columns directly, since the view already joins HR_LOOKUPS by type. When building reusable reports, prefer joining to PER_ALL_POSITIONS or HR_ALL_POSITIONS_F directly so that column semantics remain stable across releases, using PER_POSITIONS_V primarily where UI-consistent descriptions and the declared join behavior are required. Because access is mediated by HR_SECURITY logic, results may be filtered by the user's security profile.