Results for “po_headers_archive_all”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_HEADERS_ARCHIVE_ALL is the archival table for purchase order headers in the Oracle Purchasing (PO) module. It resides in the PO schema and stores archived purchase orders that have been migrated out of the operational PO_HEADERS_ALL table. In Oracle EBS 12.1.1 and 12.2.2, the Purchasing application maintains headers, lines, and distributions across active and archive layers so that long-closed or superseded documents remain queryable without degrading transaction-table performance.

The table has 201 documented columns and is keyed on PO_HEADER_ID and REVISION_NUM via the PO_HEADERS_ARCHIVE_PK constraint. A heuristic Data Vault classification mined from the foreign-key structure places this table as satellite-leaning: it carries descriptive, revision-scoped attributes tied to a purchase order hub. Under this reading, PO_HEADER_ID would serve as the hub key, REVISION_NUM as part of the satellite key, and the descriptive columns (notes, amounts, statuses, contract metadata) as satellite attributes.

Key Information Stored

The surrogate primary key is PO_HEADER_ID combined with REVISION_NUM. Two unique business-key candidates are documented: PO_HEADERS_ARCHIVE_U1 (PO_HEADER_ID, REVISION_NUM) and PO_HEADERS_ARCHIVE_U2 (SEGMENT1, REVISION_NUM, TYPE_LOOKUP_CODE, ORG_ID). SEGMENT1 is the human-readable document number.

Common Use Cases and Queries

Typical use cases include historical PO reporting, audit and compliance retrieval, and reconciliation of archived agreements without touching live transaction tables. Queries generally filter by ORG_ID for MOAC and by SEGMENT1 for document lookup.

  • Retrieve all revisions of an archived document: SELECT PO_HEADER_ID, SEGMENT1, REVISION_NUM, AUTHORIZATION_STATUS FROM PO_HEADERS_ARCHIVE_ALL WHERE SEGMENT1 = :doc_num AND ORG_ID = :org;
  • List archived documents for a supplier: join VENDOR_ID to PO_VENDORS and filter on authorization status.
  • Reporting on approved spend by currency and rate type using CURRENCY_CODE and RATE_TYPE.
  • Reconciliation against the active layer via FROM_HEADER_ID.

Because the table is large and revision-scoped, queries should always predicate on the primary or unique key columns to avoid full scans.

Related Objects