Search Results get_periodicity_nextval




Overview
Explore in AI Chat

Overview

APPS.BSC_DBI_CALENDAR is the package body of the BSC_DBI_CALENDAR package, a PL/SQL component within the Oracle E-Business Suite Balanced Scorecard (BSC) and Daily Business Intelligence (DBI) product family. Its principal business function is to load, generate, and maintain calendar and periodicity definitions used by the DBI and BSC reporting engines. DBI warehouses, such as Daily Business Intelligence for Financials, Procurement, and related applications, depend on consistent time dimensions to aggregate transactional facts into daily, weekly, monthly, quarterly, and fiscal reporting buckets. BSC_DBI_CALENDAR provides that calendar infrastructure by populating the BSC system calendar and period tables, supporting multiple calendar conventions including Gregorian, 4-4-5 retail, and enterprise-specific calendars.

The package is owned by APPS and carries a VALID status in the documented environment (Oracle EBS 12.1.1 / 12.2.2). Its classification is OTHER, indicating it is a product-internal utility rather than a published open interface such as an FND_API-based public API. It is referenced by three other database objects and itself depends on a broad set of BSC, BIS, and FND objects.

Key Procedures and Functions

The package exposes fifty documented procedures and functions. The primary loader entry points are LOAD_DBI_CAL_INTO_BSC and LOAD_DBI_CAL_INTO_BSC_FULL, which populate BSC calendar definitions from DBI sources in incremental and full modes respectively. Specialized loaders LOAD_DBI_ENT_CAL, LOAD_DBI_445_CAL, and LOAD_DBI_GREG_CAL handle enterprise, 4-4-5, and Gregorian calendar variants. LOAD_DBI_ENT_CAL_DATA and LOAD_DBI_445_CAL_DATA perform the corresponding data-level loads.

Memory-oriented loaders LOADMEM_ENT_FULL, LOADMEM_445_FULL, LOADMEM_GREG_FULL, and LOAD_FII_TIME_DAY_FULL build in-memory representations of calendar and time-day data. Utility routines include DELETE_DBI_CALENDARS for purging calendar rows, ANALYZE_TABLES for statistics gathering, INIT_ALL and INIT_CAL_PER_IDS for initialization, and GET_CALENDAR_NEXTVAL and GET_PERIODICITY_NEXTVAL for sequence generation. Logging support is provided by WRITE_TO_LOG_FILE, WRITE_TO_LOG_FILE_N, and GET_TIME. The private function GET_PERIODICITY_NEXTVAL and related helpers support the sequence-driven population of periodicity identifiers.

Tables Accessed

The package reads and writes the core BSC system calendar tables: BSC_SYS_CALENDARS_B and its translation table BSC_SYS_CALENDARS_TL, BSC_SYS_CALENDAR_ID_S, BSC_SYS_PERIODICITIES and BSC_SYS_PERIODICITIES_TL, BSC_SYS_PERIODICITY_ID_S, and BSC_SYS_PERIODS and BSC_SYS_PERIODS_TL. These tables store calendar headers, multilingual descriptions, periodicity definitions, and individual period rows. It also references BSC_DB_CALENDAR for the DBI-side calendar staging data and BIS_LEVELS / BIS_LEVELS_TL for level definitions consumed from the BIS schema. FND_LANGUAGES and FND_LOOKUP_VALUES provide language and lookup validation data, while DUAL and PLITBLM are used for standard PL/SQL constructs.

Usage Notes

BSC_DBI_CALENDAR is typically invoked during DBI and BSC implementation and maintenance cycles rather than interactively by end users. It is called by the BSC_ADAPTER and related BSC/BIS dimension public packages (BSC_BIS_DIMENSION_PUB, BSC_BIS_DIM_OBJ_PUB) during dimensional loads, and by BSC_AW_CALENDAR, BSC_AW_MD_API, and BSC_AW_MD_WRAPPER during analytics warehouse metadata operations. Automating calendar refreshes through concurrent program wrappers or scheduled database jobs is the intended operational pattern; direct calls from custom code should be limited to the documented loader signatures and executed after verifying that dependent BSC system tables contain no conflicting definitions.