Search Results create_dim_group_in_dset




Overview
Explore in AI Chat

Overview

APPS.BSC_DIMENSION_SETS_PUB is the public PL/SQL specification for the Oracle Balanced Scorecard (BSC) dimension set maintenance API. Its stated purpose, per the source header in BSCPDMSS.pls, is to create and maintain Dimension Sets within the BSC schema. A Dimension Set defines the ordered collection of dimension levels (for example, a hierarchy of organization or product levels) that a scorecard analysis operates on, together with presentation attributes and default key values. The package was created in October 2001 and has since been revised to support short names, view names, analysis identifiers, dimension reordering, and the distinction between one-to-many (C_REL_ONE_TO_MANY = 1) and many-to-many (C_REL_MANY_TO_MANY = 2) dimension relationships.

The package is classified as PUB, meaning its procedures form part of the supported integration surface for Oracle EBS 12.1.1 and 12.2.2. It exposes 21 documented procedures and is referenced by six other packages, indicating that it is a foundational layer for downstream BSC functionality rather than a leaf-level utility. All identifiers are resolved through APPS synonyms, consistent with standard EBS data-access conventions.

Key Procedures and Functions

The documented procedures fall into four functional groups. The dimension set group is anchored by CREATE_DIM_GROUP_IN_DSET, the entry point most frequently sought by integrators; it creates a dimension group within an existing dimension set, establishing the association between a set and one or more dimension levels. It is complemented by RETRIEVE_DIM_GROUP_IN_DSET, UPDATE_DIM_GROUP_IN_DSET, and DELETE_DIM_GROUP_IN_DSET, which query, amend, and remove that association respectively.

A second group manages the translated dimension set header: CREATE_BSC_KPI_DIM_SETS_TL, RETRIEVE_BSC_KPI_DIM_SETS_TL, UPDATE_BSC_KPI_DIM_SETS_TL, and DELETE_BSC_KPI_DIM_SETS_TL operate on the dimension set name, short name, and description records.

A third group governs dimension level properties, including CREATE_DIM_LEVEL_PROPERTIES, RETRIEVE_DIM_LEVEL_PROPERTIES, UPDATE_DIM_LEVEL_PROPERTIES, and DELETE_DIM_LEVEL_PROPERTIES. Related procedures CREATE_DIM_LEVELS, RETRIEVE_DIM_LEVELS, UPDATE_DIM_LEVELS, and DELETE_DIM_LEVELS maintain the dimension level definitions themselves. REORDER_DIM_LEVELS, added after the original release, adjusts the comp_order_by sequence that determines how levels appear in the scorecard. UPDATE_KPI_ANALYSIS_OPTIONS_B maintains analysis-level options against the KPI analysis options table. The package also declares the Bsc_Dim_Set_Rec_Type record, which carries action, dimension set, dimension group, display name, help text, component order, and default key value attributes across these calls.

Tables Accessed

The package reads and writes the BSC dimension metadata model. BSC_KPI_DIM_SETS_TL stores the translated dimension set headers. BSC_KPI_DIM_GROUPS holds dimension group definitions and their ordering (dim_group_id, dim_group_index). BSC_KPI_DIM_LEVELS_B and BSC_KPI_DIM_LEVELS_TL hold base and translated dimension level attributes, including comp_disp_name, help, and default_key_value. BSC_KPI_DIM_LEVEL_PROPERTIES stores level-level property values. BSC_SYS_DIM_LEVELS_B, BSC_SYS_DIM_LEVELS_TL, BSC_SYS_DIM_LEVELS_BY_GROUP, and BSC_SYS_DIM_LEVEL_RELS supply the seeded system dimension levels and their relationships. BSC_KPIS_B and BSC_KPI_ANALYSIS_OPTIONS_B tie dimension sets to KPI definitions and analysis options. PLITBLM is used for the standard EBS multi-row array processing pattern.

Usage Notes

BSC_DIMENSION_SETS_PUB is normally invoked from the Oracle Balanced Scorecard administrative forms in the BSC HTML or Forms-based UI, where dimension sets and their level groups are configured by scorecard administrators. It may also be called from concurrent programs that seed or migrate scorecard configurations, and from custom PL/SQL that programmatically provisions dimension sets across a multi-organization deployment. Callers should supply the Bsc_Dim_Set_Rec_Type record, respect the C_REL_ONE_TO_MANY and C_REL_MANY_TO_MANY constants when defining relationships, and commit explicitly. Because the package is referenced by six other packages, changes to dimension structure should be routed through these public procedures rather than direct DML to preserve referential integrity across the BSC metadata model.