Search Results fii_financial_dimensions




Overview
Explore in AI Chat

Overview

The FII_FINANCIAL_DIMENSIONS table belongs to the Oracle Financial Intelligence (FII) product family, an obsolete module that shipped with early Oracle E-Business Suite releases such as 12.1.1 and 12.2.2. In the documented 12.1.1 schema, the table is owned by the FII schema and contains 13 columns. Each row represents a single financial dimension recognized by Financial Intelligence, together with the system-level configuration flags and hierarchy metadata that govern how that dimension is presented, aggregated, and drilled into within the FII reporting engine.

The table serves as a configuration and registration point rather than a transactional store. It records which segments of the Accounting Flexfield are treated as financial dimensions, whether each dimension is enabled, which value set supplies its allowable values, and whether the dimension functions as a balancing segment or cost center. Because the product is flagged as obsolete, the table is listed as "Not implemented in this database" in current ETRM metadata, meaning it persists only in legacy environments where FII was originally deployed or in schemas retained for upgrade and data-migration purposes.

The ETRM metadata classifies FII_FINANCIAL_DIMENSIONS heuristically as a standalone object with no foreign-key relationships mined from the constraint structure. In Data Vault terms, this suggests a hub-like or reference-satellite pattern: the dimension short name behaves as a natural business key, and the remaining attributes record descriptive configuration state for that key. No link tables are documented as connecting this object to other entities.

Key Information Stored

The primary key is FII_FINANCIAL_DIMENSIONS_PK, defined on the single column DIMENSION_SHORT_NAME. A unique index, FII_FINANCIAL_DIMENSIONS_U1, is also defined on DIMENSION_SHORT_NAME, confirming that this column is the business-key candidate and the natural identifier for each dimension.

Common Use Cases and Queries

Because the table is obsolete, practical queries typically arise during upgrade assessment, data archival, or reconciliation of legacy FII configurations. A common pattern is to enumerate all enabled financial dimensions to confirm that configuration migrated correctly to a successor product such as Oracle Hyperion or the modern Financials Essbase integration.

  • Identify dimensions enabled for DBI reporting: SELECT DIMENSION_SHORT_NAME, MASTER_VALUE_SET_ID FROM FII_FINANCIAL_DIMENSIONS WHERE DBI_ENABLED_FLAG = 'Y';
  • Locate dimensions with hierarchy configuration: SELECT DIMENSION_SHORT_NAME, DBI_HIER_TOP_NODE FROM FII_FINANCIAL_DIMENSIONS WHERE DBI_HIER_TOP_NODE IS NOT NULL;
  • Distinguish balancing segments from cost centers using BALANCING_OR_COST_CENTER.
  • Audit recent configuration changes via the LAST_UPDATE_DATE and LAST_UPDATED_BY columns.

Related Objects

The documented metadata records no foreign keys and classifies the table as standalone, so no hard-coded join columns to other tables are supplied. Logical relationships implied by the documented column semantics include:

All relationships are logical rather than enforced, reflecting the standalone classification and the obsolete status of the FII product line.