Search Results bsc_user_parameters_vl

Overview

BSC_USER_PARAMETERS_VL is a translated (_VL) view belonging to the Balanced Scorecard (BSC) product family in Oracle E-Business Suite. In releases 12.1.1 and 12.2.2 the BSC module is classified as Obsolete, meaning it is no longer delivered as part of the standard, supported EBS footprint and will not be implemented in a current database. The view therefore primarily serves as a compatibility and reference construct for legacy schemas, historical data migrations, and upgrade analyses rather than as an active reporting interface.

Functionally, the view supplies a single, language-resolved row per user parameter list by joining the base definition table and its translation table and filtering on the session language. This is the standard EBS _VL pattern: the "_B" table holds language-independent attributes and the "_TL" table holds the translatable short/long descriptions and titles. Reporting tools, concurrent programs, and integration layers that reference the view receive a title already resolved to USERENV('LANG'), which removes the need for the calling application to perform its own translation join.

Because the underlying object concerns user-defined Balanced Scorecard parameter lists, the view exposes the analytical building blocks — indicators, dimensions, measures, time periods, data series, calculations, and benchmarks — that a scorecard parameter definition requires. Records are keyed by PARAM_LIST_ID, the parameter list identifier, and carry standard EBS who-columns (creation and update audit fields) suitable for downstream auditing and incremental extraction.

Underlying Base Objects

The view is defined over exactly two base objects, as documented in the ETRM metadata:

• BSC_USER_PARAMETERS_B — the base (language-independent) table holding all operational columns: application context, indicator, view type, validity flag, analytical measures, the ten dimension slots, time period, data series, calculations, benchmarks, and the standard audit columns.
• BSC_USER_PARAMETERS_TL — the translation table supplying TITLE per language, joined on the shared key PARAM_LIST_ID.

The join predicate is B.PARAM_LIST_ID = TL.PARAM_LIST_ID combined with TL.LANGUAGE = USERENV('LANG'), so at most one translated title is returned for each parameter list in the current session language. An inner join is used, meaning a base row is exposed only when a translation exists for the active language; rows lacking a matching translation language are filtered out. No other base objects are documented as referenced.

Key Columns

• PARAM_LIST_ID — primary identifier of the parameter list; the join key between the _B and _TL tables.
• TITLE — the translated, user-facing name of the parameter list, sourced from the _TL table.
• APPLICATION_ID — the application context (e.g., the owning EBS application) for the parameter definition.
• INDICATOR and VIEW_TYPE — the scorecard indicator reference and the display/view mode of the parameters.
• VALID_FLAG — flag indicating whether the parameter set is currently valid and usable.
• ANALYSIS_MEASURES — the measures configured for analytical evaluation.
• DIMENSION1 through DIMENSION10 — up to ten dimension columns describing the analytical axes of the parameter list.
• TIME_PERIOD, DATA_SERIES, CALCULATIONS, BENCHMARKS — the temporal scope, source series, calculation definitions, and benchmark comparisons applied.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns inherited from the base table.

Common Use Cases and Queries

Legacy BSC reporting and upgrade remediation are the principal use cases. To list all parameter lists visible in the current language:

SELECT PARAM_LIST_ID, TITLE, APPLICATION_ID, VALID_FLAG FROM BSC_USER_PARAMETERS_VL ORDER BY PARAM_LIST_ID;

To inspect the analytical dimensions configured for a specific list:

SELECT TITLE, INDICATOR, VIEW_TYPE, DIMENSION1, DIMENSION2, DIMENSION3 FROM BSC_USER_PARAMETERS_VL WHERE PARAM_LIST_ID = :id;

To identify recently changed definitions for incremental extraction or audit:

SELECT PARAM_LIST_ID, TITLE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM BSC_USER_PARAMETERS_VL WHERE LAST_UPDATE_DATE > :since;

Query results depend on the session NLS language; environments without the corresponding _TL rows may return no data even where base records exist. Note the ETRM classification: BSC is obsolete and the view is not implemented in the documented database, so these queries are relevant chiefly for historical datasets and migration exercises.