Search Results create_calendar_program

Overview

APPS.BSC_AW_CALENDAR is a PL/SQL package belonging to the Oracle Balanced Scorecard (BSC) analytics infrastructure in Oracle E-Business Suite. Its primary responsibility is the creation, management, and maintenance of calendar and periodicity metadata used by the Analytics Workspace (AW) engine. Specifically, the package translates the business calendar definitions stored in the BSC schema into the dimensional and relational structures required by the analytical workspaces, including the mapping between BSC period values and AW time dimensions such as aw_day and aw_month.

The package is particularly relevant in EBS 12.1.1 and 12.2.2 environments where Balanced Scorecard reporting depends on OLAP-based time dimensions. Searches for the procedure CREATE_CALENDAR_PROGRAM typically originate from administrators attempting to understand, schedule, or troubleshoot the concurrent program that drives calendar generation. The package is classified as OTHER in the ETRM repository and is referenced by eleven other packages, indicating it is a foundational utility rather than an end-user-facing API.

Key Procedures and Functions

The package exposes forty-six documented procedures and functions. The most prominent are summarized below:

• CREATE_CALENDAR — Master procedure responsible for building a calendar definition and its associated dimensional objects.
• CREATE_CALENDAR_PROGRAM — Entry point intended to be invoked as, or on behalf of, a concurrent program to generate a calendar. It orchestrates the creation workflow so the operation can run in a scheduled background job.
• CREATE_CALENDAR_OBJECTS — Creates the underlying OLAP and relational objects (dimensions, relations, tables) that represent the calendar in the analytics workspace.
• CREATE_CALENDAR_METADATA — Populates metadata records describing the calendar's structure, periodicity mappings, and dimensional relationships.
• LOAD_CALENDAR — Loads time-member data into the previously created calendar objects.
• DROP_CALENDAR_OBJECTS and PURGE_CALENDAR — Remove calendar objects and metadata, supporting cleanup and re-creation cycles.
• CHECK_CALENDAR_CREATE and CHECK_CALENDAR_LOADED — Validation routines confirming whether a calendar can be created or has already been loaded.
• GET_PERIODICITY_DIM_NAME, GET_PERIODICITY_R, GET_ALL_LOWER_PERIODICITIES, GET_CHILD_PERIODICITIES — Retrieval helpers for periodicity definitions and their parent-child hierarchies (for example, deriving days from a month).
• NORMALIZE_PER_RELATION — Normalizes periodicity relation names between BSC and AW naming conventions.
• DMP_CALENDAR — Data movement procedure used in the calendar generation pipeline.
• SET_CALENDAR_PROPERTIES and GET_CALENDAR_NAME — Manage and retrieve calendar attribute properties.
• GET_KPI_FOR_CALENDAR — Identifies KPIs associated with a given calendar.
• ATTACH_WORKSPACE — Associates a workspace with the calendar definition.
• GET_CALENDAR_CURRENT_YEAR — Returns the current reporting year for the calendar.

Tables Accessed

The package reads and writes several BSC repository tables through APPS synonyms:

• BSC_SYS_CALENDARS_B — Stores base calendar definitions; read to determine names and configuration and written when new calendars are registered.
• BSC_SYS_PERIODICITIES — Holds periodicity definitions (day, month, year, etc.) used for building hierarchies.
• BSC_DB_CALENDAR — Holds calendar data used during load and generation operations.
• BSC_OLAP_OBJECT and BSC_OLAP_OBJECT_RELATION — Record the OLAP objects and relationships created by the package, forming the bridge to the AW engine.
• DBMS_SQL and PLITBLM — Oracle-supplied packages used for dynamic SQL execution and PL/SQL table handling, evidenced by the g_stmt, g_commands, and g_init package globals.

Usage Notes

BSC_AW_CALENDAR is not intended for direct ad-hoc invocation by end users. It is typically called by the Balanced Scorecard administration layer when a calendar is being created, loaded, or purged, and CREATE_CALENDAR_PROGRAM indicates a concurrent-program pathway where calendar generation is submitted as a scheduled job from the System Administrator responsibility. Because the package depends on OLAP object infrastructure and is referenced by eleven other packages, calendar creation should be sequenced carefully—validate with CHECK_CALENDAR_CREATE, generate with CREATE_CALENDAR_PROGRAM, load with LOAD_CALENDAR, and clean up with PURGE_CALENDAR or DROP_CALENDAR_OBJECTS as needed. Custom code should call these procedures only after confirming the target workspace and periodicity definitions exist, since the package populates OLAP metadata that other BSC analytics components rely upon.