Results for “so_price_lists_vl”

30 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The SO_PRICE_LISTS_VL view is a seeded, valid database object owned by the APPS schema within the Oracle E-Business Suite Order Entry (OE) module. It is a "_VL" (view with language) translation view that presents price list header information in a language-aware format. The designation "_VL" indicates the view joins a base table (SO_PRICE_LISTS_B) with a translation table (SO_PRICE_LISTS_TL) and filters the translation rows by the session language using USERENV('LANG'). This design lets reports, concurrent programs, and integrated applications retrieve price list data with translatable attributes—specifically the price list name and description—displayed in the language of the running user session.

Price lists in EBS define the selling prices of items for a given currency, along with associated freight terms, shipping methods, and payment terms. Because the descriptive text of a price list can be translated into multiple languages, Oracle supplies this "_VL" view to abstract the join logic, ensuring that any query consistently returns only the single row appropriate to the current language environment.

Underlying Base Objects

The view is defined over two documented base objects, exposed to APPS as synonyms:

  • SO_PRICE_LISTS_B — the "base" table, storing language-independent attributes of the price list header, including the primary key PRICE_LIST_ID, currency, terms, dates, and the standard Who columns.
  • SO_PRICE_LISTS_TL — the translation table, storing language-specific descriptive text such as NAME and DESCRIPTION, keyed by both PRICE_LIST_ID and LANGUAGE.

The view joins the two on PRICE_LIST_ID, constrained by T.LANGUAGE = USERENV('LANG'). All columns from the base table are projected unaltered, while NAME and DESCRIPTION are sourced from the translation table. The ROW_ID pseudo-column is carried from the base table for use in DML and APIs that require row identification.

Key Columns

Common Use Cases and Queries

This view is commonly used in reports, interfaces, and validation routines that must display price list names in the user's language. Typical scenarios include order entry inquiries, pricing setup reports, and integration extracts that reference price list headers.

Listing active price lists:

SELECT price_list_id, name, currency_code
FROM   apps.so_price_lists_vl
WHERE  SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Joining to order lines to resolve the price list name:

SELECT l.line_id, p.name price_list
FROM   oe_order_lines_all l,
       apps.so_price_lists_vl p
WHERE  l.price_list_id = p.price_list_id;

Because the view already applies the language restriction, it should be preferred over manually joining the base and translation tables, reducing risk of returning multiple or incorrect language rows.