Search Results igi_rpi_update_lines_all




Overview
Explore in AI Chat

Overview

IGI_RPI_UPDATE_LINES_ALL is an Oracle E-Business Suite table owned by the IGI schema and delivered as part of the IGI – Public Sector Financials International product. It records global update line information for charge items and standing charge line charge items. In practical terms, the table functions as a staging and audit repository for mass price maintenance activities performed against the Retail Price Index (RPI) structures used by public sector organizations to revalue charges, fees, and standing charges in bulk. Each row captures the outcome of applying a global update to a single charge item or standing charge line item, preserving both the pre-update and post-update values.

From a dimensional modeling perspective, the metadata classifies this object heuristically as a link table. This reflects its foreign key structure, which connects two distinct business entities — ITEM_ID referencing IGI_RPI_ITEMS_ALL and STANDING_CHARGE_ID referencing IGI_RPI_STANDING_CHARGES_ALL — through a transaction-like global update event identified by RUN_ID. Treated as a link in a Data Vault model, the table would resolve the many-to-many relationship between update runs and the charge lines they modify.

Key Information Stored

The table contains 18 documented columns. The most significant are:

  • RUN_ID — Identifier for the global update run or batch that produced the line; the primary grouping key for reconciliation and rollback.
  • ITEM_ID — Foreign key to IGI_RPI_ITEMS_ALL, identifying the charge item affected by the update.
  • STANDING_CHARGE_ID — Foreign key to IGI_RPI_STANDING_CHARGES_ALL, identifying the standing charge line affected.
  • LINE_ITEM_ID — Surrogate-style identifier for the individual global update line.
  • PRICE and REVISED_PRICE — The original price and the newly computed price resulting from the update.
  • UPDATED_PRICE — The final applied price value after the update run completes.
  • EFFECTIVE_DATE, REVISED_EFFECTIVE_DATE, and PREVIOUS_EFFECTIVE_DATE — The current, proposed, and prior effective dates associated with the price change.
  • PREVIOUS_PRICE — The price value before the update, retained for audit and rollback purposes.
  • SELECT_FLAG — Indicator controlling whether the line is included in a subsequent processing step.
  • ORG_ID — Operating unit identifier, enabling multi-organization data segregation.
  • Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) — Standard EBS who-columns tracking the origin and last modification of each line.

The documented foreign keys establish ITEM_ID and STANDING_CHARGE_ID as business-key candidates. No separate surrogate primary key is enumerated in the provided metadata, so RUN_ID combined with the relevant entity identifier generally serves as the practical composite key.

Common Use Cases and Queries

Typical scenarios involve auditing a global price update run, verifying which items changed, and reporting before-and-after prices.

  • List all lines for a specific run: SELECT * FROM igi.igi_rpi_update_lines_all WHERE run_id = :run_id;
  • Compare prior and revised prices per item: SELECT item_id, previous_price, revised_price, updated_price FROM igi.igi_rpi_update_lines_all WHERE run_id = :run_id ORDER BY item_id;
  • Join to the items table for descriptive detail: SELECT u.item_id, i.item_description, u.previous_price, u.updated_price FROM igi.igi_rpi_update_lines_all u JOIN igi.igi_rpi_items_all i ON u.item_id = i.item_id;
  • Isolate selected lines for downstream processing: filter on select_flag = 'Y'.
  • Effective-date impact analysis: group by effective_date to determine which charges take effect in a given period.

These queries support revaluation reporting, audit trails, and rollback preparation where previous_price and previous_effective_date are used to reverse an update.

Related Objects

The following objects are most significant to IGI_RPI_UPDATE_LINES_ALL:

  • IGI_RPI_ITEMS_ALL — joined via IGI_RPI_UPDATE_LINES_ALL.ITEM_ID = IGI_RPI_ITEMS_ALL.ITEM_ID; provides the charge item definition.
  • IGI_RPI_STANDING_CHARGES_ALL — joined via IGI_RPI_UPDATE_LINES_ALL.STANDING_CHARGE_ID = IGI_RPI_STANDING_CHARGES_ALL.STANDING_CHARGE_ID; provides the standing charge line definition.
  • Global update run master tables in the IGI schema — referenced through RUN_ID to group lines by execution.
  • IGI RPI charges and pricing tables — consumers of the updated prices produced by these lines.
  • Standard EBS concurrent program and audit views within the IGI module that report on price maintenance activity.

As with all IGI RPI objects, direct DML should be avoided; changes should be made through the supported global update programs to preserve referential integrity and audit history.