Search Results bis_indicators_u2

Overview

The BIS.BIS_INDICATORS table is a core metadata object within the Oracle EBS Business Intelligence System (BIS) product, also exposed through the Balanced Scorecard (BSC) framework. It stores the names and identifiers of performance measures — referred to interchangeably as "indicators" in ETRM documentation — that users define to calculate and track company performance across target levels. Each row represents a single performance measure, together with the database function used to compute it, the source of actual data, and the direction in which the measure is expected to move.

From a Data Vault modeling perspective, the mined FK structure classifies this object as standalone, suggesting it be treated as a reference or dimension-like entity rather than a hub, link, or satellite. This reflects the fact that BIS_INDICATORS holds descriptive metadata (names, data source types, function names) that is referenced by fact-style calculation tables rather than participating in a network of business-key relationships. The table resides in the APPS_TS_TX_DATA tablespace with PCT FREE 10, and its indexes reside in APPS_TS_TX_IDX.

Key Information Stored

The table comprises 18 documented columns. The most operationally significant are:

• INDICATOR_ID (NUMBER) — Surrogate primary key of the performance measure; enforced by unique index BIS_INDICATORS_U1.
• SHORT_NAME (VARCHAR2(30)) — Business-key candidate for the indicator; enforced by unique index BIS_INDICATORS_U2, the object referenced in the user's search.
• DATASET_ID (NUMBER) — Foreign key to BSC_SYS_DATASETS_B; also a unique business-key candidate per index BIS_INDICATORS_U3.
• UOM_CLASS (VARCHAR2(10)) — Unit of Measure class describing the physical quantity (time, count, money, dimensionless ratio) rather than the aggregation "dimension."
• FUNCTION_NAME — Database function invoked to calculate the measure for each target level.
• ACTUAL_DATA_SOURCE_TYPE (VARCHAR2(30)) and ACTUAL_DATA_SOURCE (VARCHAR2(240)) — Identify the origin and nature of the actual results feeding the measure.
• COMPARISON_SOURCE — Source used for comparison (target, prior period, benchmark).
• MEASURE_TYPE and INCREASE_IN_MEASURE — Control semantics of the measure, including whether a higher value is favorable.
• ENABLED, OBSOLETE, and ENABLE_LINK — Status and linkage flags governing availability.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical usage centres on enumerating active measures, resolving a short name to its ID for use in downstream calculation tables, and reporting on the data sources configured for each indicator.

• Resolve SHORT_NAME to INDICATOR_ID:
  SELECT indicator_id, short_name, uom_class FROM bis.bis_indicators WHERE short_name = :p_short_name;
• List enabled, non-obsolete measures and their data sources:
  SELECT i.indicator_id, i.short_name, i.actual_data_source_type, i.actual_data_source, i.function_name FROM bis.bis_indicators i WHERE i.enabled = 'Y' AND i.obsolete = 'N';
• Join to the dataset definition to report measure grouping:
  SELECT i.short_name, d.name FROM bis.bis_indicators i, bsc.bsc_sys_datasets_b d WHERE i.dataset_id = d.dataset_id;

Related Objects

The most significant related objects, based on the documented foreign key and BI subsystem context, include:

• BSC.BSC_SYS_DATASETS_B — referenced via BIS_INDICATORS.DATASET_ID; the dataset to which each indicator belongs.
• BIS.BIS_INDICATOR_DETAILS — child table holding per-target-level calculation configuration for each indicator.
• BIS.BIS_INDICATOR_TARGETS — stores target values defined against an indicator.
• BIS.BIS_INDICATOR_GROUPS — organizes indicators into scorecard groupings.
• BSC.BSC_SYS_INDICATORS — Balanced Scorecard view/synonym layer over the underlying indicator metadata.
• BIS.BIS_DIMENSIONS — aggregation criteria associated with measure definition.
• BIS.BIS_INDICATOR_COLUMN_MAP — maps indicator results to display columns.
• FND_USER — referenced by the CREATED_BY and LAST_UPDATED_BY WHO columns.

Any custom reporting should join INDICATOR_ID rather than SHORT_NAME, since the surrogate key is stable across renames while the short name remains a unique but mutable business key.