Use the latest versions of the tools, as they contain recent corrections.
SUM is now offered in two versions. Check this separate page for more information on SUM.
Software Update/Upgrade with SUM 1.0 SP 24
Upgrade & update of SAP NetWeaver-based systems (Java; Dual-stack; ABAP with target below SAP BASIS 7.50):
Software Update/Upgrade with SUM 2.0 SP 06
Upgrade & update of AS ABAP - based systems with target SAP BASIS 7.50 or higher:
Database Migration Option (DMO) with SUM 1.0 SP 24
Combined update and migration to SAP HANA database for target systems below SAP BASIS 7.50
Database Migration Option (DMO) with SUM 2.0 SP 06
Combined update and migration to SAP HANA database for target systems targeting SAP BASIS 7.50 and higher
Install, copy, transform, split, rename, and uninstall products based on SAP NetWeaver AS ABAP and AS Java.
Software Provisioning Manager is now offered in versions 1.0 and 2.0.
You may check this section in the guide for a comparison of 1.0 versus 2.0.
SAP frontend software of many SAP products (such as SAP GUI for Windows) has to be installed and distributed reliably to Microsoft Windows hosts in your landscape. See section below and separate page on SAPSetup.
Installation Option of Software Provisioning Manager 1.0 SP 27
Installation Option of Software Provisioning Manager 2.0 SP 04
System Copy Option of Software Provisioning Manager 1.0 SP 27
System Copy Option of Software Provisioning Manager 2.0 SP 04
Rename Option of Software Provisioning Manager 1.0 SP 27
Rename Option of Software Provisioning Manager 2.0 SP 04
Developing or configuring software requires testing before you let your end-users make use of it. So you would need a place (can be a system, a tenant,..) where you develop or configure, another one for testing and finally a production environment hosting a stable version. But how to make sure that exactly what you did is tested and that everything reaches the final stage? This requires some kind of logic that collects the (changed) content and makes sure that everything is transported from development to test and production environments.
SAP offers different tools that support these tasks. The Change and Transport System (CTS) is used in a classic ABAP environment. CTS+ makes use of many mechanisms known from ABAP for non-ABAP applications. For SAP HANA and the SAP Cloud Platform, additional tools are provided
The Change and Transport System (CTS) is a tool that helps you to organize development projects in ABAP Workbench and customizing, and then transport the changes between the SAP systems in your system landscape. As well as ABAP objects, you can also transport non-ABAP objects and non-SAP applications in your system landscape.
More information is available on the CTS page
The enhanced Change and Transport System enables you to transport non-ABAP objects, such as Java objects and objects of SAP-related non-ABAP applications, in your system landscape, alongside ABAP objects. You can also administer non-ABAP systems in a CTS transport domain in SAP NetWeaver Application Server for ABAP.
The aim is to have one transport tool that supports all development workbenches and applications. The tools for creating applications and content remain the same. The different workbenches of the applications offer options to attach your objects to a CTS transport request. The level of integration depends on the particular workbench and application.
In this way the enhanced Change and Transport System provides a unified transport tool and makes the work of administrators easier when executing imports. You only need access to one tool to execute imports for different backend systems. The deployment tools are called automatically. CTS allows you to monitor imports and analyze errors. The import queues and history in CTS give an overview of imports that have already been executed or which are planned.
More information and links to detailed documentation for CTS+ and the applications that support it is available on the page Enhanced Change and Transport System
SAP HANA application lifecycle management (HALM) supports you in all phases of an SAP HANA application lifecycle, from modeling your product structure, through application development, transport, assemble, and install.
With SAP HANA Transport for ABAP (HTA), you can synchronize objects and packages from the SAP HANA repository to the SAP HANA Transport for ABAP repository (HTA repository) in the ABAP system and add them to a transport request.
More information is available on the page SAP HANA / HALM in the area of CTS.
Framework/Runtime Engine for automating configuration and verification of SAP systems.
Maintenance for Standalone Task Manager for Lifecycle Management Automation is going to end on December 31st, 2019.
From now on, no improvements will be delivered. For more information, see SAP Note 2595196 and follow the instructions of the respective SAP products for technical configuration.