Search Results load_dimension_level




Overview

BIS_DIMENSION_LEVEL_PUB is the public PL/SQL API for managing dimension levels within the Oracle EBS Key Performance Framework (KPF), the underlying analytical model that supports Balanced Scorecard and related performance management products. Dimension levels define the hierarchical structure within a dimension, establishing parent-child relationships and the granularity at which performance measures are aggregated. The package header (BISPDMLS.pls, version 120.4) carries a header date of January 2006 and is owned by APPS. The source comments explicitly note that the package should be maintained by EDW once integrated with BIS, indicating the intended long-term ownership path.

The package exposes a controlled public surface for the full lifecycle of dimension-level metadata: creation, loading, retrieval, translation, update, deletion, and customization handling. It is referenced by 23 other packages, which confirms its role as a foundational dependency for higher-level dimension and scorecard logic rather than an end-user utility.

Key Procedures and Functions

Tables Accessed

All tables are referenced through APPS synonyms. The package history references dimension object caching (bug 3760735), so read paths may be served from a cached representation rather than direct queries in some cases.

Usage Notes

The user search term load_dimension_level corresponds directly to the LOAD_DIMENSION_LEVEL procedure and its wrapper. This API is normally invoked by setup and maintenance flows rather than by end users directly: dimension-level definitions are created through the Balanced Scorecard / KPF administration forms, and concurrent programs and seed loaders call the LOAD and CREATE procedures to populate levels.

Custom code should call only the documented public procedures and the wrapper variants, since the wrappers are the interface explicitly provided to absorb internal changes. Callers must supply the Application_id and WHO columns carried in the Dimension_Level_Rec_Type record (added in 2003 and 2004 respectively), as omitting them causes audit and multi-language inconsistencies. Because the package underpins 23 dependent packages, changes should be made through the supported APIs rather than direct DML against BIS_LEVELS or BSC_SYS_DIM_LEVELS_B.