Results for “oe_price_list_lines_v”

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

Overview

The OE_PRICE_LIST_LINES_V view is an Oracle E-Business Suite database object owned by the Advanced Pricing (QP) module. It exposes price list line information derived from the pricing schema. The view is explicitly documented as being provided for backward compatibility for other applications, meaning Oracle maintains it so existing customizations, integrations, and dependent products continue to function even though the underlying pricing architecture has evolved. In Release 12.1.1 and 12.2.2, the primary pricing data resides in QP-specific tables, but legacy code paths and pre-existing reports frequently reference this compatibility view. Because the ETRM documentation records that it is "not implemented in this database," the view may not exist as a compiled object in every environment; where it is present, it functions as a read-only projection over the price list line records.

Underlying Base Objects

The view text establishes the base objects the view queries. Its principal source is OE_PRICE_LIST_LINES (aliased SPLL), which supplies the price list line attributes, descriptive flexfield columns, and audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, and related who-columns). It is joined to three supporting objects:

• MTL_SYSTEM_ITEMS_KFV (MSI) — supplies item details, joined on INVENTORY_ITEM_ID and constrained by the organization profile option QP_ORGANIZATION_ID via the ORG_ID/Master Item relationship.
• OE_PRICING_RULES (SPR) — supplies the pricing rule name (SPR.NAME), joined on PRICING_RULE_ID with an outer join (+), so price list lines without a rule still return.
• MTL_CUSTOMER_ITEMS_ALL_V (MCI) — supplies the customer name for customer item entries, joined on CUSTOMER_ITEM_ID.

The view therefore consolidates item, pricing rule, and customer item context around each price list line, rather than storing any data itself.

Key Columns

• ROW_ID / PRICE_LIST_LINE_ID — primary identifiers for the price list line record.
• PRICE_LIST_ID — parent price list to which the line belongs.
• INVENTORY_ITEM_ID — inventory item priced on the line; enriched by MTL_SYSTEM_ITEMS_KFV columns such as CONCATENATED_SEGMENTS, PADDED_CONCATENATED_SEGMENTS, ITEM_DESCRIPTION, and PRIMARY_UNIT_OF_MEASURE.
• UNIT_CODE, METHOD_CODE, LIST_PRICE — the unit of measure, pricing method, and the list price value.
• PRICING_RULE_ID — link to OE_PRICING_RULES; the rule name is exposed as SPR.NAME.
• CUSTOMER_ITEM_ID / CUSTOMER_NAME — customer item reference and associated customer name.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the line.
• PRICING_CONTEXT, PRICING_ATTRIBUTE1–15 — pricing descriptive flexfield segments.
• CONTEXT, ATTRIBUTE1–15 — standard descriptive flexfield segments.
• REPRICE_FLAG, PRIMARY, REVISION, REVISION_DATE, REVISION_REASON_CODE, COMMENTS — control and revision-tracking attributes.

Common Use Cases and Queries

This view is typically used for reporting and backward-compatible integration where a flattened price list line combined with item and rule descriptions is required. Because it depends on the QP_ORGANIZATION_ID profile option, query results reflect the item organization defined for the session.

A representative query retrieving active price list lines with item details:

• SELECT price_list_id, inventory_item_id, concatenated_segments, item_description, list_price, name, start_date_active, end_date_active
• FROM oe_price_list_lines_v
• WHERE start_date_active <= SYSDATE AND (end_date_active IS NULL OR end_date_active >= SYSDATE);

For migration or reconciliation work, joining on PRICE_LIST_ID against the modern QP price list tables allows comparison between the legacy compatibility view and current pricing definitions. Given the "not implemented in this database" note, developers should verify the view's existence in the target environment before relying on it, and confirm the QP_ORGANIZATION_ID profile setting, as item joins will silently exclude rows when the organization does not match.