Search Results bsc_sys_dataset_id_s

Overview

APPS.BSC_DIMENSION_LEVELS_PVT is the private implementation package body for dimension level maintenance within the Oracle E-Business Suite Balanced Scorecard (BSC) product family. Dimension levels define the hierarchical groupings and structural layers applied to dimensions, datasets, and measures used in scorecard modeling and analytics. The package encapsulates the low-level create, retrieve, update, and delete (CRUD) logic for dimension levels, the columns associated with those levels, and the relationships that bind levels to one another.

The _PVT suffix indicates that this is an internal, private package. It is not intended for direct invocation by external or customer-written code; rather, it is consumed by the corresponding public package, BSC_DIMENSION_LEVELS_PUB, which acts as the supported API surface. The package is documented as VALID under the APPS schema and is referenced by 20 other database objects, confirming its central role in the dimension modeling tier. Because the package name relates to the identifier sequence BSC_SYS_DIM_LEVEL_ID_S, searches for that sequence frequently surface this object, since it is the package that consumes the sequence to generate primary keys for new dimension level rows.

Key Procedures and Functions

Approximately thirty procedures and functions are documented for this package. They fall into several functional clusters:

• Core CRUD routines: CREATE_DIM_LEVEL, RETRIEVE_DIM_LEVEL, UPDATE_DIM_LEVEL, and DELETE_DIM_LEVEL provide the fundamental lifecycle operations for a dimension level record.
• Metadata (MD) operations: CREATE_BSC_DIM_LEVELS_MD, RETRIEVE_BSC_DIM_LEVELS_MD, UPDATE_BSC_DIM_LEVELS_MD, and DELETE_BSC_DIM_LEVELS_MD manage the level metadata layer that describes how levels are defined and interpreted.
• Level column operations: CREATE_BSC_SYS_DIM_LVL_COLS, RETRIEVE_BSC_SYS_DIM_LVL_COLS, UPDATE_BSC_SYS_DIM_LVL_COLS, and DELETE_BSC_SYS_DIM_LVL_COLS maintain the mapping of columns that belong to each dimension level.
• Identifier helpers: GET_NEXT_VALUE and GET_ID retrieve sequence-derived identifiers, feeding primary key population from BSC_SYS_DIM_LEVEL_ID_S.
• Validation routines: VALIDATE_DIM_LEVEL, VALIDATE_DIM_GROUP, and VALIDATE_VALUE enforce referential and business rule integrity before persistence.
• Query and relationship helpers: GET_DIM_LEVELS returns level collections, GET_OBJECT_NAME resolves object naming metadata, and CREATE_DIM_LEVEL_RELATION establishes hierarchical links between levels.

Each public-facing counterpart in BSC_DIMENSION_LEVELS_PUB delegates to these private routines, preserving API encapsulation while centralizing logic.

Tables Accessed

The package operates against the BSC dimension infrastructure tables exposed through APPS synonyms:

• BSC_SYS_DIM_LEVELS_B, _TL, _VL: the base, translated, and view layers holding dimension level definitions and language-specific text.
• BSC_SYS_DIM_LEVEL_COLS: column associations for each level.
• BSC_SYS_DIM_LEVEL_RELS: relationships expressing hierarchy between levels.
• BSC_SYS_DIM_LEVEL_ID_S: the sequence supplying identifiers for new level records.
• BSC_SYS_DIM_LEVELS_BY_GROUP and BSC_SYS_DIM_GROUPS_VL: grouping structures that organize levels.
• BSC_INDICATOR_ID_S, BSC_SYS_DATASET_ID_S, BSC_SYS_MEASURE_ID_S, BSC_SYS_DIM_GROUP_ID_S: supporting sequences for related BSC entities.
• BSC_DB_TABLES and BSC_DB_TABLES_RELS: metadata describing underlying database tables and their relationships.
• FND_LANGUAGES, FND_MESSAGE, AD_DDL, DUAL: framework tables used for language handling, message retrieval, DDL operations, and singleton queries.

Usage Notes

BSC_DIMENSION_LEVELS_PVT is invoked indirectly through BSC_DIMENSION_LEVELS_PUB and other dependent packages such as BSC_DIM_FILTERS_PUB, BSC_PMF_UI_API_PUB, and BSC_UTILITY. It leverages the FND_API and FND_MSG_PUB frameworks for error handling and message stack management, consistent with standard EBS API conventions, and references FND_GLOBAL for session context such as user and language.

In Oracle EBS 12.1.1 and 12.2.2 environments, this package is typically exercised during dimension and scorecard configuration through the Balanced Scorecard administrative forms and setup workflows, and whenever concurrent processes or integration routines build or modify dimension level definitions. Because the package is private, customizations should target the public wrapper rather than call the private routines directly; doing so risks bypassing validation and message handling, and may break when Oracle applies patches to the private implementation.