Search Results insert_olap_object_relation

Overview

BSC_AW_MD_WRAPPER is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that functions as the metadata management wrapper for the Oracle Business Intelligence (BSC) Analytic Workspace layer. Its documented object name, BSC_AW_MD_WRAPPER, follows the naming convention of the BSC "AW" family of packages, indicating its role in mediating between the ETRM application and the underlying OLAP metadata repository. The package encapsulates the DDL and DML operations required to create, modify, and drop analytic workspace metadata objects, including dimensions, key performance indicators (KPIs), calendars, and workspaces. Rather than allowing callers to manipulate the OLAP catalog directly, it centralizes these operations behind a stable interface, ensuring that the companion tables BSC_OLAP_OBJECT and BSC_OLAP_OBJECT_RELATION remain synchronized with the physical OLAP structures. The package is classified as OTHER in the ETRM repository, holding a VALID status in both Oracle EBS 12.1.1 and 12.2.2 environments. Its dependency list confirms its position within the BSC subsystem, referencing BSC_AW_ADAPTER_DIM, BSC_AW_ADAPTER_KPI, BSC_AW_CALENDAR, and BSC_AW_UTILITY, and it is itself referenced by eleven other database objects, underscoring its centrality to Analytic Workspace metadata processing.

Key Procedures and Functions

The package exposes twenty-five documented procedures and functions grouped around metadata lifecycle operations and OLAP catalog maintenance. The structural creation and removal routines include CREATE_DIM and DROP_DIM for dimension metadata, CREATE_KPI, DROP_KPI, and MARK_KPI_RECREATE for KPI metadata, CREATE_CALENDAR, and CREATE_WORKSPACE and DROP_WORKSPACE for workspace-level containers. Catalog persistence is handled by INSERT_OLAP_OBJECT, UPDATE_OLAP_OBJECT, MERGE_OLAP_OBJECT, DELETE_OLAP_OBJECT, and the parallel relational set INSERT_OLAP_OBJECT_RELATION, UPDATE_OLAP_OBJECT_RELATION, MERGE_OLAP_OBJECT_RELATION, and DELETE_OLAP_OBJECT_RELATION. Retrieval routines GET_BSC_OLAP_OBJECT and GET_BSC_OLAP_OBJECT_RELATION fetch catalog records for downstream processing. Context handling is supported by SET_CONTEXT and DEFAULT_CONTEXT_IF_NULL, which establish the session-level context required before any metadata operation executes. Parameter signatures are not documented in the ETRM extract and are therefore intentionally omitted here.

Tables Accessed

According to the documented dependency information, the package references BSC_OLAP_OBJECT and BSC_OLAP_OBJECT_RELATION through APPS synonyms. BSC_OLAP_OBJECT stores the master records describing each OLAP metadata object, while BSC_OLAP_OBJECT_RELATION maintains the hierarchical and associative links between those objects, such as the relationship between a KPI and its governing dimension or calendar. The package also depends on the DBMS_SQL built-in for dynamic SQL execution and PLITBLM for index-by table manipulation. These supporting dependencies indicate that metadata operations frequently require dynamically constructed statements and in-memory collections to manage bulk catalog updates.

Usage Notes

BSC_AW_MD_WRAPPER is not referenced by any other database object, meaning it sits at the top of the BSC metadata call stack and is invoked by external clients rather than by sibling packages. It is typically called by the BSC administrative forms, by concurrent programs that build or refresh the Analytic Workspace, and by custom code performing bulk metadata migration or reconciliation. Because it depends on companion packages such as BSC_AW_UTILITY for shared logic, callers should ensure the session context is established via SET_CONTEXT before invoking creation or deletion routines. Drop and recreate procedures should be executed during maintenance windows, as they alter OLAP structures referenced by reporting content.