Search Results bsc_sys_periods_tl




Overview
Explore in AI Chat

Overview

The BSC_SYS_PERIODS_TL table is a translation table within the Oracle E-Business Suite Balanced Scorecard (BSC) module. Its primary function is to store translated textual descriptions for system-defined periods, enabling the application to support multiple languages. This table is a critical component for the localization of period names used in scorecard reporting and analysis. It is important to note that the BSC module itself is marked as obsolete in the EBS 12.1.1 and 12.2.2 releases, indicating that while the table may exist in upgraded environments, no new development or significant enhancements are expected for this functionality. The table's structure is designed to support the standard Oracle Applications translation architecture, where the '_TL' suffix denotes a translation table.

Key Information Stored

The table stores translated period information, keyed by a composite primary key. The core columns that define the unique period and its translation are YEAR, PERIODICITY_ID, and PERIOD_ID. These columns together identify a specific period instance (e.g., "January 2023" for a monthly periodicity). The primary translated column is typically a column like PERIOD_NAME, which would hold the language-specific name for the period (e.g., "Janvier" in French). While the specific name column is not listed in the provided metadata, its presence is implied by the table's description as a translation table. The table also includes standard translation table columns such as LANGUAGE and SOURCE_LANG to manage the multilingual data set.

Common Use Cases and Queries

The primary use case is retrieving period descriptions in a user's session language for display in BSC reports and user interfaces. A common query would join this table to its base table (likely BSC_SYS_PERIODS_B) to fetch a list of periods with translated names. For instance, to generate a localized list of periods for a specific year and periodicity, a developer might use a SQL pattern such as:
SELECT tl.period_name, b.* FROM bsc_sys_periods_b b, bsc_sys_periods_tl tl WHERE b.year = tl.year AND b.periodicity_id = tl.periodicity_id AND b.period_id = tl.period_id AND tl.language = userenv('LANG');
Given the module's obsolete status, direct operational use or customization is strongly discouraged. Queries against this table are most likely encountered during data migration audits, historical report maintenance, or support for legacy implementations.

Related Objects

Based on the documented foreign key relationship, BSC_SYS_PERIODS_TL is referenced by one other table in the obsolete BSC module:

  • BSC_KPI_COMMENTS: This table references BSC_SYS_PERIODS_TL to validate the period context for Key Performance Indicator comments. The join is performed using the composite key columns: BSC_KPI_COMMENTS.PERIODICITY_ID = BSC_SYS_PERIODS_TL.PERIODICITY_ID, BSC_KPI_COMMENTS.PERIOD_ID = BSC_SYS_PERIODS_TL.PERIOD_ID, and BSC_KPI_COMMENTS.YEAR = BSC_SYS_PERIODS_TL.YEAR.
The table itself is a child of a base table (typically named BSC_SYS_PERIODS_B), which holds the non-translated, seed data for system periods. This parent-child relationship is a standard pattern in Oracle EBS but is not explicitly detailed in the provided metadata excerpt.