Results for “current_period”

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

Overview

BSC_DB_TABLES is a metadata registry table owned by the BSC (Balanced Scorecard) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the central catalogue of data tables that the Balanced Scorecard module recognizes, loads, and analyzes. Each row describes one logical data source — its type, periodicity, generation behavior, and file-based or EDW-sourced characteristics — so that loaders, calculations, and KPI definitions can resolve a symbolic table name to a consistent set of processing rules.

Because the table acts as the single authoritative reference for downstream configuration and runtime processing, it is heavily referenced by foreign keys rather than referencing many parents itself. The ETRM relationship metadata classifies BSC_DB_TABLES as hub-leaning in Data Vault terms — a modeling suggestion indicating that it behaves primarily as a hub of business keys (table names) around which satellites and links (columns, relationships, loader control, calculations, KPI associations) are organized. Its only outbound foreign key points to BSC_SYS_PERIODICITIES via PERIODICITY_ID.

Key Information Stored

The table contains 15 documented columns. The surrogate/parent key for the table is defined by the primary key constraint BSC_DB_TABLES_PK, which is enforced on TABLE_NAME. A unique index, BSC_DB_TABLES_U1, also exists on TABLE_NAME, confirming it as the business-key candidate — the human-readable identifier used throughout the Balanced Scorecard configuration.

• TABLE_NAME — the business key and primary key; the symbolic name by which the data table is referenced by calculations, loaders, columns, relations, and KPI definitions.
• TABLE_TYPE — classifies the data table (for example, fact-style versus reference-style data) so processing logic knows how to treat it.
• PERIODICITY_ID — the only outbound foreign key; ties each data table to a record in BSC_SYS_PERIODICITIES, defining whether the data is loaded monthly, quarterly, or at another cadence.
• GENERATION_TYPE — indicates how the table's content is produced (for example, loaded from a source or generated by the system).
• NUM_OF_YEARS and PREVIOUS_YEARS — govern how many years forward and backward the table spans, driving time-slicing during loads and analysis.
• CURRENT_PERIOD and CURRENT_SUBPERIOD — record the active period and sub-period context for the table, used to align loads with the scorecard's current reporting cycle.
• SOURCE_DATA_TYPE and SOURCE_FILE_NAME — describe the origin of externally supplied data, distinguishing file-based feeds from database-sourced content.
• SOURCE_FILE_DATE — captures the date associated with the source extract, supporting audit and staleness checks.
• EDW_FLAG and TARGET_FLAG — booleans marking whether the table is sourced from the Enterprise Data Warehouse and whether it participates as a target in processing.
• PROJECT_FLAG and PROPERTIES — indicate project-scoped usage and hold auxiliary configuration attributes.

Common Use Cases and Queries

Administrators and developers query BSC_DB_TABLES to inventory the data tables configured in the Balanced Scorecard, to trace which tables are file-sourced versus EDW-sourced, and to validate periodicity alignment before running loads.

• Inventory of loaded vs. target tables: SELECT TABLE_NAME, TABLE_TYPE, EDW_FLAG, TARGET_FLAG FROM BSC_DB_TABLES;
• Listing tables by periodicity: SELECT t.TABLE_NAME, p.* FROM BSC_DB_TABLES t, BSC_SYS_PERIODICITIES p WHERE t.PERIODICITY_ID = p.PERIODICITY_ID;
• Finding file-sourced feeds and their dates: SELECT TABLE_NAME, SOURCE_FILE_NAME, SOURCE_FILE_DATE FROM BSC_DB_TABLES WHERE SOURCE_DATA_TYPE IS NOT NULL;
• Confirming time breadth: SELECT TABLE_NAME, NUM_OF_YEARS, PREVIOUS_YEARS FROM BSC_DB_TABLES ORDER BY TABLE_NAME;

Related Objects

The following objects reference BSC_DB_TABLES through documented foreign keys and represent the most significant integration points:

• BSC_SYS_PERIODICITIES — referenced by BSC_DB_TABLES.PERIODICITY_ID; supplies the periodicity definition for each data table.
• BSC_DB_TABLES_COLS — column-level metadata, joined via TABLE_NAME.
• BSC_DB_TABLES_RELS — inter-table relationships, joined via both TABLE_NAME and SOURCE_TABLE_NAME.
• BSC_DB_CALCULATIONS — calculation definitions that reference a data table via TABLE_NAME.
• BSC_DB_LOADER_CONTROL — loader execution state, referencing the input table via INPUT_TABLE_NAME.
• BSC_KPI_DATA_TABLES — maps KPIs to their data tables via TABLE_NAME.