Search Results convert_to_minutes

Overview

APPS.PER_ABS_BUS is the business-layer package body for absence and attendance processing within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It forms part of the Oracle Human Resources (PER) Absence Management architecture and sits between the schema-level table handlers (PER_ABS_SHD and related shadow packages) and the public PL/SQL APIs invoked from forms, OTL, and Payroll. The package encapsulates the business rules that validate absence records, compute attendance duration, derive running and year-to-date totals, and enforce legislative and security constraints before data is committed to the PER_ABSENCE_ATTENDANCES table. It is classified as an OTHER API and is referenced by eleven other packages in the EBS data model.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions. The following are the most significant.

• GET_RUNNING_TOTALS — Retrieves year-to-date and running totals for an absence type for both days and hours, based on the person, absence attendance type, and effective date supplied by the caller.
• CONVERT_TO_MINUTES — Converts an absence duration expressed in days or hours into minutes, providing a common unit of measure for downstream calculations, accrual comparisons, and payroll element feeds. This procedure is the object most commonly retrieved by the search term convert_to_minutes.
• CALCULATE_ABSENCE_DURATION — Derives the duration of an absence from the start and end dates, taking into account the absence attendance type definition and the assignment's work pattern.
• PER_VALID_FOR_ABSENCE and CHK_TIME_FORMAT — Perform eligibility and format checks before an absence record is accepted.
• CHK_PERSON_ID, CHK_ABSENCE_ATTENDANCE_TYPE_ID, CHK_ABS_ATTENDANCE_REASON_ID, CHK_ABSENCE_PERIOD, CHK_REPLACEMENT_PERSON_ID, CHK_AUTHORISING_PERSON_ID — Individual validation routines that confirm the presence and validity of mandatory keys and related entities on the absence record.
• INSERT_VALIDATE, UPDATE_VALIDATE, DELETE_VALIDATE — Row-level validation hooks called by the table handlers during DML against PER_ABSENCE_ATTENDANCES.
• SET_SECURITY_GROUP_ID and RETURN_LEGISLATION_CODE — Support multi-org security and legislation-specific processing; the latter uses the package globals g_legislation_code and g_absence_attendance_id.

Tables Accessed

The package reads and writes through APPS synonyms to the following documented tables.

• PER_ABSENCE_ATTENDANCES — The primary transaction table holding absence records.
• PER_ABSENCE_ATTENDANCE_TYPES and PER_ABS_ATTENDANCE_TYPES_TL — Absence type definitions and their translated names.
• PER_ABS_ATTENDANCE_REASONS — Reason codes attached to an absence.
• PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, and PER_PERIODS_OF_PLACEMENT — Person, assignment, and placement data used for eligibility and duration calculations.
• 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 — Payroll accrual and element definitions that drive absence accrual and absence element processing.
• FF_FORMULAS_F — Formula definitions used when absence types are driven by Fast Formula rules.
• FND_NEW_MESSAGES — Message repository for error text raised during validation.

Usage Notes

PER_ABS_BUS is not a public API; it is invoked indirectly. The primary callers are the Absence Management form (Absence Details and Enter Absence), the Oracle Time and Labor integration that creates absence entries from timecards, and the payroll absence element processing run during the payroll cycle. The Insert, Update, and Delete validation procedures are triggered from the corresponding PER_ABS_SHD table-handler operations, so custom code should update PER_ABSENCE_ATTENDANCES through the supported absences API rather than direct DML. CONVERT_TO_MINUTES and CALCULATE_ABSENCE_DURATION are frequently referenced by custom absence reports and by accrual band configuration, where hour-based and day-based balances must be reconciled to a single unit. Because the package body carries a header dated 2008 and a version of 120.17, customisations should be placed in a separate wrapper package and never layered on top of the seeded body, to preserve supportability through patching.