Search Results reply_method_lookup_code

Overview

The view POS_PO_RFQ_HEADERS_V is owned by the APPS schema and belongs to the iSupplier Portal (POS) product family in Oracle E-Business Suite. Its documented purpose is to display Request for Quotation (RFQ) header information — the supplier-facing header records that underpin the sourcing and quotation cycle. In EBS 12.1.1 and 12.2.2 the view is a VALID object and is commonly consumed by iSupplier Portal pages, sourcing dashboards, and custom reports that need a denormalized, supplier-enriched projection of RFQ headers without joining the full underlying table set manually.

Because the view joins header data to vendor, contact, site, currency, terms, and organization attributes, it delivers a single-row-per-RFQ picture suitable for read-only reporting and integration extracts. The user search term reply_date is exposed directly by the view: REPLY_DATE reflects the date by which suppliers are expected to respond to the RFQ, and it is one of the most frequently queried header attributes alongside RFQ_CLOSE_DATE and QUOTE_WARNING_DELAY.

Underlying Base Objects

The view text selects from PO_HEADERS_ALL (POH) as the driving table, since RFQ headers are stored in the same headers table as purchase orders and distinguished by TYPE_LOOKUP_CODE. It is joined to the following documented base objects:

• PO_RFQ_VENDORS (RFQV) — associates the RFQ with invited suppliers.
• PO_VENDORS (POV) and PO_VENDOR_SITES_ALL (PVS) — supply vendor name and site code.
• PO_VENDOR_CONTACTS (PVC) — supplies the vendor contact name.
• PER_ALL_PEOPLE_F (PPF) — resolves the buyer (AGENT_ID) to a full name.
• PO_DOCUMENT_TYPES_ALL_VL (PDT), PO_LOOKUP_CODES (POLC), and GL_DAILY_CONVERSION_TYPES (GLC) — resolve type, displayed-field, and conversion-type descriptions.
• HR_LOCATIONS_ALL (HRL1/HRL2), HR_ALL_ORGANIZATION_UNITS_TL (HOU), and AP_TERMS (APT) — resolve ship-to/bill-to locations, operating unit name, and payment terms.

The SELECT DISTINCT clause suppresses duplicates introduced by the vendor and site joins. The view also references FND_GLOBAL, which supplies session context such as ORG_ID for multi-org filtering.

Key Columns

• PO_HEADER_ID, SEGMENT1–SEGMENT5 — RFQ identifier and concatenated document number segments.
• REPLY_DATE, RFQ_CLOSE_DATE, START_DATE, END_DATE, QUOTE_WARNING_DELAY — key sourcing timeline attributes.
• REPLY_METHOD_LOOKUP_CODE, QUOTE_TYPE_LOOKUP_CODE, QUOTATION_CLASS_CODE — describe how and what suppliers may quote.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE, VENDOR_CONTACT_ID — supplier and contact identity.
• AGENT_ID and FULL_NAME — the buyer responsible for the RFQ.
• CURRENCY_CODE, RATE_TYPE, RATE_DATE, RATE — currency and conversion context.
• STATUS_LOOKUP_CODE, REVISION_NUM, SUMMARY_FLAG, ENABLED_FLAG — status and revision control.
• ORG_ID and the operating unit NAME — multi-org identification.

Common Use Cases and Queries

Typical usage includes monitoring RFQs approaching their reply deadline, extracting supplier invitation data for integration, and building buyer worklists.

• Upcoming reply deadlines:

  SELECT segment1, vendor_name, reply_date, rfq_close_date
  FROM   pos_po_rfq_headers_v
  WHERE  reply_date >= SYSDATE
  AND    org_id = :p_org_id
  ORDER BY reply_date;

• RFQs by buyer and status:

  SELECT segment1, full_name, status_lookup_code, reply_date
  FROM   pos_po_rfq_headers_v
  WHERE  agent_id = :p_agent_id;

• Supplier-facing extract: filter on vendor_id and enabled_flag = 'Y' to return the RFQs visible to a given supplier in iSupplier Portal.

Because the view is a reporting projection rather than a transactional entity, it should be queried read-only and filtered by ORG_ID to respect multi-org security.