Search Results per_abs_del
Overview
PER_ABS_DEL is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is classified as an "OTHER" API and is documented with a status of VALID. The package is associated with the Oracle Human Resources (HR) absence management subsystem, which governs absence and attendance records for employees, applicants, and other person types. Its name follows the conventional EBS suffix pattern for delete-phase business logic: the "_DEL" component identifies the package as a delete handler operating alongside related absence packages such as PER_ABS_BUS, PER_ABS_RKD, and PER_ABS_SHD. In the context of Oracle HRMS, such packages form part of the internal processing layer that supports the Absence and Attendance forms and related APIs. The package is not referenced by any other database object, indicating that it functions as a top-level entry point rather than a shared utility.
Key Procedures and Functions
The ETRM documentation lists two documented procedures or functions for this object, with the name DEL identifiable. In this documented set, DEL represents the absence deletion routine. Following the established EBS naming convention for absence subprograms, the DEL procedure is responsible for removing an absence or attendance record after the appropriate validation and business rule checks have been performed by the preceding phases. The package is dependent on companion packages PER_ABS_BUS, PER_ABS_RKD, and PER_ABS_SHD, which perform before-row processing, row-key logic, and after-row processing respectively. The presence of only two documented subprograms suggests a compact package focused narrowly on delete operations rather than a broad absence API. The documentation does not disclose parameter lists, and none are reproduced here.
Tables Accessed
The package references the table PER_ABSENCE_ATTENDANCES through the APPS synonym. This is the core transactional table in Oracle HRMS that stores absence and attendance entries, including the start and end dates, absence category, and the person or assignment to which each absence belongs. The delete logic in PER_ABS_DEL operates directly on rows held in this table, removing the target absence record as part of the overall transaction. Because absence records feed downstream payroll, accrual, and cost allocation calculations, deletion through this package occurs only after the surrounding business validation has established that removal is permissible.
Usage Notes
PER_ABS_DEL is an internal handler and is not referenced by any other database object. In practice, it is invoked indirectly from the Absence and Attendance forms in Oracle HRMS when a user deletes an absence record, and may also be reached from supported public APIs that delegate to the absence business logic. The package also invokes HR_API and HR_UTILITY, and relies on STANDARD. Custom code should not call the DEL procedure directly unless it is executing within the full absence processing sequence, since bypassing the preceding validation and business-rule phases risks leaving dependent data such as accrual balances or absence histories inconsistent. Direct modifications to PER_ABSENCE_ATTENDANCES are not recommended; the supported path is through the absence forms or the documented HRMS absence APIs.
-
PACKAGE BODY: APPS.PER_ABS_DEL
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PER_ABS_DEL, status:VALID,
-
PACKAGE: APPS.PER_ABS_DEL
12.1.1
owner:APPS, object_type:PACKAGE, object_name:PER_ABS_DEL, status:VALID,
-
PACKAGE: APPS.PER_ABS_DEL
12.2.2
owner:APPS, object_type:PACKAGE, object_name:PER_ABS_DEL, status:VALID,
-
PACKAGE BODY: APPS.PER_ABS_DEL
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PER_ABS_DEL, status:VALID,
-
PACKAGE: APPS.PER_ABS_SHD
12.2.2
owner:APPS, object_type:PACKAGE, object_name:PER_ABS_SHD, status:VALID,
-
PACKAGE: APPS.PER_ABS_SHD
12.1.1
owner:APPS, object_type:PACKAGE, object_name:PER_ABS_SHD, status:VALID,
-
PACKAGE: APPS.PER_ABS_RKD
12.2.2
owner:APPS, object_type:PACKAGE, object_name:PER_ABS_RKD, status:VALID,
-
PACKAGE BODY: APPS.HR_PERSON_ABSENCE_API
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:HR_PERSON_ABSENCE_API, status:VALID,
-
PACKAGE: APPS.PER_ABS_RKD
12.1.1
owner:APPS, object_type:PACKAGE, object_name:PER_ABS_RKD, status:VALID,
-
PACKAGE BODY: APPS.HR_PERSON_ABSENCE_API
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:HR_PERSON_ABSENCE_API, status:VALID,
-
PACKAGE: APPS.PER_ABS_BUS
12.1.1
owner:APPS, object_type:PACKAGE, object_name:PER_ABS_BUS, status:VALID,
-
PACKAGE: APPS.PER_ABS_BUS
12.2.2
owner:APPS, object_type:PACKAGE, object_name:PER_ABS_BUS, status:VALID,
-
PACKAGE: APPS.PER_ABS_DEL
12.1.1
-
PACKAGE: APPS.PER_ABS_DEL
12.2.2
-
PACKAGE BODY: APPS.PER_ABS_DEL
12.1.1
-
PACKAGE BODY: APPS.PER_ABS_DEL
12.2.2
-
SYNONYM: APPS.PER_ABSENCE_ATTENDANCES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PER_ABSENCE_ATTENDANCES, status:VALID,
-
SYNONYM: APPS.PER_ABSENCE_ATTENDANCES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PER_ABSENCE_ATTENDANCES, status:VALID,
-
APPS.PER_ABS_DEL dependencies on PER_ABS_DEL
12.2.2
-
APPS.PER_ABS_DEL dependencies on PER_ABS_DEL
12.1.1
-
APPS.HR_PERSON_ABSENCE_API dependencies on PER_ABS_DEL
12.1.1
-
APPS.HR_PERSON_ABSENCE_API dependencies on PER_ABS_DEL
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
APPS.PER_ABS_DEL dependencies on HR_UTILITY
12.1.1
-
APPS.PER_ABS_DEL dependencies on HR_UTILITY
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
PACKAGE: APPS.HR_API
12.1.1
owner:APPS, object_type:PACKAGE, object_name:HR_API, status:VALID,
-
PACKAGE: APPS.HR_API
12.2.2
owner:APPS, object_type:PACKAGE, object_name:HR_API, status:VALID,
-
PACKAGE: APPS.HR_UTILITY
12.1.1
owner:APPS, object_type:PACKAGE, object_name:HR_UTILITY, status:VALID,
-
PACKAGE: APPS.HR_UTILITY
12.2.2
owner:APPS, object_type:PACKAGE, object_name:HR_UTILITY, status:VALID,
-
PACKAGE: SYS.STANDARD
12.1.1
owner:SYS, object_type:PACKAGE, object_name:STANDARD, status:VALID,