Search Results delete_color_ranges

Overview

BSC_COLOR_RANGE_PVT is a private PL/SQL package body in the Oracle EBS Balanced Scorecard (BSC) module, owned by APPS and classified as a PVT (private) API. Its stated purpose is to manage range properties and to provide CRUD (create, read, update, delete) APIs for the BSC_SYS_COLOR_RANGES_B table and its related tables. The package header comment identifies the source file as BSCVCRNB.pls and records a creation date of November 02, 2006, by Pradeep Pandey, with a subsequent modification on 26-JUN-2007 addressing PL objectives (Bug#6132361). Because it is a private package, it is not intended as a public integration surface; rather, it encapsulates the internal logic used to maintain the color range configuration that drives Balanced Scorecard threshold and status coloring. The package was searched in connection with DELETE_COLOR_RANGES, indicating user interest in how color range records are removed within this private API layer.

Key Procedures and Functions

The documented API exposes four procedures, reflecting the range management lifecycle:

• CREATE_COLOR_PROPS — Creates color property records associated with an objective, KPI measure, color type, and color range. It accepts a commit flag and property value, and returns the standard FND_API return status, message count, and message data. The body excerpt shows validation that raises the BSC_OBJECTIVE_ID_NULL error when the objective identifier is missing, and it operates within a named savepoint (BscColorRangePvt_CrtColorRng).
• CREATE_COLOR_RANGE — Creates the parent color range definition, establishing the range against which color properties are subsequently defined.
• DELETE_COLOR_RANGES — Removes color range records, serving as the deletion counterpart to range creation. This is the procedure of interest for the user's search term.
• DELETE_COLOR_PROP_RANGES — Removes the property-to-range associations, allowing color properties linked to a range to be cleared, typically ahead of or in conjunction with deleting the range itself.

No parameter signatures beyond those visible in the excerpt should be assumed; the procedures follow the standard ETRM private API convention of returning x_return_status, x_msg_count, and x_msg_data.

Tables Accessed

According to the documented metadata, the package references the following tables via APPS synonyms:

• BSC_COLOR_RANGES — The primary range definition table, written by CREATE_COLOR_RANGE and cleared by DELETE_COLOR_RANGES.
• BSC_COLOR_TYPE_PROPS — Stores the color-to-property mappings; the create and delete property routines maintain records here, as evidenced by the validation query against this table in CREATE_COLOR_PROPS.
• FND_USER — Referenced for user identity and auditing context, consistent with the last_updated_by column usage in the body.
• PLITBLM — The standard PL/SQL message index table used by FND_MSG_PUB for message handling.

Usage Notes

As a private package, BSC_COLOR_RANGE_PVT is invoked by other BSC application components rather than directly by end users. The ETRM metadata records that it is referenced by one other package, which suggests it functions as a subordinate utility within a larger scorecard configuration flow. Typical invocation occurs from Oracle Forms or internal BSC setup logic that manages scorecard color thresholds, and from concurrent or custom code that needs to create or remove color range definitions. Because several procedures rely on FND_MSG_PUB and FND_API conventions, callers must check x_return_status and retrieve messages appropriately. Direct calls from custom code should be treated with caution, since private APIs may change between 12.1.1 and 12.2.2 without public notice.