Search Results update_fiscal_change




Overview
Explore in AI Chat

Overview

BSC_CALENDAR_PVT is a private PL/SQL package in the APPS schema that belongs to the Oracle Balanced Scorecard (BSC) application family, which in Oracle E-Business Suite 12.1.1 and 12.2.2 is delivered as part of the ETRM/Performance Management module set. The package encapsulates the low-level implementation logic for creating, modifying, and deleting scorecard calendars and their associated periods, fiscal year definitions, and translated period names. As its PVT classification indicates, it is not a public API; it is the private worker package behind the public BSC_CALENDAR_PUB interface. In Oracle EBS design standards, a *_PUB package exposes a stable, documented signature for external and internal callers, while the corresponding *_PVT package performs the actual DML against the underlying tables. BSC_CALENDAR_PVT therefore serves as the engine that maintains the calendar dimension used by Balanced Scorecard KPIs, scorecards, and periodicities, ensuring that period definitions, language-specific names, and week mappings remain internally consistent.

Key Procedures and Functions

The documented package exposes five procedures that together cover the full calendar maintenance lifecycle:

  • CREATE_CALENDAR — Creates a new scorecard calendar definition, establishing the base row in the system calendars tables and its translated name records.
  • UPDATE_CALENDAR — Modifies an existing calendar definition, allowing attributes such as the calendar name and descriptive fields to be changed.
  • DELETE_CALENDAR — Removes a calendar and its dependent period and naming data, subject to referential-integrity checks against scorecard usage.
  • UPDATE_FISCAL_CHANGE — Adjusts fiscal year change behavior for a calendar, supporting organizations whose fiscal calendars do not align with the standard calendar year.
  • UPDATE_PERIODNAMES_IN_CALENDAR — Updates or regenerates the period names associated with a calendar, including translated (TL) name records across installed languages.

Because these are private procedures, parameter lists are not published; callers are expected to invoke the corresponding public wrappers in BSC_CALENDAR_PUB rather than calling BSC_CALENDAR_PVT directly.

Tables Accessed

The package reads and writes a defined set of APPS-synonymed tables. BSC_SYS_CALENDARS_B and BSC_SYS_CALENDARS_TL hold the base and translated calendar records. BSC_SYS_PERIODS and BSC_SYS_PERIODS_TL store the period definitions and their translated names. BSC_SYS_PERIODICITIES and BSC_SYS_PERIODICITIES_TL, together with BSC_KPI_PERIODICITIES, define how periods map to KPI periodicity groupings. BSC_DB_CALENDAR and BSC_DB_WEEK_MAPS support week-level mapping used in period generation. BSC_SYS_DIM_LEVELS_TL and BIS_LEVELS_TL provide dimension-level descriptions used when validating calendar structure. BSC_SYS_INIT holds initialization/configuration values, and FND_LANGUAGES supplies the set of installed languages so that translations can be created or updated. Dependencies are bidirectional with BSC_CALENDAR_PUB, which both calls and is called by this package.

Usage Notes

BSC_CALENDAR_PVT is normally invoked indirectly. The Oracle Balanced Scorecard administrative forms and concurrent programs call BSC_CALENDAR_PUB, which in turn delegates the DML work to this private package. Custom integrations or extensions that need calendar maintenance should likewise call the public package rather than the private one, because the PVT layer carries no compatibility guarantee across patches. Direct invocation is occasionally observed in diagnostic or data-fix scripts, but such usage should be limited to Oracle-supported scenarios. Because the package touches translated tables and the FND_LANGUAGES list, calendar changes may generate or require translation rows and therefore should be run in an environment where language setup is complete.