Whats the Sequence to apply

Hi List,

If I have to apply Update 1 ,JE4185 and SP22 on ERP 8 what should be the steps I need to do.
Should I :
1) Apply JE4185
2) Build and deploy Update Package
3) Apply Sp22 on both DS and ES
4) Apply Update 1
5) Build and deploy a Full Package.

Please advice..What if if the sequence is not followed?
How does it effect the system stability?

Thanks in advance.

I would apply SP, then the ESU, then the Update and then build a full package.

You may have all sorts of issues if the ESU requires SP you do not have and there's no reason to buils an Update package in between.

Logs with errors would be helpful too...

Regards,
Alex.

There are nothing in the logs as such..for update package built I get a warning messages for all the UBE version and at the end when it goes to update the parent package it is unable to update the same and the client package ends with error, surprisingly server package completes successfully.

Seing this i tried to roll back to SP21 and tried to build a update package ..it just worked. On the other hand even I tried applying the another ESU to another Environment (it went successfully no issue at all) but on building a update package I get the same set errors as stated above.

thanks in advance

Sunny...

I think there are a number of variables that would help determine a most
efficient order. The first thing is that obviously, the Planner ESU
should be put down prior to the Update. But the overall order will
really depend on your business needs and time frame you have for testing.
A planner ESU generally speaking doesn't modify anything that is used by
end users, as it usually is only concerned with objects and processes
used during ESU, ASU, and Update application processes. So the Planner
ESU can be applied with minimal chance of any issues affecting the normal
business operations. An Update and Service Pack, on the other hand, will
usually have changes (lots, in most cases), that affect the business
processes. If you have a large amount of time for testing everything,
one method would be to apply everything, then build a package and test
for and fix issues. In that case, I'd say the easiest method from an
administration standpoint would be to apply the SP and Planner ESU
(shouldn't matter which order), build and deploy a package (to test, as
SP's can affect the package build/deploy mechanisms), then apply the
Update and build and deploy packages as needed. Now, if testing and
issue fixing time is at a premium, I believe the best bet would be to
apply the Planner ESU and SP, build and deploy packages, test for issues,
fix any items, then apply the Update, test, and fix. The reason I
suggest this, is that if you apply the Update and SP together and run
into issues, you are in the uncomfortable position of having to determine
is the issue caused by the SP or the Update (or in some cases a
combination of the two)? If you apply the SP and Update separately, you
isolate issues to either the SP or the Update. Plus, if the issues are
insurmountable, you can more easily pull off a SP or Update by itself,
rather than trying to undo both.


That's my story, and I'm sticking to it.

Good Luck,

Jim

________________________________________________________________
The best thing to hit the internet in years - Juno SpeedBand!
Surf the web up to FIVE TIMES FASTER!
Only $14.95/ month - visit www.juno.com to sign up today!