Search Results igi_rpi_audit_items_all




Overview
Explore in AI Chat

Overview

The IGI_RPI_AUDIT_ITEMS_ALL table is a core audit and history object within the IGI – Public Sector Financials International module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It records charge item price updates, where each row represents a price update applied to a specific charge item maintained in IGI_RPI_ITEMS_ALL. The table therefore serves as a change-history ledger for pricing, enabling public sector organizations to retain an immutable record of how a charge item's price evolved over time. This is particularly significant in regulated public sector environments, where historical pricing evidence must be preserved for audit, legislative reporting, and reconciliation purposes.

From a dimensional modeling perspective, the documented foreign key structure suggests a satellite-leaning Data Vault classification. The single outbound reference to IGI_RPI_ITEMS_ALL via ITEM_ID indicates that this table carries descriptive attributes (price, effective dates, revisions) attached to a parent business entity, rather than acting as an independent hub or an associative link. Modelers should treat the table as a satellite of the charge-item hub, where the combination of item, run, and effective date typically defines a change event.

Key Information Stored

The table exposes twelve documented columns. The most functionally important are summarized below; the remaining columns are standard Oracle WHO-column audit fields.

  • ITEM_ID – Foreign key to IGI_RPI_ITEMS_ALL. Identifies the charge item to which the price update applies. This is the principal business-key candidate from a relationships standpoint.
  • PRICE – The price value applied to the charge item as a result of this update.
  • EFFECTIVE_DATE – The date on which the recorded price becomes effective.
  • REVISED_PRICE – The revised price value, capturing subsequent corrections or amendments to a prior price update.
  • REVISED_EFFECTIVE_DATE – The effective date associated with the revised price, allowing paired original/revised price history.
  • RUN_ID – Identifier of the concurrent program run or batch that generated the price update, supporting traceability back to the originating process.
  • ORG_ID – Operating unit / organization identifier, enabling multi-org (MOAC) partitioning of the audit records.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard Oracle audit (WHO) columns recording who created and last modified each audit row.

While the metadata does not document an explicit surrogate primary key or unique index beyond the foreign key, the ITEM_ID column combined with effective date and RUN_ID functions as the practical business-key candidate for uniquely identifying a price-update event.

Common Use Cases and Queries

Typical scenarios include pricing history reports, audit trails for regulatory review, and reconciliation of price changes per batch run.

  • Price history for a charge item – retrieve all updates for a given item ordered by effective date:
    SELECT item_id, price, effective_date, revised_price, revised_effective_date FROM igi.igi_rpi_audit_items_all WHERE item_id = :p_item_id ORDER BY effective_date;
  • Batch-level audit – list all price updates produced by a specific run:
    SELECT item_id, price, effective_date FROM igi.igi_rpi_audit_items_all WHERE run_id = :p_run_id AND org_id = :p_org_id;
  • Revised vs. original price comparison – identify items where corrections occurred:
    SELECT item_id, price, revised_price FROM igi.igi_rpi_audit_items_all WHERE revised_price IS NOT NULL AND NVL(price,-1) <> NVL(revised_price,-1);
  • Period reporting – aggregate updates within an effective-date range for management reporting.

Related Objects

  • IGI_RPI_ITEMS_ALL – Parent charge-item master table; joined on IGI_RPI_AUDIT_ITEMS_ALL.ITEM_ID = IGI_RPI_ITEMS_ALL.ITEM_ID. This is the documented foreign key relationship and the primary dependency.
  • IGI_RPI_AUDIT_ITEMS – Non-_ALL counterpart view or synonym, subject to operating-unit filtering.
  • IGI_RPI_ITEMS – Operating-unit filtered view of the parent items table.
  • FND_CONCURRENT_REQUESTS – Joined via RUN_ID to trace the concurrent program that generated updates.
  • FND_USER – Associated via CREATED_BY and LAST_UPDATED_BY for user attribution.
  • HR_OPERATING_UNITS / ORG_ORGANIZATION_DEFINITIONS – Joined via ORG_ID to resolve operating-unit context.