Search Results event_price_basis




Overview
Explore in AI Chat

Overview

The APPS.OTFV_PRICE_LIST_ENTRIES view is a reporting and integration object within the Oracle E-Business Suite (EBS) Training and Certification / ETRM (Enterprise Training Resource Management) module of Oracle Learning Management (OLM). It presents a denormalized, presentation-ready projection of training price list entries, joining price list headers to their associated activity versions, activity definitions, and organization (business group) information. Because the underlying price list configuration is stored in normalized base tables, this view allows developers, report authors, and integrators to consume a single, flattened result set that exposes business-friendly decoded values rather than raw coded identifiers.

The view is particularly relevant to the search term event_price_basis. The column price_basis in this view is produced by the call HR_BIS.BIS_DECODE_LOOKUP('EVENT_PRICE_BASIS', ple.price_basis), which resolves the stored lookup code into its descriptive meaning (for example, per event, per attendee, or per unit). This makes the view a convenient source for reports that need to explain how a given price was applied.

The view is defined WITH READ ONLY, confirming that it is intended exclusively for querying and cannot be used for DML.

Underlying Base Objects

Per the documented ETRM metadata, OTFV_PRICE_LIST_ENTRIES is defined over the following base objects:

The translation tables are outer-joined with userenv('LANG') restrictions, so entries persist even when translations are missing.

Key Columns

  • business_group_name — the translated name of the business group (organization) owning the price list.
  • price — the monetary value defined on the price list entry.
  • price_basis — the decoded EVENT_PRICE_BASIS lookup meaning, indicating the basis on which the price applies.
  • entry_start_date / entry_end_date — the validity window of the individual price list entry.
  • maximum_attendees / minimum_attendees — the attendee count boundaries for the entry.
  • price_list_name, price_list_type, price_list_description — header attributes, with price_list_type decoded via the PRICE_LIST_TYPE lookup.
  • default_price_list — decoded YES_NO flag indicating whether the list is a default.
  • training_units, unit_price — the unit definition and corresponding single-unit price.
  • price_list_currency — the descriptive currency name derived from FND_CURRENCY_NAME.
  • activity_name, activity_type — the translated activity (offering) version name and its type.
  • business_group_id, activity_version_id, activity_id, price_list_id, price_list_entry_id, rco_id — surrogate keys useful for joins and drill-downs.

Common Use Cases and Queries

Typical uses include price list auditing, pricing analytics, integration extracts, and reporting on how events are priced by basis and attendee thresholds.

  • Listing all entries for a given price list with decoded price basis.
  • Reporting prices by activity and currency for a business group.
  • Identifying entries filtered by price_basis meaning for compliance or margin analysis.

Sample SQL:

SELECT price_list_name, activity_name, price, price_basis, price_list_currency,
       entry_start_date, entry_end_date, minimum_attendees, maximum_attendees
FROM apps.otfv_price_list_entries
WHERE price_basis = 'Per Attendee'
  AND SYSDATE BETWEEN entry_start_date AND NVL(entry_end_date, SYSDATE)
ORDER BY price_list_name, activity_name;

Because the view is READ ONLY and enforces business group context via OTA_GENERAL.GET_BUSINESS_GROUP_ID, queries automatically respect the caller's security profile. Reports requiring the numeric lookup code rather than the decoded meaning should query the base OTA_PRICE_LIST_ENTRIES table directly.