Results for “aso_pvt_quote_lines_v”

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

Overview

ASO_PVT_QUOTE_LINES_V is a PL/SQL-visible, private view owned by the APPS schema within the ASO - Order Capture module of Oracle E-Business Suite. It exposes quote line information held in the Order Capture data model, joining the ASO_QUOTE_LINES detail records with supporting descriptive and cross-referenced data before presenting a flattened row per quote line. Because the object is declared private (_PVT_), it is intended primarily for internal consumption by ASO quoting APIs, forms, and related business logic rather than as a standalone public reporting interface. It is frequently used to feed quote-to-order conversion routines, price list validation, and customer-facing quote rendering. The view is valid in both EBS 12.1.1 and 12.2.2 and inherits the multi-org security model through the ORG_ID column, making it relevant to implementations that need line-level quote visibility across operating units.

Underlying Base Objects

The view is defined over several base objects. The core line records originate from ASO_QUOTE_LINES (synonym), with additional line detail attributes drawn from ASO_QUOTE_LINE_DETAILS (synonym). Lookup meanings for item type are sourced from ASO_LOOKUPS (view). Price list context is resolved through ASO_I_PRICE_LISTS_V (view) and the QP_PRICE_LIST_PVT package. Product master data comes from MTL_SYSTEM_ITEMS_VL (view). Customer and party data is joined from HZ_PARTIES, HZ_PARTY_SITES, HZ_CUST_ACCOUNTS, HZ_LOCATIONS, HZ_RELATIONSHIPS, and FND_TERRITORIES_VL (view). Together these objects support resolution of the invoice-to party, ship-to information, and the item/price metadata associated with each quote line.

Key Columns

• QUOTE_LINE_ID, QUOTE_HEADER_ID — primary and foreign keys linking the line to its quote header.
• ORG_ID — the operating unit owning the line; enforces multi-org access.
• LINE_NUMBER, LINE_CATEGORY_CODE, ITEM_TYPE_CODE, ITEM_TYPE — line sequencing and classification, with ITEM_TYPE decoded via ASO_LOOKUPS.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, UOM_CODE, QUANTITY — the item and quantity being quoted.
• PRICE_LIST_ID, PRICE_LIST_NAME, PRICE_LIST_LINE_ID, CURRENCY_CODE — pricing context for the line.
• LINE_LIST_PRICE, LINE_ADJUSTED_AMOUNT, LINE_ADJUSTED_PERCENT, LINE_QUOTE_PRICE — pricing and adjustment values.
• ACCOUNTING_RULE_ID, INVOICING_RULE_ID, SPLIT_SHIPMENT_FLAG, BACKORDER_FLAG — fulfillment and billing configuration.
• QUOTE_LINE_DETAIL_ID and service cotermination attributes from ASO_QUOTE_LINE_DETAILS.

The user-searched term invoice_to_party_name is not represented as a literal column name in the metadata, but the invoice-to party is derived through the HZ party/account objects referenced by the view; the closest exposed identifiers are the HZ party and customer account keys that consumers join back to HZ_PARTIES to obtain the party name.

Common Use Cases and Queries

Typical uses include retrieving quote lines for a given header, validating price list assignment, and resolving the invoicing party for a quote. A representative query joining back to HZ for the invoice-to party name is shown below.

• Quote line extraction for a specific header:

SELECT ql.quote_line_id,
       ql.line_number,
       ql.item_type,
       ql.quantity,
       ql.uom_code,
       ql.line_quote_price,
       ql.currency_code
FROM   apps.aso_pvt_quote_lines_v ql
WHERE  ql.quote_header_id = :p_header_id
AND    ql.org_id = :p_org_id
ORDER BY ql.line_number;

• Resolving the invoice-to party name through HZ:

SELECT ql.quote_header_id,
       ql.quote_line_id,
       hp.party_name AS invoice_to_party_name
FROM   apps.aso_pvt_quote_lines_v ql,
       apps.hz_cust_accounts     ca,
       apps.hz_parties           hp
WHERE  ql.quote_header_id = :p_header_id
AND    ca.cust_account_id = hp.party_id
AND    hp.party_id = ca.party_id;

Because the view is private, direct dependency from custom code should be treated cautiously; for supported reporting, wrap the view in a customer-owned database object or join it with ASO public views to insulate integrations from internal changes across the 12.1.1 and 12.2.2 code lines.