Search Results begin_dst_hour




Overview
Explore in AI Chat

Overview

HZ_TIMEZONES is a reference (lookup) table owned by the AR schema in Oracle E-Business Suite, documented as VALID in both 12.1.1 and 12.2.2. Its stated purpose is to hold time zone information used across the E-Business Suite. The table stores the definition of each time zone available to the applications, including its offset from Greenwich Mean Time and the rules governing daylight savings transitions. Because so many transactional and setup entities must record a time zone — locations, contact points, tasks, campaigns, service incidents, and coverage records — HZ_TIMEZONES functions as a shared, low-volatility reference hub rather than a transactional table. Rows are populated by Oracle seed data and are rarely, if ever, inserted by end users.

From a data modeling perspective, the metadata's heuristic Data Vault classification is hub-leaning. HZ_TIMEZONES can reasonably be modeled as a hub: its primary key, TIMEZONE_ID, is a stable, non-reused business key, and the numerous foreign keys pointing into it behave like links from surrounding satellites and transactional entities. Most descriptive attributes (offset and daylight savings rules) would sit in a satellite attached to that hub in a Data Vault representation.

Key Information Stored

The table is documented with 22 columns. The most significant are:

The distinction between the surrogate key and the business key is nominal here: TIMEZONE_ID serves as both, since HZ_TIMEZONES_U1 is defined on the same column as the primary key.

Common Use Cases and Queries

Typical usage centers on resolving a TIMEZONE_ID to its offset and daylight rules, or listing zones for a picklist. A common join appears in location and contact reporting:

  • Reporting locations with their zone description: join HZ_LOCATIONS.TIMEZONE_ID to HZ_TIMEZONES.TIMEZONE_ID and select GLOBAL_TIMEZONE_NAME and GMT_DEVIATION_HOURS.
  • Task scheduling: join JTF_TASKS_B.TIMEZONE_ID to resolve the zone for a task, and join JTF_TASK_AUDITS_B on both NEW_TIMEZONE_ID and OLD_TIMEZONE_ID to see time zone changes recorded in the audit trail.
  • Service and incident reporting: join CS_INCIDENTS_ALL_B.TIME_ZONE_ID to HZ_TIMEZONES.TIMEZONE_ID to determine the zone in which an incident was logged.
  • Campaign scheduling: resolve AMS_CAMPAIGN_SCHEDULES_B.TIMEZONE_ID for marketing execution windows.
  • Daily offset validation: query WHERE DAYLIGHT_SAVINGS_TIME_FLAG = 'Y' to enumerate zones subject to DST transitions.

Sample pattern:

SELECT t.GLOBAL_TIMEZONE_NAME, t.GMT_DEVIATION_HOURS FROM HZ_TIMEZONES t, HZ_LOCATIONS l WHERE l.TIMEZONE_ID = t.TIMEZONE_ID;

Related Objects

HZ_TIMEZONES is referenced by foreign keys from numerous tables. The most significant include:

  • HZ_LOCATIONS (TIMEZONE_ID) — locations and addresses across Trading Community Architecture.
  • HZ_CONTACT_POINTS (TIMEZONE_ID) — contact and communication channel records.
  • JTF_TASKS_B (TIMEZONE_ID) and JTF_TASK_AUDITS_B (NEW_TIMEZONE_ID, OLD_TIMEZONE_ID) — task records and their audit trail, the object that prompted this lookup.
  • CS_INCIDENTS_ALL_B (TIME_ZONE_ID) — service incidents.
  • AMS_CAMPAIGN_SCHEDULES_B and AMS_EVENT_OFFERS_ALL_B (TIMEZONE_ID) — marketing scheduling and offers.
  • OKS_COVERAGE_TIMEZONES and CSP_CARRIER_DELIVERY_TIMES (TIMEZONE_ID) — service coverage and delivery timing.
  • HZ_TIMEZONE_MAPPING (TIMEZONE_ID) — internal mapping of zones to other references.
  • MTL_PARAMETERS (TIMEZONE_ID) — inventory organization parameters.
  • PER_EMPDIR_LOCATIONS (TIMEZONE_ID) — HR employee directory locations.