Results for “igi_eer_setup”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGI_EER_SETUP is a configuration table owned by the IGI schema, the database account associated with the Public Sector Financials International product family in Oracle E-Business Suite. Its documented purpose is to hold details of drill-down setup, meaning it stores the parameters that govern how users navigate from summarized balances or transactions in the IGI reporting framework down to the underlying detail records held elsewhere in the applications. In release 12.1.1 and 12.2.2 the table is delivered as a VALID database object with a documented physical schema of twelve columns.

From a dimensional modeling perspective, the metadata classifies IGI_EER_SETUP as satellite-leaning. This is a heuristic suggestion rather than a delivered Oracle construct: the table behaves as a descriptive attribute store rather than a transactional fact or a pure key-resolution hub. Its rows are configuration descriptors, scoped by a single foreign key to the accounting book, and its level columns describe the attributes of that configuration rather than accumulating measurable events.

Key Information Stored

The documented column list comprises twelve fields. The most significant are described below.

• GL_SET_OF_BOOKS_ID — the only documented foreign key, referencing GL_SETS_OF_BOOKS. This column scopes each drill-down configuration row to a specific accounting book and is the primary business-key candidate for the table, since drill-down behavior is defined per ledger set.
• LEVEL_1 through LEVEL_6 — six positional level columns that describe the ordered drill-down hierarchy. Each level typically carries the identifier of a reporting dimension, account segment, or target object at that position in the navigation path, allowing the setup to define a multi-tier drill sequence.
• CREATION_DATE, CREATED_BY — standard Oracle WHO columns capturing the audit trail for row insertion.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard audit columns maintained by the Oracle Forms and OAF frameworks whenever a configuration row is amended.

No surrogate primary key column is documented in the ETRM metadata for this object; the twelve columns listed contain neither a system-generated ID nor a unique index definition, so uniqueness is most plausibly enforced by a composite of the set-of-books identifier together with the level attributes, or by a database constraint not surfaced in the excerpt.

Common Use Cases and Queries

The principal use case is diagnostic: confirming how drill-down has been configured for a given ledger, or identifying ledgers for which no drill-down setup exists. Because the table is small and configuration-oriented, queries are typically simple lookups.

• Retrieving all drill-down configurations for a ledger:
  SELECT * FROM igi.igi_eer_setup WHERE gl_set_of_books_id = :p_sob_id;
• Identifying ledgers lacking setup, using an outer join or NOT EXISTS against GL_SETS_OF_BOOKS.
• Auditing configuration drift across environments by comparing level column values between instances, or by filtering on LAST_UPDATE_DATE within a migration window.
• Reporting on the number of configured drill levels per book to detect incomplete hierarchies where some of the six level columns are null.

Related Objects

The documented relationship data identifies a single foreign key dependency, which anchors this table to the general ledger foundation.

• GL_SETS_OF_BOOKS — referenced through IGI_EER_SETUP.GL_SET_OF_BOOKS_ID, the definitive join from setup rows to the accounting book definition.
• GL_LEDGERS — the 12.x replacement view over sets of books, commonly joined when resolving ledger name and currency attributes for reporting.
• IGI_EER_SETUP-related IGI reporting objects — the drill-down targets consumed by the EER (Executive/Enterprise Reporting) framework, which read the level columns to determine navigation paths.
• FND_APPLICATION and FND_PRODUCT_INSTALLATIONS — useful in confirming that the IGI product family is installed and licensed in the target instance.

Given the limited documented relationship surface, IGI_EER_SETUP should be treated as a dependent configuration satellite of the accounting book, consulted primarily during implementation, troubleshooting, and environment comparison rather than during high-volume transaction processing.