Search Results range_yr_mod




Overview
Explore in AI Chat

Overview

APPS.BSC_SYS_CALENDARS_VL is a multilingual (language-resolved) view in the Oracle E-Business Suite Balanced Scorecard module. It presents calendar definitions used by the BSC application to organize fiscal and reporting periods. Because BSC supports multiple languages at a single site, the view reconciles translated, language-specific descriptive attributes with the underlying non-translated operational data. The result is a single, query-friendly interface that exposes both the numeric calendar parameters and the user-facing name and help text appropriate to the session language.

In the context of the search term "fiscal_change," this view is significant because it exposes the FISCAL_CHANGE column, which is central to how BSC handles a change in fiscal year definition. When an organization changes its fiscal year start, the FISCAL_CHANGE value is used by BSC period utilities and calendar packages to correctly align periods before and after the change. The view is therefore a key reference point for reporting, period setup validation, and integration logic that must respect fiscal boundary transitions.

Underlying Base Objects

The view is defined over two documented base tables:

The "_VL" suffix denotes a language-resolved view. At query time, the view joins the two tables and returns the translated rows for the language in which the user session is running, defaulting to the base language when a translation is not available. This design lets BSC display calendar information in any installed language without duplicating the operational columns across translations.

The view is referenced by several BSC packages and utilities, including BSC_CALENDAR_PUB, BSC_PERIODS_UTILITY_PKG, BSC_COPY_INDICATOR_PUB, BSC_UPDATE_UTIL, and BSC_MO_DOC_PKG. These dependencies confirm that calendar resolution is embedded in period generation, metadata description, and scorecard document processing.

Key Columns

  • CALENDAR_ID — primary identifier for the calendar; the join key across calendar-related tables.
  • FISCAL_YEAR — the fiscal year associated with the calendar definition.
  • FISCAL_CHANGE — indicator used to signal whether a fiscal year change applies, driving period alignment logic.
  • RANGE_YR_MOD — modifier controlling how year ranges are calculated across the calendar.
  • CURRENT_YEAR — flag or value identifying which year is treated as current.
  • START_MONTH and START_DAY — define the beginning of the fiscal calendar.
  • NAME, SHORT_NAME, and HELP — translated display attributes resolved from BSC_SYS_CALENDARS_TL.
  • EDW_FLAG, EDW_CALENDAR_ID, and EDW_CALENDAR_TYPE_ID — columns supporting the Enterprise Data Warehouse / analytics integration of calendar definitions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

A typical scenario is validating fiscal change behavior before running period generation. Analysts query the view to inspect FISCAL_CHANGE alongside START_MONTH and START_DAY, confirming the calendar will roll periods correctly. The following retrieves the core calendar parameters:

SELECT calendar_id, name, fiscal_year, fiscal_change, start_month, start_day FROM apps.bsc_sys_calendars_vl;

For reporting, users join the view to period tables and filter by name to present readable calendar labels in the session language. A simple lookup follows:

SELECT calendar_id, name, short_name FROM apps.bsc_sys_calendars_vl WHERE UPPER(name) LIKE '%FISCAL%';

Because the view presents translated text, reporting tools such as BI Publisher and OBIEE can consume it directly for multi-language output. Administrators also use it to audit which calendars are flagged with FISCAL_CHANGE prior to applying fiscal year modifications, ensuring downstream BSC packages act on the correct definitions.