Search Results ota_adt_rkd

Overview

OTA_ADT_RKD is a row-level database trigger handler package in the Oracle E-Business Suite Applications (APPS) schema. The suffix "RKD" follows the Oracle Designer/Forms table-handling convention, signifying that this package implements the DELETE (K in the "R-K-D" naming pattern) trigger logic for its associated base table. In the Oracle EBS architecture, each table that requires auditing, denormalization maintenance, or referential integrity enforcement is paired with a generated handler package. OTA_ADT_RKD fulfills this role for an OTA (Oracle Training Administration) table keyed by ACTIVITY_ID, which corresponds to the OTA_ACTIVITY tables that store training activity and course delivery records.

The package is declared AUTHID CURRENT_USER and carries the header identifier otadtrhi.pkh, confirming it is a generated table-handler (HR-style generator) script rather than manually authored PL/SQL. Its stated purpose is to execute business logic immediately after a row is deleted from the underlying table.

Key Procedures and Functions

The ETRM metadata documents exactly one public procedure:

• AFTER_DELETE — The post-delete trigger handler. It is invoked after a DELETE operation succeeds against the activity table. Its parameters capture the identifying key of the removed row together with the pre-delete ("old") values of descriptive columns — specifically the language, name, description, and source language. The "_o" suffix on the parameter names denotes old-row values, which are available only in an AFTER DELETE trigger context. The procedure provides the hook point where downstream processing can occur, such as writing audit or shadow records, calling the corresponding post-delete processing in the OTA_ACTIVITY business API, or propagating deletions to dependent entities. No parameter lists are invented here; the documented signature is the authoritative interface.

Tables Accessed

The ETRM metadata records no tables referenced through APPS synonyms for this package. This absence is expected for an R-K-D handler: the package itself does not query or DML other tables directly. Instead, it operates on the row image of the parent table supplied by the trigger, and any cascading work is typically delegated to business-layer APIs or other handler packages. The referenced-by relationship, in which one other package invokes OTA_ADT_RKD, indicates that the trigger on the parent activity table calls this handler. Consumers should therefore verify actual dependencies in the database rather than assume the package is dependency-free, since the excerpt is limited to the package specification.

Usage Notes

OTA_ADT_RKD is not intended for direct invocation by users, forms, or concurrent programs. It is called exclusively from the database trigger associated with its parent table whenever a training activity row is deleted. Typical call paths include:

• Oracle Forms-based maintenance screens in the OTA product where users delete training activities.
• Concurrent programs or interfaces that remove or purge activity records.
• Custom PL/SQL that performs a DELETE against the parent table, which then fires the trigger and this handler.

Because the package is generated, it should be treated as read-only from a development perspective; customizations belong in the calling trigger or in the business API. Implementers tracing OTA training-activity deletions — for example to diagnose audit gaps or unexpected cascading effects — should inspect the trigger definition and the one dependent package identified in ETRM, since the handler's specification alone exposes only the AFTER_DELETE entry point.