Search Results igi_rpi_update_hdr_all




Overview
Explore in AI Chat

Overview

IGI_RPI_UPDATE_HDR_ALL is a transactional header table within the IGI (Public Sector Financials International) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Per the ETRM metadata, it is owned by the IGI schema with status VALID, and its documented description is "Records global update header information." In practice, this table stores the master control record for a global (mass) update run — the process by which a defined value, amount, or percentage adjustment is propagated across a set of items. Each row represents one update run, identified by RUN_ID, and carries the parameters that drove that run: the item range, the effective date, the option flag, the monetary or percentage adjustment, and the processing status.

The heuristic Data Vault classification mined from the foreign key structure is link. This suggests a modeling interpretation in which the header acts as an associative entity connecting two item references (a "from" item and a "to" item) rather than functioning as a pure reference hub or a descriptive satellite. Analysts designing downstream marts may therefore treat IGI_RPI_UPDATE_HDR_ALL as the junction that resolves the relationship between item endpoints, with the remaining columns supplying run-level context.

Key Information Stored

The table carries sixteen documented columns in the 12.2.2 physical schema. The most significant are:

  • RUN_ID — The surrogate primary key, enforced by IGI_RPI_UPDATE_HDR_PK. It uniquely identifies each global update run and is the join key for all child and audit records.
  • ITEM_ID_FROM — Foreign key to IGI_RPI_ITEMS_ALL, defining the starting (lower-bound) item of the update range.
  • ITEM_ID_TO — Foreign key to IGI_RPI_ITEMS_ALL, defining the ending (upper-bound) item of the update range.
  • EFFECTIVE_DATE — The date from which the update takes effect; drives period-sensitive reporting and revaluation logic.
  • OPTION_FLAG — Governs the mode or variant of the global update applied during the run.
  • AMOUNT and PERCENTAGE_AMOUNT — The absolute value and the percentage-based value to apply, respectively.
  • INCR_DECR_FLAG — Indicates whether the adjustment is an increment or a decrement relative to the existing value.
  • STATUS — The processing state of the run (for example, pending, in progress, or complete).
  • PROCESS_ID — Correlates the header with the concurrent program or batch execution that created it.
  • ORG_ID — The operating unit, supporting multi-org (MOAC) security and partitioned reporting.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified the run.

RUN_ID is the only documented unique identifier and is therefore the surrogate business key for this entity; ITEM_ID_FROM and ITEM_ID_TO are foreign-key candidates rather than business keys in their own right.

Common Use Cases and Queries

Typical scenarios include auditing historical global update runs, reconciling item value changes against the run parameters that produced them, and reporting run volumes by operating unit and effective period. A representative query joins the header to the item definition table to resolve both endpoints of the range:

  • Run history by status and operating unit: select RUN_ID, STATUS, EFFECTIVE_DATE, AMOUNT, PERCENTAGE_AMOUNT from IGI_RPI_UPDATE_HDR_ALL where ORG_ID = :p_org_id order by CREATION_DATE desc.
  • Endpoint resolution: join IGI_RPI_UPDATE_HDR_ALL to IGI_RPI_ITEMS_ALL twice — once on ITEM_ID_FROM and once on ITEM_ID_TO — to display item descriptions for the update range.
  • Adjustment trend analysis: aggregate INCR_DECR_FLAG and OPTION_FLAG counts by EFFECTIVE_DATE to monitor how frequently revaluation versus percentage updates are executed.
  • Process traceability: filter by PROCESS_ID to tie a run back to the concurrent request that generated it.

Related Objects

The FK metadata identifies IGI_RPI_ITEMS_ALL as the principal parent reference for this table, through two distinct columns. The most significant related objects are:

  • IGI_RPI_ITEMS_ALL — Referenced via ITEM_ID_FROM; the item master supplying the lower bound of the update range.
  • IGI_RPI_ITEMS_ALL — Referenced via ITEM_ID_TO; the item master supplying the upper bound of the update range.
  • IGI_RPI_UPDATE_HDR_PK — The primary key constraint on RUN_ID, defining row uniqueness and driving index usage.
  • Child/detail tables keyed on RUN_ID — Any IGI global update detail or line table correlates back to this header through RUN_ID, forming the header-detail pattern typical of EBS batch processes.
  • Concurrent program and request metadata — Linked indirectly through PROCESS_ID, enabling traceability from the run to the executing process.

Because the documentation excerpt is limited to the header and item references, teams should confirm any additional dependent objects directly against the IGI schema in their target instance.