Search Results fii_cost_center_values_v




Overview
Explore in AI Chat

Overview

FII_COST_CENTER_VALUES_V is a database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the FII (Financial Intelligence) product family, which provides the dimensional infrastructure used by Oracle Financial Analytics, Enterprise Performance Management, and related financial reporting integrations. The view exposes the master value set node names and descriptions for the Cost Center dimension. It acts as a presentation-layer join that resolves cost center identifiers held in the FII cost center hierarchy structures to their corresponding descriptive flexfield value definitions registered in the general ledger value set repository. This makes the view suitable for ETL processes that populate a cost center dimension in an external warehouse, for BI Publisher reports requiring readable cost center labels, and for reconciliation queries that compare hierarchy node definitions against the underlying value set entries.

Underlying Base Objects

The view is defined over three documented base objects. FND_FLEX_VALUES_VL is the value-set value view that stores the key flexfield value, its translated description, and related attributes for every registered value set. FII_FINANCIAL_DIMENSIONS identifies the master value set assigned to each FII financial dimension; in this view it is filtered to the dimension whose short name is 'HRI_CL_ORGCC', the cost center dimension. FII_COST_CTR_HIERARCHIES stores the cost center hierarchy definition and supplies the parent cost center identifier and the leaf flag used in the join. The relationship is a join chain: FII_FINANCIAL_DIMENSIONS supplies the master value set identifier that links to FND_FLEX_VALUES_VL, while the value ID is matched to the parent cost center ID in FII_COST_CTR_HIERARCHIES. Because FND_FLEX_VALUES_VL is a translated (VL) view, descriptions returned reflect the language of the current session.

Key Columns

  • ID — the FLEX_VALUE_ID from FND_FLEX_VALUES_VL, uniquely identifying the value set value. This is the primary identifier used to join back to hierarchy or fact tables.
  • VALUE — the flexfield value itself, typically the cost center code (for example, an accounting flexfield segment value) as stored in the value set.
  • DESCRIPTION — the translated description of the cost center value, providing the human-readable label for the dimension node.
  • IS_LEAF_FLAG — copied from FII_COST_CTR_HIERARCHIES, indicating whether the node is a leaf (detail) cost center or an aggregate parent node in the hierarchy. This is useful for distinguishing rollup members from base members in reporting.

The DISTINCT clause in the view definition suppresses duplicate rows that can arise when a value participates in multiple hierarchy contexts.

Common Use Cases and Queries

Typical usage includes building a cost center lookup for a financial data warehouse load, validating that hierarchy parents resolve to valid value set values, and producing descriptive cost center listings for management reporting. A representative query returning all cost center values with descriptions follows:

  • SELECT id, value, description, is_leaf_flag FROM apps.fii_cost_center_values_v ORDER BY value;
  • SELECT value, description FROM apps.fii_cost_center_values_v WHERE is_leaf_flag = 'Y' ORDER BY description; — retrieves only leaf-level cost centers, useful for transaction-level reporting.
  • SELECT v.value, v.description, c.parent_cc_id FROM apps.fii_cost_center_values_v v, apps.fii_cost_ctr_hierarchies c WHERE v.id = c.parent_cc_id; — joins the view back to the hierarchy table to reconstruct parent-child relationships, since some columns of FII_COST_CTR_HIERARCHIES are filtered out of the view.

Because the view restricts FII_FINANCIAL_DIMENSIONS to the 'HRI_CL_ORGCC' dimension, it is not a general-purpose cost center query and returns only values associated with that configured dimension master value set. Queries against it depend on the FII financial dimension setup being complete and on the relevant value set having a master value set assignment; if the dimension is not configured, the view returns no rows. Performance is generally acceptable for reporting purposes when the FND_FLEX_VALUES_VL and hierarchy tables are properly indexed, though large value sets may benefit from filtering by value or description.