Search Results rfq_document_number




Overview
Explore in AI Chat

Overview

APPS.POBV_RFQ_SUPPLIERS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema. It exposes supplier assignments for Requests for Quotation (RFQs) held within Oracle Purchasing. As the ETRM metadata states, the view "shows suppliers assigned to requests for quotation," and because a single RFQ may be distributed to multiple vendors, the relationship between an RFQ and its suppliers is one-to-many. Each row of the view therefore represents a distinct RFQ-to-supplier assignment.

Because the view is registered as FND Design Data under the PO application (PO.POBV_RFQ_SUPPLIERS), it is a supported, dictionary-registered object rather than an ad hoc query. This makes it suitable for custom reports, Oracle Discoverer workbooks, Oracle BI Publisher data templates, and integration extracts where purchasing users need a flattened, read-only picture of RFQ sourcing activity. The view is read-only and does not support DML; inserts, updates, and deletes against RFQ supplier assignments must be performed through the base purchasing tables or the Oracle Purchasing forms.

The column the user searched for, RFQ_DOCUMENT_NUMBER, is the human-readable RFQ identifier and functions as the principal join key between this view and other RFQ-related views and tables. In Oracle EBS 12.1.1 and 12.2.2 the object is reported as VALID.

Underlying Base Objects

The ETRM dependency information documents that POBV_RFQ_SUPPLIERS references the following base objects:

  • PO_HEADERS_ALL — the purchasing document header table. It supplies the RFQ header attributes, including the document number and operating unit context, for documents of type RFQ.
  • PO_RFQ_VENDORS — the RFQ supplier assignment table. It provides the supplier, supplier site, supplier contact, sequence, and print-tracking attributes for each vendor invited to quote.
  • HR_ALL_ORGANIZATION_UNITS — the organization definition table, used to resolve the operating unit identifier into a descriptive operating unit name.

These base objects are referenced through APPS synonyms. The view performs the join between the RFQ header and its supplier lines, then resolves the operating unit name via HR_ALL_ORGANIZATION_UNITS. The ETRM documentation also notes that POBV_RFQ_SUPPLIERS is not referenced by any other database object, confirming its role as a terminal reporting layer rather than a building block for further views.

Key Columns

Common Use Cases and Queries

Typical uses include listing all suppliers invited against a given RFQ, auditing RFQ distribution and reprint activity, and feeding supplier participation data into sourcing or spend analysis. To retrieve all suppliers for a specific RFQ document number:

  • SELECT rfq_document_number, supplier_id, supplier_site_id, supplier_contact_id, sequence_number, print_count FROM apps.pobv_rfq_suppliers WHERE rfq_document_number = :p_rfq_number;
  • Count invited suppliers per RFQ: SELECT rfq_document_number, COUNT(*) FROM apps.pobv_rfq_suppliers GROUP BY rfq_document_number;
  • Report unprinted or low-print RFQs: SELECT rfq_document_number, last_printed_date, print_count FROM apps.pobv_rfq_suppliers WHERE last_printed_date IS NULL;

Because the view carries no operating unit security predicate by default, custom reports should filter or secure by OPERATING_UNIT_ID to respect multi-org access controls.