Results for “ibe_order_quote_line_v”

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

Overview

IBE_ORDER_QUOTE_LINE_V is an iStore (IBE) reporting view that exposes quote line information maintained by Oracle Advanced Pricing / Oracle Quoting, specifically the ASO_QUOTE_LINES table. The view presents one row per quote line, enriched with related-line metadata drawn from ASO_LINE_RELATIONSHIPS, and is intended for use in reporting, integration, and inquiry against quote lines created and managed through the quoting flow. Because it joins quote lines to their relationship records via an outer join, it preserves quote lines that have no associated related-line definition, making it suitable for full-population extracts rather than strictly relationship-scoped queries.

In Oracle EBS 12.1.1 and 12.2.2, this view functions as a read-only, denormalized projection. It does not store data and is not implemented as a physical object in the extract database; its definition is a SQL SELECT layered over the two underlying ASO tables. Any change committed to the base tables is immediately visible through the view.

Underlying Base Objects

The view is defined over two documented base tables:

• ASO_QUOTE_LINES (aliased L) — the driving table, supplying all core quote line columns. The join predicate is L.QUOTE_LINE_ID = R.QUOTE_LINE_ID(+).
• ASO_LINE_RELATIONSHIPS (aliased R) — supplies related-line information through an outer (plus) join, allowing quote lines without relationship rows to remain in the result set.

The outer join is significant: only quote lines that have matching relationship records will return populated relationship columns, while all other relationship columns (prefixed R) will be NULL. The view does not expose any additional derived or aggregate columns; every column maps directly to a column on one of the two base tables.

Key Columns

Core quote line columns include:

• QUOTE_LINE_ID — primary identifier for the quote line; the join key to ASO_LINE_RELATIONSHIPS.
• QUOTE_HEADER_ID — foreign key to the parent quote header.
• ORG_ID and ORGANIZATION_ID — operating unit and inventory organization context.
• LINE_NUMBER, LINE_CATEGORY_CODE, ITEM_TYPE_CODE, START_DATE_ACTIVE, END_DATE_ACTIVE — line sequencing and effective dating.
• INVENTORY_ITEM_ID, QUANTITY, UOM_CODE — item and quantity attributes.
• PRICE_LIST_ID, PRICE_LIST_LINE_ID, CURRENCY_CODE, LINE_LIST_PRICE, LINE_ADJUSTED_AMOUNT, LINE_ADJUSTED_PERCENT, LINE_QUOTE_PRICE — pricing context and amounts.
• INVOICE_TO_PARTY_ID, INVOICE_TO_PARTY_SITE_ID — customer and site references.
• ORDER_LINE_TYPE_ID, BACKORDER_FLAG, SPLIT_SHIPMENT_FLAG — fulfillment attributes.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard DFF/context flexfield columns.
• Standard WHO/audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, plus concurrent program columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Relationship columns (sourced from ASO_LINE_RELATIONSHIPS and disambiguated with an R prefix where names would otherwise collide) include LINE_RELATIONSHIP_ID, RELATED_QUOTE_LINE_ID, RELATIONSHIP_TYPE_CODE, RECIPROCAL_FLAG, and the R-prefixed audit columns.

Common Use Cases and Queries

Typical uses include extracting quote lines for customer-facing or pricing analysis, reconciling quote lines to their pricing adjustments, and identifying configured items and their related-line relationships. A simple extract restricted to a header:

• SELECT QUOTE_LINE_ID, LINE_NUMBER, INVENTORY_ITEM_ID, QUANTITY, LINE_QUOTE_PRICE FROM IBE_ORDER_QUOTE_LINE_V WHERE QUOTE_HEADER_ID = :p_header_id ORDER BY LINE_NUMBER;
• Relationship-aware query: SELECT QUOTE_LINE_ID, RELATED_QUOTE_LINE_ID, RELATIONSHIP_TYPE_CODE FROM IBE_ORDER_QUOTE_LINE_V WHERE RELATED_QUOTE_LINE_ID IS NOT NULL;
• Operating-unit scoped reporting: SELECT ORG_ID, COUNT(*), SUM(LINE_QUOTE_PRICE) FROM IBE_ORDER_QUOTE_LINE_V GROUP BY ORG_ID;

Because the view is read-only and not physically materialized, queries should be scoped by ORG_ID or QUOTE_HEADER_ID where possible to limit scans of the base ASO tables.