Search Results per_abs_bus




Overview
Explore in AI Chat

Overview

PER_ABS_SHD is a shadow (SHD) package in the APPS schema that supports the Absence Management functionality within Oracle E-Business Suite Human Resources. Its primary role is to provide the low-level Data Manipulation Language (DML) plumbing used by the PER_ABS family of packages that implement the Absence and Attendance business logic. Rather than exposing user-facing business rules, PER_ABS_SHD centralizes the homogeneous insert, update, and delete templates that other packages in the absence suite call into, ensuring consistent handling of the PER_ABSENCE_ATTENDANCES entity across all entry points.

The "SHD" naming convention in EBS typically denotes a shadow package whose logic mirrors the structure of the underlying table, providing reusable DML constructs and locking utilities. PER_ABS_SHD, classified as an OTHER API in the ETRM 12.2.2 metadata, is therefore an internal service package rather than a published integration API. Its dependency graph confirms this role: PER_ABS_SHD is referenced by APPS.PER_ABS_BUS, PER_ABS_INS, PER_ABS_UPD, PER_ABS_DEL, PER_ABV_SHD, PER_ABSENCE_ATTENDANCES_OVN, and HR_PERSON_ABSENCE_API. The user search term "per_abs_bus" is directly relevant here, since PER_ABS_BUS is one of the principal consumers of PER_ABS_SHD and the package that carries the business-level validation and processing rules.

Key Procedures and Functions

The ETRM metadata documents five procedures or functions within PER_ABS_SHD:

  • RETURN_API_DML_STATUS — Returns the DML status flag indicating whether the most recent insert, update, or delete operation performed through this package completed successfully. Consumers such as PER_ABS_BUS use this to determine whether to continue processing or branch into error handling.
  • CONSTRAINT_ERROR — Centralizes handling of Oracle integrity constraint violations raised during DML against the absence attendance table, translating them into a controlled error path rather than allowing raw ORA- errors to propagate.
  • API_UPDATING — A status/guard routine that indicates whether the API is currently in an update cycle. It prevents re-entrant or conflicting DML behaviour when nested calls occur within the same transaction.
  • LCK — Performs pessimistic row locking on the target absence attendance record, ensuring that concurrent absence transactions observe consistent data before modification. This is essential in HR absence processing where overlapping absence records can be created from multiple forms.
  • CONVERT_ARGS — Converts or normalizes argument values passed into the shadow DML routines, ensuring that the calling packages supply data in the format the underlying column definitions expect.

Tables Accessed

PER_ABS_SHD references two tables through APPS synonyms:

  • PER_ABSENCE_ATTENDANCES — The core absence record table. All insert, update, delete, and lock operations performed by this shadow package ultimately act on this table, maintaining the absence rows that record employee absence and attendance entries.
  • ALL_CONSTRAINTS — The data dictionary view used to look up constraint definitions. This supports the CONSTRAINT_ERROR procedure in identifying and handling integrity constraint violations programmatically.

In addition, the ETRM dependency listing shows a reference to the SYS STANDARD package, which provides standard PL/SQL language constructs and built-in exception identifiers.

Usage Notes

PER_ABS_SHD is not intended for direct invocation by end users, forms, or concurrent programs. It is an internal implementation package invoked through higher-level absence APIs. The typical invocation chain begins with the Absence Management form or with HR_PERSON_ABSENCE_API, flows into PER_ABS_BUS for business validation, and then into PER_ABS_INS, PER_ABS_UPD, or PER_ABS_DEL for the specific DML operation. Each of those packages calls PER_ABS_SHD for the underlying shadow DML and locking primitives.

Custom code that needs to create or modify absence records should use the documented public API HR_PERSON_ABSENCE_API rather than calling PER_ABS_SHD directly, since the shadow layer performs no business validation. Developers tracing the execution path of an absence transaction should expect to see PER_ABS_SHD appearing repeatedly in the call stack, consistent with its role as the shared DML foundation for the entire PER_ABS package family.