Note:
All dates used in scheduling logic, including the MISDATE field, are
consistently stored and processed in UTC (Coordinated Universal Time). This
design ensures that scheduled batch executions and system date calculations
remain standardized across all regions, eliminating discrepancies caused by
local time zones. The MISDATE represents the scheduled date of a batch as
stored in UTC. It does not adjust based on the user’s local time zone. The
SYSDATE function always reflects the current date and time in UTC when used
for scheduling logic.
Example: If a customer in Singapore (UTC+8) schedules
a batch for March 16th at 02:00 AM local time, the system automatically
converts and stores it as March 15th, 18:00 UTC. When any user views the
MISDATE field for this batch, it will display 2024-03-15 (the UTC date
stored).
Similarly, the SYSDATE value is based on the current UTC date
and time, ensuring all scheduling logic is aligned with the UTC standard. As
a result, while the user schedules the batch for March 16th in their local
time zone, the system consistently operates on the equivalent UTC date,
maintaining uniformity across all locations.