Search Results server_to_client




Overview
Explore in AI Chat

Overview

APPS.FLM_TIMEZONE is a PL/SQL package body in the Oracle E-Business Suite APPS schema that provides time zone conversion utilities for the Flow Manufacturing (FLM) module. Its central business purpose is to reconcile the divergent time zone contexts that exist between the application server, the client tier, and the calendar used by Flow Manufacturing scheduling. The package maintains an internal notion of whether time zone initialization has occurred and then exposes a family of conversion routines that translate date-time values between server, client, and calendar representations.

The package is classified in the ETRM metadata as an OTHER API, indicating that it is a supporting utility rather than a public, fully documented interface. The object is VALID in both Oracle EBS 12.1.1 and 12.2.2, and it sits low in the dependency stack: the metadata explicitly states that APPS.FLM_TIMEZONE is not referenced by any database object, meaning nothing in the database depends upon it, although it is itself referenced by eight other packages. This position is characteristic of a foundational helper utility consumed by higher-level Flow Manufacturing processing.

Key Procedures and Functions

The documented interface comprises nine procedures and functions. Their names reveal a coherent conversion and initialization design:

  • INIT_TIMEZONE — performs the package's time zone initialization, establishing whatever session or package state the conversion routines later rely upon.
  • IS_INIT — a status check that reports whether initialization has already been performed, allowing callers and the package itself to avoid redundant setup.
  • SERVER_TO_CALENDAR — converts a date-time expressed in server time into the equivalent calendar time zone value.
  • CLIENT_TO_CALENDAR — converts a date-time expressed in client (user session) time into calendar time.
  • CALENDAR_TO_SERVER — the inverse of the above, translating calendar time back to server time.
  • SERVER_TO_CLIENT — converts server time to client time for display or form-side processing.
  • CLIENT_TO_SERVER — converts client-supplied time to server time for storage and comparison.
  • CLIENT00_IN_SERVER — a specialized conversion variant, typically associated with normalizing a client-based value at the start of a period or day into server representation.
  • SYSDATE00_IN_SERVER — a specialized routine that derives the current system date anchored to midnight (00) in server time, providing a consistent day-boundary value for comparisons and shop-floor scheduling.

Parameter lists are not documented in the ETRM metadata and are deliberately not stated here; callers should inspect the package specification for exact signatures.

Tables Accessed

The package reads from two tables exposed through APPS synonyms:

  • HZ_TIMEZONES — the Trading Community Architecture (TCA) time zone reference table. It supplies the time zone definitions, offsets, and identifiers required to perform accurate conversions between server, client, and calendar zones.
  • WIP_LINES — the Work in Process production line table. Flow Manufacturing scheduling and calendar logic is associated with work in process lines, so accessing WIP_LINES allows the package to resolve the calendar context relevant to a given line when converting date-time values.

The dependency metadata additionally lists FND_MSG_PUB, FND_PROFILE, HZ_TIMEZONE_PUB, and STANDARD among referenced objects, indicating use of the message dictionary for error reporting, profile option retrieval for time zone or calendar settings, the TCA time zone public API for conversion services, and standard utilities.

Usage Notes

FLM_TIMEZONE is an internal utility rather than an end-user-facing interface. It is invoked programmatically by the eight packages that reference it, which occupy higher layers of Flow Manufacturing and scheduling logic. Typical invocation patterns include Oracle Forms sessions in the Flow Manufacturing module and concurrent programs that process or schedule production data, where consistent translation between user session time, application server time, and the manufacturing calendar is essential. Because the package holds an initialization flag queried through IS_INIT, callers should ensure INIT_TIMEZONE has executed before relying on conversion results, or allow the package to initialize lazily. Custom code extending Flow Manufacturing should treat this package as a dependency, not a supported public API, and should account for the possibility of definition changes across releases.