Search Results bsc_setup_data_rpt

Overview

APPS.BSC_SETUP_DATA_RPT is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. In the Oracle EBS architecture, the BSC prefix corresponds to the Balanced Scorecard application (part of the Oracle Enterprise Planning and Budgeting / EPM integration framework). Its status is documented as VALID in ETRM, indicating that the package compiles successfully and is available for execution within the application tier.

The package is classified as an OTHER API type, which distinguishes it from the standard public, private, or open-interface classifications. It functions as a setup verification and diagnostic reporting utility rather than as a transactional business API. Its procedural design—combining initialization, test parameter retrieval, execution, and cleanup routines—aligns it with the Oracle JTF Diagnostics framework (evidenced by the referenced JTF_DIAG_INPUTTBL and JTF_DIAG_REPORT objects) used to validate configuration integrity across the application.

Key Procedures and Functions

The package exposes eight documented procedures and functions, collectively supporting a diagnostic lifecycle:

• INIT — Initializes package state and prepares the diagnostic run, establishing the execution context before test parameters are fetched.
• GETDEFAULTTESTPARAMS — Retrieves the default parameter values used to drive the test execution when no user-supplied overrides are present.
• RUNTEST — Executes the diagnostic test logic, gathering setup data and evaluating the conditions defined for the report.
• CLEANUP — Releases resources and resets state after the test completes, ensuring no residual locks or temporary data persist.
• GETCOMPONENTNAME — Returns the name of the application component being validated.
• GETTESTNAME — Returns the identifier of the specific diagnostic test.
• GETTESTDESC — Returns the human-readable description of the test for inclusion in the diagnostic report output.
• GETTESTMODE — Returns the mode under which the test operates, governing whether execution is interactive, batched, or reporting-only.

Tables Accessed

The documented dependency list identifies two primary tables accessed via APPS synonyms:

• JTF_DIAG_INPUTTBL — The diagnostics input table, which stores the parameters and test definitions consumed during INIT and GETDEFAULTTESTPARAMS. The package reads from this table to determine what should be tested and with which values.
• JTF_DIAG_REPORT — The diagnostics report table, where RUNTEST writes its findings. The report-generation output is persisted here for subsequent retrieval or display.

Additionally, the package references V$VERSION, the dynamic performance view that exposes database version information. This reference supports environment-verification logic, confirming that the underlying database platform matches the expected release for the diagnostic run.

Usage Notes

BSC_SETUP_DATA_RPT is typically invoked through the JTF Diagnostics infrastructure rather than called directly by end users or custom business code. Within the Oracle EBS Diagnostics framework, administrators launch diagnostic tests that internally trigger INIT, RUNTEST, and CLEANUP in sequence, with the GET* functions supplying descriptive metadata to the report viewer. Because it is classified as an OTHER API and not a public interface, it should not be treated as a supported integration point.

The ETRM metadata records that no other packages reference this package, confirming its role as a leaf-level diagnostic component with no inbound program dependencies. Custom development should avoid direct invocation; instead, use the standard Diagnostics responsibility to run the associated setup data validation. This package is most relevant to functional consultants and DBAs verifying Balanced Scorecard setup completeness during implementation, cloning, or post-patching validation activities in both 12.1.1 and 12.2.2 environments.