Search Results igi_itr_charge_ranges_tmp




Overview
Explore in AI Chat

Overview

IGI_ITR_CHARGE_RANGES_TMP is a temporary staging table within the IGI (Public Sector Financials International) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. According to the ETRM documentation, the table "contains user defined accounting ranges." It serves as a transient work area where accounting segment ranges entered or imported by users are held before validation and final commitment to the permanent IGI_ITR_CHARGE_RANGES table. This staging pattern is common in the IGI inter-agency/intertransaction (ITR) charging framework, where charge ranges define the low and high boundaries of accounting flexfield segments used to determine applicable charge rules.

From a heuristic Data Vault modeling perspective, this object is best classified as a satellite. It holds descriptive range attributes (segment boundary values, flags, audit columns) that describe a business concept keyed by CHARGE_RANGE_ID, rather than acting as an independent hub or a many-to-many link. Consistent with its name suffix "_TMP," the table is populated and consumed within transactional processing and is not intended as a durable system of record.

Key Information Stored

The documented physical schema exposes 70 columns. The most significant are:

No unique index or non-surrogate business-key index is documented beyond the foreign-key relationships; CHARGE_RANGE_ID is the primary reference point.

Common Use Cases and Queries

Typical scenarios include batch loading of accounting ranges, pre-validation before commit into IGI_ITR_CHARGE_RANGES, and reconciliation reporting on staged versus committed ranges. A representative query joining the staging table to its master:

  • SELECT t.charge_range_id, t.charge_center_id, t.segment1_low, t.segment1_high, t.active_flag FROM igi_itr_charge_ranges_tmp t WHERE t.active_flag = 'Y';
  • Join to validate ownership: SELECT t.*, c.* FROM igi_itr_charge_ranges_tmp t, igi_itr_charge_center c WHERE t.charge_center_id = c.charge_center_id;
  • Reconcile staged against committed: join igi_itr_charge_ranges_tmp to igi_itr_charge_ranges on charge_range_id to detect unmatched or orphaned ranges.

Because rows are transient, purge and truncate procedures are commonly applied between processing cycles.

Related Objects

The documented foreign keys and the table's role identify the following significant related objects:

  • IGI_ITR_CHARGE_RANGES — joined via CHARGE_RANGE_ID; the permanent destination for validated ranges.
  • IGI_ITR_CHARGE_CENTER — joined via CHARGE_CENTER_ID; supplies charge center context.
  • PSB_EMPLOYEES — joined via EMPLOYEE_ID; provides employee and authoriser reference data.
  • Standard EBS audit object relationships implied by CREATED_BY and LAST_UPDATED_BY.