Search Results option_flag

Overview

IGI_RPI_UPDATE_HDR_V is an APPS-owned database view within the IGI – Public Sector Financials International product family. It presents the header-level data used by the Global Price Update form, which drives mass price revisions across item ranges in Oracle E-Business Suite. The view denormalizes the underlying header table IGI_RPI_UPDATE_HDR by joining it to item master records and to Oracle lookups, so that user-facing values such as item codes and descriptive meanings are returned alongside internal identifiers and flags. Because the Global Price Update form is a concurrent-process-driven feature, the view acts as the read interface between the form's query block and the stored update request records.

The view was originally documented against ETRM 12.1.1 and remains valid in 12.2.2, where its referenced base objects resolve through synonyms (IGI_RPI_ITEMS_ALL, IGI_RPI_UPDATE_HDR) and the shared lookup view IGI_LOOKUPS. A ROWID is exposed as ROW_ID, giving the view a notional key that form blocks and integration routines can use for record identification.

Underlying Base Objects

The view is defined over five referenced objects:

• IGI_RPI_UPDATE_HDR (SYNONYM) — the driving header table holding each global update run, including item ranges, effective dates, update option, status, amount and percentage values.
• IGI_RPI_ITEMS_ALL (SYNONYM) — the item master source, joined twice to resolve the item code at both ends of the range (from and to).
• IGI_LOOKUPS (VIEW) — joined twice against lookup types GLOBAL_UPDATE_OPTION and GLOBAL_UPDATE_STATUS to translate code values into meanings.

All joins are inner equi-joins on lookup code and item ID. Because the lookup joins are mandatory, any header row whose OPTION_FLAG or STATUS value has no corresponding lookup entry will be excluded from the result set. This is a material consideration when troubleshooting missing records.

Key Columns

• ROW_ID — ROWID of the underlying header row; used as the form's pseudo-key.
• RUN_ID / PROCESS_ID — identifiers linking the update request to its submission and concurrent process.
• ITEM_ID_FROM / ITEM_CODE_FROM and ITEM_ID_TO / ITEM_CODE_TO — the item range defining the population targeted by the update.
• EFFECTIVE_DATE — date from which the new prices take effect.
• OPTION_FLAG / UPDATE_OPTION — the update method (for example amount or percentage based), with its translated lookup meaning. This is the column most frequently located by searches on "option_flag".
• AMOUNT / PERCENTAGE_AMOUNT — the magnitude of the change and the indicator of how it is applied.
• INCR_DECR_FLAG — indicates whether the update increments or decrements prices.
• STATUS / UPDATE_STATUS — internal code and translated meaning of the run's processing state.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• ORG_ID — the operating unit that owns the header record, supporting multi-org security.

Common Use Cases and Queries

Typical usage includes reviewing pending or completed global update runs, validating the item range for a submission, and joining run data to processed price lists. A basic query returning translated values is:

SELECT run_id, item_code_from, item_code_to, effective_date, update_option, amount, percentage_amount, incr_decr_flag, update_status, org_id FROM igi_rpi_update_hdr_v ORDER BY creation_date DESC;

To examine runs using a specific update option:

SELECT run_id, item_code_from, item_code_to, update_option, amount, percentage_amount FROM igi_rpi_update_hdr_v WHERE option_flag = 'AMOUNT';

To reconcile header records against the base table, comparing OPTION_FLAG against the D.MEANING update option will quickly identify rows whose lookup code is no longer defined, since those rows are filtered out of the view. Querying ORGANIZATION_ID together with ORG_ID supports operating unit level reporting.