Upgrade Guide SAP Enhancement Package 4 for SAP ERP 6.0 ABAP Based on SAP NetWeaver 7.0 Including Enhancement Package 1 For: n Windows n Oracle Target Audience n System administrators n Technology consultants PUBLIC Document version: 1.0 ‒ 11/21/2008
Transcript
1. Upgrade GuideSAP Enhancement Package 4 for SAP ERP 6.0
ABAPBased on SAP NetWeaver 7.0 Including Enhancement Package 1For:n
Windowsn OracleTarget Audiencen System administratorsn Technology
consultantsPUBLICDocument version: 1.0 11/21/2008
2. SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18
05/34 34 34 F +49/18 05/34 34 20 www.sap.com Copyright 2008 SAP AG.
All rights reserved. UNIX, X/Open, OSF/1, and Motif are registered
trademarks of the Open Group.No part of this publication may be
reproduced or Citrix, ICA, Program Neighborhood,
MetaFrame,transmitted in any form or for any purpose without the
WinFrame, VideoFrame, and MultiWin are trademarks orexpress
permission of SAP AG. The information contained registered
trademarks of Citrix Systems, Inc.herein may be changed without
prior notice. HTML, XML, XHTML and W3C are trademarks or
registeredNo part of this publication may be reproduced or
trademarks of W3C, World Wide Web Consortium,transmitted in any
form or for any purpose without the Massachusetts Institute of
Technology.express permission of SAP AG. The information contained
Java is a registered trademark of Sun Microsystems, Inc.herein may
be changed without prior notice. JavaScript is a registered
trademark of Sun Microsystems,Some software products marketed by
SAP AG and its Inc., used under license for technology invented
anddistributors contain proprietary software components of
implemented by Netscape.other software vendors. SAP, R/3, xApps,
xApp, SAP NetWeaver, Duet, PartnerEdge,No part of this publication
may be reproduced or ByDesign, SAP Business ByDesign, and other SAP
productstransmitted in any form or for any purpose without the and
services mentioned herein as well as their respectiveexpress
permission of SAP AG. The information contained logos are
trademarks or registered trademarks of SAP AG inherein may be
changed without prior notice. Germany and in several other
countries all over the world.Some software products marketed by SAP
AG and its All other product and service names mentioned are
thedistributors contain proprietary software components of
trademarks of their respective companies. Data containedother
software vendors. in this document serves informational purposes
only.Microsoft, Windows, Excel, Outlook, and PowerPoint are
National product specifications may vary.registered trademarks of
Microsoft Corporation. These materials are subject to change
without notice.IBM, DB2, DB2 Universal Database, System i, System
i5, These materials are provided by SAP AG and its affiliatedSystem
p, System p5, System x, System z, System z10, companies (SAP Group)
for informational purposesSystem z9, z10, z9, iSeries, pSeries,
xSeries, zSeries, eServer, only, without representation or warranty
of any kind, andz/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400,
S/390 SAP Group shall not be liable for errors or omissions
withParallel Enterprise Server, PowerVM, Power Architecture,
respect to the materials. The only warranties for SAP GroupPOWER6+,
POWER6, POWER5+, POWER5, POWER, products and services are those
that are set forth in theOpenPower, PowerPC, BatchPipes,
BladeCenter, System express warranty statements accompanying such
productsStorage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, and
services, if any. Nothing herein should be construed asRedbooks,
OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent constituting an
additional warranty.Miner, WebSphere, Netfinity, Tivoli and
Informix are This document was created using stylesheet
2007-12-10trademarks or registered trademarks of IBM Corporation.
(V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXONLinux is the
registered trademark of Linus Torvalds in the 6.5.2 from Michael
Kay (http://saxon.sf.net/), XSLT versionU.S. and other countries.
1.Adobe, the Adobe logo, Acrobat, PostScript, and Readerare either
trademarks or registered trademarks of Adobe DisclaimerSystems
Incorporated in the United States and/or other Some components of
this product are based on Java. Anycountries. code change in these
components may cause unpredictableOracle is a registered trademark
of Oracle Corporation.2/144 PUBLIC 11/21/2008
3. and severe malfunctions and is therefore expressly
Documentation in the SAP Serviceprohibited, as is any decompilation
of these components. MarketplaceAny Java Source Code delivered with
this product is You can find this document at the following
address:only to be used by SAPs Support Services and may not be
http://service.sap.com/instguidesmodified or altered in any
way.11/21/2008 PUBLIC 3/144
4. Aspects Covered by this GuideSAP Component Source ReleaseSAP
ERP SAP ERP Central Component Core 5.00 with SAP ERP Central
Component Extension Set 5.00Platform SAP R/3 Enterprise 4.70
Extension Set 2.00Windows SAP R/3 Enterprise 4.70 Extension Set
1.10 SAP R/3 4.6COperating SystemWindowsDatabaseOracle4/144 PUBLIC
11/21/2008
5. Typographic ConventionsExample Description Angle brackets
indicate that you replace these words or characters with
appropriate entries to make entries in the system, for example,
Enter your . Example Arrows separating the parts of a navigation
path, for example, menu optionsExampleExample Emphasized words or
expressionsExample Words or characters that you enter in the system
exactly as they appear in the documentationhttp://www.sap.com
Textual cross-references to an internet address/example Quicklinks
added to the internet address of a homepage to enable quick access
to specific content on the Web123456 Hyperlink to an SAP Note, for
example, SAP Note 123456Example n Words or characters quoted from
the screen. These include field labels, screen titles, pushbutton
labels, menu names, and menu options. n Cross-references to other
documentation or published worksExample n Output on the screen
following a user action, for example, messages n Source code or
syntax quoted directly from a program n File and directory names
and their paths, names of variables and parameters, and names of
installation, upgrade, and database toolsEXAMPLE Technical names of
system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a
programming language when they are surrounded by body text, for
example, SELECT and INCLUDEEXAMPLE Keys on the keyboard11/21/2008
PUBLIC 5/144
6. Document History CautionBefore you start the implementation,
make sure you have the latest version of this document. Youcan find
the latest version at the following location:
http://service.sap.com/instguides.The following table provides an
overview of the most important document changes.Version Date
Description1.0 11/21/2008 First version6/144 PUBLIC 11/21/2008
11. 1 Introduction1 Introduction1.1 Quick Access
RecommendationUse the checklist in the Quick Guide.The Quick Guide
[page 21] checklist provides you with an overview of all necessary
tasks inchronological order. If you need more information, follow
the links to the detailed descriptions.If you are experienced in
performing upgrades, the checklist may contain all you need to
knowto successfully perform the upgrade.1.2 About this
DocumentPurposeThis document describes the upgrade to SAP
enhancement package 4 for SAP ERP 6.0 ABAP fromSource Release SAP
R/3 4.6C and higher on Windows. NoteSAP enhancement package 4 for
SAP ERP 6.0 is based on SAP NetWeaver 7.0 including
enhancementpackage 1.The information in this document is intended
for SAP system administrators with operating system,database, and
SAP NetWeaver Application Server knowledge.IntegrationIf you want
to upgrade this component in the context of the upgrade of an SAP
Business Suiteapplication or one of its business scenarios, it is
essential that you familiarize yourself with thecontents of the
corresponding Upgrade Master Guide before starting to upgrade.
NoteTo find the latest version of this document and the Upgrade
Master Guide, see SAP Service Marketplaceat
http://service.sap.com/instguides.11/21/2008 PUBLIC 11/144
12. 1 Introduction1.2 About this DocumentIn addition to this
document, you also require other information, such as the Release
Notes for theapplications that you implement, the SAP
Implementation Guide (IMG), the SAP Notes that arespecific to this
upgrade, and any other documentation referred to in this
document.ConstraintsIf you want to upgrade from a non-Unicode SAP
system to a Unicode SAP system, you have toperform a special
procedure named Combined Upgrade & Unicode Conversion
(CU&UC). Formore information, see SAP Service Marketplace at
http://service.sap.com/unicode@SAPCombined Upgrade & Unicode
Conversion Library . Note An upgrade from a Unicode to a
non-Unicode SAP system is not possible. Only valid for: SAP R/3
4.6C;SAP R/3 4.70 Ext. Set 1.10;SAP R/3 4.70 Ext. Set 2.00For more
information about upgrading with MDMP or SAP blended code page, see
SAP Note 928729. End of: SAP R/3 4.6C;SAP R/3 4.70 Ext. Set
1.10;SAP R/3 4.70 Ext. Set 2.00The upgrade program does not support
the update of a system from SAP ERP 6.0 to SAP enhancementpackage 4
for SAP ERP 6.0. For this purpose, use the SAP Enhancement Package
Installer for 64-bitsystems, or transaction SAINT and the Java
Support Package Manager for 32-bit systems. You canfind the
corresponding document for this installation procedure on SAP
Service Marketplace at http://service.sap.com/erp-inst SAP ERP 6.0
SAP enhancement packages for SAP ERP 6.0 SAPenhancement package 4
for SAP ERP 6.0 .How To Use This Document Caution It is essential
that you use the Quick Guide [page 21] checklist to guide you
through the upgrade. It contains certain product-specific
information that is not repeated in the detailed descriptions.The
document on upgrading the SAP system contains a large amount of
information. Its aim is togive you both the information you need
immediately at your fingertips, as well as providing
additionalbackground information when required.The document is
structured as follows:n Chapter 1 Introduction This chapter
contains information about the document, new features of the
upgrade, some naming conventions for the document, and the SAP
Notes necessary for the upgrade.n Chapter 2 Quick Guiden Chapters 3
to 6 Component Upgrade This chapter contains information about how
to plan, prepare, and perform the upgrade and on follow-up
activities after the upgrade. It begins with the Quick Guide [page
21] checklist, which lists12/144 PUBLIC 11/21/2008
13. 1 Introduction1.3 Before You Start all activities in the
right order. This checklist also contains product-specific
information, for example, preliminary sizes for the upgrade
directory or database archives, and the list of necessary DVDs. For
more information about the single steps, follow the links in the
checklist. Note Activities that you have to perform for a specific
product only are marked with the product name in the title, for
example, : . Release numbers in these texts refer to the product
releases. Activities that are not marked with a product name in the
title apply to all upgrades of products using the relevant SAP
NetWeaver Application Server Release. Release numbers in these
texts refer to the underlying SAP NetWeaver Application Server.
Note If this document contains information for more than one source
release (see Aspects Covered by this Guide on page 4), texts that
apply to one or more source releases are marked with bars. These
bars always show all aspects for which the text is valid, even
though these aspects may not be of interest for your specific
upgrade.n Chapter A Reference This chapter contains a list of the
documentation referenced in this guide.1.3 Before You Start1.3.1
Naming ConventionsSAP ECC System and SAP SystemIn this document,
the term SAP system is the same as SAP ECC system. SAP is also used
as asynonym for SAP ECC in terms such as SAP start profile or SAP
system language.SAP System IDIn this document, the SAP system ID is
abbreviated as SAPSID or sapsid. If is used,your SAP system ID must
be in lowercase letters, for example prd. If is used, you mustwrite
in uppercase letters, for example PRD.ID for the SAP System
ReleaseIn this document, stands for the relevant SAP system
release, without a decimal point,such as 700.11/21/2008 PUBLIC
13/144
14. 1 Introduction1.3 Before You StartSAP R/3 Enterprise and
SAP ERP Central ComponentSAP ERP Central Component is the successor
of SAP R/3 Enterprise. It consists of the SAP ERPCentral Component
Core with SAP ERP Central Component Extension Set. In this
document,the following short forms are used:n SAP ECC for SAP ERP
Central Componentn SAP ECC Core for SAP ERP Central Component Coren
SAP ECC Extension Set for SAP ERP Central Component Extension
SetSAP NetWeaver Application Server, SAP Web Application Server,
and SAP BasisSAP NetWeaver 7.0 renames SAP Web Application Server
as SAP NetWeaver Application Server. Inreleases before 6.10, the
component had been called SAP Basis Component. In this document,
theterms are used as follows:n The term SAP NetWeaver Application
Server (or the short form SAP NetWeaver AS) is used when referring
to SAP NetWeaver 7.0 and higher.n The term SAP Web Application
Server (or the short form SAP Web AS) is used when referring to
Releases between 6.10 and 6.40. Only valid for: SAP Basis 4.6C;SAP
Basis 4.6D;SAP R/3 3.1I;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6Bn The
term SAP Basis (or the short form Basis) is used when referring to
Release 4.6D and lower. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP
R/3 3.1I;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6BReleaseUnless
otherwise specified, the term release is used in the
product-specific sections of this documentto refer to the release
of the SAP ECC system. The titles of product-specific sections
start with thename of the product, for example, SAP ECC: Backing Up
UI Conversion Classes in ESS.In the general sections of the
document, release is used to refer to the release of the SAP Basis,
SAPWeb Application Server, or SAP NetWeaver Application Server
system.The following table explains which release of SAP Basis, SAP
Web Application Server and SAPNetWeaver Application Server
corresponds to which release of SAP R/3 and SAP ECC: SAP Basis /
SAP Web Application Server / SAP NetWeaver Application Server SAP
R/3 / SAP ECC SAP Basis 4.6C SAP R/3 4.6C SAP Web Application
Server 6.20 SAP R/3 Enterprise 4.70 with SAP R/3 Enterprise
Extension Set 1.10 or SAP R/3 Enterprise Extension Set 2.00 SAP Web
Application Server 6.40 SAP ECC 5.00 SAP NetWeaver Application
Server 7.0 SAP ECC 6.00 SAP NetWeaver Application Server 7.0
including SAP ECC 6.04 enhancement package 114/144 PUBLIC
11/21/2008
15. 1 Introduction1.3 Before You Start1.3.2 New FeaturesNew
Features in the Upgrade Feature Description Availability Upgrade
procedure and handling The upgrade procedure and handling have SAP
NetWeaver changed significantly. Amongst others, the 7.0 including
changes are: enhancement n New user interface (upgrade GUI) package
1 for SAP n Upgrade phases are grouped into roadmap NetWeaver
steps. Troubleshooting and The troubleshooting and administration
SAP NetWeaver administration documentation documentation is
included in the upgrade 7.0 including included in the upgrade
program program. The upgrade tool unpacks the enhancement
documentation at the beginning of roadmap step package 1 for SAP
Extraction. You can access the documentation from NetWeaver the
HTML start page. Upgrade of dialog instances The procedure for the
upgrade of dialog instances SAP NetWeaver was changed. Phase
APPLSERV_CHK in roadmap step 7.0 including Configuration checks if
your dialog instances run on enhancement different platforms than
the central instance. If package 1 for SAP so, it unpacks the
relevant SAP kernel files to the NetWeaver subdirectory of the abap
subdirectory of the upgrade directory.1.3.3 SAP Notes for the
UpgradeDefinitionTo prepare and perform the upgrade of your SAP
system, you require some additional informationthat is not included
in this document. This information is in a range of SAP Notes in
SAP SupportPortal (http://service.sap.com/support), some of which
you must read before you preparethe upgrade. The central Upgrade
Note contains current cross-database and
cross-applicationinformation about preparing and performing the
upgrade. The applications-specific UpgradeNote contains current
application-specific information. There are separate SAP Notes for
thedatabase-specific sections. When you actually upgrade the SAP
system, you need information fromsome additional SAP Notes. These
SAP Notes are named at the appropriate places in this document.SAP
Notes for Preparing the UpgradeYou must request the following SAP
Notes from SAP Support Portal before you start your upgrade:n
Central Upgrade Note Contains the general upgrade problems and
information about the fix archive for the upgraden Upgrade Note for
your application Contains application-specific
information11/21/2008 PUBLIC 15/144
16. 1 Introduction1.3 Before You Startn SAP Note for your
databaseSince these SAP Notes are updated regularly, make sure that
you always use the newest version. Thefollowing list contains the
SAP Notes you need to prepare for the upgrade:SAP Notes for
Preparing the Upgrade on Oracle SAP Note Number Description Area
1146578 Central information about Specific to this upgrade
upgrading to SAP NetWeaver 7.0 including enhancement package 1 and
applications based on it 1156968 Additional information about
Specific to this upgrade upgrading to SAP enhancement package 4 for
SAP ERP 6.0 819655 Oracle Database-specific, specific to this
upgradeKeyword for the UpgradeWhen you start the upgrade, you are
asked to enter a keyword, which you can get from the currentUpgrade
Note for your application 1156968. You cannot start the upgrade
until you have entered thekeyword.Other SAP NotesAs well as the SAP
Notes you need for preparing the upgrade, this document also refers
you to otherSAP Notes that contain additional information. The
following lists contain these SAP Notes:SAP Notes for All Databases
SAP Note Number Description Area 778774 Resource requirements for
ECC 5.0 Performance 752532 Resource requirements for R/3
Performance Enterprise 4.70 x 2.00 517085 Resource requirements for
R/3 Performance Enterprise 4.70 x 1.10 323263 Resource requirements
for Release Performance 4.6C 178616 Resource requirements for
Release Performance 4.6B 151508 Resource requirements for Release
Performance 4.6A 113795 Resource requirements for Release
Performance 4.516/144 PUBLIC 11/21/2008
17. 1 Introduction1.3 Before You Start SAP Note Number
Description Area 89305 Resource requirements for Release
Performance 4.0A and 4.0B 544623 New installation of Unicode SAP
Unicode systems 1139642 Hardware requirements in Unicode Unicode
systems 835625 XSS backend UI conversion classes SAP ERP 928729
Combined Upgrade and Unicode SAP ERP conversion 849887 Release
Information Note SAP ERP SAP ERP 6.0 998833 Release Restrictions
SAP ERP 6.0 - SAP ERP Enhancement Packages 706952 Data migration
for CFM-TM or SAP ERP TR-TM 1165438 Enhancement package 4 for SAP
SAP ERP ERP: Required SWCV 156387 Composite Note on upgrade
HR-specific problems for the SAP component HR (Human Resources)
854170 Switching on component VM VM Container Container 844817
Technical information for AP 7.00 VMC-based AP 7.00 engines 844816
Upgrade from IPC 4.0 to SAP AP AP 7.00 7.00 147519 Maintenance
strategy / deadlines Front end/SAP GUI SAP GUI 178788 SAP GUI for
HTML delivery Front end/SAP GUI 26417 SAP GUI resources: Hardware
and Front end/SAP GUI software 102461 Installation of a 4.0B_COM
kernel SAP kernel 318846 Installation of a 4.6D kernel SAP kernel
664679 Installing SAP kernel 6.40 into a SAP kernel system using
SAP Web AS 6.20 211077 Exchanging the target release SAP kernel
kernel during the upgrade 19466 Downloading SAP kernel patches SAP
kernel11/21/2008 PUBLIC 17/144
18. 1 Introduction1.3 Before You Start SAP Note Number
Description Area 19227 Getting the latest saposcol saposcol 816211
STARTUP script on Windows systems Start of the upgrade 816806 SAP
ECC 5.00 Extension Set: SAP ECC Extensions Activation switch 86985
SAP release for add-ons (IS) SAP add-ons 83458 Downloading Support
Packages SAP Support Packages from SAP Service Marketplace 774615
Support Package levels for SAP ERP SAP Support Packages / SAP ECC
installations / upgrade 62519 Correction locks do not belong to
Workbench Organizer system 51046 Copying the modification Change
and Transport System adjustment without a central transport
directory 96905 Error message TG063 in the ABAP Dictionary upgrade
phase JOB_RADDRCHK 867521 Upgrading an MSCS SAP system to MSCS SAP
NetWeaver 7.0 352295 Microsoft Windows Single Sign-On Single
Sign-On options 595341 Installation issues with Single Single
Sign-On Sign-On and SNC 24864 No conversion of table BSEG ABAP
Dictionary/phase PARCONV_UPG 10187 User buffer too small User
administration 197746 Maintenance Strategy Internet SAP@Web
Transaction Server (ITS) 399578 Publishing IAC objects on the ITS
SAP@Web after the upgrade 1015959 Current Note for language
Language transport transport 352941 Language import and Support
Language transport Packages 322982 Installing language during
upgrade Language transport 485741 Dealing with customer
translations Language transport in the upgrade 949463 Repairs for
upgrades General upgrade18/144 PUBLIC 11/21/2008
19. 1 Introduction1.3 Before You Start SAP Note Number
Description Area 1031160 Additional information about General
upgrade resetting the upgrade 186066 Increased free space
requirements General upgrade during the upgrade 175596 Switch to a
new batch input log General upgrade 712297 Short dumps when
restoring General upgrade variants 195157 Deleting application logs
General upgrade 1000009 ASU Toolbox 2008 General upgrade 813445
Documentation of report General upgrade UMG_POOL_TABLE 821875
Security settings in the message General upgrade server 485455
Change in code page structure for General upgrade Releases >=
6.10 511732 Removed code pages in 6.10 General upgrade 28022
Customer system: Where-used list General upgrade of SAP objects
493387 Potential effects of changes to table Activation and
structure extensions 490788 ICNV in the upgrade to SAP Web ICNV AS
6.20 and higher 922557 Making changes to enhancements Enhancements
178482 Upgrade from 3.0 to 4.0 for Adjusting customer developments
customer programs 178452 Upgrade from 4.0 to 4.5 for Adjusting
customer developments customer programs 178725 Upgrade from 4.5 to
4.6 for Adjusting customer developments customer programs 367676
Upgrade from 4.6 to 6.10 for Adjusting customer developments
customer programs 452229 Upgrade from 6.10 to 6.20 for Adjusting
customer developments customer programs 689951 Upgrade from 6.20 to
6.40 for Adjusting customer developments customer programs 857904
Upgrade from 6.40 to 7.0 for Adjusting customer developments
customer programs11/21/2008 PUBLIC 19/144
20. 1 Introduction1.3 Before You Start SAP Note Number
Description Area 805390 SAP Solution Manager is required SAP
Solution Manager for all SAP applications 1005238 Migration of
workload statistics Data Migration data to NW2004s 1006116
Migration of workload statistics Data Migration data to NW2004s (2)
1165059 ALE changepointer Data Migration 1240081 Java Cryptography
Extension SAP JVM Jurisdiction Policy FilesSAP Notes for Oracle SAP
Note Number Description Area 829483 Oracle upgrade to 10g on
Windows Oracle-specific 833766 Oracle Database 10g: Software
Oracle-specific Installation ProblemsOptional SAP Notes for Windows
SAP Note Number Description Area 690432 Windows 2003 support
Windows 2003-specific 28781 Central transport directory Mixed
systems NT/UNIX 65761 Configuration test tool for System
configuration Windows, sapntchk download 430992 Shadow instance on
another host: Upgrade under Windows Windows 138498 Single Sign-On
Solutions Single Sign-On20/144 PUBLIC 11/21/2008
21. 2 Quick Guide2 Quick GuideThis section contains a checklist
with all the actions you need to perform:n Find SAP Notesn Plan the
upgraden Prepare the upgraden Upgrade the SAP systemn Perform the
follow-up activitiesThe actions are in chronological order, so that
you can work through them like a checklist. For moreinformation,
follow the links to the descriptions of the actions.You can also
use the checklist to get a quick overview of the upgrade process.
RecommendationIf you are experienced in performing upgrades, the
checklist may contain all you need to knowto successfully perform
the upgrade.ChecklistSAP Notes for the UpgradeThis upgrade document
is enhanced and updated by SAP Notes from SAP Support
Portal(http://service.sap.com/support). These SAP Notes are an
important source of information whenyou plan and prepare your
upgrade, and also help you perform the actual upgrade.o 1. You
request the current SAP Notes for the Upgrade [page 15]. You
require at least the following SAP Notes: n Central Upgrade Note
1146578 n Upgrade Note for your application 1156968 n The relevant
database-specific SAP Note 819655Upgrade PlanningBefore you start
the actual upgrade, you must plan it carefully so that downtime is
reduced to aminimum, and the upgrade runs as efficiently as
possible. CautionStart planning your upgrade at least two weeks
before you want to begin with the upgrade.11/21/2008 PUBLIC
21/144
22. 2 Quick Guideo 1. You can upgrade the front-end software
[page 32] as soon as you receive the software package.o 2. You
familiarize yourself with the features of the System Switch Upgrade
[page 34] and its effect on the way you upgrade the system, with
the upgrade roadmap [page 36], and the upgrade GUI.o 3. You decide
on a preconfiguration mode [page 39].o 4. Before you start the
upgrade, you check the database-specific aspects [page 41] and
include them in your upgrade schedule, if necessary. Archive Sizes:
35 GB up to the DOWNCONF_TRANS phase and 43 GB to the end of the
upgrade. These sizes are an estimation based on sample data.o 5.
You check whether your system is an MCOD system [page 42].o 6. You
plan data management measures [page 42] to reduce the amount of
data, if necessary.o 7. You plan the incremental table conversion
[page 43] for ABAP tables, if necessary.o 8. You plan the upgrade
schedule [page 45]. Start your preparations for the upgrade at the
latest two weeks before you upgrade your system. Each language that
you import increases the minimum duration of the import by about 30
minutes.o 9. You decide on the sequence of upgrades in your SAP
system group [page 47].o 10. You plan the modification adjustment
[page 47] for ABAP, if necessary.o 11. You check the structural
requirements [page 50] for ABAP: You call transaction RZ10 to check
the values of the profile parameters rdisp/mshost and
rdisp/wp_no_vb.o 12. You check the hardware requirements: [page 51]
n CPU, main memory, and page file see SAP Service Marketplace at
http://service.sap.com/sizing n Disk space in the file system for
the upgrade directory (standard path usrsapupg): Make sure that you
have about 7000 MB of temporary disk space in the file system for
the upgrade directory. n Space requirements in the database
(estimation): 50 GB during the upgrade.o 13. You check the software
requirements. n Source release [page 52] of the SAP system: l SAP
R/3 4.6C l SAP R/3 Enterprise Core 4.70 with SAP R/3 Enterprise
Extension Set 1.10 l SAP R/3 Enterprise Core 4.70 with SAP R/3
Enterprise Extension Set 2.00 l SAP ERP Central Component 5.00 with
SAP ERP Central Component Extension Set 5.00 n You plan or perform
the upgrade of the operating system and database system [page 53]
if necessary: For more information about which operating system and
database versions are currently supported, see SAP Service
Marketplace at http://service.sap.com/platforms and the Product
Availability Matrix at http://service.sap.com/PAM. Database
version: At least Version 10.2.0.2 for the upgrade; you can run up
to roadmap step Checks with Version 9.2.0 or higher22/144 PUBLIC
11/21/2008
23. 2 Quick Guideo 14. You make sure that you can access the
online documentation [page 53] for the SAP NetWeaver / SAP Web
Application Server of your source release and target release. You
may also need to access the online documentation for your
application release. You can find it on SAP Help Portal at
http://help.sap.com SAP Business Suite .o 15. You plan the use of
SAP Solution Manager [page 55] in your system landscape.o 16. You
meet the requirements for the SAP Internet Transaction Server [page
56] as described in the SAP@Web Installation Guide, if necessary.
See the corresponding Upgrade Master Guide to find out whether you
require the SAP Internet Transaction Server for your business
scenario.o 17. You plan the synchronized upgrade of a dual-stack
system [page 57], if necessary.o 18. You meet the requirements for
importing additional languages [page 59] for ABAP, if necessary.o
19. You plan the handling of customer-specific translations [page
60] and Z languages in ABAP during the upgrade. Only valid for: SAP
R/3 4.6Co 20. You note the changes in the SAP Support Package
structure [page 61] as of Release 4.6. End of: SAP R/3 4.6Co 21.
You check the Support Package or patch level [page 62] of the
components included in the upgrade export.o 22. You plan the use of
the application-specific update toolbox [page 62] (ASU toolbox).o
23. You check the architectural changes for the Internet Pricing
and Configurator [page 63].Upgrade PreparationsYou can prepare for
the upgrade while the system is in production operation. The
upgrade programsupports you here by making most of the necessary
checks automatically. Run the first four roadmapsteps of the
upgrade as soon as possible before the actual upgrade so that you
can initiate or performthe necessary preparations in time.Actions
Before Starting the Upgrade Programo 1. You choose the host [page
66] for the upgrade.o 2. You note the exceptions when upgrading
with Microsoft Cluster Server [page 66].o 3. You make sure that the
requirements for the modification adjustment [page 67] have been
met.o 4. You fill the download directory [page 67].o 5. You
download enhancement packages [page 68].o 6. You meet the
requirements for the upgrade directory [page 71].o 7. You generate
the SAP Solution Manager key [page 71]. Only valid for: SAP ECC
5.00o 8. You initialize fields in table COKEY2 [page 72]. End of:
SAP ECC 5.0011/21/2008 PUBLIC 23/144
24. 2 Quick Guide Only valid for: SAP Web AS 6.20;SAP Web AS
6.40o 9. Unicode SAP systems with source release SAP Web AS 6.20
and 6.40: You run reports RUTTTYPACT and UMG_POOL_TABLE [page 72],
if necessary. End of: SAP Web AS 6.20;SAP Web AS 6.40 Only valid
for: SAP Basis 4.6C;SAP Web AS 6.20;SAP Web AS 6.40o 10. You
prepare the migration of the workload statistics data [page 73] of
the ABAP part of the SAP system. End of: SAP Basis 4.6C;SAP Web AS
6.20;SAP Web AS 6.40o 11. You check the consistency of the host
name [page 73]o 12. You call transaction RZ04 to set the operation
mode [page 74] for the upgrade.o 13. You download the JCE
Jurisdiction Policy Files [page 75]o 14. You make sure that the
page file is large enough. For more information, see Changing the
Virtual Memory/Paging File Size in the document Troubleshooting and
Administration [page 53].o 15. You make the preparations at the
database level [page 76].o 16. You make the preparations at the SAP
system level [page 77]: n You delete the AUTOSTART parameter [page
77]. n Optional: You delete application logs [page 77]. n For HR
customers only: You back up table T512W [page 78] (wage types in
HR). Only valid for: SAP ECC 5.00 n You back up UI conversion
classes [page 79] in ESS. End of: SAP ECC 5.00 n You import the new
front-end software [page 32], if necessary.Upgrade ProcessActions
for Starting and Using the Upgrade Programo 1. You start the
upgrade from the Upgrade Master DVD [page 82] as user adm on the
host with the AS instance.o 2. You start the upgrade GUI [page 83].
You can restart the upgrade [page 84] or reset the upgrade [page
85]. If you need extra software after starting the upgrade, you
import or install [page 86] it now.User Actions During the
Extraction Roadmap StepYou make the entries for the Extraction
[page 86] roadmap step.To perform the roadmap step, the upgrade
program needs certain information from you so that itcan perform
the upgrade. If possible, default values appear that you can
confirm or change.For a complete list of all phases, see Using the
ABAP Phase List for the Upgrade in the document Troubleshootingand
Administration [page 53].24/144 PUBLIC 11/21/2008
25. 2 Quick Guideo 1. This includes entering the keyword from
the current Upgrade Note for your application 1156968.o 2. You
enter mount directories. You require the data carriers listed in
the following tables: Data Carriers Required by the Upgrade Program
DVD Contents Needed Upgrade Master DVD for SAP ERP and Start DVD
with upgrade tools your database SAP Kernel DVD for SAP NetWeaver
and your Programs and configuration files for the upgrade operating
system DVD containing the upgrade export Transport requests
imported during the upgrade DVD containing the languages All
supported languages For the correct labels of the data carriers,
see the Media List which is included in the Master Guide of your
SAP solution.o 3. You enter the password for user DDIC.User Actions
During the Configuration Roadmap StepYou continue with the roadmap
step Configuration [page 88].To perform the roadmap step, the
upgrade program needs certain information from you so that itcan
perform the upgrade. If possible, default values appear that you
can confirm or change.o 1. You enter paths and parameters [page
88]. This includes the following: n You choose your
preconfiguration mode [page 39]. n You enter the port number for
internal communication. n You enter the password for the operating
system user for installing the shadow instance. n You enter the
password for user system. n You check the version of the SAP
kernel, tp, and R3trans. n You enter the Solution Manager key. n
You check the SAP Notes for the add-ons. n For the SAP ECC
Extension Add-Ons listed in phase IS_SELECT, you can use the
standard settings. n If you are running an MCOD system, confirm the
question. n If you perform a Combined Upgrade & Unicode
Conversion, confirm the question.o 2. You specify the software you
want to include [page 92] in the upgrade. n You enter mount
directories for the languages. n You check the SPAM version. n You
upload additional packages. n You decide about the add-ons. n You
confirm the Support Packages, if necessary. n You include
enhancement packages, if necessary.11/21/2008 PUBLIC 25/144
26. 2 Quick Guide n You enter the request for the modification
adjustment, if necessary.o 3. You make entries for the shadow
instance installation [page 97]. n You decide about reusing the
shadow instance profiles.User Actions During the Checks Roadmap
StepYou continue with the roadmap step Checks [page 98] and make
entries if necessary. At the end of thestep, perform the user
actions requested on the SDTExecution Intervention screen.o 1.
Microsoft Cluster Server (MSCS): You make the entries for the MSCS
configuration.o 2. You decide about using the RASUVAR reports to
save variants.o 3. You check the results of the system
check.Actions After Performing the Preparation Roadmap StepsYou
have to perform the following checks that are not supported by the
upgrade program:o 1. You evaluate the results of the preparation
roadmap steps [page 99] in the window that appears after the Checks
roadmap step has completed.Actions During the Preprocessing Roadmap
StepYou continue with roadmap step Preprocessing [page 104].o 1.
You check the central and the product-specific Upgrade Notes and
your database-specific SAP Note for new information and changes.o
2. You confirm any unconfirmed Support Packages.o 3. You enter the
keywords for add-ons, if necessary.o 4. You update your operating
system or database to the required version now at the latest, or
you import any software you still need.o 5. You remove conflicts
between customer tables and new views by deleting the customer
tables.o 6. You release the locked objects and confirm repairs. You
must do this in the REPACHK2 phase at the latest.o 7. You clean up
outstanding updates. You must do this in the JOB_RSVBCHCK_R or
JOB_RSVBCHCK_D phase at the latest.o 8. You make sure that you can
recover the old SAP kernel if this becomes necessary.o 9. For
standard resource use or high resource use: You lock the ABAP
Workbench. You must do this in the REPACHK2 phase at the latest.o
10. n You release and confirm all open repairs in phase REPACHK2 at
the latest. n For downtime-minimized: You lock the ABAP Workbench
in phase REPACHK2 at the latest.o 11. You process any uncompleted
conversion requests and restart logs.o 12. Modifications: You
confirm the request, if necessary.o 13. Phase START_SHDI_FIRST: As
of this phase you can only log on with front-end software [page 32]
that is compatible with the target release.o 14. You remove
conflicts between customer tables and new views by deleting the
customer tables in this phase at the latest.26/144 PUBLIC
11/21/2008
27. 2 Quick Guideo 15. You start the ICNV, if necessary.o 16.
You are asked to isolate the central instance, stop the application
servers, and back up the directory usrsap including the complete
upgrade directory.Actions During the Downtime Roadmap StepYou
continue with roadmap step Downtime [page 108].o 1. You change the
database recovery mode, if necessary. Make sure that you can
restore the database to this point. You back up the directory
usrsap including the upgrade directory. You check the percentage of
tables converted in transaction ICNV, if necessary.o 2.
Modifications: You adjust modified SAP objects with the SAP
standard versions.o 3. If you run a high availability system, you
stop the ASCS instance.o 4. If you run a high availability system,
you install the latest SAP kernel on the host with the ASCS
instance and restart the instance.o 5. The upgrade program asks you
to perform the following actions: n You back up the database. n You
change the database recovery mode. n You start the dialog
instances.Actions During the Postprocessing Roadmap StepYou
continue with roadmap step Postprocessing [page 112].o 1. You
generate loads [page 133] for your SAP system.o 2. You remove the P
errors.o 3. Optional: You send the evaluation of the upgrade
runtime to SAP.Follow-Up ActivitiesThe upgrade program stops at the
latest in the MODPROFP_UPG phase and prompts you to start
thefollow-up activities. The upgrade program then executes the last
phases and completes the upgrade.At the same time you can perform
the follow-up activities specified by the upgrade program.Actions
Before Restarting Production Operationo 1. You perform the
database-specific actions [page 117]: Amongst others, you create or
update the SAPDBA role, check the environment variables for
BR*Tools, and back up the database.o 2. Microsoft Cluster Server
(MSCS): You perform the follow-up activities [page 118].o 3. You
perform the follow-up activities for the SAP Kernel [page 118].o 4.
You perform follow-up activities in the monitoring area [page
119].o 5. You activate the ICM service [page 119].o 6. You install
the Java components [page 120] if necessary.o 7. You reimport
additional programs [page 120] such as RFC-SDK or CPIC-SDK from the
SAP NetWeaver Presentation DVD, if necessary.o 8. You call
transaction SPAU to adjust modifications to Repository objects
[page 120], if necessary.11/21/2008 PUBLIC 27/144
28. 2 Quick Guideo 9. You perform follow-up activities for the
SAP system security [page 121], if necessary.o 10. You check
application Release Notes [page 121] for specific follow-up
activities.o 11. You adjust the Customizing settings [page 122].
Only valid for: SAP Basis 4.6C;SAP Basis 4.6Do 12. You convert your
customer-specific codepages [page 122], if necessary. End of: SAP
Basis 4.6C;SAP Basis 4.6Do 13. You adjust your own developments
[page 123], if necessary.o 14. You update the where-used list [page
123], if necessary. Only valid for: SAP Basis 4.6C;SAP Web AS
6.20;SAP Web AS 6.40o 15. You migrate the workload statistics data
[page 124] of the ABAP part of the SAP system. End of: SAP Basis
4.6C;SAP Web AS 6.20;SAP Web AS 6.40o 16. You discuss the
activation of SAP ECC Extensions [page 124] with your business
consultants and the project team. Caution You cannot deactivate a
switch once it has been activated.o 17. HR customers: You restore
table T512W [page 124] (wage types in HR)o 18. SAP Retail
customers: You convert short texts [page 125].o 19. SAP
TR-TM/CFM-TM customers: You migrate specific data [page 125].o 20.
You perform follow-up activities for SAP Solution Manager [page
125].o 21. Configure Single Sign-On with the Microsoft LAN Manager
SSP [page 125], if necessary.o 22. You execute the conversion
program for the product master [page 129]. Only valid for: SAP
Basis 4.6C;SAP Basis 4.6Do 23. You migrate data to table TVARVC
[page 131]. End of: SAP Basis 4.6C;SAP Basis 4.6Do 24. You activate
the VMC for the Internet Pricing Configurator [page 131], if
required.Actions After Restarting Limited Production OperationYou
can perform the following follow-up activities during limited
production operation of the system.o 1. You reschedule background
jobs [page 132] that were locked when you isolated the central
instance.o 2. You perform actions for the Cost-Based Optimizer
[page 132].o 3. You generate loads [page 133] using transaction
SGEN and report RSGENINVLAS.o 4. You install the online
documentation [page 135] for the target release.o 5. You configure
the SAP Internet Transaction Server [page 56] and migrate
applications, if necessary.o 6. You perform follow-up activities in
the authorizations area [page 135]: n You adjust the assignments
between check flags and transactions. n Upward compatibility for
authorization checks: You adjust SAP_NEW. n You handle problems
with user buffers.28/144 PUBLIC 11/21/2008
29. 2 Quick Guide n You set up additional users. Only valid
for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3
4.6C;SAP Web AS 6.20;SAP Web AS 6.40o 7. You perform follow-up
activities for Application Link Enabling (ALE) [page 137]. End of:
SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.6C;SAP
Web AS 6.20;SAP Web AS 6.40o 8. You use SAPinst to upgrade or
install dialog instances [page 138].Actions After Restarting
Production OperationYou can perform the following follow-up
activities during normal production operation of thesystem.o 1. You
import Support Packages [page 138], if necessary. If you want to
install additional languages in your ABAP system, you import them
before you import the Support Packages as described in the language
transport documentation. For more information about SAP ERP 6.0
Support Packages Stacks, see the Release Information Note 849887.o
2. Transport Management System (TMS) [page 139]: You distribute the
configuration to all systems in the transport domain.o 3. Language
transport [page 139]: You copy glossary and terminology data from
container tables to database tables.o 4. You delete old tablespaces
[page 140].o 5. You save files [page 141] for follow-up upgrades,
if necessary.o 6. You make a backup of the subdirectory that
contains the shadow instance profiles [page 141], if
necessary.11/21/2008 PUBLIC 29/144
30. This page is intentionally left blank.
31. 3 Planning3 PlanningThis part of the document contains
information about planning your upgrade.Before you begin the actual
upgrade, you must first plan it carefully. This includes requesting
all theSAP Notes you need. Careful planning is a prerequisite for a
successful SAP system upgrade.The following information helps you
plan your upgrade so that downtime is reduced to a minimum,and the
upgrade runs as efficiently as possible. NoteTeamSAP offers the
free upgrade service SAP GoingLive Functional Upgrade Check. A team
ofexperts checks the parameter settings of your system in one
session before the upgrade, and givesyou detailed recommendations
on the configuration. After the upgrade, the parameters and
theentire system status are checked again in a second session. For
information about the service and onordering it, see SAP Support
Portal at http://service.sap.com/goinglive-fu.When you plan your
upgrade, note the following information in addition to the
information inQuick Guide [page 21]:n All the times specified in
this document are based on hardware with medium performance
levels.n Do not perform any additional actions during the upgrade
that could cause it to run less smoothly.n Start planning your
upgrade in good time.n To make sure that all requirements are met,
run the preparation roadmap steps of the upgrade program,
Initialization, Extraction, Configuration, and Checks, as soon as
possible. You can reset and repeat the preparation roadmap steps as
often as you need by choosing Back before you start the actual
upgrade in roadmap step Preprocessing. The successful execution of
the preparation roadmap steps is a prerequisite for starting the
upgrade in roadmap step Preprocessing.n If you are upgrading a
modified system where changes have been made to the standard ABAP
system, you must start by upgrading a development or quality
assurance system that has the same SAP system release (including
Support Package level), and contains the same modifications. The
adjustments you perform manually for the new standard in this
system can be automatically exported to the global transport
directory and are integrated into the production system upgrade
from there. This procedure eliminates the need for time-consuming
adjustments to the production system.n If it is technically
possible, or unless otherwise specified, we recommend that you
upgrade the operating and database system and your SAP system at
different times.Actions11/21/2008 PUBLIC 31/144
32. 3 Planning3.1 Time Frame for Upgrading the Front-End
SoftwareThe following sections are important for planning the
upgrade:n Time Frame for Upgrading the Front-End Software [page
32]n System Switch Upgrade [page 34]n Upgrade GUI and Roadmap Steps
[page 36]n Preconfiguration Mode Planning [page 39]n
Database-Specific Aspects [page 41]n Upgrades in an MCOD System
Landscape [page 42]n Data Management Planning [page 42]n
Incremental Table Conversion [page 43]n Upgrade Schedule Planning
[page 45]n Upgrade in an SAP System Group [page 47]n Modification
Adjustment Planning [page 47]n Checking the Structural Requirements
[page 50]n Checking the Hardware Requirements [page 51]n Checking
the Software Requirements l Checking the Source Release of the SAP
System [page 52] l Meeting the Operating System-Specific
Requirements [page 52] l Upgrading the Operating System and
Database System: Overview [page 53]n Accessing Documentation [page
53]n Using SAP Solution Manager [page 55]n Meeting the Requirements
for the SAP Internet Solution [page 56]n Synchronized Upgrade of
Dual-Stack SAP Systems [page 57]n Importing Additional Languages
[page 59]n Handling of Customer-Specific Translations and Z
Languages in the Upgrade [page 60] Only valid for: SAP R/3 3.1I;SAP
R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6B;SAP R/3 4.6Cn SAP ECC: Support
Packages [page 61] End of: SAP R/3 3.1I;SAP R/3 4.0B;SAP R/3
4.5B;SAP R/3 4.6B;SAP R/3 4.6Cn Component Levels Contained in the
Upgrade Export [page 62]n Using the Application-Specific Update
Toolbox [page 62]n Internet Pricing and Configurator [page 63]Back
to Quick Guide [page 21]3.1 Time Frame for Upgrading the Front-End
SoftwareThe new SAP system release cannot run until a compatible
version of the front-end software (SAPGUI) has been installed.
However, as the front-end software is compatible with several SAP
systemreleases, you may not have to upgrade to a new front-end
software release.If you need or want to use a different front-end
software, you can import it as soon as you receivethe software
package. If the front-end software you are using on the source
release is not compatible32/144 PUBLIC 11/21/2008
33. 3 Planning3.1 Time Frame for Upgrading the Front-End
Softwarewith the target release, the latest possible time for
upgrading the front-end software is before youstart the shadow
system for the first time in the START_SHDI_FIRST phase during
roadmap stepPreprocessing. If you choose preconfiguration mode
standard resource use or high resource use, this phase ispart of
roadmap step Preprocessing. If you choose preconfiguration mode low
resource use, this phase ispart of roadmap step Downtime.This
graphic shows the time period during which you can upgrade the
front-end software:Figure 1: Time Frame for Upgrading the Front-End
SoftwareThe front-end software is upgraded directly from a data
carrier or from a file server. Note You can use the SAP Front-End
installation software, NWSAPSetup, to optimize the deployment of
SAP GUI to thousands of clients. You can tailor installation
packages to match your requirements, distribute patches, and set up
automatic update processes for your clients.More Information Which
front-end software to use SAP Note 147519 Hardware and software
requirements SAP Note 26417 Using SAP GUI for HTML SAP Note 178788
and Meeting the Requirements for the SAP Internet Solution [page
56] Installing the front-end software and using SAP Front End
Installation Guide NWSAPSetup11/21/2008 PUBLIC 33/144
34. 3 Planning3.2 System Switch UpgradeBack to Quick Guide
[page 21]3.2 System Switch UpgradeSAP systems are upgraded with the
System Switch Upgrade procedure. This procedure installs aninstance
of the target release, the shadow system, in parallel with the
current source release system inthe same database. The parallel
system contains all the software of the target release and is used
toperform actions on the target release while the source release is
still in production operation.Operating two instances in parallel
places increased demands on free space in the file system, in
thedatabase, and on the system resources. If necessary, some
parameters in the production system mightneed to be adjusted to
enable you to operate the production and the shadow systems in
parallel.No precise guidelines can be given for the duration of an
upgrade. The duration of the individualactions depends to a great
extent on the individual system, the number of modifications, and
thenumber of included Support Packages and add-ons.In the
production database, the tables of the target release that contain
both the descriptions ofthe ABAP Dictionary and the ABAP programs
are imported as shadow tables under an alternativename. The shadow
system enables you to access these tables. If you choose
preconfiguration modestandard resource use or high resource use,
you can perform upgrade actions before downtime starts,
whichpreviously had to be performed during downtime. During the
EU_SWITCH phase in downtime, theswitch is made to the new system,
and any remaining data is imported. Any parts of the source
releasesystem that are no longer needed are deleted.Figure 2:
Process Flow of a System Switch UpgradeFeaturesABAP System Upgraden
Extended free space check34/144 PUBLIC 11/21/2008
35. 3 Planning3.2 System Switch Upgrade The Checks roadmap step
of the upgrade program also checks the free space needed for tables
created in the shadow system.n Creating the shadow system The
Configuration roadmap step of the upgrade program is used to
prepare for the shadow instance. The upgrade program first creates
profiles, directories, as well as an extra database user, and
copies programs and files needed by the shadow instance. All tables
of the SAP NetWeaver Application Server are needed as shadow tables
to operate the shadow system. As well as all substitution tables
already imported, and the newly created tables, the upgrade program
also creates all remaining SAP NetWeaver Application Server tables
and fills them. When all the required tables are in the shadow
system, aliases, synonyms or views are created for them. Additional
table contents are copied into the shadow system to enable
adjustment, activation and distribution functions in the shadow
system.n Operating the shadow system You can now use the shadow
system to perform the modification adjustment of the ABAP
Dictionary objects and activate and distribute the requests
included in the upgrade. After you have operated the shadow system,
you have a consistent inactive nametab with the descriptions of the
table structures of the target release, including Support Packages
and add-ons. While it is running, the shadow system writes to a
number of ABAP tables whose contents are required for the remainder
of the upgrade, and for operating the system afterwards. These
tables are renamed with their original names in the EU_SWITCH
phase.n ABAP table conversion All tables of the SAP NetWeaver
Application Server ABAP whose contents need to be copied from the
shadow system can be adjusted to the target release structure in
the shadow system during production operation. Even the tables into
which control data is imported already exist in the shadow system
and only need to be renamed. The tables that need to be converted
are those for which the original versions of the SAP NetWeaver
Application Server will continue to be used. These tables can be
converted during production operation by being copied to the shadow
system, or converted externally. External conversion no longer
needs the ABAP conversion program of the source release, which
means that the activation and conversion of the SAP NetWeaver
Application Server only uses target release tools. This removes the
restrictions of the previous procedure, such as no modifications to
the SAP NetWeaver Application Server in Support Packages and
add-ons. As before, the application tables are converted during
downtime in the PARCONV_UPG phase. They can be distributed during
production operation. If you use the ICNV, the tables are converted
during production operation.n After operating the ABAP shadow
system Any ABAP tables that receive entries are created as copies
with new formats in the shadow system. The upgrade then performs
the shadow import. Modifications to the contents of the original
tables are indicated by triggers. These tables must be copied and
imported during downtime.n Actions on the ABAP system during
downtime11/21/2008 PUBLIC 35/144
36. 3 Planning3.3 Upgrade GUI and Roadmap Steps After the
upgrade program has converted the data and made all preparations,
it completes the copy import action during downtime for all tables
with triggers set. The EU_SWITCH phase completes the switch to the
new system. All tables prepared in the shadow system are copied to
the target release. The KX_SWITCH_1 phase switches the SAP kernel.
The PARCONV_UPG phase converts the application table and the phase
TABIM_UPG imports the remaining data. Finally, the XPRAS_UPG phase
starts the XPRAs required by the system.Back to Quick Guide [page
21]3.3 Upgrade GUI and Roadmap StepsThe upgrade GUI provides you
with functions to monitor the upgrade and navigate through
theroadmap steps of the upgrade.Figure 3: Upgrade GUIThe upgrade
phases are grouped into modules, which in turn are grouped into
roadmap steps. Theupgrade consists of eight roadmap steps that run
sequentially and are described briefly below. NoteRoadmap steps 1
to 4 correspond to the previously used PREPARE program and are
called thepreparation roadmap steps.36/144 PUBLIC 11/21/2008
37. 3 Planning3.3 Upgrade GUI and Roadmap StepsFeaturesUpgrade
GUIThe upgrade GUI consists of the following main elements:n Menu
bar The menu bar offers you options that you need to work with the
upgrade GUI and the upgrade program. It has the following entries:
l File l Upgrade Under Upgrade, you can find the following
functions: u Stop Upgrade The upgrade program stops immediately.
When you restart the upgrade as described in Starting the Upgrade
Program [page 82], the upgrade continues at the point where you
stopped it. u Reset Upgrade Using this menu option, you can reset
the upgrade as described in Resetting the Upgrade [page 85]. u Logs
From here, you have direct access to the upgrade logs. l ABAP Here
you can start the upgrade program with options and set or remove a
breakpoint for a certain phase. You can also access the log files
of the upgrade program. l Help You can access online help for the
upgrade phases and the SAP Notes Search on the SAP Support Portal.n
Roadmap The roadmap visualizes the roadmap steps. The roadmap step
that is currently running is highlighted.n Tab pages You see the
following tab pages: l Monitor The monitor tab page displays a
progress bar for the upgrade program. The progress bar shows how
much of a phase has already been carried out. It also shows which
phase is currently running and informs you about the status
(RUNNING, COMPLETED, WAITING, ABORTED). l ABAP On this tab page,
the upgrade displays dialogs and information about the upgrade of
the SAP system.n Back and Next buttons To navigate between the
roadmap steps, you choose Back or Next. If you want to go to the
next roadmap step, you choose Next. If you want to undo the roadmap
step, you choose Back.11/21/2008 PUBLIC 37/144
38. 3 Planning3.3 Upgrade GUI and Roadmap Steps Figure 4:
Roadmap Steps If the upgrade program cannot verify the information
you entered or one or more of the prerequisites are not met, the
resulting actions are displayed in one of the following ways: l If
the upgrade program requires immediate action, it is displayed on
the respective tab page. Once you have performed this action, you
can continue choosing Next. l All other required actions are
displayed in the SDTExecution Intervention window. The messages are
sorted according to their importance. Once you have performed the
action, you can continue choosing Next.Roadmap Stepsn 1 -
Initialization The upgrade program analyzes your SAP system. On the
upgrade GUI, you always see the Monitor and the ABAP tab pages.n 2
- Extraction The upgrade program extracts the required software,
that is, the upgrade tools, the SAP kernel and the content.n 3 -
Configuration In the Configuration roadmap step, you enter all the
information required for the upgrade process, for example,
passwords, the preconfiguration mode, information about software
units, add-ons, and Support Packages that you want to include, and
information about the shadow system.n 4 - Checks The upgrade
program checks if the operating system and database version of your
source release match the requirements of the target release. It
also checks the JDK version and some application-specific
requirements.n 5 - Preprocessing In the Preprocessing roadmap step,
the upgrade program builds up the shadow system. This roadmap step
requires only few user entries. The runtime of this roadmap step
depends on the preconfiguration mode you have chosen. With
preconfiguration mode low resource use, the Preprocessing roadmap
step is rather short, since the import of the substitution tables
and the shadow38/144 PUBLIC 11/21/2008
39. 3 Planning3.4 Preconfiguration Mode Planning system
operation both happen during the downtime. With preconfiguration
modes standard resource use and high resource use, both the
substitution table import and the shadow system operation start
during the Preprocessing roadmap step. When the Preprocessing
roadmap step is finished and you choose Next, the downtime starts.n
6 - Downtime The Downtime roadmap step runs without any user
interaction. In this roadmap step, the switch to the new system
takes place. The upgrade program converts application tables and
data to match the target release layout. In addition, it switches
the SAP kernel.n 7 - Postprocessing The upgrade program creates the
upgrade evaluation, saves the log files, and asks you to start with
certain follow-up activities.n 8 - Finalization The upgrade program
removes files and directories that are no longer required and
completes the upgrade.Back to Quick Guide [page 21]3.4
Preconfiguration Mode PlanningThe downtime and the consumption of
system resources depend on the interaction of severalparameters
that you can set for the upgrade. To optimize the duration of the
downtime andthe consumption of your system resources, we have
grouped several parameter settings intopreconfiguration modes.
Instead of setting the parameters manually, you can choose
thepreconfiguration mode that suits your system resource
situation.Preconfiguration ModesThe following preconfiguration
modes are available:Preconfiguration Mode Features Scenariolow
resource use n Low system resource Low system resources consumption
n Early start of downtime shadow system operation during the
downtime (upgrade strategy parameter resource-minimized) n ICNV not
possible11/21/2008 PUBLIC 39/144
40. 3 Planning3.4 Preconfiguration Mode
PlanningPreconfiguration Mode Features Scenariostandard resource
use n Late start of downtime Standard system resources import and
shadow sy