Search Results bsc_bsc_xtd_pkg




Overview
Explore in AI Chat

Overview

BSC_BSC_XTD_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Oracle Balanced Scorecard (BSC) product family, which is part of the broader Oracle Enterprise Performance Management and Daily Business Intelligence stack. The package is classified as an OTHER API, meaning it is not a published, externally supported integration interface but rather an internal utility package used by the Balanced Scorecard application itself.

The core business purpose of BSC_BSC_XTD_PKG is the management of report key records and their associated calendar and periodicity metadata. In the Balanced Scorecard model, KPIs and reports are evaluated against defined time periods such as daily, weekly, monthly, or quarterly cycles. The package builds, corrects, and maintains the report key tables that map periodicities and calendars to reporting structures, and it generates derived date and count values required to align KPI results with those periods. Its status is VALID, confirming it compiles cleanly in the documented environment.

Key Procedures and Functions

The documented package exposes 21 procedures and functions. The principal ones include:

Tables Accessed

The package references the following tables through APPS synonyms:

  • BSC_RPT_KEYS — The primary report key store that the populate, insert, and delete routines maintain.
  • BSC_KPI_PERIODICITIES and BSC_SYS_PERIODICITIES — Define the periodicity options against which report keys are generated.
  • BSC_SYS_CALENDARS_B — Supplies base calendar definitions used to align report keys to fiscal/calendar periods.
  • ALL_TABLES — Used in DDL-related logic to verify existence before create or drop operations.
  • PLITBLM — A PL/SQL internal table type, not a persistent business table.

Additional dependencies include BSC_APPS, BSC_IM_UTILS, BSC_RPT_KEYS, FND_INSTALLATION, and SYS.STANDARD.

Usage Notes

BSC_BSC_XTD_PKG is invoked internally by the Balanced Scorecard application rather than by end users directly. It is typically called from concurrent programs, initialization routines, or other BSC packages (it is referenced by two other packages) during scorecard setup, period rollover, or data correction activities. Because it performs DDL (create/drop table) and mass inserts/deletes, it is most commonly executed during administrative maintenance windows or as part of scheduled report key generation. Its documented procedures are not intended as a public extension API, so custom development should avoid direct calls and instead rely on supported Oracle Balanced Scorecard interfaces.