Results for “bis_indicators”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIS_INDICATORS is a metadata table within the Oracle EBS BIS – Applications BIS product family, the component that underpins Oracle Balanced Scorecard and related performance-management functionality. The table defines individual indicators (key performance measures) that can be associated with datasets and evaluated against actual or comparison data sources. In Oracle EBS 12.1.1 and 12.2.2, the table owner is the BIS schema and the physical structure comprises 18 documented columns.

Within the ETRM documentation set, BIS_INDICATORS is flagged as “Not implemented in this database” for the seed/reference extract, meaning the object is shipped with the product but is populated only when Balanced Scorecard or indicator functionality is configured. Heuristically, the mined relationship data classifies BIS_INDICATORS as a standalone object rather than a pure hub, link, or satellite. As a modeling suggestion, it behaves closest to a reference/satellite-style descriptor keyed by its own surrogate identifier, with a single outgoing foreign key to the dataset definition table. This classification should be treated as guidance, not as a mandated Data Vault pattern.

Key Information Stored

The most significant columns of BIS_INDICATORS are:

• INDICATOR_ID — the surrogate primary key and the target of unique index BIS_INDICATORS_U1. It uniquely identifies each indicator record.
• SHORT_NAME — the business-key candidate enforced by unique index BIS_INDICATORS_U2; the human-readable short label for the indicator.
• DATASET_ID — the foreign key to BSC_SYS_DATASETS_B and the third unique key candidate (BIS_INDICATORS_U3), governing one indicator per dataset at the business level.
• UOM_CLASS — the unit-of-measure class that qualifies how the indicator value is expressed (currency, count, percentage, etc.).
• MEASURE_TYPE — categorizes the indicator measure, distinguishing the kind of metric being tracked.
• ACTUAL_DATA_SOURCE_TYPE and ACTUAL_DATA_SOURCE — define the origin of the actual value, e.g., a table, view, or query identifier.
• FUNCTION_NAME — the PL/SQL function or program unit used to compute the actual value.
• COMPARISON_SOURCE — the reference against which the actual is compared (target, prior period, benchmark).
• INCREASE_IN_MEASURE — a direction flag indicating whether a rising value is favorable.
• ENABLE_LINK and ENABLED — control whether the indicator is active and/or hyperlinked in the scorecard UI.
• OBSOLETE — soft-delete/retirement flag retaining historical indicator definitions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.

Common Use Cases and Queries

Typical use cases involve reporting on indicator definitions, verifying configuration before a Balanced Scorecard deployment, and auditing which indicators are enabled within a dataset.

• List active indicators for a dataset: SELECT indicator_id, short_name, measure_type FROM bis.bis_indicators WHERE dataset_id = :p_dataset AND enabled = 'Y' AND obsolete = 'N';
• Identify computed indicators: filter on function_name IS NOT NULL to find indicators whose actuals are derived from PL/SQL rather than direct data sources.
• Configuration audit: join to BSC_SYS_DATASETS_B on dataset_id to report indicator names alongside their parent dataset for compliance or migration reviews.
• Direction/UOM reporting: group by uom_class and increase_in_measure to validate that favorable-direction settings match business intent.

Related Objects

• BSC_SYS_DATASETS_B — the parent dataset definition table. Join via BIS_INDICATORS.DATASET_ID = BSC_SYS_DATASETS_B.DATASET_ID, the documented foreign-key relationship.
• BSC_SYS_DATASETS_TL — the translated dataset table, providing language-specific dataset names for reporting.
• BIS_INDICATOR_TL (if present) — translation table for indicator display names in multi-language deployments (typical BIS sibling pattern).
• BIS_INDICATOR_VALUES / fact tables — the runtime stores where actual and comparison measurements related to each INDICATOR_ID are retained.
• BSC scorecard/scorecard-indicator mapping tables — link indicators into scorecard hierarchies. Columns such as ENABLE_LINK suggest downstream linkage semantics.
• FND_LOOKUP_VALUES — commonly joined to resolve UOM_CLASS, MEASURE_TYPE, and ACTUAL_DATA_SOURCE_TYPE coded values.

Consult the ETRM 12.1.1 and 12.2.2 schema references for the authoritative column list and to confirm the presence of translation and value tables in a given deployment.