Setup and Administration For SAP Cloud ALM

Administration Guide | PUBLIC
2023-07-04
Setup and Administration for SAP Cloud ALM

© 2023 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4 Supported Solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5 Video-Guided Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
6 Requesting SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
7 Required Setup for SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

7.1 Step 1: Onboard Users in Your Identity Authentication Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
7.2 Step 2: Assign Roles to Users in SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Role Collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
7.3 Step 3: Set Up Landscape Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
8 Enabling Service Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9 Integration and Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

9.1 Enabling SAP Cloud ALM API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Managing Your Service Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
9.2 Activating the SAP Audit Log Viewer Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
9.3 Integrating SAP Central Business Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
9.4 Configuring Project User Permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
9.5 Integrating the Cloud Integration Automation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
9.6 Enabling Transport Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
SAP S/4HANA Cloud, Private Edition and On-Premise Systems. . . . . . . . . . . . . . . . . . . . . . . . . 57
SAP Cloud Transport Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
9.7 Integrating Test Automation Providers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Integrating the Test Automation Tool for SAP S/4HANA Cloud. . . . . . . . . . . . . . . . . . . . . . . . . . 68
Setting Up Tricentis Test Automation for SAP Integrated with SAP Cloud ALM. . . . . . . . . . . . . . . 70
10 Application Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
11 Launching Your Systems from SAP for Me. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
12 Finding Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

2 PUBLIC Content
13 Accessibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
14 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

14.1 User Data from SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
14.2 User Data from Managed Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
14.3 Email Notifications in SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
14.4 Change Log and Audit Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
15 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
15.1 Security Configuration Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Explanations of Table Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
16 Account Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
17 Troubleshooting and FAQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

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
The English version of this guide is open for contributions and feedback using GitHub. This allows you
to get in contact with responsible authors of SAP Help Portal pages and the development team to
discuss documentation-related issues. To contribute to this guide, or to provide feedback, choose the
corresponding option on SAP Help Portal:
•  Edit: Contribute to a documentation page. This option opens a pull request on GitHub.
•  Feedback: Provide feedback about a documentation page. This option opens an issue on GitHub.
You need a GitHub account to use these options.
More information:
• Contribution Guidelines
• Introduction Video: Open Documentation Initiative
• Blog Post: Introducing the Open Documentation Initiative
Make sure that you have the latest version of this guide, which can be found under SAP Cloud ALM.
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.

4 PUBLIC About This Guide
2 Availability
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 .
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.
EU Access
EU access, which restricts the processing of personal data to EEA/Switzerland, isn’t available.
For more information, refer to SAP Business Technology Platform – Regions.

Availability PUBLIC 5
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 fix 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 do therefore not affect the 8-GB limitation.
You can do the monitoring of the SAP HANA memory consumption in SAP Cloud ALM under Health
Monitoring "cloudalm" services SAP Cloud ALM HANA Memory .
You can configure the data and storage duration in SAP Cloud ALM for operations features. Find the guidelines
under Housekeeping in the expert 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 ).

6 PUBLIC Fair Use
• 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 ).

Fair Use PUBLIC 7
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 BTP, Cloud Foundry environment Operations Real User Monitor More under Real User Monitoring
ing (Expert Portal).
SAP S/4HANA Cloud Implementation Process Manage

• SAP Best Practices for SAP S/
ment
4HANA Cloud
• Two-Tier ERP – EPPM
• Two-Tier ERP – Finance
• Two-Tier ERP – Human Resources
• Two-Tier ERP – Manufacturing
• Two-Tier ERP – Master Data
• Two-Tier ERP – Product Lifecycle
Management
• Two-Tier ERP – Professional Serv
ices
• Two-Tier ERP – Sales
• Two-Tier ERP – Services
• Two-Tier ERP – Sourcing and Pro
curement
• Two-Tier ERP – Supply Chain
• Two-Tier ERP – Sustainability
• SAP Best Practices for analytics
with SAP S/4HANA Cloud
More under Business Process Content

in SAP Cloud ALM (Expert Portal).

8 PUBLIC Supported Solutions
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).
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
More under SAP SuccessFactors Proc

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

Supported Solutions PUBLIC 9
SAP Marketing Cloud Implementation Process Manage https://rapid.sap.com/bp/#/

ment browse/categories/lines_of_busi
ness/areas/marketing/packagever
sions/BP_CLD_MKT
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 ment Business Planning for Supply Chain
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 available: SAP Activate
Methodology for SAP S/4HANA Cloud,
private edition (new implementation
and system conversion)
SAP S/4HANA Cloud Implementation Task Management Task template available: SAP Acti
vate Methodology for SAP S/4HANA
Cloud

SAP S/4HANA (on-premise) Implementation Task Management Task template available:
• SAP Activate Methodology for

SAP S/4HANA Cloud, private edi
tion (new implementation and
system conversion)
• SAP Activate Methodology for
SAP S/4HANA Cloud, extended
edition
SAP SuccessFactors Implementation Task Management Task template available:
• SAP Activate Methodology for the

Intelligent Enterprise: Hire-to-Re
tire
• SAP Activate Methodology for SAP
SuccessFactors
SAP Sales Cloud Implementation Task Management SAP Cloud for Customer
SAP Service Cloud Implementation Task Management SAP Cloud for Customer
Intelligent Enterprise – Implementation Implementation Task Management
SAP Ariba Implementation Task Management
SAP Business Network Implementation Task Management
SAP Fieldglass Implementation Task Management
SAP S/4HANA Cloud Implementation Requirement Man

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

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

agement
SAP SuccessFactors Implementation Requirement Man

agement
SAP Sales Cloud Implementation Requirement Man SAP Cloud for Customer
agement
SAP Service Cloud Implementation Requirement Man SAP Cloud for Customer
agement
Intelligent Enterprise – Implementation Implementation Requirement Man

agement
SAP Ariba Implementation Requirement Man

agement
SAP Business Network Implementation Requirement Man

agement

SAP Fieldglass Implementation Requirement Man

agement
SAP S/4HANA Cloud Implementation Documents
SAP S/4HANA Cloud, private edition Implementation Documents
SAP S/4HANA (on-premise) Implementation Documents
SAP SuccessFactors Implementation Documents
SAP Sales Cloud Implementation Documents SAP Cloud for Customer
SAP Service Cloud Implementation Documents SAP Cloud for Customer
Intelligent Enterprise – Implementation Implementation Documents
SAP Ariba Implementation Documents
SAP Business Network Implementation Documents
SAP Fieldglass Implementation Documents
SAP S/4HANA Cloud, private edition Implementation Deployment Man More under SAP S/4HANA Cloud, Pri
agement vate Edition and On-Premise Systems
[page 57].
SAP S/4HANA (on-premise) Implementation Deployment Man More under SAP S/4HANA Cloud, Pri
agement vate Edition and On-Premise Systems
[page 57].
SAP Integration Suite – Cloud Integra Implementation Deployment Man More under Supported Content Types.
tion agement
SAP Integration Suite – API Manage Implementation Deployment Man More under Supported Content Types.
ment agement
SAP BTP, Cloud Foundry environment Implementation Deployment Man Mainly development content and some
agement
selected services
More under Supported Content Types.
SAP BTP, Neo environment Implementation Deployment Man Mainly development content and some
agement
selected services
SAP Build Work Zone Implementation Deployment Man Application content

agement
SAP Build Process Automation Implementation Deployment Man MTA

agement
SAP S/4HANA Cloud Implementation Test Management More under Integrating the Test Auto
mation Tool for SAP S/4HANA Cloud
[page 68].
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 Business Network Implementation Test Management
SAP Fieldglass Implementation Test Management
Tricentis Test Automation for SAP inte Implementation Test Management More under Setting Up Tricentis Test
grated with SAP Cloud ALM Automation for SAP Integrated with
SAP Cloud ALM [page 70].
SAP S/4HANA Cloud Operations Integration and Ex More under Integration and Exception
ception Monitoring Monitoring (Expert Portal).
SAP S/4HANA (on-premise) Operations Integration and Ex More under Integration and Exception
SAP Logistic Business Network Operations Integration and Ex More under Integration and Exception
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
SAP Cloud for Customer Operations Integration and Ex More under Integration and Exception
SAP Marketing Cloud Operations Integration and Ex More under Integration and Exception
SAP Concur Operations Integration and Ex More under Integration and Exception
SAP Order Management foundation Operations Integration and Ex More under Integration and Exception
SAP Fieldglass Operations Integration and Ex More under Integration and Exception
SAP SuccessFactors Operations Integration and Ex More under Integration and Exception
SAP Intelligent Asset Management Operations Integration and Ex More under Integration and Exception
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
SAP BTP, ABAP environment Operations Integration and Ex More under Integration and Exception
SAP Mobile Services Operations Integration and Ex More under Integration and Exception
SAP S/4HANA Cloud, private edition Operations Integration and Ex More under Integration and Exception
SAP Field Service Management Operations Integration and Ex More under Integration and Exception
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
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
SAP Business ByDesign Operations Integration and Ex More under Integration and Exception
SAP Omnichannel Promotion Pricing Operations Integration and Ex More under Integration and Exception
SAP Process Integration (Java) Operations Integration and Ex More under Integration and Exception
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
SAP Data Intelligence Operations Integration and Ex More under Integration and Exception

SAP S/4HANA Cloud 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:

to-Operate

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

to-Operate

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

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

to-Operate

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


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).
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 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 Business Suite Operations Job and Automa More under Job and Automation Moni
tion Monitoring toring (Expert Portal).

SAP S/4HANA Cloud Operations Job and Automa More under Job and Automation Moni
SAP S/4HANA Cloud, private edition Operations Job and Automa More under Job and Automation Moni
SAP S/4HANA (on-premise) Operations Job and Automa More under Job and Automation Moni
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
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
SAP Build Process Automation Operations Job and Automa More under Setup for SAP HANA
tion Monitoring Cloud (Expert Portal).
SAP BTP, Neo environment Operations Real User Monitor More under Real User Monitoring
SAP Business Suite Operations Real User Monitor More under Real User Monitoring
SAP S/4HANA Cloud, private edition Operations Real User Monitor More under Real User Monitoring
SAP S/4HANA Cloud Operations Real User Monitor More under Real User Monitoring
SAP S/4HANA (on-premise) Operations Real User Monitor More under Real User Monitoring
SAP Marketing Cloud Operations Real User Monitor More under Real User Monitoring
SAP Cloud for Customer Operations Real User Monitor More under Real User Monitoring
SAP BTP, ABAP environment Operations Real User Monitor More under Real User Monitoring
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 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 Business Suite Operations Configuration & More under Expert Portal (Expert
Security Analysis Portal).
SAP S/4HANA (on-premise) Operations Configuration & More under Expert Portal (Expert
SAP S/4HANA Cloud, private edition Operations Configuration & More under Expert Portal (Expert
SAP NetWeaver Application Server for Operations Configuration & More under Expert Portal (Expert
ABAP (7.40 and higher) Security Analysis Portal).

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 26] and Integration and Configuration Options [page 42].
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 21]
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 Your Identity Authentication Service [page 28]
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 31]
Enabling SAP Cloud ALM API
Find out how to enable the monitoring of your cloud services by enabling SAP Cloud ALM API in the SAP BTP
cockpit.
Corresponding documentation: Enabling SAP Cloud ALM API [page 44]

Video-Guided Setup PUBLIC 19
20 PUBLIC Video-Guided Setup
6 Requesting SAP Cloud ALM
You can request SAP Cloud ALM on SAP for Me for all entitled customers you have sufficient permissions for.
 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 26].
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.

Requesting SAP Cloud ALM PUBLIC 21
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.
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.
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.

22 PUBLIC Requesting SAP Cloud ALM
• 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 .
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 that contains your SAP Cloud ALM entitlement, with the name “SAP Cloud ALM”
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, and quotas.
• A subaccount that contains your SAP Cloud ALM subscription, with the name “SAP Cloud ALM”, 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.
• A Cloud Foundry organization

An organization is an additional hierarchical level in the Cloud Foundry environment.
The name of the organization is identical to the subdomain name. If the specified subdomain name
doesn't contain the suffix -cloudalm, this suffix is added to the organization name.
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.

24 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

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 90]
• 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.

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

Required Setup for SAP Cloud ALM PUBLIC 27
• Requesting SAP Cloud ALM [page 21]
• Step 1: Onboard Users in Your Identity Authentication Service [page 28]
• Step 2: Assign Roles to Users in SAP Cloud ALM [page 31]
• Step 3: Set Up Landscape Management [page 39]
• Integration and Configuration Options [page 42]
For more detailed background information and general explanations of SAP BTP concepts, refer to Basic
Platform Concepts.
7.1 Step 1: Onboard Users in Your Identity Authentication

Service
To give further users access to SAP Cloud ALM, you need to create or import users in the 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
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 31] 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.
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. Choose Save.
5. Select Send activation e-mail.
6. 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 the 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
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 28].
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

Type Description
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 33].
8. Save your settings.
The user will now also receive a welcome email from SAP Cloud ALM.
For more information on how to use the User Management app to view, add, and change roles, refer to the
in-app help.
SAP BTP Cockpit
 Note
The roles in SAP Cloud ALM are available as role collections in your subaccount in the SAP BTP cockpit.
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 28].
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 were 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.
Don't use the identity provider that's named SAP ID Service or sap.default.
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 Ad nistrator
data. ministrator
FlexOperator
 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 Au tor
ditor
This role is to be used for general audit
purposes.
User & Access Man User Create and manage users, assign and User & Ac x_uam_UserAdminis
agement Administrator approve authorizations cess Man trator
agement
FlexOperator
Adminis
trator
User & Access Man User Viewer View users and authorization assign User & Ac x_uam_UserViewer
agement ments cess Man
agement
Viewer
Landscape Manage Landscape Manage certificates Landscape x_landscape_Secur

ment Management Manage ityAdministrator
Security ment Se
Administrator curity Ad
ministrator
Project Management Project Manage projects, deployment plans, Project & imp_pjm_ProjectAd
Administrator tasks, scopes, requirements, features, Task Man ministrator
notes, test cases, defects, and tags agement
Adminis
Your permissions within implementa
trator
tion projects additionally depend on the
access level of the project and your
team assignment in the project. For
more information, refer to Configuring
Project User Permissions [page 53].

Project Management Project Lead Manage projects, deployment plans, Project & imp_pjm_ProjectLe
tasks, scopes, requirements, features, Task Man ad
notes, test cases, and defects agement
Project
Lead
Project Management Project Member View projects and deployment plans. Project & imp_pjm_ProjectMe
Manage tasks, scopes, requirements, Task Man mber
features (with restrictions ), notes, agement
test cases, and defects Project
Member
Project Management Project Viewer View projects, deployment plans, tasks, Project & imp_pjm_ProjectVi
scopes, requirements, features, notes, Task Man ewer
test cases, and defects agement
Project
Viewer
Process Management Process Author Create, edit, and delete custom solution Process imp_pm_ProcessAut
processes Manage hor
ment Proc
ess Author
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 Adminis
trator

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
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
Executor
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
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
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 Moni ops_jm_JobMonitor
Monitoring Administrator uration settings, including the display of toring Ad ingAdministrator
monitoring data ministrator
Job & Automation Job Monitoring View the job monitoring application for Job Moni ops_jm_JobMonitor
Monitoring Consumer the maintained global configurations toring ingConsumer
Consumer

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 Adminis
trator
quests Monitoring nalyst
Analyst
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 Moni UserMonitoringAdm
settings. View performance and availa toring Ad inistrator
bility of scenario executions ministrator
Synthetic User Moni Scenario Expert Create, edit, delete, and manage config- Synthetic ops_sum_Synthetic
toring uration settings. View performance and User Moni UserMonitoringExp
availability of scenario executions toring Sce ert
nario Ex
pert
Synthetic User Moni Scenario Viewer View performance and availability of Synthetic ops_sum_Synthetic
toring scenario executions User Moni UserMonitoringVie
toring Sce wer
nario
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 Adminis or
trator
Health Monitoring Health Monitoring View health overview and metrics of Health ops_hm_HealthMoni
Viewer cloud services Monitoring toringViewer
Viewer
Business Service Man Business Service Create and manage business services, Business ops_bsm_BusinessS
agement Management and plan events Service erviceManagementA
Administrator Manage dministrator
ment Ad
ministrator

Business Service Man Business Service View business services, their configura- Business ops_bsm_BusinessS
agement Management tion, and the event calendar Service erviceManagementV
Viewer Manage iewer
ment
Viewer
Configuration & Secur Configuration Administrate managed objects, configu- Configura- ops_csa_Configura
ity Analysis Monitoring ration settings, and display application tion Moni tionMonitoringAdm
Administrator data toring Ad inistrator
ministrator
Configuration & Secur Configuration Display application configuration data Configura- ops_csa_Configura
ity Analysis Monitoring tion Moni tionMonitoringAna
Analyst toring An lyst
alyst
Service Collaboration Services Execute service-specific administration Service sdc_sc_ServicesAd

Administrator tasks, configure and execute services, Collabora ministrator
and view service execution results tion Ad
ministrator
Service Collaboration Services Expert Configure and execute services, and Service sdc_sc_ServicesEx
view own and shared service execution Collabora pert
results tion Expert
Service Collaboration Services Viewer Browse through the service explorer Service sdc_sc_ServicesVi
and view the shared service execution Collabora ewer
results tion Viewer
Scoping Digital Blueprint Create and edit digital blueprints and all Digital btc_bdts_DigitalB
Administrator associated tasks, company code scop Blueprint lueprintAdministr
ing, and transformation object scoping Adminis ator
trator
SAP Readiness Check Readiness Check View all SAP Readiness Check analyses Readiness imp_rc_AnalysisVi
Analysis Viewer Check ewer
Analysis
Viewer
SAP Readiness Check Readiness Create, edit, and delete SAP Readiness Readiness imp_rc_AnalysisAd
Check Analysis Check analyses Check ministrator
Administrator Analysis
Adminis
trator

7.3 Step 3: Set Up Landscape Management
As the last step of the required setup, services and systems (technical 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 on your managed cloud, on-
premise, and business services. This information is the basis for all SAP Cloud ALM apps.
To import your services or register your systems in SAP Cloud ALM, follow the steps described in the
respective subchapters:
• Services [page 39]

• Systems [page 40]
For use-case specific setup guidance for your solution, refer to Set Up Managed Services / Systems in the
SAP Cloud ALM for Operations Expert Portal.
7.3.1 Services
Depending on your subscribed service, there are different ways of importing or creating service information in
the Landscape Management app.
Automatic Import by SAP (Preferred)
For many subscribed services, related service information is imported automatically on a daily basis by the
System Landscape Information service.
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. If you don't want
to wait for the daily import, you can import your services on demand in the Status of Imports popover by
choosing Import My Subscribed SAP Services.
If your service hasn't been imported automatically, you may need to create the service information manually by
following the steps described in the section Manual Creation (Only If Required).
 Note
Additional information for global ultimate customers:
As a global ultimate customer (that is, a customer managing SAP cloud products that are subscribed
under multiple customer accounts, for example after an acquisition) 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.

Automatic Creation by Service Registration
There are push-enabled services that register themselves in SAP Cloud ALM (for example, SAP SuccessFactors
and SAP S/4HANA Cloud). These services are created automatically in the Landscape Management app as
part of the communication arrangement or registration. If the services already exist in the app, the technical
details are updated automatically.
Manual Creation (Only If Required)
The automatic import by SAP is the preferred way to import service information for services. However, you can
also manually add any additional services if necessary (for example, services of the type Unspecific Cloud
Service (HTTP) or SAP Ariba Cloud Integration Gateway).
1. Open the Landscape Management app.

2. On the Services page, choose Add.
3. Enter the following parameters:
• Name: Enter a name for the new service.
• Description: Optional, no entry required.
• Tenant ID: Enter the system number that is available in the System Data application on SAP ONE
Support Launchpad. The tenant ID is a unique identifier or alias for the tenant and is based on the
tenant name.
• Service Type: Select the service type in the dropdown list.
• Tenant Type: Select the tenant type in the dropdown list.
• Root URL: Enter the URL that needs to be used to access the API.
• External ID: Optional, no entry required.
• Customer Number: Optional, no entry required.
• Customer Name: Optional, no entry required.
4. Save the new service. You can now see it in the list.
After adding your service to the Landscape Management app, you need to establish a connection between the
service and SAP Cloud ALM to collect monitoring data. How this connection is established depends on the
individual service type. For detailed, service type-specific information on the managed services setup, refer to
Setup Managed Services / Systems in the SAP Cloud ALM for Operations Expert Portal.
7.3.2 Systems
Systems (technical systems) can be registered by running an ABAP report.
To register on-premise systems, run the ABAP report program /SDF/ALM_SETUP as described in Setup Steps
in the SAP ABAP On-Premise System on the SAP Cloud ALM for Operations Expert Portal.
When the registration in the system has been completed, the registered system is automatically displayed on
the Systems page. Once a technical system has been registered, a default logical system (client) is created and
displayed in the System Details.
 Note
If you want to create a logical system for two clients, run the ABAP report program from both clients.

8 Enabling Service Delivery
The Service Delivery Center in SAP Cloud ALM is a collaborative application. SAP exchanges service-related
information with your SAP Cloud ALM account, such as:
• SAP pushes relevant service orders and service results to your SAP Cloud ALM tenant.
• SAP and your SAP Cloud ALM tenant exchange preparation tasks, issues, and actions that are created for
your services.
• You can upload service-related documents and access uploaded documents for your service. Documents
are stored centrally within the SAP space.
To be able to use the service delivery applications, you need to give you consent to this data exchange.
When you open the Service Delivery Center application, you're prompted with a dialog that asks for your
confirmation.
For more information see SAP Cloud ALM for Service (SAP Support Portal).

Enabling Service Delivery PUBLIC 41
9 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.

42 PUBLIC Integration and Configuration Options
• Requesting SAP Cloud ALM [page 21]

Integration and Configuration Options PUBLIC 43
• Required Setup for SAP Cloud ALM [page 26]
• Integrating SAP Central Business Configuration [page 52]
• SAP S/4HANA Cloud, Private Edition and On-Premise Systems [page 57]
• Integrating the Test Automation Tool for SAP S/4HANA Cloud [page 68]
• Enabling SAP Cloud ALM API [page 44]
• Integrating Test Automation Providers [page 68]
• 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 55]
• Configuring Project User Permissions [page 53]
• Enabling Service Delivery [page 41]
9.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 service key and connect your SAP services and systems to your SAP Cloud ALM instance.
 Note
If you've requested SAP Cloud ALM on or after 2023-06-12, a service key that can be used to connect
managed services to SAP Cloud ALM for Operations monitoring applications was generated automatically.
You can skip these steps and access the service key in the SAP BTP cockpit or in the Landscape
Management app, as described in Managing Your Service Key [page 50].
If you want to set up transport management, you still need to carry out the following instructions to
create another service key, but you can reuse the created space and no longer have to configure your
entitlements.
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. If Cloud Foundry is not available in the menu, you can enable it by following
the steps described in Create Orgs.

 Note
If you've requested SAP Cloud ALM, your user has automatically received the required authorizations
during the creation of the global account and the subaccount.
Procedure
Carry out the following steps to enable SAP Cloud ALM API:
Create a Space
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.
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. Choose Save.
Maintain an Instance

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.

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.
10. When your instance has been created or updated, click on it.
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. In the top right corner, choose  (Actions) and select Create Service Key.

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)

 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
9.1.1 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.
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:

2. Select the global account that contains your SAP Cloud ALM entitlement and then open the subaccount
that contains your SAP Cloud ALM subscription.
4. Select the space that contains your service key.
5. Choose Services Instances .
6. Select the instance that contains your service key.
7. Under Credentials, open your key and choose Download.
8. In the SAP Cloud ALM launchpad, open the Landscape Management app.
9. Open the configuration ( ) and expand the section SAP Cloud ALM Service Key.
10. Choose  (Add).
11. 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.
12. 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.
9.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.

9.3 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.
Procedure
Technical Setup
Create an endpoint for SAP Central Business Configuration by carrying out the following steps:
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.
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
Integrating SAP Cloud ALM with SAP Central Business Configuration
9.4 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.
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.
9.5 Integrating the Cloud Integration Automation Service
The Cloud Integration Automation service (CIAS) 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

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 31].
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
9.6 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.

9.6.1 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.
In order 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 have to
establish a connection between SAP Cloud ALM and the Change and Transport System (CTS). This
guide explains all steps that are needed to set up this connection.
SAP Cloud ALM supports the integration of Change and Transport System (CTS) for SAP S/4HANA
Cloud, private edition, and SAP NetWeaver Application Server for ABAP on-premise.
 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 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 22 install 3310406 and follow SAP Note 3322679 .
 Note
It's recommended to use SP22.
• For ST-PI 740 SP 21 install corrections 3240966 and follow SAP Note 3322679 .
 Note
It's recommended to install collective corrections when available.
Check that the profile parameter icm/HTTPS/client_sni_enabled is set to TRUE, as described in SAP
Note510007 .
 Note
For the profile parameter check, you can use the transaction RZ11 in the managed system

Check that profile parameterssl/client_ciphersuites is set according to section 7 of SAP Note
510007 . Make sure that DigiCert Global Root CA is imported in STRUST underSSL Client
(Anonymous) and SSL Client (Standard)
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 you plan to use as data collection background job user.
• 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
Do not forget to activate role SAP_BC_TRANSPORT_ADMINISTRATOR before usage 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

As a first step, you need to create a space and configure your entitlements in the subaccount containing your
SAP Cloud ALM subscription. To do this, perform the steps described in Enabling SAP Cloud ALM API [page
44].
Configuration of the PUSH Data Provider

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.
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 should now be 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.
• Currently supported landscapes:
• Landscapes with at least two systems per route (also virtual systems)
• Landscapes with basic consolidation and/or delivery targets, for example TMS quality
assurance or transport workflow. These are optional workflows.
For more information about these workflows, refer to TMS Quality Assurance and Transport
Workflow.
• Landscapes with client-specific transport routes or using the Central Technical
Configuration (CTC). Using CTC is optional.
• Support of several transport groups
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 to-be-imported requests from SAP Cloud ALM and triggers the import job.

• It's only necessary to set up on consolidation and target systems for import (that is, QA and PRD
systems)
 Note
Commonly, authorization-checks are performed in the system in which a change happens. In case of
the 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:
 Caution
If you want to change the transport configuration in the Transport Management system, make sure that all
current changes are completed and deployed to the production system. Additionally, the transport buffers
should be empty. Otherwise, you need to adjust the respective transport buffers manually.
Configuration of Client-Dependent Use Cases
To enable the release of transports within an SAP Cloud ALM feature, you have to execute the following setup in
each development client you're using:
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.
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:
9.6.2 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.
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.
• 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.

If you're not yet subscribed to the service, perform the following steps:
4. Go to Entitlements and choose Configure Entitlements.
5. Search for the Cloud Transport Management service in the search bar. If no results are shown in the
service list, choose Add Service Plans.
6. Select Standard (Application) Standard Plan and choose Add 1 Service Plan.

7. Choose Save.
8. Go to Instances and Subscriptions and select the Cloud Transport Management service.
9. Choose Create.

10. Select the Standard plan.
11. Choose Create.
You're now subscribed to the SAP Cloud Transport Management service.
12. Assign transport management roles to your user and to your team members in the User Management
app in SAP Cloud ALM. Usually, the two roles you need are Transport Management Viewer and
Transport Management Operator.
For more information, refer to Assign Roles to Users in SAP Cloud ALM.
With these roles, you can access the Cloud Transport Management service from within your
subaccount in the SAP BTP cockpit by choosing Go to Application.

13. To create transport nodes, refer to Create Transport Nodes.
 Note
You have to use auto forward and upload application content to dev node manually.
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 44].
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.
To set up the HTTP destination, refer to 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://eu10.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.

9.7 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.
9.7.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 test automation tool for SAP S/4HANA Cloud and created test plans.
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.
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.
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.
• 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.
Related Information
Test Automation Tool for S/4HANA Cloud - Additional Info

Maintain Communication Systems
9.7.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.

Prerequisites
• Your user in SAP Cloud ALM has the role Global 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 terms and conditions are stored on SAP Support Portal. You can read or download them from there at
any time.

3. Choose Set Up Tricentis Test Automation for SAP integrated with SAP Cloud ALM.
4. Automatically, 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 Tricentis Test Automation
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 test cases will then be authored in Tricentis Test Automation for SAP, as described in the Tricentis
documentation.
Related Information
Tricentis Test Automation for SAP integrated with SAP Cloud ALM
Tricentis Test Automation for SAP online documentation
Tricentis Test Automation execution agents
Tricentis test automation for SAP usage rights

10 Application Configuration
To adapt the solution to reflect your business processes and parameters, you can make various configuration
settings.
For several apps in SAP Cloud ALM, additional setup steps are required. You can find detailed guidance in the
SAP Cloud ALM for Implementation Expert Portal , the SAP Cloud ALM for Operations Expert Portal , and
the SAP Cloud ALM for Service Expert Portal on SAP Support Portal.
Once you've signed in to SAP Cloud ALM, you can also find application-specific personalization and
configuration options by choosing  (Configuration) at the top-right corner of many apps.

Application Configuration PUBLIC 73
11 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

74 PUBLIC Launching Your Systems from SAP for Me
12 Finding Help
SAP Cloud ALM offers different types of assistance to guide you through additional configuration activities and
to help you understand the capabilities of SAP Cloud ALM apps.
In-App Help
Each app in SAP Cloud ALM provides on-screen explanations of key features and user interface elements.
When you're signed in, you can switch on the help by choosing  (Open Help) at the top right of the screen, or
by pressing F1 on your keyboard.
The following types of help are available:
• (Help Topics): Quick reference information about specific user interface elements to help you perform
your tasks
• (Guided Tours): Guided tours of more complex procedures
• (What's New): Information about new features
SAP Help Portal
You can find an overview of all related documentation at SAP Cloud ALM.
SAP Support Portal
• SAP Cloud ALM

• SAP Cloud ALM for Implementation
• SAP Cloud ALM for Operations

Finding Help PUBLIC 75
13 Accessibility
To optimize your experience of SAP Cloud ALM, we provide features and settings that help you use the software
efficiently. Learn more about these features and settings and find out how to use them.
 Note
SAP Cloud ALM is based on SAPUI5. For this reason, accessibility features for SAPUI5 also apply. See the
accessibility documentation for SAPUI5 on SAP Help Portal at Accessibility for End Users.
For more information on screen reader support and keyboard shortcuts, see Screen-Reader Support for
SAPUI5 Controls and Keyboard Handling for SAPUI5 Elements.
Use High Contrast Black Theme
SAP Cloud ALM offers a high contrast black theme.
Context
This feature is recommended for users with need for high contrast themes.
Steps
1. In the header toolbar, choose Your Name Settings .

2. Under Appearance, select the theme High Contrast Black.
3. Once you've saved your changes, SAP Cloud ALM refreshes with the theme of your choice.

76 PUBLIC Accessibility
14 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.
14.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
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.

Data Protection and Privacy PUBLIC 77
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.
14.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.
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.

78 PUBLIC Data Protection and Privacy
 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.
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.
14.3 Email Notifications in SAP Cloud ALM
Email notifications can be set up for named users (that is, users that are maintained in the Identity
Authentication tenant) and for unnamed users. Only the recipient email ID is stored as part of the Notification
Management app.
Giving Consent
As soon as new recipients are added to the notification management, they receive an email from cloudalm-
notification@sap.com, 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

Data Protection and Privacy PUBLIC 79
• Recipients whose consent expired
14.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.
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.

80 PUBLIC Data Protection and Privacy
15 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.

Security PUBLIC 81
15.1 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.

82 PUBLIC Security
Secure Op Default
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.

Security PUBLIC 83
Secure Op Default
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
33]
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.

84 PUBLIC Security
Secure Op Default
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 39]
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 53]
created project:
project is
• Public
Public.
• Restric
Any addi ted
tional
• Private
projects
that you
create man
ually are set
to
Restricted
by default.

Security PUBLIC 85
Secure Op Default
Business Recom Roles and KPI Access You can re Use access CALM-
Process mended Authoriza Control strict the groups to BM-0001
Monitoring tions data access grant users
of a defined access only
user group to data rele
to a particu vant to their
lar business tasks.
process
scope.
By default,
access con
trol is deac
tivated.

86 PUBLIC Security
15.1.1 Explanations of Table Properties
Table Headings
Secure Op Default

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 Not
ties table.
sions, and e
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.

Security PUBLIC 87
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.

88 PUBLIC Security
16 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.

Account Termination PUBLIC 89
17 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 90]

• During the Provisioning [page 90]
• After the Provisioning [page 91]
• Identity Authentication [page 92]
• User Management [page 93]
• Your SAP Cloud ALM Tenant [page 94]
• Further Support [page 95]
• Related Information [page 96]
Before the Provisioning
Issue Resolution
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.
During the Provisioning
Issue Resolution
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 .

90 PUBLIC Troubleshooting and FAQ
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 requested SAP Cloud ALM and want to assign Refer to 3248116 .
additional administrators who can complete the
setup of SAP Cloud ALM.
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.

Troubleshooting and FAQ PUBLIC 91
Identity Authentication
Issue Resolution
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.
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.

Issue Resolution
When you log on to SAP Cloud ALM, you can Refer to SAP Note 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 Your Identity

Authentication Service [page 28].
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 31].

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.
Your SAP Cloud ALM Tenant
Issue Resolution
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 26] and that you've activated your user profile in
the Identity Authentication tenant.
You can find a link in the activation email that was sent to you when
you requested SAP Cloud ALM or when the tenant administrator
created a user for you. If you can't find the activation email, go to your
Identity Authentication tenant, enter your email address, and choose
Forgot password. You will receive a new activation email.
For more information, refer to KBA 3117604 .
You can log on to SAP Cloud ALM but do not see Refer to KBA 2982909 .
any apps.
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.

Issue Resolution
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.
You want to set up a second SAP Cloud ALM tenant. Currently, it's possible to request only one SAP Cloud ALM tenant per
entitled customer number.
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.
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 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 decommission of SAP Cloud ALM isn't yet available. How
ever, you can use a housekeeping job to delete services from the
Landscape Management app.
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

Related Information
KBA 3270970 - Most Common Onboarding Issues
Troubleshooting for Managed ABAP Systems (SAP Support Portal)

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.

Important Disclaimers and Legal Information PUBLIC 97
www.sap.com/contactsap
© 2023 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

Setup and Administration For SAP Cloud ALM

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Setup and Administration For SAP Cloud ALM

Uploaded by

Copyright:

Available Formats

Administration Guide | PUBLIC

Setup and Administration for SAP Cloud ALM

THE BEST RUN

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

6 Requesting SAP Cloud ALM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

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

8 Enabling Service Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

9 Integration and Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

10 Application Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

11 Launching Your Systems from SAP for Me. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Setup and Administration for SAP Cloud ALM

14 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

17 Troubleshooting and FAQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Setup and Administration for SAP Cloud ALM

You need a GitHub account to use these options.

Setup and Administration for SAP Cloud ALM

SAP Cloud ALM is available in the following languages:

We recommend that you use Google Chrome.

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

Setup and Administration for SAP Cloud ALM

Sufficient resources for standard use are included, per default:

• SAP HANA memory: 8 GB

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

Extension of Fair Use

Setup and Administration for SAP Cloud ALM

• What Is the Consumption-Based Commercial Model?

SAP Cloud ALM, API Outbound Volume

Setup and Administration for SAP Cloud ALM

SAP Cloud ALM SAP Cloud ALM

SAP S/4HANA Cloud Implementation Process Manage­

More under Business Process Content

Setup and Administration for SAP Cloud ALM

More under Business Process Content

SAP SuccessFactors Implementation Process Manage­

More under SAP SuccessFactors Proc­

Setup and Administration for SAP Cloud ALM

SAP Marketing Cloud Implementation Process Manage­ https://rapid.sap.com/bp/#/

SAP Fieldglass Implementation Process Manage­ SAP Fieldglass Vendor Management

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

Intelligent Enterprise – Implementation Implementation Process Manage­

Setup and Administration for SAP Cloud ALM

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

• SAP Activate Methodology for

SAP SuccessFactors Implementation Task Management Task template available:

• SAP Activate Methodology for the

Intelligent Enterprise – Implementation Implementation Task Management

SAP Ariba Implementation Task Management

SAP Business Network Implementation Task Management

SAP Fieldglass Implementation Task Management

SAP S/4HANA Cloud Implementation Requirement Man­

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

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

SAP SuccessFactors Implementation Requirement Man­

Intelligent Enterprise – Implementation Implementation Requirement Man­

SAP Ariba Implementation Requirement Man­

SAP Business Network Implementation Requirement Man­

Setup and Administration for SAP Cloud ALM

SAP Fieldglass Implementation Requirement Man­

SAP S/4HANA Cloud Implementation Documents

SAP S/4HANA Cloud, private edition Implementation Documents

SAP S/4HANA (on-premise) Implementation Documents

SAP SuccessFactors Implementation Documents

SAP S/4HANA Cloud Implementation Process Manage

SAP SuccessFactors Implementation Process Manage

More under SAP SuccessFactors Proc

SAP Marketing Cloud Implementation Process Manage https://rapid.sap.com/bp/#/

SAP Fieldglass Implementation Process Manage SAP Fieldglass Vendor Management

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

Intelligent Enterprise – Implementation Implementation Process Manage

SAP S/4HANA Cloud Implementation Requirement Man

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

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

SAP SuccessFactors Implementation Requirement Man

Intelligent Enterprise – Implementation Implementation Requirement Man

SAP Ariba Implementation Requirement Man

SAP Business Network Implementation Requirement Man

SAP Fieldglass Implementation Requirement Man

SAP Build Work Zone Implementation Deployment Man Application content

SAP Build Process Automation Implementation Deployment Man MTA

More under Business Process Monitor

More under Business Process Monitor

More under Business Process Monitor

More under Business Process Monitor

More under Business Process Monitor

More under Business Process Monitor

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