Results for “bsc_bis_kpi_meas_pub”

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

Overview

BSC_BIS_KPI_MEAS_PUB is a public PL/SQL package in the APPS schema that forms part of the Oracle Balanced Scorecard (BSC) module within Oracle E-Business Suite, commonly deployed in releases 12.1.1 and 12.2.2. The package provides the application programming interface through which KPI measures, dimension sets, and analysis options are created, maintained, and queried. It functions as the primary programmatic layer for the Balanced Scorecard configuration model, allowing callers to manipulate the underlying KPI structures without direct table access. The package is classified as a PUB (public) API, indicating that its procedures and functions are intended for external invocation by the application, other APIs, and custom extensions.

The user search term bsc_analysis_option_pub reflects the close coupling between this package and BSC_ANALYSIS_OPTION_PUB. The dependency documentation confirms that the two packages reference one another, with BSC_BIS_KPI_MEAS_PUB both calling and being called by BSC_ANALYSIS_OPTION_PUB. This bidirectional relationship reflects the shared responsibility for managing analysis options and the KPIs associated with them.

The package exposes 33 documented procedures and functions, organized around dimensions, dimension sets, KPIs, and analysis options. It is referenced by 11 other packages, including BSC_BIS_DIMENSION_PUB, BSC_BIS_KPI_CRUD_PUB, BSC_COPY_INDICATOR_PUB, and BSC_PMF_UI_WRAPPER, demonstrating its role as a central utility within the BSC schema.

Key Procedures and Functions

The documented API surface can be grouped into four functional areas.

• Dimension set management: CREATE_DIM_SET, UPDATE_DIM_SET, and DELETE_DIM_SET manage the lifecycle of dimension sets. ASSIGN_DIMS_TO_DIM_SET, UNASSIGN_DIMS_FROM_DIM_SET, and ASSIGN_UNASSIGN_DIMENSIONS handle membership of dimensions within those sets. ASSIGN_DSET_ANALYSIS_OPTIONS links dimension sets to analysis options.
• Dimension object handling: GET_DIMOBJ_VIEWBY_TBL and GET_DIMOBJ_PROPERTIES retrieve dimension object metadata. CREATE_DIM_OBJS_IN_DSET and DELETE_DIM_OBJS_IN_DSET maintain dimension object records within a dimension set.
• KPI management: CREATE_KPI and UPDATE_KPI persist KPI definitions. GET_KPIS returns KPI records, and IS_KPI_FLAG_FOR_DIM_IN_DIMSETS determines whether a KPI flag applies to a dimension within specified dimension sets.
• Analysis options and utility calls: CREATE_KPI_ANALYSIS_OPTIONS and UPDATE_KPI_ANALYSIS_OPTIONS manage the association between KPIs and analysis options. GET_DIMENSIONSETSOURCE, GET_AO_NAME, and GET_SERIES_COUNT serve as helper functions returning source information, analysis option names, and series counts respectively.

Tables Accessed

BSC_BIS_KPI_MEAS_PUB reads and writes a set of interlocking BSC configuration tables accessed through APPS synonyms. BSC_KPIS_B and BSC_KPIS_TL store KPI base and translation records; BSC_KPI_ANALYSIS_MEASURES_B holds KPI-to-measure mappings; BSC_KPI_ANALYSIS_GROUPS and BSC_KPI_ANALYSIS_OPTIONS_B/_TL store analysis grouping and option definitions. BSC_KPI_DIM_GROUPS, BSC_KPI_DIM_LEVELS_B, BSC_KPI_DIM_LEVEL_PROPERTIES, and BSC_KPI_DIM_SETS_TL hold dimension grouping, level, property, and set name data. BSC_KPI_MEASURE_PROPS stores measure properties. Reference data is drawn from BSC_SYS_MEASURES, BSC_SYS_PERIODICITIES, BIS_INDICATORS, and AK_REGIONS. Calls to FND_API provide standard EBS error handling and message conventions.

Usage Notes

The package is invoked primarily by Balanced Scorecard setup and administration forms, by concurrent programs that build or refresh scorecard metadata, and by other BSC PL/SQL APIs during KPI creation workflows. BSC_PMF_UI_WRAPPER and BSC_BIS_KPI_CRUD_PUB are common callers. Custom code extending Balanced Scorecard configuration should invoke these procedures rather than manipulating the BSC tables directly, since the API enforces validation, translation handling, and FND_API error semantics. The mutual dependency with BSC_ANALYSIS_OPTION_PUB means calls involving analysis options may traverse both packages; implementers should account for this when tracing execution or diagnosing errors.