Results for “po_rfq_vendors”

50+ results




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

Overview

PO_RFQ_VENDORS is a Purchasing (PO) module table in the Oracle E-Business Suite database, owned by the PO schema and documented as VALID in both 12.1.1 and 12.2.2. Its documented purpose is to hold the suppliers on a Request for Quotation (RFQ). Each row represents one supplier invited to respond to a given RFQ header, making the table the association between an RFQ and the trading partners from whom quotations are solicited.

In Data Vault modeling terms, the heuristic classification mined from its foreign key structure is a link table. It resolves a many-to-many relationship between RFQ headers and suppliers, and it carries descriptive satellite-style attributes such as print status and a standard EBS attribute flexfield. This classification is a modeling suggestion only; functionally the table is a dependent child of PO_HEADERS_ALL.

Key Information Stored

The documented physical schema contains 33 columns. The most significant are:

The documented unique index PO_RFQ_VENDORS_U1 (PO_HEADER_ID, SEQUENCE_NUM), also listed as the primary key constraint PO_RFQ_VENDORS_UK1, is the business-key candidate. No separate single-column surrogate key is documented.

Common Use Cases and Queries

Typical uses include listing the suppliers invited to each RFQ, locating a supplier's RFQ response record, auditing print history, and reporting RFQ distribution by supplier site or contact.

A common query joins the table back to its parent header and supplier master:

  • SELECT rv.po_header_id, rv.sequence_num, rv.vendor_id, rv.vendor_site_id, rv.vendor_contact_id, rv.print_flag, rv.print_count FROM po.po_rfq_vendors rv WHERE rv.po_header_id = :p_header_id ORDER BY rv.sequence_num;
  • To resolve supplier and site names, join rv.vendor_id = pv.vendor_id and rv.vendor_site_id = pvs.vendor_site_id.
  • To report outstanding invitations, filter on PRINT_FLAG or PRINT_COUNT to identify suppliers not yet sent the RFQ.

Because PO_HEADER_ID and SEQUENCE_NUM form the unique key, queries should always constrain or order on these columns for predictable results.

Related Objects

The following objects are the most significant references, based on the documented foreign keys:

  • PO_HEADERS_ALL — the parent RFQ header; joined on PO_RFQ_VENDORS.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID.
  • PO_VENDORS — the supplier master; joined on VENDOR_ID.
  • PO_VENDOR_SITES_ALL — supplier sites; joined on VENDOR_SITE_ID.
  • PO_VENDOR_CONTACTS — supplier contacts; joined on VENDOR_CONTACT_ID.
  • PO_RFQ_VENDOR_LISTS and related RFQ quotation tables (e.g., PO_QUOTATIONS) — dependent RFQ supplier/quotation data commonly accessed alongside this table.
  • PO_RFQ_VENDORS_UK1 / PO_RFQ_VENDORS_U1 — the documented unique index and constraint enforcing uniqueness of PO_HEADER_ID and SEQUENCE_NUM.

These relationships make PO_RFQ_VENDORS a central link between RFQ headers and the supplier master for sourcing and quotation reporting.