Results for “as_quote_items_v”

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

Overview

AS_QUOTE_ITEMS_V is a Sales Foundation (AS) reporting view that exposes quote item pricing information by flattening the relationship between Oracle Advanced Pricing price lists and their associated price list lines. In Oracle EBS 12.1.1 and 12.2.2, the view is part of the pricing infrastructure underlying quote and order entry functionality. Its principal distinguishing feature is that it unifies two distinct association paths through a UNION: lines tied to a price list directly via PRICE_LIST_ID, and lines tied to a price list through the SECONDARY_PRICE_LIST_ID attribute maintained on the price list header. The column set is intentionally narrow — a set of identifiers, a unit-of-measure code, and fifteen generic pricing attribute columns — which makes the view a composite key surface rather than a transactional detail source. It contains no pricing amounts, no effective dates, and no quote identifiers, and is therefore best understood as a resolution or lookup view used to determine which inventory items and pricing attribute combinations apply to a given price list, including its secondary list. ETRM metadata documents the view as "Not implemented in this database" for the referenced environment, meaning the definition is catalogued but the object is not instantiated in the queried instance; it may be created during specific product configuration or installation phases. Consumers should verify existence at runtime via ALL_VIEWS before depending on it in code.

Underlying Base Objects

The documented view text defines AS_QUOTE_ITEMS_V entirely over two base tables: SO_PRICE_LISTS (aliased PL) and SO_PRICE_LIST_LINES (aliased PLL). The join predicate is PLL.PRICE_LIST_ID = PL.PRICE_LIST_ID in the first branch of the UNION, and PLL.PRICE_LIST_ID = PL.SECONDARY_PRICE_LIST_ID in the second. Both branches project an identical select list, ensuring UNION semantics can be applied without column mapping errors. The practical effect is that a single price list header can contribute rows in two ways: once for lines belonging to the list itself, and once for lines belonging to whichever list is designated as its secondary price list. Because the metadata records no accompanying DBA implementation data, no indexes, synonyms, or grants specific to the view are documented. The reliance on SO_PRICE_LISTS and SO_PRICE_LIST_LINES places the view firmly within the pricing data model rather than the quote data model, despite the "AS_QUOTE" naming prefix.

Key Columns

• PRICE_LIST_ID — Identifier of the price list header selected in the current row's branch. In the secondary branch, this is the parent list, not the list owning the line.
• SECONDARY_PRICE_LIST_ID — The header-level attribute that drives the union; it identifies the alternate list whose lines are surfaced alongside the primary list's lines.
• INVENTORY_ITEM_ID — Surrogate key of the item for which the price list line exists; joins to MTL_SYSTEM_ITEMS_B.
• UNIT_CODE — Unit of measure associated with the price list line, expressed as a UOM code.
• PRICING_ATTRIBUTE1 through PRICING_ATTRIBUTE15 — Fifteen descriptive flexfield-backed columns carrying the pricing context dimensions (for example, item category, customer class, or qualifier values) that distinguish one price list line from another.

Because there is no unique constraint inherent to the projection, duplicate-looking rows can legitimately appear where a list and its secondary list share an item and attribute combination. Any downstream aggregation must account for this.

Common Use Cases and Queries

The most direct use is enumerating the pricing context a price list exposes, including via its secondary list assignment. A typical query joining to the item master is:

• Listing items effective for a given list: SELECT inventory_item_id, unit_code FROM as_quote_items_v WHERE price_list_id = :p_list_id;
• Locating lists that route through a secondary list: SELECT DISTINCT price_list_id, secondary_price_list_id FROM as_quote_items_v WHERE secondary_price_list_id IS NOT NULL;
• Resolving an item across both list paths: SELECT price_list_id, secondary_price_list_id, unit_code FROM as_quote_items_v WHERE inventory_item_id = :p_item_id AND pricing_attribute1 = :p_attr1;
• Detecting overlap between a list and its secondary list: SELECT inventory_item_id, COUNT(*) FROM as_quote_items_v WHERE price_list_id = :p_list_id GROUP BY inventory_item_id HAVING COUNT(*) > 1;

Typical scenarios include debugging why an expected item does not appear during quote or order pricing, auditing secondary price list configuration before a pricing migration, and validating that pricing attribute combinations are unique per list. Because the view lacks effective dates and amounts, it should be paired with SO_PRICE_LIST_LINES or QP_LIST_HEADERS_B when temporal or monetary detail is required.