Results for “bsc_mv_adapter”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BSC_MV_ADAPTER is an internal PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Oracle Balanced Scorecard (BSC) application family. Its name reflects its role as an adapter layer that abstracts the creation, maintenance, refresh, and removal of materialized views (MVs) used by the Balanced Scorecard and OLAP reporting infrastructure. In EBS 12.1.1 and 12.2.2, materialized views underpin the summary and KPI aggregation layers that feed scorecard dashboards, so this package centralizes the DDL and DML logic required to keep those summary objects synchronized with their base data. Because it isolates version- and platform-specific MV syntax, callers such as BSC_OLAP_MAIN and BSC_IM_UTILS do not issue raw MV DDL themselves; they delegate to BSC_MV_ADAPTER. The documented status is VALID, and the package exposes 24 documented procedures and functions, indicating a mature, actively maintained component of the BSC codebase.

Key Procedures and Functions

The documented callable units group into initialization, MV lifecycle, KPI-specific handling, logging, and validation:

• INIT_ALL — initialization entry point that primes the adapter's internal state before other operations are invoked.
• GET_TIME — returns timing information, used to measure or record elapsed time during MV operations.
• CREATE_MV_NORMAL — creates a standard (non-KPI) materialized view.
• CREATE_MV_KPI and CREATE_ZERO_CODE_MV_KPI — create KPI-oriented materialized views, the latter handling the zero-code KPI case.
• CREATE_MV_SYNONYM — creates the synonym that exposes the MV to application code.
• ALTER_MV_TO_REFRESH_DEMAND — alters an MV to refresh-on-demand, controlling refresh cost.
• CREATE_MV_LOG_ON_TABLE — creates the materialized view log required for fast refresh.
• REFRESH_MV_KPI and REFRESH_MV — perform refreshes for KPI and general MVs respectively.
• DROP_MV_KPI, DROP_MV, and DROP_SUMMARY_OBJECTS — remove KPI MVs, general MVs, and the broader set of summary objects.
• CREATE_DUMMY_MV and GET_DUMMY_MV — create and retrieve a placeholder dummy MV, commonly used during validation or setup.
• CREATE_MV_INDEX — creates supporting indexes on materialized views.
• GET_ORDERED_MV_LIST — returns MVs in dependency-correct order for coordinated processing.
• OBJECT_INDEX_VALIDATION and CHECK_OLD_MV_VIEW — validate indexes and detect legacy MV views.
• WRITE_TO_LOG_FILE — writes diagnostic output for troubleshooting MV operations.

Tables Accessed

Per the ETRM metadata, BSC_MV_ADAPTER references BSC_SYS_DIM_LEVELS_B and BSC_SYS_DIM_LEVEL_RELS, the Balanced Scorecard system dimension level and level-relationship tables. These drive which dimensions and aggregation levels an MV must include. It also accesses ALL_OBJECTS and USER_INDEXES to introspect the data dictionary, determining whether an MV or index already exists and is valid. DBMS_SQL is used for dynamic DDL/DML, PLITBLM is the index-by-table PL/SQL type used for collections, and STANDARD supplies core PL/SQL built-ins. Tables are referenced through APPS synonyms.

Usage Notes

BSC_MV_ADAPTER is not intended as a public API. It is invoked internally by BSC_IM_UTILS and BSC_OLAP_MAIN during Balanced Scorecard setup, KPI definition, and summary generation, typically triggered from BSC administrative concurrent programs or configuration forms rather than end-user screens. Customizations should call BSC_OLAP_MAIN or BSC_IM_UTILS instead of invoking the adapter directly, and any direct use must account for its dynamic DDL, dictionary access, and dependency on the ordered MV list. Because it issues DDL, appropriate privileges and maintenance-window scheduling are required.