Managing Efficient Upgrades

LCM200
Managing efficient
U d Upgrades
Upgrade to SAP ERP6 0 Upgrade to SAP ERP6.0
Disclaimer
This presentation outlines our general product direction and should
not be relied on in making a purchase decision. This presentation is
not subject to your license agreement or any other agreement with
SAP. SAP has no obligation to pursue any course of business
outlined in this presentation or to develop or release any outlined in this presentation or to develop or release any
functionality mentioned in this presentation. This presentation and
SAP's strategy and possible future developments are subject to
change and may be changed by SAP at any time for any reason
without notice. This document is provided without a warranty of any
kind either express or implied including but not limited to the kind, either express or implied, including but not limited to, the
implied warranties of merchantability, fitness for a particular
purpose, or non-infringement. SAP assumes no responsibility for
errors or omissions in this document, except if such damages were
caused by SAP intentionally or grossly negligent.
SAP AG 2007, SAP TechEd 07 / LCM200 / 2
Contributing Speakers
Roland Hamm
Product Manager Product Manager,
SAP NetWeaver PM, SAP AG
Bettina Schumer
Global Upgrade Office, pg
UCC EMEA, SAP AG
Session handouts as PDF download from the conference site!
In attempt to reduce
waste and save the
life of a significant
number of trees
SAP TechEd no
longer provides
printed handouts for
LECTURE Sessions
(handouts for
h d i hands-on session
will be still
available).
Use your personal
Agenda Builder
on the conference
website to
download the
session handout
as PDF!
Improving the technical upgrade
System Switch Upgrade Technology
Upgrading Systems based on AS ABAP, AS Java & Dual Stack Upgrade
Unicode Upgrade
Customer based Upgrade
Upgrading ERP Business Scenarios
H SAP ERP A hi i U d SAP S l i M & SAP
SAP ERP Upgrade Experiences Summary
E i f Ti & T i k
How SAP ERP Architecture impacts Upgrade, SAP Solution Manager & SAP
Software Lifecycle Manager (SLM)
Experience so far, Tips & Tricks
Managing Upgrade Projects
Upgrade Offerings
Further Information
Summary & Questions
Learning Objectives
As a result of this workshop, you will be able to:
Understand the principles of the technical upgrade process Understand the principles of the technical upgrade process
(ABAP, Java and Dual Stack)
Know measures to optimize the technical upgrade
Know how to efficiently plan upgrades of whole SAP solutions y p pg
Know additional tools to manage your upgrade project
Be familiar with SAPs Upgrade Service Offerings
Know where to retrieve comprehensive information to perform p p
upgrade projects
System Switch Upgrade Technology y pg gy
Upgrading Systems based on AS ABAP
Upgrading Systems based on AS Java
Upgrading Dual Stack Systems (ABAP+Java)
Unicode Upgrade
Customer based Upgrade Customer based Upgrade
Improvements in Upgrade Technology
Goals:
Allow reliable Planning of Technical Upgrade Execution
U tt d d ti / A t ti Unattended operation / Automation
Usability improvements
Reduction of technical downtime
Though complexity of software increases and number of to be shipped objects
raise, system outage times caused by software maintenance action could been
reduced by tool and process optimization.
New Patch Integration SAP
CBU Toolset Available
System Switch Upgrade
since
SAP
WebAS
New Patch Integration
New SGEN (faster & optimized selection)
Parallel Activation
Parallel DDL Execution
Parallel Customizing Import
Parallel Language Import
N t bl t d filli i U ti
SAP
Basis
SAP
Basis
4.6C
SR1/SR
2
6.10
Integration of Support Packages & Add-Ons into Shadow
Tables (~10% - 50%)
Incremental Data Conversion ICNV (~0% - 30%)
New table create and filling in Uptime
(~ 30% - 40%)
SAP
SAP
Basis
4.6B
Basis
4.6C
2
Remark: Most SAP Software
Maintenance actions, i.e.
d t i t d b
SAP
Optimization of Repository Switch
Integration of Support Packages into Upgrade
SAP
Basis
4.0
Basis
4.5
upgrades, are not impacted by
the pure database size, but by
the number of SAP objects to
be changed )
Basis
3.0D
Introduction of Repository Switch (~30%)
be changed.)
Release Upgrade Requires Adaption of Current Applications
Organize application adjustment process efficiently
Adjust modifications of SAP-owned workbench and DDIC objects
Id tif dj t t i t i SAP t d d bj t Identify necessary adjustments in custom programs using SAP standard objects
Understand needs for customizing adoptions and adjustments of business processes
Check and adopt interfaces
Modifications Customer
Development p
Extension
What Has the Upgrade as Tool to Care About?
Data
Consistency of
data &
General
data &
automatic Data
conversion
General
Customer Data
Customizing
Reports
Save Customer N
Domains
Reports
T bl
Documentation
Function
Modules
Repository
Save Customer
Objects
Allow Adjustment
New
Repository
Tables
Views
Dynpros
Modules
Data
Elements
Messages
Allow Adjustment
of conflicting
Objects
(SPDD/SPAU)
(SPDD/SPAU)
The System Switch Upgrade Principle
Production Instance 4.6C <NR> Shadow Instance 7.00 <NR+1>
ABAP 46C ABAP 700
Kernel 46C
Kernel 700
Kernel 46C
dbsl
Kernel 700
dbsl dbsl dbsl
TABLE~, 700
TABLE, 46C
View
46C
View
700
TABLE, 700
DB: SID DB: SID , sapr3 SID~, sapr3shd
productive
,
,
shadow
,
, p , p
System Switch Upgrade: Timing Diagram
e

e
)
Production Downtime
resource-minimized
n
s
t
a
n
c
e
r
e
l
e
a
s
e
n
n k
s
so
n

n
t
t
r
o
l

D
a
t
a

a
b
l
e
s
S
e
tProduction Downtime
downtime-minimized
h
a
d
o
w

I
n

t
a
r
g
e
t

A
c
t
i
v
a
t
i
o
n
i
s
t
r
i
b
u
t
i
o
p
p
o
r
t

P
a
c
A
d
d
-
O
n
s
o
d
i
f
i
c
a
t
i
o
d
j
u
s
t
m
e
n
r
t

o
f

C
o
n
t
n

C
o
p
y

T
a
I
C
N
V
I
m
p
o
r
t

o
f

b
s
t
i
t
u
t
i
o
n

Inst.
S
h
(
o
n
A
D
S
u
p
M
o
A
d
I
m
p
o
r
i
n
I
I
S
u
b
Upgrade
p
t
i
m
e
PREPARE Upgrade
New
Rel.
downtime-minimized a
c
k
u
p
U
m
e
p
Rel.
Imp
u
p
B
D
o
w
n
t
i
m
resource-
minimized
B
a
c
k
u
p
Upgrade
post
Imp.
B
a
c
k
u
D
Stop of
Production
(strategy-dep.)
pg
Downtime With System Switch Upgrade
Binding Support Packages to the upgrade does not impact
significantly the downtime of the upgrade process !
= Uptime !
System Switch
Upgrade
Technology
Package
count:
32 32
16
8
With t Without
packages
1h
DDIC ACT PCON TABIM XPRA Misc.
Uptime!
Resource optimized Downtime optimized
Two Upgrade Strategies
Resource optimized
Temporary SAP Web AS is used, when
central instance is down.
No additional resources are needed
Downtime optimized
Temporary SAP Web AS is used in
parallel to central instance
More resources are needed No additional resources are needed More resources are needed
(CPU/Memory)
Dowtimes 4.x to SAP R/3 Enterprise Same upgrades with "downtime minimized" method
50
5
10
15
20
u
s
t
o
m
e
r
s

i
n

%
10
20
30
40
50
C
u
s
t
o
m
e
r
s

i
n

%
0
5
0
-
2
4
-
6
8
-
1
0
1
2
-
1
4
1
6
-
1
8
2
0
-
2
2
2
4
-
2
6
2
8
-
3
0
3
2
-
3
4
3
6
-
3
8
4
0
-
4
2
4
4
-
4
6
4
8
-
5
0
5
2
-
5
4
Hours
C
u
Avg ~18
0
10
0
-
2
4
-
6
8
-
1
0
1
2
-
1
4
1
6
-
1
8
2
0
-
2
2
2
4
-
2
6
2
8
-
3
0
3
2
-
3
4
3
6
-
3
8
4
0
-
4
2
4
4
-
4
6
4
8
-
5
0
5
2
-
5
4
Hours
C
Avg ~8
downtime-
minimized
resource-
minimized
EU_IMP0
Avg.~18 Avg.~8
EU_IMPORT
ACT
DIST...
START_SHDI
STOP_SHDI
PRD SHD
MODPROF_T SHD_IMP
XCNV
PARCONV
TABIM
XPRA MODPROF_P
Remote Shadow Instance Option
Configuration with g
Central instance
and remote
DB
DB server
shadow instance
sapr3
sapr3shd
R3up
MS
DW
MS
DW
S
Central instance 4.6x Shadow instance 7.00
/usr/sap/put /usr/sap/put NFS
share
Unicode Upgrade
New Features of the ABAP Upgrade I
New Upgrade Assistant
New GUI using SDT framework
Unified GUI look and feel for all Unified GUI look and feel for all
Software Lifecycle Management tools
SAPinst (incl. System Copy)
J S P k M Java Support Package Manager
Java Upgrade Management Tool
R3up renamed to SAPup R3up renamed to SAPup
Log files are renamed accordingly
S t d St t R l Supported Start Releases
SAP Systems based on following
releases:
R/3 3.1I and higher
Products based on SAP BASIS
4.6D, for instance, APO 3.10
SAP Web AS ABAP 6.10 and higher
Web UI
Web UI
for ABAP
New Features of the ABAP Upgrade II
Improved usability for including additional packages into upgrade
Wizard based all decisions on one screen Wizard based, all decisions on one screen
Allows changes to decisions without restart of Prepare Phase
Reduced downtime through parallel import of software packages (shadow Reduced downtime through parallel import of software packages (shadow
import and main import)
I d fi k t Improved fixpack concept
Includes improvements and error corrections to upgrade tool/F1-help, keeps your upgrade to
latest state latest state
Support for Switch framework
SAPup migrates former IS-Add-ons into Switch Framework technology
Support for Unicode Conversion
Available for upgrading from R/3 4.6C to ERP 6.0
Outlook: Planned with ERP 6.0 Support Release 3
One-step upgrade including the Enhancement Package
Enable the upgrade from lower releases to include the selected EhP pg
components
No intermediate state which is not desired
Shorter downtime: no intermediate uptime which cannot be used productively Shorter downtime: no intermediate uptime which cannot be used productively
Shorter runtime, less risks to make errors or to fail
Lower project costs
Simplified Handling
The desired target configuration is computed out of the selection of the
user in the Maintenance Optimizer
EhP component versions computed out of selected business functions and EhP component versions computed out of selected business functions and
start release component versions
SP stack level / SP level: the support package level of the participating
components (EhP, std ERP, NW) ( )
The upgrade can read the configuration and skip configuration dialogs
Unicode Upgrade
I l U d E d t t h dli t i t
Deployment-Based Upgrade Features
In-place Upgrade
Start release: NetWeaver 2004 SR1/SPS09
Generic procedure applicable for all SAP
Error and restart handling at any point
Two major units:
PREPARE
Generic procedure applicable for all SAP
Applications based on NW2004 onwards UPGRADE
Including the latest Support
Package Stack
NW04s
Applications
Deploy
Package Stack
Preserve Customer Data
Migrate J2EE Engine
Binaries
J2EE Engine
Components
SAPJup
Configure
Deploy
Migrate J2EE Engine
configurations
Preserve application data and
configurations
NW04
a es
Profiles &
scripts
configurations
Upgrade Modified Components
Archives, containing new releases
Applications
J2EE Engine
Components
Migrate
Migrate
g
of modified and third-party
components, can be selected and
deployed by SAPJup
Binaries
Profiles &
Components
Adapt
Adapt
Synchronized upgrade of double-
stack systems
Profiles &
scripts
Adapt
Preparation
Preparation steps are performed during the system uptime
The PREPARE phases include following major tasks: The PREPARE phases include following major tasks:
Investigating the source system
Performing various parameter and profile checks
Determining Usages Types to be upgraded
Extracting upgrade DVDs
Including Support Packages Including Support Packages
Including custom development components
Calculating the deployment lists and order
Upgrade
The UPGRAGE phases are mainly performed during the downtime
It includes following major steps: It includes following major steps:
Stopping the system
Disabling the current user store of the UME to ensure that SAP* is the only
user who can access the system during the downtime
Updating the kernel, SAP MMC (Windows only), IGS and SDM
Undeploying and deploying SLOT1 (file system deployment) Undeploying and deploying SLOT1 (file system deployment)
Undeploying and deploying SLOT2 (database deployment)
Updating the engine bootstrap and adapting profiles
Undeploying and deploying SLOT3 (offline deployment)
Migrating engine core data (Java Migration Toolkit)
Starting the system in Safe mode Starting the system in Safe mode
Undeploying and deploying SLOT4 (online deployment)
Running application migration (application migration container)
Stopping the system
Re-enabling the original user store of the UME
Starting the system
Starting the system
Uptime And Downtime
Upgrade Uptime
Uptime is the time when the J2EE Engine is up and running. Its still
productive, in use and untouched by the upgrade procedure
Whole PREPARE unit runs in Uptime
Reconfiguring J2EE Engine is not allowed during the Uptime Reconfiguring J2EE Engine is not allowed during the Uptime
Upgrade can be stopped and cancelled during the Uptime
Upgrade downtime
Downtime is the time when the J2EE Engine is being modified and controlled
by the upgrade procedure by t e upg ade p ocedu e
The system is not productive
Even when the system is up it cant be used. Upgrade starts the J2EE
Engine in SAFE mode during DEPLOY ONLINE and Engine in SAFE mode during DEPLOY_ONLINE and
RUN_APPLICATION_MIGRATION phases.
The only active user is SAP* and it should not be changed during the
downtime downtime
Handling of Usage Types & Development Components
Mapping of Usage Types
Determining installed scenarios in the start system on the basis of Determining installed scenarios in the start system on the basis of
significant components
Presence of BI and MI must be confirmed by user
Mapping the installed scenarios on NW04 to usage types of NW04s
Upgraded system hosts the same usage types as the source system
N ti t i t ll dditi l t No option to install additional usage types
If a usage type has been detected, all usage types it depends on in NW04s will
be deployed to the system, e.g. on a NW04 BI system, both BI and EP will be
deployed during the upgrade (because BI depends on EP in NW04s)
Renamed Development Components
Un-deploying the old development components
Deploying the new development components
Issue due to un-deployment of components:
Loss of application configurations like security settings, logging
configuration
configuration
Unicode Upgrade
Architecture Overview
SDT GUI User
SDT GUI User
SDT Server SDT Server
J2EE ABAP
ICM
disp disp
server work
J2EE Upgrade Tool Set
ABAP Upgrade Tool Set
SDM tp
pg
SAPJup
J2EE ABAP
JMT
DMT
SAPup R3trans
R3load
D t b
Persistent
Data
File System CD Data
Persistent
Data
CD Data
DMT R3load
Database
Data Data
Synchronized Upgrade of ABAP and Java Stack
Reduce the overall downtime:
Both stacks start and end the downtime phases at same time
Handle common resources correctly:
for instance, system profiles and profile entries are shared by ABAP and Java stack y p p y
Upgrading (PREPARE and UPGRADE) ABAP and Java stack must
be performed in parallel with following sync points: be performed in parallel with following sync points:
At the beginning of the downtime
Wh th fil i t b difi d When the profiles are going to be modified
At the end of the downtime
If AS JAVA i t th l ti t t d AS J i t d i t ll it l t t t th If AS-JAVA is present, the only option not to upgrade AS Java is to de-install it latest at the
PREPARE Dialog REQ_J2EE.
Except for the sync points the upgrade processes of both stacks Except for the sync points, the upgrade processes of both stacks
are performed independently
Detection of Double-Stack
If AS JAVA has been detected, the only option
not to upgrade AS Java is to de-install AS Java
latest at the PREPARE Dialog REQ J2EE ! latest at the PREPARE Dialog REQ_J2EE !
Sync Points
End of Downtime
Changing Profiles
Beginning of Downtime
Starting Java System Manually During the Upgrade
Java stack is decoupled from the ABAP stack
In some problem cases, restart of the Java stack is necessary In some problem cases, restart of the Java stack is necessary
Impossible to start the Java stack from ABAP using the transaction
smicm
<jup_dir>/exe/jcontrol -DSAPSTART=1
pf=/usr/sap/<SID>/SYS/profile/<instance profile>
New Dual Stack Upgrade for SAP NetWeaver PI 7.1 (1)
New Upgrade Phase and
Structuring Model: Structuring Model:
ABAP & Java Upgrade pg
Steps merged into ONE
process !
One common UI !
New Upgrade Phase and
Structuring Model:
ABAP & Java Upgrade
Steps merged into ONE Steps merged into ONE
process !
One common UI !
Binding Support Binding Support
Packages &
Patches into
Upgrade
Switch Upgrade Switch Upgrade
Technology for AS
JAVA, too ! ,
Unicode Upgrade
Integrated Unicode Conversion With Upgrade
On SAP R/3, especially 4.6C many customers use MDMP systems.
Starting with SAP ERP 6.0, MDMP will not be supported any longer.
Customers can not upgrade their MDMP systems to ERP 6.0.
In case they do, they will be prompted during the Upgrade to sign a y , y p p g pg g
disclaimer.
Solution:
The Combined Upgrade & Unicode Conversion enables
customers to perform both procedures in one! customers to perform both procedures in one!
Transaction SPUMG for Unicode pre-conversion down-ported to
R/3 4 6c R/3 4.6c
Down-port to lower releases currently unavailable
MDMP systems and systems with Blended Code Page must be MDMP systems and systems with Blended Code Page must be
converted to Unicode
Procedure Integration Schematically
Upgrade
Uptime Downtime
Unicode Conversion
Sequentially:
Uptime Downtime
t
Downtime of complete procedure
Optimized Preparation:
Uptime Downtime
Uptime Downtime
t
Downtime of complete procedure
speed up
Prepare Unicode conversion partially in source system before the upgrade
Unicode conversion includes two subsequent steps: Preparation during the
uptime and conversion during the downtime.
Some consistency checks and conversion preparations can be performed in the
source system or in the upgrade shadow system.
y pg y
Integration: Optimized Preparation
The preparation for Unicode conversion is (partially) already done
during the upgrade uptime on the start release.
Advantages Disadvantages
MDMP Unicode conversion can The Unicode conversion relies on
be prepared on the source release,
this can reduce the time the system
is on ERP 05 with MDMP by several
k
an error-free upgrade.
System is not tested between the
upgrade and conversion:
weeks.
The downtime of the combined
procedure can be reduced by
upgrade and conversion:
identifying errors more difficult.
The combined project is more
procedure can be reduced by
several hours.
Upgrade and conversion steps
p j
complex.
mainly executed separately.
The procedure is integrated,
customers with MDMP are guided to customers with MDMP are guided to
a functional ERP 6.0.
Procedure of Unicode Conversion: Before Actual Upgrade
PREPARE
UCMIG DECISION (Module Initialization) UCMIG_DECISION (Module Initialization)
MDMP or BCP System Unicode Migration required
SCP System Unicode Migration possible
TOOLIMP4_UCMIG (Module Import)
Import the transaction SPUMG to 46C system
UCMIG_STATUS_SET0 (Module Import)
Initialization of status table UM4STATUS
Status 0 (initialized)
Preparation for Unicode conversion in source system Preparation for Unicode conversion in source system
Transaction SPUMG
Must to be completed when the Shadow System starts Must to be completed when the Shadow System starts
Sets status to 1 (complete)
Procedure of Unicode Conversion: During Actual Upgrade
UPGRADE: Uptime
UCMIG STATUS CHK1 UCMIG_STATUS_CHK1
Check status of the transaction SPUMG
Warning, if preparation steps have not been completed
UCMIG_STATUS_CHK21/22/23 (depending on upgrade strategy)
Check status of the transaction SPUMG
Error, if preparation steps have not been completed
UPGRADE: Shadow System y
No manual interaction required
Get more Information on the UNICODE matter in the following
TechEd Sessions:
- LCM211: Conversion of MDMP Systems to Unicode
- LCM262: Making programs Unicode enabled
Unicode Upgrade
Further Reduction of Overall Technical Downtime
Upgrade Downtime includes:
Technical Upgrade Runtime (R3up)
Modification Adjustments (SPDD/SPAU)
Add-on upgrades Support Packages Language Update
Import of Customer
Transport Requests after
Upgrade
(contains Repository & Add on upgrades, Support Packages, Language Update
bind of single change requests
(contains Repository &
Customizing objects)
Uptime
i
e
n
t
r
o
s
s
-
c
l
c
c
c
l
i
e
n
t
-
s
p
e
c
i
f
i
c
DDIC ACT PCON TABIM XPRA rest Imports after
p
Upgrade
Customer Based Upgrade: Process
Production Production
P@4.6 P@4.6 P@6.0 P@4.6
Production Production
CBU
copy copy
CBU CBU
Re Re--package package
upgrade upgrade
copy copy
Support Packages
Addon Installation/Upgrade
Package
pg
Customer development
Modification adjustment
C@4.6 C@6.0
upgrade upgrade
C@4.6 C@6.0
SAP
U d
test test upgrade upgrade
Upgrade
Summary: Customer Based Upgrade
Uptime
Inclusion of additional packages
Add-on installations (SAINT)
e
n
t
Add-on upgrades (SAINT)
Support Packages
Add-on patches, CRTs
c
r
o
s
s
-
c
l
i
e
t
-
c
i
f
i
c
p ,
No modification adjustments
No transports after upgrade except for
c
l
i
e
n
s
p
e
cNo transports after upgrade except for
customizing
Reductions in application adjustment
DDIC ACT PCON TABIM XPRA rest Imports after
Upgrade
Customer Based Upgrade for upgrading to SAP ERP
pp j
Accurate timing on production upgrade
Upgrade to target release including customer defined number of support packages, modification
adjustments, pre-generated loads, ...
Repackaging large number of post-upgrade transport requests nad bind them as single change
request into shadow import phase of upgrade (uptime!)
Note: Customer based Upgrade (CBU) is a Consulting Service delivered by SAP Technical
Consulting only; with direct Backoffice support of upgrade development team.
Unicode Upgrade
H SAP ERP A hi i U d
E i f Ti & T i k
How SAP ERP Architecture impacts Upgrade
SAP Solution Manager & SAP Software Lifecycle Manager (SLM)
Upgrade Offerings
Further Information
Summary & Questions
Evolution of SAP ERP Architecture
o
n
SAP ERP 6.0
Self-Services
Supplier Relationship Management
p
l
i
c
a
t
i
o
Composite Applications
Self Services
Internet Sales
and more
A
p
SAP R/3
SAP R/3 Enterprise
Strategic Enterprise Management Industry Solutions
Switch Framework Switch Framework
Enterprise Extensions Industry Extensions
Industry Sol.
SAP Enterprise
Extension Set
EhP 1
EhP 2
SAP Web
Application Server 6 20
SAP Basis
up to 4.6C
Application
SAP NetWeaver 04s
SAP ECC Core (6.0)
SAP R/3
Enterprise Core (4.70)
Extension Set
Application Server 6.20
o
g
y
n

F
r
a
m
e
w
o
r
k
L
i
f
e
PEOPLE INTEGRATION
Multi Channel Access
Portal Collaboration
INFORMATION INTEGRATION
e
c
h
n
o
l
o
e

A
p
p
l
i
c
a
t
i
o
n
e

C
y
c
l
e

M
g
m
t
Master Data Mgmt
Bus. Intelligence Knowledge Mgmt
PROCESS INTEGRATION
Integration
Broker
Business
Process Mgmt
T
e
C
o
m
p
o
s
i
t
APPLICATION PLATFORM (7.00)
t g
J2EE
ABAP
DB and OS Abstraction
ITS
Java Components Additional
Components
ABAP
Components
Java Web
Applications
SAP ECC
IS H 600
IS-CWM 600
INSURANCE 600
EA GLTRADE 600
EA-FINSERV 600
EA-APPL 600
SAP Solution
Manager
Software Components of an
SAP ECC 6.0 system
BILLER DIRECT 6.0
LSO (CP) 600
IS-PS-CA 600
IS-OIL 600
IS-M 600
IS-H 600
EA-PS 600
EA-IPPE 400
EA-HR 600
EA-GLTRADE 600
Front End
after a techn. Upgrade
SAP XSS 6.0
XECO 5.0
SAP HR 600
SAP-APPL 600
SAP AP 7.0
IS-UT 600
FI CA 600
ES-DFPS 600
ECC-DIMP 600
EA-RETAIL 600
cProject ECL
Vi 5 1 2
LSO (AE) 600
LSO (OP) 600
SEM 600
LSO (FE) 600
ST PI
SAP-HR 600
FINBASIS 600
E-Recruiting 6.0
FI-CAX 600
FI-CA 600
Viewer 5.1.2
SAP Easy Document
OpenPS for MS
Project 2.02
EP Content
Business Packages
Add Ons ABAP included in installation SAP ECC
Add Ons ABAP
E R iti 6 0
BI Content
y
Management 6.0
SEM Frontend
SAP GUI 6.20/6.40
XI Content
SEM 600
LSO (FE) 600
FINBASIS 600
E-Recruiting 6.0
BI Content 7.0
SAP SRM
SEM Frontend
Components
BI/BW Frontend
Components
XI Content for
Applications
ELSTER 2.0
WFMCORE 2.0
SAP CATALOG 2.0
cPROJECT SUITE 4.0
SEM 600
SAP SRM
SAP SRM 5.5 Server
SAP NetWeaver 7.0
WFMCORE 2.0
Upgrade to SAP ECC 6.0 (part of SAP ERP 6.0) from..
SAP ERP 6 0
SAP IS-U/FERC
SAP LEARNING SOLUTION
SAP ECC DIMP
Industry add-ons integrated into
SAP ECC 6.0 (see SAP Note 838003)
Non industry add-ons integrated into
SAP ECC 6.0 (see SAP Note 838002)
SAP ERP 6.0
SAP XECO
SAP XSS
SAP SEM
SAP ECC
Target
SAP IS-CWM
471
463
461
SAP EH&S
2.00
5.0
SAP DIMP
4 6C2
SAP DI
SAP IS-PS-FM
SAP VADM SAP IS-U/CCS
6.0
SAP ECC
2.0
3.0B
SAP IS-EC
SAP JVA
2.2B/2.7B/4.6C
2.2B/2.7B/4.6B
2.2B/2.7B/4.5B
S &S
3 0B
SAP IS-AD
4.71
4.6C2
4.62
4.61
4.02
3.00
2.05
472
471
464
461
4.72
SAP WASTE AND RECYCLING
4.6C
4.6B
4.5B
4.1B
4.6C1
2.0B
1 0B
SAP IS-MP
3.0B
2.0B
4 61
SAP IS-HT
2.1
1.0
SAP PLM RECIPE MANAGEMENT
4.72
4.71
SAP PUBLIC SECTOR PSCD
SAP IS-HER-CM
4.72
SAP PATIENT MANAGEMENT
1.0B 4.61
SAP IS-OIL
4.63
4.61
4.03
SAP BANKING
2.0
SAP CFM
4.64
4.72
4.71
4.64
4.62
4.61
4.52
SAP HR-PS
SAP R/3
SAP INSURANCE
4.63B
4.72
4.6C
4.6B
4.0B
4.6C
4.6B
SAP IS-MINE
47X200
47X110
SAP R/3 ENTERPRISE
472
471
SAP IS-M
4.6C
4.6B
4.5B
4.0B
SAP R/3
4.72
4.71
4.64
FS-CD
4.72
4.71
4.64
FS-CM
4.72
4.71
4.64
FS-CS
4.72
SAP FI-CA
472
471
SAP IS-T
SAP ERP 2004
5.0
SAP ECC
4.6C
SAP PH-ELR
464
402
3.1I
4.61
4.51
4.71
4.64
464
461
SAP ERP 2004
4.6C
SAP PLM ADDON
SAP ERP 6.0: Industry & Enterprise Extensions
Can Be Activated via the Switch Framework
SAP Switch Framework
SAP Discrete Industries
Industry Business
Function Sets
SAP Discrete Industries
Mill Products
SAP Media
SAP ECC
SAP ERP C t l
Only ONE
Industry Business
Function Set can be
SAP Telecommunication
SAP Oil and Gas
SAP ERP Central
Component 6.00
Function Set can be
activated via Switch
IE
..
Generic Business
Functions
Financial Services
Global Trade
SEVERAL Generic
..

..

SEVERAL Generic
Business Functions can be
activated via Switch EE
Activation of Industry and Enterprise Extensions
S i h F k Switch Framework:
Transaction SFW5
Customer Benefits of Retrofitting Industry Solutions
Timely Availability
Industry Solutions are available on the same y
schedule as the core software solution, SAP ERP 6.0
Secure Maintenance Path
Industry Solutions are part of the maintenance
strategy
Solution Enrichment
Over time Industry Solutions can be enriched by
generic functions from other industries
Reduced TCO
Reduced upgrade and maintenance costs (no more
separate handling for an add-on)
Possible consolidation of the system landscape
(hardware, interfaces, and maintenance)
Flexible Deployment Options
SAP ERP ABAP
components*
SAP ERP Java
components p p
SAP NW 7.0 usage types
AS-ABAP, AS-JAVA, EP, BI, PI, DI
EP
BI
XI
Note the use of Usage
Types -
No Components as of
SAP NetWeaver 7.0!
SAP
NW
SAP Solution
, , , , ,
BI
SAP NW 7.0
AS
SAP NetWeaver 7.0!
NW
TREX
SAP Solution
Manager
usage types AS-
ABAP, AS-JAVA, MI
Minimal landscape option:
All SAP ERP components on one logical instance of SAP NetWeaver
One Java and ABAP stack for all SAP ERP and SAP NetWeaver functionality One Java and ABAP stack for all SAP ERP and SAP NetWeaver functionality
System must be fully Unicode-compliant
Typically considered for smaller implementations
Notes
*) SAP ERP ABAP components: SAP ECC 6.0, SAP SRM Server 5.5, BI Content 7.0,
WFM CORE 2.0, SAP Catalog 2.0, cProject Suite 4.0
_ , g , j
System Landscapes Examples for SAP ERP 6.0
Minimal ERP System Landscape
SAP ERP ABAP components*
SAP ERP Java
components
Extended ERP System Landscape
SAP ERP ABAP components
components
SAP NW
Search and
Classification
SAP Solution
Manager
SAP NW 2004S usage types
AS-ABAP, AS-JAVA, EP, BI, BI-JAVA, PI, DI, MI**
EP
BI
PI
SAP FSCM Server (ABAP)
SAP SEM
SAP NW 2004s
SAP ERP JAVA
components
SAP NW 2004s usage type AS-ABAP
Notes
*) SAP ERP ABAP components: SAP ECC 6.0, SAP SRM Server 5.5, BI Content 7.0,
WFM_CORE 2.0, SAP Catalog 2.0, cProject Suite 4.0
**) See SAP Service Marketplace at service.sap.com/notes ? SAP Note 855534
(Embedded NetWeaver Components in ERP)
xx Content Package
SAP NW 2004s
usage types AS-ABAP, BI,
PI, DI, MI, AS-JAVA*
usage types
AS-JAVA, EP, BI-
JAVA
XI
BI EP
SAP NW
Search and
Classification
SAP Solution
Manager
Individual ERP System Landscape
xx Content Package
*) See SAP Service Marketplace at service.sap.com/notes ? SAP Note 855534 (Embedded NetWeaver Components in ERP)
Extended ERP System Landscape
with Firewall
SAP Catalog Content Mgmt
SAP NW 2004s
t AS ABAP
SAP SRM
SAP ERP ABAP
components
SAP NW 2004s
t AS ABAP
xx Content Package
y p
with Firewall
SAP ERP ABAP components
SAP NW 2004s usage type AS-ABAP
SAP NW
Search and
Classification
WFM_Core
SAP NW 2004s
usage type AS-ABAP
cProject Suite
LSO FE
R iti
usage type AS-ABAP usage type AS-ABAP
SAP SEM
SAP NW 2004s
usage types
AS-ABAP, BI
FSCM Server
XECO
SAP NW 2004s
usage type AS-JAVA
FSCM Biller Direct
SAP XSS (Self-
BI
SAP NW 2004s
usage types
AS-ABAP,
AS-JAVA, PI
XI
SAP FSCM Server (ABAP)
SAP NW 2004s
usage types: AS-ABAP, BI,
PI, DI, MI, AS-JAVA*
SAP SEM
SAP NW 2004s
usage types:
AS-JAVA, EP, BI-
JAVA
SAP ERP JAVA
components
BI
XI
EP
Fi ll
SAP Solution
Manager
SAP NW 2004s
usage types
AS-JAVA, DI
SAP Solution
Manager
SAP NW 2004s
usage types
AS-ABAP, BI
SAP NW 2004s
usage types
AS-ABAP, AS-JAVA
LSO CP
eRecruiting
SAP NW 2004s
AS-ABAP
SAP XSS (Self
Services)
SAP NW 2004s
usage types
AS-JAVA, EP, BI-Java
EP
BI
SAP NW
- Search and
Classification
SAP NW 2004s
usage types
AS-ABAP,
AS-JAVA, MI
WFM_CORE
LSO CP
LSO FE
cProject Suite
SAP NW 2004s usage types: EP, AS-ABAP, AS-JAVA
eRecruiting
Biller Direct
XSS (Self Services)
EP xx Content Package
Firewall
*) See SAP Service Marketplace at service.sap.com/notes ? SAP Note 855534 (Embedded NetWeaver Components in ERP)
Information About SAP ERP System Landscapes
SAP ERP Master Guide:
System Landscapes Examples
SAP ERP Solution Map:
Scenario and Process Descriptions
S
A
P

End-User Service Delivery
Analytics
Strategic Enterprise
Management
Financial Analytics Operations Analytics Workforce Analytics
Financials
Financial Supply Chain
Management
Financial Accounting Management Accounting Corporate Governance
Human Capital
Management
Talent Management Workforce Process Management Workforce Deployment
N
e
t
W
e
a
v
e
r
Procurement and
Logistics Execution
Procurement Supplier Collaboration
Inventory and
Warehouse
Management
Inbound and
Outbound Logistics
Transportation
Management
Product Development
and Manufacturing
Production Planning Manufacturing Execution Product Development Life-Cycle Data Management
Sales and Service Sales Order Management
Aftermarket Sales and
Service
Professional-Service
Delivery
Incentive and Commission
Management
Project and Environment
SAP Solution Manager:
I l t ti C t t
Corporate Services
Real Estate
Management
Enterprise Asset
Management
Project and
Portfolio
Management
Travel
Management
Environment,
Health and
Safety
Quality
Management
Global Trade
Services
Implementation Content
Scenario & Process Component Lists:
Process-Component Mapping
SAP Upgrade Tools and Content at a Glance
Project
Advanced offerings
to master key challenges
Project
Kickoff
Go Live
SAP Upgrade Roadmap
Project
Preparation
Final
Preparation
for Cutover
Production
Cutover & Support
Upgrade
Blueprint
Upgrade
Realization
Application
configuration
Project definition /
Monitoring
Root Cause
Analysis Solution Consultant
S l ti A hit t
Solution Consultant
S l ti A hit t
Testing
End user
Training
Project definition /
Solution design
Validation
Solution Architect Solution Architect
ChangeRequest
Management /
Maintenance*
Technical Execution* (DEV,QAS,PRD, etc.)
I t ll ti U d S t P k
Technical design
g
SAP Solution Manager
Validation
Technical Consultant
System Admin
Technical Consultant
System Admin
SAP Software Lifecycle Manager
- Installation, Upgrade, Support Packages -
g
* Subject to be developed in next release
Transfer From Solution Manager to Software Lifecycle
Manager
Transfer information of affected SAP systems and scenarios from SAP Solution
Manager to SAP Software LifeCycle Manager to validate the technical design
Scenario information System information
Based on
existing Solution existing Solution
Manager data
Upgrade project in Solution Manager
Affected systems New scenarios
Plan in Software LifeCycle Manager
Technical Design in SAP Software LifeCycle Manager (1/2)
V lid ti f t h i l d i ith S ft Lif C l M Validation of technical design with Software LifeCycle Manager
Plan in Software
LifeCycle Manager
1. Scenario selection
LifeCycle Manager
2. Determine application components
SAP R/3 Enterprise 47X200 - Server
Technical Design in SAP Software LifeCycle Manager (2/2)
V lid ti f t h i l d i ith S ft Lif C l M
Plan in Software
LifeCycle Manager
3. System mapping and impact status
Validation of technical design with Software LifeCycle Manager
LifeCycle Manager
5. Support package identification
SAP R/3 Enterprise 47X200 - Server SAP ERP 2004 ECC ABAP
4. Conflict handling
! Scenario Procurement through Automotive Supplier may not work properly anymore No conflicts found
E l i h l
Example is a showcase only
and not based on real data!
Transfer from Software LifeCycle Manager to Solution
Manager
Validation of technical
design is completed
Plan in Software LifeCycle Manager
System Application component System
information
Application component
information
Required application
components and components and
system information
are up-to-date
QW8:100
Upgrade project in Solution Manager
SAP Solution Manager, SAP Software LifceCycle Manager
in a Customers Solution Landscape
SAP Solution
Manager
Solution
SAP CRM
4 0
SAP CRM
4 0
Manager
Solution
Landscape
4.0 4.0
SAP SRM
4.0
SAP SRM
4.0
SAP APO
3.1
SAP APO
3.1
SAP R/3
4 6C
SAP R/3
4 6C
Affected systems
New scenarios
Application component
requirements
Update on system
information 4.6C 4.6C information
SAP Software
Lifecycle
MManager
* Subject to be developed in next release
Wrap up: Ensure Smooth System Landscape Transition
Understand all dependencies in the system landscape
Understand the dependencies and compatibility issues within a system, e.g. released
DB OS and UI combinations in target release (vertical stack) DB, OS and UI combinations in target release (vertical stack)
Understand dependencies between different SAP products and software components
(horizontal stack)
Identify compatibility issues with other software and hardware products, e.g. 3rd Identify compatibility issues with other software and hardware products, e.g. 3rd
party software, SAP partner add-ons or printers (horizontal stack)
Vertical Stack
Horizontal direction
SAP Components, UI,
DB, OS,
Unicode Upgrade
E i f Ti & T i k
Upgrade Offerings
Further Information
Summary & Questions
Snapshot on SAP ERP 6.0
Long-term Foundation
Newly announced 5 year release cycle
Upgrade Drivers* (in %)
Newly announced 5-year release cycle
with enhancement packages
Major cornerstone in your overall IT
t t
23
23
Technical infrastructure
Continuous compliance
Additional functionality
strategy
ERP upgrade decision
is important
6
9
19
Technical infrastructure
Process re-design
Lower system cost
Most Popular Processes* Upgrade Value*
6
y
* ASUG survey: 163 companies
Most Popular Processes*
New G/L
Employee Self Services
Upgrade Value*
87% met or exceeded ROI objectives*
Performance impact company-specific Employee Self Services
Manager Self Services
Administering Employee HR data
Performance impact company specific
Main drivers: DSO reduction, staff
productivity increase, TCO reduction
St t i l i l i d
Credit Management
Strategic value mainly perceived on
flexibility and compliance
* ASUG survey: 55 companies * Ramp-up feedback from >200 projects
y p p p p j
SAP ERP 6.0: 4800+ Live Customer Systems
North / Latin America EMEA Central / EMEA
News
APA / Japan
Boustead Petroleum
Aera Energy LLC
Eclipse Aviation Corporation
Global Enterprise Mgmt. Solution
Amphenol-Tuchel Electronics
Batigroup
Bitburger Brauerei Th. Simon
Neue Zrcher Zeitung
sterreichische Bundesbahnen
Palfinger
Boustead Petroleum
Marketing
CNI Enterprise (M) Sdn
Bhd
Higher Education Press
Intel Corporation
Petroquimica Triunfo S
Saskatchewan Power
School Board of Orange County
Bitzer Khlmaschinenbau
CIMPOR - INDSTRIA DE
CIMENTOS
Dexxon DATA MEDIA
Petron
Provincie Noord-Holland
REINZ-Dichtungs-GmbH
Sanoma Magazines
Higher Education Press
School Board of Orange County
TransAlta Corporation
Translogic Corporation
Tyson Foods
E.ON IS GmbH
Edelweiss Facility Management
EK/servicegroup eG
Sanoma Magazines
SARS
Saudi Aramco
SCHOTT
University of Mississippi
Energie AG Obersterreich
Erdgas Zrich
Fischer Advanced Composite
Gelsenwasser
SERVICIO EXTREMEO DE SALUD
Statoil ASA
STEF-TFE
Gelsenwasser
IMPRENSA NACIONAL CASA DA
Henkel KGaA
Hamburger Wasserwerke
Swiss RE
Technische Werke
Telekom Austria
TelekomSlovenije
Karstadt/Quelle
Lisa Drxlmaier
Magistrat der Stadt Wien
Telekom Slovenije
TeliaSonera
The Land and Agricultural Bank of SA
THS Treuhandstelle GmbH
MSH Medien System Haus
Wiener Stdtische Versicherungen
Factors Affecting Upgrade Tool Runtime and Downtime
Scatter Plot Downtime vs. DB-Size
100
N di t i t f DB Si d
Hard disk
configuration
Hardware /
70
80
90
e
/
h
No direct impact of DB-Size on upgrade
runtime/downtime !
Database
Hardware /
operating
system
40
50
60
D
o
w
n
t
i
m
e
Runtime /
Downtime
depending
on
Number of
modifications
Upgrade
strategy and
reaction time
0
10
20
30
Number of data
structure
conversions
Number of
installed
languages
0
0 100 200 300 400 500 600 700 800 900 1000
DB-Size/GB
Source: Analysis of RSUPGSUM reports
Number of
clients
Productive
applications/ Add-
Ons or industry
solutions
y p
As each system is highly individual regarding its configuration and application data.
A forecast of runtime and downtime is only possible when analyzing results of a test y y g
upgrade with representative set of data !
SAPs Downtime Assessment Service is recommended !
Improvements: Technical Downtime
Business Uptime
Business Downtime
Business perspective:
T h i l i
Customer specific 8,3 h
Technical perspective:
Prepare
Upgrade
Downtime
Follow-up
activities
Upgrade Uptime
p
SAP ECC 6.0 - SR0: 14,9 h
SAP significantly
reduced technical
downtime due to
SAP ECC 6.0 SR1: 10,2 h
do t e due to
incrementel tuning of
Upgrade tools.
Further reductions via
i d C t
ECC 6.0SR2: 7,9h
improved Customer
Based Upgrade (CBU)
possible.
SR = Service Release
Downtime of Upgrade to ERP 6.0: Customer Feedback
Downtime Distribution
Downtime: minimum possible technical downtime, if downtime minimized had (would have)
been used as an upgrade strategy, and there was no dialog time during procedure execution.
960
1080
# 256 (154)
14.9 h
XPRA 256
Rem.; 195
Rem ; 177
720
840
]
Rem
# 778 (492)
10.2 h
w/ DT-Minimized Strategy
TABIM; 135
XPRA; 256
XPRA; 214
Rem.; 177
R 128
480
600
D
T

[
m
i
n
]
Rem.
XPRA
TABIM
PCON
# 543 (351)
7.9 h
PCON; 350
TABIM; 169 XPRA; 166
Rem.; 128
240
360
SR0
;
PCON; 154
PCON; 57
TABIM; 99
0
120
1 2 3
SR1 SR2
Shipment
Activities:
- Improvements for Oracle
(DB patches, opt. for upgrade)
5 AIM i d
Activities:
- Optimize upgrade packages to improve
parallelization
L i t ti & t d t
- 5 AIM improved - Less interruptions & repeats due to errors
Downtime Distribution: ERP 6.0 Support Release 2
35
25
30
35
Downtime:
minimum possible
technical downtime
Evaluation type: Standard
Internal Upgrades: Excluded
Customer Upgrades: Included
15
20
#
technical downtime
(if downtime minimized had
been used as an upgrade
strategy, and there was no
dialog time during procedure
Upgrade Title:
SAP ERP 6.0 SR2
Release: 700
Database entries found 543
5
10
dialog time during procedure
execution)
0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
dt [h]
180
A 7 9 h
120
140
160
80% < 10 h
Average 7,9 h
60
80
100
#58% < 7 h
0
20
40
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29
dt [h]
Customer Satisfaction with Upgrade Downtime
Upgrade type Total feedback Satisfied pg yp
SAP ERP 6.0 SR2 Release: 700 415 88%
SAP ERP 6.0 Release: 700 188 81%
SAP ECC SR1 Release: 640 435 92%
SAP ECC Release: 640 72 89% SAP ECC Release: 640 72 89%
SAP R/3 Enterprise Release: 470/200 496 89%
SAP R/3 Enterprise EXT2 SR1 Release: 470/200 443 93%
SAP R/3 Enterprise Release: 470 843 87%
SAP R/3 Enterprise (CBU) Release: 470 2 100%
Customer Satisfaction with Upgrade Downtime
Upgrade type Total feedback Satisfied pg yp
SAP R/3 Enterprise (CBU) Release: 470 2 100%
SAP R/3 Enterprise Release: 470 843 87%
SAP R/3 Enterprise Release: 470/200 496 89%
SAP ECC Release: 640 72 89% SAP ECC Release: 640 72 89%
SAP ERP 6.0 Release: 700 188 81%
Customer Satisfaction with Documentation
Upgrade type Total feedback Satisfied
SAP R/3 E t i EXT2 SR1 R l 470/200 378 90%
Customer Satisfaction with Upgrade Documentation:
SAP ERP 6 0 Release: 700 188 84% SAP ERP 6.0 Release: 700 188 84%
Average number of Customer Calls:
Upgrade type Total feedback Average
SAP R/3 Enterprise Ext. Set 1.10 161 7
SAP R/3 Enterprise Ext Set 2 00 SR1 176 3 SAP R/3 Enterprise Ext. Set 2.00 SR1 176 3
SAP ERP 2004 31 8
SAP ERP 2004 SR1 136 3
SAP ERP 6.0 Release: 700 75 6
SAP ERP 6.0 SR1 Release: 700 94 7
SAP ERP 6 0 SR2 Release: 700 158 3
SAP ERP 6.0 SR2 Release: 700 158 3
Possible Upgrade Approaches for the Go-To-Release
Strategic Business Improvement
Focus on functionality extension and
3
Possible Upgrade Approaches
Focus on functionality extension and
improvement
Enablement of new and optimized business
processes and scenarios based on new ERP
3
core functionality
Functional/Retrofit Upgrade
2
u
e
2
pg
New functionality to be implemented as part of
the upgrade, modification clearing
Focus on reduction of system complexity
V
a
l
u
2
Technical Upgrade
Focus on pure technology upgrade
1
1
Focus on pure technology upgrade
Retain functionality used
Review Usage of custom developments
Time
Starting Point
Recommendations:
Create and evaluate your own upgrade roadmap, considering the whole spectrum
Define business justification first but start small with the technical upgrade only
Define business justification first but start small with the technical upgrade only
SAP GUI Options
SAP GUI is still the default UI with SAP ERP
SAP Enterprise Portal is not required unless
portal-specific applications are used (e.g.
Employee Self-Service) Employee Self-Service)
SAPGUI 7.10 is the recommended GUI for use with SAP ECC 6.0
SAPGUI 6 40 also supports SAP ECC 6 0 check dependencies during SAPGUI 6.40 also supports SAP ECC 6.0, check dependencies during
planning of SAPGUI Rollout
SAP GUI for Java still offered for Macintosh, Linux, etc. , ,
SAP GUI for HTML still supported via Integrated ITS
Technical Upgrade: OS/DB dependencies
OS/Database Upgrades
Check the Product Availability Matrix (PAM) to determine if any
upgrades are required to the OS or RDBMS
(http://service.sap.com/pam )
Generally such upgrades are performed in advance of the upgrade Generally, such upgrades are performed in advance of the upgrade
Oracle customers: SAP WebAS 7.0 (and thus ECC 6.0) only run on
Oracle 10!
Additional Hardware Consumption when Upgrading to
ECC 6.0
100,0%
Absolute additional hardware
consumption for an upgrade
80,0%
,
from a source Release
to SAP ECC 6.0
The notes contain only DELTA
60,0%
The notes contain only DELTA
sizing information from a source
release to the next release.
40,0%
20,0%
Source
Release:
0,0%
4.0b 4.5b 4.6b 4.6c Enterprise 1.10 Enterprise 2.00 ECC 5.00
SAP Note:
Release:
113795 178616 323263 517085 752532 778774 901070
Memory App CPU App Disk DB
Hardware Sizing
No additional business processes or users after the upgrade:
Sizing verification and proactively optimize configuration :
Going Live Functional Upgrade Check
No additional business processes or users after the upgrade:
Going Live Functional Upgrade Check
Analysis Session
Load based Analysis
Parameterization of future Landscape
Verification Session
provides corrective measures for avoiding potential bottlenecks
Extensive changes on business processes or numbers of users after the upgrade:
Quick Sizer for user / throughput based sizing
Additional Services to improve the performance of the system
Solution Management Optimization Services g
Business Benefits per Upgrade Scenario
Moving towards eSOA
Adopted SAP to deploy Enterprise SOA infrastructure Adopted SAP to deploy Enterprise SOA infrastructure
Deployed composites to deploy operational dashboards
Integrated xMII for manufacturing shop floor analytics
Introducing new functionality
Lowered post-merger costs of integration with Maytag
g y
Modernized financial accounting capabilities
Lower technical infrastructure costs
Reduced customizations to manage
T h i l U d t SAP ERP
Reduced customizations to manage
One project to upgrade ERP and retire instances
Technical Upgrade to SAP ERP
Access to new functionality
Reduction in maintenance and testing costs g
Reduce number of customizations to maintain
One project to upgrade ERP and implement support packs
Recommendations: System Downtime and Dependencies
Split different downtimes into different
maintenance slots! maintenance slots!
Use latest service release (e.g. SAP ERP 6.0 ( g
SR2) for the upgrade!
Use downtime minimized upgrade strategy
for production system!
Evaluate downtime for production system
during upgrade of QA system or already g pg y y
during sandbox Upgrade
Plan and communicate downtime of
productive system!
Further Recommendations on Upgrades I
Distribution of new SAPGUI version should
be started as soon as possible! be started as soon as possible!
Returning modifications to SAP standard g
should be one of the main targets!
Th b h d i b The better the documentation about
modifications, the easier the modifications
adjustments can be performed! adjustments can be performed!
Customer starting from SAP R/3 4.5B or g
higher benefit from the SAP Modification
Assistant !
Further Recommendations on Upgrades II
Upgrade without implementation of new
functionality (except low hanging fruits)
is preferable aka Technical/Functional Upgrade
SAP GoingLive - Functional Upgrade Check
should be requested!
SAP ERP since SAP R/3 Enterprise is Unicode
compliant, the ABAP syntax check is more
intensive, even on system with Unicode switched
off. As a result, some customer programs might , p g g
need to be checked and adjusted.
Customers with Industry Add-Ons should review y
the Industry Add-On specific upgrade guides
which can be found at
http://service sap com/instguides http://service.sap.com/instguides
Now in section ERP 6.0 included!
Unicode Upgrade
E i f Ti & T i k
Upgrade Offerings
Further Information
Summary & Questions
Key Elements influencing an Upgrade
Governance model & senior management attention and support
Approval process and requirements, e.g. ROI, cost coverage
Business Business
Business situation and priorities, e.g. M&A, globalization, BPR
Compliance requirement, e.g. SOX, FDA,
Processes supported by applications e g downtime
Business Business
Structure of the application landscape, e.g. systems, interfaces
Processes supported by applications, e.g. downtime
Applications Applications
Structure of the application landscape, e.g. systems, interfaces
Functionality implemented and in use
Languages/Code Pages implemented and in use
Applications
Landscape &
IT Infra-
structure
Applications
Landscape &
IT Infra-
structure
IT infrastructure, e.g. HW, tools, Network, bandwidth, tech.
interfaces, front-end, devices
New functionality demanded
structure structure
y
Capacity, skill available internal, externals
Strategy how to execute the upgrade project
Project Project
Strategy how to execute the upgrade project
Testing and documentation requirements and strategy
Cost, budgeting, funding and project monitoring
Planning and
Execution
Planning and
Execution
Go-life support
SAP AG 2007, SAP ERP Roadmap / 84
Release Delta Functionality: SAP ERP Solution Browser
DESCRIPTION
Enables customers and partners to learn
about new capabilities between different
R/3 and SAP ERP versions
Helps customers to build a value
proposition for the upgrade to SAP ERP
Availability: Availability:
SAP ERP Solution Browser:
http://solutionbrowser.erp.sap.fmpmedia.com/
Further information at SAP Upgrade Info Center: Further information at SAP Upgrade Info Center:
http://service.sap.com/upgrade-erp
BENEFITS
Tailored access to detailed delta information
of latest SAP ERP versions
Saving time/effort in the definition of a value
proposition / business case for a SAP
ERP transition
SAP Upgrade Experience Database
The SAP Upgrade Experience Database
provides experiences/statistics of
DESCRIPTION
EXAMPLE Project Duration
Project duration in months
Source release: SAP R/3 Enterprise Target release: SAP ECC 6 0
provides experiences/statistics of
completed upgrade projects
The SAP Upgrade Experience Database
includes the following upgrade aspects:
Source release: SAP R/3 Enterprise Target release: SAP ECC 6.0
0 1 2 3 4 5 6 7 8 9 10 11 12
Max: 6,6 Min: 1,9
Median: 4,0
g pg p
Additional hardware requirements
Project duration
Business Downtime
90% of the collected data are represented by the indicated range.
Median is reflecting the average value where 50% of all measured numbers
are smaller or equal and 50% of all measured numbers are larger or equal
0 1 2 3 4 5 6 7 8 9 10 11 12
Months
based on 15 upgrades
Business Downtime
Reasons for upgrade, etc.
Detailed results on SAP ERP 6.0 upgrades
il bl i 06/2007
are smaller or equal and 50% of all measured numbers are larger or equal.
are available since 06/2007
BENEFITS
Your Feedback is Welcome!
Customers planning an upgrade to SAP
ERP 2004 (ECC 5.0) and SAP ERP 6.0 (ECC
6.0) can participate in the upgrade
experiences gathered in similar upgrade
Register NOW:
SAP Upgrade
experiences gathered in similar upgrade
projects.
Experience
Database
Experience Database Information Provided
Reasons for Upgrades by Source Release
Main reasons for upgrades to SAP ECC 6.0
Source release: SAP R/3 Enterprise
Technical requirements *
Need of new functionality
Source
Release
Question asked:
What was the main motivation for your upgrade project?
(Reasons could be selected from a drop-down list as well as
individual reasons could be mentioned (reason others))
Approach in Upgrades by Source Release
Source
Release
Question asked:
Please specify the upgrade type of your upgrade project
0% 25% 50% 75% 100%
Others
Reduce total cost of ownership
Integration of industry solutions
Improve usability of existing solution
Leverage latest technology
Legacy system replacement
End of mainstream/ extended maintenance
SAP R/3
Enterprise
How to read the charts:
The shown reason categories correspond to the drop-down list in
the questionnaire.
As more than one reason could be selected per upgrade, the
different reason categories may not add up to 100%. The results
for each reason category are standardized to the number of
upgrades of the given sample.
Example: 50% per reason = the reason was selected in every
second upgraded project.
Approach in upgrade project
Source Release: SAP R/3 Enterprise Target release: SAP ECC 6.0
13% 87%
Technical Upgrade
Upgrade with deployment
of new funcitonality
This diagram shows the approach in the upgrade projects
Conclusion/findings:
Most upgrade projects to SAP ECC 6.0 were performed
using the upgrade approach Technical Upgrade.
SAP R/3
Enterprise
Conclusion/findings: (top three reasons)
SAP R/3 Enterprise: The Need of new functionality provided
with SAP ECC 6.0 is named as a reason for the upgrade in
nearly every second upgrade project. Technical requirements
is the most often selected reason. And Leveraging the latest
technology with the upgrade is an important reason in about
50% of the measured upgrades.
SAP R/3 4.6C: Similar to the findings in upgrades with source
release SAP R/3 Enterprise, the Need of new functionality
provided with SAP ECC 6.0 is a reason in every second
Main reasons for upgrades to SAP ECC 6.0
Source release: SAP R/3 4.6C
Reduce total cost of ownership
Integration of industry solutions
Improve usability of existing solution
Leverage latest technology
Legacy system replacement
End of mainstream / extended maintenance
Technical requirements *
Need of new functionality
SAP R/3
4.6C
SAP R/3
4.6C
Annotation:
Technical Upgrade: Upgrade of currently used SAP software
without applying new functionality during the upgrade project
On the other hand, the diagrams on the next page indicate
that the need for new functionality that is provided with SAP
ECC 6.0 is one of the main reasons to upgrade. This is in
accordance with the experiences of other SAP Upgrade
projects and in agreement with SAP recommendations. A
Technical Upgrade upgrade approach is the preferred
project type in a first step (except low-hanging fruits),
whereas new functionality is deployed in a second step.
Approach in upgrade project
Source Releaes: SAP R/3 4.6C Target release: SAP ECC 6.0
3% 97%
Technical Upgrade
Upgrade with deployment
of new functionality
SAP AG 2007, Upgrade Experiences in Upgrade Projects to SAP ECC 6.0 / 14
provided with SAP ECC 6.0 is a reason in every second
upgrade project. Technical requirements is named as
important reason in 1/3 of the measured upgrade projects.
End of mainstream/extended maintenance is the most often
selected reason.
0% 25% 50% 75% 100%
Others
* Annotation:
Examples for technical requirements: aim to have all SAP software
in use on the same release level, technical infrastructure, etc.
without applying new functionality during the upgrade project.
Upgrade with deployment of new functionality: Upgrade of
currently used SAP software, with new functionality added during
the upgrade project.
Project Duration in Months by Source Release
Source
Release
Question asked:
Business Downtime* in Hours
Source
Release
Question asked:
Please specify how many hours the solution was unavailable
Max: 6,6 Min: 1,9
Median: 4,0
Please specify the duration of your upgrade project up to the
initial go-live (in months).
To avoid distorting the results, 10% of the measured numbers
on the left hand side of the distribution and 10% of the
measured numbers on the right hand side of the distribution
were cut off.
Per sample, 80% of the collected data is represented by
SAP R/3
Enterprise
Business downtime* in hours
Upgrade strategy = downtime minimized, w/o Unicode conversion
Max: 65,0 Min: 20,0
Median: 34,0
for your end users. Even if your upgrade was finished over the
weekend, please specify how many hours the solution would
have been unavailable for end users in total.
To avoid distorting the results, 10% of the measured numbers on
the left hand side of the distribution and 10% of the measured
numbers on the right hand side of the distribution are cut off.
Per sample, 80% of the collected data is represented by
the indicated range.
Median = in a given sample, 50% of all measured numbers are
less or equal to the median, and 50% of all measured numbers
t l t th di I t i di t ib ti th
SAP R/3
Enterprise
0 1 2 3 4 5 6 7 8 9 10 11 12
Months
Source release: SAP R/3 4.6C Target release: SAP ECC 6.0
Max: 6,6
Median: 5,0
Min: 3,0
the indicated range.
Median = In a given sample, 50% of all measured numbers
are less than or equal to the median, and 50% of all measured
numbers are greater than or equal to the median. In symmetric
distributions, the median is located in the middle of the
distribution.
SAP R/3 Enterprise, SAP R/3 4.6C: Upgrades with source
releases SAP R/3 Enterprise and SAP R/3 4.6C show
similar results with a trend to slightly shorter project
SAP R/3
4.6C
0 20 40 60 80 100 120
Hours based on 11 upgrades
Business downtime* in hours
Source release: SAP R/3 4.6C Target release: SAP ECC 6.0
Upgrade strategy = downtime minimized, w/o Unicode conversion
Max: 84 0 Min: 31 2
Median: 48,0
are greater or equal to the median. In symmetric distributions, the
median is located in the middle of the distribution.
Only upgrades that followed the Downtime minimized upgrade
strategy were taken into account. No Unicode conversion was
performed.
The business downtime was <= 48 hours (2 days)
SAP R/3 Enterprise: for 64% of all measured upgrade projects
(for 82% <= 60 hours)
SAP R/3 4.6C: for 61% of all measured upgrade projects
SAP R/3
4.6C
0 1 2 3 4 5 6 7 8 9 10 11 12
Months
, ,
g y p j
durations for upgrade projects with source release SAP R/3
Enterprise. But more statistics are needed to prove this
trend.
0 20 40 60 80 100 120
Hours
Max: 84,0 Min: 31,2
(for 74% <= 60 hours)
* Annotation:
Business downtime = total time (planned and unplanned) that
the system/solution is not available for end users. This includes
the technical downtime plus the time necessary for the data
backup, final tests, etc., before the productive
environment is released for end users.
Perceived Challenges
Plan Build
40%
50%
40%
50%
20%
30%
20%
30%
0%
10%
10%
20%
0%
Source: SAP Upgrade Survey 2005 (450 interviews)
0%
Right timing for transition
f
Source: SAP Upgrade Survey 2005 (450 interviews)
0%
Project management
IT i f t t Define Value Proposition
Justify budget for project
Decide on target release
IT infrastructure
Technical upgrade / Minimum downtime
Adapt application / Modification
Other
Cost/effort estimation
Up-skill project team
adjustment
Efficient testing
End-user training
Other
Other
End user training
ERP Upgrade Service Offerings in Focus
Plan Build
Budget Planning Project Planning Technical Functional &
Quick Upgrade
A l i (QUA)
g g
Upgrade
j g
Standardized
implementation Fix price
eSOA
a
l
Analysis (QUA) Upgrade
Assessment /
Quick Upgrade
Evaluation (QUE)
implementation
services
Fix price
I l t ti
e
c
h
n
i
c
a
System
Analyzer
System
Analyzer
Evaluation (QUE)
Implementation
projects
Time & materials
T
e
Upgrade Value
Estimator
Upgrade Value
Estimator
Value
t
1
i
n
e
s
s
Solution
B
Solution
B
Value implementation Projects:
Business Process Reengineering
assessment
1
B
u
sBrowser Browser
Business Process Outsourcing
. . .
MaxAttention / Premium Support / Safeguarding for Upgrade / Upgrade Coach
1
Project Based
SAP Upgrade Newsletter(s) Register NOW!
For continuous upgrade news right
to your desk, subscribe to the SAP
Upgrade Newsletter: SAP Upgrade
Newsletter
Regional / local SAP upgrade news are proactively distributed on
a quarterly basis to customers
No. of recipients today: >15.000
Available languages/country versions:
English
German
Japanese
Russia
Upgrade News - Content:
Focus topic Focus topic
Solution-specific information,
e.g. SAP ERP
SAP upgrade tools, services and content
pg ,

SAP Safeguarding for Upgrade
Safeguarding for Upgrade is the ideal
DESCRIPTION
OVERVIEW Mapping to Lifecycle
Safeguarding for Upgrade is the ideal
and holistic engagement with SAP for
any technical risk mitigation of SAP
upgrade projects
Approach, Methodology & Deliverables:
Permanent SAP Technical Quality
Manager as key facilitator g y
Proven and standardized services,
assessments, optimizations, trainings
(E2E400 Technical Upgrade
Technical quality management for upgrade
Management) and tools
BENEFITS
Technical quality management for upgrade
projects
Minimize risk of business disruption.
Maximize efficiency of upgrade activities.
More detailed information on
SAP Safeguarding for
Upgrade is available at: Maximize efficiency of upgrade activities.
No surprises - SAP's best experts minimize
your technical risks, ensure the success!
C tifi ti t P M
Upgrade is available at:
https://service.sap.com/safe
guardingupgrade
Certification program to Program Manager
for Technical Upgrade Management
Value Proposition Safeguarding Upgrade
Upgrades in complex SAP landscapes
Multiple upgrade projects
Characteristics
Multiple upgrade projects
Each project facing unique
challenges
High degree of complexity g g p y
(Customization / Interfaces)
Need for minimum business
disruption and downtime
Potential synergies and
efficiency improvements
Value Proposition Safeguarding for Upgrade
Technical Upgrade Roadmap & Impact Analysis
We tapped into
Safeguarding to mitigate Technical Upgrade Roadmap & Impact Analysis
Continuous Engagement provided by TQM
Safeguarding to mitigate
risk.
For this upgrade we
wanted no surprises
Tailored Services for Cost & Risk mitigation
wanted no surprises
Steve Dean
Director of Appl. Architecture
Texas Instruments Inc
Texas Instruments Inc.
Address Perceived Challenges and Demand
Plan Build
Customer
Project
management
Right timing for
transition
Customer
Feedback
IT
infrastructure
Minimize
d ti
Define Value
Proposition
Justify budget
f j t
Seeking for clear
and consistent
message
downtime
Modification
adjustment
Effi i t
for project
Decide on target
release
C t / ff t
g
Demanding
estimation on
effort and benefit
Efficient
testing
End-user
training
Cost / effort
estimation
Up-skill project
team
effort and benefit
Requesting
references and
benchmark data
Other
training
0%10%20%30%40%50%
Other
0%10%20%30%40%50%
benchmark data
Claiming to focus
on the
li ti
Source: SAP Upgrade Survey 2005 (450 interviews) Source: SAP Upgrade Survey 2005 (450 interviews)
0%10%20%30%40%50% 0%10%20%30%40%50%
application
landscape
Source: MOVE/GUO, User Group Engagement
Lessons Learned
Involve and allocate responsibility to the User Community
Position project as mid-/long-term improvement strategy, but start
ith t h i l d
Business Business
with an technical upgrade
Focus on the upgrade of business processes instead of upgrading
systems
Business Business
y
Conduct Good housekeeping (esp. archiving, cleansing) drives
Applications Applications
efficiency of upgrade (e.g. optimized downtime)
Prepare UNICODE Conversion in parallel to upgrade activities
Review the Industry Add On specific upgrade guides;
pp
Landscape
& IT Infra-
structure
pp
Landscape
& IT Infra-
structure
Review the Industry Add-On specific upgrade guides;
http://service.sap.com/instguides
structure structure
Get started using services for estimation and planning
Seek for specific support for key topics, e.g. to minimize downtime,
Project
Planning
Project
Planning
test organization, UNICODE
Organize test and documentation centrally
Leverage SAP Going Live support e g Go Life Check
and
Execution
and
Execution
Leverage SAP Going-Live support e.g. Go-Life Check
Unicode Upgrade
E i f Ti & T i k
Upgrade Offerings
Further Information
Summary & Questions
Get Started
ERP Upgrade
specific
SAP Upgrade Info Center
information
SAP Upgrade Info Center
(www.service.sap.com/upgrade)
SAP Upgrade
Road Map Road Map
SAP Upgrade
Newsletter
Statistics Statistics
or
screen shot
SAP ERP
Solution Browser
SAP Upgrade Information Center Landing Page for SAP
ERP - Upgrade Aspects
Key documents:
Value of Upgrade
Functional Deltas in Detail
Key documents:
SAP ERP Upgrade Aspects
Upgrade Master Guides
SAP Upgrade Offerings SAP Upgrade Offerings
Direct access to:
SAP Upgrade Road Map
SAP Upgrade Services
SAP ERP Solution SAP ERP Solution
Browser
Projects statistics
(Upgrade Experience DB) (Upgrade Experience DB)
Product Availability Matrix
www.service.sap.com/upgrade-erp
Provide YOUR Feedback! Benefit from Feedback!
SAP Upgrade Technical Statistics:
send Upgrade Evaluation Form (Upgrade statistics plus your
individual feedback comment) via email! individual feedback comment) via email!
Upgrade statistics database helps improving upgrade performance
Your comments are reviewed within upgrade tool development !
SAP Upgrade Experience Database:
SAP has build up an "Upgrade Experience Database" that will contain the p pg p
upgrade experiences gathered in productive upgrades at customer side.
SAP Upgrade Info Center ( http://service.sap.com/upgrade )
Related Topics: SAP Upgrade Experience Database
Registration via Online Survey
1
2
Further Upgrade Information
SAP Upgrade Info Center:
Homepage: http://service.sap.com/upgrade Homepage: http://service.sap.com/upgrade
SAP ERP Upgrade Specifics: http://service.sap.com/upgrade-erp
SAP Upgrade Road Map: http://service.sap.com/upgraderoadmap pg p p p pg p
SAP Upgrade Newsletter: http://service.sap.com/upgradenewsletter
SAP Upgrade Tools:
SAP Upgrade Tools: http://service.sap.com/upgradetools
System Switch Technology: http://service.sap.com/upgradetech
SAP Solution Manager: http://service.sap.com/solutionmanager
SAP Upgrade Services:
Overview and order information: http://service.sap.com/upgradeservices
Upgrade Services of SAP Consulting: http://service.sap.com/ufg
Unicode Upgrade
E i f Ti & T i k
Upgrade Offerings
Further Information
Summary & Questions
Summary
System Switch upgrade with downtime minimized strategy minimizes y pg gy
technical upgrade process downtime
Further downtime minimization beyond standard upgrade technology
can be achieved via utilization of Downtime Assessment Service and
Customer based Upgrade Service
SAP is ready to assist you with comprehensive upgrade service
offerings in the planning and execution of your next upgrade
SAP Upgrade Road Map provides the project team guidance how to
manage the upgrade project successfully
SAP U d I f C t i th i iti l i t t fi d k d SAP Upgrade Info Center is the initial access point to find key upgrade
information
Further Information
Public Web:
www sap com www.sap.com
SAP Customer Services Network: www.sap.com/services/
Related SAP Education Training Opportunities

http://www.sap.com/education Choose your country , i.e.
http://www.sap.com/usa/education/ Upgrade Courses
R l t d W k h /L t t SAP T hEd 2006
Related Workshops/Lectures at SAP TechEd 2006

LCM216 `High Availability for Solutions based on SAP NetWeaver, LCM216 High Availability for Solutions based on SAP NetWeaver ,
2h Lecture
LCM211 Conversion of MDMP Systems to Unicode, 1h Lecture
LCM262 Making programs Unicode enabled, 2h Hands-on
Q & A
THANK YOU FOR YOUR
ATTENTION !
QUESTIONS SUGGESTIONS DISCUSSION
Please complete your session evaluation
Feedback
Please complete your session evaluation.
Be courteous deposit your trash, Be courteous deposit your trash,
and do not take the handouts for the following session.
Thank You ! Thank You !
Appendix Appendix
St t - Start -
SAP Business Connector
SAP BC and SAP XI are based on
different technologies
SAP BC 4.6 and 4.7 based on webMethods Integration Server 4.6
SAP XI b d t d d ( BPEL4WS f b i
SAP Note 309834 SAP BC
Support and Release Strategy
Supported SAP BC releases 4.6 and 4.7
SAP XI based on open standards (e. g. BPEL4WS for business
processes)
Only parts of an SAP BC
implementation can be migrated to an
pp
Supported JDK versions 1.3 and 1.2
(with limitations) only
Supported operating systems
implementation can be migrated to an
SAP XI implementation
XSLT mappings (offered since SAP BC 4.6)
Supported operating systems
Windows NT and 2000
Linux
Any custom programming done on the
basis of SAP BC will likely not be
reusable in the SAP Exchange
Infrastructure context
Sun Solaris 8 and higher (32-bit
only)
IBM AIX 4.3 and higher (32-bit only)
Infrastructure context
Example: SAP BC flow language
Customers still starting new projects
HP-UX 11.0 and higher (32-bit only)
OSS Support
C tl d t f th d f SAP BC
with SAP BC should consider XSLT for
mappings
SAP BC to SAP XI Migration Guide
Currently no date for the end of SAP BC
support is defined
New or updated SAP solutions will
b b d SAP N tW
SAP BC to SAP XI Migration Guide
be based on SAP NetWeaver
If a date is defined SAP note 571530 will
be updated -> after that date OSS
t f SAP BC ill d
support for SAP BC will end
Internet Transaction Server (ITS)
ITS 6.20 is long term supported for SAP products based on SAP
Netweaver 2004 and below as long as these products are supported
ITS 6.20 standalone cannot be used with SAP Netweaver 7.0 (SAP (
Kernel 7.00). ITS services which use Flowlogic and WebRFC are no
longer supported in system based on SAP Netweaver 7.0
Note 709038 Note 709038
Because SAP integrated ITS is part of the SAP kernel, the
maintenance is as long as the maintenance for the SAP kernel
For detailed information please check Platform Availability y
Matrix (PAM) to get up to date information
(http://service.sap.com/pam)
Example: Employee Self Service (ESS)
SAP will no longer maintain the most
ESS standard services based on
Standalone ITS Technology as of SAP
ERP 6.0. Note 870126.
SLD
CIMModel
NWWebASJava
The functional scope of ESS will be
ensured by SAP. SAP recommends
i ESS b d W b D
ECC6.0System
Front EndPC
AdobeDocument
Services1.0
WebBrowser
AdobeDocument
AdobeReader
JCo
http
NWPortal 7.0Server
SAPESS600 BPMSS
WebDynpro
SSO
SSO
using ESS based on Web Dynpro
(Java).
NWWebASABAP
RDBMS
Services1.0
AdobeReader
RDBMS
JCo
RFC
RFC htt
NWWebASJava
BPforXSS
SAPPCUI 600 NWPortal 7.0
SAPMSS600 BPESS
NWWebASJava
SAPECC6.0
For the implemented ESS-Scenarios
several SAP components have to work
together (Business Package XSS EP
ADS
RFC http
IGS
NWWebASJava
together (Business Package, XSS, EP,
Backend). The combination and
dependencies of them is dependent on
the implemented scenarios and could
be different in the individual releases.
Upgrade as a Project Discover, Evaluate, Plan
Upgrade Project
completed
Upgrade Project
started
Plan Build
Run
Operations &
Upgrade
Discovery
Upgrade Implementation
Upgrade
Evaluation
Operations &
Continuous
Improvement
Define Business and Define Minimize costs Define Business and
IT requirements
Define
strategy
Minimize costs
and risks of Upgrade Project
Upgrade Roadmap
Project
Preparation
Realization
Final Preparation
for Cutover
Production
Cutover &
Support
Blueprint
Document current
solution and set-up
project
Specify implementation
scope and solution
adjustment needs
Implement and
adjust solution
Perform integration
and system tests
and plan cutover
Execute production
system Upgrade &
Support
Key Activities in the Discovery Phase
Upgrade Discovery Upgrade Evaluation
Plan
Define Business Requirements
Key User Champs PMO Appl Mgmt
/ Cust.Dev.
Tech Op/ IT
Plan
Upgrade
P
Define
Business
R i t
Define IT
Requirements
/ Cust.Dev.
Tech Op/ IT
Plan
Upgrade
P
Define
Business
R i t
Define IT
Requirements
Define Business Requirements
Document current status of business solution
Identify impact of corporate business strategy on current
business solution
Define
Business
R i t
Define IT
Requirements
Program Requirements
q
Plan and
Update
Infrastructure
q
Plan and
Update
Infrastructure
business solution
Identify existing gaps and issues
Define future business needs
Understand new functions and features of SAP target solution
Requirements
Requirements
Test
Change
Test
Technical
Upgrade
Adjust
Application
Define
Business
and Test
KPIs
Manage
Upgrade
Project
Test
Change
Test
Technical
Upgrade
Adjust
Application
Define
Business
and Test
KPIs
Manage
Upgrade
Project
Manage
Upgrade
Project
Define IT Requirements
Map requirements to possible target solution(s)
Change
Sign-off
Upgrade
Test Core
Business
Processes
Perform
Project Change
Sign-off
Upgrade
Test Core
Business
Processes
Perform Perform
Project Project
Document current solution landscape
Identify impact of corporate IT strategy on current solution,
e.g. including provider model and data center, hardware and
platform strategies
Upgrade Technical
Upgrade
Upgrade Technical
Upgrade
Technical
Upgrade
p g
Define maintenance strategy for solution
Understand new technology features of possible SAP
target solutions
Key Activities in the Evaluation Phase
Plan
Define upgrade scope and approach
/ Cust.Dev.
Tech Op/ IT
Plan
Upgrade
P
Define
Business
R i t
Define IT
Requirements
/ Cust.Dev.
Tech Op/ IT
Plan
Upgrade
P
Define
Business
R i t
Define IT
Requirements
Identify and design possible target solution landscapes
(releases and software components) that meet business
and IT requirements
Perform high-level analysis how changes impact the
Plan
Upgrade
q
Plan and
Update
Infrastructure
q
Plan and
Update
Infrastructure
complete solution landscape (including technical platform,
SAP and non-SAP software)
Evaluate migration paths to possible target landscape and
determine best option
Program
Test
Change
Test
Technical
Upgrade
Adjust
Application
Define
Business
and Test
KPIs
Manage
Upgrade
Project
Test
Change
Test
Technical
Upgrade
Adjust
Application
Define
Business
and Test
KPIs
Manage
Upgrade
Project
Manage
Upgrade
Project
Identify TCO of the as-is solution and costs for adaptation to
Create business case
Change
Sign-off
Upgrade
Test Core
Business
Processes
Perform
Project Change
Sign-off
Upgrade
Test Core
Business
Processes
Perform Perform
Project Project
business requirements in existing landscape
Estimate TCO of planned target landscape
Estimate upgrade project costs and general change costs
Formulate business value proposition
Upgrade Technical
Upgrade
Upgrade Technical
Upgrade
Technical
Upgrade
Create business case
Key Project Activities of a Technical Upgrade at a Glance
Project Upgrade
Final
Preparation
Production
Cutover &
Upgrade
Build
Preparation Realization
Preparation
for Cutover
Cutover &
Support
Blueprint
Project Management
Time planning: Relations to other implementations or roll-out activities, Project runtime
Budgeting: IT-Costs; External and internal Resources;
Resource planning: project members; skills; roles responsibilities; number of external resources
PM
j g
Project standards & procedures: e.g. coordinating the parallel change streams of production and upgrade
landscape, define and manage the code freeze period Use Upgrade Roadmap as blueprint
Business Aspects
Release customizing: Upgrade Customizing / Delta Customizing
Identification and elimination of unused modifications and custom developments
Adjust and test customer developments, interfaces, forms; authorizations
E d U t i i l if i ifi t i t f h d d i i d
p
End-User training: only if significant user interface changes and redesign were required
Test core business processes efficiently (incl. user acceptance test)
Technical Aspects
IT infrastructure adjustments / Sizing of new release: Server, Frontend; Network
Planning of technical upgrade process: SAP application but also operating system and database
Recommendation: Split OS, DB and SAP Upgrade into different maintenance slots !
Planning Backup Strategy: during and after the technical upgrade
g p gy g pg
Executing of technical upgrade: DEV, QAS and PRD system (etc.), minimize downtime (tuning)
Post upgrade activities: Performance analysis, reorganizational actions
Milestone Planning Technical Upgrade Project
Upgrade characteristics: Assumed start release: SAP R/3 4.6C, target release: SAP ERP 6.0
Risk-minimized upgrade approach: Sandbox System and Temporary Maintenance Landscape
Advantages: Dual maintenance period can be reduced, 3-system-landscape for maintenance available
11 12 13
March
14 15 16 17
April
18 19 20 21 22
May
23 24 25 26
June
27 28 29 30
July
31 32 33 34 35
2007
August
36 37 38 39
September
40
2008
Calender week
11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40
Project preparation 1
Calender week
5 weeks
Blueprint Realization
Final preparation for
cutover
2
4
8 weeks
3 weeks
3
Go-Live & Support 5
Development
Freeze
2 w.
Upgrade strategy
Downtime requirements
Project portfolio
Elements
influencing
IT capacity and skills available
Testing requirements, e.g. GXP, SOX, FDA
End user involvement and availability
Application landscape and dependencies
influencing
project
planning
Application landscape and dependencies
1st Step: Creation of an Upgrade Project System
Project
Prepara
tion
Realizatio
n
Productio
n Cutover
& Support
Final prep.
for
Cutover
Blueprint
Legend
= new release
= old release
t l j t k
Project work
Project Management:
System landscape
tion
= actual project work
= Transport route
Project Management:
- Create detailed project plan
- Nominate project team
Order temporary hardware
UPS
4.6C
Upgrade project
system
- Order temporary hardware
Business Experts:
-Study material on new release
(Development News, SAP ERP Solution
Temporary
landscape
( p ,
Browser, )
-Perform upgrade impact analysis for
solution landscape
T i d l i
Productive
DEV PRD QAS
p
-Test preparation and planning
Developers:
- Review customer programs and
modifications
Productive
landscape
DEV
4.6C
PRD
4.6c
QAS
4.6C
Timeline
5W
3W 8W 2W
modifications
Technical Team:
- Prepare upgrade project system (UPS)
3W
May
Jun Jul Aug
2nd Step: Upgrade of the Upgrade Project System
Final prep.
for
Cutover
Blueprint
Productio
n Cutover
& Support
Project
Preparatio
n
Realizatio
n
Legend
= new release
= old release
t l j t k
System landscape Project work
Technical Team:
= Transport route
Upgrade project
system
UPS
ECC
Technical Team:
- Execute technical Upgrade
Developers:
-Perform SPDD and SPAU
Temporary
landscape
Perform SPDD and SPAU
adjustment
- Adjust & test customer reports
and transactions (total: 3 weeks)
Productive
DEV PRD QAS
p
Business Experts:
- Upgrade Customizing
- Test of business processes
(C l I 2 k )
Productive
landscape
DEV
4.6C
PRD
4.6C
QAS
4.6C
(Cycle I 2 weeks)
Deliverables:
- Business processes running in
sandbox system sandbox system
- Documentation of adjustment
activities
Timeline
5W
3W 3W
2W 5W
May
Jun Jul Aug
3rd Step: Upgrade of Development System
Project
Preparatio
n
Final prep.
for
Cutover
Realizati
on
Productio
n Cutover
& Support
Blueprint
Legend
= new release
= old release
t l j t k
System landscape Project work
Technical Team:
= Transport route
Technical Team:
- Setup a temporary development
system for maintenance (DEV)
- Upgrade of development system
(DEV)
UPS
ECC
Upgrade project
system
(DEV)
Developers:
- Redo manually SPDD and SPAU
adjustment
Temporary
landscape
DEV
4 6C
Productive
DEV PRD QAS
j
- Redo manually adjustment of
customer reports
- Short unit testing in development
system
p
4.6C
1. Copy
2. Upgrade
Double
maintenance
Productive
landscape
DEV
ECC
PRD
4.6C
QAS
4.6C
system
Business Experts:
- Redo customizing adjustments
- Unit testing in development system Unit testing in development system
Deliverables:
- Dual maintenance period starts
- Customer programs are unit tested in
Timeline
5W
3W 3W
2W 3W
development system
May
Jun Jul Aug
4th Step: Upgrade of QA System
Fi l
Realizatio
n
Project
Preparatio
n
Final
prep.
for
cutover
Productio
n Cutover
& Support
Blueprint
Legend
= new release
= old release
t l j t k
Project work
Technical Team:
System landscape
= Transport route
Technical Team:
- Setup temporary QAS system
- Upgrade of QAS system
- Transport project work to QAS
UPS
ECC
Upgrade project
system
- Transport project work to QAS
system
Business Experts:
- Final Integration tests in QA
DEV
4 6C
QAS
4 6C
Temporary
landscape g
system (Test cycle II 1 week)
Developers:
- Error corrections
DEV PRD QAS
4.6C
Double
maintenance
1. Copy
2. Upgrade
4.6C
Productive
p
T f
Deliverables:
- Tested business processes
- Refined downtime estimate
DEV
ECC
PRD
4.6C
QAS
ECC
Productive
landscape
Transfer
changes
- Detailed cutover plan
Timeline
5W
3W 3W 8W 2W
May
Jun Jul Aug
5th Step: Upgrade of Productive System
P d ti
Realizatio
n
Project
Preparatio
n
Final prep.
for
Cutover
Productio
n Cutover
&
Support
Blueprint
Legend
= new release
= old release
t l j t k
Project work System landscape
Technical Team:
pp
= Transport route
Technical Team:
-Upgrade of the production
system (PRD) Downtime
-Performance of post processing e o a ce o post p ocess g
Activities
Business Experts:
- Signing Off of the Solution in the
DEV PRD QAS
Productive
New Release
Deliverables:
- Release of the New Release for
Production Operation
T f
DEV
ECC
PRD
ECC
QAS
ECC
Productive
landscape
Production Operation
- Removal of Temporary
Enhancements from the System
Landscape
Transfer
changes
- Support for the Go-Live Date
- Project Closure
Timeline
5W
3W 3W 8W 2W
May
Jun Jul Aug
Upgrade Project Landscape
Make early experiences in the upgrade project system:
Technical upgrade procedure
Modification adjustment
Test of customer developments in new release
Upgrade customizing
Check functionality of processes in new release
T t f b i Test of core business processes
Reduce dual maintenance period:
Do high effort work in upgrade project system before
upgrade of system landscape
Reduce time window between upgrade of DEV and PRD Reduce time window between upgrade of DEV and PRD
system
Use 3-system-landscape for maintenance Use 3 system landscape for maintenance
(only emergency corrections allowed)
Plan and communicate code freeze time!
ERP Enhancement Packages
Overview
EVOLUTION OF ERP ARCHITECTURE
- Overview -
Changing the Game:
Introducing SAP Enhancement Packages
L E h t
SAP offers a new method to enhance your SAP Business Suite
and ERP solutions
Update your SAP enterprise software solutions with minimal
disruption to business and IT operations
Lean
User interface
EhA EhB
EhC EhD
EhA EhB
EhC EhD
EhA EhB
Enhancement
Package
p p
Expand on demand
Functionality
EhC EhD
EhE EhF
EhC EhD
EhE EhF
EhC EhD
EhE EhF
Enhancement Packages
Enterprise
services
SAP ERP 6.0
NetWeaver
foundation
SAP NetWeaver
What Are Enhancement Packages?
Optionally installed and activated software innovations for SAP ERP 6.0
Software innovations include; UI simplifications, functional
enhancements, industry specific capabilities and enterprise services
Cumulative in nature; current enhancement packages contain the entire Cumulative in nature; current enhancement packages contain the entire
content of earlier packages
Enhancement packages are not support packages
Improved Software Lifecycle
Installation of new functionality separated from activation via Switch Framework
Content of enhancement packages
Optional
Each SAP enhancement package contains several business functions.
Each business function can be optionally implemented and activated.
O ti l I t ll ti
Enhancement
Packages
Optional Installation
You install the business functions that are applicable to your business.
If installed:
Packages
- No UI or process change until a business function is activated
- No implications on the underlying NetWeaver platform, in addition
enhancement packages contain most current Support Package Stack enhancement packages contain most current Support Package Stack
Optional Activation
You activate the business functions you need.
Support
If activated:
- End-user training and regression testing is limited to the activated
business function(s)
Mandatory
pp
Packages
business function(s)
- Testing is simplified with templates, provided for every business
function
What Does This Mean for You?
Getting insight: Upgrade vs. Enhancement Package
Software upgrade before
Upgrade your system
Step 1
Technical upgrade
Step 2
Functional implementation
ERP
HR
ERP
APPL
Indus
Sol
__
NetWeaver New NetWeaver release
Managing Traditional Software Upgrades:
No options, All or None
Non-targeted software innovation
Heavy
Requires thorough regression testing for
t
Managing SAP Enhancement Packages:
Optional, Pick and Choose
Targeted software innovation
Li ht i ht
vs.
Lean software enhancement
Step 1
C
Step 2
Activate desired
customers Lightweight
Isolates testing effort for customers
Choose upgrade and install
business functions
ERP
HR
ERP
APPL
Indus
Sol
__
NetWeaver NetWeaver
No implication
Activate
No implication
How Does the Switch Framework Work?
Switch Framework
SAP ERP
With the Switch Framework it is now possible to control
the activation of SAP ERP objects
Individual business functions are activated via the Switch
(ECC 6.0)
Framework.
With SAP enhancement package 2 (now in Ramp-up)
there are ~50 optional business functions and 23
Enterprise Services
New/Improved Functionality
enterprise service bundles.
The Switch Framework is a proven concept (already used
to retrofit Industry Solutions in ERP 6.0)
Architectural
View
Repository
View
Package
Business
View
Switch 1
Business Function Set
Bus Fct F1
Bus Fct F2
Bus Fct F4
Business Function Set
Bus Fct F1
Bus Fct F2
Bus Fct F4
Industry Business Function Set
Media
Advertising Mgmt.
P Di t ib ti
Package
Screen
Element 1
Element 2
Switch 2
Switch 3 Bus Fct F4

Press Distribution
IMG-nodes
Package
Switch BC Set
Element 2
Enterprise Business Function
HCM, Administration
R l E t t
Switch 3
Switch 4
Switch 5
Switch n
Activated Objects
- Enhancements
- BC-Sets, IMG nodes
- Screen elements
Enhancement Package
Contains business functions that can
Switches
Switch can be activated by different
business functions. One switch can
Real Estate
Switch n

- Menu entries be optionally installed and activated activate more than one object.
ERP EhP TECHNOLOGY FACTS
LIFECYCLE OF SAP ENHANCEMENT PACKAGES
SAP R/3 Enterprise
Industry Solutions
SAP E t i
Architecture Software Components
SAP R/3
Enterprise Core (4.70)
SAP Enterprise
Extension Set
SAP_HR SAP_APPL
EA_HR EA_APPL EA_1 EA_2
..
SAP R/3 Enterprise
SAP Web
Application Server 6.20
SAP_ABA
SAP_BASIS
F t
p
(Ext. Set 1.10/2.00)
Facts
Innovation consumed via enterprise extension sets
Extension sets were innovations for an entire entity within
core (no concept of business functions)
All enterprise extensions were bundled together
Separate industry innovation
SAP ERP 6.0
Architecture Software Components
SAP ECC
EA_HR EA_APPL EA_1 IS_Oil
..
IS_1
SAP Netweaver
Application Server (7.00)
SAP ECC
Core (6.00)
SAP_HR SAP_APPL
SAP_ABA
SAP_BASIS
F t
Former SAP for Industry Add-Ons were integrated into ERP 6.0 as
SAP ERP (6.0)
Facts
o e S o dust y dd O s e e teg ated to 6 0 as
Industry Extensions
In the majority of the cases, one specific Industry Extension
represents one SAP Industry Solution represents one SAP Industry Solution
Industry Extensions are grouped by industry business function
sets and consist of one or more business functions (BF) which can
b ti t d t l be activated separately
It is not possible to activate business functions from different
industry business function sets at the same time
dust y bus ess u ct o sets at t e sa e t e
Enhancement Package 2 for SAP ERP (6.0)
Architecture
Software Components
EhP 1
EhP 2
SAP ECC
EA_HR EA_APPL EA_1
IS_Oil
..
IS_1
EhP 1
EhP 2
..
EA_HR
(602)
12
SAP Netweaver
Application Server (7.00)
SAP ECC
Core (6.00)
SAP_HR SAP_APPL
SAP_ABA
SAP_BASIS
F t
With SAP enhancement packages new Enterprise Business
SAP enhancement package 2 for SAP ERP (6.0)
Facts
With SAP enhancement packages new Enterprise Business
Functions AND Industry Business Functions are delivered
Customers can install Business Functions via the implementation
f t h i l hi h t i ABAP d ABAP of a technical usage, which can contain ABAP and non-ABAP
component versions and PI/EP/BI-content
Selective Installation: With SAP enhancement package
I t ll ti t ll ft t i ill b h d
1
Installation, not all software component versions will be changed
Selective Activation: You can select the required business function
1
2
SAP Application Software Lifecycle Introduction
Implementation/Installation
SAP R/3
Release Upgrade
1
3
SAP ERP (ECC 6.0)
SAP R/3
SAP R/3 Enterprise
SAP
S t System
Maintenance
2
Support Package Stack
Legal/Tax Changes, Corrections
Mandatory
Technically a set of Support Packages Technically a set of Support Packages
and patches
SAP Application Software Lifecycle Next Generation
Release Upgrade
SAP
S t System
Maintenance
2
Support Package Stack NEW: Enhancement Packages
New & improved functionality
Legal/Tax Changes, Corrections
Mandatory
Technically a set of Support Packages
New & improved functionality
Optional
Technically a set of new Software
Components grouped by Technical Usage
Technically a set of Support Packages
and patches
Components, grouped by Technical Usage
Activate new functionality via Business
Function
Per Business Function the installation of a
specific Technical Usage is required
Considerations for EhP Implementation Example
Possible implementation approaches
Apply latest Support Package Stack
Check Content of SAP
Enhancement Package
Check Content of SAP
Enhancement Package
Apply latest Support Package Stack Apply latest Support Package Stack
AND optionally
A) Complete Enhancement Package
B) Selected parts of Enhancement
Package
Apply latest Support Package Stack
AND optionally
A) Complete Enhancement Package
B) Selected parts of Enhancement
Package
Mar May
Jul Sep Nov
B A
Jan
Maximumuse Conservative use B A Maximum use Conservative use
Decouple technical installation from business innovation p
Install SAP enhancement package combined with Support Pack Stack as a
maintenance activity with only minor additional effort .
Enhancement Package Lifecycle
PLAN
1
Get an overview of available enhancements
Understand their potential business benefits
Discover
Evaluate & Decide Test & Go Live
2
Identify which ones are relevant for you
Evaluate & Decide Test & Go Live
5
Evaluate the relevant enhancements
Understand their particular benefit for you
Assess effort and impact of their implementation
Acceptance test using templates
End-user training where relevant
Go live
Activate & Configure Prepare & Install
4
3
Activate & Configure Prepare & Install
Download, load, and install
the relevant components
SPAU and Regression test
for the upgraded components
Check dependencies
Activate business functions
Configure new capabilities
for the upgraded components
BUILD
BUILD
Discover & Evaluate SAP Enhancement Packages
Enhancement Package Center
1 2
Enhancement Package Center
Single point of access to all
information related to a business
f ti function
Documentation
R l t Release notes
Dependencies
http://service.sap.com/ERP
Test catalogue
http://service.sap.com/ERP
Advantages for Customers
Documentation has greater level of granularity
Increased ability to analyze new software functionality
Easily identify needed Business Function(s)
Technical Details: Prepare & Install
Human Capital Management Talent Management Workforce Process Management Workforce Deployment
Customer wants to install Business Function: HCM, Administrative Services
3
Customer wants to install Business Function: HCM, Administrative Services
Implement Technical Usage HCM Administrative Services
Customer System
Landscape (As-Is)
HCM - Administrative Services:
Customer System
Landscape (To-Be)
SAP ECC 6.0
EA_HR
(600)
EA_APPL
(600)
EA_1
(600) ..
IS_1
(600)
SAP ECC 6.0
EA_HR
(602) SP00
EA_APPL
(600) SP 10
EA_1
(600)
IS_1
(600)
1. Plan
installation
with Mainten-
ance Optimizer
(SolMan)
SAP_HR
(600)
SAP_APPL (600)
(600) (600) (600)
SAP_ABA (700)
.. (600)
SAP_HR
(600) SP18
(602) SP00 (600) SP 10 (600) .. (600)
SAP_APPL (600) SP 10
SAP_ABA (700) SP12
(SolMan)
2. Install via:
- SAINT (ABAP)
SAP_BASIS (700)
SAP Enterprise Portal 7.0 SAP Enterprise Portal 7.0 SP12
SAP_BASIS (700) SP12
- JSPM (J2EE)
Technical Usage HCM, Administrativ Services: EA-HR 602 and Portal Content: BP for HR Administrator
Prerequisite: ERP SPS 10 (EA-HR/SAP HR SP 18, SAP APPL SP 10, NW SPS 12)
Prerequisite: ERP SPS 10 (EA HR/SAP_HR SP 18, SAP_APPL SP 10, NW SPS 12)
Appendix Appendix
E d - End -
SAP Certifications Related to SAP TechEd Topics
T i E L l C tifi t Titl S l ti B i Topic Exam Level Certificate Title Solution Basis
ABAP Professional SAP Certified Development Professional - ABAP System Interfaces with
SAP NetWeaver 7.0
SAP NetWeaver 7.0
ABAP Professional SAP Certified Development Professional ABAP System Interfaces with SAP NetWeaver 7 0 ABAP Professional SAP Certified Development Professional - ABAP System Interfaces with
SAP NetWeaver 7.0
SAP NetWeaver 7.0
ABAP Associate SAP Certified Development Consultant ABAP Dev with NetWeaver 2004 SAP NetWeaver 2004
ABAP Associate SAP Certified Development Associate ABAP with SAP NetWeaver 7.0 SAP NetWeaver 7.0
ADM Professional SAP Certified Technology Professional NetWeaver 7.0 Platform SAP NetWeaver 7.0
ADM Professional SAP Certified Technology Professional NetWeaver 7.0 Security SAP NetWeaver 7.0
ADM Associate SAP Certified Technology Associate SAP Web AS Platform with Oracle SAP NetWeaver 2004
ADM Associate SAP Certified Technology Consultant NetWeaver 7.0 SysAd with Oracle SAP NetWeaver 7.0
BI Associate Solution Consultant SAP NetWeaver 04s SAP BI SAP NetWeaver 7.0
E2E Associate SAP Certified E2E Application Management Expert Change Control Mgmt SAP NetWeaver 7.0
E2E Associate SAP Certified E2E Application Management Expert Root Cause Analysis SAP NetWeaver 7.0
Java Professional SAP Certified Development Professional JAVA with NetWeaver 7.0 SAP NetWeaver 7.0
Java Associate SAP Certified Development Associate JAVA with NetWeaver 7.0 SAP NetWeaver 7.0
MDM Associate SAP Certified Application Associate Master Data Management 5.5 (SP04) SAP NetWeaver 2004
SM Associate Solution Consultant SAP Solution Manager 4.0 Implementation Tools SAP NetWeaver 7.0
SOA Associate SAP Certified Associate Enterprise Architect Enterprise SOA
XI Associate Certification Development Consultant SAP NetWeaver 2004s SAP NetWeaver 7.0
For a complete listing of certifications, please go to
www sap com/services/education/certification
www.sap.com/services/education/certification
Copyright 2007 SAP AG. All Rights Reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p,
System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are
trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C
, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intended strategies developments This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments,
and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this
document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items
contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability,
fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the use of these materials This SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This
limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in
these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Managing Efficient Upgrades

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Managing Efficient Upgrades

Hochgeladen von

Copyright:

Verfügbare Formate

LCM200

Related SAP Education Training Opportunities

R l t d W k h /L t t SAP T hEd 2006

Related Workshops/Lectures at SAP TechEd 2006

Switch 3 Bus Fct F4

SAP AG 2007, SAP TechEd 07 / LCM200 / 124

, World Wide Web Consortium, Massachusetts Institute of Technology.

Das könnte Ihnen auch gefallen