Best way on Update installs?

We are planning to install Update 6.

We've got a CD dated 05/29/2002. Is that the latest? Is the bug fixable when copying F00165?

It seems to me, that the best way is to install first into an alternate environment (ESU7333), retrofit the mods in that environment and building a package for user integration testing. Then I would install into DV7333, PY7333 and transfer the mods from ESU7333 into these environments. Let the user final test in PY7333 and after this install in PD7333 and transfer mods as well.

How do you handle the installs in JDE's recommendation as described in SU Update Guide? Isn't it a problem when updating the DV7333, PY7333 with the update and simultaneous development? We do all user-development (versions, etc) in PY7333 and then transfer. So when we would update PY7333, the templates could be different.

Hi Michel

The update 6 CD date you have is the same date as I have - I believe that the date is the build date - and is often waaay before the release date.

As for how to make a large update manageable - please seek down a copy of my whitepaper "ESU Implementation Procedures" which details specifically how to implement the ESU only in Pristine (or a new pristine ESU pathcode, if you MUST have a true "pristine - no update" pathcode around !) - and to then go through OMW and split the project into 2 projects - a new "Retrofit" project that stays in Pristine and does not over-write the code in DV. Then all objects NOT requiring retrofitting can be moved through DV and into your QA procedures without worry of over-writing of code - and any objects left can be retrofitted using a variety of methods including Visual ER compare if you wish !

My whitepaper is on my website and is also in the "Tips and Tricks" section. A lot of my whitepaper finally appeared in a book recently....

Jon Steel
OneWorld Upgrade Specialist
http://www.erpsourcing.com

Hi altquark,

thanks for your reply. I had a look on your document and on others in KG as well.

With the issue of big projekt in OMW in mind, I'd prefer the install into every environment and transfer the retrofitted mods afterwards.

I would be extremely careful concerning this. Although you might prefer this technique - I am sure that your development staff will place you in a corner, and line up to beat the stuffing out of you !!!!

In a development environment, if you install an ESU to every environment - and someone has modified a JDE base object (which is not recommended, but does indeed happen - often without the CNC administrators knowledge !) - then all their code will be blown away. This is why customers are so angry that JDE is adamant in creating "monster" ESU's - since it touches WAY too many objects, and the standard procedure will blow away their development.

The only safe way to do this is through the document I wrote - install to pristine, and promote through OMW those objects that are safe - it works exactly the same way, but is controllable, and takes a little extra effort and time.

Jon Steel
erpSOURCING LLC
http://www.erpsourcing.com

Take a look at https://knowledge.jdedwards.com/bestpractices