Search Results graph_sequence

Overview

BIS.BIS_USER_TREND_PLUGS is a transactional configuration table in the Oracle E-Business Suite Business Intelligence System (BIS) schema. It stores per-user definitions of trend and graph "plugs" — the graph or portlet widgets that appear on the Oracle EBS Dashboard and related self-service analytics pages. Each row binds a specific SSWA (Self-Service Web Applications) plug, function, and responsibility context to a particular user, along with the display title, parameter string, graph ordering, and a cached graph image URL.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, indicating a conventional transactional storage profile. Under the heuristic Data Vault classification mined from its foreign key structure, the table is classified as standalone, meaning it does not sit within a classic hub-link-satellite hierarchy. It functions independently, though its PLUG_ID column carries a reference relationship to BSC_USER_KPILIST_PLUGS, and its business identity is anchored by a unique composite key rather than a single surrogate identifier.

Key Information Stored

The table contains 13 documented columns. The most significant are:

• USER_ID — the SSWA user identifier; together with PLUG_ID forms the unique business key.
• PLUG_ID — the SSWA plug identifier referencing the underlying KPI list plug definition.
• FUNCTION_ID — the SSWA function under which the plug is registered.
• RESPONSIBILITY_ID — the responsibility context scoping the plug's visibility.
• CHART_USER_TITLE (VARCHAR2 2000) — the user-defined graph or portlet title displayed in the UI.
• PARAMETER_STRING (VARCHAR2 4000) — the serialized parameter string controlling the portlet's runtime behavior.
• GRAPH_SEQUENCE — numeric ordering that determines the sequence in which graphs are rendered.
• CACHED_GRAPH (VARCHAR2 4000) — the cached graph image URL, the column most directly relevant to "cached_graph" searches. This stores a pre-rendered image location so the dashboard can display a graph without regenerating it on every page load.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking row lifecycle.

The unique index BIS_USER_TREND_PLUGS_U1 on (USER_ID, PLUG_ID) enforces that a given user has at most one configuration row per plug, making this composite pair the effective business key. There is no documented single-column surrogate primary key; the uniqueness guarantee comes entirely from the composite index.

Common Use Cases and Queries

Typical usage centers on dashboard personalization and graph cache diagnostics. To retrieve all graphs configured for a user in display order:

• SELECT PLUG_ID, CHART_USER_TITLE, GRAPH_SEQUENCE, CACHED_GRAPH FROM BIS.BIS_USER_TREND_PLUGS WHERE USER_ID = :user_id ORDER BY GRAPH_SEQUENCE;
• To locate rows where the cached graph URL may be stale or missing: SELECT USER_ID, PLUG_ID, CACHED_GRAPH FROM BIS.BIS_USER_TREND_PLUGS WHERE CACHED_GRAPH IS NULL;
• To audit changes by responsibility: join FUNCTION_ID and RESPONSIBILITY_ID to FND_FUNCTION and FND_RESPONSIBILITY to report which responsibilities expose which cached graphs.

Reporting scenarios include verifying that cached graph URLs remain valid after a patch, identifying orphaned plug configurations, and analyzing graph sequencing consistency across users.

Related Objects

• BSC_USER_KPILIST_PLUGS — referenced by PLUG_ID; the source definition of the underlying KPI list plug.
• FND_USER — joined via CREATED_BY, LAST_UPDATED_BY, and USER_ID.
• FND_LOGINS — joined via LAST_UPDATE_LOGIN.
• FND_FUNCTION — joined via FUNCTION_ID for function metadata.
• FND_RESPONSIBILITY — joined via RESPONSIBILITY_ID for responsibility context.
• APPS.BIS_USER_TREND_PLUGS — the APPS synonyms/views layer through which end-user queries are normally issued.

The table references no other database objects beyond the PLUG_ID relationship, confirming its relatively self-contained role within the BIS dashboard framework.