Search Results merge_olap_object




Overview

BSC_AW_MD_WRAPPER is the metadata abstraction layer that Oracle E-Business Suite uses to manage the Oracle OLAP (Express/AWM) analytic workspace objects underlying the Balanced Scorecard (BSC) and Daily Business Intelligence (DBI) analytics infrastructure. Its primary responsibility is to insulate the Applications schema from the mechanics of creating, altering, and deleting OLAP metadata — dimensions, cubes, measures, and their relationships — by wrapping those operations in a controlled PL/SQL interface. The package stores and reconciles its state in the BSC_OLAP_OBJECT and BSC_OLAP_OBJECT_RELATION tables, and it treats those tables as a registry of analytic objects and their dependencies, including KPI-specific metadata.

The name and header comment indicate that the wrapper was authored against the OLAP AW (Analytic Workspace) metadata model and is registered as a "noship" internal component, confirming that it is an internal engine rather than a public product API. The header shows version 120.4 dated 2006/01/14, which is consistent with the BSC/DBI generation shipped in the 12.0.x–12.1.1 timeframe and carried forward into 12.2.x.

Key Procedures and Functions

Tables Accessed

The package reads and writes the documented registry tables BSC_OLAP_OBJECT and BSC_OLAP_OBJECT_RELATION through APPS synonyms. BSC_OLAP_OBJECT holds the object identity and type information (object, object_type, parent_object, parent_object_type) and also carries runtime properties such as load start/end times and lock indicators in its property columns. BSC_OLAP_OBJECT_RELATION stores the parent-child and dependency relationships between dimensions, cubes, and KPIs. The package also relies on DBMS_SQL for dynamic DDL/DML against the workspace and on PLITBLM for PL/SQL table operations; the declared collection types (bsc_olap_object_tb, bsc_olap_object_relation_tb, bsc_runtime_tb) support this bulk metadata handling.

Usage Notes

Because it is an internal ("noship") wrapper, BSC_AW_MD_WRAPPER is invoked indirectly by the BSC/DBI load, aggregation, and workspace-maintenance programs rather than directly by end users. It is referenced by 11 other packages, reflecting its role as a shared dependency for KPI and workspace construction. The mark_kpi_recreate routine is typically called when an underlying dimension or measure changes, flagging affected KPIs for regeneration on the next run. In 12.1.1 and 12.2.2, custom code should not call create_kpi or the OLAP mutators directly; use the supported DBI/BSC administrative concurrent programs, which call this wrapper on your behalf. Direct invocation risks leaving the BSC_OLAP_OBJECT registry inconsistent with the physical analytic workspace, requiring full regeneration of the affected objects.