How often does your organization apply ESU's to stay fix current?

Mountain_Dave

Active Member
How often does your organization apply ESU\'s to stay fix current?

We're trying to get a process in place for our 5+ instances before they get too out of synch. Any help or input would be greatly appreciated. Thanks!

Also, if you've voted, can you please put a note as to why you went that route? Thanks again!

<font color="white"> zombie </font>
 
Re: How often does your organization apply ESU\'s to stay fix current?

We only apply ESUs during TR or Application (E1) upgrades because of the time taken to test all parts that an ESU touches, which varies. If we have a specific problem that is fixed in a certain ESU, then we may apply and test that ESU, or take the fix we need from the ESU if possible or fix the problem ourselves - depending on the nature and impact of the problem and the resources required for each option, including testing.
 
Re: How often does your organization apply ESU\'s to stay fix current?

David,

I selected "Other" in your survey because frequency depends on where we are in a release version's "cycle".

When first implementing or upgrading, the ESUs fly fast and furious. However as the customizations increase, as the implementation/release stabilizes, the application of ESUs falls to nearly zero by the last year of the release version's life cycle.
 
Re: How often does your organization apply ESU\'s to stay fix current?

Peter,

It depends - on our XE systems, the ESUs are by request. Usually 2 or 3 a year. On our 8.12 and 9.0 systems, we bring the entire system up to "code current", then apply our objects. Then ESUs and service packs are applied much more frequently.

- Gregg
 
Re: How often does your organization apply ESU\'s to stay fix current?

What about when updates come out, Update 3 for example? Thoughts?
 
Re: How often does your organization apply ESU\'s to stay fix current?

I have selected "Other" in your post. It all depends on the need of the Client to be code current and how many resources they have available to take care of retrofitting and related testing of objects which are touched by the ESUs. I have even worked with the Clients who did not take any ESU in 2 years and decide to take individual SARs if they need to have some new functionality. In this case you have to always take care of the compatibility issues and see if this SAR requires any Baseline ESU.
 
Re: How often does your organization apply ESU\'s to stay fix current?

Tend to do baselines at the tools release at it only means one test of testing.

Keep the planner up to date though, and obviously ESUs as they come up against issues.
 
Re: How often does your organization apply ESU\'s to stay fix current?

There's no formal difference between Fix Current and Updates.
PS You may have an update in E1 9.0
cool.gif
Did you notice the "newest" Update in 812 dates 2008
grin.gif
 
Re: How often does your organization apply ESU\'s to stay fix current?

You should apply the code-fixes to stay "fix current" throughout a CRP. Once a system goes live, and you are running in Production - then only those ESU's that are necessary to fix a business issue needs to be applied. That might require a baseline ESU (or Update) to be able to implement a specific fix - at which point you are kicking off an upgrade project (but its a smaller "update" - not necessarily a full release upgrade).

Only implement what you need for your business to be able to run. Planner ESU's can usually be applied more often - since a Planner ESU updates objects that do not necessarily impact production code (although it HAS been known to happen) - as do Tools Releases.

Therefore here is your recommended 10 steps :

1. Installation
2. Implement all Fix Current ESU's
3. Start testing/rolling out
4. During this phase, continue to implement fix-current ESU's and promote these into production through the development cycle
5. User acceptance testing / Go-live
6. Now freeze as much development as possible (after all, the system is being rolled out - so everything should be working at this point)
7. Apply Tools Releases to keep v-3 (3 releases back from current) current (apply about once every 6 months or so). Apply OS updates/patches and other software changes only when/if necessary.
8. Apply ESU if there is a bug - promote like any other development (install to DV and promote)
9. Apply Baseline ESU (Update) only if ESU requires it from step (8). This will trigger off a smaller "upgrade" project
10. Apply upgrades only if there is business justification. This will trigger off an actual upgrade project
 
Re: How often does your organization apply ESU\'s to stay fix current?

This is good information, thanks everyone who participated and responded.
cool.gif
 
Back
Top