HOW-TO GUIDE

How To... Configure SAP Business Technology

Platform, Cloud Foundry Environment for CTS

Version 1.3

January 2023
TABLE OF CONTENTS
1 SCENARIO ........................................................................................................................................ 1
2 BACKGROUND INFORMATION ....................................................................................................... 2
3 PREREQUISITES ............................................................................................................................... 3
4 RESTRICTIONS AND RECOMMENDATIONS .................................................................................. 4
5 BASIC CONFIGURATION FOR CTS ................................................................................................. 5
5.1 Configuring an HTTP Destination ................................................................................................... 5
5.2 Import SSL Certificate ..................................................................................................................... 8
5.3 Configuring the Transport Organizer Web UI .............................................................................. 14
6 CONFIGURE ‘SCP_CF’ AS APPLICATION TYPE .......................................................................... 16
7 CONFIGURE THE CLOUD FOUNDRY TRANSPORT LANDSCAPE.............................................. 18
7.1 Configuring the Transport Landscape in TMS ............................................................................ 18
7.1.1 Configuring the Development system (Export system) ............................................................. 18
7.1.2 Configuring the Test and Production System (Import Systems) ............................................... 20
7.1.3 Transport Landscape: Defining Transport Routes ...................................................................... 23
8 USE SAP BTP, CLOUD FOUNDRY ENVIRONMENT WITH CTS ................................................... 26
8.1 Select Objects and Attach to Transport Request ........................................................................ 26
8.2 Importing Transport Requests with Cloud Foundry Content .................................................... 29
8.2.1 Meaning of Return Codes - Reading the Deployment Log-File on CTS side ........................... 30
8.3 Advanced Usage of Cloud Foundry with CTS+ ........................................................................... 31
8.3.1 Tools for managing transports ..................................................................................................... 31
DOCUMENT HISTORY

Document Version Description

1.3 • Edited the 5.1 Configuring an HTTP Destination

1.2
• Updated guide to reflect the brand name change from SAP Cloud
Platform to SAP Business Technology Platform (SAP BTP):
o Changed Title from How To... Configure SAP Cloud Platform
Cloud Foundry for CTS to How To... Configure SAP Business
Technology Platform Cloud Foundry Environment for CTS
o SAP Cloud Platform, Cloud Foundry environment is now SAP
BTP, Cloud Foundry environment.
o Exchanged some graphics which also contained SAP SCP
• Added more detailed information on creating HTTP destinations

1.1
Minor corrections

1.0
First official release of this guide
TYPOGRAPHIC CONVENTIONS ICONS

Icon Description Icon Description

Example Text Words or characters quoted from Caution

the screen. These include field
names, screen titles, pushbuttons Important
labels, menu names, menu paths,
and menu options.
Cross-references to other Note
documentation

Example text Emphasized words or phrases in Recommendation or Tip

body text, graphic titles, and table
titles
Example
Example text File and directory names and their
paths, messages, names of
variables and parameters, source
text, and names of installation,
upgrade and database tools.

Example text User entry texts. These are words

or characters that you enter in the
system exactly as they appear in
the documentation.

<Example text> Variable user entry. Angle

brackets indicate that you replace
these words and characters with
appropriate entries to make
entries in the system.

EXAMPLE TEXT Keys on the keyboard, for

example, F2 or ENTER.
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

1 SCENARIO
The Change and Transport System (CTS) of ABAP has been enhanced so that it can be used
for transporting non-ABAP objects as well – this is known as CTS+ or enhanced CTS. In the
remainder of this document, the abbreviation CTS is used for the system where the transport
landscapes are configured and for the fact that CTS can also be used for non-ABAP transports.
In this guide, you can find information on how to use CTS for transporting applications running
on the SAP BTP, Cloud Foundry environment. This guide shows step by step – including sample
screenshots - how the configuration is done. Afterwards you will be able to transport Cloud
Foundry applications bundled in Multi-Target Application (MTA) archives to Cloud Foundry
spaces. If you already use CTS, for example, to manage non-ABAP transports for applications
like the SAP Enterprise Portal or to transport your BW ABAP objects, you might be interested in
using the same tool to transport the Cloud Foundry content as well. With the integration of Cloud
Foundry into CTS, this is now possible. You can model a landscape for your Cloud Foundry
spaces in CTS like for any other non-ABAP application supported by CTS. When doing that, you
associate logical systems in TMS to the spaces you have in Cloud Foundry.
Note that in the remainder of this document, the representations of the Cloud Foundry spaces
in CTS will be called systems (for example, logical non-ABAP system, source or export
system, as well as target or import system).
The following figure shows a sample transport route modeled in CTS+.

CTS does not limit your landscape to one source and one target system. All the options that you
might know from TMS are available for systems associated with Cloud Foundry spaces as well.
You can, for example, have several systems in a row or more than one target system at once.
To implement the scenario, you need a physical system where CTS is configured. For the setup
described in this guide, you must use a SAP NetWeaver system on release 7.4 or higher.
In order to trigger the transport, you must create a transport request for the first system in the
transport route (Dev in the example above) and attach the MTA archives that you want to
transport to it using the Transport Organizer tool in CTS. Afterwards you need to release the
transport request. You can then start the import into the next logical system from the transport
route, which will trigger the import into the corresponding Cloud Foundry space.

January 2023 1
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

2 BACKGROUND INFORMATION
• SAP Business Technology Platform documentation
• Guides for CTS
• The Multi-Target Application Model
• Documentation for CTS including CTS Plug-In
• Central note for CTS+: 1003674
• Security for the Enhanced Change and Transport System (CTS+)

January 2023 2
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

3 PREREQUISITES
To be able to use CTS with SAP BTP, Cloud Foundry environment as described in this guide,
your systems must fulfill the following prerequisites:
• CTS System: SAP NetWeaver 7.4 or higher
• If CTS System is on state lower than SAP NetWeaver 7.4 SP10: CTS plug-in installed on
the CTS system (taken from the latest available SL Toolset 1.0 CTS plug-in). SAP Note
for installing the SAP CTS Plug-In of SL Toolset: 1665940
• SAP Notes 2236955 and 1160362 must be applied to the CTS system.

January 2023 3
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

4 RESTRICTIONS AND RECOMMENDATIONS

You must use a system, such as the CTS system, which is on SAP NetWeaver 7.4 and at least
on SP10 or has CTS plug-in installed (for SPs below SP10).

January 2023 4
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

5 BASIC CONFIGURATION FOR CTS

You must do configurations on your CTS system and on the Cloud Foundry spaces to be able
to use CTS. This chapter helps you with these configurations. It provides a step-by-step
guide. (Remember: You may have to install the CTS plug-in on the CTS system.)

Sample Landscape

In the sample landscape shown in the picture above, you can see three systems associated
with Cloud Foundry spaces:
• BD3 represents the development CF space – also called export or source system
• BT3 is the test CF space – also called import or target system
• BP3 is the productive CF space – also called import or target system
This landscape is used as an example in the following chapters explaining the configuration.

5.1 Configuring an HTTP Destination

You must create an HTTP destination on the CTS system for every Cloud Foundry target
space (every system where you would like to execute imports).
For more information on configuring an HTTP destination in an ABAP system, see Establishing
a Connection Using a Destination (SM59).

January 2023 5
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

1. Go to transaction SM59.
2. Mark HTTP Connections to External Server and choose Create.

3. Enter a name in the field RFC Destination, for example, BT3_DESTINATION (you need a
destination for each target system).
CAUTION
The name that you enter in the field RFC Destination will automatically be
converted into upper case as soon as you save the destination. Later, you
must enter the name of the destination when you define the target system
in STMS. Make sure that you use the correct writing in there.
4. On the tab Technical Settings, enter the details of the target system.
a) Depending on the account in which BTP region and CF instance it relies on, enter the
specific hostname of the SAP Cloud Deployment service as Target Host and leave the
Service No. field empty: deploy-service.cf.<domain>, where <domain> is
the domain of your target subaccount.
The domain is derived from the Cloud Foundry API endpoint that you can find in the
SAP BTP Cockpit in the Overview of your subaccount.
For more information, see Deploying Applications in Regions and Regions and API
Endpoints Available for the Cloud Foundry Environment.
Example 1
Cloud Foundry API endpoint: api.cf.eu10-004.hana.ondemand.com
SAP Cloud Deployment service URL: deploy-service.cf.eu10-004.hana.ondemand.com

Example 2
Cloud Foundry API endpoint: api.cf.eu10.hana.ondemand.com
SAP Cloud Deployment service URL: deploy-service.cf.eu10.hana.ondemand.com

b) Then, enter the Path Prefix using the following:

/slprot/<target_org_name>/<target_space_name>/slp

January 2023 6
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

NOTE
You need to escape special characters in your org and space name with a proper
URL encoding. For example, replace space characters with %20, and commas
with %2C.
Example with URL encoding for organization ‘Example Company Test Org’ and space
‘Example Company Test Space’:
/slprot/Example%20Company%20Test%20Org/Example%20Company%20Test%20Space/slp

c) Finally, configure the HTTP Proxy Options according to your network configuration.

5. Go to the Logon & Security tab and configure the logon to the target system according to
your needs. Make sure to check the Active checkbox for SSL and note the Cert. List as it
is required below.
Currently CTS+ for SAP BTP Cloud Foundry environment supports only ‘Basic
Authentication’.
The Cloud Foundry user that you enter in here needs to have at least the role
SpaceDeveloper in the corresponding Cloud Foundry target space. More information on

January 2023 7
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

the roles is available in the SAP Business Technology Platform Documentation under
Working with Role Collections.
NOTE
All import processes of Cloud Foundry content for this target system triggered by CTS
use this username and password by default.
6. Repeat these steps for each target system.

5.2 Import SSL Certificate

The CTS system must validate the server certificate to ensure the server identity and to
prevent man-in-the-middle attacks. This means that the root certificate of the certificate
authority that was used to sign the Cloud Foundry server certificate needs to be imported.
This is the certification path for the hana.ondemand.com domain:

The following is a step-by-step description for exporting the root certificate using Google
Chrome and importing it using the transaction STRUST. These steps are exemplary for
Google Chrome. However, the certificate can also be exported from another browser, from
the operating system, or can be downloaded from digicert (https://www.digicert.com).

1. Start Google Chrome, and choose -> More Tools -> Developer Tools.

January 2023 8
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

2. Choose Security and then View certificate.

3. On the General tab, you see that the certificate is issued to the *.hana.ondemand.com
domain. Go to the Details tab.

January 2023 9
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

4. To download the certificate, choose Copy to File….

5. On the Certificate Export Wizard, choose Next.

January 2023 10
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

6. Select Base-64 encoded X.509 (.CER) and click Next.

7. Enter a filename and click Next.

January 2023 11
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

8. Click Finish on the next dialog. The certificate has now been exported.

9. Click OK.

10. Log on to the CTS system and open transaction STRUST. Open the edit mode by clicking
on the Display <-> Change button.

11. Select the certificate list on the left that you have specified in the previous chapter when
setting up the HTTP connection.

January 2023 12
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

12. Click the Import Certificate button on the bottom left.

13. In the dialog enter the file name of the certificate file which has been exported in step 6.

14. Click Add to Certificate List and leave the edit mode by clicking the Display <-> Change
button on the top.

January 2023 13
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

15. The connection test for the connection in transaction SM59 should be successful after
importing the certificate.

5.3 Configuring the Transport Organizer Web UI

CTS provides Transport Organizer Web UI, an ABAP Web Dynpro application, which is used
to get detailed information about transport requests (for example, default request, target
systems) and to create transport requests and attach objects manually. You must activate the
ICF service CTS_ORGANIZER to run and use this application.
To use the Object List Browser to see a detailed list of objects attached to a transport request
(as part of one file) you need to activate the ICF service CTS_OBJECTLIST_BROWSER.
For more details, refer to Activating Services for Transport Organizer Web UI.
If CTS+ is already in use on the CTS system where you are doing the configuration, the
services should already be activated. If not, activate them now.
If you receive error messages when running this application later or if you don’t want to
activate all ICF services read the error messages carefully and activate the services named in
the error messages via transaction SICF.
The following figure shows the Transport Organizer Web UI.

January 2023 14
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

To open the Transport Organizer Web UI, go to transaction STMS in CTS system and click on

January 2023 15
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

6 CONFIGURE ‘SCP_CF’ AS APPLICATION TYPE

To use CTS with Cloud Foundry, you must define an application type for Cloud Foundry in
CTS. The application type will then be used as unique identifier for Cloud Foundry content in
CTS. For the Cloud Foundry integration with CTS, the application type SCP_CF is used.
Documentation on how to do this is provided on the SAP Help Portal under Configuring
Source Systems for Further Applications.
The following steps describe how the application type is created and managed in CTS.

Log on to your CTS system (Domain

Controller) and open transaction
STMS. Go to the System Overview.

To create a new application type, go

to Extras → Application Types →
Configure.

You can see a list of application

types already created in your
system. Choose New Entries if
SCP_CF is not yet part of the list.

January 2023 16
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

On the next screen, you can enter

your application type and some
details. Use SCP_CF in here. A
description and support details are
required to give details on the
application type and on how
customers can get support in case of
issues.

Use Multi-Target Application (MTA)

on SCP_CF as Description and BC-
XS-SL-DS as Support Details. This is
where your customers can get
support in case of issues with Cloud
Foundry content transports.

Save your entry and click Yes to

distribute the new application type
through your landscape.

The new application type has been

saved. Click Back to return to the list
of application types.

The new application type SCP_CF is

now part of the list.

January 2023 17
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

7 CONFIGURE THE CLOUD FOUNDRY TRANSPORT LANDSCAPE

The configuration of the Cloud Foundry transport landscape consists of several steps, which
will be detailed in the following chapter.
As an example, we will set up a landscape of three systems as depicted in chapter Basic
Configuration for CTS, i.e., a development system (BD3) as the source system, a test system
(BT3) and a production system (BP3) as the target systems.
1. CTS identifies systems resp. transport nodes via 3-digit System IDs (SIDs). You cannot
derive a SID from the Cloud Foundry space directly. Therefore, think at first about the 3-
digit SIDs that you would like to use to identify your Cloud Foundry space.
NOTE
SIDs consist of three characters (letters and / or numbers). They have to be unique
within your transport domain, but they may be shared between different applications
(i.e. Portal and SLD if they run on same NW AS JAVA instance).
As an example, we will use BD3 (development system), BT3 (test system) and BP3
(production system) in the following.
2. As soon as you define the SIDs for your Cloud Foundry spaces, you can start creating the
representations for these systems in TMS and connect them with the help of transport
routes. Details are described in the Configure the Transport Landscape in TMS below.

7.1 Configuring the Transport Landscape in TMS

Create the individual spaces of your Cloud Foundry transport landscape as non-ABAP
systems in TMS. These systems identified with the corresponding SIDs represent the Cloud
Foundry spaces in TMS.
Documentation on how to create non-ABAP systems in TMS is provided on the SAP Help
Portal under Defining and Configuring Non-ABAP Systems. This chapter shows how setting
up the systems would work in our example.

7.1.1 Configuring the Development system (Export system)

Define a source system (‘BD3’) for your Cloud Foundry development space. You therefore must
select the option ‘Activate Transport Organizer’ when creating the system representation in TMS.

Log on to your CTS system (Domain

Controller). Open transaction STMS and
choose System Overview.

January 2023 18
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

Choose SAP System → Create → Non-

ABAP System

Enter the SID of your development

system (BD3 in our example) in the field
System, a Description and choose
Activate Transport Organizer. Select an
appropriate client and then choose
Save.

The system will be created and the

system list will show up.

All Cloud Foundry users that should be allowed to attach Cloud Foundry content to transport
requests have to have a corresponding user in the client of the CTS system that you are using

January 2023 19
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

for transports (= the client where you activated the Transport Organizer Web UI). To transport
non-ABAP objects, you can use the authorizations of the delivered role SAP_CTS_PLUS.
CAUTION
Do not use this role directly. Instead, use it as a template and copy it to your own role
(Z_*). More information on the creation and maintenance of roles in ABAP you can find
on the SAP Help Portal under Role Administration.
Also please read note 1003674 for recent updates on authorizations required for the different
releases.

7.1.2 Configuring the Test and Production System (Import Systems)

All other systems of your Cloud Foundry landscape – like e.g. test and production systems
(‘BT3’, ‘BP3’) must be defined as target systems. This chapter describes how this is done.

Choose SAP System → Create →

Non-ABAP System

When you create a non-ABAP target

Cloud Foundry system which should
use this new application type
SCP_CF, you must choose Other as
Method(s) and deselect all other
options. Click Save.

January 2023 20
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

Click Yes to distribute the

configuration.

When saving the non-ABAP SCP_CF

system, you are asked to define the
deployment method for your system.
Choose New Entries.
On the next screen, choose SCP_CF
as Application Type (F4-help).
Choose HTTP-based Deployment
(application-specific) as Deploy
method.
Enter the HTTP destination that you
configured for this system before in
chapter 5.1 Configuring an HTTP
Destination. Make sure that you use
the correct writing – this entry is
case-sensitive. Destinations are
stored in upper case.

Save your entries and choose Yes to

distribute the new application type
through your landscape.

Your entry is now saved. Click Back

to return to the list.

You can now see your details for

handling the application type
SCP_CF. Choose Back to return to
the system.

Create any other target system that you might need (e.g. for production system –‘BP3’) as
shown before.
You can also extend the configuration of existing systems to be able to use them with new
application types. To do so, do the following:

January 2023 21
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

Go to the system overview in

TMS and double-click on the
system where you would like to
extend the configuration.

In the details of your system,

choose Goto → Application
Types → Deployment Method

Choose New Entries and

proceed as described above for
the creation of new systems.

NOTE
The parameters DEPLOY_DATA_SHARE and DEPLOY_WEB_SERVICE are not required if
you configure CTS+ for HTTP-based deployment. Nevertheless, they are automatically
added to newly created non-ABAP systems in any case. In case of CTS+ using HTTP-
based deployment, these parameters are simply ignored at runtime. The same is valid for
the parameter CTS_FILE_PROVIDER_URI. There is no need to delete these parameters
– neither if they were added automatically when you created the system nor if you
decide to change the configuration of a certain non-ABAP system. The transport tool
check will only report errors for these parameters if they are used for at least one
transport configuration in the respective system.
You can check if the system can be reached: Return to system overview, select the target
system, and check the import settings using SAP System → Check → Transport Tool. To get

January 2023 22
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

the details about reported errors for non-ABAP systems, go to transaction SA38 and execute
the program RSTMS_NONABAP_SUPPORT.

7.1.3 Transport Landscape: Defining Transport Routes

Now that you have created representations for the different systems (BD3, BT3 and BP3 in
our example) in TMS, you must connect them with the help of transport routes.
Use client-independent transport routes.
More details on how to configure transport routes you can find on the SAP Help Portal under
Configuring Transport Routes.

Log on to your CTS system (Domain

Controller). Open transaction STMS
and go to Transport Routes

The systems BD3, BT3 and BP3 that

you just created are shown in the
upper row of systems. The systems
shown in here are not yet connected
by transport routes. Switch to Edit
mode.

Click on system BD3 and then click

in the area where the transport
routes are shown.

Repeat the previous step for BT3

and BP3

January 2023 23
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

Choose Add Transport Route

Your mouse pointer is now a pencil.

Draw a line from BD3 to BT3.

A dialog box opens. Make sure that

Consolidation is selected. A
consolidation route is needed to
connect a development system to
e.g., a test system (from a system
where you do an export to a system
where you would like to import the
transport request).

Enter a name for the Transport

Layer, e.g., ZBT3. The name must
start with a Z.
NOTE
Create one standard transport layer
(this is the default), not two separate
ones for SAP- and custom transports
as you might be familiar from
configuring transport routes for
ABAP systems.

Choose Transfer.

You must enter a Short Description

for the Transport Layer in a second
window if the transport layer does
not yet exist. Choose again Transfer.

A transport route has been added

connecting BD3 with BT3. Now draw
a line from BT3 to BP3.

January 2023 24
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

Choose Delivery for this transport

route and click on Transfer. When
you set up a delivery route, you are
making sure that all transport
requests that are imported into the
route’s source system are
automatically flagged for import into
the route’s target system.
Choose Transfer.

Save the configuration

Confirm that you would like to

Distribute and Activate the
configuration

The transport route for BD3, BT3

and BP3 is now part of the
configuration

January 2023 25
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

8 USE SAP BTP, CLOUD FOUNDRY ENVIRONMENT WITH CTS

8.1 Select Objects and Attach to Transport Request

This section shows how to attach an MTA archive to a transport request.

To add an MTA archive to a

transport request in CTS, you
first must start the Transport
Organizer.
To do this, log on to your CTS
system, open transaction
STMS and choose Transport
Organizer Web UI.

Select the first system in the

transport route (source
system), in our example, BD3.

The Transport Organizer Web

UI opens. You can either select
an existing transport request or
create a new one. To create a
new one, choose Create
Request.

January 2023 26
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

Enter a Description. In our

example, we entered My first
SCP_CF content transport
request. Choose Create.

Afterwards the transport

request is displayed in the
overview.

To attach an MTA archive to

the transport request, select
the Object List tab, choose
Display <-> Change, and then
Attach.

January 2023 27
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

In the following dialog, select

the MTA archive on your local
machine using the Browse
button, select SCP_CF as the
Application and then choose
Add to List. Then choose
Attach.

As a result, you see the

attached MTA archive in the
object list. Click on Save
Changes.

After you have added one or more MTA archives to a transport request, you can release the
transport request. This is also done in the Transport Organizer Web UI. Mark the transport request
that you would like to release and choose Release.

January 2023 28
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

After releasing the transport request, it cannot be changed any more. It is no longer visible in the
list of Modifiable transport requests in the Transport Organizer Web UI.
For information on Transport Organizer Web UI, see Transport Organizer Web UI
(CTS_ORGANIZER).

NOTE
If you encounter problems when attaching objects or releasing the transport request, check
whether you can find details for errors in the Application Log (transaction SLG1) for object
CTSPLUS.

8.2 Importing Transport Requests with Cloud Foundry Content

All transport requests that are released become part of the import queue of the first target system.
You can now import one, several, or all of them.

Log on to your CTS system and

open transaction STMS. Choose
Import Overview

Double-click on the SID of your

target system

Mark transport requests that you

would like to import and choose
Import request.

January 2023 29
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

Choose Continue to start the

import immediately or define an
appropriate time frame or event
when the import should be started
and choose Continue afterwards.

Confirm that you want to import

the transport request (click Yes).

After having imported a transport

request, a return code will be
shown for each transport request
to tell whether the import was
successful or not. Refer to the
next chapter to learn more about
return codes.

For more details on performing imports, see Importing Transport Requests with Non-ABAP Objects.
NOTE
As of CTS Plug-In 2.0 SP02 (SL Toolset 1.0 SP05), a new browser-based Import UI is
available. Alternatively, you can use the Import UI to perform imports. For more information,
see Performing Imports Using the Import Queue Web UI.

8.2.1 Meaning of Return Codes - Reading the Deployment Log-File on CTS side
Four different return codes can appear in the import queue

• RC = 0: The import has been successfully completed. Icon in the queue:

January 2023 30
How To... Configure SAP Business Technology Platform, Cloud Foundry Environment for CTS

• RC = 4: Warning that not everything was ok but import in principle worked. Icon in the
queue:
• RC = 8: Errors for the content occurred when importing. A subsequent transport is required.

Icon in the queue:

• RC = 12: There were issues with the tool during the import. The transport request can be
imported again after the issue has been fixed. Icon in the queue:
You can double-click on the icon for the return code for one transport request to learn more about
the import. Especially if the RC is not zero, it might be interesting to find out what went wrong.
Clicking on the return code will bring up the overview of the transport logs.

You can
click on the
icon in front
of the step
Deployment
to view the
deployment
log.

You can see

the
deployment
log. For
more details,
you can use
the expand-
buttons.

8.3 Advanced Usage of Cloud Foundry with CTS+

8.3.1 Tools for managing transports

In some cases, Cloud Foundry content should be kept in sync, resp. transported together with
content from other applications, for example ABAP backend content. There are tools in SAP
Solution Manager that can help you manage collections of change requests and keep changes that
are made in different systems together. These tools are called Change Request Management
(ChaRM) and Quality Gate Management (QGM). Details for both are provided on SAP Support
Portal at https://support.sap.com/en/solution-manager.html -> Change Control Management.

January 2023 31
www.sap.com/contactsap

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.