Search Results bsc_user_kpilist_kpis

Overview

BSC_USER_KPILIST_KPIS is a table in the BSC (Balanced Scorecard) product schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. The ETRM description identifies it as holding "portlet information by user" — that is, the association between a user-facing portlet plug (a configurable dashboard region or container) and the parameter list that determines which KPIs the portlet renders for that user. It is an internal configuration table rather than a transactional or analytical fact table; it controls personalization and layout behavior for the Balanced Scorecard dashboards, not the KPI measurement values themselves.

The metadata's heuristic Data Vault classification is standalone, meaning no foreign keys were mined from the physical schema. As a modeling suggestion, this suggests the table should be treated as an independent link-style association record rather than a satellite attached to a parent hub; its two key columns together express the association, and the remaining columns are standard EBS who-columns (audit and concurrency attributes).

Key Information Stored

The documented physical schema contains seven columns. The primary key constraint BSC_USER_KPILIST_KPIS_PK is defined over the composite of PLUG_ID and PARAM_LIST_ID, and a unique index, BSC_USER_KPILIST_KPIS_U1, covers the same two columns — so in this object the surrogate/composite primary key and the business-key candidate are effectively the same pair, with no separate single-column surrogate identifier.

• PLUG_ID — identifies the portlet plug (the dashboard container or region instance) to which the KPI parameter list is bound. First component of the primary key and of the unique index.
• PARAM_LIST_ID — identifies the parameter list (the set of KPI definitions and their parameters) presented within that plug for the user. Second component of the primary key and unique index.
• CREATION_DATE — date the association row was created.
• CREATED_BY — the application user ID credited with creating the row.
• LAST_UPDATE_DATE — date of the most recent modification; the standard EBS change-detection column for incremental extracts.
• LAST_UPDATED_BY — application user ID credited with the last modification.
• LAST_UPDATE_LOGIN — login/session identifier associated with the last update, used for audit and concurrent-program traceability.

The absence of WHO-column pairs beyond the five audit fields, and of any additional descriptive attributes, indicates a lean association table whose semantics are carried entirely by the two key values.

Common Use Cases and Queries

Typical use cases center on diagnosing why a user or responsibility sees a particular set of KPIs in a dashboard portlet, auditing personalization changes, and migrating or comparing configuration between environments (for example, development to production).

• Resolving the parameter list used by a given portlet: SELECT PARAM_LIST_ID FROM BSC_USER_KPILIST_KPIS WHERE PLUG_ID = :plug_id;
• Identifying which ports reference a shared parameter list: SELECT PLUG_ID FROM BSC_USER_KPILIST_KPIS WHERE PARAM_LIST_ID = :param_list_id;
• Change auditing over a deployment window: filtering on LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY to see who altered which portlet bindings.
• Configuration comparison: a full extract of PLUG_ID and PARAM_LIST_ID from two instances, diffed to locate configuration drift.
• Duplicate detection: because the unique index covers both key columns, any query returning more than one row per (PLUG_ID, PARAM_LIST_ID) pair indicates a schema or index integrity problem.

Related Objects

The documented metadata provides no foreign keys, so relationships are inferred from the key column names and the Balanced Scorecard data model; verify each against the actual instance before relying on it.

• BSC_USER_KPILIST_KPIS_PK — the primary key constraint over (PLUG_ID, PARAM_LIST_ID).
• BSC_USER_KPILIST_KPIS_U1 — unique index over the same two columns; the business-key candidate.
• BSC portlet/plug definition objects — the parent definitions referenced by PLUG_ID, which describe the dashboard container itself.
• BSC parameter list objects — the definitions referenced by PARAM_LIST_ID, which enumerate the KPI parameters rendered by the plug.
• BSC KPI and KPI list objects — hold the KPI metadata and measurements surfaced through the parameter list.
• FND_USER — join CREATED_BY and LAST_UPDATED_BY to USER_ID to attribute configuration changes to named users.
• FND_LOGINS — join LAST_UPDATE_LOGIN for session-level traceability of the most recent change.

Because the object is a standalone configuration table with seven columns, its reporting value is primarily operational: it explains dashboard behavior and supports configuration auditing rather than KPI analytics.