Search Results igi_rpi_update_hdr




Overview
Explore in AI Chat

Overview

APPS.IGI_RPI_UPDATE_HDR_V is a reporting and integration view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 ETRM (E-Business Tax and Regulatory Management / Grants) schema. It presents the header information for Retail Price Index (RPI) global update runs — a mass-maintenance mechanism that allows buyers or catalog administrators to apply a uniform amount or percentage adjustment to the prices of many items at once. The view sits on top of the IGI_RPI_UPDATE_HDR base table and enriches each run header with human-readable descriptions resolved from the IGI_LOOKUPS view, along with the corresponding item codes for the "from" and "to" items involved in each update line.

The view is primarily used for transactional reporting, audit tracking, and downstream integration. Because it exposes the option flag and status both as raw lookup codes and as decoded meanings, it is well suited for dashboards, concurrent program extract files, and interfaces that must present pricing actions in a business-friendly form. In the context of the user's search term global_update_status, the view is the canonical source for the status of a global update header, decoded through the GLOBAL_UPDATE_STATUS lookup type.

Underlying Base Objects

The view is defined over three documented referenced base objects:

  • IGI_LOOKUPS (VIEW) — joined twice, once as D for the GLOBAL_UPDATE_OPTION lookup and once as E for the GLOBAL_UPDATE_STATUS lookup. These joins supply the decoded meaning values exposed as update_option and update_status.
  • IGI_RPI_ITEMS_ALL (SYNONYM) — joined twice, as B for the source item (item_id_from) and as C for the target item (item_id_to), supplying item_code_from and item_code_to.
  • IGI_RPI_UPDATE_HDR (SYNONYM) — the driver table (A) containing the global update run headers themselves.

Joins are enforced on item_id equality between the header and the item rows, and on org_id between the header (a.org_id) and the source item (b.org_id), which keeps the view operating-unit aware. Older synonyms for IGI_RPI_ITEMS_ALL may be used for backward compatibility.

Key Columns

  • row_id — the ROWID of the underlying header row, useful for direct row addressing.
  • run_id — identifier of the global update run to which this header belongs.
  • item_id_from / item_code_from — the source item affected by the update.
  • item_id_to / item_code_to — the target item to which the price is applied.
  • effective_date — the date from which the updated price takes effect.
  • option_flag — the raw lookup code for the update option; update_option is its decoded meaning from GLOBAL_UPDATE_OPTION.
  • amount and percentage_amount — the absolute amount or percentage applied by the update, depending on the option.
  • incr_decr_flag — indicates whether the update increments or decrements the existing price.
  • status — the raw lookup code for the update status; update_status is its decoded meaning from GLOBAL_UPDATE_STATUS (this is the field relevant to the global_update_status search).
  • process_id — identifies the concurrent request or process that executed the update.
  • org_id — the operating unit that owns the header.
  • Standard WHO audit columns: creation_date, last_update_date, last_updated_by, last_update_login, created_by.

Common Use Cases and Queries

Typical use cases include monitoring the progress and outcome of global price updates, auditing who changed prices and when, exporting update runs to an external pricing system, and diagnosing items that failed to update. A common query lists all updates for a given run with decoded statuses:

  • SELECT run_id, item_code_from, item_code_to, effective_date, update_option, update_status, amount, percentage_amount, incr_decr_flag FROM apps.igi_rpi_update_hdr_v WHERE run_id = :p_run_id ORDER BY creation_date;
  • SELECT item_code_from, item_code_to, update_status FROM apps.igi_rpi_update_hdr_v WHERE org_id = :p_org_id AND update_status = 'Error';
  • SELECT run_id, COUNT(*) FROM apps.igi_rpi_update_hdr_v WHERE effective_date >= :p_from_date GROUP BY run_id;

Because the view performs lookup decoding and item code resolution at query time, it should be filtered by run_id, org_id, or effective_date for performance. It is read-only in intent and should not be used as a DML target.