Search Results per_abs_rkd

Overview

PER_ABS_RKD is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM API taxonomy as OTHER. The suffix "RKD" follows the Oracle convention for seed-data or row-level "key definition" objects generated to support the maintenance of reference and seed data within a product. In this instance the package belongs to the Oracle Human Resources (PER) product family and, as its name suggests ("ABS"), is associated with absence and attendance management functionality in Oracle HRMS.

The package is documented with a VALID status in both Oracle EBS 12.1.1 and 12.2.2, confirming it is a supported, compiled database object at those release levels. It is not referenced by any other database object, which indicates that it is an implementation detail rather than a general-purpose API consumed by other application code. Its role is therefore limited and mechanical: providing the procedural body that supports the row-key handling logic associated with absence-related seed or setup data.

Key Procedures and Functions

The ETRM metadata documents a single procedure within this package:

• AFTER_DELETE — A post-delete event handler. Its name follows the standard row-key-definition naming pattern in which procedures are named for the DML event they service. AFTER_DELETE executes after a delete operation against the absence-related reference data managed by this package. It is an internal maintenance routine rather than a publicly called API, and no parameter list is exposed in the documented metadata.

No additional procedures or functions are documented, so the package body is functionally focused on this single DML event handler.

Tables Accessed

The ETRM excerpt does not enumerate specific base tables accessed by PER_ABS_RKD. Where the suffix pattern applies, the package body normally directs its operations against the reference or seed tables corresponding to the absence definitions whose row keys it maintains, performing post-delete cleanup or audit-related updates. The absence of documented table references in the metadata reflects the limited detail captured for this object rather than any absence of DML activity. Any table interactions should be confirmed against the deployed package source in the target environment.

Usage Notes

PER_ABS_RKD is not a user-facing API and is not intended for direct invocation by custom code. It is invoked indirectly when the absence-related data it governs is removed through supported Oracle HRMS maintenance functions, such as setup forms or seeded-data loaders that trigger the AFTER_DELETE handler.

The package is not referenced by any other database object, so it does not participate in the dependency chain of application APIs. Its dependency graph confirms that it relies on HR_UTILITY and the SYS.STANDARD package, using the former for standard HRMS utility operations and the latter for core PL/SQL runtime constructs. Because its procedures are triggered internally by DML events on absence data, customization or extension of this package is discouraged; changes could interfere with the row-level key handling required by Oracle HRMS absence management. Consultants auditing absence setup should treat PER_ABS_RKD as a supporting object and verify its status as VALID when diagnosing setup or data-integrity issues in the absence module.