3.1Upgrade in an SAP System Group NoteThis section is only
relevant if you perform a release upgrade.If you have more than one
SAP system, for example, a production system, a quality assurance
system, and a development system, you have to consider the entire
system group.Upgrade your systems in the same sequence in which you
transport your modifications.In addition, the upgrade influences
the development activities, for example, dual maintenance might be
temporarily necessary to ensure that your production system is
supported with emergency corrections.ProcessSequence of
UpgradesUpdate of SAP Systems Using Software Update Manager 1.0
SP11PlanningCUSTOMER Copyright 2014 SAP AG.All rights reserved.27If
your system group consists of three SAP systems and includes a
quality assurance system that has been set up between the
development and production system, work in the following
order:1.Development system2.Quality assurance system3.Production
systemIf you have made modifications to SAP objects that you want
to retain, you have to proceed in the above sequence. The version
management functions of the SAP system record all the changes you
make only in the system in which you made the modifications (the
development system). Only this SAP system offers you optimal
support when you adjust modifications.Changes made in the
development system after the upgrade can be transported
automatically to your other SAP systems. If you use this procedure,
you no longer need to perform time-consuming adjustments in the
production system. CautionIf you have modified SAP objects, make
sure that you keep your development system. Do not copy your
production system to your development system for test
purposes.Impact on DevelopmentAt a certain point in time during the
upgrade, the development environment of the system that is upgraded
is locked. Consider this development freeze in your project plan
and inform your developers about it.To avoid the development system
being unavailable during the upgrade, we recommend that you add a
temporary copy of your development system to your system landscape.
This temporary development system can supply your production system
with emergency corrections or support a phased development go-live
after you have upgraded the original development system. You then
have to make any corrections in the original development system as
well as in the temporary development system. Make sure that your
developers are notified about the dual maintenance.O sDX7D*,#{k
DintenanceBack to Quick Guide [page 17]28CUSTOMER Copyright 2014
SAP AG.All rights reserved.Update of SAP Systems Using Software
Update Manager 1.0 SP11Planning3.2Updates in an SAP System Group
NoteThis section is relevant if you perform an enhancement package
installation or SPS update.If you have an SAP system group
consisting, for example, of a production system, a quality
assurance system, and a development system, you have to consider
the entire system group regarding the sequence of updates.In
addition, the update procedure influences the development
activities, for example, dual maintenance might be temporarily
necessary to ensure that your production system is supported with
emergency corrections.ProcedureSequence of UpdatesUpdate your
systems in the same sequence in which you transport your
modifications. Update each system with the same software
packages.If your system group consists of three SAP systems and
includes a quality assurance system that has been set up between
the development and production system, work in the following
order:1.Development system2.Quality assurance system3.Production
system RecommendationWe strongly recommend that you perform
transports only between systems of the same release or enhancement
package level, and where the same business functions are activated.
If you do not follow this recommendation, you do so at your own
risk regarding potential problems.If you have made modifications to
SAP objects that you want to retain, you have to proceed in the
above sequence. The version management functions of the SAP system
record all the changes you make only in the system in which you
made the modifications (the development system). Only this SAP
system offers you optimal support when you adjust
modifications.Changes made in the development system after the
update can be transported automatically to your other SAP systems.
If you use this procedure, you no longer need to perform
time-consuming adjustments in the production system. CautionIf you
have modified SAP objects, make sure that you keep your development
system. Do not copy your production system to your development
system for test purposes.Impact on DevelopmentAt a certain point in
time during the update procedure, the development environment of
the system that is updated is locked. Consider this development
freeze in your project plan
