Search Results bsc_upgrades_generic




Overview
Explore in AI Chat

Overview

BSC_UPGRADES_GENERIC is an Oracle Applications (APPS) schema PL/SQL package classified under the ETRM as an "OTHER" API type. It belongs to the Oracle Balanced Scorecard (BSC) product family and exists to support the structural and metadata migration of Balanced Scorecard customizations and seeded content across Oracle E-Business Suite releases, most notably the 12.1.1 to 12.2.2 upgrade path. Unlike public, customer-callable APIs, this package is upgrade-specific: its routines transform legacy scorecard definitions, tab configurations, and role-to-tab assignments into the data model expected by the post-upgrade environment. The package is recorded with a VALID status in the APPS schema and is invoked internally by the migration driver rather than through any user-facing form. Its presence in the dependency graph of BSC_MIGRATION confirms its role as a subordinate upgrade utility within the larger Balanced Scorecard migration framework.

Key Procedures and Functions

ETRM documents three procedures, each scoped to a specific upgrade transformation:

  • UPGRADE_ROLE_TO_TABS — Reconciles the historical mapping between Oracle EBS responsibilities and Balanced Scorecard tabs. It establishes or repairs the association records that determine which responsibility can view which scorecard tab after the upgrade, drawing on grant and responsibility data consolidated from the foundation schema.
  • UPGRADE_TAB_VIEW_FUNCTIONS — Migrates function-to-tab-view associations, ensuring that the function definitions registered for a tab view remain consistent and valid following the change in the underlying objects and grants model. This routine preserves the security relationship between a tab view and the functions that expose it in the navigation menu.
  • UPGRADE_TAB_VIEW_KPI_LABELS — Converts and repopulates translated KPI label definitions for tab views, harmonizing the translatable label rows with the upgraded tab view KPI structure so that end users continue to see correct, language-specific KPI captions.

No parameter lists are documented in the ETRM record, and none should be assumed; callers within the upgrade driver supply the execution context.

Tables Accessed

The package reads and writes the following documented objects, referenced through APPS synonyms:

  • BSC_SYS_INIT — System initialization and version-control flags that indicate whether a given upgrade step has already been executed.
  • BSC_TABS_B — The base table of scorecard tab definitions, the primary target for tab-level transformations.
  • BSC_TAB_VIEW_KPI_TL and BSC_TAB_VIEW_LABELS_B — Translatable KPI and label definition tables, updated to align labels with the upgraded tab view hierarchy.
  • FND_GRANTS, FND_OBJECTS, FND_RESPONSIBILITY, and FND_USER — Foundation security and identity tables used to regenerate role-to-tab and function-to-tab grants and to resolve responsibilities and users.
  • PLITBLM — A standard PL/SQL helper package used for string and table manipulation during the transformation logic.

Usage Notes

BSC_UPGRADES_GENERIC is designed for invocation inside the Oracle EBS upgrade and migration cycle, specifically as a dependent component of BSC_MIGRATION. It is not exposed to end users through a Balanced Scorecard form, report, or standalone concurrent program; rather, the migration driver or an AD (AutoPatch) upgrade step calls its procedures in the appropriate sequence after the foundation tables and BSC schema objects have been patched to the target release. Administrators generally encounter it only in upgrade logs. Custom code should not call this package directly, because its logic assumes a partially migrated, mid-upgrade state and a specific execution order. Once migration completes, the package remains valid but dormant; it may be re-entered by later maintenance scripts that re-run label or grant reconciliation. Any diagnostic work should proceed through BSC_MIGRATION and the ETRM dependency listing rather than through the package itself.