Search Results pay_ran_del




Overview
Explore in AI Chat

Overview

APPS.PAY_RAN_DEL is a PL/SQL package body within the Oracle E-Business Suite (EBS) Payroll module, classified as an "OTHER" API in the ETRM documentation for releases 12.1.1 and 12.2.2. Its name follows Oracle Payroll naming conventions, where the PAY_RAN prefix designates objects belonging to the "Range" (grade/step/rate range) family and the DEL suffix denotes a deletion purpose. The package therefore serves as the deletion handler for payroll grade and rate range records defined in the Oracle Payroll ranges framework. In EBS, ranges represent the step, grade, or rate structures used to define pay progression rules and associated rates. Because range records must satisfy complex validation rules — including effective-date (date-tracked) integrity, overlap checking, and referential dependencies against range rate definitions — simple SQL DELETE statements are not sufficient. PAY_RAN_DEL encapsulates the validation and cleanup logic required to remove ranges safely while preserving the integrity of the surrounding payroll data model.

Key Procedures and Functions

The documented package contains two procedures or functions. The ETRM metadata records only one procedure by name in the extract provided, DEL, which is the principal deletion routine. Consistent with Oracle's standard "DML wrapper" pattern used throughout Oracle HRMS and Payroll:

  • DEL — The primary deletion procedure. It is responsible for validating and removing a specific range record from the underlying range table, ensuring that the operation respects date-tracked integrity and business rules before the physical delete is performed. It forms the entry point through which callers request removal of a range definition.
  • Second documented program unit — The metadata confirms a total of two documented procedures/functions in this package. The second unit is not individually named in the supplied extract; based on the dependency on HR_UTILITY and HR_MULTI_MESSAGE, it is likely a supporting routine handling validation messages or returning status/error information to callers. No parameter lists are documented in the ETRM metadata, and none should be assumed.

Tables Accessed

The documented table accessed by this package, via the APPS synonym, is PAY_RANGES_F. This is the base ("_F") table of the Oracle Payroll ranges entity, holding the core column-level attributes of each range, including unique identifiers, effective start and end dates, and descriptive information. Because the object is a deletion handler, PAY_RAN_DEL reads from PAY_RANGES_F to locate and validate the target record and, upon successful validation, removes the row (or marks it for deletion through the appropriate date-tracked mechanism). The presence of the companion objects PAY_RAN_SHD (the "_SHD" shadow/audit table used to preserve deleted or dated-back records) and PAY_RAN_RKD in the dependency list confirms that deletion activity propagates into the audit trail infrastructure. References to PAY_RANGES_F, PAY_RAN_BUS (the business rules package), PAY_RAN_RKD, and PAY_RAN_SHD in the dependency tree indicate a coordinated delete operation spanning the base table, business validation layer, and shadow table.

Usage Notes

PAY_RAN_DEL is not referenced by any other database object in the ETRM metadata, which indicates it is a top-level entry point invoked by external callers rather than an internal helper called from other PL/SQL packages. Typical invocation paths include the Payroll ranges maintenance forms, which call the corresponding server-side deletion logic when a user deletes a range; concurrent programs or batch routines that purge obsolete range definitions; and custom extensions or data-conversion scripts that must remove ranges programmatically. Because the package depends on HR_API, HR_UTILITY, and HR_MULTI_MESSAGE, callers can expect standard HRMS error-handling behavior, including message retrieval and exception propagation. Direct invocation from custom code should follow Oracle's documented APIs for range maintenance, validate the effective dates and referential dependencies of the target range beforehand, and commit the transaction explicitly after a successful call. Given its deletion semantics, this package should be used with caution and only after confirming that no active rate, progression, or payroll assignment references the range being removed.