Learn SAP Easy

There is a sequence we need to follow,

1. Pre-steps: Please make sure all below steps are checked and completed without any errors.

Initially, Take the screenshot of Source System Version and Target System Version for SUM Upgrade
Read the SUM guide and make sure all the prerequisites are met
Check and Maintenance license using T_code : SLICENSE
SPAM and SAINT has to be in latest level
Maintain the kernel at latest level or skip kernel software selection part during Stack File generation for SP Upgrade.
Update SAP Host Agent to latest patch
Maintain minimum of 95-110 GB free in /usr/sap/ mount point to run SUM
Make sure you have root access at OS level
Check the credentials of <SID>adm user and SYSTEM user (if you are using SAP HANA DB)
Make sure you have access of DDIC in 000
Run BTCTRNS1 to suspend all the background jobs
Take Full Backup of your DB
Stack XML generation (direct to link to generate Stack XML file Generate Stack XML file from Maintenance Planner)
Download the latest SUM software from SAP Support Portal and Extract .SAR file to get SUM folder

2. Actual Upgrade steps:

Run the STARTUP.BAT file in Windows for SUM Launch; Run ./STARTUP in Linux for SUM Launch

A) Welcome screen
B) Specify Credentials: Provide the password of <SID>adm user
C) Select Target: Select either Stack Configuration File or Manually prepared directory to define (here we give path of directory containing the component updates and patches you want to apply to the system)
D) Confirm Target: Based on XML it shows Target system version and current system version.
E) Execute Process:

1. Initialization:

2. Extraction:

3. Configuration:

Here we choose the main configuration of the tool like either standard or advanced
If the screen gives MCOD warning, check the box and continue Next
Max number of ABAP processes during the update.
Max number of parallel processes for execution of SQL commands
Max number of parallel import processes (R3TRANS)
Max number of parallel R3load processes
Select the instance for Back ground job to be executed
Choosing execution strategy for running SGEN
Maintain default parameters here and continue Next.
If there are any kind of SAP Notes displayed please implement and continue further.
If there are any Add-on required select accordingly and continue Next
Support Package selection (Current and Minimum level must be nearly same)
Modification Adjustment (SPDD transport request and SPAU transport request)

4. Checks:

Check for the configuration till now we selected
Tablespace size and file system will be checked if any insufficient size it shows via error to increase the size of that tablespace
List Locked SAP objects
Sometimes it shows error like Update header records found: login to the system and go to SM13 and delete update records

5. Pre-processing:

Now, the system will be locked to create shadow instance, ABAP Workbench locking
SPDD Adjustments
After a while asks for confirmation like to stop all production now, ensure no background jobs running, make sure no user is logged on the system
Then, it will ask for check for actions confirmed and take complete backup of system.

6. Execution:

In this phase, the actual process will be copied from Shadow to Main Instance and system were unavailable here.
The system will upgraded
Any kind of data conversions, migrations be done here (if you have used DMO top)

7. Post-processing:

After downtime has finished and upgraded, system will be unlocked and will be available for post-processing
Check for any SPAU in order to adjust the modifications (else changes will be lost)
Next it will go to start of cleanup processing phase
Creates folder in trans directory (EHPi)

Pages