How to Export Using SAP Cloud Transport Management

Context

A developer creates and modifies ABAP coding in the SAP BTP ABAP environment by using the Eclipse-based IDE (ABAP development tools for Eclipse) with a rich debugger, troubleshooting, and testing tool support.
The changes are recorded in an ABAP transport request that is finally released. During the release, the changes are committed and pushed to the configured development branch of the corresponding Git repository (there is a one-to-one relation between an ABAP software component and a Git repository).
After testing and after the release decision, a release branch is created from the main branch.
The resulting combination of the corresponding software component and either the commit ID, Git tag, or the branch name is used as a reference by the following export call to the cloud transport management service (cTMS). It is recommended using the commit ID, because the latest commit of a branch may change, resulting in unreproducible deployments.
In cTMS a transport request is created containing the reference and added to the import queue of the following cTMS node (given by the configured service transport route).
Finally, a transport administrator uses the cloud transport management service UI to generate the import to the SAP BTP, ABAP system configured on the cTMS transport route. In doing so, the service calls an import API of the target SAP BTP ABAP environment system by passing the reference.
The import is done asynchronously, and the progress status is monitored by the service. When the import is finished, the service receives the transport logs from the target SAP BTP ABAP environment instance.

Procedure

Before we can start releasing transport requests that generate commits, a new communication arrangement is needed in order to use an endpoint.

Create a service instance and a service key of SAP Cloud Transport Management service. For more information, see Creating a Service Instance and a Service Key.
Navigate to the Communication Arrangements Fiori app.
Click on New and search for SAP_COM_0599 communication scenario in the list. Type in the name. Click on Create.
On the following screen, a new communication system should be created. Click on New. Type in your System ID, which is the URI from your service key. Click on Create.
On the communication system creation page find general properties and define the Host Name parameter according to the URI property in the service key created for SAP Cloud Transport Management service. For example https://transport-service-app-backend.ts.cfapps.eu10.hana.ondemand.com
Then find OAuth 2.0 Settings and put in a Token Endpoint, which is the URL from your service key. For example tmststest.authentication.sap.hana.ondemand.com/oauth/token?grant_type=client_credentials

.
Now it's time to create a user for outbound communication. Click on + and select oAuth 2.0 from the authentication method dropdown.
Type in your OAuth 2.0 client ID and client secret that can be taken from the service key for the basic authentication. Click on Create.
Define a cTMS node name that you will need for the export. The selected transport node must allow uploads and you should use the same name when creating the communication arrangement and creating the same in cTMS.

For more information, see Create Transport Nodes. Click Save afterwards to complete the process.

Export to SAP Cloud Transport Management using the Manage Software Components app

Open the Manage Software Components app and navigate to the desired software component and a branch.
Select a commit for the export and click on the Export Commit button.
A new dialog will open, where you will be prompted to select a cTMS node you want to use for this export.
Click on Export after you are ready with the selection. A status modal in the center of the screen will let you know if the process was completed successfully.
In case of an error, you will get an HTTP error code with a description.