Search Results bsc_calendar_pub




Overview
Explore in AI Chat

Overview

BSC_CALENDAR_PUB is the public API package within the Oracle E-Business Suite Balanced Scorecard (BSC) module, part of the Enterprise Performance Foundation / Strategic Enterprise Management (ETRM) product family. It exposes supported, externally callable entry points for creating, maintaining, and validating the calendar and periodicity definitions that underpin scorecard and KPI processing. A calendar in this context establishes the time periods (such as monthly, quarterly, or fiscal cycles) against which KPI targets and actuals are evaluated. The package resides in the APPS schema and holds VALID status. Because it is classified as a PUB package, its documented procedures form the sanctioned integration surface for external callers, in contrast to the private (PVT) counterparts that implement the underlying business logic. The package depends on standard Oracle SYS constructs and a set of BSC/BIS tables, and it operates alongside the companion packages BSC_CALENDAR_PVT and BSC_CALENDAR_WRAPPER.

Key Procedures and Functions

The package exposes twelve documented procedures and functions covering the full lifecycle of a calendar definition:

Tables Accessed

Through APPS synonyms, the package reads and writes the following tables. BSC_SYS_CALENDARS_B and its translation table BSC_SYS_CALENDARS_TL hold the base and language-specific calendar definitions. BSC_SYS_PERIODICITIES and BSC_KPI_PERIODICITIES store periodicity definitions and their KPI associations. BSC_SYS_DIM_GROUPS_TL provides dimension group translations, while BIS_DIMENSIONS and BIS_LEVELS supply the dimensional and level metadata used to align calendars with scorecard structures. BSC_KPIS_B, BSC_SYS_INIT, and BSC_DB_CALENDAR support KPI definitions, system initialization, and calendar working data respectively.

Usage Notes

BSC_CALENDAR_PUB is invoked by Oracle Balanced Scorecard setup forms, by concurrent programs that generate or refresh calendar and periodicity structures, and by custom integrations that need to manage scorecard calendars programmatically. The package is referenced by BSC_CALENDAR_PVT and BSC_CALENDAR_WRAPPER, and it in turn calls into BSC_CALENDAR_PVT for implementation logic. Because the public procedures are designed as a transactional API, callers should invoke them within a controlled transaction and always run VALIDATE_CALENDAR_ACTION before committing create, update, or delete operations. Custom code should call only the PUB procedures and avoid direct DML against the underlying BSC_SYS_CALENDARS tables, since post-action routines perform additional dependent maintenance.