Results for “fii_dim_mapping_rules”

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

Overview

FII_DIM_MAPPING_RULES is a Financial Intelligence (FII) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the associations between financial dimensions and chart of accounts segments. Each record defines how a dimension — identified by a dimension short name — is resolved against a specific chart of accounts. This mapping is foundational to multidimensional reporting, budgeting, and analysis within FII, because it determines which segment values of a chart of accounts correspond to which dimension members. The table resides in the FII schema, is documented as VALID, and contains 15 physical columns in the ETRM 12.1.1 schema. Its heuristic Data Vault classification is standalone, meaning it is modelled as an independent structure rather than as a hub, link, or satellite. In practice, the composite business key implies that a hub-and-satellite treatment (hub on DIMENSION_SHORT_NAME and CHART_OF_ACCOUNTS_ID, satellite carrying status and mapping attributes) may be a reasonable design alternative, but the documented structure is a flat standalone table.

Key Information Stored

The primary key is FII_DIM_MAPPING_RULES_PK, defined on the composite columns (DIMENSION_SHORT_NAME, CHART_OF_ACCOUNTS_ID). There is no single surrogate column; the natural business key is the composite itself, and it is also enforced by the unique index FII_DIM_MAPPING_RULES_U1 on the same two columns. The most significant columns are:

• DIMENSION_SHORT_NAME — identifies the financial dimension, such as a segment or analysis dimension name. Part of the primary key.
• CHART_OF_ACCOUNTS_ID — foreign reference to the chart of accounts (Accounting Flexfield structure) that the dimension maps to. Part of the primary key.
• STATUS_CODE — status of the dimension mapping rule (for example, active or inactive), controlling whether the mapping is applied.
• MAPPING_TYPE_CODE — determines how the dimension is mapped to a chart of accounts segment.
• APPLICATION_COLUMN_NAME1, APPLICATION_COLUMN_NAME2, APPLICATION_COLUMN_NAME3 — one to three segment/column references targeted by the mapping.
• FLEX_VALUE_SET_ID1, FLEX_VALUE_SET_ID2, FLEX_VALUE_SET_ID3 — the corresponding value sets constraining allowed values for each mapped segment.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns providing audit and concurrency information.

Common Use Cases and Queries

The table is queried primarily when FII needs to resolve a dimension to chart of accounts segments, and when administrators inspect or validate dimension configuration. Typical SQL patterns include:

• Retrieving all active mappings for a chart of accounts: SELECT dimension_short_name, mapping_type_code, status_code FROM fii_dim_mapping_rules WHERE chart_of_accounts_id = :coa_id AND status_code = 'A';
• Resolving segment and value set targets for a dimension: SELECT application_column_name1, flex_value_set_id1 FROM fii_dim_mapping_rules WHERE dimension_short_name = :dim AND chart_of_accounts_id = :coa_id;
• Auditing configuration changes: SELECT dimension_short_name, last_update_date, last_updated_by FROM fii_dim_mapping_rules ORDER BY last_update_date DESC;

These queries support metadata reporting, setup validation, and troubleshooting when dimension values fail to map correctly during reporting or data load.

Related Objects

The documented FK structure classifies this table as standalone, so no enforced foreign keys are declared in the metadata. Nonetheless, the following objects are the most significant logical dependents and references, joined through the documented key columns:

• FND_ID_FLEX_STRUCTURES — joined on CHART_OF_ACCOUNTS_ID (ID_FLEX_NUM) to identify the chart of accounts.
• FND_ID_FLEX_SEGMENTS — joined on chart of accounts and segment information underlying APPLICATION_COLUMN_NAME1..3.
• FND_FLEX_VALUE_SETS — joined on FLEX_VALUE_SET_ID1..3 to resolve value set definitions.
• FII_DIM_DEFINITIONS (or equivalent dimension definition table) — joined on DIMENSION_SHORT_NAME to resolve the dimension.
• FII financial reporting fact and dimension tables — consume these mapping rules at query and report generation time.

Because no physical foreign keys are documented, referential integrity is enforced at the application layer, and joins should always be validated against the corresponding FND and FII dimension objects.