Search Results deafult_price_list

Overview

APPS.OTFV_PRICE_LISTS is a read-only reporting view within the Oracle E-Business Suite (EBS) Training Administration (OTA) module, exposed by the Oracle Training and Event Management (OTM/ETRM) product family. The view consolidates price list definitions maintained in the Oracle iLearning and Training Administration subsystems, presenting them in a denormalized, human-readable format suitable for queries, concurrent programs, and downstream integrations. Its primary role is to translate coded values (currency codes, lookup types, and language-dependent organization names) into consumer-facing descriptions while restricting the result set to the current session's business group.

The "F" prefix in the view name (OTFV) follows Oracle's standard convention for "form" views — objects that surface data for display in a specific functional context rather than for base-table manipulation. The database definition includes the WITH READ ONLY clause, which guarantees that no DML can be issued against the view, reinforcing its role as a reporting and integration interface. Notably, the column aliased deafult_price_list (a misspelling preserved in the shipped definition) is the column most relevant to the search term "default_price_list"; it exposes whether a given price list is flagged as the default for its business group.

Underlying Base Objects

As documented in the ETRM 12.2.2 metadata, OTFV_PRICE_LISTS is defined over four referenced base objects:

• OTA_PRICE_LISTS (SYNONYM) — the primary driving table containing the actual price list records, columns such as NAME, DESCRIPTION, CURRENCY_CODE, DEFAULT_FLAG, START_DATE, END_DATE, PRICE_LIST_TYPE, SINGLE_UNIT_PRICE, and TRAINING_UNIT_TYPE.
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — the translated organization units table, joined on ORGANIZATION_ID = BUSINESS_GROUP_ID and LANGUAGE = USERENV('LANG') to retrieve the business group name in the user's session language.
• HR_BIS (PACKAGE) — the Business Intelligence System package providing the bis_decode_lookup function used to decode YES_NO and PRICE_LIST_TYPE lookups into descriptions.
• OTA_GENERAL (PACKAGE) — supplies fnd_currency_name for currency decoding and get_business_group_id for the row-level business group restriction.

The view therefore functions as a semantic layer over the base OTA_PRICE_LISTS table, extending it with translated lookups and organization context.

Key Columns

• business_group_name — the translated name of the business group that owns the price list.
• price_list_name and description — the identifying text for the price list.
• currency — the currency code resolved to its descriptive name via fnd_currency_name.
• deafult_price_list — the decoded YES/NO flag indicating whether the price list is the default. This is the column a user searching "deafult_price_list" is most likely seeking.
• price_list_start_date, price_list_end_date — validity dates for the price list.
• price_list_type — decoded PRICE_LIST_TYPE lookup.
• unit_price and training_unit — the single unit price and associated training unit type.
• price_list_id, business_group_id — surrogate keys for joining back to base tables.

Common Use Cases and Queries

Typical use cases include identifying the default price list for a business group, listing all active price lists and their currencies, and feeding price list data into reporting or integration extracts. Because the view automatically applies NVL(OTA_GENERAL.GET_BUSINESS_GROUP_ID, ...) and language filtering, queries return only the current session's business group context.

Example: retrieving the default price list:

SELECT price_list_id,
       price_list_name,
       deafult_price_list,
       currency
FROM   apps.otfv_price_lists
WHERE  deafult_price_list = 'Yes';

Example: listing all currently valid price lists:

SELECT price_list_name,
       price_list_type,
       price_list_start_date,
       price_list_end_date
FROM   apps.otfv_price_lists
WHERE  SYSDATE BETWEEN price_list_start_date AND NVL(price_list_end_date, SYSDATE);

Because the object is inherently read-only, it is safe for BI Publisher reports, OBIEE extracts, and ad-hoc SQL without risk of accidental DML.