Skip to Content

Dual landscape for EhP5 update?

Hello all -

Background:

We are considering EhP5 in our environment. One of concern points I have relates to that for our previous EhP updates (first #2 and #4) we only activated Business Functions that led to SAP_HR and EA_HR to be updated to 604. The Central Applications were never selected, to the core financial/logistics (SAP_APPL) is still on 600. Since then we've had some needs for business functions that require this.

While I'd love to believe that EhP only bring new/good things, I think the reality is that moving from 600->605 is enough of a change to at least "be concerned about" in terms of potential for issues/etc.

FYI - our production environment is extremely large, so making a system copy to QAS is a big challenge (technically and financially).

Questions:

Many years ago (before EhP) I would go with a dual landscape approach for upgrades (e.g. make a copy of DEV/QAS and then require folks to manually retrofit their prod support changes into the project landscape). Is anyone out there following similar approaches for EhP?

Or are the majority of shops accepting that you can effectively support production issues even though your DEV/QAS systems are updated already? That certainly minimizes the workload, but does it mitigate the risk.

Thanks for any input you have!

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Jul 18, 2011 at 06:11 PM

    Hello all -

    >

    > Background:

    > We are considering EhP5 in our environment. One of concern points I have relates to that for our previous EhP updates >(first #2 and #4) we only activated Business Functions that led to SAP_HR and EA_HR to be updated to 604. The Central >Applications were never selected, to the core financial/logistics (SAP_APPL) is still on 600. Since then we've had some >needs for business functions that require this.

    >

    First of all system cannot be on EHP4 without SAP_APPL and EA-APPL. If a system is on EHP4 then central application i.e. SAP_APPL and EA-APPL must be on 604 version.

    > Questions:

    > Many years ago (before EhP) I would go with a dual landscape approach for upgrades (e.g. make a copy of DEV/QAS and >then require folks to manually retrofit their prod support changes into the project landscape). Is anyone out there following >similar approaches for EhP?

    >

    Yes, if you want you follow dual landscape stratgey to carry out urgent changes. But make sure that you replicate those changes to your upgraded dev/QAS system as well manually. Same has been explained in the upgrade guide as well.

    Thanks

    Sunny

    Add a comment
    10|10000 characters needed characters exceeded

    • I am fairly certain it is possible/suported to have SAP_APPL at 600, with HR at 604 based on the business functions activated. Specficially I think it is the 'cross application' that drives updating SAP_APPL.

      I haven't yet made it to the upgrade guide - am a bit curious about what folks in the 'real world' are doing!

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.