Search Results po_release_xml




Overview
Explore in AI Chat

Overview

PO_RELEASE_XML is a read-only view owned by the APPS schema within the Oracle Purchasing (PO) module. It is a denormalized, XML-oriented reporting object that consolidates the header-level attributes of a purchase order release — the blanket agreement or planned purchase order release — together with buyer, vendor, currency, shipping, and acceptance details. Unlike the transactional tables PO_RELEASES_ALL and PO_HEADERS_ALL, which store raw identifiers and foreign keys, PO_RELEASE_XML resolves those keys into human-readable values and formats dates and numeric masks so that the output can be consumed directly by XML document generation or by external integration layers. The view has no physical storage of its own; every access re-executes the defining SELECT statement against the underlying EBS tables and packages. In Oracle EBS 12.1.1 and 12.2.2 the object remains VALID and is part of the standard APPS dictionary. Its primary role is to supply the buyer and vendor information required when a release is communicated to a supplier, including revision-aware buyer details that differ for original versus revised releases.

Underlying Base Objects

PO_RELEASE_XML is defined over a documented set of base objects resolved through APPS synonyms and views. The principal source is PO_RELEASES_ALL, which supplies release-level attributes such as REVISION_NUM, PRINT_COUNT, CANCEL_FLAG, ACCEPTANCE_REQUIRED_FLAG, and the various date columns. PO_HEADERS_ALL contributes SEGMENT1 (the PO number), RATE, and SHIP_VIA_LOOKUP_CODE. Buyer information is joined from PER_ALL_PEOPLE_F and PO_AGENTS, with buyer agent resolution additionally handled by the PO_COMMUNICATION_PVT package. Vendor information is drawn from the PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS views. Currency and territory lookups come from FND_CURRENCIES_TL, FND_LOOKUP_VALUES, FND_TERRITORIES_TL, and AP_TERMS, while freight defaults are supplied by ORG_FREIGHT. The PO_COMMUNICATION_PVT and PO_CORE_S packages provide formatting routines (GETFORMATMASK and the archive-buyer functions), and FND_GLOBAL supplies environment context.

Key Columns

Common Use Cases and Queries

The view is most commonly queried to reproduce the header data printed on or transmitted with a release document, and to feed XML publishers that require a single flattened row per release. A typical query filters by the parent PO segment and revision:

  • SELECT segment1, revision_num, vendor_name, document_buyer_last_name, currency_code FROM po_release_xml WHERE segment1 = :p_po_number;
  • SELECT segment1, revision_num, vendor_num, ship_via, payment_terms FROM po_release_xml WHERE cancel_flag = 'N';
  • SELECT segment1, archive_buyer_first_name, archive_buyer_last_name FROM po_release_xml WHERE revision_num > 0;

Because the view executes packaged function calls such as PO_COMMUNICATION_PVT.GETARCBUYERFNAME for every row, queries returning large result sets can incur significant cost; restricting by SEGMENT1 or REVISION_NUM is advisable. The view is intended for read-only reporting and integration and must not be used for DML against releases.