Search Results igi_itr_charge_center




Overview
Explore in AI Chat

Overview

IGI_ITR_CHARGE_CENTER is a table within the IGI (Public Sector Financials International) product family in Oracle E-Business Suite, available across 12.1.1 and 12.2.2 releases. The table stores user-defined charge center definitions, which serve as the organizational anchor for charge calculation, distribution, and recovery processing performed by the Intercompany Transaction and Recovery (ITR) functionality. In practice, a charge center represents a business entity, cost pool, or departmental grouping against which charges are accumulated and subsequently distributed to origin or service accounts.

The object holds a VALID status in the IGI schema and exposes eleven documented columns. Because it carries the charge center surrogate key referenced by numerous downstream transactional tables, the ETRM metadata classifies it heuristically as a hub-leaning object in a Data Vault style model. This is a modeling suggestion rather than a physical constraint: it encourages implementers extracting ITR data into a warehouse to treat IGI_ITR_CHARGE_CENTER as a durable business hub, with the charge center identifier serving as the natural business key around which satellites of descriptive and transactional attributes are arranged.

Key Information Stored

The table is organized around a single-column surrogate primary key, CHARGE_CENTER_ID, which is enforced by the unique index IGI_ITR_CHARGE_CENTER_PK. Every foreign-key relationship documented for this table targets this column, confirming it as the sole join discriminator.

The principal descriptive attributes are:

  • CHARGE_CENTER_ID — surrogate primary key and business-key candidate; the value propagated to all dependent ITR tables.
  • NAME — the user-defined charge center name presented in ITR setup and inquiry forms.
  • DESCRIPTION — free-form supplementary text describing the purpose of the charge center.
  • SET_OF_BOOKS_ID — the ledger context to which the charge center belongs, enabling multi-ledger deployments.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective dating window that governs when a charge center may participate in charge calculation.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — the standard Oracle Applications who-columns providing audit traceability for insertion and maintenance.

The effective dating attributes are particularly significant because ITR charge runs select charge centers whose active window covers the transaction date, so date integrity directly affects the correctness of calculated charges.

Common Use Cases and Queries

Typical reporting and integration scenarios include listing active charge centers for a given ledger, validating charge center lifecycle dates, and joining charge center definitions to their downstream transactional records. A representative query pattern is:

  • SELECT charge_center_id, name, description, set_of_books_id, start_date_active, end_date_active FROM igi.igi_itr_charge_center WHERE set_of_books_id = :p_ledger AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE)+1) ORDER BY name;
  • Join to headers and lines for charge run reporting: SELECT h.charge_center_id, c.name, h.charge_header_id, l.amount FROM igi_itr_charge_headers h, igi_itr_charge_center c, igi_itr_charge_lines l WHERE h.charge_center_id = c.charge_center_id AND l.charge_header_id = h.charge_header_id;
  • Reconciliation of service definitions per charge center: SELECT s.service_id, s.charge_center_id, c.name FROM igi_itr_charge_service s, igi_itr_charge_center c WHERE s.charge_center_id = c.charge_center_id;
  • Audit of recent maintenance activity using the who-columns: SELECT charge_center_id, name, last_updated_by, last_update_date FROM igi.igi_itr_charge_center WHERE last_update_date >= :p_since;

These patterns support charge center setup verification, period-end charge reconciliation, and data migration validation between environments.

Related Objects

IGI_ITR_CHARGE_CENTER is referenced by a wide set of ITR operational and staging tables through the CHARGE_CENTER_ID column. The most significant documented relationships are:

Because every documented foreign key resolves to CHARGE_CENTER_ID, deletion or merge of a charge center record requires coordinated handling of dependent ITR rows to preserve referential integrity.