SLSC Implement S4HANA Public Edition with SAP Cloud ALM - Best Practice V5.pdf

Public
SAP, March 2024
Implement SAP S/4HANA Cloud Public Edition with
SAP Cloud ALM – Best Practice

2
Public
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service
or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.
Disclaimer

3
Public
SAP Cloud ALM is a constantly evolving SAP solution with daily deployments.
Therefore this material can only be an incomplete guideline how to use the functionality.
It’s not possible to keep all information completely up-to date. This is specifically true for the screenshots.
Nevertheless it makes sense to combine methodical and hands-on information for a SAP Solution specific
implementation scenario. This helps to understand which of the functionalities are meaningful be used, in
which order, and how the project progress can be tracked.
The generic documentation and always current description of the SAP Cloud ALM functionality can be found at
the SAP Help Portal: https://help.sap.com/docs/cloud-alm/applicationhelp/implementation
Note before usage

4
Public
1. Introduction
1. Architecture & Process Flow
2. Use Cases & Workflow
3. How to run a project with SAP CALM
2. How to implement SAP S/4HANA Cloud Public Edition with SAP Cloud ALM
1. Prepare – Project Setup
2. Explore – Fit/Standard Workshops
3. Realize – Plan Build
4. Realize – Build
5. Realize – Test Management
6. Realize – Defect Management
7. Build Release & Deploy
3. Additional Information
Agenda

5
Public
Project leads benefit from:
• Instantly available project management platform, no deployment or configuration activities needed
• Fast onboarding of and task distribution to your project team
• Agile configuration with clear timelines & scope
• Faster test planning based on predefined solution processes
• Minimized risk by built-in transparency by predefined reporting and traceability dashboards
Consultants benefit from:
• Clear worklist based on named project tasks, user stories and requirements
• Transparency by one central access point to all relevant project data
• Accelerated time-to-value by predefined SAP Activate content and SAP’s best practice solution processes
• Predefined user stories and other content assigned to solution processes
• Efficient test execution and defect creation
1.1 SAP Cloud ALM benefits in SAP S/4HANA Cloud Public Edition context
Benefits by consultants and project leads point of view

6
Public
1.1 Requirement driven implementation
End-to-end implementation model

7
Public
High-level process flow
Deployments to production in releases
Agile implementation
in sprints
Go Live
Project
Start
Process
Management
Fit-2-Standard
Workshops
Process Scoping
& Viewer
Process
Authoring
Requirements
Collection
Documentation
Rich Text based
documentation
Status & Approval*
Document
Management
Integration*
Project Planning
Task Distribution
Task Templates
Gantt Chart
Landscape
Project & Task
Management
Project Execution
& Tracking
Requirements
Refinement
Configuration*
Extension
Management*
Integration
Management*
Test
Orchestration
Test
Planning
Test
Preparation
Test Execution
Manual
Testing
Integration of
test automation
providers
Defect
Management
Change
Enablement
Change
documentation &
reporting
Traceability &
Audit Trail
Deployment
Planning
Feature
Delivery
Deployment
Automation &
Confirmation
Deployment
Orchestration
SAP
Standard
Test Cases
SAP Activate
Roadmaps
SAP Process
Content
This is the current state of planning and may be changed by SAP at any time.
* planned

8
Public
The following slides describe the main SAP CALM capabilities:
1. To be used in the context of a specific project, e.g.:
§ Solution Processes
§ Tasks
§ Requirements
§ User Stories
§ Features
§ Test Management
§ Analytics
2. To be used cross project, e.g.:
§ Roles
§ Workstreams
§ Tags
§ Systems
§ Releases
1.1 Architecture
Project specific and project independent capabilities

9
Public
Cross
Project
Systems
Landscape
assignments
Tags
Workstreams
Project
Team 1
Scope 1
Sub-Tasks
User Story
Project Tasks
Process
Defect
Test Case
Requirement
User Story Test Case
Project Tasks
Sprint 1 Sprint 2
Run
Deploy
Realize
Explore
Discover Prepare
Project Tasks
Task Template
Project Tasks Project Tasks
Sub-Tasks
Sub-Tasks
Deployment
Plan
Roles
Release 1 Release 2
1.1 Project entities
Usage of entities within and cross projects
Customer
Processes
Feature
Document
Process
Test Plan
Sprint 3

10
Public
Project
Scope
Process
Requirement
Note
Task
Sub
Task
Test
Case
Feature
Defect
Work
stream
Deliverable
Team
Assigned
Role
Assignee
Timebox
Release
Tags
Project M M M M M (X) M M M X X
Scope M M X M X (X) M X X
Process M M X X X (X) X
Note M M X
Requirement M X X X X (X) X X X X X X X X
User Story M X X X X (X) X X X X X X X X X X
Task M X X X X X X X X X X X X X X X
Sub Task (X) (X) (X) (X) (X) X (X) (X) X X X (X) X (X) + X
Test Case M M X X X X
Defect M X X X X X X (X) X
Feature M X X X X X X
M = mandatory
X = possible
X = typically used
(x) = inherited
1.1 SAP cloud elements relations & categories
Entities to be maintained in a project - Example
Who When
What

11
Public
Business
Process
Expert
Configuration Expert
Consulting Expert
Test Lead
Testing Expert
Create/Plan
User Stories for
Developments
Process &
Complete User
Stories
Process Defects
Create Test
Cases
Collect and
Document
Requirements
Project
Lead
Execute Test
Cases
Setup Project
Approve
Requirements
Confirm
Requirements
Requirement
Ready for Test
Onboarding
Team Members
Plan Releases &
Timeboxes
Complete Project
Tasks
Select Process
Scope
Detailed process flow
Change and
Deployment Lead Create Features
Create/Assign
Transports
Deployment to
QAS
Deployment to
PRD
Manage Test
Plan & Assign
Testers
Analytics and Traceability
Run
Deploy
Realize
Explore
Discover Prepare
Sprint 1 Sprint 2 Sprint 3
Sprint 1 Sprint 1
Manage and
Execute Project
Tasks
• Test Execution Analysis
• Defect Reporting
• User Story Traceability
• Burn Up Chart
• Solution Process Traceability
• Requirement Traceability
• Requirement Distribution
• Project Progress Reporting
• Task Distribution
• Task Trend Analysis
• Releases and Timelines
• Feature Traceability

12
Public
The used project entities have impact on the usage of tagging, naming conventions, test setup, etc.
1.1 CALM integration model – Requirement centric workflow
Relations in detail
Requirement User Story
Release/
Deployment
Plan
create/
assign
create/assign
(1:n)
assign
(n:1)
(n:m)
Feature
create/assign
(n:1)
create/assign
(1:n)
Test Case
create/assign
(n:m)
create/assign
(n:m)
Transports
create/assign
(1:n)
Test Plan
assign (n:m)
create
(1:n)
assign
(n:1)
Solution
Process
create/assign
(1:n)
always inherited
Documents
Landscape
Cluster
assign
(n:1)
Project
create/assign
(1:1)
Defect
(n:m)
assign
(n:m)

13
Public
1.1 CALM integration model – Documents and IT related entities
Planned document assignments
Release/
Deployment
Plan
Feature
Test Case
Transports
Test Plan
Solution
Process
Documents
Landscape
Cluster
Project
Defect
assign
(n:m)
assign
(n:m)
assign
(n:m)
assign
(n:m)
= planned

14
Public
1. Introduction
Agenda

15
Public
SAP Cloud ALM supports implementation projects independent of the to be implemented
SAP/non-SAP solution. These functions are listed in the following table:
1.2 Implementation use cases
Generally applicable SAP Cloud ALM functions
Non-SAP SAP ARIBA,
Business Network,
Fieldglass,
Success Factors,
Concur,
Sales, Service, Analytics Cloud,
…
S/4HANA Public Cloud S/4HANA Private Cloud
Management of organizational tasks
(Project tasks)
Process modelling
Document management
Management of IT related tasks
(Requirements, user stories, sub-tasks)
Test planning, preparation & execution
Test automation integration
Deployment organization & control
(Timeboxes & features)
Predefined reporting & analytics

16
Public
Dependent on the to be implemented SAP/non-SAP solution, the usage of SAP Cloud ALM has
specific strengths listed in the following table:
1.2 Implementation use cases
Differences in SAP Cloud ALM usage
Non-SAP SAP ARIBA,
Business Network,
Fieldglass,
Success Factors,
Concur,
Sales, Service, Analytics Cloud,
…
S/4HANA Public Cloud S/4HANA Private Cloud
Activate roadmaps
DDA integration for initial process
scoping (only in combination with S/4HANA Cloud)
Best practice processes
Predefined test cases
Manual & automated Manual
Integrated test automation tool
Tricentis Tricentis SAP & Tricentis Tricentis
Integrated transport system
Partially supported by Cloud TMS
(check current state here)
ATO CTS
CBC integration
(high – level)

17
Public
In the S/4Hana Cloud implementation context there are several workflows possible, e.g.:
1. User story leading workflow for standard implementation
• Implementation of predefined, standard user stories
• Direct implementation, few documentation necessary
• Allows usage of predefined test cases
2. Requirement driven without user story
• Implementation of standard configuration, e.g. for public cloud with CBC
• Direct implementation, not needed IT alignment
• Changes are documented in features together with the related transports
3. Requirement driven workflow for customer specific requirements (best practice)
• Documentation of standard configuration (typically summarized) and customer specific requirements
• Optional requirement approval and planning process
• Requires customer specific test cases
• In deployment simple, 1:1 relation of requirement:feature
4. Requirement driven incremental workflow for customer specific requirements
• Documentation of standard configuration (typically summarized) and customer specific requirements
• Includes large requirements developed/configured over several deployments
• Optional requirement approval and planning process
• Requires customer specific test cases
• In deployment simple, 1:n relation of requirement:feature
1.2 Use cases and workflows

18
Public
User Story Leading
w/o Requirement
§ Delivered via feature
§ No usage of
requirements
1.2 Implementation use case overview
User story leading (without requirement)
§ Predefined user stories
per upload, e.g. typical for
Ariba implementations by
SAP Consulting or partner
led implementations
Process
Scenario
Requirement Leading
w/o user story
§ Delivered in
one feature
per requirement
§ No usage of
user stories
§ Agile implementation
§ S/4HANA Private Cloud
Edition / BTP
development projects
Requirement Leading
Incremental
§ Requirement break down in
user stories
§ Delivered via
multiple features
per requirement , e.g. to
document longer lasting
developments with BTP or
to separately track
corrections
Edition / BTP
§ Large requirements to be
delivered in multiple
deployments
Requirement Leading
Best Practice
§ To clarify more
complex Requirement
break down in user
stories
§ Delivered in
one feature
per requirement
Edition / BTP

19
Public
AT/FIT
Open In Progress
User
Story
DEV QAS PRD
Feature
In Testing Deployed
In
Specification
In
Implementation
1.2 E2E implementation status flow – including landscape
User story leading (without requirements)
Test Passed
= Guided status change
= Free flow status change
Done
Ready for
Production
Solution
Process
Realization Production

20
Public
User Story Leading
w/o Requirement
§ No usage of
requirements
Requirement leading (without user story)
led implementations
Process
Scenario
Requirement Leading
w/o user story
§ Delivered in
one feature
per requirement
§ No usage of
user stories
Edition / BTP
Requirement Leading
Incremental
user stories
§ Delivered via
multiple features
to separately track
corrections
Edition / BTP
deployments
Requirement Leading
Best Practice
§ To clarify more
complex Requirement
break down in user
stories
§ Delivered in
one feature
per requirement
Edition / BTP

21
Public
AT / FIT
Requirement leading (without user story)
In
Refinement
Requirements
User
Story
Confirmed
DEV QAS PRD
In
Realization
Feature
In Testing
In
Specification
In
Implementation
Deployed
Test Passed
Ready for
Deployment
Approval
In Approval
In
Testing

22
Public
User Story Leading
w/o Requirement
§ No usage of
requirements
Requirement leading (best practice)
led implementations
Process
Scenario
Requirement Leading
w/o user story
§ Delivered in
one feature
per requirement
§ No usage of
user stories
Edition / BTP
Requirement Leading
Incremental
user stories
§ Delivered via
multiple features
to separately track
corrections
Edition / BTP
deployments
Requirement Leading
Best Practice
§ To clarify more
complex Requirement
break down in user
stories
§ Delivered in
one feature
per requirement
Edition / BTP

23
Public
Open
AT / FIT
Requirement leading (best practice)
In
Refinement
Open In Progress Done
Requirements
User
Story
Confirmed
DEV QAS PRD
In
Realization
Feature
In Testing
In
Specification
In
Implementation
Deployed
Test Passed
Ready for
Deployment
Approval
In Approval
In
Testing

24
Public
User Story Leading
w/o Requirement
§ No usage of
requirements
Requirement leading (incremental)
led implementations
Process
Scenario
Requirement Leading
w/o user story
§ Delivered in
one feature
per requirement
§ No usage of
user stories
Edition / BTP
Requirement Leading
Incremental
user stories
§ Delivered via
multiple features
to separately track
corrections
Edition / BTP
deployments
Requirement Leading
Best Practice
§ To clarify more
complex Requirement
break down in user
stories
§ Delivered in
one feature
per requirement
Edition / BTP

25
Public
AT / FIT
Open
Requirement leading (incremental)
Open In Progress
Requirements
User
Story
DEV QAS
Feature
1
Ready for
Production
Deployed
In
Specification
Ready for
Production
Deployed
In
Specification
Feature
2
Confirmed
In Testing
Done
In
Refinement
In
Realization
Approval
In Approval Test Passed
PRD
In
Implementation In Testing
In
Implementation In Testing
In Testing Test Passed

26
Public
SAP Cloud ALM allows to adjust usage and workflows to the project needs. But to ensure a seamless
E2E traceability, it makes sense to follow the recommendations of this best practice.
In addition, it’s also possible to use different workflows in different project phases. E.g. it might make sense to:
• start with a lean user story leading workflow for standard configuration
• and to proceed with the requirement driven workflow to do round ups and customer specific customizing/developments
in a later project phase
The requirement driven incremental workflow can be used to keep the requirement specification in one
document, or if it’s for time scheduling reasons necessary to split a bigger deployment of configured/developed
functionality. But this results in more complex testing and traceability, so it’s better to keep the 1:1 relation
between requirement and feature.
You are not forced to use all capabilities. SAP Cloud ALM allows a flexible usage of it’s capabilities, e.g. is it
possible to only use the best practice processes in combination with the test capabilities.
1.2 Remarks

27
Public
1. Introduction
Agenda

28
Public
1.3 Essential steps to successfully use SAP Cloud ALM
SAP Cloud ALM for Implementation
Project roles and setup
§ Define project roles
§ Organizational setup
Proper assignment and
tracking of project tasks
Deliverable per status
§ Define deliverables for each
status
§ Procedures for status
settings
Standards and attributes
for used entities
§ Tags, naming conventions
Proper reporting and
filtering
Test Management
§ Test approach
§ Test case management
(types, classifications)
Efficient test planning,
execution and reporting
Deployment concept
§ Roles in deployment
§ Deployment automation
§ Deployment strategy
Deployment governance
and automation
General project setup
§ Deployment plan
§ Timebox setting
§ Task template
§ Project accessibility
Basic project structure
Implementation approach
§ Define leading entity
§ Define needed entities
§ Documentation standards
Proper breakdown /
distribution of tasks,
traceability
Business process structure
§ Scope definition
§ Process hierarchy
Project structure
according to business
processes
Input / boundary
conditions
§ Agile / waterfall
§ Project scope and products
to be implemented
§ System landscape / release
planning
§ Setup of project team
§ Tool / content integration
§ Compliance requirements
§ …

29
Public
1.3 Essential steps to successfully use SAP Cloud ALM
SAP Cloud ALM for Implementation
Reporting & Traceability
Input / boundary
conditions
§ Agile / waterfall
§ Project scope and products
to be implemented
§ System landscape / release
planning
§ setup of project team
§ Tool / content integration
§ Compliance requirements
§ …
Project roles and setup
§ Define project roles
§ Organizational setup
Proper assignment and
tracking of project tasks
Deliverable per status
§ Define deliverables for each for
each status
§ Procedures for status
settings
Standards and attributes for
used entities
§ Tags, naming conventions
Proper reporting and
filtering
Test Management
§ Test approach
§ Test case management (types,
classifications)
Efficient test planning,
execution and reporting
Deployment concept
§ Roles in deployment
§ Deployment automation
§ Deployment strategy
Deployment governance and
automation
General project setup
§ Deployment plan
§ Timebox setting
§ Task template
§ Project accessibility
Basic project structure
Implementation approach
§ Define leading entity
§ Define needed entities
§ Documentation standards
Proper breakdown /
distribution of tasks,
traceability
Business process structure
§ Scope definition
§ Process hierarchy
Project structure according
to business processes

30
Public
1. Introduction
1. Prepare – Onboarding & Technical Setup
Agenda

2.1 Prepare – Onboarding & Technical Setup
2.1.1 Maintain Identity Authentication Service (IAS)
2.1.2 Maintain authorization roles for project members
2.1.3 Select system landscape
2.1.4 Deployment orchestration and integration
Project Administrator

32
Public
2.1.1 Onboarding to SAP Cloud ALM
ü Maintain users in IAS
Details: help.sap.com

33
Public
2.1.1 Setup and administration guide
https://help.sap.com/docs/cloud-alm?task=use_task

34
Public
Procedure
1. In the tenant's administration console for Identity Authentication, open the
User Management
2. Choose + Add User.
3. Fill in the required fields.
4. Remember the email address, as you need it to assign roles to the user later.
5. Choose Save.
6. Select Send activation e-mail.
7. Save your entries.
Prerequisites
• Your Identity Authentication
tenant has been activated.
• In your Identity Authentication
tenant, you have a user with the
role Manage Users.
If you don't have this authorization,
the tenant administrator can assign
the role to you. If you don’t know
who your tenant administrator is,
create an incident on component
BC-IAM-IDS.
2.1.1 Required setup for SAP Cloud ALM
Onboard users in your identity authentication service
Before you can use SAP Cloud ALM, you need to create or import users in the Identity
Authentication tenant.
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.

35
Public
★ Make sure you follow the required setup
described on the SAP HELP PORTAL or follow
Video-Guided Setup
★ Be aware: Cloud ALM needs a productive
Identity Authentication tenant
★ Partners need to use S-User assigned to correct
customer number!
★ Check Additional Resources:
Blog First login to SAP Cloud ALM
YouTube Video How to Request SAP Cloud ALM
Expert Portal SAP Cloud ALM for Implementations
Onboarding Support

36
Public
Project roles
What is your role?
Textual definition of your purpose in the
project
Defined in SAP Cloud ALM – pre-delivered
roles based on SAP Activate, definition of
customer specific roles possible
Authorization roles
What are you allowed to do?
View or Edit authorization for different
purposes
Roles available in SAP Cloud ALM User
Management are predefined as role
collections in the subaccount in the SAP BTP
cockpit (SAP Authorization and Trust
Management service).
Identity
Who are you?
User ID, email, first name, last name,
password
Managed by the Identity Authentication
Service (IAS)
2.1.1 Identity, authorization roles, project roles

37
Public
2.1.2 Assign roles to users
ü Assign authorization roles to the users

38
Public
Assign authorization 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…
… or in the SAP BTP cockpit.
… in the SAP Cloud ALM User Management app
(recommended)

39
Public
Assign authorization roles to users in SAP Cloud ALM
Procedure
1. Access SAP Cloud ALM
2. Open app User Management (in Administration section)
3. To go to the user list, choose (Users)
4. Choose Add User
5. Enter the user ID and/or email address
6. Select a type for your user
7. Assign one or multiple authorization roles to the user
8. Save
Prerequisites
• The identities of the users to whom you want to assign roles already exist in the
identity provider (IAS)
• Your user has the authorization role Cross Global Administrator or User
Administrator

40
Public
2.1.2 SAP Cloud ALM user management 1/4
Build
SAP Cloud ALM offers a simplified user management approach by using predefined authorization roles.
The following roles are relevant for SAP Cloud ALM Build and its administration:
Cross Topics
Capability Role Description
Cross Application
Global Administrator Create and manage all SAP Cloud ALM objects, except for personal or sensitive data
Global Auditor View all SAP Cloud ALM objects, except personal or sensitive data
User & Access
Management
User Administrator Create and manage users, assign and approve authorizations
User Viewer View users and authorization assignments
Tag Management
Tag Administrator Create, update, merge and centrally delete tags, view tag usage and organize tags
into groups
Tag Viewer View tags, tag groups and tag usage
Landscape
Management
Landscape Management Security
Administrator
Manage certificates

41
Public
Build
Implementation
Change & Deployment
Management
Change Manager Approve features for production deployment
Deployment Manager Deploy transports into test and production systems
Project Management Project Administrator Manage projects, deployment plans, tasks, scopes, requirements, features, notes,
test cases, and defects
Project Lead Edit projects and all associated tasks, scopes, requirements, notes, and test cases.
View the landscape
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
Process Management Process Author Create, edit, and delete custom solution processes
SAP Readiness Check
Readiness Check Analysis Administrator Create, edit, and delete SAP Readiness Check analyses
Readiness Check Analysis Viewer View all SAP Readiness Check analyses

42
Public
Build
Implementation
Cloud Integration
Automation Service*
Cloud Integration Administrator Access My Inbox, work on assigned tasks, plan, monitor, manage and review
integration scenario execution
Cloud Integration Expert Access My Inbox, work on assigned tasks
Cloud Integration Viewer View Scenario Execution Monitoring, work on assigned tasks
Cloud Transport
Management**
Transport Management Operator Create, edit and delete transport nodes and transport routes
Transport Management Viewer View transport nodes and transport routes
* Application Cloud Integration Automation Service
** Application Cloud Transport Management

43
Public
Build
Business Transformation Center
Scoping
Digital Blueprint Administrator Create and edit Digital Blueprints and all associated tasks, company code scoping,
transformation object scoping
Digital Blueprint Viewer Consume Digital Blueprints and all associated tasks, company code scoping,
transformation object scoping

44
Public
2.1.2 Authorization Details
Roles for the Feature Workflow
The following table shows you which authorization roles can perform status actions in a Feature:
Status Action Project Admin Project Lead Change Manager Project Member
Set to "Not Planned"
Start Implementation
Handover to Test
Approve for Production
Confirm Deployment

45
Public
Roles for Transport Activities in the Feature
The following table shows you which authorization roles can perform transport activity in a Feature:
Activity Project Admin Project Lead Deployment Manager Project Member
(Un)-assign transports
Create transports
Create ToCs
Release transports
Deploy transports

46
Public
Roles for Feature Related Activities
The following table shows you which authorization roles can perform Feature related activities:
Activity
Project
Admin
Project Lead Project Member Project Viewer
Display Feature & history
Create Feature
Edit Feature
Delete Feature
Create user stories / project tasks
Assign + unassign user stories

47
Public
2.1.3 Setup landscape
ü Maintain technical system (tenant) information

48
Public
2.1.3 Landscape Management
Overview
§ Store and manage
technical information
about cloud services
and on-premise systems
in your IT infrastructure
§ Define your project
landscape according to
your implementation
scenario

49
Public
Technical Prerequisites - Connectivity
§ Public Cloud Tenants are
automatically connected
and displayed in SAP
Cloud ALM Landscape
Management
§ On-Premise Systems and
Private Cloud Tenants
need to be connected via
ST-PI Plug-In.
This connectivity needs to
be configured in the
managed system:
support.sap.com/setup-
managed-services

50
Public
Usage in SAP Cloud ALM for Implementation
§ Typical for the private cloud is
to have a 4 system landscape
with a pre-production system
for a stabile integration test
environment:
§ (Starter system)
§ Development system
§ Test system
§ Pre-production system
§ Production system

51
Public
2.1.4 Integration and configuration options
ü Integrate deployment tools

52
Public
2.1.4 Set-up external notifications
§ Replicate item creation and
updates to an external system
§ Go to Projects and Setup >
External API Management to
manage the subscriptions

53
Public
Increases transparency via
built-in traceability to keep
track of the deployment of
your changes throughout
your landscape
Ensures reliability for
changes with synchronized
go-live based on delivery
milestones and releases
Accelerates the delivery
process by orchestrating
heterogeneous transport
mechanisms
2.1.4 Deployment orchestration

54
Public
2.1.4 Deployment integration
On-Premise
Public Cloud
ATO
CTS
Cloud
TMS
Change Management &
Deployment Orchestration
available
available
Enterprise Cloud
Services
CTS
available
private edition
,
Supported Content Types
Public Cloud
SAP Analytics Cloud
available

55
Public
2.1.4 Configuration in SAP BTP Cockpit
• There are additional integration and configuration
options that help you take advantage of the full set
of capabilities of SAP Cloud ALM.
List of integration options
• To orchestrate developments and configuration
activities in SAP Cloud ALM, you need to set up a
connection between your managed systems and
SAP Cloud ALM
Link to appropriate chapter in the configuration guide
• To enable transport management of S/4HANA
Cloud, public edition, for SAP Cloud ALM, the
Adaptation Transport Organizer (ATO) needs to
be connected.
How to establish a connection between SAP Cloud ALM
and ATO
SAP BTP Cockpit
On-Premise
S/4HANA
Enterprise Cloud
Services
S/4HANA Cloud
private edition

2.2 Prepare – Project Setup
2.2.1 Project setup
2.2.2 Select task template
2.2.3 Maintain Timeboxes
2.2.4 Maintain roles and teams
Project lead

57
Public
Project Lead
Project
Member
SAP Cloud
ALM
onboarding
completed
Create and name
project
Add Team Members Customize task template
Create SAP Cloud ALM Project
Select task
template
Maintain
timeboxes
Add project
members
Optional: Connect
CBC Integration
Scenario
Review and
adjust task
template
Project Setup
Completed
Upload task
template
ü Single project vs. multiple projects
Access SAP
Cloud ALM
project
2.2.1 Project setup – single or multiple projects?

58
Public
2.2.1 Project setup
§ You can create a Project using
the „Projects“ tile
§ System allows you to create
multiple Projects and you can
easily switch between multiple
Projects

59
Public
2.2.1 Project setup
§ Projects can be hidden if
no longer in use
§ In Manage Project display,
use Archive button
§ Hiding a Project is a
reversible action
§ At Archived tab select
project and choose
Restore

60
Public
Private
Project is private and can only be
accessed by project members
Edit or Display for non-project-
members NOT allowed. Even search
results for non Project members will not
show Private projects.
Restricted
Project is restricted and
only project members can
do make changes within the project
Display for non-project-members
allowed
Newly created Projects get the access
level Restricted by default. This can be
easily changed anytime.
Public
Project is publicly accessible by
all users for Edit or Display
with project management based on a
combination of Project roles and
Authorization role
2.2.1 Project setup
Project access restrictions - manage the access level for all of the project members
In the Projects and Setup app, three access levels can be determined in a project:

61
Public
2.2.1 Project setup
Project access restrictions – detailed matrix and use cases
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.

62
Public
2.2.1 Project setup
Project access restrictions – how to manage the access level for all of the project members
Access Restriction: Public
§ Project is publicly accessible by all users for
Edit or Display with project management
based on a combination of Project roles and
Authorization role as explained further
authorizations
§ This enables the project to be easily
accessed even by non-project members for
display or edit based on their authorization
role.
Access Restriction: Restricted
§ Project is restricted and only project
members can do make changes within the
project (display for non-project members
allowed).
Access Restriction: Private
§ Project is private and can only be accessed
by project members (Edit or Display for non-
project-members NOT allowed). Even search
results for non-project members will not show
private projects.

63
Public
Project Lead
Project
Member
SAP Cloud
ALM
onboarding
completed
Create and name
project
Select task
template
Maintain
timeboxes
Add project
members
Optional: Connect
CBC Integration
Scenario
Review and
adjust task
template
Project Setup
Completed
Upload task
template
ü Activate vs. custom project template
Access SAP
Cloud ALM
project
2.2.2 Project setup – which template to use?

64
Public
2.2.2 Project setup – select task template
SAP S/4HANA Cloud Public Edition template
§ Use task templates to
§ accelerate your project
§ make sure to not miss an important step
§ Utilize gathered know how
§ Choose SAP S/4HANA Cloud Public Edition –
Implementation
§ You can also upload and update your own task
list via Excel: see Blog
§ You can only select one template per project.
If you want to use the roadmap tasks of an
additional roadmap craeate another project
download the tasks and upload to the public
cloud project as project tasks
§ Check out roadmaps here: Roadmap Viewer
Note:
§ Some Roadmaps can be combined
§ Duplicate tasks are automatically merged

65
Public
2.2.2 Setup roadmap tasks
§ SAP Cloud ALM comes
preloaded with foundation tasks
that help you get started
§ The task list is grouped by
deliverable and the initial setup
tasks can be found under the
Deliverable „SAP Cloud ALM
Setup“
§ You can find these tasks
anytime by using
§ Task type: Roadmap task
§ Task source: SAP Cloud
ALM setup
Blog

66
Public
2.2.2 Integrate Central Business Configuration tasks
§ Select the CBC Projects to be
integrated in SAP Cloud ALM
§ As a result you will get the
scoped CBC activities
automatically replicated as
roadmap tasks with source CBC
in the SAP Cloud ALM task list
Note: Currently only a few project
but no configuration activities are
replicated.

67
Public
Project Lead
Project
Member
SAP Cloud
ALM
onboarding
completed
Create and name
project
Select task
template
Maintain
timeboxes
Add project
members
Review and
adjust task
template
Project Setup
Completed
Upload task
template
ü Maintain deployment plan including
sprint and release information
Access SAP
Cloud ALM
project
2.2.3 Define checkpoints and timeboxes

68
Public
2.2.3 Define Quality Gates
Quality Gates
§ Are predefined milestones where a
project is audited to see, if it meets
the necessary criteria to move into
the next phase
§ Are displayed under Projects and
Setup, General Information (only
quality gates of the current project
phase are displayed)
§ Are linked to and maintained in the
Task List

69
Public
2.2.3 Deployment planning
Keep your production systems stable and reliable with SAP Cloud ALM for Implementation
and stay on top of your deployment activities
Synchronize
deployment across
multiple projects
Bundle requirements
with the same
deployment schedule
Keep track of
deployment
activities

70
Public
2.2.3 Deployment Plan & Releases
A deployment plan is like a train line that follows a fixed schedule. A train leaves the station on a
known, reliable schedule. Releases are individual trains of the line following this schedule. The
passengers of the train are requirements or features that need to reach a destination by a certain
time and hence need to fetch a particular release.
If a requirement or feature misses a timed
departure of a train it can catch the next
one.
Also one passenger can only be on one
train at any time hence requirements and
features can have only one release at a
time.

71
Public
2.2.3 Release Landscape
A Train runs on a particular track. That is why a deployment plan needs to know the
set of systems it is going to manage.
Deployment Plan
S4HC
SFSF
Release
1
Release
2
Release
3
Release
4
Release
5
Deployment Plan – Hire to Retire

72
Public
2.2.3 Setup of deployment plan
Best practice for deployment planning
• Assign your deployment plan on project level
• Plan your releases in alignment to your sprint planning
• Use a release on requirement level to indicate the planned
release to production
• Use a release on feature level to specify the actual release to
production
• Use the built-in traceability to keep track of the deployment

73
Public
§ A deployment plan is a
collection of releases and
system groups that can be
assigned to multiple projects
§ When assigned to a project
the deployment brings the
landscape information to the
project
2.2.3 Deployment plan
Overview

74
Public
Example 1: Implement S/4HANA
§ Select your project
§ Create a deployment plan and
enter a title
§ In case you need to
orchestrate several
deployments, maintain
releases and their planned
time range
§ Assign the system group
representing the to be
implemented S/4HANA Cloud,
private edition

75
Public
Example 2: Implement several solutions
§ Select your project
§ Create a deployment plan and
enter a title
§ Maintain releases and their
planned time range (can be a
combination of major and
minor releases)
§ Assign the S/4 HANA Cloud
and SAP Ariba system group
representing the to be
implemented SAP solutions

76
Public
2.2.3 Release assignment to projects
§ The release is an entity that establishes a
common language of communication
across projects for planning and
deployment
§ Using releases in projects enables you to
orchestrate the deployment across
multiple projects
§ You can assign only one release to one
project
§ When multiple projects want to follow a
common timeline for planning then
multiple projects can be assigned to the
same release
§ Releases can be assigned to
§ Requirements
§ User stories
§ Features
§ Defects

77
Public
Project Lead
Project Member
SAP Cloud
ALM
onboarding
completed
Create and name
project
Create Cloud ALM Project
Select task
template
Maintain
timeboxes
Add project
members
Review and
adjust task
template
Project Setup
Completed
Upload task
template
ü Teams / roles / users
ü Activate / custom roles
Access SAP
Cloud ALM
Project
2.2.4 Project setup – how to maintain teams, team members and roles

78
Public
2.2.4 Teams and project roles
Assign roles and/or individual users to teams
Business Process
Expert
Configuration
Expert
Project
Team A
Business Process
Expert
Configuration
Expert
Project
Team B

79
Public
§ System is pre-delivered with a default
team called “PMO team”
§ This team shows with a special icon
§ This team is the only team that can
contain the role “Project Lead”
§ This team can be renamed but can not
be deleted
§ You can create any number of teams
§ You can assign persons to team by roles
or by users
2.2.4 Setup of teams

80
Public
2.2.4 Setup of project roles
Predefined activate roles
§ Project role definitions are visible to all
projects
§ System is pre-delivered with role list
from Activate Methodology
§ The project lead is the only project role
that has the authorizations to add users
to other project roles
§ All other project roles have the same
more limited authorizations
§ The project roles are literal descriptions
to distribute work to or filter for project
members, e.g. testers, consultant or
developer

81
Public
2.2.4 Setup of project roles
Create project roles
§ You can add custom roles
§ Custom roles show with a
different icon
§ Custom roles can be deleted
§ Custom roles are cross project
but are selected in project context
§ Custom roles show with a
different icon
§ Custom roles can be deleted

82
Public
Custom Project Roles
ü Names are recognized by customer
ü Can be changed & added if required
ü Can structure tasks better
✘ Activate tasks and tasks coming from
requirements are not assigned automatically
based on the workstream
Activate Roles
✓ Are already pre-defined and documented within
Activate
✓ Tasks are distributed to the activate roles based
on workstreams
✓ Are stable across projects
✘ Might not match project role names
✘ Cannot be changed
2.2.4 SAP Cloud ALM guide – project setup & scoping
Activate roles vs. custom project roles

83
Public
2.2.4 SAP Cloud ALM guide – project setup & scoping
Assign team members to roles

2.3 Explore – Fit to Standard Workshops
2.3.1 Explore roadmap tasks
2.3.2 Maintain project tasks
2.3.3 Prepare fit-to standard workshops (scope and solution processes)
2.3.4 Run fit-to standard workshops
2.3.5 Document requirements
Project lead
Project lead
Project lead / functional expert
Functional expert
Functional expert

85
Public
Project Lead
Project Member
SAP Cloud
ALM
onboarding
completed
Create and name
project
Create Cloud ALM Project
Select task
template
Maintain
timeboxes
Add project
members
Optional: Connect
CBC Integration
Scenario
Review and
adjust task
template
Project Setup
Completed
Upload task
template
ü Decide if to integrate CBC in SAP Cloud ALM
Note: Currently the integration of tasks is quite high-
level. Way of integration might change in future.
Access SAP
Cloud ALM
Project
2.3 Project setup – how to maintain teams, team members and roles

86
Public
§ To integrate CBC, go to Projects and
Setup, integration scenario and select
scenario SAP Central Business
Configuration
§ Select the tenants and CBC project
related to your project
§ As a result, CBC project tasks will be
synchronized with SAP Cloud ALM
Note: Due to planning early 2024 it is
planned to even remove this high-level
integration later this year
2.3 SAP Central Business Configuration and SAP Cloud ALM
Basic setup

87
Public
2.3.1 Fit-to-Standard process – explore roadmap tasks
Fit-to-Standard Workshops Requirement Collection & Approval
Project
Lead
Functional
Expert
Project setup
completed
Schedule Fit-to-
Standard
workshops
Create
scope
Assign project
tasks to teams
and roles
Select solution
scenarios
Select solution
process
Review and
confirm project
scope
Review
and adjust
roadmap tasks
Upload custom
task template
+
ü Explore roadmap tasks

88
Public
2.3.1 Consumption of SAP Activate roadmaps
Comparison of roadmap viewer with SAP Cloud ALM
SAP Activate team publishes its task content in SAP Cloud ALM as well as Roadmap viewer.
These tools serve complete different use cases so you can find them below.
Blog
Roadmap Viewer SAP Cloud ALM
Content for both On Premise and cloud products Currently focused on cloud content
Tasks separated by Workstreams Tasks distributed by workstreams and roles
Is a guidance environment Is a working environment
Scope independent content Content reacts to customers scope
Public URL Access via entitlement

89
Public
2.3.1 Roadmap viewer
Navigate to the complete SAP S/4HANA Cloud Public Edition content
Procedure
§ To display the complete roadmap contend
open roadmap viewer:
https://go.support.sap.com/roadmapviewer/#
§ Click Explore All Roadmaps
§ Select SAP Activate Methodology for SAP
S/4HANA Cloud Public Edition
Note:
Check out supported solutions in detail

90
Public
2.3.1 Roadmap viewer roadmap content
Filter for the content
Procedure
§ To explore the content you can use
filters for:
§ Phase
§ Workstream
§ More -> allows to filter for Base Scope
§ As result you get a content list
§ Check, if there’s helpful content,
helping you to further plan and
execute your project

91
Public
2.3.1 Roadmap viewer roadmap accelerators
Filter for the list of accelerators
Procedure
§ To limit the displayed
accelerators you can use
filters for:
§ Phase
§ Workstream
§ More -> allows to filter for
further public cloud content
§ As result you get a list of
accelerators which you can
check out one by one

92
Public
2.3.1 SAP CALM roadmap content – roadmap tasks
Explore the predefined roadmap content
Procedure
§ In SAP CALM go to the task overview :
§ Filter for:
– Type: Roadmap tasks
– Source: SAP Activate methodology
§ Choose tab Items
§ Click on a roadmap task title to display
the detailed description and accelerators
§ In case a roadmap task is helpful for your
project, set status Open and assign it to a
role, team, or team member
§ In case a roadmap task is not helpful set
it to status Not Relevant

93
Public
2.3.1 SAP CALM roadmap accelerators – roadmap tasks
Navigate to and filter for the list of accelerators
Procedure
§ To get a list of most valuable
accelerators displayed:
§ Open the task overview
§ Filter for roadmap tasks
§ Choose tab accelerators
§ As result you get a streamlined list of
SAP accelerators

94
Public
A project in SAP Cloud ALM can be linked to
multiple projects in SAP Central Business
Configuration (CBC). This makes the planned
configuration activities transparent in SAP Cloud
ALM
§ When a CBC project is linked to a SAP Cloud ALM
project, project activities from CBC are replicated as
roadmap tasks with source CBC in CALM
§ The content follows the hierarchy given by SAP
Activate
§ Project activities from CBC are shown as children of
Activate roadmap tasks under the Activate
deliverables
§ In the CALM task list you can track the automatically
updated status. To check out details, there’s a high
level link back to the CBC configuration. The detailed
tracking of the mandatory standard configuration is
done in CBC.
2.3.1 Add tasks from SAP Central Business Configuration
Task integration

95
Public
Starter System
§ Used for fit-to-standard workshops with
example data
§ Development & Customizing tenant
Transports
§ No transports from starter system tenants to
development system
§ Transport requests are technically required but
not used to transport content to any other system
§ No transfer of configuration / key user extensibility
from starter to development
§ ABAP development can be taken over using
abapGit via customer-owned GIT repository
SAP Help Portal: Transferring Developer
Extensions Between Development Tenants
SAP Help Portal: 3-System Landscape and Transport Management
2.3.1 CBC roadmap task example
Setup starter system/tenant for 3-system landscape transport management

96
Public
2.3.2 Fit-to-Standard process – distribute project specific organizational tasks
Project
Lead
Functional
Expert
Project setup
completed
Schedule Fit-to-
Standard
workshops
Create
scope
Assign project
tasks to teams
and roles
Select solution
scenarios
Select solution
process
Review and
confirm project
scope
Review
and adjust
roadmap tasks
Upload custom
task template
+
ü Maintain project tasks to
organize your project

97
Public
2.3.2 Project tasks
Create project tasks

98
Public
2.3.2 Project tasks
Create project tasks

99
Public
2.3.2 Project tasks
Assign tasks to process
Procedure
§ You can display and track project tasks in
context of a process
§ To enable that
§ Go to Processes
§ Select your Solution Value Flow or Solution Process
§ Choose Assign
§ Select the to be assigned Task
§ Press Assign
§ As a result you not only have the tasks
displayed, but can also track them in the
Solution Process Traceability

100
Public
2.3.2 Maintain templates
Create template
For most of the task types like project
task, requirement, user story or defect, it
is possible to define templates.
Procedure
§ Create e.g. a User Story in form of the
wished template
§ Scroll down to Additional Information
§ Choose Use this item as template
§ Save and Close
§ As a result you can use this user story as
template when clicking Create >
From Template

101
Public
2.3.2 Maintain templates
Delete template
To have the chance to keep template
drafts, inactive templates or obsolete ones
you need to follow a two step approach
before you can delete a template.
Procedure
§ Open the item which you use as template
and want to delete, e.g. a user story
template
§ Go to Additional Options
§ Choose Set to Obsolete
§ Confirm the pop-up
§ Go to Additional Options again
§ Choose Delete
§ Confirm the pop-up

102
Public
2.3.2 Project tracking
SAP for Me integration
Procedure
§ To track project progress, SAP
Cloud ALM for Implementation
projects are integrated in SAP
Cloud for me
§ Choose Services & Support
and tab Application Lifecycle
Management to get your
project list
§ Clicking on a project name,
you navigate to SAP Cloud
ALM Projects and Setup, with
the project preselected

103
Public
2.3.3 Prepare fit-to standard workshops
Define scope
Project
Lead
Functional
Expert
Project setup
completed
Schedule Fit-to-
Standard
workshops
Create
scope
Assign project
tasks to teams
and roles
Select solution
scenarios
Select solution
process
Review and
confirm project
scope
Review
and adjust
roadmap tasks
Upload custom
task template
+
ü Specify scope granularity

104
Public
Scope definiton
o The Project can refer to one or
several scopes
o Scope consists of one or more
solution scenarios. It is the first
filter level of your solution
processes
o Solution scenarios provide choice
of country specific processes and
their variants
o Solution Processes consists of
system independent Solution
value flows as well as system
specific solution process flows
Project
Scope
Solution scenario
Solution Process

105
Public
Select relevant processes
§ Out of the selected content
packages/solution scenarios you
can pick relevant processes due
to topic and/or valid country.
Select relevant solution
scenarios
§ For the created scope select at
least one of the predefined
content packages called solution
scenarios in specific version
§ Beside SAP delivered content
also customer specific Solution
Scenario can be created and
used to describe specific
business flows
Create scope
§ Name and create at least one
scope that will be used in your
implementation project
Scope definition
i
Implementation project

106
Public
2.3.3 Reuse Scoping Data from Digital Discovery Assessment (DDA)
Overview
Digital Discovery Assessment:
§ Is a functionality to support the
customer communication
§ Can be accessed by SAP Sales,
Presales and qualified
SAP Partners
§ Is used to identify used Best
Practice processes and based on
that allows the scoping of to be
implemented processes
§ Scoping can be reused in SAP
Cloud ALM and Central Business
Configuration (CBC) to accelerate
implementation planning and
configuration
Access to more detailed information for:
§ SAP Internals
§ SAP Partners contact your SAP
contact person

107
Public
2.3.3 Import of Solution Process Scope via Excel
Example Digital Discovery Assessment (DDA)
Scope
Scoping via Excel Import
Using the excel report from the
Digital Discovery Assessment
the initial scope in SAP Cloud
ALM can be created for SAP
S/4HANA Private Edition
scenario.

108
Public
Digital Discovery Assessment (DDA)
§ Do high-level project/process scoping and download
when ready
SAP Cloud ALM
§ Select Activate roadmap and use roadmap tasks to
organize your project
§ Upload DDA content to get the initial scope
§ Process with business process scoping (solution
scenario, business processes and country version),
localization match to CBC)
CBC:
§ Demo public edition processes in starter tenant
§ Document scope in an implementation project and
deploy mandatory configuration, e.g. org. structures,
to development tenant
Detailed information how to scope and configure
public edition with CBC
-> activity status of project tasks is automatically
replicated as roadmap tasks in SAP Cloud ALM, e.g.
Confirm Scope and Organizational Structure Phase
is Completed
2.3.3 SAP Central Business Configuration & SAP Cloud ALM
Basic procedure: Scoping & mandatory configuration

109
Public
Basic procedure: Plan build, build
SAP Cloud ALM
§ To track optional configuration/developments,
maintain and approve requirements in process
context.
§ For complex requirements, create user stories
§ To track deployment status, assign features to
requirements
CBC
§ Evaluate and demo optional configuration, e.g. price
calculation, in starter system.
§ Approve configuration in Requirement, and
document scope in an implementation project
§ Repeat configuration in development
SAP Cloud ALM
§ Set status In Implementation (= approval by project
manager/change manager)
§ Manually document/assign transports to features and
track successful deployment to test

110
Public
Basic procedure: Deploy to test, test, deploy to production
S/4 Development tenant
§ Export from development and import in test tenant
SAP Cloud ALM
§ Select predefined automated test cases for
unchanged standard processes. Create manual test
cases for modified processes.
§ Execute tests and manage defects
§ Confirm successful test verbally or document
changes via project task in feature
§ Set status Ready for Production
§ Approve and deploy features with transports to
production tenant

111
Public
Scope definition variant 1: Scope = Project
Fits to small to midsize projects focussing
mostly on public cloud implementation, e.g.
implementing SAP S/4HANA Cloud and Ariba
standard processes
Advantages:
§ Simple and fast scope creation
§ All processes within one scope
§ Filtering by Business Process Group (e.g. Finance)
Disadvantages:
§ Reporting relies on additional filtering capabilities
as the processes are organized in a flat list within
the scope

112
Public
Fits midsize and big projects
focussing mostly on private/public
cloud implementation e.g., S/4HANA
Cloud, public edition
Advantages:
§ Scope contains processes of one
functional area/Software product
§ Simplification of reporting activities e.g.
notes, requirements and test
preparation grouped by functional area
Disadvantages:
§ Higher efforts while scope creation
Scope definition variant 2: Scope = Functional area (Best Practice)

113
Public
Scope definition variant 3: Scope = Localization
Fits to big projects focussing mostly
on private/public cloud
implementations into several
separate tenants for subsidiaries,
countries or plants e.g., region US,
EMEA, APJ
Advantages:
§ Scope contains processes of one
functional area/Software product
§ Simplification of reporting activities e.g.
notes, requirements and test
preparation organised in localizations
or countries
Disadvantages:
§ Higher efforts while scope creation
§ Duplication of processes
§ No cross scope reporting possibility for
requirements, user stories or notes

114
Public
How to maintain a scope
In the Manage Scopes app, you can do the following:
§ Display available scopes and solution scenario versions
§ Create scopes
§ Delete scopes (authorized users)
§ Search for scopes
§ Edit existing scopes
§ Switch on and off solution scenarios for your scopes
Note:
§ Solution scenarios can be assigned just in
ONE version to a scope, e.g. Version 2023
§ Once a Scope is selected and saved you can’t deselect it at
a later point in time
Combine solution scenarios and processes into the same
scope if:
§ The same application system landscape is used
e.g. for sites with own tenants/systems, shared services
tenants/systems
§ The solution processes require an aligned upgrade cycle
e.g. heavily dependent tenants/systems that are upgraded as a whole
§ Serve the same functional purpose
e.g. solution processes per site, solution processes for shared
services such as finance consolidation or HR shared services

115
Public
2.3.3 Prepare fit-to standard workshops – explore predefined solution processes
Project
Lead
Functional
Expert
Project setup
completed
Schedule Fit-to-
Standard
workshops
Create
scope
Assign project
tasks to teams
and roles
Select solution
scenarios
Select solution
process
Review and
confirm project
scope
Review
and adjust
roadmap tasks
Upload custom
task template
+
ü Select best practice processes
and assign them to a scope

116
Public
Solution process definition
A Solution Process is a concrete and self-contained
implementation of a Business Process.
§ Accelerators may complement the Solution Process
descriptions and provide access to additional accelerators.
Solution value flows depict the functional scope
delivered by the Solution Process.
§ A Solution Value Flow is constructed from (sub) business
processes and business activities.
§ Business activities can be re-used and should be formulated
in business user language.
Solution process flows
§ A Solution Process Flow is modeled using one or multiple
BPMN diagrams.
§ BPMN diagrams depict the actual process flows and contains
all important participants and activities.

117
Public
How to upload solution processes from other sources
§ External reference ID
helping to uniquely detect the process
coming from other sources
§ Upload of SVG file for Solution Value Flow
§ Upload of SVG or BPMN file for Solution
Process Flow
§ Copy of customer solution processes
including all solution process flows
§ Rename of copied solution processes

118
Public
How to select predefined solution processes
In the solution Processes scope app, you can select relevant
solution processes, e.g., as basis to work on pre-defined user
stories or to create requirements and notes.
In detail, the following options are available:
§ Get an overview of your solution processes
§ Search for solution processes with the help of the filters for:
§ Process Status
§ Process Hierarchy
§ Solution Scenario, e.g., Accounting and Financial Close (J58)
§ Country Region, e.g., Germany, China, United States
§ Business Process Group, e.g., Finance
§ Edit solution process scope (select/de-select process
scopes)
§ View process diagrams and pre-defined user stories
§ Navigate to related requirements, user stories and notes
§ Navigate to SAP Best Practices Explorer

119
Public
Specify graphical
representation
§ The solution value flow depicts the
functional scope delivered by the
solution process / variant.
– The solution value flow is constructed from
(sub) business processes and business
activities.
– Business activities can be re-used and should
be formulated in business user language. It
serves as a visual description of the solution
variant.
Create relevant solution
processes
§ You can create new custom
solution processes and assign
them to business processes
(process variants) that exist,
or you can create new related
business processes (process
variants).
Create Business Process
Variant
§ A solution process / variant
is a concrete and self-contained
implementation supporting a
business process.
§ Create a process variant as
representative of a process
family. This will be used to
group solution processes in
the scope selection.
2.3.3 Prepare fit-to standard workshops - Custom solution processes
Copy and organize scoped processes
i
Fit to standard: custom solution processes

120
Public
Specify graphical
representation
Create relevant solution
processes
For the created scope select at
least one of the predefined content
packages called solution scenarios
in specific version
Beside SAP delivered content also
customer specific Solution
Scenario can be created and used
to describe specific business flows
Create Business Process
Variant
2.3.3 Prepare fit-to standard workshops - Custom solution processes
i
Fit to standard: custom solution processes

121
Public
è Better visibility of available content
è Grouping content regarding functional area and responsibility
è Influencing the way how the custom process are grouped and displayed
in scope selection
Organize the list of custom solution processes by the definition of name convention (prefix).
In addition, if multiple solution processes implement the same business process, this information can be made
transparent by assignment to the same BP Variant
When creating the custom
processes, the diagrams shall
be published on the end.
Afterwars, the content is
available for being selected by
scope.

122
Public
Organize scoped processes by process hierarchy
The Process Hierarchy structures the
customer’s business and divides a complex
processes landscape into smaller better
manageable parts.
It follows the from-abstract-to-
concrete principle and provides information
about the processes on different levels of
granularity.
In the Process Hierarchy app, you can
maintain a project independent process
documentation hierarchy that reflects your
organization or/and the way you want to
organize the business processes and
documentation (available soon).
In detail, you can do the following:
- Create a process hierarchy
- Edit the title and description of a
process hierarchy node
- Delete a process hierarchy node
(starting by lowest sub-structure)

123
Public
Fit-to-
Standad
Workshop
team
Project
Lead
Scoping
completed
Conduct Fit-to-
Standard
workshops
Show & Review
process
diagrams
Create notes,
assign
documents
Create
requirements
Categorize and
prioritize
requirements
Review, reject or
approve
requirements
Define custom
value chain
diagrams
Define custom
solution process
diagrams
Set custom
processes active
and add to scope
ü Define to be used documents

124
Public
2.3.4 Documenting Notes
In the Processes app, you can create or
edit the notes for the process itself or for one
or several activities describing the functionality.
In detail, the following options are available
while note creation:
- Header: definition of note title and
categorization (“Note”)
- Tags: categorization and better reporting
- Description: giving possibility to
describe in a text format
- Relations: showing the assignments
to current or different business
processes.
- References: allowing creation of URLs
Further access and processing possible in
central Notes overview app.
Note

125
Public
Document
2.3.4 Documenting processes
A document consists of
- Content: definition of document
title and document text
- Additional information:
è Document Status
è Owner
è Information about the
document object like ID,
created by and created on
- References: URL link
- Relations: solution process
- Relations: process hierarchy
A document can have two document
editing status:
- Draft
- Saved
In the Documents app, you can create or edit documents in
context of a project.

126
Public
2.3.4 Creating documents: method
draft document
in private
visibility
Edit document
document
in general
visibility
Save
In Progress In Progress
In Review
Released
In Review
Released
Activity
Editing
status
Document
Status

127
Public
2.3.4 Creating documents: method
Definition of metadata:
Status:
- In progress (automatically assigned)
- In Review
- Released
Document type:
listing predefined document types as
attribute assigned to the document.
Priority:
- Low
- Medium (automatically assigned)
- High
- Very High
Owner (automatically filled with the creator)

128
Public
2.3.4 Linking documents
Relations
Link to one or several solution processes
Process hierarchy
Link to the process hierarchy for better organization
of documents.

129
Public
2.3.4 Linking documents
References
Link to an external URL (pointing to additional
documents).
Relations
Link to one or several solution processes
Process hierarchy
Link to the process hierarchy for better organization
of documents.

130
Public
2.3.4 Name conventions
Prefix
The prefix shall provide information about the
expected document content type. Potential
content types could be:
- Process descriptions
- Functional specifications
- Technical specifications
- Configuration documentation
- …
Title
The title shall represent the process, activity or
area for which it has been created.

131
Public
Fit-to-
Standad
Workshop
team
Project
Lead
Scoping
completed
Conduct Fit-to-
Standard
workshops
Show & Review
process
diagrams
Create notes,
assign
documents
Create
requirements
Categorize and
prioritize
requirements
Review, reject or
approve
requirements
Define custom
value chain
diagrams
Define custom
solution process
diagrams
Set custom
processes active
and add to scope
ü Define requirements strategy
and approval procedure

132
Public
2.3.5 Run fit-to standard workshops - document requirements
In the Processes app, you can create or
edit the Requirements.
• Business Experts and consultants can
collect the Requirements using the
Solution Process context
• Requirements can be collected at
Solution value flow, process or step
• Requirements can be collected for
custom process also
With relation to a Requirement, a
project task, user story or feature can be
created.
One Requirement can lead to several
User Stories, which can be assigned to
different Features and thus implemented in
different Releases.
Feature
User Story
Project
Task
Test Case
Requirement

133
Public
Status Flow
- Identify gaps with respect
to offered capabilities
- Decompose into smaller
units if required
In Refinement
- Optional step
- Validate need, design,
approach
- Send it to subsequent
teams for processing
In Approval
- Assign user stories to
sprints
- Establish relations and
priority
- Use custom tags as
needed
In realization
- Use Traceability reports
to track progress
- When appropriate ,
engage the testing teams
In Testing
- Conduct user
acceptance testing
- Deploy assoc. Features
and user stories to PRD
- Set the status to
confirmed
Confirmed

134
Public
Option 1: Create requirements from process

135
Public
Option 1: Create requirements from process

136
Public
Option 2: Upload requirements and assign to process
Procedure
1. Open the task list
2. Download Requirements to
get a xls template

137
Public
Option 2: Download requirement template
Procedure
1. Maintain requirements in xls
2. Browse for the requirements file
3. Upload

138
Public
Option 2: Assign uploaded requirements to process

139
Public
Trace if all requirements of your process are maintained
Procedure
§ In Analytics, Solution Process
Traceability
§ Click on the Requirement bar
§ Check to check for missing or
unassigned requirements

140
Public
Process implementation state: dependency to status of other entities
Fit to Standard
Workshops
Design
Implementation with
configuration and
development
activities
Realization
Productively used
Production
Correction on
configuration or
developments
Maintenance
Process not used
anymore but
configuration and
developments exist
Obsolete

141
Public
Fit to Standard
Workshops
Design
Implementation with
configuration and
development
activities
Realization
Productively used
Production
Correction on
configuration or
developments
Maintenance
Process not used
anymore but
configuration and
developments exist
Obsolete
Process implementation state: dependency to status of other entities
- Requirements:
- In Refinement
- In Approval
- Blocked
- Not Planned
- User Story:
- Assigned
- Open
- In Progress
- Project Task:
- Assigned
- Open
- In Progress
- Test Preparation:
- In Preparation
Design
- Requirements:
- In Realization
- In Testing
- Blocked
- Not Planned
- User Story:
- In Progress
- Done
- Project Task:
- In Progress
- Done
- Test Preparation:
- In Preparation
- Prepared
- Test Execution:
- Initial
- In Progress
- Failed
Realization
- Requirements:
- Confirmed
- User Story:
- Done
- Project Task :
- Done
- Test Preparation:
- Prepared
- Test execution:
- Passed
Production
- Requirements:
- In Realization
- In Testing
- Blocked
- Not Planned
- User Story:
- In Progress
- Done
- Project Task:
- In Progress
- Done
- Test Preparation:
- In Preparation
- Prepared
- Test Execution:
- Initial
- In Progress
- Failed
Maintenance
- Requirements:
- Blocked
- Not Planned
- User Story:
- Blocked
- Project Task:
- Blocked
- Test Preparation:
- -
Obsolete
Monitored
in
Solution
Process
Traceability

142
Public
Trace if all requirements of your process are approved
Procedure
§ In Analytics, Solution
Process Traceability
§ Click on the Requirement
bar
§ Select In Approval
§ Navigate to the Requirement
Overview, e.g., to check the
unapproved requirements

143
Public
The detailed tracking of the mandatory standard
configuration is directly done in CBC.
As this configuration is done in a rather short
timeframe and summarized in one transport, it’s
sufficient to track it with only one requirement.
The deployment status can be tracked with one
assigned feature, which can be directly created in
the requirement UI.
2.3.5 Document CBC activities
Track mandatory configuration

2.4 Realize – Plan Build
2.4.1 Create user stories
2.4.2 Upload user stories
2.4.3 Trace user stories
2.4.4 Create features
Functional Expert

145
Public
2.4 User story
Definition
§ In the User story, you decompose the requirement
describing the testable functionality to be implemented.
§ In detail, the following information is available for the
user story:
§ Status: by the selection of appropriate status of the
user story, you can highlight if the current state of the
description
§ Due date: describes the date to which the user story
shall be finished
§ Team: responsible group of people for the user story
§ Assignee: person responsible for the user story
Feature

User Story

Project
Task

Test Case

146
Public
2.4 User story status schema
•Decompose Requirements into smaller
buckets
•Describe a business need from user
perspective in order to provide business
value
•Definition of done
•Assign to developer/development team
•Assign to timeboxes, e.g. sprints
•Maintain requested release
Open
•Describe developments or configurations
•Describe unit test
•Send it to subsequent teams for
processing
•Perform developments or configurations
•Perform unit tests
In Progress
•Use traceability reports to track progress
in the context of engaging testing teams
•Set the status to Done
Done

147
Public
2.4 Requirement & user story hierarchy
Relations
Requirement
User Story
(1 per app.)
Sub-Task
Sub-Task
User Story
(1 per app.)
Sub-Task
Sub-Task
E.g. create technical design
E.g. approve technical design
Test Case
Feature
(transport or task)
Process
1:1
1:n
Principle:
ONE User Story per involved application

148
Public
Project
2.4 SAP Cloud ALM elements in realize phase
Solution
Process
Diagram
Process
Elements
Test Case
Test Plan Defect
Transports
Notes &
Documents
Sub-Task
planned
existing
Feature

149
Public
Project
Lead
/
Deployment
Manager
Functional
Expert
Requirements
approved
Break down
requirements into
user stories, sub-
tasks
Test
Build
Create features
for requirements
Create test cases
Project tracking & tracing
Test
Manager
/
Tester
Consultant
/
Developer
Deploy
Identify test scope
Identify testers &
create test teams
scope
Configure/
develop
Test new
configuration/
development
DEV
Create transport
request
DEV
DEV
Release
transports
Validate test
coverage
Release test plan
Execute test
cases
Deploy transports
into test system
TST
Set tasks to
status “complete”
Approve feature for
deployment
Forward & import
transports to
production
Confirm
deployment
(requirements
status)
Report defect
Release test
cases
Requirements
deployed
Testing
Successful?
YES
NO
2.4.1 Create user stories
Assign transports
to feature
Create
test plan and
assign testers
Track test
progress
Confirm successful
test case
Finish test phase
Confirm
successful test

150
Public
2.4.1 Plan build activities
Option 1: Create user stories from process

151
Public
Option 1: Create user stories from process

152
Public
Option 2: Upload user stories and assign to processes

153
Public
Trace if all user stories of your process are maintained
Procedure
§ In Analytics, Solution Process
Traceability
§ Click on the User Story bar
§ Check to check for missing or
unassigned user stories
§ Navigate to the User Story
Overview, e.g., to check if
open user stories are
assigned to a project team
member

154
Public
2.4.3 Plan Requirement, User Story & Task Maintenance
Task list view example

155
Public
2.4.3 Plan Requirement, User Story & Task Maintenance in GANTT chart
Example
Requirement:
Project Task:
Project Task:
User Story:
Sub-Task:
Sub-Task:

156
Public
2.4.3 Plan Requirement, User Story & Task Maintenance
Cards view example

157
Public
Project
Lead
/
Deployment
Manager
Functional
Expert
Requirements
approved
Break down
requirements into
user stories, sub-
tasks
Test
Build
Create or assign
features
Create test cases
Test
Manager
/
Tester
Consultant
/
Developer
Deploy
Identify test scope
Identify testers &
create test teams
scope
Configure/
develop
Test new
configuration/
development
DEV
Create transport
request
DEV
DEV
Release
transports
Validate test
coverage
Release test plan
Execute test
cases
Deploy transports
into test system
TST
Set tasks to
Approve feature for
deployment
Forward & import
transports to
production
Confirm
deployment
(requirements
status)
Report defect
Release test
cases
Requirements
deployed
Testing
Successful?
YES
NO
2.4.4 Create or assign features
Assign transports
to feature
Create
test plan and
assign testers
Track test
progress
Confirm successful
test case
Finish test phase
Confirm
successful test

158
Public
A container of
landscape information
and deployment
approvals
An orchestrator of
different transport
containers for various
software components
A vehicle to deploy
functionality
throughout your
landscape and ensure
traceability via history
2.4.4 What is a feature?
A document to store
your technical change
documentation

159
Public
2.4.4 Feature workflow
Not Planned
In
Specification
Ready for
Production
In
Implementation
Deployed
ü Indicates
that a
Feature is
postponed
ü Technical
specification of
a Feature to be
done
ü Implementing the
Feature covers
recording of
changes (assign
transports) and
deploying changes
to the test
stage
ü Indicates that
the changes
were successfully
tested and are
ready for
production
deployment
ü Confirming the
deployment of
the changes
to production
In
Testing
ü To indicate
that a
Feature is
ready to be
tested

160
Public
Change Enablement
§ Feature used for guided implementation of changes
via workflow, approval and change history
§ Assign requirements and user stories to features
to document, that they are implemented in the test
and productive public cloud instance
Deployment Orchestration
§ Synchronous deployment of multiple features by
release timebox
§ Consistent deployment ensured by underlying
landscape information
Change and deployment management

161
Public
Business transaction – Feature
§ Entity for change documentation and deployment orchestration
§ Easily assign transports and trigger their deployment throughout your landscape
§ Traceability ensured via the history of a Feature

162
Public
Feature can be created…
§ from a requirement, e.g. combining all sales and distribution or purchase configuration requests
§ as a standalone entity, just to combine related transports to ensure consolidated deployment
How to create a feature

163
Public
2.4.4 Relate user stories and project tasks
• Simply create user stories and project tasks to relate them to a Feature
• Distribute your implementation efforts by utilizing user stories

164
Public
2.4.4 Create or assign transports
§ Creation of transport requests from a
feature is possible
§ for ABAP based on-premise and
private cloud systems
§ in feature statuses
– In Specification
– In Implementation
– In Testing”
§ Transport of Copies
§ Create manual references of transports
§ Assign transports from SAP S/4HANA
Cloud, public edition Adaption Transport
Organizer (ATO)

2.5 Realize – Build
2.5.1 Develop/configure and document changes
2.5.2 Perform unit test
2.5.3 Track project progress
2.5.4 Sprint review
Project lead
Developer
Developer
Project lead

166
Public
Project
Lead
/
Deployment
Manager
Functional
Expert
Requirements
approved
Break down
requirements into
user stories, sub-
tasks
Test
Build
Create or assign
features
Create test cases
Test
Manager
/
Tester
Consultant
/
Developer
Deploy
Identify test scope
Identify testers &
create test teams
scope
Configure/
develop
Test new
configuration/
development
DEV
Create transport
request
DEV
DEV
Release
transports
Validate test
coverage
Release test plan
Execute test
cases
Deploy transports
into test system
TST
Set tasks to
Approve feature for
deployment
Forward & import
transports to
production
Confirm
deployment
(requirements
status)
Report defect
Release test
cases
Requirements
deployed
Testing
Successful?
YES
NO
2.5 Configure and develop
Assign transports
to feature
Create
test plan and
assign testers
Track test
progress
Confirm successful
test case
Finish test phase
Confirm
successful test

167
Public
Ø ABAP development using Eclipse-based ABAP
Developer Tool (ADT)
Ø ABAP development objects are client-independent
à immediately active in all tenants in the dev
system
Ø ABAP development can be taken over using
abapGit (via customer-owned GIT repository)
Ø Developer transports are transported to test
and production, managed using ADT Transport
Organizer
Ø Configuration for developer tests independent
of the “productive” business configuration in
the Customizing tenant
2.5 SAP S/4HANA Cloud 3SL transport management
Setup development tenant
SAP Help Portal: 3-System Landscape and Transport Management Detailed recordings: CBC Tutorial Library

168
Public
Setup customizing tenant
Configuration: Creation of productive business
configuration content
Ø Default configuration is deployed from a
“main” CBC workspace
Ø Finetuning is done in the customizing tenant
Extensibility: Creation of key user extensibility

169
Public
Type Managed By / With Supported Features
in the ADT / Fiori UI
Used for
recording of
Developer
Extensibility
Developer / ADT Transport Request and Task: Create, Edit,
Change user assignment, Delete, Add/delete
objects, “Copy”, Merge, Release
Development objects
Key User
Extensibility
Extensibility Expert / Fiori app Collection: Create, Edit, Delete, Add/delete
objects, Merge, Release
Extensibility Items
SAP Central
Business
Configuration
Business Process Configuration Expert /
SAP Central Business Configuration
Transport Request: Change user assignment,
Release
Default configuration
(CBC managed)
Customizing
Business Process Configuration Expert
/ Fiori app
Transport Request and Task: Create, Edit,
Change user assignment, Delete, Delete objects,
Copy, Merge, Release
Finetuning content
(client-dependent
configuration)
Cross-client
Customizing
Business Process Configuration Expert
/ Fiori app
Transport Request and Task: Create, Edit,
Change user assignment, Delete, Delete objects,
Copy, Merge, Release
Finetuning content
(client-independent
configuration)
Transport Types

170
Public
Actions & Status Values
Status
• Documentation of Actions
and Status Values: see
documentation in the SAP
Help Portal
Ø 5 Actions and 16 Status
Values

171
Public
2.5 Transport activities in the feature workflow
The following table shows you which transport activities are available in the respective feature statuses:
Feature Status Create Assign Release Unassign Deploy
Not Planned
In Specification
In Implementation
In Testing
Ready for
Production
Deployed

172
Public
2.5 Create and deploy transport of copies
Transport your software changes to the test system without releasing the original transport. The objects are
transported with the version they have in the source system.

173
Public
2.5 Feature deployment
Deploying features to test systems ensures that new features as well as needed changes can be tested
properly before the changes are propagated to the production systems. Finally features are deployed to the
production systems based on the feature status "Ready for Deployment".
The following activities can be performed to prepare the feature delivery:
• Assign modifiable or released transports to a feature
• Unassign and reassign transports
• Refresh the transport list to get the current status
• Deploy the assigned transports
DEV QAS PRD
It is always ensured that transports are deployed to the test system before all transports assigned to a
feature can be deployed to the production system. Prior to the deployment of a feature to production the
approval for deployment needs to be given by the change & release manager (at the moment project lead or
project admin).

174
Public
Deployment of features can be triggered via the "Deploy" button in the transport section.

175
Public
In the transport section you can easily scan for the transports to be deployed within the
feature. Target tenants to be delivered next are shown in dark grey color.
In this example the released transports O11K900079 and O11K900332 will be deployed to the target tenants.

176
Public
By clicking the "Deploy" button all transports assigned to the feature will be checked for
their status. After confirming the upcoming pop-up via "Deploy" the appropriate transports
will be scheduled for deployment.
In this example only the released transports will be deployed to the target tenants.

177
Public
2.5 Support of complex landscapes
• Manage complex Cloud Transport Management
landscapes within a feature
• Multiple deployment targets (transport nodes) per
transport will be supplied by a single deploy action within
a feature

178
Public
2.5 Deploy several features to production
• Deploy several features together to production for a given release
• Features will be checked for the status “Ready for Production” and whether all assigned transports are ready
to be deployed to the production systems

179
Public
Deployment of features can be triggered via the "Deploy" button in the transport section.

180
Public
Utilize Feature to keep track of your Configuration, Key User
and Developer Extensibility changes in SAP S/4HANA Cloud
§ Easily assign your released transport requests to a feature
§ Manage dependencies between different collection types by
bundling dependent transport requests in one feature
§ Simply use the Feature Traceability as a starting point to decide
about next steps like forwarding and importing transport requests
§ For more detailed info regarding the configuration of the
communication arrangement, refer to the Setup & Admin Guide
§ Blog post - SAP S/4HANA Cloud transport traceability with SAP
Cloud ALM
2.5 SAP S/4HANA Cloud transport traceability
Features

181
Public
SAP Cloud ALM for Implementation provides an option to document your
software or configuration changes and to record the changed objects within a
feature. This is a crucial part of your change enablement since it helps you
to stay on top of your adjustments to production systems hence ensuring
stable and reliable daily operations.
2.5 Change documentation and recording

182
Public
Changes can be documented in the
"Description" section. You can use
the built-in rich text
editor describe your changes.
Utilizing the toolbar provides
options to use different styles to
emphasize parts of the change
documentation accordingly. It is
possible to attach images to
finalize a concise documentation.
2.5 Change documentation

183
Public
An essential part of your change
documentation is recording the
changes accordingly. The feature
in SAP Cloud ALM offers you an
option to assign transports as
containers of your software and
configuration changes. You can
assign modifiable or released
transports to the feature.
2.5 Change recording
Assign transports

184
Public
You can simply unassign
transports from a feature. This can
be useful in order to reassign
transports to a related feature with
dependent change objects.
2.5 Change recording
Decouple transports

2.6 Realize – Test
2.6.1 Test preparation
2.6.2 Test planning
2.6.3 Test execution
2.6.4 Test reporting
Tester
Test Expert
Test Expert
Test Manager

186
Public
Project
Lead
/
Deployment
Manager
Functional
Expert
Requirements
approved
Break down
requirements into
user stories, sub-
tasks
Test
Build
Create or assign
features
Create test cases
Test
Manager
/
Tester
Consultant
/
Developer
Deploy
Identify test scope
Identify testers &
create test teams
scope
Configure/
develop
Test new
configuration/
development
DEV
Create transport
request
DEV
DEV
Release
transports
Validate test
coverage
Release test plan
Execute test
cases
Deploy transports
into test system
TST
Set tasks to
Approve feature for
deployment
Forward & import
transports to
production
Confirm
deployment
(requirements
status)
Report defect
Release test
cases
Requirements
deployed
Testing
Successful?
YES
NO
2.6 Plan and execute tests
Assign transports
to feature
Create
test plan and
assign testers
Track test
progress
Confirm successful
test case
Finish test phase
Confirm
successful test

187
Public
2.6 SAP S/4HANA Cloud 3SL Transport Management

188
Public
Test system – Test tenant
§ Import of developer, key user extensibility and customizing transports
§ Forward of transports to production
Production system – Production tenant
§ Import of developer, key user extensibility and customizing transports
SAP Help Portal: 3-System Landscape and Transport Management Detailed recordings: CBC Tutorial Library

189
Public
2.6 Testing concepts in SAP Cloud ALM
Lean
Simple concepts
No complexity
overhead
Flexible Test Levels
Test with a purpose
Relation to
Process,
Requirement,
User Story
to achieve traceability
Agile
Test as soon as possible
Test as fast as possible
Process-Oriented
Derive the structure from the
process flows
Derive the content from the
process assets
(S/4 HANA)
Add test actions
Rich text support
Advanced Test Orchestration using Test Plans

190
Public
2.6 SAP Cloud ALM test management
Objectives and capabilities
Easy to consume solution.
Open to support all products in the future:
§ Cloud and On-Premise
§ SAP and non-SAP
Test Orchestration
§ Scoping
§ Multiple Test Cycles
§ Manual Functional Testing
§ Automated Functional Testing
§ Traceability
Test Automation:
§ Integration of Cloud-based Test Automation providers:
§ Test automation tool for SAP S/4 HANA Cloud
§ Tricentis Test Automation for SAP Cloud ALM
SAP Cloud ALM
Test Orchestration
Test Automation
Framework
Test automation tool for SAP
S/4HANA Cloud
Third-party Cloud Test
Automation Providers
Test Scope
§ Management
§ Execution
§ Monitoring
§ Signoff
§ Reporting/Auditing
Manual Testing

191
Public
Process, Requirements and User Stories within SAP Cloud ALM can be associated to test cases to
ensure their test coverage before deployment to production
This allows us to
achieve traceability
§ from demand
§ through realization
§ through testing
§ until deployment
2.6 Orchestration via traceability
User
Stories
Integration
Test
Requirement
Process
Acceptance
Test
Functional
Test

192
Public
SAP Cloud ALM project scope defines test scope
§ All business processes which are in scope of the
project should be tested
§ SAP recommends at least one test per business
process to ensure sufficient test coverage
§ The test overview screen allows users to:
– Create new test cases
– Display existing test cases
– View all test cases’ current preparation status
§ Attached to the process value flows there are
predefined manual test cases to be uploaded as an
initial test case. Especially for longer processes this
dramatically speeds up test case creation.
2.6.1 Manual test preparation
Test case overview

193
Public
2.6.1 Preparing test execution
In the Test Preparation app, you can manage and
prepare test cases to ensure that the
requirements you've implemented work from a
functional perspective.
In detail, the following options are available:
• Get an overview of all of your manual and
automated test cases
• Create manual test cases and prepare their
structure
• Integrate, create or manage automated test
cases from the connected test automation tool
• Track the progress of the test preparation
Requirement

Test Case

User Story


194
Public
2.6.1 SAP Standard test cases
Automated test cases from TAT (Test Automation Tool for SAP S/4HANA Cloud)
Accelerate business process and regression tests
using SAP delivered Standard Test Scripts
Documents all automated test activities with
screenshots
Create or adapt test scripts via recording functionality
High test coverage even during short test cycles
like upgrade tests
Result dashboard with drill down functionality
Test Automation Tool, an integral part of
S/4HANA Cloud, provides pre-delivered test
scripts to automate your business process tests.

195
INTERNAL
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ
2.6.1 Test automation framework concept
Based on S/4HANA Cloud
Processes (scope)
Requirements
User Stories
Automated Test
Cases
Test Results
Test Automation
Framework
Demand Build Test Deploy
SAP Cloud ALM
Test Automation Provider Cloud
Test Automation Tool
Automated Test Cases
Data Variants
Authoring
Environment
Execution
and Scheduling
Engines
TAT Destination
Test Management and Orchestration
Manual Test
Cases

196
Public
2.6.1 S/4HANA Cloud test automation integration
Test automation tool communication flow
Process(es) Scoped
Test Preparation
Test Results
Demand Build Test Deploy
SAP Cloud ALM TAT for S/4 HANA Cloud
Associated Test Plan(s) Created
for Project, Scope and Processes
Retrieve Test
Automated Cases Return Matching Test Plan(s)
Test Execution Execute Test Plan(s)
Trigger Test Case
Execution
Get Execution
Progress
Get Execution History
Results
Scope Changed
Return Progress
Return Execution History
Test Execution

197
Public
2.6.1 Integration of test automation tools
Integration options
*This is the current state of planning and may be changed by SAP at any time.
S/4HANA Cloud test automation integration:
§ Test Automation Tool for SAP S/4HANA Cloud (TAT) can be integrated with SAP Cloud ALM. Details
how to do the integration can be found here.
§ A detailed step by step procedure on how to retrieve and execute the test cases can be found here.
Further test automation options:
§ Tricentis Cloud Automation integrated since 2023 (not part of this presentation)
§ Test Automation APIs are published in the SAP Business API Hub
(no detailed description in this presentation)

198
Public
2.6.1 Automated test preparation
Review and select predefined automated test cases
Steps
§ Go to Test Preparation and select the
scope you want to test
§ Optionally select other filter options to
further specify your search results
§ Choose tab Automated
§ Review the list of predefined test
cases
§ In case there‘s no fitting automated
test case proceed with manual test
preparation

199
Public
Preparing test execution for requirements based testing
Steps
§ Use requirement traceability to search for
requirements with completed user stories
and missing test case
§ Create test case based on scope and
solution process flow
§ Create and/or assign tags to further
categorize and classify your test cases
§ Assign created test case to requirement
§ Use requirement traceability to search for
requirements with completed user
stories, features in ‚In Implementation‘
and prepared test cases
§ Set assigned feature status to ‚In Testing‘
§ Set status of requirement to ‘In Testing’

200
Public
Benefits
A key user responsible newly assigned to
a requirement can be automatically
informed by notification, e.g. to create a
test case
Notifications
Steps
§ Click on icon Profile
§ Choose Settings
§ Choose Notifications
§ Switch on Requirements: assigned to you

201
INTERNAL – SAP and Customers Only
Alternative approach using Best
Practice Test Assets for S4/HANA see
blog post:
Import Test Scripts from the SAP Best
Practice content for SAP S/4 HANA
2.6.1 Manual testing
Test preparation for S/4HANA

202
Public
Test reporting - Requirement based
The requirement traceability provides a list
view of the status of requirements for a
specific project, together with the status of
the related entities for each requirement.
This is helpful in terms of test preparation, by
searching requirements with missing or not
marked as prepared test cases.

203
Public
Test reporting - User story based
The user story traceability provides a list
view of the status of user stories for a
specific project.
The combination of status (Done) and the
test preparation (No test cases assigned, In
Preparation), you can see which user
stories are not ready for test execution

204
Public
Benefits
§ Supports multiple test cycles or roll-
outs to multiple organizations re-using
same or similar set of test cases
§ Test Plan Status to manage
preparation, execution and completion
of test phases or test cycles
§ Dedicated execution context (status
and defects) per test plan
§ Start and end date can be set for test
plan
§ Embedded draft handling to keep
unsaved data
§ Efficient reporting and drilldown to
details per test plan*
2.6.2 Test Planning
Benefits
*This is the current state of planning and may be changed by SAP at any time.

205
Public
Benefits
§ Easy assignment of Test Cases by
search and filter capabilities
Note:
When tester assignment will be realized,
bundling of test cases to tester work
packages is possible
2.6.2 Test Planning
Benefits

206
Public
Benefits
§ Lean testing without the need
to create test plans will be still
available via filter value (None)
§ Test plans with status ‘In
testing’ available for execution
in your current test phase or
test cycle.
2.6.2 Test Execution with Test Plans
Benefits

207
Public
Steps
§ Go to Test Plans
§ Check existing Test Plans
§ Go to Create
How to create test plans

208
Public
Steps
§ Click tile Test Plans
§ Push Create
§ Enter:
§ Test plan title
§ Responsible
§ Start date
§ End date
§ Click Assign Test Cases
§ Choose selection help, e.g. to
find predefined automated test
cases

209
Public
Steps
§ Maintain testers
for test cases

210
Public
Steps
§ Select test cases
§ Choose OK
Note:
Only test cases assigned to your
project are displayed for selection

211
Public
Every execution of a test case is called a test run
Each test case has a test run history
Each test run action has a status (Pass, Fail, …)
And a history of changes
A test run should be closed to get to a final status
2.6.3 Manual test case execution
Test run concepts

212
Public
The test run status matches the persona:
Test Run Status Persona Action Required
Pass Tester -
Fail Test expert / project lead Failure analysis required for further
classification
Fail – Application issue Developer An application issue needs to be fixed
Fail – Test case issue Test expert The test case must be adjusted
Fail – Retest required Tester The testing should continue
2.6.3 Manual test case execution
Implicit workflow approach

213
Public
In the Test Execution app, you can execute the test cases
that have been prepared in the Test Preparation app, and track
the progress of the test execution.
In detail, the following functions are available:
§ Assign statuses and enter comments for individual test actions
based on observed application behavior in relation to the expected
result, assign defects
§ Trigger the execution of automated test cases in the connected test
automation tool, assign defects
§ Display a history of all executed manual and automated test runs
§ Gain insight into all actions that are performed during manual test
runs, and into their statuses
§ View the overall status of a test run, as well as the statuses of
individual manual test actions
§ Access information about detected errors
§ Navigate to the connected test automation tool for more information
Performing test execution
Test Case

Defect

214
Public
Performing manual test execution for requirements without test plans
Steps
§ Use requirement traceability to
search for requirements in Status
‘To be Tested’ and prepared Test
Cases.
§ Open test execution overview for
relevant requirements and run Test.
§ Set successful test activities to
‘Pass’ or ‘Fail in case of a failure.
§ Create and process defect for failed
tests
§ Perform re-test, finish test run and
set defect to closed

215
Public
Benefits
§ Lean testing without the need
to create test plans will be still
available via filter value (None)
§ Test plans with status ‘In
testing’ available for execution
in your current test phase or
test cycle.
Test execution - test plans

216
Public
Overview
Test Execution
Analytics
The overview in the Test Execution app provide a central view of all test execution data. It it accessible directly or via
navigation from other areas. Additionally, the Test Execution Analysis provide a adaptable progress chart.
Test Execution
Solution Process
Traceability
Requirement
Traceability
User Story
Traceability
Test Execution
Analysis
Test Execution Overview

217
Public
Project Overview allows filtering for test
plan specific test information for:
§ Test case preparation
§ Test execution
§ Failed test runs
§ Defects (planned)

218
Public
The test execution overview
provides a list view of the status
of test cases for a specific
project and test plan.
Apart from the test case status,
also the test progress and the
amount of defects is visible in that
list.

219
Public
Requirement status
The requirement traceability provide a list view of the status of
requirements for a specific project, together with the status of
the related entities for each requirement.
This is helpful in terms of test execution, e.g. by searching
requirements with failed test cases.
In test execution analysis you can display e.g. by status, test
action, scope or test plan

220
Public
Process readiness
The process traceability provides a list view
of the status of the scoped processes of a
specific project, together with the status of
the related entities.
This is helpful in terms of test execution, e.g.
by searching processes with tests still in
preparation.

2.7 Realize – Defect Management
2.7.1 Maintain defect from test case
2.7.2 Maintain defects from defects app
2.7.3 Work with defects
2.7.4 Defect reporting
2.7.5 Defect traceability
Configuration Expert/Developer
Tester
Tester
Project Manager
Project Manager

222
Public
Project
Lead
/
Deployment
Manager
Functional
Expert
Requirements
approved
Break down
requirements into
user stories, sub-
tasks
Test
Build
Create or assign
features
Create test cases
Test
Manager
/
Tester
Consultant
/
Developer
Deploy
Identify test scope
Identify testers &
create test teams
scope
Configure/
develop
Test new
configuration/
development
DEV
Create transport
request
DEV
DEV
Release
transports
Validate test
coverage
Release test plan
Execute test
cases
Deploy transports
into test system
TST
Set tasks to
Approve feature for
deployment
Forward & import
transports to
production
Confirm
deployment
(requirements
status)
Report defect
Release test
cases
Requirements
deployed
Testing
Successful?
YES
NO
2.7 Manage defects
Assign transports
to feature
Create
test plan and
assign testers
Track test
progress
Confirm successful
test case
Finish test phase
Confirm
successful test

223
Public
2.7 Defect management
Defect status flow schema
New In Progress
Retest
Required
Closed
Tester Developer
Rejected
Duplicate
Assign
developer
Set tags for
evaluations
In Progress once
the developer starts
to investigate
Fixed?
Postponed

224
Public
2.7 Defect management
Defect status flow description
The Defect Workflow consists of the following steps:
§ After creation, the defect is picked up and assigned to a team, role, or directly to a processor
§ The processor is notified about their defect assignment. She/he set the defect to the status
“In Progress”, and then analyzes and resolves the issue, being described in the defect
§ Once the defect has been corrected, the processor changes the defect status to “Retest
Required” and assigns it to the original reporter
§ The reporter is notified and retests the test case in the Test Execution app
§ If the retest is successful, the defect status can be set to “Closed”

227
Public
2.7.1 Create a defect from test case
Launch the
defects app from
test execution to
create your new
defect

228
Public

229
Public
You can create a defect either
• from a test case, or
• from a test case Step

230
Public
2.7.2 Create a defect from defects app
Provide the following information when creating a defect:
§ Issue Description
§ Project
§ Scope
§ Defect Status
§ Priority
§ Release (with Release Assignment, Defect can then be viewed
in ‚Releases and Timelines App)
§ Planned Completion Date
§ Team
§ Assigned Role
§ Responsible
§ Involved Parties
§ Sub tasks can be created
§ Tags for classification purposes (opt.)

231
Public
Manually assign an existing defect to a test case

232
Public
Manually unassign an existing defect from a test case
You can also unassign a defect from a test case, if required.

233
Public
Manually assign a test case to a defect

234
Public
2.7.3 Test execution: Sort test cases by number of defects

235
Public
Create defect from template
In case it is considered as useful, you can create
Defect Templates.
Therefore you have to:
§ Prepare a defect with template related content
§ Press button ‚Edit‘
§ Activate the checkbox ‚Use this item as a template‘ on the
defect tab ‚Additional Information‘
§ Press ‚Save‘

236
Public
Create defect from template
You can now filter your newly created defect in
§ ‚Open Tasks‘, or in
§ ‚Open Defects‘
and create a new Defect from Template.
Templates can be used to:
§ Improve the governance, and
§ Streamline and speed up the creation and the
processing of defects
This functionality is available for all Task Types

237
Public
Defect notifications: Fiori launchpad notifications service
The Fiori Launchpad notifications service posts
a notification with a badge (a red dot) in the top
bar of the Launchpad, when a Defect is
assigned to you.
By clicking on the red dot, detailed information
is being provided.

238
Public
Search: Search for tasks, requirements, defects
You can utilize the Search to let the system
display
§ Tasks, Requirements, Tasks
for a specific SAP Cloud ALM Project, for
instance.
The results can be sorted:
§ Ascending / Descending
§ per Object Type
§ etc.

239
Public
CALM Dashboard – releases and timelines: Focus on defects

240
Public
In the Dashboard ‚Releases and Timelines‘, you can perform a filtering via the following filter criterias:

241
Public
When clicking on the graphical bar representing a specific SAP Cloud ALM Project, which is assigned to
the selected Deployment Plan, a Pop up is displayed, which shows the related Defects, grouped by
statuses:
By clicking on the button ‚Defects Overview‘ you can launch, the ‚Defects Overview‘ application to get the
full details for the filtered Defects.

242
Public
‘Today’ card in SAP Cloud ALM for implementation - overview
The ‚Today‘ card displays:
§ Blocked Tasks
§ Overdue Tasks
§ Unassigned Tasks
§ Unassigned Features
§ Open Defects
which are related to
§ The selected SAP Cloud ALM Implementation Project
§ The Selected Scope
which are assigned to
§ Me
§ My Roles
§ All

243
Public
Defects card in SAP Cloud ALM for Implementation - overview
By default all open Defects of your Project are displayed.
Further filter options are:
§ Filtering via specific priorities
§ Filtering via specific defect status(es)
§ Filter defects with status „Closed“

244
Public
2.7.4 Defects reporting
Defects Reporting is part of Analytics for SAP Cloud ALM for Implementation.
.
It allows a very flexible defect evaluation and to analyze overall trends for defects
based on the following filter criteria:
§ Project
§ Scope
§ Workstream
§ Priority
§ Time Frame
§ Tag
§ Assignee
§ Defect Status
§ Team

245
Public
Table view - history

246
Public
Table view – created vs. resolved

247
Public
2.7.5 Solution process traceability
Show defects as indirect assignments
In the Solution Process Traceability you can now show indirect assignments for the displayed Solution Processes by
clicking the button ‚Indirect Assignments‘:
You can decide, if
• User Stories
• Project Tasks
• Test Cases
• Defects
should be displayed in addition as Indirect Assignments of the Solution Processes.

248
Public
2.7.5 Solution process traceability
The Solution Process Traceability now additionally displays the Defect(s), which have an indirect
Assignment to one of the listed Solution Processes:

249
Public
2.7.5 Requirement traceability
In the Requirement Traceability you can now show indirect assignments for the displayed requirements
by clicking the button ‚Indirect Assignments‘:
You can decide, if
• Test Cases
• Defects
should be displayed in addition as Indirect Assignments of the Requirements.

250
Public
2.7.5 Requirement traceability
The Requirement Traceability now additionally displays the defect(s), which have an indirect assignment
to one of the listed requirements:

251
Public
2.7.5 User story traceability
In the User Story Traceability you can now show indirect assignments for the displayed user stories by
clicking the button ‚Indirect Assignments‘:
You can decide, if defects should be displayed in addition
as indirect assignments of the user stories.

252
Public
2.7.5 User story traceability
The User Story Traceability now additionally displays the defect(s), which have an indirect assignment to
one of the displayed user stories:

2.8 Build Release & Deploy
2.8.1 Plan release
2.8.2 Check feature readiness
2.8.3 Deploy features to production
2.8.4 Feature history
Project Lead,
Change Manager,
Deployment Manager
Change Manager
Deployment Manager
Project Lead,
Change Manager,
Deployment Manager

254
Public
Project
Lead
/
Deployment
Manager
Functional
Expert
Requirements
approved
Break down
requirements into
user stories, sub-
tasks
Test
Build
Create or assign
features
Create test cases
Test
Manager
/
Tester
Consultant
/
Developer
Deploy
Identify test scope
Identify testers &
create test teams
scope
Configure/
develop
Test new
configuration/
development
DEV
Create transport
request
DEV
DEV
Release
transports
Validate test
coverage
Release test plan
Execute test
cases
Deploy transports
into test system
TST
Set tasks to
Approve feature for
deployment
Forward & import
transports to
production
Confirm
deployment
(requirements
status)
Report defect
Release test
cases
Requirements
deployed
Testing
Successful?
YES
NO
2.8 Deploy to production
Assign transports
to feature
Create
test plan and
assign testers
Track test
progress
Confirm successful
test case
Finish test phase
Confirm
successful test

255
Public
2.8. Feature – preparation
Authorization roles
There are authorization roles to control
features and transports :
• Change Manager – approves features
• Deployment Manager – deploys transports

256
Public
2.8. Feature - preparation
Safeguard deployment to production
To ensure that a production system can only be delivered with a new feature in status
"Ready for Deployment" you must assign the production system to the product role
"Production" in the Project Landscape app.
In the Project Landscape app you must add a production system, e.g. for the Service Type SAP S/4HANA. In
this example we are talking about S4H.803 as production system.

257
Public
Releases and Timelines
Change and deployment leads can monitor timelines across
projects. This application supports cross project planning, showing
the releases, the project timeboxes (phases, sprints, milestones)
and software upgrades from SAP.
Release Readiness
Change and deployment leads can monitor the release readiness
based on feature deployment status.
2.8.1 Release and deployment
Planning and reporting

258
Public
2.8.1 Release planning
Quickly find updates planned by SAP
Align your project plan with planned
public cloud releases from SAP
§ Select the projects you plan releases for
§ Crosscheck by embedded link to
release navigator, if the planned project
timelines fit to the cloud releases
shipped by SAP

259
Public
2.8.1 Release planning
Get an overview of release readiness
Solution Process Traceability
Check, if your business process is ready
for deployment, e.g. by checking of test
execution, user story and requirement
status.
Cross-Project Analysis
Get an overview, if all processes of all
solutions which are part of a release, are
ready for deployment by checking the
status of:
§ Solution processes
§ Tasks and Sub-tasks
§ Requirements
§ User stories
§ Defects
§ Features

260
Public
2.8.2 Feature traceability
Check feature readiness
The feature traceability provides you insights on the feature readiness thus serving as decision basis for
delivering features accordingly.
If everything is complete, the change manager approves the feature for production.

261
Public
2.8.3 Feature delivery
Example: How to deploy features to productive tenant
• Check Transport Status
in Feature
• Forward navigation to
WebUI allows detailed
checks and
adjustments
• Updated transport
status is automatically
shown in the Feature UI
• Demo: How to deploy

262
Public
Example: Safeguard deployment to production
A production system can only be delivered with a new feature in status "Ready for
Deployment“.
In any other status of the feature a deployment to production is not possible.

263
Public
Example: Safeguard deployment to production
You have to switch to status "Ready for Deployment" first.

264
Public
Example: Production check
To prepare for the deployment confirmation you should do the following checks:
Are all transports assigned to my feature deployed to the respective production systems?
Status should be Deployed in production system and target tenant field is empty.
All changes should have reached the production systems accordingly.

265
Public
Confirm deployment
By confirming the
deployment of a
feature you are
conducting the feature
and no further changes
to it are possible. The
final state "Deployed"
indicates that the
feature was delivered
to production
successfully.

266
Public
2.8.4 History
Auditability
All changes to your features from creation in
SAP Cloud ALM, over to documenting your
changes, recording the change objects and
performing the different workflow steps,
are documented in the history.
This helps you to keep the overview of your
project and ensures the audit trail.

267
Public
1. Introduction
Agenda

268
Public
3 Where to find SAP solution specific material
SAP Cloud ALM homepage
https://support.sap.com/en/alm/sap-cloud-alm.html?anchorId=section_copy
-> Adoption cases, e.g. SAP S/4HANA Cloud Public Edition
https://support.sap.com/en/alm/sap-cloud-alm/adoption-cases.html?anchorId=section_1568800404
-> includes links to functional up to date documentation (see next slide):
https://help.sap.com/docs/cloud-alm/applicationhelp/overview
-> Featured SAP solutions supported by SAP Cloud ALM
https://support.sap.com/en/alm/sap-cloud-alm/sap-cloud-alm-for-s4hana-cloud.html?anchorId=section
-> Expert knowledge - Expert Portal
-> includes functional description and how-to videos
https://support.sap.com/en/alm/sap-cloud-alm/implementation/sap-cloud-alm-implementation-expert-
portal.html?anchorId=section_314595689_co
-> SAP Cloud ALM Best Practices Work Zone:
https://workzone.one.int.sap/site#workzone-
home&/groups/CcOyMV24vxEssXChlNzjDP/workpage_tabs/TdGL9OAUgmggINMskcVGz1?show_draft=true

269
Public
Business
Process
Expert
Consulting Expert
Test Lead
Testing Expert
Create/Plan
User Stories for
Developments
Process &
Complete User
Stories
Process Defects
Create Test
Cases
Collect and
Document
Requirements
Project
Lead
Execute Test
Cases
Setup Project
Approve
Requirements
Confirm
Requirements
Requirement
Ready for Test
Onboarding
Team Members
Plan Releases &
Timeboxes
Complete Project
Tasks
Select Process
Scope
3 Requirement driven implementation
Detailed process flow incl. links to related sap.help
Change and
Deployment Lead Create Features
Create/Assign
Transports
Deployment to
QAS
Deployment to
PRD
Manage Test
Plan & Assign
Testers
Analytics and Traceability
Run
Deploy
Realize
Explore
Discover Prepare
Sprint 1 Sprint 2 Sprint 3
Sprint 1 Sprint 1
Manage and
Execute Project
Tasks
• Test Execution Analysis
• User Story Traceability
• Burn Up Chart
• Solution Process Traceability
• Requirement Traceability
• Requirement Distribution
• Project Progress Reporting
• Task Distribution
• Task Trend Analysis
• Releases and Timelines
• Feature Traceability
Click process steps to get detailed
help.sap.com explanations

270
Public
Support
Portal
CALM
Tenant
OpenSAP
Expert
Portal
• Public Demo Tenant
• Get your own Tenant
• SAP Cloud ALM in a Nutshell
• Accelerate Cloud Implementations with SAP Cloud ALM
• Operating Cloud-Centric Solutions
with SAP Cloud ALM
• SAP Community Blogs: # SAP Cloud ALM
• Masterlist: Project and Task Management
• TechEd 2021 GitHub Repository
• New features Videos
• 10 Demo Videos (3-6min)
• Media Center: Recorded Demos
Videos
• SAP Cloud ALM Webpage
• setup and Administration Guide
• References
• Product Roadmap
• Questions and Answers
Learning
Journey
Blogs
• SAP Cloud ALM for Implementation
• SAP Cloud ALM for Operations
• SAP Cloud ALM for Implementation
• SAP Cloud ALM for Operations
Self-Enablement Resources
More
• SAP Cloud ALM E-Book
• Integrated Help Assist

Thank you.
Contact information:
Henrik Zimmermann
henrik.zimmermann@sap.com

www.sap.com/contactsap
Follow us
© 2022 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.

SLSC Implement S4HANA Public Edition with SAP Cloud ALM - Best Practice V5.pdf

More Related Content

What's hot (20)

Similar to SLSC Implement S4HANA Public Edition with SAP Cloud ALM - Best Practice V5.pdf (20)

Recently uploaded (20)

SLSC Implement S4HANA Public Edition with SAP Cloud ALM - Best Practice V5.pdf