Search Results bsc_color_ranges

Overview

BSC_COLOR_RANGES is a table owned by the BSC schema within the Oracle E-Business Suite Balanced Scorecard module. Its documented purpose is to store the color thresholds and ranges used to drive the visual indicators displayed throughout Balanced Scorecard dashboards, scorecards, and performance reports. In Oracle EBS 12.1.1 and 12.2.2, Balanced Scorecard relies heavily on color-coded status indicators (commonly green, yellow, and red) to communicate performance against targets. Rather than hard-coding these thresholds, the application persists them in this table so that administrators and scoring model designers can configure the numeric boundaries that determine when a given color is applied to a scorecard element, KPI, or aggregated performance value.

The table is classified in the ETRM metadata as a standalone object under the BSC product. Its data-mapping classification is standalone, meaning the object can be modeled as an independent satellite rather than as a hub or link within the balanced-scorecard domain. Modeling it as a satellite of the color configuration concept is a reasonable heuristic given its limited column set and singular foreign-key dependency.

Key Information Stored

The documented physical schema for 12.1.1 lists five columns, all of which are central to the table's function:

• COLOR_RANGE_ID — The surrogate primary key that uniquely identifies each color range definition. It forms the leading component of the unique index BSC_COLOR_RANGES_U1.
• COLOR_RANGE_SEQUENCE — The second component of the unique business key candidate (BSC_COLOR_RANGES_U1). It orders the ranges so the scoring engine evaluates them deterministically, ensuring overlapping boundaries resolve predictably.
• LOW — The lower numeric bound of the range. A performance value at or above this threshold qualifies for the associated color.
• HIGH — The upper numeric bound of the range. Together with LOW, this defines the bandwidth over which the referenced color applies.
• COLOR_ID — A foreign key referencing PON_COLORS, which resolves the actual color attributes (such as RGB or named color values) from the shared colors reference table.

The uniqueness enforced on (COLOR_RANGE_ID, COLOR_RANGE_SEQUENCE) confirms that each color range is uniquely identified and ordered, which is essential for evaluating discrete threshold bands without ambiguity.

Common Use Cases and Queries

Typical use cases center on configuration review and performance-status reporting. Administrators auditing Balanced Scorecard setup frequently query the table to enumerate the configured bands and their associated colors, joining to PON_COLORS to surface readable color names:

SELECT cr.COLOR_RANGE_ID,
       cr.COLOR_RANGE_SEQUENCE,
       cr.LOW,
       cr.HIGH,
       pc.COLOR_NAME
FROM   BSC.BSC_COLOR_RANGES cr,
       PON.PON_COLORS pc
WHERE  cr.COLOR_ID = pc.COLOR_ID
ORDER BY cr.COLOR_RANGE_SEQUENCE;

Another common scenario validates that ranges are contiguous and non-overlapping, which is critical to correct scorecard rendering. Reporting extensions often extract these boundaries to external BI tools so the same threshold logic can be reproduced outside the application. Migration and cloning exercises also touch this table when color configurations must be transported across instances (for example from 12.1.1 to 12.2.2).

Related Objects

The most significant related object is PON_COLORS, referenced through the foreign key BSC_COLOR_RANGES.COLOR_ID → PON_COLORS. This relationship resolves the actual color metadata applied to each defined range. Other objects in the Balanced Scorecard and Performance Management domain that depend on or interact with this configuration include the Balanced Scorecard scorecard and KPI definition tables, the scoring and threshold engine components that consume the LOW/HIGH boundaries at runtime, and the dashboard reporting views that render colored status indicators. Because BSC_COLOR_RANGES is classified as standalone with a single documented foreign key, its immediate dependency footprint is narrow, but it remains a foundational configuration source for all color-driven status visualization within the module.