Search Results get_bsc_olap_object_relation




Overview

APPS.BSC_AW_MD_API is a PL/SQL package body belonging to the Oracle E-Business Suite Balanced Scorecard (BSC) product family. Its primary business function is to manage the metadata that defines the OLAP (Online Analytical Processing) analytics workspace (AW) objects—dimensions, KPIs, calendars, and their interrelationships—used by the Balanced Scorecard analytics engine. The package acts as a server-side API layer that shields callers from the lower-level implementation encapsulated in BSC_AW_MD_WRAPPER, exposing a stable interface for creating, querying, dropping, and rebuilding multidimensional database objects.

The header identifier (BSCAWMAB.pls 120.22) and version history confirm this is a long-lived, shipped component. In Oracle EBS 12.1.1 and 12.2.2, this package is classified as an API and is referenced by 13 other packages, underscoring its role as a foundational dependency for the analytics metadata subsystem.

Key Procedures and Functions

The package exposes 65 documented procedures and functions. The most commonly referenced operations include:

All routines wrap their bodies in exception handlers that log via LOG_N and re-raise, preserving error propagation to the caller.

Tables Accessed

The package operates against the following underlying objects, accessed through APPS synonyms:

  • BSC_OLAP_OBJECT — Stores the definitions of OLAP objects (dimensions, KPIs, and related constructs). Read primarily by GET_BSC_OLAP_OBJECT.
  • BSC_OLAP_OBJECT_RELATION — Stores the relationships between OLAP objects, such as the dimension-to-KPI mapping or parent-child hierarchies. Read by GET_BSC_OLAP_OBJECT_RELATION.
  • DBMS_SQL — Used indirectly via the DBMS_SQL.VARCHAR2_TABLE PL/SQL type for list output parameters.
  • PLITBLM — Referenced as a supporting table.

Usage Notes

BSC_AW_MD_API is invoked from within the Balanced Scorecard analytics metadata framework, typically by other BSC packages (13 documented referrers), concurrent programs responsible for building or refreshing the OLAP AW, and occasionally by custom extensions that need to query dimension/KPI metadata. It is not an end-user-facing form API; forms generally interact with higher-level Balanced Scorecard administrative screens that call these routines indirectly. Developers integrating custom code should rely on the public procedures and avoid the g_olap_object and g_olap_object_relation package globals, which are stateful caches cleared on each invocation.