Search Results fnd_timezones_vl




Overview
Explore in AI Chat

Overview

FND_TIMEZONES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the FND (Application Object Library) product family and exposes the set of system timezones known to the EBS instance, together with their offsets from Greenwich Mean Time (GMT) and related configuration flags. The "_VL" suffix identifies it as a "validated" or "language" view: the standard EBS pattern in which a base ("_B") table stores language-independent data and a translation ("_TL") table stores the language-dependent display name, joined by the current session language.

Because timezone data underpins scheduling, concurrent manager processing, workflow, notifications, and audit timestamps, FND_TIMEZONES_VL is frequently consulted by reports, integrations, and diagnostic queries that need to translate a TIMEZONE_CODE into a human-readable name or to obtain a numeric offset. The view is marked VALID and carries the standard Oracle Proprietary, Confidential Information designation.

Underlying Base Objects

The ETRM documentation records the view as being defined over two referenced base objects, both surfaced in the APPS schema as synonyms:

  • FND_TIMEZONES_B — the base table holding language-independent timezone attributes (code, offset, flags, audit columns).
  • FND_TIMEZONES_TL — the translation table holding the language-dependent NAME, keyed by TIMEZONE_CODE and LANGUAGE.

The view joins these on TIMEZONE_CODE and restricts the translation row to the session language via TZ_TL.LANGUAGE = USERENV('LANG'). This means the NAME returned reflects the language of the querying session, not necessarily the base application language. Columns sourced from the base table are prefixed TZ. in the view text; NAME is drawn from the translation table.

Key Columns

  • TIMEZONE_CODE — the unique identifier for the timezone (for example, the internal code that applications and concurrent programs store).
  • NAME — the language-translated, user-facing name of the timezone, resolved for the current session language.
  • ENABLED_FLAG — indicates whether the timezone is currently enabled and selectable.
  • GMT_OFFSET — the base offset from GMT, used for time conversion calculations.
  • DAYLIGHT_SAVINGS_FLAG — indicates whether the timezone observes daylight saving time.
  • ACTIVE_TIMEZONE_CODE — the currently active equivalent code, where applicable.
  • UPGRADE_TZ_ID — an identifier used during timezone data upgrades.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO audit columns.

Common Use Cases and Queries

Typical uses include populating timezone pick-lists in custom forms and OAF pages, resolving a stored code to a readable label in reports, and joining to tables that hold TIMEZONE_CODE values for display. A standard lookup query is:

SELECT TIMEZONE_CODE, NAME, GMT_OFFSET, ENABLED_FLAG FROM APPS.FND_TIMEZONES_VL WHERE ENABLED_FLAG = 'Y' ORDER BY NAME;

To resolve the name for a specific code:

SELECT NAME FROM APPS.FND_TIMEZONES_VL WHERE TIMEZONE_CODE = :p_code;

Because the view filters on USERENV('LANG'), results vary with the session's NLS language setting; when no translation exists for that language, the join returns no row for that code. For this reason, integrations that must guarantee a value should either constrain the query to available translations or fall back to FND_TIMEZONES_B, which always contains the code-level attributes regardless of language coverage.