Search Results budget_currency_code




Overview
Explore in AI Chat

Overview

OTA_OFFERINGS_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the OTA — Learning Management product family. It presents offering-level master data for learning offerings along with their language-dependent descriptive attributes, exposing a single denormalized row per offering in the session's language. In Oracle EBS 12.1.1 and 12.2.2, the view serves as the primary read-only reporting and integration surface for offerings, allowing concurrent programs, OBIEE extracts, and custom interfaces to retrieve offering names and descriptions alongside scheduling, audience, delivery, and financial attributes without joining the base and translation tables manually. Because the translation predicate is resolved through USERENV('LANG'), the view automatically returns the translated NAME and DESCRIPTION appropriate to the runtime language environment, which simplifies multilingual deployments and reporting.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms: OTA_OFFERINGS (aliased OFR) and OTA_OFFERINGS_TL (aliased OFL). OTA_OFFERINGS holds the non-translatable, language-independent attributes of each offering, including identifiers, scheduling dates, capacity, cost, and currency information. OTA_OFFERINGS_TL is the translation table that stores the language-specific NAME, DESCRIPTION, and LANGUAGE columns. The join is performed on OFFERING_ID, and the view is filtered by OFL.LANGUAGE = USERENV('LANG'), so only the row matching the caller's language is returned. The view is documented as VALID in APPS and includes OFR.ROWID as its ROW_ID column, which preserves row-level addressing for the underlying OTA_OFFERINGS record.

Key Columns

The view exposes a broad set of offering attributes. The requested column, BUDGET_CURRENCY_CODE, is one of the two financial currency columns, the other being CURRENCY_CODE; BUDGET_CURRENCY_CODE identifies the currency in which BUDGET_COST is expressed, while CURRENCY_CODE qualifies STANDARD_PRICE and other pricing amounts. Together with ACTUAL_COST, BUDGET_COST, and STANDARD_PRICE, these columns support cost and pricing analysis. Scheduling and audience columns include START_DATE, END_DATE, DURATION, DURATION_UNITS, MINIMUM_ATTENDEES, MAXIMUM_ATTENDEES, and MAXIMUM_INTERNAL_ATTENDEES. Delivery and content attributes include DELIVERY_MODE_ID, LANGUAGE_ID, LEARNING_OBJECT_ID, OWNER_ID, ACTIVITY_VERSION_ID, and the player configuration flags. Descriptive columns NAME and DESCRIPTION originate from the translation table. Standard EBS audit and extensibility columns are present, including OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, DATA_SOURCE, VENDOR_ID, COMPETENCY_UPDATE_LEVEL, ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE20, and BUSINESS_GROUP_ID for multi-org filtering.

Common Use Cases and Queries

Typical usage includes offering catalogs, cost and budget reporting, and interfaces that load offering data into external systems. The view is commonly filtered by BUSINESS_GROUP_ID for multi-org security and by date ranges for active offerings. A representative query retrieving budget currency alongside cost data is:

  • SELECT offering_id, name, start_date, end_date, budget_cost, budget_currency_code, standard_price, currency_code FROM apps.ota_offerings_vl WHERE business_group_id = :p_bg_id AND sysdate BETWEEN start_date AND NVL(end_date, sysdate);
  • SELECT o.offering_id, o.name, o.budget_currency_code, o.budget_cost, o.actual_cost, o.maximum_attendees FROM apps.ota_offerings_vl o WHERE o.duration_units = 'DAYS' AND o.maximum_internal_attendees > 0 ORDER BY o.start_date;
  • SELECT offering_id, name, currency_code, standard_price, vendor_id, data_source FROM apps.ota_offerings_vl WHERE vendor_id IS NOT NULL AND language_id = USERENV('LANG');

Because NAME and DESCRIPTION are language-resolved at runtime, report authors should not add an independent join to OTA_OFFERINGS_TL, as doing so can produce duplicate rows; the view already enforces the correct translation. For multipart currency comparisons, BUDGET_CURRENCY_CODE must be used in conjunction with BUDGET_COST, while CURRENCY_CODE applies to standard and price-basis amounts. All queries should respect the documented owner, APPS, and the referenced base objects OTA_OFFERINGS and OTA_OFFERINGS_TL, which define the view's authoritative lineage in ETRM 12.2.2.