Search Results update_element_entry




Overview

The APPS.HR_AU_ABSENCE_HOOK package body is an Australian localization legislative hook that supports the integration between Oracle Payroll element entries and absence records captured through Oracle Advanced Benefits and the People Management absence framework. Its principal business purpose is to keep the descriptive flexfield (DFF) values attached to an absence record synchronized with the corresponding element entry in Oracle Payroll, so that legislative reporting and payroll processing for Australian absence entitlements reflect accurate absence detail.

The package is implemented as a PL/SQL body owned by the APPS schema and is classified under ETRM as an OTHER API object rather than a public or private API. It is specifically designed to interact with the update_element_entry API: the header comment within the package states that updating the absence flexfield values is performed by calling update_element_entry, and that this API itself carries a legislative hook which propagates the element entry values from the Absence flexfield, so the hook does not need to repeat those updates locally. The package deliberately restricts its activity to recurring elements only, because for non-recurring elements the update_element_entry API is already invoked within the core absence package. The package header references version peaulhab.pkb 120.2, dated 2006/03/23, confirming its long-standing presence in the Australian localization layer since the early 11i releases and its continued inclusion through 12.1.1 and 12.2.2.

Key Procedures and Functions

  • UPDATE_ABSENCE_DEV_DESC_FLEX — The single documented procedure in the package. It accepts an absence attendance identifier and is responsible for synchronizing the descriptive flexfield information associated with that absence to the related payroll element entry. Internally it opens a cursor to locate the matching element entry and element type records, capturing the element entry identifier, effective start and end dates, the element type's processing type, and the maximum object version number. The procedure then delegates the actual flexfield update to update_element_entry, relying on that API's legislative hook to carry the absence flexfield values across. It performs this work only for recurring elements, as non-recurring elements are handled by the core absence package.

Tables Accessed

The package reads from four documented tables, all referenced through APPS synonyms:

  • PER_ABSENCE_ATTENDANCES — The driving absence record, supplying the absence_attendance_id and person_id used to correlate the absence with its payroll element entry.
  • PAY_ELEMENT_ENTRIES_F — The payroll element entry table, from which the procedure retrieves the matching element_entry_id, effective dates, and object version number. The join is made on creator_id equal to the absence attendance identifier and creator_type of 'A', confirming that the element entry originates from the absence.
  • PAY_ELEMENT_TYPES_F — Provides the processing_type of the element type, used to determine whether the element is recurring and therefore within the scope of this hook.
  • PER_ALL_ASSIGNMENTS_F — Confirms the assignment to which the element entry belongs and validates that the element entry's effective dates fall within the assignment's effective dates, ensuring the entry is valid for the person and period concerned.

Usage Notes

HR_AU_ABSENCE_HOOK is not intended to be called directly by end users or through standard Oracle Forms. It is invoked as part of the Australian absence processing flow, where the legislative hook mechanism of the update_element_entry API triggers the synchronization of absence flexfield values. The package is referenced by one other package within the ETRM repository, indicating its role as a dependent utility rather than a top-level entry point. Because it operates on recurring elements only and defers the actual flexfield update to update_element_entry, customizations should avoid bypassing this hook or duplicating its logic; any custom code that creates or modifies Australian absence element entries for recurring elements should ensure the standard absence processing path is used so that the hook executes. In 12.1.1 and 12.2.2 environments, the package remains unchanged in functional scope, and its behavior is governed entirely by the documented cursor logic and the delegated API call.