Search Results tpl_name

Overview

APPS.OTA_BOOKING_DEALS_V is a reporting and integration view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 ETRM (Enterprise Training Resource Management) module, which is part of Oracle Learning Management. It presents booking deal records — negotiated agreements that govern how a customer purchases training places at a discounted rate — in a denormalized, human-readable form. Because the view joins and decodes reference data, callers do not need to resolve lookup codes, party identifiers, or price list types themselves.

The view is particularly relevant to searches for cus_name, since it exposes a CUS_NAME column derived from HZ_PARTIES.PARTY_NAME, truncated to 50 characters via SUBSTRB. This allows reports and interfaces to display the customer name directly without joining to the trading community model (TCM) tables. The view also computes runtime attributes through the OTA_TBD_API package, such as tickets-for-learning balances, giving consumers a consolidated snapshot of each booking deal.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms:

• OTA_BOOKING_DEALS (alias TBD) — the driving table containing booking deal header data.
• OTA_PRICE_LISTS (TPL) — supplies price list name, type, unit type, single-unit price, and currency.
• OTA_EVENTS / OTA_EVENTS_TL (EVT, ENT) — provide event currency and the translated event title.
• OTA_ACTIVITY_VERSIONS_TL (TAV) — supplies the activity version name.
• OTA_CATEGORY_USAGES_TL (CAT) — provides the translated category name.
• HZ_PARTIES (PARTY) — the source of the customer name exposed as CUS_NAME.
• HZ_CUST_ACCOUNTS — links the booking deal customer to the party record.
• FND_USER (USR) — returns the approving user name.
• HR_GENERAL (package) — used via DECODE_LOOKUP to translate lookup codes into meanings.
• OTA_TBD_API (package) — supplies the calculated TFL_PURCHASED, TFL_BALANCE, and TFL_FLAG values.

In short, the view joins booking deal headers to pricing, event, customer, and user reference data, then layers lookup decoding and API-derived calculations on top.

Key Columns

• BOOKING_DEAL_ID, NAME, TYPE, TBD_TYPE_MEANING — identity and classification of the deal, with the type decoded from the BOOKING_DEAL_TYPE lookup.
• CUSTOMER_ID, CUS_NAME — the customer identifier and the 50-character party name.
• TPL_NAME, TPL_TYPE, TPL_TYPE_MEANING, TPL_UNIT, TPL_UNIT_PRICE, CURRENCY_CODE — price list details and currency, defaulting to the event currency when the price list has none.
• EVENT_ID, EVT_TITLE, ACTIVITY_VERSION_ID, TAV_NAME, CATEGORY, CAT_NAME — event, activity version, and category context.
• START_DATE, END_DATE, DISCOUNT_PERCENTAGE, NUMBER_OF_PLACES, OVERDRAFT_LIMIT, LIMIT_EACH_EVENT_FLAG — commercial terms of the deal.
• TFL_PURCHASED, TFL_BALANCE, TFL_FLAG — tickets-for-learning metrics calculated by OTA_TBD_API, populated for purchase-type deals.
• APPROVED_BY_PERSON_ID, PPF_FULL_NAME — approver information returned from FND_USER.
• TBD_INFORMATION1–20 and audit columns — descriptive flexfield attributes plus standard CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include listing active booking deals by customer, reconciling tickets-for-learning balances, and exporting deal terms to external systems. A straightforward query supporting the cus_name search is:

• SELECT booking_deal_id, name, cus_name, tbd_type_meaning, tpl_name, discount_percentage, number_of_places FROM apps.ota_booking_deals_v WHERE cus_name LIKE :customer_name;
• SELECT cus_name, tfl_purchased, tfl_balance, tfl_flag FROM apps.ota_booking_deals_v WHERE tfl_flag = 'Y';
• SELECT booking_deal_id, cus_name, evt_title, start_date, end_date, currency_code FROM apps.ota_booking_deals_v WHERE start_date >= :from_date AND end_date <= :to_date ORDER BY cus_name;

Because CUS_NAME, lookup meanings, and TFL calculations are already resolved, the view simplifies both ad hoc reporting and integration extracts across EBS 12.1.1 and 12.2.2.