Search Results pricing_attribute1




Overview
Explore in AI Chat

Overview

APPS.OE_PRICE_LIST_LINES_115_V is a backward-compatibility view in Oracle E-Business Suite (12.1.1 and 12.2.2) owned by the APPS schema within the QP — Advanced Pricing product. Its documented purpose is to expose Price List Line information in the same column layout that Oracle Order Management (OE) applications expected in release 11.5, allowing older integrations, custom reports, and dependent code to continue functioning after the pricing data model was refactored under the Advanced Pricing module. The view is marked VALID. It is defined in the ETRM metadata as a subset of the modern price list line data: the defining query selects from OE_PRICE_LIST_LINES (accessed via a synonym) with a WHERE clause restricting results to rows where CUSTOMER_ITEM_ID IS NULL, and it projects a fixed set of columns using NULL literals to fill positions that the 11.5 contract required but that are not physically stored in the current base table.

Underlying Base Objects

The view is defined over the synonym OE_PRICE_LIST_LINES, which resolves to the QP price list line table. Documented referenced base objects also include the packages QP_PRICE_LIST_PVT and QP_UTIL, which support the Advanced Pricing price list line logic and utilities. Because the query filters on CUSTOMER_ITEM_ID IS NULL, the view exposes only item-level price list lines and excludes customer-item-specific lines, which are retained in the underlying table for the richer pricing model. The view itself stores no data; all values are derived at runtime from the base objects. Columns such as CUSTOMER_ITEM_ID, REVISION, REVISION_DATE, REVISION_REASON_CODE, COMMENTS, PRIMARY, and CONVERT_FROM are not carried over from the base table — they are projected as NULL to satisfy the legacy 11.5 column signature.

Key Columns

Common Use Cases and Queries

The view is most often used by legacy Order Management reports and interfaces that still reference the 11.5 price list line structure, and by developers who need basic list prices with the legacy column set. A representative query selecting the flexfield segment of interest is:

SELECT price_list_id, inventory_item_id, unit_code, list_price, pricing_attribute15
FROM apps.oe_price_list_lines_115_v
WHERE price_list_id = :p_price_list_id
ORDER BY inventory_item_id;

Because CUSTOMER_ITEM_ID is forced to NULL, any code relying on customer-specific pricing through this view will not see those lines; such logic must query the base Advanced Pricing tables directly. Users should also confirm that PRICING_ATTRIBUTE15 is enabled and populated in the pricing descriptive flexfield before depending on it, since context-sensitive segments may be null when not applicable.