Search Results pricing_method

Overview

OEBV_PRICE_LIST_LINES is a read-only reporting view in the Oracle E-Business Suite Order Entry (OE) module. It exposes a curated subset of the price list line data maintained in the underlying SO_PRICE_LIST_LINES base table, presenting the pricing information that drives Oracle Advanced Pricing calculations at order entry time. The view is classified as "Retrofitted," indicating that it was introduced or regenerated to conform to a naming and structural convention during an ETRM migration or upgrade cycle, rather than originating as a native seeded object in the earliest releases.

Within EBS 12.1.1 and 12.2.2, the object serves reporting and integration consumers who require a stable, read-only projection of price list lines without direct access to the transactional base table. Because the view is defined with a WITH READ ONLY clause, it cannot be used as a DML target; it is intended strictly for query, extraction, and downstream data integration. The requested alias "so_price_list_lines" reflects the base table name from which the view is derived, and users searching that term should understand that OEBV_PRICE_LIST_LINES is the reporting-layer representation of that table.

Underlying Base Objects

The documented definition selects exclusively from SO_PRICE_LIST_LINES, the core Order Entry table that stores price list line records. No additional joins, lookup tables, or reference objects are documented in the view text, and ETRM metadata records no other referenced base objects. This makes the relationship straightforward: OEBV_PRICE_LIST_LINES is a column-filtered, read-only projection of SO_PRICE_LIST_LINES.

Each row in the view corresponds to a single price list line, keyed by PRICE_LIST_LINE_ID. Because no join logic is applied, attributes such as the pricing method code, list price, and effective dates are drawn directly from the base table without translation or enrichment. Consumers requiring descriptive pricing method names, item descriptions, or currency details must obtain those from other objects such as the pricing method and item master tables, since this view does not denormalize them.

Note that the ETRM implementation record states the view is "Not implemented in this database." Where the object is absent, the base table SO_PRICE_LIST_LINES remains the authoritative source and equivalent queries must target it directly.

Key Columns

The view exposes the following significant columns, drawn from the base table:

• PRICE_LIST_LINE_ID — Unique identifier for the price list line; the primary key of each row.
• METHOD_CODE / PRICING_METHOD — Code identifying the pricing method applied to the line (for example, list price or formula-based pricing).
• LIST_PRICE — The price value associated with the line.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date range during which the line is valid for pricing.
• PRICE_LIST_ID — Foreign key to the parent price list header.
• PRICING_RULE_ID — Reference to the pricing rule governing qualification and calculation.
• INVENTORY_ITEM_ID — The item to which the price list line applies.
• UNIT_CODE — Unit of measure associated with the line.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard audit columns tracking who created and last modified each record and when.

The column list in the view text uses PRICE_LIST_LINE_ID, METHOD_CODE, and LIST_PRICE, while the documented column listing refers to PRICING_METHOD, START_DATE, and END_DATE; these represent the same underlying attributes.

Common Use Cases and Queries

Typical scenarios include validating effective pricing during a date window, exporting price lists for integration with external order capture systems, and auditing price changes via the audit columns.

To retrieve active lines for a specific price list and item:

• SELECT price_list_line_id, method_code, list_price, start_date_active, end_date_active FROM oebv_price_list_lines WHERE price_list_id = :p_list AND inventory_item_id = :p_item AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

To audit recently modified pricing records:

• SELECT price_list_line_id, last_updated_by, last_update_date FROM oebv_price_list_lines WHERE last_update_date >= :p_since ORDER BY last_update_date DESC;

To review pricing rules tied to a price list:

• SELECT price_list_id, pricing_rule_id, COUNT(*) FROM oebv_price_list_lines GROUP BY price_list_id, pricing_rule_id;

Because the view is read-only and unavailable in databases where it is not implemented, scripts should fall back to SO_PRICE_LIST_LINES when the view is missing. All queries should respect effective-date logic to avoid returning expired pricing records.