Search Results is_dbi_calendar_enabled




Overview
Explore in AI Chat

Overview

The APPS.BSC_CALENDAR_WRAPPER package is a PL/SQL wrapper component within the Oracle E-Business Suite Balanced Scorecard (BSC) module. It provides a controlled, application-layer interface for managing the calendar definitions that underpin the Balanced Scorecard performance management framework. In Oracle EBS, calendars serve as the fundamental time-dimension construct against which scorecard metrics, targets, and actuals are compared across defined periods. The BSC module relies on these calendar definitions to align measurement periods, roll up results, and drive time-based analytics.

The package abstracts direct data manipulation away from calling code, exposing a set of wrapper procedures that encapsulate the business logic and integrity checks required when creating, modifying, or removing calendar definitions. Its status is VALID in the documented environment, and it is owned by the APPS schema, consistent with most seeded EBS application logic. The dependency information indicates that BSC_CALENDAR_WRAPPER references the SYS STANDARD package, meaning it leverages Oracle's built-in PL/SQL functionality (such as error handling and standard runtime behavior) at the language level rather than depending on other application packages. This positions it as a relatively self-contained unit whose logic is largely internal.

Key Procedures and Functions

The ETRM documentation records four procedures or functions within this package:

  • CREATE_CALENDAR_UI — Provides the user-interface-facing entry point for creating a new Balanced Scorecard calendar definition. This procedure is intended to be invoked when a user or process introduces a new calendar into the scorecard framework.
  • UPDATE_CALENDAR_UI — Supports modification of an existing calendar definition. It handles the changes a user makes to calendar attributes through the corresponding UI layer.
  • DELETE_CALENDAR_UI — Manages the removal of a calendar definition, providing a controlled deletion path so that referential and business-rule constraints can be respected.
  • IS_DBI_CALENDAR_ENABLED — A function that returns an indicator of whether the DBI (Daily Business Intelligence) calendar capability is enabled. This is used by calling code to conditionally branch behavior based on that configuration setting.

The naming convention (the _UI suffix) strongly suggests these routines are designed for invocation from the BSC administrative user interface rather than for bulk or background processing. No parameter lists are documented, so their exact signatures should be confirmed against the live package specification.

Tables Accessed

The provided ETRM metadata does not enumerate specific tables referenced via APPS synonyms. Based on the functional purpose of the package—calendar creation, update, and deletion within the Balanced Scorecard model—the underlying logic would be expected to operate against the BSC calendar and period definition tables maintained by the scorecard application. Because the documented dependency list shows only the SYS STANDARD package and no additional APPS package references, the data access is likely performed directly through DML or queries internal to the package body rather than being delegated to other seeded APIs.

Usage Notes

This package is typically invoked indirectly through the Oracle Balanced Scorecard administrative forms and setup screens, where calendar maintenance is performed by authorized users. The IS_DBI_CALENDAR_ENABLED function is commonly called by other application logic to determine whether DBI calendar integration is active before presenting or processing calendar options. The metadata states that BSC_CALENDAR_WRAPPER is referenced by zero other packages, indicating it is a leaf-level dependency invoked from the UI layer and not a shared utility consumed by peer packages. Custom code should avoid calling these procedures outside their intended UI context, since bypassing the forms layer may skip validation performed elsewhere in the BSC application. Any direct invocation should be validated against the actual package specification in the target EBS release (12.1.1 or 12.2.2), as the documented metadata is limited to object existence and procedure names.