LEARNING OBJECTIVES
LEARNING OBJECTIVES
The three most common types of SAP system updates.
The signifcance of enhancements.
Upgrade and enhancement terminology.
Diferences between technical and functional upgrades.
Avoiding confusing upgrades and migrations.
Upgrade proect re!uirements.
TYPES OF SAP UPDATES
TYPES OF SAP UPDATES
"ost SAP systems after they#ve fnally
gone live are updated monthly or !uarterly
in one way or another.
1. Enhancements
2. Upgrades
3. Technology stack updates
SETTING THE STAGE:
MAKING
CHANGES TO SAP
SETTING THE STAGE:
MAKING
CHANGES TO SAP
The SAP and infrastructure technical teams update
the technology stac$ on a fairly regular basis% for
e&le'
(. Server system boards and dis$ controllers re!uire
frmware updates every now and then to f& bugs
or support new hardware options.
). *ew and faster networ$ cards% dis$ controllers%
dis$ drives% and so on are updated every few
years.
+. ,perating systems and database software
re!uire patches and other updates in response to
bug f&es or to protect against virus and other
potential threats.
SETTING THE STAGE:
MAKING
CHANGES TO SAP
SETTING THE STAGE:
MAKING
CHANGES TO SAP
-eyond technology updates% the various business teams put in
re!uests to change or add business functionality'
(. The fnance team might need updates made in SAP Enterprise
Resource Plannings (ERPs) inance module to adhere to a
ne! accounting principle or to help close the monthly boo$s
faster.
). .n response to new federal and state regulations% the logistics
team might re!uest updates in how international trade is
conducted or accounted for.
+. A power user in the warehouse group might see$ to ma$e
several updates in a transaction#s screen layout to ma$e it
easier for new hires to manage inventory and storage
locations
ENHANCEMENT
ENHANCEMENT
In general, SAP enan!e"en#$ are "%&'(!a#'%n$
%r )*&a#e$ #% e+'$#'ng SAP $,$#e"$
In general, SAP enan!e"en#$ are "%&'(!a#'%n$
%r )*&a#e$ #% e+'$#'ng SAP $,$#e"$
Enan!e"en#$ !an -e SAP.&r'/en %r !)$#%"er.
&r'/en
Enan!e"en#$ !an -e SAP.&r'/en %r !)$#%"er.
&r'/en
Enan!e"en#$ !an al$% -e &el'/ere& #r%)g
$*e!'(! SAP EHP$0
Enan!e"en#$ !an al$% -e &el'/ere& #r%)g
$*e!'(! SAP EHP$0
UPGRADE TERMINOLOGY
UPGRADE TERMINOLOGY
SAP )*gra&e reall, "ean$ )*gra&'ng SAP
'#$el10
SAP )*gra&e reall, "ean$ )*gra&'ng SAP
'#$el10
Te #e!n'!al #ea" $*ea2 %1 *er1%r"'ng an
SAP #e!n'!al )*gra&e0
Te #e!n'!al #ea" $*ea2 %1 *er1%r"'ng an
SAP #e!n'!al )*gra&e0
UPGRADES ARE NOT MIGRATIONS
UPGRADES ARE NOT MIGRATIONS
SAP OS3DB MIGRATIONS
SAP OS3DB MIGRATIONS
An SAP ,S/D- migration may be conducted to
change platforms between diferent 0avors of U*.1%
2inu&% and 3indows.
4eterogeneous system copy is also used to
describe an ,S/D- migration.
5ustomers e&ecute ,S/D- migrations for a few
diferent reasons. ,ne of the primary reasons is
cost.
MORE ON SAP UPGRADES
MORE ON SAP UPGRADES
6easons for upgrading SAP are'
(. 5ompany needs the new functionality
ofered in the newest release.
). 5ustomers upgrade.
[Link] PROJECT
PLANNING
[Link] PROJECT
PLANNING
Planning for upgrade and enhancements is
critical due to the magnitude of change and
ris$.
The most important matter is to minimi7e
the ris$ of downtime whether it#s a hardware
update% ,S/D- migration or functional
upgrade.
PROJECT PLANNING FOR
ENHANCEMENTS
PROJECT PLANNING FOR
ENHANCEMENTS
8nhancements are often implemented in !uarterly waves or
phases comprising multiple SAP user groups and therefore
multiple functional areas and business processes.
4)ar#erl, )*&a#e$ al$% 'n!l)&e$ %ne %r all %1 #e
1%ll%5'ng )*&a#e$:
Server% dis$ subsystem% or other infrastructure refreshes
Database patches updates and 9upgrades:
,perating system updates% security patches% and 9upgrades:
SAP $ernel updates
SAP support pac$age stac$ ;A-AP and <ava= updates
SAP modifcation transports
5ustomer transports
PROJECT PLANNING FOR
SAP UPGRADES
PROJECT PLANNING FOR
SAP UPGRADES
Technical upgrades are more common and are pretty
fre!uent% occurring every si& months.
Upgrading re!uires si& months of planning
>ollowing are the necessary components for SAP
upgrades'
(. SAP infrastructure support fol$s.
). SAP basis professionals
+. A-AP programmers.
GETTING STARTED
GETTING STARTED
3hen the new SAP infrastructure is in place% a
system copy must occur from one of the source
SAP systems to the new environment.
Typically% a copy of production is used as the
source for the frst test upgrade.
Some customers prefer to start with an upgrade
of the development environment% but this choice
complicates things
UPGRADE TOOLS AND OPTIONS
UPGRADE TOOLS AND OPTIONS
T3, SAP T,,2S US8D -? SAP -AS.S P6,>>8SS.,*A2S
UPGRADE TESTING AND REMEDIATION
UPGRADE TESTING AND REMEDIATION
A1#er )*gra&e, $,$#e" '$ an&e& %/er #% 1)n!#'%nal an& ABAP #ea"$
