Search Results bsc_user_parameters_b




Overview
Explore in AI Chat

Overview

BSC_USER_PARAMETERS_B is a Balanced Scorecard (BSC) module table within the Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. The BSC product line is classified as obsolete in the current ETRM documentation, and this object is explicitly noted as "Not implemented in this database." The table is described as holding indicator data for the information box — that is, the configurable parameter lists that drive how scorecard indicators and analytical views are presented to end users. Each row represents a named parameter list identified by PARAM_LIST_ID, capturing the dimensions, measures, time periods, and calculation settings that shape a scorecard information box.

From a Data Vault modeling perspective, the heuristic classification for this table is standalone, with no documented foreign-key dependencies to other tables. This suggests the object behaves as an independent reference or configuration entity rather than a hub or link participating in a broader integrated model. Where it is implemented, it functions as a business-configuration satellite whose natural business key is the parameter list identifier.

Key Information Stored

The table carries 25 documented columns. The most significant are:

  • PARAM_LIST_ID — the surrogate primary key, enforced by BSC_USER_PARAMETERS_B_PK and also backed by the unique index BSC_USER_PARAMETERS_B_U1, making it the business-key candidate as well.
  • APPLICATION_ID — identifies the owning application context for the parameter list.
  • INDICATOR — the scorecard indicator associated with this parameter configuration.
  • VIEW_TYPE — controls the presentation form of the information box.
  • VALID_FLAG — indicates whether the parameter list is active and usable.
  • ANALYSIS_MEASURES — the measures available for analytical display.
  • DIMENSION1 through DIMENSION10 — ten dimension slots that define the analytical axes available to the information box.
  • TIME_PERIOD — the temporal scope of the indicator data.
  • DATA_SERIES — the source series underpinning the indicator.
  • CALCULATIONS — stored calculation definitions applied to the measures.
  • BENCHMARKS — target or comparison values against which performance is evaluated.

The standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) provide audit and concurrency tracking.

Common Use Cases and Queries

Typical use cases center on retrieving and validating indicator presentation configuration. A common retrieval pattern selects active parameter lists for a given indicator:

SELECT param_list_id, indicator, view_type, time_period, data_series
FROM bsc_user_parameters_b
WHERE valid_flag = 'Y';

Reporting queries often pivot the ten dimension columns to enumerate which analytical axes are populated:

SELECT param_list_id, dimension1, dimension2, dimension3
FROM bsc_user_parameters_b
WHERE application_id = :app_id;

Because the table is documented as not implemented, verification queries against DBA_TAB_COLUMNS should precede any development effort. Where present, audit queries using LAST_UPDATE_DATE support change tracking, and join predicates on PARAM_LIST_ID support lookups from dependent presentation logic.

Related Objects

Formal foreign-key metadata classifies this table as standalone, so no FK relationships are documented. Related objects are therefore inferred from functional dependencies on the shared business key:

  • BSC_USER_PARAMETERS_B_PK — the primary-key constraint on PARAM_LIST_ID.
  • BSC_USER_PARAMETERS_B_U1 — the unique index on PARAM_LIST_ID, serving as the business-key candidate.
  • BSC_USER_PARAMETERS_TL — the translation table conventionally paired with the _B base table, joined on PARAM_LIST_ID.
  • BSC_INDICATORS_B / BSC_INDICATORS_TL — indicator definitions referenced through the INDICATOR column.
  • BSC_ANALYSIS_MEASURES — measure definitions that align with the ANALYSIS_MEASURES column.
  • FND_APPLICATION — resolves APPLICATION_ID to an application name.

Because the object is obsolete and not implemented, no supported public APIs are documented; any integration should be treated as legacy-only and validated against the target instance before reliance.