Search Results sysdate00_in_server

Overview

FLM_TIMEZONE is an Oracle E-Business Suite PL/SQL package owned by APPS and classified as OTHER within the ETRM repository. Its purpose is to provide centralized timezone conversion support for the Oracle Flow Manufacturing (FLM) modules and any dependent application code. The package header declares AUTHID CURRENT_USER, meaning that all unqualified object references execute under the privileges of the invoking session rather than the package owner, which is consistent with the APPS schema model in Oracle EBS 12.1.1 and 12.2.2.

The package is built around a set of package-level global variables that capture the session's timezone environment at initialization time. In particular, g_enabled is a BOOLEAN flag derived from three profile options: ENABLE_TIMEZONE_CONVERSIONS must equal 'Y', CLIENT_TIMEZONE_ID and SERVER_TIMEZONE_ID must both be non-null, and the two timezone identifiers must differ. When this flag is true, the package performs real conversions between server and client time; when false, conversion functions effectively pass values through unchanged. Additional globals hold the client timezone ID, the server timezone ID, an initialization state flag (g_init), client and server start times, and the organization ID.

Key Procedures and Functions

• INIT_TIMEZONE — Initializes the package for a given organization. It accepts an organization identifier and sets up the global state (including the organization context and start-time baselines) required before any conversion function is called.
• IS_INIT — Returns a BOOLEAN indicating whether the package has already been initialized for the current session and organization. Callers use this to decide whether INIT_TIMEZONE must be invoked before performing conversions.
• SERVER_TO_CALENDAR — Converts a date expressed in server time into the corresponding calendar date used by the application.
• CLIENT_TO_CALENDAR — Converts a date expressed in client time into calendar form (introduced under bug fix 3840945).
• CALENDAR_TO_SERVER — Converts a calendar date back to server time, with an optional server-time component; its signature was modified under bug fix 3827600.
• SERVER_TO_CLIENT — Translates a server-side date into the equivalent client-side date.
• CLIENT_TO_SERVER — Translates a client-side date into the equivalent server-side date.
• CLIENT00_IN_SERVER — Returns the client's midnight (00:00) expressed in server time.
• SYSDATE00_IN_SERVER — Returns the current day's midnight expressed in server time.

Tables Accessed

The package references two tables through APPS synonyms. HZ_TIMEZONES is the Oracle Trading Community Architecture (TCA) timezone repository and supplies the timezone definitions, offsets, and daylight-saving rules needed to resolve the CLIENT_TIMEZONE_ID and SERVER_TIMEZONE_ID profile values into concrete conversion logic. WIP_LINES is referenced in the context of Work in Process data, since Flow Manufacturing scheduling and shop-floor records carry dates that must be interpreted consistently with the server timezone. Together these accesses let the package translate persisted dates without requiring each calling module to maintain its own timezone logic.

Usage Notes

FLM_TIMEZONE is referenced by eight other packages within the EBS environment, indicating that it functions as a shared utility rather than an end-user API. Callers typically invoke INIT_TIMEZONE once per session or per organization context, then guard subsequent conversion calls with IS_INIT to ensure the globals are populated. Conversion functions are used from Flow Manufacturing forms, concurrent programs, and custom extensions that store or display date-time values across client and server time zones. Because behavior is governed by the ENABLE_TIMEZONE_CONVERSIONS and timezone profile options, deployments that leave conversions disabled will observe pass-through results, and end users may see no change after upgrades. The package header also notes that several previously existing procedures were removed under bug fix 3827600, so any custom code written against an older revision should be reviewed for compatibility.