Search Results icx_po_headers_archive_v




Overview
Explore in AI Chat

Overview

The ICX_PO_HEADERS_ARCHIVE_V view is an archived purchase order header view owned by the APPS schema and shipped with the Oracle iProcurement (ICX) product. In Oracle EBS 12.1.1 and 12.2.2, its status is VALID. It exposes purchase order header information drawn from the archived purchasing tables rather than the live transactional tables, so it is the natural source when reporting against historical or purged purchase order data. Its role in reporting and integration is to present a denormalized, human-readable picture of archived PO headers: the header attributes from PO_HEADERS_ARCHIVE are joined to document type names, agent names, vendor names, vendor site addresses, and vendor contact details, allowing self-service procurement reporting, reconciliation, and archival extracts without reconstructing these joins manually. Because the view lives in APPS and is defined on archived base objects, it is typically consumed by concurrent-program extracts, custom reports, and downstream integrations that need the "as-archived" state of a purchase order.

Underlying Base Objects

Per the ETRM documentation, ICX_PO_HEADERS_ARCHIVE_V is defined over the following referenced base objects: PO_HEADERS_ARCHIVE, PO_RELEASES_ARCHIVE, PO_DOCUMENT_TYPES, PO_VENDORS, PO_VENDOR_SITES, PO_VENDOR_CONTACTS, PO_LOOKUP_CODES, HR_LOCATIONS, AP_TERMS, and GL_DAILY_CONVERSION_TYPES, together with the packages PO_INQ_SV, PO_TOTALS_PO_SV, FND_GLOBAL, FND_CURRENCY, and HR_GENERAL.

The central table is PO_HEADERS_ARCHIVE, the archived counterpart of PO_HEADERS. The view's SELECT list references the archive synonym directly through the alias POH, and pulls related attributes from the document type table (PDT.TYPE_NAME), the vendor view (V.VENDOR_NAME), the vendor sites view (VS.VENDOR_SITE_CODE and address fields), and the vendor contacts view (VC.LAST_NAME, VC.FIRST_NAME). The PO_INQ_SV package function GET_PERSON_NAME is invoked to resolve POH.AGENT_ID into a buyer name. A constant literal 'N' is projected in the first position of the select list, and DECODE and NVL expressions are applied to reproduce the defaulted semantics of the live PO header (for example, defaulting AUTHORIZATION_STATUS to 'INCOMPLETE', CLOSED_CODE to 'OPEN', and several flag columns to 'N'). The presence of PO_RELEASES_ARCHIVE and the totals package in the referenced object list reflects that release-level archival data and PO totals are also within the view's dependency set.

Key Columns

Common Use Cases and Queries

This view is used for archived PO reporting, historical procurement reconciliation, and building extracts for downstream systems. A typical query lists archived headers with buyer and vendor detail:

SELECT po_header_id, segment1, type_name, authorization_status,
       po_inq_sv.get_person_name(agent_id) buyer_name,
       vendor_name, vendor_site_code, currency_code, creation_date
  FROM apps.icx_po_headers_archive_v
 WHERE creation_date >= :p_from_date
   AND creation_date <  :p_to_date;

For reconciliation against live data, the header ID or SEGMENT1 can be used to detect records that exist only in the archive. For closure or hold analysis, filter on CLOSED_CODE, FROZEN_FLAG, or USER_HOLD_FLAG, remembering that the view applies NVL and DECODE defaults and therefore returns normalized values rather than raw nulls. When joining to PO distributions or release data, join on PO_HEADER_ID and be aware that release-level archival data is part of the underlying model. Queries on this view should generally filter by CREATION_DATE, VENDOR_ID, or AGENT_ID to limit full scans of the archive tables.