Search Results bsc_time_dim_test




Overview
Explore in AI Chat

Overview

APPS.BSC_TIME_DIM_TEST is a PL/SQL package that resides in the APPS schema and is classified under the ETRM registry with an API classification of OTHER. It forms part of the Oracle Balanced Scorecard (BSC) technology stack, which provides the analytical foundation for the enterprise performance management features embedded in Oracle E-Business Suite 12.1.1 and 12.2.2.

The package implements the Oracle Diagnostic Framework contract used to validate the configuration and integrity of the time dimension within the Balanced Scorecard data model. In Balanced Scorecard terminology, the time dimension is the structure that organizes calendars, periodicities, and periods so that measures and key performance indicators can be aggregated and compared across consistent time slices. The BSC_TIME_DIM_TEST package exists to diagnose whether these time-related objects are correctly defined and accessible, and to report the outcome through the standard JTF diagnostic reporting mechanism. The package metadata shows a status of VALID with both a package specification and package body present.

Key Procedures and Functions

The ETRM documentation records eight procedures and functions within this package:

  • INIT — Initializes the test run, preparing internal state and diagnostic input before any checks are executed.
  • GETDEFAULTTESTPARAMS — Supplies the default parameter values used when the diagnostic is launched without explicit user input.
  • CLEANUP — Releases resources and removes temporary artifacts created during the test execution.
  • RUNTEST — The principal driver that executes the time dimension validation logic and assembles the result set.
  • GETCOMPONENTNAME — Returns the name of the component being diagnosed, used for reporting and classification.
  • GETTESTNAME — Returns the display name of the diagnostic test.
  • GETTESTDESC — Returns the descriptive text that explains the purpose of the test to the end user.
  • GETTESTMODE — Returns the execution mode in which the diagnostic should operate.

Together these routines satisfy the standard diagnostic package interface, allowing the Oracle Diagnostic Framework to invoke, describe, and report the test without bespoke integration code.

Tables Accessed

The package references the following tables through APPS synonyms:

  • BSC_SYS_CALENDARS_B — The base table holding Balanced Scorecard calendar definitions.
  • BSC_SYS_PERIODICITIES — Stores periodicity definitions that determine how time is bucketed.
  • BSC_SYS_PERIODS and BSC_SYS_PERIODS_TL — The base and translated period definitions, providing language-specific period names.
  • FII_TIME_DAY — The day-level time dimension table from the Oracle Financial Intelligence/warehouse schema.
  • ALL_INDEXES — The data dictionary view used to verify that the expected indexes exist on the time dimension tables.

Reads against these objects allow the package to confirm that calendars, periodicities, and periods are present and that supporting indexes are in place. The package also depends on the JTF_DIAG_INPUTTBL and JTF_DIAG_REPORT tables, which carry input parameters and capture diagnostic output respectively.

Usage Notes

BSC_TIME_DIM_TEST is a diagnostic utility rather than a transactional API; it is not intended to be called from application forms or concurrent programs as part of normal business processing. The ETRM metadata records that the package is referenced by no other packages, confirming its role as a standalone diagnostic endpoint.

Typical invocation occurs through the Oracle Diagnostics or Diagnostic Framework user interface, where an administrator selects the Balanced Scorecard time dimension test and the framework calls INIT, GETDEFAULTTESTPARAMS, RUNTEST, and CLEANUP in sequence. Custom code may invoke the package directly when performing system health checks during implementation or upgrade projects on EBS 12.1.1 or 12.2.2, particularly after applying patches that modify Balanced Scorecard or time dimension metadata. Because the package is owned by APPS and marked VALID, it can be executed by any user granted execute privilege on it.