Search Results changes_from




Overview
Explore in AI Chat

Overview

The view APPS.ICX_PO_HEADER_DIFF_V is a reporting object within the Oracle iProcurement (ICX) product family, documented in Oracle E-Business Suite 12.1.1 and 12.2.2. Its ETRM metadata classifies the object with a description of "Obsolete," meaning Oracle no longer positions it as a supported interface for current development or customization work, even though the definition remains VALID in the APPS schema. Functionally, the view projects a filtered subset of rows from the temporary revisions table ICX_PO_REVISIONS_TEMP, restricted to records where LEVEL_ALTERED equals the literal 'ICX_HEADERS'. This restriction isolates header-level change records — that is, modifications detected against the purchasing document header rather than its lines, distributions, or other subordinate entities. The view therefore acts as a change-detection lens during the iProcurement requisition-to-purchase-order revision cycle, exposing pairs of before-and-after values for comparison and downstream processing.

Underlying Base Objects

The view is defined exclusively over one base object, the synonym ICX_PO_REVISIONS_TEMP, resolved within the APPS schema. The view performs no joins, unions, or aggregations; it is a straightforward projection of seven columns filtered by a single equality predicate. The dependence on a temporary staging table is significant: ICX_PO_REVISIONS_TEMP accumulates transient revision records generated while iProcurement compares the current state of a purchase order against a previously stored baseline. Because the data is transient, the view is meaningful only within the window in which the revision comparison process populates the staging table. Once the comparison completes and the temporary rows are cleared, the view returns no data. Consumers must therefore treat ICX_PO_HEADER_DIFF_V as a process-scoped object rather than a persistent reporting source.

Key Columns

  • LINE_SEQ — A sequence value used to order revision records within the comparison set, providing a stable sort key for the header-level differences.
  • HEADER_ID — The identifier of the purchase order header to which the detected change applies, linking the difference record to the purchasing document.
  • RELEASE_ID — The release identifier associated with the header, relevant for blanket purchase agreement releases.
  • LEVEL_ALTERED — The entity level at which the change occurred. The view always returns 'ICX_HEADERS' because of its defining predicate.
  • FIELD_ALTERED — The specific header attribute that changed, such as supplier, terms, or currency.
  • CHANGES_FROM — The prior value of the altered field, captured before the revision.
  • CHANGES_TO — The new value of the altered field, captured after the revision.

Common Use Cases and Queries

The primary use case is diagnostic and integration-oriented: identifying precisely which header fields changed between two versions of a purchase order during iProcurement revision processing. A typical query filters by header and orders by sequence, as shown below.

  • SELECT line_seq, field_altered, changes_from, changes_to FROM apps.icx_po_header_diff_v WHERE header_id = :p_header_id ORDER BY line_seq;
  • SELECT header_id, field_altered, COUNT(*) FROM apps.icx_po_header_diff_v GROUP BY header_id, field_altered;

Because the view is marked obsolete, new implementations should avoid hard dependencies on it and instead reference the underlying revision data through supported interfaces. Where the view is retained in legacy customizations, wrap access in defensive logic that tolerates an empty result set, since the transient staging data may not be present outside active revision processing.