Search Results bsc_aw_read




Overview
Explore in AI Chat

Overview

APPS.BSC_AW_READ is a VALID PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Balanced Scorecard (BSC) analytics framework, historically derived from Oracle Daily Business Intelligence and the Oracle Balanced Scorecard product line. The package name reflects its role as a reader or adapter layer for the Analytic Workspace (AW) integration used by the BSC performance-management modules. Its central responsibility is to retrieve, interpret, and normalize the metadata and measure definitions that describe KPIs, dimensions, dimension sets, levels, and periodicities, and to expose that information to the other BSC packages and to the SQL execution engine. In Oracle EBS 12.1.1 and 12.2.2 the package remains classified as API classification OTHER, indicating that it is an internal engine component rather than a published, supported public API. It is therefore subject to change and should not be called directly by customer extensions. The package forms part of the dependency chain that connects the BSC presentation layer to the underlying analytic structures and calendar definitions.

Key Procedures and Functions

The ETRM record documents 46 procedures and functions. Representative members include the following.

Tables Accessed

Documented dependencies include BSC_KPIS_B, which stores the base KPI definitions; BSC_SYS_PERIODICITIES, which holds the system time periodicities; BSC_DB_CALENDAR, which defines the calendar used for period alignment; and BSC_OLAP_OBJECT, which registers the analytic workspace objects that the reader resolves. Parameter and page context are obtained from BIS_PMV_PAGE_PARAMETER_TBL, and KPI adapter behavior is supplied through BSC_AW_ADAPTER_KPI. The package also references DBMS_SQL for dynamic SQL and PLITBLM for PL/SQL table operations. It reads these objects to build the metadata model that downstream packages and the page-rendering layer consume.

Usage Notes

BSC_AW_READ is referenced by BSC_AW_UTILITY, BSC_DIMENSION_KEYS_PKG, and BSC_UPDATE_COLOR, and it recursively references itself, confirming its role as a shared low-level metadata reader rather than a top-level entry point. It is normally invoked indirectly when a Balanced Scorecard region, dashboard, or concurrent data-refresh program triggers the BSC utility and page-rendering stack. Because it is not a public API, custom code should not call it directly; developers should instead use the supported BSC-facing views and integration points. Diagnostic procedures such as DMP_KPI and DMP_DIMSET are useful during troubleshooting of KPI or dimension-set resolution issues.