Search Results bis_levels_s

Overview

APPS.BIS_DIMENSION_LEVEL_PVT is the private implementation package body for dimension level maintenance within the Oracle E-Business Suite Business Intelligence System (BIS) / Daily Business Intelligence (DBI) architecture. In Oracle EBS 12.1.1 and 12.2.2, it supports the definition and administration of dimension levels — the hierarchical structures used to organize performance indicators, fact data, and dimensional rollups in DBI and Balanced Scorecard reporting. The package holds the actual PL/SQL logic declared by the corresponding specification, BIS_DIMENSION_LEVEL_PVT, while public entry points are exposed through BIS_DIMENSION_LEVEL_PUB, which delegates to this private layer. It encapsulates validation, translation, customization retrieval, and DML operations against the underlying BIS_LEVELS and related tables, insulating callers from direct table manipulation and enforcing the API-driven model that BIS uses for its configuration metadata.

Key Procedures and Functions

The documented API surface comprises 19 procedures and functions:

• RETRIEVE_DIMENSION_LEVELS / RETRIEVE_DIMENSION_LEVEL / RETRIEVE_MULT_DIM_LEVELS — query dimension level definitions, either in bulk, individually, or by multiple identifiers, returning level metadata to callers.
• CREATE_DIMENSION_LEVEL / UPDATE_DIMENSION_LEVEL / DELETE_DIMENSION_LEVEL — the DML core: insert, modify, and remove dimension level records after validation and authorization checks.
• TRANSLATE_DIMENSION_LEVEL / TRANS_DIMOBJ_BY_GIVEN_LANG — manage multilingual (translated) content for level names and descriptions in the TL tables, and propagate dimension object translations for a specified language.
• VALIDATE_DIMENSION_LEVEL / VALIDATE_DISABLING — enforce business rules before create/update and before disabling a level, preventing orphaned or inconsistent hierarchy configurations.
• VALUE_ID_CONVERSION — converts between level identifiers and value IDs, supporting internal key mapping across BIS structures.
• GET_CUSTOMIZED_NAME / GET_CUSTOMIZED_DESCRIPTION / GET_CUSTOMIZED_ENABLED — retrieve customer-specific overrides of level attributes from the customization tables, allowing seeded dimensions to be personalized.

Tables Accessed

The package operates against the BIS level and customization model. BIS_LEVELS is the primary definition table; BIS_LEVELS_TL holds translatable columns; BIS_LEVELS_VL and BIS_LEVELS_S provide the versioned and sequence-keyed access paths. BIS_LEVELS_CUSTOMIZATIONS, with its _TL and _VL variants, stores customer overrides read by the GET_CUSTOMIZED_* functions. BIS_TARGET_LEVELS and BIS_TARGET_VALUES link levels to targets. BSC_KPI_DIM_LEVELS_B and BSC_SYS_DIM_LEVELS_B (Balanced Scorecard) connect levels to KPI and system dimension assignments. FND_LANGUAGES and FND_MESSAGE/FND_MSG_PUB support language handling and API error messaging, while DUAL and PLITBLM support utility and bulk-collection operations. BISBV_DIMENSION_LEVELS and BISFV_DIMENSION_LEVELS are view dependencies.

Usage Notes

As a PVT package, BIS_DIMENSION_LEVEL_PVT should never be called directly by external code; it is invoked through BIS_DIMENSION_LEVEL_PUB and is also referenced by BIS_DIMENSION_PUB, BIS_DIMENSION_PVT, and BIS_DIM_LEVEL_VALIDATE_PVT, which perform cross-object orchestration. It is typically triggered from DBI/BI administration forms and concurrent programs that define or maintain dimension hierarchies, invoking FND_API and FND_MSG_PUB for standard EBS error handling and FND_GLOBAL for session context. The documented dependency list shows it is not referenced by any non-BIS database object, meaning customizations must go through the public API layer. When investigating the synonym BIS_LEVELS_S or troubleshooting level definition errors, developers should review this package body alongside the public wrapper rather than modifying logic in place.