Search Results hr_pos_hierarchy_ele_api




Overview
Explore in AI Chat

Overview

HR_POS_HIERARCHY_ELE_API is a PL/SQL application programming interface (API) package owned by the APPS schema in Oracle E-Business Suite, classified as a public API within the Oracle HRMS (Human Resources Management System) family of products. Its functional purpose is to provide a controlled, business-rule-validated interface for managing position hierarchy elements — the records that associate individual positions with a position hierarchy (position structure) in Oracle HRMS. Position hierarchies are used throughout EBS for approval routing, reporting lines, security profile definitions, and organizational modeling. Rather than permitting direct DML against the underlying base table, this package exposes formal CREATE, UPDATE, and DELETE operations that invoke the HR_API foundation layer, thereby enforcing validation rules, maintaining WHO columns (created_by, creation_date, last_updated_by, and related attributes), and preserving data integrity. The object status is documented as VALID, confirming it is a compiled, deployable component in both Oracle EBS 12.1.1 and 12.2.2 environments.

Key Procedures and Functions

The documented package interface comprises six procedures, organized as two parallel sets: a public (external) API set and an internal implementation set that performs the underlying data manipulation.

  • CREATE_POS_HIERARCHY_ELE — The public procedure used to insert a new position hierarchy element record, associating a given position with a position structure. It applies HRMS validation logic before committing the row.
  • UPDATE_POS_HIERARCHY_ELE — The public procedure used to modify an existing position hierarchy element, for example to change the parent or child relationship details held in the element record.
  • DELETE_POS_HIERARCHY_ELE — The public procedure used to remove an existing position hierarchy element, subject to HRMS referential and business-rule checks.
  • CREATE_POS_HIER_ELEM_INTERNAL — The internal implementation procedure invoked by the public create operation to perform the actual row insertion and associated validation.
  • UPDATE_POS_HIER_ELEM_INTERNAL — The internal implementation procedure invoked by the public update operation to apply changes to an existing element row.
  • DELETE_POS_HIER_ELEM_INTERNAL — The internal implementation procedure invoked by the public delete operation to perform removal of the element row.

The internal procedures are not intended to be called directly by external code; the public wrapper procedures should always be used so that the standard HRMS API validation and WHO-column maintenance are applied consistently.

Tables Accessed

The package operates against the PER_POS_STRUCTURE_ELEMENTS table, accessed through its APPS synonym. This table is the base entity storing position hierarchy element records within the PER (People/HRMS) schema family, holding the relationships that define which positions belong to which position hierarchies. The API performs inserts, updates, and deletes against this table via the HR_API foundation layer referenced in the package dependency information. All write operations route through HR_API, ensuring consistent row-level auditing and validation.

Usage Notes

HR_POS_HIERARCHY_ELE_API is referenced by one other package, HR_POS_HIERARCHY_ELE_SWI, which is the standard Oracle HRMS secondary (SWI) wrapper that exposes the API to Forms-based user interfaces. In practice, this package is therefore invoked primarily from the Position Hierarchies window in the Oracle HRMS Forms application, where end users define and maintain position hierarchy elements. Custom integrations, conversions, and extensions that load or modify position hierarchy data should call the public CREATE, UPDATE, and DELETE procedures rather than issuing direct SQL against PER_POS_STRUCTURE_ELEMENTS, ensuring validation logic and audit columns remain consistent. Its dependency on HR_API and STANDARD indicates a standard layering: the API sits above the HR_API business layer and below customer-facing UI and integration code.