Results for “bis_user_trend_plugs”

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

Overview

BIS.BIS_USER_TREND_PLUGS is a configuration table within the Oracle EBS Applications BIS product family, which provides the underlying infrastructure for the Daily Business Intelligence (DBI) and subsequently Oracle Business Intelligence (OBI) dashboard and KPI framework. The table stores per-user personalization records for trend graphs (commonly referred to as "plugs") that appear on BIS dashboard pages. Each row associates a specific dashboard user with a specific KPI trend plug definition, defining not only which plug is displayed but also how that plug is rendered for that individual user — its title, parameter binding, sequence on the page, and a cached graph representation.

In Data Vault modeling terms, the metadata classifies this object heuristically as standalone. Because the only documented foreign key is an intra-domain reference to BSC_USER_KPILIST_PLUGS and the table also carries its own user-scoped business key, it is best modeled as a satellite attached to the user/KPI-plug relationship. It holds descriptive, user-specific configuration attributes rather than acting as a pure link or a shared hub.

Key Information Stored

The physical schema documents 13 columns. The most significant include:

• PLUG_ID — Foreign key referencing BSC_USER_KPILIST_PLUGS, identifying the KPI trend plug definition that is being personalized.
• USER_ID — The dashboard user for whom the plug configuration applies. Together with PLUG_ID, this forms the unique business key candidate.
• FUNCTION_ID and RESPONSIBILITY_ID — The application function and responsibility context in which the plug is exposed, enabling responsibility-aware dashboard behavior.
• CHART_USER_TITLE — The user-defined title displayed above the trend chart.
• PARAMETER_STRING — The serialized parameter binding that drives the plug's query at runtime.
• GRAPH_SEQUENCE — The display order of the plug on the user's dashboard region.
• CACHED_GRAPH — A cached rendering of the graph, used to accelerate dashboard load times.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last modified each personalization record.

The unique index BIS_USER_TREND_PLUGS_U1 on (USER_ID, PLUG_ID) is the documented business-key candidate, while the surrogate primary key is not individually distinguished in the metadata beyond PLUG_ID's role as a foreign key.

Common Use Cases and Queries

Typical scenarios include auditing which users have customized their trend graphs, replicating one user's dashboard personalizations to another, and troubleshooting rendering issues caused by stale CACHED_GRAPH values. A representative query to list plugs for a user follows:

• SELECT p.PLUG_ID, p.CHART_USER_TITLE, p.GRAPH_SEQUENCE FROM BIS.BIS_USER_TREND_PLUGS p WHERE p.USER_ID = :user_id ORDER BY p.GRAPH_SEQUENCE;
• A join to the plug master to resolve names: SELECT u.CHART_USER_TITLE, m.PLUG_NAME FROM BIS.BIS_USER_TREND_PLUGS u, BIS.BSC_USER_KPILIST_PLUGS m WHERE u.PLUG_ID = m.PLUG_ID AND u.USER_ID = :user_id;
• Stale-cache detection: SELECT USER_ID, PLUG_ID FROM BIS.BIS_USER_TREND_PLUGS WHERE CACHED_GRAPH IS NULL OR LAST_UPDATE_DATE < SYSDATE - 30;

Related Objects

• BSC_USER_KPILIST_PLUGS — Referenced via PLUG_ID; the master definition of user KPI-list plugs.
• FND_USER — Implicit relationship through USER_ID to resolve the dashboard user identity.
• FND_RESPONSIBILITY — Related through RESPONSIBILITY_ID for responsibility-level context.
• FND_FORM_FUNCTIONS — Related through FUNCTION_ID to identify the invoking function.
• BSC_KPILIST_PLUGS — The base KPI plug definitions from which user-specific plugs derive.
• BIS_DASHBOARD / BIS_*_TREND views — BIS reporting views that surface trend data driven by these plug definitions.