Results for “location_num”

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

Overview

The view APPS.ICX_PO_LINE_DIST_DIFF_V belongs to the ICX – Oracle iProcurement product family and is documented in ETRM as Obsolete. Despite its obsolete status, the view remains present and VALID in the APPS schema in both Oracle EBS 12.1.1 and 12.2.2, which means it can still be queried and may still be referenced by legacy customizations, inbound interfaces, or historical reports. Its purpose is to expose distribution-level change records captured during the iProcurement purchasing revision process, correlating a distribution-level change tracked in the temporary revisions table with its corresponding archived shipment (line location) record.

The view serves as a reporting and diagnostic bridge: it joins the staged change information held in ICX_PO_REVISIONS_TEMP with the shipment archive data in PO_LINE_LOCATIONS_ARCHIVE, restricted to rows where the altered level is ICX_DISTRIBUTION. In this way it answers the question "which distribution changes were made, and what shipment did they affect?" without requiring consumers to write the join themselves.

Underlying Base Objects

The view is defined over two documented base objects, both exposed in the APPS schema as synonyms:

• ICX_PO_REVISIONS_TEMP (aliased POR) – the staged/pending revision records. The view filters this table with LEVEL_ALTERED = 'ICX_DISTRIBUTION', isolating changes made at the distribution level.
• PO_LINE_LOCATIONS_ARCHIVE (aliased POLLA) – the archive of purchasing line location (shipment) records. The join condition is POLLA.SHIPMENT_NUM = POR.LOCATION_ID, tying each distribution change to the shipment whose shipment number matches the recorded location identifier.

Notably, the join is a simple equi-join on those two columns with no outer join, so only distribution change records with a matching archived shipment appear in the result. Because PO_LINE_LOCATIONS_ARCHIVE is an archive table, historical shipments that have been archived remain available for correlation even when the live line location rows have changed or been purged.

Key Columns

The view exposes the following columns:

• LINE_SEQ, HEADER_ID, RELEASE_ID, LINE_ID – identity context for the purchase order and line associated with the change.
• LOCATION_ID – the location identifier from the revision record; matched against the shipment in the archive.
• LOCATION_NUM – the shipment number obtained from POLLA.SHIPMENT_NUM.
• DISTRIBUTION_ID, DISTRIBUTION_NUM – the specific distribution affected by the change.
• LEVEL_ALTERED – the level at which the change occurred; always ICX_DISTRIBUTION in this view.
• FIELD_ALTERED – the attribute that was modified.
• CHANGES_FROM, CHANGES_TO – the before-and-after values of the altered field, providing the audit trail of the change.

Common Use Cases and Queries

Typical usage centers on auditing and troubleshooting change history for iProcurement distributions, and on reconciling staged revisions against archived shipments. A representative query lists all distribution-level changes with their before/after values:

• SELECT header_id, line_id, location_id, location_num, distribution_num, field_altered, changes_from, changes_to FROM apps.icx_po_line_dist_diff_v WHERE header_id = :p_header_id;
• SELECT * FROM apps.icx_po_line_dist_diff_v WHERE field_altered = 'QUANTITY' ORDER BY header_id, line_id;
• Joining the view back to shipment archive or revision staging tables for reconciliation reports on archived versus current shipment data.

Because the object is flagged Obsolete, new development should avoid depending on it; existing queries should be reviewed against supported alternatives before upgrades. Nonetheless, for 12.1.1 and 12.2.2 diagnostics it remains a useful read-only structure for inspecting distribution-level change data.