Search Results processing_key




Overview
Explore in AI Chat

Overview

The view APPS.GCS_ACTIVE_DIMS_V is a metadata-driven dictionary view used within the Oracle E-Business Suite Financials and Enterprise Treasury/ETRM (Enterprise Tax, Treasury, and Risk Management) data model. It exposes the set of dimension columns on the FEM_BALANCES table that are flagged with the PROCESSING_KEY property and that are active for a specific application group. In Oracle EBS 12.1.1 and 12.2.2, this view functions as a configuration lookup that tells processing routines which dimension columns participate in balance processing (calculation, aggregation, and transfer) for the application group identified by ID 266.

Rather than returning financial balance data itself, the view returns descriptive metadata: the display name and column name of each qualifying dimension, plus a computed ordering value. This makes it a foundational reference for dynamic SQL generation, flexfield-style dimension handling, and any component that must iterate over the active dimensional model without hard-coding column lists.

Underlying Base Objects

The view is defined over two documented base objects, joined on table and column name:

An anti-join against FEM_APP_GRP_COL_EXCLSNS removes columns that are explicitly excluded for application group 266. A hard-coded IN list further restricts results to the recognized dimension set (CHANNEL_ID, COMPANY_COST_CENTER_ORG_ID, CUSTOMER_ID, FINANCIAL_ELEM_ID, INTERCOMPANY_ID, LINE_ITEM_ID, NATURAL_ACCOUNT_ID, PRODUCT_ID, PROJECT_ID, TASK_ID, and USER_DIM1_ID through USER_DIM10_ID).

Key Columns

  • DISPLAY_NAME — the user-facing, language-translated label of the dimension.
  • COLUMN_NAME — the physical column on FEM_BALANCES representing the dimension.
  • COLUMN_ORDER — a DECODE-derived sort rank that pins specific dimensions to fixed positions: COMPANY_COST_CENTER_ORG_ID = 1, LINE_ITEM_ID = 2, USER_DIM10_ID = 4, INTERCOMPANY_ID = 5, and all others default to 3.

Common Use Cases and Queries

Because the user search referenced processing_key, this view is most relevant when diagnosing which dimensions are treated as active processing keys. Typical scenarios include validating dimension configuration before running balance processes, replicating the active dimension list in custom reports, and troubleshooting excluded columns.

A representative query that mirrors the view's intent:

  • SELECT display_name, column_name, column_order FROM apps.gcs_active_dims_v ORDER BY column_order, column_name;
  • To inspect which dimension qualifies as a processing key, join back to FEM_TAB_COLUMN_PROP on column_name and filter column_property_code = 'PROCESSING_KEY'.

The view is therefore best understood as a configuration companion to the FEM_BALANCES fact table, not a transactional source.