Search Results igi_iac_projections




Overview
Explore in AI Chat

Overview

IGI.IGI_IAC_PROJECTIONS is a table within the IGI – Public Sector Financials International product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information about Asset Depreciation Projections, allowing organizations to model and retain projected depreciation results for assets before those results are posted to the general ledger. The object is owned by the IGI schema and holds a documented total of twelve columns.

From a data-modeling perspective, the metadata classifies this object as standalone under Data Vault heuristics. This suggests it may be modeled as an independent hub or satellite rather than a link table, since no foreign keys originate from it to other tables. The classification is a heuristic derived from FK structure and should be treated as a modeling suggestion rather than a strict architectural designation.

Key Information Stored

The most significant columns in IGI_IAC_PROJECTIONS are:

  • PROJECTION_ID – Surrogate primary key, defined by the constraint GI_IAC_PROJECTION. It uniquely identifies each depreciation projection record and is the column most frequently referenced by external consumers.
  • BOOK_TYPE_CODE – Identifies the depreciation book (for example, a corporate or tax book) against which the projection is calculated.
  • START_PERIOD_COUNTER – Indicates the beginning accounting period, expressed as a period counter, for the projection horizon.
  • END_PERIOD – Marks the final period included in the projection.
  • CATEGORY_ID – References the asset category whose depreciation behavior is being projected.
  • REVALUATION_PERIOD – Captures the period associated with a revaluation event influencing projected depreciation.
  • STATUS – Represents the lifecycle state of the projection record (for example, whether it is active or complete).
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Oracle WHO-column audit attributes recording record creation and modification.

Only PROJECTION_ID is documented as the primary key. No unique indexes beyond the primary key are documented in the supplied metadata, so no additional business-key candidates can be confirmed from ETRM alone.

Common Use Cases and Queries

Typical scenarios involve retrieving, comparing, or reconciling projected depreciation for a given book, category, or period range. A representative query is:

  • Retrieve a projection header by primary key:
    SELECT * FROM IGI.IGI_IAC_PROJECTIONS WHERE PROJECTION_ID = :p_id;
  • List projections for a book and period range:
    SELECT PROJECTION_ID, BOOK_TYPE_CODE, START_PERIOD_COUNTER, END_PERIOD, STATUS FROM IGI.IGI_IAC_PROJECTIONS WHERE BOOK_TYPE_CODE = :book AND END_PERIOD BETWEEN :from_p AND :to_p;
  • Filter by asset category and status:
    SELECT PROJECTION_ID, CATEGORY_ID, REVALUATION_PERIOD FROM IGI.IGI_IAC_PROJECTIONS WHERE CATEGORY_ID = :cat AND STATUS = 'ACTIVE';

These patterns support reporting on projected depreciation, auditing prior projection runs, and validating revaluation impacts before posting.

Related Objects

Although IGI_IAC_PROJECTIONS is classified as standalone, the documented FK metadata shows the following tables referencing PROJECTION_ID:

  • BSC_DB_TABLES_COLS – references PROJECTION_ID from IGI_IAC_PROJECTIONS; used in balanced-scorecard style metadata repositories.
  • BSC_DB_MEASURE_COLS_TL – references PROJECTION_ID; associates projection identifiers with translatable measure columns.
  • IGI_IAC_PROJECTIONS itself is joined on PROJECTION_ID when linking header rows to downstream detail consumers.

Additionally, related IGI asset-projection and asset-depreciation objects (such as those keyed by BOOK_TYPE_CODE and CATEGORY_ID) provide context for joins when reporting across the depreciation-projection domain. The two BSC tables represent the primary documented dependents.