Search Results bsc_user_kpigraph_plugs

Overview

BSC_USER_KPIGRAPH_PLUGS is a table within the BSC (Balanced Scorecard) product schema in Oracle E-Business Suite, documented under ETRM for releases 12.1.1 and 12.2.2. Its stated purpose is the storage of portlet information by user. In practical terms, the table records which scorecard KPI graph portlets a given application user has configured for display, together with the responsibility context and the rendering parameters that determine how each portlet behaves. It is the personalization layer that sits between the shared KPI graph definition and the individual user's dashboard, allowing different users to see different graph portlets without altering the underlying indicator definitions.

The ETRM metadata classifies this object heuristically as standalone in the Data Vault sense, meaning no foreign key relationships were mined into the FK structure and it is not modeled as a hub, link, or satellite. From a modeling perspective this should be treated as a suggestion rather than a constraint: the presence of a composite natural identifier (USER_ID, PLUG_ID) suggests the table is best understood as a user-facing configuration or association entity, and a designer working in a Data Vault style could reasonably model it as a link between a user hub and a portlet hub, carrying descriptive attributes as an attached satellite. The physical schema documented for 12.1.1 comprises eleven columns, and the object is reported with VALID status in the BSC schema.

Key Information Stored

The most significant columns in BSC_USER_KPIGRAPH_PLUGS are those that define the identity of a portlet row and the parameters under which it is rendered.

• USER_ID — identifies the application user who owns the personalized portlet; part of the composite primary key.
• PLUG_ID — identifies the portlet or KPI graph plug-in being configured for that user; the second component of the primary key.
• RESPONSIBILITY_ID — the responsibility under which the portlet configuration applies, allowing the same user to hold distinct portlet sets in different responsibilities.
• INDICATOR — the KPI indicator associated with the graph portlet, linking the personalization to a specific performance measure.
• PARAMETER_STRING — the serialized or delimited parameter payload that controls portlet rendering, such as selected periods, thresholds, or graph options.
• REFERENCE_PATH — the navigation or reference path used by the portlet, typically the target invoked when the graph is drilled into.
• CREATION_DATE, CREATED_BY — standard audit columns capturing who inserted the row and when.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns capturing the most recent modification and the login session that performed it.

The surrogate structure is defined by the primary key constraint BSC_USER_KPIGRAPH_PLUGS_PK, which spans (USER_ID, PLUG_ID). A separate unique index, BSC_USER_KPIGRAPH_PLUGS_U1, covers the same column pair (USER_ID, PLUG_ID), confirming that the user-portlet combination is the business key and that a user cannot hold duplicate rows for the same plug identifier. Because the business key and the primary key are identical in composition, uniqueness is enforced at the level of the natural user-portlet pairing rather than through a generated sequence value.

Common Use Cases and Queries

The dominant use case is reconstructing a user's personalized Balanced Scorecard dashboard, particularly during troubleshooting when a portlet fails to appear or renders with unexpected parameters.

• Retrieve all portlets configured for a specific user and responsibility, joining to the portlet definition to resolve display names.
• Identify which users have personalized a given KPI graph plug-in, useful when assessing the blast radius of a change to an indicator or portlet definition.
• Compare the PARAMETER_STRING stored for a user against the default parameters to determine whether a rendering issue originates from personalization.
• Audit stale personalizations by filtering on LAST_UPDATE_DATE to find rows not touched since a prior release or patch.

A representative query pattern selects the personalization rows joined to the user and portlet definitions:

SELECT p.user_id, p.plug_id, p.responsibility_id, p.indicator, p.parameter_string, p.reference_path FROM bsc.bsc_user_kpigraph_plugs p WHERE p.user_id = :user_id AND p.responsibility_id = :resp_id;

Reporting on REFERENCE_PATH values is also common when validating drill-down navigation after an upgrade, since a changed target path is a frequent cause of broken links from a scorecard graph.

Related Objects

The ETRM metadata does not document foreign keys for this table; because it is classified as standalone, the relationships below are inferred from the column semantics rather than asserted by mined constraints, and should be verified against the target instance before relying on them in a query.

• FND_USER — joined on BSC_USER_KPIGRAPH_PLUGS.USER_ID = FND_USER.USER_ID to resolve the owning user.
• FND_RESPONSIBILITY — joined on RESPONSIBILITY_ID to resolve the responsibility context in which the portlet applies.
• BSC_KPIGRAPH_PLUGS or the corresponding KPI graph portlet definition table in the BSC schema — joined on PLUG_ID to obtain the portlet name, type, and default parameters.
• BSC_INDICATORS or the equivalent indicator master table — related through the INDICATOR column to resolve the KPI measure displayed by the graph.
• BSC_USER_KPIGRAPH_PLUGS_PK and BSC_USER_KPIGRAPH_PLUGS_U1 — the primary key constraint and unique index that together enforce the user-portlet business key.

Because no foreign keys are documented, integrity between this table and the portlet and indicator master data is maintained by application logic within the Balanced Scorecard module rather than by database-level constraints, a point worth noting when designing reconciliation or data-quality reports.