Search Results update_kpi_measure_weights




Overview
Explore in AI Chat

Overview

APPS.BSC_KPI_MEASURE_WEIGHTS_PVT is a private (PVT) PL/SQL package in the Oracle E-Business Suite Balanced Scorecard (BSC) module. Its business purpose is to manage the weightings assigned to KPI measures within the context of scorecard objectives. In Balanced Scorecard methodology, individual key performance indicators contribute to overall objective scores according to configurable weights; this package encapsulates the persistence logic that creates, updates, removes, and retrieves those weight records.

Because the package is classified as PVT and is prefixed accordingly, it is not intended to be called directly by external or customer code. It functions as the private implementation layer sitting beneath the public API surface represented by BSC_KPI_MEASURE_WEIGHTS_PUB. The public package defines the record types (such as kpi_measure_weights_rec) and exposes the supported entry points, while this private package performs the actual data manipulation against the underlying table. This separation follows the standard Oracle EBS PL/SQL API architecture, in which public packages publish the interface and private packages carry out validation and DML. The header comment indicates the package has been stable since at least 2007, with a version stamp of 120.0.12000000.1, and was shipped without a customization flag ("noship").

Key Procedures and Functions

The package exposes five documented procedures:

  • CREATE_KPI_MEASURE_WEIGHTS — Inserts a new KPI measure weight record. It accepts a commit flag and a KPI measure weights record, and returns the standard concurrent-style out parameters for status, message count, and message data.
  • UPDATE_KPI_MEASURE_WEIGHTS — Modifies an existing KPI measure weight record. This is the procedure most commonly associated with the search term "update_kpi_measure_weights." It follows the same signature pattern as the create procedure, taking the commit flag and the weights record and returning status and message information.
  • DEL_KPI_MEASURE_WEIGHTS — Deletes a KPI measure weight record identified by objective and KPI measure. It accepts the commit flag together with an objective identifier and a KPI measure identifier.
  • DEL_OBJ_KPI_MEASURE_WEIGHTS — Deletes all KPI measure weight records associated with a given objective. Unlike the preceding procedure, it is keyed only on the objective identifier, making it suitable for bulk removal when an objective is dismantled or redefined.
  • RETRIEVE_KPI_MEASURE_WEIGHTS — Returns KPI measure weight information for consumption by the public API or calling processes.

All three DML procedures default the commit parameter to FND_API.G_FALSE, meaning callers must explicitly request a commit; otherwise the transaction remains open for the calling process to control. Each procedure returns x_return_status, x_msg_count, and x_msg_data, conforming to the standard EBS API error-handling convention where the message stack is populated via FND_MSG_PUB.

Tables Accessed

The package reads from and writes to a single documented table, BSC_KPI_MEASURE_WEIGHTS, accessed through its APPS synonym. This table stores the association between objectives and KPI measures together with the weight value applied to each measure. The create and update procedures insert and modify rows in this table, the two delete procedures remove rows, and the retrieve procedure queries rows. Because only one table is involved, the package requires no complex multi-table coordination, although it may depend on FND_API and FND_MSG_PUB utilities for commit control and message handling.

Usage Notes

This package should not be invoked directly by customers or integrators. It is referenced by exactly one other package, which corresponds to the public API BSC_KPI_MEASURE_WEIGHTS_PUB. Callers seeking the UPDATE_KPI_MEASURE_WEIGHTS functionality should invoke the corresponding procedure in the public package, passing a properly populated kpi_measure_weights_rec record and an explicit commit flag when immediate persistence is required. Typical invocations originate from Balanced Scorecard setup forms, scorecard configuration pages, and concurrent or batch processes that seed or adjust measure weightings. Custom code that references BSC_KPI_MEASURE_WEIGHTS_PVT directly risks breakage during patching or upgrades, since private packages are subject to change without notice; the supported integration point remains the public wrapper.