Search Results get_client_timezone_code




Overview
Explore in AI Chat

Overview

The APPS.FND_TIMEZONES package body provides the foundational timezone resolution layer for Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to translate between timezone codes, display names, and enabled/disabled status so that applications can present, interpret, and apply the correct timezone to dates, timestamps, and user-facing interfaces. Because EBS supports globally distributed deployments, every user session, concurrent request, and form interaction may occur in a different timezone than the database server. FND_TIMEZONES abstracts that complexity by centralizing lookups against the timezone definitions stored in the FND schema.

The package is classified as OTHER in the ETRM registry for 12.2.2. It is a highly integrated utility: the metadata records that it is referenced by 49 other packages, making it one of the more widely leveraged Foundation (FND) objects. It is not referenced by any database object, which confirms its role as a client of the core timezone tables rather than a dependency of them.

Key Procedures and Functions

Six documented procedures and functions constitute the public surface of the package. Parameter details are not reproduced here; the intent of each routine is described below.

  • GET_CODE — Resolves and returns the timezone code associated with a given timezone definition. This is the canonical reverse lookup used when only a name or identifier is known.
  • GET_NAME — Returns the descriptive, user-facing name for a timezone. Forms and reports call this to display a readable label in place of an internal code.
  • GET_SERVER_TIMEZONE_CODE — Retrieves the timezone code configured for the application or database server. This establishes the reference timezone against which client and session times are normalized.
  • GET_CLIENT_TIMEZONE_CODE — Returns the timezone code associated with the current client or user context. It is used to determine the display timezone for a session.
  • GET_TIMEZONE_ENABLED_FLAG — Returns the enabled or disabled status for a specific timezone, allowing callers to restrict selectable values in list-of-values and validation logic.
  • TIMEZONES_ENABLED — A Boolean-returning function that indicates whether the timezone feature is active in the current environment. It serves as a gate before more expensive lookups are performed.

Tables Accessed

The ETRM metadata documents a single table reference accessed through an APPS synonym: FND_TIMEZONES_B. This is the base (non-translated) table holding the core timezone definitions, including timezone codes, enabled flags, and related attributes. The package does not write to this table; it is a read-only lookup source. Although the dependency list also references FND_TIMEZONES_VL and FND_TIMEZONES — the translated view and the package itself — the durable data store for the package's queries is FND_TIMEZONES_B. The _VL view supplies language-specific names where translation is required, and the profile option dependency (FND_PROFILE) indicates that behavior such as default server or client timezone is influenced by profile settings.

Usage Notes

FND_TIMEZONES is most commonly invoked implicitly. Oracle Forms-based EBS screens call these routines when rendering timezone fields, validating user input, or converting timestamps for display. Concurrent programs and report templates reference the package when formatting output that must respect a user's or server's timezone.

Custom code should follow the same pattern: call TIMEZONES_ENABLED first, then use GET_SERVER_TIMEZONE_CODE or GET_CLIENT_TIMEZONE_CODE to establish the relevant zone, and use GET_CODE, GET_NAME, and GET_TIMEZONE_ENABLED_FLAG for lookups and validation. Because 49 other packages depend on this component, it should be treated as stable infrastructure; customizations should wrap rather than modify it. The package is VALID in the shipped 12.2.2 environment, and its read-only nature minimizes concurrency and locking concerns.