Search Results otl_hr_check

Overview

APPS.HR_PERSON_ABSENCE_SWI is a self-service wrapper package within the Oracle E-Business Suite Human Resources (HR) module. Its principal role is to expose an API-friendly interface over the core absence management logic held in HR_PERSON_ABSENCE_API, allowing absence records to be created, updated, and deleted through a controlled, self-service oriented entry point. The package is declared AUTHID CURRENT_USER and its header (hrabsswi.pkh, version 120.6, dated 2011/11/15) confirms its position as a thin wrapper rather than a store of primary business rules. Within the 12.1.1 and 12.2.2 releases, this package underpins self-service flows where employees or administrators record absence and attendance events without direct manipulation of the base HR absence tables. The ETRM registry classifies the package under API classification OTHER, with nine documented procedures, and records that it is referenced by two other packages, indicating that it forms part of a larger dependency chain in absence-related processing. The wrapper abstracts the more demanding pre-requisite handling of the underlying API, so that calling modules need only supply appropriately derived IN parameters and inspect a return status.

Key Procedures and Functions

• CREATE_PERSON_ABSENCE — The self-service wrapper to hr_person_absence_api.create_person_absence. It creates a person absence record, returning a status value indicating success or failure. The header shows a substantial parameter set covering effective dating, person and business group identifiers, absence/attendance type and reason, comments, notification and projected start/end dates and times, actual start/end dates and times, and out parameters for absence days and hours.
• UPDATE_PERSON_ABSENCE — The corresponding wrapper for modifying an existing person absence record through the self-service interface.
• DELETE_PERSON_ABSENCE — The wrapper that handles deletion of a person absence record.
• PROCESS_API — A supporting routine that drives the API processing cycle, handling validation, execution, and transaction management associated with the wrapper calls.
• CHK_OVERLAP — Performs overlap checking between absence entries, ensuring conflicting date or time ranges are detected before an absence is committed.
• GETSTARTDATE and GETENDDATE — Utility functions that resolve or return the computed start and end dates used during absence processing.
• DELETE_ABSENCES_IN_TT — Operates on a PL/SQL table type (TT) to remove multiple absence records in a batch, supporting set-based processing scenarios.
• OTL_HR_CHECK — An integration check between Oracle Time and Labor (OTL) and HR absence data. This procedure is the object most closely associated with the user search term "otl_hr_check" and serves to validate the interaction between recorded absences and OTL time entry, ensuring consistency between the two modules.

Tables Accessed

The package operates against PER_ABSENCE_ATTENDANCES, which stores the actual absence and attendance entries, and PER_ABSENCE_ATTENDANCE_TYPES, which defines the available absence and attendance categories referenced by those entries. Transactional integrity and API logging are supported through HR_API_TRANSACTIONS and HR_API_TRANSACTION_STEPS, which record the API call and its processing stages. Attachment handling for absence comments or supporting documentation uses FND_ATTACHED_DOCUMENTS together with FND_DOCUMENTS and FND_DOCUMENTS_TL. The XMLDOM and XMLPARSER packages appear in the reference list, indicating XML document construction or parsing within the processing flow. DUAL is used for simple single-row queries, typically for defaulting or validation checks.

Usage Notes

This package is defined as internal development use only and should not be invoked directly by end users. It is typically called from Oracle Forms self-service pages, from concurrent programs that bulk-process absences, or from custom PL/SQL extensions that require absence creation, update, or deletion through a supported API surface. When invoked, callers should supply fully derived IN parameters, respect the p_validate flag to run in validation-only mode before committing, and inspect the returned status value to confirm success or failure. Because overlap checking and OTL/HR validation are embedded in the processing flow, custom integrations should route absence changes through this package rather than writing to PER_ABSENCE_ATTENDANCES directly. Note that the p_comments parameter was changed to a CLOB to address Bug#13362792, which affects how long absence comments are passed by calling code.