Century Date-Compliance

scott_parker

Reputable Poster
I just entered in a Sales Order and put the Pick date as 11/21/25.
Which I would think would be tomorrow in 25 years?
NOPE JDE wrote the date out as tomorrow 25 years ago.
The julian date that was written out did not have that leading 1 (that specifies the century 2000)

After doing another test it seems that anything Greater then the Year 2010 gets written out as 19xx and not 20xx.

the date routine X0028 is the date routine that seems to be doing this.

So why did it move a 19 into the julian date and not a 20?

Anyone else have this happening??

Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R4 (soon to be V4R5)
 
Scott,
There is a data element in the data dictionary that tells the system
where to break between the two centuries. As soon as I can remember what it
is called I will let you know, in the mean time maybe someone else can
remember what its name is.
 
Scott,
Look at your data dictionary item #CYR - Century Change Year, you
will probably find that you need to adjust this number because it is sitting
at 10.
 

scott_parker

Reputable Poster
Re: RE: Century Date-Compliance

I tried that. Its at 50.

Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R4 (soon to be V4R5)
 

scott_parker

Reputable Poster
After further investigation I have found out that the Program X0028 does not match the source that JDE sent us.

Actually the Source they sent us has 2 copies of the program in it.
2 sets of F specs 2 sets of I specs etc. It looks like they copied the whole program at the end of itself.
After Deleting the 2nd set and recompiling it does work fine.

I have NO clue what the source is for the current Pristine Object we have.


Interesting

Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R4 (soon to be V4R5)<P ID="edit"><FONT SIZE=-1>Edited by scott parker on 11/20/00 12:54 PM.</FONT></P>
 

tstauf68

Member
JDE has a system constant the defines where the year 1900 starts. Most systems are set to 10. Sorry I can't remember where it is set.

Tim Stauffer
VP, Marketing Systems, Strings & Accessories
United Musical Instruments
Running JD Edwards World 7.3 cum 10
[email protected]
 

DBelcher

Active Member
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0534C.0EEA39A8
Content-Type: text/plain;
charset="iso-8859-1"

Scott,

This is controlled by the field #CYR and the default value is 10 and it
represents the end of the 100 year window that JDE is using in order to
determine if a date should be '19' or '20'. Check out the DD and it should
show the default value. Careful if you change it because if you have dates
in your system that reach back to 1911 (i.e. birthdays) they will suddenly
be 2011!

Doug Belcher
KV Pharmaceutical
St Louis MO
Opinions expressed are not necessarily those of my employer


>

Doug Belcher
St Louis MO
Opinions expressed are not necessarily those of my employer
 

zuccoa

Active Member
R:Century Date-Compliance

Scott,

we are at 7.3.10, we also have the same situation that you described, but
I've always thought that this was the normal "century windowing" approach
that JDE had decided to fix the Y2K bug.
In fact I was expecting that in some future release or SAR they would have
introduced a longer term solution ...

Could you please tell me where and how you got the source that "...does
work fine" ? Is it included in the 8.1.2 ?

TIA

A.Zucconi
TUBILUX PHARMA Spa

----------
Da: scott parker[SMTP:[email protected]]
Risposta a: [email protected]
Inviato: lunedi 20 novembre 2000 21.53
A: [email protected]
Oggetto: Re: Century Date-Compliance ~~1453:1466

After further investigation I have found out that the Program X0028 does
not match the source that JDE sent us.

Actually the Source they sent us has 2 copies of the program in it.
2 sets of F specs 2 sets of I specs etc. It looks like they copied the
whole program at the end of itself.
After Deleting the 2nd set and recompiling it does work fine.

I have NO clue what the source is for the current Preston Object we have.


Interesting

Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R4 (soon to be V4R5)
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=W&Numbe
r=1466
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

scott_parker

Reputable Poster
Re: R:Century Date-Compliance

The source that does work fine is in a way "Custom".
What I did was Delete the 2nd set of code that is in the X0028 program and then re-compilied it.
If you do a search in that source for the word MainLine you will see that there are 2. 2 sets of F specs 2 sets of I specs etc etc. I just deleted the 2nd set and then changed the DD value of #CYR to be 50 instead of 10.

That seems to have worked.
I will be calling JDE today and find out if this Code thing is a known problem in 8.1.2 (the version we are running)

Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R4 (soon to be V4R5)
 
I think I might have missed some of this conversation but ..... if you check
the "Default" value in the Data Dictionary for #CYR, the value in that field
determines the split for 19xx and 20xx. Example, if the value is "40", any
year 01 - 40 is 20xx. Any other value is 19xx.

Janelle Green
Gale Group
Farmington Hills, MI
 

ahenry

Member
The Data Dictionary field #CYR is used by X0028 to determine the cutoff point
for a date to be in the 19th or 20th century.

We increment that date by 1 every year. We try to make sure that number is
always approximately 75 years less than the current year. (ie. ours is set to
25 for this year)

____________________Reply Separator____________________
Subject: Century Date-Compliance ~~0:1453
Author: <[email protected]>
Date: 11/20/2000 12:04 PM


I just entered in a Sales Order and put the Pick date as 11/21/25.
Which I would think would be tomorrow in 25 years?
NOPE JDE wrote the date out as tomorrow 25 years ago.
The julian date that was written out did not have that leading 1 (that
specifies the century 2000)

After doing another test it seems that anything Greater then the Year 2010 gets
written out as 19xx and not 20xx.

the date routine X0028 is the date routine that seems to be doing this.

So why did it move a 19 into the julian date and not a 20?

Anyone else have this happening??

Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R4 (soon to be V4R5)
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=W&Number=1453
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

got_to_love_jde

Reputable Poster
scott,
contrary to all of the other opinions written here i believe that 2010 is the NEW unannounced date for ending World support ! (tee, hee,hee)
dave


NT 4.0 SP5, SQL 7.0, One World B7321 SP12.4
 

scott_parker

Reputable Poster
Does that mean they support World now?

(tee, hee, hee)

Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R4 (soon to be V4R5)
 
Top