Results for “bis_user_ind_selections”

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

Overview

BIS_USER_IND_SELECTIONS is a BIS (Applications BIS / Business Intelligence System) configuration table that stores per-user indicator selections within Oracle EBS 12.1.1 and 12.2.2. Each row captures a user-defined, dimension-scoped selection of an indicator (KPI) plug, tied to a target level, plan, responsibility, and organization context, so that dashboards, scorecards, and analytic regions render the same set of indicators for the same user across sessions. The table is owned by the BIS schema and contains 21 documented columns in the 12.1.1 physical model.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as standalone. In Data Vault terms this suggests treatment as a satellite-like record anchored on the natural business key (USER_ID plus the plug/dimension level combination enforced by the unique indexes), rather than as a true hub or link. The single documented foreign key to BSC_USER_KPILIST_PLUGS indicates it functionally depends on the KPI plug definition, while the absence of inbound foreign keys means no other table directly references it. Note that the metadata excerpt records the object as “Not implemented in this database”; this reflects the extraction environment rather than a functional limitation, and the table may still exist in production EBS installations that use BIS indicator personalization.

Key Information Stored

The most significant columns fall into four groups:

• IND_SELECTION_ID — surrogate primary key; enforced by unique index BIS_USER_IND_SELECTIONS_U1.
• USER_ID — owning EBS user for the saved selection; also a business-key component in BIS_USER_IND_SELECTIONS_U2.
• PLUG_ID — foreign key to BSC_USER_KPILIST_PLUGS, identifying the KPI/indicator plug being selected. Part of both the FK and the composite unique key.
• TARGET_LEVEL_ID, PLAN_ID, RESPONSIBILITY_ID, ORGANIZATION_ID, ORG_LEVEL_VALUE — define the analytic context: which target level, plan, responsibility, and organization scope the selection applies to.
• DIMENSION1_LEVEL_VALUE through DIMENSION7_LEVEL_VALUE — seven dimension level slots that refine the indicator selection across the BIS dimension model.
• LABEL — user-facing text for the saved selection.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns, populated by the application or via FND_STANDARD_DATE/WHO columns during DML.

The secondary unique index BIS_USER_IND_SELECTIONS_U2 spans USER_ID, PLUG_ID, TARGET_LEVEL_ID, ORG_LEVEL_VALUE, PLAN_ID, and all seven DIMENSIONn_LEVEL_VALUE columns, enforcing that a given user cannot store duplicate indicator selections for the same context. This index is the primary business-key candidate for integration and de-duplication logic.

Common Use Cases and Queries

Typical consumers retrieve a user’s saved selections to populate scorecard layouts, KPI lists, and personalized dashboard regions. Common patterns include:

• Personalization lookup: SELECT ind_selection_id, plug_id, label FROM bis_user_ind_selections WHERE user_id = :p_user_id AND plan_id = :p_plan_id ORDER BY plug_id;
• Context resolution: join to BSC_USER_KPILIST_PLUGS to resolve plug metadata: SELECT s.ind_selection_id, p.plug_name FROM bis_user_ind_selections s, bsc_user_kpilist_plugs p WHERE s.plug_id = p.plug_id AND s.user_id = :p_user_id;
• Duplicate detection: group by the U2 column set to find conflicting rows before migration or cleanup.
• Audit reporting: filter on CREATION_DATE/LAST_UPDATE_DATE ranges to see which users have recently changed their indicator preferences.
• Dimension-scoped reporting: use DIMENSION1_LEVEL_VALUE through DIMENSION7_LEVEL_VALUE to slice indicator selections by the analytic dimension hierarchy.

Related Objects

The most significant objects related to BIS_USER_IND_SELECTIONS are:

• BSC_USER_KPILIST_PLUGS — the sole documented FK parent (PLUG_ID → PLUG_ID); supplies KPI plug definitions used by each selection.
• FND_USER — source of the USER_ID value, providing user identity and responsibility context.
• FND_RESPONSIBILITY / FND_RESPONSIBILITY_VL — resolve RESPONSIBILITY_ID into responsibility names for reporting.
• HR_OPERATING_UNITS / ORG tables — resolve ORGANIZATION_ID and ORG_LEVEL_VALUE for organizational scoping.
• BIS_* KPI and scorecard tables (e.g., plug lists, target-level definitions) that share the same TARGET_LEVEL_ID and PLAN_ID semantics, enabling joins for dashboard rendering.
• BIS indicator/KPI reporting views and the BIS runtime APIs that read saved selections when building personalized indicator lists for a user session.

Together these objects allow the stored selection rows to be rendered into a user-specific, context-aware indicator display within the EBS intelligence layer.