Results for “gcs_active_dims_v”

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

Overview

The GCS_ACTIVE_DIMS_V view is a dictionary-style reporting object owned by the APPS schema in Oracle E-Business Suite, belonging to the GCS (Financial Consolidation Hub) product family. Its documented description is "FCH Active Dimension Information," indicating that it exposes the set of currently active dimension columns configured for the Financial Consolidation Hub balances table, FEM_BALANCES. In EBS 12.1.1 and 12.2.2, FCH relies on a fixed physical balances table whose columns (natural account, cost center, intercompany, and a series of user-defined dimensions USER_DIM1_ID through USER_DIM10_ID) are enabled or disabled per application group. Rather than hard-code which of these dimensions participate in consolidation, FCH query and integration logic consults GCS_ACTIVE_DIMS_V to discover, at runtime, which dimension columns are active, how they are labeled for display, and in what display order they should appear.

The view therefore plays a supporting role in EBS reporting and integration: it drives dynamic column selection in FCH dashboards, reconciliation reports, and any custom extract that must reflect the currently enabled chart of dimension segments. The user search term user_dim10_id maps directly to this view, since USER_DIM10_ID is one of the dimension columns that the view can return when it is not excluded for the relevant application group.

Underlying Base Objects

The documented view text references two underlying GCS/FEM dictionary tables. The first is FEM_TAB_COLUMNS_TL (aliased FTCB), the translated column registry that supplies DISPLAY_NAME and COLUMN_NAME for the FEM_BALANCES table. The second is FEM_TAB_COLUMN_PROP (aliased FTCP), which carries column-level property codes; the join restricts results to columns whose COLUMN_PROPERTY_CODE equals PROCESSING_KEY.

• FEM_TAB_COLUMNS_TL — stores column metadata and language-specific display names for FCH tables; the join on LANGUAGE = USERENV('LANG') ensures the user's session language is used.
• FEM_TAB_COLUMN_PROP — stores key/value properties for each table column; only processing-key columns qualify.
• FEM_APP_GRP_COL_EXCLSNS — an exclusion table; the NOT EXISTS clause filters out columns explicitly excluded for APPLICATION_GROUP_ID = 266. This is what makes the view "active" rather than merely "defined."

No further base objects are documented in the ETRM metadata; the view is read-only and references only these three dictionary tables.

Key Columns

• DISPLAY_NAME — the language-specific label for the dimension column, used to build report headers and pick lists.
• COLUMN_NAME — the physical column name on FEM_BALANCES, such as FINANCIAL_ELEM_ID, COMPANY_COST_CENTER_ORG_ID, INTERCOMPANY_ID, or USER_DIM10_ID.
• COLUMN_ORDER — a derived sort key produced by a DECODE: COMPANY_COST_CENTER_ORG_ID returns 1, LINE_ITEM_ID returns 2, USER_DIM10_ID returns 4, INTERCOMPANY_ID returns 5, and all remaining dimensions return 3. This governs the sequence in which active dimensions are presented.

The COLUMN_NAME predicate limits output to a fixed whitelist spanning CHANNEL_ID, CUSTOMER_ID, FINANCIAL_ELEM_ID, NATURAL_ACCOUNT_ID, PRODUCT_ID, PROJECT_ID, TASK_ID, and USER_DIM1_ID through USER_DIM10_ID, among others. USER_DIM10_ID specifically appears both in the IN list and in the COLUMN_ORDER DECODE, confirming it is a first-class active dimension when not excluded for the application group.

Common Use Cases and Queries

A typical consumer uses the view to enumerate enabled dimensions before generating dynamic SQL against FEM_BALANCES, or to render a legend of active segments in an FCH report.

• List all active dimensions in display order: SELECT column_name, display_name, column_order FROM apps.gcs_active_dims_v ORDER BY column_order, column_name;
• Determine whether a specific user dimension is active: SELECT column_name FROM apps.gcs_active_dims_v WHERE column_name = 'USER_DIM10_ID'; (No row returned indicates the dimension is excluded or not a processing key.)
• Build a dynamic column list for extraction: iterate the COLUMN_NAME values returned and append them to a SELECT against FEM_BALANCES.
• Validate configuration after a patch or application-group change by comparing the view's output to expected dimension enablements.

Because the view is defined over metadata tables rather than transaction data, it is inexpensive to query and safe to call from concurrent programs, OAF pages, and integration extracts across both 12.1.1 and 12.2.2.