Go live in HRMS wef 01/01/2000
To: 'HRMS Application Mail List' OraHRMS-L@mail-list.com
Subject: [orahrms-l] Going Live with Payroll on 1/1/2000?
From: Cindy Rockwell cindy.rockwell@infocus.com
Date: Wed, 19 May 1999 14:28:02 -0700
We are considering doing this to avoid loading year to date balances, but are concerned
about the perceived risk of changing anything related to systems on the dreaded Millenium
date!
Is anyone else going live with payroll on 1/1/00?
Effect on APPs on dates like 9/9/99
Date: Tue, 10 Aug 1999 00:08:53 -0500
From: "Voss, Tracey Lee" tracey.voss@au.unisys.com
Subject: RE:Y2K testing
Hi all,
Is anyone aware of any issues relating to the date 9/9/99 in either Oracle 7.3.4 server or
Oracle Financials 10.7SC 16.1? I have scanned metalink and have seen a statement that says
they are SURE that dates such as 9/9/99 will not cause problems because.... blah blah...
Does anyone have any real life experiences to relate?
Ta Tracey
Y2K test for Payment Batch spanning two years - Dec 31 to Jan 1
Date: Mon, 16 Aug 1999 12:17:39 -0400
From: Syed Nadeem Abbas nsyed@doubleclick.net
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: Y2k Testing for Oracle Financials 11.3
Hi,
I am in middle of putting some y2k test plans for Oracle Fin v.11.3. I heard about a
problem with cutting checks in AP that error out if the batch process span the new years (
that is Dec 31 to Jan 1).Is that true? And is there any site or something where I can get
some test plans.
Thanks Nadeem Syed
Y2K Cum Patches are included on the 10.7.16.1 Patch Set 4 CD
Date: Wed, 18 Aug 1999 18:58:05 -0500
From: "Uptmore, Chris" uptmorec@kci1.com
To: oraapps-l@cpa.qc.ca
Subject: RE: Confirm Shipment (Y2K Patchset 4??? - Patching Strategy)
This is a long message concerning 10.7 Patching Strategy and Y2K Patches. The bottom line
is, please respond only if you know with certainty how to read the Apps 10.7 Date Patch
List with respect to Y2K Cumulative patches vs. the 10.7.16.1 Patch Set 4; or if you know
it is being addressed in a new version due when (No guessing, since we're already doing
that.)
In the "Confirm Shipment" message ,
Chuck refers to "Oracle Y2K patch set 4" when I believe he meant "P16.1
Patch Set 4" or "10.7 Patch Set 4" (or "10.7.16.1 Patch Set 4"
since these patches are for Prod 16.1);
not to be confused with "Developer/2000 1.6.1 Patch Set 4" which is for the
JAVA-based Forms 4.5 "Forms Server" version for NCA (10.7 or 11);
and also not to be confused with Y2K Cumulative Patches.
"10.7.16.1 Patch Set 4" vs. "D2K 1.6.1 Patch Set 4" vs. "Y2K Cum
Patches" - three entirely different, mutually exclusive Patch concepts.
The 10.7 Patchset 4 released in April 1999 is made up of all the latest (as of 4/99)
"mega-patch" versions for each of the different Oracle Apps Product Groups,
(e.g., AP-Q, AR-Q, INV-C, OE-G, PO-M, etc.)
Oracle Corp. says you cannot make 10.7 Y2K-compliant without upgrading the RDBMS Server to
10.7.16.1, and you cannot apply the Patch Set 4 patches to a non-10.7.16.1 RDBMS Server.
The "MetaLink-based" Applications 10.7 Date Patch List V5.0 has a heading for
"Y2K Cum Patch" and a separate heading for "Patch Set 4". These
headings are used to specify whether a particular bug is fixed in EITHER a particular
"Y2K Cum Patch" AND/OR "Patch Set 4".
The thing that is unclear to me about the document is: what Y2K Cum Patches are included
on the 10.7.16.1 Patch Set 4 CD according to that document?
In terms of Patching Strategy, I would think this Date Patch List document would
"drive" at least people's "Y2K" Patching Strategy. So I doubt I am the
first use it for that.
I posted a question Monday on the MetaLink-based Forum called "Y2K Issues - Oracle
Apps Technical Forum" basically asking this: "Looking at that document, how can
you tell if a Y2K Cumulative patch was included in PatchSet4?"
I have had a hard time getting to the author(s) of this particular document, and have also
opened a TAR with Client Relations.
I realize I can search my 10.7.16.1 Patch Set 4 CD to see if a particular Y2K Cum Patch#
is included, but I'm thinking this should be obvious by reading the Apps 10.7 Date Patch
List document.
Rather than responding to this listserver, call Oracle Support if you are interested in
knowing the same thing. Or if you are an Oracle Employee, please reply to this Listserver
with the facts, (i.e., who is the author; is there a new version under construction that
will clarify this; etc.)
FYI and thanks,
Chris
Date: Thu, 19 Aug 1999 06:31:20 -0700
From: Karen Blackwell KBlackwell@rockshox.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Y2K Patchset 4??? - Patching Strategy
Chris -- I fully empathize with your situation. Rest assured that you are not the first to
use this document to drive Y2K compliance plan. After several ** very frustrating ** calls
to Oracle Support, I surrendered as NO ONE was able to provide a straight answer.
I pulled all "megas" from the Patch Set 4 CD (Applications patch set, Not D2K --
definitely not the same beast), uncompressed them all, read the readme's and reviewed EACH
patch driver for the bugs contained as part of the fix. Documenting all of this, I used
the latest (July 23) Date Patch List with all of the Y2K downloads from the Oracle FTP
site and the list of patches from the CD -- I created a folder for each module, gathered
all the facts I could sort out and the questions that still remained. Once that was
complete -- I opened a TAR with EACH support group for EACH module I have installed. (What
Fun!) For the most part (with the distinct exception of AOL who repeatedly directed me to
MetaLink) I got someone who readily discussed the ACTUAL requirements, and made available
the missing patches (there are several!). What I ended up with is a stack of patches ready
to go. Here's the other shoe: management has decided to go to 11, not to patch 10.7. All
in all -- this process took me about 5 days. Usually I only spent about 5-6 hours each day
on it because, gee, I have a job to do here (the other 5-6 hours of my day). ;-)
BTW: sometimes reading the matrix on the Date Patch List is very straightforward and
correct. Other times (other modules) it is not necessarily direct and is open to
interpretation. So -- what applies to one module does not apply to another module when
reading the matrix.
I apologize for having gotten long-winded. And I hope I have given you some useful
information. I will be happy to share any additional details with you if you would like.
Cheers
Karen Blackwell
DBA/System Administrator
RockShox, Inc.
408.570-4912 phone
408.435.7468 fax
Date: Thu, 19 Aug 1999 13:55:22 -0500
From: "Uptmore, Chris" uptmorec@kci1.com
To: oraapps-l@cpa.qc.ca
Subject: RE: Y2K Patchset 4??? - Patching Strategy
Thanks Karen!!
I went through the same routine in March/April to get us from 10.7.0 to 10.7.16.1C, as a
prerequisite for Y2K patching:
- opened a TAR with each product group;
- obtained/applied the latest megapatches;
- found out things like INV-C is a prerequisite for OE-G;
- pointed out the Sales Orders KeyFF info was not in the README, and had it added;
- pointed out the PO README had invalid/obsolete information, and had it updated;
- put all the TAR#s and info in a nice little doc for use in re-applying to a new test dbs
drop-down.
Then, a week later, the P16.1 Patchset 4 CD was released, containing all this info (with
the exception of AP, which already had superseded AP-Q with AP-R - and now it's up to
AP-T!!)
At the time, there was no reference to Y2K "Cum" patches, but we also grabbed
all available Y2K "one-off" patches.
I was hoping someone from Oracle Apps Support would see my last long diatribe (to which
you thoughtfully responded), and take some action with either my MetaLink 2.0 Forum
questions, or my TAR asking for the same info.
Thanks for your response, and no one from OraApps Support stepped up. This tells me they
are focusing on either:
- Rel 11 issues;
- 10.7 NCA issues (we are 10.7.16.1C "Char-only");
- avoiding Y2K "legal-schmegal";
- getting their children ready for school or;
- quitting Oracle and becoming consultants!!
No, that's not fair. They're PEOPLE - good folks - that are working just like us; are very
busy; and are doing the best they can.
It just seems to me OraApps Support Mgmt. could significantly reduce the telephone call
volume (and reduce the Support PEOPLE's workload) if this type of document had just one or
two more lines per Product Group:
- showing whether or not the particular Y2K Cum Patch was included on Patch Set 4; or
- pointing us to the FTP patch site to obtain each Y2K Cum patch and actually porting them
to the major platforms, (e.g., the AP Y2K Cum patches are on the FTP site under
AP_PROACTIVE/YR2K but the AOL Y2K Cum patches are not there under AOL_PROACTIVE!!)
I hesitate to do all the wasted leg work and documenting again with a feeling that a
"10.7.16.1 / post-PatchSet4 / Y2K Cumulative Patch Set CD" is in the works. Not
a rumor, just a feeling... okay, "wishful thinking"!!
Thanks again Karen!!
FYI,
Chris
25 hours day on Feb 29, 2000
From: Sandhya Patil [SMTP:spatil@symantec.com]
Sent: Thursday, July 29, 1999 9:56 AM
Subject: Feb 29,2000 (25 hour day ?)
Hi All,
I have question regarding February 29,2000 (25 hour day ?). What is this 25 hour day ? How
should we test this ? How will clock work for this 25hrs on 29 Feb 2000 ? I found this in
"Essential Dates to Test" paragraph of "Overall Suggestion for Year 2000
Testing of Oracle Application" published by baoaug. The internet address is
http://www.baoaug.org/TESTCOND.html.
Please send me your opinion on this to "spatil@symantec.com" this email address.
thanks, Sandhya Patil
From: Smith, Sean E. (Riverfront) [mailto:Sean.E.Smith@echostar.com]
Sent: Thursday, August 05, 1999 10:42 AM
Subject: RE: Feb 29,2000 (25 hour day ?)
I wrote the National Institute of Standards and Time. They are the government agency that
decides what time it is officially. They even add the occasional "leap second."
to the atomic clock in Boulder Colorado.
They stated that 2/29/2000 is not a 25 hour day.
So, I think we're all safe.
Autoinvoice and Y2K
Date: Tue, 31 Aug 1999 13:11:26 -0500
From: "Mandadi, Harish" HMandadi@obiwan.intecom.com
To: "'Multiple recipients of list'" oraapps-l@cpa.qc.ca
Subject: Auto Invoice Y2K Issue
Hi All,
We are in the process of Y2K testing. In that process we have bumped our system date to
31-Dec-99. We entered some orders and processed them, they all went fine until auto
invoice program and auto invoice import program some how is getting 28-AUG-99 as the
Invoice date. Did any body come across this kind of situation?? Any ideas.....
We are on HP UX -11 and 10.7 character.
Any help is greatly appreciated......
TIA
-Harish
Date: Tue, 31 Aug 1999 14:39:40 -0400
From: "=?ISO-8859-1?Q?Alain_Tr=E9panier?=" altrepan@agropur.com
To: oraapps-l@cpa.qc.ca
Subject: Re: Auto Invoice Y2K Issue
Hi
May be you can check the shipping date of your transactions ?
Alain Trepanier
Agropur
Management information systems, project manager
Date: Tue, 31 Aug 1999 13:45:37 -0500
From: "Mandadi, Harish" HMandadi@obiwan.intecom.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Auto Invoice Y2K Issue
Hi Alain,
Shipping date is 31-DEC-99
Thanks!
-Harish
Date: Tue, 31 Aug 1999 15:16:12 -0400
From: "=?ISO-8859-1?Q?Alain_Tr=E9panier?=" altrepan@agropur.com
To: oraapps-l@cpa.qc.ca
Subject: Re: Auto Invoice Y2K Issue
Check the flag of the invoice source (gl date in a closed period), which post your invoice
at the last day of the open period.
Alain
Date: Tue, 31 Aug 1999 14:23:37 -0500
From: "Mandadi, Harish" HMandadi@obiwan.intecom.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Auto Invoice Y2K Issue
Hi Alain,
It is Adjust.
Thanks!
-Harish
Date: Tue, 31 Aug 1999 18:11:18 -0400 (EDT)
From: Madhu Sudan Dada dada@csee.usf.edu
To: Multiple recipients of list oraapps-l@cpa.qc.ca
Subject: Re: Auto Invoice Y2K Issue
Check the trx date before and after you run autoinvoice. Due to shipping date actually trx
date should get computed. If trx date is null before submitting and it is 28-AUG-99 after
submitting .. and default date in submission was 31-DEC-99 then we have a problem.
Madhu Sudan Dada
PO Y2K Patches
Date: Tue, 31 Aug 1999 15:23:57 -0700 (PDT)
From: Mark Myszkowski myszko@yahoo.com
To: OraApps-L@cpa.qc.ca
Subject: PO Y2K Patch
PO has a requirement to either be on level O or N plus 903921 to have all the Y2K fixes.
This is per ver.5.2 of the Metalink patch list for 10.7 NCA. When I called support today
they said O isn't out yet and 903921 is still in testing! Has anyone heard anything about
this?
TIA
Y2K Notification
Date: Tue, 07 Sep 1999 08:58:34 -0500
From: "Danette Fedock"danette_fedock@ccmail.c-tec.com
To: oraapps-l@cpa.qc.ca
Subject: Y2K Notification
We are in Northeastern PA. I keep hearing that we will benefit when 12:00 on January 1st
hits because it will have already happened in other places in the world. Our testing has
convinced me that I am reasonably sure that we will have no problems, but I sure would
like to hear if anyone is having any trouble before it hits here. Is there any kind of a
network set up for notification?
Date: Tue, 7 Sep 1999 16:21:07 +0300
From: Mohammad Fouwaaz Mfouwaaz@savola.com
To: oraapps-l@cpa.qc.ca
Subject: RE: Y2K Notification
I have heard of a network -- but they say that it is not Y2K compliant! So they are
introducing this new ultra-modern, carrier-pigeon outfit.....
Date: Wed, 8 Sep 1999 09:19:21 +1000
From: "Bevin Watson" bevin.watson@abs.gov.au
To: oraapps-l@cpa.qc.ca
Subject: RE: Y2K Notification
There is apparently a group called The International Y2K Cooperation Centre in Washington
(the UN's Y2K arm). It has the useful acronym of IY2KCC. I would guess they have a web
site somewhere which might provide early warning.
We are providing them information as Australia is going to be one of the first places to
suffer the inevitable tidal waves and rioting.
I have heard of a network -- but they say that it is not Y2K compliant! So they are
introducing this new ultra-modern, carrier-pigeon outfit.....
Date: Mon, 13 Sep 1999 14:44:49 -0600
From: "Deborah Linke" LINKE@wapa.gov
To: bevin.watson@abs.gov.au, oraapps-l@cpa.qc.ca
Subject: RE: Y2K Notification
I received this from our Y2k coordinator and thought it might be of interest.
The United Nations has announced the establishment of Y2K emergency watch which will use
the Internet as a tool to keep tabs on the world as it enters the year 2000. The U.N.'s
International Y2K Cooperation Centre will lead the initiative which will see data
collected from more than 170 national Y2K coordinators. According to Reuters, its Web site
will flash colour-coded indicators on everything from energy and communications to
financial services, government services and air, land and sea transport. Anyone with
Internet access will be able to monitor country by country status through the transition.
(Source: Reuters, Sept. 9)
Periods opening in Year 2000
Date: Wed, 08 Sep 1999 11:41:23 PDT
From: "Murali Parthasarathy" mparthas15@hotmail.com
To: oraapps-l@cpa.qc.ca
Subject: Opening Periods in Year 2000
Hi ,
As part of our Y2k testing we are trying to open some periods in the year 2000. we did the
following .
* Created new periods for the calendar.
* When we Opened the Open/Close form we could not see the new periods created. We have 12
as the number of future periods opened in our Set of books .
In an another instance we could see the periods created in Year 2000 in the Open/Close
screen. We we try to open these periods the concurrent program ends with an Error . Any
help would ge greatly appreciated .
Thanks
Murali
Date: Wed, 8 Sep 1999 14:52:23 -0400
From: "Govathoti, George, CFCTR" ggovath0458@att.com
To: oraapps-l@cpa.qc.ca
Subject: RE: Opening Periods in Year 2000
Murali,
What version of the APPS are we talking about here ?
Thanks,
George!
Date: Wed, 08 Sep 1999 21:34:25 PDT
From: "ravi chandran" johnny_ravi@hotmail.com
To: oraapps-l@cpa.qc.ca
Subject: RE: Opening Periods in Year 2000
murali,
Ver10.7 has Y2K patches to be applied. Check with Oracle support as the number of patches
differ according to the modules. Ver11.0 has no problems.
Ravi
HR Y2K problems
Date: Tue, 14 Sep 1999 11:43:24 -0400
From: sbarbus@adtranzna.com
To: OraApps-L@cpa.qc.ca
Subject: Oracle HR Y2K issue with Medical and Dental element entries
We Have discovered a problem with our Y2K testing for HR. When we try updating or creating
medical and dental element entries in the Year 2000, we receive the following error
messages:
FRM-40735: ON-UPDATE trigger raised unhandled exception ORA-01841.
ORA-01841: (full) year must be between -4713 and +9999, and not 0
ORA-06512: at "HR_ENTRY_API", line 985
ORA-06512: at "HR_ENTRY_API", line 3536
We have applied all HR Y2K patches that have been recommended on Metalink. We are running
10.7 Smart Client, Solaris, HR only(we are not running Oracle Payroll).
Anyone have any suggestions or comments? Maybe we missed a patch somewhere along the line?
Help would be greatly appreciated.
Thanks,
Steven Barbus
sbarbus@adtranzna.com
412-655-6659
Date: Tue, 14 Sep 1999 12:20:10 -0400
From: Arun Darwar Arun.Darwar@yale.edu
To: oraapps-l@cpa.qc.ca
Subject: Re: Oracle HR Y2K issue with Medical and Dental element entries
We have also applied HR Y2K CUM PATCH ( 670050/ 715434 ) and we still have problems on the
same lines (mentioned below), but for different forms (refer -bug nos 658840 and 664395).
Since, We are not yet on 7.3.4 (DB VERSION) Oracle advised us to go to 7.3.4 or higher. We
are in the process of doing so and hopefully fixes the problem.
-- Arun
(Project - X, HR - Payroll Team )
WORK (203-436-3913)
Date: Tue, 14 Sep 1999 12:10:11 -0700
From: Brenda Finley bfinley@standard.com
To: "'oraapps-l@cpa.qc.ca'" oraapps-l@cpa.qc.ca
Subject: RE: Oracle HR Y2K issue with Medical and Dental element entries
We had the same problem. We needed a patch to fix stuff on both the client and server. I
don't believe going to 7.3.4 will fix the problem - but that's up to you! We're running
10.7SC 16.1 against 7.3.3.5 db on Sequent.
The bug numbers we had were 775115, 821800, 861559. Our TAR number was 11761751.600 if
that helps the support analyst.
Good Luck!
Brenda
P.S. It would be good for someone else to benefit from ALL THE PAIN we suffered with
Oracle on this bug!
Brenda Finley
Data Analyst IV, Business Technology Services
The Standard Insurance
1100 SW Sixth Avenue, P3B
Portland, OR 97204
[Mailto:bfinley@standard.com]
Y2K Confidence Testing on Jan 1
Date: Mon, 18 Oct 1999 11:46:11 -0800
From: Gordon Jones gpjones@gci.com
Subject: GEN: Y2K Confidence Testing on Jan 1
At my company on January 1, one of the first questions we will be asking
each other is:
"How is Oracle Financials running".
I have these questions for my fellow mail list readers:
-What will you be doing on Jan 1 to confirm confidence in your system?
-What tests, if any, will you be running? Will users be involved?
-Are you doing extensive testing, minimal testing, no testing?
-What was your thinking that led you to these decisions?
Obviously Jan 1 is too late to perform comprehensive Y2K testing, but what
are you doing to instill confidence in the database/application both to
yourselves and to your user community?
FYI
We use GL, AR, AP, INV and PO.
Release 11.0.2
Platform IBM RS6000, AIX 4.3.2
Database 8.0.4.3.1
We have read the Oracle Y2K white paper, and watched for appropriate
patches.
Looking forward to your response.
Gordon Jones
Date: Mon, 18 Oct 1999 16:24:47 -0500
From: "Danette Fedock" dfedock@ct-enterprises.com
Subject: Re: GEN: Y2K Confidence Testing on Jan 1
We have done extensive testing but still feel the need to come in on
the first to test. We plan to have one employee for every module that
we have who will do a shortened version of our Y2K testing. We are
hoping that it will not take more than a few hours.
Some might feel this is overkill, but I do not want to be around when
on the first workday, something breaks and they ask me why didn't I
test it in advance.
Date: Mon, 18 Oct 1999 16:46:34 -0400
From: =?iso-8859-1?Q?Alain_Tr=E9panier?= altrepan@agropur.com
Subject: Re: Y2K Confidence Testing on Jan 1
Gordon
In my company we did a full cycle tests on June 3 and 4 this year with many
users.
We are running AP, AR, GL and OPM in character mode. So far there is no
problem.
We schedule to have users in place january 1st and 2nd to do a full cycle
test of the applications with few transactions.
Regards,
Alain Trepanier
Date: Mon, 18 Oct 1999 14:52:49 -0600
From: "Deborah Linke" LINKE@wapa.gov
Subject: Re: GEN: Y2K Confidence Testing on Jan 1
We are backing up our production instance and shutting our database and
computer completely off on December 31. On the first our DBAs and network
folks will be in to bring the system back up. On the second, we have a
person and a backup from each module coming in to run through a checklist
of key functions and reports. We have other employees on call to come in
and assist with problems, if necessary.
Date: Mon, 18 Oct 1999 19:51:09 -0400
From: "Bill Dunham" bill.dunham@bosscorporation.com
To: oraapps-l@cpa.qc.ca
Subject: RE: Y2K Confidence Testing on Jan 1
Gordon -
Your not alone. Many organizations have procrastinated on the subject of Y2K
Testing for a long, long time. Some organizations are taking the vendors
Y2K statements to the bank and others are not...it all comes down to how
comfortable you and your organization are with the situation. I'm working
with a client that decided to do something about it rather than take the
wait and see attitude. They began testing today with the first of a series
of tests to be performed. We spent a little over two weeks planning the
effort. This not only includes the Oracle Applications, but the entire
organizations IS operations. Good luck...
Regards,
Bill Dunham BOSS Corporation