Search Results per_ctc_rkd

Overview

PER_CTC_RKD is an Oracle E-Business Suite PL/SQL package owned by the APPS schema. Its naming convention follows the Oracle "backend processing" pattern: the suffix "RKD" denotes a row-level database trigger body package associated with a key/row deletion event. In Oracle EBS, table-based business events (inserts, updates, and deletes) are frequently implemented not as inline trigger logic but as calls into stored packages. The trigger itself becomes a thin wrapper that delegates to a package procedure, allowing the same logic to be reused, versioned, and maintained independently of the table DDL.

In the context of Oracle EBS 12.1.1 and 12.2.2, PER_CTC_RKD belongs to the PER (Human Resources) product family, specifically the CTC (Core Talent/Compensation-related) module grouping. Its documented purpose centers on executing post-delete processing logic. This classification as "OTHER" in ETRM indicates it is not a public, supported API; it is internal infrastructure invoked by the EBS runtime rather than by external callers.

Key Procedures and Functions

ETRM 12.2.2 documents a single procedure for this package:

• AFTER_DELETE — The sole documented entry point. As the name indicates, this procedure encapsulates the logic that must execute after a row has been deleted from the associated base table. In the standard EBS trigger-package pattern, the table's AFTER DELETE row trigger invokes this procedure, passing the identifying key of the deleted row so that dependent or audit data can be reconciled. Typical responsibilities for such a procedure include cascading cleanup of child records, removal or invalidation of related lookup rows, and maintenance of audit or history tables. The procedure is not documented with a public parameter list, and no supported signature is exposed for direct invocation by customer code.

Tables Accessed

The ETRM dependency extract for PER_CTC_RKD records references to SYS and STANDARD only, which are PL/SQL system packages (STANDARD supplies core language constructs) rather than application tables. The documentation does not enumerate specific APPS synonyms or base tables read or written by the package body. This is typical of row-level trigger packages: the underlying table access is often performed dynamically or is obscured in the dependency report at the synonym level. Practically, the package operates against the base table whose delete trigger it supports, together with any child or audit tables that require synchronized cleanup when that delete occurs. Because the concrete table list is not exposed in the metadata, the authoritative source remains the package body itself as deployed in the APPS schema.

Usage Notes

PER_CTC_RKD is not intended for direct invocation. It is referenced by APPS.PER_CTC_DEL (a package in the same functional family) and by PER_CTC_RKD itself, indicating mutual or recursive calls within the CTC deletion-processing framework. The documented "referenced by one other package" relationship confirms it sits within an internal call chain rather than at an application boundary.

In practice, the package is invoked indirectly whenever the corresponding base-table rows are deleted — whether through an EBS form (for example, an HR or compensation maintenance form performing a row delete), a concurrent program that purges or reorganizes data, or a PL/SQL API that issues the delete. Administrators and developers troubleshooting delete-related errors, orphaned child records, or audit-trail gaps in the CTC module should inspect this package and PER_CTC_DEL. Customizations must not call AFTER_DELETE directly, because doing so bypasses the trigger's :OLD row context and can produce inconsistent results; supported integration should instead occur at the public API layer of the PER product. As with all APPS-owned packages, modifications are lost on patching, and the VALID status recorded in ETRM reflects the object's compiled state in the reference environment.