Search Results get_calendar_name

Overview

APPS.BSC_AW_CALENDAR is a PL/SQL package body in the Oracle E-Business Suite Balanced Scorecard (BSC) module. Its primary business function is to manage the lifecycle of analytic workspace (AW) calendar objects that underpin time-based performance measurement in Oracle Balanced Scorecard and related ETRM (Enterprise Territory and Resource Management) reporting. In Oracle EBS 12.1.1 and 12.2.2, the Balanced Scorecard leverages Oracle OLAP analytic workspaces to store multidimensional KPI data; the calendar dimension is fundamental to this model because scorecards, periodicities, and time-phased KPI results depend on a consistent definition of years, quarters, months, and other periods.

This package encapsulates the DDL and metadata operations required to create, load, normalize, and purge calendar structures within those analytic workspaces. It bridges relational calendar definitions held in EBS tables with the physical OLAP objects created through the DBMS_AW and DBMS_SQL infrastructure. The package is owned by APPS, is classified as OTHER, and is documented at status VALID. It is not referenced by any database object, but it depends on a substantial set of BSC packages and tables, indicating it sits near the top of the BSC customization stack and is intended to be invoked directly rather than consumed as a dependent library by other packages.

Key Procedures and Functions

The package exposes 46 documented procedures and functions. Representative members include:

• CREATE_CALENDAR — establishes the calendar definition for an analytic workspace.
• CREATE_CALENDAR_OBJECTS and DROP_CALENDAR_OBJECTS — create and remove the physical OLAP calendar objects.
• CREATE_CALENDAR_PROGRAM and CREATE_CALENDAR_METADATA — register supporting programs and metadata records.
• LOAD_CALENDAR and PURGE_CALENDAR — populate and clean up calendar dimension data.
• CHECK_CALENDAR_CREATE and CHECK_CALENDAR_LOADED — validation functions used before create or load operations.
• GET_CALENDAR_NAME, GET_CALENDAR_CURRENT_YEAR, and GET_KPI_FOR_CALENDAR — retrieval helpers.
• GET_PERIODICITY_DIM_NAME, GET_PERIODICITY_R, GET_CHILD_PERIODICITIES, and GET_ALL_LOWER_PERIODICITIES — periodicity navigation and hierarchy resolution.
• NORMALIZE_PER_RELATION — normalizes period-to-period relationships in the calendar hierarchy.
• SET_CALENDAR_PROPERTIES and ATTACH_WORKSPACE — configure and bind the calendar to a workspace.
• DMP_CALENDAR — data manipulation and propagation routine.

Tables Accessed

The package reads and writes several relational tables through APPS synonyms, including BSC_DB_CALENDAR, BSC_OLAP_OBJECT, BSC_OLAP_OBJECT_RELATION, BSC_SYS_CALENDARS_B, and BSC_SYS_PERIODICITIES. These hold the calendar definitions, OLAP object registrations, object relationships, and system periodicity configurations. It also uses DBMS_SQL and PLITBLM for dynamic SQL and PL/SQL table operations. Dependency metadata lists additional BSC packages such as BSC_AW_ADAPTER_KPI, BSC_AW_BSC_METADATA, BSC_AW_DBMS_AW, BSC_AW_MANAGEMENT, BSC_AW_MD_API, BSC_AW_MD_WRAPPER, BSC_AW_UTILITY, BSC_METADATA, and FND_LOG.

Usage Notes

APPS.BSC_AW_CALENDAR is typically invoked directly during Balanced Scorecard setup and administration, including the creation and maintenance of analytic workspace calendars, concurrent processing of calendar loads, and periodic purges. Although the documented metadata shows no inbound references, traceability to FND_LOG and the BSC_AW_* family indicates it participates in EBS logging and AW orchestration. Customizations should call the validation and creation procedures in sequence — checking prerequisites before creating objects, loading calendars, or setting properties — to preserve metadata and OLAP object integrity.