Results for “get_periodicities_for_fact”

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

Overview

BSC_DBGEN_METADATA_READER is a PL/SQL package body owned by the APPS schema within the Oracle E-Business Suite Balanced Scorecard (BSC) product family. It forms part of the BSC Database Generator (DBGEN) subsystem, a metadata-driven engine responsible for constructing the analytical structures that support scorecard fact and dimension processing. The package serves as the metadata interrogation layer: it inspects the underlying fact, dimension, level, periodicity, and calendar definitions held in the BSC metadata tables and exposes that information to the broader DBGEN generation process. In this capacity it translates the abstract definitions captured through the scorecard configuration interface into concrete structural information — column names, partitioning details, level hierarchies, and measure lists — that the generator uses when building or refreshing the analytic objects behind a scorecard.

The package is marked VALID in the ETRM repository for both 12.1.1 and 12.2.2 and is classified under the generic "OTHER" API category, reflecting its role as an internal infrastructure component rather than a public, supported API.

Key Procedures and Functions

The package exposes approximately forty-eight documented procedures and functions, organized around several functional groupings:

• Initialization: INITIALIZE establishes the working context for a metadata read session.
• Fact and measure discovery: GET_FACTS_TO_PROCESS, GET_MEASURES_FOR_FACT, GET_FACT_IDS_FOR_CALENDAR, and GET_B_TABLE_MEASURES_FOR_FACT resolve the facts in scope and the measures associated with each, including those required for the B (base) table representation.
• Dimension and hierarchy traversal: GET_DIMENSIONS_FOR_FACT, GET_PARENTS_FOR_LEVEL, GET_CHILDREN_FOR_LEVEL, GET_LEVEL_INFO, GET_FACTS_FOR_LEVEL, IS_DIM_RECURSIVE, and IS_TARGET_AT_HIGHER_LEVEL supply the hierarchical and recursive-dimension information needed to navigate scorecard structures.
• Periodicity and calendar resolution: GET_PERIODICITIES_FOR_FACT, GET_PERIODICITY_FOR_TABLE, GET_CALENDAR_ID_FOR_FACT, and GET_DB_CALENDAR_COLUMN map facts to their calendars and identify the appropriate database calendar column.
• Physical structure inspection: GET_S_VIEWS, GET_LEVELS_FOR_TABLE, and GET_FILTER_FOR_DIM_LEVEL interrogate the physical or logical structures and the dimension-level filters that constrain them.
• Dimension set resolution: GET_DIM_SETS_FOR_FACT returns the dimension sets applicable to a given fact.

Tables Accessed

The package reads metadata from the core BSC configuration tables, addressed through APPS synonyms: BSC_DB_TABLES (physical table registration), BSC_KPI_PERIODICITIES and BSC_SYS_PERIODICITIES (periodicity definitions), BSC_SYS_DIM_LEVELS_B and BSC_SYS_DIM_LEVEL_RELS (dimension levels and their relationships), and BSC_KPIS_VL for KPI definitions. It also queries the Oracle data dictionary views ALL_TAB_COLUMNS, ALL_PART_TABLES, ALL_PART_KEY_COLUMNS, and ALL_TAB_PARTITIONS to determine column layouts and partitioning schemes, uses DBMS_SQL for dynamic statement execution, and consults DUAL, PLITBLM, and V$PARAMETER for control and environment information. No write operations against application data tables are documented; the package is primarily a reader.

Usage Notes

BSC_DBGEN_METADATA_READER is not intended for direct invocation by end users and is not referenced by any database object per the ETRM dependency report, though it depends on several sibling packages including BSC_DBGEN_BSC_READER, BSC_DBGEN_STD_METADATA, BSC_DBGEN_UTILS, BSC_OLAP_MAIN, BSC_AW_UTILITY, BSC_MO_HELPER_PKG, and BSC_APPS. It is typically invoked indirectly by the DBGEN generation routines — most likely from concurrent programs that build or refresh scorecard analytical workspaces — and only after INITIALIZE has established the run context. Customizations that alter scorecard metadata definitions should be validated through the standard scorecard configuration forms rather than by calling this package directly, since its output feeds the generator's structural assumptions.