Search Results bsc_objective_metadata_setup




Overview
Explore in AI Chat

Overview

The APPS.BSC_OBJECTIVE_METADATA_SETUP package is a diagnostic and setup utility within the Oracle E-Business Suite Balanced Scorecard (BSC) module. It belongs to the Oracle Diagnostic Framework (ODF), as evidenced by its dependencies on JTF_DIAG_INPUTTBL and JTF_DIAG_REPORT, the shared diagnostic infrastructure tables used across EBS applications. The package implements the standard diagnostic test interface: it exposes routines that initialize a test run, declare default parameters, execute the test logic, and return results to the framework.

Functionally, the package validates the metadata configuration underlying BSC objectives and their associated dimensions. Because Balanced Scorecard reporting depends on correctly defined objectives, dimension levels, and time members, inconsistencies in this metadata can corrupt scorecard output. This package serves as a self-check that surfaces such inconsistencies before they affect users. It is classified as an OTHER API, indicating it is not a public business API but an internal support utility, and it is owned by the APPS schema with status VALID in both 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM documentation for 12.1.1 records nine procedures and functions. Consistent with the diagnostic framework contract, they fall into two groups:

  • INIT — Initializes the diagnostic test, preparing the runtime context required before execution.
  • GETDEFAULTTESTPARAMS — Supplies the framework with the default input parameters that govern the test run.
  • CLEANUP — Releases resources and resets state after the test completes.
  • RUNTEST — Executes the core diagnostic logic, evaluating objective metadata and writing findings to the diagnostic report.
  • GETCOMPONENTNAME — Returns the component name associated with the test for reporting and registration.
  • GETTESTNAME — Returns the display name of the diagnostic test.
  • GETTESTDESC — Returns the descriptive text explaining the test's purpose to the end user.
  • GETTESTMODE — Returns the mode in which the test operates (for example, whether it is read-only or corrective).
  • GET_MESSAGE_NAME — Resolves the message name used to retrieve translatable text and output messages.

No parameter lists are documented in the ETRM extract; the descriptions above reflect the standardized diagnostic interface responsibilities of each routine.

Tables Accessed

Per the documented metadata, the package references BSC_SYS_INIT through an APPS synonym. This table holds Balanced Scorecard system initialization and configuration data, and it is the logical source for objective-related metadata settings that the diagnostic verifies. In addition, the dependency list shows direct references to JTF_DIAG_INPUTTBL, which carries framework-supplied input parameters, and JTF_DIAG_REPORT, into which test findings are written. Only two application-level tables plus the diagnostic infrastructure tables are documented.

Usage Notes

This package is not intended for direct invocation by end users or custom code. It is invoked by the Oracle Diagnostic Framework when an administrator or support engineer runs BSC diagnostic tests, typically from the Diagnostic Testing UI or through the concurrent diagnostic framework. The documented reverse dependencies confirm this: it is referenced by report packages including BSC_CORRUPT_OBJECTS_RPT, BSC_INVALID_DIM_LVLS_RPT, BSC_PMA_DIAG_TEST, BSC_SETUP_DATA_RPT, and BSC_TIME_DIM_TEST, and by itself for recursive or self-referential logic. These dependents are diagnostic and reporting utilities rather than transactional programs, reinforcing that BSC_OBJECTIVE_METADATA_SETUP is a support-focused package. Because it is not a public API, it should not be called from custom extensions; any invocation should occur exclusively through the supported diagnostic framework.