Hi All,

Internally Baan ERP (Baan V) stores all the dates as UTC dates.
Is it the same with Baan IV? or in Baan IV all the dates will be stored as local dates?

Thanks,
Sat

It converts the date into the number of days, from the beginning, i.e., 01-01-01.

ok thanks morpheus.
So, you mean to say that baanIV uses 'Local Date Format' to store the dates and not UTC format.

SAT,

morpheus, means that in BaaN-IV, the dates are converted into numbers are stored.

Most of them use the tools function - http://www.baanboard.com/programmers_manual_baanerp_help_functions_date_time_zones_date_num[/WIK]

Can you please elaborate ?

So, you mean to say that baanIV uses 'Local Date Format' to store the dates and not UTC format.


Do you mean the time zone set by the user data template?

Hi Rao,

I know that the long value will be stored for a date in Baan.

BaanV internally stores all the dates as UTC dates i.e. number of seconds (long value) since 01-01-1970 T 00:00 ,

but what my doubt is,
is it the same in Baan IV too? i.e. even in Baan IV the dates are treated as UTC dates internally or they are stored as local dates (again number !!!) which is number of days since 01-01-0001

Hope this time it is clear.

Thanks,

Hi,

Baan IV only supports the "date" type (i.e. number of days since 01/01/0001).
Baan V supports both "date" and "utc" types. Here again the "date" type represents the number of days since 01/01/0001. The "utc" type represents the number of seconds since 01/01/1970.

Your assumption that since Baan V all dates are stored as "utc" internally is wrong.

Hi FransG, Thanks for the reply..

But what I read from the BaanV help is that, In BaanV internally the dates are stored as UTC dates.
please see BaanERP help below :


Universal Coordinated Time

BaanERP provides time-zone independent date and time support. The user interface always shows local dates and times. Internally, however, BaanERP stores dates and times in Universal Coordinated Time (UTC). It stores both date and time in a single long integer referred to as the UTC long format. This integer represents the number of seconds since 0:00 hour, January 1, 1970 (in UTC). The use of a long integer imposes an upper date limit of 2038.

© 1998 Baan Development B.V. All rights reserved



Regards,

Sat,

As Frans, has mentioned -

Your assumption that since Baan V all dates are stored as "utc" internally is wrong.

If you refer to the tables like, ttadv505, ttams330-342 (role authorization related templates), the date storage is still based on the number or days. But most the application tables date/time formats have been modified to UTC formats but not the tools tables.

So I think you need to be clear and explicit about what you are looking for or your requirement is.

Hoi Frans Gerritsen, nice to hear from you... :p

Hi *ALL,

in BaanIV you have the type date and the type time. The type date is still the same in BaanV but the type time is changed to UTC. Time only store the time and not the time combined with a date. UTC in BaanV stored a date/time combination.

The other issue is the way the time is stored in BaanIV. So is the time stored with the local value in the database or with the UTC or GMT time. Like my experience is till now this is differently handled in the sessions. The jobhandling was changed some time ago from local time to UTC time handling. If you look for the time values in the ttaad5xx tables then you see the time is stored for the timezone 0 (GMT) and all the display is for local time.

So please keep the 2 different issue in mind. The way of storing data and the transformation of the time.

I hope this helps and it was hard to understand,

Garfield :eek:

Originally posted by NPRao
Sat,

As Frans, has mentioned -

Your assumption that since Baan V all dates are stored as "utc" internally is wrong.

If you refer to the tables like, ttadv505, ttams330-342 (role authorization related templates), the date storage is still based on the number or days. But most the application tables date/time formats have been modified to UTC formats but not the tools tables.

So I think you need to be clear and explicit about what you are looking for or your requirement is.

Hoi Frans Gerritsen, nice to hear from you... :p

Then how come the BaanERP help is giving wrong information about the dates? Read the below quote

Universal Coordinated Time

BaanERP provides time-zone independent date and time support. The user interface always shows local dates and times. Internally, however, BaanERP stores dates and times in Universal Coordinated Time (UTC). It stores both date and time in a single long integer referred to as the UTC long format. This integer represents the number of seconds since 0:00 hour, January 1, 1970 (in UTC). The use of a long integer imposes an upper date limit of 2038.

© 1998 Baan Development B.V. All rights reserved


Regards,

Sat,


Then how come the BaanERP help is giving wrong information about the dates? Read the below quote

BaanERP provides time-zone independent date and time support. The user interface always shows local dates and times.


Since, I am no more in the BaaN R & D, I cannot give you the right answer. But my general remark is - that quote is meant for the application tables. There will be a lot of issues for changes to the tools internal tables, upgradations between tools shuttles/service packs/versions, affects the job timings, role authorizations, log changes etc. So it will take sometime, versions to have all utc enabled.

So, the end user should not be worried of what format the tools tables are using as long as they are working. The tools are BaaN propritory. If the application tables are using the UTC then you have the advantage to have the time zone independent format, which will be useful for the order management, shipping, delivery, planning dates/time etc.