Search Results execute_update_process

Overview

APPS.BSC_UPDATE is the central orchestration package body for the Oracle Balanced Scorecard (BSC) update engine in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its documented classification in the ETRM repository is OTHER, reflecting that it is an internal engine rather than a public API. The package coordinates the loading of dimension and fact tables, the calculation of KPI measures, the enforcement of periodicity and profit-calculation rules, and the management of process identifiers that track a running update cycle. The header comment $Header: BSCDUPDB.pls 120.20 2007/12/07 ... ship $ identifies it as a shipped, Oracle-maintained database object that is patched with the application, and the package exposes 54 documented procedures and functions. Dependency metadata shows it is referenced by five other packages, confirming that it sits beneath higher-level BSC programs in the call stack rather than being invoked directly by end users.

Key Procedures and Functions

The procedures fall into four functional groups.

• Process orchestration: EXECUTE_UPDATE_PROCESS is the master driver for an update run and is the entry point associated with the user search term "execute_update_process". EXECUTE_YEAR_CHANGE_PROCESS and its overload EXECUTE_YEAR_CHANGE_PROCESS_AT handle roll-forward of scorecard data across a fiscal year boundary, with the _AT variant accepting a caller-supplied execution context. GET_PROCESS_ID and INIT_ENV_VALUES initialize the package-level state (g_process_id, g_process_name) that the remaining procedures rely on.
• Dimension and table validation: CAN_LOAD_DIM_TABLE determines whether a dimension table may be loaded by inspecting parent-child relationships in BSC_SYS_DIM_LEVELS_B and BSC_SYS_DIM_LEVEL_RELS via BSC_UPDATE_UTIL. CAN_CALCULATE_SYS_TABLE applies the equivalent test to system-calculated tables. FLAG_LAST_STAGE_INPUT_TABLE, GET_LAST_STAGE_INPUT_TABLE, GET_BASE_TABLE_OF_INPUT_TABLE, GET_EDW_DIMS_IN_INPUT_TABLES, and GET_PROCESS_INPUT_TABLES resolve input-table lineage for the calculation stage.
• Calculation configuration: CONFIGURE_PERIODICITY_CALC, CONFIGURE_PERIODICITY_CALC_VB, CONFIGURE_PROFIT_CALC, and CONFIGURE_PROFIT_CALC_VB write the derived calculation rows used by the KPI engine; the _VB variants are the value-based implementations used by the visible/valid business layer.
• Metadata and import utilities: EXISTS_PROTOTYPE_INDICATORS, GET_INDICATORS_TO_COLOR, IMPORT_ITABLES_FROM_DBSRC, and IMPORT_ITABLES_FROM_DBSRC_AT support indicator discovery and import of input tables from an external database source.

Tables Accessed

The package reads and writes configuration and control tables through APPS synonyms. BSC_DB_PROCESS_CONTROL, BSC_DB_LOADER_CONTROL, and BSC_DB_PROCESS_ID_S provide process tracking and sequence-based identifier allocation. BSC_DB_TABLES, BSC_DB_TABLES_COLS, and BSC_DB_TABLES_RELS define the physical and relational metadata that drive load ordering and CAN_LOAD_DIM_TABLE. BSC_DB_CALCULATIONS and BSC_DB_CALENDAR supply calculation definitions and period definitions used by the CONFIGURE_PERIODICITY_* and CONFIGURE_PROFIT_* routines. BSC_DB_VALIDATION holds validation rules applied during the update. On the KPI side, BSC_KPIS_B, BSC_KPI_ANALYSIS_MEASURES_B, BSC_KPI_DEFAULTS_B, BSC_KPI_DATA_TABLES, BSC_KPI_DIM_LEVELS_B, and BSC_KPI_PERIODICITIES identify which indicators are calculated, from which data tables, and at which dimensional and periodicity levels.

Usage Notes

BSC_UPDATE is not normally called directly from a form or a user-written concurrent program. It is invoked internally when a scorecard update is initiated from the Balanced Scorecard administrator responsibility, and by the five dependent packages that delegate lower-level work to it. The public-facing entry point is EXECUTE_UPDATE_PROCESS; customizations should call it rather than the individual stage routines so that process identifiers, environment values, and load ordering remain consistent. Because the package relies on package-level variables such as g_process_id and g_process_name, it assumes a single logical update session per database session. Recompilation or validation that changes BSC_DB_TABLES_RELS or BSC_SYS_DIM_LEVEL_RELS can alter the load order enforced by CAN_LOAD_DIM_TABLE and should be tested against a full update cycle before being promoted to production.