Results for “buyer_last_name”

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

Overview

PO_RFQ_HEADERS_PRINT is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. Its documented purpose is to provide a print-oriented projection of Request for Quotation (RFQ) header data. Unlike the transactional tables that store RFQ definitions, this view denormalizes header, supplier, site, contact, agent, terms, and lookup information into a single flat result set intended for formatted output — typically a BI Publisher or concurrent-program report that renders printed RFQ documents for distribution to suppliers.

The view is relevant in both 12.1.1 and 12.2.2. In 12.2.2 it retains the same APPS owner and VALID status; the primary difference across releases is the underlying multi-org and security plumbing exposed through the referenced packages (FND_GLOBAL, FND_PROFILE, HR_GENERAL, HR_SECURITY). The view is not a public API and should be treated strictly as a read-only reporting object. Because it filters on print flags and header status, it returns only RFQs currently eligible for printing, not the entire RFQ population.

Underlying Base Objects

The view joins a fixed set of documented base objects. PO_HEADERS supplies the RFQ header itself (segment1, revision, dates, notes, attributes). PO_RFQ_VENDORS links each RFQ to its invited suppliers and carries the print flag and sequence number that drive filtering and ordering. Supplier master data is drawn from PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS, providing names, addresses, phone numbers, and contact details. HR_LOCATIONS appears twice (aliased HR1 and HR2) to resolve bill-to and ship-to addresses, while HR_EMPLOYEES supplies the buyer/agent name. AP_TERMS supplies payment terms; PO_LOOKUP_CODES resolves ship-via and reply-method display values. Supporting packages and synonyms include FND_GLOBAL, FND_PROFILE, FND_LOOKUP_VALUES, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and AP_TERMS.

The join is driven by PRV.PRINT_FLAG = 'Y' and POH.STATUS_LOOKUP_CODE IN ('A','P'), so only active or approved RFQs flagged for printing are returned. Supplier site joins are constrained by ORG_ID to honor the operating unit of the header.

Key Columns

• SEGMENT1, REVISION_NUM, PO_HEADER_ID, ORG_ID — RFQ identity and operating unit.
• RFQ_CLOSE_DATE, REPLY_DATE, START_DATE, END_DATE — key RFQ lifecycle dates.
• NOTE_TO_VENDOR — the header-level instruction text printed on the RFQ.
• VENDOR_NAME, VENDOR_SITE segment1, CUSTOMER_NUM — supplier identification.
• ADDRESS_LINE1/2/3, CITY, STATE, ZIP, COUNTRY — supplier site address used for the "To" block.
• HR1.POSTAL_CODE, HR2.POSTAL_CODE, TOWN_OR_CITY — bill-to and ship-to address details; these correspond to the postal-code values users locate when searching for vendor_postal_code-style fields.
• FIRST_NAME, LAST_NAME (agent) — the buyer responsible for the RFQ.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield context captured for the header.
• CURRENCY_CODE, PRINTED_DATE, SEQUENCE_NUM, LANGUAGE — print and localization context.

Common Use Cases and Queries

The primary use case is a concurrent or BI Publisher report that prints RFQ documents per supplier. A secondary use is ad-hoc extraction for audit or reconciliation of which RFQs and supplier sites were sent.

Example — list printable RFQs with supplier address and postal code:

• SELECT r.segment1, r.revision_num, r.vendor_name, r.address_line1, r.city, r.zip FROM po_rfq_headers_print r WHERE r.org_id = :p_org_id ORDER BY r.segment1, r.sequence_num;

Example — retrieve header details for a single PO_HEADER_ID for reproduction:

• SELECT * FROM po_rfq_headers_print WHERE po_header_id = :p_po_header_id AND org_id = :p_org_id;

Because the view is owner APPS and restricts rows via the RFQ print flag, callers expecting all RFQs should query PO_HEADERS or PO_RFQ_VENDORS directly instead.