Search Results update_bis_indicators




Overview
Explore in AI Chat

Overview

BIS_PMF_MIGRATION_PVT is a private PL/SQL package body owned by APPS that performs one-time data migration of legacy performance management framework (PMF) structures into the Oracle E-Business Suite 12.1.1 and 12.2.2 Balanced Scorecard data model. Its central responsibility is to convert old-model performance measure, indicator, and dimension-level data into the current BIS schema, preserving the hierarchical relationships between indicators, target levels, and dimension values. The package is classified as PVT (private), indicating it is an internal utility not intended for direct customer invocation; it is called by a single dependent package rather than exposed through a public API surface.

The header history shows the object evolved over approximately five years, from its creation in July 2000 through a December 2005 correction (Bug 4879417) that added a NULL check when executing dynamic SQL. Intermediate fixes addressed dimension resequencing (Bug 3583357), avoidance of migrating target levels that already exist (Bug 2790164), migration of BIS_USER_IND_SELECTIONS, and a SQL literal hardening change under Enhancement 4618419.

Key Procedures and Functions

  • MIGRATE_PERFORMANCE_MEASURES — Migrates legacy performance measure definitions into the new model. Its internal cursor, c_targetlvls, was deliberately restricted to rows originating from the old data model so that already-converted records are skipped.
  • MIGRATE_INDICATOR_DIMENSIONS — Migrates indicator-to-dimension associations from the pre-12.x structures into BIS_INDICATOR_DIMENSIONS.
  • RESEQUENCE_DIMENSION_LEVELS — Re-orders dimension levels to reflect the ordering held in BIS_TARGET_LEVELS, correcting sequence gaps introduced during migration.
  • RESEQUENCE_DIM_LEVEL_VALUES — Resequences the values belonging to each dimension level after levels have been reordered.
  • RESEQUENCE_IND_LEVEL_VALUES — Performs the equivalent resequencing for indicator-level values.
  • UPDATE_BIS_INDICATORS — Applies post-migration corrections to indicator rows in BIS_INDICATORS.
  • RESEQUENCE_IND_DIMENSIONS — Rebuilds the display order of indicator dimensions, using dimension-level order as the sort basis.
  • NEED_RESEQUENCE — Predicate that determines whether resequencing work is required for a given scope before the resequence procedures are executed.
  • GET_DIMENSION_ID — Lookup function that resolves a dimension identifier from a supplied dimension level identifier by querying BIS_LEVELS.
  • NEEDS_MIGRATION — Gate function that reports whether a candidate row still requires migration; it was amended to suppress migration when the target level already exists in the destination model.

Tables Accessed

The package reads and writes the core Balanced Scorecard tables through APPS synonyms. BIS_INDICATORS and BIS_INDICATOR_DIMENSIONS hold migrated indicator definitions and their dimension links. BIS_TARGET_LEVELS, BIS_TARGET_VALUES, and BIS_ACTUAL_VALUES store the level definitions and the corresponding target and actual result values. BIS_LEVELS provides level-to-dimension resolution used by GET_DIMENSION_ID and by the resequencing logic. BIS_USER_IND_SELECTIONS records user-selected indicators and required a dedicated migration fix (June 2001). PLITBLM is the standard Oracle Applications temporary/lookup table used to stage identifier lists during migration processing.

Usage Notes

BIS_PMF_MIGRATION_PVT is invoked indirectly by one other package and is normally driven by the PMF migration process supplied with Balanced Scorecard rather than by end users. It is not associated with a form-level button or a standalone concurrent program in the documented metadata; existing implementations typically trigger it through the migration routine that runs after an upgrade to 12.1.1 or 12.2.2, or through custom upgrade scripts that wrap the dependent package. Because the object is private, custom code should not call its procedures directly; instead, use the public migration entry points. Note that the "dim_level_name" term users search for is a column-level concept in BIS_LEVELS, and this package references levels only through identifiers — the lookup returns dimension_id, not a level name.