Results for “level_altered”

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

Overview

ICX_PO_LINE_LOC_DIFF_V is a view owned by the APPS schema in Oracle E-Business Suite, registered under the ICX product family (Oracle iProcurement). The view is documented in the ETRM as Obsolete, meaning it is retained in the database for backward compatibility but is no longer actively maintained or referenced by current iProcurement functionality. Its purpose was to expose the subset of purchase order and release change records whose altered attribute was the shipment or distribution location — the condition enforced by the literal LEVEL_ALTERED = 'ICX_LOCATION' in the view definition. In that role, the view served as a filtered presentation layer over the iProcurement change-tracking staging table, allowing callers to isolate location-level modifications to PO lines and releases without writing the predicate themselves.

The user search term "icx_location" corresponds directly to the value stored in the LEVEL_ALTERED column that this view filters on, which is likely why this object surfaces in such searches. In 12.1.1 and 12.2.2, the view is valid but should be treated as legacy; new development should not depend on it.

Underlying Base Objects

The view is defined over a single base object: the synonym ICX_PO_REVISIONS_TEMP, which resolves to a table in the APPS schema. All rows and columns exposed by the view originate from that table; there are no joins, unions, or additional objects referenced. The relationship is a straightforward projection with one row-level filter:

• All ten columns are selected directly from ICX_PO_REVISIONS_TEMP with no transformation, aliasing, or expression.
• The only restriction is WHERE POR.LEVEL_ALTERED = 'ICX_LOCATION', so the view returns exactly those rows of the temp table representing location-level revisions.

Because the view simply wraps the table's ICX_LOCATION rows, any purge, archive, or truncate operation against ICX_PO_REVISIONS_TEMP directly affects the view's result set. Change records are transient by nature, so row counts can fluctuate as the iProcurement revision process writes and clears entries.

Key Columns

The column list mirrors the change-tracking model of the underlying table:

• LINE_SEQ — sequence number identifying the line entry within the change set.
• HEADER_ID — purchase order header identifier; the anchor for the document being changed.
• RELEASE_ID — release identifier where the change occurred against a blanket agreement release.
• LINE_ID — the PO line affected by the revision.
• LOCATION_ID — the location (ship-to or internal location) associated with the changed line.
• LOCATION_NUM — the location number, providing a human-readable reference to LOCATION_ID.
• LEVEL_ALTERED — the level at which the change was recorded; always ICX_LOCATION in this view, since the predicate fixes it.
• FIELD_ALTERED — the specific attribute that changed within the location level.
• CHANGES_FROM — the prior value of the altered field.
• CHANGES_TO — the new value of the altered field.

Together, HEADER_ID, LINE_ID, and LOCATION_ID form the practical key for correlating a revision back to the affected PO line and its location, while the CHANGES_FROM/CHANGES_TO pair supplies the before-and-after audit detail.

Common Use Cases and Queries

Historically the view supported iProcurement diagnostics and change-audit reporting, for example identifying which PO lines had their location altered during a given processing window, or reconstructing the prior and current location values for a disputed change. Because LEVEL_ALTERED is fixed by the view, queries need not repeat that filter. For example:

• List all location-level revisions for a specific purchase order:
  SELECT line_seq, line_id, location_id, location_num, field_altered, changes_from, changes_to FROM apps.icx_po_line_loc_diff_v WHERE header_id = :p_header_id;
• Examine changes against a particular line:
  SELECT location_id, field_altered, changes_from, changes_to FROM apps.icx_po_line_loc_diff_v WHERE line_id = :p_line_id;
• Confirm the view is empty (typical in steady state, since it is obsolete and its base table is transient):
  SELECT COUNT(*) FROM apps.icx_po_line_loc_diff_v;

Given the Obsolete designation, these queries are appropriate for troubleshooting or historical investigation only. Integrations, concurrent programs, and custom reports in 12.1.1 or 12.2.2 should target supported change-history objects rather than this view, and any existing dependency should be reviewed for replacement.