SUM in the family way
[2021-11-18] Important note:
Information on SUM versions can be found on our SAP Support Portal page for Software Update Manager now, check that page instead, as the content of this blog post is no longer updated.
You are familiar with Software Update Manager (SUM), and with it’s version 1.0. As Product Manager for SUM, I want to draw your attention to the fact that we have made SUM 2.0 available in September, as part of Software Logistics Toolset 1.0 SP stack 21. What does that mean for you?
SUM 2.0 available as of September 11th 2017
SUM 1.0 will still be around, so both SUM 1.0 and 2.0 will be offered in parallel. But each scenario is covered by only one of the SUM versions – the other SUM version will refuse to work on that scenario (“Hey buddy, you are on the wrong side of tools – ask my bro’ for this“). But as Maintenance Planner will anyhow provide to download the adequate version for your scenario, you shouldn’t experience this.
Which SUM for which scenario?
Easy decision matrix:
- SUM 2.0 is for ABAP single stacks, targeting systems based on BASIS 7.50 and higher
(exception: SUM 2.0 is used for ZDO even if target is BASIS 7.40)
- SUM 1.0 is always used if the source system is either a dual-stack system, or a Java stack
- SUM 1.0 is used for ABAP stack if target is based on BASIS 7.40 or lower
- all System Conversions (transition SAP ERP to SAP S/4HANA) will be done by SUM 2.0.
- SUM 2.0 targets BASIS 7.50 and higher, which in turn requires that
- the source system is already Unicode, and
- the source is based on BASIS 7.00 or higher
Note that the coding of SUM 2.0 is not greenfield – it is the proven coding of SUM 1.0, but with a slimming cure, as it does not handle all the scenarios that the previous SUM 1.0 was covering.
What’s in: Software Logistics Toolset 1.0 SPS 21?
Well, let’s turn to the numbers game: the SL Toolset is still 1.0, and SP stack 21 is available since September. SL Toolset 1.0 SPS 21 includes SUM 2.0 SP 0 and SUM 1.0 SP 21.
See blog https://blogs.sap.com/?p=545723 on SL Toolset 1.0 SPS 21.
Stay tuned for more news with SUM 2.0, as soon as the new kid on the block is available.
Short FAQ on SUM 2.0
[added on September 23th 2017]
Q: Is SUM 2.0 part of SUM 1.0?
A: No, the two versions are delivered separately in their own archives
Q: Where do I find SUM 2.0 for downloading?
A: The archive is available in the download area. The landing page of the Software Logistics Toolset lists the link (among links to guides), see: http://support.sap.com/sltoolset
Q: I have used SUM 1.0 SP 20 for a system conversion run towards SAP S/4HANA. Now conversion is only offered with SUM 2.0 – can’t I use SUM 1.0 any longer?
A: SUM 1.0 SP 21 can’t be used for a conversion scenario. If you have used SUM 1.0 SP 20 for a conversion until now, the recommendation is to switch to SUM 2.0 SP 00. You may continue to use SUM 1.0 SP 20 for a while, typically 3 months after the next SP is available. This phase is called “patch-on-request”: SUM 1.0 SP 20 is no longer available for download, but patches may be individually provided when required, based on an incident. Check the Maintenance Strategy of the SL Toolset which is attached to the respective SAP note, e.g. SAP Note 2475015 for SL Toolset 1.0 SPS 21.
Q: will SUM 2.0 cover the target 7.50 for java source systems in the future?
A: No, SUM 2.0 will remain as tool for pure ABAP based source systems.
Short FAQ on SUM 1.0
[added on May 13th 2018]
Q: Why is SUM 1.0 offered in two archives: SUM10SP22* and SUM10HDBSP22*?
- You need the archive with HDB in the name whenever a SAP HANA database is part of your scenario: either your system is running on SAP HANA database, or you intend to migrate your system to SAP HANA database (using DMO of SUM)
- Reason is that the HANA client is only supported for EXT kernel, so you use SUM10HDB*
- With SUM 1.0 SP 22, this separation of SUM 1.0 archives happens for more operating systems than before, but it is not a new concept
- This is only relevant for SUM 1.0 – not for SUM 2.0 which uses EXT kernel anyhow
Product Manager SUM, SAP SE