Search Results igi_itr_charge_lines_audit




Overview
Explore in AI Chat

Overview

The IGI.IGI_ITR_CHARGE_LINES_AUDIT table is a standalone audit table within the IGI — Public Sector Financials International product family of Oracle E-Business Suite (available in 12.1.1 and 12.2.2). As documented in the ETRM metadata, its stated purpose is to "hold details of deleted charge lines." It therefore acts as a historical record for charge lines that have been removed from the primary IGI_ITR_CHARGE_LINES processing table, preserving the financial and descriptive attributes of each deleted row so that expenditures, encumbrances, and GL postings can still be traced.

The metadata records a heuristic Data Vault classification of standalone. In Data Vault modeling terms this suggests the table behaves less like a pure hub (which would hold only a business key) or a pure satellite (which would hold descriptive attributes against a parent hub), and more like a self-contained record. Because it retains a composite identity and descriptors, it is best treated as a satellite-style audit store whose grain is one deleted charge line, keyed by ITR_AUDIT_LINE_ID and its parent header context.

Key Information Stored

The table documents 36 columns. The most significant for identification, tracing, and financial reconciliation include:

The composite of IT_HEADER_ID plus IT_LINE_NUM, or the standalone ITR_AUDIT_LINE_ID, defines the uniqueness of each archived record.

Common Use Cases and Queries

Typical scenarios include investigating why a charge line disappeared from the live processing view, reconstructing amounts for a reconciliation, and auditing encumbrance reversals. A representative pattern is:

  • Retrieve all deleted lines for a given header: SELECT * FROM igi.igi_itr_charge_lines_audit WHERE it_header_id = :p_header;
  • Trace deleted amounts by charge center and ledger: SELECT charge_center_id, set_of_books_id, SUM(entered_dr) FROM igi.igi_itr_charge_lines_audit GROUP BY charge_center_id, set_of_books_id;
  • Reconcile against encumbrances using ENCUMBERED_AMOUNT, UNENCUMBERED_AMOUNT, and GL_ENCUMBERED_PERIOD_NAME.

These queries support period-close review and internal audit reporting.

Related Objects

The documented foreign keys tie this table to the charge processing model:

  • IGI_ITR_CHARGE_HEADERS — joined via IT_HEADER_ID, providing the parent header context.
  • IGI_ITR_CHARGE_CENTER — joined via CHARGE_CENTER_ID, identifying the cost center.
  • IGI_ITR_CHARGE_LINES — the live processing table from which rows are archived; implied source of the deleted records.
  • IGI_ITR_CHARGE_SERVICE — referenced through CHARGE_SERVICE_ID for service linkage.
  • GL_JE_HEADERS / GL_JE_LINES — referenced through JE_HEADER_ID for journal entry traceability.

Collectively these associations preserve the full financial and budgetary lineage of each deleted charge line.