Search Results document_buyer_agent_id




Overview
Explore in AI Chat

Overview

APPS.PO_HEADERS_PRINT is an Oracle E-Business Suite internal view owned by the APPS schema. It is registered in FND Design Data under the product short name PO as PO.PO_HEADERS_PRINT with a status of VALID. The view is classified as a "View Type: Internal" object and carries the standard Oracle warning that it is for Oracle Internal Use Only and that Oracle Corporation does not support access to Oracle applications data through this object except from standard Oracle Applications programs.

Functionally, PO_HEADERS_PRINT presents a flattened, denormalized projection of purchasing document header information specifically oriented toward document printing and rendering. Instead of forcing a printing program to join the purchasing header, vendor, vendor site, contact, currency, payment term, and buyer-person tables at runtime, the view exposes the resolved presentation values directly — vendor name and address lines, currency name and conversion rate, payment terms, ship-via, FOB, freight terms, and both the current and archived buyer names in separate first/last name columns. This design supports the Purchase Order Print and related printing/reporting flows, where the goal is to emit a human-readable document rather than to model normalized transactional data.

Underlying Base Objects

The documented dependency list for PO_HEADERS_PRINT in release 12.2.2 is broad and reflects the view's role as a presentation aggregator across several EBS schemas. The purchasing document core is sourced from PO_HEADERS, PO_HEADERS_ALL, and PO_HEADERS_ARCHIVE_ALL. Release header data is drawn from PO_RELEASES and PO_RELEASES_ARCHIVE_ALL. Vendor and contact presentation attributes come from PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS. Currency and territory display values come from FND_CURRENCIES_TL and FND_TERRITORIES_TL. Payment terms are sourced from AP_TERMS, and lookup display values from PO_LOOKUP_CODES.

The buyer-name columns are resolved through HR and PER objects: HR_EMPLOYEES, PER_PEOPLE_F, and the HR_PERSON_NAME, HR_GENERAL, and HR_SECURITY packages. Session and profile context — organization, user, and security predicates — is obtained through the FND_GLOBAL and FND_PROFILE packages. Because the view references the HR_SECURITY and FND_GLOBAL/FND_PROFILE constructs, the rows and values it returns are filtered by the effective MO/operating unit and security profile of the session, which is central to why Oracle treats it as an internal, supported-only-from-standard-programs object.

Key Columns

Document identity and lifecycle columns include PO_TYPE, PO_NUM, REVISION_NUM, PRINT_COUNT, PRINTED_DATE, REVISED_DATE, EFFECTIVE_DATE, and EXPIRATION_DATE, together with the standard WHO creation columns. NOTE_TO_VENDOR carries the vendor-facing note text.

The buyer identity, the focus of the user's search term "document_buyer_last_name", is exposed through three related columns: DOCUMENT_BUYER_FIRST_NAME and DOCUMENT_BUYER_LAST_NAME (both VARCHAR2(150)) with DOCUMENT_BUYER_AGENT_ID (NUMBER). Parallel columns ARCHIVE_BUYER_FIRST_NAME, ARCHIVE_BUYER_LAST_NAME, and ARCHIVE_BUYER_AGENT_ID hold the buyer captured against the archived record. Together these support change-history comparison between the current document buyer and the archived buyer on the printed output.

Commercial and delivery terms are exposed as CURRENCY_CODE, CURRENCY_NAME, CURRENCY_CONVERSION_RATE, SHIP_VIA, FOB, FREIGHT_TERMS, PAYMENT_TERMS, and AMOUNT_AGREED. Flags include CANCEL_FLAG, CONFIRMING_ORDER_FLAG, and ACCEPTANCE_REQUIRED_FLAG, alongside ACCEPTANCE_DUE_DATE. Vendor presentation columns include VENDOR_NUM, VENDOR_NAME, VENDOR_ADDRESS_LINE1 through LINE4, VENDOR_CITY, VENDOR_STATE, VENDOR_POSTAL_CODE, VENDOR_COUNTRY, VENDOR_PHONE, and the vendor contact name and phone fields. ATTRIBUTE1 through ATTRIBUTE5 expose descriptive flexfield segments.

Common Use Cases and Queries

The primary scenario is print/report retrieval of resolved header presentation values for a purchasing document. Because the view is internal and unsupported for direct customer access, queries are typically issued from within supported Oracle printing programs or during controlled diagnostics. A representative query is:

  • SELECT po_num, revision_num, document_buyer_last_name, document_buyer_first_name, vendor_name, currency_code FROM apps.po_headers_print WHERE po_type = :p_type AND po_num = :p_num AND revision_num = :p_rev;
  • SELECT po_num, document_buyer_last_name, archive_buyer_last_name FROM apps.po_headers_print WHERE document_buyer_last_name != archive_buyer_last_name; — used to identify documents whose buyer changed after archival.
  • SELECT po_num, vendor_name, payment_terms, ship_via, fob, freight_terms FROM apps.po_headers_print WHERE creation_date >= :p_from_date ORDER BY creation_date DESC; — for printing-oriented reporting over a date range.

When diagnosing buyer-name discrepancies, the DOCUMENT_BUYER_* and ARCHIVE_BUYER_* column pairs should be compared, and any resolution of the underlying person should be traced back to PER_PEOPLE_F/HR_EMPLOYEES rather than relied upon from the view alone, given the security and MO filtering applied through HR_SECURITY and FND_GLOBAL.