Search Results gcs_fem_active_dims_v

Overview

GCS_FEM_ACTIVE_DIMS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GCS (Financial Consolidation Hub) product. Its documented description is "FEM Active Dimension Information," identifying it as a metadata-driven view over the Enterprise Performance Foundation (FEM) balances model. The view exposes the set of dimension columns that are configured as active processing keys for the FEM_BALANCES table, together with user-facing display names and an explicit sort ordering.

In EBS 12.1.1 and 12.2.2, Financial Consolidation Hub relies on the FEM schema for staging and consolidating balances. Because the physical shape of the balances table can vary by configuration — different dimensions may be enabled as processing keys — this view provides a stable, query-friendly interface that lists only those dimensions currently flagged as processing keys. Reporting and integration components can therefore enumerate active dimensions dynamically rather than hard-coding column names. The view is read-only and is exposed through the standard APPS synonym, permitting direct SQL access from custom reports, concurrent programs, and integration extracts.

Underlying Base Objects

The view is defined over two FEM dictionary tables:

• FEM_TAB_COLUMNS_TL (aliased FTCB) — the translated table/column catalog. It supplies the column identifier (COLUMN_NAME) and the language-specific display name (DISPLAY_NAME) for each balance column.
• FEM_TAB_COLUMN_PROP (aliased FTCP) — the column property table, which carries the classification code applied to each column.

The join is constrained on TABLE_NAME equal to 'FEM_BALANCES' across both tables, on matching COLUMN_NAME, and on an inner selectivity condition restricting the translated rows to the session language via USERENV('LANG'). The decisive filter is FTCP.COLUMN_PROPERTY_CODE = 'PROCESSING_KEY', which restricts output to dimensions designated as processing keys. A final IN list limits the candidate columns to the recognized FEM dimension set — including COMPANY_COST_CENTER_ORG_ID, LINE_ITEM_ID, USER_DIM10_ID, INTERCOMPANY_ID, and the remaining USER_DIM1 through USER_DIM9 columns, plus CHANNEL_ID, CUSTOMER_ID, FINANCIAL_ELEM_ID, NATURAL_ACCOUNT_ID, PRODUCT_ID, PROJECT_ID, and TASK_ID. Because the joins are inner joins, any dimension lacking a translated name, a processing-key property, or the matching language row is excluded from the result.

Key Columns

• DISPLAY_NAME — the user-facing, language-specific label of the dimension as maintained in the FEM column catalog. This is the value suitable for presentation in report headers, consolidation setup screens, and parameter lists.
• COLUMN_NAME — the physical column name on FEM_BALANCES, such as NATURAL_ACCOUNT_ID or COMPANY_COST_CENTER_ORG_ID. This value is used programmatically when dynamic SQL must be constructed against the balances table.
• COLUMN_ORDER — a derived ordinal produced by the DECODE expression, which assigns fixed positions to a subset of dimensions: COMPANY_COST_CENTER_ORG_ID = 1, LINE_ITEM_ID = 2, USER_DIM10_ID = 4, INTERCOMPANY_ID = 5, and all other listed dimensions = 3. The result set is ordered by COLUMN_ORDER and then by COLUMN_NAME, yielding a deterministic, configuration-stable sequence for displaying or iterating dimensions.

Common Use Cases and Queries

Typical uses include rendering the active dimension list on consolidation configuration pages, validating that expected dimensions are enabled as processing keys, and driving dynamic report generation where the balances table is queried by dimension name.

A basic enumeration of active dimensions:

• SELECT column_order, display_name, column_name FROM apps.gcs_fem_active_dims_v ORDER BY column_order, column_name;

To verify whether a specific dimension is an active processing key:

• SELECT display_name FROM apps.gcs_fem_active_dims_v WHERE column_name = 'NATURAL_ACCOUNT_ID';

To build a dynamic column list for a query against FEM_BALANCES, concatenate the COLUMN_NAME values returned by the view. Note that DISPLAY_NAME is language-dependent through USERENV('LANG'), so multilingual environments may return different labels for the same dimension. Access is subject to the standard APPS grants; no base objects outside the two FEM dictionary tables are documented.