KEMBAR78
SUM Process Step by Step For Version Upgrade | PDF | Databases | Kernel (Operating System)
0% found this document useful (0 votes)
263 views4 pages

SUM Process Step by Step For Version Upgrade

The SAP Software Update Manager (SUM) process for a version upgrade consists of six main steps: Extraction, Configuration, Checks, Preprocessing, Execution, and Postprocessing. Each step involves specific activities aimed at preparing, executing, and finalizing the upgrade while minimizing downtime and risks. Thorough preparation and validation at each step are critical for a successful upgrade.

Uploaded by

ganesh.bhadury
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
263 views4 pages

SUM Process Step by Step For Version Upgrade

The SAP Software Update Manager (SUM) process for a version upgrade consists of six main steps: Extraction, Configuration, Checks, Preprocessing, Execution, and Postprocessing. Each step involves specific activities aimed at preparing, executing, and finalizing the upgrade while minimizing downtime and risks. Thorough preparation and validation at each step are critical for a successful upgrade.

Uploaded by

ganesh.bhadury
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

SUM process step by step for version

upgrade
The SAP Software Update Manager (SUM) process for a version upgrade involves six
main steps, each with specific phases and activities to ensure a smooth and successful
upgrade. Here's a detailed step-by-step overview:

1. Extraction

 Purpose: Prepare and extract all necessary files and information for the upgrade.

 Activities include:

 Validating DDIC user credentials.

 Identifying the current database and SAP version.

 Checking the stack XML file and scanning the download directory for patches.

 Extracting files to the EPS/in directory.

 Verifying the SPAM version (skip if already latest).

 Checking system profiles, SAP release, and source/target system validity.

 Implementing pre-upgrade SAP Notes (S-notes).

 Reading system profiles and running initial system checks.

2. Configuration

 Purpose: Set parameters and options for the upgrade process.

 Activities include:

 Defining upgrade type (e.g., downtime-optimized, high complexity).

 Configuring database archiving.

 Setting execution strategies for transaction SGEN.

 Defining maximum parallel processes for load generation, DDL, imports, and
batch jobs.

 Selecting enhancement packages and add-ons.

 Handling modification adjustments (SPDD and SPAU transport requests).


 Calculating add-on queues and preparing adjustment calculations.

3. Checks

 Purpose: Perform extensive system checks to ensure readiness.

 Activities include:

 Checking database space and extending tablespaces if needed.

 Verifying system environment, kernel, OS, and leftover objects from previous
upgrades.

 Checking for activation errors, background job access, and free file system
space.

 Listing locked SAP objects and checking for double entries in update tables.

 Running BW checks and conversion readiness.

4. Preprocessing

 Purpose: Prepare the system for the main upgrade execution.

 Activities include:

 Preliminary upgrade processing.

 Adjusting system settings and locking objects as needed.

 Running transport requests for modification adjustments.

 Preparing shadow system tables for downtime phases.

5. Execution

 Purpose: Perform the actual upgrade and switch to the new system version.

 Activities include:

 Switching the SAP kernel.

 Copying and importing data during downtime.

 Converting application tables and importing remaining data.

 Changing environment variables to the new release.


 Completing the switch to the target system.

6. Postprocessing

 Purpose: Finalize the upgrade and clean up.

 Activities include:

 Saving log files and generating upgrade evaluation reports.


 Running cleanup activities and removing obsolete files.
 Prompting for and facilitating follow-up activities.
 Displaying feedback forms for SAP technical analysis.

Summary Table of SAP SUM Upgrade Steps

Step Key Activities

Extraction Validate credentials, scan patches, extract files, check system profiles and
SAP release

Configuratio Set upgrade parameters, select add-ons, configure parallel processes,


n handle modifications

Checks Verify database space, system environment, kernel, activation errors,


locked objects

Preprocessin Prepare system and shadow tables, lock objects, run transport requests
g

Execution Switch kernel, import data, convert tables, switch environment to new
release

Postprocessi Save logs, cleanup, generate reports, prompt for follow-up activities
ng

This structured approach ensures a controlled and automated upgrade process


minimizing downtime and risks. The SUM tool handles most technical complexities, but
thorough preparation and validation at each step are critical for success [1][2][3][4][5][6].


1. https://basisgenie.blogspot.com/2020/08/sap-sum-software-update-manager-phases.html

2. https://community.sap.com/t5/technology-blog-posts-by-members/sap-sum-software-update-
manager-upgrade-phases/ba-p/13489422

3. https://community.sap.com/t5/technology-blogs-by-members/sap-sum-software-update-manager-
upgrade-phases/ba-p/13489422

4. https://help.sap.com/docs/SLTOOLSET/e77d62449806411cb142a7f58fdc8290/
c08defdfacbf4aaa8f7d981b1b5dec8e.html

5. https://buddysap.com/steps-sap-ehp-stack-upgrade-using-sum/

6. https://www.youtube.com/watch?v=OjhcSKglWsA

You might also like