Search Results bsc_aw_adapter_dim




Overview

BSC_AW_ADAPTER_DIM is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that functions as the dimension adapter layer for the Oracle Business Intelligence (BSC) Analytic Workspace (AW) integration. It mediates between the EBS Balanced Scorecard metadata model and the Oracle OLAP analytic workspace, translating dimension definitions stored in the EBS repository into the physical dimension objects, levels, hierarchies, and relations that the analytic workspace requires. In ETRM terms the package is classified as OTHER, meaning it is an internal implementation package rather than a public, supported API, though it exposes a large surface of callable units.

The package is documented with 75 procedures and functions and is referenced by ten other database objects, confirming its role as a foundational utility in the BSC/OLAP metadata build path. It is not referenced by any database object itself at the package level, indicating it sits near the top of the call stack within this subsystem.

Key Procedures and Functions

The documented units group into several functional clusters:

No parameter signatures are asserted here; only documented names and their evident roles are described.

Tables Accessed

The package references DBMS_SQL (dynamic SQL execution), BSC_OLAP_OBJECT and BSC_OLAP_OBJECT_RELATION (EBS repository tables holding analytic workspace object definitions and their relationships), and PLITBLM (the PL/SQL integer table type used for array binding and bulk operations). BSC_OLAP_OBJECT and BSC_OLAP_OBJECT_RELATION are the primary persistent stores the package reads and writes when synchronizing dimension metadata with the AW.

Usage Notes

BSC_AW_ADAPTER_DIM is invoked during Analytic Workspace generation and refresh cycles, typically from concurrent programs and from higher-level BSC packages such as BSC_AW_LOAD_DIM, BSC_AW_MD_API, BSC_AW_MD_WRAPPER, and BSC_AW_UTILITY. It is not intended for direct customer invocation; customizations should prefer supported BSC APIs. Behavior is consistent across EBS 12.1.1 and 12.2.2.