Search Results lock_migration

Overview

The APPS.BSC_MIGRATION package is a PL/SQL migration utility within the Oracle E-Business Suite Balanced Scorecard (BSC) module. Its principal responsibility is to orchestrate the migration of Oracle Balanced Scorecard metadata and transactional objects between environments and releases, performing the structural transformations required to make legacy indicator, KPI, and dimension definitions usable in the target schema. The package operates on dynamic tables and views, generating and dropping database objects at runtime in order to reconcile the physical data model with the logical scorecard model.

In Oracle EBS 12.1.1 and 12.2.2, BSC_MIGRATION is classified as an OTHER API and is validated in the APPS schema. It forms part of the internal infrastructure that supports the Balanced Scorecard configuration lifecycle, including copying, upgrading, and re-basing scorecard artifacts. Because it manipulates metadata directly, it is not intended for general customer invocation and should be run only through supported migration flows.

Key Procedures and Functions

The package exposes fifty-six documented procedures and functions. The most significant are described below.

• EXECUTE_MIGRATION — The primary entry point that drives the migration process end to end, coordinating the other routines.
• LOCK_MIGRATION — Serializes migration activity to prevent concurrent migration runs from conflicting.
• GET_MIGRATION_PARAMETERS — Retrieves the configuration inputs that govern a migration run.
• CREATE_DYNAMIC_OBJECTS / DROP_DYNAMIC_OBJECTS — Create and remove the dynamic tables and views required during migration.
• CREATE_COPY_OF_TABLE_DEF / CREATE_COPY_OF_VIEW_DEF — Produce copies of table and view definitions as part of the migration.
• CREATE_TABLE_INDEXES / CREATE_INDEXES_DYNAMIC_TABLES — Build the indexes needed for the dynamically created structures.
• ANALYZE_BASE_AND_DIM_TABLES — Gathers statistics on base and dimension tables to support optimizer performance.
• INIT_MIGRATION_OBJECTS_ARRAYS / INIT_METADATA_TABLES_ARRAY — Initialize the internal arrays that track objects and metadata tables.
• INIT_INVALID_PMF_OBJECTS / CLEAN_METADATA_INVALID_PMF — Identify and clean invalid performance management framework objects.
• CHECK_LANGUAGES_TL_TABLES — Verifies translation (TL) tables for language completeness.
• INSERT_ORIGIN_TABLES / DELETE_METADATA_TABLES — Populate origin table records and remove obsolete metadata table entries.
• GET_LST_TABLE_COLUMNS / DECOMPOSE_NUMERIC_LIST — Resolve table columns and parse numeric lists used in migration definitions.
• ASSIGN_TARGET_RESPONSIBILITIES — Maps migrated artifacts to the appropriate target responsibilities.

Tables Accessed

BSC_MIGRATION reads and writes several Balanced Scorecard metadata tables through APPS synonyms. BSC_KPIS_B and BSC_KPIS_TL hold the base and translated KPI definitions that are migrated. BSC_DB_TABLES and BSC_DB_TABLES_RELS describe the physical database tables and their relationships, while BSC_DB_MEASURE_GROUPS_S stores measure group sequence data. BSC_INDICATOR_ID_S, BSC_COLOR_RANGE_ID_S, and BSC_INTERNAL_COLUMN_S supply identifier and column-sequence values. BIS_DIMENSIONS, BIS_INDICATORS, and BIS_LEVELS provide the BIS analytical dimension and indicator structures. AK_ATTRIBUTES, AK_REGIONS, AK_REGION_ITEMS, and AK_REGION_ITEMS_TL contribute application framework region and attribute metadata. FND_API and FND_TABLE_OF_NUMBER, along with STANDARD, are standard EBS dependencies used for API error handling and array handling.

Usage Notes

BSC_MIGRATION is an internal infrastructure package, not a public API. It is referenced by BSC_COPY_INDICATOR_PUB, indicating that it is invoked during indicator copy operations, and by BSC_MIGRATION itself for internal recursion. The package is normally executed in the context of Balanced Scorecard upgrade and migration tasks rather than from Oracle Forms or standard concurrent programs. Custom code should not call these procedures directly because the routines create and drop database objects dynamically and manipulate metadata tables. In 12.1.1 and 12.2.2, customers should rely on supported Oracle-supplied migration flows and treat BSC_MIGRATION as a dependent implementation detail.