Search Results quote_vendor_quote_number




Overview
Explore in AI Chat

Overview

APPS.PO_CATALOG_QUOTES_ALL_V is a reporting view in the Oracle E-Business Suite Purchasing module that exposes supplier catalog quotation headers. In Oracle Purchasing, a catalog quotation is a purchasing document used to record supplier pricing and availability for goods, typically as a precursor to negotiation or as a reference for sourcing decisions. The view isolates quotation-type documents by filtering PO_HEADERS on TYPE_LOOKUP_CODE = 'QUOTATION', providing a narrow, purpose-built projection of quotation header data rather than the full breadth of the PO_HEADERS record.

The "_ALL" suffix indicates the view is not restricted to a single operating unit through row-level security in the manner of many operational views; it presents quotation records across the organizations visible in the underlying data. The presence of ORG_ID among the selected columns reinforces that quotations are organization-specific and that consumers of the view are expected to filter or group by operating unit as required. The view is owned by APPS and is intended for read-only reporting and integration scenarios rather than transactional processing.

Underlying Base Objects

The view is defined over a single base object, PO_HEADERS, referenced through a synonym. PO_HEADERS is the central header table of the Purchasing schema and stores the common attributes shared by all document types — requisitions converted to orders, purchase orders, RFQs, and quotations — with TYPE_LOOKUP_CODE distinguishing them. Because the view selects only from PO_HEADERS, it inherits no distribution, line, or shipment detail; it is strictly a header-level projection. The defining predicate TYPE_LOOKUP_CODE = 'QUOTATION' means the view returns only quotation documents and excludes standard purchase orders and other document types stored in the same table.

Since the view is a simple filtered select against PO_HEADERS, it is a non-updatable, read-only construct. No joins, aggregations, or analytic functions are applied, so query performance is governed entirely by the access path chosen for PO_HEADERS, typically an index on document type or organization combined with organization and type filters.

Key Columns

  • SEGMENT1 — The document number of the quotation. This is the human-readable identifier presented to users and is the field most commonly correlated with search terms such as "quote_vendor_quote_number."
  • QUOTE_VENDOR_QUOTE_NUMBER — The supplier's own reference or quote number associated with the quotation. This column supports the business need to trace an EBS quotation back to the vendor's originating quote document, and it is frequently used as a search or matching key in integrations and reports.
  • PO_HEADER_ID — The unique internal identifier of the header record in PO_HEADERS. This is the primary key used to join the view to quotation lines, shipments, distributions, and other dependent tables that are not exposed here.
  • ORG_ID — The operating unit (organization) that owns the quotation. Because multiple operating units share PO_HEADERS, this column is essential for scoping results correctly.
  • CREATION_DATE — The date the quotation header record was created, useful for aging, audit, and date-bounded reporting.

Common Use Cases and Queries

Typical uses include listing all quotations for an operating unit, retrieving a quotation by its document number, and locating a quotation using the supplier's own quote reference. The latter is the most direct response to a search on "quote_vendor_quote_number."

  • List recent quotations for an organization:
    SELECT segment1, quote_vendor_quote_number, creation_date FROM apps.po_catalog_quotes_all_v WHERE org_id = :org_id ORDER BY creation_date DESC;
  • Find a quotation by vendor quote number:
    SELECT segment1, po_header_id, org_id FROM apps.po_catalog_quotes_all_v WHERE quote_vendor_quote_number = :vendor_quote_number;
  • Join to header detail for extended attributes:
    SELECT v.segment1, v.quote_vendor_quote_number, h.vendor_id, h.vendor_site_id FROM apps.po_catalog_quotes_all_v v, apps.po_headers h WHERE v.po_header_id = h.po_header_id;

Because the view surfaces the PO_HEADER_ID, it serves as a convenient entry point into the wider Purchasing data model whenever users need quotation lines, price breaks, or supplier terms. Reports and interfaces should always constrain by ORG_ID to avoid cross-operating-unit results.