Search Results icx_po_revisions_temp




Overview
Explore in AI Chat

Overview

The PO_RELEASES_ARCHIVE_ALL table is a core data repository within the Oracle E-Business Suite Purchasing (PO) module, specifically for releases generated against Blanket Purchase Agreements (BPAs). Its primary role is to serve as the historical archive for all revisions of release documents. When a release is amended, the system preserves the previous version's complete record in this archive table before creating a new, current revision in the primary transaction table, PO_RELEASES_ALL. This design is fundamental to maintaining a full audit trail, enabling compliance reporting, and supporting the revision history functionality critical for procurement processes in versions 12.1.1 and 12.2.2.

Key Information Stored

The table stores a comprehensive snapshot of a release document at a specific point in its revision history. Each row represents a unique combination of a release and its revision number. While the full column list is extensive, key fields typically include the unique identifier PO_RELEASE_ID, the REVISION_NUM that sequences the changes, and a complete set of document attributes such as the releasing supplier, ship-to and bill-to locations, currency, authorized amount, release date, and approval status. The combination of PO_RELEASE_ID and REVISION_NUM forms the table's primary key (PO_RELEASES_ARCHIVE_PK), ensuring each archived revision is uniquely identifiable.

Common Use Cases and Queries

The primary use case is historical auditing and compliance reporting. Analysts can query this table to reconstruct the complete lifecycle of a release, track changes to critical terms like price or quantity over time, or generate reports for internal or external auditors. A common query pattern involves joining the archive to the main releases table to compare current and historical states. For example:

  • Retrieving Full Revision History: SELECT * FROM po_releases_archive_all WHERE po_release_id = :release_id ORDER BY revision_num;
  • Comparing Specific Revisions: Joining the archive to itself on PO_RELEASE_ID to diff consecutive revisions and identify changed columns.
  • Audit Reporting: Generating reports that show all modifications made to releases within a specific period, often joined with user tables (FND_USER) to capture who made the change.

Related Objects

As per the provided ETRM metadata, the table has a direct foreign key relationship, indicating its integration within the Purchasing data model. The documented relationship is:

  • Foreign Key Reference: The table ICX_PO_REVISIONS_TEMP references PO_RELEASES_ARCHIVE_ALL. The join is made using the columns ICX_PO_REVISIONS_TEMP.RELEASE_ID (to PO_RELEASE_ID) and ICX_PO_REVISIONS_TEMP.REVISION_NUM (to REVISION_NUM). This temporary table is typically used by the Oracle iProcurement module for processing revision data during requisition conversion or other interactive sessions.

Fundamentally, this archive table is intrinsically linked to its source transaction table, PO_RELEASES_ALL, with which it shares an identical structure for a given PO_RELEASE_ID, differing only by the active revision number.