Search Results maintain_delegate_bookings




Overview

The APPS.OTA_EVENT_ASSOCIATIONS_PKG package body is a component of the Oracle E-Business Suite (EBS) Oracle Training Administration (OTA) module, which is part of the Oracle iLearning and OTA Event Management application family. Its principal business function is to manage and validate the associations that exist between events, delegates, booking deals, and finance lines within the training administration lifecycle. The package encapsulates the business rules that govern how delegate bookings are created, maintained, and reconciled against the constraints defined for a booking deal — most notably the maximum number of places permitted for a given deal.

Within the ETRM 12.2.2 metadata, this package body is classified with an API classification of OTHER, indicating it is not exposed as a formally published public API but rather serves as a supporting internal utility package invoked by other OTA components. This classification is significant for developers, as it implies the package should generally be called indirectly through supported business flows rather than directly from custom code.

Key Procedures and Functions

The documented ETRM metadata lists a single publicly named procedure for this package body:

  • MAINTAIN_DELEGATE_BOOKINGS — This is the primary documented entry point associated with the search term maintain_delegate_bookings. Its purpose is to carry out the maintenance of delegate booking records associated with events and booking deals. The procedure is responsible for the validation and persistence logic relating to delegate bookings, coordinating with the surrounding event association rules. As the metadata does not include an enumerated parameter list, the exact signature is not restated here; consumers should consult the package specification in their environment.

In addition to the documented procedure, the excerpt reveals private helper logic contained in the package body, notably check_booking_deal_places. This private procedure validates that the maximum number of places for a booking deal is not exceeded. It reads the configured maximum from OTA_BOOKING_DEALS and compares it against the sum of places already consumed by qualifying delegate bookings. The cursor aggregates NUMBER_OF_PLACES from OTA_DELEGATE_BOOKINGS joined to OTA_FINANCE_LINES, filtering on non-cancelled finance lines and booking status types in the active set ('P', 'A', 'E'). This private routine is typically called as part of the logic invoked by MAINTAIN_DELEGATE_BOOKINGS.

Tables Accessed

The package body operates against the following OTA base tables through APPS synonyms:

  • OTA_BOOKING_DEALS — Read to obtain the maximum number of places (NUMBER_OF_PLACES) configured for a booking deal, which serves as the ceiling constraint for the places check.
  • OTA_BOOKING_STATUS_TYPES — Read to restrict the places aggregation to bookings in active or eligible status types ('P', 'A', 'E'), excluding cancelled or otherwise inactive bookings.
  • OTA_DELEGATE_BOOKINGS — Both read and written; this is the central transactional table for delegate booking records. The places-used cursor aggregates NUMBER_OF_PLACES from here.
  • OTA_EVENTS — Read to evaluate event-level attributes such as PRICE_BASIS ('C' per customer or 'S' per student), which influences whether a booking consumes a shared place.
  • OTA_FINANCE_LINES — Read to link bookings to their booking deal and to filter out cancelled lines (CANCELLED_FLAG = 'N'), ensuring only financially active bookings count toward the place limit.

Usage Notes

The OTA_EVENT_ASSOCIATIONS_PKG is referenced by two other packages within the Oracle EBS application, confirming its role as a shared internal utility rather than a standalone API. It is typically invoked during delegate booking maintenance transactions — such as when a delegate is added to, or removed from, an event tied to a booking deal — so that place limits and associations are validated consistently.

Because the package is classified as OTHER and not a supported public API, direct invocation from custom forms, concurrent programs, or personalizations is discouraged. Organizations extending Oracle EBS 12.1.1 or 12.2.2 should instead rely on the supported OTA business flows and standard Oracle Forms that call this package internally. Where the check_booking_deal_places logic is relevant, developers should ensure that any custom code enforcing equivalent limits mirrors the status filters and price-basis rules described above, as these embody Oracle's standard booking deal constraint semantics.