Administration Guide | PUBLIC

2024-01-30

Setup and Administration for SAP Cloud ALM

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

THE BEST RUN

Content

1 About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Fair Use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

4 Supported Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

5 Video-Guided Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6 Requesting SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

7 Required Setup for SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

7.1 Step 1: Onboard Users in the Identity Authentication Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.2 Step 2: Assign Roles to Users in SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Role Collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
7.3 Step 3: Set Up Landscape Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

8 Integration and Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

8.1 Enabling SAP Cloud ALM API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Enabling SAP Cloud ALM API in Cloud Foundry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Managing Your Service Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8.2 Activating the SAP Audit Log Viewer Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
8.3 Enabling Email Channel for In-App Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
8.4 Integrating SAP Central Business Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
8.5 Configuring Project User Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
8.6 Integrating the Cloud Integration Automation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
8.7 Enabling Transport Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
SAP S/4HANA Cloud with Adaptation Transport Organizer (ATO). . . . . . . . . . . . . . . . . . . . . . . . 66
SAP S/4HANA Cloud, Private Edition and On-Premise Systems. . . . . . . . . . . . . . . . . . . . . . . . . 71
SAP Cloud Transport Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Tips and Troubleshooting for Your Setups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
8.8 Integrating Test Automation Providers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Integrating the Test Automation Tool for SAP S/4HANA Cloud. . . . . . . . . . . . . . . . . . . . . . . . . . 90
Setting Up Tricentis Test Automation for SAP Integrated with SAP Cloud ALM. . . . . . . . . . . . . . . 92
8.9 Enabling Service Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

9 Application Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Setup and Administration for SAP Cloud ALM

2 PUBLIC Content
10 Launching Your Systems from SAP for Me. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

11 Account Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

12 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

12.1 User Data from SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
12.2 User Data from Managed Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
12.3 Email Notifications in SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
12.4 Change Log and Audit Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

13 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
13.1 Development and Product Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
13.2 Security Configuration Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107
Explanations of Table Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

14 Troubleshooting and FAQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114

Setup and Administration for SAP Cloud ALM

Content PUBLIC 3
1 About This Guide

SAP Cloud ALM is a cloud-based application lifecycle management offering that allows you to implement and
operate your cloud solutions.

This guide describes the steps you need to perform to set up, configure, and administer SAP Cloud ALM, and
provides important information about data protection and privacy and security topics. The guide addresses
system administrators and key users as a target audience.

 Tip

To leave feedback and contribute to this guide, choose  Feedback and select from one of the following
options:

• Comment: Leave a comment about a documentation page directly on SAP Help Portal. Before you can
comment, you need to log on with your S-user or P-user.
• Create issue (English version only): Provide feedback about a documentation page via issue on GitHub.
To create an issue, you need to log on to your GitHub account.
• Edit document (English version only): Contribute to a documentation page via pull request on GitHub.
To create a pull request, you need to log on to your GitHub account.

This allows you to get in contact with the technical authors responsible for the SAP Help Portal page to
discuss documentation-related issues.

For more information about feedback channels on GitHub, refer to the blog post Introducing the Open
Documentation Initiative .

SAP makes no warranty, either expressed or implied, for the information provided here. Due to short-term
software updates, completeness cannot be guaranteed and the information is subject to change. For the same
reasons, translations of this guide into languages other than English may not reflect the latest changes.

Setup and Administration for SAP Cloud ALM

4 PUBLIC About This Guide
2 Availability

Usage Rights

To find out if you're entitled to use SAP Cloud ALM, refer to Usage Rights – SAP Cloud ALM on SAP Support
Portal.

Technical Prerequisites

The solution is designed for desktop use, and we currently don't support mobile devices.

SAP Cloud ALM supports the browsers listed in the Feature Scope Description for SAP BTP.

 Tip

We recommend that you use Google Chrome.

Languages

SAP Cloud ALM is available in the following languages:

• English
• German
• French
• Spanish
• Portuguese
• Japanese
• Chinese
• Russian

The default display language of the solution is based on the language that is maintained in your browser
settings.

You can change the language either in your browser settings or in the SAP Cloud ALM launchpad by clicking on
your user profile in the top-right corner and choosing Settings Language & Region .

EU and NS2 Access

EU access, which restricts the processing of personal data to EEA/Switzerland, isn’t available.

Setup and Administration for SAP Cloud ALM

Availability PUBLIC 5
NS2 access, which restricts the processing of personal data to the USA, isn’t available.

For more information, refer to SAP Business Technology Platform – Regions.

Setup and Administration for SAP Cloud ALM

6 PUBLIC Availability
3 Fair Use

SAP Cloud ALM is included in cloud subscriptions with SAP Enterprise Support as described in the SAP usage
rights .

Sufficient resources for standard use are included, per default:

• SAP HANA memory: 8 GB

• API usage: 8 GB outbound data transfer per month
• Cloud operations at SAP
• Administration and monitoring

You can subscribe to additional services, to cover extended use scenarios.

Extension of Fair Use

Additional memory usage, beyond the standard, requires the subscription of the microservice SAP Cloud ALM,
memory extension.

This service is available in blocks of 4 GB, with a fixed price per month.

The following requirements can cause an extended SAP Cloud ALM usage, above the average usage:

• Extensive storing of data from monitoring activities on the SAP HANA database
• Storing large amounts of monitoring data for a large system landscape for a longer time period
(performance, business process monitoring, or integration monitoring)
• Building own UIs or dashboards
• Programming own enhancements
• Using additional monitoring platforms outside the SAP landscape and uploading monitoring data daily,
from a third-party system.

Be aware that any document uploads aren't stored in the SAP HANA memory. They require that you connect
an SAP or external DMS service and therefore do not affect the 8 GB limitation.

You can do the monitoring of the SAP HANA memory consumption in SAP Cloud ALM in the Health Monitoring
app by selecting your SAP Cloud ALM service and checking the SAP Cloud ALM HANA Memory metric.

You can configure the data and storage duration in SAP Cloud ALM for operations features. Find the guidelines
under Housekeeping on SAP Support Portal.

 Tip

The SAP Cloud ALM, memory extension service is available via a service subscription on CPEA: see SAP
Discovery Center .

There's no need to subscribe to the service before the limit reached. SAP also actively approaches you if
your memory usage is beyond the baseline memory (see also the usage rights ).

Setup and Administration for SAP Cloud ALM

Fair Use PUBLIC 7
• The activation of the memory extension service is required after SAP has reviewed the status together with
customer and suggested how a decrease of memory could be achieved.
• You're informed when the overusage has been recognized and requested to start a CPEA agreement during
the next month and activate the service SAP Cloud ALM, memory extension.
• If you continue to extend the 8 GB memory over the next months, without an extension, SAP reserves the
right to take legal action.

Charging of costs:

• When the service is activated, you're automatically charged for every month where you extend the memory
at least once.
• In months without a memory consumption beyond 8 GB, there's no charging.
• Metering starts at first day of the month and rests on the latest day of the month.
• The service is available in packages of 4 GB memory. If, for example, you need an extra of 6 GB in a month,
you're charged for two packages.

More

• What Is the Consumption-Based Commercial Model?

• FAQ: Consumption-based commercial model CPEA & Cloud Credits

SAP Cloud ALM, API Outbound Volume

You can't extend the given limitation of 8 GB API outbound volume, until further notice. Check this document
for updates.

SAP actively approaches you if your API outbound volume is beyond the baseline memory (see also the SAP
usage rights ).

Setup and Administration for SAP Cloud ALM

8 PUBLIC Fair Use
4 Supported Solutions

The following table shows in which way your SAP product is supported by SAP Cloud ALM.

You can find the latest additions to the scope in What's New for SAP Cloud ALM. For a complete list of SAP
Cloud ALM features, refer to SAP Cloud ALM Feature Scope Description.

SAP makes no warranty, either expressed or implied, for the information provided here. Due to short-term
software updates, completeness can't be guaranteed. The features in the list are subject to change.

SAP Cloud ALM SAP Cloud ALM

SAP Solution Area Capability Notes

SAP S/4HANA Cloud, public edition Implementation Process Manage-

• SAP Best Practices for SAP S/
ment
4HANA Cloud, public edition
• Two-Tier ERP
• SAP Best Practices for analytics
with SAP S/4HANA Cloud

More under Business Process Content

in SAP Cloud ALM (Expert Portal).

SAP Ariba Implementation Process Manage- • SAP Ariba Buy & Receive
ment
• SAP Ariba Contract
• SAP Ariba Invoice
• SAP Ariba Sourcing
• SAP Ariba Spend Analysis
• SAP Ariba Supplier Management
• SAP Ariba Supply Chain Collabora-
tion

More under Business Process Content

in SAP Cloud ALM (Expert Portal).

Setup and Administration for SAP Cloud ALM

Supported Solutions PUBLIC 9
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP SuccessFactors Implementation Process Manage- • SAP SFSF Compensation

ment
• SAP SFSF Employee Experience
• SAP SFSF HR Administration
• SAP SFSF Learning
• SAP SFSF Manage Benefits
• SAP SFSF Onboarding
• SAP SFSF Organizational Manage-
ment
• SAP SFSF Payroll
• SAP SFSF Performance and Goals
• SAP SFSF Recruiting
• SAP SFSF Succession and Devel-
opment
• SAP SFSF Time and Attendance
Management
• SAP SFSF Benefits
• SAP SFSF Employee Central
• SAP SFSF Opportunity Market-
place
• SAP SFSF Service Center
• SAP SFSF Time Tracking
• SAP SFSF Workforce Planning
• SAP SFSF Internal Talent Mobility
• SAP SFSF Dynamic Teams

More under SAP SuccessFactors Proc-

ess Library (S-user required) and
Business Process Content in SAP Cloud
ALM (Expert Portal).

SAP Marketing Cloud Implementation Process Manage- SAP Best Practices for SAP Marketing
ment Cloud

SAP Sales Cloud Implementation Process Manage- SAP Cloud for Customer
ment

SAP Service Cloud Implementation Process Manage- SAP Cloud for Customer
ment

SAP Fieldglass Implementation Process Manage- SAP Fieldglass Vendor Management

ment System

SAP Intelligent Robotic Process Auto- Implementation Process Manage- SAP Best Practices for SAP Intelligent
mation (iRPA) ment Robotic Process Automation integra-
tion

SAP Integrated Business Planning for Implementation Process Manage- SAP Best Practices for SAP Integrated
Supply Chain (SAP IBP) ment Business Planning for Supply Chain

Setup and Administration for SAP Cloud ALM

10 PUBLIC Supported Solutions
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP S/4HANA (on-premise) Implementation Process Manage-

• SAP Best Practices for SAP S/
ment
4HANA
• Rapid Data Migration to SAP S/
4HANA

Intelligent Enterprise – Implementation Implementation Process Manage-

• Acquire to Decommission
ment
• Idea to Market
• Lead to Cash
• Plan to Fulfill
• Recruit to Retire
• Source to Pay

SAP S/4HANA Cloud, private edition Implementation Task Management Task template: SAP Activate Methodol-
ogy for SAP S/4HANA Cloud, private
edition – Implementation and Sys-
tem Conversion

SAP S/4HANA Cloud, public edition Implementation Task Management Task templates:

• SAP Activate for SAP S/4HANA

Cloud, public edition (3-system
landscape) – Implementation
• SAP Activate for Upgrade of SAP
S/4HANA Cloud, public edition,
three-system landscape – Up-
grade
• Baseline Activation Service for SAP
S/4HANA Cloud (3-system land-
scape)
• SAP Activate for SAP S/4HANA
Cloud, public edition (2-system
landscape) – Implementation

Setup and Administration for SAP Cloud ALM

Supported Solutions PUBLIC 11
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP S/4HANA (on-premise) Implementation Task Management Task templates:

• SAP Activate Methodology for

Transition to SAP S/4HANA
• SAP Activate Methodology for
SAP S/4HANA Cloud, private ed-
ition – New Implementation,
System Conversion, and Selective
Data Transition
• SAP Activate Methodology for SAP
S/4HANA Upgrades – Techni-
cal Upgrade and Upgrade and
Product Integration

SAP SuccessFactors Implementation Task Management Task template: SAP Activate Methodol-
ogy for SAP SuccessFactors – Im-
plementation

SAP Sales Cloud Implementation Task Management Task template: SAP Activate Methodol-
ogy for SAP Sales Cloud Roadmap

SAP Service Cloud Implementation Task Management Task template: SAP Activate Methodol-
ogy for SAP Service Cloud Roadmap

Intelligent Enterprise – Implementation Implementation Task Management Task template: SAP Activate Methodol-
ogy for the Intelligent Enterprise –
Implementation

SAP Ariba Implementation Task Management Task template: SAP Activate Method-
ology for SAP Ariba and SAP Field-
glass – Implementation

SAP Fieldglass Implementation Task Management Task template: SAP Activate Method-
ology for SAP Ariba and SAP Field-
glass – Implementation

SAP Concur Implementation Task Management Task template: SAP Activate Methodol-
ogy for SAP Concur

SAP Integrated Business Planning for Implementation Task Management Task template: SAP Activate for SAP In-
Supply Chain (SAP IBP)
tegrated Business Planning for Supply
Chain – Implementation

SAP Analytics Cloud Implementation Task Management Task template: SAP Activate Methodol-
ogy for SAP Analytics Cloud

Setup and Administration for SAP Cloud ALM

12 PUBLIC Supported Solutions
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP Datasphere Implementation Task Management Task template: SAP Activate Methodol-
ogy for SAP Datasphere

SAP BW/4HANA Implementation Task Management Task template: SAP Activate Meth-
odology for Transition to SAP BW/
4HANA

SAP S/4HANA Cloud, public edition Implementation Requirement Man-

agement

SAP Marketing Cloud Implementation Requirement Man-

agement

SAP Integrated Business Planning for Implementation Requirement Man-

Supply Chain (SAP IBP) agement

SAP Intelligent Robotic Process Auto- Implementation Requirement Man-

mation (iRPA) agement

SAP S/4HANA (on-premise) Implementation Requirement Man-

agement

SAP SuccessFactors Implementation Requirement Man-

agement

SAP Sales Cloud Implementation Requirement Man-

agement

SAP Service Cloud Implementation Requirement Man-

agement

Intelligent Enterprise – Implementation Implementation Requirement Man-

agement

SAP S/4HANA Cloud, private edition Implementation Requirement Man-

agement

SAP Ariba Implementation Requirement Man-

agement

SAP Fieldglass Implementation Requirement Man-

agement

SAP S/4HANA Cloud, public edition Implementation Document Man-

agement

SAP S/4HANA Cloud, private edition Implementation Document Man-

agement

SAP S/4HANA (on-premise) Implementation Document Man-

agement

SAP SuccessFactors Implementation Document Man-

agement

SAP Sales Cloud Implementation Document Man-

agement

Setup and Administration for SAP Cloud ALM

Supported Solutions PUBLIC 13
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP Service Cloud Implementation Document Man-

agement

Intelligent Enterprise – Implementation Implementation Document Man-

agement

SAP Marketing Cloud Implementation Document Man-

agement

SAP Integrated Business Planning for Implementation Document Man-

Supply Chain (SAP IBP) agement

SAP Intelligent Robotic Process Auto- Implementation Document Man-

mation (iRPA) agement

SAP Ariba Implementation Document Man-

agement

SAP Fieldglass Implementation Document Man-

agement

SAP S/4HANA Cloud, public edition Implementation Change & Deploy- More under SAP S/4HANA Cloud with
ment Management Adaptation Transport Organizer (ATO)
[page 66].

SAP S/4HANA Cloud, private edition Implementation Change & Deploy- More under SAP S/4HANA Cloud, Pri-
ment Management vate Edition and On-Premise Systems
[page 71].

SAP S/4HANA (on-premise) Implementation Change & Deploy- More under SAP S/4HANA Cloud, Pri-
ment Management vate Edition and On-Premise Systems
[page 71].

SAP Integration Suite – Cloud Integra- Implementation Change & Deploy- More under Supported Content Types.
tion ment Management

SAP Integration Suite – API Manage- Implementation Change & Deploy- More under Supported Content Types.
ment ment Management

SAP BTP, Cloud Foundry environment Implementation Change & Deploy- Mainly development content and some
ment Management
selected services

More under Supported Content Types.

SAP BTP, Neo environment Implementation Change & Deploy- Mainly development content and some
ment Management
selected services

More under Supported Content Types.

SAP Build Work Zone Implementation Change & Deploy- Application content
ment Management
More under Supported Content Types.

SAP Build Process Automation Implementation Change & Deploy- MTA

ment Management
More under Supported Content Types.

Setup and Administration for SAP Cloud ALM

14 PUBLIC Supported Solutions
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP S/4HANA Cloud, public edition Implementation Test Management More under Integrating the Test Auto-
mation Tool for SAP S/4HANA Cloud
[page 90].

SAP SuccessFactors Implementation Test Management

SAP S/4HANA Cloud, private edition Implementation Test Management

SAP S/4HANA (on-premise) Implementation Test Management

SAP Sales Cloud Implementation Test Management SAP Cloud for Customer

SAP Service Cloud Implementation Test Management SAP Cloud for Customer

Intelligent Enterprise – Implementation Implementation Test Management

SAP Ariba Implementation Test Management

SAP Fieldglass Implementation Test Management

SAP Integrated Business Planning for Implementation Test Management

Supply Chain (SAP IBP)

SAP Intelligent Robotic Process Auto- Implementation Test Management

mation (iRPA)

SAP Marketing Cloud Implementation Test Management

SAP S/4HANA Cloud, public edition Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP S/4HANA Cloud for projects, re- Operations Integration and Ex- More under Integration and Exception
source management ception Monitoring Monitoring (Expert Portal).

SAP S/4HANA (on-premise) Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Logistic Business Network Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Information Collaboration Hub for Operations Integration and Ex- More under Integration and Exception
Life Sciences ception Monitoring Monitoring (Expert Portal).

SAP Business Suite Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Cloud for Customer Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Marketing Cloud Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Concur Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Order Management foundation Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Fieldglass Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

Setup and Administration for SAP Cloud ALM

Supported Solutions PUBLIC 15
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP SuccessFactors Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Analytics Cloud Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP BTP, Cloud Foundry environment Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Intelligent Asset Management Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Integration Suite – Cloud Integra- Operations Integration and Ex- More under Integration and Exception
tion ception Monitoring Monitoring (Expert Portal).

SAP BTP, Neo environment Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP BTP, ABAP environment Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Mobile Services Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP S/4HANA Cloud, private edition Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Field Service Management Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Ariba Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring: SAP Ariba (Expert Por-
tal).

SAP NetWeaver Application Server for Operations Integration and Ex- More under Integration and Exception
ABAP (7.40 and higher) ception Monitoring Monitoring: SAP Ariba (Expert Por-
tal).

SAP Master Data Integration Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Master Data Governance, cloud Operations Integration and Ex- More under Integration and Exception
edition ception Monitoring Monitoring (Expert Portal).

SAP SuccessFactors Employee Central Operations Integration and Ex- More under Integration and Exception
Payroll ception Monitoring Monitoring (Expert Portal).

SAP Integrated Business Planning for Operations Integration and Ex- More under Integration and Exception
Supply Chain (SAP IBP) ception Monitoring Monitoring (Expert Portal).

SAP Batch Release Hub for Life Scien- Operations Integration and Ex- More under Integration and Exception
ces ception Monitoring Monitoring (Expert Portal).

Integration Hub for Life Sciences Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Business ByDesign Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

Setup and Administration for SAP Cloud ALM

16 PUBLIC Supported Solutions
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP Omnichannel Promotion Pricing Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Process Integration (Java) Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

Data ingestion for industry cloud solu- Operations Integration and Ex- More under Integration and Exception
tions ception Monitoring Monitoring (Expert Portal).

SAP Subscription Billing Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Data Intelligence Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Entitlement Management Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Digital Vehicle Hub Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Event Broker for SAP cloud appli- Operations Integration and Ex- More under Integration and Exception
cations ception Monitoring Monitoring (Expert Portal).

SAP Predictive Replenishment Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP Cell and Gene Therapy Orchestra- Operations Integration and Ex- More under Integration and Exception
tion ception Monitoring Monitoring (Expert Portal).

SAP Intelligent Product Recommenda- Operations Integration and Ex- More under Integration and Exception
tion ception Monitoring Monitoring (Expert Portal).

SAP BTP, Kyma runtime Operations Integration and Ex- More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).

SAP S/4HANA Cloud, public edition Operations Business Process Supported KPIs for the business sce-
Monitoring
narios:

Lead-to-Cash, Source-to-Pay, Design-

to-Operate

More under Business Process Monitor-

ing KPIs (Expert Portal).

SAP S/4HANA (on-premise) Operations Business Process Supported KPIs for the business sce-
Monitoring
narios:

Lead-to-Cash, Source-to-Pay, Design-

to-Operate

More under Business Process Monitor-

ing KPIs (Expert Portal).

Setup and Administration for SAP Cloud ALM

Supported Solutions PUBLIC 17
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP Business Suite Operations Business Process Supported KPIs for the business sce-
Monitoring
narios:

Lead-to-Cash, Source-to-Pay, Design-

to-Operate

More under Business Process Monitor-

ing KPIs (Expert Portal).

SAP SuccessFactors Operations Business Process Supported KPIs for the business sce-
Monitoring
nario:

Recruit-to-Retire

More under Business Process Monitor-

ing KPIs (Expert Portal).

SAP S/4HANA Cloud, private edition Operations Business Process Supported KPIs for the business sce-
Monitoring
narios:

Lead-to-Cash, Source-to-Pay, Design-

to-Operate

More under Business Process Monitor-

ing KPIs (Expert Portal).

SAP Cloud for Customer Operations Business Process Supported KPIs for the business sce-
Monitoring
narios:

Lead-to-Cash

More under Business Process Monitor-

ing KPIs (Expert Portal).

SAP Entitlement Management Operations Business Process Supported KPIs for the business sce-
Monitoring
narios:

Lead-to-Cash

More under Business Process Monitor-

ing KPIs (Expert Portal).

SAP S/4HANA Cloud, private edition Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP S/4HANA (on-premise) Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP Business Suite Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP SuccessFactors Employee Central Operations Health Monitoring More under Health Monitoring (Ex-
Payroll pert Portal).

Setup and Administration for SAP Cloud ALM

18 PUBLIC Supported Solutions
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP Cloud ALM Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP Intelligent Robotic Process Auto- Operations Health Monitoring More under Health Monitoring (Ex-
mation (iRPA) pert Portal).

SAP Integration Suite – API Manage- Operations Health Monitoring More under Health Monitoring (Ex-
ment pert Portal).

SAP Integration Suite – Cloud Integra- Operations Health Monitoring More under Health Monitoring (Ex-
tion pert Portal).

SAP BTP, ABAP environment Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP BTP, Neo environment Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP BTP, Cloud Foundry environment Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP NetWeaver Application Server for Operations Health Monitoring More under Health Monitoring (Ex-
ABAP (7.40 and higher) pert Portal).

SAP HANA Cloud Operations Health Monitoring More under Setup for SAP HANA
Cloud (Expert Portal).

SAP Build Process Automation Operations Health Monitoring More under Setup for SAP HANA
Cloud (Expert Portal).

SAP S/4HANA Cloud, public edition Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP Integrated Business Planning for Operations Health Monitoring More under Health Monitoring (Ex-
Supply Chain (SAP IBP) pert Portal).

SAP Marketing Cloud Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP Cloud Connector Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP BTP, Kyma runtime Operations Health Monitoring More under Health Monitoring (Ex-
pert Portal).

SAP Business Suite Operations Job and Automa- More under Job and Automation Moni-
tion Monitoring toring (Expert Portal).

SAP S/4HANA Cloud, public edition Operations Job and Automa- More under Job and Automation Moni-
tion Monitoring toring (Expert Portal).

SAP S/4HANA Cloud, private edition Operations Job and Automa- More under Job and Automation Moni-
tion Monitoring toring (Expert Portal).

SAP S/4HANA (on-premise) Operations Job and Automa- More under Job and Automation Moni-
tion Monitoring toring (Expert Portal).

Setup and Administration for SAP Cloud ALM

Supported Solutions PUBLIC 19
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP SuccessFactors Employee Central Operations Job and Automa- More under Job and Automation Moni-
Payroll tion Monitoring toring (Expert Portal).

SAP Marketing Cloud Operations Job and Automa- More under Job and Automation Moni-
tion Monitoring toring (Expert Portal).

SAP Intelligent Robotic Process Auto- Operations Job and Automa- More under Job and Automation Moni-
mation (iRPA) tion Monitoring toring (Expert Portal).

SAP Integrated Business Planning for Operations Job and Automa- More under Job and Automation Moni-
Supply Chain (SAP IBP) tion Monitoring toring (Expert Portal).

SAP NetWeaver Application Server for Operations Job and Automa- More under Job and Automation Moni-
ABAP (7.40 and higher) tion Monitoring toring (Expert Portal).

SAP BTP, ABAP environment Operations Job and Automa- More under Job and Automation Moni-
tion Monitoring toring (Expert Portal).

SAP BTP, Cloud Foundry environment Operations Job and Automa- More under Job and Automation Moni-
tion Monitoring toring (Expert Portal).

SAP Build Process Automation Operations Job and Automa- More under Job and Automation Moni-
tion Monitoring toring (Expert Portal).

SAP BTP, Kyma runtime Operations Job and Automa- More under Job and Automation Moni-
tion Monitoring toring (Expert Portal).

SAP BTP, Neo environment Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP Business Suite Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP S/4HANA Cloud, private edition Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP S/4HANA Cloud, public edition Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP S/4HANA (on-premise) Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP Marketing Cloud Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP Cloud for Customer Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP BTP, ABAP environment Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP SuccessFactors Employee Central Operations Real User Monitor- More under Real User Monitoring
Payroll ing (Expert Portal).

SAP Integrated Business Planning for Operations Real User Monitor- More under Real User Monitoring
Supply Chain (SAP IBP) ing (Expert Portal).

Setup and Administration for SAP Cloud ALM

20 PUBLIC Supported Solutions
 SAP Cloud ALM SAP Cloud ALM
SAP Solution Area Capability Notes

SAP BTP, Cloud Foundry environment Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP NetWeaver Application Server for Operations Real User Monitor- More under Real User Monitoring
ABAP (7.40 and higher) ing (Expert Portal).

Data Quality Management, Microservi- Operations Real User Monitor- More under Real User Monitoring
ces for Location Data (DQM Microservi- ing (Expert Portal).
ces)

SAP Broker Reconciliation for Com- Operations Real User Monitor- More under Real User Monitoring
modity Derivatives ing (Expert Portal).

SAP Ariba Category Management Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP Batch Release Hub for Life Scien- Operations Real User Monitor- More under Real User Monitoring
ces ing (Expert Portal).

Integration Hub for Life Sciences Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP BTP, Kyma runtime Operations Real User Monitor- More under Real User Monitoring
ing (Expert Portal).

SAP Business Suite Operations Configuration & More in the Expert Portal (SAP Sup-
Security Analysis port Portal).

SAP S/4HANA (on-premise) Operations Configuration & More in the Expert Portal (SAP Sup-
Security Analysis port Portal).

SAP S/4HANA Cloud, private edition Operations Configuration & More in the Expert Portal (SAP Sup-
Security Analysis port Portal).

SAP NetWeaver Application Server for Operations Configuration & More in the Expert Portal (SAP Sup-
ABAP (7.40 and higher) Security Analysis port Portal).

Identity Authentication Operations Configuration & More in the Expert Portal (SAP Sup-
Security Analysis port Portal).

SAP Credential Store Operations Configuration & More in the Expert Portal (SAP Sup-
Security Analysis port Portal).

SAP NetWeaver Application Server for Implementation Change & Deploy- Prerequisites:
ABAP (7.40 and higher) ment Management
• SAP_BASIS 7.40 SP 20 and higher
or 7.50 SP 04 and higher
• ST-PI 740 SP 18 and higher

SAP Business Suite Implementation Change & Deploy-

ment Management

Setup and Administration for SAP Cloud ALM

Supported Solutions PUBLIC 21
5 Video-Guided Setup

To learn how to set up SAP Cloud ALM for productive use, you can watch the following step-by-step how-to
videos.

For more detailed information, refer to the corresponding documentation under Required Setup for SAP Cloud
ALM [page 28].

Requesting SAP Cloud ALM on SAP for Me

Find out how to request SAP Cloud ALM on SAP for Me.

Corresponding documentation: Requesting SAP Cloud ALM [page 23]

Onboarding Users in Your Identity Authentication Service

Find out how to activate your account in the Identity Authentication service, how to create users in your Identity
Authentication tenant, and how to add them to SAP Cloud ALM.

Corresponding documentation: Step 1: Onboard Users in the Identity Authentication Service [page 30]

Assigning Roles to Users in SAP Cloud ALM

Find out how to assign roles to users in the User Management app in SAP Cloud ALM and in the SAP BTP
cockpit.

Corresponding documentation: Step 2: Assign Roles to Users in SAP Cloud ALM [page 32]

Setup and Administration for SAP Cloud ALM

22 PUBLIC Video-Guided Setup
6 Requesting SAP Cloud ALM

You can request SAP Cloud ALM on SAP for Me for yourself or for all entitled customers for whom you have
sufficient permissions.

 Caution

The S-user who requests SAP Cloud ALM receives permissions that are required for administrative tasks in
the SAP BTP cockpit and in SAP Cloud ALM. In addition, the S-user is added to the Identity Authentication
service (IAS) tenant.

Therefore, to avoid authorization issues during the configuration of SAP Cloud ALM, only carry out the
following steps if you will later perform the configuration described in Required Setup for SAP Cloud ALM
[page 28].

If you request SAP Cloud ALM and then want to assign additional administrators who can perform the
initial setup, refer to KBA 3248116 .

Prerequisites

• You have an S-user with the role Edit Cloud Data on SAP for Me.
You can manage your users and authorizations by following the steps described in Manage User
Authorizations.
• You're assigned to the respective customer.

Procedure

1. Open the Systems & Provisioning dashboard on SAP for Me.

2. Under Products Available for Provisioning, find your entitlement for SAP Cloud ALM.

Setup and Administration for SAP Cloud ALM

Requesting SAP Cloud ALM PUBLIC 23
3. Choose Start Provisioning.
4. Select the geographical region in which you would like to provision SAP Cloud ALM. A suitable data center
will be selected for you.
To find out on which data centers SAP Cloud ALM is available, refer to Data Center Locations in SAP
Security and Trust.
Please note that it's currently not possible to move your SAP Cloud ALM application from the data center
in which it was originally provisioned to a different data center.
5. Enter a unique subdomain name.
The subdomain name is used for the creation of an SAP Cloud ALM-specific subaccount in the SAP Cloud
ALM-specific global account on SAP BTP. It's also part of the URL that is used to access SAP Cloud ALM,
as in https://<subdomain>.<region>.alm.cloud.sap. Therefore, the subdomain name needs to be
unique.
Don't use a pre-existing subdomain. Choose a new subdomain name specifically for SAP Cloud ALM.
Please also keep the following recommendations and restrictions in mind when choosing a subdomain
name:
• Companies with multiple international subsidiaries or working in multiple industries should use
different subdomains for each unit.
• We strongly recommend using the suffix -cloudalm at the end of the subdomain name, for example,
company-cloudalm.
• Allowed characters for the name are lowercase letters, digits, and hyphens. The length of the selected
name must not exceed 56 characters.

 Caution

The subdomain name can't be changed after the system has been provisioned.

6. Specify an SAP Cloud Identity Service:

• If you don’t have an existing productive Identity Authentication tenant, a new one will be created for
you.

Setup and Administration for SAP Cloud ALM

24 PUBLIC Requesting SAP Cloud ALM
 We recommend reusing this newly created productive Identity Authentication tenant for other
productive SAP cloud offerings (such as SAP S/4HANA Cloud) that you may want to use in the future.
• If you already have a productive Identity Authentication tenant, select it from the list.

 Tip

If you have multiple Identity Authentication tenants and you're unsure about which one to select,
look up the administrators of the Identity Authentication tenants that are assigned to your
customer ID at https://iamtenants.accounts.cloud.sap . The administrators can give you more
guidance on what to consider when selecting an Identity Authentication tenant.

Here are some additional recommendations:

• To ensure the best performance, select an Identity Authentication tenant in a region that is
close to the region of your SAP Cloud ALM tenant.
• To simplify the maintenance of administrators in your Identity Authentication tenant, select an
Identity Authentication tenant whose administrators will also govern the identity information
for SAP Cloud ALM.
• If your company has specific requirements (functional or legal) to not allow users from an SAP
Cloud ALM tenant to access an SAP SuccessFactors tenant (or vice versa), both applications
should use separate Identity Authentication tenants. You can find more SAP SuccessFactors-
specific guidance on this topic here.
If you have no other Identity Authentication tenants available for selection, you can request a
new one as described in Tenant Model and Licensing – Getting an Additional Tenant.

If you've already been working with an Identity Authentication tenant but it isn't listed here, it may not
be a productive tenant or it may be assigned to a different customer ID.
If you later want to use a different Identity Authentication tenant for SAP Cloud ALM, you can change
the assignment by following SAP Note 3020352 .

Setup and Administration for SAP Cloud ALM

Requesting SAP Cloud ALM PUBLIC 25
7. If you agree to the terms and conditions stated in the linked order document, mark the checkbox.
8. Once you choose Submit, you can track the status of the provisioning under Provisioning Status.
9. When the status is Provisioning Triggered, SAP automatically prepares SAP Cloud ALM and creates the
following entities (see also graphic below):
• A global account with the name “SAP Cloud ALM” followed by your customer number.
A global account is the realization of a contract you made with SAP. It's region-independent, and it's
used to manage subaccounts, members, entitlements (including your SAP Cloud ALM entitlement),
and quotas.
• A subaccount with the name “SAP Cloud ALM” that contains your SAP Cloud ALM subscription and
subscriptions to the Cloud Integration Automation service and SAP Cloud Transport Management.
Subaccounts let you structure a global account according to your organization's and project's
requirements with regard to members, authorizations, and entitlements.

 Caution

You can't subscribe to any additional applications in the subaccount containing your SAP Cloud
ALM subscription. The subaccount is set up exclusively for SAP Cloud ALM.

Don't delete this subaccount or your SAP Cloud ALM subscription if you've already started using
SAP Cloud ALM productively. Deleting your SAP Cloud ALM subscription causes all created
artifacts, stored data, and current configurations to be deleted as well.

10. A mutual trust relationship between SAP Cloud ALM and the selected Identity Authentication tenant is
established.

If you want to know more about the role of SAP Cloud ALM and your Identity Authentication tenant in the
context of SAP S/4HANA Cloud in the 3-system landscape, refer to User Onboarding for SAP S/4HANA
Cloud with SAP Central Business Configuration.
11. You receive emails containing logon information, configuration guidance, and links to support resources.

Setup and Administration for SAP Cloud ALM

26 PUBLIC Requesting SAP Cloud ALM
  Note

If you've requested SAP Cloud ALM, you've been automatically signed up for cloud email notifications. This
way, you can remain informed and receive timely updates regarding SAP Cloud ALM.

You can manage your notification settings in the Cloud System Notification Subscriptions application, as
described in KBA 2900069 .

Related Information

SAP for Me Online Help

Cloud Integration Automation Service
SAP Cloud Transport Management

Setup and Administration for SAP Cloud ALM

Requesting SAP Cloud ALM PUBLIC 27
7 Required Setup for SAP Cloud ALM

After you've requested SAP Cloud ALM, there are additional mandatory configuration steps that are required to
set up SAP Cloud ALM for productive use.

SAP Cloud ALM is included in your cloud subscription and helps you to implement and operate intelligent cloud
and hybrid business solutions. By following steps 1-3 in the next chapters, you can start to use SAP Cloud ALM
immediately.

Need Support?

If you need support, take a look at the following resources:

• Services for SAP Cloud ALM

• Troubleshooting and FAQ [page 114]
• Schedule an Expert

 Caution

It's currently not possible to move your SAP Cloud ALM application from the data center in which it was
originally provisioned to a different data center.

Required Authorizations

If you requested SAP Cloud ALM, your user has received all authorizations required to perform the initial setup.
However, we recommend also manually assigning these authorizations to at least one more user.

The following authorizations are required to perform the initial setup of SAP Cloud ALM:

Environment Role

Identity Authentication tenant Administrator

If a new Identity Authentication tenant was created for you when you
requested SAP Cloud ALM, you've automatically received the required
roles in the Identity Authentication tenant.

If someone else requested SAP Cloud ALM or if you're using a pre-ex-

isting Identity Authentication tenant for SAP Cloud ALM, the administra-
tor can add you as an administrator by following the steps described
in Managing Administrators in Identity Authentication.

Setup and Administration for SAP Cloud ALM

28 PUBLIC Required Setup for SAP Cloud ALM
 Environment Role

SAP BTP cockpit • Global Account Administrator in the global account that contains
your SAP Cloud ALM entitlement
If you don't have this authorization, the global account administrator
can assign it to you by following the steps described in Add Mem-
bers to Your Global Account.
• Subaccount Administrator in the subaccount that contains your SAP
Cloud ALM subscription
If you don't have this authorization, the subaccount administrator
can assign the role to you by following the steps described in Add
Members to Your Subaccount.
• Org Manager for the Cloud Foundry organization in your SAP Cloud
ALM subaccount
This role is only required if a Cloud Foundry org and space exist in
your SAP Cloud ALM subaccount and is in use in the context of SAP
Cloud ALM APIs.
If you don't have this role, the org manager can assign it to you
by following the steps described in Add Org Members Using the
Cockpit.

SAP Cloud ALM • Global Administrator or User Administrator

If you don't have these authorization, the Global Administrator can assign
one of the required roles to you by following the steps described in Assign
Roles to Users in SAP Cloud ALM.

Overview: Onboarding Procedure

On this interactive image, you can see all mandatory setup steps for SAP Cloud ALM at a glance. For detailed
guidance, click on the respective sections.

Setup and Administration for SAP Cloud ALM

Required Setup for SAP Cloud ALM PUBLIC 29
• Requesting SAP Cloud ALM [page 23]
• Step 1: Onboard Users in the Identity Authentication Service [page 30]
• Step 2: Assign Roles to Users in SAP Cloud ALM [page 32]
• Step 3: Set Up Landscape Management [page 42]
• Integration and Configuration Options [page 44]

For more detailed background information and general explanations of SAP BTP concepts, refer to Basic
Platform Concepts.

7.1 Step 1: Onboard Users in the Identity Authentication

Service
To give further users access to SAP Cloud ALM, you need to create or import users in your Identity
Authentication tenant.

Context

In SAP Cloud ALM, the Identity Authentication service assumes the role of the identity provider. This means
that business users log on to SAP Cloud ALM with the mechanisms and credentials defined in the Identity
Authentication tenant.

 Note

You can also use an already existing corporate identity provider (LDAP), in which case we strongly
recommend using Identity Authentication as a proxy. Changing to a corporate identity provider while

Setup and Administration for SAP Cloud ALM

30 PUBLIC Required Setup for SAP Cloud ALM
 already using SAP Cloud ALM productively can result in invalidated user IDs and can cause users in SAP
Cloud ALM to be deactivated.

For more information, refer to Corporate Identity Providers.

When you requested SAP Cloud ALM, you either selected a pre-existing Identity Authentication tenant or
requested a new one:

• Reusing an existing Identity Authentication tenant:

If you requested SAP Cloud ALM on SAP ONE Support Launchpad, your pre-existing Identity
Authentication tenant was automatically used as your identity provider for SAP Cloud ALM. If you
requested SAP Cloud ALM on SAP for Me, you were able to select a pre-existing SAP Cloud Identity
Service. In both cases, you were only made a member in the respective Identity Authentication tenant. You
didn't automatically receive administrator authorizations in this tenant and you didn't receive an additional
activation email for it.
Your pre-existing tenant may already contain identity information. If you don't need new users in the
tenant, you can proceed directly to Step 2: Assign Roles to Users in SAP Cloud ALM [page 32] to add
these users to SAP Cloud ALM and assign roles to them.
If you do want to create new users in the tenant, contact the administrator of the Identity Authentication
tenant that is connected to SAP Cloud ALM and either request that they follow the procedure below, or ask
them to assign the required roles to you.
• Creating a new Identity Authentication tenant:
If you didn't have a productive Identity Authentication tenant when you requested SAP Cloud ALM, a new
tenant was automatically created for you in the same data center where SAP Cloud ALM is provisioned.
This tenant is connected to the SAP Cloud ALM subaccount. As the requesting user, you were made an
administrator in this new tenant and received an email asking you to activate your account in the Identity
Authentication service.
The productive Identity Authentication tenant you received for SAP Cloud ALM may also be used for other
productive SAP cloud offerings (such as SAP S/4HANA Cloud) that you may want to use in the future.
In the newly generated tenant, no identity information is currently maintained. Before SAP Cloud ALM can
be used, users have to be created or imported.

For more information, refer to the following step-by-step video:

Prerequisites

• Your Identity Authentication tenant has been activated.

If your Identity Authentication tenant was newly created when you requested SAP Cloud ALM, you've
received an email with the subject Activate Your Account for Identity Authentication Service. Follow the
guidance to activate the account and create a user profile for yourself.
• In your Identity Authentication tenant, you have a user with the role Manage Users.
If you've requested SAP Cloud ALM and a new Identity Authentication tenant was set up for you, your user
has automatically received this authorization during the creation of the tenant. If someone else requested
SAP Cloud ALM or you're using an existing Identity Authentication tenant in which you don't have this
authorization, the tenant administrator can assign the role to you by following the steps described in
Managing Administrators in Identity Authentication.
To find the administrator of your Identity Authentication tenant, refer to Viewing Assigned Tenants and
Administrators.

Setup and Administration for SAP Cloud ALM

Required Setup for SAP Cloud ALM PUBLIC 31
Procedure

1. In the administration console of the SAP Cloud Identity Services, open the User Management app.

 Tip

The URL has the following pattern: https://<tenant ID>.accounts.ondemand.com/admin

The first administrator that was created for the Identity Authentication tenant received an activation
email containing a direct link to the administration console.

2. Choose + Add User.

3. Fill in the required fields.
Remember the email address, as you need it to assign roles to the user later.
For information about the available user types, refer to User Types.
4. Under Personal Information, enter the first and the last name of the user. Use only the allowed characters
A-Z, a-z, spaces, and hyphens.
5. Save.
6. Select Send activation e-mail.
7. Save your entries.

The new user now receives an activation email and can set a password.

 Note

If you've already defined users elsewhere in your landscape, you can also import them to the Identity
Authentication service by using various tools, such as SAP Identity Management and the Identity
Provisioning service.

For more information, refer to Import or Update Users for a Specific Application in the documentation for
the Identity Authentication service.

Related Information

SAP Cloud Identity Services - Identity Authentication

7.2 Step 2: Assign Roles to Users in SAP Cloud ALM

After onboarding your users to your Identity Authentication tenant, you need to add them to SAP Cloud ALM
and assign roles to them.

You can assign roles to users directly in the SAP Cloud ALM User Management app (recommended) or as
corresponding role collections in the SAP BTP cockpit.

 Note

If you're working with role mapping to user groups in your identity provider, you must assign role collections
in the SAP BTP cockpit. In this case, you can't view or change roles in the User Management app. You

Setup and Administration for SAP Cloud ALM

32 PUBLIC Required Setup for SAP Cloud ALM
 also can't use the role request and assignment features in SAP Cloud ALM, so we don't recommend this
method.

SAP Cloud ALM User Management (Recommended)

Prerequisites

• Your user has the role Global Administrator or User Administrator.

If you've requested SAP Cloud ALM, you've automatically received the role Global Administrator. If
someone else has requested SAP Cloud ALM, they can assign one of the required roles to you by following
the process below.
• The identities of the users to whom you want to assign roles already exist in the identity provider, as
described in Step 1: Onboard Users in Your Identity Authentication Service [page 30].

Procedure
1. Access SAP Cloud ALM. A link is included in the email Welcome to SAP Cloud ALM.
Sign in with the email address and password you've defined when activating your account in the Identity
Authentication service. Do not sign in with your S-user.
2. Open the User Management app, which is located in the Administration section.
3. To go to the user list, choose  (Users).
4. Choose Add User.
5. Enter the User ID and/or Email as you've defined them in the settings of your identity provider. If, as per our
recommendations, you've selected your email address as your user ID in your identity provider, you only
need to enter the email address.
6. Select a type for your user. Possible types are:

Type Description

Not Assigned No user type (default value)

Employee Employee of your company

SAP Consultant from SAP

Partner Consultant from official SAP partner

Other Person from a company other than SAP or official SAP

partner

7. Assign one or multiple roles to the user.

For an overview of all predefined role collections that are available in SAP Cloud ALM, refer to Role
Collections [page 35].
8. Save your settings.

The user will now also receive a welcome email from SAP Cloud ALM.

Setup and Administration for SAP Cloud ALM

Required Setup for SAP Cloud ALM PUBLIC 33
For more information on how to use the User Management app to view, add, and change roles, refer to User
Management.

SAP BTP Cockpit

The roles in SAP Cloud ALM are available as role collections in your subaccount in the SAP BTP cockpit.

 Note

The role collections that you assign in the SAP BTP cockpit are synchronized by the User Management app
only once a day.

As a result, although the role collection assignment takes effect in SAP Cloud ALM immediately (with the
next logon of the user), it may not be displayed in the User Management app for up to 24 hours.

Prerequisites

• Your user has the role Subaccount Administrator in the subaccount that contains your SAP Cloud ALM
subscription.
If you have requested SAP Cloud ALM, your user has automatically received this authorization during the
creation of the subaccount. If you don't have this authorization, the subaccount administrator can assign
the role to you by following the steps described in Add Members to Your Subaccount.
• The identities of the users to whom you want to assign roles already exist in the identity provider, as
described in Step 1: Onboard Users in Your Identity Authentication Service [page 30].

Procedure

1. Open the SAP BTP cockpit.

2. Select the global account that contains your SAP Cloud ALM entitlement, which was created when you
requested SAP Cloud ALM.
3. Under Subaccounts, select the subaccount that contains your SAP Cloud ALM subscription.
4. Navigate to Security Role Collections .
5. Select the role collection to which you want to add users.
6. Choose Edit.
7. Add users to this role collection as follows:
• If you’re using the standard configuration in trust settings and identity provider that was set when you
requested SAP Cloud ALM, enter the email address of the user into the fields ID and E-Mail. Select
Custom IAS Tenant as identity provider.
• If you've manually connected the identity provider or selected a different identification attribute (such
as user ID) in your identity provider, enter the identification attribute that you maintained there into the
field ID and make sure to select the correct identity provider.

 Caution

Don't use the identity provider Default identity provider, SAP ID Service, or sap.default.

Setup and Administration for SAP Cloud ALM

34 PUBLIC Required Setup for SAP Cloud ALM
7.2.1 Role Collections

Role collections in SAP Cloud ALM are delivered predefined and ready to use.

Each application role in SAP Cloud ALM represents a role collection in your SAP BTP subaccount, which in
turn corresponds 1:1 to the respective role template. This means that you don't have to configure any role
collections yourself. Instead, you can simply assign the relevant role collections to the users based on their
tasks and requirements.

 Caution

The Cross Global Administrator and the User & Access Management Administrator role collections consist
of more than one role template.

If you want to create your own role collections by bundling several predefined role collections
together, don't forget to add the role template FlexOperator whenever you include the role templates
x_calm_GlobalAdministrator or x_uam_UserAdministrator.

The following role collections are available for each application area in SAP Cloud ALM:

Role Title in SAP Role Col-

Cloud ALM User lection
Capability Management Description Name Role Template

Cross Global Create and manage all SAP Cloud ALM Cross x_calm_GlobalAdmi
Administrator objects, except for personal or sensitive Global nistrator
data Administra
FlexOperator
tor
 Caution
This role provides the complete set
of authorizations. We recommend
assigning suitable roles to your
users.

Cross Global Auditor View all SAP Cloud ALM objects, except Cross x_calm_GlobalAudi
personal or sensitive data Global tor
Auditor
This role is to be used for general audit
purposes.

User & Access Man- User Create and manage users, assign and User & x_uam_UserAdminis
agement Administrator approve authorizations Access trator
Manageme FlexOperator
nt
Administra
tor

Setup and Administration for SAP Cloud ALM

Required Setup for SAP Cloud ALM PUBLIC 35
 Role Title in SAP Role Col-
Cloud ALM User lection
Capability Management Description Name Role Template

User & Access Man- User Viewer View users and authorization assign- User & x_uam_UserViewer
agement ments Access
Manageme
nt Viewer

Tag Management Tag Administrator Create, update, merge and centrally de- Tag x_tag_TagAdminist
lete tags, view tag usage and organize Manageme rator
tags into groups nt
Administra
tor

Tag Management Tag Viewer View tags, tag groups and tag usage Tag x_tag_TagViewer
Manageme
nt Viewer

Landscape Manage- Landscape Manage certificates Landscape x_landscape_Secur

ment Management Manageme ityAdministrator
Security nt Security
Administrator Administra
tor

Project Management Project Manage projects, deployment plans, Project & imp_pjm_ProjectAd
Administrator tasks, scopes, process hierarchy nodes, Task ministrator
requirements, features, notes, docu- Manageme
ments, test cases, defects, tags, and nt
SAP Readiness Check analyses Administra
tor
The permissions within implementation
projects of users with this role addition-
ally depend on the access level of the
project and the team assignment. For
more information, refer to Configuring
Project User Permissions.

Project Management Project Lead Manage projects, deployment plans, Project & imp_pjm_ProjectLe
tasks, scopes, process hierarchy nodes, Task ad
requirements, features, notes, docu- Manageme
ments, test cases, and defects, and view nt Project
SAP Readiness Check analyses Lead

The permissions within implementation

projects of users with this role addition-
ally depend on the access level of the
project and the team assignment. For
more information, refer to Configuring
Project User Permissions.

Setup and Administration for SAP Cloud ALM

36 PUBLIC Required Setup for SAP Cloud ALM
 Role Title in SAP Role Col-
Cloud ALM User lection
Capability Management Description Name Role Template

Project Management Project Member View projects, deployment plans, and Project & imp_pjm_ProjectMe
SAP Readiness Check analyses. Man- Task mber
age tasks, scopes, process hierarchy Manageme
nodes, requirements, features (with nt Project
restrictions), notes, documents, test Member
cases, and defects

The permissions within implementation

projects of users with this role addition-
ally depend on the access level of the
project and the team assignment. For
more information, refer to Configuring
Project User Permissions.

Project Management Project Viewer View projects, deployment plans, tasks, Project & imp_pjm_ProjectVi
scopes, process hierarchy nodes, Task ewer
requirements, features, notes, docu- Manageme
ments, test cases, defects, and SAP nt Project
Readiness Check analyses Viewer

The permissions within implementation

projects of users with this role addition-
ally depend on the access level of the
project and the team assignment. For
more information, refer to Configuring
Project User Permissions.

Process Management Process Author Create, edit, and delete custom solution Process imp_pm_ProcessAut
processes Manageme hor
nt Process
Author

Change & Deployment Change Manager Approve features for production deploy- Change & imp_cdm_ChangeMan
Management ment Deployme ager
nt
Manageme
nt Change
Manager

Change & Deployment Deployment Deploy transports into test and produc- Change & imp_cdm_Deploymen
Management Manager tion systems Deployme tManager
nt
Manageme
nt
Deployme
nt
Manager

Setup and Administration for SAP Cloud ALM

Required Setup for SAP Cloud ALM PUBLIC 37
 Role Title in SAP Role Col-
Cloud ALM User lection
Capability Management Description Name Role Template

SAP Readiness Check Readiness Create, edit, and delete SAP Readiness Readiness imp_rc_AnalysisAd
Check Analysis Check analyses Check ministrator
Administrator Analysis
Administra
tor

SAP Readiness Check Readiness Check View all SAP Readiness Check analyses Readiness imp_rc_AnalysisVi
Analysis Viewer Check ewer
Analysis
Viewer

Business Process Process Maintain global and specific configura- Business ops_bm_ProcessMon
Monitoring Monitoring tions, consume KPIs and the respec- Process itoringAdministra
Administrator tive process content (including sensitive Monitoring tor
data), and process alerts Administra
tor

Business Process Process Manager Consume KPIs and the respective proc- Business ops_bm_ProcessMan
Monitoring ess content (including sensitive data), Process ager
process alerts, and maintain specific Monitoring
configurations Process
Manager
Additionally, the access to particular
business processes and data criteria
can be restricted for users with this role
by setting up access groups. For more
information, refer to Creating Access
Groups.

Business Process Process Executor Consume KPIs and the respective proc- Business ops_bm_ProcessExe
Monitoring ess content (including sensitive data), Process cutor
and process alerts Monitoring
Process
Additionally, the access to particular
Executor
business processes and data criteria
can be restricted for users with this role
by setting up access groups. For more
information, refer to Creating Access
Groups.

Setup and Administration for SAP Cloud ALM

38 PUBLIC Required Setup for SAP Cloud ALM
 Role Title in SAP Role Col-
Cloud ALM User lection
Capability Management Description Name Role Template

Business Process Process Consume KPIs and the respective proc- Business ops_bm_ProcessMon
Monitoring Monitoring ess content (including sensitive data), Process itoringConsumer
Consumer and view alerts Monitoring
Consumer
Additionally, the access to particular
business processes and data criteria
can be restricted for users with this role
by setting up access groups. For more
information, refer to Creating Access
Groups.

Business Process Process Consume KPIs and non-sensitive proc- Business ops_bm_ProcessMon
Monitoring Monitoring Viewer ess content, without access to alert in- Process itoringViewer
formation Monitoring
Viewer
Additionally, the access to particular
business processes and data criteria
can be restricted for users with this role
by setting up access groups. For more
information, refer to Creating Access
Groups.

Integration & Excep- Integration Configure integration monitoring Integration ops_im_Integratio

tion Monitoring Architect Monitoring nArchitect
Integration
Architect

Integration & Excep- Integration Owner View the messages in integration moni- Integration ops_im_Integratio
tion Monitoring toring Monitoring nOwner
Integration
Owner

Integration & Excep- Integration Owner View the messages in integration mon- Integration ops_im_Integratio
tion Monitoring Sensitive itoring, including data defined as sensi- Monitoring nOwnerSensitive
tive Integration
Owner
Sensitive

Job & Automation Job Monitoring Create, edit, delete, and manage config- Job ops_jm_JobMonitor
Monitoring Administrator uration settings, including the display of Monitoring ingAdministrator
monitoring data Administra
tor

Job & Automation Job Monitoring View the job monitoring application for Job ops_jm_JobMonitor
Monitoring Consumer the maintained global configurations Monitoring ingConsumer
Consumer

Setup and Administration for SAP Cloud ALM

Required Setup for SAP Cloud ALM PUBLIC 39
 Role Title in SAP Role Col-
Cloud ALM User lection
Capability Management Description Name Role Template

Real User Monitoring Real User Analyst View utilization and performance of re- Real User ops_rum_RealUserA
Administrator quests, including sensitive data like the Monitoring nalystAdministrat
user ID, and configure the real user Analyst or
monitoring app Administra
tor

Real User Monitoring Real User Analyst View utilization and performance of re- Real User ops_rum_RealUserA
quests Monitoring nalyst
Analyst

Real User Monitoring Real User Analyst View utilization and performance of re- Real User ops_rum_RealUserA
Sensitive quests, including sensitive data like the Monitoring nalystSensitive
user ID Analyst
Sensitive

Synthetic User Moni- Scenario Create, edit, delete, manage configura- Synthetic ops_sum_Synthetic
toring Administrator tions and manage global application User UserMonitoringAdm
settings. View performance and availa- Monitoring inistrator
bility of scenario executions Administra
tor

Synthetic User Moni- Scenario Expert Create, edit, delete, and manage config- Synthetic ops_sum_Synthetic
toring uration settings. View performance and User UserMonitoringExp
availability of scenario executions Monitoring ert
Scenario
Expert

Synthetic User Moni- Scenario Viewer View performance and availability of Synthetic ops_sum_Synthetic
toring scenario executions User UserMonitoringVie
Monitoring wer
Scenario
Viewer

Health Monitoring Health Monitoring Create, edit, delete, and manage config- Health ops_hm_HealthMoni
Administrator uration settings, including the display of Monitoring toringAdministrat
monitoring data Administra or
tor

Health Monitoring Health Monitoring View health overview and metrics of Health ops_hm_HealthMoni
Viewer cloud services Monitoring toringViewer
Viewer

Setup and Administration for SAP Cloud ALM

40 PUBLIC Required Setup for SAP Cloud ALM
 Role Title in SAP Role Col-
Cloud ALM User lection
Capability Management Description Name Role Template

Business Service Man- Business Service Create and manage business services, Business ops_bsm_BusinessS
agement Management and plan events Service erviceManagementA
Administrator Manageme dministrator
nt
Administra
tor

Business Service Man- Business Service View business services, their configura- Business ops_bsm_BusinessS
agement Management tion, and the event calendar Service erviceManagementV
Viewer Manageme iewer
nt Viewer

Configuration & Secur- Configuration Administrate managed objects, configu- Configurati ops_csa_Configura
ity Analysis Monitoring ration settings, and display application on tionMonitoringAdm
Administrator data Monitoring inistrator
Administra
tor

Configuration & Secur- Configuration Display application configuration data Configurati ops_csa_Configura
ity Analysis Monitoring on tionMonitoringAna
Analyst Monitoring lyst
Analyst

Service Collaboration Services Execute service-specific administration Service sdc_sc_ServicesAd

Administrator tasks, configure and execute services, Collaborati ministrator
and view service execution results on
Administra
tor

Service Collaboration Services Expert Configure and execute services, and Service sdc_sc_ServicesEx
view own and shared service execution Collaborati pert
results on Expert

Service Collaboration Services Viewer Browse through the service explorer Service sdc_sc_ServicesVi
and view the shared service execution Collaborati ewer
results on Viewer

SAP Business Trans- Digital Blueprint Create and edit digital blueprints and all Digital btc_bdts_DigitalB
formation Center – Administrator associated tasks, company code scop- Blueprint lueprintAdministr
Scoping ing, and transformation object scoping Administra ator
tor

SAP Business Trans- Digital Blueprint Consume digital blueprint content, view Digital btc_bdts_DigitalB
formation Center – Viewer company code scoping and transforma- Blueprint lueprintViewer
Scoping tion object scoping Viewer

Setup and Administration for SAP Cloud ALM

Required Setup for SAP Cloud ALM PUBLIC 41
7.3 Step 3: Set Up Landscape Management

As the last step of the required setup, services and systems need to be set up in the Landscape Management
app in SAP Cloud ALM.

Landscape management in SAP Cloud ALM helps you manage information about your services, systems, and
business services. This information is the basis for all SAP Cloud ALM apps.

What Are Services and Systems?

In SAP Cloud ALM, services are understood as subscribed cloud services, that is, solutions and applications
that are offered on-demand from the servers of a cloud provider (SaaS).

Systems are defined as on-premise systems, that is, solutions and applications that are provided by SAP but
installed and run on the premises of the company or organization using them, or in a private cloud solution.

Connecting Services and Systems

For more information on how services and systems are connected to SAP Cloud ALM, refer to the following
subpages:

• Services [page 42]

• Systems [page 43]

You have full control which data from managed services and systems is transferred to SAP Cloud ALM:

When you activate your SAP Cloud ALM tenant and register your systems and services in the Landscape
Management app of SAP Cloud ALM, the collection of observability data is not started automatically. SAP
Cloud ALM follows a central configuration approach: You need to explicitly configure the data collection
processes.

In addition, SAP is moving from customer-managed connectivity (established by customers) to SAP-managed

connectivity (established by SAP). To find out which additional steps are necessary to establish customer-
managed connectivity, see Setup Managed Services / Systems in the operations expert portal.

If you encounter issues while working with the Landscape Management app, take a look at Landscape
Management – Troubleshooting and Customer Support on SAP Support Portal.

7.3.1 Services

The import method of services in SAP Cloud ALM depends on the service type of your solution.

• Most service types are imported into SAP Cloud ALM automatically if they are assigned to the same
customer number as your SAP Cloud ALM tenant. This import is done on a daily basis by the System
Landscape Information service.

Setup and Administration for SAP Cloud ALM

42 PUBLIC Required Setup for SAP Cloud ALM
 To display the current status in the Landscape Management app, open the Configuration ( ), expand the
section Import of Subscribed SAP Services, and click on the first icon after Status of imports.

 Note

If you have services that are assigned to a different customer number (for example, as a global ultimate
customer), you need to enter an S-user that has the authorizations to access the system data for all
subsidiary customer accounts to ensure that the Landscape Management app has access to the data.

The S-user must not be a technical S-user but a standard dialog S-user with CCC Group
authorizations. For more information on how to create such an S-user, refer to SAP Note 3070306 .

To add the S-user, open the Landscape Management app and choose  (Configuration). Under Import
of Subscribed SAP Services, choose  (Add S-User) and enter the credentials of the S-user.

• Other services types (such as SAP SuccessFactors and SAP S/4HANA Cloud) are push-enabled services
that register themselves in SAP Cloud ALM. These services are created automatically in the Landscape
Management app as part of the communication arrangement or registration.
• Only some service types (for example, Unspecific Cloud Service (HTTP) or Managed Gateway for Spend &
Network) must be added to the Landscape Management app manually.

Observability data from your connected services isn't automatically sent to your SAP Cloud ALM tenant. If you
want to start monitoring observability data, the data transfer to SAP Cloud ALM first needs to be configured.

To find out which additional setup steps are required to monitor your service, refer to Setup Managed
Services / Systems in the SAP Cloud ALM for Operations Expert Portal.

7.3.2 Systems

Most systems can to be registered with an ABAP report.

When the registration in the system has been completed, the registered system is automatically displayed on
the Services & Systems page. Once a technical system has been registered, a default logical system (client) is
created and displayed in the System Details.

Only a few system types (for example, SAP Focused Run, Cloud Connector, and SAP Process Integration) can't
be registered but need to be set up manually.

Observability data from your connected systems isn't automatically sent to your SAP Cloud ALM tenant. If you
want to start monitoring observability data, the data transfer to SAP Cloud ALM first needs to be configured.

To find out which setup steps are required for your system, refer to Setup Managed Services / Systems in
the SAP Cloud ALM for Operations Expert Portal.

Setup and Administration for SAP Cloud ALM

Required Setup for SAP Cloud ALM PUBLIC 43
8 Integration and Configuration Options

There are additional integration and configuration options that help you take advantage of the full set of
capabilities of SAP Cloud ALM.

On this interactive image, you can see all optional setup steps for SAP Cloud ALM at a glance. For detailed
guidance, click on the respective sections.

• Enabling SAP Cloud ALM API [page 45]

• Activating the SAP Audit Log Viewer Service [page 59]
• Integrating SAP Central Business Configuration [page 61]
• Enabling SAP Cloud ALM API [page 45]
• Integrating Test Automation Providers [page 90]
• https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal.html [https://
support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal.html]
• Integrating the Cloud Integration Automation Service [page 65]
• Configuring Project User Permissions [page 63]
• Enabling Service Delivery [page 95]
• Enabling Email Channel for In-App Notifications [page 59]
• Integrating the Cloud Integration Automation Service [page 65]
• https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal.html [https://
support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal.html]

Setup and Administration for SAP Cloud ALM

44 PUBLIC Integration and Configuration Options
 • Enabling Transport Management [page 66]
• Integrating Test Automation Providers [page 90]
• Enabling Service Delivery [page 95]

8.1 Enabling SAP Cloud ALM API

To set up the connection between your managed systems and individual SAP Cloud ALM applications, you
need to retrieve your binding credentials and connect your SAP services and systems to your SAP Cloud ALM
instance

Depending on the provisioning date of your SAP Cloud ALM tenant, some or all steps described in this
document have already been automatically completed for you:

Provisioning Date Actions

On or after 2023-10-16 A binding was generated automatically.

You can skip these steps altogether and access your binding in the SAP BTP cockpit or
in the Landscape Management app, as described in Managing Your Service Key [page
57].

Between 2023-06-12 and A service key that can be used to connect managed services to SAP Cloud ALM for
2023-10-16 Operations monitoring applications was generated automatically.

You can access it in the SAP BTP cockpit or in theLandscape Management app, as
described in Managing Your Service Key [page 57].

You only need to carry out these steps if you want to set up transport management, but
you no longer have to configure your entitlements. You can access it in the SAP BTP
cockpit or in the

Before 2023-06-12 No service key or binding has been created as part of the initial provisioning. To create
one manually, carry out the steps listed below.

 Note

This document describes how to retrieve a service key without a Cloud Foundry organization.

You can access it in the SAP BTP cockpit or in theIf a Cloud Foundry organization and space already exist
in your SAP Cloud ALM subaccount (as shown in the image below) and are already in use in the context
of SAP Cloud ALM APIs, you can also follow Enabling SAP Cloud ALM API in Cloud Foundry [page 50].
However, we strongly recommend following the approach without Cloud Foundry.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 45
Prerequisites

Your user has the role Global Account Administrator in the global account that was created when you requested
SAP Cloud ALM, and is a member of the subaccount containing your SAP Cloud ALM subscription.

If you don't have this role, the global account administrator can assign it to you by following the steps described
in Add Members to Your Global Account.

Procedure

Configure Entitlements

An entitlement is your right to provision and consume a resource.

1. Open the SAP BTP cockpit.

2. Select the global account that contains your SAP Cloud ALM entitlement, which was created when you
requested SAP Cloud ALM.
3. Under Subaccounts, select the subaccount that contains your SAP Cloud ALM subscription.
4. Choose Entitlements Configure Entitlements .

Setup and Administration for SAP Cloud ALM

46 PUBLIC Integration and Configuration Options
 5. Choose Add Service Plans.
6. Add the required service plan as follows:
1. Select the entitlement SAP Cloud ALM API.
2. Under Available Plans, check the option standard.
3. Choose Add 1 Service Plan.

7. Save.

Maintain an Instance

1. Choose Services Instances and Subscriptions .

2. If you already have an instance, choose  (Actions) and select Update. Then proceed to step 4.
If you don't have an instance yet, choose Create.
3. Under Basic Info, provide the following details:
• Service: SAP Cloud ALM API

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 47
 • Plan: standard
• Runtime Environment: Other
• Instance Name: Enter a meaningful instance name.
The length of the instance name must not exceed 32 characters. Use only alphanumeric characters,
numbers from 0 to 9, periods, and hyphens. Instead of spaces, use underscores.

4. Choose Next.
5. Paste the following JSON code into the text editor:

{
"xs-security": {
"xsappname": "<your-instance-name>",
"authorities": [
"$XSMASTERAPPNAME.imp-cdm-feature-display-ui",
"$XSMASTERAPPNAME.imp-cdm-feature-manage-ui"
],
"oauth2-configuration": {
"credential-types": [
"binding-secret"
]
}
}
}

6. Replace <your-instance-name> with your instance name.

7. Choose Create.

Setup and Administration for SAP Cloud ALM

48 PUBLIC Integration and Configuration Options
 8. When your instance has been created or updated, click on it.

Create a Binding
Bindings allow you to configure an external application so that it can connect to an SAP Cloud ALM API service
instance.

1. Next to your instance, choose  (Actions) and select Create Binding.

2. Enter a name for your binding.

3. Choose Create.
4. Next to the created binding, choose  (Actions) and select View.
5. You can now see your binding in JSON format.
It includes the following information:
• The application base URL (endpoints.Api)
• The clientid and clientsecret to access the service
• The oAuth URL to generate the oAuth token (uaa.url)

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 49
  Caution

Outside of the SAP BTP cockpit, bindings must be stored securely. If you need a binding, create the binding
directly in the SAP BTP cockpit, and access it from there whenever you need it.

Related Information

Entitlements and Quotas

API Guide for SAP Cloud ALM

8.1.1 Enabling SAP Cloud ALM API in Cloud Foundry

To set up the connection between your managed systems and individual SAP Cloud ALM applications, you
need to retrieve a service key or binding and connect your SAP services and systems to your SAP Cloud ALM
instance.

Depending on the provisioning date of your SAP Cloud ALM tenant, some or all steps described in this
document have already been automatically completed for you:

Setup and Administration for SAP Cloud ALM

50 PUBLIC Integration and Configuration Options
 Provisioning Date Actions

On or after 2023-10-16 A binding was generated automatically.

You can skip these steps altogether and access your binding in the SAP BTP cockpit or
in the Landscape Management app, as described in Managing Your Service Key [page
57].

Between 2023-06-12 and A service key that can be used to connect managed services to SAP Cloud ALM for
2023-10-16 Operations monitoring applications was generated automatically.

You can access it in the SAP BTP cockpit or in the Landscape Management app, as
described in Managing Your Service Key [page 57].

You only need to carry out these steps if you want to set up transport management, but
you can reuse the created space and no longer have to configure your entitlements.

Before 2023-06-12 No service key or binding has been created as part of the initial provisioning. To create
one manually, carry out the steps listed below.

 Note

This document describes how to retrieve a service key in the Cloud Foundry environment. This is no longer
the recommended approach.

If a Cloud Foundry organization and space don't exist in your SAP Cloud ALM subaccount (as shown in
the image below), or if they exist but are not in use in the context of SAP Cloud ALM APIs, please follow
Enabling SAP Cloud ALM API [page 45] instead.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 51
Prerequisites

• Your user has the role Global Account Administrator in the global account that was created when
you requested SAP Cloud ALM, and is a member of the subaccount containing your SAP Cloud ALM
subscription.
If you don't have this role, the global account administrator can assign it to you by following the steps
described in Add Members to Your Global Account.
• Your user has the role Org Manager in your Cloud Foundry organization.
If you don't have this role, the org manager can assign it to you by following the steps described in Add Org
Members Using the Cockpit.

Procedure

Create a Space
1. Open the SAP BTP cockpit.
2. Select the global account that contains your SAP Cloud ALM entitlement, which was created when you
requested SAP Cloud ALM.
3. Under Subaccounts, select the subaccount that contains your SAP Cloud ALM subscription.
4. Choose Cloud Foundry Spaces .
5. If you already have a space with the required authorizations, proceed to the Configure Entitlements
section.
If you don't have a space yet, choose Create Space.

Setup and Administration for SAP Cloud ALM

52 PUBLIC Integration and Configuration Options
 6. Enter a space name and select the roles that you want to assign to your user for this space. To perform the
following steps, your user needs at least Space Developer authorizations.
7. Choose Create.

Configure Entitlements
An entitlement is your right to provision and consume a resource.

1. Choose Entitlements Configure Entitlements .

2. Choose Add Service Plans.

3. Add the required service plan as follows:
1. Select the entitlement SAP Cloud ALM API.
2. Under Available Plans, check the option standard.
3. Choose Add 1 Service Plan.

4. Save.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 53
Maintain an Instance

1. Choose Cloud Foundry Spaces .

2. Select your space.
3. Choose Services Instances .
4. If you already have an instance, choose  (Actions) and select Update. Then proceed to step 6.
If you don't have an instance yet, click on the Create dropdown and select Service Instance.

5. Under Basic Info, provide the following details:

• Service: SAP Cloud ALM API
• Plan: standard
• Instance Name: Enter a meaningful instance name.
The length of the instance name must not exceed 32 characters. Use only alphanumeric characters,
numbers from 0 to 9, periods, and hyphens. Instead of spaces, use underscores.

Setup and Administration for SAP Cloud ALM

54 PUBLIC Integration and Configuration Options
 6. Choose Next.
7. Paste the following JSON code into the text editor:

{
"xs-security": {
"xsappname": "<your-instance-name>",
"authorities": [
"$XSMASTERAPPNAME.imp-cdm-feature-display-ui",
"$XSMASTERAPPNAME.imp-cdm-feature-manage-ui"
]
}
}

8. Replace <your-instance-name> with your instance name.

9. Choose Create.

Create a Service Key

Service keys allow you to configure an external application so that it can connect to an SAP Cloud ALM API
service instance.

1. When your instance has been created, choose  (Actions) next to it and select Create Service Key.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 55
2. Enter a name for your service key.
3. Choose Create.
4. Next to your newly created service key, choose  (Actions) and select View.
5. You can now see your service key in JSON format.
It includes the following information:
• The application base URL (endpoints.Api)
• The clientid and clientsecret to access the service
• The oAuth URL to generate the oAuth token (uaa.url)

Setup and Administration for SAP Cloud ALM

56 PUBLIC Integration and Configuration Options
  Caution

Outside of the SAP BTP cockpit, service keys must be stored securely. If you need a service key, create the
service key directly in the SAP BTP cockpit, and access it from there whenever you need it.

Related Information

Managing Spaces
Entitlements and Quotas
API Guide for SAP Cloud ALM

8.1.2 Managing Your Service Key

If you requested SAP Cloud ALM on or after 2023-06-14, an automatically generated SAP Cloud ALM service
key was uploaded to the Landscape Management app for you. This key can be used to connect managed
services to push monitoring data using OAuth 2.0.

Prerequisites

To access and upload your service key, you need the role Landscape Management Security Administrator.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 57
Accessing Your Service Key

You can access the service key in the Landscape Management app by opening the configuration ( ) and
expanding the section SAP Cloud ALM Service Key.

Here, you can manage your service key as follows:

•  (Display Service Key): Display the content of the uploaded service key.
•  (Download Service Key): Download the service key as a TXT file. The content will be in JSON format.
•  (Delete Service Key): Delete a service key from landscape management.
•  (Test Service Key): Check if this key can be used to log on to the SAP Cloud ALM API.

Uploading a Service Key

If no service key has been uploaded yet, you can add it as follows:

1. Open the SAP BTP cockpit.

2. Select the global account that contains your SAP Cloud ALM entitlement and then open the subaccount
that contains your SAP Cloud ALM subscription.
3. Choose Services Instances and Subscriptions .
4. Under Instances, find the instance that contains your service key.
5. Under Credentials, open your key and choose Download.
6. In the SAP Cloud ALM launchpad, open the Landscape Management app.
7. Open the configuration ( ) and expand the section SAP Cloud ALM Service Key.
8. Choose  (Add).
9. Upload the TXT file containing the service key.

 Note

• You can only upload one service key for this SAP Cloud ALM tenant.
• We recommend that you upload the service key to landscape management that is used regularly to
connect managed services and systems to SAP Cloud ALM, for example, for monitoring setup or
transport management.
• You can use the same service key for all managed services and systems to connect them for the
same purpose, such as monitoring.
• If you use a different "one-use" service key for each managed service, don't upload this key to
landscape management. This functionality is intended for regularly used keys only.
• Don't upload service keys for API calls, such as the SAP Cloud ALM Analytics API, to landscape
management.

10. Choose Upload.

A format check is performed before uploading the service key to make sure it is a valid service key.

 Caution

If you delete a service key or an SAP Cloud ALM API service instance in the BTP cockpit, the service key in
the Landscape Management app will not be deleted automatically. Please make sure to also delete it from
landscape management, as it can no longer be used for authentication.

Setup and Administration for SAP Cloud ALM

58 PUBLIC Integration and Configuration Options
8.2 Activating the SAP Audit Log Viewer Service

By integrating the SAP Audit Log Viewer service for SAP BTP, you can view the audit logs for your SAP
Cloud ALM tenant to track the end user activity in SAP Cloud ALM. Audit logs represent security-relevant
chronological records that provide documentary evidence for an event or activity.

To display the audit logs in the Audit Log Viewer Service application on SAP BTP, subscribe to the SAP Audit
Log Viewer service in your subaccount as described in Audit Log Viewer for the Cloud Foundry Environment.

8.3 Enabling Email Channel for In-App Notifications

You can enable the email channel for the in-app notifications that are sent by SAP Cloud ALM.

In detail, the following in-app notifications are created:

App Cause of the notification

Projects New Roadmap content updates exist.

Tasks A task was assigned to you.

A new comment exists on a task assigned to you.

Requirements A requirement was assigned to you.

A new comment exists on a requirement assigned to you.

Defects A defect was assigned to you.

A new comment exists on a defect assigned to you.

Features A feature was assigned to you.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 59
App Cause of the notification

User Management Open authorization requests exist.

 Note

In SAP Cloud ALM for operations, email notifications are sent based on events using Intelligent Event
Processing and Notification Management. These notifications are not the subject of this topic because they
are not displayed in the in-app notifications.

Prerequisites

To enable email notifications, you need to maintain a destination in your SAP BTP subaccount for SAP Cloud
ALM, as described in Configuring an SMTP Mail Destination.

 Caution

For the configuration mentioned above you have to operate your own email server which is under your
responsibility. Also, your email solution must support basic authentication.

Procedure

When the prerequisites are met, every user can configure for themselves in their profile settings in SAP Cloud
ALM if and for which of these notification types they want to receive emails.

Setup and Administration for SAP Cloud ALM

60 PUBLIC Integration and Configuration Options
  Note

Only those types are available for configuration that are relevant for the user, meaning where they've
received notifications in the past. If you were never assigned to a task, for example, you won’t see that
specific notification type in your settings and cannot check the email flag for this notification type. Whereas
the in-app notification is active by default, the email works on an opt-in basis.

After the configuration, the user will receive the corresponding email notifications. The email contains all
relevant information for the notification, and a link to the corresponding application in SAP Cloud ALM to
process the issue.

8.4 Integrating SAP Central Business Configuration

By integrating SAP Central Business Configuration with SAP Cloud ALM, you can import roadmap content into
the Tasks app. This helps you understand the order in which the tasks need to be executed, and allows you to
navigate directly to SAP Central Business Configuration as needed.

SAP Central Business Configuration is a solution that supports the configuration of SAP S/4HANA Cloud.

While an SAP Cloud ALM project applies the SAP Activate methodology to provide end-to-end procedural
guidance on how to start and execute an implementation project, an SAP Central Business Configuration
project shows the project and configuration activities focused on your specific business configuration.

To use SAP Central Business Configuration in SAP Cloud ALM, you first need to carry out the following setup
procedure.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 61
Procedure

Technical Setup
Create an endpoint for SAP Central Business Configuration by carrying out the following steps:

1. In the SAP Cloud ALM launchpad, open the Landscape Management app.
2. In the  Select a Scope dialog, make sure that the service SAP Central Business Configuration is selected.
3. On the Services & Systems page, use the search or filter options to find your SAP Central Business
Configuration service and open it.
4. Under Endpoints, choose Create Endpoint Automatically.

Please note that you can maintain only one service and one endpoint for the integration of SAP Central
Business Configuration.

Integration During Project Creation

After you've completed the technical setup, select SAP Central Business Configuration as an integration
scenario by carrying out the following steps:

1. In the SAP Cloud ALM launchpad, open the Projects and Setup app.
2. To create a new project, choose Create.
3. Enter the following parameters:
• Project: Enter a project name of your choosing, such as Implementation Project.
• SAP Activate Roadmap: Select the desired roadmap.
• Access Level: Select an access level for your project.
• Status: Select On Track.
• Current Phase: Select Prepare.
• Scenario: Select SAP Central Business Configuration.

4. Select the SAP Central Business Configuration project or projects that you want to connect to SAP Cloud
ALM.

Setup and Administration for SAP Cloud ALM

62 PUBLIC Integration and Configuration Options
 You can unassign SAP Central Business Configuration projects from the corresponding SAP Cloud ALM
project at any time.
5. Save the new project.

After saving the new project, you can navigate to your SAP Central Business Configuration project with the
direct links in the table or via the respective tasks.

Related Information

SAP Central Business Configuration – SAP Help Portal

Integrating SAP Cloud ALM with SAP Central Business Configuration – SAP Community

8.5 Configuring Project User Permissions

Project user authorizations are defined by the project access levels, the roles users are assigned to in the user
management, and the roles users are assigned to in project management.

In the Projects and Setup app, three access levels can be determined in a project:

• Public: This project is publicly accessible by all users with project management authorizations.
• Restricted: This project is restricted and only project members can make changes within the project
(display for non-project-members allowed).
• Private: This project is private and can only be accessed by project members (display for non-project-
members not allowed).

 Note

When a project is created, the access level is set to Restricted by default. This can be changed later.

Within each access level, the combination of role assignments in User Management and the team assignment
in a project defines the project permissions for a user.

In User Management, the following roles are available:

• Project Administrator: Manage projects, deployment plans, tasks, scopes, requirements, features, notes,
test cases, defects, and tags
• Project Lead: Manage projects, deployment plans, tasks, scopes, requirements, features, notes, test cases,
and defects
• Project Member: View projects and deployment plans. Manage tasks, scopes, requirements, features (with
restrictions ), notes, test cases, and defects
• Project Viewer: View projects, deployment plans, tasks, scopes, requirements, features, notes, test cases,
and defects

In the Projects and Setup app, users can be assigned to teams based on numerous roles, such as Project
Lead, Analytics Expert, Business Process Expert. As soon as a user is assigned, a request is triggered in User
Management to assign the user to the respective role collection.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 63
Please refer to the below table to get detailed information.

The first column of the table shows the three access levels that can be determined during project setup in
the Projects and Setup app. The second column shows the team assignment type. The rest of the columns
shows the different roles a user can be assigned to in the User Management app. In the table legend, the
different authorizations are defined that result from the user assignments and project access level settings in
the different apps.

When you set the access level for a project to Public, user authorizations are only affected by the roles that
are assigned in User Management. This is not the case for the access levels Restricted and Private. Here, user
authorizations are both affected by the roles that are assigned in User Management and the team assignments
made in the Projects and Setup app.

 Note

Any authorization changes to projects or assignments to projects or teams only apply to the individual
users after they have logged out of SAP Cloud ALM.

Setup and Administration for SAP Cloud ALM

64 PUBLIC Integration and Configuration Options
8.6 Integrating the Cloud Integration Automation Service
The Cloud Integration Automation service provides you with a guided workflow to integrate SAP cloud
solutions to on-premise and other SAP cloud solutions. The guided workflow contains instructions for manual
and automated tasks to enable an easy and quick integration configuration setup.

Prerequisites

• You have a subscription to the Cloud Integration Automation service.

When your SAP Cloud ALM tenant was requested, a subscription to the Cloud Integration Automation
service was automatically created in your SAP Cloud ALM subaccount.
• Your user in SAP Cloud ALM has the role Global Administrator or User Administrator.

Procedure

1. From the SAP Cloud ALM launchpad, open the User Management app.
2. To go to the user list, choose  (Users).
3. Select the user to whom you want to assign the Cloud Integration Automation roles.
4. Choose Edit.
5. Under Cloud Integration Automation Service, select one of the following roles:
• Cloud Integration Administrator
• Cloud Integration Expert
• Cloud Integration Viewer

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 65
 For more information on the Cloud Integration Automation roles, their corresponding role collections, and
their respective privileges, refer to the section Pre-Defined Roles in Assigning Roles to the Users.
For more information on role assignments in SAP Cloud ALM, refer to Step 2: Assign Roles to Users in SAP
Cloud ALM [page 32].
6. Save your settings.
7. Follow the steps described in the blog post Start a scenario integration workflow with Cloud Integration
Automation Service on Cloud Foundry (BTP) .
8. To configure the integration, access the application and execute the Cloud Integration Automation
procedure.

Related Information

Cloud Integration Automation Service – SAP Help Portal

8.7 Enabling Transport Management

You can enable transport management of different transport environments for SAP Cloud ALM.

In this section, you can find the setup steps for the enablement of the transport management for different
transport environments in SAP Cloud ALM.

8.7.1 SAP S/4HANA Cloud with Adaptation Transport

Organizer (ATO)

Enable the transport management with Adaptation Transport Organu

By enabling the transport management for SAP S/4HANA Cloud with the Adaptation Transport Organizer
(ATO), you can keep track of the deployment of transport requests through your implementation landscape.

 Note

Only released transports can be be assigned to features. For more information please check the following
documentation: https://help.sap.com/docs/cloud-alm/applicationhelp/integration-of-deployment-tools

In order to use the ATO for SAP S/4HANA Cloud in an SAP Cloud ALM environment, you have to establish a
connection between SAP Cloud ALM and the ATO.

Setup and Administration for SAP Cloud ALM

66 PUBLIC Integration and Configuration Options
Procedure

1. Retrieve SAP Cloud ALM API credentials as described in Enabling SAP Cloud ALM API [page 45].
Depending on the provisioning date of your SAP Cloud ALM tenant, the creation and configuration of your
entitlements in the subaccount containing your SAP Cloud ALM subscription is generated automatically or
has to be adjusted manually:
• On or after 2023-10-16: A service binding was generated automatically. You can skip the steps in the
linked guide altogether and access your service binding in the SAP BTP cockpit or in the Landscape
Management app, as described in Managing Your Service Key [page 57]
• Between 2023-06-12 and 2023-10-16: You only need to carry out the steps in the linked guide if you
want to set up transport management, but you no longer have to configure your entitlements.

 Note

If you've already set up an instance previously, it's recommended to set up a new instance with a
new name including the respective scopes. If the new instance works and the old one isn't needed
anymore, you can delete the old instance.

The procedure for deleting an instance is described here: Deleting Service Instances.

• Before 2023-06-12: No service binding has been created as part of initial provisioning. To create one
manually, carry out the steps listed in Enabling SAP Cloud ALM API [page 45].

 Note

For background information about communication systems in SAP S/4HANA Cloud context, please
have a look at Communication Management

2. Create communication system: Create a communication system using the Communication System app
that represents the SAP Cloud ALM tenant you want to communicate with.

 Note

The following steps have to be performed for every tenant you want to establish.

1. In the Communication Systems app, set up a new communication system by choosing New.
Set up a communication system using any ID in the System ID field and with a reasonable name (for
example the tenant name, you want to communicate with) in the System Name field.

2. Choose Create.
3. In the next view, add the root URL from the SAP Cloud ALM API (see step 1 of this guide) in the Host
Name field and the port (443) into the Port field in the Technical Data - General section.
The relevant entry for the host name is the following: { “endpoints”: { “Api” . https://
eu10.alm.cloud.sap/api }. Enter the URL without the /api extension at the end.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 67
 4. Add a token URL based on the UAA url from your SAP Cloud ALM API instance in the Token Endpoint
field and add /oauth/token at the end of the URL.
The token URL in the service key JSON file looks like that: "url": "https://tenant-
name.authentication.eu10.hana.ondemand.com"

5. To create a new outbound user, go to the Users for Outbound Communication section of the
Communication Systems app and choose  .

6. Choose Oauth 2.0 in the Authentication Method dropdown and enter your credentials based on client
ID and secret from your SAP Cloud ALM API instance in the OAuth 2.0 Client ID and Client Secret fields.
You can find the client ID and secret in the UAA section of the service key JSON and has a structure like
in the following examples: "clientid": "instance-name!b123456|sapcloudalm!b456789"
and "clientsecret": "asdfasdfasdfasdfasdfasdf".

Setup and Administration for SAP Cloud ALM

68 PUBLIC Integration and Configuration Options
 7. Choose Create.
The entry now looks like this:

8. Choose Save.
3. Create a communication arrangement:
1. Create a communication arrangement in the Communication Arrangement app based on scenario
SAP_COM_0690 and use the system that was created in step 2 of this guide.

2. Go to the Outbound Services section in the Communication Arrangement app. In this section you can
find the following four outbound services.
• SAP Cloud ALM for implementation - Deployment Management Export
• SAP Cloud ALM for implementation - Deployment Management Import
• SAP Cloud ALM for implementation - Deployment Management Retry
• SAP Cloud ALM for implementation - Deployment Management Status Change
In each of this outbound services, the same entries have to be filled out by you.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 69
 Make sure that the Service Status is marked as Active and that the Port entry is filled out with 443.
In the Job Execution Details section, the Job Status doesn't have to be checked as this will be
scheduled automatically in the background. Enter 5 minutes in the Run Every field.
The Package Size entry can be ignored.
3. Choose Save.

Information About Available Outbound Services

The following list contains the outbound services that are currently available:

• Export: This outbound scenario reacts to exported ATO collection versions

• Import: This service notifies SAP Cloud ALM about imports that were performed by ATO
• Retry: Retries failed communication between ATO and SAP Cloud ALM
• Status Change: This service reacts to ATO status changes and sends these changes to SAP Cloud ALM

 Note

The collector jobs can only react to future events once they are activated. Past actions before the activation
are not collected.

Reporting Incidents

If you encounter issues while using this app, open  (Built-In Support) to find helpful resources and context-
sensitive information, and to chat with SAP experts. You can also book a live session with the Schedule an
Expert function in SAP for Me.

Create incidents for the Features app in SAP for Me , under component SV-CLM-IMP-FTR .

Setup and Administration for SAP Cloud ALM

70 PUBLIC Integration and Configuration Options
8.7.2 SAP S/4HANA Cloud, Private Edition and On-Premise
Systems
By enabling the transport management for SAP S/4HANA Cloud, private edition, and SAP NetWeaver
Application Server for ABAP on-premise, you can orchestrate the deployment of transport requests through
your implementation landscape.

To use the Change and Transport System (CTS) for SAP S/4HANA Cloud, private edition, and SAP
NetWeaver Application Server for ABAP on-premise in an SAP Cloud ALM environment, you've to establish a
connection between SAP Cloud ALM and the (CTS).

 Caution

Transport-related data is pushed to SAP Cloud ALM from your managed systems by setting up the
integration. This includes data of the transport owner.

Technical Prerequisites

For the Transport Management System (TMS) Setup

Currently supported landscapes:

• Any kind of consistent Transport Management System (TMS) landscape. The last system in a track will
always be treated as a production system.
• Client-specific transport routes (TMS option CTC) are strongly recommended.
• TMS transport groups are supported.

 Caution

If you want to implement landscape changes, please note the following information:

• Adding new systems to a track is supported as long as no consolidation routes are changed. Mind, that
you need to adjust the transport buffers manually.
• Refreshing a (test) system is supported if the system ID stays the same. This still means, the transport
buffers and imports need to be adjusted manually.
• Changing delivery routes is partly supported. This means, the transport buffers need to be adjusted
manually and removed systems are still reported on in the feature traceability.
• Deleting a system from a track is partly supported. This means, the transport buffers need to be
adjusted manually and the deleted system is still reported on in the feature traceability.
• Changing or deleting export targets is not supported.
• Switching on or off client specific transport routes is not supported.

If you need to perform unsupported changes of the transport configuration in the Transport Management
System (TMS), make sure that all open features and transports are completed and deployed to the production
system. Therefore, the transport buffers should be empty.

 Tip

We strongly recommend using always client-dependent transport routes (TMS option CTC) from the
very beginning. By using client-dependent transport routes, you can always enhance your landscape with

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 71
 additional clients. Turning on client-dependent transport routes at a later point in time is a complete
landscape change that isn't supported while there are still transports open.

We strongly recommend using a transport target group as consolidation target. By using the transport
target group, you can always change your consolidation systems by just changing the systems within the
consolidation target group while technically the consolidation target (which is the consolation target group)
stays stable.

For the ABAP System

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).

• For ST-PI 740 SP 23, install 3310406 and follow SAP Note 3322679 .

 Note

It's recommended to use SP23.

• For ST-PI 740 SP 22, install 3310406 and follow SAP Note 3322679 .
• For ST-PI 740 SP 21, install corrections 3240966 and follow SAP Note 3322679 .
• For ST-PI 740 SP 20, install corrections 3240966 and follow SAP Note 3322679 .
• For ST-PI 740 SP 19, install corrections 3196078 and follow SAP Note 3322679 .
• For ST-PI 740 SP 18, install corrections 3196078 and follow SAP Note 3322679 .
It's recommended to install the current version of collective corrections.
• Check that the profile parameter icm/HTTPS/client_sni_enabled is set to TRUE, as described in SAP
Note 510007 .

 Note

For the profile parameter check, you can use the transaction RZ11 in the managed system.

• Check that profile parameter ssl/client_ciphersuites is set according to section 7 of SAP Note
510007 .
• Make sure that the following certificates are imported in STRUST under SSL Client (Anonymous) and
SSL Client (Standard):
• DigiCertGlobalRootCA
• DigiCertGlobalRootG2
• DigiCertRSA4096RootG5

Setup and Administration for SAP Cloud ALM

72 PUBLIC Integration and Configuration Options
Required Authorizations

You need to consider two users in the managed ABAP system for the setup.

Note that the authorization steps are only needed for system client 000. For other clients, these steps can't be
performed.

• To run transaction /SDF/ALM_SETUP, the user needs the PFCG role SAP_SDF_ALM_SETUP.

 Note

In this role, you need to maintain the authorization field S_BTCH_NAM > BTCUNAME either with '*' or
with the user name of the user that you plan to use for the data collection background job.

• The user you specify as background user requires the PFCG role SAP_SDF_ALM_METRIC_PUSH_FND and
the role SAP_BC_TRANSPORT_ADMINISTRATOR.

 Note

Don't forget to activate role SAP_BC_TRANSPORT_ADMINISTRATOR before using it with the

background user.

Download the latest version of the role SAP_SDF_ALM_METRIC_PUSH_FND from SAP Note 3104662 .

Procedure

Create a Space and Configure Entitlements

Configuration of the PUSH Data Provider
As a first step, retrieve SAP Cloud ALM API credentials as described in Enabling SAP Cloud ALM API [page 45].

Depending on the provisioning date of your SAP Cloud ALM tenant, the creation and configuration of your
entitlements in the subaccount containing your SAP Cloud ALM subscription is generated automatically or has
to be adjusted manually:

• On or after 2023-10-16: A service binding was generated automatically. You can skip the steps in the linked
guide altogether and access your service binding in the SAP BTP cockpit or in the Landscape Management
app, as described in Managing Your Service Key [page 57]
• Between 2023-06-12 and 2023-10-16: You only need to carry out the steps in the linked guide if you want to
set up transport management, but you no longer have to configure your entitlements.

 Note

If you've already set up an instance previously, it's recommended to set up a new instance with a new
name including the respective scopes. If the new instance works and the old one isn't needed anymore,
you can delete the old instance.

The procedure for deleting an instance is described here: Deleting Service Instances.

• Before 2023-06-12: No service binding has been created as part of initial provisioning. To create one
manually, carry out the steps listed in Enabling SAP Cloud ALM API [page 45].

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 73
The configuration of the push data provider is needed to enable the processing of batch jobs. These batch jobs
are then scheduled to send and receive data as well as tasks that are needed for the processing of transport
jobs.

1. Log on to ABAP system client 000.

 Note

Step 1 has to be performed for each system that has to be connected.

2. Start transaction /n/SDF/ALM_SETUP.

If you start the transaction for the first time, it looks like this:

3. Target ALM Destination

1. To create a new SAP Cloud ALM Destination, enter a name (for example SAP Cloud ALM) and
confirm your input with the Enter key.
2. To change an existing SAP Cloud ALM destination, select one from the F4 input help and press
Enter .
3. Press Enter . The subsequent fields are filled out automatically.
4. Maintain HTTP Destination
1. Choose Update Destination.
2. Copy the content of the JSON file you've created in the Create a Service Key section. Choose Paste
Service Keys and paste it into the text field popup.

 Note

Alternatively, you can enter the required fields for SAP Cloud ALM manually:
1. Token Endpoint: Enter the SAP Cloud ALM OAuth URL, following the pattern url + /oauth/
token.
Example: calm-tenant.authentication.eu10.hana.ondemand.com/oauth/token
2. Client ID: Enter SAP Cloud ALM client ID.

Setup and Administration for SAP Cloud ALM

74 PUBLIC Integration and Configuration Options
 3. Client Secret: Enter SAP Cloud ALM client secret.
4. Proxy User (if necessary)
5. Proxy Password (if necessary)
6. Proxy Host (if required by your network infrastructure. For SAP S/4HANA Cloud, private
edition, enter value: proxy)
7. Proxy Port (if required by your network infrastructure. For SAP S/4HANA Cloud, private
edition, enter value: 3128)

3. Choose Continue. The destination is now updated.

4. Choose Continue. A success message appears if the connection was established.
5. Enter Registration Target
1. If the Target ALM Root URL field isn't already prefilled, enter the target SAP Cloud ALM root URL
depending on your region, for example https://eu20.alm.cloud.sap.
This is the URL that is shown in the JSON file during the creation of the service key. The URL
is shown under endpoints.API or uaa.url respectively. The SAP Cloud ALM root URL depends on
the region of the customer account was created under, for example eu10.alm.cloud.sap or
eu20.alm.cloud.sap.
2. Enter the background user that you created to perform the data collection.
3. Choose Register to call SAP Cloud ALM and register the system.
4. Choose Continue.
An LMS ID is retrieved and displayed.

 Note

To unregister a system, choose Unregister.

This stops all data collection and heartbeat measurements.

6. Select the use cases that you want to collect and push data for. The push mechanism supports the
following use cases:
• For development systems: Feature Deployment: Manage Transports
• For a domain controller system: Feature Deployment: Read Landscape
• All other systems (test or production): Feature Deployment: Import Transports

 Tip

Further information about activating use cases:

Feature Deployment: Read Landscape

• Reports the STMS landscape configuration to SAP Cloud ALM.
• It's only necessary to set up on one system per domain (that is the domain controller). A domain
controller is mandatory for the TMS. Using the same domain controller to connect to SAP Cloud
ALM is optional.

Feature Deployment: Manage Transports

• Reports transport requests to SAP Cloud ALM for assignment to features.
• It's only necessary to set up on source systems, specifically DEV systems.

Feature Deployment: Import Transports

• Queries the requests that are to be imported from SAP Cloud ALM and triggers the import job.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 75
 • Only needs to be set up on consolidation and target systems for import (that is, QA and PRD
systems).

 Note

Commonly, authorization-checks are performed in the system where a change happens. For Features
app, this app takes over the authorization check for importing transports in the SAP Cloud ALM
environment instead of the managed system. In the managed system, the user you specified as
background user for the data collection performs the transport actions. Since this background user
has transport authorization by definition, the distinct check whether a specific end user is allowed to
perform a transport operation is done in SAP Cloud ALM.

7. Choose Continue.
8. If everything is set up correctly, it looks like this:

Configuration of Client-Dependent Use Cases

The following client-dependent use cases are available to you:

• Create transports
• Delete empty transports
• Release transports
• Transport of copies

Relevant Jobs in Managed Systems

There are important jobs to be executed in the managed systems. The jobs mentioned below should be at least
released, but always check for scheduled and active jobs in case of issues.

To create and release transports as well as creating transport of copies, for example in client 100 of the
development system use the following transaction: /SDF/CALM_CDM_TR_PROC_CL_DEP-100

 Note

The job /SDF/CALM_CDM_DIAGNOSTICS pushes data about the available capabilities in the managed
system ST-PI to SAP Cloud ALM.

Setup and Administration for SAP Cloud ALM

76 PUBLIC Integration and Configuration Options
 This job is supposed to be released and executed once per day and client.

For the import of transports there is a job executed in each target system client 000: /SDF/
CALM_CDM_IMPORT_TRANSPORTS

To enable the use cases mentioned above within an SAP Cloud ALM feature, execute the following setup in
each development client that you want to use:

 Note

Before you start with the setup, please make sure that you've performed all the configuration steps in the
Technical Prerequisites for the ABAP System section of this guide. Additionally, make sure that you've
implemented the current version of the SAP Note. Currently it's 3322679 .

Also make sure that setup for client 000 was already performed and that the use case Feature
Deployment: Manage Transports was already activated.

1. Log on to the respective ABAP system client and start transaction /n/SDF/ALM_SETUP.
2. You can reuse the SAP Cloud ALM destination from your PUSH data configuration.
At the start of the process, the transaction looks like this:

3. Under Maintain HTTP Destination, choose Update Destination and paste the JSON file you've already
created in the Configuration of the PUSH Data Provider section of this guide.
4. Under Enter Background User and Register System, choose Unregister.
5. Enter the background user you've created to perform the data collection.
6. Choose Register to call SAP Cloud ALM and register the system. Confirm the scheduling of the respective
jobs.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 77
 If it’s successful, an LMS ID is retrieved and is displayed.
7. Select the use case you want to activate:
Feature Deployment: Manage Transport per Client
• Queries to-be-released transport requests from SAP Cloud ALM and triggers the release job.
• It's necessary to execute this setup on all development clients you use for customizing activities.
8. If everything is set up correctly, it looks like this:

Configuration of the Transport Organizer Web UI

Before you can start using the navigation to the transport organizer for CTS managed transports by using the
transport id in the Features app, you have to activate the web-service for transport organizer web ui.

Setup and Administration for SAP Cloud ALM

78 PUBLIC Integration and Configuration Options
Please follow the steps in the Activating the Web Service for Transport Organizer Web UI documentation.

 Note

If the transport organizer web ui is throwing exceptions, check the following:

• Make sure that you've configured the start authorization according the following notes: 1413011
and/or 3064888 respectively.
• Check the HTTP_WHITELIST 0002578665 and the UCON_CHW allowlist 0003290787 .

Reporting Incidents

If you encounter issues while using this app, open  (Built-In Support) to find helpful resources and context-
sensitive information, and to chat with SAP experts. You can also book a live session with the Schedule an
Expert function in SAP for Me.

Create incidents for the Features app in SAP for Me , under component SV-CLM-IMP-FTR .

8.7.3 SAP Cloud Transport Management Service

By enabling the transport management for the SAP Cloud Transport Management service, you can orchestrate
the deployment of transport requests through your implementation landscape.

SAP Cloud Transport Management is automatically subscribed in your SAP Cloud ALM BTP subaccount. Only
this subscription can be used for the integration with SAP Cloud ALM.

To use the transport capabilities of SAP Cloud ALM in conjunction with the SAP Cloud Transport Management
service, you first have to establish a connection between them.

 Note

SAP Cloud ALM supports the parallel delivery of several nodes at once.

Before you can use the deployment functionality in SAP Cloud ALM, you have to configure the nodes in the
SAP Cloud Transport Management service.

Prerequisites

• You've set up the product (for example, SAP Integration Suite) with which you want to integrate the SAP
Cloud Transport Management service for SAP Cloud ALM.
For more information about the general setup, refer to Initial Setup of SAP Cloud Integration in the Cloud
Foundry Environment.
• You've familiarized yourself with how to use the SAP Business Technology Platform (SAP BTP) cockpit, in
particular Account Administration concepts.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 79
• You're subscribed to the SAP Cloud Transport Management service and your user has the required
transport management roles Transport Management Viewer and Transport Management Operator.

Procedure

1. Set Up the Product

Set up the specific use case according to the respective documentation, for example Enabling Content
Transport, Cloud Foundry Environment.
2. Set Up an SAP Cloud ALM API Instance
Set up the SAP Cloud ALM API instance and the Change and Deployment display and the scope
management by performing the steps described in Enabling SAP Cloud ALM API [page 45].
3. Set Up HTTP Destinations and Transport Routes with SAP Cloud ALM Pass-Through

 Note

The following steps apply only to the SAP Integration Suite. For other integrations, refer to the relevant
documentation.

The product requires a destination to the SAP Cloud Transport Management service. In the SAP BTP
subaccount where your source product tenant is hosted, create a destination targeted at the SAP Cloud
Transport Management service.
In the Destination Configuration section, enter the values in the respective fields based on the description
that is provided in the following table:

Destination Configuration Values

Field Description

Name TransportManagementService (this value is case-sen-

sitive)

Type HTTP

Description (optional) You can provide a description for your reference.

URL Enter the URL (“Api”) of the service key of your

SAP Cloud ALM API instance and append /imp-cdm-
transport-management-api/v1. That follows a pat-
tern like this: https://eu10.alm.cloud.sap/api/imp-cdm-
transport-management-api/v1

Proxy Type Internet

Authentication OAuth2ClientCredentials

Client ID clientid from the service key of your SAP Cloud ALM
API instance.

Setup and Administration for SAP Cloud ALM

80 PUBLIC Integration and Configuration Options
 Field Description

Client Secret clientsecret from the service key of your SAP Cloud
ALM API instance.

Token Service URL Enter the value of the url (uaa section) from the service
key of your SAP Cloud ALM API instance. Append /oauth/
token at the end of URL fetched from the service key.

Additional Properties Choose New Property.

Enter sourceSystemId (this value is case-sensitive) as

the key and provide a value of your choice. Reuse the
same value as the name of the source transport node in a
later step.

Additional information about how to set up the HTTP destination, please have a look at the following
information: Creating HTTP Destinations and Transport Route Go to the Cloud Transport Management tab.
In the URL section for the endpoint, enter the URL of your SAP Cloud ALM API instance
that follows the pattern https://<tenant name>.<region>.alm.cloud.sap/api/imp-cdm-
transport-management-api/v1. The first part of the URL until /api depends on your company
account and is variable.

Special Setup Cases with SAP Business Technology Platform (SAP BTP) and
Continuous Integration and Delivery (CI/CD)

1. If you work with a SAP Business Technology Platform (SAP BTP) product (for example CPI), then just
create a three system landscape in the Cloud Transport Management service (cTMS) as described in the
standard documentation above. Your development is already available in the DEVELOPMENT system, so
your transports are exported from the DEVELOPMENT system and imported into the buffer of the follow-up
system TEST.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 81
2. For other developments outside of SAP BTP, like Business Application Studio, there is no dedicated cloud
development system. In this case, the developments are performed in the Business Application Studio.
Your developments then are uploaded with the upload command through the Continuous Integration
and Delivery (CI/CD) service directly into the TEST system. In order to support this scenario, you need
a dummy node before your test node. Your developments aren't deployed in this dummy DEVELOPMENT
node, but this node is needed in order to support this scenario. You can still deploy, but then as a pure
sandbox deployment through a pipeline directly without cTMS.

For the initial setup of SAP Continuous Integration and Delivery (CI/CD), please follow
the guide https://help.sap.com/docs/continuous-integration-and-delivery/sap-continuous-integration-and-
delivery/initial-setup?version=Cloud

To integrate cTMS into your CI/CD pipeline please

follow this documentation: https://help.sap.com/docs/continuous-integration-and-delivery/sap-

Setup and Administration for SAP Cloud ALM

82 PUBLIC Integration and Configuration Options
continuous-integration-and-delivery/configure-sap-fiori-in-cloud-foundry-environment-job-in-your-repository?
version=Cloud#(optional)-integrate-sap-cloud-transport-management-into-your-pipeline

To create the nodes in the cTMS in this context, please follow the documentation https://help.sap.com/docs/
cloud-transport-management/sap-cloud-transport-management/create-transport-nodes, especially steps 1
and 2.

Reporting Incidents

If you encounter issues while using this app, open  (Built-In Support) to find helpful resources and context-
sensitive information, and to chat with SAP experts. You can also book a live session with the Schedule an
Expert function in SAP for Me.

Create incidents for the Features app in SAP for Me , under component SV-CLM-IMP-FTR .

8.7.4 Tips and Troubleshooting for Your Setups

Find information how to fix issues.

In this section, you can find information about how to fix issues you may encounter during the setup for the
enablement of the transport management for different transport environments in SAP Cloud ALM.

8.7.4.1 Tips and Troubleshooting for SAP S/4HANA Cloud,

Private Edition and On-Premise Systems

Issues and Solutions

In this document, you can find answers to some of the most common questions and issues that may arise
during the setup of the transport management of SAP S/4HANA Cloud, private edition or SAP NetWeaver
Application Server for ABAP on-premise.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 83
Issue Solution

I can't create transports Go to the managed system:

1. Check if the service key is missing the auth scopes.

If it's missing, please follow the steps from step 4 (Main-
tain HTTP Destination) on in the Procedure section of
the SAP S/4HANA Cloud, Private Edition and On-Prem-
ise Systems guide.
2. Check if the use case Feature Deployment: Manage
Transports per Client is active in the export tenant
(working client shouldn't be 000).
3. Check if the job /SDF/
CALM_CDM_TR_PROC_CL_DEP-100 is released and is
running frequently in the export tenant.
4. Check if the job /SDF/CALM_CDM_DIAGNOSTICS is
running in development system client 000.

In SAP Cloud ALM check the following:

Export tenant is in the system group and is assigned to the

project through the deployment plan.

I can't release transports Go to the managed system:

1. Check if the service key is missing the auth scopes.

2. Check if the use case Feature Deployment: Manage
Transports per Client is active in the export tenant
(working client shouldn't be 000).
3. Check if the job /SDF/
CALM_CDM_TR_PROC_CL_DEP-100 is released and is
running frequently in the export tenant.
4. Check if the job /SDF/CALM_CDM_DIAGNOSTICS is
running in development system client 000.

I can't create Transport of Copies Go to the managed system:

1. Check if the service key is missing auth scopes.

2. Check if the use case Feature Deployment: Manage
Transports per Client active in the export tenant(work-
ing client shouldn't be 000).
3. Check if the job /SDF/
CALM_CDM_TR_PROC_CL_DEP-100 is released / and
is running frequently in the export tenant.
4. Check if the job /SDF/CALM_CDM_DIAGNOSTICS is
running in development system client 000.

Setup and Administration for SAP Cloud ALM

84 PUBLIC Integration and Configuration Options
 Issue Solution

I can't deploy features Go to the managed system:

1. Check if the service key is missing auth scopes.

2. Check if the use case Feature Deployment: Import
Transports active in target system client 000
3. Check if the job /SDF/CALM_CDM_IMPORT_TRANS-
PORTS is released and running .

I can't assign transports Go to the managed system:

1. Check if the service key is missing auth scopes.

2. Check if the use case Feature Deployment: Manage
Transports is active in development client 000.

My import jobs are stuck Go to the managed system:

1. The job /SDF/CALM_CDM_IMPORT_TRANSPORTS is

released and running.
2. The job log of /SDF/CALM_CDM_IMPORT_TRANS-
PORTS shows a component version mismatch. In case
several features are deployed together, all the trans-
ports assigned are imported as an import subset. If
one transport request of the subset leads to a compo-
nent mismatch situation, the import of all transports is
blocked.

To resolve the mismatch issue refer to the following SAP

Note:1688610

How to Deal With Connection Issues

If you encounter connection issues during the setup of the transport management of SAP S/4HANA Cloud,
private edition or SAP NetWeaver Application Server for ABAP on-premise, you can perform the respective
steps below to solve the connection issues.

Troubleshooting Steps

1. Connection Check Report

1. To check whether your connection is established properly, execute the program /SDF/
CALM_CDM_CONN_DIAGNOSTIC in client 000 and all working clients of all managed systems you want
to connect to SAP Cloud ALM.
Additionally, you can use transaction /SDF/ALM_DIAGNOSTIC to execute the checks.
2. Here, you choose the SAP Cloud ALM destination used for the connection to your SAP Cloud ALM
tenant. Then, you can execute the report with the defaulted options.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 85
 3. After you've performed the previous step, check the result.
4. The token was reset. This means that the latest configuration is applied.
Token scopes must contain the following entries:
• imp-cdm-feature-manage-ui
• imp-cdm-feature-display-ui

If that’s not the case, you need to update the SAP Cloud ALM API instance with the corresponding
scope described here: Enabling SAP Cloud ALM API [page 45]
5. The following use cases must be active:
• Feature Deployment: Read Transport Landscape: CALM_CDM_TMS_LNDSCP to synchronize the
transport landscape from TMS - in the domain controller client 000.

Setup and Administration for SAP Cloud ALM

86 PUBLIC Integration and Configuration Options
 • Feature Deployment: Manage Transports: CALM_CDM_TMS for managing transports (mainly to
assign existing transport requests) - in the development system client 000.
• Feature Deployment: Import Transports: CALM_CDM_TMS_IMPORT for importing transports - in all
target systems client 000.

 Note

If development clients are supposed to be supplied with changes, you must activate the use
case there as well.

• Feature Deployment: Manage Transport per Client:CALM_CDM_TMS_CLI_DEP to create and release

transports and to create transport of copies. This is true for all development clients.

 Note

A typical 3-tier looks like that:

• Transport route: O11.100 –> O12.100 –> O13.100
• Domain controller: O11

The following table shows the different use cases per client.

Use Case Available per Client

Use Case / Client O11 .000 O11.100 O12.000 O13.000

Feature Deploy- Active

ment: Manage
Transport per Client

Feature Deploy- Active Active

ment: Import Trans-
ports

Feature Deploy- Active

ment: Read Trans-
port Landscape

Feature Deploy- Active

ment: Manage
Transports

6. The result of the connection check should provide a table of active use cases:

The Message column provides information about the last execution. In case you find an error message,
check the chapter application logs in this section of this guide for further investigation steps.
7. The batch user must have the following roles (or copied ones with the same authorizations):
1. SAP_BC_TRANSPORT_ADMINISTRATOR
2. SAP_SDF_ALM_METRIC_PUSH_FND

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 87
 8. In the Installed Components table, you must check SAP_BASIS and ST-PI levels. The prerequisites are
SAP_BASIS 7.40 SP20 or higher (accordingly 7.50 SP04) and ST-PI 7.40 SP 18.

 Note

You can find additional details about roles and other prerequisites at the beginning of this guide.

9. In addition, you get an overview of all installed notes related to the integration scenario:

10. Please make sure that all manual steps included in the necessary notes were executed properly.

2. Applications Logs
In case of issues showing up in the table of active use cases of the connection check result (see column
Message) you can check the application log:
1. Go to transaction SLG1 and execute a search for the following objects: Object: /SDF/CALM,
Subobject: BUILD_CDM.
2. Check for errors to collect further information.
3. Relevant Jobs in Managed Systems
There are important jobs to be executed in the managed systems. The jobs mentioned below should be at
least released but always check for scheduled and active jobs in case of issues.
To create and release transports as well as creating transport of copies, for example in client 100 of the
development system use the following transaction: /SDF/CALM_CDM_TR_PROC_CL_DEP-100

Setup and Administration for SAP Cloud ALM

88 PUBLIC Integration and Configuration Options
  Note

The job /SDF/CALM_CDM_DIAGNOSTICS pushes data about the available capabilities in the managed
system ST-PI to SAP Cloud ALM.

This job is supposed to be released and executed once per day and client.

For the import of transports there is a job executed in each target system client 000: /SDF/
CALM_CDM_IMPORT_TRANSPORTS

In case of import issues, you can have a look into the job log.
Sometimes a component version mismatch is detected, and this would block the import of all transports
assigned to features if the mismatch situation is not resolved.

 Note

In case several features are deployed together, all the transports assigned will be imported as import
subset. If one transport request of the subset leads to a component mismatch situation the import of
all transports is blocked.

To resolve this issue please refer to the following SAP Note: 1688610 https://me.sap.com/notes/
0001688610

Please make sure that all manual steps included in the necessary notes were executed properly.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 89
8.8 Integrating Test Automation Providers

In addition to manual testing, which is performed directly in SAP Cloud ALM, you can also integrate SAP and
third-party test automation providers with SAP Cloud ALM.

By integrating automation providers with SAP Cloud ALM, you can reduce your manual testing efforts and take
advantage of its test orchestration, execution monitoring, and reporting capabilities.

8.8.1 Integrating the Test Automation Tool for SAP S/4HANA

Cloud

You can integrate automated test cases from the test automation tool for SAP S/4HANA Cloud for use in test
orchestration in SAP Cloud ALM.

The test automation tool for SAP S/4HANA Cloud is a free automation provider delivered as part of the guided
configuration tools for SAP S/4HANA in SAP Activate. It enables you to test SAP Best Practice processes after
implementation or upgrade of SAP S/4HANA Cloud.

To use this integration in your project, you need to configure a service and an endpoint in the Landscape
Management app in SAP Cloud ALM.

Prerequisites

• You have a Test system for the test automation tool for SAP S/4HANA Cloud.

 Note

Don't connect your SAP S/4HANA Cloud Production system to SAP Cloud ALM. Test cases shouldn't
be tested in production.

• You've set up the app Test Your Processes in the test automation tool for SAP S/4HANA Cloud, as
described here.

Procedure

 Caution

SAP recently revisited the way test automation providers are modeled in the Landscape Management app.

If you've already created a test automation endpoint for the test automation tool for SAP S/4HANA Cloud,
do not change or delete it. It will continue to work. If you delete it and re-create it, it might impact the
existing automated test cases that have been already synchronized with SAP Cloud ALM.

If you want to add a new automation provider, follow the new procedure described below.

Setup and Administration for SAP Cloud ALM

90 PUBLIC Integration and Configuration Options
 1. To communicate with the test automation tool for SAP S/4HANA Cloud, a communication user is
required. If you need to create the communication user, follow the procedure described in Communication
Management. The communication scenario is COM0620.
2. In the SAP Cloud ALM launchpad, open the Landscape Management app.
3. In the  Select a Scope dialog, make sure that the service SAP S/4HANA Cloud is selected.
4. On the Services & Systems page, choose  (Cloud Service Filter) and filter by the service type SAP
S/4HANA Cloud and by the tenant role Test.
The list now displays all SAP S/4HANA Cloud tenants that are currently connected to your SAP Cloud ALM
tenant.
5. Check whether there's an existing service for which the root URL matches the root URL of your test SAP
S/4HANA Cloud system. If so, proceed directly to step 7.
6. If no service exists for your SAP S/4HANA Cloud system, choose Add New Cloud Service and enter
the following parameters:
• Name: Enter a name that follows a naming convention that fits your organization, for example
<Root_URL_S/4> or <S/4_System_SID>.
Please note that spaces and special characters other than hyphens and underscores aren't allowed.
• Description: Enter a short description, such as Test SAP S/4HANA Cloud for <Department, if
relevant>.
• Tenant ID: Enter a meaningful tenant ID for the test automation tool for SAP S/4HANA Cloud that
uniquely identifies the service in the Landscape Management app. This ID can be freely chosen.
• Service Type: Select SAP S/4HANA Cloud.
• Tenant Type: Select Test.
• Root URL: Enter the root URL of your SAP S/4HANA Cloud launchpad, starting with https and ending
with .com or .sap.
• External ID: Leave empty.
• Customer Number: Enter your customer number.
• Customer Name: Enter your customer name.
7. Save the new service.
You can now see it in the list.
8. To create an endpoint, select the service.
9. Under Endpoints, check whether there's an existing endpoint with the use case Test Automation or Test
Management. If so, you can update it by choosing  (Edit).
10. If no endpoint exists for the Test Automation or Test Management use case, choose Add and enter the
following parameters:
• Endpoint Name: Enter a meaningful and unique endpoint name that helps you easily identify the test
automation tool. This name will later be displayed in the test management apps.
• Description: Enter a short endpoint description, such as Endpoint for test automation for
system <SID>. This description will later be displayed in the General Information section of the test
cases.
• Use Case: Select Test Automation.
• Root URL: The root URL of your previously specified service is prefilled. After .com or .sap, add the
suffix /sap/bc/http/sap/sap_calm_testautomation_api/.
The final URL follows the pattern https://<SAP S/4HANA Cloud Root URL>/sap/bc/
http/sap/sap_calm_testautomation_api/.
• Connection Test Path: Leave empty.
If this field is already prefilled, make sure to remove any extra parameters.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 91
 • Authentication Type: Select Basic Authentication.
• User: Enter the communication user.
• Password: Enter the password for the created communication user.
11. Save the new endpoint.

 Note

You can maintain multiple endpoints for test automation. However, we strongly recommend only
maintaining one endpoint per SAP S/4HANA Cloud tenant.

You should maintain two test automation endpoints if you're working with a 3-system landscape setup for
SAP S/4HANA Cloud with two test automation tenants (one for the main line and one for the project line).

Once you've established the connection between SAP Cloud ALM and the test automation tool for SAP S/
4HANA Cloud, a synchronization with the SAP S/4HANA Cloud system takes place to retrieve the existing
automated test cases whenever new processes are scoped in your SAP Cloud ALM projects.

Reporting Incidents

If you encounter issues while using this app, open  (Built-In Support) to find helpful resources and context-
sensitive information, and to chat with SAP experts. You can also book a live session with the Schedule an
Expert function in SAP for Me.

Alternatively, you can create a case in SAP for Me on the component SV-CLM-IMP-TAT.

Related Information

Test Automation Tool for S/4HANA Cloud - Additional Info

Maintain Communication Systems

8.8.2 Setting Up Tricentis Test Automation for SAP

Integrated with SAP Cloud ALM

Tricentis Test Automation for SAP integrated with SAP Cloud ALM is a continuous testing platform that allows
you to design automated, functional, end-to-end software tests across all layers of your enterprise architecture.

By using this integration in your project, you can take advantage of the test orchestration, execution
monitoring, and reporting capabilities of SAP Cloud ALM.

Setup and Administration for SAP Cloud ALM

92 PUBLIC Integration and Configuration Options
Prerequisites

• Your user in SAP Cloud ALM has the role Global Administrator or Project Administrator.
• You have an S-user with the role Edit Cloud Data and an email address that corresponds to the email
address used in SAP Cloud ALM.
You can evaluate valid S-users for your organization in SAP for Me, under Important Contacts .

If you requested SAP Cloud ALM, you've received the authorizations required to set up this integration.

Procedure

1. In the SAP Cloud ALM launchpad, open the app Set Up Tricentis Test Automation for SAP.
2. Read and accept the terms and conditions.
The following information is checked to determine if you meet the prerequisites to accept the terms and
conditions:
• In SAP Cloud ALM:
• The ID of your SAP Cloud ALM tenant
• The customer number for which your SAP Cloud ALM tenant was initially provisioned
• The email address of the current user
• In the SAP Support Portal back end:
• Valid S-users for the given customer number
• S-users with an email address that corresponds to the email address used by the current SAP
Cloud ALM user
• S-users with the role Edit Cloud Data
If one or more such S-users are found, you can give consent. If your user does not meet these criteria,
take a look at Important Contacts to identify a user who is authorized to accept the terms and
conditions.

 Tip

The terms and conditions are stored on SAP Support Portal. You can read or download them from there
at any time.

3. To start the automated setup, choose Set Up Tricentis Test Automation for SAP integrated with SAP Cloud
ALM.

 Caution

The automated setup can only be performed if the following prerequisites are met:
• You're using a standard SAP identity provider.
• You haven't changed the hierarchy of the SAP Cloud ALM application in the identity provider.
During the automated setup, the Tricentis application in the identity provider is created as a child
application to the SAP Cloud ALM application. If your SAP Cloud ALM application was changed to
be a child application of another application, the automated setup can't be completed because it's
not possible to create a child application for a child application.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 93
 If any of these prerequisites aren't met, please open an incident under component SV-CLM-IMP-TM
with the title Request manual provisioning of Tricentis test automation for SAP tenant after you've
accepted the terms and conditions.

In the incident description, please provide the URL of your SAP Cloud ALM tenant along with
information about your identity provider type and/or application hierarchy setup.

4. The following setup steps are performed:

• Setup of the Tricentis application
• Provisioning of the Tricentis tenant
• Update of the Tricentis application
• Configuration of the endpoint for the test automation
5. Set up Tricentis execution agents for remote execution, as described in Execution Agents .

You can now start using Tricentis Test Automation for SAP integrated with SAP Cloud ALM from the Test
Preparation app in SAP Cloud ALM. The authoring of test cases happens directly Tricentis Test Automation for
SAP, as described in the Tricentis documentation linked below.

There's no need to create any additional users. Once an SAP Cloud ALM user accesses Tricentis Test
Automation for SAP from SAP Cloud ALM, a user in the tool is automatically created.

Reporting Incidents

If you encounter issues while using this app, open  (Built-In Support) to find helpful resources and context-
sensitive information, and to chat with SAP experts. You can also book a live session with the Schedule an
Expert function in SAP for Me.

Alternatively, you can create a case in SAP for Me on one of the following components:

• For issues while setting up or using the integration with SAP Cloud ALM, use the component SV-CLM-IMP-
TAT.
• For issues with the test automation tool itself, use the component XX-PART-TRI-TTA-CLD.

Related Information

SAP Help Portal – Tricentis Test Automation for SAP integrated with SAP Cloud ALM
Usage Rights for Tricentis Test Automation for SAP
Tricentis Test Automation for SAP Cloud ALM: Online Help

Setup and Administration for SAP Cloud ALM

94 PUBLIC Integration and Configuration Options
8.9 Enabling Service Delivery

An SAP service is usually delivered as part of a service contract like SAP MaxAttention, SAP ActiveAttention or
SAP Enterprise Support.

Typically, SAP consultants deliver such a service via SAP internal applications. Information required for the
collaboration between SAP and the customer during the delivery of such services and the outcome of these
service deliveries are shared with the customer via a data transfer into the customer's SAP Cloud ALM tenant.

With this data transfer, the following service-related information is sent from SAP to your SAP Cloud ALM
tenant:

• Service details and results

• Preparation tasks, notes, issues, and actions
• Attachments

In addition, SAP synchronizes changes that you make to the following service-related documents from your
SAP Cloud ALM tenant back to SAP:

• Comments and status changes for your preparation tasks, notes, and attachments
• Status changes for issues and actions
If you assign a task or an issue to a user, this assignment information is not replicated from your SAP Cloud
ALM tenant back to SAP.
• Attachments you upload

 Note

All pictures and attachments are stored in a separate SAP-internal storage and don't affect the overall size
of your SAP Cloud ALM tenant.

Activating and Deactivating the Data Transfer

This data transfer is automatically activated when your SAP Cloud ALM tenant was provisioned. If you don't
want service information to be transferred into your SAP Cloud ALM tenant, you can request to deactivate the
data transfer by creating an incident on component SV-CLM-SD. Please provide the following information in the
incident:

• Your customer number

If you have multiple customer numbers, please list all customer numbers for which the data transfer
should be deactivated.
• The URL of the SAP Cloud ALM tenant for which you want to deactivate the data transfer

 Note

Service information that was already transferred to your SAP Cloud ALM tenant is not deleted when the
data transfer is deactivated.

You can reactivate the data transfer at any time in the same way and by providing the same information.

Setup and Administration for SAP Cloud ALM

Integration and Configuration Options PUBLIC 95
If you don't know whether the data transfer for your tenant is active, access the Service Delivery Center app in
your SAP Cloud ALM tenant. If the data transfer is deactivated, you will see a message on the initial screen of
the app.

For more information, refer to Data Transfer for Service Information and SAP Note 3401303 .

Tenant Mapping

Services are always requested and delivered for a specific customer number. The data transfer for service data
uses this customer number to determine which SAP Cloud ALM tenant should receive the service information.
Customers with several customer numbers can maintain a tenant mapping to determine into which SAP Cloud
ALM tenant the service information for each of their customer numbers should be transferred.

For more information, refer to Maintain Tenant Mapping.

Related Information

SAP Cloud ALM for Service

Setup and Administration for SAP Cloud ALM

96 PUBLIC Integration and Configuration Options
9 Application Configuration

For several apps in SAP Cloud ALM, additional setup steps are required or possible.

SAP Cloud ALM for Implementation

There are many integration options that can be used to extend the functionalities of SAP Cloud ALM for
implementation. The setup of these integrations is described under Integration and Configuration Options
[page 44].

SAP Cloud ALM for Operations

Data Collection

You have full control which data from managed services and systems is transferred to SAP Cloud ALM:

When you activate your SAP Cloud ALM tenant and register your systems and services in the Landscape
Management app of SAP Cloud ALM, the collection of observability data is not started automatically. SAP
Cloud ALM follows a central configuration approach: You need to explicitly configure the data collection
processes.

In addition, SAP is moving from customer-managed connectivity (established by customers) to SAP-managed

connectivity (established by SAP). To find out which additional steps are necessary to establish customer-
managed connectivity, see Setup Managed Services / Systems in the operations expert portal.

Personalization and Configuration

In many apps, you can also perform application-specific personalizations and configurations by choosing
 (Configuration) in the top-right corner.

For more information, refer to the Configuration pages of the respective apps in the Application Help on SAP
Help Portal.

SAP Cloud ALM for Service

To use SAP Cloud ALM for service, consent to the data exchange needs to be given. For more information, refer
to Enabling Service Delivery [page 95].

Setup and Administration for SAP Cloud ALM

Application Configuration PUBLIC 97
10 Launching Your Systems from SAP for Me

The Systems & Provisioning dashboard on SAP for Me is your one-stop place for all your active public cloud
systems on SAP BTP.

From here, you can navigate to your global account on SAP BTP and to your SAP Cloud ALM tenant:

1. To find your system information for SAP Cloud ALM, open the Systems page on SAP for Me.
2. Under Public Cloud Systems on BTP, filter by cloud service SAP Cloud ALM. This lists two entries for SAP
Cloud ALM:
• Data Center Region: Global
• Data Center Region: <Region of the subaccount>

 Note

If your company has multiple customer numbers, the entries related to SAP Cloud ALM may occur
for several of these customer numbers. Each customer number can have its own SAP Cloud ALM
installation.

3. Launch the respective systems as follows:

• To launch SAP Cloud ALM, click on the system number of the entry with the data center region
<Region of the subaccount>. Then choose Launch System.
• To launch your global account on SAP BTP, click on the GUID in the Global Account column. Then
choose Launch System.

Related Information

Systems Tab – SAP Support Portal

System Details – SAP Support Portal

Setup and Administration for SAP Cloud ALM

98 PUBLIC Launching Your Systems from SAP for Me
11 Account Termination

When your SAP contracts expire, your SAP Cloud ALM tenant and all related data will be terminated after a
grace period has passed.

The termination process starts with a notice period. The requestor of the global account that contains your
SAP Cloud ALM entitlement receives an email about the expiring contract, and a warning banner is displayed
for the global account in the SAP BTP cockpit. If this happens, you can request an export of your data by
opening an incident on component SV-CLM-INF-ONB, if required.

30 days after your contracts with SAP end, the SAP BTP global account is closed and access to your SAP Cloud
ALM tenant is blocked. At this point, if you renew your SAP contracts, your account can still be restored to a
fully active state without data loss.

60 days after your contracts with SAP expire, your global account and your SAP Cloud ALM tenant are fully
decommissioned. All customer-related data for the account and for all associated services is deleted and
cannot be restored or recovered.

Setup and Administration for SAP Cloud ALM

Account Termination PUBLIC 99
12 Data Protection and Privacy

Data protection is associated with numerous legal requirements and privacy concerns.

In addition to compliance with general data protection and privacy acts, it’s necessary to consider compliance
with industry-specific legislation in different countries. SAP provides specific features and functions to support
compliance with regard to relevant legal requirements, including data protection. SAP doesn’t give any advice
on whether these features and functions are the best method to support company, industry, regional, or
country-specific requirements.

Furthermore, this information shouldn’t be taken as advice or a recommendation regarding additional features
that would be required in specific IT environments. Decisions related to data protection must be made on a
case-by-case basis, considering the given system landscape and the applicable legal requirements.

 Note

SAP doesn’t provide legal advice in any form. SAP software supports data protection compliance by
providing security features and specific data protection-relevant functions, such as simplified blocking and
deletion of personal data. In many cases, compliance with applicable data protection and privacy laws
won’t be covered by a product feature. Definitions and other terms used in this document aren’t taken from
a particular legal source.

SAP Cloud ALM is compliant with DSGVO and GDPR.

EU and NS2 Access

EU access, which restricts the processing of personal data to EEA/Switzerland, isn’t available.

NS2 access, which restricts the processing of personal data to the USA, isn’t available.

For more information, refer to SAP Business Technology Platform – Regions.

12.1 User Data from SAP Cloud ALM

To support users in their job, the following types of personal data are stored in SAP Cloud ALM:

• First and last name

• Email address
• User ID

Hyperscalers, on which SAP products are running, can't access personal data.

Setup and Administration for SAP Cloud ALM

100 PUBLIC Data Protection and Privacy
Finding User Data

A user with the User Administrator role can find all user data in the User Management app in SAP Cloud ALM.

Apart from this user record, personal data in SAP Cloud ALM exists in form of personalization configuration
and in relation to application objects (such as projects, tasks, and alerts). These objects have their own lifetime
and retention periods, independent of the users.

Deleting or Deactivating User Data

To keep the link between application objects and users even after a user was offboarded, the user-related data
is kept for auditability purposes (for example, to see who performed a particular task, executed a test case, or
made a certain configuration).

To protect the personal data of offboarded users, the user administrator can deactivate the user record within
SAP Cloud ALM. If the SAP BTP account is integrated into a central identity management via the Identity
Provisioning service, this also happens automatically if the user is deleted from the Identity Authentication
tenant.

However, this automatic deactivation is done only after a grace period of 30 days. This prevents an accidental
automatic user deactivation while changing the settings in the Identity Authentication service. During this
period, deactivated users aren't authorized to use SAP Cloud ALM, but their personal settings and tasks
assignments are still valid after changing the settings in the Identity Authentication service.

When a user is deactivated in SAP Cloud ALM, all role assignments to the user are deleted and personalized
data is removed. The person-related data of deactivated users is only visible for users with the role User
Administrator or Global Auditor. To all other users, the deactivated user is anonymized.

The user's identity in the identity provider and a mapping of user groups to roles (if available) aren't affected
by this. Therefore, if the user is still active in the Identity Authentication tenant and still has authorizations, for
example, because of a group mapping, a deactivated user can still log on to SAP Cloud ALM. In this case, the
user is reactivated and the personal data becomes visible again to all users in the respective SAP Cloud ALM
applications.

User records can also be deleted by the user administrator after the deactivation. However, deletion isn’t
recommended when the user has worked in SAP Cloud ALM, since it’s more difficult to trace back actions to
the user. Dependent data, that is, business objects that the user has worked on, have their own lifetime and are
deleted according to their own deletion concept.

Only if the SAP Cloud ALM account is closed and deleted, all data is deleted as well.

12.2 User Data from Managed Systems

If you've set up integrations with other SAP solutions or third-party applications, some user-related data from
the managed systems may be stored in SAP Cloud ALM.

Hyperscalers, on which SAP products are running, can't access personal data.

Setup and Administration for SAP Cloud ALM

Data Protection and Privacy PUBLIC 101
Transport Management

Once you've enabled transport management, and transport data (transport request information) is pushed
from the managed system, the transport owner ID is stored in SAP Cloud ALM. No further data related to the
transport owner is stored.

The transport owner ID is usually not known in SAP Cloud ALM and therefore can't be found in the User
Management app. It's only displayed in the Features app.

 Note

The master data is subject to the lifecycle in the managed system.

Monitoring Applications

User-related data that is collected from managed systems as part of the monitoring data, for example in
Integration and Exception Monitoring, Business Process Monitoring, and Real User Monitoring, can only be
accessed by users with roles with a sensitive scope and API calls with sensitive scopes.

The Configuration & Security Analysis collects configuration data and a few config stores contain user IDs.

Within standard memory usage, this user-related monitoring data is considered transient data because it's only
visible in SAP Cloud ALM for the duration of the defined retention period. Once the retention period is over,
all user-related data from managed systems is deleted and not aggregated. For this reason, the retrieval and
manual deletion of user-related monitoring data is currently not supported.

12.3 Email Notifications in SAP Cloud ALM

There are two different ways in which email notifications are handled in SAP Cloud ALM.

In-App Notifications

Email notifications for in-app notifications, which are used predominantly for SAP Cloud ALM for
implementation, can be set up centrally by following Enabling Email Channel for In-App Notifications [page
59].

Once this email channel is enabled, every user can configure for themselves in their profile settings if and for
which notification types they want to receive emails. If users no longer want to receive email notifications, they
can adjust their notification settings at any time.

When an email notification is triggered, the email address of the user is transferred to the SAP Alert
Notification service for SAP BTP. From there, the email notification is sent via a customer-specific email server.

Setup and Administration for SAP Cloud ALM

102 PUBLIC Data Protection and Privacy
Notifications from SAP Cloud ALM for Operations

Email notifications for SAP Cloud ALM for operations applications are managed in the Notification Management
app. They can be set up for both named users (that is, users that are maintained in the Identity Authentication
tenant) and for unnamed users. Only the recipient email ID is stored in SAP Cloud ALM.

Giving Consent
As soon as new recipients are added to the notification management, they receive an email from cloudalm-
[email protected], requesting them to verify their email ID and to offer consent to store their email ID and
receive notification emails from SAP Cloud ALM.

Once given, the consent is valid for 6 months. Shortly before their consent expires, recipients can renew their
own subscription.

Recipients can unsubscribe from notifications at any time by choosing Unsubscribe in the footer of any email
sent by the Notification Management app.

Housekeeping
Recipients who are not required are deleted once every 10 days. This includes:

• Recipients who unsubscribed

• Recipients who were added but did not offer consent to receive emails
• Recipients whose consent expired

12.4 Change Log and Audit Log

Change Log

In SAP Cloud ALM, only the User Management app contains master data. This app uses change logging for all
changes to its data, such as changes of authorizations and user master data.

Change logging in SAP Cloud ALM is implemented on application level and reflects changes, such as the date
and time of the access and the change, and new and old values of the changed attributes.

SAP Audit Log Viewer Service for SAP BTP

The SAP Audit Log Viewer service records the following information:

• Security event log: Security events in SAP Cloud ALM applications

• Changes to personal data: All changes to the user master data
• Read access to sensitive personal data: No application in SAP Cloud ALM stores sensitive personal data.
• Configuration changes: For some applications, configuration changes are registered in the SAP Audit Log
Viewer service. For example, changes to project teams in Projects and Setup are registered.

Setup and Administration for SAP Cloud ALM

Data Protection and Privacy PUBLIC 103
Audit log entries are automatically deleted after a defined retention period. For information about audit log
retention, see Audit Log Retention for the Cloud Foundry Environment in the SAP BTP documentation.

You can access the audit log of SAP Cloud ALM with the SAP Audit Log Viewer service. For information about
subscribing to the viewer and authorizing your business users to access the log, refer to Audit Log Viewer for
the Cloud Foundry Environment in the SAP BTP documentation.

Setup and Administration for SAP Cloud ALM

104 PUBLIC Data Protection and Privacy
13 Security

For security-related information, see the following sources of information:

• Security for SAP BTP, Cloud Foundry Runtime

• Security for SAP BTP

Network and Communication Security

SAP Cloud ALM uses encrypted communication channels based on HTTPS/TLS, supporting TLS version 1.2 or
higher.

For more information see Security.

13.1 Development and Product Security

SAP applies the following measures to make SAP Cloud ALM safe for you to use.

• Security Scans - SAST and FOSS:

• SAP performs daily scans for static application security testing (SAST).
• SAP scans daily for vulnerabilities in the used free and open-source software (FOSS).
• Threat Modeling:
• For every new app and every new functionality, threat modeling is mandatory.
• New software is only released after all risks are mitigated.
• Security Validation: Regular security validations ensure that security requirements are fulfilled.
• Hacker Simulation and Penetration Test: Regular external penetration tests enhance protection from
outside attacks.
• Bug Bounty: Constant security testing by external security researchers.
• Compliance Standards:
• SAP Cloud ALM is compliant with SAP-internal technical policies, procedures, directives, guidelines,
and product standards, such as the directive for network device security and the directive for cloud
infrastructure.
• Employees and operators are bound to the SAP code of business conduct and other behavioral
security standards, such as clean desk and communication.
• Security Product Standards: SAP Cloud ALM follows the general SAP security product standards.
• Certifications and Compliance: SAP Cloud ALM is certified for ISO 27001 and ISO 9001.
• Security Incident Management:
• An emergency plan for sudden security incidents is in place.

Setup and Administration for SAP Cloud ALM

Security PUBLIC 105
 • Security incidents are handled according to the Security Incident Management Process. This process
foresees classification, containment, and resolving of the issue. Internal groups and decision-makers
are involved as needed.
• Security Education and Awareness: SAP employees that are involved in SAP Cloud ALM are regularly
trained on the importance of security. Software developers are trained for secure programming.

Product Security
• Audit logs provide security-relevant logging. They can also be accessed through third-party tools. More
under Change Log and Audit Log.
• SAP Cloud ALM provides security configuration recommendations to empower you to make informed
security-related decisions. More under Security Configuration Recommendations.
• The ability of users to access certain types of data and to perform certain activities in SAP Cloud ALM can
be managed with role collections. More under Role Collections.
• Connections are encrypted with TLS 1.3, X.509 authentication.
• Geo blocking and blocking of sanctioned persons and organizations are in place.
• Data at rest is encrypted.
• SAP HANA databases are regularly backed up.
• For the time being, tenant-specific data recovery is not available.
• Physical security is ensured by hyperscalers.
• Uploaded files are scanned for malware.
• Free text input is sanitized.
• Denial of service attacks are prevented.
• Session timeout is enabled.

Data Protection and Privacy

SAP Cloud ALM is compliant with DSGVO and GDPR.

• Only limited personal data is stored: first name, last name, and email address.
• Information retrieval, edit, and deletion is possible and documented in User Data from SAP Cloud ALM
[page 100].
• Data is anonymized after an employee leaves the company. Then, the data is only visible for auditors with
special authorization.
• Hyperscalers can't access personal data.
• EU access and SAP NS2 aren't supported.

More under Data Protection and Privacy [page 100].

Setup and Administration for SAP Cloud ALM

106 PUBLIC Security
13.2 Security Configuration Recommendations

Use the information in this table to secure the configuration and operation of SAP Cloud ALM services in your
landscape.

Secure Op- Default

erations Setting or Recom- More Infor- Last Up-
Capability Priority Map Topic Behavior mendation mation date Index

Cross Critical Audit Log- Audit By integrat- Enable the Audit Log CALM-
Viewer for X-0001
ging ing the SAP SAP Audit
the Cloud
Audit Log Log Viewer
Foundry En-
Viewer service for vironment
service for SAP BTP.
SAP BTP,
you can
view the au-
dit logs for
your SAP
Cloud ALM
tenant to
track the
end user
activity in
SAP Cloud
ALM.

Cross Recom- Client Se- Cookies Depending To be able CALM-

X-0002
mended curity on your to use the
browser, in-app help
third-party and Built-In
cookies Support, ei-
may be dis- ther allow
abled by third-party
default. cookies or
enter the
respective
domain as
Sites that
can always
use cook-
ies.

Setup and Administration for SAP Cloud ALM

Security PUBLIC 107
 Secure Op- Default
erations Setting or Recom- More Infor- Last Up-
Capability Priority Map Topic Behavior mendation mation date Index

Cross Advanced Client Se- External You can add To protect CALM-
X-0003
curity APIs and config- information
ure service about the
instances to service in-
allow exter- stance,
nal applica- such as the
tions to ac- OAuth se-
cess the cret,
APIs pub- choose cer-
lished on tificate-
SAP Busi- based au-
ness Accel- thentica-
erator Hub tion.
.
To prevent
To do this, external ap-
you need to plications
configure from per-
authentica- forming un-
tion for the authorized
service in- operations,
stances and assign the
set allowed minimal set
scopes in of scopes.
the service Create sep-
instance. arate serv-
ice instan-
ces with in-
dividual
scopes for
required
purposes
instead of
assigning
all scopes in
one in-
stance and
using them
for all API
access.

Setup and Administration for SAP Cloud ALM

108 PUBLIC Security
 Secure Op- Default
erations Setting or Recom- More Infor- Last Up-
Capability Priority Map Topic Behavior mendation mation date Index

External Advanced Authentica- Secure Sys- When con- Use the au- SAP BTP CALM-EX-
tem-to-Sys-
API Man- tion and figuring a thentication Security TAPI-0001
tem Inte-
agement Single Sign- webhook to method Recom-
gration
On point to the that is rec- mendations
target ex- ommended
ternal serv- by the
ice API, you Landscape
need to se- Manageme
lect either nt app or
an SAP BTP SAP BTP.
destination
or an end-
point in the
Landscape
Manageme
nt app.

User & Ac- Critical Roles and Roles Roles in Assign suit- Role Collec- CALM-
tions [page UAM-0001
cess Man- Authoriza- SAP Cloud able roles
35]
agement tions ALM are de- that give
livered as users only
predefined the authori-
collections. zations they
need to per-
The initial
form their
user re-
tasks.
ceives the
role Global
Administrat
or, which
provides
the com-
plete set of
authoriza-
tions in SAP
Cloud ALM.

Setup and Administration for SAP Cloud ALM

Security PUBLIC 109
 Secure Op- Default
erations Setting or Recom- More Infor- Last Up-
Capability Priority Map Topic Behavior mendation mation date Index

Landscape Critical Authentica- Strong Au- When add- Choose one Step 3: Set CALM-
Up Land- LM-0001
Manage- tion and thentication ing a serv- of the more
scape Man-
ment Single Sign- ice man- secure
agement –
On ually, you methods Services
can choose according [page 42]
between to the capa-
several au- bilities of
thentication the end-
settings for point pro-
new end- viding cloud
points. The service:
available
• OAuth
options de-
2Client
pend on the
Creden
cloud serv-
tials
ice.
• ClientC
ertifica
teAuth
enticati
on
• Auth2S
AMLBe
arerAut
hentica
tion

Project Advanced Roles and Project Ac- The access Select the Configuring CALM-
Project PTM-0001
Manage- Authoriza- cess Re- level of the appropriate
User Per-
ment tions strictions initial, auto- access level
missions
matically for your [page 63]
created project:
project is
• Public
Public.
• Restric
Any addi- ted
tional
• Private
projects
that you
create man-
ually are set
to
Restricted
by default.

Setup and Administration for SAP Cloud ALM

110 PUBLIC Security
 Secure Op- Default
erations Setting or Recom- More Infor- Last Up-
Capability Priority Map Topic Behavior mendation mation date Index

Business Recom- Roles and KPI Access You can re- Use access Creating CALM-
Process mended Authoriza- Control strict the groups to Access BM-0001
Monitoring tions data access grant users Groups
of a defined access only
user group to data rele-
to a particu- vant to their
lar business tasks.
process
scope
and/or ac-
cording to
selected
process at-
tributes.

By default,
access con-
trol is deac-
tivated.

Setup and Administration for SAP Cloud ALM

Security PUBLIC 111
13.2.1 Explanations of Table Properties

Table Headings

Secure Op- Default

erations Setting or Recom- More Infor- Last Up-
Service Priority Map Topic Behavior mendation mation date Index

The name Defines the The Secure A topic is a Describes Defines our A link to Date of the A stable
of the criticality of Operations short de- the usage recommen- documen- last signifi- unique ref-
service or the recom- Map is a ref- scription or of the se- dation for tation that cant erence to
area to mendation. erence a general curity set- this config- explains change. identify the
which the model to heading to ting, includ- uration. how you recommen-
For an ex- See also
setting structure find similar ing any con- can achieve dation.
planation of What's New
belongs. the broad topics text, or de- the recom-
the priority for SAP
area of se- across serv- fault setting mendation.
levels, see Cloud ALM.
curity for ices. behavior (if
the follow-
content, available).
ing Priori-
discus-  No
ties table.
sions, and te
as a basis
Please
for a 360°
expect
view on se-
change
curity.
s here.
For more in-
formation
about the
Secure Op-
erations
Map, see
Security
Overview
as part
of the SAP
Security
Optimiza-
tion Serv-
ices Portfo-
lio.

Priorities

Priority Description

Critical Exposes the system to significant risk or threatens system reliability.

Recommended Improves the security of the landscape and significantly reduces the attack sur-
face.

Setup and Administration for SAP Cloud ALM

112 PUBLIC Security
 Priority Description

Advanced Extends the recommendation to a higher standard. The recommendation either

extends the security standards to higher level of protection or to additional areas,
such as your organization-specific requirements.

Setup and Administration for SAP Cloud ALM

Security PUBLIC 113
14 Troubleshooting and FAQ

In this document, you can find answers to some of the most common questions and issues that may arise
while requesting and setting up SAP Cloud ALM.

To get started, find your current phase or the subject of your issue and jump to the corresponding section:

• Before the Provisioning [page 114]

• After the Provisioning [page 116]
• Identity Authentication [page 117]
• User Management [page 118]
• Logon Issues (Administrators) [page 119]
• Logon Issues (Users) [page 120]
• Your SAP Cloud ALM Subaccount [page 121]
• Lifecycle Management of Your SAP Cloud ALM Tenant [page 121]
• Related Troubleshooting Guides [page 122]
• Further Support [page 122]

Before the Provisioning

Issue Resolution

You want to know how much it costs to use SAP SAP Cloud ALM is part of SAP Enterprise Support and other con-
Cloud ALM. tracts. To find out if you're entitled to provision SAP Cloud ALM, refer
to the Usage Rights – SAP Cloud ALM on SAP Support Portal. You
can start the provisioning process here .

SAP Cloud ALM options for which you may get charged are docu-
mented in our Fair Use [page 7] statement.

You want to request SAP Cloud ALM on SAP for Me, Make sure you fulfill the following prerequisites:
but you can't access the request dashboard.
• Your company number has sufficient product and support con-
tracts.
• You're assigned to the respective customer.
• You have an S-user with the role Edit Cloud Data on SAP for
Me.

Setup and Administration for SAP Cloud ALM

114 PUBLIC Troubleshooting and FAQ
 Issue Resolution

You want to determine if an SAP Cloud ALM ten- Open the Provisioning dashboard on SAP for Me:
ant has already been provisioned for your customer
number, or if it can still be provisioned.
• If SAP Cloud ALM is available in the section Products Available
for Provisioning, it has not been provisioned yet and you can
request it.
• If SAP Cloud ALM is available in the section Provisioning Status,
the provisioning is either in progress or completed.

You want to provision your SAP Cloud ALM tenant The Netherlands | Amsterdam region was available during the initial
in the Netherlands | Amsterdam region. phase of the SAP Cloud ALM rollout, which is why it may still be listed
at different places on SAP websites, for example, under Data Center
Locations in the SAP Trust Center.

However, this region is no longer available for the provisioning of SAP

Cloud ALM.

You have questions on which subdomain name to For more information and recommendations, take a look at the fol-
use for your SAP Cloud ALM tenant. lowing resources:

• The SAP for Me  Help for the section Subdomain

• Step 5 in Required Setup for SAP Cloud ALM [page 28]

You have questions on which Identity Authentica- For more information and recommendations, take a look at the fol-
tion tenant to select for the provisioning. lowing resources:

• The SAP for Me  Help for the section SAP Identity Service
• Step 6 in Required Setup for SAP Cloud ALM [page 28]

When requesting SAP Cloud ALM on SAP for Me, Your Identity Authentication tenant may not show up for the following
your Identity Authentication tenant isn't available reasons:
for selection.
• It may not be a productive tenant.
• It may be assigned to a different customer ID.

You can find all Identity Authentication tenants assigned to your cus-
tomer ID and their type at https://iamtenants.accounts.cloud.sap .

Setup and Administration for SAP Cloud ALM

Troubleshooting and FAQ PUBLIC 115
After the Provisioning

Issue Resolution

You want to find the welcome emails and activation Welcome Emails from SAP Cloud ALM
emails that were sent to you when you requested
• If you requested SAP Cloud ALM, you've received a welcome
SAP Cloud ALM.
email with the subject Access information for SAP Cloud ALM.
• If someone else requested SAP Cloud ALM and added you to
the system, you've received a welcome email with the subject
Welcome to SAP Cloud ALM.

Activation Emails from the Identity Authentication Service

• If you didn't have a productive Identity Authentication tenant

when you requested SAP Cloud ALM, a new Identity Authentica-
tion tenant was created for you. You've received an email with
the subject Activate Your Account for Identity Authentication
Service.
• If someone added your user to a productive Identity Authentica-
tion tenant, you've received an email with the subject Activate
Your Account for User Profile.
• If someone added your user to a productive Identity Authentica-
tion tenant as an administrator, you've received an email with the
subject Activate Your Account for Administration Console.

You can't find or didn't receive your activation email Search for an email with the subject Activate Your Account for...
for your Identity Authentication tenant. Don't forget to also check your spam folder.

If you still can't find it, create an incident on component SV-CLM-INF-

ONB to have the activation email resent to you.

You want to add an administrator to the global ac- Refer to KBA 3342350 .
count and/or subaccounts for SAP Cloud ALM in
SAP BTP.

You requested SAP Cloud ALM and want to assign Refer to KBA 3248116 .
additional administrators who can complete the
setup of SAP Cloud ALM.

The person who originally requested SAP Cloud Refer to KBA 3365171 .
ALM is no longer available and you want to give
yourself or another user full administrator privi-
leges.

You're an Ultimate Global Customer with multiple Refer to SAP Note 3070306 .
customer numbers and want to import all your cus-
tomer numbers for cloud subscriptions into one
SAP Cloud ALM system. You don't want to maintain
several SAP Cloud ALM systems.

Setup and Administration for SAP Cloud ALM

116 PUBLIC Troubleshooting and FAQ
Identity Authentication

Issue Resolution

You have questions on which Identity Authentica- Refer to the section Before the Provisioning [page 114].
tion tenant to select for the provisioning.

You want to connect SAP Cloud ALM to a non-pro- We don't recommend connecting SAP Cloud ALM to a non-produc-
duction Identity Authentication tenant. tion Identity Authentication tenant because there's no way to migrate
users from a test Identity Authentication tenant to a production Iden-
tity Authentication tenant. This could cause issues in your landscape
if you later decide to use SAP Cloud ALM in a productive manner.

You want to use a different Identity Authentication Refer to KBA 3020352 .

tenant than the one that was provisioned with SAP
Cloud ALM.

You want to use a different Identity Authentication Creating multiple productive Identity Authentication tenants splits
in SAP Cloud ALM than the one you're using for the user base and requires an individual administrator for each ten-
your managed system. ant. This means that users that are maintained in the Identity Authen-
tication tenant of your managed system also need to be created in
the Identity Authentication tenant that is used for SAP Cloud ALM, if
they need to work in both solutions.

If you still want to change your Identity Authentication tenant assign-

ment in SAP Cloud ALM, refer to KBA 3020352 .

You want to use a corporate identity provider You can also use an already existing corporate identity provider
(LDAP) for SAP Cloud ALM. (LDAP), in which case we strongly recommend using Identity Authen-
tication as a proxy. Changing to a corporate identity provider while
already using SAP Cloud ALM productively can result in invalidated
user IDs and can cause users in SAP Cloud ALM to be deactivated.

For more information, refer to Corporate Identity Providers.

You want to find out which Identity Authentication Refer to Viewing Assigned Tenants and Administrators.
tenants are assigned to your customer ID and who
the administrator is.

You want to find out which Identity Authentication Follow the first 6 steps described in KBA 3020352 .
tenant is used for your SAP Cloud ALM tenant.

You're facing issues with your Identity Authentica- Refer to KBA 3090756 .
tion tenant after requesting SAP Cloud ALM.

Your Identity Authentication tenant was created in a You can request it be moved by raising an incident on component
different data center than SAP Cloud ALM. BC-IAM-IDS.

Setup and Administration for SAP Cloud ALM

Troubleshooting and FAQ PUBLIC 117
Issue Resolution

You can't access your Identity Authentication ten- Refer to KBA 2579343 .
ant. The following error message appears:

Sorry... You entered a valid URL, but you are not

authorized to view the content; contact your system
administrator.

When you log on to SAP Cloud ALM, you can Refer to KBA 3086201 .
choose between multiple identity providers.

User Management

Issue Resolution

You want to create a large number of users for SAP There is no limit to the number of users that can be created for an
Cloud ALM. SAP Cloud ALM system.

You've added users in the User Management app The onboarding of users consists of two steps that take place in two
in SAP Cloud ALM, but they haven't received a wel- different applications:
come email.
• User Management in your Identity Authentication (IAS) tenant
• User Management in SAP Cloud ALM

Before you can add users in SAP Cloud ALM and assign roles to them,
you need to create them in your Identity Authentication tenant.

For more information, refer to Step 1: Onboard Users in the Identity

Authentication Service [page 30].

You want to create a user in your SAP Cloud ALM Refer to KBA 3032960 .
tenant that SAP development can use for trouble-
shooting and support purposes.

You have the role Project Administrator, but you The role Project Administrator only enables you to administer projects
don't have access to the User Management app to and assign users that have already been added to SAP Cloud ALM.
create business users in SAP Cloud ALM.
To add users to SAP Cloud ALM, you need the role Global
Administrator or User Administrator.

For more information, refer to Step 2: Assign Roles to Users in SAP

Cloud ALM [page 32].

Setup and Administration for SAP Cloud ALM

118 PUBLIC Troubleshooting and FAQ
 Issue Resolution

Users in SAP Cloud ALM have the status Expiring In SAP Cloud ALM, the Identity Authentication service (IAS) assumes
Soon. the role of an identity provider. If users are deleted in the Identity
Authentication tenant or if user IDs are changed due to changes in
the Identity Authentication configuration (for example, from email to
login name), the affected users are automatically deactivated in SAP
Cloud ALM after a grace period of 30 days.

The number of days specified by the Expires Soon status indicates

the end of the grace period after which the user will be deactivated. A
user with this status is not authorized to use SAP Cloud ALM.

If you revert the Identity Authentication configuration within the grace

period, the user's personal settings and project assignments are still
valid. If you want to keep your current configuration, the personal
settings and project assignments are lost and you need to reassign
the authorizations to the new user ID.

Logon Issues (Administrators)

Issue Resolution

You can't find or didn't receive your activation email Search for an email with the subject Activate Your Account for...
for your Identity Authentication tenant. Don't forget to also check your spam folder.

If you still can't find it, create an incident on component SV-CLM-INF-

ONB to have the activation email resent to you.

You can't log on to SAP Cloud ALM. Verify that you've entered the correct credentials: You need to log on
with the email address and password defined in the Identity Authenti-
cation tenant, not your S-user.

Make sure you've completed all steps in Required Setup for SAP
Cloud ALM [page 28] and that you've activated your user profile in
the Identity Authentication tenant.

If you can't find the activation email, go to your Identity Authentica-

tion tenant, enter your email address, and choose Forgot password.
You will receive a new activation email.

When logging on to SAP Cloud ALM, you can Refer to KBA 3086201 .
choose between multiple identity providers.

Setup and Administration for SAP Cloud ALM

Troubleshooting and FAQ PUBLIC 119
Issue Resolution

When you try to access SAP Cloud ALM via the Refer to SAP Note 3046343 .
tenant URL, the following error messages appear:

Sorry a technical error occurred during the logon

process. Please contact your technical support.

Sorry, you can't sign in right now.

When you try to access SAP Cloud ALM from the Check whether you have a firewall setting that prevents you from
SAP BTP cockpit, an HTTP 500 error occurs. But accessing the application. You may need to specify a port.
from outside the organization, for example SAP
support, you can access the application.

Logon Issues (Users)

Issue Resolution

You can't find your SAP Cloud ALM welcome email. Search for an email with the subject Welcome to SAP Cloud ALM.
Don't forget to also check your spam folder.

If you can't find one, ask your administrator to give you the URL of
your SAP Cloud ALM tenant. You can log on directly with this URL.

You can't find your activation email from the Iden- Search for an email with the subject Activate Your Account for User
tity Authentication Service. Profile. Don't forget to also check your spam folder.

If you can't find one, ask your administrator to resend the email as
described in Send Reset Password Email.

You can't log on to SAP Cloud ALM. Verify that you've entered the correct credentials: You need to log on
with the email address and password defined in the Identity Authenti-
cation tenant, not your S-user.

Check with your administrator if your user profile in the Identity Au-
thentication tenant has been created.

When logging on to SAP Cloud ALM, you can Contact your administrator and refer them to KBA 3086201 .
choose between multiple identity providers.

You can log on to SAP Cloud ALM but do not see Your user may not yet have any roles in SAP Cloud ALM.
any apps.
Ask your administrator to assign roles to you in the User Management
app or in the SAP BTP cockpit, as described in Step 2: Assign Roles to
Users in SAP Cloud ALM [page 32].

You want to know who the administrator of your Refer to Viewing Assigned Tenants and Administrators.
Identity Authentication tenant is.

Setup and Administration for SAP Cloud ALM

120 PUBLIC Troubleshooting and FAQ
Your SAP Cloud ALM Subaccount

Issue Resolution

You can't find your subaccount for SAP Cloud ALM Refer to this question on SAP Community.
in the SAP BTP cockpit.

You want to subscribe to additional applications in You can't subscribe to any additional applications in the subaccount
the subaccount containing your SAP Cloud ALM containing your SAP Cloud ALM subscription. The subaccount is set
subscription. up exclusively for SAP Cloud ALM.

Lifecycle Management of Your SAP Cloud ALM Tenant

Issue Resolution

You want to set up a second SAP Cloud ALM tenant. Currently, only one SAP Cloud ALM tenant can be requested per
entitled customer number.

You want to move your SAP Cloud ALM application It's currently not possible to move your SAP Cloud ALM application
to a different data center. from the data center in which it was originally provisioned to a differ-
ent data center.

You want to migrate your SAP Cloud ALM applica- Refer to KBA 3352417 .
tion to a different data center.

You want to change the subdomain of your SAP It's currently not possible to change the subdomain of an existing
Cloud ALM tenant. SAP Cloud ALM tenant

After deleting your SAP Cloud ALM application, you Refer to KBA 3257720 .
want to set it up again from scratch.

You want to delete your SAP Cloud ALM subscrip- Refer to KBA 3247776 .
tion in your subaccount.
 Caution
Deleting your SAP Cloud ALM subscription causes all created
artifacts, stored data, and current configurations to be deleted as
well. It will not re-enable you to request SAP Cloud ALM on SAP
for Me.

You want to decommission SAP Cloud ALM. Official decommissioning of SAP Cloud ALM isn't yet available. How-
ever, you can use a housekeeping job to delete services from the
Landscape Management app.

Setup and Administration for SAP Cloud ALM

Troubleshooting and FAQ PUBLIC 121
Issue Resolution

You want to move your SAP Cloud ALM tenant from Refer to SAP Note 3282741 .
one customer number to another customer num-
ber.

Related Troubleshooting Guides

• KBA 3270970 - Most Common Onboarding Issues

• Troubleshooting for Managed ABAP Systems (SAP Support Portal)
• Landscape Management – Troubleshooting and Customer Support (SAP Support Portal)

Further Support

If you encounter issues that aren't listed here or if you're unable to perform the described resolutions yourself,
schedule an expert session or create a support ticket on the following components:

Area Component

Provisioning and setup of SAP Cloud ALM SV-CLM-INF-ONB

Onboarding of users and assignment of roles SV-CLM-INF-UAM

Setup and usage of landscape management SV-CLM-INF-LMS

Setup and Administration for SAP Cloud ALM

122 PUBLIC Troubleshooting and FAQ
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Setup and Administration for SAP Cloud ALM

Important Disclaimers and Legal Information PUBLIC 123
www.sap.com/contactsap

© 2024 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.

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.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN