Search Results balancing_or_cost_center

Overview

FII.FII_FINANCIAL_DIMENSIONS is a configuration table in the Financials Intelligence (FII) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. Each row corresponds to a single financial dimension — a segment of the Accounting Flexfield used for reporting and analysis — and carries the system-level settings that govern how that dimension behaves within Financials Intelligence, Daily Business Intelligence (DBI), and related analytical engines. The table stores no transactional balances; it is a seed and control table residing in the APPS_TS_SEED tablespace, which confirms its role as reference data populated during setup rather than at runtime.

The heuristic Data Vault classification returned for this object is standalone. In modeling terms, this suggests treating FII_FINANCIAL_DIMENSIONS as a small reference or dimension hub rather than a link or satellite. The unique key DIMENSION_SHORT_NAME acts as a natural business key, and the surrounding attribute columns (enabled flags, hierarchy configuration, and the balancing/cost center mapping) behave as descriptive attributes that could be staged as a satellite if a formal Data Vault model were applied.

Key Information Stored

The primary key is FII_FINANCIAL_DIMENSIONS_PK, defined on DIMENSION_SHORT_NAME (VARCHAR2(30)). A unique index, FII_FINANCIAL_DIMENSIONS_U1, is also defined on the same column, making DIMENSION_SHORT_NAME the sole business-key candidate and the primary join predicate for nearly all downstream queries. The most significant columns are:

• DIMENSION_SHORT_NAME — the financial dimension identifier; the primary key and the value referenced by dependent objects.
• SYSTEM_ENABLED_FLAG — indicates whether the dimension is enabled at the system level.
• DBI_ENABLED_FLAG — indicates whether the dimension is exposed to Daily Business Intelligence.
• INCL_MASTER_VS_LEAF_NODES_FLAG — controls whether leaf-level nodes from the master value set are included in the hierarchy.
• MASTER_VALUE_SET_ID — the flexfield value set identifier that anchors the dimension's hierarchy.
• DBI_HIER_TOP_NODE and DBI_HIER_TOP_NODE_ID — the top node of the DBI hierarchy, stored both as a display value and as a flexfield segment value identifier.
• BALANCING_OR_COST_CENTER — records whether the dimension is mapped to a balancing segment or a cost center segment, the attribute most directly relevant to the user's search.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns, useful for change tracking and reconciliation of configuration drift across environments.

Common Use Cases and Queries

Typical usage centers on confirming which dimensions are active and how they are classified before building reports or reconciling Financials Intelligence output.

• Listing all enabled dimensions: SELECT DIMENSION_SHORT_NAME FROM FII.FII_FINANCIAL_DIMENSIONS WHERE SYSTEM_ENABLED_FLAG = 'Y';
• Identifying balancing versus cost center mappings: SELECT DIMENSION_SHORT_NAME, BALANCING_OR_COST_CENTER FROM FII.FII_FINANCIAL_DIMENSIONS WHERE BALANCING_OR_COST_CENTER IS NOT NULL;
• Auditing DBI exposure and hierarchy roots: SELECT DIMENSION_SHORT_NAME, DBI_ENABLED_FLAG, DBI_HIER_TOP_NODE FROM FII.FII_FINANCIAL_DIMENSIONS WHERE DBI_ENABLED_FLAG = 'Y';
• Reconciling configuration between instances by comparing LAST_UPDATE_DATE against the WHO columns.

Related Objects

The documented relationship data classifies this object as standalone, with no foreign keys to external tables recorded. The following objects are the most significant conceptual dependents, joined via DIMENSION_SHORT_NAME:

• FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — joined through MASTER_VALUE_SET_ID to resolve the dimension's value set.
• FND_SEGMENT_ATTRIBUTES — carries the balancing and cost center flags at the segment level, aligned with BALANCING_OR_COST_CENTER.
• FII Financials Intelligence fact and summary objects — consume DIMENSION_SHORT_NAME when constructing analytical output.
• DBI reporting views — rely on DBI_ENABLED_FLAG and DBI_HIER_TOP_NODE_ID to resolve hierarchy roots.
• GL_JE_SEGMENT_VALUES / GL_CODE_COMBINATIONS — the transactional sources whose segments correspond to the configured dimensions.

Because the table is seed data, any modification should be performed through the supported Financials Intelligence configuration flows rather than direct DML.