Search Results reply_method_lookup_code

Overview

The APPS.ICX_PO_RFQ_HEADERS_V view is a reporting and integration construct within Oracle iProcurement (ICX) that exposes Request for Quotation (RFQ) header information in a denormalized, business-friendly form. It is defined as a database view owned by the APPS schema and carries a VALID status in Oracle EBS 12.1.1 and 12.2.2. Unlike the transactional PO_HEADERS table, which stores RFQ data in raw, coded form, ICX_PO_RFQ_HEADERS_V resolves lookup codes into displayed values and joins in descriptive attributes from suppliers, sites, contacts, people, currencies, payment terms, and locations. This makes the view well suited for ad-hoc reporting, custom concurrent programs, Oracle XML Publisher data templates, and inbound or outbound interface scripts that need RFQ header context without reconstructing multi-table joins manually. Because the view is built on top of Oracle Purchasing base objects, it allows iProcurement and sourcing functionality to surface RFQ details that originate in the Purchasing module.

Underlying Base Objects

The view text draws primarily from PO_HEADERS (aliased POH), which supplies the RFQ header identity, status, currency, dates, terms, and the descriptive flexfield ATTRIBUTE1 through ATTRIBUTE15 columns. It also references PO_HEADERS again (aliased POH2) to resolve the originating document SEGMENT1 through FROM_HEADER_ID and FROM_TYPE_LOOKUP_CODE, supporting RFQ reference chains. Supplier information is sourced from PO_VENDORS and PO_VENDOR_SITES, while RFQ-to-vendor assignments come from PO_RFQ_VENDORS. Vendor contact details are resolved through PO_VENDOR_CONTACTS and PO_VENDOR_SITES. Employee and contact names are produced from PER_PEOPLE_F combined with HR_PERSON_NAME, while organizational security and location logic rely on HR_SECURITY, HR_GENERAL, and HR_LOCATIONS. Type, status, freight terms, ship-via, FOB, and quote type descriptions are resolved from PO_DOCUMENT_TYPES and PO_LOOKUP_CODES. Currency conversion details are provided by GL_DAILY_CONVERSION_TYPES and FND_GLOBAL, and payment terms come from AP_TERMS.

Key Columns

• PO_HEADER_ID / SEGMENT1 – Primary key of the RFQ header and its user-visible RFQ number.
• TYPE_LOOKUP_CODE / TYPE_NAME – Document type code and its descriptive name.
• STATUS_LOOKUP_CODE – Current RFQ lifecycle status (for example, active, closed, or cancelled).
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_SITE_CODE – Supplier and supplier site associated with the RFQ.
• VENDOR_CONTACT_ID and the derived LAST_NAME || ', ' || FIRST_NAME expression – the vendor contact person, which is the column most commonly targeted by users searching for vendor_contact. Note that the contact name is derived from POH.VENDOR_CONTACT_ID via DECODE against PO_VENDOR_CONTACTS, and may return NULL when no contact is assigned.
• AGENT_ID and FULL_NAME – The buyer or sourcing agent responsible for the RFQ.
• RFQ_CLOSE_DATE, REPLY_DATE, START_DATE, END_DATE – Key scheduling columns for quote deadlines and response windows.
• CURRENCY_CODE, RATE_TYPE, RATE_DATE, RATE – Currency and exchange rate context.
• SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID, LOCATION_CODE – Delivery and invoicing location identifiers and codes.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY – Descriptive flexfield values carried through from the header.

Common Use Cases and Queries

Typical uses include RFQ status reporting, vendor response tracking, sourcing cycle-time analysis, and integration extracts feeding external sourcing or e-procurement platforms. Because the view resolves lookup codes, it is frequently used as the source for BI Publisher reports that would otherwise require several lookup joins. A representative query retrieving RFQ headers with supplier and contact information follows:

SELECT po_header_id, segment1, type_name, status_lookup_code, vendor_name, vendor_site_code, vendor_contact_id, agent_id, full_name, rfq_close_date, currency_code FROM apps.icx_po_rfq_headers_v WHERE status_lookup_code = 'ACTIVE' ORDER BY rfq_close_date;

To isolate RFQs with an assigned vendor contact, filter on the derived contact column: SELECT segment1, vendor_name, vendor_contact_id FROM apps.icx_po_rfq_headers_v WHERE vendor_contact_id IS NOT NULL;

Analysts should note that the view applies no organization-level security predicate by itself in the excerpt provided; callers requiring operating unit or org isolation should join to PO_HEADERS or apply HR_SECURITY-aware conditions as appropriate for their deployment.