Search Results hr_delete




Overview

APPS.HR_DELETE is a server-side PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema. It is classified under the ETRM API taxonomy as OTHER, indicating that it is not a public, supported business API but rather an internal utility used to support Oracle HRMS data maintenance operations. The package is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its dependency footprint confirms a tightly scoped role: it operates against a narrow set of Oracle Human Resources, Oracle Payroll (Fast Formula), Oracle Advanced Benefits, and Oracle Application Object Library (FND) tables.

The functional purpose of HR_DELETE is to remove or purge rows that exist below a user's security and business group boundary — specifically data associated with organizations, positions, and related configuration that must be cleaned up in a controlled fashion. Its single documented procedure, DELETE_BELOW_BG, encapsulates this "delete below business group" logic, ensuring that deletions respect the multi-tenant structure of HRMS, where business groups act as the top-level partitioning unit.

Key Procedures and Functions

The ETRM metadata documents exactly one callable program unit within this package:

  • DELETE_BELOW_BG — The procedure name indicates its scope: it performs deletion of records that reside below the business group (BG) level in the HRMS security hierarchy. Rather than deleting a business group itself, it targets the dependent entities belonging to a given business group context, enforcing the referential and security boundaries defined by the FND security model. As documented, no parameter list is published for this internal routine; consumers of the package should treat it as an implementation detail invoked by Oracle-delivered cleanup logic rather than a custom-callable API.

Tables Accessed

The package reads and writes across several functional areas, as evidenced by the referenced APPS synonyms:

Usage Notes

HR_DELETE is referenced by no other documented packages (0 dependents), which reinforces its status as a leaf-level internal routine rather than a shared API surface. It is not intended for direct invocation from Oracle Forms, concurrent programs, or custom extensions. Instead, it is typically called by Oracle-delivered HRMS maintenance and cleanup logic — for example, during business group restructuring, organization deletion, or data purge activities performed through supported HRMS administration flows.

Because it is classified as OTHER and exposes no documented parameter interface, custom developers should avoid calling DELETE_BELOW_BG directly. Any requirement to remove HRMS organizational data should be routed through supported APIs and concurrent programs to preserve data integrity, security group boundaries, and Oracle support coverage.