Search Results user_dim10_id




Overview
Explore in AI Chat

Overview

APPS.GCS_FEM_ACTIVE_DIMS_V is a metadata view in Oracle E-Business Suite that exposes the set of dimension columns actively enabled as processing keys on the FEM_BALANCES table. It is part of the Enterprise Tax, Regulatory and Reporting Management (ETRM / Financial Consolidation Hub) schema owned by GCS. Rather than storing balances or transactional data, the view returns configuration information: for each dimension column on FEM_BALANCES that has been designated a processing key, it returns the translated display name, the physical column name, and a numeric ordering value used to sequence the dimension when it is presented to end users or consumed by processing logic.

Its reporting and integration role is that of a discovery mechanism. Downstream reports, extracts, and custom integrations that need to enumerate the active dimensions of the FEM_BALANCES model — rather than hardcode them — can query this view to obtain a language-sensitive, correctly ordered list. The column ordering is derived from the DECODE expression, which maps selected dimensions to fixed ordinals while assigning all remaining dimensions the default order 3.

Underlying Base Objects

The view is defined over two documented base objects:

The join is further constrained by TABLE_NAME = 'FEM_BALANCES' and LANGUAGE = USERENV('LANG'), so each row is filtered both to the balances table and to the session's language. The IN list explicitly enumerates the twenty columns eligible to appear, including the standard dimensions (CHANNEL_ID, CUSTOMER_ID, NATURAL_ACCOUNT_ID, PRODUCT_ID, PROJECT_ID, TASK_ID, FINANCIAL_ELEM_ID) and the USER_DIM1_ID through USER_DIM10_ID generic slots.

Key Columns

  • DISPLAY_NAME — the user-facing, language-translated label for the dimension, suitable for report headers and LOVs.
  • COLUMN_NAME — the physical column identifier on FEM_BALANCES, required when constructing dynamic SQL.
  • COLUMN_ORDER — a derived integer used for sorting and presentation. COMPANY_COST_CENTER_ORG_ID returns 1; LINE_ITEM_ID returns 2; USER_DIM10_ID returns 4; INTERCOMPANY_ID returns 5; and all other listed dimensions return the default 3.

The USER_DIM10_ID value of 4 reflects its fixed position in the DECODE mapping, distinguishing the tenth user dimension — and INTERCOMPANY_ID, which follows it — from the bulk of the standard dimensions.

Common Use Cases and Queries

A frequent requirement is to determine how the user dimensions are sequenced within the active dimension set, which is the context in which USER_DIM10_ID is typically searched. The following query returns the ordered dimension list:

  • SELECT display_name, column_name, column_order FROM apps.gcs_fem_active_dims_v ORDER BY column_order, column_name;
  • SELECT column_name, column_order FROM apps.gcs_fem_active_dims_v WHERE column_name = 'USER_DIM10_ID'; — confirms the ordinal 4 assigned to this dimension.
  • SELECT display_name FROM apps.gcs_fem_active_dims_v WHERE column_name LIKE 'USER_DIM%' ORDER BY column_order;

These queries are commonly embedded in dynamic balance-extraction routines, dimension-driven report generators, and validation scripts that verify FEM_BALANCES processing key configuration before a consolidation run. Because results depend on USERENV('LANG') and on the enabled PROCESSING_KEY property, the view always reflects the current configuration of the balances model in the given session language.