Search Results store_anal_opt_grp_count

Overview

BSC_ANALYSIS_OPTION_PVT is a private PL/SQL package in the APPS schema that implements the internal processing logic behind the Oracle Balanced Scorecard (BSC) analysis option framework in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as the private companion to the public package BSC_ANALYSIS_OPTION_PUB, which acts as the API gateway for external callers. The naming convention confirms this relationship: the "PVT" suffix denotes a private implementation package intended to be invoked only by its public counterpart or by other members of the BSC module family.

Business users interact with this logic indirectly through the Balanced Scorecard administration and KPI configuration flows, where administrators define and maintain analysis options for scorecards. These analysis options drive how scorecard data is aggregated, which measures are exposed, and how data series are mapped to underlying KPIs. The package therefore underpins the configuration layer of the BSC product, translating user and API-driven requests into DML against the BSC configuration tables while enforcing referential and business validation rules.

Key Procedures and Functions

The ETRM metadata documents 23 procedures and functions. The core lifecycle set comprises CREATE_ANALYSIS_OPTIONS, RETRIEVE_ANALYSIS_OPTIONS, UPDATE_ANALYSIS_OPTIONS, and DELETE_ANALYSIS_OPTIONS, which manage the master analysis option definitions. Parallel procedures manage measures: CREATE_ANALYSIS_MEASURES, RETRIEVE_ANALYSIS_MEASURES, UPDATE_ANALYSIS_MEASURES, and DELETE_ANALYSIS_MEASURES.

Additional deletion and cleanup utilities are provided in DELETE_DATA_SERIES, DELETE_ANALYSIS_OPTION (singular, distinct from the plural DELETE_ANALYSIS_OPTIONS), DELETE_ANA_OPT_MULT_GROUPS, and DELETE_EXTRA_SERIES. Grouping and synchronization logic is handled by SYNCH_KPI_ANAL_GROUP and STORE_ANAL_OPT_GRP_COUNT, which maintain the association between KPIs and analysis groups.

Utility and integrity procedures include REFRESH_SHORT_NAMES, which regenerates short display names; VALIDATE_CUSTOM_MEASURE, which validates user-defined measures; SWAP_DATA_SERIES_ID, which exchanges series identifiers; CASCADE_SERIES_DEFAULT_VALUE and CASCADE_DATA_SRC_VALUES, which propagate default values across dependent series; and GET_NEXT_ASSOCIATED_OBJ_SN, which generates sequence numbers for associated objects. No parameter lists are documented in the supplied metadata and none are asserted here.

Tables Accessed

The package reads and writes the principal BSC configuration tables through APPS synonyms. BSC_KPI_ANALYSIS_OPTIONS_B and its translation table BSC_KPI_ANALYSIS_OPTIONS_TL store the base and language-specific analysis option definitions. BSC_KPI_ANALYSIS_MEASURES_B and BSC_KPI_ANALYSIS_MEASURES_TL provide the equivalent storage for measures. BSC_KPI_ANALYSIS_GROUPS and BSC_SYS_DATASETS_B support grouping and dataset associations.

BSC_KPIS_B and BIS_INDICATORS supply the KPI and indicator master data against which analysis options are defined. FND_LANGUAGES and PLITBLM are standard Oracle Applications infrastructure tables used for localization and PL/SQL index-by table handling. The view BSC_OAF_ANALYSYS_OPT_COMB_V is also referenced, along with the generic FND_API package used for standard API error handling and messaging.

Usage Notes

As a private package, BSC_ANALYSIS_OPTION_PVT should never be called directly from custom code. Oracle's supported integration point is BSC_ANALYSIS_OPTION_PUB, which invokes the private layer. The metadata confirms bidirectional dependency: the PVT package references the PUB package and is referenced by it. Four additional packages depend on it: BSC_BIS_KPI_CRUD_PUB, BSC_BIS_KPI_MEAS_PUB, BSC_OBJ_ANALYSIS_OPTIONS_PUB, and the package itself.

Typical invocation occurs through the Balanced Scorecard configuration forms, associated concurrent programs that build or refresh scorecard metadata, and internal BSC processing triggered during KPI and measure maintenance. Customizations requiring analysis option maintenance should call BSC_ANALYSIS_OPTION_PUB under the FND_API error-handling conventions rather than the private package.