Search Results bsc_sys_periodicities_tl




Overview
Explore in AI Chat

Overview

BSC_SYS_PERIODICITIES_TL is the translation table for periodicity definitions used by the Oracle Balanced Scorecard (BSC) module. In Oracle EBS, periodicity denotes the frequency context in which scorecard measures, targets, and initiatives are evaluated — for example daily, weekly, monthly, quarterly, or yearly cycles. Because periodicity names and descriptions must be presented to end users in the language of their session, the base table BSC_SYS_PERIODICITIES stores language-independent attributes while BSC_SYS_PERIODICITIES_TL stores the translated, language-specific text. Both tables reside in the BSC schema. The module is flagged as obsolete in current ETRM documentation, and the metadata explicitly records that this object is "not implemented in this database," meaning it may not exist in every 12.1.1 or 12.2.2 instance, particularly where Balanced Scorecard was never licensed, configured, or was removed during upgrade consolidation.

From a Data Vault modeling perspective, the mined metadata classifies this object as standalone, with no foreign key relationships recorded. This suggests modeling it as an independent satellite-like structure keyed by the natural composite business key, rather than as a hub, link, or dependent child of another entity.

Key Information Stored

The table carries nine documented columns. The most significant are:

  • PERIODICITY_ID — the surrogate identifier for the periodicity. Together with LANGUAGE it forms the composite primary key BSC_SYS_PERIODICITIES_TL_PK, linking each translated row back to its parent definition in BSC_SYS_PERIODICITIES.
  • LANGUAGE — the language code of the translated text, typically the NLS language abbreviation. It is the second component of the primary key and determines which users see which row.
  • SOURCE_LANG — the source language from which the translation was derived, normally the base language of the installation.
  • NAME — the translated display name of the periodicity, such as "Monthly" or its localized equivalent. This is the principal user-facing attribute.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit lineage for row creation and modification, including the application user and the login session responsible for the last change.

The unique index BSC_SYS_PERIODICITIES_TL_U1 also enforces (PERIODICITY_ID, LANGUAGE), confirming that no two rows may describe the same periodicity in the same language. Because the table is a translation (TL) table, NAME is the only true descriptive payload; the remaining attributes support administration and referential integrity.

Common Use Cases and Queries

Reporting scenarios that expose periodicity labels to users must join the translation table to honor the session language. A typical pattern restricts rows to the current language and falls back to the source language when no translation exists:

  • Listing periodicities with translated names: SELECT t.periodicity_id, t.name FROM bsc_sys_periodicities_tl t WHERE t.language = USERENV('LANG') ORDER BY t.name;
  • Auditing which periodicities lack a translation in a given language by comparing BSC_SYS_PERIODICITIES against BSC_SYS_PERIODICITIES_TL.
  • Extracting multilingual label sets for data warehouse or BI publication, keyed on PERIODICITY_ID and LANGUAGE.
  • Investigating translation staleness using SOURCE_LANG, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Because the object is obsolete and possibly absent, queries should be guarded with existence checks or wrapped in exception handling before being deployed to production.

Related Objects

The most significant related objects are:

  • BSC_SYS_PERIODICITIES — the base (non-translated) table; join on PERIODICITY_ID to obtain language-independent attributes.
  • BSC_SYS_PERIODICITIES_TL_PK and BSC_SYS_PERIODICITIES_TL_U1 — the primary key constraint and unique index enforcing (PERIODICITY_ID, LANGUAGE).
  • BSC_SYS_PERIODICITIES_B / _TL style base-translation pairs, consistent with the EBS MLS convention used across BSC setup entities.
  • BSC_SYS_PERIODICITIES_TL dependent scorecard setup tables that reference periodicity identifiers when defining measure frequencies.
  • FND_LANGUAGES and FND_TERRITORIES — standard reference objects for validating LANGUAGE values.

No foreign keys are documented for this table, so joins to related objects are conventional rather than enforced at the database level.