Search Results yearly_flag

Overview

APPS.BSC_SYS_PERIODICITIES_VL is a multilingual (language-resolved) view in the Oracle E-Business Suite Balanced Scorecard (BSC) module. Its purpose is to present periodicity definitions — the time-based roll-up and aggregation periods used by BSC scorecards and analytics — in the language installed at the reporting site. The view is owned by the APPS schema and is registered in FND Design Data as BSC.BSC_SYS_PERIODICITIES_VL and FND.BSC_SYS_PERIODICITIES_VL. According to ETRM it carries a status of VALID and is classified as a "MultiLingual view (a language resolved view of the data)."

In EBS 12.1.1 and 12.2.2, BSC leverages these periodicity records when building scorecard displays, calendar hierarchies, and Enterprise Data Warehouse (EDW) extraction logic. Because the view is language-resolved, it is the appropriate source for any report, concurrent program, or integration that must surface periodicities to end users rather than referencing the underlying translation tables directly.

Underlying Base Objects

The view joins translated, language-specific values from BSC_SYS_PERIODICITIES_TL with the non-displayed attributes held in the base table BSC_SYS_PERIODICITIES. ETRM dependency information also lists BSC_LOOKUPS and BSC_SYS_CALENDARS_B as referenced objects, reflecting lookup-driven columns (such as periodicity type) and calendar associations. The _VL suffix confirms that the view applies the standard EBS language-resolution pattern: it returns exactly one row per periodicity for the session's language, falling back to the base language when a translation is missing.

ETRM records that the view is referenced by several BSC program units, including BSC_BIS_LOCKS_PVT, BSC_CALENDAR_PUB, BSC_CALENDAR_PVT, BSC_COPY_INDICATOR_PUB, BSC_DBGEN_BSC_READER, and BSC_METADATA_DESC. This confirms the view is a supported internal dependency for calendar and metadata processing rather than a standalone object.

Key Columns

• PERIODICITY_ID — Primary identifier for the periodicity definition.
• NAME — Translated, language-specific display name (VARCHAR2 150).
• SHORT_NAME — Abbreviated translated label (VARCHAR2 30).
• NUM_OF_PERIODS / NUM_OF_SUBPERIODS — Counts of periods and sub-periods in the definition.
• PERIOD_COL_NAME / SUBPERIOD_COL_NAME — Column names used to map periods and sub-periods to fact tables.
• DB_COLUMN_NAME — Physical database column associated with the periodicity (VARCHAR2 30).
• YEARLY_FLAG / EDW_FLAG — Flags indicating yearly periodicities and EDW relevance.
• CALENDAR_ID / EDW_PERIODICITY_ID — Foreign keys to the calendar definition and its EDW counterpart.
• CUSTOM_CODE — Numeric code used to identify custom periodicity definitions.
• PERIODICITY_TYPE — Lookup-driven classification of the periodicity.
• PERIOD_TYPE_ID, RECORD_TYPE_ID, XTD_PATTERN — Type identifier and extended pattern metadata used by BSC analytics.
• SOURCE — Origin indicator for the definition (VARCHAR2 200).

Common Use Cases and Queries

The view is typically queried to enumerate periodicities available for scorecard or calendar configuration, to resolve display names for a user's language, and to drive EDW or calendar processing. Because it is language-resolved, callers do not need to join BSC_SYS_PERIODICITIES_TL themselves.

Listing all periodicities with their translated names:

SELECT periodicity_id, name, short_name, num_of_periods, periodicity_type
FROM apps.bsc_sys_periodicities_vl
ORDER BY name;

Filtering custom-defined periodicities by custom code:

SELECT periodicity_id, name, custom_code, db_column_name
FROM apps.bsc_sys_periodicities_vl
WHERE custom_code IS NOT NULL;

Retrieving periodicities tied to a specific calendar and flagged for EDW:

SELECT p.periodicity_id, p.name, c.calendar_name
FROM apps.bsc_sys_periodicities_vl p, apps.bsc_sys_calendars_b c
WHERE p.calendar_id = c.calendar_id
AND p.edw_flag = 1;

These patterns support scorecard configuration, metadata validation, and EDW-bound extraction routines where periodicity context is required.