Search Results insert_abs_for_bee

Overview

PER_ABSENCE_ATTENDANCES_PKG3 is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle HRMS / Payroll family of objects and operates in the boundary zone where absence and attendance records intersect with payroll batch processing. Its documented API classification is OTHER, indicating that it is an internal support package rather than a public, fully documented integration API.

The package exists to create absence records that must remain synchronized with payroll processing. In a typical EBS deployment, absence entries captured through Self-Service or the Absence Management forms must eventually be reflected in the payroll run through element entries and batch lines. PER_ABSENCE_ATTENDANCES_PKG3 automates the programmatic insertion of absence rows when absence data arrives from a payroll mix or a Business Event Entity (BEE) driven process. This makes it a bridge between the PER_ABSENCE_ATTENDANCES base table and the PAY_* element entry tables that drive payroll calculation.

Key Procedures and Functions

The ETRM metadata documents three callable members of this package:

• INSERT_ABS_FOR_PAYMIX — Inserts absence and attendance records on behalf of a payroll mix. This procedure is used when absence data must be generated to match the payroll mix assigned to an employee or assignment, ensuring that the payroll process sees a consistent set of absence entries.
• INSERT_ABS_FOR_BEE — Inserts absence records driven by a Business Event Entity. This supports event-based integration where an external or upstream business event triggers the creation of an absence record without direct user entry in the absence forms.
• Additional documented procedure/function — The metadata notes three documented procedures or functions in total; the two named above are the primary entry points, with the third supporting the same insertion-for-payroll logic.

Because the metadata does not publish parameter lists, no signature details are asserted here. Consumers should not assume a stable public contract; the procedures are internal helpers invoked by the package body itself and by related payroll objects.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• PER_ABSENCE_ATTENDANCES — the core absence/attendance record store; the package inserts rows here.
• PER_ABSENCE_ATTENDANCE_TYPES — supplies the absence type definition that governs the inserted record.
• PAY_ELEMENT_TYPES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_ENTRIES_F, PAY_INPUT_VALUES_F — the payroll element definition, link, entry, and input value tables that connect the absence to pay.
• PAY_BATCH_LINES — the payroll batch line table, referenced directly in the dependency list.
• HR_ENTRY and PLITBLM — supporting HR and payroll internal structures referenced during processing.

The combination of PER_* and PAY_* tables confirms the package’s role in translating an absence into the payroll element entries that a payroll run requires.

Usage Notes

PER_ABSENCE_ATTENDANCES_PKG3 is an internal package and is not intended as a supported public API. It is referenced by one other package and by PAYPLNK, indicating it is called from payroll link processing and from within the absence package itself rather than directly by end users. Typical invocation paths include payroll batch processing, absence form save logic, and Business Event Entity based integrations. Custom code that calls INSERT_ABS_FOR_PAYMIX or INSERT_ABS_FOR_BEE should be treated as a customization risk: the package may change between 12.1.1 and 12.2.2, and Oracle does not document its parameter interface. Where possible, customers should use the supported absence and payroll APIs rather than invoking this package directly.