Change last day of Feb 2000 from 28 to 29
Date: Tue, 20 Jul 1999 09:01:18 -0400
From: Teri Forner tforner@fore.com
Subject: GL: Is your accounting calendar for Feb-00 a leap year?
We are currently doing Y2K testing, and are testing the leap year 2/29/00
date. But, we've run into a BIG problem. Our Accounting Calendar in GL
for FEB-00 was setup from 01-FEB-2000 to 28-FEB-2000, instead of
01-FEB-2000 to 29-FEB-2000.
Now the application will not let us change this. I've called Oracle
Support, and they said we had to create all new sets of books (30+). This
obviously isn't practical.
Is there anyone else who has this problem? Do you have a way to correct
this problem?
Your help would be greatly apprecieated.
Date: Tue, 20 Jul 1999 09:10:55 -0400
From: "McShane, Chris" Chris.McShane@glenayre.com
Subject: RE: Is your accounting calendar for Feb-00 a leap year?
We just recently went through this problem and oracle support provided a
supported solution. Below are the scripts they sent to me.
update gl_periods
set end_date = to_date('29-FEB-00','DD-MON-RR')
where end_date like '%28-FEB-00%';
update gl_period_statuses
set end_date = to_date('29-FEB-00','DD-MON-RR')
where end_date like '%28-FEB-00%'
AS GL
SET ECHO ON
SET FEEDB ON
TRUNCATE TABLE GL.GL_DAT_PERIOD_MAP TABLE
RUN GL_TOP/ADMIN/SQL/GLUABCAL.SQL
Date: Tue, 20 Jul 1999 09:13:12 -0400
From: "McShane, Chris" Chris.McShane@glenayre.com
Subject: RE: Is your accounting calendar for Feb-00 a leap year?
In regards to my earlier post, this will not fix the problem if it occurs in
the Projects module.