Search Results original_list_price




Overview
Explore in AI Chat

Overview

APPS.OEBV_ORDER_LINES is a seeded Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as ONT.OEBV_ORDER_LINES. It exposes order line-level information from the Order Management (ONT) module in a denormalized, business-friendly form. The view is classified as an internal object, and Oracle Corporation explicitly does not support direct customer access to its contents except through standard Oracle Applications programs. Despite that restriction, the view is widely referenced within Oracle's own concurrent programs, OBIEE/BI Publisher extracts, and ETL routines that stage order data for downstream reporting.

The view presents one row per order line and includes quantities, pricing, scheduling, fulfillment, tax, customer, and audit columns. Because it includes both the raw priced attributes (UNIT_LIST_PRICE, ORIGINAL_LIST_PRICE, UNIT_SELLING_PRICE) and derived quantities, it is commonly used as a single-source snapshot for order-line analysis in 12.1.1 and 12.2.2.

Underlying Base Objects

The documented referenced base object is OE_ORDER_LINES, referenced through a synonym. In EBS, OE_ORDER_LINES stores the transactional detail of sales orders, and it is the primary underlying table for this view. The view inherits the line-level grain and the ORG_ID partitioning characteristic of OE_ORDER_LINES, meaning queries must be filtered by operating unit (ORG_ID) for correct results in multi-org environments.

Additional attributes exposed by the view — such as pricing list, agreement, salesrep, and commitment identifiers — are sourced from related pricing, customer, and order-management entities that the view joins internally. The _LA: prefixed columns are flexfield/attribute descriptors surfaced by the view definition, and _DF:PRICING indicates a descriptive flexfield context on the pricing dimension.

Key Columns

Common Use Cases and Queries

A frequent scenario is a list-price variance report that compares the original captured list price against the current line list price to surface unauthorized discounts or list changes.

SELECT line_id,
       header_id,
       org_id,
       ordered_item_id,
       unit_list_price,
       original_list_price,
       unit_list_price - original_list_price AS list_price_delta,
       unit_selling_price,
       ordered_quantity,
       ordered_quantity_uom,
       schedule_ship_date
FROM   apps.oebv_order_lines
WHERE  org_id = :p_org_id
AND    original_list_price <> unit_list_price
ORDER  BY list_price_delta DESC;

Another common use is order-line backlog and fulfillment tracking, aggregating ordered, shipped, and cancelled quantities by item and requested date:

SELECT ordered_item_id,
       SUM(ordered_quantity)   AS qty_ordered,
       SUM(shipped_quantity)   AS qty_shipped,
       SUM(cancelled_quantity) AS qty_cancelled,
       SUM(fulfilled_quantity) AS qty_fulfilled
FROM   apps.oebv_order_lines
WHERE  org_id = :p_org_id
AND    request_date BETWEEN :p_start AND :p_end
GROUP  BY ordered_item_id;

Because this is an unsupported internal view, custom interfaces should ideally read the supported OE_ORDER_LINES and related pricing tables directly, or consume order data through the published Order Management open interfaces and public APIs. Where read-only reporting against OEBV_ORDER_LINES is used, Oracle recommends confining access to reporting schemas and never updating the view.