Results for “dim_level1_value”

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

Overview

BIS_PARAM_COLOR_TRIGGERS is a configuration table owned by the BIS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Applications BIS product family, which underpins the Oracle Balanced Scorecard and related performance-management functionality. Within the E-Business Suite, the table stores the rule definitions that determine when a colour indicator — typically a red, amber or green status — is applied to a metric, indicator or scorecard element for a given dataset and plan.

Each row represents a conditional trigger: it binds a specific dataset, planning context and indicator together, then supplies the dimensional coordinates that scope the trigger and a reference to the colour set that governs the visual threshold logic. The ETRM metadata notes that the object is Not implemented in this database, meaning the physical table is created and maintained by the BIS product installation but is documented here only for reference; it is populated at implementation time by scorecard configuration, not by general transaction processing.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In Data Vault modelling terms this suggests the table behaves as an independent reference or configuration entity rather than a classic hub, link or satellite. The single documented foreign key to BSC_SYS_DATASETS_B nonetheless gives it a hub-like dependency on the dataset master, so a practitioner may reasonably treat it as a configuration satellite attached to the dataset.

Key Information Stored

The documented physical schema contains 24 columns. The most significant are:

• DATASET_ID — the foreign key to BSC_SYS_DATASETS_B that identifies the scorecard dataset to which the trigger belongs. This is the primary business-key candidate and the principal join column.
• PLAN_ID — identifies the plan or version context in which the colour trigger applies, allowing different threshold rules per planning scenario.
• INDICATOR — the indicator or metric whose colour status is being controlled by the trigger.
• COLOR_SET_ID — references the colour set definition that supplies the actual colour bands and thresholds applied when the trigger fires.
• DIM_LEVEL1_KEY through DIM_LEVEL10_KEY — ten paired dimensional key columns that identify the dimension members at each level of the trigger's scope.
• DIM_LEVEL1_VALUE through DIM_LEVEL10_VALUE — the corresponding display or descriptive values for each dimensional level, retained so reports can render the trigger scope without additional lookups.

The metadata does not document a dedicated surrogate primary key column, so the effective uniqueness is derived from the combination of DATASET_ID, PLAN_ID, INDICATOR and the populated dimension key pairs. The ten-level dimension structure is the defining characteristic of the table, allowing highly granular scoping of colour rules down to the tenth dimension level.

Common Use Cases and Queries

Typical usage centres on configuration validation and reporting of scorecard threshold logic. A frequent pattern lists all triggers for a dataset alongside the colour set each one references:

• Identify orphaned or duplicate triggers where the same dataset, plan and indicator combination is defined more than once, which causes ambiguous colour rendering.
• Audit which dimension members have explicit colour rules and which fall back to dataset defaults.
• Produce an implementation workbook showing every colour trigger and its dimensional scope for sign-off during a Balanced Scorecard rollout.

A representative query joins the trigger to its dataset master and filters by dataset and plan, then orders by the dimension keys to expose the scope hierarchy. Because the table is read-mostly and configuration-oriented, queries are usually run during setup, upgrade testing or periodic configuration review rather than in transactional reporting.

Related Objects

• BSC_SYS_DATASETS_B — the documented foreign-key parent; join on BIS_PARAM_COLOR_TRIGGERS.DATASET_ID = BSC_SYS_DATASETS_B.DATASET_ID to resolve dataset names and descriptions.
• The dataset translation table for BSC_SYS_DATASETS_B, used to retrieve language-specific dataset labels for reporting.
• The colour set definition objects referenced by COLOR_SET_ID, which supply the threshold and colour band logic applied by each trigger.
• Indicator and metric definition tables that resolve the INDICATOR column to a business-friendly metric name.
• Plan and version definition tables that give meaning to PLAN_ID.
• Balanced Scorecard configuration and administration forms and concurrent programs that populate and maintain BIS_PARAM_COLOR_TRIGGERS.

Because the table is documented as standalone with a single mined foreign key, its dependency footprint is narrow; the dataset master remains the dominant related object and the primary anchor for all joins.