ADM326
ADM326 SAP ECC Upgrade
SAP ECC Upgrade
SAP ECC 6.05
AS ABAP 7.02
BS 7i2010
(as part of SAP enhancement package 5 for SAP ERP 6.0)
(as part of SAP enhancement package 2 for SAP NetWeaver 7.0)
(Business Suite 7 Innovations 2010)
© SAP 2010
Material number: 50101086
Copyright
Copyright 2011 SAP AG. All rights reserved.
Neither this training manual nor any part thereof may
be copied or reproduced in any form or by any means,
or translated into another language, without the prior
consent of SAP AG. The information contained in this
document is subject to change and supplement without prior
notice.
All rights reserved.
© SAP 2010
Trademarks:
Microsoft ®, Windows ®, NT ®, PowerPoint ®, WinWord ®, Excel ®, Project ®, SQL-Server ®,
Multimedia Viewer ®, Video for Windows ®, Internet Explorer ®, NetShow ®, and HTML Help ®
are registered trademarks of Microsoft Corporation.
Lotus ScreenCam ® is a registered trademark of Lotus Development Corporation.
Vivo ® and VivoActive ® are registered trademarks of RealNetworks, Inc.
ARIS Toolset ® is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrücken
Adobe ® and Acrobat ® are registered trademarks of Adobe Systems Inc.
TouchSend Index ® is a registered trademark of TouchSend Corporation.
Visio ® is a registered trademark of Visio Corporation.
IBM ®, OS/2 ®, DB2/6000 ® and AIX ® are a registered trademark of IBM Corporation.
Indeo ® is a registered trademark of Intel Corporation.
Netscape Navigator ®, and Netscape Communicator ® are registered trademarks of Netscape
Communications, Inc.
OSF/Motif ® is a registered trademark of Open Software Foundation.
ORACLE ® is a registered trademark of ORACLE Corporation, California, USA.
INFORMIX ®-OnLine for SAP is a registered trademark of Informix Software Incorporated.
UNIX ® and X/Open ® are registered trademarks of SCO Santa Cruz Operation.
ADABAS ® is a registered trademark of Software AG
The following are trademarks or registered trademarks of SAP AG; ABAP/4, InterSAP, RIVA, R/2,
R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript,
SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and
ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included
herein are also trademarks or registered trademarks of SAP AG.
Other products, services, logos, or brand names included herein are trademarks or registered
trademarks of their respective owners.
Course Prerequisites
Required Knowledge
Knowledge of SAP system administration
Basic knowledge of database and operating system administration
Recommended Knowledge
ADM100 Administration AS ABAP I
ADM325 Software Logistics AS ABAP
Target Audience
This course is intended for the following audiences:
SAP system administrators
Technology consultants
Project team leads
Duration: 5 days
User notes
These training materials are not a teach-yourself program. They complement the explanations
provided by your course instructor. Space is provided on each page for you to note down
additional information.
There may not be sufficient time during the course to complete all the exercises. The exercises
provide additional examples that are covered during the course. You can also work through
these examples in your own time to increase your understanding of the topics.
Course Goals
This course will prepare you to:
plan and implement upgrades for SAP systems
Course Objectives
After completing this course, you will be able to:
plan and implement upgrades for SAP systems
Agenda
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
Agenda: Concept and Architecture
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
1-1
Concept and Architecture
Contents:
Why and when should a customer upgrade a productive system?
Overview of different releases
Products and terms used in the context of an upgrade
Upgrade
New Release
Old Release
© SAP AG
ADM326
1-2
The SAP Business Suite: Process Excellence
to Reduce Cost and to Capture Opportunities
Embedded
analytics
Harmonized UI across
applications and
processes
For business insight
and control
For increased
end user
productivity
SOA enablement
SAP Business Suite
For process flexibility
and business agility
SAP NetWeaver
Composition
Industry Applications
For process
integrity and
increased business
and IT efficiency
Continuous innovation
for every line of
business in all industries
For improved performance
SAP SRM
SAP CRM
SAP SCM
SAP PLM
Supplementary Applications
SAP NetWeaver
Integration
Best-Run Now
Packages
Fast deployment and
quick ROI to address
priorities in current
economy
EHP
SAP ERP
EHP
Value Scenarios
Enhancement
packages: ‘Nondisruptive’
innovation for
the SAP
Business Suite
For faster
innovation with
lower TCO
Industry Best Practices
For improved business
performance in core
processes
The SAP Business Suite consists out of SAP ERP, SAP CRM, SAP SCM, SAP SRM and SAP PLM
SAP ERP consists out of ECC, XSS, XECO, BW, Portal, PI and many more. These are upgradeable
units.
You can not upgrade (to) SAP ERP in general. You can upgrade (to) ECC or XSS and so on.
© SAP AG
ADM326
1-3
Technology
Application
Apples and Pears
© SAP 2008
Here you can see a brief overview about the evolution of the SAP ERP architecture.
With SAP R/3 4.6 and SAP R/3 Enterprise 4.7 the SAP Web Application Server (former 'Basis')
based on ABAP was the foundation of the ERP applications. There was no SAP NetWeaver (as a
name), the SAP industry solutions were add-ons on top of the core applications. SAP started to
support Unicode with SAP R/3 Enterprise 4.7.
Since SAP R/3 Enterprise 4.7 SAP developed new applications and shipped them as Enterprise
Extensions. A concept which was based on smaller software packages to deliver new functionality to
customers.
With SAP ERP 6.0 SAP provides a solution which is built on top of SAP NetWeaver, e.g the SAP
NetWeaver Portal can be leveraged as a unified User Interface (UI) for all applications, also the SAP
Business Warehouse (SAP BW) and SAP Process Integration are integral parts of SAP’s ERP
solution. The application was also enhanced tremendously, with SAP ERP most industry solutions
became part of the application plus new functionality is ready to use. Due to the new Enhancement
Framework introduced with SAP NetWeaver Application Server ABAP 7.0 it was possible to ship
new functionality in a more granular way. These new functions are now included in the enhancement
packages.
© SAP AG
ADM326
1-4
SAP ERP 6.0 – Components
Overview of SAP ERP 6.0 Components
ERP 6.0 MG Chapter 3
ABAP Components - The ABAP components of SAP ERP 6.0 consist of the:
SAP ERP Central component (SAP ECC), the SRM Server, as well as different ABAP-based
add-on components.
Technical component BI Content. This includes the content required to install the usage type
Business Intelligence and is always installed in addition.
Java Components - Java components include:
General Java web applications; content packages for the usage type Portal or usage type PI (XI)
These components are always installed in addition to an instance of the usage type Portal or a
deployment of PI (Exchange infrastructure). The components included in Java web applications are
independent J2EE components, combined into a single installation tool as a product instance SAP
XECO. Therefore, if you want to install one or more of these components, you will require Java
components for an ERP installation, which is done by the SAPinst tool.
Additional Components - Additional components include the mobile functions of SAP ERP, for
example, mobile time and travel components and mobile asset management. Furthermore, the
relevant front-end components are considered as additional components.
Depending on the key capabilities or business processes you intend to deploy, you install the add-ons
shown explicitly within the frame Additional Components.
Industry Add-Ons - most former industry solution add-ons are integrated into SAP ECC.
© SAP AG
ADM326
1-5
SAP Enhancement Packages & SAP ERP 6.0
2006
2012+
Quick Facts About SAP ERP 6.0
Enhancement Packages
Launched in June 2006
Platform upon SAP will deliver future
2008
2010
software innovations via ‘SAP enhancement
packages’
SAP ERP 6.0
SAP enhancement package 5 for SAP ERP
6.0 generally available in 2011
SAP NetWeaver
SAP Business Suite - Stable Core
What are enhancement packages?
Optionally installed and activated software innovations for SAP ERP 6.0
Software innovations include
UI simplifications
Functional enhancements
Enterprise services
Cumulative: current enhancement package contains all functionalities of previous packages
Enhancement packages are not Support Packages: Support Packages contain corrections and legal
changes, SAP enhancement packages new functionality
SAP enhancement packages for SAP ERP include functional enhancements, industry-specific
enhancements and simplifications. To discover and evaluate which innovations are shipped in which
SAP enhancement package, visit the SAP Service Marketplace. In addition, enterprise services (ES)
bundles are delivered with SAP enhancement packages. Each ES bundle comprises a set of
enterprise services to support an end-to-end business process (for example Order to Cash) across the
SAP Business Suite.
From a functional perspective SAP enhancement packages are cumulative: each current SAP
enhancement packages contain the entire content of earlier packages. So each SAP enhancement
package is based on the previous one. SAP enhancement packages have the same maintenance
duration as the underlying core application, SAP ERP 6.0. As before, all legal changes and
corrections will be available via Support Packages. SAP provides Support Packages for SAP ERP
6.0 on a regular basis during the defined maintenance period and, in parallel, in the equivalent
Support Packages for SAP enhancement packages for SAP ERP.
Since Business Suite 7 Innovation 2010 (BS 7i2010) SAP enhancement packages also exist for SAP
CRM, SAP SCM, and SAP SRM.
© SAP AG
ADM326
1-6
R/3/R/3 Enterprise/ECC Releases
Basis functionality
(SAP Basis/SAP Web AS/
SAP NetWeaver AS)
Part of
SAP NetWeaver
2004 ('04)
7.0 (2004s)
7.0
7.0
7.0
7.0 EHP1
7.0 EHP2
7.3
4.6C
4.6D
6.10
6.20
6.30
6.40
7.00
7.00
7.00
7.00
7.10
7.01
7.02
7.11
7.30
Main business functions
(-/Core)
4.6C
4.7
4.7
5.0
6.0
(6.01)
(6.02)
(6.03)
(6.04)
(6.05)
-
Additional business
functions
(-/Extension Set)
1.10
2.00
5.00
6.00
(6.01)
(6.02)
(6.03)
(6.04)
(6.05)
-
Part of
SAP ERP
2003
2003
2004
6.0 (2005)
6.0 EHP1
6.0 EHP2
6.0 EHP3
6.0 EHP4
6.0 EHP5
-
Releases 4.0A, 4.5A and 4.6A are missing. These were only versions for controlled availability
(CA).
No SAP R/3 release exists for SAP Basis/SAP Web AS/SAP NetWeaver AS 4.6D, 6.10 and 7.10.
Concerning the ABAP part, SAP Web AS 6.30 is the same as SAP Web AS 6.20.
Several renaming took place in the past; here are a few of them:
SAP R/3 was renamed to SAP R/3 Enterprise beginning with 6.20/4.7/1.10
SAP R/3 Enterprise was renamed to SAP Enterprise Resource Planning Central Component (SAP
ECC) beginning with 6.40/5.0/5.00
SAP Basis was renamed to SAP Web Application Server ABAP (SAP Web AS ABAP) beginning
with 6.10
SAP Web Application Server was renamed to SAP NetWeaver Application Server ABAP beginning
with 7.00
Starting from ECC 6.01 the new releases are called enhancement packages.
The brackets starting from 6.01 indicate, that not all software components have to be on this release
level.
© SAP AG
ADM326
1-7
SAP R/3 4.6C
Modification free
add-on,
Plug In, Y2K check,
and many others
SAP R/3 4.6C
Add-On
Modifying
add-on,
IS-U, IS-Oil, and
many others
Add-On
SAP_APPL 4.6C
SAP_HR 4.6C
Core applications
ABAP 4.6C
SAP_ABA
Basis, including
TMS,
performance tools,
development tools,
user administration,
and many more
SAP_BASIS 4.6C
The software components of an SAP R/3 4.6C remain more or less as they are up to the latest release
ECC 6.05. But during the releases these software components were updated and new software
components were added.
The figures do not show a complete list of all software components.
© SAP AG
ADM326
1-8
SAP R/3 Enterprise 4.7x2.00
SAP R/3 4.7
Add-On
Enterprise Extensions
EA-APPL,
EA-HR,
and others
EE
2.05
Add-On
EE
2.00
EE
2.05
EE
2.00
SAP_APPL 4.7
SAP_HR 4.7
ABAP 6.20
SAP_ABA
Basis is now called
SAP Web AS ABAP
SAP_BASIS 6.20
The Enterprise Extensions were introduced with R/3 Enterprise 4.7. They should help to change the
core software components SAP_APPL and SAP_HR as less as possible, in order to keep them stable
and to simplify upgrades for customers.
The Basis was renamed.
© SAP AG
ADM326
1-9
SAP ECC 6.0
Industry Extensions
IS-UT,
IS-Oil,
and others
SAP ECC 6.0
Add-On
EE
6.05
Add-On
EE
6.00
EE
6.00
EE
6.00
IE
6.00
IE
6.00
SAP_APPL 6.00
IE
6.00
IE
6.00
SAP_HR 6.0
ABAP 7.00
SAP_ABA
Basis is now called
SAP NetWeaver
AS ABAP
SAP_BASIS 7.00
Former SAP for Industry Add-Ons were integrated into SAP ECC 6.0 as Industry Extensions.
Industry Extensions are grouped by industry business function sets and consist of one or more business
functions (BF) which can be activated separately.
It is not possible to activate business functions from different industry business function sets at the same time.
The Switch Framework (SFW) allows you to externally control the visibility of Repository objects or
their components by means of switches. The main purposes of the Switch Framework are to:
Simplify an ABAP-based system landscape by adopting one or more industry solutions in a standard
system
By using the Switch Framework, most industry solutions and a restricted list of repository objects are
delivered in an inactive state in the system. You no longer need to install an industry solution – you can
activate it when required.
Introduce a new, modification-free enhancement concept
The Switch Framework is integrated in the ABAP Workbench and works closely together with the
Enhancement Framework.
The Enhancement Framework enables the implementation of the best-practice solutions defined within an
industry, while the Switch Framework controls which enhancement implementations are to be performed.
The Switch on industry solutions and Enterprise Add-Ons
Develop new functions without affecting the existing ones
Enhance delivered partner and customer systems by adding functions in the context of the Enhancement
Framework
The Basis was renamed again.
© SAP AG
ADM326
1-10
SAP ECC 6.05 (Example)
SAP ECC 6.05
Add-On
EE
6.05
Add-On
EE
6.00
EE
6.05
EE
6.00
IE
6.05
IE
6.00
SAP_APPL 6.05
IE
6.00
IE
6.00
SAP_HR 6.0
ABAP 7.02
SAP_ABA
Some software
components
are on 6.0,
some are on 6.05
SAP_BASIS 7.02
With SAP enhancement packages new Enterprise Business Functions and Industry Business
Functions are delivered.
Customers can install Business Functions via the implementation of a technical usage, which can
contain ABAP and non-ABAP component versions and PI/Portal/BW-content .
Selective Installation: With SAP enhancement package Installation, not all software component
versions will be changed, but only those selected.
Selective Activation: You can select the required business function within an SAP ECC system
© SAP AG
ADM326
1-11
SAP ECC 6.0 and above: Industry and
Enterprise Extensions
Industry Extensions
Consist of Business Functions Sets (BFS) and Business Functions (BF)
Activated per Switch Framework
Only ONE Industry Extension can be activated per SAP system
Cannot be deactivated once it has been activated (no switch to another industry
extension possible)
Activation of one or more Business Functions (BFS and BF) per SAP system possible
See note 838003 for further information
Enterprise Extensions
Parts of former industry solutions were integrated in Enterprise Extensions
Consist of Generic Business Functions
Activation of all Enterprise Extensions by the SAP Switch Framework
The Enterprise Extensions are available in addition to the Industry Extensions
Activation of one or more Enterprise Extension per SAP system possible
Activation of more than one generic business function of the Enterprise Extension at the
same time possible
See note 838002 for further information
Examples for Industry Extensions (see note 838003 and ERP 6.0 master guide for detail
information):
ECC-DIMP, DIMP, DI, IS-SW, IS-HT, IS-MP, IS-AD, IS-A is now included in Software component
ECC-DIMP = 'Discrete Industries & Mill Products'
INSURANCE is now included in Software component INSURANCE = 'Insurance'
IS-U/CCS, ISUCEN and IS-U/I is now included in Software component IS-UT
Examples for Enterprise Extensions (see note 838002 and ERP 6.0 master guide for detail
information):
BANKING, BANK/CFM, TR-TM-PO are now included in Extension EA-FINSERV
EHS is now included in Extension EA-APPL
PI and PI-A are now included in Extension SAP_APPL and SAP_HR
General information about available industry solutions and how they are deployed within ERP 6.0
ERP 6.0 Master Guide
Note 838002 for Enterprise Extension overview
Note 838003 for Industry Extension overview
© SAP AG
ADM326
1-12
Activation of Industry and Enterprise
Extensions
Switch Framework:
Transaction SFW5
Via the Switch Framework (transaction SFW5) Business Functions Sets can be activated.
© SAP AG
ADM326
1-13
"Switchable" Industry Solutions in
SAP ECC 6.0
Exclusive Activation
Multiple Activation
SAP ECC Industry Extension Healthcare 6.0
SAP ECC Enterprise Extension Consumer Products 6.0
SAP ECC Industry Extension Chemicals 6.0
SAP ECC Enterprise Extension Defense Forces & Public Security 6.0
SAP ECC Industry Extension Contract Accounting 6.0
SAP ECC Enterprise Extension Financials 6.0
SAP ECC Industry Extension Discrete Industries & Mill Products 6.0
SAP ECC Enterprise Extension FERC: Regulatory Reporting 6.0
SAP ECC Industry Extension Insurance 6.0
SAP ECC Enterprise Extension Financial Services 6.0
SAP ECC Industry Extension Media 6.0
SAP ECC Enterprise Extension Global Trade 6.0
SAP ECC Industry Extension Mining 6.0
SAP ECC Enterprise Extension Human Capital Management 6.0
SAP ECC Industry Extension Oil & Gas 6.0
SAP ECC Enterprise Extension Incentive & Commission Management 6.0
SAP ECC Industry Extension Public Services 6.0
SAP ECC Enterprise Extension Industry-specific Sales Enhancements 6.0
SAP ECC Industry Extension Retail 6.0
SAP ECC Enterprise Extension Joint Venture Accounting 6.0
SAP ECC Industry Extension Telecommunications 6.0
SAP ECC Enterprise Extension PLM 6.0
SAP ECC Industry Extension Utilities, Waste & Recycling 6.0
SAP ECC Enterprise Extension Public Sector Management 6.0
SAP ECC Enterprise Extension Retail 6.0
SAP ECC Enterprise Extension SCM 6.0
Single Activation
SAP ECC Enterprise Extension Travel Management 6.0
Multiple Usage
You can activate multiple Enterprise Extensions but only one Industry Extension at the most.
© SAP AG
ADM326
1-14
Upgrade as a Project –
Discover, Evaluate & Implement
Upgrade Project
completed
Upgrade Project
started
Plan
Upgrade
Discovery
Define Business and IT
requirements
Run
Build
Upgrade
Evaluation
Upgrade Implementation
Define
strategy
Operations &
Continuous
Improvement
Minimize costs
and risks of Upgrade Project
Upgrade Roadmap
Project
Preparation
Document current
solution and set-up
project
Blueprint
Specify
implementation
scope and solution
adjustment needs
Realization
Implement and
adjust solution
Final Preparation
for Cutover
Perform integration
and system tests
and plan cutover
Production
Cutover &
Support
Execute production
system Upgrade &
Support
An upgrade of a productive ECC system is not done at one weekend. But it is a whole project, that
lasts for months.
© SAP AG
ADM326
1-15
Upgrade to SAP ECC 6.05 (part of SAP
enhancement package 5 for SAP ERP 6.0)
Upgrade to SAP ECC 6.0 including SAP Enhancement Package 5 possible from…
SAP ERP 6.0 + EHP 5
Industry add-ons integrated into
SAP ECC 6.0 (see SAP Note 838003)
SAP ECC DIMP
SAP XECO
SAP XSS
SAP IS-CWM
5.0
Target
SAP ECC 6.0
2.0
Non industry add-ons integrated into
SAP ECC 6.0 (see SAP Note 838002)
SAP SEM
EHP 5
SAP LEARNING SOLUTION
2.00
SAP DIMP
SAP DI
SAP IS-U/CCS
SAP VADM
4.71
4.6C2
472
471
464
461
3.00
2.05
SAP IS-AD
SAP IS-EC
3.0B
3.0B
2.0B
SAP IS-HT
4.61
SAP WASTE AND RECYCLING
4.72
SAP PUBLIC SECTOR PSCD
4.6C1
2.0B
1.0B
4.72
4.71
4.64
SAP IS-HER-CM
4.72
4.71
4.64
SAP PATIENT MANAGEMENT
SAP IS-OIL
4.72
4.63B
4.72
4.6C
4.6B
4.0B
SAP INSURANCE
FS-CD
FS-CM
FS-CS
4.72
4.71
4.64
4.61
4.51
4.72
4.71
4.64
4.72
4.71
4.64
SAP IS-T
472
471
464
461
4.6C
4.6B
4.5B
4.1B
SAP EH&S
4.62
4.61
4.02
2.2B/2.7B/4.6C
2.2B/2.7B/4.6B
2.2B/2.7B/4.5B
SAP PLM RECIPE MANAGEMENT
2.1
1.0
SAP HR-PS
SAP BANKING
4.62
4.61
4.52
4.63
4.61
4.03
SAP IS-MINE
SAP CFM
2.0
SAP R/3 ENTERPRISE
4.6C
4.6B
47X200
47X110
SAP IS-M
472
471
464
402
471
463
461
SAP IS-PS-FM
SAP JVA
SAP IS-MP
SAP IS-U/FERC
SAP FI-CA
4.72
4.71
4.64
SAP R/3
SAP ECC
SAP PH-ELR
5.0
4.6C
SAP ERP 2004
4.6C
SAP PLM ADDON
4.6C
This overview shows all possible start releases for the upgrade to SAP ECC 6.05 (SAP enhancement
package 5 for SAP ERP 6.0, Business Suite 7 Innovations 2010).
SAP offers for all industry solutions an upgrade path to SAP ECC 6.0.
The smallest start release for the upgrade to SAP ECC 6.0 without an enhancement package is SAP
R/3 3.1I
Beginning of Service Release 3 for SAP ECC 6.0 the smallest start release is SAP R/3 4.0B.
Since SAP enhancement package 3 for SAP ERP 6.0 together with Service Release 3 for SAP ERP
6.0, it is possible to include parts of the enhancement package into the upgrade procedure.
Beginning with ECC 6.05 the smallest start release is SAP R/3 4.6C.
© SAP AG
ADM326
1-16
Possible Upgrade Approaches:
Think Big And Start Small
…are large projects…
…but with progressive scope !
Technical Upgrade
Affecting the whole
enterprise
Demanding in-depth
knowledge of
Fast
Business models
Processes
Application landscapes
Low costs
and manageable
impact
Application modification
New
Functionality
Protect
investment
Requiring strict planning
and precise timing
Take your
time
Generate
value
as you go
Serviceoriented
architecture
Discover,
prepare
and
get even
more
value
Think BIG and start SMALL!
Technical Upgrade: Reduction of Modifications
Eliminate modification not used: Up to 80% of all modification
Replace modification with standard functionality: Up to 50% of all modifications
Technical and functional optimization: Archiving, master date clean-up, interface optimization
Functional: Focus
Modernization of the Core SAP ERP, Stabilization of the basis
Individualization of the user interface
Strategic: Focus
Standardization
Harmonization
Consolidation
© SAP AG
ADM326
1-17
Customer Feedback - Main Reasons to
Upgrade / not to Upgrade to SAP ECC 6.0
Why Upgrade
End of standard/
Extended maintenance
Why not
Conflicting business
priorities
62%
Use of latest technology
enhancement packages
42%
End of old hardware servers
41%
Empowering new business
(SOA)
40%
Time and effort to upgrade
38%
No business case
27%
Lack of project resources
25%
24%
Replacing custom
development
21%
Achieve enhance user
experience
20%
Thorough implementation
of function enhancements
20%
Consolidation of system
landscape
17%
Too costly
23%
Still receiving maintenance
for current release
22%
Do not understand value of
SAP ERP 6.0
17%
Legal compliance
13%
Higher number of
modifications
Replacement of modifications
11%
Other
9%
Too much downtime involved
to upgrade
8%
Others
N=1484
6%
13%
N=994
The report include answers from the following 360° Upgrade adoption programs: North America (Jan 2008), Brazil (March 2008), Germany (March 2008), Japan
(March 2008), UK & Ireland (March 2008), Australia (April 2008), Sweden (April 2008),China (May 2008), India (May 2008) and France (Sept 2008)
Results of the worldwide customer surveys in 2008 on Upgrade adoption programs
© SAP AG
ADM326
1-18
Upgrades to SAP ERP 6.0:
Satisfaction with Upgrade Approach
SAP R/3
Enterprise
based on 83 upgrades
SAP R/3
4.6C
based on 152 upgrades
Almost all customers were satisfied or more than satisfied with the upgrade to SAP ECC 6.0
Source: Customer Experience Database
© SAP AG
ADM326
1-19
Upgrades to SAP ERP 6.0:
Approach in Upgrades by Source Release
Definitions:
1 Technical upgrade
SAP R/3
Enterprise
Limited impact in
business processes
May include the
elimination of unused
modifications
based on 83 upgrades
2 New functionality
Technical upgrade
with subsequent
functional enhancements
3 Service Oriented
SAP R/3
4.6C
Architecture (SOA)
Technical upgrade with
functional enhancements
and subsequent SOA
adoption
based on 154 upgrades
In most landscapes the upgrade to SAP ERP 6.0 represents the first step to create a stable and
modern core before.
Most customers follow the recommended tree-step-approach by executing a technical upgrade first
before implementing new functionality delivered with SAP ERP 6.0 and preparing a service-oriented
architecture.
© SAP AG
ADM326
1-20
Solution Changes - New 7-2 Maintenance
Strategy
7-2 maintenance strategy for new releases of the core applications* of
SAP Business Suite: 7 years of mainstream maintenance, 2 years of extended
maintenance
7
New
EHP**
SAP CRM 7.0,
SAP SCM 7.0,
SAP SRM 7.0
EHP**
EHP**
EHP**
RampUp
EHP**
EHP**
Mainstream Maintenance
EHP**
EHP**
EHP**
RampUp
2006
EHP**
2008
Extended Maint.
(+ 2%)*
Cust.-Spec.
Maintenance
Dec
Dec
2009
2010
EHP**
2011
2012
2009
2013
2014
2015
2016
2017
EHP**
Ext. Maint.
(+ 2%)*
Mainstream Maintenance
2007
Cust.-Spec.
Maintenance
2010
2011
2012
Ext. Maintenance
(+ 4%)*
2013
2014
Cust.-Spec.
Maintenance
Mar
SAP ERP 6.0, SAP
NetWeaver 7.0
2008
Mar
Before
2007
Mar
2006
Extended Maint.
(+ 2%)*
EHP**
Mainstream Maintenance
Nov
SAP ERP 6.0, SAP
NetWeaver 7.0
EHP**
RampUp
2
2015
2016
2017
* 7-2 strategy applies to new releases of the core applications of SAP Business Suite, starting with SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0, SAP PLM 7.0; plus SAP ERP 6.0 (EHP4)
and SAP NetWeaver 7.0. Industry-specific add-on applications and SAP enhancement packages based on these core application releases will offer mainstream and extended maintenance
in line with these releases.
** Enhancement packages: Illustrative only; does not reflect exact shipment times and frequency.
In November 2008 SAP introduced the 7-2 maintenance strategy for new core application releases
introduced and shipped to customers after this point in time.
In particular, for SAP CRM 7.0, SAP SCM 7.0, SAP SRM 7.0, and SAP PLM 7.0, SAP will offer
mainstream maintenance to December 2015, and extended maintenance for two additional years to
December 2017.
In parallel, maintenance for SAP ERP 6.0 and SAP NetWeaver 7.0 will also be adapted to this new
strategy, meaning that mainstream maintenance for these releases is extended from March 2013 to
December 2015; extended maintenance will be offered to December 2017.
Main advantages of this new strategy:
Long-term planning security and higher return on investment – nine years’ maintenance horizon
Additional time to deploy and benefit from innovation delivered via enhancement packages
Less additional cost for extended maintenance
© SAP AG
ADM326
1-21
Solution Changes – SAP Release Strategy
Release and maintenance strategy SAP ERP
Ext. Maint.
(+ 2%)*
Ext. Maintenance
(+ 4%)*
Ext. Maintenance
(+ 4%)*
Customer-Specific
Maintenance
Customer-Specific
Maintenance
Customer-Specific
Maintenance
As of January 01, 2009, extended
maintenance for SAP R/3 4.6C and
SAP R/3 Enterprise 4.7 is included
in SAP Enterprise Support and
extended by one year
2009
Dec
Mar
Dec
Mar
2010
2011
* Overall payment is SAP support fee plus additional fee of 2% or 4% of the maintenance base per year.
** SAP ERP 6.0 is the application release formerly known as mySAP ERP 2005.
Mar
2008
Mar
2007
Mar
Dec
Customer-Specific
Maintenance
Dec
Jun
2006
New 7-2 maintenance
strategy for SAP ERP 6.0:
Customer-Specific
Maintenance
Extended maintenance (no add. fee,
included in SAP Enterprise Support contract)
Ext. M.
(+ 4%)*
Customer-Specific
Maintenance
Extended maintenance (no add. fee,
included in SAP Enterprise Support contract)
Mainstream Maint.
Ext. Maint.
(+ 2%)*
Ext. Maintenance
(+ 4%)*
Cust.-Spec.
Maint.
2012
2013
Dec
Mainstream Maint.
SAP R/3
4.6C
SAP R/3
3.1I – 4.6B
Ext. Maint.
(+ 2%)*
Mainstream Maintenance
Dec
mySAP ERP
2004
SAP R/3
Enterprise
47x110, 47x200
Ext. Maint.
(+ 2%)*
Mainstream Maintenance
SAP ERP 6.0**
2014
2015
2016
2017
This strategy is also valid for all industry-specific add-on
applications and SAP enhancement packages for SAP
ERP based on the releases above.
According to SAP customer surveys, the SAP release and maintenance strategy is an important
driver for upgrades, particularly, for older releases (see SAP Upgrade Experience Database).
The above picture shows the current maintenance strategy for SAP ERP. Information for other SAP
products is provided in the SAP Service Marketplace under alias /maintenance.
© SAP AG
ADM326
1-22
Summary
© SAP AG
“
Business is the driver for change
“
Every solution is different
“
Benefit from SAP enhancement package concept
Early involvement
and commitment of business
stakeholders is key success factor for every IT change
projects
Take the time to analyze your situation and to create your
own solution transition roadmap
improve your TCO and get faster access to innovation
ADM326
1-23
SAP ERP 6.0 Solution Information –
Resources (1/2)
Access to Upgrade information
www.sap.com: Solutions
www.sap.com: Services
SAP ERP Info Center
http://service.sap.com/erp
SAP Upgrade Info Center
http://service.sap.com/upgrade
SAP Enhancement
Package Info Center
http://service.sap.com/erp-ehp
SAP Community Network
www.sdn.sap.com/irj/sdn
Solution browser tool
http://erp.fmpmedia.com/
© SAP AG
Public websites containing marketing content and high-level
information: http://www.sap.com/solutions/index.epx,
http://www.sap.com/services/programs/erpupgrade/index.epx
Access to all information/assets regarding SAP ERP 6.0
Access to upgrade specific information
Access to all information/assets concerning the
enhancement packages for SAP ERP 6.0
Access to technical (SDN) and business process information
(BPX), weblogs, forums, and Wiki (login required)
ERP solution browser tool for SAP ERP 6.0
ADM326
1-24
SAP ERP 6.0 Solution Information –
Resources (2/2)
Release Notes
Access to Upgrade Information
http://service.sap.com/release
notes
SAP Help
http://help.sap.com/
Scenario & Process
Component List
http://service.sap.com/scl
Solution Maps
http://service.sap.com/bmet
ERP Learning Maps
http://service.sap.com/rkt
Upgrade Course Finder
© SAP AG
Fairy detailed information on news/changes within ECC 6.0
up to EHP3
Access to library with complete documentation and
description of the solutions (technical and functional for each
release)
Access realization alternatives for SAP Solutions, business
scenarios, and processes
Blueprints visualizing how various processes are covered.
Offer drill down from Solution Area/Key Capabilities to
Business processes also providing configuration variants
and partly Business Scenario Maps showing possible value
potential
High level evaluation of functionalities running best with SAP
ERP 6.0 in terms of ease/speed of implementation and
possible innovation potential
Access to upgrade related trainings by SAP Education:
http://www.sap.com/services/education/catalog/erp/coursefinder.epx
ADM326
1-25
© SAP AG
ADM326
1-26
Agenda: Sequence and Major Steps
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
2-1
Sequence and Major Steps
Contents:
Identify the different types of documentation
Describe the structure and content of the Upgrade Guide
Use the Upgrade Guide more effectively
© SAP AG
ADM326
2-2
The Main SAP Documentation Types
Implementation
Operation
Upgrade
SAPterm
SAP Library
Upgrade Master Guide
Master Guide
Describes the
upgrade
Provides you
with additional
information
Component
Upgrade Guide
Component
Installation Guide
Intended for system
administrator with
knowledge of:
Security Guide
Configuration
Documentation
Release Notes
Implementation Guide (IMG)
Delta and Upgrade IMG
Solution Management Guide
Operating
system
Database
SAP Basis/
SAP Web
AS/SAP
NetWeaver AS
SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 languages.
The SAP Library is a collection of function- and process-oriented docu for SAP components.
The Implementation Guide (IMG) is a tool for configuring the SAP system to meet customer
requirements. Its structure and documentation are component-oriented.
The Security Guide describes the settings for a medium security level.
The Master Guide is the starting point for implementing an SAP solution. It lists the required SAP
components, and third-party applications that are required for each Business Scenario.
The Component Installation Guide describes the technical implementation of an SAP component.
The Configuration Documentation in SAP Solution Manager is a tool with various functions, one of
its main functions being the configuration of SAP solutions and Business Scenarios.
The Solution Management Guide is the starting point for operating an SAP solution. The guide refers
users to the tools and documentation that are needed to carry out various tasks, such as monitoring,
backup / restore, master data maintenance, transports, and tests.
Upgrade Master Guide is the starting point for upgrading the Business Scenarios of an SAP solution.
It provides scenario-specific descriptions of preparation, execution, and follow-up.
The Component Upgrade Guide describes the technical upgrade of an SAP component.
Release Notes are documents that contain short descriptions of new features or changes in an SAP
component since the previous release.
© SAP AG
ADM326
2-3
The Upgrade Documentation:
Upgrade Guide + Troubleshooting and Admin.
© SAP AG
ADM326
2-4
The five major Technical Steps
Needed Technical Usages of SAP
Enhancement Package 5 for SAP
ERP 6.0 and corresponding SAP
Support Packages
1
Solution Manager: select target release
2
SAP Notes: pre Upgrade steps
Upgrade Guide: pre Upgrade steps
ASU Toolbox: pre Upgrade steps
See Upgrade Guide
3
SAPup: preparational steps
SAPup: resolving negative checks
Roadmap steps 1 - 4
4
SAPup: Upgrade
Roadmap steps 5 - 8
5
SAP Notes: post Upgrade steps
Upgrade Guide: post Upgrade steps
ASU Toolbox: post upgrade steps
SAP Note 1000009
See Upgrade Guide
SAP Note 1000009
© SAP 2010
The technical upgrade procedure can be described with these five major steps. The slides of this
chapter refer to these steps.
© SAP AG
ADM326
2-5
Upgrade Guide + Troubleshooting and
Administration
Upgrade Guide
1.3.3 SAP Notes for the Upgrade
(part of)
1
2 Quick Guide
(part of)
2
3 Planning
3
4 Preparation
4
5 Upgrade Process
5
6 Follow-Up Activities
(part of)
Troubleshooting and
Administration
© SAP AG
2 Troubleshooting
3 Administration
ADM326
2-6
Upgrade: Quick Guide
Step by step list to
perform the Upgrade
(Extract)
(part of)
1
(part of)
2
3
4
(part of)
© SAP AG
ADM326
5
2-7
Upgrade Tools with SAP NetWeaver AS 7.02
3
Main Upgrade tool, that helps preparing the Upgrade by checking for problems and
configuring the software components for the upgrade and performs the actual upgrade
4
Tool, that simplifies handling of the
upgrade by providing a multi-functional
user interface
SAPup
Upgrade
Controller
Upgrade
Front-end
SAP Software Delivery Tool (SDL)
Tool from Upgrade Front-end, that
shows the progress of the current
roadmap step
Upgrade
Monitor
The SAPup is the main Upgrade tool. Starting with Upgrades to SAP ECC 6.04 it includes the
functionality of the former PREPARE and the steps of the actual Upgrade process.
Starting with Upgrades to SAP ECC 6.04 also a new design is introduced.
The Upgrade Assistant is a graphic-based tool which has been available since upgrades to SAP R/3
4.6.
The Upgrade Monitor is a feature of the Upgrade Assistant.
With upgrades to AS ABAP 7.01 the Upgrade Assistant has a new look and feel.
The Upgrade Monitor has a new design and no more progress bar for the running phase starting with
upgrades to AS ABAP 7.01.
© SAP AG
ADM326
2-8
SAPup / SAPJup
DESCRIPTION
3
Standard SAP upgrade tool for ABAP and Java
Execution of main upgrade activities
For an ABAP system you require SAPup; for a
Java system you require SAPJup.
The tools share a similar architecture consist
of an upgrade program (SAPup or SAPJup) and
a control program (Upgrade GUI or SDT GUI).
4
ACCESS
SAPup and SAPJup are part of the upgrade
software kit shipped by SAP
More Information is available on SDN:
http://sdn.sap.com/irj/sdn/upgradetech
BENEFITS
New upgrade GUI layout and simplified upgrade
procedure for AS ABAP 7.01, AS Java 7.1 and
AS ABAP+Java 7.1 ('dual stack') upgrades
Established system switch upgrade technology
is also available for AS Java 7.1 and AS
ABAP+Java 7.1 ('dual stack') upgrades
Synchronized upgrade procedure for
ABAP+Java 7.0 ('dual stack') upgrades
© SAP AG
ADM326
2-9
Upgrade Tools: Upgrade Front-end
3
Central Instance host
Upgrade
Port 4240
Upgrade Controller
Remote client host
4
Port 4239
HTTP
Port 4241
© SAP AG
ADM326
2-10
Upgrade Controller
3
4
dir
ec
tl y
sta
rts
Start the UA server
Only on the central instance host
Command from the Upgrade Master DVD:
<DVD drive>:\ STARTUP.BAT "upgdir=<upgrade directory>" "jce_policy_zip=<path to JCE
policy archive>"
If you would like the upgrade GUI to start automatically, use the following parameter:
STARTUP.BAT "guistart=on"
Choose a password when starting for the first time
© SAP AG
ADM326
2-11
Upgrade Front-end (1)
3
4
New setup
with upgrade
to AS ABAP/AS
Java 7.01
Start the Upgrade Front-end on a client host with network access to the central instance host
In the Web Browser call the URL: http://<central-instance-host>:4239
The UA client GUI starts after the download of the client application code is complete.
© SAP AG
ADM326
2-12
Upgrade Front-end (2)
3
4
You can log on to the Upgrade Front-end with different roles.
Administrator:
New design with
upgrade to AS
ABAP/AS Java 7.01
Power user gets full functionality of Upgrade Assistant
Use the password you have chosen
This user can be logged in once
If the administrator logs on, another active administrator will be switched to user observer
Observer:
This user can only monitor the upgrade
Use the password you have chosen
This user can be logged on several times
An observer can take over the administrator role when applying the administrator password
© SAP AG
ADM326
2-13
Upgrade Front-end: Input Window
3
4
New look and feel
with upgrade to AS
ABAP/AS Java 7.01
New feature:
download directory
The Upgrade Front-end input window has a new look and feel with upgrades to AS ABAP/AS Java
7.01
It is now possible to provide a central download directory for all patches and files that should be
bound to the upgrade
© SAP AG
ADM326
2-14
Upgrade Front-end: Upgrade Monitor
3
4
New look and feel
with upgrade to AS
ABAP/AS Java 7.01
Informs the administrator about
Progress of current roadmap step
Status of current phase
The Upgrade Monitor has a new look and feel with upgrades to AS ABAP/AS Java 7.01
© SAP AG
ADM326
2-15
Upgrade Front-end: Upgrade Documentation
3
4
New access to information
with upgrade to AS ABAP 7.01
There is a new access to information with upgrades to AS ABAP 7.01
© SAP AG
ADM326
2-16
Upgrade Front-end: Upgrade Phase List
3
4
New phase list design with
upgrade to AS ABAP 7.01
There is a new Phase List design with upgrades to AS APAB 7.01.
Besides others this new phase list takes into account, that there is no separation between PREPARE
and Upgrade anymore.
© SAP AG
ADM326
2-17
ASU Toolbox – Management Tool for Manual
Follow-up Activities
(part of)
Delivered with ST-PI
Must be started manually /ASU/UPGRADE
Preparation phase: REQ_PRE_ASU_RUN
Downtime phase: REQ_POST_ASU_RUN
See SAP Note 1000009
© SAP AG
ADM326
5
Guidance for manual steps
Benefit: Reduction of runtime
and downtime
2-18
Agenda: Selecting the Target Release
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
3-1
Selecting the Target Release
Contents:
© SAP AG
Create Solution Manager key with the SAP Solution Manager
Create XML/TXT files for the upgrade with the Maintenance Optimizer
ADM326
3-2
Select the Target Release of the Upgrade with
SAP Solution Manager
How is this stack
file created?
A properly installed Solution Manager system is required to generate the xml and txt file to bind an
individual selection on SAP Enhancement Package 5 for SAP ERP 6.0 components to the upgrade.
This step is mandatory for the 6.04 upgrade!
© SAP AG
ADM326
3-3
Generation of Stack Configuration File:
Initial Setup
SOLUTION_MANAGER:
create solution
SOLUTION_MANAGER:
assign system via
logical component
In the Solution Manager system in transaction SOLUTION_MANAGER: create a solution
(application) and assign the logical component assigned to the SAP system entry from transaction
SMSY.
The logical component is the link between the solution and the SAP system.
© SAP AG
ADM326
3-4
Generation of Stack Configuration File:
Create Maintenance Transaction
1. Enter description
2. Choose product version
3. Choose system(s)
Select the solution (application) and create a maintenance transaction.
© SAP AG
ADM326
3-5
Generation of Stack Configuration File:
Choose Scenario 'Upgrade'
1. Calculate files automatically
2. Upgrade
Choose 'upgrade' (this feature only exists if the Solution Manager system has the required SAP
Support Package level - for details see upgrade guide)
Find download files.
© SAP AG
ADM326
3-6
Generation of Stack Configuration File:
Select Technical Usages
1. Select desired technical usages
Select the technical usages, that are required from a business point of view. This selection should not
be done by the administrator but is part of the upgrade project planning.
Find download files for the stack version (minimum for the upgrade: SAP Support Package stack 2 recommendation: use the latest!)
© SAP AG
ADM326
3-7
Generation of Stack Configuration File:
Select Operating System
1. select operating system and database
2. …
3. Select Download Basket
Now the files can be downloaded with
the Download Manager
Select operating system.
Maybe there are stack independent files. Select these also.
© SAP AG
ADM326
3-8
Generation of Stack Configuration File:
Copy xml and txt File to Upgrade
Copy the txt file,
so it can be accessed by
the Upgrade
The xml and txt files are generated in the transport directory of the Solution Manager system,
subdirectory EPS\in.
Copy them so they are accessible by the upgrade.
© SAP AG
ADM326
3-9
© SAP AG
ADM326
3-10
Agenda: Modification Adjustment
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
4-1
Modification Adjustment
Contents:
Basic ideas of SPDD and SPAU/SPAU_ENH
Changing the SAP standard
Preparing the modification adjustment
Adjusting follow up systems in the landscape
Handling transport requests for modifications
© SAP AG
ADM326
4-2
Changing the SAP Standard
Customizing
Setting of business
parameters
(obligatory or optional)
Customizing
Development
SAP
Standard
Enhancements
Mod.
Adv. Corr.
Development
Adv. Corrections
Modifications
Enhancements
Own applications
SW changes in
regard to a later
upgrade
Changes to the
SAP software
Use of existing user
exits or BAdIs for
software
enhancements
There are five types of SAP system changes:
Customizing:
Involves setting system business parameters using special Customizing transactions. Changes
are scheduled and organized in advance. Customizing is mandatory before using the SAP
system in a live environment. Do not confuse with technical parameters from transaction RZ10!
Customer developments:
Creation of customer-specific objects according to naming conventions.
Enhancements:
Customer changes to SAP Repository objects without the need for modifications.
Modification:
Customer-specific changes to SAP Repository objects. When SAP objects are changed, the
customer version has to be modified to match the new SAP version.
Advanced correction:
Apply bug fixes from SAP directly to the SAP system.
© SAP AG
ADM326
4-3
Modification: Yes or No?
Modifications that need adjustment
Manually implemented advanced correction in accordance with a SAP Note
Adjustments of customer beyond Customizing (Repair)
Customer transports (<SID>K9*)
No modifications
Advanced correction with SAP transport (<SID>K0*)
will probably be part of the new release
SAP Support Packages
will be part of the new release or an SAP Support Packages of the new release
Add-ons
will be part of the new release (Extension Set) or need an upgrade DVD
© SAP AG
ADM326
4-4
Calculation of Modified Objects to be Adjusted
List of customer
requests and tasks
E071
E070
C11K900001
C11K900001
SAPK01384
COMMFILE
C11K900004
C11K900004
{
{
...
...
C11K900001
LIMU REPS
RSPUTPRT
C11K900001
C11K900001
C11K900004
R3TR PROG
R3TR TABL
LIMU DOMD
RDDFINFO
GODIR
RESULT
...
resolve
single
objects
List of modified part objects
‘Back to SAP standard’
Object key
Objects modified
by SAP
that come with
new release
TODIR
LIMU
LIMU
LIMU
LIMU
LIMU
Objects
modified by
customer
UMODOBJ
REPS
REPS
DYNP
TABD
DOMD
...
RSPUTPRT
RDDFINFO
RDDFINFO1000
GODIR
RESULT
SPDD
SPAU/SPAU_ENH
X
X
UMODHDR
Without modification adjustment, you would lose all modifications you made to objects that conflict
with SAP modifications when you upgrade the system. The modification adjustment lets you make
your modifications to the appropriate new objects in the upgrade.
You can identify modifications as repairs to the SAP standard or as imports of SAP objects. Requests
in the customer namespace (number range 900000 to 9ZZZZZ) “modify” the SAP objects included
in them. All other requests are dealt with as preliminary corrections.
The ABAP Dictionary objects (tables, data elements, domains, and so on) can be adjusted during
productive operation before the activation of the ABAP Dictionary. The adjusted objects are
collected in a repair that is released to a transport request. You should not release this transport
request; instead it must be flagged for export in transaction SPDD. Towards the end of the upgrade,
SAPup exports this transport request into the transport directory /usr/sap/trans and then registers it
for transport in the file umodauto.lst.
Repository objects (reports, screens, and so on) are adjusted toward the end of the upgrade, during
downtime. At this stage, the import of SAP objects has already been completed. However, the old,
modified version is still available in the versions database. As with ABAP Dictionary objects, all
adjustments are released to a transport request that is noted and then exported and registered by
SAPup.
© SAP AG
ADM326
4-5
Upgrade System Landscape
DEV
QAS, PRD
system active
Production
Production
system down
SPAU
SPAU_ENH
SPAU
SPAU_ENH
Switch
Switch
SPDD
SPDD
Import
Import
system active
Transport
Directory
Integration of the
created transport
requests into
the upgrade
bin/umodauto.lst
data/R...
cofiles/K..
buffer/SAP
The start of the upgrade process involves the transfer of new data to the system from the shipped
DVDs. SAP Repository objects are imported into the system and the customer objects are compared.
All ABAP Dictionary objects that have been modified by customers must be compared to the new
SAP standard during this upgrade process.
To avoid loss of data and table fields that customers may have created, conflicting structures must be
merged before the mass activation of ABAP Dictionary objects in the upgrade process.
If objects need to be adjusted, use the transactions SPDD and SPAU/SPAU_ENH. All modifications
made by customers are then merged with the new SAP object versions to retain data; otherwise, the
new SAP version will be activated and data may be lost.
Upgrades to >= 6.10: The system is available during the activation phase. The activation takes place
on the shadow instance.
When the upgrade is completed, the SAP system is successfully running at the new release level.
Customer-developed objects and modifications have been preserved.
© SAP AG
ADM326
4-6
Preparation Aspects
SPDD
modification
adjustment on
shadow
instance
Preliminary
corrections
are lost
SPDD:
No transport
into system
manually
SPDD/SPAU
Without
adjustment,
modifications
are lost
SPDD:
Do not
activate
objects
SPAU/SPAU_ENH
14 Days
without
key check
SPAU/SPAU_ENH
objects:
Adjusted at the
end of
upgrade
Do not attempt to import adjustment transport requests into the system manually during SPDD. This
can leads to a loss of data in customer fields.
Do not activate any objects. Activation is carried out automatically after the adjustment.
If errors are reported when you activate your own developments after executing this phase, you can
correct these here, since SAPup stops when errors occur. However, you also have the option of
choosing Ignore to temporarily ignore these errors. You do not need a password to do this. If you
chose Ignore here, you must activate these objects after the upgrade.
After you have completed the upgrade, you have a maximum of 14 days to execute transaction
SPAU/SPAU_ENH without a key check (SAP Software Change Registration) for the objects that
you changed.
For further information, see the Component Upgrade Guide and online application help for SPDD
and SPAU/SPAU_ENH.
© SAP AG
ADM326
4-7
SPDD
SPDD provides the following functions:
Display
Comparing old and new versions
Maintenance
Reset to original
Marking objects as processed
Refresh
Marking for transport
Display: Within individual packages or corrections, the objects are displayed according to type. To
view a changed object, select it with a double-click. You are automatically shown an overview of all
existing versions of the selected object.
Comparing old and new versions: Selecting an individual object lets you view all existing versions of
the object stored in version management. The display is the same as the one with which you are
presented when you compare two objects in version management. The information reflects the status
of the objects after their activation. For example, a comment in a table field indicating deletion
means that the field will be deleted after activation, provided no maintenance is carried out
beforehand.
Maintenance: Transaction SPDD lets you compare the most important attributes of old (modified)
and new (SAP standard) versions of domains and data elements. This helps you to decide how to
proceed. Perform the adjustments required in transaction SE11, preferably in a second window.
Reset to original: If, after comparing the results of the analysis, you conclude that you do not wish to
retain previous modifications, choose Reset to original for the object in question. For example, you
may need this function if you have patched an object by hand. When SAP delivers the same patch
together with other corrections in the next upgrade, you can return to the SAP standard because you
no longer need your own modification.
Marking objects as processed: To facilitate work with the generated object list, you can assign the
status Completed to each object. Selecting the function changes the status of the object and indicates
this by highlighting it with a different color. The completed flag is meant only to assist you in
organizing your work and has no other internal function.
Marking for Transport: The Select for transport function helps you to adjust other SAP systems.
© SAP AG
ADM326
4-8
SPAU
Automatic adjustment
Semi-automatic adjustment
Manual adjustment
Unknown adjustment mode
Reset to original
Automatic adjustment: Customer modification can be automatically adopted. Clicking on the icon
causes the system to automatically adjust the object (only With Modification Assistant category).
Semi-automatic adjustment: Semi-automatic means that each tool will individually offer you support
during the adjustment process. When adjusting programs, the split-screen editor is called, whereas in
the other tools any entries made in the collision dialog box lead to the necessary adjustments being
made automatically. As with the green traffic light, the semi-automatic adjustment icon only appears
in the With Modification Assistant category.
Manual adjustment: Objects in the Without Modification Assistant sub-tree can only be postprocessed manually after the adjustment process. Manual adjustment means that you must make
modifications without any special support from the system. Use the log as a help. Using Version
Management, you can retrieve old versions or use your recordings to process the newly imported
objects. In rare cases, the red traffic light may also appear in the With Modification Assistant
category.
Unknown adjustment mode: The adjustment mode (manual, semi-automatic, automatic) for at least
one of the objects in question could not be determined for modification adjustment with the
Modification Assistant. If this is the case and you start transaction SPAU, a dialog box informs you
that you can start a background process by choosing the appropriate button, which determines the
adjustment modes for all objects.
Reset to original: If you choose Reset to original for an object displayed in the overview, no
modifications are adopted for this object. The original is the version that was last imported into the
SAP R/3/ECC system during the upgrade or an SAP Support Package.
© SAP AG
ADM326
4-9
SPAU_ENH
Object List
Selector
Navigation
Area
Tool
Area
Automatic adjustment
Tool-supported adjustment
Manual adjustment
Semantic change
All enhancements that you have to adjust are shown in transaction SPAU_ENH. In contrast to
modifications of source code units, you only have to adjust enhancements if the underlying SAP
development objects were deleted or changed in an incompatible way.
For the quality assurance and production system, we recommend that instead of adjusting
modifications and enhancements manually, you automatically transfer the transport requests
exported from the first system: one for the ABAP Dictionary objects adjusted using transaction
SPDD and one for the Repository objects adjusted using transactions SPAU and SPAU_ENH.
If you have implemented enhancement framework options of the new Enhancement Framework or
implemented a new kernel-based BAdI (also part of the new Enhancement Framework), and the
underlying development objects have changed in an incompatible way, you must adjust these objects
in transaction SPAU_ENH.
The enhancement framework does not support modifying enhancement definitions or enhancement
implementations. In some cases you can, however, replace enhancement implementations of a higher
layer with your own enhancement implementations.
© SAP AG
ADM326
4-10
Handling Transport Requests During
Adjustment
Create one new transport
request for SPDD and one for SPAU/SPAU_ENH
Transport routes:
Local or transportable transport request
Only release tasks after modification
adjustment, do not release the transport request now
Select for transport function in SPDD and SPAU
The configuration of the transport routes in the SAP system determines whether changes to objects
during modification adjustment are recorded in a local or transportable transport request. You cannot
and must not change these settings during the upgrade. In all cases, the transport request can still be
used for automatically transferring modifications to a subsequent system. For this procedure, the
transport requests are not released in the normal way, but handled specially.
Do not change the configuration of the transport routes in your system group during the upgrade.
When modification adjustment has been completed, release your tasks. The tasks are the repairs
and/or corrections that were automatically assigned to you when the transport request was created.
Do not release the transport request at this point if you want to use it to automatically transfer the
modification adjustments to subsequent systems.
During the adjustment of the ABAP Dictionary objects, releasing requests is locked until the edited
objects have been activated. Do not release these requests until after the upgrade.
To automatically transfer modifications to a subsequent system when you have completed
modification adjustment, use the Select for transport function in SPDD or SPAU.
If your modifications are recorded in several transport requests, you first have to place all entries in a
single request. Several requests cannot be marked for transport.
© SAP AG
ADM326
4-11
During the Adjustment:
Before the Upgrade:
Transport Requests: Notes
Use the Modification Browser (SE95) for analysis
on modified objects (if available)
Analysis report Search for objects in requests/tasks
in transaction SE03 can be used to check whether
the objects modified are recorded in repairs
Objects that have been modified and differ from the
SAP standard must be included in a repair
The Reset to Original function should be used for
objects with no differences.
Also for objects where last and second to last
versions were created by user SAP (R3trans)
Before the upgrade:
Check whether the objects you modified are recorded in repairs. To do this, you can use
transaction SE95 and search for objects in requests/tasks in transaction SE03.
No repairs or customer transports are displayed by the Transport Organizer (SE01) and the
Workbench Organizer (SE09), although you know that objects have been modified in the SAP
system. Indicate the objects that have been modified and differ from the SAP standard by
including them in a repair and subsequently releasing it.
During the adjustment:
No differences are found when you compare the second-to-last and third-to-last versions:
During the last upgrade you did not perform adjustments to retain changes you had made to
objects. Indicate that modifications to these objects are no longer needed with the Reset to
original function.
The last and second-to-last versions were created by user SAP (R3trans):
During the last upgrade you did not perform adjustments to retain changes you had made to
objects. Indicate that modifications to these objects are no longer needed with the Reset to
original function.
© SAP AG
ADM326
4-12
Modification Adjustment Transactions
Different modified
objects require
different
transactions
for modification
adjustment
Domains
Reports
Data elements
Menus
Tables
Screens
Views
Lock objects
Transaction SPDD
For most ABAP
Dictionary objects
Transaction SPAU
For all other
Repository objects
If you do not use SPDD where necessary, you risk data loss
Transaction SPDD is used to perform modification adjustments to certain ABAP Dictionary objects
such as domains, data elements, table structures, transparent tables, pooled tables, cluster tables, and
table technical settings. Not performing modification adjustment for these objects would cause data
loss.
After activating the new Repository, transaction SPAU/SPAU_ENH is used to perform modification
adjustment for objects for which not performing modification adjustment would NOT directly lead to
data loss. These objects include:
Some ABAP Dictionary objects (lock objects, views, and so on)
All other Repository objects (such as module pools, ABAP programs, function modules, menus,
and screens)
After running transactions SPDD and SPAU/SPAU_ENH, all modifications are incorporated
into the new SAP release
The preparation phases check which modified objects need adjustment to enable you to better plan
the time required for modification adjustment.
© SAP AG
ADM326
4-13
© SAP AG
ADM326
4-14
Agenda: Technical Phases
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
5-1
Technical Phases
Contents:
© SAP AG
Overview of the major steps of the upgrade
Most important phases of the upgrade
ADM326
5-2
New Upgrade Interface
© SAP AG
ADM326
5-3
Resource Consumption of the Upgrade
New with upgrade
to AS ABAP 7.01
Resource minimized
Downtime minimized
'Low recourse use' triggers 'Resource minimized'
'Standard' and 'High resource use' trigger 'Downtime minimized'
© SAP AG
ADM326
5-4
Overview
DB and upgrade directory
must be restorable to
state at end of production!
© SAP AG
ADM326
5-5
SAPGUI
Be sure to have a suitable SAPGUI in place when needed:
The end users need a suitable SAPGUI when productive operations is started in the upgraded
productive system.
The users from the departments involved in the upgrade project need a suitable SAPGUI at the end
of the upgrade of the sandbox system.
Developers involved in the upgrade project need a suitable SAPGUI starting from SPDD
modification adjustment in the sandbox system.
The administrators involved in the upgrade project need a suitable SAPGUI starting from the begin
of the upgrade project.
© SAP AG
ADM326
5-6
PRD: delta transports
Manual actions
XPRAS*
TABIM*
PMVNTAB_UPG
PARCONV_UPG
EU_SWITCH
MODPROF_TRANS
SHADOW_IMPORT*
DIFFEXP*I
Transaction ICNV
PARDIST_SHD
ACT_UPG
Transaction SPDD
DIFFEXP*
RUN_RDDIT006
EU_IMPORT*
Apply SAP notes
Important Phases of the Upgrade
EU_IMPORT* Copies substitution set from Upgrade CD to the shadow tables
RDDIT006 Determines deviations of the current system from the future standard SAP system
(objects and modifications that need to be copied)
DIFFEXP* Exports objects not stored in shadow tables: Add-on objects, SAP Support Package
objects, generated objects, unsent modified objects, customer developments, customer extensions to
SAP object documentation, documentation for customer objects, local private objects and test objects
in the SAP name range
ACT_UPG Activates all ABAP dictionary objects, that are not part of the standard upgrade DVDs
PARDIST_SHD Starts distributor
DIFFEXP*I Import of objects into shadow repository exported by DIFFEXP*
SHADOW_IMPORT* Imports upgrade and language data into the new tables, imports included
Add-on and SAP Support Packages into the shadow tables and the new tables
MODPROF_TRANS Stops SAP system and changes profiles
EU_SWITCH Switches to new Repository
PARCONV_UPG Converts application tables and activates their nametab entries
PMVNTAB_UPG Converts application views and activates remaining nametab entries
TABIM_UPG Import of additional transport requests
XPRAS* Executes XPRAs
© SAP AG
ADM326
5-7
Status at Phase ACT_UPG / SPDD
(Example: 4.6C Start Release)
Shadow instance
7.02
...
Application data
customizing data
user master data
Add. application data
add customizing data
(imported after ACT)
SAPR3SHD
Productive instance
4.6D
SAPR3
Productive instance
4.6D
(Application data)
customizing data
user master data
Repository
Accesses
Repository
Shadow repository
4.6C/4.6C
7.02/6.05
Productive system
4.6C/4.6C
Shadow repository
7.02/6.05
7.02
DB
Shadow system
7.02
At the most, there are three repositories active at the same time:
the old repository
the shadow repository (which will be the new productive repository at the end of the upgrade)
the repository of the shadow system.
© SAP AG
ADM326
5-8
Operation of Shadow System
Phase START_SHDI_FIRST
Start shadow instance for the first time
tion
c
u
d
pro
Batch jobs on shadow instance
Versioning preparations
SPDD
Modification adjustments on shadow instance
Activation: Phase ACT_UPG
Parallel activation on shadow instance
Distribution: Phase PARDIST_SHD
Parallel distribution on shadow instance
Phase STOP_SHDI_LAST
o
ad
sh
Stop shadow instance finally
w
The shadow instance is used for SPDD, batch monitoring, troubleshooting during shadow phases
DDIC user
Password copied from productive instance
Create additional users with transaction SU01
No access to application tables
Only basis tables accessible
No customizing
No production operation
No tp import to shadow instance
No tp mvntabs, no DDL statements
No online activation and conversion
Only “inactive“ activation in SE11
No operations in SE14
Access to target release repository during production operation on source release
© SAP AG
ADM326
5-9
Danger
DAN
Connect to shadow system:
GER
!
R3load, R3trans and tp need additional environment settings
to connect to shadow system correctly.
Manual calls of R3load or tp with wrong environment
will damage the system!
Calling SAPup with this setting could damage the system!
© SAP AG
ADM326
5-10
Upgrade of AS Java based SAP System:
Prerequisites
Source
system prepared for the deployment of Adobe Document Service (ADS) if
ADS not installed yet. Refer to Java Upgrade Guide
JDK
version, refer to SAP Note 709140
JCE
requirement, refer to SAP Note 865166: Only required if the source system
uses stronger encryption and a new JDK version is installed
SAP
Support Package level of the source system
Web AS: 6.40 SP09
SDM version > 6.40 SP13
The application components must be:
EP: 6.0_640 SP09
XI: 3.0 SP09
BI-Java: 3.5 SP09
ADS: 1.0 SP09
KW IKS: 1.0 SP09
ADS becomes an integral part of the NW 7.0 Application Server. It will be deployed in the target
system regardless whether it is installed in the start release.
Including the latest SAP Support Package Stack
Preserve Customer Data
Migrate J2EE Engine configurations
Preserve application data and configurations
Upgrade Modified Components
Archives containing new releases of modified and third-party components can be selected and
deployed by SAPJup
© SAP AG
ADM326
5-11
Deployment-Based Upgrade
7.02
Deploy
SAPJup
Applications
Deploy
J2EE Engine
Components
Configure
2004
Binaries
Profiles &
scripts
Applications
J2EE Engine
Components
Binaries
Profiles &
scripts
Preparation steps are performed during the system uptime
The PREPARE phases include following major tasks:
Migrate
Migrate
Adapt
Adapt
Investigating the source system
Performing various parameter and profile checks
Determining Usages Types to be upgraded
Extracting upgrade DVDs
Including SAP Support Packages
Including custom development components
Calculating the deployment lists and order
Additional instances (non-central instances) have to be re-installed using SAPinst.
© SAP AG
ADM326
5-12
Uptime and Downtime
Upgrade Uptime
Uptime is the time when the J2EE Engine is up and running. It’s 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
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
The system is not productive
Even when system is up – it can’t be used. Upgrade starts the J2EE 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
The UPGRAGE phases are mainly performed during the downtime.
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 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
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
© SAP AG
ADM326
5-13
Upgrade of AS ABAP+Java System
(Dual Stack)
Synchronized upgrade of
ABAP stack and
Java stack
Synchronization points at
Begin of downtime
End of downtime
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
Upgrading (PREPARE and UPGRADE) ABAP and Java stack must be performed in parallel with
following sync points:
At the beginning of the downtime
When the profiles are going to be modified
At the end of the downtime
Except for the sync points, the upgrade processes of both stacks are performed independently
The vast majority of the Java upgrade takes place during the downtime
© SAP AG
ADM326
5-14
Agenda: Troubleshooting
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
6-1
Troubleshooting
Contents:
Monitoring upgrade activity
Troubleshooting within job phases, transport phases, bulk import phases
Log file analysis
© SAP AG
ADM326
6-2
Overview: Upgrade Executables
User Interface
Main Programs
Tools Used During Upgrade
tp
Start
SAPup
R3load
DB
User interaction
&
SAPup output
SAP system
The user interface is described in the Upgrade Manual.
The version of most SAP executables can be determined with the option -V.
For those tools which connect to the database, a value in the DB library line indicates that the
corresponding DB library can be loaded.
The Upgrade Assistant GUI does not require a permanent connection to the server.
© SAP AG
ADM326
6-3
Overview: Monitoring Upgrade Activity
Upgrade Assistant Monitor
Current phase, estimated runtime
Operating System
CPU activity (UNIX: top, Win: Task Manager)
Active processes (UNIX: ps, Win: pstat)
Current log files in DIR_PUT/tmp
SAP System
SM50 Work process overview
SM37 Active background jobs
You can use the above tools to see the upgrade activity.
If input is required, the upgrade will stop. A file, upalert.log, is then written to <upgrade
directory>\abap\tmp.
© SAP AG
ADM326
6-4
Overview: When the Upgrade Stops
Upgrade
Stop
Read message from SAPup
Determine the current phase,
check the log file mentioned
in the phase list for this phase.
Check the most recently written
log files in <upgrade directory>\abap\log
and <upgrade directory>\abap\tmp.
In the SAP System (if it runs):
SM21 system log
SM37 job logs of finished
or canceled jobs
ST11 trace files
ST22 short dumps
For the database,
check the database alert file.
These steps should be processed to find what caused the upgrade to stop.
The current phase is the last in SAPup.log.
Additional logs can be created in transactions SM21 and SM37 for activities inside the SAP system.
The database alert file can contain special DB-related errors such as archiver stuck.
© SAP AG
ADM326
6-5
Overview: Phases
JOB_ or RUN_ phases:
SAPup starts a background
job or a function module
in the SAP System
Transport phases:
SAPup starts tp to do one of the following:
tp connects to the database and
executes an SQL script
tp starts R3trans. R3trans connects
to the DB and imports/changes data
tp starts sapevt. sapevt sends an event. RDDIMDP
runs once, transport steps are processed in the
background
Bulk import phases:
SAPup starts R3load to import
new data (full)
An upgrade to SAP ECC 6.0 contains several hundred different phases. Most of the phases fit into
one of three described classes.
SAPup itself cannot connect to the database. To read or change information in a database table,
SAPup needs a tool that can access the database. In each of the three classes, SAPup chooses
different tools. Details of these classes are described on the following pages.
During upgrade phases with names like JOB_ or RUN_ , SAPup starts a function module in the
system using RFC to schedule and start a background job. After the job had finished, the result is
evaluated from the log file.
Phases with names such as TABIM, TABUIMP, VIEWIMP, PORT_IMP, TOOLIMP and so on are
classical import phases. tp starts R3trans, R3trans imports data.
Phases like DIFFEXP or SHADOW_IMPORT are similar phases, except that R3trans imports into
the shadow tables.
The EU_IMPORT phases are the bulk import phases during which the new Repository is imported
into the shadow tables invisible to the production SAP System.
Most of the data in the Repository is not unique to the system, therefore an exchange is more
efficient than a import of the delta. In contrast, customizing is unique to each system, and therefore
only the delta is imported.
© SAP AG
ADM326
6-6
Job Phases: Control Flow
External programs
SAPup
Within SAP system
Function module
RFC
Schedules
Read & Write
Job
Write
Log Files in
<upgrade directory>\abap\log
Database
SAPup starts a function module in the SAP system as user DDIC in client 000
(SUBST_START_BATCHJOB).
This function schedules a background job for the phase.
SAPup regularly checks the status of this job with a new RFC call (SUBST_CHECK_BATCHJOB),
until the job has finished.
The log file written by the job in <upgrade directory>\abap\tmp is analyzed and evaluated by SAPup.
© SAP AG
ADM326
6-7
Job Phases: Log Files
During a JOB phase, the following kind of log files are written:
<name>.LOG
RFC login, start and check a
background job <name>
<name>.<SID>
Where <name> is not a transport log file,
it can be the log file of a background job
<name>.ELG
Errors collected from the previous log
<name>.SAV
.LOG and .ELG from previous runs
Example for phase RUN_RDDIT006:
DIFFCALC.LOG
RFC logon
CUSTEXP.<SID>
Log file of background Job RDDIT006
DIFFCALC.ELG
Condensed errors from CUSTEXP.<SID>
(DIFFCALC.SAV)
.LOG and .ELG from previous runs.
The first RFC phase is RFCCHK_INI in PREPARE. Only the RFC logon is performed during this
phase, and no background jobs are started (RFCCHK_INI.LOG).
The check of the background job functionality is made during BATCHCHK phases (for example,
BATCHCHK_IMP.LOG).
© SAP AG
ADM326
6-8
Transport Phases: Control Flow (TABIM)
Data file
SAPup
Start
tp
Read
Start
Read & Write
R3trans
Write
Write
Import
Log Files
<upgrade directory>\abap\log
Database
This is also valid for TOOLIMP, DIFFEXP*, and other import phases.
During the DIFFEXP* phases, R3trans reads from the source release tables and writes into the target
release tables (copy to shadow).
SAPup evaluates a direct return code from the tools (finished) and evaluates an indirect return code
from the written log files.
© SAP AG
ADM326
6-9
Transport Phases: Control Flow (ACT, XPRA)
Jobs within
SAP system
External programs
SAPup
Start
tp
Start
sapevt
Trigger
RDDIMPDP
Read & Write
Schedules
Write
RDD*
Write
Log Files in
<upgrade directory>\abap\log
Database
Instead of R3trans, a transport background job might also be started for actions such as activation.
The start of RDDIMPDP works differently from the start of a job during a JOB phase.
PARCONV (parallel conversion) is similar to this, but SAPup starts the transport background jobs
(distribution, conversion) itself, and in parallel. After distribution, an additional check is made for
lost fields (FDSAVPROT). SAPup then starts tp only for movenametab (PMVNTAB, execution of
DDLs).
© SAP AG
ADM326
6-10
Transport Phases: Log Files
SAPup calls tp with a special transport profile (TPPARAM/TP<Domain>.PFL)
SAPup log files
TP.ECO or R3up.ECO stdout of tp
*.ELG
Collected error lines from transport logs
tp log files
ULOG...
ALOG<rel>
SLOG<rel>
tp call inclusive used transport profile
Finished steps (request, return code)
Details of tp call
R3trans log files
SAPI*
SAPH*
(Main) Import logs
Dictionary import logs
Transport background jobs log files
SAPA*
DS<nnnnnn>
N<nnnnnn> or
NCONV<nn>
Activation logs
Distribution
Conversion
The special upgrade log files are .ECOs for standard output and .ELGs, where errors from other log
files are collected. A line in a transport log is transferred if it contains an E in the second column.
The log files for tp differ only in the naming from the usual transport log files.
Additional PCON log files are:
FDSAVPRT.<SID> Check for lost fields
PA<date>.<SID>
Only nametab activated
PD<date>.<SID>
Activate and alter table (add field or similar)
PL<date>.<SID>
Delete table and remove nametab
© SAP AG
ADM326
6-11
Transport Phases: Strategy for Problems
Did a tool
write an error
Yes
message into its log file?
(Check the
.ELG File)
No
Yes (that is, an error line appears in ELG):
check the corresponding original log file
mentioned in the ELG.
R3trans import:
In most cases during import phases,
errors are related to DB problems and a DB
error message is found in the import log.
Activation error:
Check the object in transaction SE11.
XPRA error or short dump:
Check the report documentation of the XPRA
No (that is, ELG of transport phase does not contain error lines):
Check if tp finished correctly (ECO File).
Check log files written by tp for errors (especially SLOG)
Activation errors should be resolved or classified as non-critical. Otherwise, there is a chance that
data in PARCONV will be lost.
In ACT, TABIM and XPRA, a return code of 8 means that individual objects were not processed
successfully. You could repeat the phase at your own risk with repair severe errors. If you do this,
then only return codes larger than 8 will stop the phase.
Check for lost fields fails in PARCONV :
Verify that this is correct (SAP Note). Data might be lost if the phase is repeated with Do not repeat
checks.
© SAP AG
ADM326
6-12
Bulk Import Phases: Control Flow
SAPup
Read
Start
Data file from DVD
R3load
Read & Write
Write
Import
Log Files in
<upgrade directory>\abap\log
Database
SAPup starts R3load for each data package EX<nnnnn>.
EX<nnnnn>.DPR is the import log file,
EX<nnnnn>.DST is the statistics log file.
Depending on your upgrade strategy (downtime minimized, resource minimized and sub-strategies):
If the system is productive during EU_IMPORT phases, you can slow down the R3load process
so that the performance of the SAP system is not affected.
If the system is not productive during EU_IMPORT, the SAP system is shut down during
EU_IMPORT and several parallel R3load processes are started.
The statistics log file contains only the number of imported bytes and the total number of bytes in
this data package.
The restart of an EU_IMPORT phase with init first removes all previously imported tables and then
starts R3load to import all tables again.
The restart of an EU_IMPORT phase with repeat just starts R3load to restart from the point where
the error occurred.
Duplicate keys during the creation of a index are caused by CD read problems. The recommended
solution is init of the phase with the DVD copied to disk.
© SAP AG
ADM326
6-13
Log File Analysis
SAPup checks the log file for errors (E in the second column) and copies these lines into
an .ELG file. The number of errors in one phase is equal to the number of lines copied
into the .ELG.
Example
A line in a log file starting, for example, with
2EETG779 ....
means:
Severity 2 (Level of log file display in SE09),
Error,
English,
Message class TG,
Message 779.
Transaction SE91 can be used to display the long texts of error messages. (>long text
>document >screen)
SE91 can also be used to identify the development class of the message. The development class has a
component assigned. Especially for XPRAs, the customer message can be opened directly on this
component.
© SAP AG
ADM326
6-14
Access to Troubleshooting Guide
© SAP AG
ADM326
6-15
Providing SAP Support with Information
SAP Product
Component
SAP Solution Manager
SV-SMG
Index Management Server
BC-SRV-TRX
OLTP R/3 System
BC-UPG
R/3 Standalone Gateway
BC-UPG
SAP Add-On
BC-UPG-ADDON
SAP Supply Chain Management
APO-BAS
SAP Business Connector
BC-MID-BUS
SAP Business Information Warehouse
BW-SYS
SAP Business-to-Business Procurement
BBP-SAD
SAP Customer Relationship Management:
Communication Station and Mobile Development Workstation
CRM Server
Internet Pricing and Configurator (IPC)
Mobile Client Component
SAP R/3, SAP R/3 Enterprise, SAP ECC
CRM-MW
BC-MID-INT-SRV
CRM-MT-IU-SPE
CRM-WBT-IU
BC-UPG
SAP TREX Search Engine (SAP DrFuzzy Search Engine)
BC-SRV-TRX
SAP Front End
BC-INS
SAP Internet Transaction Server
BC-FES-ITS
SAP Knowledge Management
KM-KW
SAP Enterprise Core Component
BC-UPG
SAP Strategic Enterprise Management
BC-UPG-ADDON
SAP NetWeaver Application Server ABAP
BC-UPG
SMART Installation
BC-UPG
If you encounter problems that are specific to the upgrade, create an error message in SAP Support
Portal (http://service.sap.com/support) and assign it to component BC-UPG. Answer the following
questions and put these answers in your customer message:
For which SAP component do you want to perform the upgrade?
Which release are you upgrading from? Which release are you upgrading to?
Which operating system version are you using?
What was the original release of your SAP system?
In which upgrade program phase does the error occur?
This information is listed at the end of the SAPup.log file located in the upgrade directory.
Did you have problems with the SAP system before upgrading?
In any case you should send the troubleshooting ticket file created by SAPup to SAP!
© SAP AG
ADM326
6-16
Recommendations
Test upgrade: Problems can be localized and analyzed to avoid them during the
production upgrade.
Ignore a phase: The upgrade was tested at SAP and should work without ignoring
any phases with a password. In general this leads to more problems in later phases.
Distinguish between an ‘Ignore’ that requires a password and an ‘Ignore’ without a
password!
Backup: In case the upgrade cannot be finished, ensure that you have made matching
backups of the database and of the upgrade directory!
During a test upgrade, problems can be localized and analyzed, so that they can be avoided during
the production upgrade.
The upgrade was tested at SAP and should work without ignoring any phases. To ignore a phase
with a password will, in general, lead to more problems in later phases, Therefore passwords are
given only by SAP support.
In the very rare case that the upgrade cannot be finished, ensure that you have made a backup of the
database and of DIR_PUT as described in the Component Upgrade Guide. The database and the
upgrade directory must have a matching state.
© SAP AG
ADM326
6-17
© SAP AG
ADM326
6-18
Agenda: Incremental Conversion
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
7-1
Incremental Conversion
Contents:
© SAP AG
Early incremental table conversion (ICNV) during an upgrade to a system
based on AS ABAP 6.x/7.x
Description of the conversion procedure
ADM326
7-2
Goals of Early ICNV
Early ICNV is not available when using low resource use!
Reduction of upgrade downtime
Large tables are now converted during uptime
Only switch to new structure during downtime
(in PARCONV)
Easy handling
Fully integrated into upgrade process
Configurable conversion process
Exclusion times
Progress prediction
The main goal of the ICNV is to reduce the downtime during an upgrade.
The procedure should not be too complicated and it should be fully integrated into the upgrade
process.
The conversion process is executed during uptime. The database load is expected to be higher during
this process; therefore, it is possible to define exclusion times during which no ICNV processes are
running.
The administrator should be informed about the estimated end of the process to be able to plan the
upgrade accurately.
© SAP AG
ADM326
7-3
Overview
View T1
Create (4)
Table QCM1T1
Table T1
Table QCMT1
(New structure)
Add
Field
(3)
Create (1)
Rename (2)
Create
(5)
Update
trigger
Delete
trigger
Create (6)
Here is the sequence of steps during an incremental table conversion:
The conversion table candidates are selected.
(1) A QCM table with a new structure is created.
(2) The table T1 is renamed to QCM1T1.
(3) An additional status field is added to QCM1T1.
(4) A view on the old table structure is created. The applications access the view from now on.
To log these changes the update (5) and the delete (6) trigger is needed
The table content is copied (low priority copy) to the shadow table QCMT1.
QCMT1 is filled by periodic runs
At beginning of downtime, only a few conversions should remain. The downtime due to table
conversion is significantly reduced.
© SAP AG
ADM326
7-4
Need for Logging Mechanism
Production
operation Active table (QCM1T1)
Shadow table (QCMT1)
Update
Needs update
Delete
Out of use
Insert
Missing
Copy
Missing
A shadow table named QCMT1 with is created the new structure.
The data from the original table QCM1T1 is copied using a background process during uptime to the
shadow table QCMT1.
QCM1T1 is still accessible by the applications. Therefore the changes during the data transfer must
be logged and also be executed on the shadow table.
QCM1T1 is modified by creating a flag field. This field indicates if this entry was already copied to
the corresponding fields in QCMT1.
Programs can perform updates, deletes and inserts on QCM1T1.
Update of already converted entry: The “x” in the flag field is erased by the update trigger.
Deletion of already converted entry: The corresponding entry in the new table is directly deleted
by the delete trigger.
Insert: The flag field for this entry is left empty.
Every entry in table QCM1T1 with an empty flag field is copied to QCMT1
Periodically, the copy is repeated for all new rows since the last copy
© SAP AG
ADM326
7-5
Logging Mechanism
QCM1T1
Update
Delete
Insert
Update trigger
QCMT1
x
x
x
x
x
x
x
x
x
x
Needs update
Delete
trigger
out of use
Copy
Still missing
This could be the situation right after beginning of downtime:
Some rows are updated or inserted but not copied yet (empty flag field).
There can be a part of the old table which has not been transferred to QCMT1 (empty flag field).
The latest insert/update operations and the remaining conversion will be processed during downtime.
Inserting rows is possible without an additional load at that point in time, because no insert trigger is
used.
The update trigger is very efficient, because the additional load just consists of filling the flag field.
Delete operations must be executed in both tables and are therefore inefficient.
After the incremental conversion starts, dictionary definitions for the relevant tables cannot be
changed until the upgrade ends. This affects changing, deleting or adding field definitions.
Transaction SE11 is locked for these tables.
If you use incremental table conversion, do not start an SAP archiving program for these tables in
parallel, since this can lead to performance bottlenecks. Therefore, archive as much as possible
before starting the conversion.
Incremental conversion requires sufficient background work processes. Ideally, there should be one
process for each table to be converted. If you cannot have one process for each table due to a large
number of tables, you can still convert the tables since transaction ICNV distributes the tables by
itself to the available background processes. However, completing the incremental conversion takes
longer, and therefore more time is needed before beginning the upgrade downtime.
© SAP AG
ADM326
7-6
Transaction ICNV: Selection of Candidates
Selection of conversion candidates:
EU_IMPORT
Modified tables that will be converted are included
Tables can be excluded from ICNV even at this point (for
example: a hot spot with frequent updates / deletes)
DIFFEXP
START_SHDI
ACT
ICNV
SHD_IMP
SWITCH
PCON
TABIM
XPRA
By calling transaction ICNV, all potential candidates are displayed with their current selection status.
You can decide which of the pre-selected tables should be processed by ICNV.
Tables can be excluded from being processed by ICNV with 'Do not perform ICNV'. This should be
used for tables with a high number of updates and / or deletes, because in this case the ICNV can be
inefficient. The delete operations are especially critical. The load on the database is doubled by
performing a delete on a table processed by ICNV.
This efficiency check must be done manually. There is no tool that excludes “hot spot tables”
automatically!
© SAP AG
ADM326
7-7
Transaction ICNV: ICNV Assistant
ICNV configuration:
Number of background jobs
Selection of background
hosts
Exclusion times
ICNV assistant:
Initialization
Start of data conversion
Monitor progress:
Computation of
conversion statistics
Estimation of time
to finish
Status display
Transition
to new
repository structure
is done by the
upgrade!
ICNV offers several features to configure the incremental conversion process
Batch hosts can be specified
The number of running batch processes is adjustable
Exclusion times for processing can be specified for each table (This enables you to run
conversion job at times with relatively low table I/0).
The log files of the conversion processes for each table can be accessed
See online documentation in ICNV
After deciding about all tables, the user can choose to be guided through the necessary steps by an
ICNV Assistant. For the upgrade scenario, there are two steps needed to be started manually:
Initialization
- Extension by flag field
- Build of an index on the flag field
- Creation of update and delete triggers
- Replacement of table by a view and renaming table
Start of the data transfer
The remaining steps (switch and delete entry in ICNV) are then performed by SAPup !
© SAP AG
ADM326
7-8
Transaction ICNV: UI Elements
Control Elements
Assistant
Control menu
Menu Edit Add table
Monitoring elements
Performance analysis
Error log
Standard log
Job overview
Configuration elements
Menu Edit Options used for
background processing configuration
Menu Control Exclusion times used to limit execution
When starting an activity, starting date / time can be set
Other elements
Compute progress (usually not needed, recalculates the estimated runtime of data transfer)
Menu Edit Detailed information (same as double-klick on table)
Don't trust SE11 and SE14, consistency checks and so on. Objects are mostly not what they appear to
be
Don't use the reset option in case of trouble. Only error free ICNV cases can be reset and even then
this has an impact on the customer system.
After a reset, fix the DDIC definition and convert again.
In the standard upgrade scenario, you cannot make changes to the target definition, as you are
working in the standard instance and the shadow instance is gone.
Don‘t enter Upgrade downtime with an ICNV conversion in error. If you do so, you have to reset to
the MODPROF_TRANS and finish ICNV first.
© SAP AG
ADM326
7-9
Transaction ICNV: Initialization and Steps
Do not start steps 3 and 4.
They are started within the
upgrade downtime automatically.
Initialization is downtime for the table.
Choose a suitable time for that action.
There are useful tools for analysis and trouble shooting
FuBa DD_ICNV_REPAIR lets you execute individual transition steps
Report RADIMOVE lets you start the data transfer
Report RADINCNV lets you move along the transition graph
Report RUTNTCHECK (rutntchk in older releases) lets you display (true) runtime objects
- Option S for DDIC source, Option N for nametab, Option I for internal ICNV description
- A for Active, N for inactive variants
There is a step count in table ICNV
If you want to change execution plans, debug to the statement table
© SAP AG
ADM326
7-10
Aspects of ICNV
Conversion
of large tables during system uptime
Conversion
process can be stopped and restarted
Possible
error situations during uptime
ICNV
especially suited for WORM tables
ICNV
is fully integrated into the upgrade
Tables
to be processed by ICNV can be selected
Conversion
Additional
Sufficient
Execute
process is configurable
resource usage of DBMS
number of background work processes
ICNV as early as possible
Because most data is converted before the beginning of downtime, downtime can be reduced by
several hours. The actual reduction depends on the table size. The dependence of downtime on the
database size is also strongly reduced. The downtime can be predicted more accurately.
The conversion process can be stopped and restarted at any time without loss of converted data.
Error situations like table space overflow or reaching of maxextends due to the incremental
conversion occur during uptime.
ICNV is especially suited for large Write Once Read Many (WORM) tables
Pay special attention to the resource usage of your database management system to detect
bottlenecks early.
Incremental conversion requires double the space in the relevant database container (tablespace,
dbspace, and so on) for each affected table during the conversion.
Due to the continuous data transfer, there are more transactions. Therefore, you should also
monitor the space for the rollback information.
Incremental conversion eventually requires more background work processes.
Make sure, that at beginning of downtime most data is converted.
© SAP AG
ADM326
7-11
© SAP AG
ADM326
7-12
Agenda: Support Packages and Add-Ons
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
8-1
Support Packages and Add-Ons
Contents:
© SAP AG
Why bind SAP Support Packages and Add-Ons to the upgrade?
Handling of objects from Add-Ons and SAP Support Packages during the
upgrade
ADM326
8-2
Binding Add-Ons and SAP Support Packages
Integrating Add-Ons and SAP Support Packages into the upgrade prevents you from
losing data
PREPARE gives warnings about different patch levels between source and target release
The upgrade runtime is extended but
The upgrade downtime is almost the same when using a ‘downtime minimized’ strategy
('high resource usage' or 'medium recourse usage')
Loading of the included packages into the shadow repository during uptime
© SAP AG
ADM326
8-3
SAP Support Packages (1)
Begin of availability
Bind SAP Support Packages of the
destination release to the upgrade!
End of maintenance
SAP Support Package
SAP ECC 6.05
SAP_APPL 605
2
SAP ECC 6.0
SAP_APPL 600
20
SAP R/3 4.6C
SAP_APPL 46C
60
t
SAP Support Packages on the start release are produced also after a potential destination release has
been shipped.
SAP R/3 4.6C SAP_APPL Support Package 60 for example has been shipped after the shipment of
SAP ECC 6.0.
On each potential destination release, SAP Support Packages are available, too.
There is some relation between the SAP Support Packages: usually fixes have been mad at the same
time for different releases.
An upgrade from SAP R/3 4.6C SAP_APPL Support Package 60 to SAP ECC 6.0 SAP_APPL
Support Package 0 would partially downgrade the system.
But: it is possible to bind SAP Support Packages to the upgrade: you can go directly to ECC 6.0
SAP_APPL Support Package 20 or higher (in this example).
Advantages:
No need to supply the SAP Support Package on the destination release after the upgrade
No (temporary) downgrade
© SAP AG
ADM326
8-4
SAP Support Packages (2)
Example: Field ‘E‘ was delivered
in SAP_HR SP 140 of SAP R/3 4.6C and SAP_HR SP 4 of SAP ECC 6.05
TABLE X
TABLE X
SAP
ECC 6.05
SPAM
A
B
C
D
A
OK
SAP
R/3 4.6C
OK
TABLE X
B
C
D
E
new field ‘E‘
SAP_HR SP 4
TABLE X
SPAM
A
B
C
A
B
C
E
new field ‘E‘
SAP_HR SP 140
If 4.6C SP 140 is the start configuration: bind at least SP 4 to the upgrade!
An example of why binding SAP Support Packages is necessary:
Imagine, the field E has been shipped in SAP R/3 4.6C SAP_HR Support Package 140 and SAP
ECC 6.05 SAP_HR SP 4.
If the start release is 4.6C with SAP_HR Support Package 140 or higher an upgrade to SAP
ECC 6.05 SAP_HR Support Package lower than 4 would drop the field! The data would be lost.
Even if the SAP_HR Support Package 4 was applied after the upgrade, the data of field E still is
lost.
An upgrade of SAP R/3 4.6C SAP_HR Support Package level 140 should got to SAP ECC 6.0
SAP_HR Support Package 4 or higher.
PREPARE calculates the so called Equivalence Level (not available with start release 3.1I).
© SAP AG
ADM326
8-5
New Features in AS ABAP 6.x/7.x:
Queue Calculation (Example)
IS-B
IS-A
HR
APPL
ABA
BASIS
4
3
3.0
2.0
4.6C
4.6C
4.6C
4.6C
140
56
56
56
Condition for IS-A
+
Upgrade DVD
IS-A
IS-B
Queue of EHP5-parts, Add-Ons, SPs… Condition for IS-B
only one step
to the system you like
IS-B
IS-A
HR
APPL
ABA
BASIS
5.0
3.0
6.05
6.05
7.02
7.02
1
2
4
3
2
2
The queue calculation is necessary to determine, in which sequence the SAP Enhancement Package
5 for SAP ERP 6.0 software components, Add-Ons and SAP Support Packages have to be applied to
the new repository (to the shadow repository).
This is, because SAP Support Packages can be based on each other and Add-Ons may require a
certain Support Package level.
© SAP AG
ADM326
8-6
Handling of Add-ons/Software Components
Depending on the situation in the old and the new release, during
an upgrade the following is possible:
Additional software component is newly installed as
standard component
Existing Add-on becomes part of standard delivery
Existing Add-on becomes part of other standard
components
Existing Add-on is upgraded
Existing Add-on is kept as it is (keep)
Existing Add-on is deleted (active/passive)
Add-on is newly installed
Depending on the situation in the old and the new release, during an upgrade the following is
possible:
A additional software component is newly installed as standard component: for example the
software components from the Extension Set
Existing Add-on becomes part of standard delivery: for example in SAP R/3 4.6C IS-U is an
Add-on, in SAP ECC 6.0 it is in standard delivery (Enterprise Extension IS-UT)
Existing Add-on becomes part of other standard components: for example the Plug-in (PI) is an
Add-on in SAP R/3 4.6C, but part of standard components in SAP ECC 6.0
Existing Add-on is upgraded: for example from a release fitting the old SAP R/3 4.6C to a
release fitting the new SAP ECC 6.0
Existing Add-on is kept as it is: for example because it fits just as well the old SAP R/3 4.6C as
the new SAP ECC 6.0 (option 'keep')
Existing Add-on is deleted: because it is not needed any longer (active or passive deletion)
Add-on is newly installed: it is possible to install a new Add-on during the upgrade
© SAP AG
ADM326
8-7
Upgrade of Components 7.02
Industry
Extensions
(none selected here)
Enterprise
Extensions
© SAP AG
ADM326
8-8
IS_SELECT: Selection
© SAP AG
ADM326
8-9
Decision about Add-On
Upgrade with Add-On CD: Add-On upgrade with supplement CD (must be mounted). If the
supplement CD contains a SAINT attribute package (AOS), it is handled by the Add-On queue
calculation (phase ADDON_QCALC)
Upgrade with SAINT package: Add-On upgrade with SAINT package (AOU). Package must be
available in <EPS>/in directory and is automatically uploaded. Add-On upgrade is handled by the
Add-On queue calculation (phase ADDON_QCALC)
Upgrade to version on std. upgrade CDs: Only possible for Add-Ons that are delivered with the
Upgrade. This is the default selection for these Add-Ons. Must be changed only if a newer version is
available and you want to include it (usually for PI and PI_BASIS Add-Ons)
Keep (with vendor key): Component upgrade only. Only possible for Add-Ons that refer to
components that remain unchanged in the upgrade. This is the default selection for these Add-Ons.
Add-On is transferred unchanged to new release
Delete: Passive deletion. Only possible if the Add-On is not protected (that is, listed in file
<putdir>/bin/IS_PROTECT.LST)
Delete with CD: Active deletion with a deletion CD (must be mounted).
no decision yet: Decision is needed. Default selection for all optional Add-Ons. Phase can be
finished successfully only when all Add-Ons have been determined
© SAP AG
ADM326
8-10
BIND_PATCH: Selection
Minimum SAP Support Package Level (min)
Required for the given Add-On selection
Available only after successful Add-On queue calculation (phase ADDON_QCALC)
Set to <unknown> if Add-On queue calculation not successful
An SAP Support Package selection that does not meet the minimum package levels leads to an
error.
Equivalent SAP Support Package Level (equi)
SAP Support Package level that is equivalent to the level for the source release
<unknown> if equivalent level could not be determined (for source release 3.1I, for example)
To avoid loss of data we strongly recommend that you include enough Support Packages to
reach the equivalent level.
An SAP Support Package selection that does not meet the equivalent package levels leads to a
warning.
Current SAP Support Package Level (current) is the maximum package level that
Is delivered with the upgrade
Has already been selected (and confirmed) by the customer
Is already installed in the customer system, if the release of the component does not change with
the upgrade (only relevant for component upgrades)
© SAP AG
ADM326
8-11
Availability of SAP R/3, SAP R/3 Enterprise, and
SAP ECC Add-Ons (1)
Availability of SAP R/3, SAP R/3 Enterprise and SAP ECC Add-Ons
IndustrySpecific
Component
SAP R/3 3.1I4.6B
Aerospace &
Defense
SAP Aerospace
& Defense
Add-On (4.0B,
4.5B)
Aerospace &
Defense
SAP Discrete
Industries
Apparel &
Footwear
SAP Apparel &
Footwear
Automotive
SAP Discrete
Industries
Banking
SAP Banking
Consumer
Products
SAP Beverage
Consumer
Products
SAP Catch
Weight
Management
Engineering,
Construction &
Operations
SAP
Engineering &
Construction
Industry
Solution
SAP R/3 4.6C
Add-On (4.0B,
4.6B)
SAP R/3
Enterprise
47x200
SAP ERP 2004
SAP ERP 6.0*
SAP ECC 5.0
SAP ECC 6.0*
Add-On
Industry
Extension*
integrated into
SAP Discrete
Industries
Add-On
Add-On (3.1I,
4.5B)
SAP R/3
Enterprise
47x110
Add-On
Add-On
Add-On
Add-On
Add-On
Add-On
Industry
Extension
Add-On
Add-On
Industry
Extension*
Industry
Extension
Industry
Extension
Industry
Extension*
Industry
Extension
(limited)
Industry
Extension
(limited)
Industry
Extension*
(limited)
Add-On
Add-On (4.5B)
Industry
Extension*
integrated into
SAP Discrete
Industries
This and the next slide show the impact of Add-Ons when choosing a target release.
If an Add-On is not offered for a release, it is not possible to perform an upgrade to this release!
© SAP AG
ADM326
8-12
Availability of SAP R/3, SAP R/3 Enterprise, and
SAP ECC Add-Ons (2)
Availability of SAP R/3, SAP R/3 Enterprise and SAP ECC Add-Ons
Industry
Solution
IndustrySpecific
Component
SAP R/3 3.1I4.6B
SAP R/3 4.6C
SAP R/3
Enterprise
47x110
SAP R/3
Enterprise
47x200
Add-On
Industry
Extension
Industry
Extension
Add-On
Add-On
SAP ERP 2004
SAP ERP 6.0*
SAP ECC 5.0
SAP ECC 6.0*
Industry
Extension
Industry
Extension*
Financial
Service
Providers
SAP Corp.
Finance
Management
Healthcare
SAP Patient
Management
Add-On (4.0B)
Add-On
High Tech
SAP High Tech
Add-On (4.5B,
4.6B)
integrated into
SAP Discrete
Industries
High Tech
SAP Discrete
Industries
Add-On
Add-On
Higher
Education &
Research
SAP Campus
Management
Add-On
Add-On
Add-On
Industry
Extension*
Insurance
SAP Insurance
FS-CD
Add-On
Add-On
Add-On
Industry
Extension*
Insurance
SAP Insurance
FS-CM
Add-On
Add-On
Add-On
Industry
Extension*
Insurance
SAP Insurance
FS-CS
Add-On
Add-On
Add-On
Industry
Extension*
Add-On (4.5B,
4.6B)
Industry
Extension*
Add-On
Industry
Extension*
* Information on availability with SAP ERP 6.0 / SAP ECC 6.0 reflects current planning status and is subject to change.
© SAP AG
ADM326
8-13
Availability of SAP R/3, SAP R/3 Enterprise, and
SAP ECC Add-Ons (3)
Availability of SAP R/3, SAP R/3 Enterprise and SAP ECC Add-Ons
Industry
Solution
IndustrySpecific
Component
Insurance
SAP Insurance
FS-RI
Media
SAP IS-M
Mill Products
SAP R/3 3.1I4.6B
SAP R/3 4.6C
SAP R/3
Enterprise
47x110
SAP R/3
Enterprise
47x200
Add-On
Add-On
Add-On
Add-On (4.0B)
Add-On
Add-On
Add-On
SAP Cable
Solution
Add-On (3.1I,
4.5B)
Add-On
integrated
into SAP
Discrete
Industries
Mill Products
SAP Mill
Products
Add-On (4.5B,
4.6B)
Add-On
integrated
into SAP
Discrete
Industries
Mill Products
SAP Discrete
Industries
Mining
SAP Mining
Add-On (4.6B)
Add-On
mySAP PLM
SAP
Environment,
Health & Safety
Add-On (4.5B,
4.6B)
Add-On
Oil & Gas
SAP Oil & Gas IS-Oil
Add-On (4.0B,
4.6B)
Add-On
Add-On
SAP ERP 2004
SAP ERP 6.0*
SAP ECC 5.0
SAP ECC 6.0*
Industry
Extension*
Add-On
Add-On
Industry
Extension
Industry
Extension
Add-On
Industry
Extension*
Industry
Extension*
Industry
Extension
Industry
Extension*
Industry
Extension*
* Information on availability with SAP ERP 6.0 / SAP ECC 6.0 reflects current planning status and is subject to change.
© SAP AG
ADM326
8-14
Availability of SAP R/3, SAP R/3 Enterprise, and
SAP ECC Add-Ons (4)
Availability of SAP R/3, SAP R/3 Enterprise and SAP ECC Add-Ons
SAP ERP 2004
SAP ERP 6.0*
SAP ECC 5.0
SAP ECC 6.0*
Industry
Extension
Industry
Extension*
Industry
Extension
Industry
Extension
Industry
Extension*
Industry
Extension
Industry
Extension
Industry
Extension
Industry
Extension*
Add-On
Add-On
Add-On
Industry
Extension*
Add-On (4.6B)
Add-On
Add-On
Add-On
Industry
Extension*
SAP IS-U/CCS
Add-On (4.6B)
Add-On
Add-On
Add-On
Industry
Extension*
Utilities
SAP IS-U/FERC
Add-On (4.6B)
Add-On
Add-On
Industry
Extension
Utilities
SAP IS-WASTE
Add-On
Add-On
Add-On
IndustrySpecific
Component
SAP R/3 3.1I4.6B
Oil & Gas
SAP Oil & Gas JVA
Add-On (4.0B,
4.5B, 4.6B)
Add-On
Industry
Extension
Industry
Extension
Public Sector
SAP Funds
Management
Add-On (4.0B,
4.6B)
Add-On
Industry
Extension
Public Sector
SAP HR Public
Sector
Add-On (4.0B,
4.5B, 4.6B)
Add-On
Public Sector
SAP Public
Sector PSCD
Telecommunicat
ion
SAP RM-CA
Utilities
Industry
Solution
SAP R/3 4.6C
SAP R/3
Enterprise
47x110
SAP R/3
Enterprise
47x200
Industry
Extension
Industry
Extension*
Industry
Extension*
* Information on availability with SAP ERP 6.0 / SAP ECC 6.0 reflects current planning status and is subject to change.
© SAP AG
ADM326
8-15
Availability of Other Add-Ons
Availability of Other Add-Ons
Industry Solution
Industry-Specific
Component
SAP Basis 4.6C
SAP Web AS
6.10
SAP Web AS
6.20
SAP NetWeaver
AS 2004
Add-On
Add-On (SAP
Web AS 6.20,
SAP BW 3.1
Content)
Add-On
Banking
SAP Bank Analyzer
Banking
SAP CYT
Management
Banking
SAP Account
Management
Media
SAP IS-M/AMC
Add-On
Retail
SAP Forecasting
& Replenishment
Add-On (SAP
SCM 4.1)
Utilities
SAP IS-U/UCES
Add-On
Add-On
SAP NetWeaver
AS 7.0
Add-On
Add-On*
Add-On
Add-On*
Add-On (SAP
SCM 5.0)*
* Information on availability with SAP NetWeaver 7.0 reflects current planning status and is subject to change.
© SAP AG
ADM326
8-16
Agenda: Downtime
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
9-1
Downtime
Contents:
What is downtime?
What causes the downtime during an upgrade?
How can downtime be reduced?
© SAP AG
Outlook: Near Zero Downtime Upgrade
ADM326
9-2
What is Business Downtime?
Uptime: end users can use
the system’s applications in
production
Production
operation
SAP system is not available
for end users
“
Downtime
High availability is the requirement to maximize system
availability from an end-users point of view.
Business downtime is the duration, in which an end user cannot use the systems applications in
production.
Why downtime?
The big advantage of SAP‘s Upgrade technology is, that we allow our customers to adapt,
extend and modify SAP software, and these extensions will be kept and adjusted to the new
release during the Upgrade process. Most of the required processing steps can be performed
during system uptime.
Downtime is necessary, whenever live running transactions have to be replaced by new
functionality, and a potential risk of data inconsistency is given, i.e. changing the processing
logic, or changing the data model/structure.
© SAP AG
ADM326
9-3
Causes for Downtimes and Measures
Unplanned downtime
Planned downtime
Hardware/OS failures
Other disasters
Application failures
Operating / handling errors
Unintentional data deletion
…
System/system landscape &
infrastructure maintenance
Having a highly available technical
infrastructure in place is crucial in order
to reduce 'unplanned downtimes'
From a technical infrastructure point of
view, the architectural and technical
single point of failures (SPOF) need to be
identified and secured in an appropriate
manner.
Patches, release upgrades,
Deployment / transports
Configuration changes
...
Improved/optimized Upgrade and
patch processes
Proven software lifecycle
management and propagation
engines (i.e. enhanced CTS)
To be avoided with scalable components
which enable rolling maintenance
“Human errors” (= 80% of downtime
causes) to be addressed by ease of
system management and with improved
change and problem management
processes
not solvable by automatic
switchover!!
© SAP AG
Main causes for unplanned downtime
HW, OS failures,
disasters
20%
Application
failures
40%
Operator
errors
40%
Source: Gartner Group
ADM326
9-4
Planned Downtime - Availability Impact
Weekly
High
frequency
Monthly
Offline
backups
without splitmirror
Offline
backups with
split-mirror
Kernel
patches
Transports
Profile
parameter
changes
SAP Support
Packages
Quarterly
End of
daylight
saving time
Yearly
SAP
enhancement
package
Release
upgrades
OS/DB migration /
Database
Unicode
reorganizations
conversions
Single
Low
frequency Event
Minutes
0,5 … 2 hours
10…15 hours
Short duration
20…48 hours
Long duration
© SAP 2010
Overall guideline:
Avoid frequent downtime with long downtime period.
Frequent events need to be minimized regarding the downtime
Offline backups need to be avoided
Database reorganizations should be a rare occurrence
© SAP AG
ADM326
9-5
The High Availability Scale
Availability
Downtime per
week
Weekly downtime usable
for (examples)
Downtime
per year
Yearly downtime usable for ….
99,9999%
0,6 sec
??
30 sec
??
99,999%
6 sec
Weekly fast switchover
5 min
1 yearly restart (?)
99,99%
1 min
Daily fast switchover
52 min
One short offline software
maintenance per year
One offline software
maintenance per year
ACHIEVABLE
ACHIEVABLE TODAY
TODAY
99,9%
10 min
1 Weekly restart
8 hours 45
min
99%
1h 40 min
Offline software
maintenance
87,5 hours
90%
16h 48 min
1 Offline backup per week
36 days
© SAP AG
ADM326
9-6
Downtime Costs versus Availability Costs
Availability cost curve
(Source: Gartner Group)
Cost
costs
downtime
95%
98%
Downtime costs are usually not linear over
the time of system outage
They depend on the business impact
For longer downtimes costs can increase
progressively
Example: when SCM processes are stuck
longer than 3 hours the whole production will
be stuck and cause even higher costs
© SAP AG
ADM326
99,5%
Costs
99,9%
Availability
Redundant components
Disaster recovery site
System management tools
IT staff
Capacity planning
Guaranteed SLA
Proactive services
9-7
Planning the Upgrade Strategy: Purpose
I
su m p
bs ort
pr se titu of
o
t
op du t in ion
c
er ti
at on
io
n
ve
hi e
c
d
Ar m o f
e
o as
b
ta
da
Upgrade
Strategy
of
e
in
z
Si erta ase
c tab es
l
da tab
M
pe axi
do rm mu
wn itte m
tim d
e
© SAP AG
Database
backup
ADM326
9-8
Decoupling of OS, DB and SAP Upgrade
New SAP version may require
new database version
new operating system version
SAP
DB
OS
The start release of SAP software
runs on
target release DB and
target release OS
Destination
release
configuration
Start release
configuration
SAP
DB
OS
System downtime
Recommendation: Split into different maintenance slots!
SAP usually also releases 'older' SAP releases on DB and OS versions higher than those used
initially
This enables customers to run an SAP release on the latest DB and OS versions if required. Thus the
maintenance periods of SAP releases can be enlarged.
During the upgrade of an SAP / DB / OS combination this feature may be used to split up the system
downtime (e.g. into two different weekends):
First, do the upgrade of DB and OS to the version required by the target release of SAP system.
Second, upgrade SAP system to target release.
© SAP AG
ADM326
9-9
Production Downtime During Upgrade
Downtime behavior with standard, high and low resource use.
'Standard and High Resource Use' refers to the 'Downtime minimized' strategy
'Low Resource Use' refers to the 'Resource minimized' strategy
© SAP AG
ADM326
9-10
Production Downtime During Upgrade
What are the elements of production downtime?
Upgrade technical runtime (SAPup) – most of this is not production downtime!
Post-upgrade transports & manual adjustments
Business validation & acceptance testing
Possibly pre- and post-upgrade system backups
Business ramp-down & ramp-up
rampup
up
down
up
SAPup:
PREPARE
&
repository
import
SAPup:
conversion,
XPRAS, etc.
transports &
manual tasks
Business
validation
tests
down
rampdown
backup?
Basis
go/no-go decision
Functional/
business
backup?
Operations
Begin and end of downtime is not only a 'click' but could be a complex process: for example
stopping the production line with all its implications.
Both could take hours of time. So this should be called 'ramp down' and 'ramp up' instead of just
'stop' and 'start'.
© SAP AG
ADM326
9-11
Potential to Reduce Downtime
go/no-go decision
up
down
SAPup:
PREPARE
&
repository
import
before
rampdown
SAPup:
conversion,
XPRAS, etc.
1
ramp-up
up
2
down
backup?
Business
validation
tests
Transports &
manual tasks
backup?
Basis
ramp-up
Functional/
business
Operations
up
down
up
SAPup:
PREPARE
&
repository
import
SAPup:
conversion,
XPRAS, etc.
down
after
backup?
go/no-go decision
The highest potential lays in:
Speeding up the delta transports and manual tasks (for example using a Customer Based
Upgrade)
Speeding up business validation test (for example using tools like eCATT)
© SAP AG
ADM326
9-12
Influencing Factors for Runtime & Downtime
1
3
2
Downtime
Type & performance of
the storage
(I/O throughput)
Number and type of
CPU´s for the app. & DB
server
Type & performance of
Runtime
the Storage
Number and type of
CPU´s for the app. & DB
server
4
Software
Hardware
Configuration
Start & target Release
Upgrade
Version of the Upgrade
parameterization (e.g.
number of processes)
Number of clients
tools
Productive applications/
Upgrade
parameterization (e.g.
number of processes)
Number of included SAP
Support Packages
Number of modifications
(downtime or resource
minimized)
Usage of Incremental
Usage of Incremental
Conversion (ICNV)
Number of installed
languages
on standard SAP objects
Version of the Upgrade
Upgrade strategy
Conversion (ICNV)
Add-Ons or industry
solutions
Start & target release
Strategy
Import destination time
tools
Productive applications/
Add-Ons or industry
solutions
“
Each system is highly individual regarding it‘s configuration and
application data runtime/downtime forecasts are only possible
when analyzing results of a test upgrade with production data !
Upgrade runtime: Total duration of the upgrade controlled by SAPup including preparation and
uptime activities.
Runtime and downtime depend on:
Hardware and operating system: The whole upgrade runtime depends on the hardware and
operating system you use.
Hard disk configuration: Input/output throughput, backup speed
Database: Size of tables, database configuration, parameter tuning
Number of modifications: SPDD and activation time
Number of data structure conversions: Phase PARCONV; depends on start/target releases;
bigger leaps mean more data conversions
Productive applications: More productive applications mean more data conversions
Number of clients: Client cascade in phase TABIMP
Number of installed languages: More data import
Upgrade strategy: More or less down- and runtime
A test upgrade on a production system mirror (sandbox system upgrade) and thorough analysis of the
upgrade log files can highlight many possibilities for effective manual tuning activities early in the
project.
© SAP AG
ADM326
9-13
Phases
Upgrade Tuning Within SAP Standard
Actions to Reduce Runtime & Downtime
Prepare
Upgrade
downtime
Upgrade uptime
Follow-up
activities
Usage of new hardware
Actions to reduce downtime
Usage of the latest Upgrade software/tools (SAP ECC 6.05 / SAPup / Fixbuffer)
Usage of 'Downtime minimized' upgrade strategy
Use as many parallel upgrade processes as possible
Including all required SAP Support Packages into the upgrade
Use transports created for automatic mod. Adjustment
(SPDD/SPAU)
Set import destination time
Usage of ASU Toolbox
Usage of ICNV
Usage of
Upgrade Accelerator / ASU
Create well thought out cutover plan
Hardware
Backup strategy
Software & tools
Configuration
Test automation for
business validation
Strategy
© SAP AG
ADM326
9-14
Upgrades to SAP ECC 6.0:
Business Downtime by Source Release1
Business downtime in hours
Median: 33,0
SAP R/3
4.7
Min: 15,5
0
12
24
Max: 71,0
36
48
60
72
84
96
108
Hours
based on 76 upgrades
Business downtime in hours
Median: 48,0
SAP R/3
4.6C
Min: 24,0
0
12
24
Max: 86,0
36
48
60
72
84
96
108
Hours
based on 131 upgrades
1
based on Upgrade Experience DB
Business downtime: Total time that the system is not available for end users, including the technical
downtime plus the time necessary for data backup, final tests, etc.
© SAP AG
ADM326
9-15
Upgrades to SAP ECC 6.0 –
Project Duration in Weeks
Project duration in weeks
Median: 15,8
SAP R/3
4.7
Min: 7,0
0
4
8
12
Max: 30,9
16
20
24
28
32
Weeks
36
40
44
48
52
based on 82 upgrades
Project duration in weeks
Distribution of values
Median: 21,0
SAP R/3
4.6C
Min: 12,0
0
4
8
12
16
Max: 35,0
20
24
28
32
Weeks
36
40
44
48
52
based on 154 upgrades
On an average an upgrade project takes around 21 weeks (with an SAP R/3 4.6C start release). But
the range is quite large. This is because an upgrade project is highly individual and depends on the
special circumstances and environment of the landscape.
© SAP AG
ADM326
9-16
Upgrades to SAP ECC 6.0:
Technical Downtime
Technical downtime:
Downtime
250
Total time during which the system
cannot be used productively. This
does not include time for data
backup, testing etc.
200
# Upgrades
Average technical downtime:
8.3 h
150
Upgrade strategies: Downtimeminimized, resource-minimized
Number of Systems Analyzed: 755
100
< 18
17
15
31
11
9
7
5
3
0
0
50
Hours (average 8.3)
© SAP AG
ADM326
9-17
Upgrade Tuning (in Addition to Standard)
Hardware
I/O throughput of the storage /
more and faster CPU‘s
Tools
Use latest Support Release
for Upgrade
Service
Cutover
Planning
1
Downtime
Optimization Service1
Parallelize
tasks
Use new backup tools &
strategy
Use Incremental Conversion
(ICNV) if possible
Customer Based
Upgrade (CBU)
Improve backup
strategy
Upgrade
Coach2
Automate testing for
GO decision
Service is part of SAP's Premium Support (AGS)
guidance to reduce downtime
2 Gives
With these tuning methods the downtime can be reduced.
© SAP AG
ADM326
9-18
Transaction ICNV: Reduction of Upgrade
Downtime
Reduction of upgrade downtime
Large tables are now converted during uptime
Only switch to new structure during downtime
(in PARCONV)
Easy handling
Fully integrated into upgrade process
Configurable conversion process
Exclusion times
Progress prediction
Because most data is converted before the beginning of downtime, downtime can be reduced by
several hours. The actual reduction depends on the table size. The dependence of downtime on the
database size is also strongly reduced. The downtime can be predicted more accurately.
Conversion of large tables during system uptime
Conversion process can be stopped and restarted
Possible error situations during uptime
ICNV especially suited for WORM tables
ICNV is fully integrated into the upgrade
Tables to be processed by ICNV can be selected
Conversion process is configurable
Additional resource usage of DBMS
Sufficient number of background work processes
Execute ICNV as early as possible
© SAP AG
ADM326
9-19
Application-Specific Upgrade (ASU) Toolbox
Description
Example
Management tool for application specific
manual preparation and follow-up task
such as
Restoring of certain user specific settings
Manual transactions or correction reports to
be started after upgrade
Reports needing manual input by users
Special data migrations
Integrated with SAPup and Solution
Manager
Delivered via support tool plug-in ST-PI
Refer to SAP Note 1000009
Benefits
More efficient preparation and execution
of upgrade relevant application tasks
Less manual efforts during upgrade
Higher business stability after upgrade
© SAP AG
ADM326
9-20
Upgrade Accelerator
The
Upgrade Accelerator executes known and automatically executable additional
preparation and follow-up activities.
This reduces significantly the number and efforts spent with additional
manual upgrade steps!
The
Upgrade Accelerator is being executed automatically during the preparational
phases and at the end of the downtime:
Preparational phase: RUN_UACC_PREP
End of downtime:
RUN_UACC_POST
The
add-on ST-PI delivers the Upgrade Accelerator Framework. It is being checked
as an upgrade requirement by SAPup in phase ASU_CHK.
The
newest content is available via the SAPup Fix Buffer as download from SAP
Service Marketplace.
© SAP AG
ADM326
9-21
Database Size and Upgrade
No direct relation between DB size and
upgrade downtime
Scatter plot downtime vs. DB-Size
100
Some tables that undergo structural changes
may have to be converted and therefore
affect the downtime
90
80
Downtime/h
70
60
50
40
30
20
10
0
0
100 200 300 400 500 600 700 800 900 1000
DB-Size/GB
Source: Analysis of RSUPGSUM reports of SAP R/3 4.6C Upgrades
“
Upgrade without Unicode conversion:
Archive and delete only selectively
“
Unicode conversion: Archive and delete
as much as possible
Q: Does the total database size affect the upgrade downtime? A: No, only in special cases the size of
single tables may have an effect on upgrade downtime.
Q: Why may some tables affect upgrade downtime? A: The following situations require downtime:
Structural changes of the table or index such as changed field length and altered index will lock
the table and can only take place during downtime. The fewer records are contained in that
table, the faster the operation can be performed.
Functional and design changes require an update of the table content.
Note: Besides reducing the table content, other technical tuning options such as parallelization of the
index creation should be investigated because they may be easier to implement than archiving or
deletion.
Q: Will new fields added to an existing table cause downtime? A: No, only in the case of these
exceptions:
iSeries (AS/400): To change the table structure all records of the previous table have to be
copied and transferred to the new table structure.
All DB systems: In some cases the new fields are initialized with a default value. This value has
to be updated in every record of the table and will therefore require downtime.
Q: How to determine which tables may increase upgrade downtime? A: The most precise way is to
do a test upgrade and evaluate the upgrade log, especially the parts: DDLs, conversions and XPRAs.
© SAP AG
ADM326
9-22
Near Zero Downtime Upgrade (NZDT)
Summarized customers’ requirements
The requirements of the customers
Business
Downtime for a release upgrade is 2 - 4 hours
In
case of problems the procedure is completely resettable
Upgrade procedure should be reusable for all SAP systems, initially R/3
The
procedures should also be applicable for SAP Support Packages
The method can be used for numerous downtime events
Upgrade
Upgrade and Unicode Conversion
Upgrade and OS/DB Migrations
… and also
OS patch
HW replacement
DB reorg
© SAP AG
ADM326
9-23
Technologies for Near Zero Downtime
Consistent system copy (clone) with the logging of database changes
Normal Upgrade / Unicode conversion
Synchronization of the changes between the main system and the copy – delta replay
Transports, Pre-Validation while Uptime
PRD
R/3 4.6C nUC
hostA
downtime
PRD
R/3 4.6C nUC
hostB
PRD
ECC 6.0 UC
hostB
+ Transports
+ Add Ons
+ Pre-Testing
Upgrade + UC Downtime
© SAP AG
Final-Validation
Upgrade
and Unicode conversion
Infrastructure
adjust. - interfaces
hostA
Last Delta replay
clone
Prepare + Upgrade Uptime
Delta replay
Recording
Post Processing
ADM326
Delta
Transfer
Infra
structure
Vali
dation
9-24
Technologies for Near Zero Downtime
Consistent system copy (clone) with the logging of database changes
Normal Upgrade / Unicode conversion
Synchronization of the changes between the main system and the copy – delta replay
Transports, Pre-Validation while Uptime
PRD
ECC 6.02
hostA
downtime
Final-Validation
Infrastructure
adjust. - interfaces
hostA
Last Delta replay
clone
Prepare + Upgrade Uptime
Delta replay
Recording
PRD
ECC 6.05
hostB
SAP Enhancement Package 5 for SAP ERP 6.0
PRD
ECC 6.02
hostB
+ Transports
+ Add Ons
+ Pre-Testing
EHP installation downtime
© SAP AG
Post Processing
ADM326
Delta
Transfer
Infra
structure
Vali
dation
9-25
Near Zero Downtime
Architecture
Including Upgrade logic
freeze
freeze
Customizing
ignore
System tables
ignore
Repository
© SAP AG
Z-Cust.
Application data
Customizing
Z-Application data
Application data
Z-Application data
Allow changes
Delta
Hot clone + enhancement package
Delta
Z-Cust.
System tables
Repository
ADM326
9-26
Comparison of Business Downtimes
Standard Method versus NZDT
Standard EHP implementation with SAPehpi
backup?
SAPehpi: conversion,
XPRAS, etc.
SAPehpi:
PREPARE &
repository import
up
transports
& manual
tasks
down
go/no-go decision
backup?
freeze
business
validation
tests
rampdown
rampup
up
Replicate Data
SAPehpi:
PREPARE &
repository import
SAPehpi: conversion,
XPRAS, etc.
transports
& manual
tasks
Final
Delta
sync
down
NZDT Upgrade
Basis
© SAP AG
Functional/ business
ADM326
Operations
9-27
Near Zero Downtime for SAP ECC
Minimizing Planned Downtimes
Near Zero Downtime method as a tool for minimizing downtimes
Applicable for
Effort per execution
Upgrade
Release upgrade
SAP Support Package updates
Customizing waves
DB maintenance – table reorganization
OS or DB patch
DB reorg
SAP enhancement
package
SAP Support Packages
DB reorg
Number of executions
© SAP 2010
© SAP AG
ADM326
9-28
Agenda: Planning and Preparation
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
10-1
Planning and Preparation
Contents:
Upgrade as a project
Upgrading a three system landscape
Upgrade Dependency Analyser (UDA)
Technical aspects
Upgrade experiences
© SAP AG
Further information
ADM326
10-2
Unit 10: Overview Diagram
Unit 10 – Upgrade Planning and Preparation
Lesson 1: Upgrade as a Project
Lesson 2: Upgrade of a Three System Landscape
Lesson 3: Upgrade Dependency Analyzer
Lesson 4: Technical Aspects
Lesson 5: Upgrade Experiences
Lesson 6: Further Information
© SAP 2010
© SAP AG
ADM326
10-3
Upgrade Project: Key Questions
Key Questions
Will the upgrade go live
on time?
Will the solution still do
what we designed it to?
How do we minimize the
disruption to business?
Have we identified all
the potential risks?
Will the system perform
at optimal levels?
© SAP AG
ADM326
10-4
Key Success Factors for any Upgrade Project
Ensure a smooth system landscape transition
Plan your IT infrastructure
Manage parallel changes
Adapt applications
Ensure business continuity
Perform data operations
Minimize business downtime
“
Managing these focus topics is the key for a
successful upgrade project
Based on SAP experiences in consulting, support and development seven key challenges have been
identified that are relevant for any upgrade project. If you manage to control them the project will
succeed, if not serious issue will arise.
© SAP AG
ADM326
10-5
Main Challenges when Planning and Executing
an Upgrade – Worldwide Results
Plan
Build
Estimate cost & effort
69%
Define business case
Efficient testing
64%
46%
Downtime minimization
Define and allocate
project team/resources
46%
Downtime minimization
46%
54%
Modification adjustment
Assess impact on
existing solution
29%
Interoperability
28%
Compliance
considerations
47%
End user training
39%
IT infrastructure/sizing
39%
14%
Others
N=1484
Project management
43%
Find information on
upgrade methods & tools
48%
Others
4%
0%
20%
40%
60%
80%
100%
N=1484
5%
0%
20%
40%
60%
80%
100%
The report includes answers from the following 360° Upgrade adoption programs: North America (Jan 2008), Brazil (March 2008), Germany (March 2008), Japan
(March 2008), UK & Ireland (March 2008), Australia (April 2008), Sweden (April 2008),China (May 2008), India (May 2008) and France (Sept 2008)
© SAP AG
ADM326
10-6
Possible Upgrade Approaches:
Think Big and Start Small
…are large projects…
…but with progressive scope !
Technical Upgrade
Affecting the whole
enterprise
Demanding in-depth
knowledge of
Fast
Business models
Processes
Application landscapes
Low costs
and manageable
impact
Application modification
Requiring strict planning
and precise timing
New
Functionality
Protect
investment
Take your
time
Generate
value
as you go
Serviceoriented
architecture
Discover,
prepare
and
get even
more
value
Think BIG and start SMALL!
Technical Upgrade: Reduction of modifications
y Eliminate modification not used: Up to 80% of all modification
y Replace modification with standard functionality: Up to 50% of all modifications
y Technical and functional optimization: Archiving, master date clean-up, interface optimization
Functional: Focus
y Modernization of the Core SAP ECC, stabilization of the basis
y Individualization of the user interface
Strategic: Focus
y Standardization
y Harmonization
y Consolidation
© SAP AG
ADM326
10-7
Upgrade to ECC 6.0:
Start and Target Release
You can directly upgrade:
from
(and above)
to
(and below)
SAP R/3 3.1I
SAP ECC 6.0
SAP R/3 4.0B
SAP ECC 6.0 EHP 3 or 4
SAP R/3 4.6C
SAP ECC 6.0 EHP >= 5
* AS/400: Start release must be >= 4.6C
Note: it is not possible to upgrade from SAP R/3 3.1I to ECC 6.03 and above anymore!
Starting from upgrades to ECC 6.05 only upgrades from start release 4.6C and above are supported!
© SAP AG
ADM326
10-8
Complexity Drivers
Business related levers
Number of modified
objects
Impact: medium to high
Number & type of ext.
interfaces
Source release
Code freeze strategy
Upgrade
project
complexity
drivers
OS / DB migration
requirements
Number of codepages
Type of Upgrade
(Technical/functional)
Number of Add-ons /
Industry Solutions
Testing requirements
IT related levers
Required downtime
Impact: medium to high
An upgrade project is more or less complex, depending on several drivers.
© SAP AG
ADM326
10-9
SAP Solution Manager
SAP
SAP Customer
Test
Workbench
Upgrade
Roadmap
E-learning mgmt.
Change Management
SAP Service
Marketplace
SAP Experts
End-to-end
solution operations
© SAP AG
ADM326
10-10
SAP Upgrade Road Map – Overview
EXAMPLE
DESCRIPTION
SAP's standard methodology to plan and execute
the upgrade of an SAP solution
Content: Best practices and templates for
project management, functional and technical
aspects facilitating key tasks of the entire project
team
Formats:
SAP
Solution Manager
HTML
version on SAP Upgrade Info Center
at: http://service.sap.com/upgraderoadmap
Availability:
Since
06/2004
Languages:
English, German
BENEFITS
Repeatable approach that helps to mitigate risks,
attack key time consumers and reduce costs and
effort
Central point of access to upgrade project
information and integrated use with SAP Solution
Manager
The SAP Upgrade Roadmap: On one side, this is a methodology, as the Upgrade Roadmap
represents SAP’s standard project methodology (it is a flavour of the ASAP methodology). On the
other side, it is a tool, as it is really a tangible application. It covers:
y Organizational/basic project management aspects
y Application-specific aspects
- Application and modification adjustments
- Test planning and execution
- End-user training and documentation
y Technology aspects
- IT infrastructure planning and re-sizing
- Administration and security concept
- Technical upgrade procedure
Target group:
y Project lead as well as
y Project team members
© SAP AG
ADM326
10-11
Upgrade as a Project – Plan, Build, Run
Upgrade
project
completed
Upgrade
project
started
Plan
Upgrade
Discovery
Define business and
IT requirements
Run
Build
Upgrade
Evaluation
Upgrade Implementation
Define
strategy
Operations &
Continuous
Improveme
nt
Minimize costs
and risks of Upgrade Project
Upgrade Roadmap
Project
Preparation
Document current
solution and set-up
project
Blueprint
Specify implementation
scope and solution
adjustment needs
Realization
Final Preparation
for Cutover
Implement and
adjust solution
Perform integration
and system tests
and plan cutover
Production
Cutover &
Support
Execute production
system Upgrade &
support
The Upgrade project does not start with the kick-off. Before an upgrade project some tasks has to be
done for defining business and IT requirements, define an upgrade strategy and create a business
case for the upgrade project during discovery and evaluation phase before the project starts itself.
Three different phases of an upgrade project:
y Plan
y Build
y Run
Use SAP Upgrade Roadmap to handle the complete 'Build' phase
© SAP AG
ADM326
10-12
Key Activities in the Discovery Phase
Plan
Upgrade
Discovery
Build
Upgrade
Evaluation
Project
Preparation
Blueprint
Realization
Update Corporate Business and IT strategies
Define Business Requirements
Document current status of business solution
Identify impact of corporate business strategy on current
business solution
Identify existing gaps and issues
Define future business needs
Understand new functions and features of SAP target
solution
Map requirements to possible target solutions
Production
Cutover
& Support
Create Upgrade Master Plan
Identify and design possible target solution landscapes
(releases and software components) that meet business
and IT requirements
Perform high-level analysis of how changes affect the
complete solution landscape (including technical
platform, SAP and non-SAP software)
Evaluate migration paths to possible target landscape
and determine best option
Create business case
Define IT Requirements
Final Preparation
for Cutover
Identify TCO of the as-is solution and costs for adaptation
to business requirements in existing landscape
Document current solution landscape
Estimate TCO of planned target landscape
Identify impact of corporate IT strategy on current solution,
for example. including provider model and data center,
hardware and platform strategies
Estimate upgrade project costs and general change costs
Formulate business value proposition
Create business case
Define maintenance strategy for solution
Understand new technology features of possible SAP
target solutions
Considerations that help to define the IT requirements are as follows:
y Which changes are intended in the foreseeable future, either driven by the corporate IT program
management or by local system owners?
y Is a change of the provider model planned? May systems get moved into a hosting scenario?
y Will geographical re-locations take place, for example, centralization or de-centralization?
y Is it possible to merge servers into one data center?
y Will global agreements with hardware vendors about new architectures be negotiated regarding
new CPU type, blade server, adaptive computing and so on?
y Does the global policy regarding operating system or database product change?
y Regarding an SAP maintenance contract, what type of contract situation do you have: standard
maintenance, extended maintenance, or customer-specific maintenance?
© SAP AG
ADM326
10-13
Key Project Activities of a Technical Upgrade
at a Glance
Plan
Upgrade
Discovery
Build
Upgrade
Evaluation
Project
Preparation
Blueprint
Realization
Final Preparation
for Cutover
Production
Cutover
& Support
Project Management
Time planning: Dependencies to other implementation or roll-out activities, project runtime
Budgeting: IT costs; project costs (internal and external)
Resource planning: number of project members; skills; roles & responsibilities; external resources involved
Business Aspects
Application Adjustments:
Release Customizing: Upgrade Customizing / Delta Customizing
Redesign of missing SAP functionality: redesign; application and technology migration (if required)
Modifications/Custom Developments: Identification and elimination of unused code
Other adjustments: interfaces, forms, authorizations
Testing of key business processes
End-User Training: only if significant user interface changes and redesign / application adjustments were required
Technical Aspects
IT Infrastructure Adjustments / Sizing of new release: Server, Frontend; Network
Planning – Technical Upgrade Process: SAP application but also operating system and database
Planning - Backup Strategy: during and after the technical upgrade
Execution - Technical Upgrade: DEV, QAS and PRD system as well as additional project & training systems
Post Upgrade Activities: Performance analysis, reorganizational actions
© SAP AG
ADM326
10-14
Maintenance Optimizer
DESCRIPTION
Central tool for planning, executing, and
managing the installation of enhancement
packages, SAP Support Packages and patches
across the entire SAP landscape
Monitors the complete maintenance procedure
for your entire SAP solution.
ACCESS
SAP Service Marketplace at:
http://service.sap.com/solman-mopz
SAP Solution Manager 7.0 SP15 or higher
Data maintenance with Solution Manager
System Landscape (SMSY)
BENEFITS
Gain stability and access to innovation
Upgrade only the enhancements applicable
to your business
Reduce risk and downtime
Speed implementation and test less
© SAP AG
ADM326
10-15
Project Duration – Influencing Factors (1/3)
Strategy
Technical upgrade vs. upgrade with new functionality
New features and functions
New features in existing transactions
Number of new functionalities to implement
Modifications
Number of modifications, which could be returned to SAP
standard
Number and complexity of modifications needed in the
new release
Documentation
Level and quality of documentation of business processes,
custom programs, and modifications
Documentation for testing
Last but not least …
Hardware requirements
Range of testing and training
Customer or partner skills in upgrade projects
Management commitment and available resources
© SAP AG
ADM326
10-16
Project Duration – Influencing Factors (2/3)
Hardware requirements of the new release
Server
Frontend
Network
Sizing and system configuration for the new
release
Going Live – Functional upgrade check
Planning of technical upgrade process
Operating system, database, and SAP ERP
Planning a backup strategy
During the technical upgrade
After release upgrade
Executing of technical upgrade
Development, quality assurance, and productive systems
Training systems
Activities after upgrade
© SAP AG
Performance analysis, re-organizational actions
ADM326
10-17
Project Duration – Influencing Factors (3/3)
Determine software requirements
SAP Industry Solutions (most of them absorbed into SAP
ERP Central Component as of SAP ERP 6.0)
SAP country-specific versions
Third-party products or add-ons
Interfaces between SAP ERP and non-SAP software
Operating system and database
Communication protocols
© SAP AG
ADM326
10-18
Scheduling Factors (1/2)
Key Upgrade Considerations
Impact
Software license requirements
Any needed? … Allow for approval cycles, if required
Operating system/database upgrade
Does the operating system & database need to be upgraded?
Hardware upgrades
Add time & dependencies
Set-up of upgrade project system
infrastructure
Usually takes two weeks, unless hardware is needed
Unicode conversion
Will add more time to the project
Dependencies on other SAP software
components, e.g., Employee SelfService or SAP CRM
Additional time & effort if other components will be upgraded
Dependencies on non-SAP software
Early inquiries with vendors on SAP compliance
Installation of SAP enhancement
packages
Upgrade + plus install latest SAP enhancement package; allow time for installation
Functional enhancements
Usually require additional effort; requires separate scoping effort to assess impact
Business constraints
Timing & availability of resources for testing; amount of time production system will
& regression testing. Activating functionality will have a greater impact on the
project scope
be taken down during cut-over time.
© SAP AG
ADM326
10-19
Scheduling Factors (2/2)
Key Upgrade Considerations
Impact
Parallel projects
Planned projects that may affect the upgrade, change control/code freeze plans,
Landscape analysis
Upgrade of other SAP applications; analysis of source SAP system (volume &
complexity of custom modifications & developments; number of modules in use;
number of interfaces, number of end user)
Fiscal year end
Generally drives the go-live date
IFRS compliance
New G/L involves a GL migration project; upgrade typically before a new GL
migration project
© SAP AG
ADM326
10-20
Unit 10: Overview Diagram
Unit 10 – Upgrade Planning and Preparation
Lesson 1: Upgrade as a Project
Lesson 2: Upgrade of a Three System Landscape
Lesson 3: Upgrade Dependency Analyzer
Lesson 4: Technical Aspects
Lesson 5: Upgrade Experiences
Lesson 6: Further Information
© SAP 2010
© SAP AG
ADM326
10-21
Key Project Activities –
Project Preparation
Plan
Upgrade
Discovery
Build
Upgrade
Evaluation
Project
Preparation
Project work
Blueprint
Realization
Final Preparation
for Cutover
Production
Cutover
& Support
System landscape
Project Management Team:
Create project plan
Nominate project team
Plan and facilitate project team training
Order temporary hardware
Define test concept
Upgrade project
system
UPS
System copy
Old
Technical Team:
Prepare upgrade project system UPS
Update SAP GUIs (if required)
Business Team:
Study material on new release
(Development news, Service
Marketplace material, documentation
and so on)
Developers:
Review customer programs and
modifications
Milestones:
Productive
landscape
DEV
QAS
PRD
Old
Old
Old
Legend
= new release
= old release
= actual project work
= Transport route
= System copy
Project prepared (Start of Project)
Deliverables at milestone 'project prepared' (Solution Manager project milestone 'Start of Project'):
y Project plan exists describing the project organization with roles, tasks and responsibilities as
well as exact timelines, milestones and deadlines
y Project resources (internal/external) are nominated and trained
y Test focus and framework have been defined
y Upgrade project (sandbox) system is prepared for first test upgrade
© SAP AG
ADM326
10-22
Key Project Activities –
Upgrade Blueprint
Plan
Upgrade
Discovery
Build
Upgrade
Evaluation
Project
Preparation
Project work
Project Management Team:
Kick-off project
Refine project plan
Plan end-user trainings
Review solution operation concept
Blueprint
Realization
Final Preparation
for Cutover
Production
Cutover
& Support
System landscape
Upgrade project
system
UPS
New
Technical Team:
Upgrade project system UPS
Define future IT infrastructure
Prepare DEV system upgrade
Business Team:
Perform initial business processes
tests
Design business processes changes
Developers:
Start application adjustment on UPS
Milestones:
Blueprint completed (Scope to Build)
Productive
landscape
DEV
QAS
PRD
Old
Old
Old
Legend
= new release
= old release
= actual project work
= Transport route
= System copy
Deliverables at milestones 'blueprint completed' (Solution Manager project milestone 'Scope to
Build'):
y New business processes, process enhancements and replacements of custom developments with
the SAP standard are fully specified
y Adjustment requirements are specified and all performed adjustment activities (SPDD, SPAU,
custom developments, customizing, etc) are documented
y Existing core business processes run in sandbox system without errors, at least for standard
regression test scenarios
y Full documentation of upgrade procedure, issues and problem resolutions exists in central
upgrade script
y Documentation and first analysis of technical downtime performed during sandbox upgrade
© SAP AG
ADM326
10-23
Key Project Activities –
Upgrade Realization I
Plan
Upgrade
Discovery
Build
Upgrade
Evaluation
Project
Preparation
Project work
Project Management Team:
Prepare integration tests
Prepare end-user trainings
Realization
Blueprint
Final Preparation
for Cutover
Production
Cutover
& Support
System landscape
Upgrade project
system
UPS
New
Update solution operation concept
Technical Team:
Set-up temporary DEV' system for
maintenance
Upgrade DEV system
Prepare QAS system upgrade
Start optimizing technical downtime
Double
maintenance
Business Team:
Complete customizing adjustments
Productive
landscape
Temporary
maintenance
landscape
DEV'
Old
Transfer
changes
DEV
QAS
PRD
New
Old
Old
Developers:
Redo manually adjustments in DEV
Complete application adjustments
Perform unit tests in DEV
Milestones:
Solution built (Build to Test)
Legend
= new release
= old release
= actual project work
= Transport route
= System copy
Deliverables at milestones 'solution built' (Solution Manager project milestone 'Build to Test'):
y Development system is upgraded to new release
y Double Maintenance and code freeze phase for current production environment is in place.
y All changes or enhancements to business processes, customizing or custom developments are
completed and unit tested in the development system
© SAP AG
ADM326
10-24
Key Project Activities –
Upgrade Realization II
Plan
Upgrade
Discovery
Build
Upgrade
Evaluation
Project
Preparation
Project work
Project Management Team:
Prepare integration tests
Prepare end-user trainings
Realization
Blueprint
Final Preparation
for Cutover
Production
Cutover
& Support
System landscape
Upgrade project
system
UPS
New
Update solution operation concept
Technical Team:
Set-up temporary QAS' system for
maintenance
Upgrade QAS system
Transport project work to QAS system
Optimize technical downtime
Business Team:
Perform main integration and
acceptance tests in QAS
Developers:
Correct errors
Milestones:
Integration, performance and system
tests complete (Test to Deploy)
Temporary
maintenance
landscape
DEV'
Old
Transfer
changes
QAS'
Old
Transfer
Double
maintenance
Productive
landscape
changes
DEV
New
Transfer
changes
QAS
PRD
New
Old
Legend
= new release
= old release
= actual project work
= Transport route
= System copy
Deliverables at milestones 'Integration, performance and system tests complete' (Solution Manager
project milestone 'Test to Deploy'):
y Development system is upgraded to new release
y Double Maintenance and code freeze phase for current production environment is in place
y All changes or enhancements to business processes, customizing or custom developments are
completed and unit tested in the development system
© SAP AG
ADM326
10-25
Key Project Activities –
Final Preparation for Cutover
Plan
Upgrade
Discovery
Build
Upgrade
Evaluation
Project
Preparation
Project work
Project Management Team:
Create detailed cutover schedule
Technical Team:
Final Preparation
for Cutover
Production
Cutover
& Support
System landscape
Upgrade project
system
Perform final integration tests
Temporary
maintenance
landscape
Sign off solution in the new release
Project Steering Committee:
Double
maintenance
Sign off production system upgrade
Productive
landscape
Realization
UPS
New
Perform final system tests
Deploy new production infrastructure
Prepare PRD system upgrade
Business Team:
Blueprint
Milestones:
Cutover prepared
DEV'
QAS'
Old
Old
DEV
QAS
PRD
New
New
Old
Legend
= new release
= old release
= actual project work
= Transport route
= System copy
Deliverables at milestones 'Cutover prepared':
y Cutover schedule and upgrade script are compiled
y Final integration and system tests are completed without issues
y Infrastructure is ready for production system upgrade
© SAP AG
ADM326
10-26
Key Project Activities –
Final Preparation for Cutover
Plan
Upgrade
Discovery
Build
Upgrade
Evaluation
Project
Preparation
Project work
Blueprint
Realization
Final Preparation
for Cutover
Production
Cutover
& Support
System landscape
Technical Team:
Upgrade production system PRD
Perform post processing activities
Business Team:
Finally sign off business solution
Support go-live
Developers:
Support go-live
Project Management Team:
Handover solution to production
Close project
Milestones:
Start of production
Handover to production (End of Project)
Productive
landscape
DEV
QAS
PRD
New
New
New
Legend
= new release
= old release
= actual project work
= Transport route
= System copy
Deliverables at milestones 'Start of production':
y Production system is upgraded to new release and released for production operation
Deliverables at milestones 'Handover to production' (Solution Manager project milestone 'End of
Project'):
y Standard operating organization resumes responsibility for solution
y Temporary project enhancements of system landscape are removed
y Project is finally signed off and closed
© SAP AG
ADM326
10-27
Recommended Upgrade Project Landscape –
Upgrade Project System
Reasons for an upgrade project system:
Test technical upgrade procedure
Æ learn about specifics of your system
Test of customer developments in new release
Æ understand and plan custom development changes in detail
Start modification and custom development adjustment
Æ limit efforts by focusing on objects in production
Æ reduce double maintenance/code freeze period
Perform first tests of core business processes in new release
Æ understand and plan integration tests requirements
Perform first checks of new functions
Æ obtain insight in new release and plan future functional roll-outs
Obtain first test results of technical upgrade downtime
Æ understand and plan downtime optimization requirements
“
Making early upgrade experiences helps
mitigating risks
better planning project efforts
The upgrade project system is frequently also called 'upgrade sandbox system'.
SAP recommends creating the upgrade project system as copy from the production system with full
data. Otherwise all benefits listed above cannot be achieved.
© SAP AG
ADM326
10-28
Adjust Applications
Challenge: Organize application adjustment process efficiently
Adjustments of modifications, custom developments, customizing and interfaces are one of
the key cost driver of any upgrade project!
How to plan efforts and resources for adjustment process
How to identify adjustment needs in custom programs using SAP standard objects
Client 100
(company codes, plants,
storage locations, and so on)
(orders,
invoices, and
so on)
User
User
Client-Specific
Customizing
(authorizations, master,
records, and so on)
(orders,
invoices, and
so on)
Application
data
Client-Specific
Customizing
…
(company codes, plants,
storage locations, and so on)
(authorizations, master,
records, and so on)
Client 200
Application
data
Cross-Client Customizing
Repository Objects
Modifications
(such as table definitions, programs, transactions, function modules)
Technology
FI
CO
HR
PP
MM
SD
…
Grouping to form packages
© SAP AG
ADM326
Customer
Development
Customer developments
in the customer
namespace
Extension
10-29
Recommended Upgrade Project Landscape
3-system landscape
Legend
= new release
= old release
Upgrade project
system
Temporary
maintenance
landscape
UPS
New
DEV'
Old
QAS'
Transfer
changes
Old
Transfer
changes
Double
maintenance
Productive
landscape
= Transport route
= System copy
System copy
DEV
New
Transfer
changes
QAS
PRD
New
Old
The upgrade project landscape consists of the following system groups:
Productive Landscape
This is the landscape that shall be upgraded to the new release. The standard landscape is assumed to
consist of a development system (DEV), a quality assurance system (QAS) used for testing, and the
production system (PRD).
If more systems exists in the actual landscape, more upgrades might be necessary. However,
depending on the system role and creation process, some of these additional system could also be
created as copies of the three main systems above after the upgrade has been completed. For
example, a training system could be created as copy of the upgraded QAS or PRD systems.
Temporary Maintenance Landscape
This landscape is set up during the project to ensure the maintenance of the production system on the
old release until it is upgraded. The systems will be removed after the completion of upgrade project.
Upgrade Project System
This system – sometimes also called upgrade sandbox system – is created in the preparation or
upgrade blueprint phase to conduct the first upgrade tests. This system should be available
throughout the project. Even after the DEV and QAS system upgrades, it can serve as additional test
system, for example, for optimizing the technical downtime. The upgrade project system can also be
removed after the completion of the upgrade project.
© SAP AG
ADM326
10-30
Manage Parallel Changes
Challenge: Coordinating the parallel change streams
Code freeze: yes or no? - avoid possible system and testing inconsistencies versus fulfilling
ongoing business requirements
Plan efforts required for implementing and testing changes in both landscapes, particularly
with ongoing developments in production landscape
Manage emergency repairs in production landscape during code freeze period and align with
upgrade landscape
Production
support
Upgrade
project
© SAP AG
Production Landscape
DEV'
QAS'
PRD
Old
Old
Old
Upgrade Project Landscape
DEV
QAS
New
New
ADM326
10-31
Recommended Upgrade Project Landscape –
Special Cases
2-system landscape
Upgrade project
system
Temporary
maintenance
landscape
UPS
System copy
New
DEV'
Legend
= new release
= old release
= Transport route
= System copy
Old
Double
maintenance
Transfer
changes
DEV
Productive
landscape
Recommended upgrade
project landscape for
two system maintenance
landscapes
Transfer
PRD
changes
New
Old
3-system landscape
Upgrade project
system
Temporary
maintenance
landscape
UPS
New
DEV'
Transfer
Old
changes
QAS'
Old
Transfer
Double
maintenance
changes
DEV
Productive
landscape
Recommended upgrade
project landscape for
three system maintenance
landscapes including a temporary
development system for new projects
after the upgrade
System copy
QAS
PRD
New
Old
Transfer
New
changes
Transfer changes
Temporary
development
landscape
DET
New
For certain SAP products (SAP BW, SAP NetWeaver PI) or systems with a small business scope,
two system maintenance landscapes might be used. In these cases, development and quality
assurance are done on one system (here: DEV). Nevertheless, an upgrade projects system should be
installed as well.
In case, you do a pure technical upgrade first, but nevertheless plan a functional upgrade or roll-out
soon after the upgrade, you could set up an additional temporary development system on the new
release. This step avoids conflicts with the project or code freeze and saves time for the preparation
of the roll-out. The temporary development system should be created as copy from the upgraded
development system after completion of the initial application adjustments. During the project the
temporary development system receives change transports and corrections from the project
development system.
© SAP AG
ADM326
10-32
Change Management During the Upgrade
Project
Source Release Landscape
Corrections
TR
DEV'
TR
ABAP
QAS'
TR
PRD
ABAP
ABAP
Transport
Buffer
Transport
Buffer
Export
Export
TR
TR
Manually re-apply
Target Release Landscape
TR
DEV
TR
QAS
ABAP
ABAP
Transport
Buffer
Transport
Buffer
Export
Export
TR
TR
Import
after
Upgrade
TR
Transport Requests
In the standard three-system landscape, each system is updated in the standard transport sequence.
Tasks such as Customizing, applying patches, and custom developments are performed in the
development system and transported to the quality assurance and production systems.
During the upgrade of the development and test systems no development roll-outs or other changes
in the production landscape should be done ('code freeze'). Otherwise SPDD and SPAU transports
have to adjusted as well leading to higher efforts ('double maintenance').
Emergency situations may arise during the upgrade project requiring a change to be made to the
production system. If such situations arise, handle them on an individual basis and always use SAP
Change Management tools to make any corrections.
Note: All changes to the production environment should be manually reproduce in the upgraded
development system. Customizing transports between different releases are not supported, repository
transports are critical (e.g. SAP note 1090842).
Consequences of inconsistent transport management during upgrade projects:
y SPDD and SPAU transports created during the upgrade of development system may be not valid
for test and production system.
y Results of the upgrade of one system in the landscape can not be used as reference for upgrade
of another system.
y Identification of modifications and creation of test cases can take much longer without
appropriate documentation.
© SAP AG
ADM326
10-33
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
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 system
© SAP AG
Always 3-system-landscape for maintenance
(only emergency corrections allowed)
Plan and communicate code freeze time!
ADM326
10-34
Adjustments in an Upgrade Project
Blueprint
Custom Objects
Modification
Definition: any development in the
customer namespace
Definition: any change to an SAP-owned
workbench object
Custom reports & transactions
Types of modifications
Generate programs (SGEN) post-upgrade to
identify syntax errors (or use UCCHECK)
Modifications made due to SAP notes
Customer modifications
Who “owns” the modification?
What is the business justification for retaining
the modification?
Enhancements
E.g.: user exits - these are generally not issues
in upgrades (Unicode – SAP note 553110)
What objects must be adjusted?
Objects that have been modified by customer
AND changed by SAP
What must be decided?
Keep new SAP-standard or modify again
Customizing
Study release notes; generate Upgrade IMG
(SPRO_ADMIN)
Key issue: degree of reliance on SAP
standard objects
Pure custom development should require
little/no work
Custom ABAP Dictionary objects
Generally require little re-work – any errors
are identified immediately during activation
of new repository
“Cloned” objects
SAP-standard objects copied into the
customer namespace
Cloned objects present unique challenges –
possible approach: re-clone them on the
new release.
367676 4.6 to 6.10
452229 6.10 to 6.20
689951 6.20 to 6.40
857904 6.40 to 7.0
e.g. ABAP and Unicode, ABAP objects, Internal tables, Open SQL, ABAP Compiler, ABAP
runtime
Integration (R/3 Plug-In): http://service.sap.com/R3-Plug-In
Queries Please read SAP note: 672784
Batch Input Please read SAP note: 311440
Authorizations: SAP_NEW profile contains authorizations for new checks in functions .
After the upgrade:
y To copy the latest SAP default values while retaining your own modifications, call transaction
SU25 (steps 2 and 3)
y Delete all the individual profiles from SAP_NEW that refer to releases that are lower than the
source release for the upgrade.
y Go through the profile SAP_NEW and decide for each authorization object, into which
customer profile the authorizations need to be copied.
© SAP AG
ADM326
10-35
Ensure Business Continuity
Final prep.
for cutover
Make sure that no big surprises occur after upgrade weekend
Define business requirements and KPIs for a successful go-live
Define suitable test scope: Find right balance between level of risk mitigation and testing effort
Set-up efficient test procedures and test KPIs
Identify appropriate training scope and efficient training methods
Testing
effort
???
High avail-
Testing all
Testing only
Unsufficient
ability
processes in
core business
test
use
processes
No testing
management
e.g. sampling
Æ Good
effort-risk
e.g.
balance
iterative
testing
Evaluate Rethink your
test automation test management
Risk
© SAP AG
ADM326
10-36
Test Stages –
Overview
Final prep.
for cutover
Phase
e.g. SAP Support
Packages
Regression tests
Operation
User acceptance tests
Production
preparation
tests
Technical system tests
Integration tests
Functional
tests
Scenario tests
Realization
Functional tests
Developer tests
Realization
Source: Testing SAP Solutions, ISBN 978-1-59229-127-4
Tremendous resource effort, thousands of person-hours
y Reducing testing costs while enhancing current testing processes and coverage
y A scalable approach that can extend into multiple business groups / lines and applications
y Lack of resources and/or loss of productivity due to using business users and/or analyst
throughout all testing cycles
Managing quality throughout the life cycle that includes new implementations, upgrades and
maintenance through the development and use of a reusable regression suite
y Little or no test automation
y Testing not enough and/or too late to reduce the cost of fixing defects
y Lack of SAP accelerators to reduce automation test development cycle time
y No component approach to test design to lower maintenance effort and Total Cost of Ownership
(TCO)
Planning for adequate testing procedures and infrastructure to insure application quality and
performance
Supporting global deployments that support multiple languages and localization
© SAP AG
ADM326
10-37
Test Strategies
ti o
no
f te
stin
g
Ev
olu
Business
Process Test
Script
Accelerated Testing
Solution for SAP
Automated record
and replay
]
]
]
eCATT unit testing plus
manual integrated testing
Manual testing
Hope for the best
Automated Testing:
y Human intervention only for triggering the test process, BUT not running it
y Dramatically reduced test period; time available for “value added/random manual tests
y Immediate detection of errors
y Clear test case results (OK or not OK)
y Greater degree of reliability; repeatability
y Detailed test logs; troubleshooting
Manual Testing
y Potentially greater flexibility in design, creation & execution of test cases. Manual testers can
use expert knowledge to fill in gaps about test requirements
y Identification of “real” issues; is functionality not working or temporary condition due to
network connectivity issues?
y Testers can perform random tests that meaningfully extend the scope of the test plan
© SAP AG
ADM326
10-38
Impact Analyzer
Via Transaction SFW5
Using the Impact Analyzer, you can analyze which user interfaces are affected for which
roles and users if you activate a business function
This enables you to answer the following questions at a very early stage, that is, before
you activate a business function:
Which training material is affected?
To what extent does the training material have to be adjusted?
Which users have to be informed and may need delta training courses?
To use the impact analyzer, start transaction SFW5, select a business function, and
choose Impact Analyzer Planned BFs
© SAP 2009 /
It evaluates the following user interfaces:
y Transactions
y Portal i-Views and portal roles
y Reports/programs of the ABAP-based system
y ABAP WebDynpro applications
© SAP AG
ADM326
10-39
Where to Find Test Case Templates
Two Options
Before Installing an EHP
After Installing an EHP
All test cases are available as
documents in
the enhancement package information
center
(http://service.sap.com/erp-ehp)
Documents (texts) can be downloaded
Test cases are shipped with the
enhancement package and are part
of the installation (SAP ECC)
Access the test case from the
switch transaction (SFW5)
From there, you will (by drilldown)
enter the test workbench
Test cases can be transported to SAP
Solution Manager via workbench request
You can either access the Test Case Templates via the Service Marketplace or transaction SFW5
after the installation.
© SAP AG
ADM326
10-40
Unit 10: Overview Diagram
Unit 10 – Upgrade Planning and Preparation
Lesson 1: Upgrade as a Project
Lesson 2: Upgrade of a Three System Landscape
Lesson 3: Upgrade Dependency Analyzer
Lesson 4: Technical Aspects
Lesson 5: Upgrade Experiences
Lesson 6: Further Information
© SAP 2010
© SAP AG
ADM326
10-41
Big Bang versus Phased Upgrades
Question
What
is the best roll-out approach for a series of upgrades?
Examples:
Different ERP systems are part of a common transport landscape, e.g. in a global
template landscape, and need to be upgraded together.
Several SAP products of a common solution shall be upgraded, e.g. because of
business process dependencies.
Options
1.Big Bang: All systems are upgraded in parallel in one common project and go-live at the
same date.
ECC
Big Bang
Upgrade ECC + SCM
SCM
2.One project, phased go-live: All systems are upgraded in parallel in one common project,
but go-lives are distributed over several dates (e.g. subsequent weekends)
Phased Go-Live
Upgrade ECC + SCM
ECC
SCM
3.Phased projects: Projects are scheduled and executed independently with go-lives at
different dates.
Phased Projects
Upgrade ECC
ECC
Upgrade SCM
© SAP AG
ADM326
SCM
10-42
Evaluation of Big Bang versus Phased Upgrade
Option 1
Big Bang
Option 2
One project, phased go-live
Option 3
Two separate projects
Risks
– Issues of one project can impact the
+ Go-lives do not depend on each
+ Projects do not depend on each
Costs&
Efforts
+ one test phase
+ one project Æ less overhead
– more hardware resources required
other
– problem analysis can be harder
other
+ One test phase
+ one project Æ less overhead
– Min. test of intermediate state
Criteria
for project
– more external project resources
+ Less hardware resources
requirement for project
+ projects better handled with internal
resources
required
– More hardware resources required
– Two test phases
for project
– more external project resources
Benefits
+ Earlier realization of process
Business
Impact
+ one business downtime
+ one code freeze period
+ key business users needed only one
+ Earlier realization of process
enhancements in new releases
time
– problem resolution may need longer
– higher work load on key users
other
– Later realization of process
enhancements in new releases
+ Root cause of problems can be
+
+
–
–
better separated
one code freeze period
key business users needed only one
time
Two Business Downtimes
higher work load on key users
enhancement in new releases
+ Root cause of problems can be
+
–
–
–
better separated
less work load for key users
Two Business Downtimes
two code freeze periods
key business users needed two
times for projects
Note: The pros and cons arguments above represent general considerations that are valid for most
situations in which a roll-out approach has to be defined. Nevertheless, they shall be regarded as
model only. Content, importance and judgment of the pro and con arguments will definitely differ in
a specific customer situation.
© SAP AG
ADM326
10-43
Upgrade in Complex Landscapes:
Upgrade Dependency Analyzer
Self
Services
Self
Services
SEM
SEM
SRM
Upgrade ECC
R/3
CRM
ECC
9
Learning
Solution
SRM
CRM
?
Learning
Solution
...
...
Identify release dependencies
Which Upgradeable Units to
upgrade at the same time
Potential release dependencies
between Upgradeable Units
Prerequisites and assumptions:
y Upgrade Dependency Analyzer always compares two systems, one system that is being
upgraded vs. one other system in the system landscape
y The result of a dependency analysis is a predefined dependency statement and optionally an
SAP note
y Dependency statements refer to separately installed systems/upgradeable units
y Only functionality/processes are considered that are currently used, e.g. an analysis result of 'no
upgrade dependencies' means, that functionality/processes that worked before the upgrade, will
still work properly after the upgrade
y No information about new functionality/processes, because they often require the upgrade of
both components
y Only information about standard SAP functionality/processes, not about custom developments
or self-defined customer processes
y Restricted to the ‘top 80%' of upgradeable units, no individual software components considered
y All software components that are part of one system will be upgraded at the same time. Upgrade
Dependency Analyzer delivers no information about possible combinations of software
component versions within one system.
© SAP AG
ADM326
10-44
Upgrade Dependency Analyzer
Customer View (1)
Planning
an Upgrade?
Find
out dependencies
within your SAP
system landscape!
Example:
http://service.sap.com/uda
© SAP AG
ADM326
10-45
Upgrade Dependency Analyzer
Customer View (2)
Planning
an Upgrade?
Find
out dependencies
within your SAP
system landscape!
Example:
Upgrade
one system
to SAP ECC 6.05
© SAP AG
ADM326
10-46
Upgrade Dependency Analyzer
Customer View (3)
Planning
an Upgrade?
Find
out dependencies
within your SAP
system landscape!
Example:
Upgrade
one system
to SAP ECC 6.05
Searching
for
dependencies to
second system SAP
SCM 7.0
© SAP AG
ADM326
10-47
Upgrade Dependency Analyzer
Customer View (4)
Planning
an Upgrade?
Find
out dependencies
within your SAP
system landscape!
Example:
Upgrade
one system
to SAP ECC 6.05
Searching
for
dependencies to
second system SAP
SCM 7.0
Result:
9Accessible via SAP Service Marketplace
9Also integrated in SAP Solution Manager
no known
upgrade
dependencies!
Possible Results of a Dependency Analysis:
y No known upgrade dependencies, independent upgrade possible: When upgrading to the target
component, all standard cross-system functions that worked prior to the upgrade will be
retained. New cross-system functions may require an upgrade of the existing component you
have specified.
y Independent upgrade possible, but with known restrictions: When upgrading to the target
component, all standard cross-system functions that worked prior to the upgrade will be
retained. If there are restrictions, you will find them in the attached SAP Note.
y Independent upgrade not possible: After the upgrade to the target component, some or all
standard cross-system functions will no longer work. It is required to also upgrade the existing
component you have specified, or you may have to manually implement those cross-system
functions in a different way.
y Loss of cross-system functions: After the upgrade to the target component, some or all standard
cross-system functions will no longer work. You need to manually re-implement those crosssystem functions in a different way. It is not possible or sufficient to upgrade the existing
component.
y No interaction: The two components you have specified have no standard cross-system
functions in common. No direct interaction exists. You can upgrade the components
independently.
y No interaction in existing release combination: The releases specified are indicating an existing
release combination with no standard cross-system functions in common. No direct interaction
exists before the upgrade. You can upgrade the components independently.
© SAP AG
ADM326
10-48
Upgrade Dependency Analyzer
Description
Check the existence of upgrade dependencies
between two separately installed SAP systems
in your system landscape
Landscape analysis capabilities (planned for
next SAP Solution Manager release)
Access
SAP Service Marketplace at:
http://service.sap.com/uda
Planned: SAP Solution Manager ‘Implement./
Upgrade: Upgrade Analysis’ work center
Benefits
Simplification of upgrade planning
Fast and easy access to needed dependency
information for all SAP solutions
Reduction of risks, costs and effort
Reuse of customer specific system landscape
definition (planned for next release)
© SAP AG
ADM326
10-49
Focus of Upgrade Dependency Analyzer vs.
Scenario & Process Component List
Upgrade Dependency Analyzer
Scenario & Process Component List
High level technical planning
Detailed analysis on process level
Shows known dependencies on technical
level according to categories:
Shows predefined scenarios/processes before
and after an upgrade according to categories:
Dependency exists
Conditional dependency exists
Already available
Additionally available after upgrade
Currently no dependencies
Answers the question:
Will a given combination of two systems still
work (still be supported by SAP) after the
upgrade of one of these systems?
© SAP AG
Not available after upgrade
Answers the question:
Which scenarios/processes will continue to work
(or will not work any more) after the upgrade of a
component in a defined system landscape?
ADM326
10-50
Unit 10: Overview Diagram
Unit 10 – Upgrade Planning and Preparation
Lesson 1: Upgrade as a Project
Lesson 2: Upgrade of a Three System Landscape
Lesson 3: Upgrade Dependency Analyzer
Lesson 4: Technical Aspects
Lesson 5: Upgrade Experiences
Lesson 6: Further Information
© SAP 2010
© SAP AG
ADM326
10-51
Technology Aspects
Hardware requirement on new release: server, front end, network
Sizing forecast and system configuration for new release
Planning of OS, DB and SAP system upgrades
Testing and validating of backup strategy for upgrade
and on the new release
Performing technical upgrade on the whole system landscape
Post-upgrade activities including performance monitoring
Since the requirements of the new release are changing, we need a sizing forecast which in turn
requires changes to the configuration. Finally the whole environment is concerned, for example the
server hardware, the client hardware, the network, the operating system and the database. Especially
when changing the operating system, other software on this computer has to be tested. For example
the backup software has to be tested.
Because of the new requirements, performance monitoring gets more important after the upgrade.
© SAP AG
ADM326
10-52
SAPup / SAPJup
DESCRIPTION
Standard SAP upgrade tool for ABAP and Java
Execution of main upgrade activities
For an ABAP system you require SAPup; for a
Java system you require SAPjup.
The tools share a similar architecture Æ consist
of an upgrade program (SAPUp or SAPJup) and
a control program (Upgrade GUI or SDT GUI).
ACCESS
SAPup and SAPJup are part of the upgrade
software kit shipped by SAP
More Information is available on SDN:
http://sdn.sap.com/irj/sdn/upgradetech
BENEFITS
New upgrade GUI layout and simplified upgrade
procedure for ABAP (SAP NW 7.01), Java (SAP
NW 7.1) and dual stack (SAP NW 7.1) upgrades
Established system switch upgrade technology
is also available for Java (SAP NW 7.1) and dual
stack (SAP NW 7.1) upgrades
Synchronized upgrade procedure for dual stack
SAP NW 7.0 upgrades
© SAP AG
ADM326
10-53
Bind parts of SAP Enhancement Package 5 for
SAP ERP 6.0 to the SAP ECC 6.0 Upgrade
With the upgrade to SAP ECC 6.0 SR3 it is possible for the first time to
bind the relevant parts of an SAP Enhancement Package for SAP ERP 6.0 to the
upgrade. This includes also the necessary SAP Support Packages.
The SAP Enhancement Package 5 for SAP ERP 6.0 can be bound to the upgrade by providing a text
and XML file to the Upgrade. This text and XML files contain the stack configuration, calculated
and created by the Maintenance Optimizer.
© SAP AG
ADM326
10-54
SAP Support Packages (1)
Begin of availability
Bind SAP Support Packages of the
destination release to the upgrade!
End of maintenance
SAP Support Package
SAP ECC 6.05
SAP_APPL 605
2
SAP ECC 6.0
SAP_APPL 600
20
SAP R/3 4.6C
SAP_APPL 46C
60
t
SAP Support Packages on the start release are produced also after a potential destination release has
been shipped.
SAP R/3 4.6C SAP_APPL Support Package 60 for example has been shipped after the shipment of
SAP ECC 6.0.
On each potential destination release, Support Packages are available, too.
There is some relation between the Support Packages: usually fixes have been mad at the same time
for different releases.
An upgrade from SAP R/3 4.6C SAP_APPL Support Package 60 to SAP ECC 6.0 SAP_APPL
Support Package 0 would partially downgrade the system.
But: it is possible to bind Support Packages to the upgrade: you can go directly to ECC 6.0
SAP_APPL Support Package 20 or higher (in this example).
Advantages:
y No need to supply the SAP Support Package on the destination release after the upgrade
y No (temporary) downgrade
© SAP AG
ADM326
10-55
Handling of Add-ons / Software Components
Depending on the situation in the old and the new release, during an
upgrade the following is possible:
Additional software component is been newly installed
as standard component
Existing Add-on becomes part of standard delivery
Existing Add-on becomes part of other
standard components
Existing Add-on is upgraded
Existing Add-on is kept as it is
Existing Add-on is been deleted
Add-on is been newly installed
Depending on the situation in the old and the new release, during an upgrade the following is
possible:
y Additional software component is been newly installed as standard component: for example the
software components from the Extension Set
y Existing Add-on becomes part of standard delivery: for example in SAP R/3 4.6C IS-U is an
Add-on, in SAP ECC 6.0 it is in standard delivery
y Existing Add-on becomes part of other standard components: for example the Plug-in (PI) is an
Add-on in SAP R/3 4.6C, but part of standard components in SAP ECC 6.0
y Existing Add-on is upgraded: for example from a release fitting the old SAP R/3 4.6C to a
release fitting the new SAP ECC 6.0
y Existing Add-on is kept as it is: for example because it fits just as well the old SAP R/3 4.6C as
the new SAP ECC 6.0 (option 'keep')
y Existing Add-on is been deleted: because it is not needed any longer (active and passive
deletion)
y Add-on is been newly installed: it is possible to install a new Add-on during the upgrade
© SAP AG
ADM326
10-56
Upgrade Downtime
up
up
SAPup:
PREPARE
&
repository
import
SAPup:
conversion,
XPRAS, etc.
transports &
manual tasks
Business
validation
tests
down
go/no-go decision
backup?
ICNV
backup?
Near Zero Downtime Upgrade
(reduced) uptime
PRD
R/3 4.6C
Upgrade and Unicode Conversion
Delta replay
clone
Recording
downtime
PRD
ECC 6.05
Validation,
sign-off
cloned
PRD
© SAP AG
ADM326
10-57
Application-Specific (ASU) Toolbox
DESCRIPTION
Before/after a technical upgrade often additional
application-specific steps need to be performed
Æ ASU collects and summarizes these activities
Enables you to recognize the necessary steps
and perform them in a controlled manner
ACCESS
ASU toolbox is integrated with the upgrade GUI
through the ASU phase in the upgrade process
BENEFITS
One tool for all kinds of predefined tasks
(reducing the upgrade time)
Making the upgrade more transparent (avoid
mistakes)
Avoiding problems after the upgrade
(message reduction)
© SAP AG
ADM326
10-58
Check Technical Prerequisites
OS/DB Dependencies
OS/DB Upgrades
Check impact and dependencies early!!!
Perform your OS/DB upgrade in advance of the SAP
upgrade
Key Take Aways
Check the Product Availability Matrix (PAM) to determine if any upgrade are required to the
OS/DB via Service Marketplace quick link: /pam
Oracle customers: SAP NetWeaver 7.0 (and thus ECC 6.0) only run on Oracle 10
For new installations 64bit OS-/DB releases are mandatory since SAP NetWeaver 7.0
For upgrades to SAP NetWeaver 7.0 64bit OS-/DB releases are recommended
© SAP AG
ADM326
10-59
Check Technical Prerequisites
SAP GUI Options
SAP GUI
For existing functionality SAP GUI
is still the default UI
SAP Enterprise Portal is not required unless portal-specific
applications are used (e.g. Employee Self-Service)
Key Take Aways
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 planning
of SAPGUI rollout
SAP GUI for Java still offered for Macintosh, Linux, etc.
SAP GUI for HTML still supported via ICM (Integrated ITS)
Check the Product Availability Matrix (PAM) for technical prerequisites about your SAP GUI
via Service Marketplace quick link: /pam
© SAP AG
ADM326
10-60
SAP Business Connector
SAP note 309834 – SAP BC support and
release strategy
SAP BC and SAP XI/PI are based on
different technologies
Supported SAP BC releases 4.6 and 4.7
Supported JDK versions 1.3 and 1.2 (with
limitations) only
SAP BC 4.6 and 4.7 based on webMethods‘
Integration Server 4.6
SAP XI/PI based on open standards (e. g.
BPEL4WS for business processes)
Supported operating systems
•
Windows NT and 2000
•
Linux
•
Sun Solaris 8 and higher (32-bit only)
Only parts of an SAP BC
implementation can be migrated to an
SAP XI/PI implementation
•
IBM AIX 4.3 and higher (32-bit only)
•
HP-UX 11.0 and higher (32-bit only)
Any custom programming done on the
basis of SAP BC will likely not be
reusable in the SAP XI/PI context
OSS Support (SAP note 571530)
The end-of-maintenance dates for the two BC
versions are defined as follows:
- BC 4.6: December 31, 2008.
- BC 4.7: December 31, 2009.
Customers that want to keep a BC running that is
not out of maintenance should read the
announcement of BC 4.8 in SAP note 1094412.
© SAP AG
XSLT mappings (offered since SAP BC 4.6)
Example: SAP BC flow language
Customers still starting new projects
with SAP BC should consider XSLT for
mappings
Æ SAP BC to SAP XI/PI Migration Guide
ADM326
10-61
Internet Transaction Server (ITS)
ITS 6.20 is long term supported for SAP products based
on SAP Netweaver 2004 (6.40) 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
Because SAP ICM (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 Matrix
(PAM) to get up to date information (http://service.sap.com/pam)
© SAP AG
ADM326
10-62
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.
The functional scope of ESS will be ensured by SAP.
SAP recommends using ESS based on Web Dynpro (Java).
For the implemented ESS scenarios several SAP components have to
work together (Business Package, XSS, Portal, backend).
The combination and dependencies of them is dependent on the
implemented scenarios and could be different in the individual releases.
© SAP AG
ADM326
10-63
Get Support from SAP!
Planning
Execution
QUA,
QUE (TUP),
UVA
64 %
Define & assign
project resources
Define Business Case
Modification
adjustments
38 %
17 %
Impact on the
62 %
Downtime
minimization
IT-infrastructure/
sizing
Knowledge
system landscape
Platform
and Upgrade Search & find upgrade
related information
Dependency
Analyzer
Interoperability
75 %
Efficient testing
43 %
31 %
Enduser trainings
21 %
Projectmanagement
21 %
Others
21 %
39 %
25 %
17 %
SAP Upgrade Factory, Upgrade Coaching,
Safeguarding for Upgrades
Estimate the
costs and efforts
UpgradeServices:
Source: DSAG-360°-Customer Feedback Program: Upgrade (March 2008 – 138 participants – 138 companies)
More information available at http://service.sap.com/upgradeservices
© SAP AG
ADM326
10-64
Unit 10: Overview Diagram
Unit 10 – Upgrade Planning and Preparation
Lesson 1: Upgrade as a Project
Lesson 2: Upgrade of a Three System Landscape
Lesson 3: Upgrade Dependency Analyzer
Lesson 4: Technical Aspects
Lesson 5: Upgrade Experiences
Lesson 6: Further Information
© SAP 2010
© SAP AG
ADM326
10-65
Customers’ Perceived Challenges –
Worldwide Results Survey
Plan
Build
71%
Estimate cost & effort
Assess impact on
existing solution
55%
49%
Downtime minimization
48%
Modification adjustment
49%
46%
Project management
47%
44%
End user training
41%
41%
Define business case
Define and allocate
project team/resources
Downtime
minimization strategy
69%
Efficient testing
Find information on
upgrade methods & tools
29%
IT infrastructure/sizing
Interoperability/
Dependencies
28%
Cost/Effort Estimation
19%
Justify budget
17%
Compliance
considerations
15%
Others 4%
N = 1,362
Others 5%
N = 1,362
Participants: North America (Jan 2008), Brazil (March 2008), Germany (March 2008), Japan (March 2008),
Australia (April 2008), Sweden (April 2008), China (May 2008) and India (May 2008), UK & Ireland (March 2008).
© SAP AG
ADM326
10-66
Average Durations of ERP Upgrade Projects
Target Release
Start Release
ERP 6.0
< R/3 4.6C
R/3 4.6C
R/3 4.7
ECC 5.0
Upgrade only
6±3
5±3
4±2
4±2
Combined Upgrade &
Unicode Conversion
- MDMP
n/a
7±2
4±3
n/a
Combined Upgrade &
Unicode Conversion
- Single CP
n/a
5±2
4±2
n/a
duration in months; results derived from SAP Upgrade Experience database 11/2008
© SAP AG
ADM326
10-67
Additional Hardware Requirements
for an Upgrade to ECC 6.0 non-UNICODE
Absolute additional hardware consumption for an
upgrade from a source Release to SAP ECC 6.0
The notes contain only DELTA sizing information
from a source release to the next release.
100,0%
80,0%
60,0%
40,0%
20,0%
0,0%
Start-Release:
SAP Note:
4.0B
4.5B
4.6B
4.6C
4.7/1.10
4.7/2.00
5.0
113795
178616
323263
517085
752532
778774
901070
Memory Application Server
CPU Application Server
This chart above shows absolute additional hardware consumption for an upgrade from different
source releases to SAP ECC 6.0
This chart is only valid for a pure technical upgrade.
y Absolute additional hardware requirements are shown in the figure.
y The SAP notes mentioned contain only delta information between one release and another, for
example, SAP Note 901070 contains delta hardware requirements between SAP ECC 5.0 and
SAP ECC 6.0.
To check sizing plausibility and proactively optimize configuration use:
y Continuous Quality Check for Upgrade (service is part of Enterprise Support)
- Analysis session
Load-based analysis
Parameterization of future landscape
- Verification session provides corrective measures for avoiding potential bottlenecks
© SAP AG
ADM326
10-68
Additional Hardware Requirements for
Unicode
Based on parallel benchmarking of Unicode and non-Unicode test systems. The CPU and RAM
figures are measured average numbers and will be different for different transactions
CPU
RAM
+30%
Depending on
existing scenario
(MDMP, double byte)
Database size
UTF-8*
UTF-16 : + 20 to 60%
1. Priority
+50%
Application servers
are based on UTF-16
internally
Network Load
: up to +10%
ORACLE, DB/2 (AIX)
SQL Server, DB/2 (AS400),
MAX DB (7.0)
UTF-8
Almost no change
due to efficient
compression
*35% is the observed maximum in growth for small systems (db size < 200 GB).
* 10% is the observed maximum for bigger systems (db size > 200 GB).
All of the values are average values. Also refer to SAP note 1139642. Based on the real scenario that
is used in the system to be upgraded those values may be very different from the ones displayed here.
For example, measurements in customer system using UTF-8 based databases showed that more than
90% of the databases actually have shrunk about 10%. The main reason for this decrease is that with
the Unicode conversion also an implicit database re-organization is performed freeing unused space.
Particularly, with large databases such re-organizations are carried out seldom because it impacts the
availability and performance of the system.
© SAP AG
ADM326
10-69
Average Cost Structure of ERP Upgrade
Projects
2-5%
0-5%
Software license
10-20%
0-10%
0-20%
Hardware / infrastructure
SAP technical upgrade
Custom code and
modification adjustment
Testing
Project management
15-25%
25-60%
Change management /
training
10-30%
Support
© SAP AG
ADM326
10-70
How to Keep Upgrade Costs Down
Reduce Upgrade Costs by
IT
Infrastructure
Set-up
Reduce DB size
and growth
Optimize system
configuration
Optimize
operation
Outsource
temporary
hardware
requirements
Business
Downtime
Analyze
downtime drivers
Choose
downtime
optimization
tools and
procedures that
meet best your
requirements
Define
emergency
procedures
during cut-over
Custom Code
Testing
Eliminate unused
Assess efficiency
custom code
Assess if you
can return to
standard with
new release or
enhancement
package
Avoid
modifications
and encapsulate
custom
developments
of test
organization
Define standard
regression test
cases
Use test
administration
and automation
tools
Focus on critical
Training
Identify training
requirements
early
Improve learning
material creation
and effectiveness
Use state-of-the-
art learning
material
distribution and
training methods
areas
Implement technical risk management / quality assurance
© SAP AG
ADM326
10-71
Comparison of Upgrade Experiences in
Business Suite and NetWeaver
Topic
Adjustment
Requirements
Reference:
ECC
CRM
SCM
SRM
NW BW
NW PI
NW EP
500-1500 mods
2500-10000
cust obj
Technical
Downtime
3-10h
3-10h
5-12h*
2-6h
2-8h
1-6h
1-6h
Project
Duration
4-6 mths
4-5 mths
3-4 mths
3-4mths
2-3 mths
1-3 mths
1-3 mths
Product
Specific
Challenges
Upgrade:
Industry
Solutions
Transition:
Mobile
Scenarios
Compatibility:
Add-ons
Conversion:
MDMP
Infrastructure:
Java
Deployment
Release
Dependend
Topics
Legend: effort/duration is
Downtime:
LiveCache
Compatibility:
LC Build,
com routines,
SPs
Business
downtime:
Ramp down/
ramp up of
interfaces
Business
downtime:
Higher
requirements
>
BW 7.0:
Web Reporting
deployment
> CRM 2007: UI
Migration
> CRM 2005:
VMC deployment
lower than
comparable to
higher than ECC reference
SAP Business Suite and SAP NetWeaver products are compared with average SAP ECC Upgrade
project.
The average SAP ECC upgrade project is defined based on figures from SAP Upgrade Experience
Database from Nov 2008 (~290 entries) for upgrades to SAP ECC 6.0.
Comments:
* SCM downtime: 2-6h SCM Server + 3-6h Live Cache export/import
© SAP AG
ADM326
10-72
Strong Customer Demand for Upgrade
Experiences Gathered in Upgrade Projects
A frequent request from SAP customers to SAP:
'We would like to see benchmarking data from other
completed customer upgrade projects'
SAP Upgrade Experience Database
provides orientation on
Project duration
Business downtime
Satisfaction with the upgrade
Etc.
The anonymous results are available in SAP Service Marketplace.
Note: The SAP Upgrade Experience Database currently provides only information on ERP upgrades.
© SAP AG
ADM326
10-73
Questionnaire Used for the SAP Upgrade
Experience Database
Only upgrades of production systems are measured
A standardized questionnaire (online) is used for data collection (available in English and
German versions)
The questionnaire is tailored to tracking upgrade experiences
Many questions can be answered by simple mouse clicks
At present, the database holds data for upgrades to SAP ECC 6.0 and for upgrades to SAP
ECC 5.0
y
© SAP AG
ADM326
10-74
Feedback from Customers who have
Completed the Upgrade
95 % of our
customers
who upgraded
to ECC 6.0
were satisfied
or even gave
a better rating
Very satisified
More than satisfied
Satisfied
Less satisified
Not satisfied
Based on 212 upgrades
© SAP AG
Proven approach and
tools
Excellent documentation
Very few highly critical
problems
Qualified support
ADM326
10-75
Upgrades to SAP ECC 6.0: Number of Datasets
in Database by Source Release
SAP R/3 <4.6C
SAP ECC 5.0
30
The following slides provide the results
for the source releases
SAP R/3 Enterprise and
32
Total: 333
upgrades
103
SAP R/3
Enterprise
SAP R/3 4.6C.
168
SAP R/3 4.6C
Results for the other source releases will be provided as the number of datasets in the SAP Upgrade
Experience Database increases.
© SAP AG
ADM326
10-76
Upgrades to SAP ECC 6.0: Approach in
Upgrades by Source Release
SAP R/3 Enterprise
Approach in upgrade project
Technical upgrade + subs.
functional enhancements
20%
Total: 103
upgrades
64%
Technical
upgrade only
4%
Functional upgrade
12%
Strategic upgrade
SAP R/3 4.6C
Approach in upgrade project
Technical upgrade + subs.
functional enhancements
14%
Functional upgrade 2%
Strategic upgrade
Total: 167
upgrades
79%
Technical
upgrade only
5%
Annotation:
y Technical upgrade + subs. functional enhancements = technical upgrade with subsequent
implementation of additional functional or strategic enhancements
y Functional upgrade = technical upgrade with additional functional enhancements
y Strategic upgrade = technical upgrade with strategic enhancements
Findings:
y Most upgrade projects to SAP ECC 6.0 were performed using the upgrade approach “Technical
upgrade only.”
y On the other hand, the diagrams on the next page indicate that the new functionality 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.
© SAP AG
ADM326
10-77
Upgrades to SAP ECC 6.0: Reasons for
Upgrades by Source Release
SAP R/3 Enterprise
Reasons for upgrade
Functional requirements
Improve usability of existing solution
End of mainstream or extended maintenance
Legal compliance
Leverage latest technology
Business Innovation
System landscape consolidation / Integration of
industry solutions
Replacement / elimination of modifications and / or
customer specific development by SAP standard
0%
25%
50%
75%
100%
based on 103 upgrades
Reasons for upgrade
SAP R/3 4.6C
Functional requirements
Improve usability of existing solution
End of mainstream or extended maintenance
Legal compliance
Leverage latest technology
Business Innovation
System landscape consolidation / Integration of
industry solutions
Replacement / elimination of modifications and / or
customer specific development by SAP standard
0%
25%
50%
75%
100%
based on 168 upgrades
How to read the charts:
y More than one reason per upgrade could be selected. The results for each reason category are
standardized to the number of upgrades of the given sample.
© SAP AG
ADM326
10-78
Upgrades to SAP ECC 6.0: Upgrade Strategy
by Source Release (System Switch Upgrade)
SAP R/3 Enterprise
Upgrade strategy
Resource
minimized
19%
Total: 102
upgrades
81%
Downtime
minimized
SAP R/3 4.6C
Upgrade strategy
© SAP AG
Resource
minimized
23%
Total: 166
upgrades
ADM326
77%
Downtime
minimized
10-79
Upgrades to SAP ECC 6.0: Overall Satisfaction
with Upgrade Approach by Source Release
SAP R/3 Enterprise
Overall satisfaction with upgrade
Less than satisfied
6%
Satisfied
15%
33%
Very satisfied
Total: 102
upgrades
46%
More than satisfied
Overall satisfaction with upgrade
SAP R/3 4.6C
Less than satisfied 1%Not satisfied at all
4%
Satisfied
18%
Very satisfied
36%
Total: 165
upgrades
41%
More than satisfied
Annotation:
y The following satisfaction levels could be selected:
y ++ Very satisfied
y +
More than satisfied
y O
Satisfied
y -
Less than satisfied
y --
Not satisfied at all
© SAP AG
ADM326
10-80
Upgrades to SAP ECC 6.0: Customers’
Perceived Challenges by Source Release
SAP R/3 Enterprise
Customers' perceived challenges
Planning phase
Cost / effort estimation
Justify budget for project / value proposition
Building Phase
Project Management
IT infrastructure / sizing
Modification adjustment
Efficient testing
Minimize downtime
End-user training
0%
25%
50%
75%
100%
based on 88 upgrades
Customers' perceived challenges
Planning phase
SAP R/3 4.6C
Cost / effort estimation
Justify budget for project / value proposition
Building Phase
Project Management
IT infrastructure / sizing
Modification adjustment
Efficient testing
Minimize downtime
End-user training
0%
25%
50%
75%
100%
based on 144 upgrades
How to read the charts:
y More than one category per upgrade could be selected.
© SAP AG
ADM326
10-81
SAP R/3 Enterprise
Upgrades to SAP ECC 6.0: Project Duration in
Weeks by Source Release
Project duration in weeks
Distribution of values
Range of values
Median: 18,0
(w/o outlier values)
Min: 8,1
0
4
8
Max: 31,9
12
16
20
24
28
Weeks
32
36
40
44
48
52
based on 102 upgrades
SAP R/3 4.6C
Project duration in weeks
Distribution of v alues
(w/o outlier values)
Min: 12,0
0
Range of values
Median: 21,0
4
8
12
16
Max: 36,6
20
24
28
Weeks
32
36
40
44
48
52
based on 168 upgrades
Question asked:
y “Please specify the duration of your upgrade project up to the initial go-live (in weeks).”
How to read the charts:
y Distribution of values: shows the frequency distribution of all measured values (in weeks,
without cutting at the edges).
y Range of values: by cutting 10% of the number of values at each end of the frequency
distribution outlier values are excluded. The length of each bar indicates the variance of the
measured values.
© SAP AG
ADM326
10-82
Upgrades to SAP ECC 6.0: Duration of Project
Phases in Weeks by Source Release
SAP R/3 Enterprise
Duration of single project phases in weeks
Project duration (total)
18,0
Project preparation phase 2,0
2,0
Upgrade blueprint phase
Upgrade realization phase
6,0
Final preparation for cutover phase
3,0
Production cutover & support phase
2,0
0
5
10
15
20
25
Weeks
Duration of single project phases in weeks
SAP R/3 4.6C
Project duration (total)
21
Project preparation phase
3,0
3,0
Upgrade blueprint phase
Upgrade realization phase
8,0
Final preparation for cutover phase
3,0
Production cutover & support phase
2,0
0
5
10
15
20
25
Weeks
Question asked:
y “Duration of project phases according to the SAP Upgrade Roadmap (in weeks).”
How to read the charts:
y For each project phase, the median value of all answers is shown. In a project, overlaps or gaps
between the project phases are possible.
© SAP AG
ADM326
10-83
SAP R/3 Enterprise
Business Downtime* in Hours by Source
Release, without Unicode Conversion
Business downtime* in hours
Distribution of values
Range of values
Median: 34,0
Max: 65,0
Min: 15,0
0
12
24
36
48
60
72
84
Hours
96
108
based on 91 upgrades
Business downtime* in hours
SAP R/3 4.6C
Distribution of values
Range of values
Median: 48,0
Min: 22,9
0
12
24
Max: 86,2
36
48
60
Hours
72
84
96
108
based on 140 upgrades
* 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.
Question asked:
y “Assuming a 24x7 hours operation of the production system, how many hours was the
production system unavailable for the end users?”
How to read the charts:
y Distribution of values: shows the frequency distribution of all measured values (in hours,
without cutting at the edges).
y Range of values: by cutting 10% of the number of values at each end of the frequency
distribution outlier values are excluded. The length of each bar indicates the variance of the
measured values.
y Only upgrades that followed the “Downtime minimized“ upgrade strategy were taken into
account. No Unicode conversion was performed.
Findings:
y The business downtime was <= 48 hours (2 days)
y SAP R/3 Enterprise: for 74% of all measured upgrade projects (for 88% <= 60 hours)
y SAP R/3 4.6C:
© SAP AG
for 53% of all measured upgrade projects (for 65% <= 60 hours)
ADM326
10-84
SAP R/3 Enterprise
Upgrades to SAP ECC 6.0: Modules* (Business
Scope) Used in the Upgraded ECC System
Modules* used in ERP component
100%
75%
50%
25%
0%
CO
FI
HR
LE
MM
PM
PP
PS
QM
SD
based on 102 upgrades
SAP R/3 4.6C
Modules* used in ERP component
100%
75%
50%
25%
0%
CO
FI
HR
LE
MM
PM
PP
PS
QM
SD
based on 167 upgrades
* Despite the fact that SAP R/3 modules are no longer applicable in SAP ECC
6.0, customers were asked to describe the business functionality of the
upgraded SAP software in terms of the classic SAP R/3 modules (e.g., “FI”) in
order to provide a comparison with the business scope of the upgraded SAP
software.
How to read the charts:
y More than one SAP R/3 module could be selected:
y the results for each module are standardized to the number of upgrades of the given sample.
Conclusion / findings:
y A broad coverage of components, and therefore a wide scope of business functionality, can be
observed in the upgraded systems.
© SAP AG
ADM326
10-85
SAP R/3 Enterprise
Upgrades to SAP ECC 6.0: Database Size in GB
by Source Release
Database size in GB
Distribution of values
Range of values
Median: 375
Min: 122
0
(w/o outlier values)
Max: 1870
1000
2000
3000
4000
GB
5000
6000
based on 102 upgrades
SAP R/3 4.6C
Database size in GB
Distribution of values
Range of values
Median: 340
(w/o outlier values)
Min: 78
0
Max: 1340
1000
2000
3000
GB
4000
5000
6000
based on 163 upgrades
Questions asked:
y “What was the used database size in your productive environment (in GB)?
How to read the charts:
y Distribution of values: shows the frequency distribution of all measured values (in GB, without
cutting at the edges).
y Range of values: by cutting 10% of the number of values at each end of the frequency
distribution outlier values are excluded. The length of each bar indicates the variance of the
measured values.
Findings:
y SAP R/3 Enterprise: 80% of the upgrades Æ DB size <1000 GB
56% of the upgrades Æ DB size < 500 GB
y SAP R/3 4.6C:
86% of the upgrades Æ DB size <1000 GB
62% of the upgrades Æ DB size < 500 GB
© SAP AG
ADM326
10-86
Upgrades to SAP ECC 6.0: Number of Projects
by Number of Users and Source Release
SAP R/3 Enterprise
Number of users
=10000
5000 - 9999 1% 1 - 99
2000 - 4999
5% 5%
100 - 249
9%
1000 - 1999
15%
Total: 99
upgrades
17%
31%
17%
250 - 499
500 - 999
Number of users
5000 - 9999
SAP R/3 4.6C
9%
1000 - 1999
=10000
3%1%
2000 - 4999
1- 99
15%
16%
Total: 166
upgrades
20%
500 - 999
18%
100 - 249
19%
250 - 499
© SAP AG
ADM326
10-87
Lessons Learned:
Project Management
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
• Test of core business processes
PM
Reduce dual maintenance period
Do add. effort work in upgrade project system before upgrade of system landscape
Reduce time window between upgrade of DEV and PRD system
•
•
Test output programs
Most companies focus on the business process testing and forget about print
programs and forms
•
Involvement and commitment
Early Involvement of key users and management commitment are key success
factors
•
Plan and communicate code freeze time!
© SAP AG
ADM326
10-88
Lessons Learned:
Functional Aspects
Good housekeeping drives efficiency of upgrade
• Archiving, Cleansing of un-used custom code and SAP modifications
• Document table changes thoroughly and their usage in custom programs
The older release the more money spent on training
• Significant for customers starting with SAP R/3 4.5B and below (Enjoy
transactions, tree structures…)
• Utilize computer based training: Easy to distribute and review at the
convenience of the user
Industry Add-on
• Customers with Industry Add-ons should review the specific upgrade guides
Tackle custom developments as early as possible
• The faster the development team can have access the faster business process
issues can get resolved
Modification adjustments and testing are key cost drivers
• The better the documentation and existing test procedures, the easier and less
time consuming those project tasks will be)
© SAP AG
ADM326
10-89
Lessons Learned:
Technical Aspects
Upgrade Strategy
• „Downtime minimized“ method should be used
• In order to get a realistic forecast about the expected downtime, a Sandbox
upgrade with representative configuration and data set is highly recommended
Distribution of new SAP GUI version should be started early
Check impact and dependencies early
• With the help of the Product Availability Matrix and PCL e.g. On OS/DB compliance,
availability of country versions and 3rd party products, ITS and dependencies to
other SAP products
Perform test upgrades over and over until you get it right
• A key for success mentioned by many customers
Verify sizing - leverage SAP GoingLive Functional Upgrade Check
• Consider the additional hardware requirements
Install and use SAP Solution Manager
© SAP AG
ADM326
10-90
Unit 10: Overview Diagram
Unit 10 – Upgrade Planning and Preparation
Lesson 1: Upgrade as a Project
Lesson 2: Upgrade of a Three System Landscape
Lesson 3: Upgrade Dependency Analyzer
Lesson 4: Technical Aspects
Lesson 5: Upgrade Experiences
Lesson 6: Further Information
© SAP 2010
© SAP AG
ADM326
10-91
Documentation
New with SAP NetWeaver 7.0 :
Master Guides reflect new concept:
General
information provided (mapping to
new building blocks – systems with usage
types, standalone engines, clients) and
planning information (landscape-related
topics– SAP NetWeaver Administrator,
SAP Solution Manager, SLD, SLM, …)
One section for every IT scenario providing
information of its system landscape and
implementation/upgrade sequence
Description:
Documentation provides information required to
understand and perform software life-cycle tasks
•
Planning Guides ([Upgrade] Master Guide, …)
•
Installation Guides
•
Upgrade Guides
•
SAP Support Package Stack Guide
•
SAP Library documentation
•
Tool documentation (F1 help, …)
For the installation of a system with
usage types, only one Installation Guide
– SAP NetWeaver required
Comprises
the information for your
platform/database and all usage types
No
longer separate guides required for BI,
EP, etc.
OS
Dependencies included/no longer
required due to Prerequisite Checker
Profiling prepared: in the future, it is planned that more specific guides can be created on demand
that only contain information for required usage types and operating systems
© SAP AG
ADM326
10-92
Information Sources
ERP Upgrade
specific
information
SAP Upgrade Info Center
(www.service.sap.com/upgrade)
SAP Upgrade
Newsletter
Statistics
or
screen shot
SAP ERP
Solution Browser
Enhancement
Package info
center
© SAP AG
ADM326
10-93
Information at SAP Service Marketplace
Upgrade
Homepage: http://service.sap.com/upgrade
Upgrade services: http://service.sap.com/upgradeservices
Upgrade Dependency Analyser: http://service.sap.com/uda
SAP ERP
Homepage: http://service.sap.com/erp
Development News: http://service.sap.com/developmentnews
Release Notes: http://service.sap.com/releasenotes
Release Strategy: http://service.sap.com/releasestrategy
Maintenance Strategy: http://service.sap.com/maintenance
Scenario & Process Component List: http://service.sap.com/scl
SAP Enhancement Packages
SAP ERP enhancement package Installation: http://service.sap.com/ehp-inst
SAP ERP enhancement package Homepage: http://service.sap.com/erp-ehp
EHP Installation Guides for existing products
SAP NetWeaver:
© SAP AG
Homepage: http://www.sdn.sap.com/irj/sdn/netweaver
SAP NetWeaver Administrator: SDN Netweaver Administration
System Landscape Directory: https://www.sdn.sap.com/irj/sdn/nw-sld
Software Lifecycle Manager: https://www.sdn.sap.com/irj/sdn/softwarelogistics
ADM326
10-94
SAP Upgrade Newsletter – Register NOW!
For continuous upgrade news right
to your desk, subscribe to the SAP
Upgrade Newsletter: SAP Upgrade
Newsletter
Regional and local SAP upgrade news is proactively distributed on a
quarterly basis to customers
No. of recipients today: more than 10,000
Available language/country versions:
English
German
Japanese
Russia
Upgrade News - Content:
© SAP AG
Focus topic
Solution-specific information, for example, mySAP ERP
SAP upgrade tools, services and content
…
ADM326
10-95
© SAP AG
ADM326
10-96
Agenda: Enhancement Packages
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
11-1
Enhancement Packages
Contents:
The idea of the enhancement packages
Binding enhancement packages to the upgrade
© SAP 2010
© SAP AG
ADM326
11-2
Bind SAP ERP Enhancement Package 5 for
SAP ERP 6.0 to the ECC 6.0 Upgrade
Since the upgrade to ECC 6.0 SR3 it is possible for the first time to bind the
relevant parts of an enhancement package to the upgrade. This includes also the
necessary SAP Support Packages.
© SAP AG
ADM326
11-3
Agenda: SAP Enhancement
Package Concept & Strategy
1.
2.
3.
4.
SAP Enhancement Package Concept & Strategy
Architecture and Technology
Implementation Procedure
Customer Experiences and Summary
© SAP 2010
© SAP AG
ADM326
11-4
How is this Possible?
1. Always install parts of SAP enhancement packages combined
with Support Pack Stack as a maintenance activity with minor additional
effort and facilitated by the new EHP Installer tool (SAPehpi).
EHP
SAP
System
Support
Package
Support
Package
Inactive Business
Functions
EHP
Support
Package
Support
Package
Time
active
active
Business Function Activation
2. Select and activate the functionality needed by your
business using the Switch Framework. Functionality your
business does not need will remain dormant.
© SAP 2010
© SAP AG
ADM326
11-5
At-a-Glance
SAP Enhancement Package 5 for SAP ERP 6.0
SALES
Improvements for configurable sales UI
SHARED SERVICE CENTER
ENTERPRISE ASSET MANAGEMENT
New shared service framework (SSF) as a platform
for multifunctional shared service organizations
Enhancements in financials, HCM, travel
management, and supplier relationship
management to integrate processes with the SSF
New role: simplified and improved maintenance
planning and execution processes
New functionality for modeling of linear assets
More granular cost collection
Improvements in rotable management
SAP Real Estate Management application:
Enhanced processes in commercial real estate
management
PROCUREMENT AND
LOGISTICS EXECUTION
Procurement:
Integration with SAP Supplier Relationship
Management service procurement functionality
Further procure-to-pay improvements
New stock type for inventory management
SAP Auto-ID infrastructure offering
Improvements for outsourced manufacturing
scenarios
New FMEA (failure mode and effects analysis)
features
Integration with SAP EHS Management
SUSTAINABILITY:
EH&S COMPLIANCE MANAGEMENT
Enhanced reporting and master data maintenance
Legal compliance for product safety and
occupational health
Enhanced incident management (delivered as
add-on for SAP ERP EHP 5 in September 2010)
Talent management:
Enhanced UI and functionalities of
compensation management and talent
management
Improved insights into learning activities
Workforce process management:
Automated performance assessment process
UI flexibility and organization management
analytics
Extended integration of e-recruiting and HR
core system in the hiring process
Enhancements for organization chart
visualization
Next-generation employee self-services
Additional HCM – localizations
Improvements in SAP Travel Management
application
FINANCIALS
PRODUCTION PLANNING AND
EXECUTION
QUALITY MANAGEMENT
HUMAN CAPITAL MANAGEMENT
Work-in-process batch tracking and valuation
Engineering and manufacturing product structure
synchronization
Production order integration with ME applications
Power lists for process orders
Manufacturing analytics:
Overall equipment efficiency (OEE) analytics
via Xcelsius software
Manufacturing analytics via Xcelsius
Shift report and shift note enhancements
Extensions in Lean Manufacturing (Kanban)
XSteps and PI sheet enhancements
SAP Treasury and Risk Management application:
Streamlined hedge management process
Enhancements in in-house cash
SAP Master Data Governance application
for financials:
Managing and distributing organizational units
(profit center, cost center)
Enhancements in SAP Financial Supply Chain
Management set of applications
New features in financial accounting and new
general ledger – reorganization of profit center
Improved formats of financial reports
Localizations for India, Japan, Chile, and Russia
Enhancements in SAP Strategic Enterprise
Management business consolidation functionality
for legal compliance
Highlights
© SAP AG
ADM326
11-6
Productive SAP Enhancement Package
Customers (June 2010)
7,915 EHP
customers
May ’09 Jun ’09 Jul ’09 Aug ’09 Sep ’09 Oct’09
Nov’09 Dec’09 Jan’10 Feb’10
Mar’10
Apr’10 May ’10 Jun ’10
General availability of
SAP Enhancement
Package 4
for SAP ERP 6.0
© SAP AG
ADM326
11-7
SAP Enhancement Packages & SAP ERP 6.0
2006
2008
2010
2012+
What Are Enhancement Packages?
Optionally installed and activated software
innovations for SAP ERP 6.0
Software innovations include UI
simplifications, functional enhancements and
Enterprise services
SAP enhancement packages are built on top
of each other
Enhancement packages are not SAP Support
Packages: SAP Support Packages contain
corrections and legal changes
Enhancement Packages
SAP ERP 6.0
SAP NetWeaver
SAP Business Suite - Stable Core
Quick Facts About SAP ERP 6.0
Preamble: SAP enhancement packages are shipped as a delta shipment to SAP ERP 6.0
1. Selective Installation: Each enhancement package contains new versions of existing software
components. You only update software components, which are related to the functionality you want to use.
After installation: No UI or process change until a Business Function is activated (ABAP). One common
regression test for both, SAP Support Packages and SAP enhancement package
2. Selective Activation: New functionality must be explicitly switched on to become active in the system
(EHP5: ~600 Business Functions).
If activated: Changes are predictable, only well described changes in the activated areas.
Testing is simplified with templates, provided for every Business Function
SAP enhancement packages for SAP ERP include functional enhancements, industry-specific
enhancements and simplifications. To discover and evaluate which innovations are shipped in which
SAP enhancement package, visit the SAP Service Marketplace.
In addition, enterprise service (ES) bundles are delivered with SAP enhancement packages. Each ES
bundle comprises a set of enterprise services to support an end-to-end business process (for example
Order to Cash) across the SAP Business Suite. To learn which ES bundles are available and to
understand the details of the services, please refer to the Enterprise Service Wiki Pages in SDN.
From a functional perspective SAP enhancement packages are built on top of each other: By
installing the current SAP enhancement package the entire content of earlier packages is
incorporated.
SAP enhancement packages have the same maintenance duration as the underlying core application,
SAP ERP 6.0. As before, all legal changes and corrections will be available via SAP Support
Packages. SAP provides SAP Support Packages for SAP ERP 6.0 on a regular basis during the
defined maintenance period and, in parallel, in the equivalent SAP Support Packages for SAP
enhancement packages for SAP ERP. Since Business Suite 7i2010 SAP deliver SAP enhancement
packages for other SAP applications (e.g. SAP CRM or SAP SCM) as well.
The first three generations of SAP enhancement packages for SAP ERP 6.0 have been delivered and
adopted in the market. This is proven by high number of live customers.
© SAP AG
ADM326
11-8
New 7-2 Maintenance Strategy
7-2 maintenance strategy for SAP Business Suite 7 core applications*:
7 years of mainstream maintenance, 2 years of extended maintenance
Long-term planning security and higher return on investment – nine year maintenance horizon
Additional time to deploy and benefit from innovation delivered via enhancement packages
Less additional cost for extended maintenance
New
7
EHP**
SAP CRM,
SCM, SRM 7.0
RampUp
EHP**
EHP**
RampUp
EHP**
EHP**
Mainstream Maintenance
EHP**
EHP**
EHP**
2006
2007
2008
Extended Maint.
(+ 2%)*
Cust.-Spec.
Maintenance
Extended Maint.
(+ 2%)*
Cust.-Spec.
Maintenance
EHP**
Dec
Mainstream Maintenance
Nov
SAP ERP 6.0,
SAP NW 7.0
EHP**
2
Dec
2009
2010
2011
2012
2013
2014
2015
2016
2017
Before
2006
EHP**
EHP**
Ext. Maint.
(+ 2%)*
Mainstream Maintenance
2007
2008
2009
2010
2011
2012
Ext. Maintenance
(+ 4%)*
2013
2014
Cust.-Spec.
Maintenance
Mar
EHP**
Mar
RampUp
Mar
EHP**
SAP ERP 6.0,
SAP NW 7.0
2015
2016
2017
* Core applications of SAP Business Suite 7: SAP CRM 7.0, SAP SRM 7.0, SAP SCM 7.0, SAP PLM 7.0; plus SAP ERP 6.0 (EHP4) and SAP NetWeaver 7.0. Industry-specific add-on
applications and SAP enhancement packages based on these core application releases will offer mainstream and extended maintenance in line with these releases.
** SAP Enhancement Packages: Illustrative only; does not reflect exact shipment times and frequency.
Beginning with Business Suite 7 core applications, the mainstream maintenance phase is 7 years.
The extended maintenance phase is 2 years, for an additional fee.
© SAP AG
ADM326
11-9
Agenda: Architecture and
Technology
1.
2.
3.
4.
SAP Enhancement Package Concept & Strategy
Architecture and Technology
Implementation Procedure
Customer Experiences and Summary
© SAP 2010
© SAP AG
ADM326
11-10
Example: SAP Enhancement Package 5
Focus: Installation
1. Installation of EHP components
with regular maintenance
Architecture
..
EHP 5
EHP 4
Switch Framework
Industry
Enterprise
Extensions
Extensions
SAP ECC
Core (6.00)
EA-HR
(605)
SAP_HR
(605)
SAP NetWeaver
Application Server 7.0
Facts
Technical Usage:
“Human Capital Management”
1
1
EA-APPL
(600)
IS-OIL
(600)
SAP_APPL (600)
SAP_ABA (702)
SAP_BASIS (702)
Selective, component-wise installation: With SAP enhancement packages
you can selectively update software components. Matching combinations
of software components, as well as PI/Portal/BW-content and Java
software components are grouped by Technical Usages.
As the number of software components are limited, e.g. a separated
installation of logistics and financials (both are located in the core
software component SAP_APPL/EA-APPL) is not possible.
Strict separation of technical installation and the implementation of the
new functionality: Explicit activation separately for each Business
Function (with SAP Enhancement Package 5 for SAP ERP 6.0: ~600
Business Functions).
However only backend functionality (ABAP) is switchable.
Step 1:
A selective exchange of one component is possible: With SAP enhancement packages you can
selectively update software components. Please note that matching combinations of software
components, as well as PI/Portal/BW-content and Java software components are grouped by
Technical Usages. As the number of software components are limited, e.g. a separate
installation of logistics and financials (both are located in the core software component
SAP_APPL/EA-APPL) is not possible.
Step 2:
Strict separation of technical installation and the implementation of the new functionality:
Explicit activation separately for each Business Function (with EHP3 we have approximately
150 Business Functions). However only backend functionality (ABAP) can be switched.
© SAP AG
ADM326
11-11
SAP Enhancement Package Installation Tool:
SAP Enhancement Package Installer
Quick facts
SAPehpi: Standard tool to implement SAP enhancement packages
Technology: System Switch Procedure
Available for:
All 32-bit and 64-bit platform for ABAP, Java and Dual-Stack
SAP Business Suite 7 and SAP Business Suite 7 Innovations 2010*
SAP Enhancement Package 1 and 2 for SAP NetWeaver 7.0
SAP Enhancement Package 1 for SAP Process Integration 7.1
SAP Support Packages for ABAP – only systems
New Features
•
•
© SAP 2010
© SAP AG
Manageability and usability
•
Observer mode
•
Alerting functionality
•
GUI reconnect
Stability & Robustness
•
Check consistency of stack.xml
•
Redesign of the add-on handling
* SAP Enhancement Package 4 and 5 for SAP ERP 6.0; SAP Enhancement Package 1 for SAP CRM, SAP SRM, SAP SCM 7.0
ADM326
11-12
Example: SAP Enhancement Package 5
Focus: Activation
..
EHP 5
EHP 4
Switch Framework
Industry
Enterprise
Extensions
Extensions
SAP ECC
Core (6.00)
1
2
1
Business Function:
“Employee Interaction Center”
2
EA-HR
(605)
SAP_HR
(605)
SAP NetWeaver
Application Server 7.0
Facts
2. Activation of
Business Functions
1. Installation of EHP Components
with regular maintenance
Architecture
EA-APPL
(600)
IS-OIL
(600)
SAP_APPL (600)
EA-HR
(605)
EA-APPL
(600)
SAP_HR
(605)
IS-OIL
(600)
SAP_APPL (600)
SAP_ABA (702)
SAP_ABA (702)
SAP_BASIS (702)
SAP_BASIS (702)
Selective, component-wise installation: With SAP enhancement
packages you can selectively update software components. Matching
combinations of software components, as well as PI/Portal/BWcontent and Java software components are grouped by Technical
Usages.
As the number of software components are limited, e.g. a separated
installation of logistics and financials (both are located in the core
software component SAP_APPL/EA-APPL) is not possible.
Strict separation of technical installation and the implementation of
the new functionality: Explicit activation separately for each Business
Function (with SAP Enhancement Package 5 for SAP ERP 6.0: ~600
Business Functions).
However only backend functionality (ABAP) is switchable.
Step 1:
A selective exchange of one component is possible: With SAP enhancement packages you can
selectively update software components. Please note that matching combinations of software
components, as well as PI/Portal/BW-content and Java software components are grouped by
Technical Usages. As the number of software components are limited, e.g. a separate
installation of logistics and financials (both are located in the core software component
SAP_APPL/EA-APPL) is not possible.
Step 2:
Strict separation of technical installation and the implementation of the new functionality:
Explicit activation separately for each Business Function (with EHP3 we have approximately
150 Business Functions). However only backend functionality (ABAP) can be switched.
© SAP AG
ADM326
11-13
Switch Framework Enables Optional
Activation of Business Functions
With the Switch Framework it is possible to control the
activation of SAP ERP objects.
Switch Framework
Activating a Business Function triggers switches.
The switch controls whether the switch-controlled code is
executed or not at runtime.
SAP ECC
The Switch Framework is a proven concept (already used
to retrofit Industry Solutions in ERP 6.0).
Fundament: Enhancement Framework is the solution of SAP NetWeaver 7.0 to
allow adaptations of development objects without touching them.
All enhancements offered by Enhancement Framework
can be switched by the Switch Framework.
All reports, includes, classes, function modules, and Web Dynpro ABAP UIs can
be changed and enhanced using the Enhancement Framework.
The new BAdI is also integrated in the Enhancement Framework.
Every change is hidden behind a switch
About 50 Business Functions delivered with enhancement package 2 that can be activated separately.
In the background happens a lot, activation of code an DDIC objects.
Switch and Enhancement Framework is not totally new and already used for IS retrofit since ECC
6.0.
© SAP AG
ADM326
11-14
Switch Framework - How Does It Work?
Business View:
Business Function
Architectural
View:
techn. Switch
Repository View:
“Enhancement
Framework”
Business Function Set
Business Function Set
Enhancements
Bus Fct F1
Industry Business Function
BusBus
FctFct
F2 F1Set “Media“
Switch 1
BusBus
FctFct
Advertising
F4 F2
Mgmt.
Bus Fct
F4
Press Distribution
Switch 2
…
Enterprise Business
Function
HCM, Administration
Switch 3
Switch 4
Switch 5
Real Estate
…
Element 2
IMG-nodes
Enhancements
Screen
Element 1
Switch n
Switch BC Set
A s witch controls the vis ibility of other repos itory
objects .
The Switch Framework Enables Optional Activation Of Business Functions:
With the Switch Framework, it is possible to control the activation of SAP ERP objects.
Activating a business function triggers switches, which then “influence” the execution of the
code enhancements. These switches ensure that you only see the new functions if you have
activated them. All functional changes and the impact of an activated business function are
made transparent in advance by the documentation. Bear in mind that once a business function
is activated you cannot reverse it. Please note: The activation process starts a job in your SAP
system which automatically performs all changes in the system.
The Switch Framework is a proven concept as it was already used to retrofit Industry Solutions
in ERP 6.0.
© SAP AG
ADM326
11-15
Things You Should Know Before
Installing SAP Enhancement Packages
EHP Facts
Only one EHP Level per
system
One application system can
only consist of one EHP level
(e.g. EHP4 or EHP5). Hence
installed EHP components have
to be updated with every future
EHP implementation.
Technical Delivery
EHPs are “cumulative”
When installing the latest EHP
you will automatically get all
functionality delivered with
previous SAP enhancement
packages.
Technically the EHP installation
delivers only changed objects to
your system (delta Shipment):
- In case you have already
installed EHP4 you will only
install the new objects of EHP 5.
- In case you have installed
EHP 3 you will install EHP 4
and EHP 5 objects in one step
Industry Solutions
Customers who have activated
an industry business function
set have to include the
corresponding EHP industry
software component during
installation.
EHP Installation and
functional activation is
partially non-reversible
© SAP AG
Enhancement Package 2
for SAP NetWeaver 7.0
available
ADM326
Project Perspective
Modification Adjustment
After installing SAP
enhancement packages
modifications must be adjusted
– even if no business function
has been activated.
Regression Test required
The installation of an SAP
enhancement package requires
a full regression test – even if no
business function has been
activated.
Effort Estimation
Most customers say that the
installation effort is a bit higher
with EHP’s (without activating
business functions) compared to
pure SAP Support Package
updates.
11-16
Agenda: Implementation
Procedure
1.
2.
3.
4.
SAP Enhancement Package Concept & Strategy
Architecture and Technology
Implementation Procedure
Customer Experiences and Summary
© SAP 2010
© SAP AG
ADM326
11-17
Implementation Scenarios
Different Use Cases
1
New Installation
2
Upgrade of an
Existing System
3
Enhancement
Package
Installation
© SAP 2010
© SAP AG
ADM326
11-18
Implementation Scenarios
Different Use Cases
1 New Installation
NW
7.0
NW
EHP2
* SAP ERP 6.0 EHP5 Ready Installation
NW
7.1
NW
EHP1
ERP
EHP4
SAPInst
SAPehpi
ERP
6.0
NW
EHP1
ERP
EHP5
SAPehpi
ERP*
EHP5
ERP
6.0
NW
EHP2
ERP
EHP5
ERP
6.0
SAPehpi
NW
EHP2
© SAP AG
ERP
6.0
ADM326
ERP
6.0
NW
EHP2
11-19
Implementation Scenarios
Different Use Cases
Upgrade of an Existing System
2
NW
7.0
NW
EHP2
NW
2004
SAPup/ SAPJup
NW
7.1
NW
EHP1
ERP
EHP4
ERP
6.0
R/3
4.6C
NW
EHP1
SAPup/ SAPJup
ERP
EHP5
ERP
6.0
NW
EHP2
© SAP AG
ADM326
11-20
Implementation Scenarios
Different Use Cases
Enhancement Package Installation
3
NW
7.0
NW
7.1
SAPehpi
SAPehpi
NW
7.0
NW
EHP2
NW
7.1
NW
EHP1
ERP
EHP4
ERP
6.0
SAPehpi
ERP
6.0
NW
EHP1
ERP
EHP5
ERP
6.0
© SAP AG
SAPehpi
ADM326
ERP
6.0
NW
EHP2
11-21
Phase 1:
Select Required Business Functions
Requirements
Design
Build & Test
Business
Deploy
Identification: Enhancement Package Info Center
Single point of access to all information related to EHP’s:
•
Presentations, documentation and release notes
•
Test catalogue and learning maps
Documentation at deep level of granularity
Great ability to analyze new software functionality
Easily identify needed Business Function(s)
Further Services and Tools
Accelerated Innovation Enablement (AIE)
- Five days of SAP enablement helping to evaluate
the innovation capabilities of the latest SAP EHP
Solution Browser and Business Function Prediction
http://service.sap.com/erp-ehp
AIE
Experts
Result:
High-level business
requirements
and selection of
Business Functions
First of all the business expert has to select the required business functions.
The Enhancement Package Information Center is the single point of access to all information related
to a business function for the business expert.
Here you can find presentations, documentation, release notes, test catalogues and learning maps.
The Business Function Documentation allows the user to get to know the capabilities behind a
business function and how to use them; learn about options the business function provides; and notes
which software components are needed. Please note that each Business Function has a technical
name. This identifier is important to determine which parts of the system needs to be updated.
© SAP AG
ADM326
11-22
SAP Enhancement Packages for SAP ERP 6.0
Business Function Prediction
F re
serv e
offe ice
ring
Wondering which
enhancement package
functionality is potentially
relevant for you?
SAP now offers a solution:
Prediction of relevant enhancement
package functionality based on
your existing system usage
Including direct access to:
Overview presentation
Release Notes
Documentation
Test case catalogs
Mapping to Technical Usage
Register for a free Business Function Prediction today!
http://service.sap.com/BFP
© SAP 2010
A new version of SAP Enhancement Package Must Know Guide available
© SAP AG
ADM326
11-23
How To Use The Enhancement Package
Information Center
Requirements
Design
Build & Test
Business
Deploy
The Concept
Purpose of the SAP ERP
enhancement package strategy
Concept and methodology of
enhancement packages
What you need to know before
How to implement them
What to test at what point in time
Functional Overview
Which enhancements are included
in each enhancement package?
Which areas of the solution were
touched by new developments?
Level 1 =>
‘Short overview presentation’:
Level 2 =>
‘Detailed overview presentation’:
Level 3 =>
‘Detailed presentation’:
Get an idea of each business function
(short description and target group)
Understand each business function with
features included, benefits, target users
and their and technical name.
(~ 1 slide per business function)
Understand each feature of
a business function
(~ 1 slide per feature)
© SAP 2010
© SAP AG
ADM326
Level 4 =>
‘Online information’:
Assess each business function,
using all related information.
This is presented in a table-like
list with links to documentation,
test cases, release notes, detail
presentations, etc.
11-24
Business Function Documentation
Business
The SAP enhancement
package information center
contains documentation for
each enhancement package
business function
Technical Usages and
Business Packages that are
required to use the business
function
Additional business
functions that must be
activated as well
Prerequisites that must be
satisfied before the
activation
Features that become
available when the business
function is activated
© SAP AG
First, select the appropriate link from section (1), then search for
the required business function and click on link (2).
ADM326
11-25
How to Evaluate a Business Function in Your
System Landscape
Requirements
Design
Build & Test
Deploy
Legend
System landscape
= ERP + EHP5
= old release (6.0)
EHP 5
= actual project work
SBX
ECC
Enhancement package
evaluation system
Productive landscape
DEV
ECC
= Transport route
System
copy
QAS
ECC
PRD
ECC
For evaluation („Does the Business Function add value?“) you should not use the DEV system
Recommendation: Use a sandbox system (SBX)
Keep in mind: Activation of a business function can in most cases not be revoked (exception: some
newly available reversible business functions)
You can only transport the complete BF system switch settings across the system landscape
© SAP AG
ADM326
11-26
Phase 2:
Design
Requirements
System
Administrator
Design
Build & Test
Deploy
Prepare Technical Installation
Check Prerequisites
What are the prerequisites to check before installing?
Choose Installation Approach
Selective or Broad
Map Business Functions and Technical Usage
Which are ‘Technical Usages’ are relevant?
Define Business Aspects
Create business blueprint for Innovation
Execute implementation project with ASAP
methodology
© SAP AG
Business
ADM326
Result:
Business blueprint
and technical
preparation
activities
11-27
Prerequisites For SAP ERP 6.0 – SAP
Enhancement Package 5 Installation
Requirements
Design
Build & Test
System
Administrator
Deploy
1. Up-to-date SAP Solution Manager
SAP Enhancement package 1 for SAP Solution Manager 7.0 (SP 23 is mandatory)
2. Latest installation or upgrade tools
For systems on ECC 6.0 use Enhancement Package Installer (SAPehpi)
For systems from SAP R/3 4.6C to SAP ECC 5.0 use upgrade tools (SAPup) & bind in SAP
Enhancement Package 5 for SAP ERP 6.0 parts
3. Compatibility of Add-ons
Ask your add-on provider whether your add-ons are compatible with the SAP Enhancement
Package for SAP ERP 6.0
4. SAP Support Packages
In general there is no minimal Support Pack level required in the source system where the SAP
enhancement package will be installed – refer to the guides and relevant notes for more details.
First you have to bring your SAP Solution Manager up-to-date.
In order to use the Maintenance Optimizer application, you need SAP Solution Manager 4.0 with the
highest SAP Support Package level in your system landscape. Your system landscape has to be
maintained in the Solution Manager system. You can find more information about the SAP Solution
Manager at help.sap.com > SAP Solutions > SAP Solution Manager.
Please make also sure that you have installed the latest SPAM/SAINT update in your system.
Secondly, as you need a certain SAP Support Package level in your system let the Solution Manager
Maintenance Optimizer calculate the needed (and equivalent) SAP Support Packages for you. They
can be included in the installation queue - the details are explained in the next step.
Thirdly please note that if you have an add-on installed in your system, ask your add-on provider
whether it is compatible with the SAP Enhancement Package for SAP ERP 6.0. See SAP note
1117309 for details of add-ons delivered by SAP.
Fourthly read the documentation and the referenced notes to check that all other prerequisites are
met.
© SAP AG
ADM326
11-28
Mapping Process (Example)
Business Function
Technical Usage
A “Business Function”
is the activatable unit
within the SAP ECC
Server
A “Technical Usage”
groups software
components which must
be installed together.
ABAP Product
Instance: Media
Real Estate Management
Technical Name:
RE_GEN_CI_1
New General Ledger
Accounting
Technical Name:
FIN_GL_CI_1
Business Function 3
Lean Manufacturing
Technical Name:
LOG_PP_LMAN
...
© SAP AG
Mapping via OSS Note 1324838
Business Function 2
SAP ECC Server
Media
Business Function 1
Main Instances &
Software Components
Central
Applications
ABAP Product Instance:
Central Application
Financials
ABAP Product Instance:
Leasing/Contract A/R & A/P
BF EA-APPL 605
BF
BF SAP_APPL 605
Central Application
EA-HR 605
SAP_HR 605
ERECRUIT 600
EA_GLTRADE 600
…….
HCM Self Services
ABAP Product Instance:
Human Capital Management
JAVA Product Instance:
SAP XSS (Self Services)
ADM326
SAP NetWeaver 702
11-29
Installation Procedure At A Glance
Broad Installation
Selective Installation
1. Choose business functions,
e.g.: ‘Retail Buying’
1+2. Choose relevant Technical
Usage(s) with potential business
value for your company.
More information about this
approach can be found here.
Business
2. Map business function(s)
to Technical Usage(s)
EHP5 SAP
Note: 1324838
Now defined: technical usage(s)
Design
Queue of installable
packages + stack xml
3. Select technical usage(s) using Solution
Manager Maintenance Optimizer.
Automated calculation and download
of required installation files
4. Install installation packages using SAPehpi
Build & Test
5. Modification Adjustment
6. Regression Test
© SAP AG
ADM326
11-30
Reading Sequence Of Documentation
about EHP Implementation Procedure
Requirements
Design
Build & Test
System
Administrator
Deploy
3
1
2
SAP Enhancement
SAP Enhancement
Package 5 Master
Package Installation
Guide
How to install SAP
Guide
Enhancement Package 5
The documentation can be found via:
http://service.sap.com/erp-ehp-inst
© SAP 2010
© SAP AG
ADM326
11-31
Phase 3:
Build and Test
Requirements
Design
System
Administrator
Test & Build
Deploy
Software Installation And Activation
Installation of SAP enhancement package with EHP-installer
Activation of Business Functions using the Switch Framework
Regression and Acceptance Testing
SAP delivers EHP test case templates
SAP Solution Manager enables risk based testing (BPCA)
Further Services
Expert Guided Implementation
- Update to SAP Solution Manager Enhancement
Package 1 including basic configuration
Result:
Getting the solution
ready and tested
First of all the business expert has to select the required business functions.
The Enhancement Package Information Center is the single point of access to all information related
to a business function for the business expert.
Here you can find presentations, documentation, release notes, test catalogues and learning maps.
The Business Function Documentation allows the user to get to know the capabilities behind a
business function and how to use them; learn about options the business function provides; and notes
which software components are needed. Please note that each Business Function has a technical
name. This identifier is important to determine which parts of the system needs to be updated.
© SAP AG
ADM326
11-32
E2E SAP Enhancement Package Installation
Process
Maintenance Optimizer
(MOPZ)
SAP
Solution Manager 7.0
latest SP level
3
PPMS
Download Basket
a
Stack
Configuration
File.xml
Technical Usages
based on
SAP EHP 5*
MOPZ
Stack
Configuration
File.xml
EHP SW
Comp.
b
SMSY
2
1
Landscape
Verification
Wizard
1 Run Landscape Verification Wizard
EHP SW
Comp.
SP‘s
c
SP‘s
SLD
SAP
ERP
SAP ERP 6.0
EHP
5 6.0
onNW
SAP
7.02
basedBased
on SAP
7.0NW
EHP
2 Maintain System landscape via SLD/SMSY
3 Run Maintenance Optimizer
a Select required Technical Usages and SP level
SCS
Insta nce
Add -I n Cen
ICM
tr al Ins ta nce
ENQ S er ver
(Java)
ABAP
Dispa tcher
Java Dispa tc her
MOPZ generate Stack Configuration file
and calculates dependent software
components and SPs
5
MS G S er ver
(Java)
W or k
W Pr
or kocess
Wor
P rkocess
Pr ocess
b
SAPehpi
4
Java
S er ver
Java
S er ver
Pr ocess
S erPr
verocess
P r ocess
E NQ WP
(ABAP )
S DM
Java
Globa l FS
Gateway
MS G S er ver
(ABAP
ABAP )
IGS
c Download SW components and SPs via Download Basket
ABAP Schema
Java Schema
4 Provide your download to SAPehpi
5 Perform the SAP enhancement package implementation
*Example for SAP ERP 6.0. CRM 7.0, SRM 7.0 und
SCM 7.0 you choose the SAP enhancement package
E2E SAP Enhancement Package installation process – example
Customer plans to update a SAP ERP 6.0 system to SAP Enhancement Package 5 for SAP ERP 6.0.
Therefore the customer needs to have installed a SAP Solution Manager 7.0 on the latest available
SP level (SP23). In addition SAP Solution Manager Maintenance Optimizer needs to be configured.
Before the customer starts a new maintenance transaction the Landscape Verification Wizard need
to run to check the system data in SMSY for inconsistencies and if needed provides hints to update
the system data.
As soon as the system data in SMSY is maintained a new maintenance transaction can be started.
During the maintenance transaction the customer has to select the required Technical Usages as well
as the target SAP Support Package level. This selection is used by the Maintenance Optimizer to
generate a Stack Configuration File, the SAP enhancement package software components as well as
the dependent SAP Support Packages.
These files can be downloaded via Download Manager. After the download the files have to be
provided to the SAP enhancement package installer. The SAP enhancement package installer uses
the files to update the SAP ERP 6.0 system to an SAP ERP 6.0 system including SAP Enhancement
Package 5 of SAP ERP 6.0
© SAP AG
ADM326
11-33
New: Landscape Verification 1.0 for SAP
Solution Manager
Correctness of landscape data is the key for a successful EHP installation:
A correct landscape configuration is a major prerequisite for error-free execution of MOpz
Erroneous or incomplete landscape information can result in failure of the update procedure
Guidance towards correctly entering all information needed in the update process is required
New Solution: landscape verification 1.0 for SAP Solution Manager
Helps to analyze system landscape data in SAP Solution
Manager System Landscape (SMSY) in order to identify issues
in landscape description
Add-on installation - details can be found here
Landscape verification promotes the “landscape pattern” concept:
Hub and sidecar - details can be found here
Using landscape verification 1.0 for SAP Solution Manager helps to improve
landscape data quality as a major prerequisite for smooth installation of SAP
enhancement packages for SAP Business Suite.
© SAP AG
ADM326
11-34
Guided Download Procedure:
Maintenance Optimizer
Requirements
Design
Test & Build
Technical usage: predefined, installable
subsets of an SAP enhancement package
for SAP ERP
SAP Note 1324838 (EHP5) maps identified
business functions to a technical usage
You enter the technical usage in the
Maintenance Optimizer and it automatically
calculates the relevant download files
Prerequisites:
- Solution Manager 7.0 EHP1 (SPS 23),
Accuracy of system data
- Data maintenance with Solution Manager
System Landscape (SMSY)
Deploy
* This is an example of installed software components in SAP ECC. For Java components and BI-, PI- and Portal content, a different installation procedure would be used.
If you use the SAP Solution Manager Maintenance Optimizer - as strongly recommended and
already required for downloading SAP Support Packages in general - you only need the name of the
Technical Usage to install all needed software components. Based on that information, the SAP
Solution Manager Maintenance Optimizer calculates the needed software components and SAP
Support Packages automatically. Create a new maintenance transaction for updating your system
with SAP enhancement packages for SAP ERP 6.0. A guided procedure leads you through the
preparation process for updating your systems. Select all systems that are affected by the application
of the SAP enhancement package. In the next step of the guided procedure, you select the Technical
Usages you want to apply to your systems. The Solution Manager Maintenance Optimizer
automatically calculates all needed SAP Support Packages and new software component versions
needed for installing the previously selected Technical Usages. As a result, the Solution Manager
Maintenance Optimizer creates the Stack-XML file that can be read by the installation tools to create
a valid import queue. You can find further information about the Solution Manager Maintenance
Optimizer at service.sap.com/solman-mopz, detailed documentation at help.sap.com > SAP Solution
Manager > (select your preferred language) in the "Change Management" section.
Please remember: The software components of SAP enhancement packages for SAP ERP 6.0
contain new developments (as we partially replace existing software components). Therefore, if you
take a look at your system after applying the SAP enhancement package software components, you
will find software components in version 600 (e.g. with SAP Support Package stack 10) as well as
software components in version 602 (e.g. SAP enhancement package 2 with SAP Support Package
stack 0 which contains equivalent corrections to SP level 10 of the same component in version 600).
© SAP AG
ADM326
11-35
System Landscape Aspects during Build &
Test Phase
Requirements
Test & Build
Design
Deploy
Legend
System landscape
= ERP + EHP5
= old release (6.0)
Temporary
development
system
= actual project work
DEV
ERP
Dual
Maintenance
EHP 5
Productive landscape
DEV
ERP
Transport
changes
= Transport route
Emergency
Corrections
EHP 5
QAS
ERP
PRD
ERP
During and after enhancement package or SAP Support Package installation your development system
may not be able to support your production line with emergency corrections and/or phased development
go-lives unless you add temporarily a copy of the development system
Based on your risk profile you should consider appropriate measures
Ensure dual maintenance
© SAP AG
ADM326
11-36
Installation of Additional Technical Usages
If you want to activate a business function that does not belong to the technical usages
that have been installed initially, you must install the missing technical usage later.
There are two different options to install additional technical usages:
SAPehpi
Transaction SAINT
Mandatory for the initial enhancement package 5
installation
Advantages:
Shorter downtime compared with transaction
SAINT
Productive work is possible before downtime
Reset is possible until beginning of downtime
Large installation queues can be processed
Prerequisites:
The enhancement package 5 Technical Usage
“Central Applications” must be already installed
Disadvantages:
Longer downtime compared with EHP Installer
Limited possibilities to reset installation
Advantage:
Disadvantage:
Total runtime is longer compared with SAINT
Shorter total runtime for small installation
queues (few packages and/or small packages)
Both installation options require modification adjustment and regression tests for the
affected software components!
© SAP AG
ADM326
11-37
Activate and Configure
Business
Transaction: SFW5
Activities before the activation …
View the list of Business Functions now selectable
Access documentation, release notes, test
catalogue and possible dependencies from here
Install the relevant documentation, refer to
SAP note 1066110
Benefits
Transparency of all system and UI changes that
will take place
Stability for all other parts of the solution
Activities after the activation …
Activate the chosen Business
Function
Configure the chosen Business
Function
Benefits
New coding becomes active only
where activated
Faster implementation because only
activated parts are configured
© SAP 2010
The switch transaction shows all the Business Functions that can now be activated after the
installation of the new software components.
In the switch framework transaction you can:
View the list of Business Functions available with the latest system setup
Access documentation, release notes, test catalogue, and possible dependencies
Install the relevant documentation, refer to SAP note 1066110
Before the activation you get transparency of all system and UI changes that will take place.
Afterwards you can activate the chosen business functions and perform the configuration tasks.
By that the new coding becomes effective. All other parts of the system remain stable.
© SAP AG
ADM326
11-38
New With Enhancement Package 5:
First Set of Reversible Business Functions
New: reversible Business Functions:
A reversible Business Function can be tested / evaluated in DEV/QAS systems
but only in separate clients
During the test of reversible Business Functions no other tests must take place
in the whole system as Business Functions are active in all clients
To completely ‘undo’ a Business Function the whole client has to be deleted
Currently there are 37 reversible Business Functions
© SAP AG
ADM326
11-39
Switch Framework: Transaction SFW5
Transport of Switch Settings
Business
Transaction: SFW5
activate Business
Functions manually
activate Business
Functions manually
Sandbox
DEV
generate transport
with switch settings
© SAP AG
QAS
transport
import transport with
switch settings
ADM326
transport
PRD
import transport with
switch settings
11-40
Test & Go Live:
SAP Delivers Test Case Templates
Requirements
Activities
Acceptance test for
selected Business Functions
Use standard test case
templates
Train end-users
Go live, transport switch
activities to production system
Benefits
Faster test preparation due to
test case templates
Smaller test scope because
changes are documented for
each business function
Test & Build
Design
Smaller training effort due to
limited and documented effect
on user interfaces
Business
Deploy
You can access the TCTs before Installing an EHP..
All test cases are available as
documents in
the enhancement package
information center
(http://service.sap.com/erp-ehp)
Documents (texts) can be
downloaded
..or after installing an EHP
Test cases are shipped with the
enhancement package and are part
of the installation (SAP ECC)
Access the test case from the
switch transaction (SFW5)
From there, you will (by drilldown)
enter the test workbench
Test cases can be transported to
SAP Solution Manager via workbench request.
Test case templates will be available for each business function that is new to an enhancement
package.
These templates can be called directly from the switch transaction. The link to the corresponding test
case is located right next to each Business Functions.
The SAP test case templates help you to plan and perform your acceptance test and train your
end users for the selected business functions.
By that you are also able to narrow down the test scope because functional changes are
documented for each business function.
So - where to find Test Case Templates?
Firstly before installing an enhancement package in SAP Service Marketplace. All test cases are
available as documents in the enhancement package information center and can be downloaded.
Secondly after installing an enhancement package via the switch framework. Test cases are
shipped with the enhancement package and are part of the installation (SAP ECC). From there,
you will (by drilldown) enter the test workbench. Test cases can be transported to SAP
Solution Manager via workbench request.
© SAP AG
ADM326
11-41
Phase 4:
Deploy
Requirements
System
Administrator
Design
Build & Test
Deploy
Go-Live and Support
Update of production system:
EHP Installer is specialized to minimize downtime
Release of the EHP System for Production Operation
Support after Go-Live
Project Closure
Services
SAP delivers continuous quality checks
Transport Management synchronizes deployment to
production
Result:
Innovation is
available for
business
First of all the business expert has to select the required business functions.
The Enhancement Package Information Center is the single point of access to all information related
to a business function for the business expert.
Here you can find presentations, documentation, release notes, test catalogues and learning maps.
The Business Function documentation allows the user to get to know the capabilities behind a
business function and how to use them; learn about options the business function provides; and notes
which software components are needed. Please note that each Business Function has a technical
name. This identifier is important to determine which parts of the system needs to be updated.
© SAP AG
ADM326
11-42
Current Statistics
SAP Enhancement Package Installer
Requirements
Design
Build & Test
System
Administrator
Deploy
EHP Installer Statistics for
SAP enhancement package 4
for SAP ERP 6.0
SAPehpi runtime
SAPehpi downtime
Median runtime: 44h
Median downtime: 7,5h
*This statistic is based on the current evaluation forms referring to test and productive systems where an enhancement package 4 implementation was performed.
© SAP AG
ADM326
11-43
Service offering: Enhancement Package
Planning for SAP ERP 6.0
Overview….
Intensive 2 days onsite workshop
We plan your enhancement package installation project & strategy
Learn from experienced SAP consultants
Feel well prepared to start your implementation project!
Project Milestone Plan
We define a customer specific implementation
ew
S
ser AP c
vic
e o onsul
t
ffer
ing ing
Knowledge Transfer
Getting behind the new technology
approach & EHP strategy
Understand the concept of switchable Business
We create an enhancement package project
Functions & Technical Usages
roadmap based SAP’s best practices & proved
methodology
*N
Learn how to use “EHP Installer” Tool
Landscape Dependencies
Order & Contact Details…
Identify technical dependencies of your system
Direct contact: upgradecc@sap.com
landscape
Service Market Place link: /ufg
Outlines critical issues for a smooth
Implementation project
© SAP AG
ADM326
11-44
Agenda: Customer
Experiences and Summary
1.
2.
3.
4.
SAP Enhancement Package Concept & Strategy
Architecture and Technology
Implementation Procedure
Customer Experiences and Summary
© SAP 2010
© SAP AG
ADM326
11-45
Benefits of SAP Enhancement Packages
Further Customer Proof Points
‘Within an extremely short timeframe, we managed to implement
functional enhancements around Real Estate Management. We went
live after only a few weeks.’
Innovate Just in Time
•
Stability and Access to
Innovation – activate new
functionality on demand.
Martin Kling, Head of Group Financials,
TreuHandStelle GmbH
‘We were delighted that no side effects occurred at all
outside the activated new functional capability. The EHP concept
allowed us to fulfill requirements years before we will start our next
release upgrade. The end-user reactions were very positive and no
critical issues occurred.’
Stephan Polster, Project Manager,
ThyssenKrupp Steel
Cost reduction
•
•
Lower effort to install
functional enhancements,
ideally silent as part of
system maintenance
Easier testing with standard
test case templates
‘The implementation of SAP enhancement package 2 for SAP ERP
6.0 was much easier than upgrading a full release. We installed all
the software components that we could get in order to be open to
implement further innovations at minimized cost at any time.’
Thomas Muhler, Technology Consultant,
cormeta ag
‘We implemented enhancement package 2 in order to use the new
capabilities for Bank Relationship Management. No critical issues
occurred. The implementation was very easy.’
Joerg Engel, System Engineer, Wuerth-Group
© SAP 2010
© SAP AG
ADM326
11-46
Comparing SAP Enhancement Packages for
SAP ERP and SAP NetWeaver
SAP Enhancement Package 2 for SAP NetWeaver
supports SAP Enhancement Package 5 for SAP ERP
SAP
Enhancement
Packages for
Installation Procedure
Impact of Installation
SAP ERP
(SAP ECC)
SAP
NetWeaver
Selective Activation
New functions are
switched on selectively
(ABAP switch
framework)
Both: Efficient and fast
installation with SAPehpi
based on proven SAP
software lifecycle
management tools
Both: No UI or process
change for end users after
installation of SAP
enhancement package.
NW EHP adds new
functionality, but
does not replace
existing functionality
SAP provides an impact
analyzer tool and test
case templates
Switching procedure
between old and new
UI screens is provided
So where is the difference between SAP enhancement packages for SAP ERP and for SAP
NetWeaver?
All in all there are a lot of similarities. The installation procedure is in both cases efficient and fast.
The installation is performed with SAPehpi based on proven SAP software lifecycle management
tools.
In both cases there is no UI or process change for end users after installation of an enhancement
package and by that the impact of Installation is limited. Furthermore new functions are switched on
selectively, either with the switch framework or other, alternative procedure.
© SAP AG
ADM326
11-47
Upgrade versus SAP Enhancement Packages
Installation: Customer Experience (Overview)
Criteria
Upgrades¹
Reduction
Business downtime
(technical installation)
Ø 48 hours
Total project duration
Ø 21 weeks
Duration of project
phases in weeks
Preparation: 3 w
Blueprint: 3 w
Realization: 8 w
Prep for cutover: 3 w
Prod. cutover & support: 2 w
- 50%
- 62%
SAP Enhancement
Packages²
Ø 24 hours
n = 87
Ø 8 weeks
n = 88
up to
70%
Preparation: 1 w
Blueprint: 1 w
Realization: 2,5 w
Prep for cutover: 2 w
Prod. cutover & support: 1 w
n = 67
According to current statistics the installation of enhancement
packages for SAP ERP 6.0 greatly increases
the speed of innovation while reducing its cost.
1
Based on n = 168 upgrades from SAP R/3 4.6C to SAP ECC 6.0; Source: Upgrade Experience Database
² Total number of enhancement package installations (EHP 2 to 4): n = 91; only those considered which provided details on these questions; this number
represents an extract only out of more than 5,900 enhancement package installations globally (as of February 2010); Source: Enhancement Package
Experience Database
© SAP 2010
© SAP AG
ADM326
11-48
Upgrade versus SAP Enhancement Package
Installation: Overall Satisfaction And Reasons
Criteria
Upgrades¹
Customer
satisfaction
n = 165
18%
SAP Enhancement Packages²
4%
1%
8%
Very satisfied
More satisfied
36%
5%
2%
Very satisfied
More satisfied
Satisfied
Satisfied
32%
Less satisfied
Less satisfied
Not satisfied
53%
Not satisfied
41%
Reasons for
upgrading /
installing
enhancement
packages
n = 168
Legal compliance
System landscape cons.
Manage modifications
Functional requirements
Improve usability
Use latest technology
Business innovation
Maintenance
Legal compliance
System landscape cons.
Manage modifications
Functional requirements
Improve usability
Use latest technology
Business innovation
Others
0
20
40
60
80
100
0
20
40
60
80
100
1
Upgrades from SAP R/3 4.6C to SAP ECC 6.0; Source: Upgrade Experience Database
² Based on n = 91 enhancement package installations (EHP 2 to 4); this number represents an extract only out of more than 5,900 enhancement package
installations globally (as of February 2010); Source: Enhancement Package Experience Database
© SAP 2010
© SAP AG
ADM326
11-49
Upgrade versus SAP Enhancement Packages
Installation: Business Downtime
Upgrade1
(hours/overall)
n = 140
Min: 22,9
0
12
24
Median: 48,0
36
48
Max: 86,2
60
72
84
96
108
Hours
Enhancement
package2
installation
Min: 8
(hours/overall)
n = 87
0
Median: 24
12
24
Max: 48
36
48
Hours
1
2
Upgrades to SAP ECC 6.0 with source release SAP R/3 4.6C ; Source: Upgrade Experience Database
Enhancement packages for SAP ERP 6.0; this number represents an extract only out of more than 5,900 enhancement package installations globally
(as of February 2010); Source: Enhancement Package Experience Database;
© SAP 2010
© SAP AG
ADM326
11-50
Upgrade versus SAP Enhancement Packages
Installation: Project Duration and Effort
Project
duration
(weeks)
Weeks
Project
effort
(person days)
Project person days
1
2
Upgrades to SAP ECC 6.0 with source release SAP R/3 4.6C and SAP R/3 Enterprise, no Unicode Conversion; Source: Upgrade Experience Database
Enhancement packages for SAP ERP 6.0; this number represents an extract only out of more than 5,900 enhancement package installations globally
(as of February 2010); Source: Enhancement Package Experience Database
© SAP 2010
© SAP AG
ADM326
11-51
SAP ERP – Top 10 Business Functions*
S A P E nhanc ement P ac kag e 2 for S AP E R P 6.0
S A P E nhanc ement P ac kag e 3 for S AP E R P 6.0
B us ines s F unc tion Name
B us ines s F unc tion Name
F IN_T R AV E L _1
S D _01
HC M_AS R _C I_1
F IN_F S C M_INT E G R AT IO N
HC M_L S O _C I_1
F IN_AC C _G R O UP _C L O S E
L O G _MM_C I_1
IS U_UT IL _1
R E _G E N_C I_1
F IN_F S C M_C C D
B us ines s F unc tion Des c ription
S AP T ravel Management E nhancements
O rder‐to‐C ash S implification
HC M P rocesses and F orms
F S C M, Integration
S AP L earning S olution
G roup C lose
B usiness F unction Materials Management
Utilites, G eneral E nhancements
R eal E state Management
F S C M, F unctions
F IN_G L _C I_1
F IN_R
_S IMP_S
L _1
/K
Y K /GEEPN_AIO
IMP L IF IC AT IO
N
HC M_E S S _C I_1
B us ines s F unc tion Des c ription
New G eneral L edger Accounting
R eporting F inancials
R oles in S AP All‐In‐O ne
HC M, E S S for P ersonal Information
O P S _P S _C I_1
HC M_E R C _C I_1
P roject S ystem
HC M, S AP E ‐R ecruiting 1
F IN_T R M_L R _F I_AN
L O G _E S O A_OP S _2
HC M_E R C _S E S _1
L O G _S D _C I_01
T R M: Hedge Management, New
Instruments, New K ey F igures
O perations, E nterprise S ervices 2
HC M, S AP E ‐R ecruiting ‐ S earch 1
S ales and D istribution
S A P E nhanc ement P ac kag e 4 for S A P E R P 6.0
B us ines s F unc tion Name
E R P _E NT E R P R IS E S E AR C H
HC M_O S A_C I_1
HC M_AS R _C I_2
F IN_R E P _S IMP L _2
F IN_G L _C I_2
E R P _AL L _P DF _F O R MS
L O G _MMF I_P 2P
E R P _AL L _L IS T S
HC M_L S O _C I_2
HC M_T MC _C I_1
B us ines s F unc tion Des c ription
E nterprise S earch in S AP E R P
HC M, P erformance Management 01
HC M, Administrative S ervices 02
R eporting F inancials 2
G eneral L edger Accounting 2
All C ommon F orms Available in P DF
MM, Integration of MM and F I
E R P , New User Interface for AB AP L ists
HC M, L earning S olution 02
HC M, C ore P rocesses in T alent Management
*1st July 2010
© SAP 2010
© SAP AG
ADM326
11-52
New version of SAP Enhancement Package
Must Know Guide available
What IT professionals
must know about
SAP enhancement packages
for SAP ERP
service.sap.com/erp-ehp
© SAP 2010
A new version of SAP Enhancement Package Must Know Guide available
© SAP AG
ADM326
11-53
Get Started - Enhancement Package
Infocenter: http://service.sap.com/erp-ehp
SAP enhancement package
strategy for SAP ERP
SAP Enhancement Packages Frequently Asked Questions
Master Guide
&
How to Install EHP5:
A Practical Guide
SAP EHP Info Center
ERP@BPX: EHP Forum & Wiki
Lifecycle of SAP
enhancement packages
SAP EHP Technology Facts
© SAP AG
ADM326
11-54
Agenda: Unicode Conversion
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
12-1
Unicode Conversion
Contents:
What is Unicode?
Major steps in an Unicode conversion project
What has a Unicode conversion to do with an upgrade?
Combined Upgrade and Unicode Conversion (CU&UC)
Twin Upgrade and Unicode Conversion (TU&UC)
© SAP AG
ADM326
12-2
Single Code Pages (Non-Unicode) in SAP
Systems
Japanese
Hebrew
Every ellipse represents
one code page
Single Code Page system
means that only
languages within ONE
ellipse can be used
Chinese
Korean
Greek
Taiwanese
Russian
Ukrainian
English
Icel
and
ic
Thai
Danish
Dutch,
German
Finnish
French, Italian
Norwegian
Portuguese
Spanish
Swedish Turkish
Croatian
Czech
Hungarian
Polish
Rumanian
Slovakian
Slovene
Without Unicode a SAP system makes use of one or more 'small' codepages.
© SAP AG
ADM326
12-3
Unicode: Example Languages Supported with
Unicode
Japanese
Unicode
ellipse
Chinese
Hebrew
Korean
Greek
Farsi
Hindi
Taiwanese
Bashkir
Panjabi
Sanskrit
Arabic
Azerbaijani
Icel
Belarusian
Bengali
and
ic
Russian
Ukrainian
English
Danish
Dutch
German
Finnish,
French, Italian
Norwegian
Portuguese
Spanish,
Swedish
Turkish
Thai
Croatian
Czech
Hungarian
Polish
Rumanian
Slovakian
Slovene
Urdu
Vietnamese
With Unicode a SAP system makes use of only one 'big' codepage.
© SAP AG
ADM326
12-4
Globalization Requirements
Acting in global business requires support of a global character set!
Companies running global business processes like global HR systems
Companies offering web services to their customers: global master data containing multiple
local language characters!
Companies using open standards: J2EE and .NET integration
Japanese
Hebrew
Chinese
Korean
Greek
Unicode is the 'master-codepage'
Taiwanese
Russian
Ukrainian
MDMP
Single
codepage
English
Danish
Dutch,
German
Finnish
French, Italian
Norwegian
Portuguese
Spanish
Swedish
Turkish
Afar
Abkhazian
Avestan
Afrikaans
Amharic
Arabic
Assamese
Aymara
Azerbaijani
Bashkir
Belarusian
Bulgarian
Thai
Croatian
Czech
Hungarian
Polish
Rumanian
Slovakian
Slovene
Bihari
Bislama
Bengali
Tibetan
Breton
Bosnian
Catalan
Chechen
Chamorro
Corsican
Czech
Church Slavic
Chuvash
Welsh
Danish
German
Dzongkha
Greek
English
Esperanto
Spanish
Estonian
Basque
Persian
Finnish
Fijian
Faroese
French
Frisian
Irish
Gaelic
Gallegan
Guarani
Gujarati
Manx
Hausa
Hebrew
Hindi
Hiri Motu
Croatian
Hungarian
Armenian
Herero
Interlingua
Indonesian
Interlingue
Inupiak
Icelandic
Italian
Inuktitut
Japanese
Javanese
Georgian
Kikuyu
Kuanyama
Kazakh
Greenlandic
Khmer
Kannada
Korean
Kashmiri
Kurdish
Komi
Cornish
Kirghiz
Latin
Letzeburgesch
Lingala
Lao
Lithuanian
Latvian
Malagasy
Marshallese
Maori
Macedonian
Malayalam
Mongolian
Moldavian
Marathi
Malay
Maltese
Burmese
Nauru
Norwegian Bokmål
Ndebele
Nepali
Ndonga
Dutch
Norweg. Nynorsk
Norwegian
Ndebele
Navajo
Nyanja
Occitan
Oromo
Oriya
Ossetian
Panjabi
Pali
Polish
Pushto
Portuguese
Quechua
Raeto-Romance
Rundi
Romanian
Russian
Kinyarwanda
Sanskrit
Sardinian
Sindhi
Northern Sami
Sango
Serbo-Croatian
Sinhalese
Slovak
Telugu
Tajik
Thai
Tigrinya
Turkmen
Tagalog
Tswana
Tonga
Turkish
Tsonga
Tatar
Twi
Tahitian
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Volapük
Wolof
Xhosa
Yiddish
Yoruba
Reserved- cust.
Zhuang
Chinese trad.
Chinese
Zulu
SAP ECC 6.0 and Unicode:
ONLY mandatory for MDMP customers
© SAP AG
ADM326
12-5
Communication: The Ideal Picture
The ideal picture:
Unicode components only
Conversions are done
algorithmically (1:1 relation)
No data misinterpretation
SAP R/3 4.7
No data loss
All business relevant characters
available at the same time
SAP BW
3rd party
R/3 4.7
Internet
Files
The Unicode logo is used here as an placeholder for any of the Unicode encoding formats UTF16LE,
UTF-16BE or UTF-8.
In case of an Unicode Unicode combination RFC passes all character data without code page
conversion or merely with adaption of the endianness.
UTF-16 big endian = SAP code page 4102
UTF-16 little endian = SAP code page 4103
Information about the destination is maintained in SM59
special options character width in target system
1 Byte = non-Unicode
2 Byte = Unicode
© SAP AG
ADM326
12-6
Communication: Reality
Reality: Unicode and
non-Unicode component
Conversions between incompatible
code pages everywhere
Only common subset exchangeable
SAP R/3 4.6C
ISO8859-1
SJIS
Special rules have to be followed to
make communication possible
SAP BW
ISO8859-1
3rd party
EBCDIC
R/3 4.7
Internet
...charset=iso-8859-1" >
...charset=windows-1257" >
...charset=Shift_JIS" >
...charset=utf-8" >
Files
SJIS
IS0-1
IS0-8 1251
1251
BIG-5
697/ 697/
1251
0500 0277
IS0-7
1252IS0-2
In an MDMP (Multi Display Multi Processing Code Page) system character data is encoded in
different code pages. Only that part of the data that belongs to the current system code page will be
handled correctly during string processing or code page conversions. In an MDMP system you have
to ensure that you use language keys to mark your data. Use SET LOCALE LANGUAGE to switch
between different system code pages.
© SAP AG
ADM326
12-7
Unicode: Communication Rules RFC
Sender
Unicode
Receiver
MDMP
“
MDMP
no issues
no issues as Unicode is
superset of all code pages
understands all characters
special measure required to
ensure communication
receiver understands only
characters that are part of
the SCP in use
No issues in case of
identical SCP; otherwise
only ASCII 7 subset can be
exchanged without errors
No issues in case SCP is
part of MDMP and language
info is correct; otherwise
only ASCII 7 subset can be
exchanged without errors
receiver understands only
characters that are part of
its MDMP code pages
No issues in case SCP is
part of MDMP; otherwise
only ASCII 7 subset can be
exchanged without errors
receiver understands only
characters that are part of
its MDMP code pages
Unicode
Single Code
Page (SCP)
Single Code Page (SCP)
Complex communication landscapes that worked before will
work also after Unicode conversion if communication rules and
user discipline is preserved!
Examples for issues of Unicode <> MDMP communication:
Language key must be provided correctly, otherwise inconsistencies and short dumps may occur
on receiver side;
The connection of an Unicode SAP BW system to an MDMP SAP ECC system requires special
interface adoptions to work correctly.
Special attention should be paid to SAP to non-SAP interfaces. Unicode compliance of non-SAP
software must be ensured. Especially, links to printer or fax machines should be tested as well.
© SAP AG
ADM326
12-8
Expected Hardware Requirements Database
Database
Encoding
Add. Storage Req‘s
DB2 (Universal Database for Unix / NT)
UTF-8
~10%
Oracle
CESU-8
~10%
MaxDB
UCS-2
40 … 60%
MS SQL
UCS-2
40 … 60%
DB2 for AS/400
UTF-16
10 … 20%*
DB2 for z/OS**
UTF-16
20 … 60%**
* small growth as biggest part of the Ascii based database is already UC
** white range as it depends on compression usage
Average database growth at customers (sum of all sizes):
UTF-8 and CESU-8: -14% (for more than 90% of the installations the database
shrunk - due to the reorganization)
UTF-16: +30% - +40%
© SAP AG
ADM326
12-9
Additional Hardware Requirements for
Unicode
Based on parallel benchmarking of Unicode / non-Unicode test systems
Note: The CPU/RAM figures are measured average numbers and will be different for different transactions
CPU
RAM
+30%
depending on
existing scenario
(MDMP, double byte)
Database size
UTF-8*
: up to +10%
ORACLE, DB/2 (AIX)
UTF-16 : + 20 ... 60%
SQL Server, DB/2 (AS400),
MAX DB (7.0)
1. Priority
+50%
Application Servers
are based on UTF-16
internally
Network Load
UTF-8
almost no change
due to efficient
compression
* 35% is the observed maximum in growth for small systems (db size < 200 GB).
* 10% is the observed maximum for bigger systems (db size > 200 GB).
When using Unicode, characters use up more space in database and main memory.
This causes the need of much more hardware to keep the system performance the same as without
Unicode.
© SAP AG
ADM326
12-10
Conversion (Without Upgrade)
Import and export during downtime
Unicode conversion during export
SPUMG
Reprocess
Log
Control
Table
non
Unicode
Vocabulary
EXPORT + Conversion
R3load
Data
R3load
Unicode
IMPORT
The default conversion method is to export the entire database using R3Load, create a new Unicode
database, and then import the database using R3Load again.
Conversion from Unicode to non-Unicode is not possible
MCOD (more than one SAP system in one database):
a Unicode SAP system is not compatible with a non-Unicode SAP system
Unicode SAP systems are not released for Informix.
If the source system is a MDMP system perform additional steps that are described SAP Note
551344.
If you are using HR functionality within SAP R/3/SAP ECC, additional steps are mandatory, which
are described in SAP Note 573044.
Currently SAP does not support an upgrade with simultaneous Unicode conversion. Therefore you
must first upgrade a non-Unicode system with a basis release less than AS ABAP 6.20 to AS ABAP
6.20 (or higher). Once the non-Unicode system uses AS ABAP 6.20 or later you can convert to
Unicode.
Perform the following steps on the source system:
Preparation step in the transaction SPUMG
Initialize the worklist (see SAP Note 548016)
© SAP AG
ADM326
12-11
Downtime: Dependencies
Single Code Page or MDMP conversion?
MDMP requires more reconversion tasks and post conversion handling in the Unicode
system
Biggest tables – optimize parallelization of export/import processes
(splitting of R3load packages)
Processing of cluster tables
Sizes of cluster tables (compared to
transparent tables)
SAP Note
784118
857081
Hardware
Number and speed of CPUs
Performance of disks
Separate server available for Unicode system?
Time spent on optimization (problems not related to runtime)
Production time:
Unicode enabling of customer programs and conversion of customer code pages
Transport for import of customer programs
Unicode preparation with tool SPUMG
Downtime:
Unicode Conversion (system copy with SAPinst)
Manual completion steps
© SAP AG
ADM326
12-12
Runtimes – Customer Experiences
Examples for Export / Import Runtimes
Net Runtimes in hours
(Database Size > 1000GB)
50
45
40
35
30
25
20
15
10
5
0
800
1800
2800
3800
4800
5800
6800
7800
8800
DB size in GB
Net runtimes on PRD systems: time needed from begin of export until end of import
(without e.g. prepare jobs, back-up, tests after the conversion etc.)
Most of the shown examples used two servers
(export on server 1 and import on server 2 in parallel).
Experiences show that the reduction can be significantly high when using the two servers
scenario (e.g. from 50 h 28 h for the runtimes).
The pure export and import of the database should be possible within a two days downtime window.
© SAP AG
ADM326
12-13
Steps to Minimize Unicode Downtime
1. Use old system for export and new machine for import
2. Create database statistics
3. Parallelize export/import processes (2 proc. for each CPU core)
4. Split packages (separate TOP 50 tables)
5. Split TOP 10 biggest tables (R3ta)
6. Use FAST LOAD option (DB feature)
7. Use unsorted UNLOAD
8. Parallelize index creation
9. Increase your I/O throughput
Optimization
enhancements do not
result in an
acceptable downtime:
10. Create reusable scripts
Minimized Downtime Service (MDS) is offered by SAP Consulting
(but not possible in combination with an upgrade)
If necessary, the IMIG (incremental migration) technology is used
Please have a look at SAP Note 693168 - Email: MDS@sap.com
Hardware Tuning (e.g. additional CPUs)
Use additional (new) server for the Unicode system
Database tuning (see note 936441)
R3Load package split (see System Copy Guide)
Table split (see note 952514)
Migration monitor (See note 784118)
Distribution monitor (See note 855772)
Export: unsorted export of transparent tables (see note 954268)
Import: R3Load option 'Fastload' (See note 864861)
© SAP AG
ADM326
12-14
Who Needs Unicode?
Acting in global business
requires support of a global character set!
Companies running global business processes like global HR systems or global master data
management
Companies offering web services to their customers: global master data containing multiple
local language characters!
Companies using open standards: J2EE and .NET integration (JAVA speaks Unicode!)
Collaborative business: integration of third party products that run on different code pages
First upgrade, then conversion to Unicode.
Customers upgrade their SAP systems to the required non-Unicode target release (at least AS ABAP
6.20).
Afterwards they perform the Unicode Conversion - as a separate project.
© SAP AG
ADM326
12-15
Unicode Conversion
Questions
Which Unicode Conversion approaches exist in combination with upgrades
or other activities?
What are SAP recommendations?
What are prerequistes and side effects?
Options ECC
UC without upgrade
standard method (SAPInst/R3load)
Minimized Downtime Service (MDS) with IMIG
UC with upgrade
Twin Upgrade & Unicode Conversion (TUUC)
Combined Upgrade & Unicode Conversion (CUUC)
Near Zero Downtime Method (NZD)
Options other products
UC without upgrade
UC with upgrade
standard method
Combined Upgrade & Unicode Conversion (CUUC)
Note: For non-ECC products, the method CUUC is only available as pilot projects for sources with
AS ABAP 6.20 or later. Please contact SAP for more information.
© SAP AG
ADM326
12-16
Building Blocks of Unicode Conversion
Projects
ABAP Unicode
enabling
Interface
adaptation
Project
management
Technical
conversion
© SAP AG
MDMP
handling
ADM326
12-17
Unicode Conversion Roadmap
The Conversion Roadmap takes you step-by-step through the process of converting a
non-Unicode system to a Unicode system.
Prerequisites: You must first ensure that you employ Unicode-based SAP components and a
Unicode-enabled database, as detailed in the following SAP Notes 379940 and 79991
Phases
Preparation
Conversion
Post-conversion
High level description
During preparation, topics such as additional hardware requirements,
downtime issues, Unicode-enabling of customer developments, and the
special treatment of MDMP systems have to be taken into consideration.
The Unicode conversion process is based on a system copy, and during this
process, the database conversion and system shutdown/restart are as
automated as possible. For small to mid-size databases (< 1 TB), this is
based on an SAP unload/reload of the complete database; minimum
downtime tools will be used for larger databases.
Once the Unicode system is up and running, you need to verify data
consistency on a scenario basis, as well as carry out general integration
testing. For systems that support multiple languages, special emphasis
needs to be placed on cross-language handling during the test phase.
Correction tools are provided by SAP, which can be used in the case that
conversion did not run properly.
Note: For details and conversion guides see SAP Service Marketplace http://sercive.sap.com/unicode
© SAP AG
ADM326
12-18
Which Factors Influence the UC Conversion
Project?
easy
medium
difficult
Used language
support technology
Single
codepage
Asian
codepage
Multiple
codepages (MDMP)
Type of system
SAP NetWeaver AS
standalone
SAP ECC
SAP CRM
with Mobile Sales
System properties:
Database size
Downtime
Hardware performance
Small database size
Long Downtime window
Good performing Hardware
Large database size
Small Downtime window
Bad performing Hardware
ABAP enabling
Small amount of
objects
Easy objects
(CS, …)
Large amount of
objects
Difficult objects
(Offset)
Conversion methods
Standard
Table
splitting
Interfaces to
SAP systems
SAP Unicode
systems
SAP single
codepage Latin-1
Interfaces to
Non-SAP systems
Unicode based
systems
Single codepage
Latin-1
© SAP AG
ADM326
Combined Upgrade
& Unicode Conversion
SAP MDMP
+ TABLES
SAP MDMP
+ ALE (container)
Single codepage
Asian
12-19
Recommended Upgrade Paths for Unicode
Conversion
Unicode
Conversion
before Upgrade
SAP R/3 4.7 Convert SAP R/3 4.7 Upgrade
SAP ECC 6.0
and above
and above
UNICODE
MDMP
Unicode
Combined
Upgrade &
Unicode
Conversion
(CUUC)*
SAP R/3
4.6C
and above
MDMP
SAP R/3 4.6B
or lower
Twin Upgrade
& Unicode
Conversion
(TUUC)*
All releases
MDMP
SAP R/3 4.7
and above
Unicode
Conversion
before Upgrade
SAP R/3 4.7 Convert SAP R/3 4.7 Upgrade
SAP ECC 6.0
and above
and above
Unicode
SCP
Unicode
SAP R/3 4.6C
or lower
Upgrade before
Unicode
conversion
All releases Upgrade SAP ECC 6.0 Convert SAP ECC 6.0
SCP
SCP
Unicode
SAP R/3 4.7
and above
SAP R/3
4.6C
Yes
Do you
currently
use
MDMP?
Upgrade, directly followed by
Unicode Conversion
Upgrade, directly followed by
Unicode Conversion
SAP ECC 6.0
Unicode
SAP ECC 6.0
Unicode
No
>90%
of customers
*CUUC/TUUC: it is also possible to upgrade with CUUC or TUUC, if the start release is an SCP system
Prior to building the SAP ECC 6.0 upgrade business case, it should be determined if Unicode is a
relevant topic for your company and how to handle Unicode
Depending if you are currently handling multi-code pages through MDMP, your options might look
different:
The most typical – and our recommendation for more than 90% of customers who are not using
MDMP – is for customers who are on SAP R/3 4.7 to do the Unicode conversion and then the
upgrade.
Alternatively for customers who are on a release lower than SAP R/3 4.7, we recommend first
to upgrade and then leverage conversion tools to do the conversion on SAP ECC 6.0.
If you are using MDMP which is true for multi-national customers, and depending on your current
release, you can either do the upgrade, immediately followed by the unicode conversion. If the gap is
very small, the conversion can be done in a very short time. If you are on a lower release than 4.6C,
you will need to upgrade first, but we would recommend to keep the time as short as possible
between upgrade and conversion since SAP doesn‘t support MDMP anymore as of SAP ECC 6.0
and thus we require a special disclaimer from you.
© SAP AG
ADM326
12-20
Ways to Your Unicode SAP System
Supported Unicode Conversion Paths:
Unicode Conversion without Upgrade
standard path for >= R/3 4.7
Combined Upgrade & Unicode Conversion
source release >= R/3 4.6C
for target release >= ECC 6.0 only
Twin Upgrade & Unicode Conversion
especially source release < R/3 4.6C MDMP
Advantages of CU&UC
Upgrade and Unicode Conversion in one Downtime
MDMP scan (SPUM4) can be performed on the SAP R/3 4.6C source system
Possible for SAP R/3 4.6C / SAP R/3 4.7 / SAP ECC 5.0 (MDMP and Single Codepages)
Prerequisites and Restrictions of CU&UC
Information and restrictions according to note 928729 / CU&UC Conversion Guide
Complexity of the project is high - two projects are combined into one !
Downtime needs to be tested and usually enhanced
Sandbox conversion is highly recommended
- Evaluation of proper downtime is only possible on a sandbox system
ABAP Unicode Enabling needs to be done e.g. in sandbox system or upgraded development
system for start release SAP R/3 4.6C
Development freeze during project highly recommended
© SAP AG
ADM326
12-21
Combined Upgrade & Unicode Conversion
(CU&UC)
Many customers have SAP R/3 4.6C systems with MDMP configurations.
They want to upgrade to a release >= SAP ECC 6.0.
Problem:
MDMP support is discontinued starting with release SAP ECC 6.0 .
Customers can not upgrade their MDMP systems to SAP ECC 6.0
first and then convert to Unicode afterwards.
Customers can not convert to Unicode first and then upgrade to
SAP ECC 6.0 because SAP R/3 4.6C is not a Unicode-enabled release.
Solution:
The 'Combined Upgrade & Unicode Conversion (CU&UC)' enables
customers to upgrade to SAP ECC 6.0 and switch to Unicode in one downtime window.
Note:
CU&UC is globally available for >= SAP R/3 4.6C - for other products pilot only.
Please read SAP Note 928729 for details.
Every customer who runs on SAP ECC 6.0 with MDMP productively (it does not matter how
long) has to sign the disclaimer - there are no exceptions.
The customer specific support during this time has to be clarified within the project.
There is no longest time frame, this needs to be clarified in the project as well. Recommendation
would be to make it as short as possible and not to exceed 3 month.
See also
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_SCENARIO=01100
035870000000112&_OBJECT=011000358700006895212005E --> last page
During CU&UC upgrade and Unicode conversion are executed sequentially.
Time saving: Nametab creation during system uptime
The cost saving of CU&UC lies in the project time. You need to test only one target (the upgraded
Unicode system) instead of two (the upgraded Non-Unicode system and the final Unicode system).
© SAP AG
ADM326
12-22
CU&UC Example:
SAP R/3 4.6C MDMP → SAP ECC 6.05 Unicode
SAP R/3 4.6C
MDMP
Unicode
preparation
SAP ECC 6.05
MDMP(!)
Unicode
conversion
Upgrade
SAP
BASIS
4.6C
Production time
SAP ECC 6.05
Unicode
Unicode post
processing
AS
ABAP
7.02
AS
ABAP
7.02
Downtime
*SAP ECC 6.05 = Enterprise Central Component of SAP Enhancement Package 5 for SAP ERP 6.0
During CU&UC upgrade and Unicode conversion are executed sequentially.
The cost saving of CU&UC lays in:
a) the project time. You need to test only one target (the upgraded Unicode system) instead of
two (the upgraded Non-Unicode system and the final Unicode system).
b) Nametab generation is done automatically during system uptime
© SAP AG
ADM326
12-23
Twin Upgrade & Unicode Conversion (TU&UC)
Customers with MDMP <= SAP R/3 4.6B want to upgrade to >= SAP ECC 6.0.
Problem:
They can not make use of the CU&UC because the Unicode Preconversion tool is not utilizable
in their release.
Solution:
The 'Twin Upgrade & Unicode Conversion (TU&UC)' is a release-independent concept which
allows a combination of Upgrade and Unicode conversion.
Note:
TU&UC enables customers to perform both procedures in one downtime window!
How?
Preparation steps (SPUMG) are done in an upgraded copy of the production system (twin
system):
The twin system is used for collecting all necessary information required for a fast run in the
production system and for creating the control information needed for the correct conversion of
the MDMP data.
The results are then reused during the conversion of the production system in order to minimize
the downtime.
Every customer who runs on ECC 6.0 with MDMP productively (it does not matter how long) has to
sign the disclaimer - there are no exceptions.
The customer specific support during this time has to be clarified within the project.
There is no longest time frame, this needs to be clarified in the project as well. Recommendation
would be to make it as short as possible and not to exceed 3 month.
See also
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_SCENARIO=01100
035870000000112&_OBJECT=011000358700006895212005E --> last page
Options: Customers can upgrade their MDMP system to a release lower than ECC 6.0, perform the
‚normal‘ Unicode conversion and then upgrade the Unicode system to ECC 6.0 or choose the
CU&UC after the first upgrade.
= too much downtime – unacceptable!
Reason for no SPUM4 in SAP R/3 4.6B: for SPUMG and SPUM4 we need ABAP Objects. This
ABAP feature is available as of Basis Release 4.6C
© SAP AG
ADM326
12-24
TU&UC Example:
SAP R/3 4.6B MDMP SAP ECC 6.05 Unicode
Unicode
conversion
Upgrade
Production
run
SAP ECC 6.05
SAP R/3 4.6B
MDMP
MDMP (!)
Downtime
SAP ECC 6.05
Unicode
Import
results
System
copy
Unicode post
processing
Unicode
preparation
Upgrade
SAP R/3 4.6B
MDMP
SAP ECC 6.05
MDMP (!)
Twin run
With the end of support of MDMP systems based on AS ABAP 7.00 (e.g. SAP ECC 6.0; see notes
79991 and 838402) there is a need for MDMP customers to convert their systems before going live
with their targeted upgrade version.
Depending on the software component several MDMP customers now face the problem, that
Unicode is not available in their start release (e.g. SAP R/3 4.6B) and MDMP is not supported in the
target release (e.g. SAP ECC 6.0). As the MDMP Unicode conversion preparations with SPUMG
are only possible on the target release and as they take normally at least one week, customers are
faced with a unacceptable downtime for the combination of upgrade and Unicode conversion.
In order to close this gap SAP is providing the so called 'Twin Upgrade & Unicode Conversion'
which allows to combine upgrade and Unicode within one downtime window. The twin concept is
doing the MDMP Unicode conversion preparations in an upgraded copy of the production system
(twin system) and the results are later reused for the productive conversion without the need to rerun
the MDMP Unicode preparation steps in the production
© SAP AG
ADM326
12-25
Unicode Conversion
Overview of methods and tools
Standard UC1
Incremental
Migration1
SAPinst/R3load
Tools
CUUC
IMIG tool
(using DB trigger)
SAPInst/R3load
SAPup
SAPInst/R3load
special programs (e.g.
SPUM4)
TUUC
SAPup
R3load
special programs
Near Zero
Downtime
Prerequisites
Source: ≥ SAP R/3 4.7,
SAP SCM 4.0, SAP CRM
4.0, SAP SRM 4.0, SAP
SEM 4.0, SAP BW 3.5,
SAP KW 7.0
source ≥ SAP R/3 4.7
source: ≥ SAP R/3 4.6C;
target: SAP ECC 6.0
pilot possible for other
products ≥ AS ABAP 6.20
Source: all SAP R/3
releases; only MDMP or
blended code page
systems
source: ≥ SAP R/3 4.6C;
Product: ERP/ AS ABAP
+ established method
+ usable for all products
+ reduced downtime by
uptime transfer of large
tables
+ one project
+ optimized handling and
slightly reduced downtime
of combination
+ preparation w/o upgrade
+ one project
+ optimized handling and
slightly reduced downtime
of combination
+ available for all releases
+ one project
+ significant reduction of
downtime
+ improved fallback
scenarios
Standard UC project
+10% -100% DB storage
- SAP consulting offer, not
delivered by partners
- additional project
hardware (full DB server)
- additional test cycles
Combination of
standard upgrade +
UC
+ less test efforts
+ no add. hardware for
Unicode conversion
Combination of
standard upgrade + UC
+ less test efforts
additional project
hardware required (full DB
server)
- SAP consulting offer, not
delivered by partners
- additional project hardware
(full DB server)
- additional test cycles
+ SAP guarantees
downtime ≤ 24h
Benefits
Costs
100-200 GB/hour
throughput
≤ 1 TB ≤ 48 h
Downtime2
Business impact
- long downtime
- extra code freeze
(partly)
- extra upgrade project
1 No upgrade, has to be separate project
© SAP AG
system copy
DB trigger
SAPup
R3load
SLO Migration
Workbench
- performance impact in
production by DB triggers
- extra code freeze (partly)
- extra upgrade project
≤ 1 TB ≤ 48 h
~ 3 TB ~ 60h
~ 4 TB ~ 72h
+ no upgrade required for
language scan
- performance impact in
production by SPUM4
- reduced functionality of
SPUM4
≤ 1 TB ≤ 48 h
~ 3 TB ~ 60h
~ 4 TB ~ 72h
+ full functionality of
SPUMG for language scan
+ goal: downtime ≤ 12h for
arbitrary system sizes
- performance impact in
production by DB triggers
2 throughput figures are rough estimates based on SAP experience; depends on customer environment
ADM326
12-26
Unicode Conversion
Rules for complex landscape conversions
“
Convert MDMP systems first
“
“
“
“
“
© SAP AG
Do not extend or implement MDMP in existing systems – convert these
systems to Unicode the more code pages the more complicated the conversion gets
Unicode compatible release and SAP Support Package level need to be met
Minimize Unicode – MDMP Interfaces they cause most effort
Convert the fast growing systems in the first place
The bigger the system, the more effort needs to be spent on downtime
Minimize Unicode Single Codepage interfaces
Risk of transfer of non-supported characters from Unicode to Single Code Page
SCP system only sending to Unicode system can be converted later
no “data loss risk”
If several PRD systems connect to one DEV system, convert all
PRD systems to Unicode
Check multi language requirements in different systems
Example: SCM system is often operated in EN only – low Unicode priority
ADM326
12-27
UNICODE – Summary and Recommendations
There is no MDMP support in SAP ECC 6.0 and above
Evaluate Unicode usage for single codepage systems
Choose option for Unicode conversion
Enable your customer developments for Unicode
Consider the high effort for preparing Unicode conversion
in MDMP systems (language/codepage assignment)
Test and optimize runtime/downtime of the Unicode
conversion
Plan your Unicode conversion project in close relation to
your upgrade project
Be aware of the importance of the data integrity - interface
check regarding the switch from non-Unicode to Unicode
© SAP AG
ADM326
12-28
Further Information
SAP Service Marketplace Quick Links
www.service.sap.com/unicode@sap
www.service.sap.com/unicode
www.service.sap.com/upgrade-erp
SAP Notes
551344 'Unicode Conversion'
548016 'Conversion to Unicode'
79991 'Multi-Language and Unicode support of mySAP solutions'
928729 'Combined Upgrade & Unicode Conversion FAQ'
959698 'Twin Upgrade & Unicode Conversion FAQ'
Required documentation
CU&UC Guide: www.service.sap.com/unicode@sap
Component Upgrade Guide:
www.service.sap.com/upgrade-erp
Homogeneous and Heterogeneous System Copy for SAP Systems
based on SAP NetWeaver 7.0: www.service.sap.com/installnw2004s
© SAP AG
ADM326
12-29
Unicode Conversion Downtime Optimization:
Costs vs. Benefits
Business Downtime
Basic
( 500 GB)
Medium
( 1000 GB)
Large
( 4000 GB)
Huge
(> 4000 GB)
Costs to reduce downtime
Standard
Unicode
Conversion
© SAP AG
Use latest SAPInst
tools (tp, R3Load,
etc)
Usage of faster CPU´s
& Storage
Table Split
Database Tuning
Migration Monitor
Additional server
Distribution Monitor
R3Load Package
Split
Unsorted export
Fastload
ADM326
Minimized
Downtime Service
using incremental
migrations (IMIG)
Near Zero
Downtime
approach
12-30
Customer Experiences – Throughput and
Runtimes
Unicode conversion throughput
200
Speed in GB/h
180
160
140
120
100
80
60
40
20
0
0
500
1000
1500
2000
2500
3000
3500
4000
DB size in GB
Depending on hardware and parallelization effort,
the R3load throughput is normally 10 to 200 GB/h.
Highest reported throughput was ~690 GB/h for
standard conversion.
Actual production runtimes do not increase with
size because of tuning measures.
Technical background for fastest measurement:
690 GB/h have been reported for 6.4 TByte (+ indices) MDMP system. Total time of 9h 15 min
for export and import.
DB was Oracle, OS was IBM AIX.
Old and new hardware was used for export and import with several powerful application
servers.
Hardware was dynamically allocated based on export and import progress.
Tables were split with DB specific measures (ROWID splitter, SAP Note 1043380).
Customer staff performed several more Unicode conversions for production systems with sizes
between 4 and 9 TByte before this conversion. Performance increased with every execution.
© SAP AG
ADM326
12-31
Combined Upgrade and Unicode Conversion
Procedure Integration Schematically
Sequentially:
Upgrade
Uptime
Unicode Conversion
Downtime
Uptime
Downtime
time
Downtime of complete procedure
Optimized Preparation:
Uptime
Downtime
Uptime
Downtime
Downtime of complete procedure
speed up
time
What can be gained?
Customer example:
© SAP AG
System Size in GB
Generation of Unicode Nametabs
Cluster Tables Check
880
5h
12 h
526
1,5 h
20,7 h
ADM326
12-32
Example Unicode Conversion with MDS
(Minimized Downtime Service)
Technical downtime for an 8 TB Database comprises:
1. MDS completion 1,5hrs
2. Export/Import of the rest tables (4 hrs)
3. Technical post activities 2,5 hrs
- The total Business Downtime will be less than 24hrs
© SAP AG
ADM326
12-33
© SAP AG
ADM326
12-34
Agenda: Tools and Services
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
13-1
Tools and Services
Contents:
Understand how SAP upgrade services, tools and accelerators address
customer challenges and needs
Where to find up-to-date information
© SAP 2010
© SAP AG
ADM326
13-2
Agenda
1. Introduction
2. Planning Tools for Upgrades and SAP Enhancement Packages
3. Technical Upgrade and Implementation Tools
4. Change Management Tools
5. Test Tools
6. Summary and Further Information
© SAP 2010
© SAP AG
ADM326
13-3
Agenda: Introduction
1. Introduction
2. Planning Tools for Upgrades and SAP Enhancement Packages
3. Technical Upgrade and Implementation Tools
4. Change Management Tools
5. Test Tools
6. Summary and Further Information
© SAP 2010
© SAP AG
ADM326
13-4
Main Challenges When Planning And
Executing an Upgrade – Worldwide Results
Plan
Build
Estimate cost & effort
69%
Define business case
Efficient testing
64%
46%
Downtime minimization
Define and allocate
project
team/resources
46%
Downtime minimization
46%
Assess impact on
existing solution
29%
Interoperability
28%
Compliance
considerations
48%
Project management
47%
End user training
39%
IT infrastructure/sizing
39%
14%
Others
N=1,484
Modification adjustment
43%
Find information
on upgrade methods &
tools
54%
Others
4%
0%
20%
40%
60%
80%
100%
N=1,484
5%
0%
20%
40%
60%
80%
100%
The report include answers from the following 360° Upgrade adoption programs: North America (Jan 2008), Brazil (March 2008), Germany (March 2008), Japan
(March 2008), UK & Ireland (March 2008), Australia (April 2008), Sweden (April 2008),China (May 2008), India (May 2008) and France (Sept 2008)
© SAP 2010
© SAP AG
ADM326
13-5
Technical Innovation – Upgrades…
…are large projects…
…but with progressive scope !
Technical Upgrade
Affecting the whole
enterprise
Demanding in-depth
knowledge of
Business models
Processes
Application landscapes
Fast
Requiring strict planning
and precise timing
Take your
time
Low costs
and manageable
impact
Application modification
New
Functionality
Protect
investment
Generate
value
as you go
Enterprise
SOA
Discover,
prepare
and
get even
more
value
Think BIG and start SMALL!
© SAP 2010
© SAP AG
ADM326
13-6
How to Find the Right Tool for My Upgrade or
Enhancement Package Implementation Project
„...there are so
many different
tools available.
Which tool can
support me in my
project?“
What I need is a short
overview – with expedient
criteria to find the right tool
for my upgrade and SAP
enhancement package
implementation projects.
© SAP 2010
© SAP AG
ADM326
13-7
SAP Solution Manager
SAP
SAP Customer
Test Workbench Upgrade Roadmap
Maintenance Optimizer
eCATT
Test Case Templates for SAP ERP Business Process Change Analyzer
SAP Custom Development Management Cockpit
SAP Service
Marketplace
Solution Documentation Assistant
SAP Experts
++
End-to-end
solution operations
SAP Enhancement Package 1
for SAP Solution Manager 7.0
SAP Solution Manager 7.0
Mainstream Maintenance
2005
2006
2007
2008
2009
2010
Customer-specific
maintenance
2011
© SAP 2010
© SAP AG
ADM326
13-8
Tools Overview
Plan
Tools
supporting
upgrades and
enhancement
package
implementations
Technical
upgrade and
implementation
tools
Change
management
tools
Testing tools
Build
Run
SAP Upgrade Road Map
Solution Browser Tool
Upgrade Dependency Analyzer
Scenario and Process Component List
Product Availability Matrix
Quick Sizer Tool
SAP Upgrade Experience Database
Solution Documentation Assistant
Business Function Prediction for SAP ERP
Landscape Verification
Maintenance Optimizer
Application-specific Upgrade Toolbox
SAPup / SAPjup
Near Zero Downtime for ERP
SAP Enhancement Package Installer
SAINT / JSPM
Business Process Change Analyzer
Custom Development Management Cockpit
Custom Code Library
SAP CloneFinder and Dynamic Usage Detector
Enhanced Change and Transport System
Change Request Management
Enhancement and Switch Framework
Modification Adjustment Tools: SPDD / SPAU / SPAU_ENH
SAP Landscape Transformation
SAP Test Data Migration Server
eCATT
SAP Test Workbench
SAP Test Acceleration and Optimization
SAP Quality Center by HP
SAP LoadRunner by HP
© SAP 2010
© SAP AG
ADM326
13-9
Agenda: Planning Tools for Upgrades
and SAP Enhancement Packages
1. Introduction
2. Planning Tools for Upgrades and SAP Enhancement Packages
3. Technical Upgrade and Implementation Tools
4. Change Management Tools
5. Test Tools
6. Summary and Further Information
© SAP 2010
© SAP AG
ADM326
13-10
SAP Upgrade Road Map
Description
SAP's standard methodology to plan and
execute the upgrade of an SAP application
Content: Best practices and templates for
project management, functional and technical
aspects facilitating key tasks of the entire
project team
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/upgraderoadmap
Locally in your SAP Solution Manger
Benefits
Repeatable approach that helps to mitigate
risks, attack key time consumers and reduce
costs and effort
Central point of access to upgrade project
information and integrated use with SAP
Solution Manager
© SAP 2010
© SAP AG
ADM326
13-11
Solution Browser Tool
Description
Discover new functionality across different
SAP ERP releases and SAP enhancement
packages for SAP ERP
Assess the business benefits and the value of
upgrading by comparing functional
enhancements
Further Information / Tool Access
Via SAP Upgrade Info Center at:
http://service.sap.com/upgrade-erp
Direct access at:
http://erp.fmpmedia.com
Benefits
Tailored access to detailed and structured delta
information
Reduced effort to define a business case or
value proposition for an upgrade
Fast identification of capabilities that respond
to user requirements
© SAP 2010
Highlights:
SAP Business Suite content available soon
New design available soon
The solution browser tool for SAP ERP is an online tool and is accessible in the SAP Service
Market Place or alternatively on http://erp.fmpmedia.com/
This tool is a kind of database which contains all information about release delta functionality
It helps to identify new features that have been added between two releases of SAP ERP or any of
the available enhancement packages and helps to find details of their respective business benefits
The user logs on directly and freely and will get a selection on release delta functionality filtered by
source release, target release, solution area and module.
The customers are strongly encourage to use this tool to get an insight into new functionality that the
new ERP release brings and to evaluate relevant new functionality which can then be mapped against
the customer requirements
Doing so, the solution browser tool for SAP ERP provides the input to build a value proposition for
the upgrade
© SAP AG
ADM326
13-12
Upgrade Dependency Analyzer (UDA)
Description
Check the existence of upgrade dependencies
between two separately installed SAP systems
in your system landscape
Landscape analysis capabilities (planned for
next SAP Solution Manager release)
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/uda
Planned: SAP Solution Manager
‘Implementation / Upgrade’ work center
Benefits
Simplification of upgrade planning
Fast and easy access to needed dependency
information for SAP products
Reduction of risks of late problem discovery
Reuse of customer specific system landscape
definition (planned for next release)
© SAP 2010
© SAP AG
ADM326
13-13
Scenario & Process Component List (SCL/PCL)
Description
Allows to flexibly illustrate possible technical
realization alternatives for key business
scenarios and processes
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/scl
Benefits
Easy identification of the components needed
to realize a new business scenario / processes
Quick access and easy to use
Central access point across all SAP solutions
Customers starting an upgrade can find out
which components can - or cannot - be
combined for certain business scenarios /
processes
© SAP 2010
© SAP AG
ADM326
13-14
Product Availability Matrix (PAM)
Description
PAM bundles technical and release planning
information for SAP software product versions
for quick reference
Provides detailed information for SAP products
on availability and maintenance end dates,
upgrade paths, as well as technical release
information such as supported DB platforms
and operating systems
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/pam
Benefits
Central access point across all SAP software
product versions
Quick access and easy to use
Reduction of risks of late problem discovery
© SAP 2010
© SAP AG
ADM326
13-15
Delta Sizing / Quick Sizer Tool
Description
Joint development of SAP and its hardware
partners to support system sizing
Can be used for delta sizing during upgrade
and SAP enhancement package projects if new
functionality is being implemented
For pure technical upgrades the additional
resource requirements can be determined by
SAP note 85524 and related notes (per release)
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/quicksizing
Benefits
Allows verification of hardware resources for
SAP systems
Reduces risk of performance problems
Supports the budget planning
© SAP 2010
© SAP AG
ADM326
13-16
SAP Upgrade Experience Database and SAP
Enhancement Package Experience Database
Description
Provides statistical data about SAP ERP 6.0
upgrade projects
Additional database for SAP CRM 7.0 upgrades is
currently being build up
Statistical data for SAP enhancement package
implementation projects for SAP ERP is
available in the SAP enhancement package
experience database
SAP R/3 4.6C
Further Information / Tool Access
SAP Service Marketplace:
SAP Upgrade Experience Database:
http://service.sap.com/upgradedb
SAP Enhancement Package Experience
Database: http://service.sap.com/erp-ehp
Distribution of values
Range of values
Median: 21,0
(w/o outlier values)
Min: 12,0
0
4
8
12
Max: 36,6
16
20
24 28 32
Weeks
36
40
44
48
52
based on 168 upgrades
Business downtim e* in hours
Benefits
Provides consolidated project data for project
duration, business downtime, reasons for
upgrade, customer satisfaction etc.
Supports project planning by answering most
common questions
SAP R/3 4.6C
Project duration in weeks
Distribution of values
Range of v alues
Median: 48,0
Min: 22,9
0
12
24
Max: 86,2
36
48
Hours
60
72
84
96
1
based on 140 upgrade
© SAP 2010
© SAP AG
ADM326
13-17
Solution Documentation Assistant
Description
Verifies and rates customers’ business process
documentation
Analyzes usage of technical objects like
transactions, reports, BADIs and custom
developments
SQL statement analysis enables live system
analysis from a business perspective
Further Information / Tool Access
SAP Solution Manager Work Center
SAP Service Marketplace at:
http://service.sap.com/solutionmanager
Benefits
Accelerates initial solution documentation
Enhanced solution and usage transparency
Bridging the gap between business and IT with
concise solution documentation
Cost-efficient through automated verification of
solution documentation
Basis for optimized test planning
© SAP 2010
Solution Documentation Assistant verifies and rates customers’ business process documentation.
Data basis is the usage frequency of technical objects related to the business process structure. The
usage frequency gives transparency about potentially obsolete and clarity about mission-critical
objects and is an excellent starting point for initial documentation as well.
Scope
Analysis of template, implementation and maintenance projects
Analyzes usage of technical objects like transactions, reports, BADIs and custom developments
SQL statement analysis enables live system analysis from a business perspective
Uses the existing SAP Solution Manager infrastructure like system connections and technical
statistical data
Benefits
Accelerates initial Solution Documentation
Enhanced solution and usage transparency
Enables simple and fast system consolidation
Facilitates business improvements
Standardization through comparison of business processes at different locations
Basis for optimized test planning
Cost-efficient through automated verification of Solution Documentation
© SAP AG
ADM326
13-18
Business Function Prediction for SAP ERP
Description
SAP now offers a free report: prediction of
relevant SAP enhancement package
functionality based on your existing system
usage, cluding direct access to:
Overview Presentation
Release Notes, Documentation
Test Case Catalogs
Mapping to Technical Usage
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/bfp
Email: ehp-tech@sap.com
Benefits
Tailored access to detailed and structured delta
information for your business
Reduced effort to define a business case or
value proposition for an upgrade
Fast identification of capabilities that respond
to user requirements
© SAP 2010
© SAP AG
ADM326
13-19
Agenda: Technical Upgrade
and Implementation Tools
1. Introduction
2. Planning Tools for Upgrades and SAP Enhancement Packages
3. Technical Upgrade and Implementation Tools
4. Change Management Tools
5. Test Tools
6. Summary and Further Information
© SAP 2010
© SAP AG
ADM326
13-20
Landscape Verification for SAP Solution
Manager
Description
Analyze your landscape data in SAP Solution
Manager System Landscape to safely identify
issues in landscape description
Further Information / Tool Access
Add-on for SAP Solution Manager: Landscape
verification 1.0 for SAP Solution Manager in
Ramp-up since 08/2010
Transaction LVSM
SAP Service Marketplace at:
http://service.sap.com/rampup Technology
Components
Benefits
Helps finding a wide range of errors in the SAP
Solution Manager System Landscape
Provides detailed error description and
information on required correction procedure
Administration based on a correct description of
the landscape will run with less effort, in
shorter time, and better success
© SAP 2010
landscape verification 1.0 for SAP Solution Manager for TechEd session In ALM107 (NOTE that
the add-on is in Ramp-Up still and mark your slides accordingly.)
© SAP AG
ADM326
13-21
Maintenance Optimizer
Description
Central tool for planning, executing, and
managing the installation of SAP enhancement
packages, SAP Support Packages and patches
across the entire SAP landscape
Monitors the complete maintenance procedure
for your entire SAP solution
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/solman-mopz
Solution Manager
- Data maintenance: Transaction SMSY
- Maintenance Optimizer: Transaction DSWP
Benefits
Gain stability and access to innovation
Upgrade only the enhancements applicable
to your business
Reduce risk and downtime
Speed implementation and test less
© SAP 2010
© SAP AG
ADM326
13-22
Application-Specific Upgrade (ASU) Toolbox
Description
Before / after a technical upgrade often additional
application-specific steps need to be
performed ASU collects and summarizes
these activities
Enables you to recognize the necessary steps
and perform them in a controlled manner
Further Information / Tool Access
ASU toolbox is integrated with the upgrade GUI
through the ASU phase in the upgrade process
Benefits
One tool for all kinds of predefined tasks
(reducing the upgrade time)
Making the upgrade more transparent (avoid
mistakes)
Avoiding problems after the upgrade
(message reduction)
© SAP 2010
© SAP AG
ADM326
13-23
SAPup / SAPJup
Description
Standard SAP upgrade tool for ABAP (SAPup)
and Java (SAPJup)
The tools consist of an upgrade program
(SAPup or SAPJup) and a control program
(Upgrade GUI or SDT GUI).
Further Information / Tool Access
Part of the upgrade software kit
More Information is available on SDN:
http://sdn.sap.com/irj/sdn/upgradetech
Benefits
Execution of main upgrade activities
New upgrade GUI layout and simplified
upgrade procedure for ABAP, Java, and dual
stack system upgrades (SAP NetWeaver 7.1)
Established system switch upgrade
technology is also available for Java and dual
stack upgrades (SAP NetWeaver 7.1)
Synchronized upgrade procedure for dual
stack upgrades (SAP NetWeaver 7.0)
© SAP 2010
© SAP AG
ADM326
13-24
Near Zero Downtime for ERP –
Incremental Upgrade & Unicode Conversion
Description
Methodology to significantly reduce business
downtime for Upgrades, Unicode conversions
and SAP enhancement package installations
Consistent system split with the recording of
database changes
Synchronization of the changes between the
main system and the copy – delta replay
Further Information / Tool Access
Available via SAP Minimized Downtime Service
Email: mds@sap.com
Benefits
Significant cost savings due to improved system
availability
Optimization of system validation and sign-off
Re-usability for implementation of SAP Support
Packages, OS patches, DB patches
Late go/no-go decision and very fast reset of the
system additional contingency
First Customers:
Airbus: Successful project – Go-live in Q2/2009
Further customers are currently executing
projects or investigating opportunities
© SAP 2010
© SAP AG
ADM326
13-25
SAP Enhancement Package Installer
Description
Standard SAP enhancement package
installation tool for ABAP and Java
Installs SAP enhancement packages for SAP
Business Suite 7 (and above) application and
for SAP NetWeaver 7.0 (and above)
Execution of main installation activities
Also able to install SAP Support Packages only
Further Information / Tool Access
SAP Software Distribution Center in SAP
Service Marketplace at:
http://service.sap.com/swdc
Benefits
Uses proven technology
New GUI layout and simplified procedure for
ABAP, Java, and dual stack systems
Synchronized installation procedure for dual
stack systems
© SAP 2010
© SAP AG
ADM326
13-26
SAINT / JSPM
Description
Tool for installation of additional SAP
enhancement package components, SAP
Support Packages, and Add-ons
AS ABAP: SAINT
AS Java: JSPM
Further Information / Tool Access
AS ABAP: Transaction SAINT
AS Java: start JSPM from operating system
level
Benefits
Assure consistent deployment of components
by checking prerequisites and installed
software components and SAP Support
Package levels
Easy to use
Platform independent
© SAP 2010
© SAP AG
ADM326
13-27
Agenda: Change
Management Tools
1. Introduction
2. Planning Tools for Upgrades and SAP Enhancement Packages
3. Technical Upgrade and Implementation Tools
4. Change Management Tools
5. Test Tools
6. Summary and Further Information
© SAP 2010
© SAP AG
ADM326
13-28
Business Process Change Analyzer1)
(BPCA)
Description
Business Process Change Analyzer
Identification of mission-critical business
processes impacted by software changes
Planned software changes
SAP Support Packages
Order to Cash
Sales Order code change
SAP Enhancement
Delivery
Packages/ Business
Goods Issue UI change
Functions
Billing
Custom code changes
Procure to Pay
Create PO customizing change
Customizing changes
Test scope optimization based on object
coverage and test effort analysis (with next
SAP Solution Manager release)
Analysis of planned business function activation
Automatic test plan generation
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/solutionmanager
and http://service.sap.com/testing
Benefits
Precise insight of impacted Business Processes
Improved handling of change events
Risk-based test scope recommendation and
automatic test plan generation
1
) Available with SAP Solution Manager 7.0 enhancement package1
© SAP 2010
Verweis: teched session on BPCA (ALM163)
which show cases the new SAP Solution Manager functionality
© SAP AG
ADM326
13-29
Custom Development Management Cockpit1)
(CDMC)
Description
Central management cockpit for custom
developments and respective analysis:
Usage analysis of custom developments
Clearing analysis: Identification of potentially
obsolete objects
Change Impact Analysis: Identification of potential
impacts of an upgrade on custom code
Calculation of the effort necessary for adjusting
custom developments affected by an upgrade
Further Information / Tool Access
Transaction CNV_CDMC or SAP Solution
Manager Work Center
SAP Service Marketplace at:
http://service.sap.com/alm-processes Upgrade
Management
Benefits
Usage transparency of custom developments
Big saving potential by clearing identified
obsolete custom-specific objects
1
) Available with
SAP Solution Manager 7.0
Enhancement Package 1
Accelerated upgrade
© SAP 2010
Verweis: teched session on BPCA (ALM163)
which show cases the new SAP Solution Manager functionality
© SAP AG
ADM326
13-30
Custom Code Library
Description
Central library that provides full transparency
of all custom code objects across systems
Helps to identify candidates for clearing
projects to reduce custom code
Further Information / Tool Access
Planned for next SAP Solution Manager release
SAP Service Marketplace at:
http://service.sap.com/alm-processes
Benefits
Cost reduction by clearing obsolete/ non-used
customer objects
Monitoring and tracking of changes of key
figures for the complete SAP solution
Provides transparency to derive proactive
operations and optimizations projects
SAP Standard
Enhancement w/ interfaces
Enhancement w/o interfaces
Modification assisted
Modification not assisted
Custom with SAP reference
Custom (independent)
© SAP 2010
© SAP AG
ADM326
13-31
SAP CloneFinder1) and Dynamic Usage
Detector
Description
Powerful tool to find clones in a system
landscape (across systems)
Determines the similarity degree of clones
against SAP originals and also inherited clone
versions
Finds dynamic connections between SAP Code
and custom code (Customizing, table entries)
Further Information / Tool Access
Planned for next SAP Solution Manager release
SAP Service Marketplace at:
http://service.sap.com/alm-processes
Benefits
Fast and impressive overview in an easy to use
UI to manage clones
Direct split screen editor feature to merge
clone differences
Enhanced attributes to support the clone
retirement process
1)
Patent pending
© SAP 2010
© SAP AG
ADM326
13-32
Enhanced Change and Transport System
(CTS)
Enhancement of CTS to enable the transport of
non-ABAP objects in the system landscape
Allows to transport non-ABAP objects within
an ABAP transport request
Runtime
Env.
Further Information / Tool Access
Transport Organizer: Transaction SE09
Transport Management System: Transaction
STMS
SAP NetWeaver
EP
PI Development
Developer StudioContent Studio
environment
Dev. &
Transport
Environment
Dev.
Tools
Description
NWDI
(AS Java)
(Non-ABAP)
Java
Java
DEV
TEST/PRD
Java
Java
CONS
PROD
CTS
EP
DEV
EP
PROD
XI
XI
DEV/QA/PRD
QAS XI
PROD
ABAP
Workbench
(ABAP)
ABAP
ABAP
DEV/QA/PRD
ABAP
QA
PROD
Benefits
Solves transport issues by combining and
synchronizing transports in a comprehensive
approach
Allows to use the standard transport
management transactions to centrally transport
all objects, of ABAP and non-ABAP systems
Integrated into standard CMS transactions
© SAP 2010
The enhanced CTS functions are available as of Support Package Stack (SP Stack) 12 of SAP
NetWeaver 7.0. As there are further enhancements with SP Stack 14 however, the use of SP stack 14
or higher is recommended for transporting non-ABAP objects with the help of CTS.
© SAP AG
ADM326
13-33
Change Request Management1) with
SAP Solution Manager (ChaRM)
Description
Ensures that standard methods and
procedures are used for efficient handling of all
changes
Manages maintenance and implementations
spanning multiple components
Further Information / Tool Access
SAP Solution Manager, Change Management
work center
SAP Service Marketplace at:
http://service.sap.com/alm-processes Change
Control Management
Benefits
Minimizes impact of change-related incidents
Improves day-to-day operations
Changes are administered, tested and
transported within the system landscape
Workflow driven
Project definition, control and change tracking
Access to all involved systems
1)
Available with
SAP Solution Manager 7.0
enhancement package1
© SAP 2010
© SAP AG
ADM326
13-34
Enhancement and Switch Framework: Enable
Optional Activation of Business Functions
Description
The Enhancement Framework brings all
enhancement techniques under one roof
The Switch Framework controls the activation of
business functions
Activating a business function triggers switches,
which then ‘influence’ the execution of
program code, fields of tables etc.
Switch Framework is used to:
Retrofit industry solutions in SAP ECC 6.0
Switch the business function sets within SAP
enhancement packages
Further Information / Tool Access
Switch Framework
Switch Framework: Transaction SFW5
Benefits
Creation of enhancements avoids modifications
and helps to save cost and effort
Enhancements are very flexible and can be
switched via the Switch Framework
SAP ERP
(ECC 6.04)
© SAP 2010
Available with SAP NetWeaver 7.0
© SAP AG
ADM326
13-35
Modification Adjustment Tools
SPDD / SPAU / SPAU_ENH
Description
Tools for performing modification adjustment
and maintaining enhancements during upgrade
and SAP enhancement package installation
Further Information / Tool Access
Transaction SPDD for dictionary repository
objects
Transaction SPAU for other repository objects
Transaction SAPU_ENH for enhancements
Benefits
Automatic or semi-automatic adjustment
possible (depending on modification)
SPDD adjustments possible during productive
operation
Compare old and new versions
Reset to original if modification is not needed
any longer
Resulting transport requests can be integrated
into subsequent SAP enhancement package
installations / upgrades
© SAP 2010
© SAP AG
ADM326
13-36
SAP Landscape Transformation1) (SAP LT)
Including Client Transfer with Upgrade
Description
Cost-efficient realization of IT and/or businessdriven system landscape transformation
Available transformation solutions:
Client Transfer (may include Upgrade,
Unicode conversion, and OS/DB change
Chart of Accounts Conversion
Company Carve-Out
Further Information / Tool Access
Add-on for SAP Solution Manager 7.0 (SP15),
available since 07/2010 in Ramp-up
Transaction LTS (SAP LT Work Center)
SAP Service Marketplace at:
http://service.sap.com/saplt
Benefits
Increased agility of SAP solutions
Cost-efficient and risk-minimized project
execution through roadmaps and highly
automated transformation solutions
Client Transfer: Accelerated upgrade in
combination with system consolidation leads to
lower system complexity and reduced TCO
1)
Additional license required
© SAP 2010
© SAP AG
ADM326
13-37
Agenda: Test Tools
1. Introduction
2. Planning Tools for Upgrades and SAP Enhancement Packages
3. Technical Upgrade and Implementation Tools
4. Change Management Tools
5. Test Tools
6. Summary and Further Information
© SAP 2010
© SAP AG
ADM326
13-38
SAP Test Management Options for SAP Customers
based on SAP Solution Manager 7.0
Type of Change
New SAP
Solution
Test Scope Identification
Business Blueprint
Test Planning
Test System Setup
SAP Solution
Update
Test Option 1
Change
Deployment
Test Execution
Change Impact Analysis
Test Planning
Test Scope Identification
Manual Tests
Automated Tests
UI + Backend Tests
eCATT
SAP Solution Manager
Business Blueprint
SAP Solution Manager
Test Workbench
SAP Solution Manager
Business Process
Change Analyzer1
SAP TDMS2
SAP Solution Manager
SAP TDMS2
SAP Solution Manager
Test
Workbench
SAP Solution Manager
eCATT
UI based Tests
HP QTP2
MicroFocus2
Worksoft2
IBM Rational2
Test Option 2
Business Blueprint
SAP Quality Center by HP
SAP Solution Manager
SAP Quality Center by HP + QTP
Business Process
Change Analyzer1
SAP TAO2
Note: Further test options are currently in planning see ALM115: Overview Test Management
© SAP 2010
© SAP AG
1)
Available with SAP Solution Manager 7.0 enhancement package1
ADM326
2)
Additional license required
13-39
SAP Test Data Migration Server1)
(SAP TDMS)
Description
Create small, easy-to-use test environments
with consistent, relevant extracts of business
data from production systems
Refresh test data without affecting repository
and administrative data
SAP TDMS
Quickly transfer pre-defined business objects
or business process data to test systems
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/tdms
Benefits
Test systems contain up-to-date test data for
more accurate test results
Improved quality of software developments
Minimized infrastructure and maintenance
expenses
Scrambling of sensitive data is possible
1)
Additional license required
© SAP 2010
© SAP AG
ADM326
13-40
Extended Computer Aided Test Tool
(eCATT)
Description
Test automation for nearly all transactions and
business process across all SAP solutions that
run in SAP GUI
Creation of modular tests that can be used as
single-function tests and combined with other
modules to represent entire business
processes and document test activities
Further Information / Tool Access
Transaction SCAT (CATT), SECATT (eCATT)
SAP Service Marketplace at:
http://service.sap.com/testing
Benefits
Largely reduced costs and efforts by using
repeatable, automated tests of individual
transactions and whole business processes
Enables test execution in distributed system
landscapes
Integrated with Test Workbench and partner
tools for seamless test management
© SAP 2010
© SAP AG
ADM326
13-41
Test Workbench
Description
Management of functional tests from test
planning via test execution to test status
reporting and test sign-off including:
Planning of manual & automated test cases
Links business processes and test cases
Test status reporting for test coordinators and
trend reports through integrated SAP BI
reports
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/testing
Benefits
Comprehensive and mature functionality for
E2E Test Management
1-click access from test management to test
systems
Test sign-off including digital signatures
Integration w/ external tools, e.g. SAP QC by HP
© SAP 2010
© SAP AG
ADM326
13-42
Test Case Templates for SAP Enhancement
Packages for SAP ERP
Description
Predefined test case templates are available
for new business functions that are shipped
with SAP enhancement packages for SAP ERP
Test case templates can be used in test
workbench and are based on the scope of an
acceptance test to verify if the new
functionality
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/erp-ehp
Via transaction SFW5 after SAP enhancement
package installation
Benefits
Can be adjusted to customer specific test
cases
Time and cost savings due to faster test
planning based on templates
Simplification of test preparation and execution
© SAP 2010
© SAP AG
ADM326
13-43
SAP Test Accelerator and Optimizer1)
(SAP TAO)
Description
Automation of business process testing by
composition of automated test cases
Automatic generation of test components for
SAPGUI-based SAP business processes
Fast composition of automated test cases
using standard functionality of SAP TAO and
Quality Center
Optimized maintenance of automated test
cases via component-based exchange of
damaged test components after SAP updates
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/saptao
Benefits
Accelerated approach to create modularized
test cases for SAP business processes
Optimized way to maintain test cases leading to
lower TCO
Integrated with Quality Center and SAP
Solution Manager
1)
© SAP 2010
© SAP AG
ADM326
Additional license required
13-44
SAP Quality Center by HP1)
Description
Requirements module
Definition of test requirements for business processes
Test plan module
Test planning and definition of test cases
Test lab and defect module
Test execution and defect management
QuickTest Professional
Test automation for SAP and non-SAP applications
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/testing
Benefits
Manage test strategies and processes based on
business risk
Enable centralized management of manual and
automated test assets
Ensure all business critical requirements are
planned for testing
Significant reduction in post go-live defects
1)
© SAP 2010
© SAP AG
ADM326
Additional license required
13-45
SAP LoadRunner by HP1)
and SAP LoadRunner Enterprise Edition by HP1)
Description
Supports load tests in an SAP context for the
following user interfaces: SAP GUI, Web
Dynpro, http(s), and e-mail protocols
Replaces real users with thousands of “virtual”
users
Emulates production workload on SAP
landscapes
Further Information / Tool Access
SAP Service Marketplace at:
http://service.sap.com/testing
Benefits
Ease of use reduces the learning curve and
script development time
Breadth of environment support helps assure
that all enterprise applications are covered
Reduce support costs, application response
times and time to resolve problems
1)
© SAP 2010
© SAP AG
ADM326
Additional license required
13-46
Agenda: Summary and
Further Information
1. Introduction
2. Planning Tools for Upgrades and SAP Enhancement Packages
3. Technical Upgrade and Implementation Tools
4. Change Management Tools
5. Test Tools
6. Summary and Further Information
© SAP 2010
© SAP AG
ADM326
13-47
Information:
SAP Service Marketplace – Upgrade Information
SAP Upgrade Info Center
Upgrade-specific
Information for
SAP ERP
(http://service.sap.com/upgrade)
SAP Upgrade
Newsletter
SAP Solution
Manager
SAP Upgrade Tools Portfolio:
http://service.sap.com/upgradetools
Enhancement
Package Info
Center
© SAP 2010
© SAP AG
ADM326
13-48
Upgrade Services – Focus on Customer
Decision Making
Plan
Global
Connected
End-to-end
processes
Run
Project planning
Project
exec.
Optimization
First estimation
for budgeting
Detailed project
plan – Technical
Upgrade
On-time,
On-budget
Upgrade
End-to-End
solution
operation
Quick Upgrade
Analysis (QUA)
First value
estimation
Solution Browser
Tech. Upgrade
Planning (QUE)
Detailed value
proposition
Upgrade Value
Assessment
Customers Decision Point
Build
Budget planning
Customers Decision Point
Focused
Business
Technical
Customer Demand
Technical
Upgrade
Secure
business
value
Competitive
differentiation
MaxAttention / Enterprise Support /
Safeguarding for Upgrade / Upgrade Value Coaching / Upgrade Coaching
Related Services
Unicode Conversion / Test Management and Optimization / Test Data Migration Service
© SAP 2010
© SAP AG
ADM326
13-49
SAP Global Upgrade Services Portfolio
Upgrade Services
Plan
Build
Run
Enablement
Provide direction and Quick upgrade analysis for SAP ERP
qualification
Quick upgrade analysis for SAP CRM
Technical upgrade planning for SAP Business
Suite
Expert Guidance
Technical upgrade planning for SAP ERP
Provide detailed
Upgrade and migration assessment for SAP CRM
advice to key
Technical upgrade planning for SAP NetWeaver BW
questions or
challenges
Upgrade value assessment
Upgrade training
Technical upgrade for SAP ERP
Technical upgrade for SAP CRM
Solution Delivery
Provide solution or
knowledge transfer
Quality
Management Audit
and provide
directions
Solution migration for SAP CRM
Technical upgrade implementation for SAP
NetWeaver BW
Upgrade coaching for SAP ERP
SAP Safeguarding for Upgrade
© SAP 2010
© SAP AG
ADM326
13-50
SAP Global Upgrade Services Portfolio
Upgrade-Related Services
Plan
Build
Run
Enablement
Provide direction and SAP enhancement package planning for SAP ERP
qualification
Expert Guidance
Provide detailed
advice to key
questions or
challenges
Test tool strategy workshop
Unicode conversion
Solution Delivery
Provide solution or
knowledge transfer
Test management and optimization
Test data migration services
You can find more SAP ERP services in the Global Consulting Service Portfolio for SAP ERP.
© SAP 2010
© SAP AG
ADM326
13-51
© SAP AG
ADM326
13-52
Agenda: SAP Notes for this Course
1.
2.
3.
4.
5.
6.
7.
Concept and Architecture
Sequence and Major Steps
Selecting the Target Release
Modification Adjustment
Technical Phases
Troubleshooting
Incremental Conversion
8.
9.
10.
11.
12.
13.
14.
Support Packages and Add-Ons
Downtime
Planning and Preparation
Enhancement Packages
Unicode Conversion
Tools and Services
SAP Notes for this Course
© SAP 2010
© SAP AG
ADM326
14-1
SAP Note No. 156387
________________________________________________________________________
Number
156387
Version
35 from 12.06.2008
Status
Released for Customer
Set on
12.06.2008
Language
EN
Master language
DE
Short text
References to upgrade notes regarding HR
Responsible
SAP
Component
PA
Personnel Management
________________________________________________________________________
Long text
Symptom
***********************************************************************
This note is a composite note concerning the HR upgrade. It contains
references to further notes on the upgrade to Releases 5.0 and 6.0.
***********************************************************************
This note is constantly updated. Therefore, we recommend that you check
the note regularly to see whether any new notes have been added that may
be useful for your system. This note lists the most important notes, but
not all the notes relevant to this subject. Some of the notes specified
may have been archived since this note was created and others may have
been changed. The status of the relevant note applies.
Note the release level for which the notes apply. The notes are listed
under the target release for an upgrade.
In addition, you should also consult notes the subject areas BC-UPG-RDM
and BC-UPG-ADDON, since these contain notes about the upgrade that may
be of interest for HR.
Other terms
Reason and Prerequisites
Solution
© SAP AG
ADM326
14-2
Content:
0/ General information/ Points to consider
I/ Upgrade to ERP 2004 (ECC 5.0)
I/ Upgrade to ERP 6.0 (ECC 6.0)
© SAP AG
ADM326
14-3
0/ General information/ Points to consider
I/ Upgrade to ERP2004 (ECC 5.0)
310852 PA-PA Performance improvement with upgrade and service packages
317722 PA-BC Upgrade information for table T77S0
353861 PA-BC HR: Upgrade to 4.6C (or higher)
374172 PY-CA Q&A: Master Note for Conversions/Upgrades - Canada
546167 PA-PA Termination in PA10: Infotype 0122 does not exist
549368 PA-PA-KR HR-KR+CN: Retrofitting HR-KR+CN to R/3 standard SAP_HR
Page 2
560272 PA-RC Unicode: Conversion of standard texts
573044 PA Unicode conversion for HR application
679275 PY-XX-BS T52C5: Report for Unicode conversion
728730 PY-XX-DT Short dump in PCP0 after upgrade fr 4.6c to a higher
release
731747 PY-XX-DT HR upgrade to 4.7 Enterprise or higher: user exit
migration
734068 Upgrade to SAP ECC 500 w/ Campus Management deinstallation
737902 PA-PA-FR HCM-FR: Social Security number in infotype 0002
763880 PY-XX-BS Upgrade and customer-specific enhancement of PC2*
structures
775435 PA-BC PM01: Missing TADIR entries of %_Includes
796825 PY-XX-IT PU12: Performance issue for PU12-conversion
829174 PA Contents & applying HRSP ERP5.00/Ext.Set5.00
871937 PA-PA-XX Unicode conversion: Language for object 'CP'
875811 PY-XX-TL RPUOCB00 only displays one personnel number
910573 Container-Migration: Structures with incompatible changes
925390 PY-NL Loonaangifte does not find payroll result after upgrade
950493 PY-AT RPCL16A*, RPCBGNA*, RPCE18A*: Announcement of end of
maintenance
962287 PY-CA CONV: RPC224K0 displays duplicate messages in output log
963753 PY-AU Change in Area Menu for Payment Summary
970556 CA-TS-SV IF_EX_CATSXT_EVENT->ON_MYLIST_SELECTED
980275 PY-CA CONV: RPC224K0 generates one IT0462 record instead of two
982769 PY-FR RPLAASF1: date of payment not shown after upgrade
997275 PY-ES Payroll results of cluster RE inconsistent after upgrade
1001192 PY-DE-PS Operation VARAB: Parameter PSS fehlt nach Upgrade
(German only)
1005516 PY-PCM Upgrade with PYCM 100_*
1013796 PA-PA Table T5ESAIT_SCREEN valid only in ERP04 (ECC500)
© SAP AG
ADM326
14-4
1032298 PY-US-TP GEN: HR3PRNA 019 - No payee text found in RPURMR00
report
1034603 PY-XX-TL H99UCDP0: Entries with 0 value created in BALHDR
1106904 HR-IT: Overview of released notes
1113536 PY-BE: Text for processing class 61 option 0 is different
1116583 PA-PA-BE: Overview screen 3000 of infotype 0100 has other
descriptions
1136159 PA-PM Commitment processor: Parameter T77SO/CHKOI is ignored
1169004 PY-BE Payroll function BLIT - Parameter 3 value missing
© SAP AG
ADM326
14-5
II/ Upgrade to ERP 6.0 and above (ECC 6.0 and above)
317722 PA-BC Upgrade information for table T77S0
374172 PY-CA Q&A: Master Note for Conversions/Upgrades - Canada
560272 PA-RC Unicode: Conversion of standard texts
573044 PA Unicode conversion for HR application
679275 PY-XX-BS T52C5: Report for Unicode conversion
871937 PA-PA-XX Unicode conversion: Language for object 'CP'
948937 PY-XX ERP2005: Syntax Error in Payroll in ERP2005 after
SAPKH60001
976001 PA-PA-RU 'Payroll Russia' SAP Menu item is missing in ERP2005
________________________________________________________________________
Valid releases
Software Component
Release
from
to
SAP_HR
R/3 Standard Human Resource
500
- 605
X
Further components
PY
Payroll
BC-UPG
Upgrade - general
PA-PA
Personnel Administration
________________________________________________________________________
Note attributes
Transaction codes HIER
PPOM
Transaction codes PU12
XPRA
________________________________________________________________________
Reference to related Notes
________________________________________________________________________
© SAP AG
ADM326
14-6
SAP Note No. 317722
________________________________________________________________________
Number
317722
Version
7 vom 20.02.2003
Status
Released for Customer
Set on
21.02.2003
Language
EN
Mastersprache
DE
Short text
Upgrade information for table T77S0
Responsible
SAP
Component
PA-BC
Basis
________________________________________________________________________
Long text
Symptom
A number of entries in table T77S0 delivered in the standard system
are incorrect. These include:
PLOGI ORGA
TRSP CORR
PLOGI EVENB
...
After upgrade, it is possible that the system response changed in many
instances in HR. For example, after the upgrade the automatic transport
connection is always active. For example, the automatic transport link is
always active after the upgrade.
Other terms
Upgrade
Reason and Prerequisites
The error occurs during an upgrade from a release <= 4.6C to a Release
> 4.6C.
Solution
Attached to this note you fin a transport request containing the
required programs RH77S0BU and RH77S0RE.
Start the report RH77S0BU before the upgrade. This report saves the T77SO
entries in all clients in table INDX.
Copy report RH77S0RE to your customer name range so that you still have
© SAP AG
ADM326
14-7
the report after the upgrade. It is important that you also copy the
status of the report. After the upgrade you can run the copied report
per client.The report provides a list of entries that are different and
can restore the old status where necessary.The problem only concerns
entries that were changed by the customer in a former release. No new
flags should be deleted.
________________________________________________________________________
Note is not release-specific
________________________________________________________________________
References to related notes
Number Short text
____________________________________________________________
748338 Upgrade LSO (Table LSO_CUSTOMIZE_C)
505820
Backup of Table entries in T77S0 for CM Upgrade
373038 Organizational Management: data missing after upgrade
353861 HR: Upgrade to 4.6C (or higher)
________________________________________________________________________
© SAP AG
ADM326
14-8
SAP Note No. 817463
________________________________________________________________________
Number
817463
Version
75 from 17.11.2010
Status
Released for Customer
Set on
17.11.2010
Language
EN
Master language
DE
Short text
Addtnl info for upgrade to SAP NetWeaver 7.0 ABAP:
MaxDB
Responsible
SAP
Component
BC-UPG-RDM
README: Upgrade Supplements
________________________________________________________________________
Long text
Symptom
There are problems with the guide or the upgrade procedure.
Other terms
Reason and Prerequisites
Solution
************************************************************************
This note contains only problems that are specific to MaxDB.
************************************************************************
Topics:
I/
Important general information
II/ Errors in the guide
III/ Activities prior to the upgrade
IV/ Problems during individual phases
V/ Activities after the upgrade
VI/ Documentation
© SAP AG
ADM326
14-9
************************************************************************
I/ Important general information
************************************************************************
1. !!! Caution:
Note the following during ERP 2005 upgrades with the following
conditions:
Source system:
46C
Operating system: Linux X86_64 (AMD64)
Under certain circumstances, TADIR entries are incorrectly copied
during the SAP upgrade and the SAP upgrade does not notice this.
This has the following consequences:
1. After the upgrade, customer objects can no longer be edited.
2. Problems occur during the XPRAS_UPG phase because objects without
a TADIR entry were edited.
3. Problems occur during the ACT_UPG phase because objects had no
TADIR entry.
This faulty copy operation appears to be caused by a database error
in MaxDB Version 7.6.
Unfortunately, we have not managed to reproduce the error internally
at SAP using the relevant DB trace, in the same way as it has been
reproduced externally.
If you carry out an ERP 2005 upgrade subject to the conditions
mentioned above, you must implement the workaround described below:
1. After the PREPARE and before you start the actual upgrade, create
a file called R3UPPHAS.BRK in the /usr/sap/put/bin directory with
the following content line:
RUN_RDDCP4TB
2. Then start the actual upgrade, which is then halted _before_ the
RUN_RDDCP4TB phase. This is still in the uptime.
3. You can now execute the RDDCP4TB report, which must be executed
in the phase, online in transaction SE38.
When calling RDDCP4TB, you must specify two parameters:
Enter the TADIR~ value for NEWTADI.
© SAP AG
ADM326
14-10
Enter the TADIR value for OLDTADI.
The system then issues 5 lines of numbers in the log. The sum of
these numbers (sum of the lines Saved, Updated, Deleted, Invalid and
Original) must match the number of entries in the original TADIR. If
this is the case, the copy procedure was successful. To display the
number of entries in the original TADIR, choose
transaction SE16 -> TADIR number of entries.
© SAP AG
ADM326
14-11
4. If the RDDCP4TB report, which is executed manually, returns the
correct result, you can continue with the upgrade.
If the report returns results that do not match the number of
entries in the original TADIR, proceed as follows:
a) If this is a time-critical upgrade, execute the report manually
again once or several times, if necessary.
After the report has run and returned the correct result, you can
continue with the upgrade.
If you are unable to obtain the correct result when you run the
report, contact SAP Support.
b) If this is a test upgrade or a non-time-critical upgrade, notify
SAP Support and provide them with access to your system (component
BC-DB-DB as specified in Note 826037). They will then investigate
the report directly using the relevant database tracing (SQL trace
ST05 and precompiler trace) in an effort to identify the actual
cause of the error.
2. SAPup patches
You can check the SAPup version using the following command:
SAPup -V
Version Patch Level Remark
700-1
23.059
Correction for phase INDQUE_CHK:
Check inactive when using DCK kernel
!!! You may not use patch level 24.071 - 24.074 since, otherwise, an
error occurs in phase VIEWCHK that can only be corrected by a later
patch level as of 24.075 or higher.
SAPup patches are available on SAP Service Marketplace.
Note 663258 provides the information required for the download.
3. R/3 extended kernel in the source release
Make sure that the minimum Precompiler Runtime version, which is
required for the R/3 Extended Kernel in Note 789086,
is imported in the system. Now use transaction SM50 to check, for
example,
the trace file of a work process:
© SAP AG
ADM326
14-12
> Select process > Display Trace.
The trace log names the Precompiler Runtime Version:
> C Precompiler Runtime : C-PreComp 7.3.1
Build 018 ...
4. For the SCM 5.0 upgrade, a maximum three R3trans processes should be
selected, otherwise the phase termination described in section IV
can occur in phase SHADOW_IMPORT_UPG2.
© SAP AG
ADM326
14-13
5. For SCM upgrades with database instances of type "liveCache OneDB",
proceed in accordance with Note 1248891.
6. Before you start the PREPARE, check the value of the profile
parameter
dbs/ada/schema, if "sapSID" is in lower case, it must
be changed to upper case ("SAPSID").
7. To avoid the error described in section IV on Windows AMD64 in the
PREPARE phase UVERS, you should replace the tools in the directory
<DIR_PUT>/tools immediately after they were unpacked by the PREPARE
phase with 46D tool versions, for more details see section IV.
8. To avoid the problems in upgrade phase "SCEXEC_ALIAS" listed in
Section IV, select the default password "sap" for the ABAP database
shadow user in the PREPARE phase "Installation".
9. To avoid the problems mentioned in Note 37291, use at least version
7.6.01.12 or higher for SAP upgrades with MaxDB Version 7.6.
Otherwise, database terminations with the following error may occur
during the SAP upgrade:
SYSERROR -9400 AK Cachedirectory full
10. For SCM 5.1 upgrades, you require liveCache Version 7.7.02.15 or
higher for One-DB systems (liveCache and SCM schema in a database).
11. If you have to reset the SAP upgrade during the EU_IMPORT phases,
you must delete the entries of the table "/MAXDB/INDEXSTATEMENTS".
In this case, see Note 1529347.
************************************************************************
II/ Errors in the guide
************************************************************************
© SAP AG
ADM326
14-14
************************************************************************
III/ Activities prior to the upgrade
************************************************************************
OS : UNIX/Linux
With SAP Kernel 640_EX2 or higher, the new MaxDB DBSL (dbsdbslib) and,
therefore, disp+work use the SQLDBC interface (libSQLDBC) of the MAXDB
client installation. To ensure that the MaxDB DBSL can find and load the
libSQLDBC, the relevant system variables that are dependent on the
operating system must be set. For all precompiler-based SAP applications
(upgrade of source release) with an SAP kernel lower than Kernel
640_EX2, the .dbenv scripts must therefore be updated in the home
directory of sidadm on all application servers.
Otherwise, terminations will occur when executing tools of the upgrade
SAP kernel under <UPGDIR>/abap/exe. In the developer trace, the problem
will be displayed as follows:
M calling db_connect ...
B create_con (con_name=R/3)
B Loading DB library '<path>/dbsdbslib.so' ...
M *** ERROR => DlLoadLib: dlopen()= libSQLDBC76.so: cannot open shared
object file: No such file or directory -> DLENOACCESS (0,Success)
B *** ERROR => Couldn't load library '<path>/dbsdbslib.so'
As sidadm user, unpack the DBENV.SAR package that is available in Note
1066891 into a temporary directory using the following command:
SAPCAR -xvf DBENV.SAR
Copy the files DBENV.CSH and DBENV.SH into the home directory of the
sidadm user and overwrite the .dbenv files contained in that directory:
cp DBENV.CSH /<homedirectory>/.dbenv_<hostname>.csh
cp DBENV.SH /<homedirectory>/.dbenv_<hostname>.sh
If you perform the upgrade with MaxDB 7.6.00.09, check the database
parameter MAX_SPECIALTASK_STACK before the start of the PREPARE. If
MAX_SPECIALTASK_STACK is lower than 200, set the parameter to 200. As of
MaxDB 7.6.0.10, you do not need to change this database parameter.
If you carry out the upgrade with a MaxDB version lower than 7.6.00.15,
the OPTIMIZE_OPERATOR_JOIN parameter must be set to NO, otherwise the
Signal 11 error (knldiag) can occur during the upgrade:
DBSTATE Caught signal 11(SIGSEGV)
COREHAND ABORTING due to signal 11
(SAP internal information: PTS 1137641)
If you upgrade from Release 4.5B or lower with MaxDB 7.6.00.14 or a
© SAP AG
ADM326
14-15
lower build, check the _PACKET_SIZE database parameter before the start
of the PREPARE. If _PACKET_SIZE is larger than 36864, set this parameter
to 36864 before starting the PREPARE. Otherwise, the PREPARE will
terminate because R3trans cannot connect to the database. After the
upgrade, you should set the database parameter to the maximum value
131072.
© SAP AG
ADM326
14-16
If you perform the upgrade from Release 4.6D with MaxDB 7.6.00.14 or a
lower build, check the _PACKET_SIZE database parameter before the start
of the PREPARE. If _PACKET_SIZE is larger than 126125, set this
parameter to 126125 before starting the PREPARE. Otherwise, the PREPARE
will terminate because R3trans cannot connect to the database. After the
upgrade, you should set the database parameter to the maximum value
131072.
************************************************************************
IV/ Problems during individual phases
************************************************************************
Phase: UPGRADE general
OS : any
If you use a MaxDB version that is lower than 7.6.01.12, the database
may terminate with the following log entry:
SYSERROR -9400 AK Cachedirectory full
In this case, restart the database and continue the SAP upgrade process.
For this reason, further database terminations may occur during the SAP
upgrade. In this case, proceed in the same way.
For information about how you can solve this problem, see section I.
Phase: PREPARE
OS : LinuxIA64 and LinuxPPC
The database connection closes and the log file
records signal 11 (SIGSEGV). Database parameter USE_COROUTINES
is set to the default value YES. The necessary procedure is described in
Note 851105.
Phase: READDATA_UPGTOOLS (PREPARE)
When the PREPARE is repeated, this phase may be terminated, and the file
<PUT_DIR>/log/CAR.SAV may issue the following error:
dbadashoplib.dll (error 28). The process cannot access the file
because it is being used by another process.
Or:
SAPCAR: could not open for writing
<UPGDIR>/abap/bin/dbadashoplib.<extension> (error 28). Text file busy
Workaround 1:
Choose first "Cancel" and then "Stop Upgrade" from the menu of the
Upgrade Assistant, then restart the Upgrade Assistant and choose
"Repeat" to continue with the upgrade process.
Workaround 2:
© SAP AG
ADM326
14-17
Rename the file <UPGDIR>/abap/bin/dbadashoplib.<extension> and use
"Repeat" to repeat the phase.
© SAP AG
ADM326
14-18
Phase: DBCHK_PRE (PREPARE)
OS : Unix
Source release: 31I
A phase termination occurs and a SharedLibrary path is specified in the
<DIR_PUT>/log/DBSDBDLL.LOG file, which references a dependant
directory of the database software: /sapdb/<SID>/db/...
Enhance the SharedLibrary path variable
SUN, DEC, SNI: LD_LIBRARY_PATH
HP
: SHLIB_PATH
AIX: LIBPATH
in the environment of the <sid>adm user by adding the correct path to
the libSQLDBC76 library:
/sapdb/programs/lib[/lib64]
AND
the path specified in file DBSDBDLL.LOG.
Then repeat the phase.
Phase: INITPUT_PRE (PREPARE)
DB: 7.3.00
Phase INITPUT_PRE hangs because the "xuser -& c list" command executed
from SAPup does not work on DB Version 7.3.00.
Carry out the DB version change on Version 7.6.00 required for the
PREPARE, and repeat the phase.
Phase: START_SHDI_FIRST
OS : Unix
When you start the shadow instance manually on the remote host, the
connection to the database does not work if the settings for the
<sid>adm user environment are not correct. The problem is that the
program cannot find the library libSQLDBC. Check if the libSQLDBC
library is available in either of the /sapdb/programs/lib or
/sapdb/programs/lib/lib64 directories, and add this directory to the
SHLIB_PATH (HP-UX), LIBPATH (AIX) or LD_LIBRARY_PATH for the <sid>adm
user.
Phase: SHADOW_IMPORT_UPG2
A phase termination may occur with the SQL error "-60".
Repeat the phase in this case.
© SAP AG
ADM326
14-19
Phase: SHADOW_IMPORT_UPG2
A phase termination may occur and you see the following SQL error in the
log files of the upgrade:
SQL error "-1000" Too many lock requests
To avoid the problem, you have the following options:
1) Increase the MAXLOCKS database parameter (recommended)
Increase the MAXLOCKS database parameter based on the number of R3trans
selected. To do this, you should apply the following rule of thumb:
R3trans number * 150,000 = MAXLOCKS value
(however, at least 800,000)
Note that parameter changes only become active when you restart the
database.
2) Reduce the R3trans parallelism
To do this, call SAPup as described below:
"SAPup set std"
You can use this call to change the upgrade parameters specified in the
PREPARE In this case, choose an R3trans process number of 3. To activate
the change, you must then repeat the phase using the "Init" option.
Phase RUN_RSPTBFIL_DEST
Failure to comply with point I.6 in this note can lead to the following
error:
R3up>
BATCH JOB RSPTBFIL FAILED
Replace all incidences of sap<SID> with SAP<SID> in the entries of the
startsap and stopsap scripts in the
<PUTDIR>/<SID>/homeshd/<SID> directory:
You must restart the shadow instance for the changes to become active:
<PUTDIR>/<SID>/homeshd/<SID>/stopsap r3
<PUTDIR>/<SID>/homeshd/<SID>/startsap r3
Phase SCEXEC_ALIAS
The phase terminates with the following error:
ERROR: no logfile list SQLEXEAL.LOG
The SCEXEC_A.EC0 log file contains the following entry:
TRACE-INFO: 49: [dbsdbsql ,00000]
*** ERROR => Connect to database
rc = -4008 (POS(1) Unknown user name/password combination)
This error is due to the fact that SAPup created the SAP<SID>SHD user
with a default password instead of the password chosen in the PREPARE.
Use the following statement to change the password to the password
chosen in the PREPARE:
1) dbmcli -d <DBSID> -u control,<control password>
-uSQL superdba,<superdba password>
© SAP AG
ADM326
14-20
2) sql_execute alter password SAP<SID>SHD <new password>
You can then repeat the SCEXEC_ALIAS phase and continue with the
upgrade.
© SAP AG
ADM326
14-21
Phase: KX_SWITCH_2
OS : Windows
System
: SCM
For systems with liveCache on the central instance, the phase
KX_SWITCH_2 terminates because the liveCache is using a file of the SAP
kernel, which cannot be used as a consequence:
SEVERE ERROR: Could not delete file '<path>icudt30.dll' in
Reason: 'ErrorMessage: Access is denied.
Shut down the liveCache, continue the SAP upgrade and restart the
liveCache immediately after phase KX_SWITCH_2. (SAP internal
information PTS 1149478)
Phase: START_SHDI_FIRST
This phase terminates and in the dev traces of the shadow system
<DIR_PUT>/<SAPSID>/...
the following entries are displayed:
ERROR => the connected dbid (<DBSID>) is not the right database id
[dbslsdb.cpp 4652]
ERROR => application has to connect to rsdb/dbid=<SAPSID>
(<SAPSID> does not equal <DBSID>)
To the instance profile of the shadow system
<DIR_PUT>/<SAPSID>/SYS/profile/<SAPSID>_DVEBMGS<nr>_<host>
add, the following line:
rsdb/dbid = <DBSID>
Then stop the shadow system.
<DIR_PUT>/bin/SAPup stopshd
Then repeat the upgrade phase.
Phase: INDQUE_CHK
The phase terminates and the following trouble ticket exists:
SAPup broke during phase INDQUE_CHK in module MAIN_SHDCRE
/ Import and Modification Transfer
Error Message : Index creation during database load is inconsistent,
please search section IV of note 817463 for 'INDQUE_CHK'
Check whether the problem described in Note 1428985 exists.
Phase: EU_IMPORT
ERROR: Execute for create index <INDEXNAME> on <TABNAME> failed
(dbrc=103) (SQL error -942)
See Note 1529347.
© SAP AG
ADM326
14-22
************************************************************************
V/ Activities after the upgrade
************************************************************************
If you set the OPTIMIZE_OPERATOR_JOIN parameter to NO before the upgrade
for MaxDB Versions lower than 7.6.00.15, you should now reactivate this
parameter.
Schema user SAPR3SHD or SAP<SID>SHD
In the database, the upgrade created the schema user SAPR3SHD or
SAP<SID>SHD for the shadow system. This schema is not deleted at the end
of the upgrade. It can be kept for a follow-up upgrade. Alternatively,
you can delete it using database tools.
As a result of delivery errors, this schema may still contain database
objects
(synonyms). You can also delete these.
************************************************************************
VI/ Documentation
************************************************************************
************************************************************************
________________________________________________________________________
Valid releases
Software Component
Release
from
to
700
- 702
SAP_BASIS
SAP Basis component
© SAP AG
ADM326
14-23
________________________________________________________________________
Reference to related Notes
Number
Short text
____________________________________________________________
1529347 Upgrade: R3load Error "Unknown Table Name"
1481369 Release of MaxDB Version 7.8 for older SAP versions
1293745 Add. info.: Upgrade to SAP NetWeaver 7.0 EHP 1 SR1 (ABAP)
1293744 Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP1 SR1
1293387 Add. Info. on Upgrading to SAP SRM Server 7.0 SR1 ABAP
1292071 Add. info. on upgrading to SAP SCM 7.0 SR1 ABAP
1292070 Add. info. on upgrading to SAP CRM 7.0 SR1 ABAP
1292069 Add. info. on upgrading to SAP ERP 6.0 EHP4 SR1 ABAP
1289161 Consulting note: Procedure for upgrading SAP F&R 5.0 to 5.1
1276895 Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1
1248891 SAP SCM upgrade to liveCache OneDB
1156970 Add. info. on upgrading to SAP SCM 7.0 ABAP
1156969 Add. info. on upgrading to SAP CRM 7.0 ABAP
1156968 Add. info. on upgrading to EHP 4 for SAP ERP 6.0 ABAP
1156844 Add. Info. on Upgrading to SAP SRM Server 7.0
1146578 Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP1
1142632 Enhancements for Enhancement Package installer: MaxDB
1123603 ABAP Dictionary adjustments for MaxDB 7.7
1108510 Add. Info.: Upgrade to SAP SRM Server 5.5 SR3 ABAP
1099841 Add. info.: Upgrade to SAP NW 7.0 Support Rel. 3 ABAP
1071404 Add. info.: Upgrade to SAP CRM 2007 ABAP
1039395 Add. info.: Upgrade to SAP CRM 5.2 ABAP
1010762 Add. info. on upgrading to SAP SCM 5.1 ABAP
1002641 SQL error -4004/-942 in DB02 during index consistency check
975861 Add. Info.: Upgrade to SAP SRM Server 6.0 ABAP
961513 Add. Info.: Upgrade to SAP SRM Server 5.5 SR2 ABAP
961512 Add. info. on upgrading to SAP SCM 5.0 SR2 ABAP
961511 Add. info.: Upgrade to SAP CRM 5.0 SR2 ABAP
961410 Add. info. on upgrading to SAP ECC 6.0 SR2 ABAP
960783 Add. info.: Upgrade to SAP NW 7.0 Support Rel. 2 ABAP
947991 Add. info.: Upgrade to SAP CRM 5.1 ABAP
930416
MaxDB precompiler terminates with signal 11
925240 Add. Info. on upgrading to SAP SCM 5.0 SR1 ABAP
916795 Replacement for MaxDB system table SYS.ALL_TAB_COLUMNS
913971 Add. info. on upgrading to SAP ERP Central Component 6.0 SR1
913849 Add. info.: Upgrade to SAP CRM 5.0 ABAP SR1
913848 Add. Info.: Upgrade to SAP SRM Server 5.5 SR1
905029 Add. info.: Upgrade to SAP NW 2004s Support Rel. 1 ABAP
© SAP AG
ADM326
14-24
898358
R3load: Entries remain in "/MAXDB/INDEXSTATEMENTS"
890202 Add. info.: Upgrade to SAP Solution Manager 4.0
851105 Deactivating the co-routines for MaxDB on UNIX systems
826488
Enhancements to upgrade on SAP CRM 5.0 ABAP
826487 Add. Info.: Upgrade to SAP SRM Server 5.5 ABAP
826093 Add. info. on upgrading to SAP SCM 5.0 ABAP
826092 Add. info. on upgrading to SAP ERP Central Component 6.0
818322 Add. info.: Upgrade to SAP NW 2004s ABAP
814704
MaxDB Version 7.6 parameter settings for OLTP/BW
789086
Precompiler Runtime to be used for Extended Kernel
415073
Termination or very long runtime in prepare phase DYNSPCADD
________________________________________________________________________
© SAP AG
ADM326
14-25
SAP Note No. 1298878
________________________________________________________________________
Number
1298878
Version
9 from 21.01.2011
Status
Released for Customer
Set on
21.01.2011
Language
EN
Master language
EN
Short text
Installation of SAP Enhancement Package 5 on SAP ERP 6.0
Responsible
SAP
Component
BC-UPG-ADDON
Upgrade Add-On Components (IS)
________________________________________________________________________
Long text
Symptom
You update and enhance existing software components using Enhancement
Package 5 on SAP ERP Central Component 600 (referred to here as SAP ECC
600).
Other terms
Updating and enhancing existing software components, Enhancement
Package, DVD 51039101, 605, SAPK-605DHINEAAPPL, SAPK-605DHINEADFPS,
SAPK-605DHINEAFINSRV, SAPK-605DHINEAGLTRAD, SAPK-605DHINEAHR,
SAPK-605DHINEAPS, SAPK-605DHINEARETAIL, SAPK-605DHINECCDIMP,
SAPK-605DIINERECRUIT, SAPK-605DHINFICA, SAPK-605DHINFICAX,
SAPK-605DIINFINBASIS, SAPK-605DHININSURANC, SAPK-605DHINISCWM,
SAPK-605DHINISH, SAPK-605DHINISM, SAPK-605DHINISOIL, SAPK-605DHINISPSCA,
SAPK-605DHINISUT, SAPK-605BGINLSOFE, SAPK-605DHINSAPAPPL,
SAPK-605BGINSEMBW, SAPK-605AGINERECRUIT, SAPK-605AGINFINBASIS,
SAPK-605AGINLSOFE, SAPK-605AGINSEMBW, SAPK-605IHINECCSE,
SAPK-605GGINECCSE.
© SAP AG
ADM326
14-26
Reason and Prerequisites
You plan an update and enhancement of existing software components of
SAP ERP 6.0 (this is referred to here as "installation").
Solution
This note provides additional information to the document 'How-to
Install Enhancement Package 5 for SAP ERP 6.0'. This guides is available
in the SAP Software Distribution Center at http://service.sap.com/swdc
-> Installations and Upgrades -> Installations and Upgrades - Entry by
Application Group -> SAP Application Components -> SAP ERP -> SAP ERP
ENHANCE PACKAGE -> EHP5 FOR SAP ERP 6.0 -> Technical Documentation.
This note is updated constantly. Make sure you have the current version
of this note before you start the installation.
Contents
I/....Keywords
II/...Important General Information
III/..Corrections to the Guide
IV/...Preparing the EHP Installation
V/....Problems During the EHP Installation
VI/...Problems After the EHP Installation
VII/...SAINT Passwords
VII/..Chronological Summary
----------------------------------------------------------------------I/ Keywords
Roadmap step 'Extraction', phase KEY_CHK: see central SAP Enhancement
Package Installer Note
Roadmap Step Checks, Phase EHPKEY_CHK: 2658825
Phase ADDONKEY_CHK: 2096499
For SAINT passwords, see "VII/ SAINT Passwords"
© SAP AG
ADM326
14-27
II/...Important General Information
---------------------< D029128 DEC/23/10 >--------------------------SEM-BW Add-On
If SEM-BW is installed on your SAP NetWeaver BW Hub system, see SAP Note
1531022 for information about the different landscape options.
---------------------< D053561 MAY/06/10 >----------------------------SAP ERP Components on SAP NetWeaver Systems
If additional SAP ERP Components (ERECRUIT, SEM-BW, FINBASIS or LSOFE)
are installed on your SAP NetWeaver system, see SAP Note 1326576 for
information about the update process.
---------------------< D031901 JUL/07/10 >----------------------------SRM Add-On
If you want to install the SRM Add-On 7.0 Enhancement Package 1 für ERP
6.0 EHP5 (SRM One-Client Scenario), see SAP Note 1321231 for more
information.
-----------------------------------------------------------------------
III/..Corrections to the Guide
/
-----------------------------------------------------------------------
IV/...Preparing the EHP Installation
---------------------< D033315 JAN/21/11 >---------------------------Delete View ZVMSEG
At the latest before the start of the Preprocessing Roadmap Step, delete
the view ZVMSEG if it exists in your system.
This prevents and the following activation error in phase ACT_UPG:
Check view ZVMSEG (DDIC/11.01.11/00:16)
Field BWART: Position relative to Basis table cannot be exchanged
Field DMBTR: Position relative to Basis table cannot be exchanged
Field KUNNR: Position relative to Basis table cannot be exchanged
© SAP AG
ADM326
14-28
Field LIFNR: Position relative to Basis table cannot be exchanged
View ZVMSEG is not consistent
For more information, see SAP Note 304670.
© SAP AG
ADM326
14-29
---------------------< D033315 JAN/21/11 >---------------------------IS-H only: Use updated Support Package Stacks
If you use IS-H, then do not apply Support Package Stacks 03 - 05 that
you have downloaded before January 14, 2011. Do only apply the updated
versions of these Support Package Stacks that have been provided for
download on January 14. For more information, see SAP Note 1549249.
---------------------< updated AUG/03/10 >------------------------------------------------< D037264 JUL/07/10 >---------------------------Components and Support Package requirements
o Regardless of the initial release, it is essential that you
import EHP5 including EHP5 Support Package Stack 01 (or higher)
to avoid errors.
We always recommend that you include the Support Package stack
that is currently proposed by SAP Solution Manager in the update
process.
o Calculation of Support Packages for Industry Solutions
When the Maintenance Optimizer calculates the required software
packages for the enhancement package installation, the behavior
regarding Support Packages for industry solutions is as follows:
- If you have not activated any industry solution in your
system, then the Maintenance Optimizer calculates Support
Packages for all industry solutions.
- If you have activated one or more industry solutions, the
Maintenance Optimizer only calculates Support Packages for the
activated industry solutions.
o If you have installed the software component ECC-SE, the
following applies: The ECC-SE release must always correspond to
the installed ERP Enhancement Package release. This means that
when you update to ERP Enhancement Package 5, the component
ECC-SE must also be updated to Version 605.
o You can also install the components SEM-BW 605
(SAPK-605AGINSEMBW), FINBASIS 605 (SAPK-605AGINFINBASIS),
ERECRUIT 605 (SAPK-605AGINERECRUIT) and LSOFE 605
(SAPK-605AGINLSOFE) on a pure SAP NetWeaver system (SAP NetWeaver
© SAP AG
ADM326
14-30
7.0 with Enhancement Package 2).
o DVDs for Enhancement Package 5 are not automatically sent to
customers. If you cannot use the Maintenance Optimizer for the
download, request the DVD with the material number 51039101 and
also the DVDs of SAP NW 7.02 (if not yet installed) from your
local subsidiary, or download the DVD from SAP Service
Marketplace. Copy the content of the DVDs to the download
directory, which is then accessed by the SAP Enhancement Package
Installer.
© SAP AG
ADM326
14-31
V/....Problems During the EHP Installation
-------------------< D035496 DEC/14/10 >------------------------------LOAD_SWITCHSTATES_LOST shortdump
If the procedure stops in phase MAIN_SHDRUN/ACT_UPG with a
LOAD_SWITCHSTATES_LOST shortdump, then stop the shadow instance and
start the shadow instance again.
This error can occur if you selected several technical usages and SAP
Kernel 720 with patch level 70 is used for the shadow instance.
--------------------< D032835 NOV/16/10 >-----------------------------Failure of Phase SHADOW_IMPORT_INC
When you update your system from SAP ERP 6.0 or enhancement package 3
for SAP ERP 6.0 to enhancement package 5, the following error can occur:
"Checks after phase MAIN_SHDIMP/SUBMOD_SHIMP/SHADOW_IMPORT_INC were
negativ!
Last error code set Unresolved requests in buffer ...
Check logfiles 'SHDALLIMP.ELG! ...
For a solution, see SAP Note 1525742.
----------------------< D037264 JUL/07/10 >---------------------------Include Support Packages
To avoid known errors, we recommend that you include all available
Enhancement Package 5 Support Packages and the relevant Support Package
stack directly in the queue. The SAP Solution Manager also proposes
these.
----------------------< D037264 JUL/07/10 >---------------------------DDIC Activation
The following errors can occur during the DDIC Activation:
o If your system has a lower SP level than SAP_BASIS SP13 in the
start release, the following error for view V_SH_ANKP occurs and
can be ignored:
3 EDO525XActivate dependent view "V_SH_ANKP"
EDH202 Check dependent search help "SH_ANKP"
1
1
EDH103 Search help "SH_ANKP" is consistent
4EEDT721 View "V_SH_ANKP" cannot be buffered
© SAP AG
ADM326
14-32
o The search helps H_5ITCN and H_5ITTT cannot be activated:
- "Srch Help" "H_5ITCN" could not be activated
- "Srch Help" "H_5ITTT" could not be activated
If Support Package 35 for SAP_HR 600 is already contained in the
source release, repeat the activation phase. If a lower Support
Package level is contained in the source release SAP_HR 600,
ignore the error and see Note 1243014.
© SAP AG
ADM326
14-33
----------------------< D037264 JUL/07/10 >---------------------------Errors During the Main Import
o If you source release is lower than ERP 6.0 EhP3, the following
error occurs during the main import of ECC-DIMP 603 into
non-Unicode systems: 'duplicate key error during insert into
table SALRTCATCT occured'
Solution: see SAP Note 1083533, unit 5. -> Errors during the
installation
----------------------< D037264 JUL/07/10 >---------------------------Errors in the method execution
When you update from Enhancement Package 1, the method FDT_AFTER_IMPORT
terminates with return code 0012.
Solution: Implement Note 1053777 and then continue the installation.
----------------------< D037264 JUL/07/10 >---------------------------Generation errors
o INSURANCE 605:
Program SAPLVKKN, include LVKKNU27: Syntax error in line 000034
INCLUDE report 'ISCDGEN_ACC_OP' not found.
Solution: After you install INSURANCE 605, execute the report
SAPRGEN_CD to generate the includes ISCDGEN_ACC_OP,
ISCDGEN_ACC_OPK and ISCDGEN_COPA.
o IS-H 605:
Screen SAPLNCOOPA003 0100: You can ignore the error (see release
note ISH_461_US_KLASSEN).
VI/...Problems After the EHP Installation
----------------------< D002243 23/DEC/10 >-------------------------Renamed DIMP Implementations
Some DIMP Implementations have been renamed. If you have created your
own implementations, the references to SAP´s DIMP implementations are
lost because of their new names. You have to redo your implementations.
For more information, see SAP Note 1540938.
© SAP AG
ADM326
14-34
----------------------- <D029263 15/APR/10 >-------------------------SAP Master Data Governance Customers Only: Migrating Settings
If you have activated the business function Financial Master Data
Management: Charts of Accounts (FIN_MDM_ACC) in EHP 4 and want to use
the business function Master Data Governance, Generic Functions
(MDG_FOUNDATION) after the update to EHP 5, some of the existing data
needs to be migrated to new tables, further settings have to be made in
new Customizing activities, and the new portal content has to be
adapted. For more information, see SAP Note 1456270.
Delivery Customizing is imported only into client 000. If you want to
copy Customizing into existing clients, read Note 337623.
VII/...SAINT Passwords
These passwords are only required, if you install additional technical
usages with SAINT. This is only possible for systems, which have the
technical usage "Central Applications" already installed.
Component
Password
SAPK-605BGINERECRUIT
SAPK-605BGINLSOFE
CD11D22C4B
C806AE4435
SAPK-605DHINEAAPPL
DE13CB5034
SAPK-605DHINEADFPS
C813D45031
SAPK-605DHINEAFINSRV
SAPK-605DHINEAGLTRAD
C70DD42245
C217D53156
SAPK-605DHINEAHR
DC63A7503D
SAPK-605DHINEAPS
DD63A75025
SAPK-605DHINEARETAIL
CB17C6394B
SAPK-605DHINECCDIMP
CA0ACA2236
SAPK-605DHINFICA
SAPK-605DHINFICAX
SAPK-605DHININSURANC
CF63A45836
CF1BA45836
DB11CA3145
SAPK-605DHINISH
8E438B621D
SAPK-605DHINISM
8E438B6218
SAPK-605DHINISOIL
C70FAB423A
SAPK-605DHINISPRA
DC02AB4225
SAPK-605DHINISPSCA
SAPK-605DHINISUT
SAPK-605IHINSEMBW
SAPK-605IHINECCSE
SAPK-605IHINFINBASIS
SAPK-605IHINISCWM
© SAP AG
DD00CA4225
DA63AB4220
CC14B15938
DD06A75F36
CC02D73C48
D90EAB4F36
ADM326
14-35
VII/..Chronological Summary
Date.......Topic....Short Description
----------------------------------------------------------------------JAN/21/11...IV......IS-H only: Use updated Support Package Stacks
JAN/21/11...IV......Delete View ZVMSEG
DEC/23/10...VI......Renamed DIMP Implementations
DEC/23/10...II......SEM-BW Add-On
DEC/14/10...V.......LOAD_SWITCHSTATES_LOST shortdump
NOV/16/10...V.......Failure of Phase SHADOW_IMPORT_INC
JUL/07/10...II......SRM Add-On
JUL/07/10...IV......Components and Support Package Requirements
JUL/07/10....V......Include Support Packages
JUL/07/10....V......DDIC Activation
JUL/07/10....V......Errors During the Main Import
JUL/07/10....V......Errors in the method execution
JUL/07/10....V......Generation errors
JUL/07/10....V......Postprocessing
MAY/06/10...II......SAP ERP Components on SAP NetWeaver Systems
APR/15/10....VI.....SAP Master Data Governance: Migrating Settings
© SAP AG
ADM326
14-36
________________________________________________________________________
Valid releases
Software Component
Release
from
to
605
- 605
605
- 605
605
- 605
SAP_APPL
SAP Application
IS-M
IS Media
IS-OIL
SAP OIL & GAS
ECC-SE
ESA FAST TRACK (ERP)
605
- 605
EA-HR
SAP R/3 Enterprise AddOn Human Resource
605
- 605
EA-RETAIL
SAP R/3 Enterprise AddOn Retail
605
- 605
EA-PS
SAP R/3 Enterprise AddOn Public Sector
605
- 605
EA-FINSERV
SAP R/3 Enterprise AddOn Financial Servi
605
- 605
605
- 605
605
- 605
FINBASIS
FINBASIS
INSURANCE
SAP Insurance
EA-APPL
SAP R/3 Enterprise PLM, SCM, Financials
605
- 605
EA-GLTRADE
SAP R/3 Enterprise Global Trade
605
- 605
FI-CAX
FI-CAX: Extended FI-CA
605
© SAP AG
- 605
ADM326
14-37
LSOFE
Learning Solution - Front End
605
- 605
605
- 605
ERECRUIT
E-Recruiting
FI-CA
FI Contract Accounts Receivable and Paya
605
- 605
EA-DFPS
SAP R/3 Enterprise Defense Forces & Publ
605
- 605
SEM-BW
SAP Strategic Enterprise Management
605
- 605
ECC-DIMP
ECC Discrete Industries Mill Products
605
- 605
605
- 605
IS-H
IS-Hospital
IS-PS-CA
IS-Public Sector Contract Accounting
605
- 605
605
- 605
605
- 605
IS-PRA
IS-UT
IS-UT
________________________________________________________________________
Reference to related Notes
Number
Short text
____________________________________________________________
1456663 SAINT: Enhancement Package 5 components on NW 7.02
1344564 Maintenance Optimizer: Check system landscape
1302772 Central Note - SAP Enhancement Package Installer 7.00
337623
Customizing after installation or upgrade
________________________________________________________________________
© SAP AG
ADM326
14-38
SAP Note No. 1299009
________________________________________________________________________
Number
1299009
Version
19 from 11.01.2011
Status
Released for Customer
Set on
11.01.2011
Language
EN
Master language
EN
Short text
Central Note: Upgrade Systems on SAP NetWeaver 7.0
EHP 2
Responsible
SAP
Component
BC-UPG-RDM
README: Upgrade Supplements
________________________________________________________________________
Long text
Symptom
Upgrade to SAP Systems based on SAP NetWeaver 7.0 including SAP
enhancement package 2.
Other terms
Upgrade, SAP NetWeaver 7.0 EHP2, central Note
Reason and Prerequisites
*
Solution
This is the central Note for upgrades to SAP systems based on SAP
NetWeaver 7.0 including enhancement package 2.
----------------------------------------------------------------------
CONTENTS
Part A: Upgrade Notes and Keywords
Part B: New Upgrade Program Release and Version
Part C: Correction Package for the Upgrade Program
Part D: General Problems / Information on all Upgrades
............I/ ...... Upgrade Keyword
© SAP AG
ADM326
14-39
............II/ ..... Important General Information
............III/ .... Corrections to the Guide
............IV/ ..... Errors on the CD-ROM
............V/ ...... Preparing the Upgrade
............VI/...... Problems During the Upgrade Phases
............VII/ .... Problems After the Upgrade
............VIII/ ... Chronological Summary
________________________________________________________________
________________________________________________________________
© SAP AG
ADM326
14-40
Part A: Upgrades Notes and Keywords
For more information on the upgrade of your specific application and the
current keyword, see one of the following Notes:
SAP NetWeaver 7.0 EhP2.......Note 1299008
SAP CRM .....................Note 1341978
SAP ERP .....................Note 1341975
SAP SCM .....................Note 1341981
SAP SRM .....................Note 1448239
Database................................................ Note number
______________________________________________________________________
SAP MaxDB .................................................. 817463
IBM DB2 for i ..............................................1168235
IBM DB2 for Linux, UNIX, and Windows ....................... 819876
IBM DB2 for z/OS ........................................... 815202
MS SQL Server .............................................. 825146
Oracle ..................................................... 819655
________________________________________________________________
________________________________________________________________
Part B: New Upgrade Program Release and Version
Before you start the upgrade program, check if there is a new release
and version of SAPup.
The current SAPup release is:
SAPup version lmt_001
1. To determine the currently used SAPup release and version,
2. proceed as follows:
- UNIX: Go to <UPGRADE_DIRECTORY>/abap/bin and call './SAPup
-V'.
© SAP AG
ADM326
14-41
Under UNIX, you have to enter the ABAP upgrade directory to
allow SAPup to use the correct OS libraries.
- Windows: Go to <UPGRADE_DIRECTORY>\abap\bin and call
'.\SAPup.exe -V'.
- IBM i: ADDLIBLE <SAPuplib>
SAPup UPGDIR(<DIR_PUT>) PARMLIST(' -V')
© SAP AG
ADM326
14-42
3. SAPup displays the following message:
This is SAPup version lmt_001, patch level <major>. <minor>
To download SAPup from SAP Service Marketplace go to http://service.sap.
com/patches.
Select Entry by Application Group -> Additional Components -> Upgrade
Tools -> SAPUP UNICODE -> SAPUP 7.02 UNICODE -> <OPERATING SYSTEM> ->
SAPUPLMT001 archive.
Caution: Always use the Unicode SAPup release and version regardless
of your SAP system being Unicode or non-Unicode!
Unpack the archive to a temporary location. In roadmap step
"Extraction", the upgrade program asks you to specify the path to the
new SAPup.
To get a list of all patches contained in a specific SAPup, call
SAPup -V
________________________________________________________________
________________________________________________________________
Part C: Correction Package for the Upgrade Program
Before the upgrade, it is VITAL that you apply the correction package
for the upgrade program, if available.
The correction package is provided as SAR archive that you must
integrate into the upgrade. Each SAR archive is valid for only one
product (= exactly one delivered DVD set).
The upgrade control program displays the correct name of the correction
package you have to apply.
The SAR archives are available at the following SAP Service Marketplace
area:
http://service.sap.com/patches -> Entry by Application Group ->
Additional Components -> Upgrade Tools -> Corrections for Upgrade ->
CORRECTIONS FOR UPGRADE 7.02 -> #OS independent
There are two packages, one for ABAP and one for Java:
ABAP Package Name: FIX_NW702.UPG
Java Package Name: FIX_J_BS7I2010.UPG
© SAP AG
ADM326
14-43
Comments:
o Caution: All products (SAP NetWeaver 7.0 EHP2 and all products
based on it) use the same correction package.
o The archive names on SAP Service Marketplace have a slightly
different naming convention:
The prefix "FIX_" ist not displayed. In addition, they have an
extension representing the patchlevel and <number> - an 8 digit
number. Thes extension varies with each patchlevel of the
archive.
o Some products are known under different names and can be used
differently. For example, NW-AS 7.00 which is part of Netweaver
04s is the successor product to WEB-AS as well as to the BW
product family. However, there is only one correction package
regardless of the use of the system.
Integration into the upgrade
4. Download the correction package for your product.
5. Store the SAR archive in the main upgrade directory.
6. Unpack the SAR archive using "SAPCAR -xvf <name>.SAR" You will get
two files, one of them is <Correction package name>.UPG, the other
one contains a history of changes.
7. During the KEY_CHK phase, the upgrade program searches the upgrade
directory for the correct correction package. If it is successful,
the package is automatically integrated into the upgrade. If the
upgrade program does not find a valid package, it displays a user
dialog requesting that you place the correction package in the
upgrade directory. You can use "Retry" to repeat the search.
The UPG archive contains data files and cofiles for the transport
requests and the corresponding buffer files (ABAP upgrade only), and
control files of the upgrade.
The corrections to the ABAP tools of the source release are imported in
the TOOLIMP4_FIX, TOOLIMP6_FIX phases (provided these exist), while the
© SAP AG
ADM326
14-44
corrections for the shadow system are imported in the SHD_FIX_IMP phase.
The transport requests are imported automatically.
You must not import requests into the system manually!
The corrections to the J2EE upgrade program and control files are
included automatically and the program is restarted to make the changes
become active.
________________________________________________________________
________________________________________________________________
© SAP AG
ADM326
14-45
Part D: General Problems / Information on all Upgrades
I/ Upgrade keyword
---------------------------------------------------------------------For the upgrade keyword, see the relevant product-specific Note listed
in part A of this Note.
----------------------------------------------------------------------
II/ Important General Information
-----------------------< D034302 DEZ/03/03 >-------------------Windows only: Execute program R3dllins.exe
The 6.40 kernel is compiled with the new version of MS compiler and
requires additional libraries for operation. To prevent problems during
and after the upgrade, you must execute program R3dllins.exe on your
central host, all application hosts, and on the remote shadow host, if
you are planning to use one.
You can find the program on the Upgrade Master CD in the
NT\I386\NTPATCHfolder. It must be executed before you start the upgrade
program and directly from the NTPATCH folder (it can be shared). Copying
and executing the program will not work!
------------------------< D042621 FEB/02/05 >------------------------LSMW now part of SAP_BASIS
As of SAP Web AS 6.20, LSMW is part of SAP_BASIS. If you are using LSMW
and your source release is based on SAP Web AS 6.10 or lower, do not
implement LSMW after the upgrade.
For more information, see SAP Note 673066.
© SAP AG
ADM326
14-46
-----------------------< D020904 MAR/15/07 >-------------------------MSCS Configuration: Split the ABAP Central Instance
In an MSCS configuration, you must split the ABAP central instance into
the ABAP central instance (ASCS) and central instance, as described in
SAP Note 1011190, if one of the following cases apply:
o You have upgraded your SAP NetWeaver '04 ABAP only system to SAP
NetWeaver 7.0 ABAP
o You have upgraded your SAP NetWeaver '04 ABAP only system to SAP
NetWeaver 7.0 ABAP, and now want to install a Java Add-In. The
split must done before the Java Add-In installation.
The split is required for the use of the enqueue replication server. If
you run an MSCS configuration without enqueue replication server, which
is the traditional MSCS configuration (where the clustered central
instance runs the message server and enqueue work process), you will
loose the enqueue lock table during a failover. The enqueue replication
server configuration prevents this loss.
If you want to migrate an ABAP+Java system that is already upgraded to
SAP NetWeaver 7.0 to the new configuration with enqueue replication
server you must perform a homogeneous system copy.
--------------------------------------------------------------------III/ Corrections to the Guides
-------------------------< D038245 APR/14/10 >-------------------------Manual Start of ASCS and ERS Instance (Phase REQ_ASCS_START)
When you update the SAP kernel on the host with the ASCS instance, also
run program 'cleanipc'. For more information about this program, see SAP
Note 1195961.
------------------------< updated D050889 JAN/11/11 >-----------------------------------------< C5078662 MAY/11/10 >------------------------Starting the Upgrade Program
It is no longer required to specify the jce_policy_zip option when
starting the upgrade program.
--------------------------------------------------------------------IV/ ..... Errors on the CD-ROM
---------------------------------------------------------------------
© SAP AG
ADM326
14-47
V/ Preparing the Upgrade
------------------------< D022989 JUN/11/10 >------------------------Avoing Error with the "DB_STORAGE_GET" Module>
When you include SAP NetWeaver 7.0 EHP2 Support Package 4 into the
upgrade, than implement SAP Note 1470501 afterwards to avoid an error
with the "DB_STORAGE_GET" module.
----------------------- < D001330 04/FEB/10 > -------------------------For Source Releases SAP R/3 4.6C and SAP R/3 4.6D Only: Prevent Lossof
your BSVV objects during the upgrade
If are upgrading your SAP system with the source SAP R/3 4.6C or SAP R/3
4.6D and have created customer-defined objects such as R3TR BSVV Z*
before the upgrade, you might lose parts of your BSVV objects during the
upgrade.
To solve this issue, proceed as described in SAP Note 1432102 prior to
starting the upgrade.
----------------------<changed D001658 10/JUL/07 >------------------------------------------< D001330 03/JUL/07 >-----------------------Parameter for the Central Syslog rslg/collect*
There may be conflicts with parameter values for the central syslog
"rslg/collect*" of the default profile.
If the parameters are set with 39<no.> and 40 <no.>, you must change
them to 14<no.> and 15<no.>. Make sure that the ports are not used by
other applications. If so, choose some other number.
For more information, see Note 1069225.
-----------------------< D038006 02/NOV/05 >-------------------------Source Release on Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
If you are using the above combination on your source release and have
set environment variable LD_ASSUME_KERNEL 2.4.21 according to SAP Note
797084, proceed as follows:
Before you start the upgrade, you need to delete the environment
variable LD_ASSUME_KERNEL 2.4.21 and deactivate component icman by
setting the following instance profile entry:
rdisp/start_icman=false
Restart the system. After the upgrade, delete the instance profile entry
again.
© SAP AG
ADM326
14-48
--------------------------< D003327 15/SEP/05 >-----------------------Back up customer-specific entries in table EDIFCT
If you have maintained customer-specific entries in table EDIFCT, they
may get lost during the upgrade. If you do not want to lose these
entries, export them before the upgrade and reimport them after the
upgrade.
For more information, see Note 865142.
© SAP AG
ADM326
14-49
--------------------------< D034302 16/AUG/05 >----------------------Windows only: Last profile text line must end with line feedback
Check that the last text line in all profiles ends with a line
feedback.To check this, open a profile file with a text editor, go down
with the cursor and ensure that the last line is empty. Otherwise there
could be problems in the KX_SWITCH phase as some tools will not be able
to handlethe profiles properly.
--------------------------< D034302 07/JUN/05 >----------------------Windows only: Stop SAP MMC during the upgrade downtime
Make sure that SAP MMC is not running during the upgrade downtime.
Otherwise, the files in the kernel directory will be in use and the
phase KX_SWITCH is not executed successfully.
--------------------------< D034302 07/JUN/05 >----------------------Windows only: Comment out parameter DIR_SERVER_ORAHOME
Check the default profile of your system. If you find the parameter
DIR_SERVER_ORAHOME, comment it out. Otherwise the phase KX_SWITCH is not
executed successfully.
-----------------------------------------------------------------------
VI/ Problems During the Upgrade Phases
---------------------<D037517 25/NOV/10 >-----------------------------SPS06 included in Upgrade: Error in Preprocessing / Phase
RUN_RSDB02CK_END
If you include Support Package SAP_ABA 702 06 into the upgrade, the
following error can occur:
Checks after phase MAIN_POSTP/RUN_RSDB02CK_END were negative! Last error
code set: Batch Job RSDB02CK Failed: Error(s) were found in the log(s),
accumulated in "RSDB02CK.ELG".
In the log file, the following error message exists:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DB02 consistency check ERRORS and RETURN CODE in RSDB02EN.QO1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EETG033 Table "TASYB" does not exist in the database
You can ignore this error.
© SAP AG
ADM326
14-50
If you include a lower or higher Support Package into the upgrade, the
error does not occur.
© SAP AG
ADM326
14-51
------------------------< D053561 02/JUN/10 >----------------------Phase IS_SELECT
An error in the IS_SELECT phase can erroneously lead to the deletion of
the add-on. In the following situation, the error can occur:
The add-on has the status 'KEEP'. When you choose 'Continue' a message
informs you that 'KEEP' is not valid and the status is set to
'UNDECIDED'. You select another option, for example, 'Keep with vendor
key'. When you then choose 'Back' and run the Configuration roadmap
stepa second time, you no longer get the message that 'KEEP' is not
possible and you cannot choose another option. Although the status of
the add-on is then still 'KEEP', the add-on will be deleted.
To solve the problem, reset the upgrade completely by choosing 'Back'
several times. Then, start the upgrade from scratch.
------------------------<D034302 01/JUN/10 >--------------------------Phase PARCONV_UPG
During the upgrade, the phase PARCONV_UPG can fail with an error during
the creation of secondary indexes. In the conversion log files of the
form NCONV..<SID> the following error is reported:
Index " " could not be created completely in the database
To solve this problem, repeat the phase. To avoid the error in advance
include the support packages mentioned in SAP Note 1468467 in the
upgrade procedure.
----------------------< D030559 27/APR/10 > ---------------------------Phase: MAIN_NEWBAS/RUN_RSAIMMERGE_UPG
To avoid a runtime error in your target system, increase parameter
"em/initial_size_MB = 1024" to "em/initial_size_MB = 4096" in the
instance profile.
For more information, see SAP Note 1460004.
----------------------< D038245 19/APR/10 > ---------------------------Phase: MODPROF_PFPAR_UPG
If the following error occurs: "MODPROF_PFPAR_UPG:fails even rc=0", add
the following paramenter to the instance profile: "SAPup_check_level =
5".
----------------------< D037517 17/FEB/10 > ---------------------------Phase: MAIN_SHADOW/START_SHDI_FIRST
Description: An RFC error occurs (RFC LOGIN FAILED)
Solution:
© SAP AG
ADM326
14-52
8. In the SAPup.par file, set the value of the
/UNIX/sleep_after_shdsys_start parameter to 200.
9. Restart the upgrade program and repeat the phase.
© SAP AG
ADM326
14-53
----------------------< C5050355 JAN/22/10 >-------------------------Adjust Hostnames in Shadow Instance Profiles Manually
When you have chosen option "Take profiles from save" to reuse the
profiles for the shadow instance of your previous upgrade, update the
hostnames in the profiles for the shadow instance manually after the
"Configuration" roadmap step. You can find these profiles under
<DIR_PUT>/abap/<SID>/SYS/profiles. This workaround will be fixed for
tools delivered with BS7i2010.
------------------------< D025988 JUN/16/00 >------------------Phase: PARDIST_SHD
Description: For Windows NT only
The upgrade is terminated during the PARDIST_SHD phase. The PCONUPG.ELG
log file contains an incomplete error text which was extracted from the
DS<date>. <SID> log file. Repeat the phase.
-------------------------- < D034302 07/OCT/05 >----------------------Phase: REQJOBRES
Description: Windows only - SAPup issues the error message
value returned by call sappfpar.exe Start_Program_01 pf=...is incorrect.
Please analyze the content of ...\put\log\NTPARVAL.LOG
You can ignore this error. Repeat the phase to continue.
--------------------------< D034302 16/AUG/05 >----------------------Phase: KX_SWITCH (Windows only) Description: Upgrade stops with an error
message which asks you to checkfile NTPARVAL.LOG. In this file, messages
like the following are displayed:
fopen(...): Invalid argument
Check that the last text line in all profiles ends with a line
feedback.To check the profile, open a profile file with a text editor,
go down with the cursor, and ensure that the last line is empty. If it
is not, add an empty line at the end of the file and save it.
--------------------------< D034302 07/JUN/05 >----------------------Phase: KX_SWITCH (Windows only)
Description: Because SAP MMC is running, SAPup stopped with the
following error message:
SAPup> SEVERE ERROR: Could not delete file '...\sapstartsrv.exe' ...
Reason: 'ErrorMessage: Access is denied.
In this case, shutdown SAPMMC and SAP service of your system and repeat
the phase.
© SAP AG
ADM326
14-54
--------------------------< D034302 07/JUN/05 >----------------------Phase: KX_SWITCH (Windows only)
Description: If parameter DIR_SERVER_ORAHOME has not been commented out
,SAP up will stop with the following error message:
Error: value returned by call sappfpar.exe Start_Program_01 pf=...is
incorrect. Please analyze the content of ...NTPARVAL.LOG.
The NTPARVAL.LOG states:
immediate ...\sapcpe.exe pf=...Illegal Parameter in Default Profile:
"DIR_CLIENT_ORAHOME". sapparam: Illegal Parameter in Default Profile:
"DIR_SERVER_ORAHOME". (no Default-Value)
In this case, comment the parameter out and repeat the phase.
--------------------------< D021063 OCT/12/06 >---------------------Phase: XPRAS_UPG
Description: The phase issues the following short dump:
"GEN_BAD_MACRO_SOURCE" for program /1BCDWB/<XXXXXXXXXXXXXXXXXX>
You can ignore this message.
----------------------< D038245 FEB/28/06 >-------------------------Phase: MODPROFP_UPG
Description: When you are performing a dual-stack upgrade (ABAP and Java
system at the same time), in phase MODPROFP_UPG the ABAP system is
started together with the Java system part for the first time. The phase
may fail if the SAP J2EE Engine does not start fast enough.
Check manually if the SAP J2EE Engine is running and if so, choose
"repeat" to repeat the upgrade phase.
----------------------------------------------------------------------
Phase: CHK_POSTUP
Note: 996953
Description: Log file LONGPOST.LOG prompts you to migrate a CMOD project
although no project exists.
----------------------------------------------------------------------
VII/ Problems After the Upgrade
--------------------< D020815 DEC/23/10 >-----------------------------Reconfiguration of User Reauthentication
If you have performed the upgrade from a source release lower than SAP
NetWeaver 7.0 EHP1, you have to reconfigure the user reauthentication
© SAP AG
ADM326
14-55
after the ugprade.
As of SAP NetWeaver 7.0 EHP1, there is a new implementation of the user
reauthentication and it is not active until you have configured it.For
more information, see SAP Note 1532874.
© SAP AG
ADM326
14-56
----------------------< D027133 30/NOV/10 >----------------------------Missing Table
If you included SAP_ABA 702 SP 06 into the upgrade, the you see the
following in transaction DB02 under 'Missing Tables and Indexes':
Results of Consistency Check
Object missing in the database
Tables
X TASYB
You can either ignore this issue or create the table in the database in
transaction DB02.
If you included a lower or higher Support Package into the upgrade,
thisissue does not occur.
----------------------< D034302 09/JUL/10 >-------------------------Ignore Short Dump
If the following short dump occured during the enhancement package
installation, you can ignore it:
Category
Runtime Errors
Except.
ABAP Program
ABAP Programming Error
CALL_FUNCTION_NOT_FOUND
CX_SY_DYN_CALL_ILLEGAL_FUNC
CL_ENH_TOOL_BADI_IMPL=========CP
Application Component BC-DWB-CEX
Date and Time
12.05.2010 08:59:40
----------------------< D001330 15/JUL/10 >---------------------------Delete CUA Load after the Upgrade
If after the upgrade you face an issue with the CUA load in your SAP
system, delete the CUA load using report "RSLANG20" as described in SAP
Note 110910.
----------------------<enhanced C5068728 25/MAY/10 >-----------------------------------------< I043868 12/APR/10 >-----------------------Ignore obsolete tables "PATRTVERS2","PATRTCONF", and "PATRTPHASE"
If you run into the table "PATRTVERS2", "PATRTCONF", "PATRTPHASE"
(SPAM-specific), or table "sap_tmp_stmt_stats_tab" (MS SQL
server-specific) after the upgrade, ignore these tables. They have
become obsolete and will be deleted automatically!
------------------------< I043868 12/APR/10 >--------------------------Windows Only: Ignore obsolete table "sap_tmp_stmt_stats_tab"
If you run into the table "sap_tmp_stmt_stats_tab" (MS SQL
© SAP AG
ADM326
14-57
server-specific) after the upgrade, ignore this table. It has become
obsolete and will be deleted automatically.
© SAP AG
ADM326
14-58
--------------------------< I803368 21/JUL/09 >------------------------Syntax error in TREX ABAP Client after the upgrade
If you perform an upgrade from SAP NetWeaver 7.00 SP17 or higher to
SAP NetWeaver 7.0 including enhancement package 1 SP2 / SP3 / SP4 or
to SAP NetWeaver 7.0 including enhancement package 2 SP1,
you will get a syntax error in class your TREX ABAP client
(CL_TREX_FACADE). To solve this issue, check SAP Note 1355746.
--------------------<enhanced D038245/JUNE/05 >--------------------------------------------< D003551 02/MAY/05--------------------------Check Primary Index of Table MEMGMT_DEPLOYMNT
After the upgrade, check that the primary index of table
MEMGMT_DEPLOYMNT exists. If not, create the index manually.
If you still get the message that MEMGMT_DEPLOYMNT00 is an unknown
object in the dictionary, drop it on the database level.
------------------------< D020815 AUG/23/02 >-----------------------SPAU: Names of interface methods are truncated
Some methods (ABAP objects) that were modified and overwritten by the
upgrade can be displayed in transaction SPAU with their names shortened
to 30 characters.
As a result, the system may also incorrectly sort methods in SPAU under
"Deleted objects".
Caution: Deleted objects are not displayed in the standard selection in
SPAU. It is easily possible to overlook these!
For more information about the correction, see Note 547773.
----------------------------------------------------------------------
© SAP AG
ADM326
14-59
Date.....Topic..Short description
----------------------------------------------------------------------DEC/23/10..VII..Reconfiguration of User Reauthentication
NOV/30/10..VII..Missing Table
JUL/27/10..VII..Ignore Short Dump
JUL/15/10..VII. Delete CUA Load after the Upgrade<
JUN/11/10..V....Avoiding Error with the "DB_STORAGE_GET" Module
JUN/07/10..V....Preventing long runtime of SUSR_AFTER_IMP_PROFILE
JUN/02/10..VI...Phase IS_SELECT
JUN/01/10..VI...Phase PARCONV_UPG
MAY/11/10..III..Starting the Upgrade Program
APR/28/10...V...Avoiding Loss of Customer Objects During the Upgrade
MAR/10/10...V...Preventing Unrequired Table Conversion
APR/19/10...VI..MODPROF_PFPAR_UPG: Add parameter to the instance profile
APR/14/10..III..Manual Start of ASCS and ERS Instance: cleanipc
APR/12/10...VII.Ignore tables "PATRTVERS2","PATRTCONF", and "PATRTPHASE
APR/12/10...VII.Windows Only:Ignore obsolete table "sap_tmp_stmt_..."
FEB/17/10...VI..Phase MAIN_SHADOW/START_SHDI_FIRST
FEB/04/10...V...Prevent Loss of your BSVV Objects During the Upgrade
JUL/21/09...VII.Syntax error in TREX ABAP Client after the upgrade
JUL/03/07....V..Parameter for the Central Syslog rslg/collect*
MAR/15/07...II..MSCS Configuration
FEB/28/07...VI..Applying Support Packages on the Source Release
FEB/28/07...VI..Phase CHK_POSTUP - CMOD/SMOD migration
OCT/12/06...VI..Phase XPRAS_UPG: short dump GEN_BAD_MACRO_SOURCE
FEB/28/06...VI..Phase MODPROFP_UPG fails - check J2EE Engine
NOV/02/05....V..Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
OCT/07/05...VI..Phase: REQJOBRES
AUG/16/05...VI..Windows only: KX_SWITCH - Check file NTPARVAL.LOG.
AUG/16/05....V..Windows only: Last profile text line - line feedback
JUN/07/05....V..Windows only: Stop SAP MMC during the upgrade downtime
JUN/07/05....V..Windows only: Comment out parameter DIR_SERVER_ORAHOME
JUN/07/05...VI..Windows only: KX_SWITCH - SAP MMC is running
JUN/07/05...VI..Windows only: KX_SWITCH - parameter DIR_SERVER_ORAHOME
MAY/02/05..VII..Check Primary Index of Table MEMGMT_DEPLOYMNT
FEB/02/05...II..LSMW now part of SAP_BASIS
DEZ/03/03...II..Windows only: Execute program R3dllins.exe
SEP/17/03....I..SAPup keyword
AUG/23/02..VII..SPAU: Names of interface methods are truncated
JUL/19/02...II..Problems with the shadow instance
MAY/24/02...II..Corrections and repairs for the upgrade
________________________________________________________________________
© SAP AG
ADM326
14-60
Valid releases
Software Component
Release
from
to
701
- 702
SAP_BASIS
SAP Basis component
________________________________________________________________________
Reference to related Notes
Number
Short text
____________________________________________________________
1355746 Syntax error in class cl_trex_test_facade
1341981 Add. info. on upgrading to SAP SCM 7.0 including EHP1 ABAP
1341978 Add. info. on upgrading to SAP CRM 7.0 including EHP1 ABAP
1341975 Add. info. on upgrading to SAP ERP 6.0 including EHP5 ABAP
1338386 Upgrade to SAP NetWeaver 7.0 EHP2 ABAP (IBM DB2 for i)
1293387 Add. Info. on Upgrading to SAP SRM Server 7.0 SR1 ABAP
________________________________________________________________________
© SAP AG
ADM326
14-61
SAP Note No. 1341975
________________________________________________________________________
Number
1341975
Version
3 from 15.12.2010
Status
Released for Customer
Set on
15.12.2010
Language
EN
Master language
EN
Short text
Add. info. on upgrading to SAP ERP 6.0 including
EHP5 ABAP
Responsible
SAP
Component
BC-UPG-RDM
README: Upgrade Supplements
________________________________________________________________________
Long text
Symptom
Errors in the upgrade procedure or in the upgrade guide; preparations
for the upgrade; additional information to the upgrade guide
Other terms
Update, migration, upgrade, release upgrade, SAPup, SAP ERP Central
Component 6.0,
Reason and Prerequisites
*
Solution
CAUTION:
This note is updated regularly!
Therefore, you should read it again immediately before starting the
upgrade.
What information can I expect from this note?
This note describes problems that may occur during the system upgrade
and provides information on how to solve them. This usually takes the
form of references to other notes.
The main purpose of this note is to prevent data loss, upgrade
shutdowns, and long runtimes.
© SAP AG
ADM326
14-62
It deals with database-independent problems only.
Which additional notes do I require in preparation for the upgrade?
You need to refer to the relevant database-specific note below:
Database .................................................. Note number
© SAP AG
ADM326
14-63
_______________________________________________________________________
SAP MaxDB .......................................................817463
IBM DB2 for i (NetWeaver-specific)..............................1168235
IBM DB2 for i (Business Suite-specific).........................1179413
IBM DB2 for Linux, UNIX and Windows .............................819876
IBM DB2 for z/OS.................................................815202
MS SQL Server....................................................825146
Oracle...........................................................819655
You also need to refer to the following important SAP Notes:
Short text ................................................ Note number
_______________________________________________________________________
Central Note: Upgrade to Systems on SAP NetWeaver 7.0 EHP2......1299009
OCS: Known problems with Support Packages in SAP NW 7.0 AS ABAP..822379
Contents
I/ ...... SAPup Keyword
II/ ..... Important General Information
III/ .... Corrections to the Guide
IV/ ..... Errors on the CD-ROM
V/ ...... Preparing the Upgrade
VI/...... Problems During the PREPARE and Upgrade Phases
VII/ .... Problems After the Upgrade
VIII/ ... Chronological Summary
I/ SAPup keyword
---------------------------------------------------------------------The SAPup keyword is: 20077540
This must be entered in phase KEY_CHK.
----------------------------------------------------------------------
© SAP AG
ADM326
14-64
II/ Important General Information
-----------------------< D025323 NOV/21/08 >-------------------------Corrections and Repairs for the Upgrade
Before the upgrade, it is vital that you check whether the following is
available for your specific upgrade:
o A new version of SAPup.
o Repairs to the ABAP upgrade programs.
For more information, see Note 1299009.
It is ESSENTIAL that you apply this Note.
-----------------------< D034302 DEC/03/03 >-------------------------Windows only: Execute program R3dllins.exe
The 6.40 kernel is compiled with the new version of MS compiler and
requires additional libraries for operation. To prevent problems during
and after the upgrade, you must execute program R3dllins.exe on your
central host, all application hosts, and on the remote shadow host, if
you are planning to use one.
You can find the program on the Upgrade Master CD in the NT\I386\NTPATCH
folder. It must be executed before you start PREPARE and directly from
the NTPATCH folder (it can be shared). Copying and executing the program
will not work.
-----------------------< D028310 JUL/19/02 >-------------------------Problems with the Shadow Instance.
The following Notes contain information about problems with the shadow
instance:
o 525677: Problems when starting the shadow instance
o 430318: Remote shadow instance on a different operating system
------------------------< D042621 FEB/02/05 >------------------------LSWM now part of SAP_BASIS
As of SAP Web AS 6.20, LSMW is part of SAP_BASIS. If you are using LSMW
and your source release is based on SAP Web AS 6.10 or lower, do not
implement LSMW after the upgrade.
For more information, see Note 673066.
© SAP AG
ADM326
14-65
-----------------------< D020904 MAR/15/07 >--------------------------MSCS: Upgrade of the ABAP system only, or Upgrade of the ABAP system
with subsequent Java Add-In installation:
In an MSCS configuration, you must split the ABAP central instance into
the ABAP central instance (ASCS) and central instance, as described in
SAP Note 1011190, if one of the following cases apply:
o You have upgraded your SAP NetWeaver '04-based ABAP system to SAP
NetWeaver 7.0-based ABAP system
o You have upgraded your SAP NetWeaver '04-based ABAP system to SAP
NetWeaver 7.0-based ABAP system, and now want to install a Java
Add-In. The split must done before the Java Add-In installation.
The split is required for the use of the enqueue replication server. If
you run an MSCS configuration without enqueue replication server, which
is the traditional MSCS configuration (where the clustered central
instance runs the message server and enqueue work process), you will
loose the enqueue lock table during a failover. The enqueue replication
server configuration prevents this loss.
If you want to migrate an ABAP+Java system that is already upgraded to
SAP NetWeaver 7.0 to the new configuration with enqueue replication
server, you must perform a homogeneous system copy.
---------------------------------------------------------------------
III/ Corrections to the Guides
---------------------------------------------------------------------
IV/ Errors on the CD-ROM
---------------------------------------------------------------------
© SAP AG
ADM326
14-66
V/ Preparing the Upgrade
------------------------< D047992 23/APR/09 >-----------------------Check if Matchcodes Exist in Your System
Before starting the upgrade, check if old help views or matchcodes
existin your SAP system. If so, this can lead to an upgrade failure with
a subsequent system restore.
Use report TWTOOL01 as described in SAP Note 1330256 to check if
matchcodes exist in your system.
If you are running a combined upgrade and Unicode conversion, it is
mandatory that you delete or migrate matchcode objects to Search Helps
before you start SAPup.
For more information about Search Helps that have replaced the
matchcodes, see the online documentation for the ABAP Dictionary.
------------------------< D035496 31/MAR/09 >-----------------------Selecting the Target SP Stack Level in Maintenance Optimizer
When selecting an enhancement package release and a target SP Stack
level for the stack XML generation in Maintenance Optimizer, it is
mandatory to select Support Package Stack 02 or higher. If you select a
lower SP Stack level, you will get an error message in phase
EHP_INCLUSION.
------------------------< D038245 09/DEC/08 >-----------------------Downloading Kernel DVDs for the Upgrade
The software of the kernel is split into two files with the following
naming convention:
<product><version>
<product><version>Upgrade
When you download the kernel DVDs for the upgrade, you must download
both files from SAP Service Marketplace.
------------------------< D044675 17/JAN/08 >-------------------------Upgrade from Source Release 4.6C: Including a minimum SP level
If your source release system includes SAP_HR 46C Support Package level
D1, data loss may occur during the upgrade. To prevent any data loss,
include at least Support Package 26 of the target release into the
upgrade, although the upgrade program does not request it.
Alternatively, update your system to SAP_HR 46C Support Package level D2
before the upgrade.
----------------------<changed D001658 10/JUL/07 >--------------------© SAP AG
ADM326
14-67
------------------------< D001330 03/JUL/07 >-------------------------Parameter for the Central Syslog rslg/collect*
There may be conflicts with parameter values for the central syslog
"rslg/collect*" of the default profile.
If the parameters are set with 39<no.> and 40<no.>, you must change them
to 14<no.> and 15<no.>. Make sure that the ports are not used by other
applications. If so, choose some other number.
For more information, see Note 1069225.
© SAP AG
ADM326
14-68
-------------------< D003327 05/FEB/07 >------------------------------Back up customer-specific entries in table EDIFCT
If you have maintained customer-specific entries in table EDIFCT, they
may get lost during the upgrade. If you do not want to lose these
entries, export them before the upgrade and reimport them after the
upgrade.
For more information, see Note 865142.
------------------------< D044675 18/DEC/06 >-----------------------New SPAM/SAINT Version on Source Release
Before you include Support Package SAPKH60007 in the upgrade, you must
apply at least the following SPAM/SAINT versions on your source release:
o Source Rel. SAP R/3 4.x: SPAM/SAINT version 0045
o Source Rel. SAP R/3 Enterprise, SAP ECC. 5.0: SPAM/SAINT version
0022
If you use an older version, you will receive conflict messages for
SAP_APPL SP 07 with ECC-DIMP, object list SAPKGES01G, during PREPARE. In
this case, you can repeat the phase after applying the SPAM/SAINT
update.
-----------------------< D028310 28/AUG/06 >-------------------------Update SAP Kernel on Source Release
If you want to convert logical cluster tables incrementally using
transaction ICNV during the upgrade, you must make sure that the level
of the SAP kernel on the source release is high enough.
For more information, see SAP Note 946659.
-----------------------< D022188 24/APR/06 >-------------------------Prepare table COEP for the upgrade
If your source release is SAP R/3 4.6C or below and table COEP contains
many data, the conversion of this table during the upgrade can lead to
aprolonged downtime.
For more information about reducing downtime, see Note 937389.
-----------------------< D038006 02/NOV/05 >-------------------------Source Release on Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
If you are using the above combination on your source release and have
set environment variable LD_ASSUME_KERNEL 2.4.21 according to SAP Note
797084, proceed as follows:
Before you start the upgrade, you need to delete the environment
© SAP AG
ADM326
14-69
variable LD_ASSUME_KERNEL 2.4.21 and deactivate component icman by
setting the following instance profile entry:
rdisp/start_icman=false
Restart the system.
After the upgrade, delete the instance profile entry again.
© SAP AG
ADM326
14-70
--------------------------< D034302 16/AUG/05 >----------------------Windows only: Last profile text line must end with line feedback
Check that the last text line in all profiles ends with a line
feedback.To check this, open a profile file with a text editor, go down
with the cursor and ensure that the last line is empty. Otherwise there
could be problems in the KX_SWITCH phase as some tools will not be able
to handle the profiles properly.
------------------------< D031149 13/JUL/05 >------------------------Source Rel. ECC DIMP 5.0: MPN Conversion Exit
In release ECC DIMP 5.0 - up to and including CRT02 - the MPN conversion
exit is delivered as "active" by default. The conversion exit is set to
active, if the checkbox "Active conversion exit" in the following
customizing transaction is flagged: Logistics - General -->
Interchangeability of Parts --> Set Up Conversion Exit for Material
Numbers.
If the MPN conversion exit should not be used in the system, it is very
important that it is deactivated before the upgrade (in Source release
ECC DIMP 5.0).
For more information on how to proceed, see Note 854523.
The problem is solved with CRT03 of release ECC DIMP 5.0.
-----------------------< D031049 14/OCT/04 >-------------------------Source Rel. 4.0B: Project-Related Incoming Orders
If you are using the preliminary solution for project-related incoming
orders published with Note 118780, you have to modify data elements
before the upgrade.
For more information, see Note 369542.
----------------------< D038245 09/SEP/04 >--------------------------Source Release Extension Set 1.10: Exchange containers
If your system was installed with SAP R/3 Enterprise Ext. Set 1.10
(based on SAP Web AS 6.20) and you are using a database that uses
different containers for saving data (Oracle, Informix and DB2 UDB for
UNIX and Windows), refer to note 674070 before the upgrade.
Otherwise, the exchange containers (tablespaces/dbspaces) cannot be
emptied during the upgrade and cannot be deleted after the upgrade.
------------------------< D038245 19/APR/04 >-----------------------Unicode Systems: Downward Compatible Kernel 6.40
If you are using the normal kernel for Release 6.20 with your Unicode
system, PREPARE issues the error message:
Could not open the ICU common library.
© SAP AG
ADM326
14-71
Before you start PREPARE, install the Downward Compatible Kernel for
Release 6.40. Until this kernel is available, proceed as described in
Note 716378.
© SAP AG
ADM326
14-72
------------------------< D032986 22/SEP/05 >-----------------------Upgrading with reintegrated add-ons (retrofit)
For SAP ERP Core Component 6.0 (ECC 6.0), more add-ons were reintegrated
into the main ECC system or the Extension Sets.
The following Notes contain additional information on processing these
add-ons before, during and after the upgrade.
o Note 838002 Add-ons (non-IS) integrated in SAP ECC 600
o Note 838003 Industry Add-ons integrated in SAP ECC 600
--------------------------< D032986 27/JAN/04 >----------------------Upgrading with PI/PI-A
For information on how to upgrade your system with PI/PI-A plug-ins, see
Note 700779.
--------------------------< D025323 24/APR/03 >----------------------Upgrade on AIX: saposcol
Refer to Note 526694 before the upgrade.
--------------------------< D019926 DEC/10/02 >----------------------Upgrading with AIX 5.1
If you want to upgrade with AIX 5.1, see Note 502532 before starting the
upgrade.
-----------------------< D025323 FEB/20/02 >-------------------------Source Releases on UNIX 32-bit or AIX 64-bit
In some cases, you may have to upgrade the operating system to 64-bit
before the actual upgrade.
When you upgrade from AIX 4.3 64-bit, you must perform some additional
actions before upgrading.
For more information, see Notes 496963 and 499708.
-----------------------------------------------------------------------
© SAP AG
ADM326
14-73
VI/ Problems During the Preparation and Upgrade Phases
This section addresses known problems that cannot be avoided using
preventive measures. These problems will only occur under very specific
circumstances.
Problems During the Preparation Phases
------------------------< D035496 31/MAR/09 >-----------------------Error in the EHP_INCLUSION Phase
If you have selected a target SP stack level lower than SP stack 02 for
the stack XML generation in Maintenance Optimizer, you will get a
similar error message in phase EHP_INCLUSION:
EHP patch level 34 for component SAP_HR is too low, destination level is
already at 37.
Solution:
1. Select SP Stack 02 or higher as the target SPS level for enhancement
package 4 and rerun the package calculation in Maintenance
Optimizer.
2. Download the additional packages calculated by the Maintenance
Optimizer to your EPS inbox directory.
3. Repeat the failed phase with the newly generated stack XML file.
--------------------------< D038245 28/FEB/08 >----------------------Windows only: MSSERV_INTERN port numbers
During PREPARE, the upgrade tool requests a port number for the
MSSERV_INTERN port. If your system is running on Windows, you cannot use
port numbers within the following range: 6665 - 6669.
-----------------------< D038245 APR/11/02 >-------------------------Termination in the TOOLIMPD3 phase
The TOOLIMPD3 phase terminates during the tool import. The following
message appears in the log file:
ABAP runtime error CALL_FUNCTION_NO_RECEIVER
Receiving data for unknown CPIC link XXXXXX.
Repeat the phase and continue with the upgrade.
----------------------------------------------------------------------Problems During the Upgrade Phases
© SAP AG
ADM326
14-74
--------------------< D030182 05/AUG/10 > -----------------------------Phase: JOB_RCIFSTKUREN2
Description: Oracle Only: After this phase, on DB platform Oracle you
may encounter an inconsistency with primary DB index of table
"CIFSTKUCOUNT".
Solution: Include the corresponding SP mentioned in SAP Note 1483213
into the upgrade.
If this SP is not yet released, and inconsistency with the DB index
exists, rename index with execution of funtion module DB_RENAME_INDEX
(transaction SE37, only on DB platform Oracle):
Parameters:
TABNAME:
CIFSTKUCOUNT
INDNAME_NEW: CIFSTKUCOUNT~0
INDNAME_OLD: CIFSTKUCNT~0
To avoid errors with index information on Oracle systems, apply SAP Not
1483213.
------------------------< I043270 15/JUL/10 >-------------------------LONGPOST.LOG
- The message: "A1PESEEF_BADI 103 BAdI implementation
FMFG_HELD_PO_NO_UPD must still be migrated" can be ignore
since the implementation is obsolete. See SAP Note 1246090.
- You can ignore the following messages:
'3PETG447 Table and runtime object "/SAPAPO/RESDIM" exist
without DDIC reference ("Transp. table")'
'3PETG447 Table and runtime object "/SAPAPO/RES_HEAD" exist
without DDIC reference ("Transp. table")'
'3PETG447 Table and runtime object "/SAPAPO/RES_TXT" exist
without DDIC reference ("Transp. table")'
The tables are deliberately kept on the database when you
upgrade (For more information, see Note 827490).
- Messages with the following pattern can also be ignored:
'4PEDH176 Parameter list of append search help "..." differs
from appending one'.
© SAP AG
ADM326
14-75
------------------------< D021548 05/MAY/10 >-------------------------Phase: MAIN_NEWBAS/XPRAS_AIMMRG
Description: Shortdump OBJECTS_OBJREF_NOT_ASSIGNED_NO
SAP Note: 1465173
------------------------< D026178 15/OCT/09 >-------------------------Phase CHK_POSTUP
Description: P messages in LONGPOST.LOG file:
o 4PEDH176 Parameter list of append search help "ASH_FICO_TREX"
differs from appending one
o 4PEDH176 Parameter list of append search help "FICO_APPEND"
differs fro appending one
o 4PEDH176 Parameter list of append search help "FICO_SUBSTRINGS"
differs from appending one
o 4PEDH176 Parameter list of append search help "ASH_GRANT_TREX"
differs from appending one
o 4PEDH176 Parameter list of append search help "GRANTS_APPEND2"
differs from appending one
Solution: You can ignore these P messages.
--------------------------< I027631 17/APR/09 >----------------------Phase: ACT_UPG
Note: 1321756
Description: During the ACT_UPG phase, you might get the following error
message:
1EEDO519X"Table" "USMDZ1FCRS" could not be activated
Proceed as described in Note 1321756.
--------------------------< D034302 16/AUG/05 >----------------------Phase: KX_SWITCH (Windows only)
Description: Upgrade stops with an error message which asks you to check
file NTPARVAL.LOG. In this file, messages like the following are
displayed:
fopen(...): Invalid argument
Check that the last text line in all profiles ends with a line feedback.
To check the profile, open a profile file with a text editor, go down
with the cursor, and ensure that the last line is empty. If it is not,
add an empty line at the end of the file and save it.
---------------------<changed D003551 OCT/04/05 >---------------------
© SAP AG
ADM326
14-76
--------------------------< D021867 AUG/10/04 >----------------------Phase: JOB_RDDNTPUR
Description: In the longpost-log file, you may get the error message:
3PETG447 Table and runtime object "TA22EQU_WAO" exist without DDIC
reference.
or
3PETG447 Table and runtime object "TVERTREE" exist without DDIC
reference
You can ignore this message.
--------------------------< I002675 OCT/07/05 >----------------------Phase: SHADOW_IMPORT_INC
Note: 884809
Description: The upgrade fails in phase SHADOW_IMPORT_INC. Check if the
log files display error messages as stated in the above Note. If so,
proceed as described in the Note.
--------------------------< C5003135 MAY/03/09 >----------------------Phase: SHDUNINST_DB
Description: The upgrade fails with the following error message:
'Could not drop database shadow user <shadow DB user>'
The log file <upgrade directory>/abap/log/SHDUNINST.LOG contains the
error:
BR0152E Environment variable SAPDATA_HOME is not set
Solution:
4. Stop the SL Controller and SAPup.
5. Set the environment variable SAPDATA_HOME to the directory <upgrade
directory>/abap/tmp (by default /usr/sap/<SAPSID>/upg/abap/tmp) in a
local shell for user <sapsid>adm.
6. Start the SL Controller from this local shell by executing the
startup script from the upgrade directory.
7. Start the upgrade GUI and use the 'repeat' option for this phase.
© SAP AG
ADM326
14-77
--------------------------< I027631 MAY/03/09 >----------------------Phase: XPRAS_UPG
Description: You may get the following error message in phase XPRAS_UPG:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR700XP3.O64
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012X Program terminated (job: "RDDEXECL", no.: "20563602")
Long text:
Cause
Program "<(><<)>(><<(><<)>)>(><(><<)>(><(>&<)><(><<)>)><(><<)>(>
<<(><<)>)>)>V#&", which was started in the background, was terminated
abnormally.
Solution: Download lib_dbsl_<patch level>.sar (patch level must be at
least 38) from SAP Service Marketplace and replace the library
dboraslib.dll, then repeat the phase.
-------------------------< D023536 14/MAR/08 >-----------------------Phase: XPRAS_UPG (sourse release < 4.6C only)
Description: In certain cases, the shortdump
SAPSQL_ARRAY_INSERT_DUPRECmay occur in program "SAPLSBAL_DB_INTERNAL".
If you encounter this error, repeat the phase. If the error persists,
proceed as described in SAP Note 196113.
---------------------------------------------------------------------Phase: CHK_POSTUP
Note: 996953
Description: Log file LONGPOST.LOG asks you to migrate a CMOD project
although no project exists.
----------------------< D038245 FEB/28/06 >-------------------------Phase: MODPROFP_UPG
Description: When you are performing a dual-stack upgrade, in phase
MODPROFP_UPG, the ABAP stack is started together with the Java stack for
the first time. The phase may fail if the SAP J2EE Engine does not start
fast enough.
Check manually if the SAP J2EE Engine is running and if so, choose
"repeat" to repeat the upgrade phase.
----------------------------------------------------------------------
© SAP AG
ADM326
14-78
VII/ Problems After the Upgrade
This section addresses known problems that cannot be avoided using
preventive measures. These problems will only occur under specific
circumstances.
-----------------------< I036707 26/MAR/10 >-------------------------Missing instance.box.number in the instance.properties
After the upgrade, you might receive an error message when you try to
display the system details in the SAP NetWeaver Administrator.
To solve this problem, apply SAP Note 927561.
--------------------<enhanced D038245/JUNE/05 >--------------------------------------------< D003551 02/MAY/05 >------------------------Check Primary Index of Table MEMGMT_DEPLOYMNT
After the upgrade, check that the primary index of table
MEMGMT_DEPLOYMNT exists. If not, create the index manually.
If you still get the message that MEMGMT_DEPLOYMNT00 is an unknown
object in the dictionary, drop it on the database level.
------------------------< D020815 AUG/23/02 >------------------SPAU: Names of interface methods are truncated
Some methods (ABAP objects) that were modified and overwritten by the
upgrade can be displayed in transaction SPAU with their names shortened
to 30 characters.
As a result, the system may also incorrectly sort methods in SPAU under
"Deleted objects".
Caution: Deleted objects are not displayed in the standard selection in
SPAU. It is easily possible to overlook these!
For more information about the correction, see Note 547773.
---------------------------------------------------------------------Linux: Importing the new saposcol version
For more information, see Note 19227.
---------------------------------------------------------------------ReliantUNIX: saposcol version 32-bit or 64-bit
For more information, see Note 148926.
---------------------------------------------------------------------Solaris: saposcol version 32-bit or 64- bit
© SAP AG
ADM326
14-79
For more information, see Note 162980.
----------------------------------------------------------------------
© SAP AG
ADM326
14-80
VIII/ Chronological Summary
Date.....Topic..Short description
----------------------------------------------------------------------AUG/05/10...VI..Phase: JOB_RCIFSTKUREN2
JUL/15/10...VI..LONGPOST.LOG
MAY/05/10...VI..Phase: MAIN_NEWBAS/XPRAS_AIMMRG
MAR/26/10..VII..Missing instance.box.number in the instance.properties
OCT/15/09...VI..Phase CHK_POSTUP
MAY/03/09...VI..Phase: XPRAS_UPG
MAY/03/09...VI..Phase: SHDUNINST_DB
APR/23/09....V..Check if Matchcodes Exist in Your System
APR/17/09...VI..Phase: ACT_UPG
MAR/31/09...VI..Error in the EHP_INCLUSION Phase
MAR/31/09....V..Selecting the Target SPS Level in Maintenance Optimizer
DEC/09/08....V..Downloading Kernel DVDs for the Upgrade
NOV/21/08...II..Corrections and Repairs for the Upgrade
MAR/14/08...VI..Phase XPRAS_UPG - shortdump SAPSQL_ARRAY_INSERT_DUPREC
FEB/28/08...VI..Windows only: MSSERV_INTERN port numbers
FEB/25/08..VII..Error when Converting Print Parameters
JAN/17/08....V..Source Release SAP R/3 4.6C: Including a min. SP level
JUL/03/07....V..Parameter for the Central Syslog rslg/collect*
MAY/09/07....V..Preparations for FI-CA
MAR/15/07...II..MSCS Configuration
FEB/28/07...VI..Phase CHK_POSTUP - CMOD/SMOD migration
FEB/05/07....V..Back up customer-specific entries in table EDIFCT
DEC/18/06....V..New SPAM/SAINT Version on Source Release
AUG/28/06....V..Update SAP Kernel on Source Release
APR/24/06....V..Prepare table COEP for the upgrade
FEB/28/06...VI..Phase MODPROFP_UPG fails - check J2EE Engine
DEC/12/05....V..SD Texts: Check Text Customizing on Source Release
DEC/12/05..VII..Addition to the Release Notes
NOV/02/05....V..Kernel 6.40 with SuSE SLES 9 IA64 / RedHat 4.0 IA64
OCT/07/05...VI..Phase SHADOW_IMPORT_INC
SEP/22/05....V..Upgrading with reintegrated add-ons (retrofit)
SEP/21/05....V..Checking Application Log
AUG/16/05...VI..Windows only: KX_SWITCH - Check file NTPARVAL.LOG.
AUG/16/05....V..Windows only: Last profile text line - line feedback
JUL/13/05....V..Source Rel. ECC DIMP 5.0: MPN Conversion Exit
MAY/02/05..VII..Check Primary Index of Table MEMGMT_DEPLOYMNT
FEB/02/05...II..LSWM now part of SAP_BASIS
OCT/14/04....V..Source Rel. 4.0B: Project-Related Incoming Orders
© SAP AG
ADM326
14-81
OCT/14/04....V..Component PS-ST-WBS: Prel. Inclusion of Field KIMSK
OCT/06/04....V..Source Release 4.6C: SMODILOG Entries
© SAP AG
ADM326
14-82
SEP/09/04....V..Source Release Extension Set 1.10: Exchange containers
AUG/10/04...VI..Phase JOB_RDDNTPUR: TA22EQU_WAO without reference
APR/19/04....V..Unicode Systems: Downward Compatible Kernel 6.40
JAN/27/04....V..Upgrading with PI/PI-A
DEC/03/03...II..Windows only: Execute program R3dllins.exe
APR/24/03....V..Upgrade on AIX: saposcol
DEC/10/02....V..Upgrading with AIX 5.1
AUG/23/02..VII..SPAU: Names of interface methods are truncated
JUL/19/02...II..Problems with the shadow instance
MAY/23/02...VI..Phase CHK_POSTUP - objects without DDIC reference
APR/11/02...VI..Termination in the TOOLIMPD3 phase
FEB/20/02....V..Source releases on UNIX 32-bit or AIX 64-bit
OCT/19/00..VII..Linux: Importing the new saposcol version
FEB/16/00..VII..saposcol version 32-bit or 64-bit on Reliant UNIX
FEB/16/00..VII..saposcol version 32-bit or 64-bit on Solaris
----------------------------------------------------------------------
________________________________________________________________________
Valid releases
Software Component
Release
from
to
600
- 605
702
- 702
SAP_APPL
SAP Application
SAP_BASIS
SAP Basis component
________________________________________________________________________
Reference to related Notes
Number
Short text
____________________________________________________________
1475582 Migration tool for Travel Management for CEE countries
1349967 Upgrade to Business Suite 7 Innovation 2010: IBM DB2 for i
1299009 Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP 2
________________________________________________________________________
© SAP AG
ADM326
14-83
