Search Results entry_end_date




Overview
Explore in AI Chat

Overview

The APPS.OTFV_PRICE_LIST_ENTRIES view is a business view template generated from the Oracle Learning Management (OTA) flexfield framework. It consolidates pricing data across price lists, price list entries, and their associated training activities into a single flattened structure, and is principally consumed by Oracle EBS reporting and integration layers that need to reference price list entries by their descriptive attributes. The view carries a static '_DF:OTA:OTA_PRICE_LIST_ENTRIES:PLE' descriptor as a column, reflecting its origin as a descriptive flexfield (DFF) view template. It remains VALID in both release 12.1.1 and 12.2.2, defined WITH READ ONLY, meaning it is query-only and cannot be used as a DML target.

Underlying Base Objects

The view is defined over several base and supporting objects, joined as follows:

Key Columns

Columns are grouped by source entity:

Common Use Cases and Queries

A frequent requirement is to identify which price list is the default within a business group and enumerate its entries. The view makes this straightforward because the default flag is pre-decoded and the business group filter already honours session context.

SELECT price_list_name,
       price_list_entry_id,
       activity_name,
       price,
       price_basis,
       entry_start_date,
       entry_end_date
  FROM apps.otfv_price_list_entries
 WHERE default_price_list = 'Yes'
   AND SYSDATE BETWEEN entry_start_date AND entry_end_date;

To report all entries with their associated training activities and currencies for a given business group:

SELECT business_group_name,
       price_list_name,
       price_list_currency,
       activity_type,
       activity_name,
       unit_price
  FROM apps.otfv_price_list_entries
 WHERE price_list_date_to > SYSDATE;

Because the view enforces read-only access and applies the GET_BUSINESS_GROUP_ID predicate, it is well suited to BI Publisher reports, OAF-based inquiry pages, and integration extracts where price list pricing must be surfaced without bespoke join logic. Note the outer joins to activity versions and definitions mean that price list entries not yet linked to an activity are still returned, with activity columns null.