Search Results delete_measures

Overview

BSC_DATASETS_PVT is a private PL/SQL package in the Oracle E-Business Suite Balanced Scorecard module. It is owned by the APPS schema and classified as a PVT (private) API, meaning it is intended for internal use by the Balanced Scorecard application layer rather than direct invocation by external or customer-written code. In Oracle EBS 12.1.1 and 12.2.2, the package provides the underlying implementation logic for creating, maintaining, and querying datasets — the logical groupings of key performance indicators (KPIs), measures, and calculated values that drive scorecard visualizations and analytics.

The header comment ($Header: BSCVDTSS.pls 120.2 2006/01/05) indicates the package has been stable since early releases of the product, with the private API layer serving as the workhorse behind the corresponding public BSC_DATASETS_PUB package. Both packages share the BSC_DATASET_REC_TYPE record structure, confirming that the private package manipulates the same dataset record type exposed to callers through the public API.

Key Procedures and Functions

The package exposes sixteen documented procedures organized around four logical entities: measures, datasets, dataset calculations, and utility routines.

• CREATE_MEASURES, RETRIEVE_MEASURES, UPDATE_MEASURES, DELETE_MEASURES — Manage measure definitions associated with scorecards. Retrieval returns data through an IN OUT dataset record.
• CREATE_DATASET, RETRIEVE_DATASET, UPDATE_DATASET, DELETE_DATASET — Provide the full CRUD lifecycle for dataset header definitions, including translated names and descriptions.
• CREATE_DATASET_CALC, RETRIEVE_DATASET_CALC, UPDATE_DATASET_CALC, DELETE_DATASET_CALC — Manage calculated dataset entries, the formulas and derived values that supplement base measures. This is the family referenced by the user search term create_dataset_calc, the implementation procedure behind creation of a calculated dataset member.
• VALIDATE_MEASURE — Performs business-rule validation on a measure record prior to persistence.
• TRANSLATE_MEASURE and TRANSLATE_MEASURE_BY_LANG — Handle multilingual (TL) support, populating translated name and description columns for a given measure, optionally filtered by language.
• IS_STRUCTURE_CHANGE — Determines whether a proposed modification alters the structural definition of a dataset, a check typically used to decide whether dependent calculations must be re-evaluated.

All procedures follow the Oracle Application Object Library (AOL) API convention, accepting a p_commit flag defaulting to FND_API.G_FALSE and returning standard x_return_status, x_msg_count, and x_msg_data out parameters for error handling and message stack reporting.

Tables Accessed

The package reads and writes a defined set of underlying Balanced Scorecard and Application Object Library tables, referenced through APPS synonyms:

• BSC_SYS_DATASETS_B and BSC_SYS_DATASETS_TL — Base and translation tables for dataset headers, holding the primary dataset definitions and their multilingual descriptions.
• BSC_SYS_DATASET_CALC — Stores calculated dataset entries manipulated by the CREATE/RETRIEVE/UPDATE/DELETE_DATASET_CALC procedures.
• BSC_SYS_MEASURES — The measure repository managed by the MEASURES CRUD procedures.
• BSC_KPIS_B and BSC_KPI_ANALYSIS_MEASURES_B — KPI definitions and the association between KPIs and their analysis measures.
• BIS_INDICATORS and BIS_CUSTOM_CAUSE_EFFECT_RELS — BIS indicator definitions and cause-and-effect relationship metadata used in scorecard strategy maps.
• FND_LANGUAGES and PLITBLM — Language reference data for translation procedures and the PL/SQL message/error message table used by the AOL error handling framework.

Usage Notes

As a PVT package, BSC_DATASETS_PVT is not called directly by forms, concurrent programs, or customer extensions. It is instead invoked internally by the public wrapper package BSC_DATASETS_PUB, which re-exposes the same operations with appropriate security and validation. The ETRM metadata notes the package is referenced by four other packages, all within the Balanced Scorecard module.

Practically, the procedures execute whenever a user creates, edits, or deletes datasets, measures, or calculated entries through the Balanced Scorecard administrator and scorecard configuration UI. Customizations or data migrations that need to manipulate these records programmatically should target BSC_DATASETS_PUB rather than the private package, and should respect the FND_API.G_FALSE commit convention so that transaction boundaries remain under the caller's control. Understanding BSC_DATASETS_PVT remains valuable for debugging why dataset calculation records behave as they do, since all persistence logic for the BSC_SYS_DATASET_CALC table ultimately flows through the Create_Dataset_Calc family documented here.