Time Zone settings...UTC not being reflected properly.

Good Afternoon!

It hasn't been an issue for us to pay attention to in the past...but because of a few commercial changes, this problem is very visible.

Our Time Zone settings in DRS045 for &SYS is -5:00 from UTC (essentially Eastern time).

However when I look in the database (specifically at Order Lines) the column for Local Time (OBCOHM) is identical to the column for UTC (OBCOHZ). No conversion to UTC is being done for the UTC columns.

Has anyone experienced that before? And perhaps do we have things configured incorrectly?

Thanks,

Steve

Find more posts tagged with

Accepted answers

All comments

simon-pentolfe

Hi Steve - my understanding of these fields for our 13.4 On Prem version is that they show the time for the warehouse and the customer, not specifically UTC.

M3 will get the time zone from the place for the MMS005 record and CRS610 record and use this for the conversion. When an order is placed in M3, the requested time is entered in the customer's time zone and converted to the warehouse's time zone.

Legacy Contributor

So if that is the case, then if the Customer and Warehouse are in the same Time Zone, it is intended for these to be equal?

Legacy Contributor

Hi Steve,

If you are on M3 CE then check out this KB article KB 2091107. Otherwise make sure you check the time zone definitions are correct as per Simon's suggestion.

Abstract:

Conversion of system date and time to user time zone in configurable views.

Background:

In M3 CE, all system dates are stored in UTC in the database. In some programs, the system date and time is part of the key and in order to work with such a program it would be easier to view the system dates and times in the user's time zone.

Legacy Contributor

We are M3 Cloud Single Tenant...

And as I look in the database at the Order Line table...the record Create Date, Create Time, Order Dates and Time...are all in my Local...not UTC.

simon-pentolfe

Yes - the point of these times are to let the warehouse know in their time zone when the product needs to arrive at the customer and for the customer to know in their time zone when they will get the product,

Legacy Contributor

Apologies
&SYS should be set at 0 hours
Take note that for M3 CE, the server time is in UTC and therefore, &SYS should always be 0 hours from UTC. movexDate() and movexTime() are always considered to relate to the &SYS time zone. RGDT, RGTM, and LMDT are stored in the database in the &SYS (Example: these fields are always displayed as server times without conversion).
Then you would create AEDT & AEST zones which would be defined in relevant Time Zone programs.

Copyright © 2025 Infor. All rights reserved.