Results for “oebv_price_lists”

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

Overview

OEBV_PRICE_LISTS is a read-only reporting view exposed by the Oracle Order Entry (OE) module. In the ETRM 12.2.2 documentation set the object is catalogued under the title "View: OEBV_PRICE_LISTS" with the product designation OE – Order Entry and a description of simply "Retrofitted," indicating that the object was carried forward from an earlier release lineage into the current EBS code level rather than being a newly designed 12.2 construct. The ETRM metadata notes that the view is "Not implemented in this database," meaning it is documented as part of the dictionary but was not instantiated in the reference environment against which the documentation was generated.

The view presents a denormalized, consumer-friendly projection of price list header data. Its role is to provide a stable, narrowed read interface over the SO_PRICE_LISTS base table so that reports, concurrent programs, and integration extracts can retrieve price list attributes without carrying the full column breadth of the underlying transactional entity. Because the definition terminates in WITH READ ONLY, the view is strictly a query object; no DML is possible through it.

Underlying Base Objects

The ETRM metadata documents no referenced base objects separately, but the embedded view text establishes the relationship unambiguously. The view is defined over a single source: SO_PRICE_LISTS. The projection selects fifteen named columns from that table and applies the read-only constraint. No joins, unions, or aggregations appear in the documented text, so OEBV_PRICE_LISTS is a straight column-subset view rather than a transformation or consolidation layer. This single-table lineage is significant for performance analysis: predicate pushdown to SO_PRICE_LISTS is unaffected, and any index on the base table remains available to queries issued against the view.

Key Columns

The columns exposed by the view map directly to price list header attributes, with one nomenclature divergence from the base table worth noting.

• PRICE_LIST_ID – Primary identifier of the price list header; the principal join key to price list line and qualifier tables.
• NAME and DESCRIPTION – Human-readable identification of the list for display and selection purposes.
• SECONDARY_PRICE_LIST_ID – The attribute most relevant to users searching on this term. It references a secondary price list associated with the header, supporting scenarios in which price resolution falls through from a primary list to a secondary one. Because it is an identifier, it is typically resolved against SO_PRICE_LISTS itself to obtain the secondary list's NAME.
• FREIGHT_TERMS_CODE – Documented in the view text as FREIGHT_TERMS_CODE, while the corresponding column list abbreviated it as FREIGHT_TERMS.
• ROUNDING_FACTOR – Controls rounding behavior applied to list prices.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Validity window of the price list; abbreviated elsewhere as START_DATE and END_DATE.
• SHIP_METHOD_CODE and TERMS_ID – Shipping method and payment terms defaults associated with the list.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY – Standard EBS audit columns supporting change tracking and extract delta logic.

Common Use Cases and Queries

Typical usage centers on price list inventory reporting, active-list validation, and cross-referencing secondary price list relationships. A foundational query retrieving active lists and resolving their secondary counterparts follows:

• SELECT p.PRICE_LIST_ID, p.NAME, p.SECONDARY_PRICE_LIST_ID, s.NAME AS SECONDARY_NAME FROM OEBV_PRICE_LISTS p LEFT JOIN SO_PRICE_LISTS s ON s.PRICE_LIST_ID = p.SECONDARY_PRICE_LIST_ID WHERE SYSDATE BETWEEN p.START_DATE_ACTIVE AND NVL(p.END_DATE_ACTIVE, SYSDATE + 1);

A second common pattern verifies that a price list was created or modified within a given window for audit or interface reconciliation:

• SELECT PRICE_LIST_ID, NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM OEBV_PRICE_LISTS WHERE LAST_UPDATE_DATE >= :p_from_date;

All such statements inherit the view's read-only nature, making OEBV_PRICE_LISTS suitable for reporting responsibility layers while all maintenance continues to be performed through the supported Order Management forms and APIs against SO_PRICE_LISTS.