Search Results po_rfq_vendors




Overview
Explore in AI Chat

Overview

The PO_RFQ_VENDORS table is a core transactional entity within the Oracle E-Business Suite Purchasing (PO) module. It serves as the definitive repository for storing the list of suppliers invited to respond to a specific Request for Quotation (RFQ). An RFQ is a formal solicitation document used to obtain price and delivery terms from potential suppliers for goods or services. This table is essential for managing the competitive bidding process, as it maintains the relationship between the RFQ document (header) and each invited vendor, along with their specific contact and site details. Its integrity is enforced by a primary key and multiple foreign key relationships to master data tables, ensuring referential consistency across the procurement system.

Key Information Stored

The table's structure is designed to capture the essential details of each invited vendor for an RFQ. The primary key is a composite of PO_HEADER_ID and SEQUENCE_NUM, uniquely identifying each vendor record within a specific RFQ. Key columns include PO_HEADER_ID, which links to the parent RFQ document in PO_HEADERS_ALL, and SEQUENCE_NUM, which orders the vendors. The VENDOR_ID column references the master supplier record in PO_VENDORS. To specify the exact location and point of contact for the RFQ, the table stores VENDOR_SITE_ID (linking to PO_VENDOR_SITES_ALL) and VENDOR_CONTACT_ID (linking to PO_VENDOR_CONTACTS). Additional columns, not detailed in the excerpt but typical for such a table, would track the status of the vendor's response and other transactional flags.

Common Use Cases and Queries

This table is central to reporting and process management for RFQs. Common use cases include generating a vendor list for a specific RFQ to track invitation status, analyzing supplier participation history, and auditing the competitive bidding process. A typical query would join PO_RFQ_VENDORS with PO_HEADERS_ALL and PO_VENDORS to produce a report of all RFQs and their invited suppliers. For example:

  • Identifying all vendors invited to a particular RFQ: SELECT v.vendor_name, prv.* FROM po_rfq_vendors prv, po_vendors v WHERE prv.vendor_id = v.vendor_id AND prv.po_header_id = <RFQ_ID>;
  • Finding all RFQs where a specific vendor was invited: SELECT ph.segment1 AS rfq_number FROM po_rfq_vendors prv, po_headers_all ph WHERE prv.po_header_id = ph.po_header_id AND prv.vendor_id = <VENDOR_ID>;

Data from this table is also critical for the system's automatic creation of quotations from vendor responses.

Related Objects

As indicated by its foreign keys, PO_RFQ_VENDORS has strong dependencies on several master and transactional tables. Its primary relationship is with PO_HEADERS_ALL, the parent RFQ document. For vendor master data, it references PO_VENDORS. For location and contact specifics, it relies on PO_VENDOR_SITES_ALL and PO_VENDOR_CONTACTS, respectively. This table is also a likely parent to other transactional tables that store the detailed line-level responses from each vendor. In application logic, it is accessed and maintained by the standard Purchasing APIs and forms, particularly during the RFQ creation and vendor invitation processes.