Deployment Management

Create and Process Feature to Deploy Changes Through the Landscape

The brand new Feature can be created in the Features application with a relation to the project and the scope. Features can be used to document your software or configuration changes and deploy the changes through your landscape. In the following figure the main properties of a Feature are illustrated.


To deploy Features through your landscape the integration into the various deployment mechanisms of SAP is crucial. The integrations mentioned below are already available:

Deployment ToolsIntegrated Solutions
Change & Transport System (CTS)SAP S/4HANA Cloud, private edition
CTSSAP S/4HANA on-premise
CTSSAP NetWeaver Application Server for ABAP on-premise

Before you can start enabling the transport management for SAP S/4HANA Cloud, private edition or SAP NetWeaver Application Server for ABAP on-premise, you need to fulfill the following prerequisites:

  • Install SAP_BASIS 7.40 SP20 or higher (accordingly 7.50 SP04).

  • Install ST-PI 7.40 SP16 or higher.

  • Check that the profile parameter icm/HTTPS/client_sni_enabled is set to TRUE. For more information, refer to SAP Note 510007 Information published on SAP site.
  • Check that DigiCert Global Root CAInformation published on SAP site is imported in STRUST under SSL Client (Anonymous) and SSL Client (Standard).

You can find the configuration guide to enable the integration in the Setup & Administration Guide:


Essence of the Feature is the transport section which provides the following option:

  • Assign modifiable or released transports to a feature once
  • Un-assign and re-assign transports
  • Refresh the transport list to get the current status
  • Deploy the transports in the release order of the subset assigned to the Feature

It is always ensured that transports are deployed to the test system before all transports assigned to a Feature can be deployed to the production system. Prior to the deployment of a Feature to production the approval for deployment needs to be given by the change & release manager.

A Feature follows an easy workflow with the following statuses:

  • Not Planned: To indicate that a Feature is postponed
  • In Specification: Technical specification of a Feature to be done
  • In Implementation: Implementing the Feature covers recording of changes (assign transports) and deploying changes to the test stage     
  • Ready for Deployment: Indicates that the changes were successfully tested and are ready for production deployment
  • Deployed: Confirming the deployment of the changes to production

The feature serves the purpose to establish the cloud mindset by making the move to the continuous feature delivery. Continuous feature delivery shifts the focus on delivering new functionality incrementally.