Search Results per_abs_shd




Overview
Explore in AI Chat

Overview

APPS.PER_ABS_SHD is a shadow (seed data handler) package body in the Oracle E-Business Suite Applications schema. It forms the server-side counterpart to the PER_ABS absence API family and exists to provide the standardized entry points that Oracle's seed data framework expects when moving absence and attendance records between environments. In practice, the package serves as the programmatic interface used during data migration, cloning, and setup-data loading so that rows in PER_ABSENCE_ATTENDANCES can be validated and posted consistently rather than through direct SQL against the base table. It is classified in ETRM as API classification OTHER, indicating it is not a mainstream public business API such as HR_API but a supporting utility layer. The package body depends on a small set of well-defined objects — FND_MESSAGE, HR_API, HR_UTILITY, the PER_ABSENCE_ATTENDANCES table, the ALL_CONSTRAINTS data dictionary view, and the SYS.STANDARD package — which together provide error messaging, HR validation routines, constraint introspection, and generic PL/SQL support.

Key Procedures and Functions

The documented package exposes five procedures or functions:

  • RETURN_API_DML_STATUS — Reports whether the API has performed or is permitted to perform DML during the current call context. Callers use this to determine the transactional state after an invocation.
  • CONSTRAINT_ERROR — Centralized handler for constraint violations raised while processing absence and attendance rows, converting low-level Oracle errors into meaningful application messages.
  • API_UPDATING — Indicates whether the API is currently executing in an update mode, allowing downstream logic to distinguish insert, update, and delete processing paths.
  • LCK — Locking routine that manages row-level or logical locks against the affected absence records, guarding against concurrent modification.
  • CONVERT_ARGS — Argument conversion utility that normalizes inbound parameter values before they are applied to the underlying records.

Parameter signatures are not documented in the ETRM metadata and should be obtained from the deployed package specification. Referenced dependents include HR_API and HR_UTILITY, which supply the validation and date-handling logic that these procedures rely upon.

Tables Accessed

Two tables are documented as referenced through APPS synonyms:

  • PER_ABSENCE_ATTENDANCES — The core absence and attendance transaction table. The package reads and writes this table as the primary target of its DML and validation activity.
  • ALL_CONSTRAINTS — The data dictionary view used for constraint introspection, supporting the CONSTRAINT_ERROR routine's ability to identify and report the specific constraint that failed.

The ALL_CONSTRAINTS reference confirms that error handling is dynamic rather than hard-coded, and the PER_ABSENCE_ATTENDANCES reference confirms the package's scope is confined to absence records.

Usage Notes

PER_ABS_SHD is not referenced by any other database object per the ETRM dependency data, meaning it is invoked directly rather than called from within other packaged code. It is typically executed by Oracle seed data loader utilities, during environment cloning or setup data migration exercises, and by custom conversion scripts that must populate absence and attendance data while preserving the integrity rules enforced by the HR APIs. Because it is a shadow package, direct invocation outside of these controlled contexts is discouraged. Seven other packages are documented as referencing related absence functionality, so any customization touching this package should be validated against those dependencies before deployment in a 12.1.1 or 12.2.2 environment.