Results for “bsc_user_parameters_b_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BSC.BSC_USER_PARAMETERS_B is a transactional configuration table within the Balanced Scorecard (BSC) product family of Oracle E-Business Suite. It persists parameter definitions that govern how portlets, indicators, and analytical views are rendered and evaluated for a given application context. In practice, the table acts as a repository of user- or role-scoped presentation parameters: which measures are analysed, which dimensions are displayed, what time period and data series are applied, and which calculations or benchmarks are attached to a scorecard view.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10 and is owned by the BSC schema, with FND design data registered as BSC.BSC_USER_PARAMETERS_B. Its primary key is BSC_USER_PARAMETERS_B_PK on PARAM_LIST_ID, and the unique index BSC_USER_PARAMETERS_B_U1 (the object referenced in the user's search) enforces uniqueness on PARAM_LIST_ID itself.

From a Data Vault modelling perspective, the metadata's heuristic classification is standalone. This suggests the table behaves as an independent reference or configuration set rather than as a hub or link participating in a shared business-key network; if modelled formally, it would most plausibly map to a hub or a small reference satellite keyed on PARAM_LIST_ID, with no documented foreign-key dependencies to sibling BSC tables.

Key Information Stored

The table has 25 documented columns. The most operationally significant are:

• PARAM_LIST_ID — Surrogate primary key and the sole column of unique index BSC_USER_PARAMETERS_B_U1; it uniquely identifies each parameter list.
• APPLICATION_ID — Identifies the Oracle EBS application context to which the parameter set belongs.
• INDICATOR — The indicator code whose rendering the parameter list controls.
• VIEW_TYPE — Numeric discriminator describing the type of view (for example scorecard versus trend presentation).
• VALID_FLAG — Status flag indicating whether the parameter row is currently active.
• ANALYSIS_MEASURES — The measure or measures selected for analysis.
• DIMENSION1 through DIMENSION10 — Up to ten dimension slots defining the analytical breakdown of the view.
• TIME_PERIOD — The reporting period applied to the analysis.
• DATA_SERIES — The data series from which values are sourced.
• CALCULATIONS — Calculation definition applied to the measures.
• BENCHMARKS — Benchmark or target reference used for comparison.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY and LAST_UPDATE_LOGIN provide audit traceability.

A secondary non-unique index, BSC_USER_PARAMETERS_B_U2, covers APPLICATION_ID, INDICATOR and VIEW_TYPE, supporting the most common lookup path used by the application when resolving parameters for a specific indicator and view.

Common Use Cases and Queries

Typical usage centres on resolving the rendering parameters for a scorecard or portlet, auditing which indicator/view combinations are configured, and diagnosing mismatches between stored configuration and expected presentation.

• Retrieve the active parameter list for a given application, indicator and view type using the U2 index path.
• Audit inactive or stale configurations by filtering on VALID_FLAG.
• Report on dimension usage across parameter sets to understand the analytical model applied to each indicator.
• Reconcile configuration drift by comparing CALCULATIONS, BENCHMARKS and TIME_PERIOD values across applications.

A representative query is:

SELECT PARAM_LIST_ID, APPLICATION_ID, INDICATOR, VIEW_TYPE, TIME_PERIOD, DATA_SERIES
FROM BSC.BSC_USER_PARAMETERS_B
WHERE APPLICATION_ID = :app AND INDICATOR = :ind AND VIEW_TYPE = :vt AND VALID_FLAG = 1;

For dimension analysis, selecting DIMENSION1 through DIMENSION10 alongside PARAM_LIST_ID allows reporting teams to map the configured analytical axes for each indicator without joining to other objects, since the table is self-contained.

Related Objects

The documented metadata classifies this table as standalone with no foreign-key relationships to other BSC objects. The relationships that matter operationally are therefore index- and component-level rather than declarative:

• BSC_USER_PARAMETERS_B_PK — Primary-key constraint on PARAM_LIST_ID, enforcing row identity.
• BSC_USER_PARAMETERS_B_U1 — Unique index on PARAM_LIST_ID; the object referenced in the search term.
• BSC_USER_PARAMETERS_B_U2 — Non-unique index on APPLICATION_ID, INDICATOR and VIEW_TYPE; the primary access path for application lookups.
• FND_APPLICATION — Resolves APPLICATION_ID to an application short name and description for reporting and diagnostics.
• BSC indicator and portlet definition tables — Consume PARAM_LIST_ID indirectly through application logic; because no FK is documented, joins must be validated against the BSC data model for the specific release.

Administrators should note that, in the absence of enforced referential integrity, orphaned PARAM_LIST_ID values may persist after configuration changes. Periodic reconciliation against the consuming portlet and indicator definitions in the BSC schema is therefore advisable.