Results for “bsc_user_kpilist_plugs”

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

Overview

BSC_USER_KPILIST_PLUGS is a legacy Oracle EBS table residing in the BSC (Balanced Scorecard) schema. The product module is designated Obsolete and the ETRM implementation record explicitly notes "Not implemented in this database," which indicates that the table is typically absent or inactive in current 12.1.1 and 12.2.2 environments. Its documented purpose is to hold "Portlet information by user" — that is, configuration and personalization metadata describing how individual users have plugged KPI-oriented portlets into their dashboards and worklist pages.

The table functions as a master registry of "plugs" (portlet instances). Each plug is identified by a single column primary key, BSC_USER_KPILIST_PLUGS_PK, defined over PLUG_ID. A unique index, BSC_USER_KPILIST_PLUGS_U1, also covers PLUG_ID, reinforcing it as the sole business-key candidate; the table is not modeled with composite natural keys.

The heuristic Data Vault classification mined from the FK structure is standalone. In Data Vault modeling terms this suggests the object behaves as a reference or lookup entity — a hub-like anchor of portlet identities — rather than a transactional link or a descriptive satellite. Because numerous downstream tables reference PLUG_ID, it acts as a central point of conformance for portlet configuration across the BSC and workflow schemas.

Key Information Stored

The documented physical schema contains ten columns. The most significant are:

• PLUG_ID — surrogate primary key and unique business-key candidate; the identifier propagated to every referencing table.
• REFERENCE_PATH — the navigation or reference target associated with the portlet definition.
• DETAILS_FLAG and GROUP_FLAG — control flags governing whether detail-level and group-level displays are permitted for the portlet.
• KPI_MEASURE_DETAILS_FLAG — indicates whether KPI measure detail is exposed for this plug.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns providing who/when lineage.

Only three non-audit attribute columns carry configuration semantics, which confirms the lean, registry-style design implied by the standalone classification.

Common Use Cases and Queries

Typical use cases center on reconciling portlet assignments, auditing orphaned personalizations after upgrades, and tracing which user-facing components depend on a given plug. A representative query joining the registry to its most frequent consumer is:

• SELECT p.PLUG_ID, p.REFERENCE_PATH, c.PLUG_ID FROM BSC_USER_KPILIST_PLUGS p, ICX_PORTLET_CUSTOMIZATIONS c WHERE p.PLUG_ID = c.PLUG_ID;
• Orphan detection: SELECT PLUG_ID FROM BSC_USER_KPILIST_PLUGS WHERE PLUG_ID NOT IN (SELECT PLUG_ID FROM BIS_SCHEDULER);
• Audit reporting filtered on CREATION_DATE and CREATED_BY to identify plugs introduced by specific users.

Because the table is documented as obsolete, these patterns are primarily relevant to legacy-data extraction, pre-upgrade impact analysis, or historical reconciliation projects rather than active 12.2.2 development.

Related Objects

Nine tables reference PLUG_ID as a foreign key, indicating broad dependency. The most significant include:

• ICX_PORTLET_CUSTOMIZATIONS.PLUG_ID — per-user portlet personalization.
• ICX_CUSTOM_MENU_ENTRIES.PLUG_ID — menu entries tied to portlets.
• WF_WORKLIST_DEFINITIONS.PLUG_ID and WF_WORKLIST_COL_DEFINITIONS.PLUG_ID — worklist configuration.
• BIS_SCHEDULER.PLUG_ID and BIS_SCHEDULE_PREFERENCES.PLUG_ID — scheduling metadata.
• BIS_USER_IND_SELECTIONS.PLUG_ID, BIS_USER_TREND_PLUGS.PLUG_ID, and BIS_PMF_POPULATE_PORTLET.PLUG_ID — user selections, trends, and portlet population.

All joins are performed on the single PLUG_ID column, making BSC_USER_KPILIST_PLUGS the conformance anchor for the legacy BSC portlet subsystem.