Search Results tz_tl

Overview

Within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 data model, APPS.FND_TIMEZONES_VL is a bilingual (translated) reporting and integration view owned by the APPS schema. Its primary function is to expose the list of time zones registered in the application, together with their translated display names and time zone attributes, in a single flat structure suitable for SQL queries, concurrent programs, and outbound interfaces.

The view is a standard Oracle EBS "_VL" (View Language) construct. It joins the base time zone definition table to its translation table and filters the display name by the session's current language. This ensures that a query executed by a user logged into an English session returns English names, while a session configured for another installed language returns the corresponding translated names. Because the view is owned by APPS, it is exposed to end-user reporting tools such as Oracle Reports, BI Publisher, and ad hoc SQL, and it is commonly referenced when building lists of values (LOVs) or validating time zone codes submitted by external systems.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two base objects, both referenced through synonyms that resolve to the FND foundation tables:

• FND_TIMEZONES_B — the base ("B") table storing the non-translatable, language-independent definition of each time zone, including its code and offset attributes.
• FND_TIMEZONES_TL — the translation ("TL") table storing the language-specific display name (NAME) for each time zone code, keyed by TIMEZONE_CODE and LANGUAGE.

The view equates TZ.TIMEZONE_CODE = TZ_TL.TIMEZONE_CODE and restricts rows with TZ_TL.LANGUAGE = USERENV('LANG'), so the translation table contributes exactly one name per time zone for the current session language. The result is an inner join: a time zone appears only if a translation exists for the session language. The referenced objects are listed as FND_TIMEZONES_B (SYNONYM) and FND_TIMEZONES_TL (SYNONYM), confirming the standard FND synonym layer in 12.2.2.

Key Columns

The view projects the following columns, as documented in the ETRM source text:

• TIMEZONE_CODE — the unique key identifying a time zone.
• NAME — the translated display name sourced from FND_TIMEZONES_TL for the current session language.
• ENABLED_FLAG — indicates whether the time zone is currently enabled for use.
• GMT_OFFSET — the offset from Greenwich Mean Time, used in date/time conversions.
• DAYLIGHT_SAVINGS_FLAG — indicates whether the zone observes daylight saving.
• ACTIVE_TIMEZONE_CODE — the active time zone code associated with the record.
• UPGRADE_TZ_ID — the upgrade-related time zone identifier.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit/concurrency columns.

Common Use Cases and Queries

Typical scenarios include populating time zone selection lists in custom forms and reports, validating an inbound time zone code during integration, and resolving a display name for reporting on date/time data.

To list all enabled time zones with translated names:

• SELECT timezone_code, name, gmt_offset, daylight_savings_flag FROM apps.fnd_timezones_vl WHERE enabled_flag = 'Y' ORDER BY name;

To validate a specific code supplied by an interface:

• SELECT name, gmt_offset FROM apps.fnd_timezones_vl WHERE timezone_code = :p_timezone_code;

Because the view applies USERENV('LANG'), the same query returns language-appropriate names automatically, making it the preferred access point rather than querying the base and translation tables directly.