Search Results hz_timezones




Overview
Explore in AI Chat

Overview

The HZ_TIMEZONES table is a foundational reference table within Oracle E-Business Suite (EBS) that stores canonical time zone information. Owned by the AR (Receivables) module, its primary role is to provide a standardized, normalized list of time zones for use across the entire application suite. This table acts as a master source, ensuring consistent time zone data is referenced by numerous transactional and master data tables in modules such as Marketing (AMS), Service, and Tasks. Its design supports the global operations of EBS by enabling accurate time-based calculations and scheduling relative to specific geographical regions.

Key Information Stored

While the provided metadata does not list all columns, the table's structure is centered on a unique time zone identifier. The primary key is the TIMEZONE_ID column, which is the foreign key referenced by all related tables. It is reasonable to infer, based on standard EBS TCA (Trading Community Architecture) patterns, that the table also contains columns for the time zone name (e.g., 'America/Los_Angeles'), a descriptive field, and potentially an abbreviation. The table's purpose is to store the discrete list of valid time zones from which users can select when defining locations, contact points, or event schedules.

Common Use Cases and Queries

A primary use case is reporting and data validation, ensuring time-related data across modules is aligned to a valid reference. For instance, an administrator may need to identify all marketing triggers (AMS_TRIGGERS) set for a specific time zone. A common query involves joining HZ_TIMEZONES to a transactional table to translate the ID into a meaningful name for reports. For example, to list active marketing triggers with their time zone names:

  • SELECT trig.NAME, tz.TIMEZONE_NAME FROM AMS_TRIGGERS trig, HZ_TIMEZONES tz WHERE trig.TIMEZONE_ID = tz.TIMEZONE_ID AND trig.ENABLED_FLAG = 'Y';

Another critical use is during data migration or integration, where the HZ_TIMEZONES table is used to map and validate incoming time zone data before populating dependent tables like HZ_LOCATIONS or HZ_CONTACT_POINTS.

Related Objects

The HZ_TIMEZONES table is a central reference point, as evidenced by its numerous foreign key relationships. Key documented dependencies include:

  • AMS_TRIGGERS: Links via AMS_TRIGGERS.TIMEZONE_ID to define the time zone for marketing automation events.
  • AMS_EVENT_OFFERS_ALL_B & AMS_LIST_HEADERS_ALL: Other Marketing objects that reference it for scheduling and communication timing.
  • HZ_LOCATIONS & HZ_CONTACT_POINTS: Core TCA tables that store the time zone for addresses and contact methods.
  • CS_INCIDENTS_ALL_B: Service requests reference it for time zone tracking.
  • JTF_TASKS_B & JTF_TASK_AUDITS_B: Task management tables use it for scheduling and auditing time zone changes.
  • HZ_TIMEZONE_MAPPING: Likely used for internal mapping and conversions between different time zone standards.