Search Results igi_itr




Overview
Explore in AI Chat

Overview

IGI_ITR is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. The package forms part of the Oracle Financials for Government / ETRM (Expenditure Tracking and Reporting) product family, and its naming and dependent objects indicate that it manages the submission, validation, and accounting impact of interest-related charge transactions against the General Ledger. In the ETRM context, the IGI_ITR package serves as the integration layer between charge headers and lines held in ETRM-specific tables and the Oracle General Ledger journal import interface.

The package is classified as an OTHER API in the ETRM 12.2.2 metadata. It is not a public, supported extension API in the same sense as the standard Oracle Financials open interfaces; rather, it is invoked internally by concurrent programs and forms to drive the transfer of interest computation results into GL. Its status is VALID, confirming that the compiled object is present and usable in the target environment.

Key Procedures and Functions

The documented package exposes eight procedures and functions:

  • SUBMIT — Initiates the primary processing cycle of the package, typically launching a concurrent request or triggering the batch-oriented transfer of charge data into GL.
  • ACTION — Executes the requested business action against the charge records, acting as a dispatcher for the processing mode requested by the caller.
  • SET_BATCHES — Establishes the journal batch structures that will be populated with the ETRM charge entries prior to journal import.
  • PROCESS_BATCHES — Performs the core processing of the prepared batches, mapping charge headers and lines into GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES, and GL_INTERFACE rows.
  • CONTROL — Manages the control totals and GL_INTERFACE_CONTROL records that govern a journal import run, ensuring that the imported data balances.
  • ACCEPT — Marks charge transactions as accepted for accounting, allowing them to proceed to journal creation.
  • REJECT — Marks charge transactions as rejected, excluding them from further accounting processing.
  • STATUS — Returns or updates the processing status of an ETRM charge record, enabling the caller to determine whether a transaction is pending, accepted, or rejected.

The presence of both ACCEPT and REJECT alongside STATUS confirms that the package operates within a review-and-approval workflow in which interest charge records must be explicitly dispositioned before they reach the general ledger.

Tables Accessed

IGI_ITR reads and writes a defined set of tables through APPS synonyms. The ETRM-specific tables IGI_ITR_CHARGE_HEADERS and IGI_ITR_CHARGE_LINES hold the charge transactions that are the subject of processing. The General Ledger tables GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES, GL_JE_CATEGORIES, and GL_JE_SOURCES provide the journal structures and validation references used when constructing journal entries. GL_INTERFACE and GL_INTERFACE_CONTROL receive the staged journal data and control totals for journal import, while GL_JOURNAL_IMPORT_S is used in the submission of the import concurrent program. DUAL is referenced for standard PL/SQL expression evaluation. The package also depends on FND_REQUEST for concurrent request submission, on IGI_GEN for shared ETRM utility logic, and on STANDARD for standard PL/SQL package references.

Usage Notes

IGI_ITR is a server-side package that is normally invoked by ETRM concurrent programs and Oracle Forms rather than being called directly by end users. The SUBMIT procedure is the typical entry point for batch processing, with FND_REQUEST used to launch the associated concurrent request and GL_JOURNAL_IMPORT_S used to submit journal import. The ACCEPT, REJECT, and STATUS procedures are more likely to be invoked interactively from an ETRM form when a user reviews and dispositions interest charges.

Because the package is classified as OTHER and is a package body with an accompanying specification, customizations should treat it as internal ETRM code. Extension points in ETRM should be preferred over direct modification of this package. The metadata notes that IGI_ITR is referenced by one other package, and the object is not referenced by any further database object, indicating that its usage is confined to the immediate ETRM processing flow. When diagnosing journal creation issues, the GL_INTERFACE and GL_INTERFACE_CONTROL contents produced by this package are the primary evidence available to confirm whether interest charges were correctly staged for General Ledger import.