Search Results po_headers_xml




Overview

The APPS.PO_HEADERS_XML view is a denormalized, XML-oriented reporting view within the Oracle Purchasing (PO) module. It is defined in the APPS schema and holds VALID status in both Oracle E-Business Suite 12.1.1 and 12.2.2. The view presents a single, flattened record per purchasing document header, exposing the attributes most frequently required to render purchase orders, blanket purchase agreements, and contract documents in printed or electronic form. Its design reflects the requirements of the PO Communication/XML Publisher infrastructure: rather than joining the base purchasing tables at run time, the view encapsulates the joins and lookups, applies formatting, and surfaces business-friendly column aliases.

Because it delivers buyer details, vendor address information, currency, terms, freight and FOB references, and formatted dates and amounts in one row, PO_HEADERS_XML functions as the header-level data source for purchasing document templates and downstream integrations. It is typically consumed alongside a corresponding lines view to produce the complete document payload.

Underlying Base Objects

The view is defined primarily over the PO_HEADERS_ALL synonym, which supplies the document header columns. It joins to PER_ALL_PEOPLE_F to resolve the buyer's name and title, to AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL for vendor identification and address data, to AP_TERMS for payment terms, and to FND_CURRENCIES_TL for the currency name. Lookup semantics are resolved through FND_LOOKUP_VALUES, HR_LOOKUPS, FND_TERRITORIES_TL, and ORG_FREIGHT_TL. Supporting objects include PO_AGENTS, PO_VENDOR_CONTACTS, HZ_LOCATIONS, and PO_DOC_STYLE_LINES_TL.

Several values are not read directly from tables but are computed by the PO_COMMUNICATION_PVT package, including the archive buyer agent, name, and title, the amount format mask via GETFORMATMASK, and the string-to-number conversion of the blanked base amount. PACKAGE dependencies on PO_CORE_S, HR_API, and FND_GLOBAL indicate that the view participates in agent resolution, security context, and formatting logic. Reach-through joins to PO_VENDOR_CONTACTS and HZ_LOCATIONS account for the vendor contact and address fragments visible in the view text.

Key Columns

Common Use Cases and Queries

Typical consumers use the view to populate XML Publisher templates for PO printing, to drive supplier-facing document output, or to expose header data to integrations without reimplementing lookup joins.

  • Retrieve a document header by number: SELECT segment1, revision_num, vendor_name, currency_code, amount_agreed FROM apps.po_headers_xml WHERE segment1 = :po_number;
  • List open documents for a buyer: SELECT segment1, type_lookup_code, creation_date FROM apps.po_headers_xml WHERE document_buyer_agent_id = :agent_id AND cancel_flag = 'N';
  • Join to lines for a complete payload, keying on SEGMENT1 and REVISION_NUM.
  • Snapshot buyer and vendor detail at revision time using the ARCHIVE_BUYER_* columns for historical reprints.