Search Results igi_itr_charge_ranges_u1

Overview

The IGI.IGI_ITR_CHARGE_RANGES table is a core configuration table within the Oracle E-Business Suite Internal Trading (ITR) module, used to store the Accounting Flexfield ranges defined by users when setting up internal trading charge centers. It corresponds directly to the Account Ranges region in the Define Internal Trading Charge Centers window, and forms the backbone of the rule-matching logic that determines how intercompany and intragroup charges are calculated and distributed across legal entities, business units, and cost centers.

Under the Data Vault classification heuristic mined from its foreign key structure, this object is characterized as satellite-leaning. In practice, this means IGI_ITR_CHARGE_RANGES behaves as a descriptive satellite attached to the IGI_ITR_CHARGE_CENTER hub. The table does not define independent business events; rather, it enriches a charge center with detailed range definitions that describe which accounting segment combinations are subject to that center's charge rules. Modeling this as a satellite keyed on CHARGE_RANGE_ID, with a functional dependency to CHARGE_CENTER_ID, aligns with the natural parent-child relationship observed in the documented schema. The table is stored in the APPS_TS_TX_DATA tablespace with a PCT FREE of 10 and is owned by the IGI schema. Its status is VALID in both 12.1.1 and 12.2.2 releases.

Key Information Stored

The table contains seventy documented columns. The most significant are summarized below.

• CHARGE_RANGE_ID — the surrogate primary key, a NUMBER(15) that uniquely identifies each range record. It is enforced by the unique index IGI_ITR_CHARGE_RANGES_U1 on APPS_TS_TX_IDX, which is the business-key candidate referenced in ETRM documentation and the object searched as igi_itr_charge_ranges_u1.
• CHARGE_CENTER_ID — a NUMBER(15) foreign key to IGI_ITR_CHARGE_CENTER, linking each range to its owning charge center.
• SEGMENT1_LOW through SEGMENT30_LOW and SEGMENT1_HIGH through SEGMENT30_HIGH — thirty pairs of VARCHAR2(30) columns that hold the low and high bounds of each Accounting Flexfield segment range. These columns support flexible key flexfield configurations with up to thirty segments.
• EMPLOYEE_ID — a foreign key to PSB_EMPLOYEES, identifying the employee associated with the range authorization.
• AUTHORISER_ID — the identifier of the user who authorized the range definition.
• ACTIVE_FLAG — indicates whether the range is currently enabled for charge processing.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS WHO columns that capture audit and concurrency information.

Common Use Cases and Queries

Typical usage focuses on retrieving and validating the accounting ranges assigned to a charge center. A frequent reporting query joins the range table back to the charge center to display all ranges for a given center:

SELECT r.charge_range_id, r.charge_center_id, r.segment1_low, r.segment1_high, r.active_flag FROM igi.igi_itr_charge_ranges r WHERE r.charge_center_id = :charge_center_id AND NVL(r.active_flag, 'Y') = 'Y';

Another common scenario validates whether a given accounting combination falls within any defined range, supporting charge calculation and reconciliation reporting. Interfaces that load charge centers into IGI_ITR_CHARGE_RANGES_TMP and IGI_ITR_CHARGE_LINES_TMP rely on the primary key relationship to resolve the CHARGE_RANGE_ID during import and processing. Reconciliation reports often join to IGI_ITR_CHARGE_LINES to confirm that generated charge lines map to defined ranges.

Related Objects

• IGI.IGI_ITR_CHARGE_CENTER — parent of the charge center definition; joined via CHARGE_CENTER_ID.
• PSB_EMPLOYEES — source of the EMPLOYEE_ID reference.
• IGI.IGI_ITR_CHARGE_LINES — stores generated charge lines and references CHARGE_RANGE_ID as a foreign key.
• IGI.IGI_ITR_CHARGE_RANGES_TMP — temporary staging table that references CHARGE_RANGE_ID and is used during data loading.
• IGI.IGI_ITR_CHARGE_LINES_TMP — staging counterpart for charge lines, also referencing CHARGE_RANGE_ID.

Together these objects form the internal trading charge configuration and processing chain, with IGI_ITR_CHARGE_RANGES providing the segment mapping rules that drive downstream charge line generation.