Introduction
SAP system upgrades and software maintenance are essential for maintaining system performance, compatibility, security and business continuity. SAP provides the Software Update Manager (SUM) to help administrators perform software updates, release upgrades, support package stack updates and supported system conversions.
However, SAP SUM has multiple versions, and choosing the correct one depends on the source system, target release, system architecture and planned maintenance activity.
The three versions commonly discussed by SAP Basis professionals are SUM 1.0, SUM 1.1 and SUM 2.0. Although they serve a similar overall purpose, they are intended for different technical scenarios.
In this blog, we will explain the difference between SUM 1.0, SUM 1.1 and SUM 2.0, their supported use cases, important capabilities and how to determine which version is appropriate for an SAP upgrade.
What Is SAP Software Update Manager (SUM)?
SAP Software Update Manager is a maintenance tool included in the Software Logistics Toolset (SL Toolset). It supports several SAP software maintenance activities, including:
- SAP software release upgrades.
- Support Package Stack and Enhancement Package updates.
- Installation of supported add-ons.
- Updates to individual software components.
- System conversion to SAP S/4HANA or SAP BW/4HANA, where supported.
- Database migration using the Database Migration Option (DMO), where applicable.
SUM guides administrators through technical update procedures, including system checks, preparation, software changes and post-processing activities.
The exact functions available depend on the SUM version, support package level and supported upgrade scenario.
What Is SUM 1.0?
SUM 1.0 is an earlier generation of SAP Software Update Manager. It was used for software maintenance and upgrades of older SAP systems.
SUM 1.0 included different archive variants depending on the kernel requirements and technical scenario. The older SUM 1.0 SP26 is still relevant for certain legacy source systems based on SAP Basis 4.6C, 6.20 or 6.40.
As SAP's maintenance requirements evolved, SUM 1.1 became the successor to SUM 1.0 SP28 for supported scenarios.
Key Points About SUM 1.0
- Designed for earlier SAP software maintenance scenarios.
- Relevant to specific legacy SAP source releases.
- SUM 1.0 SP26 may be required for certain older source systems.
- SUM 1.0 SP28 was succeeded by SUM 1.1 SP00 and later support package levels.
What Is SUM 1.1?
SUM 1.1 is the successor to SUM 1.0 SP28. SAP introduced the SUM 1.1 naming convention in 2022 to reflect changes in kernel support and long-term maintenance.
SUM 1.1 is intended for supported maintenance scenarios involving SAP Java systems, dual-stack systems and certain ABAP systems.
According to SAP's documented decision criteria, SUM 1.1 is generally used when the source system is a Java or dual-stack system, or when an ABAP upgrade targets SAP_BASIS 7.40 or lower. It also applies to specified ABAP source-release scenarios based on SAP Basis 7.00 through 7.40.
Key Points About SUM 1.1
- Successor to SUM 1.0 SP28.
- Supports specified Java and dual-stack maintenance scenarios.
- Used for qualifying ABAP upgrade paths targeting SAP_BASIS 7.40 or lower.
- SUM 1.1 is provided for EXT/EX2 kernel scenarios.
- The appropriate support package and maintenance guide must be checked before starting an upgrade.
SUM 1.1 and SUM 2.0 are maintained in parallel because they cover different technical scenarios. SUM 1.1 is not merely a temporary step that every SAP system must pass through before using SUM 2.0.
What Is SUM 2.0?
SUM 2.0 is designed for supported maintenance scenarios involving modern ABAP-based SAP systems, including systems based on SAP_BASIS 7.50 and higher.
It supports software upgrades, support package updates and relevant system conversion procedures. SUM 2.0 is also used for supported conversions to S/4HANA and SAP BW/4HANA.
SUM 2.0 includes capabilities for database migration through DMO, where supported, and downtime-optimization approaches for eligible maintenance scenarios.
Key Points About SUM 2.0
- Intended for qualifying ABAP single-stack systems targeting SAP_BASIS 7.50 and higher.
- Used for supported SAP S/4HANA system conversion scenarios.
- Supports the Database Migration Option (DMO) for applicable migrations.
- Provides downtime-optimization options for eligible scenarios.
- Includes advanced maintenance capabilities documented in the relevant SUM support package guides.
The correct SUM 2.0 support package must be selected based on the target product, source release, operating system, database and applicable SAP Notes.
Difference Between SUM 1.0, SUM 1.1 and SUM 2.0
The following table summarizes the main differences between the three SAP Software Update Manager versions.
| Comparison | SUM 1.0 | SUM 1.1 | SUM 2.0 |
|---|---|---|---|
| Main role | Earlier SUM generation | Successor to SUM 1.0 SP28 | SUM generation for modern supported ABAP scenarios |
| Typical applicability | Certain legacy source releases | Java, dual-stack and qualifying ABAP scenarios | Qualifying ABAP single-stack systems |
| ABAP target release guideline | Depends on the specific legacy release and procedure | Generally, SAP_BASIS 7.40 or lower | Generally, SAP_BASIS 7.50 and higher |
| Legacy source systems | SUM 1.0 SP26 may be required for specified older releases | Used for supported source releases based on SAP Basis 7.00 and higher | Depends on the supported source-to-target path |
| S/4HANA conversion | Not the standard choice for modern conversions | Not the standard choice for modern ABAP conversion scenarios | Used for supported SAP S/4HANA conversions |
| DMO and migration | Depends on the specific archive and supported scenario | Available for supported procedures | Available for supported procedures, including relevant modern migration scenarios |
| Selection criteria | Legacy source release and tool requirements | Source architecture and supported upgrade path | Target release, source prerequisites and supported procedure |
These release guidelines are intended as a general comparison, not a definitive compatibility matrix. Always confirm the specific source-to-target combination in SAP's official documentation.
SUM 1.0 vs SUM 1.1: What Changed?
SUM 1.1 succeeded SUM 1.0 SP28 and reflected SAP's updated kernel support and maintenance strategy.
The key differences include:
- Updated naming and maintenance: SUM 1.1 introduced a revised version numbering scheme.
- Kernel requirements: SUM 1.1 is provided for EXT/EX2 kernel scenarios, unlike the earlier SUM 1.0 variants.
- Legacy compatibility: Certain older source systems still require SUM 1.0 SP26.
- Supported upgrade paths: SUM 1.1 continues to support specified older ABAP, Java and dual-stack maintenance scenarios.
Therefore, SUM 1.1 should be viewed as the successor to the relevant SUM 1.0 release, rather than as a universal replacement for every older SAP system.
SUM 1.1 vs SUM 2.0: What Is the Main Difference?
The primary difference between SUM 1.1 and SUM 2.0 is the supported maintenance scenario, particularly the SAP system architecture and target SAP_BASIS release.
SUM 1.1 Is Generally Used For
- SAP Java systems.
- SAP dual-stack systems.
- ABAP systems targeting SAP_BASIS 7.40 or lower.
- Supported upgrade procedures starting from specified older ABAP releases.
SUM 2.0 Is Generally Used For
- ABAP single-stack systems targeting SAP_BASIS 7.50 and higher.
- Supported SAP S/4HANA system conversions.
- Applicable SAP BW/4HANA conversion and upgrade procedures.
- Supported DMO and downtime-optimization scenarios.
For example, an eligible ABAP system targeting SAP_BASIS 7.50 or higher would generally use SUM 2.0. A qualifying Java or dual-stack system would use SUM 1.1.
How to Choose the Correct SAP SUM Version
Selecting the right SUM version is an important part of SAP upgrade planning. Follow these steps before starting the maintenance process.
Step 1: Identify the Current SAP Release
Check the source system's SAP_BASIS release, kernel version, database and operating system.
Step 2: Confirm the Target Release
Identify the intended target product and release, including the relevant SAP_BASIS version.
Step 3: Check the System Architecture
Determine whether the system is ABAP single-stack, Java or dual-stack.
Step 4: Review the Supported Upgrade Path
Consult the applicable SUM guide, SAP Notes and Maintenance Planner recommendations for your source-to-target combination.
Step 5: Select the Correct SUM Package
Download the appropriate SUM version and support package level for your specific maintenance procedure.
Step 6: Prepare and Validate the System
Complete the required readiness checks, backups, prerequisite updates, custom-code assessments and test upgrades before performing the production maintenance.
Following these steps helps reduce avoidable errors and improves upgrade planning.
Why Is the Correct SUM Version Important?
Using the correct SUM version is necessary because SAP maintenance tools are designed for specific supported scenarios.
Selecting an unsuitable version may result in the tool rejecting the upgrade path or the procedure failing to meet the technical prerequisites.
Correct planning helps organizations:
- Reduce upgrade-related risks.
- Identify compatibility issues earlier.
- Plan system downtime more effectively.
- Prepare for database migration where required.
- Improve coordination between SAP Basis, functional and development teams.
SUM automates parts of the technical process, but it does not eliminate the need for thorough planning, testing, backup validation and post-upgrade verification.
Conclusion
SUM 1.0, SUM 1.1 and SUM 2.0 serve different SAP software maintenance scenarios.
SUM 1.0 is relevant to certain legacy SAP systems, while SUM 1.1 succeeded SUM 1.0 SP28 and supports specified Java, dual-stack and older ABAP upgrade scenarios. SUM 2.0 is the standard choice for supported ABAP single-stack scenarios targeting SAP_BASIS 7.50 and higher, including relevant SAP S/4HANA conversion procedures.
The most important rule is to select SUM according to the supported source-to-target upgrade path, rather than simply choosing the newest version.
For the latest compatibility information, refer to SAP's official Software Update Manager documentation before beginning any upgrade or conversion.
For more details about Fortun8 Technologies and our SAP solutions, explore our services, including SAP AMS Services, SAP Implementation Services, SAP Upgrading and Patching Services, and SAP Migration Services.
Need Support With Your SAP Environment?
Explore Fortun8 Technologies for SAP server access, implementation, maintenance, upgrading, patching and migration solutions tailored to your project requirements.