Results for “bsc_indicators”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.BSC_DATASETS_PVT is the private implementation body of the Balanced Scorecard dataset management API in Oracle E-Business Suite. In the Oracle EBS architecture, the _PVT suffix denotes a package body that holds the actual business logic and DML operations, while the companion public package (typically BSC_DATASETS_PUB) exposes the callable interface and layer. This package is responsible for creating, retrieving, updating, and deleting BSC datasets — the analytical structures that group measures and calculations into a reportable scorecard entity. The header comment dates the original creation to October 2001 and identifies the artifact as BSCVDTSB.pls. The package is classified as PVT in the ETRM metadata and sits within the BSC (Balanced Scorecard) product family under the APPS schema.

Key Procedures and Functions

The package documents sixteen procedures and functions, organized into four functional pairs plus supporting utilities.

• Dataset lifecycle: CREATE_DATASET, RETRIEVE_DATASET, UPDATE_DATASET, and DELETE_DATASET manage the core dataset entity, including its translated (TL) attributes.
• Measure lifecycle: CREATE_MEASURES, RETRIEVE_MEASURES, UPDATE_MEASURES, and DELETE_MEASURES manage the measures belonging to a dataset. The historical header notes document multiple bug fixes here concerning duplicate measure columns, duplicate source columns by source type, and incremental update handling.
• Dataset calculation lifecycle: CREATE_DATASET_CALC, RETRIEVE_DATASET_CALC, UPDATE_DATASET_CALC, and DELETE_DATASET_CALC maintain calculation definitions attached to a dataset.
• Supporting utilities: VALIDATE_MEASURE enforces measure-level integrity; TRANSLATE_MEASURE and TRANSLATE_MEASURE_BY_LANG synchronize measures across all installed languages (originally addressing bugs 3160325 and related); IS_STRUCTURE_CHANGE determines whether a modification affects dataset structure, enabling callers to decide whether dependent objects require regeneration.

The documented history indicates that rollback management was removed from this layer, with transaction control delegated to the Java/BC4J side. Error propagation to outer layers is also explicitly handled per the documentation.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

• BSC_SYS_DATASETS_B and BSC_SYS_DATASETS_TL — the base and translated dataset definitions.
• BSC_SYS_MEASURES — measure definitions; the history references a cursor created to read the Type column from this table during Update_Measure.
• BSC_SYS_DATASET_CALC — persisted dataset calculation definitions.
• BSC_KPIS_B and BSC_KPI_ANALYSIS_MEASURES_B — KPI and analysis-measure relationships used during validation and structure checks.
• BIS_INDICATORS and BIS_CUSTOM_CAUSE_EFFECT_RELS — indicator and cause/effect relationship data, relevant to the user's search on "bsc_indicators," reflecting the linkage between datasets and BIS indicator definitions.
• FND_LANGUAGES — installed-language lookup supporting translation procedures.
• PLITBLM — the standard PL/SQL index-by table type used for internal collections.

Usage Notes

BSC_DATASETS_PVT is a private package and should not be invoked directly by custom code; the documented public wrapper BSC_DATASETS_PUB is the supported entry point. The package is referenced by four other packages within the BSC schema stack. It is typically invoked from the Balanced Scorecard HTML/BC4J application layer when users define or maintain datasets, measures, and calculations, and it may be reached indirectly from concurrent programs that build or refresh scorecard structures. Because transaction control is handled by the calling layer, callers are responsible for committing or rolling back. Any customization should target the public API; direct calls to the private body risk breaking on patching, since the packaged body carries a 120.9 version stamp subject to Oracle's upgrade cycle across 12.1.1 and 12.2.2.