Search Results sub_organization_name




Overview
Explore in AI Chat

Overview

APPS.HRIBV_ORG_HRCHY is a Business Intelligence System (BIS) view in Oracle E-Business Suite, owned by the APPS schema and registered in FND Design Data under the identifier HRI.HRIBV_ORG_HRCHY. Its purpose is to support "Organization Include Subordinate" queries across all Organization Hierarchy Versions. In practical terms, the view flattens the parent–subordinate relationship within an organization hierarchy so that each row expresses a pairing between an organization and one of its subordinate organizations, qualified by the hierarchy and version in which that relationship is valid.

Because hierarchy definitions change over time, Oracle EBS stores versions of organization hierarchies rather than a single static tree. The HIERARCHY_VERSION column is central to this design: it identifies which version of a named hierarchy is in effect. Users searching on "hierarchy_version" encounter this view specifically because it exposes both the version number and the effective date range (HIERARCHY_VERSION_DATE_FROM and HIERARCHY_VERSION_DATE_TO) for each versioned relationship. The view is documented as Oracle Internal Use Only, meaning Oracle does not support direct customer access except through standard Oracle Applications programs.

Underlying Base Objects

The view is defined over the following documented dependencies:

  • HRI_ORG_HRCHY_SUMMARY (SYNONYM) — the summarized organization hierarchy data that forms the core of the view.
  • HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — the translated organization unit definitions supplying organization names.
  • PER_ORGANIZATION_STRUCTURES (SYNONYM) — the definitions of organization hierarchies.
  • PER_ORG_STRUCTURE_VERSIONS (SYNONYM) — the version records that carry effective dates for each hierarchy.
  • HR_BIS (PACKAGE) and HR_BIS dependent code — Business Intelligence System helper logic.
  • HR_GENERAL (PACKAGE) and its dependent code — general HR utility functions used during view resolution.

The view therefore joins hierarchy metadata (name, hierarchy ID) with version metadata (version number, date bounds) and organization detail (organization name, level, and the corresponding subordinate organization identifiers).

Key Columns

Common Use Cases and Queries

The view is typically used to resolve all subordinates of a given organization within a specific hierarchy version, or to enumerate organizations at a particular level. A representative query filters by hierarchy name and version:

  • SELECT hierarchy_name, hierarchy_version, organization_name, sub_organization_name
  • FROM apps.hribv_org_hrchy
  • WHERE hierarchy_name = :p_hierarchy
  • AND hierarchy_version = :p_version
  • AND organization_name = :p_org;

Because version date bounds are exposed (including the null-safe HRCHY_VERSION_DATE_TO_NN), the view also supports as-of-date reporting, allowing a hierarchy to be evaluated as it existed on a chosen date. This makes it suitable for historical organizational reporting, security rollups, and integration extracts that must reflect the correct hierarchy version.