Search Results aso_pvt_quote_lines_num_v




Overview

APPS.ASO_PVT_QUOTE_LINES_BALI_V is a reporting and integration view in the Oracle E-Business Suite Quote Management (ASO) module. It exposes quote line information enriched with the dynamically derived user-interface line number, presenting a flat, denormalized projection of quote line data suitable for concurrent programs, OBIEE/BIP reports, and interface extracts. Unlike the underlying transactional tables, which store raw configuration identifiers and internal flags, this view applies the ASO_LINE_NUM_INT package function to compute a human-readable UI_LINE_NUMBER, resolving line numbering references for both standard and configured or serviceable items.

The view is significant because the user search term "aso_pvt_quote_lines_num_v" indicates the caller is looking for a numeric variant. ASO_PVT_QUOTE_LINES_BALI_V references ASO_PVT_QUOTE_LINES_NUM_V internally, meaning it is the presentation layer that wraps and extends the numeric-line-numbering view with additional descriptive and pricing columns (currency code, price list, extended selling price, charge periodicity meaning, and so on). The "_BALI_" prefix typically denotes a "base line" or business-logic enriched variant.

Underlying Base Objects

Per documented ETRM 12.2.2 metadata, the view is defined over the following referenced base objects:

  • ASO_PVT_QUOTE_LINES_NUM_V (VIEW) — the immediate parent view supplying the core quote line columns and numeric line numbering logic.
  • ASO_LINE_NUM_INT (PACKAGE) — provides the ASO_QUOTE_LINE_NUMBER function invoked in the SELECT list; this function derives UI_LINE_NUMBER from the quote line ID and item/config attributes.
  • FND_PROFILE (PACKAGE) — supplies profile option values, typically for org or security context resolution.

Because the base object chain terminates in ASO quote line tables, this view inherits the standard ASO multi-org and MOAC security model through ORG_ID and SECURITY_GROUP_ID columns.

Key Columns

Important exposed columns include:

Common Use Cases and Queries

Typical scenarios include quote line extraction for reporting, reconciliation of extended selling prices, and interface feed generation.

  • Line-level quote report: SELECT UI_LINE_NUMBER, INVENTORY_ITEM, QUANTITY, UOM_CODE, LINE_QUOTE_PRICE, EXTENDED_SELLING_PRICE FROM ASO_PVT_QUOTE_LINES_BALI_V WHERE QUOTE_HEADER_ID = :p_header_id ORDER BY UI_LINE_NUMBER;
  • Multi-org filtered extraction: SELECT QUOTE_LINE_ID, ORG_ID, CURRENCY_CODE, EXTENDED_SELLING_PRICE FROM ASO_PVT_QUOTE_LINES_BALI_V WHERE ORG_ID = :p_org_id AND LAST_UPDATE_DATE >= :p_since;
  • Configured item inspection: SELECT UI_LINE_NUMBER, CONFIG_HEADER_ID, CONFIG_REVISION_NUM, ITEM_TYPE_CODE FROM ASO_PVT_QUOTE_LINES_BALI_V WHERE CONFIG_HEADER_ID IS NOT NULL;
  • Pricing reconciliation: Comparing LINE_LIST_PRICE, LINE_ADJUSTED_AMOUNT, and EXTENDED_SELLING_PRICE across lines.

Because UI_LINE_NUMBER is computed per row via a package function, queries returning large result sets may incur performance overhead; filtering by QUOTE_HEADER_ID or ORG_ID before ordering improves efficiency.