Search Results per_absence_attendances_pkg2

Overview

The APPS.PER_ABSENCE_ATTENDANCES_PKG2 package is a PL/SQL API within the Oracle E-Business Suite Human Resources (HR) module, classified under the ETRM (E-Business Technical Reference Manual) as an "OTHER" API. Its business function is to manage absence and attendance element entries associated with employee assignments. In Oracle EBS, absence records — such as vacation, sickness, or other leave types — are represented as element entries linked to an assignment through the element link and element entry infrastructure of Oracle Payroll/HR. This package provides a programmatic interface for creating and maintaining those element entries, encapsulating the data manipulation logic that would otherwise need to be performed directly against the underlying payroll entity tables.

The package is defined with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user rather than the package owner. The header comment (peaba02t.pkh 115.1, dated December 2002) indicates the package has remained stable across the 11i and R12 code lines, including 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents two procedures within this package. Neither is a function; both are void procedures intended for DML operations on absence element entries.

• INSERT_ELEMENT — Creates a new absence/attendance element entry. It accepts a range of inputs covering the effective dating of the entry, the assignment and element link to which the entry belongs, the creator identity and creator type, the entry type, and a single input value identified by its input value identifier alongside its corresponding entry value. Its signature uses IN OUT NOCOPY parameters for the effective start date, effective end date, and element entry identifier, which implies the procedure can both receive and return these values — most notably the newly generated p_element_entry_id, allowing the caller to capture the surrogate key of the inserted row. The NOCOPY hint reflects a performance optimization for the OUT parameters.
• UPDATE_ELEMENT — Modifies an existing element entry. It takes an update mode indicator, a session date, the target element entry identifier, creator information, and an input value identifier with its entry value. The presence of an explicit update mode parameter (p_dt_update_mode) suggests date-tracked updates, consistent with Oracle date-tracked entity conventions.

Both procedures are declared in the package specification, and the specification terminates at line 24, confirming these are the only two public entry points.

Tables Accessed

The single documented table referenced by this package — via an APPS synonym — is PAY_ELEMENT_LINKS_F. This is the element links DateTracked (hence the _F suffix) table in Oracle Payroll, which stores the association between an element and the criteria (assignment, organization, or position) that makes the element valid for a population of employees. PER_ABSENCE_ATTENDANCES_PKG2 reads this table to validate that a valid element link exists for the assignment and element being processed before creating or updating the corresponding element entry. The procedure INSERT_ELEMENT accepts p_element_link_id directly as an input, confirming the package relies on a caller-supplied link identifier resolved against this table. The absence element entries themselves are ultimately stored in the payroll element entry tables, though the metadata excerpt only documents the link table reference.

Usage Notes

This package is typically invoked from within Oracle HR forms and concurrent processes handling absence and attendance data, rather than being exposed directly to end users. Custom code that needs to create or amend absence-related element entries programmatically should call INSERT_ELEMENT or UPDATE_ELEMENT rather than performing direct inserts on the underlying tables, because the package encapsulates the required DateTrack handling and validation against PAY_ELEMENT_LINKS_F.

The IN OUT NOCOPY parameters on INSERT_ELEMENT mean callers must supply host variables for the effective dates and the element entry identifier, and may read back the populated entry identifier after the call. Given the package is AUTHID CURRENT_USER, invoking code must itself possess the necessary privileges on the underlying payroll objects. The metadata records zero dependent packages, indicating this API is not referenced by other documented packages and is intended as a leaf-level call. Because the documentation is limited to the package specification, the precise internal exception handling and validation logic are not exposed and should be verified against the package body in the target instance before reliance in production customizations.