Search Results ind_tl




Overview
Explore in AI Chat

Overview

APPS.BIS_INDICATORS_VL is a translation-enabled (VL, "view language") database view in the Oracle E-Business Suite 12.1.1 and 12.2.2 releases. It presents the master definition of Business Intelligence System (BIS) indicators together with their language-specific translated attributes. Indicators within BIS represent the measurable metrics, key performance indicators, and analytical values that populate Oracle EBS dashboards, balanced scorecards, and performance management reporting. Because indicator names and descriptions are maintained in multiple languages, Oracle delivers this information through the standard MLS (Multi-Language Support) "VL" pattern: a base table holding language-independent attributes joined to a translation (_TL) table holding language-dependent attributes.

For reporting and integration purposes, the view abstracts the join and the language filter from the caller. A developer or BI Publisher report can query a single object and receive indicator records already restricted to the session language, avoiding the need to manually join the base and translation tables while preventing duplicate rows per language.

Underlying Base Objects

The view is defined over two tables, as reflected in the documented view text:

  • BIS_INDICATORS IND — the base table storing language-independent indicator attributes, including the indicator identifier, short name, dataset association, enabled and obsolete flags, measure type, and standard WHO audit columns.
  • BIS_INDICATORS_TL IND_TL — the translation table storing the language-dependent NAME and DESCRIPTION for each indicator.

The two tables are correlated on INDICATOR_ID, and the translation row is further restricted by IND_TL.LANGUAGE = USERENV('LANG'). This USERENV call returns the language of the current session, so the view returns exactly one translated row per indicator for the runtime language environment. The ETRM metadata does not document additional referenced base objects, and no synonyms or additional joins are present in the supplied definition.

Key Columns

  • ROW_ID — the ROWID of the BIS_INDICATORS row, exposed for row-level addressing.
  • INDICATOR_ID — the unique primary key identifying the indicator; the join key between the base and translation tables.
  • SHORT_NAME — the language-independent short identifier or code for the indicator.
  • NAME — the translated display name drawn from BIS_INDICATORS_TL.
  • DESCRIPTION — the translated descriptive text for the indicator.
  • DATASET_ID — the identifier of the dataset to which the indicator belongs, linking the indicator to its underlying data source or collection.
  • ENABLED — flag indicating whether the indicator is currently active and available for use.
  • OBSOLETE — flag marking indicators that have been retired from active use.
  • MEASURE_TYPE — classification of the measurement semantics of the indicator.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns inherited from the base table.

Common Use Cases and Queries

Typical usage includes populating LOVs for indicator selection, validating indicator configuration in dashboard setups, and extracting indicator metadata for enterprise reporting.

List all active indicators for the session language:

SELECT indicator_id, short_name, name, dataset_id
FROM   apps.bis_indicators_vl
WHERE  enabled = 'Y'
AND    obsolete = 'N'
ORDER  BY name;

Retrieve a translated name and description for a specific indicator:

SELECT name, description
FROM   apps.bis_indicators_vl
WHERE  indicator_id = :p_indicator_id;

Join to related dataset metadata to report indicator-to-dataset mapping:

SELECT v.short_name, v.name, v.dataset_id, v.measure_type
FROM   apps.bis_indicators_vl v
WHERE  v.dataset_id = :p_dataset_id;

Because the view already enforces the language filter, no additional join to BIS_INDICATORS_TL is required in consumer queries, and results remain consistent across multilingual deployments.