Search Results quote_vendor_quote_number




Overview
Explore in AI Chat

Overview

PO_CATALOG_QUOTES_ALL_V is a catalog quote view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is delivered as part of the PO - Purchasing product family and carries a VALID status in the ETRM repository. The view is flagged "10SC ONLY" in the source documentation, indicating that it is a narrowly scoped component rather than a general-purpose purchasing interface. Functionally, it exposes a filtered projection of purchasing document headers, restricted exclusively to records whose TYPE_LOOKUP_CODE equals 'QUOTATION'. This restriction means the view answers a single business question: which purchasing documents are quotations? Because quotations serve as the origin of catalog sourcing and supplier bid negotiation, this view is most commonly consumed by reporting layers, custom concurrent programs, and integration touchpoints that need a compact list of quotation headers without the full breadth of the PO_HEADERS table.

Underlying Base Objects

The view is defined over a single referenced base object, PO_HEADERS, accessed through a synonym in the APPS schema. The defining query is intentionally simple: it selects SEGMENT1, CREATION_DATE, QUOTE_VENDOR_QUOTE_NUMBER, PO_HEADER_ID, and ORG_ID from PO_HEADERS, applying the predicate TYPE_LOOKUP_CODE = 'QUOTATION'. Because the filter is embedded in the view definition, every query against PO_CATALOG_QUOTES_ALL_V automatically inherits the quotation restriction; consumers cannot accidentally retrieve standard purchase orders, blanket agreements, or contracts through this view. No joins, unions, or aggregation are present, so the view behaves as a virtual subset of PO_HEADERS with column pruning. This makes it inexpensive to query but also means it offers no attributes beyond those five columns.

Key Columns

  • PO_HEADER_ID — The primary key of the underlying PO_HEADERS row. This is the join key used when the view must be linked back to PO_HEADERS, PO_LINES, or any other purchasing table.
  • SEGMENT1 — The document number of the quotation as displayed to users and printed on the quotation document.
  • QUOTE_VENDOR_QUOTE_NUMBER — The supplier's own quotation reference number. This is the column most often targeted by user searches, since buyers commonly trace a supplier's quoted reference back to the internal purchasing document. The column name is often searched as "quote_vendor_quote_number".
  • CREATION_DATE — The date on which the quotation header record was created, useful for aging, cutoff, and audit reporting.
  • ORG_ID — The operating unit identifier, enabling multi-org aware filtering when the view is queried in a Multi-Org Access Control (MOAC) context. Reporting queries should constrain ORG_ID to avoid cross-operating-unit data leakage.

Common Use Cases and Queries

The principal use case is locating a quotation by the supplier's quoted reference. A typical lookup returns the internal document number and creation date for a given vendor quote number:

  • SELECT po_header_id, segment1, quote_vendor_quote_number, creation_date FROM po_catalog_quotes_all_v WHERE quote_vendor_quote_number = :p_vendor_quote_number;
  • SELECT segment1, quote_vendor_quote_number FROM po_catalog_quotes_all_v WHERE org_id = :p_org_id AND creation_date >= :p_from_date;
  • SELECT c.segment1 AS quotation_number, c.quote_vendor_quote_number, h.vendor_id FROM po_catalog_quotes_all_v c, po_headers h WHERE c.po_header_id = h.po_header_id;

Because the view is a straight projection with no aggregation, it is safe to join to PO_HEADERS on PO_HEADER_ID to obtain vendor, currency, status, and other header attributes that the view intentionally omits. Integrations that extract quotation data for external catalog systems or spend analysis frequently use this view as an efficient entry point, then enrich the extract through the header join. When the requirement extends beyond quotation headers — for example, to quotation lines or price breaks — the view is insufficient and PO_HEADERS combined with PO_LINES must be queried directly. Consumers should also note the "10SC ONLY" designation and confirm applicability against their specific 12.1.1 or 12.2.2 implementation before depending on the view in production.