Results for “icx_location”

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

Overview

APPS.ICX_PO_LINE_LOC_DIFF_V is a reporting and integration view in Oracle E-Business Suite (EBS) used by the iProcurement and Internet Procurement Foundation (ICX) modules to expose line-level location change information captured against purchasing documents. The view is a filtered projection of a temporary revision staging table rather than a standalone persistent entity. It presents the set of purchase order or release line records whose changed attribute, recorded at the location level, has been flagged with the level designation ICX_LOCATION.

In EBS 12.1.1 and 12.2.2, this object serves the "what changed" comparison logic that determines which purchasing document attributes were modified between revisions. Because the view restricts output to location-level alterations, consumers of the view receive only those differences attributable to ship-to or deliver-to location changes on a purchase order line, which is central to supplier-facing alerts, change notifications, and procurement review screens.

Underlying Base Objects

The view is defined over a single referenced object, documented in the ETRM metadata as the synonym ICX_PO_REVISIONS_TEMP. The synonym resolves to the underlying temporary revision table that stores detected differences between the current and prior states of a purchasing document. The view does not perform joins or aggregations; it is a simple SELECT with a WHERE predicate that filters the staging table to rows where LEVEL_ALTERED = 'ICX_LOCATION'. All ten columns projected by the view are drawn directly from that base object, so the view inherits the base table's data lifecycle, including the temporary or session-scoped nature of the revision staging rows.

Key Columns

• LINE_SEQ — Sequence number of the affected purchase order line, used for ordering and identifying the line within a document.
• HEADER_ID — Identifier of the purchase order or agreement header to which the changed line belongs.
• RELEASE_ID — Identifier of the associated release, populated when the changed document line belongs to a release rather than the base order.
• LINE_ID — Unique identifier of the purchase order line carrying the location change.
• LOCATION_ID — Identifier of the location (ship-to or deliver-to) affected by the alteration.
• LOCATION_NUM — Number of the location record, complementing LOCATION_ID for display and reference.
• LEVEL_ALTERED — The level at which the change was detected; for this view the value is always ICX_LOCATION.
• FIELD_ALTERED — The specific field within the location level that was modified.
• CHANGES_FROM — The value prior to the change.
• CHANGES_TO — The value after the change.

Common Use Cases and Queries

The view is typically queried to retrieve location-related differences for a given document so that change notifications, approval routing, or supplier communication can reflect only relevant modifications. A typical retrieval for a specific order is:

• SELECT LINE_SEQ, HEADER_ID, RELEASE_ID, 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 ORDER BY LINE_SEQ;
• Restricting by line: ... WHERE LINE_ID = :p_line_id;
• Auditing a specific location: ... WHERE LOCATION_ID = :p_location_id;
• Reporting the changed fields per release: ... WHERE RELEASE_ID = :p_release_id;

Because the view filters on LEVEL_ALTERED = 'ICX_LOCATION', queries need not repeat that predicate; the filter is already applied. Practically, the view is consumed programmatically by iProcurement change-processing logic and can be used in custom reports to surface "location changed" events for a purchase order. Given that the source object is a temporary revision table, results reflect only currently staged differences, and callers should confirm that revision data has been populated before relying on the output.