Search Results chk_org_in_hierarchy

Overview

APPS.PER_OSE_DEL is a PL/SQL package body belonging to the Oracle E-Business Suite Human Resources (HR) product family, specifically within the Oracle Organization Structure and Enterprise (OSE) subsystem. The package is classified under the "OTHER" API category and is not part of the formally published, supported public API surface. Its name and contents indicate that it is a utility and validation package used internally by the organization hierarchy engine, providing logic to verify and delete organization structure elements maintained in the PER_ORG_STRUCTURE_ELEMENTS table.

The package carries the source control header peoserhi.pkb 120.2.12000000.1, dated 2007, confirming that it is a long-standing internal component carried forward intact through both the 12.1.1 and 12.2.2 releases. The "DEL" suffix conventionally denotes delete-oriented logic, while the visible private procedure chk_org_in_hierarchy supplies the membership verification that must precede any destructive operation. This pairing reflects a defensive design in which an organization is only removed from a structure version after its presence in the hierarchy has been positively confirmed.

Key Procedures and Functions

• DEL — The primary deletion routine of the package. It performs removal of organization structure element records associated with a given organization structure version, in support of maintaining the integrity of the organization hierarchy. The procedure relies on the validation supplied by chk_org_in_hierarchy before proceeding.
• CHK_ORG_IN_HIERARCHY — A membership validation procedure that determines whether a specified organization participates in a given organization structure version. It accepts the organization structure version identifier and organization identifier as inputs and returns an existence indicator, conventionally set to 'Y' or 'N'. The logic first tests whether the organization appears as a child node. If that test fails, a secondary test determines whether the organization is a parent/top node that is not itself a child elsewhere in the hierarchy. This two-pass design ensures that the top node of a structure — which by definition has no parent — is still correctly recognized as belonging to the hierarchy.

The documentation lists three procedures or functions in total, with DEL and CHK_ORG_IN_HIERARCHY named in the ETRM metadata. No parameter signatures are reproduced here beyond those documented, and private helper routines are not exposed as supported entry points.

Tables Accessed

• PER_ORG_STRUCTURE_ELEMENTS — The sole documented table referenced, accessed through the APPS synonym. This table stores the parent-child relationships that define an organization hierarchy within a specific organization structure version. The package reads it to validate membership and hierarchy position, and the DEL routine operates against it to remove hierarchy elements. Columns of interest documented in the source include org_structure_version_id, organization_id_child, and organization_id_parent, which together model each edge of the hierarchy graph.

Usage Notes

As an internal component classified under "OTHER" and carrying a 12.1-era header, PER_OSE_DEL is not intended as a public extension point. Custom code should not call this package directly; supported organization hierarchy operations should be performed through the published HR organization APIs instead. The ETRM metadata records that the package is referenced by two other packages, indicating that its procedures are invoked from within the OSE subsystem — most likely from organization hierarchy maintenance, validation, or form-driven deletion flows in Oracle HRMS.

Typical invocation occurs implicitly during organization hierarchy administration, when an administrator modifies or removes an organization from a structure version. The chk_org_in_hierarchy logic guards those operations by confirming membership before changes are committed. Because the package manipulates hierarchy data directly and exposes no public interface, direct invocation in a production environment risks data inconsistency and is not recommended. Any diagnostic use should be confined to non-production instances under the guidance of Oracle Support.