Search Results get_date_time




Overview

APPS.OTA_TIMEZONE_UTIL is a utility PL/SQL package within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 codebase that centralizes time zone resolution, conversion, and lookup logic for the Oracle Learning Management (OTA) and, more broadly, the Oracle iLearning / Training Administration modules. The package is owned by the APPS schema and is classified as a UTIL (utility) API in the ETRM metadata, indicating that it is not a business-entity API with a formal lifecycle but rather a reusable service layer consumed by other packages, forms, and concurrent programs.

The primary business function of OTA_TIMEZONE_UTIL is to insulate callers from the complexities of time zone handling across the OTA schema. Events, offerings, resource bookings, and category usages each carry distinct time zone attributes (an online_flag on category usages, a timezone column on events, and a timezone_code on resource bookings). The package reconciles these attributes with the FND (Foundation) and HZ (Trading Community / Customer) time zone reference tables so that display names, identifiers, and converted date/time values remain consistent regardless of the invoking session's locale.

The metadata lists 14 documented procedures and functions, and the package is referenced by 17 other packages, confirming its role as a shared dependency across the OTA product family. Because it declares AUTHID CURRENT_USER, it executes with the privileges of the calling schema, subject to the standard APPS synonym grants.

Key Procedures and Functions

The documented subprograms fall into three functional groups.

Tables Accessed

The package declares two explicit cursors and, per the ETRM metadata, reads from the following tables through APPS synonyms:

Usage Notes

OTA_TIMEZONE_UTIL is typically invoked indirectly. Forms in the OTA/iLearning footprint (class scheduling, resource booking, and event maintenance) and concurrent programs that generate learner-facing schedules call these subprograms to render dates in the appropriate time zone. Custom code that needs to display or compare OTA event, offering, or resource booking times should call GET_TIMEZONE_NAME and the CONVERT_DATE family rather than querying FND_TIMEZONES_TL directly, since the package encapsulates profile-option handling and language-sensitive name resolution. Because the package is AUTHID CURRENT_USER and referenced by 17 other packages, changes to its specification should be treated as having broad impact across the OTA dependency chain.