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.
Feature workflow updated with status In Testing
A Feature follows an easy workflow with the following statuses:
The following table shows you which activities related to the transport section are available in the respective feature statuses:
|Ready for Production||Yes||Yes||Yes||Yes|
The following table shows you which activities related to the user stories section are available in the respective feature statuses:
|Ready for Production||Yes||Yes|
The available project roles enable different actions with respect to features. The following table provides an overview of the most important actions possible:
Note: 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 (at the moment project lead or project admin).
Note: All transport tasks must be released by the developer(s) in the source system before releasing the transports.
Features can serve hybrid use cases, e.g. to deploy changes for SAP S/4HANA Cloud, private edition and SAP Integration Suite - Cloud Integration in an orchestrated way. Simply assign transports from both export sources to one feature and deploy the feature to the corresponding systems defined in the the transport track.
In our example we have a 2-tier landscape for Cloud Integration and a 3-tier landscape for SAP S/4HANA Cloud, private edition.
In this example only transport O11K904513 will be deployed to the target tenant, since the transport for Cloud Integration is ready for production due to the 2-tier landscape and deployment to production is synchronized by SAP Cloud ALM.
Handling of complex landscapes with multiple deployment targets is easy. TMS transport target groups and Cloud TMS transport routes with multiple targets are resolved to make the flow of transports through your landscape transparent.
Alle target clients were supplied with the changes and now the production clients are flagged as target tenants.
SAP Cloud ALM is aware of the transport tracks since the information is pushed to SAP Cloud ALM from the connected systems. Hence the production system (last system of the transport track) is known, and it is ensured that the deployment of a feature to production can only be executed in status "Ready for Production".
Based on the releases defined in the deployment plan several features can be bundled for a release delivery. In the feature overview this bundle of features can be deployed to production. Prerequisite is that the features are in status “Ready for Production” and the assigned transports are ready for the import into the production systems.
Nice to know: As you can see in this screenshot the release is already closed and the scope of the release cannot be changed anymore.
All ABAP based transports assigned to the selected features are imported as a subset. So, there is no need to worry about the transport sequence.