Search Results bsc_mo_loader_config_pkg




Overview
Explore in AI Chat

Overview

BSC_MO_LOADER_CONFIG_PKG is a configuration and administration package within the Oracle E-Business Suite Balanced Scorecard (BSC) module, owned by the APPS schema. Its header comment places its origin in mid-2005, and the package falls under the API classification OTHER, indicating it is an internal utility rather than a public, supported extension interface. The package exists to configure and maintain the metadata-driven loader infrastructure that moves source data into the Balanced Scorecard data model. Specifically, it manages the definition of origin tables, the configuration of upload fields, and the creation of materialized views that support actualization — the process by which actual performance figures are loaded and aggregated against KPIs and dimensions.

Because Balanced Scorecard deployments must frequently adapt to new source systems, table layouts, and upload requirements, this package provides the programmatic mechanism for reconfiguring the loader without manual DDL work. It is referenced by four other packages, confirming its role as a shared configuration dependency in the BSC loader chain.

Key Procedures and Functions

The package exposes six documented program units:

  • ConfigureActualization — Establishes or refreshes the configuration required to actualize data. This is the principal entry point for setting up the loader so that actual figures can be pulled from origin tables into the BSC structures.
  • ReConfigureUploadFieldsIndic — Accepts a numeric indicator and reconfigures the upload field definitions accordingly. It is used to toggle or reapply the upload field configuration, typically after metadata changes.
  • ReCreateMaterializedViewsIndic — Accepts a numeric indicator and re-creates the materialized views used by the loader and actualization logic, ensuring the pre-aggregated data structures match current definitions.
  • Corrections — Performs data or metadata corrections within the loader configuration, addressing inconsistencies without a full reconfiguration.
  • InsertOriginTables — Takes a table of table names and an IN OUT NOCOPY table of origin table definitions, inserting origin table registrations into the configuration metadata.
  • isBasicTable — A Boolean function that determines whether a given table name qualifies as a basic table, allowing callers to distinguish base source tables from derived or temporary structures.

A package-level CurTyp REF CURSOR type is declared for internal cursor handling.

Tables Accessed

The package reads and writes the BSC metadata repository. BSC_DB_TABLES, BSC_DB_TABLES_COLS, and BSC_DB_TABLES_RELS store table, column, and relationship definitions respectively, forming the core loader metadata that InsertOriginTables and Corrections maintain. BSC_DB_CALCULATIONS holds calculation definitions used during actualization. BSC_KPI_DATA_TABLES and BSC_KPI_DIM_LEVELS_B associate KPI and dimension level structures with their data tables. BSC_TMP_BIG_IN_COND is a temporary staging table used for large IN-list conditions. AD_DDL is the Applications DDL utility invoked for dynamic object creation, and PLITBLM and DBMS_SQL support dynamic SQL and PL/SQL table handling.

Usage Notes

This package is not intended for direct ad hoc invocation by end users. It is typically called from Balanced Scorecard administrative flows — loader setup and reconfiguration processes — and from other BSC packages that depend on it. The Indic parameters on the reconfigure procedures suggest callers pass flags that control whether upload fields or materialized views are rebuilt, allowing partial reconfiguration. In Oracle EBS 12.1.1 and 12.2.2, the package resides in the APPS schema and should be treated as Oracle-owned internal code. Customizations should avoid modifying it; instead, supported configuration should be performed through the standard BSC administration screens or concurrent programs that ultimately invoke these procedures.