Search Results bsc_sys_calendars_vl




Overview
Explore in AI Chat

Overview

BSC_SYS_CALENDARS_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite, classified under the FND – Application Object Library product family. It presents system calendar definitions used by the Balanced Scorecard (BSC) and Enterprise Tax/Reporting Management (ETRM) components of the E-Business Suite. The view exposes calendar configuration alongside language-specific descriptive attributes, giving both technical and functional consumers a single, date-effective-independent source for calendar metadata.

Because it is a "VL" (view language) object, the view resolves the NAME and HELP attributes against the session's active language. This makes it suitable for concurrent programs, Oracle Reports, OAF pages, and BI Publisher data templates that must render calendar labels in the user's language without explicit join logic. Its role in reporting and integration is therefore twofold: it serves as a lookup source for calendar-driven period arithmetic, and it provides localized descriptive text for user-facing output.

Underlying Base Objects

The view is defined over two base tables:

  • BSC_SYS_CALENDARS_B — the base (language-neutral) table holding the calendar's structural definition, fiscal configuration, EDW linkage, and audit columns.
  • BSC_SYS_CALENDARS_TL — the translation table supplying NAME and HELP in each installed language.

The join predicate is B.CALENDAR_ID = TL.CALENDAR_ID, filtered by TL.LANGUAGE = USERENV('LANG'). The USERENV('LANG') call ensures exactly one translated row is returned per calendar, matching the runtime session language. This is the standard Oracle EBS VL pattern (B for base, TL for translations), and it means the view behaves as a virtual inner join that self-filters by language. No additional base objects are documented for this view in the ETRM metadata.

Key Columns

The view projects all significant base columns. Notable ones include:

Common Use Cases and Queries

Typical scenarios include populating calendar LOVs, driving fiscal-period calculations in custom reports, and confirming EDW exposure before data extraction jobs run. A basic lookup for the current session language follows:

  • SELECT calendar_id, name, short_name, fiscal_year, current_year FROM apps.bsc_sys_calendars_vl WHERE short_name = :p_short_name;
  • SELECT calendar_id, name, start_month, start_day FROM apps.bsc_sys_calendars_vl ORDER BY name;
  • SELECT calendar_id, name, edw_flag, edw_calendar_id FROM apps.bsc_sys_calendars_vl WHERE edw_flag = 'Y';

Because the view already applies the USERENV('LANG') filter, queries should not add their own language predicate; doing so would duplicate the restriction. For multi-language extracts, query BSC_SYS_CALENDARS_TL directly instead. Ensure the APPS schema grants and MO: Security profile grants permit access before deployment.