Search Results org_exists_in_hierarchy

Overview

HR_SA_ORG_INFO is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and classified under the "OTHER" API category. It belongs to the Saudi Arabia (SA) localization layer of Oracle HRMS, as indicated by the "SA" prefix convention in the PESA product family (the source header references pesaorgi.pkb). The package supplies utility services for resolving and validating organizational structures maintained in Oracle HRMS, specifically the named organization hierarchies stored in the PER_ORG_STRUCTURE_ELEMENTS and PER_ORG_STRUCTURE_VERSIONS tables.

Its business purpose is to answer structural questions about an organization within a named hierarchy: whether a given organization participates in a hierarchy, which hierarchy is currently active for a business group, and how to obtain employer naming information. These are common validation requirements for Saudi localization processes such as statutory reporting, where the employer entity and its position in the organizational tree must be confirmed before data is submitted.

Key Procedures and Functions

The package exposes seven documented programs. The following functions are the principal ones:

• NAMED_HIERARCHY — Service function returning the current named hierarchy for a given organization. It resolves the hierarchy by reading the organization information record whose context is SA_HR_BG_INFO, effectively mapping a business group to its configured hierarchy.
• LATEST_NAMED_HIERARCHY_VERS — Returns the latest version of the named hierarchy, ensuring downstream logic operates against the most current structure version rather than a superseded one.
• ORG_EXISTS_IN_HIERARCHY — The function associated with the user's search term. It validates whether a specified organization exists within a given hierarchy structure version. Internally the package implements this through hierarchical queries against PER_ORG_STRUCTURE_ELEMENTS using CONNECT BY PRIOR traversal, walking from a starting child organization upward to its parents. A flag parameter (conventionally 'Y') controls whether the starting organization itself is included in the result set.
• CHK_FOR_ORG_IN_HIERARCHY — A companion check routine confirming organization membership in the hierarchy, typically used where a Boolean-style outcome or exception handling is required rather than a hierarchical result set.
• GET_EMPLOYER_NAME — Retrieves the employer name associated with the organization, supporting statutory and localization reporting requirements.

Tables Accessed

The package reads from the following objects through APPS synonyms:

• PER_ORG_STRUCTURE_ELEMENTS — The core hierarchy table. Parent-child organization relationships are traversed here using CONNECT BY, filtered by org_structure_version_id.
• PER_ORG_STRUCTURE_VERSIONS — Provides version context for the hierarchy, supporting the LATEST_NAMED_HIERARCHY_VERS logic.
• HR_ALL_ORGANIZATION_UNITS — Supplies organization and business group identifiers used to join organization information.
• HR_ORGANIZATION_INFORMATION — Stores the descriptive flexfield context SA_HR_BG_INFO from which the named hierarchy identifier (ORG_INFORMATION1) is derived.
• FND_SESSIONS — Used for session context, typically to resolve the current business group or runtime environment.
• DUAL — Used in the UNION branch of the hierarchy cursors to optionally seed the result with the input organization at level zero.

Usage Notes

HR_SA_ORG_INFO is an internal localization utility rather than a public, registered API. The ETRM metadata records zero referencing packages, indicating it is not designed as a shared dependency for other delivered code. It is most likely invoked from Saudi-localized Oracle HRMS forms, concurrent programs, or localization-specific report generation logic, and it may also be called from customer-written extensions that need to verify hierarchy membership.

Developers should treat ORG_EXISTS_IN_HIERARCHY and CHK_FOR_ORG_IN_HIERARCHY as read-only validation helpers. Because the source header dates to 2004 and the package is tightly coupled to the SA localization context (SA_HR_BG_INFO), it should not be repurposed for generic multi-legislation hierarchy checks without review.