Search Results primary_meaning




Overview
Explore in AI Chat

Overview

APPS.PER_HIERARCHY_LOV is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data identifier PER.PER_HIERARCHY_LOV. In Oracle EBS 12.1.1 and 12.2.2 it functions as a Forms LOV (List of Values) support view rather than as a transactional or reporting object. Its purpose is to present a denormalized, user-friendly list of organization hierarchy definitions so that Oracle Forms-based screens — primarily within Oracle HRMS and Oracle Payroll — can offer a selection list of hierarchies without embedding complex joins directly into the form block.

The view status is VALID. Oracle classifies it as a supplementary view used to simplify forms coding, and the documented metadata carries an explicit warning that Oracle does not recommend querying or altering data through this view because its definition may change dramatically in subsequent minor or major releases. As a result, custom reports and integrations that reference PER_HIERARCHY_LOV accept a degree of upgrade risk; identifier-based joins against the underlying base tables are generally preferred for long-term stability.

Underlying Base Objects

The view is defined over several documented base objects. PER_ORGANIZATION_STRUCTURES provides the definition record for each organization hierarchy, including its name and business group context. PER_ORG_STRUCTURE_VERSIONS supplies version-level detail for each hierarchy, which is essential because hierarchies are versioned and only certain versions are valid at a given point in time. FND_LOOKUPS is joined to resolve lookup meaning values — the source of the PRIMARY_MEANING column. FND_SESSIONS and FND_GLOBAL provide session and runtime context, such as the effective business group and environment values derived from the FND_GLOBAL package. The view therefore combines structural hierarchy data with lookup translation and session filtering, presenting a single row per selectable hierarchy entry to the calling form.

Key Columns

The view exposes seven columns:

  • ROW_ID (ROWID): The physical row identifier for the underlying hierarchy row.
  • VERSION_NUMBER (NUMBER): The version sequence of the hierarchy definition; hierarchies are versioned, and this identifies which version the row represents.
  • VERSION_ID (NUMBER): The unique identifier of the organization structure version.
  • ORGANIZATION_STRUCTURE_ID (NUMBER, length 15): The primary identifier of the organization hierarchy itself, linking to PER_ORGANIZATION_STRUCTURES.
  • HIERARCHY_NAME (VARCHAR2, length 30): The user-facing name of the hierarchy, displayed in the LOV.
  • BUSINESS_GROUP_ID (NUMBER): The business group that owns the hierarchy; this is the principal security and partitioning attribute.
  • PRIMARY_MEANING (VARCHAR2, length 80): The descriptive meaning resolved from FND_LOOKUPS, used as the primary display text in the LOV.

The user's search term "primary_meaning" corresponds directly to this final column, which supplies the translated display string that forms present to end users when they select a hierarchy.

Common Use Cases and Queries

Typical usage centers on resolving hierarchy identifiers for a given business group, or displaying hierarchy names alongside their lookup meaning. A straightforward selection is:

SELECT organization_structure_id, hierarchy_name, primary_meaning, version_number
FROM apps.per_hierarchy_lov
WHERE business_group_id = :p_business_group_id
ORDER BY primary_meaning;

A second scenario joins the view back to PER_ORG_STRUCTURE_VERSIONS to obtain the currently valid version for reporting:

SELECT l.hierarchy_name, l.primary_meaning, v.version_id
FROM apps.per_hierarchy_lov l,
     apps.per_org_structure_versions v
WHERE l.organization_structure_id = v.organization_structure_id
  AND l.version_number = v.version_number;

Because the view depends on FND_SESSIONS and FND_GLOBAL, direct SQL execution from outside an EBS session may require a valid HR security context to return rows. Where the object is used purely for display in Forms, this session dependency is satisfied automatically. For custom integrations that must remain stable across patches, developers should treat PRIMARY_MEANING as a convenience derivation and map it to the appropriate FND_LOOKUPS lookup code when a durable data contract is required.