Search Results validate_hierarchy




Overview
Explore in AI Chat

Overview

PER_GENERIC_HIERARCHY_PKG is a server-side PL/SQL package in the Oracle E-Business Suite (EBS) Human Resources (PER) module, owned by the APPS schema and defined with AUTHID CURRENT_USER. Its declared purpose is to support the generic hierarchy form by performing two categories of business operations: validating hierarchies and copying hierarchies. A generic hierarchy in EBS provides a flexible, user-defined tree structure across HRMS entities, and this package encapsulates the validation and duplication logic that the form relies upon rather than embedding that logic directly in the form's client-side or trigger code. The package header carries the source identifier peghrval.pkh, indicating it originated as a validation-related header file. First created in January 2001, the package remained stable, with the only documented revision (115.3, December 2002) adding nocopy to the output parameters as a performance optimization. Because the package is classified as OTHER in the documented API metadata and is referenced by zero other packages, it is best understood as an internal supporting component invoked by the hierarchy maintenance form rather than a published integration API.

Key Procedures and Functions

The documented interface exposes three procedures.

  • validate_hierarchy — Accepts a hierarchy version identifier and validates that version of a generic hierarchy. Given the package's stated purpose and the source file name, this is the central routine: it confirms the hierarchy version is structurally and logically valid, presumably checking nodes, dates, and parent-child integrity before the hierarchy is saved or activated. This procedure corresponds directly to the object the user searched for.
  • copy_hierarchy — Copies an entire generic hierarchy. It accepts the source hierarchy identifier, a name for the new hierarchy, and an effective date, and returns the identifier of the newly created hierarchy through an output parameter declared nocopy.
  • copy_hierarchy_version — Copies a specific version of a hierarchy. It accepts the source hierarchy version identifier, a new version number, a date-from and date-to range, and an effective date, returning the identifier of the newly created version via a nocopy output parameter.

No parameter lists beyond those documented above should be assumed; the nocopy hint on output arguments reflects the 2002 performance revision noted in the header history.

Tables Accessed

The package operates against three core generic hierarchy tables, reached through APPS synonyms.

  • PER_GEN_HIERARCHY — The header table holding each defined hierarchy; read by validate_hierarchy and written by copy_hierarchy when the duplicate hierarchy record is created.
  • PER_GEN_HIERARCHY_VERSIONS — Stores the dated versions belonging to each hierarchy; consumed during validation and during both copy operations, and inserted into when new versions are produced.
  • PER_GEN_HIERARCHY_NODES — Holds the individual nodes comprising a hierarchy version; the primary subject of structural validation and the primary data duplicated when copying.

Usage Notes

This package is normally invoked indirectly, through the generic hierarchy form in the HRMS responsibility, which calls validate_hierarchy when a user saves or submits a hierarchy and calls the copy procedures when a user duplicates a hierarchy or version. It is not referenced by other packages, so it does not form part of a wider public API chain. In custom code, the procedures may be called directly from custom PL/SQL or concurrent program wrappers, but because this is an internal, non-published component, direct invocation should be treated cautiously: the interface is stable only for the version in which it ships, and output values are returned through the documented output parameters rather than functions. The AUTHID CURRENT_USER declaration means privileges are evaluated as the calling user, so callers should execute it from within the APPS context.