Search Results inv_orghierarchy_pvt




Overview
Explore in AI Chat

Overview

The APPS.INV_ORGHIERARCHY_PVT package body is a private (PVT) PL/SQL API within Oracle E-Business Suite Inventory that resolves how inventory organizations are arranged within organizational hierarchies and how those hierarchies are exposed through responsibility-based security. In a multi-organization EBS deployment, inventory organizations are rarely flat; they are grouped into structures such as a legal entity hierarchy, an inventory management hierarchy, or a reporting hierarchy defined in Oracle HRMS organization structures. The package evaluates a given organization against these structures, applies the security profiles and responsibility assignments that control visibility, and returns the resulting organization lists to calling code.

The package is classified with an API type of PVT, meaning it is intended for internal consumption by other Oracle application modules rather than as a published interface for customers. The ETRM registry lists 21 other packages that reference it, which confirms its role as a shared lower-level utility rather than a standalone entry point. Because it is private, it is unsupported for direct customer use, although it frequently appears in dependency listings and diagnostic queries, which is the context in which most users encounter the name inv_orghierarchy_pvt.

Key Procedures and Functions

The documented package exposes 13 procedures and functions. Their purposes are summarized below without reproducing parameter signatures.

  • VALIDATE_PROPERTY — Confirms that a named hierarchy property is recognized and usable before further processing continues.
  • GET_ORGANIZATION_LIST — Returns the set of inventory organizations visible to the current session based on hierarchy and security rules.
  • CONTAINED_IN_HIERARCHY — Determines whether a specific organization belongs to a given hierarchy structure.
  • ORG_HIERARCHY_ACCESS — Evaluates whether the current user or responsibility has access to an organization through the hierarchy.
  • ORG_HIERARCHY_LEVEL_ACCESS — Extends the access check to a particular level within the hierarchy rather than the hierarchy as a whole.
  • ORG_HIERARCHY_LIST — Produces the list of organizations associated with a hierarchy definition.
  • ORG_HIER_LEVEL_PROPERTY_ACCESS — Tests access to a hierarchy level in combination with an associated property.
  • ORG_HIER_LEVEL_RESP_ACCESS — Tests access to a hierarchy level for a specific responsibility.
  • ORG_HIER_ORIGIN_RESP_ACCESS — Tests access originating from a responsibility at the hierarchy origin point.
  • ORG_EXISTS_IN_HIERARCHY — Boolean-style existence check for an organization within a hierarchy.
  • INSERT_HIERARCHY_INDEX_LIST — Populates a PL/SQL index table with hierarchy data for downstream processing.
  • LOG_INITIALIZE — Initializes the package's diagnostic logging facility.
  • LOG — Writes diagnostic messages through the logging mechanism.

Tables Accessed

The package reads organization and hierarchy definitions from HR_ALL_ORGANIZATION_UNITS, HR_ORGANIZATION_INFORMATION, PER_ORGANIZATION_STRUCTURES, PER_ORG_STRUCTURE_ELEMENTS, and PER_ORG_STRUCTURE_VERSIONS. Security-related visibility is derived from PER_SECURITY_PROFILES and ORG_ACCESS. Inventory context comes from MTL_PARAMETERS, which identifies inventory organizations and their defaults. GL_SETS_OF_BOOKS supplies set of books information used for organizational context. FND_PROFILE and FND_FILE are used for profile option retrieval and file or log output, while OE_DEBUG_PUB supports debugging. DUAL and PLITBLM appear as utility references, the latter being the standard EBS PL/SQL index table type used by INSERT_HIERARCHY_INDEX_LIST.

Usage Notes

Because this is a private package, it is invoked indirectly. Oracle Inventory forms and concurrent programs that need to restrict organization selection to a hierarchy, such as organization-level inquiry, reporting, and transaction entry windows, call into this package through supported wrappers. Custom code should likewise consume the public inventory organization APIs rather than calling INV_ORGHIERARCHY_PVT directly, since private APIs may change between releases without notice. When troubleshooting organization visibility problems, DBAs and developers commonly query the dependencies of this package to trace why a user can or cannot see a given inventory organization. The package is valid in both EBS 12.1.1 and 12.2.2, and the reference to FND_FILE indicates that its logging procedures can emit output to the concurrent manager log when invoked from a concurrent program context.