Re: JD Edwards Dates

["Michael Kenney" <kenney@xxxxxxxxxxx>]

I believe one of the reasons to going julian was to add a century without
increasing the file sizes.  They represent the julian date as CYYDDD where
C is the century.  0 is  1900 and 1 is the year 2000.  January 1,  2000 is
represented as 100001 and December 31  1999 is 099365 . However I don't
beleive this follows the SI protocol.

Personally  I find the Julian date easier to work with when doing reports.
Before I would need to compute a value in order to select a range of dates
that spanned a year.




> Somewhere along the line I must not be living right because I seem to be
> paying for it now...

> We are in the process of upgrading from JDE A6.2 to A7.3.  We just came
> across the documentation for date storage.  Historically, JDE has stored
> stuff in Gregorian format in four seperate fields DD, MM, CC, and YY.
>
> Now in 7.3 all dates are being changed to 'Julian'.  The format is XYYJLN
> where X is a centery flag(0 = 19, 1 = 20), YY is year, and JLN is the
> Julian day within a year.

> According to their documentation, and I quote, 'Julian date processing
> allows for the use of a single field, eases manipulation, sorting, and
> calculation of dates'.

> I'm real frustrated because we have to change a lot of access points.
> Multiple systems, DDM files, modifications, and query tools.  Am I
missing
> the boat or does this change make sense.......besides benefiting JDE?



Michael Kenney
University of Windsor
Canada
KENNEY@UWINDSOR.CA


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---