Search Results per_abs_ins




Overview
Explore in AI Chat

Overview

PER_ABS_INS is an internal PL/SQL package in the APPS schema that supports the Oracle E-Business Suite absence management infrastructure within Oracle Human Resources (Oracle HRMS). Its designation as an "OTHER" API classification indicates that it is not part of the public, supported extension interface, but rather a helper package used by the higher-level absence APIs and the shadow (tracking) table maintenance mechanism. The package is validated against both the 12.1.1 and 12.2.2 releases and remains in VALID status.

The package exists to perform low-level persistence work for absence records. Specifically, it interacts with the absence entity's base table and its shadow table. Shadow tables in Oracle HRMS are used to maintain a change-tracking or "pending" copy of rows where date-tracked or datetracked (DateTrack) updates are staged before the effective-date processing commits them to the base table. PER_ABS_INS therefore forms part of the plumbing that ensures absence rows are correctly inserted and keyed for downstream processing by the public absence API.

Key Procedures and Functions

  • INS — The insert procedure. It writes absence rows into the relevant absence tables, serving as the internal insertion routine invoked during absence creation. It encapsulates the row-level insert logic that the shadow-table framework expects.
  • SET_BASE_KEY_VALUE — A utility procedure responsible for establishing the base key value for the absence record. The "base key" concept refers to the primary identifier used to link a shadow (tracking) row back to its corresponding base-table row, so that inserts and subsequent datetracked updates resolve to the same entity.

Two additional internal units exist but are not part of the documented surface. No parameter lists are documented for the documented procedures, and none should be assumed; callers rely on the public APIs rather than invoking these directly.

Tables Accessed

Two absence tables are accessed through APPS synonyms:

  • PER_ABSENCE_ATTENDANCES — the base table holding the authoritative absence/attendance records. INS writes here, and SET_BASE_KEY_VALUE uses it to derive or align the record's primary key.
  • PER_ABSENCE_ATTENDANCES_S — the shadow (tracking) table paired with the base table. It stages insert and datetrack operations prior to effective-date resolution, allowing the framework to detect and reconcile changes.

PER_ABS_SHD also appears as a reference in the dependency metadata, reflecting the shadow-table support infrastructure that this package participates in.

Usage Notes

PER_ABS_INS is referenced by HR_PERSON_ABSENCE_API and HR_PERSON_ABSENCE_SWI. The former is the public, supported API for creating and maintaining person absences; the latter is the self-service (SWI) wrapper used by employee self-service absence flows. This dependency chain confirms the intended usage pattern: application code calls the public HR_PERSON_ABSENCE_API (or its self-service counterpart), and that API in turn delegates internal insert and key-maintenance work to PER_ABS_INS.

Because the package is classified as OTHER rather than a public API, custom code should never call PER_ABS_INS directly. Direct invocation bypasses the validation, datetrack handling, and business rules enforced by HR_PERSON_ABSENCE_API, and it risks corrupting the base/shadow relationship maintained through SET_BASE_KEY_VALUE. Form-based absence entry (for example, through the Absence and Attendance windows) and self-service transactions ultimately route through the documented APIs, so PER_ABS_INS is exercised transparently as part of those operations. Customers performing absence integrations or data conversions should use the supported API and treat PER_ABS_INS strictly as an internal implementation detail.