This blogs will guide you step by step how to upgrade SAP systems using SUM Tool for different SAP Product systems.
Software Update Manager
The Software Update Manager (SUM) is a multi-purpose tool that supports various processes, such as performing a release upgrade, installing enhancement packages, applying Support Package Stacks or updating single components on SAP NetWeaver.
Planning
Before you start the actual upgrade, you have to plan it carefully so that downtime is reduced to a minimum and the upgrade runs as efficiently as possible. We recommend that you start planning your update at least two weeks before you begin it.
Software Update Manager (SUM) is the tool for system maintenance: Release upgrade, EHP implementation, SP stacks implementation for SAP NetWeaver based systems, DMO. SUM is delivered with Software Logistics Toolset 1.0 and can be downloaded from the link:
http://service.sap.com/sltoolset
New SUM patches are released frequently with latest features and fixes for known bug.
The Master Guide (Upgrade Master Guide) takes you through the complete update and references the required documentation for each step. It is essential to read the upgrade guide & master guide for your product version before starting the upgrade.
If there are preparation and follow-up activities for the upgrade that are specific to your product, they are described in a product-specific document. This document is also referenced in the Master Guide (or Upgrade Master Guide).
The required guides can be downloaded from the link:
http://service.sap.com/instguides
Please consider as well that each Operating System and Database combination have their specific SUM guide, available at:
https://service.sap.com/~sapidb/011000358700000783082011E/SUM10_Guides.htm
Alternatively you can follow this path:
http://service.sap.com/sltoolset -> Software Logistics Toolset 1.0 -> Go to the bottom of the page -> Expand “System Maintenance” -> Updating SAP Systems Using Software Update Manager 1.0 SP<XX>
To prepare and perform the update of your SAP system, it is required to verify additional information, not included in the guides. This information is in a range of SAP Notes in SAP Support Portal, which you have to read before you start the preparations.
We recommend to access the following SAP Notes from SAP Support Portal before you start the update procedure:
●Central Software Update Manager Note
● SAP Note for your database
● SAP Note 1940845 - MOpz: enhancement to support new backend services
● DMO Central Note 1813548– in case you are using the Database Migration Option (DMO):
These SAP Notes are updated regularly, make sure that you always use the newest version.
The keyword for performing the upgrade in confirm target roadmap is available in the Software Update Manager note. It is not possible to continue with the upgrade without this keyword.
Additional SAP notes may be required. It can be downloaded using the link:
Before starting the upgrade, it is mandatory to check the CPU, main memory, disk space and page file.
For more information please refer the link:
https://service.sap.com/sizing
Free Disk Space Requirements
Disk space in the file system for the SUM directory, the download directory, and directory DIR_TRANS. The space required depends on the product you are updating.
The Software Update Manager calculates the space requirements for the database. The free space required for the database is approximately in the range from 50 to 200 GB. Please consider it can be higher, depending on your database size and structure.
SUM Directory Approximately 20 GB
Download Directory (temporary space requirement) Approximately 20 GB
DIR_TRANS Approximately 20 GB
Shadow System Approximately the space required for your source release instance, that is, the size of the following directory:
● UNIX: /usr/sap/<sapsid>
● Windows: <Drive>:\usr\sap\<sapsid>
● IBM i: /usr/sap/<SID>
When you upgrade the SAP system, the target release of your upgrade may require you to update the operating system version and database version as well.
You can determine if the target release is supported on your current Operating System and Database using the Product Availability Matrix (PAM):
For upgrades including Database Migration Option, the minimum database versions can be checked in Note 1813548 - Database Migration Option (DMO) of SUM
If you need to upgrade an operating system or database, or migrate a database, then the timing and the sequence of the individual upgrades is of great importance. The procedure differs according to each database.
Please consider that upgrades from older releases may require to be executed in two steps. More details are available in the file SUM_xx_paths.pdf attached to the Central Software Update Manager Note. Cross-check your DB/OS information at PAM for such requirement.
Note: upgrades to target 740 may require Database updates dependent on the target kernel release as well, see details in note 1969546 - Release Roadmap Kernel 740.
Your SAP system should have one of the source releases that are available for your upgrade and DB/OS combination. Different SAP NetWeaver usage types may have different minimum Support Package levels. If you upgrade an SAP NetWeaver-based system containing various usage types, make sure that your source release is on a minimum Support Package level for all usage types implemented in the system.
Please refer to SAP Note 1850327 and its references for Support Package Stack source and update your system if necessary. The correct SP level will be then calculated by Solution Manager Maintenance Optimizer. Additional patches, such as Java patches, can be obtained from:
Typically, SAP systems like SAP ERP, SAP CRM, SAP SCM or SAP SRM are part of an SAP system landscape that contains various interconnected systems. Business processes can run across the various systems. When planning an upgrade of the systems in your landscape, if you want to know whether this has an impact on other systems in your landscape, that is, whether the upgrade requires changes to other systems in the landscape as well, please access:
Preparation
In order to update perform a Support Package Update, EHP installation or Release Upgrades, a stack XML file must be generated in Solution Manager’s Maintenance Optimizer. Landscape verification is required to enable the Maintenance Optimizer to create a proper stack configuration XML file for the correct product constellation.
To be able to generate a correct XML file for the upgrade, please make sure that you read note 1887979 carefully. Also make sure that the LMDB is updated with correct software system info.
Further information and reference:
http://wiki.scn.sap.com/wiki/x/VIwqCw
Maintenance Planning Guide for SAP Solution Manager 7.1 SP05 and higher
If the maintenance to be performed is a Java patch import or the update of a custom component, you have to use the Manually Prepared Directory option.
For more information on this option, read SAP note 1641062 - Single component update and patch scenarios in SUM
In the SUM Update Guide, the Chapter named "Applying Single Component Updates and Patches Using a Manually Prepared Directory" have the steps to be followed and more information.
SAP Host Agent Version 142 or higher is required for the proper execution of the update process.
If it is included in the stack.xml, SAP Host Agent can be automatically installed only in the primary application
server host.
To manually install SAP Host Agent or update it on remote hosts, proceed as described in the SAP Library [page 15]
The Software Update Manager controls the entire procedure, from checking the system requirements and
importing the necessary programs through stopping production operation until production operation is resumed. The procedure is divided up into a number of different roadmap steps. The roadmap steps are in turn divided into individual steps. The successful completion of a step is a precondition for the success of all subsequent steps.
For a complete list of all steps, see the process overview report, which you can access by choosing the GUI menu option -> Update Process Overview .
Alternatively, you can see the ProcessOverview.html file available in the directory <DRIVE>:\<path to SUM directory>\SUM\sdt\htdoc.
In case of any issues please refer the following troubleshooting guide containing information of all the Known issues during the upgrade.
Troubleshooting procedures
Performance issues
Performance during Upgrades and Enhancement Packages http://wiki.scn.sap.com/wiki/x/cAgsG
Troubleshooting guides
System Upgrade And Update central page – http://wiki.scn.sap.com/wiki/x/mYB5Fw
SUM for ABAP – http://wiki.scn.sap.com/wiki/x/hwGlFw
SUM for Java – http://wiki.scn.sap.com/wiki/x/TwGpFw
SPAM & SAINT – http://wiki.scn.sap.com/wiki/x/VAGpFw
For other errors or issues, the following SAP Knowledge Base Article can help you finding a solution:
SAP KBA 2081285 - How to get best results from an SAP search?
Follow-up activities
Please refer to the section 6 of the SUM guide for detailed information of the follow-up activities which need to be performed in the system before releasing the system for Production use.
Emergency procedures
Resetting an upgrade
Please refer to section 5.x of the SUM guide “Resetting the Software Update Manager”.
Additional information is also available in this page.
SAP Note 1790486 - SAP_ABA is in an undefined state that is not safe to be upgraded
Data loss after upgrade
http://wiki.scn.sap.com/wiki/x/WJOPFw
Additional resources
You can also use some of the expert SAP Continuous Quality Checks and SAP Improvement Services during the lifecycle of your upgrade. Some of the available services are:
These services are available as part of SAP support offerings and can also be ordered as single services.
Browse through our catalog of videos, documents, live sessions of Quick IQ’s, Meet the Expert sessions, Expert Guided Implementations, Best Practices and much more.
In case you have any question during the upgrade, please access the Software Logistics space on SAP Community Network, where you will be able to find further information and exchange experiences with other customers and professionals.