Search Results ota_tdb_del




Overview
Explore in AI Chat

Overview

OTA_TDB_DEL is an Oracle Applications (APPS) PL/SQL package belonging to the Oracle Time and Labor / OTA (Oracle Training Administration and delegate booking) family of database objects within Oracle E-Business Suite. In ETRM 12.2.2 the package is classified with an API classification of OTHER, indicating that it serves an internal processing role rather than a published, externally supported interface. Its purpose, consistent with its naming convention and its dependency on OTA_TDB_SHD, is the deletion and cleanup of delegate training and booking data. The "_DEL" suffix denotes a delete-handling utility, while "TDB" corresponds to the delegate booking schema area. The package is created and owned by the APPS schema and holds a VALID status, confirming that it is successfully compiled and available for execution.

Key Procedures and Functions

The documented package exposes a single identifiable program unit named DEL. As its name implies, this procedure is responsible for removing delegate booking records and their dependent child rows. It encapsulates the delete logic required by the delegate booking model so that callers need not replicate the multi-table cleanup sequence themselves. The ETRM metadata does not publish a parameter list for this procedure, and none should be assumed. It is worth noting that OTA_TDB_DEL also references itself, indicating that recursion or internal re-entry is possible within its delete processing, and it depends upon the shadow table object OTA_TDB_SHD, which is typically used to stage records immediately before or during deletion.

Tables Accessed

The package operates against four documented tables accessed through APPS synonyms: OTA_BOOKING_STATUS_HISTORIES, OTA_DELEGATE_BOOKINGS, OTA_FRM_NOTIF_SUBSCRIBERS, and OTA_FRM_OBJ_INCLUSIONS. OTA_DELEGATE_BOOKINGS is the principal business entity, holding the delegate's training booking records; the DEL procedure removes rows from this table. OTA_BOOKING_STATUS_HISTORIES stores status transition history for those bookings and must be purged in step with the parent booking to avoid orphaned audit rows. OTA_FRM_NOTIF_SUBSCRIBERS and OTA_FRM_OBJ_INCLUSIONS belong to the OTA framework notification and object inclusion tables, which hold subscriber and inclusion relationships tied to the deleted objects. Their inclusion confirms that deletion of delegate bookings also requires cleaning up framework-level notification subscriptions and object inclusion mappings so that no residual references remain.

Usage Notes

OTA_TDB_DEL is referenced by one other package, OTA_DELEGATE_BOOKING_API, which is the most probable production caller. This relationship indicates that the DEL procedure is invoked indirectly through the delegate booking API rather than being called directly by end users. Typical invocation paths include form-based actions on delegate booking screens, or concurrent program and workflow processing that cancels, withdraws, or otherwise removes delegate bookings. Because the package is classified as OTHER rather than a public API, customizations should not call OTA_TDB_DEL directly; custom code should instead invoke the supported OTA_DELEGATE_BOOKING_API entry points, letting that API orchestrate the delete through this package. Direct invocation risks bypassing validation, notification, and audit-handling performed by the API layer. Any modification to the package body should be treated as an unsupported customization, and the reference to OTA_TDB_SHD suggests that delete operations are paired with a shadow-table mechanism that should be preserved. The package status remains VALID in both Oracle EBS 12.1.1 and 12.2.2.