Search Results decompose_page_parameters




Overview

APPS.BSC_CAUSE_EFFECT_UI_WRAPPER is a PL/SQL package that belongs to the Oracle Balanced Scorecard (BSC) module, part of the Enterprise Performance Foundation / ETRM stack shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented API classification is OTHER, indicating it is an internal, product-owned wrapper rather than a published public API intended for customer extension. The package serves as the server-side presentation and data-access layer for the cause-and-effect diagram functionality in the Balanced Scorecard user interface. A cause-and-effect diagram (also known as a strategy map or fishbone model) expresses directional causal relationships between strategy elements, and the wrapper centralises the PL/SQL logic required to render, validate and persist those cause-and-effect relationships within the OAF or Forms-based Scorecard pages.

The object resides in the APPS schema with status VALID. Its dependency footprint is deliberately narrow: it references only SYS.STANDARD and is referenced by no other package, confirming that it is a terminal consumer in the call graph rather than a reusable service.

Key Procedures and Functions

The ETRM repository documents twelve procedures and functions in the package. Their names disclose the following purposes:

Tables Accessed

Through APPS synonyms the package touches four underlying objects. BSC_SYS_DATASETS_B and BSC_SYS_MEASURES supply the Balanced Scorecard measure and dataset metadata that defines the nodes displayed in a cause-and-effect diagram. FND_FORM_FUNCTIONS is queried by HAS_FUNCTION_ACCESS to evaluate responsibility-based function security. PLITBLM is the standard Oracle Forms PL/SQL table storage mechanism, used here for array handling and list decomposition support rather than for application data.

Usage Notes

BSC_CAUSE_EFFECT_UI_WRAPPER is invoked internally by the Balanced Scorecard HTML and Forms user interface whenever a user opens, edits or saves a cause-and-effect view. Because it is classified as OTHER and is referenced by no other package, Oracle does not guarantee its interface across releases. Customers should treat it as an unsupported internal object: it must not be called from custom concurrent programs or extensions, and any customisation should be performed only through supported BSC setup and personalisation frameworks.