Search Results update_calendar_ui




Overview
Explore in AI Chat

Overview

BSC_CALENDAR_WRAPPER is a PL/SQL wrapper package body in the APPS schema that serves as the interface layer between Oracle EBS user interface components and the underlying calendar business logic housed in BSC_CALENDAR_PUB. Its documented purpose is to accept calendar attribute values entered by a user on a UI form, populate a BSC_CALENDAR_PUB.Calendar_Type_Record structure with those values, and then delegate the actual create, update, or delete operation to the public API. This indirection keeps the UI layer decoupled from the packaged API and centralizes validation, message initialization, and error propagation.

The package is part of the Balanced Scorecard (BSC) product family, which uses calendars to define fiscal and time hierarchy structures for performance management reporting. ETRM classifies the package under API classification OTHER, indicating it is not a formally published public API but rather an internal UI-support wrapper.

Key Procedures and Functions

  • CREATE_CALENDAR_UI — Populates a calendar record with values supplied from the UI and invokes the create operation on BSC_CALENDAR_PUB. It is the documented entry point for new calendar definitions. The source excerpt confirms it accepts the full set of calendar attributes (calendar identifier, EDW flags, fiscal year and fiscal change indicators, range year modifier, current year, start month and day, name, help text, dimension short name, application identifier, base period identifiers, and standard WHO audit columns) and returns the standard API status triple.
  • UPDATE_CALENDAR_UI — Mirrors the create wrapper for modification of an existing calendar. It takes UI-supplied values, loads the calendar record, and delegates the update to the public API.
  • DELETE_CALENDAR_UI — The procedure located by the search term "delete_calendar_ui." It handles removal of a calendar record requested from the UI, passing the identifying key to the underlying public API and returning the standard return status, message count, and message data outputs. Locking APIs were added to the package in July 2005, so the delete path participates in the same record-locking discipline as create and update.
  • IS_DBI_CALENDAR_ENABLED — A function that reports whether the DBI (Daily Business Intelligence) calendar capability is enabled. It is used by the UI to conditionally control which calendar fields or behaviors are presented to the user.

Tables Accessed

The ETRM metadata lists no directly referenced tables for this package. This is consistent with its wrapper design: all persistence is performed by BSC_CALENDAR_PUB, which owns the DML against the BSC calendar tables. Any table access therefore occurs indirectly through the public API rather than through direct SQL in this package body.

Usage Notes

BSC_CALENDAR_WRAPPER is invoked from the Balanced Scorecard calendar maintenance UI rather than from concurrent programs or external integrations. The UI form calls CREATE_CALENDAR_UI, UPDATE_CALENDAR_UI, or DELETE_CALENDAR_UI depending on the user action, supplying the calendar attributes and audit information, and then inspects x_Return_Status, x_Msg_Count, and x_Msg_Data to determine success or to display errors raised through FND_MSG_PUB. The package initializes the message stack (FND_MSG_PUB.Initialize) at the start of each call and defaults the return status to FND_API.G_RET_STS_SUCCESS. Because the package is classified as OTHER and is referenced by no other packages, custom code should call BSC_CALENDAR_PUB directly rather than this wrapper, which exists solely to service the standard forms interface.