Search Results bsc_aw_bsc_metadata




Overview
Explore in AI Chat

Overview

The APPS.BSC_AW_BSC_METADATA package body is a core metadata engine within the Oracle EBS Balanced Scorecard (BSC) module, specifically belonging to the Analytic Workspace (AW) integration layer. Its primary business function is to resolve, assemble, and expose the structural metadata that describes KPIs, dimensions, dimension sets, calendars, and data sources used by the Balanced Scorecard analytics engine. Essentially, this package translates the logical BSC configuration stored in the E-Business Suite repository into a form that can be consumed by the analytic workspace and reporting layers. It is classified as an OTHER API, meaning it is intended primarily for internal module use rather than as a public integration API. The package is VALID in the APPS schema and is heavily reused: the ETRM metadata confirms that APPS.BSC_AW_BSC_METADATA is not referenced by any database object directly in the dependency graph shown, but it is referenced by seven other packages and depends on a wide set of BSC components.

Key Procedures and Functions

The package exposes 39 documented procedures and functions. Among the most significant are:

Tables Accessed

The ETRM metadata lists the referenced objects as DBMS_SQL, PLITBLM, STANDARD, and the BSC internal packages BSC_AW_ADAPTER_DIM, BSC_AW_ADAPTER_KPI, BSC_AW_BSC_METADATA (self-reference), BSC_AW_CALENDAR, BSC_AW_UTILITY, and BSC_METADATA. These are accessed via APPS synonyms rather than as physical tables. DBMS_SQL and PLITBLM are Oracle-supplied packages used for dynamic SQL execution and index-by-table (PL/SQL table) operations respectively. The BSC_METADATA package is the principal source of logical BSC definitions, while the adapter and calendar packages supply KPI, dimension, and calendar metadata. The package therefore reads metadata rather than writing transactional business data, and no direct base-table DML is documented.

Usage Notes

BSC_AW_BSC_METADATA is invoked internally by the Balanced Scorecard analytics and AW build processes. Because it is an OTHER-class API and is referenced by seven other packages, it is typically called indirectly—for example, when a user configures KPIs or dimension sets in the BSC administrator forms, or when a concurrent program refreshes the analytic workspace. Custom code should call it only with caution, since its procedures are not published integration interfaces and their behavior is tightly coupled to the BSC metadata model. The dynamic SQL reliance via DBMS_SQL means privileges on the underlying objects must be granted to the APPS schema, and the package is valid and supported on Oracle EBS 12.1.1 and 12.2.2.