Results for “hr_person_delete”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.HR_PERSON_DELETE is a PL/SQL package within the Oracle Human Resources (HR) module of Oracle E-Business Suite. Its documented purpose is to declare the procedures required to delete person records from Oracle HRMS. The package header, sourced from peperdel.pkh, explicitly states that it does not encompass the additional validation supplied by calling programs — such as screen QuickPicks and HRLink validation — nor the validation enforced through database constraints and triggers held against individual tables. This scoping statement means the package performs the deletion logic itself while assuming that broader integrity checks are handled elsewhere in the call stack or at the database level.

The package carries a long history. It was originally created on 10-AUG-93 as version 70.0, and its delete procedures were moved out of the hr_person package (originally coded by PBARRY) to reduce the size of that original package. Version 70.3, dated 14-Jun-95, introduced the moderate_predel_validation procedure, indicating an evolution toward tiered validation levels prior to deletion. In ETRM 12.2.2 the package is classified as an "OTHER" API, owned by APPS, and exposes eight documented procedures and functions.

Key Procedures and Functions

The documented procedures reflect a layered design centred on pre-deletion validation and the deletion itself:

  • PRODUCT_INSTALLED — reported as PRODUCT_INST in the header comment, it checks whether a product has been installed and returns status together with the related Oracle application ID. This underpins decisions about which downstream data, such as payroll or benefits records, must be handled during person deletion.
  • WEAK_PREDEL_VALIDATION — the least restrictive pre-deletion validation tier.
  • MODERATE_PREDEL_VALIDATION — a mid-level validation tier introduced in version 70.3.
  • STRONG_PREDEL_VALIDATION — the most restrictive pre-deletion validation tier, applied when the greatest degree of referential scrutiny is required.
  • CHECK_CONTACT — validates contact-related information associated with the person before processing the deletion.
  • DELETE_A_PERSON — the core deletion routine implementing removal of the person record.
  • PEOPLE_DEFAULT_DELETES — handles default deletion processing logic for people, likely coordinating cascading or dependent record removal.
  • APPLICANT_DEFAULT_DELETES — parallel deletion handling for applicants, distinguishing the applicant data model from that of regular employees.

Tables Accessed

The package references a broad set of tables through APPS synonyms, spanning HR, payroll, and benefits:

The presence of FND_USER is notable because person deletion may interact with application user provisioning, though the metadata does not specify the exact linkage.

Usage Notes

HR_PERSON_DELETE is invoked when a person or applicant record must be removed from Oracle HRMS. It is typically reached through the standard HRMS forms and self-service flows that perform deletion, through concurrent programs handling bulk or terminated-employee cleanup, and through custom PL/SQL that calls the package directly. The package is referenced by two other packages according to ETRM, indicating it is itself a dependency of higher-level APIs.

Because the header explicitly excludes validation provided by calling screens, HRLink checks, and table constraints or triggers, custom callers must ensure that appropriate business validation is applied before invocation. The tiered WEAK, MODERATE, and STRONG validation procedures allow callers to select the level of pre-deletion scrutiny appropriate to the context. The extensive footprint across payroll, benefits, and HR tables means deletions carry significant data-integrity implications, and the transactional bookkeeping through HR_API_TRANSACTIONS suggests deletions are recorded as auditable API operations rather than as raw DML.