Search Results delete_delegate_booking_a




Overview

OTA_DELEGATE_BOOKING_BK3 is an Oracle EBS Applications (APPS) package body that serves as an API hook pre-processor for the Oracle Training Administration (OTA) module, part of Oracle HRMS/Enterprise Learning Management. It was auto-generated by the Oracle HRMS API Hook Pre-processor, as indicated by the header comment, and belongs to the family of generated "BK" (hook) layer packages that wrap business logic with commit-unit management and application hook invocation. The package addresses the business function of deleting a delegate booking — the record that associates a person (delegate) with a training booking event. Deletion of delegate bookings is a routine administrative operation in training administration, performed when a learner cancels or is removed from a scheduled class or event. The BK3 layer ensures that such deletions pass through the standard HRMS API framework, respecting validation sets, commit units, and registered application hooks. The object is classified as API classification OTHER and resides in the APPS schema, dating to a header revision of 2011 with generation in late 2012.

Key Procedures and Functions

The package exposes two documented procedures, both named for the delete-delegate-booking operation:

  • DELETE_DELEGATE_BOOKING_A — The primary hook procedure. It accepts the booking, object version, and person context, sets a location marker for debugging, captures the current commit unit via hr_api.return_commit_unit, conditionally invokes application hooks through the corresponding BE3 business-entity package (OTA_DELEGATE_BOOKING_BE3.DELETE_DELEGATE_BOOKING_A), ends the validation set using hr_multi_message.end_validation_set, and validates the commit unit with hr_api.validate_commit_unit. This structure guarantees that any registered customer hooks execute around the core deletion logic while transactional integrity is preserved.
  • DELETE_DELEGATE_BOOKING_B — A secondary procedure in the same package that, per the documented source, performs no substantive work beyond entry and exit location markers. It functions as a placeholder or companion hook entry point within the generated BK3 layer, consistent with the pattern whereby the "B" variant is reserved for a different hook stage or simply carries no logic in this revision.

Tables Accessed

The provided ETRM metadata lists no directly referenced tables via APPS synonyms for this package body. Because it is a generated hook pre-processor, all DML against the underlying delegate booking tables is delegated to the BE3 business entity package (OTA_DELEGATE_BOOKING_BE3) and ultimately to the table-handler layer. Any reads or writes to delegate booking, booking, or person records occur downstream of the calls shown in the source excerpt, not within this package itself. The absence of direct table references reflects the layered architecture of the HRMS API stack rather than an expectation of no data access.

Usage Notes

This package is invoked in the context of the standard HRMS API call chain for deleting a delegate booking. Typical invocation paths include the Oracle Training Administration forms, which call the public API surface that routes through the BK3 hook layer, and any concurrent programs or custom PL/SQL that call the corresponding delete API. It is referenced by one other package in the ETRM inventory, confirming its role as a dependent layer rather than an entry point. Because the package is auto-generated with a revision-tagged header, it should not be modified directly; customizations belong in user-registered hooks invoked through the hr_api.call_app_hooks mechanism. The commit-unit handling and validation-set management embedded here mean callers must respect HRMS API commit conventions, invoking the API within a valid commit unit and allowing the framework to manage validation messaging. Administrators and developers searching on "delete_delegate_booking" will find this object as the pre-processor stage whose naming mirrors the underlying deletion operation.