Search Results bsc_sys_labels_b




Overview
Explore in AI Chat

Overview

BSC_SYS_LABELS_B is the base table of the Labels information entity within the Balanced Scorecard (BSC) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the BSC schema and holds the language-independent definition of system labels used throughout the Balanced Scorecard application, including scorecard, strategy, and performance-management user interface elements. Translation-dependent text for each label is stored separately in the companion table BSC_SYS_LABELS_TL, which references the base table through the composite key columns LABEL_ID, SOURCE_TYPE, and SOURCE_CODE.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object is hub-leaning: its composite primary key BSC_SYS_LABELS_B_PK (LABEL_ID, SOURCE_TYPE, SOURCE_CODE) behaves as a durable business key that the translation satellite (BSC_SYS_LABELS_TL) attaches to. The base table therefore functions as the anchor for descriptive label metadata, while textual content is held in the translated child.

Key Information Stored

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

  • LABEL_ID — Surrogate identifier for the label record and the first component of the composite primary key BSC_SYS_LABELS_B_PK.
  • SOURCE_TYPE — Classifies the origin or category of the label. Part of the primary key and the unique business-key index BSC_SYS_LABELS_B_U1.
  • SOURCE_CODE — Identifies the specific source element to which the label applies. Part of the primary key and the unique index.
  • LEFT_POSITION — Horizontal placement coordinates used when rendering the label.
  • TOP_POSITION — Vertical placement coordinates for label rendering.
  • FONT_SIZE — Presentation attribute controlling displayed text size.
  • FONT_STYLE — Presentation attribute controlling the font or styling of the rendered label.

The unique index BSC_SYS_LABELS_B_U1 (SOURCE_TYPE, SOURCE_CODE, LABEL_ID) serves as a business-key candidate, while the primary key BSC_SYS_LABELS_B_PK (LABEL_ID, SOURCE_TYPE, SOURCE_CODE) is the surrogate composite key. The remaining columns supply layout and typographic detail rather than identity.

Common Use Cases and Queries

Typical scenarios include auditing the label inventory, resolving layout attributes for a given label, and joining to translations for multilingual reporting. A representative query joining the base to the translation child is:

  • SELECT b.LABEL_ID, b.SOURCE_TYPE, b.SOURCE_CODE, b.FONT_SIZE, b.FONT_STYLE, t.LABEL_TEXT FROM BSC_SYS_LABELS_B b, BSC_SYS_LABELS_TL t WHERE b.LABEL_ID = t.LABEL_ID AND b.SOURCE_TYPE = t.SOURCE_TYPE AND b.SOURCE_CODE = t.SOURCE_CODE;
  • Filtering by source: SELECT * FROM BSC_SYS_LABELS_B WHERE SOURCE_TYPE = :p_type AND SOURCE_CODE = :p_code;
  • Reporting on layout: SELECT LABEL_ID, LEFT_POSITION, TOP_POSITION, FONT_SIZE FROM BSC_SYS_LABELS_B ORDER BY SOURCE_TYPE, SOURCE_CODE;

These patterns support reconciliation of label definitions, detection of orphaned or untranslated labels, and extraction of display configuration for custom BSC pages.

Related Objects

The principal dependent is the translation table, which references the base through its composite key. Additional Balanced Scorecard objects commonly join or derive from this table along the same key columns.

  • BSC_SYS_LABELS_TL — Translation child; joins on LABEL_ID, SOURCE_TYPE, SOURCE_CODE.
  • BSC_SYS_LABELS_VL — Typical view-layer wrapper exposing base plus translated text.
  • Other BSC configuration and scorecard-definition tables that consume label identifiers produced by this base entity.

Because the composite key is shared with the translation table, any integration or extraction must carry all three key columns to preserve referential integrity across the label entity.