Results for “as_quotes_v”

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

Overview

AS_QUOTES_V is a quotations view belonging to the AS – Sales Foundation product family in Oracle E-Business Suite. It presents header-level quotation information maintained by Oracle Sales, exposing the attributes that describe a sales quotation: its identity (quote number and name), the customer and contact it is addressed to, pricing and currency context, status, validity dates, and a broad set of order-entry attributes carried on the quote header. As a view over the AS_QUOTES base table, it provides a reporting- and integration-friendly projection of quotation data without requiring consumers to reference the underlying table directly.

In EBS 12.1.1 and 12.2.2 the view serves as a read-only access point for quotation headers. Its utility in reporting and interfaces is that it consolidates quote identification, commercial terms, and order-related defaults into a single relational source that can be joined to customer, contact, employee (salesperson), and price list entities.

Underlying Base Objects

The view text is defined over AS_QUOTES, selecting the base table's columns directly. The first projected expression is AS_QUOTES.ROWID ROW_ID, which supplies a stable row identifier for the quotation record. The remaining columns are a straight projection of AS_QUOTES attributes with no documented joins, aggregations, or filters; consequently the view returns one row per quotation header row stored in AS_QUOTES.

The ETRM metadata notes that the view is not implemented in this database and lists no referenced base objects in its documented view metadata. This indicates that the view definition is shipped as part of the Sales Foundation schema, but may not be deployed in every environment; its presence should be verified against ALL_VIEWS before being relied upon in a report or interface.

Key Columns

• QUOTE_ID, QUOTE_NUMBER, QUOTE_NAME, QUOTE_VERSION – primary identity and versioning attributes of the quotation.
• EMPLOYEE_PERSON_ID – the salesperson (resource) associated with the quote; this is the column that drives resolution of the sales representative's surname, typically through a join to the employee/person tables rather than a SALESREP_LAST_NAME column on the view itself.
• CUSTOMER_ID, CONTACT_ID, ADDRESS_ID – the customer account, contact, and address for the quotation.
• QUOTE_STATUS, QUOTE_START_DATE, QUOTE_END_DATE – lifecycle state and validity window.
• CURRENCY_CODE, EXCHANGE_RATE, EXCHANGE_TYPE_CODE, EXCHANGE_RATE_DATE – currency and conversion context.
• TOTAL_QUOTE_PRICE, TOTAL_LIST_PRICE, TOTAL_DISCOUNT_AMOUNT, TOTAL_DISCOUNT_PERCENT, TOTAL_TAX – monetary totals for the quote.
• PRICE_LIST_ID, DISCOUNT_ID, DISCOUNT_MTHD_CODE, AGREEMENT_ID, PAYMENT_TERM_ID – pricing, agreement, and payment references.
• SHIP_TO_*, INVOICE_TO_* – ship-to and invoice-to site use and contact references.
• ORIGINAL_QUOTE_ID, LEAD_ID, PROMOTION_ID – lineage and demand-generation references.
• ATTRIBUTE_CATEGORY and descriptive flexfield columns – extensibility attributes.

The view also exposes standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent request columns for auditing.

Common Use Cases and Queries

Typical usages include quotation registers, open-quote aging, salesperson performance summaries, and extract interfaces into downstream order capture. Because the view does not carry the salesperson's surname, a query for that attribute must join EMPLOYEE_PERSON_ID to the appropriate person/employee tables.

• Listing active quotations with customer and totals.
• Summarising quote value by salesperson.
• Feeding quotation data into integration or data-warehouse loads.

Illustrative SQL:

• SELECT quote_number, quote_name, quote_status, total_quote_price FROM as_quotes_v WHERE quote_status = 'ACTIVE';
• SELECT q.quote_number, p.last_name, q.total_quote_price FROM as_quotes_v q, per_all_people_f p WHERE p.person_id = q.employee_person_id AND SYSDATE BETWEEN p.effective_start_date AND p.effective_end_date;