Search Results per_valid_for_absence

Overview

APPS.PER_ABS_BUS is the business-rule layer of the Oracle EBS Absence Management module. It centralises the validation logic that governs whether an absence or attendance record may be created, changed, or removed against a person's assignment. The package header carries the identifier peabsrhi.pkh, confirming its origin as a table handler generated for the PER_ABSENCE_ATTENDANCES entity and subsequently extended with hand-coded business logic. Its scope covers existence checks on the person, absence type, reason, replacement person, and authorising person; verification that an absence falls inside a valid period of service; conversion and formatting of duration values; year-to-date and running-total accumulation; and the insert, update, and delete validation entry points invoked by the absence table handler.

Key Procedures and Functions

The package exposes eighteen documented program units. The validation routines form the core of the API:

• PER_VALID_FOR_ABSENCE — the function named in the originating search. It validates that the person exists and holds a valid period of service covering the entire duration of the absence. It is the principal gate for absence eligibility.
• CHK_PERSON_ID, CHK_ABSENCE_ATTENDANCE_TYPE_ID, CHK_ABS_ATTENDANCE_REASON_ID, CHK_REPLACEMENT_PERSON_ID, and CHK_AUTHORISING_PERSON_ID — mandatory and reference checks for the key identifiers on an absence record.
• CHK_ABSENCE_PERIOD — confirms that the supplied start and end dates form a coherent absence period.
• INSERT_VALIDATE, UPDATE_VALIDATE, and DELETE_VALIDATE — the row-level handlers that sequence all relevant checks before a DML operation proceeds.
• GET_RUNNING_TOTALS — returns running and year-to-date totals in both hours and days for a person and absence type at an effective date.
• CALCULATE_ABSENCE_DURATION, CONVERT_TO_MINUTES, and CHK_TIME_FORMAT — duration computation, normalisation to minutes, and validation of the time format supplied.
• SET_SECURITY_GROUP_ID and RETURN_LEGISLATION_CODE — session context and legislation determination used by the surrounding validation logic.

Tables Accessed

The package reads and writes through APPS synonyms. Core absence data resides in PER_ABSENCE_ATTENDANCES, PER_ABSENCE_ATTENDANCE_TYPES, PER_ABS_ATTENDANCE_TYPES_TL, and PER_ABS_ATTENDANCE_REASONS. Person and assignment context is drawn from PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_PERIODS_OF_PLACEMENT, the latter being the source used to confirm a valid period of service in PER_VALID_FOR_ABSENCE. Payroll integration tables — PAY_ACCRUAL_PLANS, PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_ENTRY_VALUES_F, and PAY_INPUT_VALUES_F — supply accrual plan and element definitions used when accrual balances and durations are calculated. FF_FORMULAS_F supports Fast Formula evaluation, while FND_NEW_MESSAGES supplies the seeded error messages raised on validation failure.

Usage Notes

Access status is documented as internal table handler use only; the package is not intended as a public API, and API updating is not required because it is called from other check procedures that already perform API-level updates. It is referenced by eleven other packages within the Oracle EBS schema. Typical invocation paths are the Absence Management self-service and professional forms in HRMS, absence-related concurrent programs, and payroll processes that consume absence results. Developers extending absence functionality should call the supported public APIs rather than PER_ABS_BUS directly, but should be aware of its validation rules — particularly PER_VALID_FOR_ABSENCE and CHK_ABSENCE_PERIOD — since they determine when an absence record is rejected.