
The figure illustrates the typical workflow to develop and configure a feature.
The preceding table illustrates which transport activities are enabled in which feature status:
Available Transport Activities in Which Feature Status
Feature Status | Create | Assign | Create ToC | Release | Unassign | Deploy |
---|---|---|---|---|---|---|
Not Planned | no | no | no | no | yes | no |
In Specification | yes | yes | no | no | yes | no |
In Implementation | yes | yes | yes | yes | yes | yes |
In Testing | yes | yes | yes | yes | yes | yes |
Successfully Tested | no | no | no | yes | no | yes |
Ready for Production | no | no | no | yes | no | yes |
Deployed | no | no | no | no | no | no |

The screenshots illustrate a feature with two transports for different target tenants and an example of the history of a feature:
- A Feature is the entity for change documentation and deployment orchestration.
- With SAP Cloud ALM, it is easy to assign transports and trigger their deployment throughout your landscape.
- The creation of Transport of Copies (ToC) for early testing without releasing the original transport is possible, if supported by the managed system.
- Traceability is ensured via the history of a feature.
ToC is not supported in Public Cloud Systems; the Cloud TMS Adapter cannot do this.