Search Results po_lines_archive




Overview
Explore in AI Chat

Overview

ICX_PO_LOCATIONS_DIFF_V is an APPS-owned database view in Oracle E-Business Suite that isolates location-level change records captured during the Purchasing document revision process. It is one of the differential views built on the ICX_PO_REVISIONS_TEMP temporary staging table, which the EBS framework populates during approval and revision workflows to track what changed on a purchasing document. This particular view filters the revision staging data to only those rows where the LEVEL_ALTERED column equals 'ICX_LOCATION', meaning the change event involved a ship-to location, deliver-to location, or a related location attribute on a purchase order or release line.

Because it filters on a specific revision level and joins to the archived line table PO_LINES_ARCHIVE and the item key flexfield view MTL_SYSTEM_ITEMS_KFV, the view is not a general-purpose transactional view. Instead it is a diagnostic and reporting utility used to reconstruct location-attribute differences during document change tracking. That distinction is important for users searching on terms such as "po_lines_archive," since PO_LINES_ARCHIVE is one of the three underlying objects and the view exists precisely to correlate location change context with archived line detail.

Underlying Base Objects

The view definition references three objects, all exposed to APPS through synonyms:

  • ICX_PO_REVISIONS_TEMP (SYNONYM) — aliased POR. This is the revision tracking table that records the level altered, the field altered, and the before/after values for each change.
  • PO_LINES_ARCHIVE (SYNONYM) — aliased POLA. This is the archived/versioned copy of purchase order lines, holding the line-level snapshot including LINE_NUM and ITEM_ID.
  • MTL_SYSTEM_ITEMS_KFV (SYNONYM) — aliased MSI. This is the key flexfield view over inventory items, providing the CONCATENATED_SEGMENTS value used to display the item description flexfield.

Joins are established between POR.LINE_ID and POLA.PO_LINE_ID, and between POLA.ITEM_ID and MSI.INVENTORY_ITEM_ID. The ICX_PO_REVISIONS_TEMP row therefore acts as the driver, with PO_LINES_ARCHIVE and MTL_SYSTEM_ITEMS_KFV supplying line and item context.

Key Columns

  • LINE_SEQ — sequence identifier from the revision staging record, used for ordering change entries.
  • HEADER_ID, RELEASE_ID, LINE_ID — keys from ICX_PO_REVISIONS_TEMP, tying the change to its header, release, and line.
  • LINE_NUM, ITEM_ID — line-level detail from PO_LINES_ARCHIVE.
  • CONCATENATED_SEGMENTS — the concatenated key flexfield value of the inventory item.
  • LOCATION_ID, LOCATION_NUM — the location involved in the change, central to this view's purpose.
  • LEVEL_ALTERED, FIELD_ALTERED — LEVEL_ALTERED is always 'ICX_LOCATION'; FIELD_ALTERED identifies the specific location attribute modified.
  • CHANGES_FROM, CHANGES_TO — the prior and new values for the altered field.

Common Use Cases and Queries

Typical uses include auditing which location fields were modified during document revisions, validating that archive rows captured the change, and reconciling revision staging against archived PO lines. A representative query is:

SELECT LINE_SEQ, HEADER_ID, RELEASE_ID, LINE_ID, LINE_NUM, CONCATENATED_SEGMENTS, LOCATION_ID, LOCATION_NUM, FIELD_ALTERED, CHANGES_FROM, CHANGES_TO FROM APPS.ICX_PO_LOCATIONS_DIFF_V WHERE HEADER_ID = :p_header_id ORDER BY LINE_SEQ;

Because the view is restricted to LEVEL_ALTERED = 'ICX_LOCATION', queries should not be expected to return price, quantity, or item-level changes; those are covered by other differential views. When the revision staging table is cleared, results reflect only the currently staged change set.