Search Results bsc_tabs_vl




Overview
Explore in AI Chat

Overview

BSC_TABS_VL is a seeded, valid database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the BSC (Balanced Scorecard) product family, which forms part of the Oracle Enterprise Performance Management and Daily Business Intelligence stack. The view presents tab metadata — the navigational and configuration elements that group KPIs, scorecards, and models within the Balanced Scorecard user interface.

The "_VL" suffix denotes a "view language" or translated view construct. Oracle EBS employs this naming convention wherever an entity stores translatable descriptive text separated from its base attribute data. BSC_TABS_VL joins the base table BSC_TABS_B, which holds language-independent attributes, with BSC_TABS_TL, which holds translated columns (NAME and HELP) keyed by LANGUAGE. As a result, the view exposes a single logical row per tab, resolving descriptive text according to the session's language environment through USERENV('LANG'). Its structure mirrors the underlying base tables, and Oracle documents it as INVALIDATION-capable and REPORTING-eligible, making it a supported read-only surface for concurrent programs, BI Publisher reports, OBIEE/OBIA extracts, and custom integrations that need tab labels in the caller's locale.

Because the view is a thin projection over two tables with no business logic beyond the language filter and an NVL on TAB_INDEX, it is safe for high-volume SELECT access. It does not enforce row-level security beyond standard EBS multi-org and responsibility conventions established at the underlying model level.

Underlying Base Objects

The ETRM metadata documents BSC_TABS_VL as a view over exactly two base objects:

The join predicate is B.TAB_ID = TL.TAB_ID AND TL.LANGUAGE = USERENV('LANG'). The LANGUAGE filter restricts results to the session language, so a query in an English session returns only the English rows. If a translation row is missing for the session language, the tab is not returned by the view. The view text also applies NVL(B.TAB_INDEX, B.TAB_ID) to TAB_INDEX, guaranteeing a non-null display ordering value by falling back to the tab's primary key when no explicit index is defined. Standard EBS TL tables maintain a row for the base ("US") language, so tabs created in the base language remain visible in base-language sessions.

Key Columns

  • TAB_ID — Primary key of the tab; foreign key to the parent model definitions. Serves as the join key between the base table and translation table.
  • NAME — Translated display name of the tab, sourced from BSC_TABS_TL. This is the label presented in the Balanced Scorecard UI navigation.
  • HELP — Translated help text for the tab, also from BSC_TABS_TL.
  • KPI_MODEL, BSC_MODEL, CROSS_MODEL, DEFAULT_MODEL — Flags or identifiers indicating which model types the tab applies to (KPI-only, scorecard-only, cross-model, or the default model tab). These govern how the tab is rendered for a given Balanced Scorecard configuration.
  • ZOOM_FACTOR — Numeric display scaling factor applied to the tab's visualization.
  • TAB_INDEX — Presentation order for the tab, computed as NVL(TAB_INDEX, TAB_ID). Use this column for ORDER BY clauses when reproducing UI ordering.
  • PARENT_TAB_ID — Self-referencing parent tab, enabling hierarchical tab groupings.
  • OWNER_ID — Identifier of the owning user or party for the tab.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns inherited from the base table for audit and change tracking.
  • ADDITIONAL_INFO — Translated extended attribute for the tab from BSC_TABS_TL.

Common Use Cases and Queries

The view is most frequently queried to enumerate tabs for a given model configuration, to retrieve localized tab labels for reporting, and to drive custom or external front-ends that replicate the Balanced Scorecard navigation. The following examples assume an English session.

List all tabs with localized names and ordered for display:

SELECT TAB_ID, NAME, TAB_INDEX, PARENT_TAB_ID, DEFAULT_MODEL
FROM   APPS.BSC_TABS_VL
ORDER BY TAB_INDEX, TAB_ID;

Retrieve tabs associated with the scorecard model only:

SELECT TAB_ID, NAME, HELP, ZOOM_FACTOR
FROM   APPS.BSC_TABS_VL
WHERE  BSC_MODEL = 'Y'
ORDER BY TAB_INDEX;

Fetch a single tab's label and help text for a specific locale-aware lookup:

SELECT NAME, HELP, ADDITIONAL_INFO
FROM   APPS.BSC_TABS_VL
WHERE  TAB_ID = :p_tab_id;

Because the language filter is embedded, no additional language predicate is required; the session's NLS_LANG determines which translation row is returned. For integrations outside EBS that connect directly to the database, ensure the connection sets the correct NLS environment or route the query through a concurrent program so that USERENV('LANG') resolves correctly.