Search Results igi_iac_exceptions




Overview

IGI_IAC_EXCEPTIONS is a transactional table owned by the IGI schema within Oracle E-Business Suite, delivered as part of the IGI – Public Sector Financials International product. Its documented purpose is to hold the assets that fall under exception conditions at the time a revaluation is performed. In public sector deployments that rely on the IGI asset revaluation and inflation accounting functionality, this table acts as an error and exception log: rather than silently skipping an asset or aborting the revaluation run, the process records the offending asset along with a message describing the condition that prevented normal processing.

From a Data Vault modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. The table is keyed primarily to a revaluation event and carries descriptive attributes about the exception; it is best treated as a dependent descriptive structure rather than an independent hub. This is a modeling suggestion only, since the physical implementation is a conventional relational table.

Key Information Stored

The documented physical schema contains ten columns. The most significant are:

  • REVALUATION_ID – The foreign key to the parent revaluation run (IGI_IAC_EXCEPTIONS.REVALUATION_ID). This ties each exception row to the specific revaluation execution that generated it and is the principal business-key candidate for joining back to the revaluation header.
  • ASSET_ID – Identifies the individual asset that triggered the exception condition.
  • CATEGORY_ID – The asset category of the affected asset, useful for grouping exceptions by class of asset.
  • BOOK_TYPE_CODE – The depreciation book in which the asset resides, allowing exceptions to be analyzed per book.
  • EXCEPTION_MESSAGE – Free-text description of the exception condition encountered during revaluation. This is the primary diagnostic payload of the table.
  • Audit columnsCREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, LAST_UPDATED_BY. These capture standard EBS who/when audit information for troubleshooting and compliance.

The metadata does not document an explicit surrogate primary key or unique index; the natural business key is effectively the combination of REVALUATION_ID and ASSET_ID, which uniquely identifies an asset's exception within a given run.

Common Use Cases and Queries

The most common use is post-run reconciliation: after a revaluation completes, users query this table to identify which assets failed or were flagged, and why. A typical pattern lists exceptions for a specific revaluation:

  • SELECT asset_id, category_id, book_type_code, exception_message FROM igi.igi_iac_exceptions WHERE revaluation_id = :p_revaluation_id;
  • Count exceptions by book or category to gauge the scope of the problem.
  • Join to the revaluation header (via REVALUATION_ID) to obtain run date and parameters.

Reporting use cases include exception dashboards, trend analysis of recurring exception messages across multiple revaluation periods, and audit evidence demonstrating that flagged assets were investigated and resolved. Because EXCEPTION_MESSAGE is free text, grouping by message prefix is a practical way to categorize exception types.

Related Objects

  • Parent revaluation table (via REVALUATION_ID) – The header table that defines each revaluation run; this is the documented foreign key target.
  • Asset master (via ASSET_ID) – Provides asset description, tag number, and status for the flagged asset.
  • Asset categories (via CATEGORY_ID) – Supplies category names for grouping exceptions.
  • Book controls (via BOOK_TYPE_CODE) – Identifies the depreciation book and its accounting rules.
  • IGI revaluation and inflation accounting process tables – The batch routines that populate IGI_IAC_EXCEPTIONS during execution.

Because the ETRM metadata is limited, joins beyond REVALUATION_ID should be validated against the actual IGI data model in the target instance before being used in production reporting.