Search Results ota_delegate_booking_be3




Overview
Explore in AI Chat

Overview

APPS.OTA_DELEGATE_BOOKING_BE3 is a PL/SQL package within the Oracle E-Business Suite (EBS) Training and Learning Management (OTM/OTA) module. It belongs to the business entity layer that supports delegate booking functionality, which governs how learners (delegates) are associated with scheduled training events and classes. The "BE3" suffix indicates this is a business-entity handler generated by the Oracle Application Object Library (AOL) API generator, a legacy code-generation facility whose header signature (hrapiwfe.pkb) confirms it was produced automatically rather than hand-coded. The package header was generated on 30 March 2009 and carries the version tag 120.4.12010000.2, placing it within the 12.1.1 code line that also ships in 12.2.2. It is classified as OTHER in the ETRM repository, meaning it is not formally designated as a public, invokable API but rather as an internal generated handler. Its role is narrow and transactional: it exposes the low-level operation required to remove a delegate booking record while maintaining version-number integrity for optimistic locking. In practice, this package sits beneath the user-facing booking screens and is invoked indirectly by higher-level OTA APIs, forms, or concurrent processes rather than called directly by end users.

Key Procedures and Functions

The package exposes a single documented procedure:

  • DELETE_DELEGATE_BOOKING_A — Performs the deletion of a delegate booking. The "_A" suffix denotes an AOL-generated "A" (primary) version of the delete operation, which is the entry point the framework invokes after validation and business-rule checks have already been applied by callers. It accepts a booking identifier and an object version number, the latter used to enforce optimistic concurrency control so that a stale user session cannot overwrite or delete a record that a concurrent transaction has already modified. If the supplied version does not match the current database value, the delete is rejected.

No public functions are documented. Because the metadata lists only one procedure, the package's behavioral surface is intentionally minimal, consistent with a generated handler whose complexity resides in the underlying private implementation body rather than the specification.

Tables Accessed

The documented table references resolve through APPS synonyms and include:

  • PER_WF_EVENTS_S — The Oracle Workflow events sequence/table used to support workflow event subscription and event-key generation associated with booking lifecycle operations. Deletion of a delegate booking may raise or record a workflow event so that downstream business events (such as notification or subscription handlers) remain consistent.
  • DBMS_LOB — The Oracle-supplied large-object package, referenced for handling CLOB/BLOB columns (for example comments or notes attached to a booking) during the delete routine.
  • DUAL — The standard single-row utility table, typically reached through a synonym in generated code for scalar evaluations and sequence lookups.

These references indicate the procedure reads the identified booking for version checking and writes/deletes the corresponding rows while interacting with workflow-event infrastructure rather than the more obvious OTA booking base tables, which are accessed by the parent business logic.

Usage Notes

OTA_DELEGATE_BOOKING_BE3 is invoked as part of the broader delegate booking deletion chain, not directly from standard concurrent program parameters or self-service forms. Callers are typically other OTA packages (the metadata records that one other package references it) or generated business-entity code that sequences validation, then calls this handler to perform the physical removal. The "_A" procedure convention means it should be treated as a framework entry point: applications should route deletions through the supported OTA booking APIs, which enforce security, validation, and event publication, and which then delegate to this package. Because it is an unclassified (OTHER) generated handler carrying an Oracle proprietary header, it is not intended for direct custom invocation, and any customization should avoid modifying it, since regenerating the AOL layer would overwrite changes. Its presence is consistent across 12.1.1 and 12.2.2, so behavior and signature remain stable across those releases, simplifying upgrade and retrofitting analysis.