Search Results get_base_table_of_input_table
Overview
BSC_UPDATE is a core PL/SQL package in the APPS schema of Oracle E-Business Suite, belonging to the Oracle Balanced Scorecard (BSC) application. Its primary business function is to orchestrate the update, calculation, and recalculation of Key Performance Indicator (KPI) data within the Balanced Scorecard framework. The package acts as the central controller for the update process, managing the sequence of loading dimension tables, calculating system tables, applying periodicity calculations, executing year-change processing, and importing input tables from remote database sources.
The package is classified as OTHER in the ETRM repository and holds VALID status. It depends on BSC_UPDATE_UTIL and the SYS.STANDARD package, and is referenced by several other BSC packages, including BSC_MIGRATION, BSC_MO_LOADER_CONFIG_PKG, BSC_UPDATE_BASE_V2, BSC_UPDATE_INC, and BSC_UPDATE_LOCK. This dependency structure confirms that BSC_UPDATE is a foundational driver of the Balanced Scorecard update engine, invoked and extended by migration, incremental update, and locking utilities.
Key Procedures and Functions
The package exposes 54 documented procedures and functions. The following represent core capabilities documented in the ETRM metadata:
- EXECUTE_UPDATE_PROCESS / EXECUTE_YEAR_CHANGE_PROCESS / EXECUTE_YEAR_CHANGE_PROCESS_AT — Orchestrate the main update and year-change processing cycles, including an "AT" variant for alternate or scheduled execution contexts.
- CAN_CALCULATE_SYS_TABLE / CAN_LOAD_DIM_TABLE — Determine whether a system table or dimension table is eligible for calculation or loading, providing prerequisite validation before execution.
- CONFIGURE_PERIODICITY_CALC / CONFIGURE_PERIODICITY_CALC_VB / CONFIGURE_PROFIT_CALC / CONFIGURE_PROFIT_CALC_VB — Configure periodicity and profit calculation settings, with "_VB" variants supporting view-based or value-based processing paths.
- EXISTS_PROTOTYPE_INDICATORS / GET_INDICATORS_TO_COLOR / FLAG_LAST_STAGE_INPUT_TABLE — Support indicator classification, coloring logic, and identification of the terminal stage of an input table in a calculation chain.
- GET_BASE_TABLE_OF_INPUT_TABLE / GET_LAST_STAGE_INPUT_TABLE / GET_PROCESS_INPUT_TABLES / GET_EDW_DIMS_IN_INPUT_TABLES — Resolve input table relationships, base tables, process input tables, and EDW dimension references.
- GET_PROCESS_ID — Retrieve the identifier for an update process instance.
- INIT_ENV_VALUES — Initialize environment values required for the update run.
- IMPORT_ITABLES_FROM_DBSRC / IMPORT_ITABLES_FROM_DBSRC_AT — Import input tables from an external database source, with an "AT" variant for alternate connection or timing scenarios.
Tables Accessed
BSC_UPDATE references tables through APPS synonyms, spanning configuration, control, calendar, and KPI metadata domains:
- BSC_DB_CALCULATIONS, BSC_DB_PROCESS_CONTROL, BSC_DB_PROCESS_ID_S — Drive calculation definitions, process control state, and process ID sequence generation.
- BSC_DB_CALENDAR — Supplies calendar and periodicity context for time-based calculations.
- BSC_DB_LOADER_CONTROL — Manages loader execution control during data staging and import.
- BSC_DB_TABLES, BSC_DB_TABLES_COLS, BSC_DB_TABLES_RELS, BSC_DB_VALIDATION — Define the metadata model for tables, columns, relationships, and validation rules used by the update engine.
- BSC_KPIS_B, BSC_KPI_ANALYSIS_MEASURES_B, BSC_KPI_DATA_TABLES, BSC_KPI_DEFAULTS_B, BSC_KPI_DIM_LEVELS_B, BSC_KPI_PERIODICITIES — Hold KPI definitions, analysis measures, data table mappings, defaults, dimension levels, and periodicity assignments.
Usage Notes
BSC_UPDATE is typically invoked from within the Balanced Scorecard update flow, most commonly through concurrent programs or from forms that launch KPI recalculation and year-change processing. Because BSC_UPDATE_BASE_V2, BSC_UPDATE_INC, BSC_UPDATE_LOCK, and BSC_MIGRATION reference this package, custom or extension code should route update logic through these dependent packages rather than calling BSC_UPDATE procedures directly, to preserve locking and incremental-update integrity. Direct invocation is appropriate for administrative tasks such as importing input tables from a remote database source or reinitializing environment values during troubleshooting. Administrators should monitor the BSC_DB_PROCESS_CONTROL and BSC_DB_PROCESS_ID_S tables to track process execution state.