Search Results delete_absence

Overview

The APPS.HR_LOC_ABSENCE package is a server-side PL/SQL API within Oracle E-Business Suite that governs the creation, retrieval, modification, and deletion of absence and attendance records and their associated payroll element entries. It forms the technical backbone of the Oracle HRMS absence and attendance framework, bridging the functional absence records stored in the PER_ABSENCE_ATTENDANCES tables with the payroll element entry structures stored in the PAY tables. Because absences frequently drive payroll processing — through element entries that determine payment, deduction, or accrual — this package provides the transactional logic that keeps absence records and their corresponding payroll element entries synchronized. Organizations implementing absence management for statutory sick pay, maternity, vacation, or other leave types rely on this API to translate an approved absence into the element entries consumed by the payroll run. The package is classified as OTHER within the ETRM documentation, indicating it is an internal API rather than a formally published public interface, though it is callable from custom code with appropriate validation.

Key Procedures and Functions

The documented procedures and functions of HR_LOC_ABSENCE serve distinct roles in the absence-to-element lifecycle:

• GET_ELEMENT_DETAILS — Returns the element type and up to fifteen input value identifiers and their corresponding entry values for a given absence and assignment, allowing callers to inspect the payroll elements that would apply to an absence.
• CREATE_ABSENCE — Creates an absence record against a specified absence attendance identifier over a defined effective date range with start and end dates.
• GET_ELEMENT_FOR_CATEGORY — Returns the element type identifier associated with the absence category of a given absence attendance record.
• GET_PACKAGE_FOR_CATEGORY — Returns the name of the PL/SQL package responsible for processing the absence category, enabling category-specific logic dispatch.
• GET_ABSENCE_ELEMENT — Retrieves the element details for an absence, providing callers with the element definition applicable to the record.
• DELETE_ABSENCE_ELEMENT — Removes the element entry associated with an absence, typically invoked when an absence is cancelled or reversed. This is the procedure most directly relevant to the user search term "delete_absence_element".
• UPDATE_ABSENCE_ELEMENT — Modifies an existing absence element entry when absence details change.
• INSERT_ABSENCE_ELEMENT — Inserts a new element entry for an absence record.
• UPDATE_ABSENCE — Updates the absence attendance record itself.
• DELETE_ABSENCE — Deletes the absence attendance record, with dependent cleanup of associated element entries.

Tables Accessed

The package reads and writes across the HR and Payroll schemas via APPS synonyms. PER_ABSENCE_ATTENDANCES and PER_ABSENCE_ATTENDANCE_TYPES hold the absence records and their category definitions. PER_ALL_ASSIGNMENTS_F supplies assignment context. PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, and PAY_ELEMENT_LINKS_F store the element entry header, input values, and element link eligibility. PAY_ELEMENT_TYPES_F and PAY_INPUT_VALUES_F supply element and input value definitions, while PAY_USER_TABLES, PAY_USER_ROWS_F, and FND_SESSIONS support user-defined tables, rows, and session context. DUAL is used for singleton queries.

Usage Notes

HR_LOC_ABSENCE is typically invoked indirectly through Oracle HRMS absence entry forms, the absence element generation processes, and payroll pre-processing logic. The DELETE_ABSENCE_ELEMENT procedure is commonly called when an absence is cancelled or corrected, ensuring orphaned element entries do not feed the payroll run. Because the package is classified as OTHER, direct invocation from custom PL/SQL is possible but should be preceded by validation against the supported public APIs. Three other packages reference HR_LOC_ABSENCE, confirming its role as a shared dependency in the absence processing stack. Customizations should preserve the documented parameter contracts and avoid bypassing the synchronization logic between absences and element entries.