Results for “as_quote_price_items_v”

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

Overview

AS_QUOTE_PRICE_ITEMS_V is a database view defined within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, belonging to the AS – Sales Foundation product family. Its documented description is the "Quote items pricing view," indicating that it is designed to expose quote line items together with the pricing information associated with a given price list. The view is principally a reporting and integration artifact: it flattens data spread across quote header/line tables, price list definitions, and the item master so that external programs, custom reports, and interfaces can retrieve quoting results without reproducing the underlying multi-table join logic.

The ETRM metadata explicitly records the implementation status as "Not implemented in this database," meaning the object is delivered as part of the application's data model but is not materialized as a physical table or instantiated view in that particular instance. Consequently, querying the view in those environments returns no rows until the relevant product components are installed or the view is created by the application's install scripts. This is a critical consideration for developers who assume the view is queryable on every EBS instance.

The user's search term, pricing_attribute15, is directly relevant because the view's defining SQL joins price list lines to quote items using the full set of PRICING_ATTRIBUTE1 through PRICING_ATTRIBUTE15 (and beyond) as part of the matching criteria. These attributes form the price list line's qualifier key, and the view's row identification depends upon them.

Underlying Base Objects

Although the documented metadata lists no referenced base objects, the view text reveals the actual sources involved:

• AS_QUOTE_ITEMS_V (AQIV) — the driving quote items view, supplying PRICE_LIST_ID, INVENTORY_ITEM_ID, UNIT_CODE, and the pricing attribute columns.
• SO_PRICE_LISTS (PL) — joined on PRICE_LIST_ID, providing the price list header context.
• SO_PRICE_LIST_LINES (PLL, PLL2) — the price list line detail tables, joined with outer joins ((+)) so that quote items retain rows even when no matching price list line exists.
• MTL_SYSTEM_ITEMS_VL (MSI) — the item master view supplying description, organization, and the SEGMENT1–SEGMENT20 item key flexfield attributes.

The join keys between AQIV and PLL consist of the item, unit of measure, price list, and — importantly — the NVL(...,' ') equality tests on PRICING_ATTRIBUTE1 through at least PRICING_ATTRIBUTE15. This defensive NVL treatment treats a NULL pricing attribute as a single space, ensuring that quote items with unpopulated attributes still match price list lines rather than being silently dropped.

Key Columns

• PRICE_LIST_ID — identifier of the price list against which the quote item is priced.
• INVENTORY_ITEM_ID — the inventory item being quoted, the central key across all joins.
• DESCRIPTION — item description drawn from MTL_SYSTEM_ITEMS_VL.
• ORGANIZATION_ID — the item-master organization context.
• SEGMENT1–SEGMENT20 — the item key flexfield segments, exposed for reporting and integration.
• PRICING_ATTRIBUTE1–PRICING_ATTRIBUTE15 (and beyond) — the pricing qualifier columns used both as join predicates and as returned attributes. pricing_attribute15 is one of the qualifying attributes whose NULL-adjusted equality determines whether a quote item links to a price list line.

Many columns in the select list are literal NULL placeholders, indicating the view was authored to a fixed column footprint expected by its consumers rather than mirroring every source column.

Common Use Cases and Queries

Typical uses include extracting quote line pricing for analysis, validating that quote items resolve to a price list line, and feeding downstream pricing interfaces. A basic query resembles:

• SELECT PRICE_LIST_ID, INVENTORY_ITEM_ID, DESCRIPTION, SEGMENT1
• FROM AS_QUOTE_PRICE_ITEMS_V
• WHERE PRICE_LIST_ID = :p_price_list_id;

Because the object may report "Not implemented in this database," developers should first confirm its presence in ALL_VIEWS before relying on it, and should be aware that the outer joins mean price list line pricing may be absent for quote items lacking a matching line — a behavior consumers must handle explicitly.