Search Results oe_price_lists_v




Overview
Explore in AI Chat

Overview

OE_PRICE_LISTS_V is an APPS-owned database view in the Oracle E-Business Suite QP (Advanced Pricing) product family. Per its documented metadata, it presents price list header information and exists primarily for backward compatibility, exposing a stable interface that older Oracle applications and integrations can reference even as the underlying pricing architecture evolves. The view is listed as VALID in the ETRM 12.2.2 metadata, and it is available in both 12.1.1 and 12.2.2 releases.

Because it is a view rather than a table, OE_PRICE_LISTS_V does not itself store data. It is a read-oriented projection of price list definitions maintained in the pricing module. Its name reflects legacy Oracle Order Entry ("OE") naming, which indicates that it originally served order-entry-related components before price list management was consolidated under Advanced Pricing. Applications that still issue queries against the OE prefix — rather than the native QP objects — continue to function through this compatibility layer.

Underlying Base Objects

The documented base objects referenced by OE_PRICE_LISTS_V are:

  • QP_PRICE_LISTS_V (VIEW) — the immediate source object from which all columns are selected.
  • QP_PRICE_LIST_PVT (PACKAGE) — the pricing API package associated with price list processing logic, listed as a referenced object in the ETRM metadata.

The view text is a direct projection: SELECT ... FROM QP_PRICE_LISTS_V QPPRL. No joins or derivations are applied within OE_PRICE_LISTS_V itself; column-for-column, it mirrors QP_PRICE_LISTS_V, including the full set of DDL audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) and the DESCRIPTIVE FLEXFIELD columns CONTEXT and ATTRIBUTE1 through ATTRIBUTE15. This means any change to QP_PRICE_LISTS_V propagates automatically to OE_PRICE_LISTS_V, and consumers should treat the QP object as the authoritative definition.

Key Columns

  • PRICE_LIST_ID — Primary key and the unique identifier for each price list row; the standard join key to price list line and qualifier tables.
  • NAME — The user-defined price list name displayed in pricing and order-entry forms.
  • CURRENCY_CODE — The currency in which list prices are denominated.
  • ROUNDING_FACTOR — The value used to round calculated list prices.
  • SECONDARY_PRICE_LIST_ID — The identifier of an associated secondary price list. This is the column most directly relevant to the search term and is exposed unmodified from QP_PRICE_LISTS_V; it is used in pricing setups where a supplementary list operates alongside the primary list.
  • SHIP_METHOD_CODE and FREIGHT_TERMS_CODE — Shipping-method and freight-term qualifiers attached to the price list.
  • TERMS_ID — Payment terms associated with the list.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — The active date range governing when the price list is available for pricing.
  • COMMENTS and DESCRIPTION — Free-text annotations.
  • CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — The descriptive flexfield segments enabling customer-specific extensions.

Common Use Cases and Queries

Typical uses include validating price list setups, resolving a price list name to its ID for integration payloads, and reporting on active price lists and their currency and rounding behavior. The SECON DARY_PRICE_LIST_ID column is frequently queried during pricing configuration audits.

List active price lists:

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

Locate a price list by name and inspect its secondary list:

SELECT price_list_id, name, currency_code,
       secondary_price_list_id, rounding_factor
FROM   apps.oe_price_lists_v
WHERE  name = :price_list_name;

Find all lists configured with a secondary price list:

SELECT price_list_id, name, secondary_price_list_id
FROM   apps.oe_price_lists_v
WHERE  secondary_price_list_id IS NOT NULL;

Because the view is a thin projection over QP_PRICE_LISTS_V, queries carry no additional filtering semantics; callers must apply their own date, organization, and security predicates. Oracle documents this object as a backward-compatibility interface, so new development should generally target QP_PRICE_LISTS_V or the QP_PRICE_LIST_PVT APIs, while existing OE-prefixed integrations may continue to rely on OE_PRICE_LISTS_V.