Search Results oe_price_list_lines




Overview
Explore in AI Chat

Overview

APPS.OE_PRICE_LIST_LINES_115_V is a compatibility view in the Oracle E-Business Suite Order Management and Advanced Pricing modules. It exposes a subset of the OE_PRICE_LIST_LINES entity, filtered to rows where CUSTOMER_ITEM_ID is null, and projects fixed NULL placeholders into columns that exist in a later, more feature-rich definition of the same logical entity. The view name suffix "115" signals that it reproduces the row shape and semantics of the price list line structure as it existed at release 11.5, allowing code written against that older interface to continue functioning against the 12.1.1 and 12.2.2 data model without modification.

Its principal role is backward compatibility for reports, concurrent programs, and integration interfaces that reference customer-item-agnostic price list lines. Because it is owned by APPS and defined over synonyms and public packages, it is intended to be queried directly by custom code rather than treated as a base table.

Underlying Base Objects

The view is defined over three documented base objects: the OE_PRICE_LIST_LINES synonym (which resolves to the actual price list line table in the APPS schema), and the QP_PRICE_LIST_PVT and QP_UTIL packages. The two packages belong to the Advanced Pricing (QP) module and provide the pricing business logic; their presence in the dependency chain indicates that the view participates in the pricing engine's price list resolution path. The driving table, however, is OE_PRICE_LIST_LINES, from which all persisted values are drawn.

The WHERE clause CUSTOMER_ITEM_ID IS NULL restricts output to price list lines that are not tied to a specific customer item. Lines associated with customer items are therefore excluded and must be sourced from a different view or directly from the base object.

Key Columns

Common Use Cases and Queries

Typical usage includes legacy report regeneration, migration scripts, and interfaces that expect the pre-12 pricing line layout. A representative query follows:

  • SELECT PRICE_LIST_ID, INVENTORY_ITEM_ID, UNIT_CODE, LIST_PRICE FROM APPS.OE_PRICE_LIST_LINES_115_V WHERE PRICE_LIST_ID = :p_list_id;
  • SELECT INVENTORY_ITEM_ID, LIST_PRICE, START_DATE_ACTIVE, END_DATE_ACTIVE FROM APPS.OE_PRICE_LIST_LINES_115_V WHERE INVENTORY_ITEM_ID = :p_item AND SYSDATE BETWEEN START_DATE_ACTIVE AND END_DATE_ACTIVE;
  • SELECT COUNT(*) FROM APPS.OE_PRICE_LIST_LINES_115_V WHERE PRICE_LIST_ID = :p_list_id;

Because convert_from is always NULL and customer-item lines are excluded, code requiring those values must use the current-generation view or the base table instead.