Search Results get_associations

Overview

OTA_TEA_BUS is a business-layer PL/SQL package in the Oracle E-Business Suite Training and Event Management (OTA) module. Its name and the body header identifier ottea01t.pkb reflect its role as one of the "business" (BUS) packages that implement validation, derivation, and rule enforcement logic for the OTA schema. Unlike the public OTA APIs that expose a formal interface to external callers, OTA_TEA_BUS supplies the internal checks and computations invoked by forms, other OTA packages, and concurrent processes whenever event, booking, deal, and price-list data is created or modified.

The package is classified as API of type OTHER in ETRM 12.2.2 and resides in the APPS schema. The body excerpt documents the tea_has_tdb function, which determines whether a delegate booking exists for a given event and customer by querying OTA_DELEGATE_BOOKINGS, and a check that precedes it through hr_api.mandatory_arg_error. This pattern of mandatory-argument validation and cursor-driven existence checks is characteristic of the package as a whole. The package is referenced by four other packages, confirming that it sits in the dependency chain of higher-level OTA processing.

Key Procedures and Functions

Eight documented procedures and functions make up the public surface of the package:

• INSERT_VALIDATE — Validates the data supplied when a new record (for example, a booking, deal, or finance line) is inserted, ensuring mandatory and referential conditions are met before the row is committed.
• UPDATE_VALIDATE — Applies the equivalent validation rules when an existing record is modified.
• DELETE_VALIDATE — Checks whether a record may be removed, typically enforcing that dependent delegate bookings, finance lines, or price-list references do not exist.
• CLIENT_CHECK_EVENT_CUSTOMER — Confirms the relationship between an event and its customer (client), using the delegate-booking and event-association data to establish that the specified customer is a legitimate participant or purchaser for that event.
• DERIVE_STANDARD_PRICE — Calculates the standard price applicable to a booking or event, drawing on the OTA price-list tables to supply a default when no negotiated price applies.
• NEW_PRICE_LIST_HIT — Determines whether a given transaction matches an entry on a price list, returning the applicable price-list entry so that the correct price can be applied.
• CHECK_PRE_PURCHASE_AGREEMENT — Evaluates whether a pre-purchase (pre-agreement) arrangement exists that governs the booking, allowing discounts or contractual terms to be honored.
• NUMBER_OF_DELEGATES — Computes or returns the count of delegates associated with an event or booking, used for capacity checks and pricing tiers.

Although the user search term "check_customer" does not correspond to one of these documented names, the closest documented procedure is CLIENT_CHECK_EVENT_CUSTOMER, which performs the customer-event consistency check. The body excerpt shows the related tea_has_tdb function and check_event procedure, both of which follow the same validation idiom and may be private helpers alongside the listed public entries.

Tables Accessed

OTA_TEA_BUS reads and, in the validate routines, indirectly governs changes to a wide set of OTA and shared reference tables:

• OTA_EVENTS, OTA_EVENT_ASSOCIATIONS — Event definition and the associations that link events to customers, suppliers, and related objects; used by event-customer and event-type checks.
• OTA_DELEGATE_BOOKINGS — Delegate-level booking records, queried by tea_has_tdb and the customer check to confirm delegate participation.
• OTA_BOOKING_DEALS, OTA_BOOKING_STATUS_TYPES — Deal terms and booking status classifications used in insert, update, and delete validation.
• OTA_FINANCE_LINES — Financial detail lines checked when validating and deleting bookings.
• OTA_PRICE_LISTS, OTA_PRICE_LIST_ENTRIES — Price lists and their entries, read by DERIVE_STANDARD_PRICE and NEW_PRICE_LIST_HIT to resolve applicable pricing.
• OTA_VENDOR_SUPPLIES — Vendor supply records relevant to procurement and pre-purchase evaluation.
• HZ_CUST_ACCOUNTS, HZ_PARTIES — Trading-community customer and party master data used to resolve the customer identity in CLIENT_CHECK_EVENT_CUSTOMER.
• HR_ALL_ORGANIZATION_UNITS, PER_ALL_POSITIONS, PER_JOBS — Organization, position, and job reference data used for validation and delegate/employee resolution.

All access is performed through APPS synonyms, consistent with the package's installation in the APPS schema.

Usage Notes

OTA_TEA_BUS is an internal business package rather than a directly invoked public API. It is typically called from OTA module forms and from other OTA packages — four packages reference it in the documented dependency set — whenever event, booking, deal, or price data is validated or derived. Because its procedures accept and return no externally documented parameter lists, the safe usage pattern is to invoke it only through the documented callers rather than calling its procedures directly from custom code. Customizations that must enforce the same validations should reference OTA_TEA_BUS from within an OTA context where the required arguments are already assembled by the calling form or package. When the package body is compiled or invalidated, the dependent packages listed in the dependency set must be recompiled, and any change to underlying tables such as OTA_DELEGATE_BOOKINGS or the price-list structures should be reviewed against this package's cursors to preserve validation integrity.