Search Results get_bis_dimension_id

Overview

BSC_BIS_DIMENSION_PUB is the public PL/SQL API package in the APPS schema that manages dimensions within the Oracle EBS Balanced Scorecard and Business Intelligence (BSC/BIS) subsystem. A dimension is the analytic axis — customer, product, time, channel, geography — against which KPIs are measured and aggregated. This package owns the full lifecycle of those dimension definitions: creation, update, deletion, assignment to indicator/dimension objects, and the metadata queries that other BSC modules use to resolve dimension identity and level structure.

Because it is classified as a PUB (public) API, it is a supported integration point: other application modules and custom extensions are expected to call it rather than manipulating the underlying BSC/BIS tables directly. The dependency graph confirms this role — twelve packages reference it, including BSC_BIS_DIM_OBJ_PUB, BSC_DBI_CALENDAR, BSC_DIMENSION_SETS_PUB, BSC_KPI_PUB, BSC_BIS_KPI_CRUD_PUB, and BSC_UPGRADES. It is thus a foundational component in the BSC metadata layer, sitting beneath both the dimension-object API and the KPI definition APIs.

Key Procedures and Functions

The ETRM metadata documents 24 procedures and functions. The principal groups are:

• Lifecycle operations: CREATE_DIMENSION, UPDATE_DIMENSION, and DELETE_DIMENSION create, maintain, and remove dimension definitions.
• Object assignment: ASSIGN_DIMENSION_OBJECT, ASSIGN_DIMENSION_OBJECTS, ASSIGN_UNASSIGN_DIM_OBJS, and UNASSIGN_DIMENSION_OBJECTS attach dimension objects (such as levels or source columns) to a dimension or detach sets of them, supporting batch as well as single-object operations.
• Metadata retrieval: GET_DIMENSION_SOURCE, GET_LVL_DTLS, GET_SPEC_EDW_DTLS, and GET_GENE_EDW_DTLS return dimension source information and level detail, including EDW (Enterprise Data Warehouse) specific and generic variants used when wiring dimensions to warehouse sources.
• Identity and name lookups: GET_BIS_DIMENSION_ID, GET_BSC_DIMENSION_ID, and GET_BSC_DIMENSION_NAME resolve internal identifiers and display names used across the BSC schema. DIM_WITH_SINGLE_DIM_OBJ tests whether a dimension is associated with exactly one dimension object.
• Validation and impact checks: IS_KPI_FLAG_FOR_DIMENSION and IS_KPI_FLAG_FOR_DIMPROP_CHANGE indicate whether a dimension (or a change to its properties) is referenced by KPIs; IS_CONFIG_IMPACT_DIM reports whether a dimension affects configuration; IS_DIMENSION_IN_IND checks membership of a dimension in an indicator; REMOVE_EMPTY_DIMS_FOR_DIMSET prunes dimension sets that contain no populated dimensions.

Tables Accessed

Through APPS synonyms the package reads and writes the BIS/BSC dimension metadata tables. BIS_DIMENSIONS and BIS_INDICATOR_DIMENSIONS store the core dimension and indicator-to-dimension associations; BIS_LEVELS holds level definitions. BSC_SYS_DIM_GROUPS_TL, BSC_SYS_DIM_LEVELS_B, BSC_SYS_DIM_LEVELS_BY_GROUP, and BSC_SYS_DIM_LEVELS_TL carry system dimension group and level metadata (base and translated). BSC_KPIS_B, BSC_KPI_DIM_GROUPS, BSC_KPI_DIM_LEVELS_B, BSC_KPI_DIM_LEVEL_PROPERTIES, BSC_KPI_DIM_SETS_TL, and BSC_KPI_MEASURE_PROPS provide the KPI-side dimension and measure property context used by the validation routines. BSC_SYS_INIT and PLITBLM (the FND standard PL/SQL table) support initialization and array handling during bulk assignment calls.

Usage Notes

BSC_BIS_DIMENSION_PUB is normally invoked indirectly. Scorecard setup forms and concurrent programs for dimension and KPI maintenance call the higher-level public APIs (BSC_BIS_DIM_OBJ_PUB, BSC_KPI_PUB, BSC_DIMENSION_SETS_PUB), which in turn delegate to this package. BSC_UPGRADES also calls it during version upgrades, and BSC_SIMULATION_VIEW_PVT uses it when validating simulation views. The validation functions such as IS_KPI_FLAG_FOR_DIMENSION are intended to be called before a dimension change is committed, so callers can detect KPI impact and either block the change or cascade it. Direct custom invocation is supported for setup automation, but callers should follow the standard API error-handling pattern (FND_API is among the declared dependencies) and avoid DML against the BSC/BIS tables directly, since this package maintains the integrity relationships between dimensions, levels, and KPIs.