Search Results aso_quote_headers_v




Overview
Explore in AI Chat

Overview

The APPS.ASO_QUOTE_HEADERS_V view is a denormalized reporting interface over the Oracle Order Capture (ASO) quotations data model. It consolidates quote header attributes from ASO_QUOTE_HEADERS with descriptive references from Oracle Pricing, Trading Community Architecture (TCA), and resource management, exposing them through a single queryable object. Its principal purpose is to support reporting, Oracle Discoverer workbooks, BI Publisher data models, and integration extracts where quote header information is required without joining the underlying transactional tables directly. Because the view joins validated TCA and pricing entities, it provides human-readable values — status meanings, price list names, party names — alongside the internal identifier columns needed for drill-down.

Underlying Base Objects

The view is defined in the APPS schema and is documented as referencing a broad set of base objects. Transactional header data originates from ASO_QUOTE_HEADERS. Status information is resolved through ASO_QUOTE_STATUSES_B and ASO_QUOTE_STATUSES_TL, which supply the status code, meaning, update-allowed flag, and auto-version flag. Customer and contact attributes are sourced from the TCA family: HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_ORG_CONTACTS, HZ_CONTACT_POINTS, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_RELATIONSHIPS, with ASO_I_PARTIES_V acting as the party abstraction layer. Price list references come from QP_LIST_HEADERS_B and QP_LIST_HEADERS_TL. Sales representative assignment draws on JTF_RS_SALESREPS, while currency, territory, sales credit type, and transaction type descriptions are resolved through FND_CURRENCIES, FND_TERRITORIES, FND_TERRITORIES_TL, OE_SALES_CREDIT_TYPES, OE_TRANSACTION_TYPES_ALL, and OE_TRANSACTION_TYPES_TL. The ASO_SHIPMENT_PVT package is also referenced, primarily to supply shipment-related computed attributes.

Key Columns

Common Use Cases and Queries

The most frequent use case is quote pipeline and win/loss reporting filtered by operating unit and status. Because SALESREP_FULL_NAME is exposed directly, users searching for that term typically retrieve the representative name alongside the quote without joining JTF_RS_SALESREPS manually.

Sample query listing quotes with representative, customer, and status:

  • SELECT quote_header_id, quote_number, quote_status, salesrep_full_name, organization_name, person_last_name, price_list_name, creation_date FROM aso_quote_headers_v WHERE org_id = :p_org_id AND quote_status_code = 'OPEN' ORDER BY creation_date DESC;

Additional scenarios include extracting converted quotes by filtering on ORDER_ID for integration with downstream order systems, and aggregating quote counts by sales representative using SALESREP_FULL_NAME as the grouping attribute. Reporting on price list usage and status aging is also common. Because the view references TCA and multi-org columns, queries should always constrain ORG_ID and be validated against the MOAC security profile in use. For 12.1.1 and 12.2.2, the view definition and dependencies are consistent; the primary variation is the underlying TCA table versions, which remain API-stable across both releases.