Search Results linked_to_element

Overview

APPS.HR_PERSON_ABSENCE_API is the public PL/SQL API for creating, maintaining, and deleting person absence records within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is the supported entry point for recording employee absences in the PER_ABSENCE_ATTENDANCES table and for driving the associated payroll element processing. The package encapsulates the business rules of Oracle Human Resources (Oracle HRMS) and Oracle Payroll, ensuring that absence data is validated, that payroll elements are attached or detached correctly, and that the transactional footprint is recorded in the HR API transaction framework.

The package exposes both pure HRMS operations (absence creation and change) and payroll integration operations. The presence of GET_ABSENCE_ELEMENT, GET_ELEMENT_DETAILS, INSERT_ABSENCE_ELEMENT, UPDATE_ABSENCE_ELEMENT, DELETE_ABSENCE_ELEMENT, and LINKED_TO_ELEMENT confirms that a core purpose of the package is to link an absence record to the payroll element that will pay or account for that absence period, and to manage the resulting element entry.

Key Procedures and Functions

• CREATE_PERSON_ABSENCE – Creates a new absence record for a person, applying validation and defaulting rules and returning the new absence identifier.
• UPDATE_PERSON_ABSENCE – Modifies an existing absence record, including dates, type, and reason, while preserving audit and date-tracked history.
• DELETE_PERSON_ABSENCE – Removes an absence record, including the related element processing where applicable.
• GET_PRIMARY_ASSIGNMENT – Retrieves the primary assignment for a person, which is required to determine the correct payroll relationship for element linkage.
• LINKED_TO_ELEMENT – Determines whether an absence is linked to a payroll element; this is the routine the user searched for and is central to deciding whether absence element processing should proceed.
• GET_ABSENCE_ELEMENT – Returns the payroll element associated with a given absence or absence type.
• GET_PROCESSING_TYPE – Returns the processing type that governs how the absence element is handled during payroll runs.
• GET_ELEMENT_DETAILS – Retrieves the element classification, input values, and other attributes needed to build an element entry.
• INSERT_ABSENCE_ELEMENT – Creates the payroll element entry corresponding to an absence.
• UPDATE_ABSENCE_ELEMENT – Modifies an existing absence element entry when the absence changes.
• DELETE_ABSENCE_ELEMENT – Removes the element entry when the absence is deleted or is no longer payable.
• OTL_HR_CHECK – Performs validation against Oracle Time and Labor (OTL) requirements before absence processing continues.
• GET_ABSENCE_DATA – Returns the full absence record, including descriptive and attribute flexfield values, for downstream consumers.

Tables Accessed

• PER_ABSENCE_ATTENDANCES – The primary store of absence records; inserted, updated, and queried by the API.
• PER_ABSENCE_ATTENDANCE_TYPES – Defines the absence types and associated element and processing rules.
• PER_ALL_ASSIGNMENTS_F – Resolves the person's assignment to identify the correct payroll relationship.
• PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_INPUT_VALUES_F – Provide the element definition, eligibility, and input value metadata required to construct a valid element entry.
• PAY_ELEMENT_ENTRIES_F – Holds the element entries created, updated, or deleted by the API.
• HR_API_TRANSACTIONS, HR_API_TRANSACTION_STEPS – Record the API call and its processing steps for audit and error handling.
• PLITBLM, XMLDOM, XMLPARSER – Utility tables used in message handling and XML payload processing.

Usage Notes

HR_PERSON_ABSENCE_API is invoked by the Oracle HRMS absence entry forms, by Oracle Payroll absence element processing, by Oracle Time and Labor integration logic, and by concurrent programs that import or reconcile absence data. It is referenced by ten other packages, which confirms its role as a shared service layer rather than a private implementation detail.

Custom code should call the public procedures — particularly CREATE_PERSON_ABSENCE, UPDATE_PERSON_ABSENCE, DELETE_PERSON_ABSENCE, and LINKED_TO_ELEMENT — rather than writing directly to PER_ABSENCE_ATTENDANCES or PAY_ELEMENT_ENTRIES_F, because the API enforces date-tracked integrity, element linkage, and transaction logging. Callers must supply a valid business group, assignment context, and absence type, and should expect errors to be reported through the HR API transaction tables. In 12.2.2 the package remains the supported interface, so direct table manipulation bypasses payroll element synchronization and can produce inconsistent absence and payroll results.