Search Results calc_new_period_base_table

Overview

APPS.BSC_UPDATE_BASE is a PL/SQL package in the Oracle E-Business Suite Balanced Scorecard (BSC) module. Its principal responsibility is the maintenance, recalculation, and population of the base tables that underpin the Balanced Scorecard data model. In the BSC architecture, base tables hold the summarized fact data derived from transactional source systems before it is aggregated into scorecard indicators for display and analysis. This package provides the programmatic layer that creates staging and generic temporary tables, recomputes base table contents for defined periods, and refreshes those contents when the periodicity, dimension levels, or week-mapping definitions used by the scorecard change.

The package is classified as OTHER, indicating it is an internal utility package rather than a public, committed interface. It is documented as VALID in the APPS schema for both Oracle EBS 12.1.1 and 12.2.2 and is a dependency of the APPS.BSC_UPDATE package, which drives the higher-level scorecard refresh process.

Key Procedures and Functions

The ETRM metadata documents eight procedures and functions within BSC_UPDATE_BASE:

• CALCULATE_BASE_TABLE — Populates or recalculates the base table data set for the current processing context.
• CALCULATE_BASE_TABLE_AT — A variant of base table calculation that operates against a specified alternate target or context.
• CALC_NEW_PERIOD_BASE_TABLE — Creates and calculates base table content for a newly defined period.
• CALC_NEW_PERIOD_INPUT_TABLE — Parallel routine that builds input table content for a newly defined period.
• CREATE_GENERIC_TEMP_TABLES — Creates generic temporary/staging tables used during the calculation cycle.
• CREATE_GENERIC_TEMP_TABLES_AT — Creates the same generic temporary tables against an alternate target context.
• UPDATE_BASE_TABLE — Applies updates to existing base table rows, reflecting changes in source data or recalculation results.
• GET_BASE_AW_TABLE_NAME — A function that resolves and returns the physical base table name, typically for an Analytical Workspace (AW) context.

The presence of both standard and "_AT" variants reflects an internal design pattern in BSC that allows the same logic to execute against a default working schema or against an explicitly named alternate target.

Tables Accessed

The package references several configuration and metadata tables through APPS synonyms:

• BSC_DB_CALCULATIONS — Stores the defined calculations that drive how base tables are populated.
• BSC_DB_TABLES — The BSC repository of table definitions used by the engine to resolve and manage base and temporary tables.
• BSC_DB_WEEK_MAPS — Provides the week-mapping definitions used when periodicity is weekly.
• BSC_SYS_DIM_LEVELS_B — Dimension level definitions that determine the granularity at which base data is calculated.
• BSC_SYS_PERIODICITIES — Valid periodicity settings (for example daily, weekly, monthly) that govern period-based calculation.
• ALL_TABLES — Queried via the data dictionary to verify existence of dynamically named temporary and base tables.
• PLITBLM — A system table used by PL/SQL for dynamic SQL and column metadata resolution.

Usage Notes

BSC_UPDATE_BASE is an internal engine package. It is referenced by APPS.BSC_UPDATE and recursively by itself, and it depends in turn on APPS.BSC_UPDATE_UTIL. Customers and implementers do not normally invoke its procedures directly; instead they run the Balanced Scorecard concurrent programs or DBI (Daily Business Intelligence) refresh requests that call BSC_UPDATE, which orchestrates the calls into BSC_UPDATE_BASE. It is invoked whenever base table data must be established for a new period, recalculated after a periodicity or dimension-level definition change, or refreshed as part of the routine scorecard load cycle. Custom code should treat the package as a private implementation detail, since its interface is not documented as a supported public API.