Search Results po_release_archive_xml




Overview
Explore in AI Chat

Overview

The PO_RELEASE_ARCHIVE_XML view, owned by the APPS schema within the Oracle E-Business Suite Purchasing (PO) module, presents archived release data in a denormalized structure tailored for XML document generation and reporting. Its purpose is to produce a consolidated rowset representing a purchase order release as it existed at the time of archival, combining header, release, vendor, contact, buyer, currency, freight, and terms information. Because archived releases capture point-in-time snapshots rather than live transactional data, the view serves as a stable source for regenerating release documents and for auditing historical release content without depending on current transactional state. The presence of a number of customizable descriptive flexfield columns and formatted date strings indicates the view is designed for direct consumption by report layouts and XML publisher templates rather than for transactional processing.

Underlying Base Objects

According to documented ETRM metadata for 12.2.2, the view references a range of base objects including PO_HEADERS_ALL, PO_RELEASES_ARCHIVE_ALL, PO_AGENTS, PO_VENDORS, PO_VENDOR_CONTACTS, PO_VENDOR_SITES_ALL, PER_ALL_PEOPLE_F, AP_TERMS, FND_CURRENCIES_TL, FND_LOOKUP_VALUES, FND_TERRITORIES_TL, and ORG_FREIGHT. Two PL/SQL packages, PO_COMMUNICATION_PVT and PO_CORE_S, are also referenced, along with the FND_GLOBAL package. The primary driving table is PO_RELEASES_ARCHIVE_ALL, which stores the archived release revisions, joined to PO_HEADERS_ALL through the header identifier. Buyer details are resolved from PER_ALL_PEOPLE_F via the agent identifier on the header. Vendor name and address data derive from PO_VENDORS, PO_VENDOR_SITES_ALL, and PO_VENDOR_CONTACTS, while code meanings are translated through the FND lookup and territory views and through AP_TERMS and ORG_FREIGHT. The PO_COMMUNICATION_PVT package supplies archive-specific buyer values through functions such as GETARCBUYERFNAME, GETARCBUYERLNAME, and GETARCBUYERTITLE.

Key Columns

The view exposes identifying and descriptive columns spanning several categories. Document identifiers include SEGMENT1 (the release number) derived from the header, along with REVISION_NUM, PRINT_COUNT, CANCEL_FLAG, and the CREATION_DATE, PRINTED_DATE, and REVISED_DATE date values. Buyer information appears as DOCUMENT_BUYER_FIRST_NAME, DOCUMENT_BUYER_LAST_NAME, DOCUMENT_BUYER_TITLE, and DOCUMENT_BUYER_AGENT_ID, complemented by archive-specific equivalents ARCHIVE_BUYER_AGENT_ID, ARCHIVE_BUYER_FIRST_NAME, ARCHIVE_BUYER_LAST_NAME, and ARCHIVE_BUYER_TITLE, which are null unless a nonzero revision exists. Currency data is provided via CURRENCY_CODE, CURRENCY_NAME, and a formatted RATE. Commercial terms include SHIP_VIA, FOB, FREIGHT_TERMS, and PAYMENT_TERMS. Vendor information comprises CUSTOMER_NUM, VENDOR_NUM, VENDOR_NAME, the address components VENDOR_ADDRESS_LINE1 through VENDOR_ADDRESS_LINE3, VENDOR_CITY, VENDOR_STATE, VENDOR_POSTAL_CODE, VENDOR_COUNTRY, and VENDOR_PHONE. The vendor contact is represented by VENDOR_CONTACT_FIRST_NAME, VENDOR_CONTACT_LAST_NAME, and VENDOR_CONTACT_TITLE. Acceptance parameters appear as ACCEPTANCE_REQUIRED_FLAG and ACCEPTANCE_DUE_DATE, and ten descriptive flexfield columns (ATTRIBUTE1 through ATTRIBUTE10) carry implementation-specific extensions.

Common Use Cases and Queries

The view is most often queried to retrieve archived release content for document regeneration, vendor correspondence, and audit reporting. A user searching for vendor_contact_title would query the VENDOR_CONTACT_TITLE column, which is sourced from the title attribute of the vendor contact record. A representative query retrieving releases together with vendor and contact details is:

  • SELECT SEGMENT1, REVISION_NUM, CANCEL_FLAG, VENDOR_NAME, VENDOR_CONTACT_FIRST_NAME, VENDOR_CONTACT_LAST_NAME, VENDOR_CONTACT_TITLE FROM APPS.PO_RELEASE_ARCHIVE_XML WHERE VENDOR_NUM = :vendor_num;
  • SELECT SEGMENT1, REVISION_NUM, ARCHIVE_BUYER_TITLE, VENDOR_CONTACT_TITLE, CREATION_DATE FROM APPS.PO_RELEASE_ARCHIVE_XML WHERE SEGMENT1 = :release_num ORDER BY REVISION_NUM DESC;
  • SELECT SEGMENT1, VENDOR_NAME, CURRENCY_CODE, RATE, FOB, FREIGHT_TERMS, PAYMENT_TERMS FROM APPS.PO_RELEASE_ARCHIVE_XML WHERE CANCEL_FLAG = 'N';

Because the underlying source is an archive, results reflect the release as captured at archive time and should not be treated as current transaction status. Filtering on REVISION_NUM allows reconstruction of each archived revision, and the archive-specific buyer columns permit accurate rendering of buyer identity as it appeared in the original document.