Search Results changes_from

Overview

The APPS.POS_PO_REVISIONS_TEMP_V view is a Purchasing (PO) module database object that exposes the content of the temporary revision-tracking table ICX_PO_REVISIONS_TEMP in a denormalized, presentation-ready form. It belongs to the Oracle E-Business Suite release 12.1.1 and 12.2.2 code line and carries a status of VALID. Its functional purpose is to surface the attributes that Oracle Purchasing has flagged as modified during a document revision, so that the change notification and modification-history user interfaces can display a human-readable label for each altered field together with its previous value and its new value.

The view does not perform transactional data manipulation. It is a read-only projection used for reporting and for feeding the EBS notification framework. Because it joins descriptive metadata (the field label) to the raw revision deltas, downstream components can present revision lines without embedding the AK attribute lookup logic themselves.

Underlying Base Objects

The view is defined over four base objects plus one package:

• ICX_PO_REVISIONS_TEMP (synonym; base table PORT) — the driving table, holding the revision deltas written during a modify operation on a purchase order, release, line, shipment, or distribution. Every row in the view corresponds to one revision detail record.
• MTL_SYSTEM_ITEMS (synonym; alias MSI) — outer-joined on ITEM_ID = INVENTORY_ITEM_ID to resolve the inventory item, and used to supply the ROWID consumed by the POS_GET.ITEM_FLEX_SEG function.
• FINANCIALS_SYSTEM_PARAMS_ALL (synonym; alias FSP) — joined on the inventory organization, with NVL applied so that rows are retained when the item carries no organization context. This establishes the operating context (organization) for the flexfield resolution.
• AK_REGION_ITEMS_VL (view; alias ARI) — the descriptive flexfield/attribute registry. The join is hard-coded to region application 601 and region code 'ICX_PO_REVISIONS_PROMPTS', with attribute application 178 and ATTRIBUTE_CODE = PORT.FIELD_ALTERED, so that each changed field yields its translated long label (ATTRIBUTE_LABEL_LONG).
• POS_GET (package) — invoked as POS_GET.ITEM_FLEX_SEG(MSI.ROWID) to return the concatenated item key flexfield, delivered in the ITEM_NUMBER column of the projection.

Key Columns

• LEVEL_ALTERED — the document level at which the change occurred (for example header, line, shipment/location, or distribution). This column is the anchor for the user's search term "level_altered" and is the discriminator used to group revision deltas by structural level.
• FIELD_ALTERED / ATTRIBUTE_LABEL_LONG — the internal field identifier and its translated display label; the latter is derived via the AK_REGION_ITEMS_VL join.
• CHANGES_FROM / CHANGES_TO — the prior and revised values for the altered field, enabling before/after comparison.
• Header and hierarchy keys — HEADER_ID, RELEASE_ID, LINE_ID, LOCATION_ID, DISTRIBUTION_ID, each NVL-defaulted to -99 to preserve non-applicable levels.
• Descriptive keys — PO_NUM, REVISION_NUM, LINE_NUM, LOCATION_NUM, DISTRIBUTION_NUM, ITEM_ID, ITEM_NUMBER, LINE_SEQ, and CREATION_DATE, providing the human-readable document reference and audit timestamp.

Common Use Cases and Queries

Typical scenarios include building a revision-history report for a purchase order, auditing which fields were changed at a given level, and troubleshooting change-notification behavior.

List all alterations at the distribution level for a header:

• SELECT po_num, revision_num, line_num, level_altered, attribute_label_long, changes_from, changes_to FROM apps.pos_po_revisions_temp_v WHERE header_id = :p_header_id AND level_altered = 'DISTRIBUTION' ORDER BY line_seq;

Count changes grouped by level:

• SELECT level_altered, COUNT(*) FROM apps.pos_po_revisions_temp_v WHERE header_id = :p_header_id GROUP BY level_altered;

Retrieve item context for altered lines:

• SELECT po_num, line_num, item_number, attribute_label_long, changes_from, changes_to FROM apps.pos_po_revisions_temp_v WHERE item_id = :p_item_id ORDER BY creation_date DESC;

Because the view is a projection over a temporary staging table, its contents reflect only the revision session in scope; result sets are therefore typically filtered by HEADER_ID, CREATION_DATE, or the session that populated ICX_PO_REVISIONS_TEMP.