The Software Update Manager (SUM) can be used for several scenarios or use cases; Software Maintenance, Database Migration, System Migration, Customer Transport Integration and Correction of Installed Software Information (CISI).
SUM 1 versus SUM 2.0: each scenario is covered by only one of the SUM versions, depending on the target release:
SUM 1 versions, depending on the source release:
The Software Update Manager is the tool for system maintenance:
For more information, read this blog on SUM in the SAP Community which provides an introduction and lists several links to detailed blogs as well.
A database migration transfers the SAP system from one database type to another. The Software Update Manager offers the Database Migration Option (DMO), which is the combination of the SAP software update with the database migration.
DMO was initially a procedure to migrate to an SAP HANA database only. At this time, only the combination of upgrade and migration was possible, since typically the source system was not yet on a software level that is supported by SAP HANA database. Now, DMO allows for migration to other database types than SAP HANA database (see respective SAP note for details and restrictions) and DMO can be used for a pure migration, without changing the SAP software level: DMO without System Change. In addition, it is possible to change not only the database (host), but also the Application Server: DMO with System Move.
The technical unicode conversion can be part of the DMO procedure if the target software level is lower than SAP BASIS 7.50.
System Conversion is the transition of an SAP ERP system into an SAP S/4HANA system. The Software Update Manager executes the technical conversion of that procedure.
The relevant SAP S/4HANA releases are all based on SAP BASIS 7.50 or higher, so SUM 2.0 will be the SUM version to use for a system conversion.
For the conversion process, see the dedicated SUM 2.0 conversion guide.
Customer Transport Integration (CTI) allows customers to apply customer releases and customer transports either along with the SAP software shipment or standalone. Applying customer transports using SUM significantly reduces the overall business runtime.
Based on a white list approach, objects will be imported during uptime. Examples for enabled transport objects are dictionary objects such as DOMA, DOMD, DTEL, XINX, INDX, and repository objects such as METH, CLAS, REPS, PROG, VARI. SGEN for customer objects is also started in the shadow system.
Customer Transport Integration is described in the standard SUM guide in the Integration of Customer Transports and Integrating Customer Transports into the Update Procedure chapters. For additional information, see SAP Note 1759080 - Conditions for SUM including customer transport requests.
Correction of Installed Software Information (CISI) allows customers to correct and update information about the installed software instances in SAP systems using the Software Update Manager. A specific stack configuration file has to be generated using the Maintenance Planner.
Start SUM and provide this specific stack configuration file then SUM will then apply the required adaptations in the system.
Software Update Manager supports several scenarios - for some, downtime-optimized approaches are offered. Check the following overview on approaches and scenarios. The listed SAP Notes are the main entry point for more information, restrictions, and prerequisites.
|Near-Zero Downtime Maintenance (ABAP)||nZDM (ABAP)||Update/Upgrade & System Conversion||Unrestricted available||1678565|
|Zero Downtime Option for SAP S/4HANA||ZDO||Update/Upgrade||Available for educated experts (ADM330e)||2707731|
|Downtime-optimized DMO||Uptime Migration||Database Migration|
& System Conversion
|Downtime-optimized Conversion||System Conversion to|
|Available for educated experts (ADM329)||3211805|
|Near-Zero Downtime Maintenance (Java)||nZDM Java||Update/Upgrade||Unrestricted available||2847197|
|Near-Zero Downtime Technology||NZDT||several||service based||693168|