Search Results edw_calendar_type_id




Overview
Explore in AI Chat

Overview

The view BSC_EDW_CALENDAR_TYPE_VL belongs to the Balanced Scorecard (BSC) product family within Oracle E-Business Suite and resides in the APPS schema. It exposes calendar type reference data used by the Enterprise Data Warehouse (EDW) components of Balanced Scorecard. The "_VL" suffix follows the standard Oracle EBS convention for a "view of a translated table" — specifically, a language-specific view over the translation table BSC_EDW_CALENDAR_TYPE_TL, filtered to the session's current language. Its principal role is reporting and integration: it provides a language-resolved, read-friendly projection of calendar type definitions for the EDW layer that supports Balanced Scorecard metrics, time-period definitions, and scorecard analytics. Because the view resolves the user's language through USERENV('LANG'), it also serves as the standard access path for localized calendar type names rather than querying the underlying _TL table directly.

Underlying Base Objects

As documented, this view is defined over the translation table BSC_EDW_CALENDAR_TYPE_TL. The view text is a straightforward selection and column rename:

SELECT EDW_CALENDAR_TYPE_ID, NAME AS NAME, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN
FROM BSC_EDW_CALENDAR_TYPE_TL
WHERE LANGUAGE = USERENV('LANG')

Two points are worth noting. First, the translation table BSC_EDW_CALENDAR_TYPE_TL is the sole documented base object; the view does not join to a base _B table, meaning it exposes only the translated name and the shared key plus audit columns rather than other attributes that would normally reside on a base table. Second, no other base objects are documented in the ETRM metadata, so any additional relationships (for example, to a calendar definition or period table) should be confirmed against the actual dictionary in the target instance. The view is the localized counterpart to the base translation table: it isolates the single row per EDW_CALENDAR_TYPE_ID for the active language, ensuring callers receive one locale-appropriate name per calendar type.

Key Columns

The view exposes the following columns, reproduced from the documented column list:

  • EDW_CALENDAR_TYPE_ID — The primary identifier for the EDW calendar type. This is the key referenced in the search term "edw_calendar_type_id" and is the joining column to any dependent calendar, period, or metric definitions.
  • NAME — The translated, language-specific name of the calendar type. It is the alias of the NAME column from BSC_EDW_CALENDAR_TYPE_TL and is presented in the caller's session language.
  • CREATED_BY — Standard EBS audit column identifying the user who created the translation row.
  • CREATION_DATE — The date the translation row was created.
  • LAST_UPDATED_BY — The user who most recently modified the translation row.
  • LAST_UPDATE_DATE — The date of the last modification.
  • LAST_UPDATE_LOGIN — The login associated with the last update, used for audit and concurrency tracking.

Because the view is language-filtered, the audit columns reflect the lifecycle of the specific translated record rather than a consolidated base record.

Common Use Cases and Queries

Typical usage centers on reporting, integration extracts, and validation of calendar type reference data for Balanced Scorecard EDW. Common scenarios include populating lookups in a reporting layer, validating that a given EDW_CALENDAR_TYPE_ID exists, and joining localized names onto fact or calendar tables.

List all calendar types in the session language:

SELECT EDW_CALENDAR_TYPE_ID, NAME
FROM APPS.BSC_EDW_CALENDAR_TYPE_VL
ORDER BY NAME;

Resolve a name for a specific identifier:

SELECT EDW_CALENDAR_TYPE_ID, NAME
FROM APPS.BSC_EDW_CALENDAR_TYPE_VL
WHERE EDW_CALENDAR_TYPE_ID = :p_calendar_type_id;

Join to a dependent object by key:

SELECT d.EDW_CALENDAR_TYPE_ID, v.NAME, d.OTHER_ATTRIBUTE
FROM APPS.BSC_EDW_CALENDAR_DEFN d,
     APPS.BSC_EDW_CALENDAR_TYPE_VL v
WHERE d.EDW_CALENDAR_TYPE_ID = v.EDW_CALENDAR_TYPE_ID;

Detect recently changed reference data for incremental extracts:

SELECT EDW_CALENDAR_TYPE_ID, NAME, LAST_UPDATE_DATE
FROM APPS.BSC_EDW_CALENDAR_TYPE_VL
WHERE LAST_UPDATE_DATE > :p_since_date;

Note that dependent tables referenced above are illustrative; only BSC_EDW_CALENDAR_TYPE_TL is documented as a base object for this view. All queries should be executed in the appropriate language context, since the view returns rows solely for the session language.