Search Results igi_itr_charge_lines




Overview
Explore in AI Chat

Overview

IGI_ITR_CHARGE_LINES is a transactional table in the IGI (Public Sector Financials International) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual charge line records that make up an interagency transfer (ITR) charge document, capturing the accounting distribution, amount, encumbrance posture, and processing status of each line. The table is owned by the IGI schema and holds 43 documented columns in the 12.2.2 ETRM physical schema. Each row represents one charge line belonging to a parent charge header, and the table serves as the operational detail layer behind the IGI interagency billing and chargeback workflow.

Under the heuristic Data Vault classification derived from the foreign key structure, this object is best modeled as a link table. It resolves relationships between the parent charge header, the charge center, the charge range, accounting code combinations, and service identifiers, rather than acting as a standalone hub of business entities. Modelers should treat it as an intersection of those referenced dimensions and hubs.

Key Information Stored

The primary key is defined by the unique index IGI_ITR_CHARGE_LINES_PK, composed of IT_HEADER_ID and IT_LINE_NUM. IT_HEADER_ID is both a business-key candidate and a foreign key to the charge header, while IT_LINE_NUM provides the line sequence within that header. Together they form the natural identity of a charge line; there is no separate surrogate key column.

The most significant columns include:

Common Use Cases and Queries

Typical reporting retrieves charge lines for a given header, balances debits and credits, and reconciles encumbrance versus posted amounts. A representative query pattern:

  • SELECT it_line_num, entered_dr, entered_cred, status_flag FROM igi_itr_charge_lines WHERE it_header_id = :header_id ORDER BY it_line_num;
  • Aggregate by code combination to produce distribution reports: SELECT code_combination_id, SUM(entered_dr), SUM(entered_cr) FROM igi_itr_charge_lines GROUP BY code_combination_id;
  • Encumbrance reconciliation: filter on encumbrance_flag and compare encumbered_amount to unencumbered_amount.
  • Posting audit: join on posting_flag and je_header_id to trace lines that generated journal entries.
  • Rejection analysis: query rejection_note where status_flag indicates a rejected line.

Related Objects

The table participates in several documented foreign key relationships and depends on the following significant objects:

  • IGI_ITR_CHARGE_HEADERS – joined via IGI_ITR_CHARGE_LINES.IT_HEADER_ID; the parent document.
  • IGI_ITR_CHARGE_CENTER – joined via CHARGE_CENTER_ID.
  • IGI_ITR_CHARGE_RANGES – joined via CHARGE_RANGE_ID.
  • GL_CODE_COMBINATIONS – referenced through CODE_COMBINATION_ID for accounting validation.
  • GL_JE_HEADERS – referenced through JE_HEADER_ID for journal entry linkage.
  • IGI interagency billing APIs and concurrent programs that populate and post charge lines depend on this table as their primary detail store.

In EBS 12.1.1 and 12.2.2, referential integrity is enforced by the documented FK constraints, and the composite primary key guarantees one row per header and line number combination.