Results for “get_server_timezone_code”

20 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_TIMEZONES is a foundational Oracle E-Business Suite PL/SQL package that centralizes time zone resolution across the application tier. In a global EBS deployment spanning Release 12.1.1 and 12.2.2, users, concurrent managers, and application servers may operate in different geographic regions, each observing distinct offsets and daylight saving rules. FND_TIMEZONES provides a single, authoritative interface for converting between internal numeric time zone identifiers and the human-readable codes stored in the underlying FND_TIMEZONES_B table, and for determining whether time zone support is active for the current session.

Its principal business value is consistency: rather than allowing individual forms or concurrent programs to query time zone data directly, FND_TIMEZONES exposes small, stable functions that return the correct code, translated name, and enablement state. The package declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema, and the header comment (AFTZONES.pls, version 115.1, 2002) confirms it dates to the early Oracle Applications codebase and remains a long-lived dependency — referenced by 49 other packages within the documented metadata.

Key Procedures and Functions

The package exposes six documented functions:

  • GET_CODE — Returns the time zone code (VARCHAR2) corresponding to a given numeric time zone identifier. It is used to translate an internal ID, such as one stored on a user profile or session record, into the standard code recognized elsewhere in the application.
  • GET_NAME — Returns the translated display name for a supplied time zone code. Because the name is translated, this function respects the language of the current session and is the correct choice when presenting a time zone to an end user.
  • GET_SERVER_TIMEZONE_CODE — Returns the time zone code configured for the application server.
  • GET_CLIENT_TIMEZONE_CODE — Returns the time zone code associated with the client (the user's session or form connection).
  • GET_TIMEZONE_ENABLED_FLAG — Returns 'Y' or 'N' indicating whether time zones should be enabled, based on configuration.
  • TIMEZONES_ENABLED — Returns 'Y' only when the master time zone switch is on and both the server and client time zone identifiers are non-null, providing a definitive check that full time zone handling is available.

All functions are declared without exposed parameters in the documented signature excerpt; parameter lists should not be assumed beyond those documented.

Tables Accessed

The package reads from FND_TIMEZONES_B via an APPS synonym. This table holds the base, language-independent time zone definitions — the codes and numeric identifiers that GET_CODE and GET_NAME resolve against. Translated names are supplied through the associated translation layer, which is why GET_NAME is documented as returning a translated value. No writes are documented; FND_TIMEZONES is a read-only lookup utility.

Usage Notes

FND_TIMEZONES is invoked primarily from Oracle Forms, concurrent programs, and custom PL/SQL that must display or interpret time zone information. A form displaying a user's preference typically calls GET_CODE and GET_NAME; session initialization logic calls TIMEZONES_ENABLED before applying any conversion. The convenience functions GET_SERVER_TIMEZONE_CODE and GET_CLIENT_TIMEZONE_CODE are commonly used where an application needs to reconcile the two environments. Because 49 packages reference it, customizations should treat this package as a stable, shared dependency and avoid reimplementing its lookups against FND_TIMEZONES_B directly.