Search Results delegate_contact_title_meaning




Overview
Explore in AI Chat

Overview

The APPS.OTA_EVENT_ASSOCIAT_BILLING_V view is a supplementary database view belonging to the Oracle E-Business Suite (EBS) Enterprise Training Management (ETRM) module, owned by the APPS schema and identified in FND Design Data as OTA.OTA_EVENT_ASSOCIAT_BILLING_V. Its status is VALID. According to the Oracle metadata, this is a "supplementary view used to simplify forms coding," with an explicit warning that Oracle does not recommend querying or altering data through this view, as its definition may change dramatically in subsequent minor or major releases. It is therefore best treated as an internal mechanism that consolidates billing-related attributes for delegate event associations, rather than as a public, stable reporting interface.

Functionally, the view flattens event association, booking, delegate contact, and finance transaction data into a single row set, enabling ETRM billing and forms logic to retrieve pricing, deal, invoice, and customer details without manually joining the underlying base tables. The presence of the column BOOKING_DEAL_TYPE — the term the user searched for — indicates that deal classification used for booking-level pricing is exposed directly by this view for downstream billing processing.

Underlying Base Objects

The documented dependencies show that the view is defined over a mix of ETRM base tables, HR packages, and Oracle Trading Community Architecture (TCA) objects. The core ETRM objects include OTA_EVENT_ASSOCIATIONS, OTA_DELEGATE_BOOKINGS, OTA_EVENTS, OTA_BOOKING_DEALS, OTA_PRICE_LISTS, OTA_FINANCE_HEADERS, OTA_FINANCE_LINES, and OTA_BOOKING_STATUS_TYPES_TL. Reference data is sourced through HR_LOOKUPS, AR_LOOKUPS, and HR_LOOKUPS views, while HR_GENERAL and HR_API packages supply derived values such as formatted names. Customer and party information is joined via HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_ORG_CONTACTS, HZ_PARTIES, and HZ_RELATIONSHIPS. Working through these dependencies, EVENT_ASSOCIATION_ID derives from OTA_EVENT_ASSOCIATIONS, BOOKING_DEAL data derives from OTA_BOOKING_DEALS, and invoice amounts come from OTA_FINANCE_HEADERS and OTA_FINANCE_LINES.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling delegate bookings to finance lines, reporting on the booking deal type applied to each booking, and validating invoice amounts against the standard event price. The following query demonstrates retrieving deal and billing information for a specific booking:

  • SELECT EVENT_ASSOCIATION_ID, BOOKING_ID, BOOKING_DEAL_NAME, BOOKING_DEAL_TYPE, EVENT_STANDARD_PRICE, MONEY_AMOUNT FROM APPS.OTA_EVENT_ASSOCIAT_BILLING_V WHERE BOOKING_DEAL_TYPE = :deal_type;
  • SELECT BOOKING_ID, DELEGATE_CONTACT_FULL_NAME, EVENT_STANDARD_PRICE, EVENT_CURRENCY_CODE, MONEY_AMOUNT FROM APPS.OTA_EVENT_ASSOCIAT_BILLING_V WHERE BOOKING_ID = :booking_id;

Because the metadata warns against reliance on this view, production reporting should preferably be built directly on the documented base tables rather than through OTA_EVENT_ASSOCIAT_BILLING_V.