Upgrade guides sap erp 6.0 ehp4
Upcoming SlideShare
Loading in...5
×
 

Upgrade guides sap erp 6.0 ehp4

on

  • 23,194 views

 

Statistics

Views

Total Views
23,194
Views on SlideShare
23,194
Embed Views
0

Actions

Likes
3
Downloads
960
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Upgrade guides sap erp 6.0 ehp4 Upgrade guides sap erp 6.0 ehp4 Document Transcript

  • 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
  • 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
  • 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 SAP’s Support Services and may not be http://service.sap.com/instguidesmodified or altered in any way.11/21/2008 PUBLIC 3/144
  • 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
  • Typographic ConventionsExample Description<Example> Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”. 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
  • 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
  • Table of ContentsChapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . 111.1 Quick Access . . . . . . . . . . . . . . . . . . . . . . . . 111.2 About this Document . . . . . . . . . . . . . . . . . . . . . 111.3 Before You Start . . . . . . . . . . . . . . . . . . . . . . . 131.3.1 Naming Conventions . . . . . . . . . . . . . . . . . . . . . 131.3.2 New Features . . . . . . . . . . . . . . . . . . . . . . . . 151.3.3 SAP Notes for the Upgrade . . . . . . . . . . . . . . . . . . . 15Chapter 2 Quick Guide . . . . . . . . . . . . . . . . . . . . . . . . 21Chapter 3 Planning . . . . . . . . . . . . . . . . . . . . . . . . . 313.1 Time Frame for Upgrading the Front-End Software . . . . . . . . . . 323.2 System Switch Upgrade . . . . . . . . . . . . . . . . . . . . 343.3 Upgrade GUI and Roadmap Steps . . . . . . . . . . . . . . . . 363.4 Preconfiguration Mode Planning . . . . . . . . . . . . . . . . . 393.5 Database-Specific Aspects . . . . . . . . . . . . . . . . . . . 413.6 Upgrades in an MCOD System Landscape . . . . . . . . . . . . . 423.7 Data Management Planning . . . . . . . . . . . . . . . . . . 423.8 Incremental Table Conversion . . . . . . . . . . . . . . . . . 433.9 Upgrade Schedule Planning . . . . . . . . . . . . . . . . . . 453.10 Upgrade in an SAP System Group . . . . . . . . . . . . . . . . 473.11 Modification Adjustment Planning . . . . . . . . . . . . . . . . 473.12 Checking the Structural Requirements for ABAP . . . . . . . . . . . 503.13 Checking the Hardware Requirements . . . . . . . . . . . . . . 513.14 Checking the Software Requirements . . . . . . . . . . . . . . . 513.14.1 Checking the Source Release of the SAP System . . . . . . . . . . . 523.14.2 Meeting the Operating System-Specific Requirements . . . . . . . . . 523.14.3 Upgrade of the Operating System and Database System: Overview . . . . 533.15 Accessing Documentation . . . . . . . . . . . . . . . . . . . 533.16 Using SAP Solution Manager . . . . . . . . . . . . . . . . . . 553.17 Meeting the Requirements for the SAP Internet Solution . . . . . . . . 563.18 Synchronized Upgrade of Dual-Stack SAP Systems . . . . . . . . . . 573.19 Importing Additional Languages . . . . . . . . . . . . . . . . . 593.20 Handling of Customer-Specific Translations and Z Languages in the Upgrade 603.21 SAP ECC: Support Packages . . . . . . . . . . . . . . . . . . . 6111/21/2008 PUBLIC 7/144
  • 3.22 Component Levels Contained in the Upgrade Export . . . . . . . . . 623.23 Using the Application-Specific Update Toolbox . . . . . . . . . . . 623.24 Internet Pricing and Configurator . . . . . . . . . . . . . . . . 63Chapter 4 Preparation . . . . . . . . . . . . . . . . . . . . . . . . 654.1 Determining the Host for the Preparations . . . . . . . . . . . . . 664.2 Upgrading with Microsoft Cluster Server . . . . . . . . . . . . . . 664.3 Checking the Requirements for the Modification Adjustment . . . . . . 674.4 Filling the Download Directory . . . . . . . . . . . . . . . . . 674.5 Downloading Enhancement Packages . . . . . . . . . . . . . . . 684.6 Meeting the Requirements for the Upgrade Directory . . . . . . . . . 714.7 Generating the SAP Solution Manager Key . . . . . . . . . . . . . 714.8 SAP ECC: Initializing Fields in Table COKEY2 . . . . . . . . . . . . 724.9 Unicode SAP Systems: Running Reports RUTTTYPACT and UMG_POOL_TABLE . . . . . . . . . . . . . . . . . . . . . 724.10 Preparing the Migration of Workload Statistics Data . . . . . . . . . . 734.11 Checking the Consistency of the Host Name . . . . . . . . . . . . 734.12 Setting the Operation Mode for the Upgrade . . . . . . . . . . . . 744.13 Providing the JCE Jurisdiction Policy Files . . . . . . . . . . . . . . 754.14 Making Preparations at the Database Level . . . . . . . . . . . . . 764.15 Making Preparations at the SAP System Level . . . . . . . . . . . . 774.15.1 Deleting the AUTOSTART Parameter . . . . . . . . . . . . . . . 774.15.2 SAP ECC: Deleting Application Logs . . . . . . . . . . . . . . . 774.15.3 SAP ECC: Backing Up Wage Types in HR (T512W) (HR Customers) . . . . 784.15.4 SAP ECC: Backing Up UI Conversion Classes in ESS . . . . . . . . . . 79Chapter 5 Upgrade Process . . . . . . . . . . . . . . . . . . . . . . 815.1 Starting the Upgrade Program . . . . . . . . . . . . . . . . . . 825.2 Starting the Upgrade GUI . . . . . . . . . . . . . . . . . . . 835.3 Restarting the Upgrade Program . . . . . . . . . . . . . . . . . 845.4 Resetting the Upgrade . . . . . . . . . . . . . . . . . . . . 855.5 Importing or Installing Software After Starting the Upgrade . . . . . . . 865.6 Making Entries for the Extraction Roadmap Step . . . . . . . . . . . 865.7 Making Entries for the Configuration Roadmap Step . . . . . . . . . 885.7.1 Entering Paths and Parameters . . . . . . . . . . . . . . . . . 885.7.2 Including Software . . . . . . . . . . . . . . . . . . . . . . 925.7.3 Making Entries for the Shadow Instance Installation . . . . . . . . . 975.8 Making Entries for the Checks Roadmap Step . . . . . . . . . . . . 985.9 Evaluating the Results of the Preparation Roadmap Steps . . . . . . . . 995.10 Making Entries for the Preprocessing Roadmap Step . . . . . . . . . . 1045.11 Making Entries for the Downtime Roadmap Step . . . . . . . . . . . 1085.12 Making Entries for the Postprocessing Roadmap Step . . . . . . . . . 1128/144 PUBLIC 11/21/2008
  • Chapter 6 Follow-Up Activities . . . . . . . . . . . . . . . . . . . . 1156.1 Oracle: Performing Specific Actions . . . . . . . . . . . . . . . . 1176.2 Follow-Up Activities for the Microsoft Cluster Server . . . . . . . . . 1186.3 Performing Follow-Up Activities for the SAP Kernel . . . . . . . . . . 1186.4 Performing Follow-Up Activities in the Monitoring Area . . . . . . . . 1196.5 Activating the ICM Service . . . . . . . . . . . . . . . . . . . 1196.6 Installing Java Components . . . . . . . . . . . . . . . . . . . 1206.7 Reimporting Additional Programs . . . . . . . . . . . . . . . . 1206.8 Adjusting Repository Objects . . . . . . . . . . . . . . . . . . 1206.9 Performing Follow-Up Activities for Security . . . . . . . . . . . . 1216.10 Performing Application-Specific Activities . . . . . . . . . . . . . 1216.11 Adjusting Customizing Settings . . . . . . . . . . . . . . . . . 1226.12 Converting Codepages . . . . . . . . . . . . . . . . . . . . 1226.13 Adjusting Customer Developments . . . . . . . . . . . . . . . 1236.14 Updating the Where-Used List in the ABAP Workbench . . . . . . . . 1236.15 Migrating the Workload Statistics Data . . . . . . . . . . . . . . 1246.16 SAP ECC: Activating SAP ECC Extensions . . . . . . . . . . . . . 1246.17 SAP ECC: SAP HR Customers Only: Reloading Table T512W (Wage Types in HR) 1246.18 SAP ECC: SAP Retail Customers Only: Converting Short Texts . . . . . 1256.19 SAP ECC: TR-TM Customers and CFM-TM Customers Only: Migrating Data 1256.20 Performing Follow-Up Activities for SAP Solution Manager . . . . . . . 1256.21 Secure Single Sign-On with Microsoft LAN Manager SSP . . . . . . . . 1256.22 Executing Conversion Programs for the Product Master . . . . . . . . 1296.23 Migrating Data to Table TVARVC . . . . . . . . . . . . . . . . 1316.24 Activating VMC for the Internet Pricing and Configurator . . . . . . . 1316.25 Rescheduling Background Jobs . . . . . . . . . . . . . . . . . 1326.26 Oracle: Performing Actions for the Cost-Based Optimizer . . . . . . . 1326.27 Generating Loads . . . . . . . . . . . . . . . . . . . . . . 1336.28 Installing the SAP Online Documentation . . . . . . . . . . . . . 1356.29 Performing Follow-Up Activities in the Authorizations Area . . . . . . . 1356.30 Performing Follow-Up Activities for Application Link Enabling (ALE) . . . 1376.31 Upgrading or Installing Dialog Instances . . . . . . . . . . . . . . 1386.32 Importing Support Packages After the Upgrade . . . . . . . . . . . 1386.33 Transport Management System: Distributing the Configuration . . . . . 1396.34 Performing Follow-Up Activities for the Language Transport . . . . . . 1396.35 Oracle: Deleting Tablespaces . . . . . . . . . . . . . . . . . . 1406.36 Saving Files for Follow-Up Upgrades . . . . . . . . . . . . . . . 141Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 143A.1 List of Documentation . . . . . . . . . . . . . . . . . . . . 14311/21/2008 PUBLIC 9/144
  • 10/144 PUBLIC 11/21/2008
  • 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
  • 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
  • 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, “<SAP component>: <Title>”. 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 “<sapsid>” is used,your SAP system ID must be in lowercase letters, for example “prd”. If “<SAPSID>” is used, you mustwrite in uppercase letters, for example “PRD”.ID for the SAP System ReleaseIn this document, “<rel>” stands for the relevant SAP system release, without a decimal point,such as “700”.11/21/2008 PUBLIC 13/144
  • 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 Component”n “SAP ECC Core” for “SAP ERP Central Component Core”n “SAP ECC Extension Set ” for “SAP ERP Central Component Extension Set”SAP 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
  • 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 <platform> 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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 usrsap<SAPSID>upg): 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
  • 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 <your application> .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
  • 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 <sapsid>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
  • 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 <release> 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
  • 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<x> 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
  • 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<SAPSID> 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<sapsid> 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
  • 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
  • 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
  • This page is intentionally left blank.
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 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
  • 3 Planning3.4 Preconfiguration Mode PlanningPreconfiguration Mode Features Scenariostandard resource use n Late start of downtime ‒ Standard system resources import and shadow system available operation while the SAP system is still in production operation (upgrade strategy parameter downtime-minimized) n Database archiving mode is off during downtime n Database backup required before downtimehigh resource use n Late start of downtime ‒ High system resources available import and shadow system operation while the SAP system is still in production operation (upgrade strategy parameter downtime-minimized) Late start of downtime ‒ import and shadow system operation while the SAP system is still in production operation n Fast import n Database archiving mode is on, which results in a large amount of archiving logs during downtimemanual selection n Expert mode Special requirements n Control over all parameters For more information, see Manual Selection of Parameters in the document Troubleshooting and Administration [page 53].ParametersUpgrade StrategyThe upgrade strategy parameter is one of the main factors in determining how much downtimeis involved.For strategy parameter resource-minimized, the operation of the shadow system, including modificationadjustment, activation, and delta import, is performed during downtime. Additional resourceconsumption is low.For strategy parameter downtime-minimized, the operation of the shadow system and the shadow importare performed during production operation. Using function ICNV, you can further reduce downtimeby moving the conversion of large tables to the uptime.40/144 PUBLIC 11/21/2008
  • 3 Planning3.5 Database-Specific AspectsDatabase Archiving ParameterDatabase archiving cannot be deactivated automatically. When you choose a preconfiguration modefor which archiving needs to be deactivated during the downtime, the upgrade program asks you atthe beginning of roadmap step Downtime to deactivate archiving. CautionOnce you have deactivated archiving, you can no longer use the SAP system in production operation. CautionMCOD systems: If you specified during the preparation roadmap steps that you are performing theupgrade in a Multiple Components in One Database System (MCOD), which means that multipleSAP systems are installed in your database, you are not prompted about archiving. Archiving isautomatically activated during the entire upgrade. For more information about MCOD systems,see SAP Service Marketplace at http://service.sap.com/mcod.Background Process and Tool ParametersThere are several parameters with which you can influence the use of SAP system resources for theupgrade process during uptime and downtime. These are, for example, the number of backgroundprocesses or the number of parallel processes used by R3trans during uptime and downtime. Thepreconfiguration modes make sure that these numbers fit to the upgrade strategy and databasearchiving strategy used.Shadow Instance ParametersThere are several parameters used for running the shadow instance. Most of these parameters are setautomatically, for example, an instance number not yet used in your system landscape.Back to Quick Guide [page 21].3.5 Database-Specific AspectsOracleAt the end of step Preprocessing before the start of roadmap step Downtime, you are prompted to stopall work in the SAP system.You must be able to recover the database to the state it has at this point in time. RecommendationIf you make a full backup of your database now, in case of a recovery you need not import all thearchives created so far, including those written during the previous import.11/21/2008 PUBLIC 41/144
  • 3 Planning3.6 Upgrades in an MCOD System Landscape NoteMake sure that you back up the upgrade directory including subdirectory sdt.At the beginning of roadmap step Downtime, you can deactivate the archiving of the database.If you deactivate archiving, you have to make a full backup of the database after the downtime beforeyou switch archiving back on. This must be executed as an offline backup.For a detailed description on deactivating and activating the archiving of the database, see Changing theOracle Database Recovery Mode in the document Troubleshooting and Administration [page 53].Back to Quick Guide [page 21]3.6 Upgrades in an MCOD System LandscapeAs of SAP Web Application Server 6.10, you can upgrade systems in a Multiple Components in OneDatabase (MCOD) system landscape. Note the following when you upgrade an MCOD system:n Do not switch off archiving when upgrading in an MCOD system landscape. All SAP systems in the database are affected if you need to reset the upgrade. At the start of the upgrade, the upgrade program determines automatically whether there is more than one SAP system installed in the database. If there is more than one SAP system installed in the database, do not switch off archiving during the upgrade.n Do not perform parallel upgrades of MCOD systems.For more information about MCOD systems, see SAP Service Marketplace athttp://service.sap.com/mcod.Back to Quick Guide [page 21]3.7 Data Management PlanningThe upgrade runtime ‒ and in particular the system downtime ‒ is extended when dealing withlarge database tables. Table conversions during the upgrade and data adjustments at the end of theupgrade are the most time consuming actions and can result in long upgrade runtimes. To avoidthese problems, you should minimize the quantity of table entries that have to be converted priorto the upgrade. The best way to achieve this is to carry out Data Management measures, such asarchiving or deleting data records from the tables.As part of an overall Information Lifecycle Management (ILM) process, Data Management is vital formaintaining a “healthy” live system because it helps to keep system performance high and to makeoptimal use of existing hardware resources. One of the most effective Data Management methodsis Data Archiving. It allows administrators to remove data that is no longer needed in everydayoperations from the database and store it in archive files. These files can then be passed on to a storage42/144 PUBLIC 11/21/2008
  • 3 Planning3.8 Incremental Table Conversionsystem for long-term storage. After archiving, the data can still be accessed in read-only mode whenthe need arises, for example, during an audit.For more information about Data Archiving, see SAP Service Marketplace athttp://service.sap.com/ilm.ProcedureBefore the upgrade, analyze the database to find out which database tables can be reduced in size,and how this can be achieved.For more information, see the Data Management Guide on SAP Service Marketplace at http://service.sap.com/ilm Data Archiving Media Library Literature & Brochures .You can also take advantage of the comprehensive update offering „SAP Safeguarding for Upgrade“.For more information, see http://service.sap.com/safeguardingupgradeBack to Quick Guide [page 21]3.8 Incremental Table Conversion CautionYou can use incremental table conversion for ABAP tables only if you use preconfiguration modestandard resource use or high resource use.The structure of some of the tables in your database changes each time you upgrade your system to anew release. In some cases you need to convert these tables. This involves completely restructuringthem and converting each individual data record. These conversions are usually made during theupgrade downtime (phase PARCONV_UPG).The incremental conversion function enables many of these tables to be converted before thedowntime. The data is converted during production operation of the system.This approach has the following benefits:n Reduced downtime during the upgrade, especially for systems with one or more add-onsn Simple return to the SAP standard for modified tablesPrerequisitesThe System Switch Upgrade only determines the candidates for transaction ICNV after the targetstructure of the tables has been defined. The candidates are determined in the ICNVREQ phase. Theupgrade program checks whether the system contains tables for which an incremental conversion isan advantage. These include tables that need to be converted, and that contain large volumes of data,and therefore would increase the downtime significantly during a conversion. The System SwitchUpgrade also enables you to use transaction ICNV for tables that have been modified by SupportPackages, add-ons, or customer developments.If the above applies, the upgrade program prompts you to start the incremental conversion.11/21/2008 PUBLIC 43/144
  • 3 Planning3.8 Incremental Table ConversionUse of the incremental conversion function is optional. If you do not want to use incrementalconversion, the tables are converted during downtime.FeaturesIncremental conversion is performed using transaction ICNV. This transaction offers the followingfunctions:n Displays the tables determined by the upgrade program (candidates for incremental conversion)n Decides which candidates should be converted incrementallyn Starts the conversionn Monitors the conversionn Estimates the runtime of the conversionFor up-to-date information, see SAP Note 490788. For more information, call transaction ICNVand choose F1 or Information.Note the following:n Transaction ICNV makes modifications to the database tables that you want to convert during the preparation roadmap steps. You cannot reset these modifications by resetting the upgrade. In particular, you cannot directly upgrade these modifications.n If you use incremental table conversion, do not start an SAP archiving program for these tables at the same time, since this can lead to performance bottlenecks. Therefore, archive as much data as possible before you start the conversion.n After the incremental conversion starts, you cannot change any more ABAP Dictionary definitions for the relevant tables until the upgrade is complete. This means that you cannot change, delete or add field definitions. Transaction SE11 is locked for these tables.n Pay special attention to the resource usage of your database management system to detect bottlenecks early on. Incremental conversion requires double the space in the relevant database memory area for each table affected during the conversion. The continuous transfer of data results in more transactions being performed. Therefore, also monitor the space available for the rollback information.n Do not begin the upgrade downtime before at least 95% of the total data has been converted. The upgrade program checks this at the beginning of downtime. If this percentage has not been reached, the upgrade program displays an appropriate message. This gives you the advantage of reducing critical downtime. To monitor the progress of the conversion, you can call transaction ICNV. You can start downtime even if the 95% minimum has not been reached. However, the remaining data is transferred entirely during downtime. If this process is not finished before the PARCONV_UPG phase, the downtime increases depending on the remaining conversion set.n Incremental conversion requires a sufficient number of background work processes. Ideally, there should be one process for each table that needs to be converted. If you cannot have one process44/144 PUBLIC 11/21/2008
  • 3 Planning3.9 Upgrade Schedule Planning for each table because there are too many of them, you can still convert them since transaction ICNV automatically distributes the tables to the available background processes. However, the incremental conversion then takes longer to complete, and the time for beginning downtime is pushed back.Back to Quick Guide [page 21]3.9 Upgrade Schedule PlanningCreate an exact schedule for your SAP system upgrade.PrerequisitesYou have decided on a preconfiguration mode [page 39].Process1. You decide when to begin preparing for the upgrade. When you start the upgrade preparations does not depend only on the length of the preparations but also on the length of the upgrade itself. To determine the expected total length of the upgrade of your production system, perform a test upgrade of an SAP system with a similar set of data (a system copy of your production system is ideal).2. You decide when to start the upgrade. If you have special requirements regarding the availability of your SAP system, adjust the process and the length of the upgrade to fit the expected amount of downtime. During the upgrade, various actions are performed by and in the shadow system. The runtime of these actions depends on various factors and is therefore specific to each SAP system: n Creating the Shadow Repository n Importing the additional software packages such as languages, Support Packages, and add-ons The minimum runtime of the import phase increases with every Support Package, add-on, and language that is included. n Adjusting modifications to the ABAP Dictionary objects (transaction SPDD) n Mass activation and distribution n Incremental conversion of ABAP tables (transaction ICNV) The duration of these actions depends on the preconfiguration mode that you choose. If you have chosen mode low resource use, these actions take place during downtime in the Downtime roadmap step of the upgrade program. If you have chosen mode standard resource use or high resource use, you can continue to use your SAP system in production operation during these actions, as they run in the Preprocessing roadmap step of the upgrade program. Therefore start the upgrade in good time. If you finish the activities before the scheduled start of downtime, you can stop the upgrade before the Downtime roadmap step by not choosing Next when the Preprocessing roadmap step has completed.11/21/2008 PUBLIC 45/144
  • 3 Planning3.9 Upgrade Schedule Planning Figure 5: Upgrade Up- and Downtime3. You take the necessary measures to extend the time in which the upgrade can run unmonitored. n Specify all mount directories at the start of the upgrade. The upgrade program asks you to specify mount directories when you start upgrading. This significantly increases the amount of time the upgrade can run without user input. n Early locking of the ABAP Workbench If you are sure that you can do without the ABAP Workbench, confirm the lock when you are asked for the first time.4. You decide when a full backup is performed after the upgrade. The full database backup is a prerequisite for resuming production operation of your system when archiving is deactivated. It must be made after you have performed all necessary follow-up activities. This has the advantage that all database changes resulting from follow-up activities are included in the full backup.5. You decide when production operation resumes. If possible, resume production operation only after you have performed all required follow-up activities.Back to Quick Guide [page 21]46/144 PUBLIC 11/21/2008
  • 3 Planning3.10 Upgrade in an SAP System Group3.10 Upgrade in an SAP System GroupIf you have more than one SAP system, for example, a production system and a development system,you must consider the entire system group.Upgrade your systems in the same sequence in which you transport your modifications.Processn If you have a development system and a production system, work in the following order: 1. Development system 2. Production systemn If your system group consists of three SAP systems and includes a quality assurance system that has been set up between the development and production system, work in the following order: 1. Development system 2. Quality assurance system 3. Production systemIf you have made modifications to SAP objects that you want to retain, you must proceed in the abovesequence. The version management functions of the SAP system record all the changes you makeonly in the system in which you made the modifications (the development system). Only this SAPsystem offers you optimal support when you adjust modifications.Changes made in the development system after the upgrade can be transported automatically toyour other SAP systems. If you use this procedure, you no longer need to perform time-consumingadjustments in the production system. CautionIf you have modified SAP objects, make sure that you keep your development system. Do not copyyour production system to your development system for test purposes.For test purposes with realistic production data, set up a quality assurance system between thedevelopment system and production system. This system can be a copy of the production system.Back to Quick Guide [page 21]3.11 Modification Adjustment Planning NoteIf you are sure that your SAP system corresponds exactly to the standard SAP system, you can skipthis section.Modifications are changes to objects of the SAP standard. There are two types of modifications: onesthat make changes to the translation of an object text, and ones that make changes to the object itself.11/21/2008 PUBLIC 47/144
  • 3 Planning3.11 Modification Adjustment PlanningChanges to the Translation of an Object TextThe changes are made in the translation environment (transaction SE63) or in the ABAP Workbench.An SSCR key is not required. CautionChanges to translations of SAP objects are not retained when you perform an upgrade. They areoverwritten by a new version or deleted. For more information about retaining these changes,see SAP Note 485741.Modifications to the ObjectYou may need an SSCR key to perform the modification adjustment. Get the key before youupgrade the system.For more information, see SAP Service Marketplace at http://service.sap.com/sscr.All modified standard SAP objects are displayed for adjustment in transaction SPDD or SPAU. Objectsthat SAP no longer delivers are deleted. If you want to keep these objects, you have to accept themodifications in transaction SPDD or SPAU. CautionMake sure that before the upgrade there is at least one package in the customer namespace (Z*).You need this package if you have to create objects during the modification adjustment, for example,for an append structure for customer fields of an SAP table.You cannot create packages during the upgrade.If you choose preconfiguration mode standard resource use or high resource use, the modification adjustmentof ABAP Dictionary objects occurs during production operation. This is possible since the completeversion management is available in the shadow system. The remaining Repository objects are stilladjusted at the end of the upgrade.For more information about the modification adjustment, see SAP Service Marketplace at http://service.sap.com/abapwb Modification & Enhancement .ProcessModification Adjustment in the First System (Development System) NoteSince all modifications to standard SAP objects are displayed during the upgrade, and you have toadjust all the displayed objects, you must schedule enough time for the modification adjustment.You must test the modification adjustment in a development system that has the same SAP systemrelease and that has been modified in the same way as the production system. If the development48/144 PUBLIC 11/21/2008
  • 3 Planning3.11 Modification Adjustment Planningsystem contains more modifications, including the Support Package level, contact an experienced SAPconsultant for help. The following explanation assumes that the levels of modification are identical.1. The list of objects that must be adjusted in your SAP system is determined in the ADJUSTCHK phase. This phase is executed in the Configuration roadmap step and runs between the import of the substitution set and the end of the production period. The list is in the UMODPROT<SAPSID> log in the abaplog subdirectory of the upgrade directory.2. If you choose preconfiguration mode standard resource use or high resource use, the ABAP Dictionary objects (tables, data elements, domains, and so on) are adjusted during production operation. If you choose preconfiguration mode low resource use, they are adjusted during downtime before the ABAP Dictionary is activated. The adjusted objects are collected in a repair that is released to a transport request. You cannot release this transport request; instead you must flag it for transport in transaction SPDD. Towards the end of the upgrade, the upgrade program exports the request to the transport directory $(SAPGLOBALHOST)sapmnttrans and registers it for transport in the umodauto.lst file.3. Repository objects (reports, screens, and so on) are adjusted towards the end of the upgrade. At this stage, the import of SAP objects has already been completed. However, the old modified version is still available in the version database. As with ABAP Dictionary objects, all changes are released to a transport request that is flagged and then exported and registered by the upgrade program.Modification Adjustment in Subsequent SystemsFor the quality assurance and production system, we recommend that instead of adjustingmodifications manually, you automatically transfer the two transport requests exported from the firstsystem, as described in “Modification Adjustment in the First System (Development System)” above. NoteIf you have not set up a central transport directory, you must perform some more steps before thetransport requests can be transferred automatically. These steps are described in SAP Note 51046. CautionMake sure that the Support Package levels included in the upgrade of the subsequent systems aresimilar to the Support Package levels included in the first upgrade.The ADJUSTPRP phase in the Configuration roadmap step prepares the requests from the developmentsystem to be transferred.If you confirm the transport requests, they are integrated into the upgrade.The phase also checks whether all the modifications identified in the system are handled by transportrequests. If this is the case, you do not need to perform a modification adjustment.11/21/2008 PUBLIC 49/144
  • 3 Planning3.12 Checking the Structural Requirements for ABAP CautionThe number of objects in the adjustment transport requests might exceed the number ofmodifications in the receiving system. In this case, the upgrade will import changes that previouslydid not exist in the receiving system.For a detailed description of the modification adjustment function, see the SAP Library [page 53] foryour target release at: SAP NetWeaver Library Function-Oriented View Application Server ABAP Application Development on ASABAP ABAP Customer Development Changing the SAP Standard (BC) Upgrade Procedure /Support PackagesBack to Quick Guide [page 21]3.12 Checking the Structural Requirements for ABAPYou must meet the following structural requirements before you upgrade your system:n The message server must run on the host with the central instance. During the upgrade, the upgrade program uses Remote Function Call (RFC) to call function modules and temporarily schedules ABAP report programs for background processing. For this reason, the message server must still be running after the additional application server instances are stopped. You can only guarantee this if the message server is located on the same host as the central instance.n Update processes must run on the central instance when you make modifications to the standard SAP system. If you have made modifications to the standard SAP system, versions of the modified objects are created by the version management functions during the upgrade. The update program writes these versions. This means that an update process must be running on the central instance.A standard installation meets the specified structural requirements.If you are not sure whether you have a standard installation, you can use the following procedure tocheck the structural requirements.Procedure1. Call transaction RZ10. Choose Goto Profile values Of a server .2. Choose the server (host) where the central instance is running. The profile parameters for this server are displayed with their values.3. Check the profile parameter rdisp/mshost. This parameter contains the host name where the message server is running. It must run on the same host as the central instance. This makes sure that the message server is active during50/144 PUBLIC 11/21/2008
  • 3 Planning3.13 Checking the Hardware Requirements downtime, because only the central instance runs during downtime, while the dialog instances are stopped.4. If you have made changes to the standard SAP system, check the profile parameter rdisp/wp_no_vb. This parameter displays the number of update processes for the central instance. The number must be greater than 0.Back to Quick Guide [page 21]3.13 Checking the Hardware RequirementsCPU, Main Memory, Disk, and Swap SpaceCheck whether you have sufficient hardware resources, such as CPU, main memory, diskspace, and swap space. For more information about sizing, see SAP Service Marketplace athttp://service.sap.com/sizing.To plan technical upgrades (without functional extensions), see the information about how to performa delta sizing for upgrades on SAP Service Marketplace at http://service.sap.com/sizingSizing Guidelines .Space Requirements in the File SystemMake sure that there is enough temporary disk space available in the file system for the upgrade. Youneed this free space to create the upgrade directory.For information about the required space, see Quick Guide [page 21].Space Requirements in the DatabaseMake sure that enough temporary and permanent free space is available in your database.The upgrade program takes the status of your database into account and calculates the exact spacerequirements.For preliminary information about extending the database, see Quick Guide [page 21]. NoteFor Unicode systems, the amount of free space needed is higher than for non-Unicode systems.For more information, see SAP Note 1139642.You can recover the difference between the minimum disk space requirements and the permanentdisk space requirements by deleting the old substitution tablespaces.Back to Quick Guide [page 21]3.14 Checking the Software RequirementsYou must meet certain software requirements before you upgrade the SAP system.11/21/2008 PUBLIC 51/144
  • 3 Planning3.14 Checking the Software Requirements1. Check the source release [page 52] of the SAP system.2. Meet the operating system-specific requirements [page 52].3. If necessary, upgrade the operating system and database system [page 53].Back to Quick Guide [page 21]3.14.1 Checking the Source Release of the SAP SystemBefore the upgrade, your SAP system must have one of the source releases, which have been releasedfor this upgrade and which apply to all databases. For more information, see Quick Guide [page 21]. NoteThe upgrade program also checks whether your source release has been released for the upgrade. CautionIf you have to apply Support Packages on your source release shortly before the upgrade, checkwhether the equivalent Support Package for the target release is already available. Otherwise, thismay delay your upgrade schedule.Procedure for ABAP SystemsTo determine the source release of the SAP system, log on to the system and choose System Status . Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40The release appears in the Component version field. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40Back to Quick Guide [page 21]3.14.2 Meeting the Operating System-Specific RequirementsAll Operating SystemsDepending on the database, 32-bit systems and 64-bit systems are supported by the upgrade. Formore information, see the Product Availability Matrix (PAM) on SAP Service Marketplace athttp://service.sap.com/PAM.Back to Quick Guide [page 21]52/144 PUBLIC 11/21/2008
  • 3 Planning3.15 Accessing Documentation3.14.3 Upgrade of the Operating System and DatabaseSystem: OverviewWhen you upgrade the SAP system, you may have to update your operating system and databaseto a new version.For more information about which versions are currently supported, see SAP Service Marketplace athttp://service.sap.com/platforms. The upgrade program only checks the minimum versionsrequired for upgrade.If you need to upgrade an operating system or database, or migrate a database, then the timing andthe sequence of the individual upgrades is of great importance. The procedure differs according tothe database you use. The following text provides an overview of the main process steps for upgradingthe operating system and database system for each database.ProcessOracleFor preliminary information about the minimum required version, see Quick Guide [page 21].Proceed as follows:1. You install the Oracle client software for the target release. For more information, see the document Upgrade to Oracle Database <Version>: <Platform>.2. You perform the following steps: a) Execute the following SQL statement on the database via SQL*Plus: SQL> select * from V$NLS_PARAMETERS where PARAMETER = ’NLS_NCHAR_CHARACTERSET’ ; b) If the NLS_NCHAR_CHARACTERSET returns value US7ASCII, change it to UTF8 as described in SAP Note 669902.3. You start the upgrade program and analyze the results of the preparation roadmap steps. Roadmap step Checks informs you about the minimum version for the operating system and database. If necessary, upgrade the operating system. If you have not already done so, migrate the Oracle database as described in the document Upgrade to Oracle Database <Version>: <Platform> to at least the minimum required version.4. You upgrade the SAP system.Back to Quick Guide [page 21]3.15 Accessing DocumentationBefore, during, and after the upgrade you require additional documentation:n SAP NetWeaver online documentation for the source release and the target release11/21/2008 PUBLIC 53/144
  • 3 Planning3.15 Accessing Documentationn Online documentation for your applicationn Troubleshooting and administration documentationThere are different ways to access the documentation:n SAP Library documentation l SAP NetWeaver Library on SAP Help Portal You can access documentation for all maintained product releases on SAP Help Portal. l SAP Library for your application on SAP Help Portal You can access documentation for all product releases that are in maintenance on SAP Help Portal. l Local installation of the SAP Library for your application Note The documentation for the target release is not available online in your system until you have completed the upgrade and the installation procedure for the online documentation. Before the upgrade, you can make sure that you can read the DVD offline. After the upgrade, you need to install the documentation for the target release.n Troubleshooting and administration documentation The documentation is included in the upgrade program.SAP Help PortalTarget Release DocumentationYou can find the SAP Library for SAP NetWeaver 7.0 including enhancement package 1 on SAP HelpPortal at http://help.sap.com/ SAP NetWeaver SAP NetWeaver <Release> SAP NetWeaver<Release> Knowledge Center SAP NetWeaver <Release> Library <Language> .You can find the SAP Library for SAP enhancement package 4 for SAP ERP 6.0 on SAP Help Portal at http://help.sap.com/ SAP ERP SAP ERP Central Component SAP ERP Enhancement Packages<Release> .Source Release Documentation Only valid for: SAP Web AS 6.40You can find the SAP Library for SAP NetWeaver 2004 on SAP Help Portal at http://help.sap.com/SAP NetWeaver 2004 <Language> SAP NetWeaver . End of: SAP Web AS 6.40 Only valid for: SAP Web AS 6.20You can find the SAP Library for SAP Web Application Server 6.20 on SAP Help Portal at http://help.sap.com/ SAP NetWeaver Prior to SAP NetWeaver 2004 SAP Web Application Server=< 6.30 SAP Web Application Server 6.20 <Language> . End of: SAP Web AS 6.2054/144 PUBLIC 11/21/2008
  • 3 Planning3.16 Using SAP Solution Manager Only valid for: SAP R/3 4.6CYou can find the SAP Library for SAP R/3 4.6C on SAP Help Portal at http://help.sap.com/SAP R/3 and R/3 Enterprise SAP R/3 Release 4.6C <Language> . End of: SAP R/3 4.6CLocal Installation of the SAP Library for Your ApplicationBefore and during the upgrade, you must read the online documentation for the target release onthe DVD.Troubleshooting and Administration DocumentationThe troubleshooting and administration documentation is included in the upgrade program.The upgrade tool unpacks the documentation at the beginning of roadmap step Extraction.You can access the documentation as follows:n From a link on the upgrade GUI. Proceed as follows: 1. If it is not running yet, start the upgrade program. 2. On page http://<host name>:4239, choose ABAP documentation. 3. Choose Troubleshooting and Administration for Systems Running on <platform>.n From file Troubleshooting_and_Administration_Windows.pdf in directory UPGabaphtdoc3.16 Using SAP Solution ManagerUsing SAP Solution Manager throughout the life cycle of your SAP application leads to a fasterimplementation and more efficient operation of the SAP application by providing all implementationand upgrade content for commonly used standard processes. In addition, projects become moretransparent, having up-to-date central project documentation all in one place at any point in time.For technical reasons, you require an SAP Solution Manager system to upgrade your SAP application.During the upgrade process you are prompted to enter an SAP Solution Manager key. Withoutthis key, the upgrade process cannot continue. NoteYou may generate all needed SAP Solution Manager keys [page 71] for your entire system landscape(development, quality assurance, and production system) in one SAP Solution Manager system.If you plan to install several solution landscapes (for example, in different countries), one SAPSolution Manager system is still sufficient.You require SAP Solution Manager 7.0 Support Package 15 or higher.For more information, see SAP Note 805390 and SAP Service Marketplace athttp://service.sap.com/solutionmanager.11/21/2008 PUBLIC 55/144
  • 3 Planning3.17 Meeting the Requirements for the SAP Internet SolutionProcedure1. If you have not been using SAP Solution Manager yet, install it as described in the document Installation Guide ‒ SAP Solution Manager. You can find this document on SAP Service Marketplace at http://service.sap.com/instguides SAP Components SAP Solution Manager Release <x> .2. Make sure that the SAP system for which you want to perform an upgrade is known to your SAP Solution Manager. To create your SAP system in the Solution Manager System Landscape transaction, proceed as follows: a) Log on to your SAP Solution Manager system. b) Call transaction SMSY (Solution Manager System Landscape). c) Select the landscape component Systems and in the context menu, choose Create. d) In the next dialog box, enter the SAP system ID as the system name. e) Choose a product and a product version from the input help. f) Save your entries.Back to Quick Guide [page 21]3.17 Meeting the Requirements for the SAP Internet SolutionAs of SAP NetWeaver ’04, the SAP Internet Transaction Server (SAP ITS) is integrated into the SAPNetWeaver component SAP Web Application Server as an Internet Communication Framework (ICF)service, which you can access, like other services, through the Internet Communication Manager(ICM). With the SAP ITS integrated in the SAP Web Application Server, the Web browser nowcommunicates directly with the SAP system. Furthermore, all SAP ITS-related sources, such as servicefiles, HTML templates, or MIME files, are now stored in the database of the system.The SAP-integrated ITS supports the following functions:n SAP GUI for HTMLn Internet Application Component (IAC) runtime or Web Transaction technologyThe SAP-integrated ITS does not support the following functions:n SAP ITS Flowlogic runtimen WebRFCn Web Reportingn GUI XTAs of SAP NetWeaver 7.0, these functions are no longer supported at all. Applications based on any ofthe no longer supported functions must be migrated.SAP ITS 6.20 is compatible with SAP systems up to and including SAP systems based on SAP NetWeaver’04. However, it is not compatible with SAP systems based on SAP NetWeaver 7.0 or higher. Thismeans that as of SAP NetWeaver 7.0, each application based on ITS technology can only be usedvia SAP integrated ITS.56/144 PUBLIC 11/21/2008
  • 3 Planning3.18 Synchronized Upgrade of Dual-Stack SAP Systems NoteYou can use the ABAP Workbench of the SAP system to develop your own Internet applications ormodify the applications delivered with the standard SAP system. Any modification you make toInternet applications delivered in the standard SAP system are recorded by the Modification Assistantand can be adjusted with transaction SPAU during the upgrade.ProcedureIf you want to use the SAP integrated ITS 7.0, proceed as follows:1. Perform the upgrade of the SAP system.2. Configure the SAP integrated ITS. For information about how to configure the SAP integrated ITS, see the SAP Library [page 53] for you target release at SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server ABAP Presentation Development on AS ABAP ITS/SAP@Web Studio (BC-FES-ITS) SAP ITS in the SAP Web Application Server Configuration .3. Migrate the applications. For information about how to migrate SAP ITS-based Internet services, see the SAP Library [page 53] for your target release at SAP NetWeaver Library SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server ABAP Presentation Development on AS ABAP ITS/SAP@Web Studio (BC-FES-ITS) SAP ITS in the SAP Web Application Server Developing IACs with the SAP integrated ITS Migration of Existing ITS Services .Back to Quick Guide [page 21]3.18 Synchronized Upgrade of Dual-Stack SAP SystemsIf you run an ABAP-based server and a Java-based server in the same SAP system, you must upgradethem in parallel. The two upgrade processes require a synchronization that affects the following areas:n Upgrade progressn User managementn Profile changesn Starting and stopping of the SAP systemn Reset of the upgradeProgress of the UpgradeThe upgrades for both parts, the ABAP-based server and the Java-based server, have to be synchronized.For a proper synchronization, it is essential that you first start the upgrade of the ABAP-based server,that is, you start the upgrade program SAPup. SAPup then detects that there is a Java server installed inthe same system and prompts you to start the Java server upgrade as well.11/21/2008 PUBLIC 57/144
  • 3 Planning3.18 Synchronized Upgrade of Dual-Stack SAP Systems CautionThe Java server upgrade must be started only after the Configuration roadmap step of the ABAP serverupgrade is completed.The ABAP part of the upgrade program, SAPup, and the Java part, SAPJup, synchronize themselvesat several points during the upgrade. That is, if one upgrade has already reached a synchronizationpoint but the other has not, the first one waits. Once both have reached the synchronization point,they can proceed.The following synchronization points exist:n At the beginning of downtimen When the profiles are about to be changedn At the end of downtimeThis synchronization ensures that the downtime is as short as possible.Figure 6: Synchronization Points of Parallel ABAP and Java UpgradePreconfiguration ModeFor a synchronized upgrade of a dual-stack system, you can only use the preconfiguration modesstandard resource use or high resource use for the ABAP part.UME ConfigurationDuring the ABAP upgrade downtime, ABAP user management is not available. If your UserManagement Engine (UME) uses ABAP user management, it cannot access any user data duringthis period. Therefore, the Java upgrade program switches the UME configuration to data source“local”. This is only a temporary configuration for the duration of the upgrade and is switchedback after the upgrade.58/144 PUBLIC 11/21/2008
  • 3 Planning3.19 Importing Additional LanguagesProfile ChangesDepending on the configuration of your source release system, the profile changes are made indifferent ways:n ABAP server Unicode and Java server Unicode If ABAP and Java server both run Unicode, only one kernel is required during regular production operation. However during the upgrade, two kernels exist temporarily. A second, validated kernel is required for ABAP profile changes. This validated kernel is installed automatically during the kernel switch phase of the ABAP server upgrade. At the end of the downtime, the kernel used by the Java server, which is the latest available kernel, is copied to the executable directory.n ABAP server non-Unicode and Java server Unicode Since two kernels are installed, no dependencies exist. Make sure that you have both required SAP kernel DVDs available.Start and Stop of the SAP SystemThe ABAP upgrade program changes the profile parameters for starting and stopping the SAP systemso that the Java instance is not started automatically together with SAP Web Application Server ABAP.The Java upgrade program starts and stops the J2EE Engine with internal commands when required.Reset of UpgradesIf one upgrade fails, you must reset both upgrades. You must not proceed with only one upgradeprocess, since this would lead to an inconsistent system state.Back to Quick Guide [page 21]3.19 Importing Additional LanguagesAfter the upgrade you have the option of importing new languages into the SAP system. Werecommend that you only use this option if the system contains the Support Packages for thelanguage DVD you are using. This is the case if you did not include any additional Support Packagesin the upgrade, or did not import any additional Support Packages after the upgrade. For moreinformation, see the Language Transport documentation, or SAP Note 352941.The upgrade procedure itself only offers to update existing languages. You cannot install any newlanguages during the upgrade. However, you do have the option of classifying new languages in theSAP system before the upgrade with transaction SMLT, and importing them during the upgrade. Formore information about this procedure, see SAP Note 322982.If you intend to use additional languages in your system in the future, import them during theupgrade. In this way, you can avoid any sequencing problems arising from Support Packages includedin the upgrade, or Support Packages you need to import after the upgrade.11/21/2008 PUBLIC 59/144
  • 3 Planning3.20 Handling of Customer-Specific Translations and Z Languages in the Upgrade RecommendationImporting new languages during an upgrade is a highly efficient process and is preferable toimporting a language into a production system after an upgrade.Back to Quick Guide [page 21]3.20 Handling of Customer-Specific Translations and ZLanguages in the UpgradeUsing the translation environment in the SAP system, you can translate missing texts of SAP objectsor translate existing texts, for example, to customize them with your own terminology. For the latter,you need to define your own language (Z language) in the SAP system.SAP system objects that you have changed are scanned by the Repository scanner during the upgrade.Objects for which the SAP standard has not changed for the new release are taken on by the upgrade.Objects that collide with the new SAP standard are offered for modification adjustment.Your translations of SAP system texts are not considered as modifications to the SAP system.Therefore, these translations do not appear in the modification adjustment and are not saved duringthe upgrade of the SAP system.You can preserve your translations by gathering them in a transport request or language package.You then download the request or package from the source system and upload it into the targetsystem. The procedure varies depending on your source release. CautionIf you decide to save your translations, note the following: n In addition to your translations, the transport request also contains language-independent parts. Importing these language-independent parts into the target system using the standard import tool tp or TMS can harm your system considerably! Make sure that you only import them with report RSTLAN_IMPORT_SINGLE. n If SAP has changed the texts for which you have created translations in the target system, the upload of your translation into the target system overwrites the changes made by SAP.Process Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.401. To gather your translations on the source release, you can either create a transport request using report RSLTMOD or create a language package using transaction SMLT_EX.2. Download the transport request or language package before you perform the upgrade.3. Upload the transport request or language package after the upgrade.60/144 PUBLIC 11/21/2008
  • 3 Planning3.21 SAP ECC: Support Packages To upload the language package, use transaction SMLT. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40More InformationFor more information about using transactions SMLT_EX, SMLT, Z languages, and customertranslations, see the language transport documentation in the SAP Library [page 53] for your targetrelease at SAP NetWeaver Library Administrator´s Guide Technical Operations Manual for SAP NetWeaverGeneral Administration Tasks Software Life-Cycle Management Software Logistics Change and Transport SystemLanguage Transport and SAP Note 1015959.Back to Quick Guide [page 21] Only valid for: SAP R/3 4.6C3.21 SAP ECC: Support PackagesAs of Release 4.6, Hot Packages and Legal Change Patches (LCPs) are divided into several subpackages:n Hot Packages: l Support Packages (for technical component SAP_BASIS) l Support Packages (for technical component SAP_ABA) l Support Packages (for technical component SAP_APPL)n Legal Change Patches: l Support Packages (for technical component SAP_BASIS) l Support Packages (for technical component SAP_ABA) l Support Packages (for technical component SAP_APPL) l Support Packages (for technical component SAP_HR) CautionIf you use SAP HR, you must include the Support Packages for the technical component SAP_HR.If you upgrade your system without doing this, the Support Packages for technical componentSAP_HR already imported into your SAP system are canceled and data is lost. Reimporting theSupport Packages in the target release does not solve this problem. We recommend that you includeall existing Support Packages for technical component SAP_HR in the BIND_PATCH phase of theupgrade. For more information, see SAP Service Marketplace at http://service.sap.com/hrsp.Back to Quick Guide [page 21] End of: SAP R/3 4.6C11/21/2008 PUBLIC 61/144
  • 3 Planning3.22 Component Levels Contained in the Upgrade Export3.22 Component Levels Contained in the Upgrade ExportThe transport requests that are imported during the upgrade from the Upgrade Export DVD containdata for the main SAP system components and for add-on components that are included in thestandard SAP delivery of SAP NetWeaver or your SAP solution. For Support Releases, the componentlevels on the DVDs are usually quite high.In the IS_SELECT phase of the Configuration roadmap step, the upgrade program only prompts you foradd-ons contained on the DVD for which we may deliver another update. Add-ons from the standarddelivery for which we will not ship updates until the next release are not offered on the screen. Youdo not have to make a decision about them as they are updated automatically.In the BIND_PATCH phase of the Configuration roadmap step, the upgrade program asks you to includeSupport Packages in the upgrade. If the Upgrade Export DVD already contains a Support Package levelhigher than 0, only include Support Packages above this level.For information about the component levels of the Upgrade Export DVD and on the minimum SupportPackage levels, see SAP Note 774615. CautionIf, for some reason, you must apply Support Packages shortly before the upgrade, make sure that atleast the equivalent Support Package for the target release is available.Back to Quick Guide [page 21]3.23 Using the Application-Specific Update ToolboxThe application-specific update toolbox (ASU toolbox) allows you to manage the preparation andfollow-up activities you need to perform for the technical upgrade.It consists of two parts:n Application-specific content (ASU content definition) in the form of an XML file The XML file contains a list of manual and automatic steps. It is included in the upgrade export and updated with the correction package for the upgrade program.n Interface that interprets the XML file and presents the steps to the user for processing Before the upgrade, this interface displays the preparation activities. After the upgrade, it displays the follow-up activities. Using the interface, you can enhance the XML file with your own activities and comments.Prerequisitesn Your source release SAP system must contain add-on ST-PI with one of the following minimum levels:62/144 PUBLIC 11/21/2008
  • 3 Planning3.24 Internet Pricing and Configurator l 2005_1_<46C/620/640> SP08 l 2005_1_700 SP06 l 2005_1_710 SP04n You require authorization for the following transactions: l /ASU/START l /ASU/UPGRADE l /ASU/SSMn You have the authorizations you require for the individual activities in the ASU toolbox step list. Recommendation Operate the ASU toolbox with a user with SAP_ALL authorizations.ProcedureIn roadmap step Checks, the upgrade program prompts you to call transaction /ASU/UPGRADE.For more information, see SAP Note 1000009. NoteYou can perform the follow-up activities listed in the ASU toolbox in parallel to adjusting repositoryobjects using transaction SPAU.3.24 Internet Pricing and ConfiguratorAs of SAP Business Suite 2005, the Internet Pricing and Configurator (IPC) is part of the software layerSAP Application Platform (SAP AP) 7.0. IPC is no longer a separate server, instead it is processed on theABAP application servers using the Virtual Machine Container (VMC) as runtime environment. Formore information about the architectural changes, see SAP Note 844817.For information about whether you require the IPC for your business processes, see the Upgrade MasterGuide for your application.To be able to use the IPC, you must activate the VMC after the upgrade. For more information, seeActivating VMC for the Internet Pricing and Configurator [page 131].For information about the upgrade from IPC 4.0 to SAP AP 7.0, see SAP Note 844816.Back to Quick Guide [page 21]11/21/2008 PUBLIC 63/144
  • This page is intentionally left blank.
  • 4 Preparation4 PreparationThis part of the document contains information on the preparations that you need to make beforeyou upgrade your system.You can prepare for the upgrade while the system is in production operation. Careful preparation ofthe upgrade is the best guarantee that it will run without errors.The upgrade program supports you here by making most of the necessary checks automatically. Formore information about the checks performed by the upgrade program, see the descriptions ofroadmap steps Extraction, Configuration, Checks, and Preprocessing in Upgrade Process [page 81].ActionsYou perform the following actions before you start the upgrade program:n Determining the Host for the Upgrade Preparations [page 66]n Upgrading with Microsoft Cluster Server [page 66]n Checking the Requirements for the Modification Adjustment [page 67]n Filling the Download Directory [page 67]n Downloading Enhancement Packages [page 68]n Meeting the Requirements for the Upgrade Directory [page 71]n Generating the SAP Solution Manager Key [page 71] Only valid for: SAP ECC 5.00n SAP ECC: Initializing Fields in Table COKEY2 [page 72] End of: SAP ECC 5.00 Only valid for: SAP Web AS 6.20;SAP Web AS 6.40n Unicode SAP Systems: Running Reports RUTTTYPACT and UMG_POOL_TABLE [page 72] 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.40n Preparing the Migration of Workload Statistics Data [page 73] End of: SAP Basis 4.6C;SAP Web AS 6.20;SAP Web AS 6.40n Checking the Consistency of the Host Name [page 73]n Setting the Operation Mode for the Upgrade [page 74]n Providing the JCE Jurisdiction Policy Files [page 75]n Making Preparations at the Database Level [page 76]n Making Preparations at the SAP System Level [page 77] l Deleting the AUTOSTART Parameter [page 77] l SAP ECC: Deleting Application Logs [page 77] l SAP ECC: Backing Up Wage Types in HR [page 78]11/21/2008 PUBLIC 65/144
  • 4 Preparation4.1 Determining the Host for the Preparations Only valid for: SAP ECC 5.00 l SAP ECC: Backing Up UI Conversion Classes in ESS [page 79] End of: SAP ECC 5.00Back to Quick Guide [page 21]4.1 Determining the Host for the PreparationsYou need to prepare for the upgrade on the host with the central instance.ProcedureDecide which hosts you need for the upgrade preparation and the actual upgrade of the SAP system:n Host with the central instance You must execute the upgrade process on the host where the central instance is running. The SL Controller also runs on this host.n Other hosts The Software Distribution Technology graphical user interface (SDT GUI) can run on any hosts that meet the necessary requirements.n Database host You must perform the actions that affect the database on the database host. For a description of these actions, see Making Preparations at the Database Level [page 76].Back to Quick Guide [page 21]4.2 Upgrading with Microsoft Cluster ServerThe SAP system is stopped and started repeatedly during the upgrade. To make sure thatthe configuration for the upgrade program is unchanged during the upgrade, the resourceSAP-R/3<SAPSID> is set offline the first time that the SAP system is stopped. This occurs with thepreconfiguration mode low resource use in the EU_IMPORT1 phase, and with the preconfiguration modestandard resource use or high resource use in the DOWNCONF_TRANS phase.Before you set the resource SAP-R/3<SAPSID> online again in the cluster administrator, follow theinstructions in the section Follow-up Activities for the Microsoft Cluster Server [page 118].Back to Quick Guide [page 21]66/144 PUBLIC 11/21/2008
  • 4 Preparation4.3 Checking the Requirements for the Modification Adjustment4.3 Checking the Requirements for the ModificationAdjustmentIf you modified SAP objects in your SAP system, make sure that you meet the requirements for themodification adjustment [page 47]. CautionIn particular, make sure that changes to the Repository are allowed in the client in which you wantto perform the modification adjustment. To check this, call transaction SCC4.For more information about the requirements for the modification adjustment, see the SAP Library[page 53] for the target release at: SAP NetWeaver Library Function-Oriented View Application Server ABAP Application Development on ASABAP ABAP Customer Development Changing the SAP Standard The Modification Assistant CautionIf you do not make sure that you have met the requirements for the modification adjustment, wecannot guarantee complete support during the adjustment. You also risk losing the data for ABAPDictionary objects.Back to Quick Guide [page 21]4.4 Filling the Download DirectoryYou can put all files and software packages that you want to include in the upgrade in a downloaddirectory. During the Configuration roadmap step, you are prompted to enter the path to the downloaddirectory. The upgrade program reads this directory, unpacks the .SAR files and moves the files to theappropriate directories from where they are then further processed by the upgrade program.For example, when you have downloaded the latest SAP kernel, the unpacked files are moved tosubdirectory exenew of the abap subdirectory of the upgrade directory.You can put the following files in the download directory:n Correction package with corrections for the upgrade program (mandatory) The correction package ensures the stability and high performance of the upgrade tools. For more information about the procedure and the availability of correction packages, see SAP Note 1146578.n Latest SAPup version (optional) For more information about the SAPup version, see SAP Note 1146578n Support Package stacks (optional)n Enhancement packages (optional)11/21/2008 PUBLIC 67/144
  • 4 Preparation4.5 Downloading Enhancement Packagesn SAP kernel (optional) Unless you are performing the upgrade directly after you have received the DVDs, you can always check whether there is a newer version of the SAP kernel available on SAP Service Marketplace and download it to the download directory. The upgrade program then unpacks the files and moves them to subdirectory exenew of the abap subdirectory of the upgrade directory. To download the latest version of the SAP kernel has the following advantages: l You do not have to install the latest SAP kernel after the upgrade. During the KX_SWITCH_1 phase, the upgrade program installs the kernel that is in the exenew subdirectory. If the latest SAP kernel is available in this subdirectory, the SAP kernel of your system is already up-to-date after the upgrade. l You can avoid the prompt during the KX_SWITCH_1 phase that requests you to exchange the SAP kernel files in the exenew subdirectory. This prompt appears if you have included SAP Basis Support Packages in the upgrade and dependencies exist between these Support Packages and the SAP kernel version.n Support Package stack xml file (optional)n DVDs (optional) You can, for example, provide all necessary language DVDs in the download directory.Procedure1. Create a download directory. The directory can be located anywhere on your host.2. Download the required files. n Correction packages and the latest SAPup version are available at http://service.sap.com/swdc Download Support Packages and Patches Entry by Application Group Additional Components Upgrade Tools . n Support Package stacks and the Support Package stack xml file can be downloaded using the Solution Manager Maintenance Optimizer. n SAP kernel files are available at http://service.sap.com/swdc Download Support Packages and Patches Entry by Application Group Additional Components SAP Kernel .Back to Quick Guide [page 21]4.5 Downloading Enhancement PackagesTo download SAP enhancement packages, you use the Maintenance Optimizer in SAP SolutionManager. The Maintenance Optimizer supports you in selecting and downloading all requiredenhancement package and Support Package files.In addition, the Maintenance Optimizer generates an enhancement package stack configuration fileand provides it to the software logistics tools for installation and upgrade using the EPS inbox of SAPSolution Manager. The tools then use this information for installing the enhancement packageand Support Package files.68/144 PUBLIC 11/21/2008
  • 4 Preparation4.5 Downloading Enhancement PackagesPrerequisitesn You have identified which technical usages you want to implement. For more information, see the corresponding Master Guide and SAP Note 1165438.n You have configured the Maintenance Optimizer in SAP Solution Manager as described on SAP Help Portal at http://help.sap.com SAP Solutions SAP Solution Manager SAP Solution Manager <Release> <Language> Change Management Maintenance Optimizer Planning and Monitoring Product Maintenance and also in section Automatically Calculating Product Maintenance Files.n You have assigned an ABAP system to a product maintenance procedure. This system is now automatically considered to be relevant for the upgrade.n In System Landscape Solution Manager (transaction SMSY), you have specified as relevant the Java instances that are installed in the source release system and that are relevant for the upgrade.n You have implemented the SAP Notes listed in SAP Note 1122966.n If you want to use the Software Lifecycle Manager capabilities in the Maintenance Optimizer, you have familiarized yourself with SAP Note 1137683.Procedure1. Start SAP Solution Manager using the transaction solution_manager. To start the Maintenance Optimizer, choose Operations Change Management Maintenance Optimizer .2. In the Maintenance Optimizer, choose the solution for which you want to download enhancement package files.3. Choose Create New Maintenance Transaction.4. Select the product version for which you want to include the enhancement package installation into the upgrade. The Maintenance Optimizer displays all the systems assigned to the selected product version.5. Select the checkbox for the system, for which you want to include the enhancement package installation into the upgrade, and choose Continue.6. On the subsequent screen, select the Upgrade option and then choose Find Download Files. The Maintenance Optimizer displays all installable enhancement package releases for the intended product version.7. Select an enhancement package release and a target Support Package Stack level. Note Bear in mind that during the upgrade, you are only allowed to include SAP enhancement package 4 for SAP ERP 6.0. Lower enhancement package releases are incompatible with SAP NetWeaver 7.0 including enhancement package 1.8. If required by your application, select the technical usage that you want to update with the enhancement package.11/21/2008 PUBLIC 69/144
  • 4 Preparation4.5 Downloading Enhancement Packages Note You require at least the same Java instances that are already installed and used in the source release system. You can only select those technical usages that are appropriate to be included in your upgrade.9. Choose Find Download Files for the Stack Version. The Maintenance Optimizer displays the product maintenance files in three successive lists.10. Select the required files from the displayed lists: n The first list shows all files that depend on the type of your operating system and database system. Select the files that correspond to the combination of your operating system and database and the database-independent files. n You get to the second list by choosing Continue. This list displays all Support Package files that are not assigned to the selected Support Package Stack. You must check whether the Support Package files listed here are suitable for your product maintenance procedure. Deselect the checkbox for the files for the following components: l Components for which you do not want to download Support Packages l Components that you do not want to include in the installation n You get to the third list by choosing Continue. The list displays all product maintenance files that are part of the selected Support Package Stack. Ensure that all files that are assigned to the Support Package Stack are selected here. Files that are not selected will not be included later in the download.11. Choose Continue. To download the files, select whether you want to download them with the Software Lifecycle Manager (SLM) or with the Download Basket, then choose Select Download Type.12. Once the files have been put in your Download Basket, choose Continue and then Confirm Files in Download Basket. A dialog window appears and displays all files.13. Confirm the download for all files.14. Open your SAP Download Manager and download the files to the EPS inbox directory <Drive>:usrsaptransEPSin. Note The stack configuration XML file is generated by the Maintenance Optimizer and saved to the EPS inbox directory of SAP Solution Manager.Back to Quick Guide [external document]70/144 PUBLIC 11/21/2008
  • 4 Preparation4.6 Meeting the Requirements for the Upgrade Directory4.6 Meeting the Requirements for the Upgrade DirectoryThe SAP system is upgraded using the upgrade directory, which can be a softlink to another physicaldirectory. It is divided into subdirectories that can also be softlinks.When you start the upgrade, the upgrade directory is created automatically on the central instancewith the standard path usrsap<SAPSID>upg. NoteIf an upgrade directory with this name already exists, it must be empty. Otherwise the upgradestartup fails.You can also use a different path and name for the upgrade directory. This is useful if you havemultiple SAP systems on a single host and you want to upgrade them all to a new release. To usean upgrade directory other than the default one, you have to specify the directory when you start theupgrade [page 82].ProcedureMake sure that there is enough free disk space for the upgrade directory. This space is required for theupgrade and the logs and is distributed among several subdirectories.For an estimation of the disk space needed for the upgrade directory, see Quick Guide [page 21]. The sizemay vary by up to 25%, depending on your database and source release. NoteWith the System Switch Upgrade, there are dynamic percentages in the subdirectories abapdataand abaplog in the upgrade directory.The following factors increase the amount of free space needed for these directories: n Your systems include extensive customer developments or large amounts of individual documentation. n You want to include Support Packages and add-ons in the upgrade. n Your systems contain languages other than English or German (see Quick Guide [page 21]).4.7 Generating the SAP Solution Manager KeyIn the Configuration roadmap step, you have to enter a key generated by SAP Solution Manager tobe able to proceed with the upgrade.PrerequisitesYou have installed SAP Solution Manager 7.0.11/21/2008 PUBLIC 71/144
  • 4 Preparation4.8 SAP ECC: Initializing Fields in Table COKEY2Procedure1. In your SAP Solution Manager system, call transaction SMSY. The Solution Manager System Landscape screen appears.2. In the System Landscape menu, choose Other Object.3. Set the System indicator.4. From the input help, choose the system for which you want to perform the upgrade.5. Choose Generate Installation/Upgrade Key.6. Enter the requested information. If necessary, change the default values.7. Choose Generate Key. The system displays the key.Back to Quick Guide [page 21] Only valid for: SAP ECC 5.004.8 SAP ECC: Initializing Fields in Table COKEY2With SAP ERP 2004, table COKEY2 has been extended by two fields. As the upgrade does not initializethe fields, you need to run report Z_873466_REPAIR_AFTER_UPGRADE before you perform the upgrade.For more information, see SAP Note 873466.Back to Quick Guide [page 21] End of: SAP ECC 5.00 Only valid for: SAP Web AS 6.20;SAP Web AS 6.404.9 Unicode SAP Systems: Running Reports RUTTTYPACT andUMG_POOL_TABLEIf your SAP system is a Unicode system, reports RUTTTYPACT and UMG_POOL_TABLE must haverun before you start the upgrade tool.Prerequisitesn You are running a Unicode SAP system.n Your source release is SAP Web AS 6.20 or SAP Web AS 6.40.n You have not run reports RUTTTYPACT and UMG_POOL_TABLE in your Unicode SAP system yet.ProcedureRun reports RUTTTYPACT and UMG_POOL_TABLE as described in SAP Note 544623.72/144 PUBLIC 11/21/2008
  • 4 Preparation4.10 Preparing the Migration of Workload Statistics DataFor more information about report UMG_POOL_TABLE, see SAP Note 813445.Back to Quick Guide [page 21] End of: SAP Web AS 6.20;SAP Web AS 6.40 Only valid for: SAP Basis 4.6C;SAP NetWeaver 7.0;SAP Web AS 6.20;SAP Web AS 6.404.10 Preparing the Migration of Workload Statistics Data NoteMigrating the workload statistics data is optional.ProcedureFor detailed information about preparing the migration of your workload statistics data, see SAPNote 1005238.Back to Quick Guide [page 21] End of: SAP Basis 4.6C;SAP NetWeaver 7.0;SAP Web AS 6.20;SAP Web AS 6.404.11 Checking the Consistency of the Host NameFor all references to the host names in the SAP system, you need to check whether you need to enterthe host name in uppercase or lowercase letters. If the host name is inconsistent, problems occur inthe phases PROFCHK and RFCCHK. When you enter the host name, you must use the TCP/IP host name.ProcedureExecute the following steps to check how host names are used:1. Determine the TCP/IP name, by choosing: Start Settings Control Panel Network Connections <Local Area / Public> Protocols TCP/IP Protocol Properties DNS Host Name2. Check the SAP profiles: All references to the host name in SAP profiles (for example, rdisp/btcname, SAPDBHOST, SAPLOCALHOST) must contain the TCP/IP name. The only place where uppercase and lowercase letters are not important is the SAPGLOBALHOST parameter. If you have made corrections to the SAP profiles, stop the SAP system and the SAP Service and start them both again.3. Check the entries in the file etchosts: Edit the file %WINDIR%system32driversetchosts11/21/2008 PUBLIC 73/144
  • 4 Preparation4.12 Setting the Operation Mode for the Upgrade Recommendation We recommend that you maintain all the addresses and host names of all the SAP servers in the grouping in the local file hosts. In addition, insert an entry for the IP address and the TCP/IP name of your computer according to the following convention: <IP address> <TCP/IP host names> Delete any ALIAS entries that assign the host names in a different case lettering than the ALIAS for your IP address. Example of what you should not use: 155.56.172.17 pccpq1 PCCPQ14. Use transaction SM51 to check the host name. The host names in the first and second columns must be identical and must match the TCP/IP host name. The output could appear as follows: pn0014_KKK_10 pn0014 Dialog Update Enqueue Batch If the first parameter is not correct, check step 2 again (Check the SAP profiles). If the second parameter is not correct, check the entries made under step 3 (Check the entries in the file etchosts).5. Check the operation mode definition: Check the case lettering of your host name in the definition of your operating types. To do this, call transaction RZ04 and make sure that the TCP/IP name is always referenced.Back to Quick Guide [page 21]4.12 Setting the Operation Mode for the UpgradeVarious background jobs are started during the upgrade. When you schedule jobs, a check is made tosee whether the SAP instance on which you want them to run is defined in an operation mode. Theoperation mode specifies which services are offered by the work processes (dialog, update, backgroundprocessing, enqueue, spool, and so on).PrerequisitesNo operation modes must exist that contain servers other than those belonging to the current system.Procedure1. Call transaction RZ04 to check the definition of your operation modes. In addition, check the DUMMY operation mode. The DUMMY operation mode may have <host name>_<SAPSID> entered as the server name. Change this entry to <host name>_<SAPSID>_<instance number>.2. Delete the invalid operation modes. If operation modes contain names of servers other than those belonging to the system, problems may arise in the background interface in some phases. The74/144 PUBLIC 11/21/2008
  • 4 Preparation4.13 Providing the JCE Jurisdiction Policy Files jobs may be released, but not set as active (in theory, this affects all jobs scheduled to start on a specific server and triggered by an event).3. If the SAP instance on which you want to upgrade the system is not entered in an operation mode, create the operation mode for the upgrade as follows: a) Call transaction RZ04. b) Choose Operation mode Create . Enter a name for the operation mode, for example, Upgrade. Enter a short description and then save the operation mode. c) Make sure that the instance required for the upgrade has been started up. d) Position the cursor on the new operation mode and choose Operation mode Maintain instances Instances/OP modes . e) Choose Settings Based on act. status New Instances Create . This displays all instances and their current configuration. f) Choose Save. g) Call transaction SM63 to enter the operation mode you have defined as an active operation mode for 24 hours (select Normal operation (24 hours)).Back to Quick Guide [page 21]4.13 Providing the JCE Jurisdiction Policy FilesThe Java Cryptography Extension (JCE) Jurisdiction Policy files are no longer part of SAP JVM.However, without these files a SSL communication between the GUI backend and a remote frontendis not possible.You have to download the policy files from SAP Service Marketplace or from SUN and provide themto the upgrade program using a command line option during the start.ProcedureFor information about the file download, see SAP Note 1240081.Back to Quick Guide [page 21]11/21/2008 PUBLIC 75/144
  • 4 Preparation4.14 Making Preparations at the Database Level4.14 Making Preparations at the Database LevelMaking Database-Specific Preparations for Oracle Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.401. Make sure that the statistics are up-to-date for all tables. Out-of-date statistics can increase the runtime of the upgrade significantly. Proceed as described in Oracle: Performing Actions for the Cost-Based Optimizer [page 132]. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.402. Check the value of parameter shared_pool_size: select NAME, VALUE from v$parameter where name=’shared_pool_size’; select NAME, VALUE from v$parameter where name=’shared_pool_reserved_size’; If the value is lower than 150 MB, increase it to at least 150 MB (400 MB is better), and restart the database.3. Log on as user <sapsid>adm at the operating system level.4. Log on to the database as the Oracle user system with sqlplus (default password is manager).5. Check the resource quotas of the database user SAP<SCHEMA-ID> or SAPSR3: Oracle error 1536 can occur during the upgrade if the resource quotas of database user SAP<SCHEMA-ID> or SAPSR3 are limited. Make sure that these quotas are unlimited. Check whether the table DBA_SYS_PRIVS contains one of the following entries: grantee=’SAPSR3/SAP<SCHEMA-ID>’,privilege=’UNLIMITED TABLESPACE’,adm=’YES’ grantee=’SAPSR3/SAP<SCHEMA-ID>’,privilege=’UNLIMITED TABLESPACE’,adm=’NO’ To do this, enter the following SQLPLUS statement: select * from dba_sys_privs where grantee = ’SAPSR3/SAP<SCHEMA-ID>’; If this entry does not exist, enter the SQLPLUS statement: grant unlimited tablespace to saspr3/SAP<SCHEMA-ID>;6. Log off from the database with the command exit.7. Only if using the dictionary managed tablespaces function: Make sure that the storage parameters MAXEXTENTS and NEXT have the correct values for certain tables and indexes. Otherwise, they may overflow during the upgrade. The Oracle-specific upgrade SAP Note contains the tables and the required minimum values. You can display the current settings with BRSPACE. The index names are not constant. However, you can also determine these names with BRSPACE. SAP Note 11777 describes how to change the parameters NEXT and MAXEXTENTS.8. If your database version is already higher than the minimum version for the new release, we recommend that you exchange the DBA tools (such as BRSPACE) for the upgrade. The Database Software Oracle DVD for the database contains the up-to-date tools that you unpacked on the76/144 PUBLIC 11/21/2008
  • 4 Preparation4.15 Making Preparations at the SAP System Level current SAP kernel when you migrated the database. After you execute the preparation roadmap steps, unpack this archive again into the subdirectory exe of the abap subdirectory of the upgrade directory. This overwrites the DBA tools optimized for the minimum required database version with the tools best suited to your database version.Back to Quick Guide [page 21]4.15 Making Preparations at the SAP System LevelYou need to make the following preparations at the SAP system level:n Deleting the AUTOSTART Parameter [page 77]n SAP ECC: Deleting Application Logs [page 77]n SAP ECC: Backing Up Wage Types in HR [page 78] Only valid for: SAP ECC 5.00n SAP ECC: Backing Up UI Conversion Classes in ESS [page 79] End of: SAP ECC 5.00Back to Quick Guide [page 21]4.15.1 Deleting the AUTOSTART ParameterDelete the parameter AUTOSTART = 1, if it is set, in the start prole (START_<SPECIFICA-TION><INSTANCE_NO>_<HOSTNAME>).Setting the parameter Autostart = 1 causes the SAP service and the SAP system to start when theWindows system is booted.This mechanism must be switched off during the upgrade.You can set the parameter again if required once the upgrade has been successfully completed. Notethat this parameter may not be set in an MSCS cluster configuration.Back to Quick Guide [page 21]4.15.2 SAP ECC: Deleting Application LogsAs of Release 4.6C, application logs are stored in a new format. To be able to read the old applicationlogs, the SAP system has to convert them into the new format. Depending on the amount ofapplication logs, the conversion may be time-consuming. In order to avoid performance problems,you can delete application logs created in releases below 4.6C before upgrading to the new release.11/21/2008 PUBLIC 77/144
  • 4 Preparation4.15 Making Preparations at the SAP System Level CautionOnly delete application logs that you no longer need.ProcedureFor more information on how to delete application logs, see SAP Note 195157.Back to Quick Guide [page 21]4.15.3 SAP ECC: Backing Up Wage Types in HR (T512W) (HRCustomers)We recommend that you back up the wage type table T512W before the upgrade. You must backup this table in the following cases:n You have modified technical wage types, that is wage types beginning with ’/’ (adjustment of processing class, evaluation class, and so on).n You are using SAP model wage types, that is wage types beginning with a letter, and have modified these wage types.n You have defined wage types that do not lie within the customer name range. To find out if this applies, check in table TRESC by entering T512W as the table name and TABU as the object.PrerequisitesYou use the SAP component Human Resources (SAP HR).Procedure1. Before the upgrade, back up table T512W or selected areas of this table. To do this, use report RPU12W0S. The documentation on the report includes instructions on how to proceed. Note Table T512W is client-specific. Make sure that you back up the data in all the SAP HR clients in the system.2. Document exactly which wage types you have modified.3. After the upgrade, you can restore your backup copy. To do this, you can use report RPU12W0C. It reloads selected parts of table T512W. This method is particularly suitable if you have exact documentation about the wage types you have modified.78/144 PUBLIC 11/21/2008
  • 4 Preparation4.15 Making Preparations at the SAP System Level Note If you are not sure whether you have to reload the table data, contact your HR application consultant.For more information about upgrading the SAP application component SAP HR, see SAP ServiceMarketplace at http://service.sap.com/hrupgrade .Back to Quick Guide [page 21] Only valid for: SAP ECC 5.004.15.4 SAP ECC: Backing Up UI Conversion Classes in ESSThe following only applies if your source release is SAP ECC 5.0 and you are running an ESS PersonalInfo scenario. For SAP ECC 6.0, the UI conversion classes have been redesigned. If you have modifiedexisting or created new UI conversion classes, your changes will be lost during the upgrade.Proceduren If you have modified existing UI conversion classes, proceed as follows: 1. Before the upgrade, make a backup copy of the modified UI conversion classes. 2. After the upgrade, enhance the new UI conversion classes in you target release system using the BADI concept.n If you have created UI conversion classes in SAP ECC 5.0, migrate you conversion classes.For more information, see SAP Note 835625.Back to Quick Guide [page 21] End of: SAP ECC 5.0011/21/2008 PUBLIC 79/144
  • This page is intentionally left blank.
  • 5 Upgrade Process5 Upgrade ProcessThis part of the document provides information about upgrading your system.When you upgrade your system, note the following:n Before you start with the upgrade, you must have completed all required planning and preparation actions.n The upgrade program controls the entire upgrade of the SAP system, from checking the requirements and importing the necessary programs through stopping production operation until production operation is resumed. The upgrade procedure is divided up into a number of different roadmap steps. The roadmap steps are in turn divided into phases. The successful completion of a phase is a precondition for the success of all subsequent phases. This section describes all the required user input and actions, as well as critical points during the upgrade. For a complete list of all ABAP phases, see the Phase List. You can find a link to the phase list on the start page of the upgrade program. For more information, see Using the ABAP Phase List for the Upgrade in the document Troubleshooting and Administration [page 53].n The upgrade program must run on the application server of the central instance.n If your central instance and database are running on different hosts, you must perform the actions that affect the database on the database host.n You can use the upgrade logs to monitor the upgrade. The upgrade program logs all actions in the upgrade logs, which you can use as your starting point for troubleshooting.n Many phases of the upgrade require no user input. In the following, you can find a description of all necessary user input.n User actions are also required when errors occur. If an error occurs, correct it and repeat the phase in which the error occurred. Once the phase has been repeated successfully, you can continue the upgrade. For more information about troubleshooting, see the document Troubleshooting and Administration [page 53].n During the upgrade, you are prompted to enter a mount directory for a specific data carrier at the appropriate times. To avoid having to manually enter the mount directory during the upgrade, you can specify several mount directories at the beginning of the upgrade. If you have multiple DVD drives, you can ignore instructions to enter mount directories.11/21/2008 PUBLIC 81/144
  • 5 Upgrade Process5.1 Starting the Upgrade Program Caution If your system is installed in a high availability switch-over environment, make sure that the failover capabilities of the cluster switch-over software are disabled during the downtime. This is to prevent unwanted failover actions during stop actions of the upgrade procedure.Actions Note If the upgrade program displays a dialog box and you need further information about the required input, you can identify the current upgrade phase using the SAPupConsole.log. This log file is located at <upgrade directory>abaplog.You perform the following actions to start and use the upgrade program:n Starting the Upgrade Program [page 82]n Starting the Upgrade GUI [page 83]n Restarting the Upgrade [page 84]n Resetting the Upgrade [page 85]n Importing or Installing Software After Starting the Upgrade [page 86]You perform the following actions during the upgrade roadmap steps:n Making Entries for the Extraction Roadmap Step [page 86]n Making Entries for the Configuration Roadmap Step [page 88] l Entering Paths and Parameters [page 88] l Including Software [page 92] l Making Entries for the Shadow Instance Installation [page 97]n Making Entries for the Checks Roadmap Step [page 98]n Evaluating the Results of the Preparation Roadmap Steps [page 99]n Making Entries for the Preprocessing Roadmap Step [page 104]n Making Entries for the Downtime Roadmap Step [page 108]n Making Entries for the Postprocessing Roadmap Step [page 112]Back to Quick Guide [page 21]5.1 Starting the Upgrade ProgramTo start the upgrade program, you have to execute the startup script from the Upgrade Master DVD.This starts the SL Controller and you can then control the upgrade using the upgrade GUI.Prerequisitesn You have met the requirements for the upgrade.82/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.2 Starting the Upgrade GUIn The database and the SAP system have been started.n You have downloaded the latest version of the correction package [page 67] and any other software that you want to include into the upgrade.Procedure1. Mount the Upgrade Master DVD.2. Log on to the host on which the central instance is running as user <sapsid>adm.3. Start the STARTUP script from the command line with the following command: <DVD drive>: STARTUP.BAT "jce_policy_zip=<path to JCE policy archive>" Note Only use the jce_policy_zip option for the initial start of the upgrade program. If you exit the upgrade program and then restart, do not enter this parameter. If you want to use a different upgrade directory than the default one, then additionally specify the upgrade directory path: STARTUP.BAT "upgdir=<upgrade directory>" Note If you want to use a different upgrade directory, note the following: n User SAPServiceSID must have write access to this directory. n No usrsap<sapsid>upg directory must exist on this host. n The maximum length of the upgrade directory is 24 characters. If you would like the upgrade GUI to start automatically, use the following parameter: STARTUP.BAT "guistart=on" For a detailed description of the actions of the STARTUP.BAT script, see SAP Note 8162114. Start the Upgrade GUI [page 83].Back to Quick Guide [page 21]5.2 Starting the Upgrade GUIThe procedure depends on the host on which you are starting the GUI. We recommend that you callthe GUI from an Internet browser.If, for example, you have to use the SAProuter to pass a firewall, call the GUI by using the Java runtimeenvironment. In this case, you can specify the required routing string.Starting the GUI from the Internet BrowserTo start the GUI from a browser, proceed as follows:11/21/2008 PUBLIC 83/144
  • 5 Upgrade Process5.3 Restarting the Upgrade Program1. Enter the following Internet address: http://<host name>:4239 Replace <host name> with the name of the host on which the upgrade program is running. Note Java WebStart may not be available for the Windows platforms IA64 and X86_64. When you try to start the GUI on http://<host name>:4239, a dialog box that prompts you to open or save the file sdtdsu.jnlp may appear. In this case, you can use an alternative method to start the GUI as described below.2. On the following screen, choose Start Frontend. NoteFrom the same page, you can display the phase list, upgrade documentation, and additionalinformation about the upgrade.Starting the GUI on Windows Hosts1. So that the GUI can be executed on a Windows host, you need an upgrade directory on this host including the following files: n <upgrade directory>sdtlib n <upgrade directory>sdtexeDSUGui.bat2. Start the GUI in a command prompt with the command DSUGui.bat.Back to Quick Guide [page 21]5.3 Restarting the Upgrade ProgramWhen you restart the upgrade program, it continues at the point where it had stopped. You may needto restart the upgrade program in the following cases:n If an error occurred and an upgrade phase terminatedn If a system failure occurredPrerequisitesn If an error occurred, you first have to correct the error. For more information about finding and correcting errors, see the Troubleshooting part of the document Troubleshooting and Administration [page 53]. If you are not sure how to proceed, contact SAP Support.n Before you restart the upgrade after a system failure, you must make sure that you meet the requirements for restarting the system successfully. For more information, see Preparing the Restart of the Upgrade After a System Failure in the document Troubleshooting and Administration [page 53].84/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.4 Resetting the UpgradeProcedureYou can restart the upgrade program by executing the startup script from the upgrade directory:usrsap<SAPSID>upgSTARTUP.BAT Note Only use the jce_policy_zip option for the initial start of the upgrade program. If you exit the upgrade program and then restart, do not enter this parameter.5.4 Resetting the UpgradeYou can reset the upgrade, that is undo all changes that have been done in the system by the upgradeprogram. For example, you may want to reset the upgrade in the following cases:n You want to repeat one of the preparation roadmap steps (steps 1‒ 4) to change an entry.n You ran the preparation roadmap steps for information purposes only and do not want to upgrade the system now, but at a later point in time.n You cannot complete the upgrade in time and therefore need to reset the system to enable production operation again.The procedure for resetting the upgrade depends on the roadmap step the upgrade program hasreached.During the Execution of the Preparation Roadmap StepsAs long as the upgrade is in one of the preparation roadmap steps, you can reset a roadmap step bypressing the Back button of the upgrade GUI.During the Preprocessing Roadmap StepTo reset the upgrade, proceed as follows:1. From the upgrade GUI menu bar, choose Upgrade Reset Upgrade .2. Stop the SL controller.3. Remove the upgrade directory.4. Start the upgrade from the beginning.After Reaching the Downtime Roadmap Step Note Before you overwrite or delete the upgrade directory and the directory usrsap<SAPSID>, make a backup of these directories. SAP Support may need this backup to analyze the error.11/21/2008 PUBLIC 85/144
  • 5 Upgrade Process5.5 Importing or Installing Software After Starting the Upgrade CautionThe time of the backup of the upgrade directory and the directory usrsap<SAPSID> must matchwith the time of the backup of your database.1. Reset the database, directory usrsap<SAPSID>, and the upgrade directory if it is not part of usrsap<SAPSID>. Use the backup you made before entering the Downtime roadmap step, at the end of the Preprocessing roadmap step [page 104].2. There are two options how to proceed: n Reset the upgrade completely and repeat all roadmap steps. To do this, choose Upgrade Reset Upgrade from the upgrade GUI menu. n Continue with roadmap step Downtime without repeating the other roadmap steps. You can leave the upgrade in step Preprocessing until you are ready to proceed with the roadmap step Downtime. NoteIf you want to reset the upgrade after you have upgraded the operating system or database system,you might need to downgrade these software components. For downgrading options, see thevendor´s specification. The safest method is to reload a full backup of the whole system, includingthe operating system.Back to Quick Guide [page 21]5.5 Importing or Installing Software After Starting theUpgradeAfter you have started the upgrade, you may need to import software, such as SAP Support Packages,languages, or add-ons (and add-on updates), or perform an add-in installation of Java software.Procedure1. Reset the upgrade [page 85].2. Import or install the required software.3. Start the upgrade again from the DVD [page 82] and repeat the preparation roadmap steps.Back to Quick Guide [page 21]5.6 Making Entries for the Extraction Roadmap StepEnter the following information or confirm the existing values when prompted by the upgradeprogram:86/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.6 Making Entries for the Extraction Roadmap StepKeyword from the SAP Upgrade Note (Phase KEY_CHK)You must enter the keyword for the upgrade.The keyword, the upgrade program, and the correction package belong together. An error canoccur if the upgrade program or the correction package are outdated. In this case, download thelatest correction package or upgrade program from SAP Service Marketplace and replace them. Ifnecessary, restart the upgrade program.If you have not already done so, request the latest SAP Notes now. SAP Notes are continually beingupdated. For a list of the SAP Notes you need for the upgrade, see SAP Notes for the Upgrade [page 15].Download Directory / Mount Directories for the Data Carriers (PhaseKEY_CHK)You need to enter the path to the download directory.If you have not copied the contents of all necessary data carriers into the download directory, theupgrade program asks for a path to the data carriers. NoteFor more information about which data carriers are required for the upgrade, see Quick Guide [page 21].The other data carriers in the upgrade package are not required by the upgrade program. Theyare used by other programs related to the upgrade, for example, for importing a new version ofthe database system. NoteFor a system that is based on SAP NetWeaver ’04 and higher, the package with the DVDs and CDsneeded for the upgrade contains the following boxes: n Box with the DVDs and CDs for your SAP business system components n Box with the DVDs and CDs for SAP NetWeaverIf the upgrade requires you to install or upgrade a component that is part of the SAP NetWeaverdelivery, for example, SAP kernel or SAP GUI, use the DVDs from the SAP NetWeaver box.If you have only one DVD drive, you do not have to enter any other mount directories. Whenevernecessary, the upgrade program prompts you to specify a mount directory or to change the datacarrier.If you have more than one DVD drive or if you are able to copy the contents of the DVDs and CDsto disk, enter all the mount directories used. You can enter up to 24 mount directories.The maximum length of the mount directory path is 42 characters. It may not contain any blanksor special characters.11/21/2008 PUBLIC 87/144
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap Step NoteWhen you enter the mount directories, you can use a wildcard in the last part of the mountdirectory path, for example, mnt*dvd*. The upgrade program fills the mount directory entryfields with all directories that the wildcard matches. Any duplicate entries found by the wildcardare removed automatically.If you entered mount directories for all data carriers required by the upgrade, and the program findsthe right directory, you are not prompted to enter mount directories. If you do this, you can ignoreall further instructions to enter mount directories in this document.If you do not have enough DVD disk drives, you can copy the contents of each DVD and CD toseparate directories on your hard disk (providing you have sufficient disk space). Specify the names ofthese directories when the program prompts you to enter the mount directories.Password of User DDIC (Phase PROFREAD)You must enter the password of user DDIC in the system, client 000.This password is needed for the RFC connection to the SAP system. To be able to perform all necessaryactions, user DDIC needs the authorization SAP_ALL.During the upgrade, you must unlock the user. After the upgrade, the user will not be lockedagain automatically.Usually, it is not necessary to change the password of user DDIC during the upgrade. If you do changethe password, you have to change it in the original system, the shadow system, and in the upgradeprogram.Back to Quick Guide [page 21]5.7 Making Entries for the Configuration Roadmap StepThis roadmap step asks for all information required to run the upgrade. For clarity, this section isdivided into the following subsections:n Entering Paths and Parameters [page 88]n Including Software [page 92]n Making Entries for the Shadow Instance Installation [page 97]Back to Quick Guide [page 21]5.7.1 Entering Paths and ParametersEnter the following data:88/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap StepConfiguring the Upgrade ProgramTo configure the upgrade program, you can choose between the following preconfiguration modes [page 39]:n Low resource use If you choose this option, the shadow system operation is performed during the downtime to save system resources.n Standard resource use (archiving off during downtime) If you choose this option, the database archiving is switched off during the system downtime. You are prompted to create a database backup before the downtime starts.n High resource use (archiving on) If you choose this option, the database archiving stays active during the whole upgrade process.Port Number for Internal Communication (Phase INITPUT_PRE)To prevent unwanted clients to access the message server as application servers, you need to separateinternal communication from external communication by using different port numbers.During the upgrade, the concept is implemented on the central instance by introducing parameterrdisp/msserv_internal in the default profile.For more information about the concept, see SAP Note 821875.Password of the Operating System User for Installing the ShadowInstance (Phase INITPUT_PRE)The SAP<SAPSID>_<shadow instance no.> service is created during the upgrade for locally installingthe shadow instance. This service is started by the same operating system user as the central instance.Enter the password for the operating system user. You are then asked to verify the password byentering it a second time. CautionIf you change the password for the operating system user, remember that in a standard installation,the SAP service or the SAPOSCOL service run under the same user. This means that you also haveto change this logon data accordingly. Otherwise problems occur when the SAP service is startedafter the SAP kernel switch.Password for Oracle User SYSTEM (Phase DBQUERY_PRE)The upgrade program needs the password for the Oracle user SYSTEM to create the schema for theshadow instance.Upgrade of an MCOD System (Phase MCOD_CHK_INI)The MCOD_CHK_INI phase asks you whether more than one SAP system is installed in your database,which means that you are upgrading an MCOD system [page 42].11/21/2008 PUBLIC 89/144
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap StepTool Versions (Phase TOOLVERSION_INI)The upgrade program checks the tool versions in your system (SAP kernel patch level, the tp version,and the date of R3trans). NoteIf necessary, the upgrade program prompts you to switch the SAP kernel or the other tools to aversion and patch level released for the upgrade.SAP KernelThe subsequent roadmap steps require the version of the SAP kernel released for the upgrade, sinceolder versions contain errors that cause problems in some of the phases. CautionApart from the disp+work package, you also need the corresponding database library for the SAPkernel. CautionDo not replace programs in the preexe, tools and exe subdirectories of the abap subdirectory of theupgrade directory. You may only do this if you get approval from SAP Support.If your current SAP kernel does not fulfill the requirements of the upgrade, proceed as follows:1. Before switching the SAP kernel, back up the existing kernel directory. Caution When you switch the SAP kernel, you overwrite all files and subdirectories in directory usrsap<SAPSID>SYSexerun. For more information, see the log file CHECKS.LOG. Only valid for: SAP Basis 4.6C;SAP R/3 4.6B2. Switch the SAP kernel as described in SAP Note 318846. End of: SAP Basis 4.6C;SAP R/3 4.6B Only valid for: SAP Web AS 6.20;SAP Web AS 6.10 Switch the SAP kernel as described in SAP Note 664679. End of: SAP Web AS 6.20;SAP Web AS 6.10 Only valid for: SAP NetWeaver 7.0;SAP Web AS 6.40 Switch the SAP kernel. End of: SAP NetWeaver 7.0;SAP Web AS 6.4090/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap Step Caution Before continuing the upgrade, make sure that the SAP kernel has at least the minimum required patch level.Tools R3trans and tpThe upgrade may require a certain version for tools R3trans and tp. For the required versions ofthese tools, see SAP Service Marketplace at http://service.sap.com/sdwc Download SupportPackages and Patches .SAP Solution Manager Key (Phase SOLMAN_CHK)You are asked to enter the SAP Solution Manager key.Add-On Strategy Check (Phase ADDON_INFO)For most of the add-ons produced by SAP, there are special SAP Notes containing information aboutthe upgrade strategy. In the ADDON_INFO phase, the upgrade program writes the SAP Note numbersfor your upgrade into the CHECKS.LOG file. The upgrade program lists the general add-on Note as wellas, if possible, specific add-on upgrade Notes to the add-ons installed.Before the upgrade, check all SAP Notes listed in the CHECKS.LOG file. If there are add-ons installed inyour SAP system for which there is no information in one of the listed SAP Notes, refer to the add-onproducer for information.Combined Upgrade & Unicode Conversion (Phase UCMIG_DECISION)If you are upgrading a non-Unicode system, you are asked if you want to perform a CombinedUpgrade & Unicode Conversion (CUUC). If you plan to perform a Unicode conversion after theupgrade, you must answer this question with "yes". In this case, several preparatory steps for theUnicode conversion must already be performed on the source release or in the shadow systemof the upgrade. CautionAs of mySAP ERP 2005, MDMP systems are no longer supported. For these systems, a Unicodeconversion is mandatory before you can use them in production operation.For more information, see http://service.sap.com/unicode@sap Combined Upgrade & UnicodeConversion Library .Back to Quick Guide [page 21]11/21/2008 PUBLIC 91/144
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap Step5.7.2 Including SoftwareMount Directories for Languages (Phase LANG_SELECT)If you have not provided all necessary language DVDs in the download directory, the upgradeprogram prompts you now to mount the necessary directories of the language DVDs. You need to dothis even if only the standard languages English and German are installed in your system.If you have installed languages other than the standard languages, you have the option of excludingsome of these languages from the upgrade. The standard languages are always imported. CautionIf you exclude a language, you cannot work in this language after the upgrade. CautionIf you perform the upgrade in a Terminal Server Session, you also have to mount the language DVDfor accessing the SAP Kernel outside of the Terminal Server Session.To do this, mount the language DVD with the console as user <SID>ADM, or use PCAnywhere. Youcan also copy the contents locally to the hard drive, and specify the path of the local directories tothe upgrade program.In principle, it is possible to install additional languages during the upgrade. For more information,see Importing Additional Languages [page 59]. Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40SPAM Version Check (Phase SPAM_CHK_INI)The upgrade program calls functions of the SAP Support Package Manager (transaction SPAM)to include add-on updates and Support Packages in the upgrade. The upgrade program checksif the level of the SPAM version on your source release is sufficient for the upgrade. If your SPAMversion is not high enough, the upgrade program prompts you to import the latest SPAM updatefor your source release.For more information about importing a SPAM update, see the online help in transaction SPAM,or the SAP Library [page 53] for the corresponding source release. Only valid for: SAP Basis 4.6C;SAP R/3 4.6B;SAP R/3 4.5B;SAP R/3 4.0BChoose Basis Components Upgrade ‒ General Online Correction Support Support Package ManagerImporting Support Packages with the Support Package Manager Importing a SPAM/SAINT Update . End of: SAP Basis 4.6C;SAP R/3 4.6B;SAP R/3 4.5B;SAP R/3 4.0B92/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap Step Only valid for: SAP Web AS 6.20;SAP Web AS 6.10;SAP Basis 4.6DChoose mySAP Technology Components SAP Web Application Server Upgrade ‒ General Online CorrectionSupport Support Package Manager Importing Support Packages with the Support Package Manager Importing aSPAM/SAINT Update . End of: SAP Web AS 6.20;SAP Web AS 6.10;SAP Basis 4.6D Only valid for: SAP Web AS 6.40Choose SAP NetWeaver Solution Life Cycle Manager Software Change Management Support PackageManager Importing Support Packages with the Support Package Manager Importing a SPAM/SAINT Update . End of: SAP Web AS 6.40 End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40Upload of Additional Packages (Phase UPLOAD_REQUEST)The upgrade program prompts you to make additional packages such as add-on upgradepackages (SAINT packages) that are required for the upgrade available in the specified directory. Ifcorresponding add-on DVDs are available, you can add them now. The upgrade program searches forpackages on the DVD and copies them to the EPS directory. For more information about availableadd-on DVDs, see the add-on-specific upgrade Notes. CautionIf you want to include Conflict Resolution Transports as well as Add-On Support Packages foradd-on components, make sure that these packages are also in the EPS inbox.When you select add-ons in the IS_SELECT phase, or when you select Support Packages in theBIND_PATCH phase, the corresponding packages appear as the default value.Enhancement Package ‒ Stack Configuration File (Phase EHP_INCLUSION)You can include an enhancement package into the upgrade in this phase. If your system is connectedto an SAP Solution Manager system, the upgrade program automatically requests the enhancementpackage stack configuration file from it. Otherwise, you have to enter the paths to the stackconfiguration file manually. Based on the provided stack configuration file, the upgrade programcalculates the import queue and checks if all required packages are available in the EPS inbox.Decision About Add-Ons (Phase IS_SELECT)The upgrade program determines all the add-ons that are contained in the SAP system and promptsyou to decide how to proceed. All add-ons that are included on the Upgrade Export DVDs and that youcan update to a new release appear on the selection screen with default status INST/UPG WITH STDCD. For these add-ons, there is no need to make a new decision, unless you want to include a newerversion of the add-on in the upgrade.For add-ons with status UNDECIDED, you have to decide how to proceed.11/21/2008 PUBLIC 93/144
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap StepDepending on the add-on status, there are two different ways to proceed:n Add-on with status INST/UPG WITH STD CD: The add-on is included on the upgrade DVDs. Depending on whether the software components required by the add-on must be kept the same or must be updated, the add-on can also remain unchanged or may have to be updated. You have the following alternatives: l Upgrade with an add-on-specific DVD (Upgrade with Add-On CD) When you choose this alternative, you are asked to insert the corresponding CD. The data is copied to the upgrade directory. l Upgrade to the version on the Upgrade Export DVD (Upgrade to version on std. Upgrade CD) This alternative is valid only if there is an add-on on the Upgrade Export DVD. Once you have chosen this alternative, you do not need any additional CDs or packages for the add-on. Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6B;SAP R/3 4.6C;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40 l Upgrade with SAINT packages (UPG WITH SAINT PACKAGE) The packages must be in the EPS inbox of the transport directory usrsaptransEPSin. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6B;SAP R/3 4.6C;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40n Add-on with status UNDECIDED: These are optional add-ons that were installed on the source system. Caution Your software vendor has predefined the strategy to choose for each add-on. For more information, see the SAP Note displayed by the upgrade program or contact your software vendor. For an add-on with status UNDECIDED, you have the following options in addition to the ones described above: l Keep the present version of the add-on (Keep (with vendor key)). The add-on is transferred unchanged to the new release. Caution You must enter a password if you choose this alternative. l Keep the add-on as it is (Keep yours). The upgrade program only displays this option when you are performing a component upgrade. In this case, the level of the component to which the add-on refers does not change during the upgrade. If you choose Keep yours, the add-on is transferred without any changes to the new release. You do not have to enter a vendor key. During a component upgrade, this option is marked by default. l Delete the add-on (Delete).94/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap Step l Delete the add-on with CD (Delete with CD).To complete phase IS_SELECT successfully, none of the add-ons may have status UNDECIDED.Support Package Confirmation Check (Phase PATCH_CHK3)This phase tests whether all Support Packages have been confirmed.Unconfirmed Support Packages are displayed on the screen and in the PATCHOUT.LOG file insubdirectory log of the abap subdirectory of the upgrade directory. Confirm these Support Packageswith transaction SPAM.If the source release contains Support Packages that are more recent than those in the deliveredtarget release, a warning appears that informs you which Support Packages these are. All softwarecomponents appear whose Support Package level is more up-to-date than the status of the softwarecomponents on the Upgrade Export DVDs. RecommendationAlways include all available Support Packages for the target release, and all available Basis SupportPackages. This means that your system is completely up-to-date after the upgrade.If you use an add-on component, you can find information about including the correspondingAdd-On Support Packages or Conflict Resolution Transports in the SAP Note for the add-onsupplement DVD.If the upgrade program displays a warning that your Support Package level of the source release istoo up-to-date and you want to include the corresponding Support Packages of the target release,you must do this in the next phase BIND_PATCH. You can include the Support Packages for multiplesoftware components in this phase.Including Support Packages (Phase BIND_PATCH)You can include the Support Packages for the target release in this phase.If the release of a component does not change during the upgrade, the Support Packages previouslyinstalled for this component are automatically kept and do not have to be included again. Evenanother adjustment of the modifications contained within using transaction SPDD or SPAU is notrequired. You can also include additional Support Packages for this component.To include Support Packages, proceed as follows:1. If you want to include Support Packages for your various software components, answer Yes to the prompt about including Support Packages in the BIND_PATCH phase. If you did not download the Support Packages during the UPLOAD_REQUEST phase, do this now. Proceed as described in steps 1 to 5 in the description of phase UPLOAD_REQUEST above.2. In the column Selection, enter the Support Package level you want for your various software components.11/21/2008 PUBLIC 95/144
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap Step Note When the BIND_PATCH phase is started for the first time, the upgrade program tries to find a default Support Package queue. It first searches for a package inclusion file of a previous upgrade. If it can find one in subdirectory save of the abap subdirectory of the upgrade directory, the upgrade program checks whether this package inclusion file contains a selection valid for the current upgrade. If the selection is valid, you can use it as default. If there is no package inclusion file from a previous upgrade, the upgrade program calls the SPAM Patch Queue Calculator. It tries to generate a Support Package queue of all Support Packages that you have uploaded. If it can generate a valid queue, you can use it as default. Column Minimum Level contains the minimum Support Package level required for a component to meet the import prerequisites of the add-ons in the IS_SELECT phase. Column Equivalent Level contains the equivalence Support Package level. This is the Support Package level of the target release, which corresponds to the Support Package level of the source release. To avoid data loss, the Support Package level of the target release must not be lower than the equivalence Support Package level. Note You no longer need to reset the upgrade program to reduce the number of Support Packages that you want to include. All you need to do is overwrite the default Support Package level. If you want to cancel the selection for a software component completely, delete the relevant entry. Column Current Level contains the highest Support Package level that is currently included. To find out the current state of the SAP system, the upgrade program checks the following Support Package level information: a) Support Package level that has already been installed in the source system. This only applies when the release of the SAP component does not change during the upgrade (component upgrade procedure). b) Support Package level that is delivered with the upgrade DVDs (for example, a Support Release level) c) Support Package level that has already been selected and confirmed by the customer3. Apart from including Support Packages, you can also include the latest SPAM update for the target release. This prevents any error messages resulting from the fact that your SPAM update in the source release is newer than the SPAM version on the upgrade DVD. It can also save you from having to import the latest SPAM update immediately after the upgrade. The upgrade program automatically looks in the EPS inbox for a current SPAM update and offers it for inclusion.4. In addition, you can include a single change request. In certain situations, you can use a single change request to avoid losing data. The modification adjustment function ignores this request.96/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.7 Making Entries for the Configuration Roadmap Step Caution Using the single change request function is risky. Only use this function if the owner of the request can guarantee that it is compatible with the upgrade. Note Apart from the single change request and the requests for the modification adjustment, there is no other way of importing a request into the system before activation, or during the adjustment of the ABAP Dictionary objects.5. When you confirm the confirmation prompt, you integrate all Support Packages up to the specified level into the upgrade for this component.It may take a few minutes to unpack the Support Package data.You can include any necessary Conflict Resolution Transports (CRTs) in the upgrade. Any SupportPackages that you cannot include in the upgrade must be imported into the system after the upgrade.Request for Automatic Modification Adjustment (Phase ADJUSTPRP)If you want to execute the upgrade program in a target system and you made preparations for anautomatic modification adjustment in the first system, you are prompted to choose a request.Back to Quick Guide [page 21]5.7.3 Making Entries for the Shadow Instance InstallationAll tables of the application server are needed as shadow tables to operate the shadow system.You decide whether to run the central instance and the shadow instance on the same host or ondifferent ones. If you install the shadow instance locally, the upgrade program automatically createsthe SAP Service, required profiles, and directories, and copies programs and files for the shadowinstance in the Installation module. If you run the shadow instance remotely, the dialog instance thatalready exists is adjusted for use as the shadow instance. CautionSAP recommends that you install the shadow instance locally, provided that this does not cause abottleneck of resources when you run both instances at the same time.If you want to run the shadow instance on a separate host, follow the instructions in SAP Note 430992before you start with the entries for the shadow instance installation.Operating System-Specific Actions (Phase SHDINST_OS)The upgrade program performs operating system-specific actions in this phase:11/21/2008 PUBLIC 97/144
  • 5 Upgrade Process5.8 Making Entries for the Checks Roadmap Step1. It maintains the ports that are required for the shadow system in the file %WINDIR%system32driversetcservices.2. If it is a local shadow instance, the SAP service is installed and started for the shadow instance. If it is a remote shadow instance, the existing SAP service is adjusted and started for the shadow instance.Reusing Shadow Instance Profiles (Phase SHDINST_CPY)If you have made a backup of the save directory from a previous upgrade, you can now use the profilesfor the shadow instance [page 141] that have been stored in the directory. CautionOnly use the profiles if both upgrades have the same environment and use the same preconfigurationmode.If you want to use the shadow instance profiles, make sure that the save directory has been copied tothe upgrade directory and confirm the prompt with Yes.Back to Quick Guide [page 21]5.8 Making Entries for the Checks Roadmap StepMaking Entries for the MSCS ConfigurationIn an MSCS configuration, the CONFCHK phase determines that the database and central instance arerunning on different servers and prompts you for the operating system of the database host. Thisprompt also appears if both are running on the same cluster server because, in a cluster, the databaseand the SAP System are assigned different logical host names.Enter the operating system for the database.Starting the Application-Specific Update ToolboxYou can start the application-specific update toolbox (ASU toolbox) using transaction/ASU/UPGRADE. The system loads the XML file (ASU.XML) contained in the upgrade directory,generates a task list, and branches to the task list maintenance.For more information, see SAP Note 1000009. Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.5B;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40Saving VariantsAfter the upgrade, many of your variants can no longer be used because the relevant selection screenshave changed. To save the variants, the SAP system offers two reports:n RASUVAR1 saves your variants on the source system.98/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.9 Evaluating the Results of the Preparation Roadmap Stepsn RASUVAR2 restores the variants in the target system.During phase SAVE_VAR_CHK you can decide whether you want the upgrade tool to run reportRASUVAR1. The report is started in phase JOB_RASUVAR1. If you have decided to run reportRASUVAR1, phase JOB_RASUVAR2 automatically starts report RASUVAR2 towards the end of theupgrade.For more information about the reports, see SAP Note 712297. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.5B;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40Checking the Results of the System CheckAt the end of the Checks roadmap step, the SDTExecution Intervention window displays the results of thesystem check. The entries can be error messages, information, or prompts for user actions.You have to carry out the user actions before you can start with the Preprocessing roadmap step.Back to Quick Guide [page 21]5.9 Evaluating the Results of the Preparation Roadmap StepsThe results of the Checks roadmap step are displayed in a separate window, which opens up oncethis roadmap step is completed. The entries in the windows can be error messages, information,or prompts for user action.You can also find the results in the CHECKS.LOG file. This file is located in subdirectory log of the abapsubdirectory of the upgrade directory.To make sure that all the requirements for the upgrade are met, you can repeat certain roadmapsteps until their status is set to succeeded.ProcedureCheck the entries in the dialog box and perform any measures required by the information it contains.Most of the entries are self-explanatory. You can find information and troubleshooting proceduresfor entries that are not self-explanatory below:n Your Windows dlls have been updated. Reboot your operating system before starting the upgrade. The upgrade program has updated several Dynamic Link Libraries of Windows that contain SAP-specific corrections. You must restart the host before you start the upgrade so that the current DLLs are used.n The buffers of your SAP system instance are not automatically validated. 1. Make sure that parameter rdisp/bufrefmode has one of the following values in the DEFAULT.PFL profile of directory usrsap<SAPSID>SYSprofile:11/21/2008 PUBLIC 99/144
  • 5 Upgrade Process5.9 Evaluating the Results of the Preparation Roadmap Steps Values in DEFAULT.PFL Profile Value Meaning sendon,exeauto Your SAP system (<SAPSID>) has multiple instances. sendoff,exeauto Your SAP system (<SAPSID>) has only one instance. 2. Make sure that parameter rdisp/bufrefmode is not set in the instance profile. If you have distributed application servers that do not use NFS to share access to the profile of the central instance, follow the procedure described above for each server. Caution After making changes to the DEFAULT profile and the START profile you must start up the SAP service to activate the changes. It is not enough to just start the SAP system.n Insufficient freespace in the database as follows: The new release needs more space in the database. The existing space in your database is not sufficient to import the data for the new release. For information about the extensions that you need to make, see the table that follows the message in the dialog box. Add the space you need for any extra data that is created before you actually upgrade your system. The procedure is described in the section Extending Free Space in the Oracle Database in the document Troubleshooting and Administration [page 53]. Recommendation If you are using DICTIONARY managed tablespaces, tablespaces may still overflow during the upgrade. This can happen due to your specific tablespace fragmentation. To avoid unwanted tablespace overflows during downtime, we recommend that you migrate these tablespaces to LOCALLY managed. Alternatively, you should create at least one AUTOEXTENSIBLE segment to ensure that all requirements can be met. Note Due to limited statistical data about table and index sizes, in rare cases the upgrade program may ask for more free space than is actually needed during the upgrade. This occurs especially for index tablespaces. In this case, create a customer message to help us improve the statistics.n In Release <rel> you applied the following unconfirmed patches to your system. There are unconfirmed Support Packages in your SAP system (such as Support Packages for technical components SAP_BASIS, or SAP_BW). To confirm these Support Packages, call transaction SPAM.100/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.9 Evaluating the Results of the Preparation Roadmap Stepsn There are dependencies between Basis Support Packages included in phase BIND_PATCH and the patch level of the target release kernel in directory <upgrade directoy>exe. The disp+work needs at least patch level <number> or higher. Please proceed as described in note 211077. A Support Package included in the upgrade requires a different patch level for the SAP kernel. Proceed as described in SAP Note 211077.n The following function groups (FUGR) are inconsistent. The TADIR entry (and the frame program) have no corresponding entry in the master table TLIBG. Your SAP system contains customer function groups that have not been entered in table TLIBG. To enter the function groups in table TLIBG, call transaction SE80. If you do not fix the problem, the customer function groups will be lost during the upgrade. In case of questions or problems, create a customer message on component BC-DWB-TOO-FUB.n no write permission on <file name>: The specified file in the directory of user <sapsid>adm cannot be overwritten because the authorizations have not been set correctly or the owner of the file is not <sapsid>adm. Correct this by changing the authorizations or the owner.n Release these open transport requests and repairs: Caution If you ignore open repairs, you could lose modifications. Your SAP system contains locked SAP objects in open repairs or requests. The numbers of these repairs or requests are listed. Before you start the upgrade, you must release and confirm all the open repairs and requests listed by the upgrade program, since the objects in them are locked. Note If open repairs that do not belong to this system appear, then this system was created by a database copy. You cannot release these repairs in the normal way. For more information about releasing these repairs, see SAP Note 62519. To release and confirm these open repairs, you must log on to the system with the name of their owner. The list in the dialog box contains these names.n Restart logs of DB conversions found. Outstanding DB conversions found. Your SAP system contains outstanding conversions and restart logs of terminated conversions. Clean these up as described under Cleaning Up Terminated Conversions in the DB Conversion Phases in the document Troubleshooting and Administration [page 53].n Unresolved request found in TRBAT. ....... TRBAT entry indicates that a batch job is running.11/21/2008 PUBLIC 101/144
  • 5 Upgrade Process5.9 Evaluating the Results of the Preparation Roadmap Steps ....... TRBAT entry indicates that a batch job has finished. ....... Corrupted TRBAT entry found. ....... The transport control program tp uses the table TRBAT to communicate with the SAP system. Entries found in this table by SAPup may be the remains of a terminated or running imports or exports. When you prepare the upgrade, locate any entries left over from imports or exports that terminated and clean them up. Do not delete entries made by running imports or exports during production operation. First try to process the TRBAT entries from usrsaptransbin with the following command: tp getprots <SAPSID> This does not affect any imports or exports that are still running.tp informs you about possible processing problems in the file usrsaptranslogSLOG<rel>. You can monitor this file using the command type or tail (MKS tools), but do not use an editor. where <YY> is the year (two digits) and <WW> is the calendar week (two digits). To delete any entries in TRBAT that cannot be processed and that are no longer needed, call transaction SM31. For more information about the transport control program tp, see the SAP Library [page 53] for your source release: Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP R/3 4.6B;SAP R/3 4.5B;SAP R/3 4.0B BC ‒ Basis Components Change and Transport System BC ‒ Transport Tools Transport Control Program tp End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP R/3 4.6B;SAP R/3 4.5B;SAP R/3 4.0B Only valid for: SAP Web AS 6.20;SAP Web AS 6.10 mySAP Technology Components SAP Web Application Server Change and Transport System Transport Tools Transport Control Program tp End of: SAP Web AS 6.20;SAP Web AS 6.10 Only valid for: SAP Web AS 6.40 SAP NetWeaver Library SAP NetWeaver by Key Capability Solution Life Cycle Management Software Change Management Change and Transport System Transport Tools Transport Control Program tp End of: SAP Web AS 6.40n The following indexes <number> were read: Indexes whose names are identical up to the 14th character were found in a table belonging to the substitution set. The 14th character is an ’X’ in one of the two names and is empty in the other. This is an inconsistency and would result in an error during the import of the substitution set. The index with the ’X’ as the 14th character can only have occurred in a previous upgrade or have been created outside the SAP system. For more information, contact your SAP consultant.102/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.9 Evaluating the Results of the Preparation Roadmap Stepsn The following database tables have names that are identical to names of Basis views. The views will be created in this upgrade. Therefore ... Delivered views may have names identical to the names of customer tables in the SAP namespace. You must delete these tables. If you need the table data, you must make a backup before deleting the tables.n Update records still exist - please process Make sure that you have cleaned up all outstanding updates. Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.0B;SAP R/3 4.5B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40 Make sure that you have cleaned up all outbound queue RFC calls by the JOB_RSVBCHCK_R or JOB_RSVBCHCK_D phase (during downtime) at the latest. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.0B;SAP R/3 4.5B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40 If you are still in the preparation phase (before the beginning of the Preprocessing roadmap step) and therefore in production operation, you must only delete the terminated updates. Recommendation We recommend that you clean up as many updates and RFC calls as possible. Otherwise, you will have to clean them up during downtime. To find terminated or outstanding updates, proceed as follows: 1. Call transaction SM13. 2. Delete the default values for the client, user, and time. 3. Select all the update requests. To find outstanding outbound queue RFC calls, proceed as follows: 1. Call transaction SMQ1. 2. Delete the default values for the client. 3. Make sure that the list of outbound queue RFC calls is empty. Otherwise you might lose data in other systems (for example, in SAP BI). Caution If you have installed the PI plug-in, more information is displayed.n Your database and central instance are running on different hosts. Executables have to be transferred to the database host. MSCS Configuration: If the database and the SAP system are running on different nodes in a cluster installation, ignore the above warning.Back to Quick Guide [page 21]11/21/2008 PUBLIC 103/144
  • 5 Upgrade Process5.10 Making Entries for the Preprocessing Roadmap Step5.10 Making Entries for the Preprocessing Roadmap StepConfirmation of Support Packages (Phase PATCH_CHK)This phase checks that the following prerequisites are met:n All Support Packages have to be confirmed for the source release. Unconfirmed Support Packages are displayed on the screen and in the PATCHOUT.LOG file in subdirectory log of the abap subdirectory of the upgrade directory.n The source release does not contain Support Packages that are more recent than those in the delivered target release.If you have to confirm Support Packages for the source release, proceed as follows:1. Call transaction SPAM and confirm the Support Packages that are proposed there.2. If a warning appears that the Support Package level of your source release is too high, proceed as follows: n If you have already included Support Packages in the BIND_PATCH phase, you can ignore this warning. n If you have not included any Support Packages in the BIND_PATCH phase, you will lose data if you continue with the upgrade. In this case, you must reset the upgrade, repeat all phases including phase BIND_PATCH, and include the necessary Support Packages.Keywords for Add-Ons (Phase ADDONKEY_CHK)If you use SAP add-on components in your SAP system (such as IS components), you are promptedfor keywords. SAP systems that have other software components (add-ons) installed on top of themmust wait until the upgrade has been released by the relevant add-on software vendor.Operating System and Database Version (Phase CONFCHK_X)This target release is released for certain combinations of operating system and database versionsonly. This phase checks that the operating system and database versions installed on your computersatisfy the requirements for the upgrade.If the version check determines that the database or the operating system must be upgraded to a newversion, or that you need to import additional software, you can interrupt the upgrade program atthis point. CautionDo not make any changes in the upgrade directory.Conflicts with Customer Tables in the SAP Namespace (Phase VIEWCHK*)This phase displays conflicts between customer tables in the SAP namespace and views that aredelivered for the first time. It also writes this information to a log file.104/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.10 Making Entries for the Preprocessing Roadmap StepYou must rename or delete the tables. If the tables are transparent, you can delete the customer tablesusing the upgrade program. You must delete pool or cluster tables manually in the SAP system.First save any data that you need in these tables.Repairs and Requests Containing Objects Locked by SAP (PhaseREPACHK1)This phase displays all repairs and requests containing objects locked by SAP, and writes them tothe REPACHK1.LOG file.You can ignore the messages at this point. These objects must be released and the repairs confirmedat the latest by the REPACHK2 phase.Outstanding or Incomplete Updates (Phase JOB_RSVBCHCK2)If there are any outstanding or incomplete updates, the upgrade stops in this phase with a message.If errors occur in this phase and you have not stopped production operation yet, you can skip theseerrors with ignore without entering a password. However, we recommend that you check for theseupdates and clean them up. The message is:Update records still exist - Please processFree Space in Subdirectory log (Phase FREECHK_X)This phase checks whether there is enough free space in subdirectory log of the abap subdirectory ofthe upgrade directory during the upgrade. You must have enough free space in the log subdirectoryso that the upgrade can run without errors.During downtime, the SAP programs are substituted in the SAP kernel directoryusrsap<SAPSID>SYSexerun. This phase also compares the free disk space in the SAP kerneldirectory with the space requirements of the new SAP kernel.At this point, make sure that you are able to restore the old SAP kernel, if this becomes necessary. CautionAll files and subdirectories in the kernel directory usrsap<SAPSID>SYSexerun are overwrittenwhen the SAP kernel is switched. For more information, see the log file CHECKS.LOG.ABAP Workbench Locking (Phase LOCKEU_PRE)If you have chosen preconfiguration mode standard resource use or high resource use, the upgrade programasks you in this phase if you want the ABAP Workbench to be locked on all SAP instances now or inphase REPACHK2.This lock is needed to prevent development objects (for example, ABAP reports, table definitions, andso on) from being changed during the upgrade, since these modifications would be lost.If you have chosen preconfiguration mode standard resource use or high resource use, you can continue touse your SAP system in production operation, even if you confirm that the ABAP Workbench canbe locked.11/21/2008 PUBLIC 105/144
  • 5 Upgrade Process5.10 Making Entries for the Preprocessing Roadmap StepIf you confirm the lock now:n The upgrade program does not stop in the REPACHK2 phase to allow you to confirm the lock on the ABAP Workbench. This increases the time in which the upgrade program does not need user input after the last request for a mount directory.n You may not perform any more transports into or out of the SAP system.n The upgrade program waits until the time you entered as the maximum synchronization time for all the instances has expired.Unreleased Repairs and Corrections (Phase REPACHK2)This phase displays all the repairs and corrections that are not released and writes them to theREPACHK2.LOG file.n Before you continue, you must release and confirm all the open repairs; otherwise the objects in them are locked. For a description of this procedure, see Releasing and Confirming Open Repairs and Requests in the document Troubleshooting and Administration [page 53]. Caution If you ignore open repairs, you could lose modifications. Once you have released and confirmed all the open repairs, you must repeat the REPACHK2 phase. Any modifications made to SAP objects in your repairs might be overwritten during the upgrade. For information about how modifications are copied to the new SAP standard during the upgrade, see the SAP Library [page 53] for the target release under SAP NetWeaver Library Function-Oriented View Application Server ABAP Application Development on AS ABAP ABAP Customer Development Changing the SAP Standard Upgrade Procedure / Support Packages .n Preconfiguration mode standard resource use / high resource use: If you did not confirm the ABAP Workbench lock in the LOCKEU_PRE phase, do this now. Note After you have confirmed the ABAP Workbench lock, no more transports can be made into or out of the SAP system. The upgrade program waits until the time you entered as the maximum synchronization time for all instances has expired. This phase displays all the repairs that are still in open transport requests. They are also written to the REPACHK2.LOG file. Release these transport requests so that you can continue; otherwise the objects contained in the repairs will be locked.Terminated Conversion Cleanup (Phase CNV_CHK_XT)This phase checks whether the following still exist:106/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.10 Making Entries for the Preprocessing Roadmap Stepn Unprocessed conversion requestsn Restart logsIf there are errors, you will receive an error message. Proceed as described in Cleaning Up TerminatedConversions in the DB Conversion Phases in the document Troubleshooting and Administration [page 53].Comparison of Modifications (Phase ADJUSTCHK)If you chose to copy a request in the ADJUSTPRP phase, the modifications it contains are now comparedwith the modifications in the system. The result of this comparison appears.You are prompted to confirm that the request was copied. If this request contains all the modificationsfound in the system, the upgrade program does not stop before the activation of the ABAP Dictionaryobjects. However, you can still specify that you want the upgrade program to stop in this phase.Cleanup of Outstanding Updates (Phases JOB_RSVBCHCK_R andJOB_RSVBCHCK_D)If some updates have not been performed yet, the upgrade stops in phase JOB_RSVBCHCK_R (if you usepreconfiguration mode low resource use), or in phase JOB_RSVBCHCK_D (if you use preconfiguration modestandard resource use or high resource use).In this phase you must clean up all outstanding updates. Proceed as follows:1. Clean up the outstanding updates as described in Evaluating the Results of the Preparation Roadmap Steps [page 99]. The message is: Update records still exist - Please process2. Repeat this phase.Incremental Table Conversion (Phase ICNVREQ)If you chose preconfiguration mode standard resource use or high resource use, you are asked if you want touse the incremental table conversion (ICNV). The upgrade program only displays this dialog ifit has found tables that fulfil the prerequisites.Preparation of SAP System for Downtime (Phase DOWNCONF*)If you chose preconfiguration mode standard resource use or high resource use, you are requested in phaseDOWNCONF* at the end of step Preprocessing to perform actions that prepare your SAP system for thedowntime.Perform the following actions:1. Make sure that all production work in the SAP system is stopped and no users are logged on to the SAP system.2. Make sure that all dialog instances are shut down.3. Isolate the central instance. For more information, see Isolating the Central Instance in the document Troubleshooting and Administration [page 53].11/21/2008 PUBLIC 107/144
  • 5 Upgrade Process5.11 Making Entries for the Downtime Roadmap Step4. Back up directory usrsap<SAPSID> including the upgrade directory. In case of problems during the downtime, for example, a hardware failure, you need the backup of the directories to reset the SAP system to the current state. The directories include, amongst others, profiles, trace files, and files for the SAP kernel needed for a reset of the SAP system. Note If the upgrade directory is not part of directory usrsap<SAPSID>, make a separate backup of the complete directory including the subdirectory sdt. Caution Make sure that you can restore the database to this point.Back to Quick Guide [page 21]5.11 Making Entries for the Downtime Roadmap StepActions After Shutdown (Phase STOPSAP_<x>)The upgrade program has stopped the central instance. It prompts you to perform several actions,depending on your database and the preconfiguration mode you have chosen. Once you havecompleted the actions, the upgrade program modifies the instance profile for the duration of thedowntime. NoteIf you want to use transaction RZ10 to adjust the instance profile during or after the upgrade, startby reimporting the current version of the profile into your SAP system. If you do not do this, thechanges made by the upgrade are reset, which can cause the upgrade to stop running.If you want to disable archiving, you are prompted at the beginning of this phase to do the following:n Verify that you can recover the database to its current state at this point. For more information about making backups as well as about the programs brbackup and brarchive, see the SAP online documentation on database administration for Oracle.n Disable the capability of the database to continually restore data. For information about how to do this, see Changing the Oracle Database Recovery Mode in the document Troubleshooting and Administration [page 53].If you called transaction ICNV during the upgrade, the upgrade program checks whether you havealready converted the recommended percentage of the selected data (see Incremental Table Conversion[page 43]). The upgrade program informs you if you have not. If you ignore the information from theupgrade program, the rest of the data is converted in the conventional manner during downtime. Fordetails on the status of the incremental conversion, call transaction ICNV.108/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.11 Making Entries for the Downtime Roadmap StepModification Adjustment (Phase ACT_<Rel>)Depending on the results of the ADJUSTCHK phase, you may be asked at the beginning of this phaseto adjust your modifications to ABAP Dictionary objects so that they correspond to the new SAPstandard version of the objects. CautionThe objects are adjusted on the shadow instance.The ACT_<rel> phase can take very long, particularly when you have made a lot of modifications tothe SAP system or included a lot of Support Packages. This is because report RADMASDSC calculatesthe dependent objects and the activation sequence for all ABAP Dictionary objects that need to beactivated. For example, structures must be activated before they can be used in tables or table types.These dependencies between a set of ABAP Dictionary objects are often complicated. The same kindof dependencies might have to be calculated several times with different input sets. During thiscalculation phase, the mass activator does not write a log. Nevertheless, you can check in the processoverview of transaction SM50 that report RADMASDSC is running. CautionDo not attempt to import adjustment transport requests into the system manually in this phase.This leads to the loss of data in customer fields.Any requests for automatic adjustment from previous upgrades can be included in this upgrade inphase ADJUSTPRP only.You must make adjustments in the ACT_<rel> phase if you have made structural changes to tables.Otherwise, data will be lost.1. On the GUI, confirm that you want to perform a modification adjustment.2. Add an entry for the shadow instance to the SAP Logon. Take the values from the original system for the server and system ID; for the instance number, take the value you specified in the preparation units for the shadow instance. The default value is the instance number of the original system plus one. Since the original system is still running if you use the preconfiguration mode standard resource use or high resource use, you can also log on to the shadow instance in transaction SM59 with the RFC connection SAP_UPGRADE_SHADOW_SYSTEM.3. Log on to the shadow instance with the user DDIC and the DDIC password of the original system. Only the users DDIC and SAP* exist in the shadow instance.4. Call transaction SE06 to set the system change option. Perform the following actions: a) Set the global setting to Modifiable. b) Set the change option for the software components to Modifiable or Restricted modifiable. c) Set the SAP namespace to Modifiable.11/21/2008 PUBLIC 109/144
  • 5 Upgrade Process5.11 Making Entries for the Downtime Roadmap Step5. Call transaction SU01 to create one or more users to perform the modification adjustment. To do this, copy the DDIC user. Caution If you directly create new users, this may cause terminations. Note In some cases, the error message Error occurred in address management appears. You can ignore this error message. The new users exist only on the shadow instance and are not copied to the original system.6. Log on to the shadow instance with one of the new users. Caution Modification adjustment of ABAP Dictionary objects must be performed in client 000.7. Use transaction SPDD to determine the ABAP Dictionary objects that need to be adjusted. For more information about transaction SPDD, see the SAP Library [page 53] for the target release at SAP NetWeaver Library Function-Oriented View Application Server ABAP Application Development on AS ABAP ABAP Customer Development Changing the SAP Standard Upgrade Procedure /Support Packages Adjusting ABAP Dictionary Objects . For an FAQ on SPDD and more information about the Modification Assistant, see SAP Service Marketplace at http://service.sap.com/spau.If errors appear when you activate your own developments after executing this phase, you cancorrect these here since the upgrade program stops when errors occur. However, you also have theoption of choosing ignore to temporarily ignore these errors. You do not need a password to do this. Ifyou chose ignore here, you must activate these objects after the upgrade. CautionOnly choose ignore if you are sure that this does not affect SAP objects.If you are prompted for a password anyway, this means that the activation has been terminated andyou must not continue with the next phase. You first have to remove the cause of the termination. CautionOn the shadow system, adjust only objects of the ABAP Dictionary. You can make changes to the SAPRepository (changing and creating programs or packages, for example), but we do not recommendthis since it may make the system inconsistent.110/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.11 Making Entries for the Downtime Roadmap StepManual Stop of ASCS Instance (Phase REQ_ASCS_STOP)If your SAP system is a high availability system and you run the ASCS instance on a separate host,you have to stop this instance manually now.During the downtime, the upgrade program temporarily installs an ASCS instance on the centralinstance. After the downtime has finished, this temporary instance is no longer needed and isuninstalled by the upgrade program.Profile of User <sapsid>adm (Phase ENVCHK)This phase tests the environment of user <sapsid>adm. If you replace the profiles of this useryou also prevent an obsolete user environment from causing problems during the upgrade. Theenvironment files previously used are copied to <upgrade directory>abapexeINSTALL beforebeing overwritten.The following files are changed.dbenv_<host name>.csh.dbenv_<host name>.sh.sapenv_<host name>.csh.sapenv_<host name>.shstartsap_<host name>_<instance number>stopsap_<host name>_<instance number>If you made changes to the environment of user <sapsid>adm, they are no longer active after theupgrade.1. If this is the case, make the changes again. Caution Do not copy back the environment files that were saved to <upgrade directory>abapexeINSTALL. This can lead to incorrect settings being made.2. If other application servers exist, copy the files listed above, and the change you have made to the environment of user <sapsid>adm to these servers.Manual Start of ASCS Instance (Phase REQ_ASCS_START)If you run a high availability system, you are asked to do the following:1. On the host with the ASCS instance, install the latest SAP kernel.2. Restart the ASCS instance.Database Archiving and Backup (Phase STARTSAP_PUPG)You are asked to make a full backup of your database. If you have deactivated archiving, you are askedto change the archiving mode of your database.For more information about database archiving and backup strategies, see Database-Specific Aspects[page 41].11/21/2008 PUBLIC 111/144
  • 5 Upgrade Process5.12 Making Entries for the Postprocessing Roadmap StepDialog Instances (Phase REQDOWNFINI)At the end of roadmap step Downtime, you are asked to start the dialog instances.Back to Quick Guide [page 21]5.12 Making Entries for the Postprocessing Roadmap StepConfiguration of SAP Start Service (Phase REQSTARTSRV)The upgrade does not configure the SAP start service (sapstartsrv) to automatically start as adaemon when you start the operating system. If you want to set up the automatic start, you need toperform some manual actions.For more information about how to set up the automatic start of the SAP start service during theoperating system startup, see SAP Note 823941.Load Generation (Phase REQGENLD)You can now start to generate loads for your SAP system.For more information, see Generating Loads [page 133]Solution of P-Errors (Phase CHK_POSTUP)You can solve some of the problems that occur during an upgrade after you have completed theupgrade. This type of problem is indicated by a P in the second column of the .ELG logs.You can find a complete list of these P messages in the CHK_POSTUP phase in the LONGPOST.LOG file. Youmust usually remove the cause of these problems before you start using your SAP applications again. ExampleSome of the secondary indexes may not have been created because they were not unique. Use theABAP Dictionary tools (transaction SE14) to create these indexes in the database.To remove an error, proceed as described in the long text of the message.Any messages that you do not handle immediately need to be handled at the next opportunity. NoteIf you receive an error message stating that a table with the naming convention M_<four-charactermatchcode object><one-character ID> does not have an ABAP Dictionary reference, you candelete this table without informing SAP Support.Upgrade Runtime EvalutionOur aim is to provide you with a fast and efficient upgrade procedure. At the end of the Postprocessingroadmap step, the upgrade program extracts statistical data and evaluates the upgrade, for example,calculates the runtimes of the individual phases. Evaluating this information helps us to improve112/144 PUBLIC 11/21/2008
  • 5 Upgrade Process5.12 Making Entries for the Postprocessing Roadmap Stepboth the current upgrade procedure and new upgrades. We would also appreciate feedback onyour experience with the SAP system upgrade. Therefore, we have designed the SAP System UpgradeEvaluation. It contains the following:n Upgrade Evaluation Form This form consists of a simple questionnaire on your experiences with the upgrade and an upgrade log file generated by the upgrade program. Note Your feedback from the Upgrade Evaluation Form is mainly used to identify areas in need of improvement. If you have specific questions on the upgrade and need an answer soon, open a customer message in SAP Support Portal (http://service.sap.com/support).n Upgrade Information Using the corresponding link in the text, you can open the file upana.htm. It is designed to help you evaluate your upgrade and to better plan follow-up upgrades. It contains detailed information about the system, the overall upgrade and the individual phases.The SAP System Upgrade Evaluation is displayed automatically in a browser window.Prerequisitesn A browser has been installed on the machine from which you are monitoring the upgrade. Note Not all browsers are able to send the form.n The machine has an e-mail connection.n The upgrade has finished.ProcedureTo send the Upgrade Evaluation Form to SAP, proceed as follows:1. At the end of the Postprocessing roadmap step, a browser window appears displaying the SAP System Upgrade Evaluation.2. Answer the questions under Upgrade Evaluation Form. Note Answering the questions is optional.3. Choose Send to SAP. This submits the Upgrade Evaluation Form to SAP.11/21/2008 PUBLIC 113/144
  • 5 Upgrade Process5.12 Making Entries for the Postprocessing Roadmap Step Note After the upgrade has finished, you can return to the SAP System Upgrade Evaluation by entering the following path: http://<host name>:4239 Upgrade EvaluationBack to Quick Guide [page 21]114/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6 Follow-Up ActivitiesThis part of the document contains information about the follow-up activities that you need toperform after you have upgraded your SAP system.When you perform follow-up activities, note the following information (in addition to theinformation in Quick Guide [page 21]):n Perform the actions described in Quick Guide [page 21] in the specified order.n Before you start the follow-up activities, you must have run the upgrade up to and including the MODPROFP_UPG phase.n The upgrade program stops in the MODPROFP_UPG phase and prompts you to start several follow-up activities. It then executes the last phases and completes the upgrade. At the same time, you can already perform the specified follow-up activities.The follow-up activities are divided into three blocks:n Actions needed before resuming production operation These actions ensure that all the processes that are relevant to system operation are available again. You can start these actions while the upgrade program is finishing the upgrade.n Actions during limited production operation During this time, your SAP system is already consistent and all the processes that are relevant to system operation are available. However, this system state does not yet contain measures for optimizing performance, or actions for resuming standard operation (resuming background processing, or adjusting authorizations, for example). Check the actions that are listed in this block and perform them before you restart production operation, if necessary.n Actions during production operation You can also perform these actions when the system is back to production operation.ActionsYou must perform the following actions before you resume production operation of your system:n Oracle: Performing Specific Actions [page 117]n Performing Follow-Up Activities for the Microsoft Cluster Server [page 118]n Performing Follow-Up Activities for the SAP Kernel [page 118]n Performing Follow-Up Activities in the Monitoring Area [page 119]n Activating the ICM Service [page 119]n Installing Java Components [page 120]n Reimporting Additional Programs [page 120]n Adjusting Repository Objects [page 120]n Performing Follow-Up Activities for Security [page 121]11/21/2008 PUBLIC 115/144
  • 6 Follow-Up Activitiesn Performing Application-Specific Activities [page 121]n Adjusting Customizing Settings [page 122] Only valid for: SAP Basis 4.6C;SAP Basis 4.6Dn Converting Codepages [page 122] End of: SAP Basis 4.6C;SAP Basis 4.6Dn Adjusting Customer Developments [page 123]n Updating the Where-Used List in the ABAP Workbench [page 123] Only valid for: SAP Basis 4.6C;SAP Web AS 6.20;SAP Web AS 6.40n Migrating the Workload Statistics Data [page 124] End of: SAP Basis 4.6C;SAP Web AS 6.20;SAP Web AS 6.40n SAP ECC: Activating SAP ECC Extensions [page 124]n SAP ECC: SAP HR Customers Only: Reloading Table 512W (Wage Types) [page 124]n SAP ECC: SAP Retail Customers Only: Converting Short Texts [page 125]n SAP ECC: TR-TM Customers and CFM-TM Customers Only: Migrating Data [page 125]n Performing Follow-Up Activities for SAP Solution Manager [page 125]n Secure Single Sign-On with the Microsoft NT LAN Manager SSP [page 125]n Executing the Conversion Programs for the Product Master [page 129] Only valid for: SAP Basis 4.6C;SAP Basis 4.6Dn Migrating Data to Table TVARVC [page 131] End of: SAP Basis 4.6C;SAP Basis 4.6Dn Activating VMC for the Internet Pricing and Configurator [page 131]You can perform the following actions during limited production operation of your system:n Rescheduling Background Jobs [page 132]n Oracle: Performing Actions for the Cost-Based Optimizer [page 132]n Generating Loads [page 133]n Installing the SAP Online Documentation [page 135]n Performing Follow-Up Activities in the Authorizations Area [page 135] 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.40n Performing 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.40n Upgrading or Installing Dialog Instances [page 138]You can perform the following actions during production operation of your system:n Importing Support Packages After the Upgrade [page 138]n Transport Management System: Distributing the Configuration [page 139]n Performing Follow-Up Activities for the Language Transport [page 139]n Oracle: Deleting Tablespaces [page 140]n Saving Files for Follow-Up Upgrades [page 141]Back to Quick Guide [page 21]116/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.1 Oracle: Performing Specific Actions6.1 Oracle: Performing Specific ActionsPrerequisitesYou have not yet resumed production operation of the system.Creating and Updating the SAPDBA RoleTo increase the security of your system, do not assign the DBA role to the OPS$ database users as ofSAP Basis Release 4.x. You have already performed most of the required manual changes when youmigrated Oracle to the required version (see the guide Upgrade to Oracle Database <Version>: <Platform>).The upgrade imports additional objects that you need to adjust. This means that you must executethe SQL scriptsapdba_role.sql again.Proceed as follows:1. Log on as user <sapsid>adm at the Windows level.2. Start the SQL script with: cd %ORACLE_HOME%/database copy <DRIVE>:usrsap<SAPSID>SYSexerunsapdba_role.sql sapdba_role.sql sqlplus /nolog @sapdba_role <SAPSCHEMA-ID> Where <SAPSCHEMA-ID> is SR3 for SAPSR3. If the following error message appears, you can ignore it: Error accessing PRODUCT_USER_PROFILE Warning: Product user profile information not loaded! You may need to run PUBLD.SQL as SYSTEM.Checking the Environment Variables for the BR*Tools ProgramTo check whether all the environment variables have been set correctly for BR*Tools at the Windowslevel, see the SAP Library [page 53] for your target release at SAP NetWeaver Library Administrator´s Guide Technical Operations for SAP NetWeaver Administration ofDatabases Database Administration for Oracle SAP Database Guide: Oracle Getting Started with Oracle and theSAP System Database System Configuration Environment Variables (Windows). Note As of SAP Web AS 6.40, SAP no longer delivers SAPDBA. To help you administer your Oracle database, SAP now provides you with the BR*Tools. The tools can be used for all SAP Releases running on Oracle 9i and higher. For more information about the BR*Tools, see the SAP Library [page 53] for your target release at SAP NetWeaver Library Administrator´s Guide Technical Operations for SAP NetWeaver Administration of Databases Database Administration for Oracle SAP Database Guide: Oracle BR*Tools for Oracle DBA .11/21/2008 PUBLIC 117/144
  • 6 Follow-Up Activities6.2 Follow-Up Activities for the Microsoft Cluster ServerBacking Up the DatabaseThe procedure for backing up the database depends on the mode with which you operated thedatabase during the upgrade.Backup: Database Was Operated in NOARCHIVELOG ModeActivate ARCHIVELOG mode again and create a full backup of the database. This must be executedas an offline backup.Proceed as follows:1. Stop your SAP system.2. Use BRSPACE to activate the ARCHIVELOG mode again. To do this, execute the ARCHIVE_ON.BAT script from the directory usrsap<SAPSID>sysexerun. This stops and starts the database again.3. Use the brbackup program to start the offline backup of the database.4. When you have made the backup, you can start up your SAP system againFor more information about offline backups and brbackup, see the SAP online documentation ondatabase administration for Oracle.Backup: Database Was Operated in ARCHIVELOG ModeSince a large number of archives was created during the upgrade, make a full offline or online backupof the database as quickly as possible. Otherwise restoring the database may be very time-consuming.Back to Quick Guide [page 21]6.2 Follow-Up Activities for the Microsoft Cluster ServerSome follow-up activities are necessary for an MSCS configuration. For more information, see SAPNote 1050343.Procedure1. Stop the SAP system and the SAP service.2. Perform the steps listed in SAP Note 1050343.3. Set the resource SAP-R/3<SAPSID> online in the cluster administrator.Back to Quick Guide [page 21]6.3 Performing Follow-Up Activities for the SAP KernelInstalling the SAP KernelFor production operation, you must replace the SAP kernel that was installed during the upgradewith the current SAP kernel from SAP Service Marketplace.118/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.4 Performing Follow-Up Activities in the Monitoring Area NoteIf you have downloaded the latest SAP kernel files to the download directory [page 67] before the upgrade,you do not have to replace the SAP kernel.For more information about how to install the current SAP kernel, see SAP Note 19466.Checking the saposcol VersionMake sure that your saposcol version matches your operating system, especially with respect to the32-bit and 64-bit distinction.For more information about how to get the latest saposcol, see SAP Note 19227.Back to Quick Guide [page 21]6.4 Performing Follow-Up Activities in the Monitoring Area 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.6B;SAP R/3 4.6C;SAP R/3 4.70 Ext. Set 1.10;SAP R/3 4.70 Ext. Set 2.00;SAP Web AS 6.10;SAP Web AS 6.20Setting Up the Monitoring ArchitectureWith the monitoring architecture of the Computing Center Management System (CCMS), youcan monitor your entire IT landscape centrally, including quick and reliable problem reporting.SAP Support can only provide optimal support for landscapes for which the CCMS has been setup properly.Perform the configuration tasks that are described in the document Monitoring Setup Guide for SAPNetWeaver available on SAP Service Marketplace at http://service.sap.com/instguidesnw<Release> Operations . 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.6B;SAP R/3 4.6C;SAP R/3 4.70 Ext. Set 1.10;SAP R/3 4.70 Ext. Set 2.00;SAP Web AS 6.10;SAP Web AS 6.206.5 Activating the ICM ServiceThe upgrade program disables services of the Internet Communication Framework (ICF) during theupgrade for security reasons. You have to activate the services you require again after the upgrade.ProcedureCall transaction SICF and activate the required services.Back to Quick Guide [page 21]11/21/2008 PUBLIC 119/144
  • 6 Follow-Up Activities6.6 Installing Java Components6.6 Installing Java ComponentsPrerequisites1. You have upgraded the central instance successfully.2. If your SAP system is a non-Unicode system, make sure that the database you are using for the SAP NetWeaver Application Server Java supports Unicode. For more information, see the Product Availability Matrix (PAM) on SAP Service Marketplace at http://service.sap.com/PAM.ProcedureYou can now install Java components as required by your scenario. For more information, see thedocument Upgrade Master Guide ‒ <SAP NetWeaver / SAP application>.Back to Quick Guide [page 21]6.7 Reimporting Additional ProgramsDuring the upgrade, the contents of directory usrsap<SAPSID>SYSexerun are completelydeleted before the new SAP kernel is imported. If you installed additional programs in this directory,such as the RFC library, you must install them again.In roadmap step Checks, you were prompted to protect files that you do not want to be deleted by theupgrade in file protect.lst. If there are files for which you have made a backup in some other way,you can now reimport them into this directory.ProcedureDownload the files for the RFC library, the CPIC library, or ArchiveLink and unpack them intothe kernel directory.You can now also reimport files that you have not protected using file protect.lst.Back to Quick Guide [page 21]6.8 Adjusting Repository ObjectsIf you have made modifications to programs, screens or interfaces (GUIs), you must adjust themwith transaction SPAU.Until now, customer exits were used to enhance the standard SAP system without modifying it. Toexploit the advantages of the new Business Add-In technology, and to unify enhancement techniques,some of the customer exit definitions you use might have been migrated to Business Add-Ins by SAP.You can migrate the customer exits you have implemented to Business Add-In implementations atthe touch of a button. The implementations that need migrating are displayed by the modificationadjustment functions.120/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.9 Performing Follow-Up Activities for SecurityThe enhancement framework does not support modifying enhancement definitions or enhancementimplementations. You can, however, replace them with you own enhancement implementations.ProcedureFor more information about the modification adjustment, see the online documentation for thetarget release under SAP NetWeaver Library Function-Oriented View Application Server ABAP Application Development on ASABAP ABAP Customer Development Changing the SAP Standard Upgrade Procedure / Support PackagesAdjustment of Repository Objects .For an FAQ on SPAU and more information about Business Add-Ins, see SAP Service Marketplaceat http://service.sap.com/spau.For more information about replacing enhancement definitions or enhancement implementation,see SAP Note 922557. NoteAfter you have completed the upgrade you have a maximum of 14 days to execute transaction SPAUwithout the key being checked (SAP Software Change Registration) for the objects that you modified.Back to Quick Guide [page 21]6.9 Performing Follow-Up Activities for SecurityAs of SAP NetWeaver 7.0, there are more settings with which you can increase the security level ofyour message server. For example, you can decide whether external monitors like msmon can connectto the message server or you can separate external and internal communication. NoteThese settings are optional.ProcedureIf you want to increase the security of you message server, proceed as described in SAP Note 821875.Back to Quick Guide [page 21]6.10 Performing Application-Specific ActivitiesSome applications require you to perform some application-specific follow-up activities, withoutwhich the applications cannot run. These application-specific activities are described in the ReleaseNotes for the particular application.11/21/2008 PUBLIC 121/144
  • 6 Follow-Up Activities6.11 Adjusting Customizing SettingsIf you need to display Release Notes in your SAP system, proceed as follows:n In the IMG structure, choose Additional Information Release Notes .n If you want to display the Release Notes independently from the IMG, choose Help Release Notes . When you choose this option for the first time, you are prompted to generate the Release Notes before you can display them.Back to Quick Guide [page 21]6.11 Adjusting Customizing SettingsAfter the upgrade, there are new and changed functions in your SAP system for which you may haveto adjust the Customizing settings. CautionAdjusting the Customizing settings is done in close cooperation with the business consultants andother upgrade project team members.ProcedureTo adjust the Customizing settings for new and changed functions in your SAP system, proceedas follows:1. Call transaction SPRO_ADMIN.2. Select your existing project IMG or create a new Customizing project.3. Create one or more release-specific project views of your project IMG by selecting the activities for delta Customizing and upgrade Customizing.4. Call transaction SPRO.5. Choose Add to work list and add the project view.6. Make the necessary Customizing settings in your release-specific project views.For more information about how to create project views and make Customizing settings, see theonline documentation for the transactions.Back to Quick Guide [page 21] 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.6B6.12 Converting CodepagesIn SAP Basis Release 6.10, the codepage administration has changed considerably. If you have createdcustomer-specific codepages starting with “9”, and you want to continue using them after the122/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.13 Adjusting Customer Developmentsupgrade, convert the codepages with report RSCP0126. For more information, see SAP Notes 485455and 511732.Back to Quick Guide [page 21] 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.6B6.13 Adjusting Customer DevelopmentsThe programs and applications that you have written, which run without errors on the sourcerelease, may contain syntax or runtime errors after the upgrade. These may be caused by additionaldevelopments of the ABAP Workbench, changes to the ABAP syntax, or stronger syntax checks whenyou upgrade from one release of SAP Basis, SAP Web AS, or SAP NetWeaver AS to the next one. Youcan solve these problems by adjusting your programs to the new version of the ABAP Workbench.ProcedureFor information about how to adjust customer developments (recommendations for adjustmentsand instructions), see the following SAP Notes:SAP Note SAP Basis/SAP Web AS/SAP NW AS Release367676 4.6 to 6.10452229 6.10 to 6.20689951 6.20 to 6.40857904 6.40 to 7.0Back to Quick Guide [page 21]6.14 Updating the Where-Used List in the ABAP Workbench NoteThis action is optional.As of Release 6.10, the where-used list for ABAP Dictionary objects and object types has changed. Itnow has an index of its own. If you need a complete display of the where-used list in your SAP system,you must recreate the index after the upgrade.ProcedureTo create the index, you need to run report SAPRSEUB in the background.11/21/2008 PUBLIC 123/144
  • 6 Follow-Up Activities6.15 Migrating the Workload Statistics Data NoteSince the runtime of the report may be quite long, we recommend that you run it in thedevelopment system only.For more information about this report, see SAP Note 28022.Back to Quick Guide [page 21] Only valid for: SAP Basis 4.6C;SAP Web AS 6.20;SAP Web AS 6.406.15 Migrating the Workload Statistics DataProcedureFor detailed information about migrating your workload statistics data, see SAP Notes 1005238 and1006116.Back to Quick Guide [page 21] End of: SAP Basis 4.6C;SAP Web AS 6.20;SAP Web AS 6.406.16 SAP ECC: Activating SAP ECC ExtensionsSAP ECC Extension functions are activated by setting the activation switches. The activation of theswitches highly depends on the later use of the SAP system. CautionBefore you activate a switch, you must discuss this with your business consultants and the projectteam.You cannot deactivate a switch once it has been activated.ProcedureFor more information about activating a switch and the possible restrictions, see SAP Note 816806.Back to Quick Guide [page 21]6.17 SAP ECC: SAP HR Customers Only: Reloading TableT512W (Wage Types in HR)If you have saved table T512W before the upgrade, reload it now. For the exact procedure, see SAP ECC:Backing Up Wage Types in HR (T512W) (HR Customers) [page 78].Back to Quick Guide [page 21]124/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.18 SAP ECC: SAP Retail Customers Only: Converting Short Texts6.18 SAP ECC: SAP Retail Customers Only: Converting ShortTextsYou must replace the short texts for some languages. For more information, see the SAP onlinedocumentation under Help SAP Library SAP R/3 Enterprise Application Components Logistics SAPRetail Basic Principles Retail Terminology .Back to Quick Guide [page 21] 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.006.19 SAP ECC: TR-TM Customers and CFM-TM Customers Only:Migrating DataWith SAP R/3 Enterprise 4.70 with SAP R/3 Enterprise Extension Set 2.00, there have been majorchanges in the data model. If your source release is lower than this, you must perform a data migrationafter the upgrade using transaction TPM_MIGRATION. For more information, see SAP Note 706952.Back to Quick Guide [page 21] End of: SAP R/3 4.6C;SAP R/3 4.70 Ext. Set 1.10;SAP R/3 4.70 Ext. Set 2.006.20 Performing Follow-Up Activities for SAP SolutionManager1. Connect the newly upgraded SAP system to SAP Solution Manager. For more information, see the Configuration Guide: SAP Solution Manager, sections “Solution Monitoring: Setting Up the SAP Solution Manager” and “Solution Monitoring: Setting Up the Service Data Control Center” on SAP Service Marketplace at http://service.sap.com/instguides SAP Components SAP Solution Manager Release <x> .2. Activate the EarlyWatch alert. For more information, see the SAP Solution Manager online documentation at SAP Solution Manager Solution Monitoring Using SAP EarlyWatch Alert .Back to Quick Guide [page 21]6.21 Secure Single Sign-On with Microsoft LAN Manager SSPSingle Sign-On (SSO) is a secure method of logging on to the SAP system that simplifies the logonprocedure without reducing security. When your system is configured for SSO, an authorized userwho has logged on to the operating system can access the SAP system simply by selecting it in the11/21/2008 PUBLIC 125/144
  • 6 Follow-Up Activities6.21 Secure Single Sign-On with Microsoft LAN Manager SSPSAP logon window or clicking the shortcut. No SAP system user name or password is necessary. SSOmakes it significantly easier for you to manage SAP system users.In this section, we describe the option that is the easiest to implement when using a full 32-bitMicrosoft Windows landscape (Windows 9x, Windows ME, Windows NT, Windows 2000 and higher).It is a tailored version for SSO with Secure Network Communications (SNC), which uses Microsoft’sdomain authentication, LAN Manager Security Service Provider (NTLM SSP).For more information about SNC, see the SNC User’s Guide on SAP Service Marketplace athttp://service.sap.com/securityPrerequisitesn Typically, SNC requires an external security product that adheres to the Generic Security Service API V2 (GSS-API V2) interface and that has been certified by the SAP Software Partner Program. However, in this scenario, we provide a library that adheres to the GSS-API V2 interface on one side and that communicates with Microsoft’s NTLM SSP on the other. Since NTLM SSP is already built into Microsoft Windows 32-bit platforms, you do not need to purchase an additional security product to use SSO. Note The Microsoft NTLM SSP only provides authentication based on a challenge-response authentication scheme. It does not provide data integrity or data confidentiality protection for the authenticated network connection. All third-party SNC certified security products offer data integrity and privacy protection. If you want to use these security features, you have to obtain a certified security product. If you use Windows 2000 and higher, we offer an alternative library (gsskrb5.dll) that uses the Microsoft Kerberos SSP instead of the NTLM SSP for authentication. We distribute two different versions of the wrapper library for Microsoft’s NTLM SSP. The older version is called gssapi32.dll and the newer version is called gssntlm.dll. For more information about how to get the gssntlm.dll file, see SAP Note 595341.n A pure Microsoft Win32 environment is required (Windows 9x, Windows ME, Windows NT, Windows 2000 and higher). The Microsoft NTLM SSP is not available for UNIX or any other operating system.n Bi-directional trust between Windows domains is required if there are separate domains for users, front-end PCs, and SAP application servers.n The GSS-API V2 library wrapper (gssntlm.dll) must be installed on every application server.n The GSS-API V2 library wrapper must also be installed on every front-end PC.n We recommend that you use the 7-bit ASCII character set for all Windows user IDs.n When the code page of the SAP system is different from the code page on the Windows machines, it is not possible to enter Windows user IDs that contain 8-bit characters into the USRACL table (for example, by calling transaction SU01). The combination of Windows ANSI (=ISO Latin 1)126/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.21 Secure Single Sign-On with Microsoft LAN Manager SSP and the default SAP code page 1100 provides the same encoding of 8-bit characters and permits the use of 8-bit characters with gssntlm.dll.n For more information about how to improve the security of your system with third-party products, see the SAP Library [page 53] for your target release at SAP NetWeaver Library Function-Oriented View Security Network and Transport Layer Security Secure Network CommunicationsProcedure1. Prepare the application server for Single Sign-on. a) Start the service NT LM Security Support Provider: A) Choose Start Programs Administrative Tools Services . B) Select the service NT LM Security Support Provider. C) Choose General. D) Change the startup type from manual to automatic. b) Copy the gssntlm.dll file to the following directory on your global host: <DRIVE>:USRSAP<SAPSID>SYSEXE<codepage><platform> For more information about how to get the gssntlm.dll file see SAP Note 595341. c) Set the environment variable SNC_LIB to the location of the library. d) In the central instance profile, set the following SNC parameters: snc/data_protection/max =1 snc/data_protection/min =1 snc/data_protection/use =1 snc/enable =1 snc/gssapi_lib = (<DRIVE>:USRSAP<SAPSID>SYSEXE<codepage><platform><gssntlm.dll>) snc/identity/as =p:<DOMAIN_NAME>SAPService<SAPSID> SAPService<SAPSID> is the user who runs the SAP system. <DOMAIN_NAME> is the Windows domain of this user. Note If you use a local account for SAPService<SAPSID>, most operations are successful. However, any operations or communications where the SAP system initiates SNC-protected communication to a remote machine, do not work with a local account for SAPService<SAPSID>. Therefore, use a domain account. Additional SNC Parameters The following profile parameters let you continue with password-based access to the SAP system when SNC has been enabled. To log on to the SAP system as an administrator to maintain the mapping of Windows user accounts to SAP system user IDs (user and client), you have to use these additional parameters at least once after enabling SNC. Once the mapping (at11/21/2008 PUBLIC 127/144
  • 6 Follow-Up Activities6.21 Secure Single Sign-On with Microsoft LAN Manager SSP least for the administrator) has been entered, you can disable further password-based logons by removing the respective profile parameters. snc/accept_insecure_cpic =1 snc/accept_insecure_gui =1 snc/accept_insecure_rfc =1 snc/permit_insecure_start =1 snc/permit_insecure_comm =1 e) Stop and restart the SAP system to activate the profile parameters. Changes to SNC profile parameters always require an application server restart to take effect.2. Prepare SAP GUI and SAP Logon for Single Sign-on. a) Copy the gssntlm.dll file to the SAP GUI directory. For downloading the gssntlm.dll file, see SAP Note 352295. b) Set the Windows environment variable SNC_LIB on the PC where your SAP GUI runs. The variable specifies the path to the gssntlm.dll file. You can do this using one of the following methods: n Copy gssntlm.dll to a location of your choice and set the environment variable SNC_LIB to that location, for example, <DRIVE>:<SAPGUI_PATH>gssntlm.dll A) Right-click My Computer and choose Properties Advanced Environment Variables . B) In User Variables for <user> enter the following: Variable: SNC_LIB Value: <DRIVE>:<SAPGUI_PATH>gssntlm.dll C) Confirm your entries with OK. D) To activate the new environment variable setting, log off and log on to your Windows system again as the same user. n Copy gssntlm.dll to a directory of the default search path, for example, %SystemRoot%system32 and rename the file to sncgss32.dll. This is the default file name that SNC uses when SNC_LIB is neither entered on the command line nor available in the environment. c) Set the required logon options to activate SSO: A) In the SAP logon window, right-click an entry and choose Properties. B) Select the Network tab and activate Activate Secure Network Communication. C) In the SNC name field, enter: p:<DOMAIN_NAME>SAPService<SAPSID> <DOMAIN_NAME> is the Windows domain that the user SAPService<SAPSID> belongs to. Example If the system HWA is running on account SAPServiceHWA of the DEC_NT domain, you enter: p:DEC_NTSAPServiceHWA128/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.22 Executing Conversion Programs for the Product Master The SAP Logon window now displays an icon with a small yellow key beside the system entry. This indicates that SSO is active. When the SAP administrator has entered the mapping between a user’s Windows Account and the user’s SAP system user ID, the next time this SAP system user logs on to the system, the application is opened without requiring the user to enter a user name and password. If only one possible match exists between the Windows account and the SAP system user ID, the logon screen is skipped, unless the profile parameter snc/force_login_screen = 1 is present in the instance profile of the application server.3. Map SAP system users to Windows users for Single Sign-On. a) Log on to the SAP system. b) Choose Tools Administration User Maintenance Users or call transaction SU01. The User Maintenance window appears. c) Enter the name of the SAP system user and choose User names Change . d) Choose SNC. e) In SNC name, use uppercase to enter the name of the Windows user that is to be assigned to the SAP system user: p:<DOMAIN_NAME><NT_USERNAME> <DOMAIN_NAME> is the Windows domain that the Windows user belongs to <NT_USERNAME> is the logon ID of the Windows user. p is a prefix that all SNC names require. Example For the Windows user Kissnerj, belonging to the domain SAP_ALL, enter: p:SAP_ALLKissnerj f) Select Insecure communication permitted. This lets the user work in a different domain because it permits the user to access the system without SSO. g) Save your entries.Back to Quick Guide [page 21]6.22 Executing Conversion Programs for the Product MasterAs of SAP NetWeaver 7.0, several conversion programs needed for the product master are bundledinto the single program COM_PRODUCT_UPGRADE. This program makes enhancements ortechnical modifications in any of the following areas, if necessary:n It ensures that all search helps that are required in the locator of transaction COMMPR01 for product maintenance exist.11/21/2008 PUBLIC 129/144
  • 6 Follow-Up Activities6.22 Executing Conversion Programs for the Product Mastern It creates TADIR objects for already existing table entries. This affects the following transport objects: l SETT for set types l ATTR for attributes l ILTP for relationship types l ILOT for relationship object types l ALID for alternative ID types l SETA for set type attributesn It ensures that all structures that are required for the template framework (TFW) exist.After you have run report COM_PRODUCT_UPGRADE in the SAP system for which you have madethe upgrade, you have to run it again in each subsequent system because it also converts master data.The runtime depends on various parameters including the following:n The number of defined set types and attributesn The number of search helps requiredn The number of TADIR objects to be createdn The source release NoteYou can only call up the product master once you have executed this program. If you attempt towork with the product master without executing the program, the system tells you to execute it first.Prerequisitesn The upgrade log LONGPOST.LOG (displayed in roadmap step Postprocessing [page 112]) requests you to execute the upgrade report COM_PRODUCT_UPGRADE.n You have the authorization to maintain set types and attributes. NoteThe set types you have defined might be partly regenerated during the conversion. Any changesthat you have made to the source code are overwritten. For this reason, make sure that you backup your changes before you execute this program. To do this, you can create a copy of the set typefunction group ZOM<SETTYPE_NAME>.Procedure1. Call transaction SE38 and execute report COM_PRODUCT_UPGRADE. When you execute report COM_PRODUCT_UPGRADE, the SAP system asks for a transport request. This transport request serves to collect all generated objects to transport them into the subsequent system.2. Import the transport request into the subsequent systems to convert the master data. This avoids that database tables and classes are generated again.130/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.23 Migrating Data to Table TVARVC3. Run report COM_PRODUCT_UPGRADE again in each subsequent system. CautionSince this is a cross-client report, only execute this report once in each system in your SAP systemlandscape.ResultAny error, warning or information messages that appear during the conversion are recorded in a log.Back to Quick Guide [page 21] 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.5B6.23 Migrating Data to Table TVARVCAs of SAP Web Application Server 6.10, the cross-client table TVARV is replaced by the client-specifictable TVARVC. You maintain the table with transaction STARV. After the upgrade, you need tomigrate the data from table TVARV to table TVARVC using report RSTVARVCLIENTDEPENDENT.This report copies the data from table TVARV to table TVARVC in all clients.ProcedureRun report RSTVARVCLIENTDEPENDENT before you use the SAP system in production operation.For more information, see SAP Note 557314.Back to Quick Guide [page 21] End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP R/3 3.1I;SAP R/3 4.0B;SAP R/3 4.5B6.24 Activating VMC for the Internet Pricing and ConfiguratorIf you want to use the Internet Pricing and Configurator 7.0, you have to activate the Virtual MachineContainer (VMC). For information about whether you require the IPC for your business processes,see the Upgrade Master Guide for your application.ProcedureActivate the VMC as described in SAP Note 854170.Back to Quick Guide [page 21]11/21/2008 PUBLIC 131/144
  • 6 Follow-Up Activities6.25 Rescheduling Background Jobs6.25 Rescheduling Background JobsUse this procedure to release all background jobs that were locked when you isolated the centralinstance.Procedure Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.5B;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.401. Log on in client 000 as user DDIC.2. Execute report BTCTRNS2. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 4.5B;SAP R/3 4.6B;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40Errors may occur if a background report was changed by the upgrade, since the report variants will nolonger be correct. If this is the case, you must reschedule the job.Back to Quick Guide [page 21]6.26 Oracle: Performing Actions for the Cost-Based OptimizerThe following text only describes those actions that you need to perform for the Cost-BasedOptimizer (CBO) directly after the upgrade. For more information about this topic, see the followingdocuments in the target release online documentation:n SAP NetWeaver Library Administrator´s Guide Technical Operations for SAP NetWeaver Administration of Databases Database Administration for Oracle SAP Database Guide: Oracle BR*Tools for Oracle DBA BRCONNECT Update Statistics with BRCONNECT Note As of SAP Web AS 6.40, SAP no longer delivers SAPDBA. To help you administer your Oracle database, SAP now provides you with the BR*Tools. The tools can be used for all SAP Releases running on Oracle 9i and higher. For more information about the BR*Tools, see the SAP library under SAP NetWeaver Library Administrator´s Guide Technical Operations for SAP NetWeaver Administration of Databases Database Administration for Oracle SAP Database Guide: Oracle BR*Tools for Oracle DBAn SAP NetWeaver Library Administrator´s Guide Technical Operations for SAP NetWeaver Administration of Databases Database Administration for Oracle SAP Database Guide: Oracle CCMS: Oracle Update Statistics for Cost-Based Optimizer in CCMS (Oracle)132/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.27 Generating Loads Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP R/3 4.6B;SAP R/3 4.5B;SAP R/3 4.0BUpdating the StatisticsIf your system had Basis Release 4.x before the upgrade, your database is already running in cost-basedoptimizer mode. After the upgrade you only need to update the statistics. NoteUse the following command to call the brconnect program:brconnect -c -f stats -t allIf the user system does not have the default password manager you need to add the followingcommand option in front of the –f option:-u system/<password>You can do this during production operation. System performance is reduced considerably duringthis time. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP R/3 4.6B;SAP R/3 4.5B;SAP R/3 4.0BScheduling Periodic Statistics UpdatesMake sure that the statistics are updated at regular intervals. After the database has been in use forone day after the upgrade, schedule the next call periodically (every Saturday or Sunday night, forexample).brconnect -u / -c -f stats -t allYou can schedule these actions with transaction DB13. For more information about transaction DB13,see the online documentation under Help Application help .Back to Quick Guide [page 21]6.27 Generating Loads CautionBefore starting the load generation after the upgrade, make sure that the new SAP kernel has beeninstalled. If you have placed the SAP kernel files in subdirectory exenew of the abap subdirectory ofthe upgrade directory, the SAP kernel has been installed by the upgrade tool. SAP kernel parametersintroduced in the new SAP kernel might otherwise invalidate the loads.After an upgrade, many loads do not yet exist in the SAP system and need to be generated. Loadgeneration requires a large amount of system resources. There are several ways to create loads afterthe upgrade, depending on the way you use the SAP system.n For objects that are new in the SAP system after the upgrade, you can use transaction SGEN to create the following loads:11/21/2008 PUBLIC 133/144
  • 6 Follow-Up Activities6.27 Generating Loads l ABAP programs in the SAP system When you call an ABAP program, a load is automatically generated if it does not already exist for this program. This may, however, impair performance in a production system. To avoid this, you can generate the missing loads using the option Regenerate after an SAP System upgrade in transaction SGEN before you use the system in production operation. l Business Server Page applications (BSP applications) If you plan to implement BSP applications in your SAP system, you can generate them with the SGEN option Generation of BSP Applications. l Web Dynpro applications Select the SGEN option Generation of Web Dynpros. Transaction SGEN offers the following functions: l Selection of predefined generation tasks l Selection of software components (such as SAP_ABA, SAP_BASIS) to restrict the amount of objects being generated l Selection of the application servers for parallel generation l Generation in the background l Job Monitor for checking the progress of the generation in the backgroundn If you want to regenerate invalidated loads after the upgrade, you can use report RSGENINVLAS. This report regenerates all invalidated ABAP loads for every machine type that exists in your system. Note The load of an object is invalidated if, since the time the load was generated, activated changes have been made to the object or objects used by this object (such as includes or tables). This can occur, for example, in SAP systems into which you import objects regularly. To minimize wait times for users or developers while the SAP system regenerates invalidated loads, you can schedule the report RSGENINVLAS to run periodically (every night, for example).Generating Loads with Transaction SGEN1. Call transaction SGEN.2. Select one of the following options: n Regenerate after an SAP System upgrade n Generation of BSP Applications n Generation of Web Dynpros3. Repeat the generation for all options that you want to perform.For a detailed description of these features, see the online documentation in transaction SGEN bychoosing Information on the SAP Load Generator , or in the Job Monitor by choosing Job Monitor .For more information about the free space requirements in the load tables, see SAP Note 186066.134/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.28 Installing the SAP Online DocumentationRunning Report RSGENINVLAS NoteRunning the report is optional.1. Call transaction SE38.2. Run report RSGENINVLAS.Back to Quick Guide [page 21]6.28 Installing the SAP Online DocumentationYou must perform the following actions before you can display the online documentation (SAPLibrary) in your SAP system:Install the online documentation from the documentation DVD. The instructions for installing thedocumentation are on the DVD in file Onldoc_e.pdf or Onldoc_e.htm.Back to Quick Guide [page 21]6.29 Performing Follow-Up Activities in the AuthorizationsAreaAdjusting the Assignments Between Check Flags and TransactionsYou can use transaction SU24 to do the following:n Deactivate checks within a transaction.n Define proposals for the profile generator for activated checks.Both the check flags and the default values are based on SAP default values. To change these, calltransaction SU24.To copy the latest SAP default values while retaining your own modifications, call transaction SU25(steps 2 and 3):n This transaction displays the differences between your own check flags or authorization default values and the new SAP default values for all the changes by SAP.n It also defines all the roles that will have to be generated later on with the profile generator, so that authorizations can be generated for all the current checks.For more information, see the online documentation for transaction SU25.11/21/2008 PUBLIC 135/144
  • 6 Follow-Up Activities6.29 Performing Follow-Up Activities in the Authorizations AreaUpward Compatibility for Authorization Checks Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40Some functions are protected in more detail by new authorization objects in the new release. Theauthorizations for these new objects are in the single profiles S_NEW_<rel><number>, where<rel> is the release for which the new authorization check was delivered. The composite profileSAP_NEW contains all single profiles S_NEW_<rel><number>. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40 Caution Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40The SAP_NEW composite profile contains all the individual S_NEW_<rel><number> profiles.This means that the composite role also contains the overall authorization for the S_TCODE check. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40Every user should have the profile SAP_NEW in his or her master record. This guarantees that afteran upgrade users can still perform the same functions that they were able to perform previouslywithout an authorization check. Before this, delete all the individual profiles from SAP_NEW thatrefer to releases that are lower than the source release for the upgrade.After the upgrade the user administrator must go through the profile SAP_NEW and decide for eachauthorization object, into which customer profile the authorizations need to be copied. This defineswhich users can continue to perform the corresponding functions. Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40Empty and activate the SAP_NEW profile after completing these actions. To do this, remove thesingle profile S_NEW_<rel><number> from the composite profile SAP_NEW. Keep the singleprofiles S_NEW_<rel><number>, so that you can find out later which authorization appearedin which release. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP Web AS 6.10;SAP Web AS 6.20;SAP Web AS 6.40 CautionThe SAP_NEW profile does not contain the authorizations for functions delivered in the upgrade. Itonly contains the authorizations for new checks in functions that have already been delivered.Handling Problems with User BuffersIf the user master records were already very large before the upgrade, the predefined buffer size mightnot be large enough for the newly delivered profiles. If you encounter authorization problems afterthe upgrade where authorizations are missing for users although they are included in the masterrecord, see SAP Note 10187.136/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.30 Performing Follow-Up Activities for Application Link Enabling (ALE) Only valid for: SAP Web AS 6.20;SAP Web AS 6.40Setting Up Additional UsersIf you are planning to use your SAP ABAP system together with an SAP NetWeaver Application ServerJava that has been newly installed on Release 7.0 or higher, you need to set up the following additionalusers in the ABAP system to avoid communications errors between the ABAP and Java systems:n ADS_AGENTn ADSUSER Caution Do not maintain roles for these users. End of: SAP Web AS 6.20;SAP Web AS 6.40Back to Quick Guide [page 21] Only valid for: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 3.1I;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6B;SAP R/3 4.6C;SAP Web AS 6.20;SAP Web AS 6.406.30 Performing Follow-Up Activities for Application LinkEnabling (ALE)If you are upgrading from SAP NetWeaver 2004 or lower and you are using Application Link EnablingShared Master Data Management (SMD), you need to migrate the change pointers to the new tableBDCP2. Until you have migrated all change pointers, both the former and the new table are used. Forperformance reasons, migrate the change pointers as soon as possible after the upgrade.Procedure1. To check which message types are affected and how many change pointers need to be migrated, run report RBDCPMIG_ALL_WITHOUT_MIG_FLAG in test mode.2. Decide if you want to run the report for all message types at once or separately. Running the report for each message type separately splits up the total runtime into smaller sections.3. Run report RBDCPMIG_ALL_WITHOUT_MIG_FLAG in production mode.For more information, see SAP Note 1165059. End of: SAP Basis 4.6C;SAP Basis 4.6D;SAP NetWeaver 7.0;SAP R/3 3.1I;SAP R/3 4.0B;SAP R/3 4.5B;SAP R/3 4.6B;SAP R/3 4.6C;SAP Web AS 6.20;SAP Web AS 6.4011/21/2008 PUBLIC 137/144
  • 6 Follow-Up Activities6.31 Upgrading or Installing Dialog Instances6.31 Upgrading or Installing Dialog InstancesAfter the upgrade of the central instance, you need to upgrade the dialog instance to the new release.To do this, you install the new dialog instance on top of the old dialog instance using the tool SAPinst. Note If you experience problems when installing a new ABAP dialog instance on top of the old one, uninstall the old dialog instance first.You can now also install more dialog instances, if necessary.ProcedureProceed as described in the document Installation Guide ‒ <SAP NetWeaver / SAP application>(<Technology>) on <Operating System>: <Database>. Caution If you upgrade a dialog instance, make sure to use the same instance number as on the source release.Back to Quick Guide [page 21]6.32 Importing Support Packages After the UpgradeTo make sure that your SAP ABAP software is running smoothly, we recommend importing newSupport Packages into your system as soon as they become available. This also applies after theupgrade, to avoid potential problems in your system before they occur.If you have not included all the necessary Support Packages in the upgrade, you can still importthem after the upgrade. Note For the ABAP Support Packages, apply the most recent SPAM update.ProcedureImport all missing Support Packages including the most recent Support Package.138/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.33 Transport Management System: Distributing the Configuration Caution If you want to install additional languages in your SAP ABAP system, perform the language import before you import the ABAP Support Packages. The Support Packages always contain the current language version for text-relevant objects. For information about importing a language, see the SAP Library [page 53] for your target release at SAP NetWeaver Library Administrator´s Guide Technical Operations Manual for SAP NetWeaver Administration of SAP NetWeaver Systems AS ABAP (Application Server ABAP) Software Logistics Language Transport and SAP Note 1015959.Back to Quick Guide [page 21]6.33 Transport Management System: Distributing theConfigurationAfter an upgrade, you must distribute the information about the new release to all systems in thetransport domain.ProcedureIf your Transport Management System has already been set up, proceed as follows:1. Log on to the system that is configured as the domain controller.2. Call transaction STMS and choose Overview Systems .3. Select the system that has been upgraded and choose SAP System Update Configuration .4. Choose Extras Distribute TMS Configuration .Back to Quick Guide [page 21]6.34 Performing Follow-Up Activities for the LanguageTransportTo reduce downtime during the upgrade, some data from the Languages DVD was only importedinto container tables, and not yet imported into the actual database tables of the system. This dataincludes glossary and terminology data. If you want to use a glossary or terminology in your system,use the following procedure to copy the data from the container tables to the database tables.Prerequisitesn You have imported a language during the upgrade.n You are using a glossary or terminology in your system.11/21/2008 PUBLIC 139/144
  • 6 Follow-Up Activities6.35 Oracle: Deleting TablespacesProcedureCall transaction SMLT.The transaction automatically recognizes that follow-up activities are necessary, and schedulesa background job for this purpose. CautionFor languages that have been supplemented before the upgrade, you have to repeat thesupplementation after the upgrade with transaction SMLT.Back to Quick Guide [page 21]6.35 Oracle: Deleting TablespacesAfter the upgrade, several tablespaces are empty and are no longer used. You can delete thesetablespaces. This applies to the following tablespaces in a System Switch Upgrade (<source release>is the source release for the current upgrade):For a non-MCOD system:n PSAPES<source release>Dn PSAPES<source release>In PSAPEL<source release>Dn PSAPEL<source release>IFor a system with MCOD layout:PSAP<SAPSID><source release> NoteIf the source release is the same as the target release, the upgrade program cannot use the normalnaming conventions. To distinguish the old tablespace from the new tablespace, SAPup adds an X tothe name of the new tablespace: PSAPES<source/target release>DX. In this case, you can delete theold tablespace PSAPES<source/target release>D.To delete tablespaces, use the program BRSPACE. This program checks whether the followingprerequisites are met:n The tablespace is empty.n The space has actually been released. You may be asked whether you want to wait until Oracle releases the files. NoteMake sure that no other application has access to the files.140/144 PUBLIC 11/21/2008
  • 6 Follow-Up Activities6.36 Saving Files for Follow-Up UpgradesProcedure1. Start the program BRSPACE at the operating system level as user <sapsid>adm with the following command: brspace –f tsdrop2. Choose Drop tablespace.3. Select the tablespace you want to delete.4. Choose Continue to drop the tablespace. If the tablespace is empty, BRSPACE executes the drop command on the database and deletes the data files at the operating system level.Back to Quick Guide [page 21]6.36 Saving Files for Follow-Up UpgradesIn phase SAVEPRO, several upgrade files are saved in subdirectory save of the abap subdirectory of theupgrade directory. If you perform a follow-up upgrade with the same environment and the samepreconfiguration mode, you can reuse these files.PrerequisitesYou are planning a follow-up upgrade with the same environment and the same preconfigurationmode.Procedure1. After the upgrade, make a backup of subdirectory save of the abap subdirectory of the current upgrade directory.2. When you start with the new upgrade, copy the save subdirectory to the new upgrade directory. Note You can copy the subdirectory as soon as you have created the new upgrade directory. The new upgrade directory has to be empty. The following files are saved in the directory and can be used in a follow-up upgrade: n Shadow system profile In the preparation phase SHDINST_CPY, you can reuse the shadow system profiles. n Results from phase BIND_PATCH (file patbind.sav) If suitable, you can use the Support Package selection as default selection.Back to Quick Guide [page 21]11/21/2008 PUBLIC 141/144
  • This page is intentionally left blank.
  • A AppendixA AppendixA.1 List of DocumentationDocument Internet AddressUpgrade Master Guide for your SAP application http://service.sap.com/instguides SAP Business Suite Applications <SAP Business Suite Application> <Release> UpgradeMaster Guide for your SAP application http://service.sap.com/instguides SAP Business Suite Applications <SAP Business Suite Application> <Release> InstallationSAP Frontend Installation Guide http://service.sap.com/instguidesNW <Release> InstallationInstalling the SAP Library http://service.sap.com/instguidesNW Other Documentation SAP LibraryInstallation Guide ‒ <SAP application> <Technology> on http://service.sap.com/instguides SAP Business<Operating System>: <Database> Suite Applications <SAP Business Suite Application> <Release> InstallationUpgrading to Oracle Version <x>: <Platform> http://service.sap.com/instguides Other Documentation Database Upgrades OracleConfiguration Guide: SAP Solution Manager http://service.sap.com/instguides SAP Components SAP Solution Manager <Release>11/21/2008 PUBLIC 143/144
  • 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.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may bechanged without prior notice.