Search Results bsc_color_pub




Overview
Explore in AI Chat

Overview

APPS.BSC_COLOR_PVT is a private PL/SQL package within the Oracle E-Business Suite Balanced Scorecard (BSC) module, family of products collectively referred to as Oracle Scorecard and Strategy Management. It resides in the APPS schema and is classified as a PVT (private) API, meaning it is intended for internal use by the public API layer rather than direct invocation by external or customer code. The package provides the underlying implementation logic for managing the color definitions that the Balanced Scorecard application uses to visually represent scorecard status, thresholds, and performance indicators.

In the Balanced Scorecard model, colors are a fundamental presentation element: scorecard owners configure color bands (for example, green, yellow, red) to signal whether a metric, initiative, or KPI is meeting, approaching, or missing its target. BSC_COLOR_PVT encapsulates the create, maintain, and translation operations for these definitions, shielding the physical data model in BSC_SYS_COLORS_B and BSC_SYS_COLORS_TL from callers. Its existence as a distinct PVT layer reflects Oracle's standard API architecture, in which a public package (in this case APPS.BSC_COLOR_PUB) exposes the supported interface while the PVT package performs the actual DML, validation, and error handling.

Key Procedures and Functions

The ETRM metadata documents five procedures within this package:

  • CREATE_COLOR — Inserts a new color definition into the system, establishing its base record and associated translated name.
  • UPDATE_COLOR — Modifies an existing color definition, allowing administrators to adjust attributes of a color already registered in the system.
  • DELETE_COLOR — Removes a color definition from the system, handling the corresponding base and translation rows.
  • TRANSLATE_COLOR — Creates or maintains the language-specific description of a color, supporting Oracle's multi-language (MLS) architecture for the translated columns.
  • LOAD_COLOR — Loads a color definition into the system, typically supporting bulk or seeded data population of the color setup tables.

These procedures conform to the Oracle API programming standard, using the FND_API package for message handling and error reporting, as confirmed by the documented dependency on APPS.FND_API. Parameter lists are intentionally not reproduced here; callers should consult the package specification or delegate to BSC_COLOR_PUB rather than calling these private entry points directly.

Tables Accessed

The package operates against two tables, referenced through APPS synonyms:

  • BSC_SYS_COLORS_B — The base (non-translated) table holding each color definition and its system-level attributes. CREATE_COLOR, UPDATE_COLOR, DELETE_COLOR, and LOAD_COLOR write to this table.
  • BSC_SYS_COLORS_TL — The translation table storing language-specific display text for each color, keyed to the base row. TRANSLATE_COLOR and the create/update flows maintain this table.

The _B and _TL naming convention confirms that BSC colors are modeled as a translatable entity, which is why a separate TRANSLATE_COLOR procedure exists.

Usage Notes

BSC_COLOR_PVT is referenced by APPS.BSC_COLOR_PUB, which is the only documented caller. In practice, this means the private package is invoked indirectly: forms, concurrent programs, setup utilities, and any custom extensions in the Balanced Scorecard module should call BSC_COLOR_PUB, which in turn delegates to BSC_COLOR_PVT for validation and DML. Direct calls to BSC_COLOR_PVT are not supported and are subject to change between releases.

The confusion between the searched term "bsc_color_pub" and this object is common: BSC_COLOR_PUB is the public wrapper, while BSC_COLOR_PVT is the implementation package. When troubleshooting color setup errors, developers should trace failures from BSC_COLOR_PUB into BSC_COLOR_PVT, where FND_API error messages are raised. Both packages are valid in Oracle EBS 12.1.1 and 12.2.2. The package also references itself, indicating internal helper routines used across its procedures.