OpenSAP Solman2-1 Week 5 All Slides

Week 5: Release Management
Unit 1: Change Logistics

Change Logistics
Deep integration between process control and underlying transport mechanism
Focused Build Processes

▪ Predefined work package / item workflows and processes
▪ Provides link between requirements and implementation with full traceability
▪ Highly integrated in other SAP Solution Manager functionalities
SAP’s Central Transport Management Infrastructure

▪ Full control and transparency over change execution
▪ Fully integrated transport mechanism and change control system to
manage changes across technology stacks and application components
▪ Incorporates SAP’s best practices for transport management
▪ One source of truth to avoid and manage risk of application changes in a
project
▪ Additional functions to increase consistency and minimize manual efforts
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Change Logistics
Transport control independent of underlying technology
Manage ABAP and non-ABAP technologies via CTS+
Transport Management System Enhanced Change & Transport System
Create and release transports in direct context of work items

Control technical deployment via workflow
&

Change Logistics
Improved monitoring with less effort
Get rid of endless spreadsheets through automatic transport tracking for

easier release deployment

Change Logistics
Following transport best practices I
“Transport of copies” is built into standard Change Request Management processes

Transport of Copies
DEV QAS PRE PRD
Original Transport
of Normal Change
Iterative testing: Possibility to test work items in QAS without releasing original transports
Only original transport will be released when whole release enters the test phase – fewer
transports for import mean less import time
Change Logistics
Following transport best practices II
Receive warnings before creating potential downgrade situations or creating a

real downgrade!
1. Cross-System Object Lock (CSOL) 2. Downgrade Protection Checks
Dev System 1
Object A
Client 1
… Production
Test
System System
Dev System 2
Client 1 Object A
…
Cross-System Object Lock

Change Logistics
Following transport best practices III
Create a blacklist of critical objects and control all changes to those sensitive objects
with additional approvals
Approve critical objects
Define critical objects via

new Administration Cockpit

Change Logistics
Flexibility if required
By default, SAP Solution Manager always keeps the import sequence of transports the same as
they were when released from the development system.
However, work items can be removed from the release and imported first if required.
WIs assigned to
release cycle
Change Logistics
Direct access to transport status
Track the status of the imports directly in the work items
Get notifications about potential risks or transport errors
? ? ? ?
Missing Transports Transport Errors Missing Synchronization Open Transports

Change Logistics
Demo

Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2021 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.
Unit 2: Software Deployment
Software Deployment
High-level process flow
Work Package Requirement
DEV QA PrePRD PRD
In
Approved Realized Productive
Realization
Single Functional Test & FIT &

Created Scoping UAT
To Be Successfully Hand Over
IT,RT Productive
Scope To Be In Develop- Tested Tested to Release
Finalized Developed ment
Unit Test
Work Item
In Develop- To Be Successfully Hand Over

Created Productive
New ment Tested Tested
Test to Release
create batch import batch import

Transport Transport
Release Import
TOC* Transport
* Transport of Copies
Software Deployment
Import jobs per test level
Prepare for
Deploy
Prepare Build Test Deploy Hypercare
Project
Realize Deploy Run
Integration Test
Integration Test
Acceptance
Acceptance
Integration
Functional
Functional
Functional
Wave 1 Wave 2
Final
Test
Test
Test
Single Single WP
Work Package Functional Functional Handover
Test Test to Release
Sprint 1 Sprint 2
Work Item Unit Test Unit Test hourly daily
Transport for Transport for
Defect Correction retesting
retesting
Test in Test in
QAS PRE PRD
Software Deployment
Define import concept and schedule import jobs
▪ Things to consider:
− For unit test, ToC will be imported to QAS right after work item has been changed to UT status
− After successful unit test, TRs will be released and imported with the next execution of import job
− When SFT/FIT/UAT starts, import to QAS for TR from work item as well as DC should be scheduled with adequate
frequency, for example, 60 minutes. (Project team should adjust the frequency according to project needs.)
− During final integration and regression test in PRE, keep import frequency for QAS and schedule automatic import to
PRE (e.g. once a day based on project requirements)
▪ Steps
1. Run transaction code SE38
2. Execute program /SALM/BATCH_IMPORT_TRIGGER
3. Select Release
4. Select variant: /SALM/QAS (Work Item & DC TR import to QAS); /SALM/RELEASE_PRE
(Work Item & DC TR import to PRE); /SALM/INTEGRATION_TEST (DC import to PRE);
/SALM/RELEASE_PRODUCTION (Work Item & DC import to PRD)
5. Select ‘Enable Automatic Rescheduling’, it will schedule itself to run again as a job

Software Deployment
Release batch import – Highlight functions
1. Simulate the import via test mode to

identify downgrades or import errors
beforehand.
2. Schedule a reoccurring job executing
the import in the desired timeframe.
3. Enable downgrade checks and skip
downgraded transports to not block
conflict-free transports.
4. Evaluate relationships between work
items or work packages that have a
logical dependency.

Software Deployment
Release batch import – Quality assurance system
Steps
1. Run transaction code SE38.
2. Execute Program /SALM/BATCH_IMPORT_TRIGGER
3. Select Release.
4. Select Variant
– /SALM/QAS
5. Check ‘Enable Automatic Rescheduling’, execute the
import regularly.
6. Activate downgrade protection (strongly recommended).
To avoid blocking of conflict-free transports, you can
activate skipping of downgrade transports.
7. During the final FIT in pre-P system, execute this import
at least every hour. (Project team should adjust the
frequency according to project needs.)

Software Deployment
Pre-checks before deployment to preproduction and production
Report /SDF/CMO_TR_CHECK – addressing import

questions before running into problems:
1. Are there sequence violations when triggering the import?
2. Are there referenced objects that will not be imported
causing an import error?
3. How long does the import take?
4. Can the import be executed online?

Software Deployment
Demo

Software Deployment
Release batch import – Preproduction system
Steps
3. Select Release.
4. Select Variant
– /SALM/INTEGRATION_TEST or /SALM/RELEASE_PRE
5. Do not check ‘Enable Automatic Rescheduling’, execute
the import just once.
6. During the final FIT in pre-P system, execute this import
once per day. (Project team should adjust the frequency
according to project needs.)
7. Check “Downgrade Protection”. Do not check “Skip
downgrade Transports”.

Software Deployment
Release batch import – Production import
Steps
3. Select Release.
4. Select Import into Production Systems, otherwise if
there is PRD system configured in the variant, it will
change to Test Run automatically.
5. Select variant
– /SALM/PRODUCTION
6. Do not check ‘Enable Automatic Rescheduling’, execute
the import just once.
– Related TRs will be imported to PRD system and SolDoc content
related to work packages will be released to Production branch
automatically.
– Related work package/work item status will be set to Productive
automatically, Defect correction status will be set to Closed
automatically.

Software Deployment
Demo

Software Deployment
Release batch import – Selection options
3
4
5
6
7
8
9
10
11
12

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 3: Release Management
Release Management
Overview architecture
Releases synchronize project go-lives and

ensure continuous delivery and integration. Agile Releases
Final UAT
and
Integration
Project to bundle deliverables. Projects Testing
Multiple and parallel projects are possible.
Phases ending with Quality Gates. Prepare Explore Realize Deploy Run
Short prepare and scope, incremental build.
User
Waves ending with acceptance Acceptance
by the business (~ 8 – 12 weeks). Test
Waves
Sprints with Show and Tell sessions to the Unit & Single
Functional
business (~ 2 weeks). Test
Sprints

Release Management
Recommendation: combined deployments
Synchronized
Go Live
Go-
Build & Functional Test Freeze
Joint Integration
Live
Test Phase
Project 1
Go-
Build & Functional Test Freeze Live
Project 2
Go-
Build & Functional Test Freeze Live
Project 3
Scope Build Test Deploy Hypercare Operate
Release 1
Reduce Risks, Simplify Go-Live Process, and Decrease Test Efforts

Release Management
Release example 1 – Synchronized waves across projects
Year
JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC
▪ Release Schedule
1.0 2.0
– Major Releases
▪ Master Project Discover & Ex-

Realize Deploy
Prepare plore
– Phases
Wave 1 Wave 2
– Waves
▪ Build Project 1 Realize Deploy

– Phases
Wave 1 Wave 2
– Waves
Sprint 1 Sprint 2 Sprint 3 Sprint 1 Sprint 2 Sprint 3
– Sprints
▪ Build Project 2 Realize Deploy

– Phases
– Waves
Wave 1 Wave 2
– Sprints
Sprint 1 Sprint 2 Sprint 3 Sprint 1 Sprint 2 Sprint 3 Release Number
X.X
Go-Live Date
Quality Gates
Release Management
Release example 2 – Independent wave schedule
Year
1.0 2.0 3.0
– Major Releases
▪ Master Project Discover & Ex-

Realize Deploy
Prepare plore
– Phases
Wave 1 Wave 2 Wave 3 Wave 4 Wave 5
– Waves Release Number
X.X
Go-Live Date
▪ Build Project 1
Realize Deploy
– Phases
Wave 1 Wave 2 Wave 3 Quality Gate
– Waves
▪ Build Project 2
– Phases Realize Deploy
– Waves
Wave 1 Wave 2 Wave 3 Quality Gate
▪ Build Project 3
– Phases Realize Deploy
– Waves Wave 1 Wave 2 Wave 3 Wave 4 Quality Gate

Release Management
Assignment of releases per project or per wave
Release to
Project
Assignment
Release to
Wave
Assignment

Release Management
Release phases
The release has many different phases which all have a defined semantic meaning.
The phases of the release also control which activities are possible in the work packages and
work items related to the release.
▪ e.g. assignment to a release, import of transports, …

Release Management
Details for the Prepare release phase
Deployment
Prepare Build Test Deployment Hypercare
Preparation
Created
In Development
Release Tasks
To Be Tested Successfully Tested

Import in QAS 
Import buffer Import buffer Import buffer
DEV QAS PRE PRD

✓
✓
✓

Release Management
Demo

Release Management
Details for the Build release phase
Deployment
Preparation

Release Management
Building the release
Steps
1. Select Mass Change for Work
Package and Defect Correction
IT.
2. Select all items in “Successfully
tested” and put them in status
Handed Over to Release if they
shall be in scope of the next
release.
Note: Handed over to Release
is the point of no return!
3. Non-completed work packages
and work items in the release
will be handed over to the next
release.

Release Management
Demo

Release Management
Details for the Test release phase
Deployment
Preparation
Handed Over to Release

(Status set by WP)
Import in PRE 
DEV QAS PRE PRD

✓
✓
✓

Release Management
Details for the Deployment Preparation release phase
Deployment
Preparation
▪ In the Deployment Preparation phase, the technical steps to perform the cutover into the production system
need to be done.
▪ This includes all required preparation steps – technical as well as non-technical.
▪ Typically, Deployment Preparation is a short phase which is directly followed by the Deployment phase.
▪ Use check report /SDF/CMO_TR_CHECK to prepare production import

Release Management
Details for the Deployment release phase
Deployment
Preparation
Productive
(Status set by Import)
Import in PRD 
DEV QAS PRE PRD

✓
✓
✓

Release Management
Details for the Hypercare release phase
Deployment
Preparation
▪ After the Deployment phase there is a special phase called “Hypercare”.

▪ This is due to the fact that usually shortly after a go-live, the number of incidents increases significantly.
▪ Sometimes this is due to missing information about the new functionality, incorrect documentation, or bugs
that have not previously been detected and solved.
▪ During this time, there is still high attention on the release and consistent monitoring of the incident queue.
▪ Usually, this phases ends after a few days or weeks – then the release will be formally handed over from the
Project team to the IT Operation team, which ensures production support.

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 4: Defect Correction
Defect Correction
Handling of defects during test execution
Test Test Create

Tester Execution Results Error? Defect
Perform
Provide Apply
L1 Support Team Root Cause
Solution Correction
Analysis
No fix
available Create
Solution Architect Correction
Process
Development Team Correction
Tester Retest

Defect Correction
Involved roles
Testing Team Defect Creation
Defect
L1 Support Team Processing
Fix? Enhancement?
Defect Requirement
Solution Architect Correction Management
Defect
Development Team Correction
Work Item

Defect Correction
High-level process with test suite and work package integration
Wait for Defect

Defect
Test Information Solution

Case Created In Process Defect Correction Confirmed
Correction in Process Required Proposal
Information
Work Package Defect Correction
To Be
Required
Retested
w/o
Transport
Being Transport to Handed Over
Created In Delivery Confirmed Closed
Corrected Retesting to Release
Scope To Be In Develop- To Be Successfully Handed Over Productive/

Created Scoping In Repair
Finalized Developed ment Tested Tested to Release Completed

Defect Correction
Seamless integration
▪ The goal is to offer seamless Defect Status Defect Correction

communication between testers and Status
the L1 and L2 support teams in the
New
defect resolution process
Wait for Error
▪ The status profiles of defect and defect Correction
Created
correction are interlinked
Information Required Information Required
▪ The tester needs to work only on the
defect Information Provided Being Corrected
▪ The developer needs to work only on Confirmed Confirmed

defect correction
▪ Status update of defect updates the
status of defect correction
automatically, and vice versa

Defect Correction
Trigger defect correction from defect
Steps
1. Update needed information and enter
description of the defect
2. Processor can perform the following actions
after checking the defect:
− Propose Solution: The defect does not
need code fix, and only need is to provide
guide to tester
− Create Defect Correction: The defect
requires code fix, Defect correction will be
created automatically, and work package
status will changed to In Repair
automatically
− Set to ‘Tester Action’: The defect is
missing information and needs tester to
provide more details
− Forward: forward defect to an expert for
feedback
3. Tester will receive an email notification if the
solution architect triggers the action → ‘E-
Mail to Reporter (Mail)’

Defect Correction
Demo

Thank you.
open@sap.com
Defect Correction
Create transport requests
Steps
1. Select Defect Correction and set to
‘To Be Corrected’
2. Then navigate to Transport tab to
create transport request
3. The related work package status will
change from ‘To Be Tested’ to ‘In
Repair’

Defect Correction
Trigger release of transport request
Steps
1. Developer selects Actions → Set to
‘Retest with Transport’
– The TR will be released
automatically
– The defect status will be changed
to ‘Solution Proposal’
automatically
2. Tester will get email notification for
retest

Defect Correction
Confirm the defect
Steps
1. Update the defect status after retest
– Confirm (defect is fixed)
– Set to ‘In Process’ (defect still
exists)
2. When the defect is confirmed, the
defect correction will be confirmed
automatically. Thus the related TR will
be ready for import to the pre-
production system
3. However, the import to pre-production
will take place after the related work
package with assigned work item(s)
and defect correction(s) has been set
to status ‘Hand over to Release’
4. The related work package status will
change from ‘In Repair’ to ‘To be
Tested’
Defect Correction
Update work package after confirmed repair
Steps
1. ‘Confirm Successful Test’ for the
related work package
2. The work package status will change
to ‘Successfully Tested’, which
indicates that this work package has
passed SFT successfully

Follow all of SAP

warranty.
Unit 5: Release Dashboard
Release Dashboard
Overview
▪ Optimized working environment for

release managers, development
teams and system owners
Release Manager Development Team System Owner
▪ Retain an overview of all ongoing
releases and related transports
▪ Easy identification of release issues
and non-compliant transports
▪ Detailed analysis via drilldown

Release Dashboard
Main features
▪ Drill down from top level dimensions to

transport request level
▪ Breadcrumb navigation to show current
context
▪ Filter options for work packages, work items,
defect corrections, and transport requests
▪ Get status ratings to evaluate the
completeness of releases
▪ Find work items and transport requests that
do not comply with the Focused Build release
building process
▪ Interface to mass change app

Release Dashboard
Functions
1 3 1 3 1 3
Features
▪ Drill down from top level dimensions to
1
transport request level
2▪ Filter options available, e.g.
Development Team or Ratings
2 3 1 2 3 4 1 2 3
3▪ Status ratings
4▪ Evaluate work Items and transport

requests that do not comply with the
Focused Build release building process
1 2 3 2 3 2 3 4

Release Dashboard
New with SP03 – Integration to the mass change application
Interface to the mass change

app for work packages, work
items, and defect corrections
Benefits
Selection of work packages,
work items, and defect 2
corrections via release
dashboard and transfer to the 1
mass change app
Usage example
▪ Work packages are selected
1
▪ Work packages are
2
transferred to the mass
change app

Release Dashboard
Individual view – Customize what you want to see
1▪ Tiles can be hidden via Customizing
2▪ Information that is not needed is not displayed

Release Dashboard
Tile for work item
1
1 New tile for work items
Work items can be

evaluated independently
of the work packages in
which they have been
scoped

Release Dashboard
Provided ratings
▪ Status Compliance Rating – Checks that a WP or WI

is in the right status compared to the Release Status
▪ Test Rating – Checks that a Work Package is part of
a Testplan/Testpackage
▪ Document Rating – Checks for every WP/WI to see if
a required document in the required status exists
▪ Transport Rating – Checks that a transport is
successfully imported in the right system according to
the status of the work item or release
▪ Retrofit Rating – Checks if a transport created in the
maintenance landscape has been retrofitted to the
project landscape

Release Dashboard
Provided ratings – Benefits during Build-Phase of the Release
▪ Release Dashboard bridges the gap between WP status and readiness of underlying transport to be
imported to Preproduction system
▪ Release Manager has more decision criterias which WP shall be part of the release and which shall be left
behind (e.g. due to missing documents)
▪ Direct access from Release Dashboard to Mass Change app to take over Release Selection

Release Dashboard
Demo

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 6: Handover to Operations
Handover to Operations
Hypercare phase
Deployment
Preparation
Challenges in Hypercare Phase:

▪ The number of incidents shortly after Go-Live increases significantly due to unknown functionality, wrong
documentation, or bugs
▪ The incidents are usually processed by the Project Implementation team that was involved in the release
development
▪ For incident processing, a dedicated process will be used – different options exist for that

Available options
Variant 3: Standard
SAP Solution Manager
Variant 2: Focused
Build Fix Pace
Variant 1: Focused ▪ Usage of separate
Build Simple Flow change cycles
▪ Individual
▪ RfC and urgent and maintenance
▪ Usage of existing
standard change processes (UC,
implementation
process NC..)
project
▪ WP and WI process

Variant 1: Focused Build simple flow
Year
1.0 2.0 3.0
– Major Releases
▪ Build Project 1
Release Number
– Phases X.X
Go-Live Date
• Build Wave 1 Preliminary Import
▪ Build Project 2
– Phases Wave 2 Preliminary Import
• Build
To release urgent fixes

Wave 3 Preliminary Import
▪ Create Work Package
▪ Select Build Project
▪ Select Wave
▪ Use Work Item with Action
Preliminary Import

Variant 1: summary of activities per role
Tool Lead
No action needed
Key User / Business Analyst / End User
User needs a quick fix → Create incident or requirement
Service Desk / Organization
Transport for fix is needed → Create work package
Architect
Scope work package, create work item
Developer
Process work item
2nd Developer / Architect
Unit test → Set status Successfully Tested (Work Item)
Request preliminary import
Architect
No test on work package level
IT Operator
Trigger import to production system
Variant 2: Focused Build extended flow
Year
1.0 2.0 3.0
– Major Releases
▪ Build Project 1
Wave 1 Release Number
– Phases X.X
Go-Live Date
• Build Hypercare
Wave 2
Hypercare
Wave 3
Hypercare

Variant 2: summary of activities per role 1/2

User needs a quick fix → Create incident
Transport for fix or enhancement is needed → Create request for change
Architect / Change Manager
Scope request for change, create change documents (type urgent or
standard change)
Developer
Process change document and set status To Be Tested, which triggers the
automatic import into QAS in case of an urgent change

Variant 2: summary of activities per role 2/2
2nd Developer / Architect / Change Manager

After unit test, set status Successfully Tested and the
transport(s) are automatically imported into PRE in case of an
urgent change
Change Manager
Set status Handover to Production
Release Manager
Set status Productive, which will trigger the import into PRD in
case of an urgent change
Change Manager
Set status Confirmed of the RfC

Variant 3: SAP Solution Manager full scope
Year
1.0 2.0 3.0
– Major Releases
Realize
▪ Build Project
Wave 1 Release Number
X.X
▪ Build Project Go-Live Date
Realize
▪ Build Project Wave 2
Realize
Wave 3
Perform urgent fixes on maintenance branch
▪ Create Request for Change Project Cycle in Change Request Management
▪ Use Change Document
Change Change Change Change Change
Change Change Change Change Change
Change Change Change
SAP Solution Manager full scope – additional systems required
To be added
Development Quality Assurance

Maintenance System System
Production System
Development Quality Assurance Pre-Production

Innovation System System System

Variant 3: summary of activities per role
Tool Lead
Create change cycle (phase/release/continuous)
User needs a quick fix → Create incident
Transport for fix is needed → Create request for change
Architect
Create change
Developer
Process change
2nd Developer / Architect
After unit test → Request preliminary import
Architect
No test on request for change level
IT Operator
Trigger import to production system
Project Manager
Go to CRM UI (standard ChaRM) to get an overview of maintenance activities
Checklist for change request management implementation
✓ Change processes defined?
✓ Roles and responsibilities defined?
✓ Release management defined?
✓ Responsibilities for dual-landscape-synchronization defined?
✓ Cutover strategy from innovation to maintenance landscape defined?
✓ Training concept and training material created?
✓ Suitable ChaRM Go-Live defined?
✓ Internal resources enabled for ChaRM-support?

Available variants – summary
Variant 1 ▪ No extra implementation efforts ▪ No immediate solving of

incidents
▪ Continued usage of known Focused ▪ No split between
Build processes innovation and
maintenance
▪ Available from SP0
Variant 2 ▪ No extra implementation efforts ▪ As of SP04
▪ Segregation of innovation and
maintenance from a process perspective
▪ Familiar process with known SAPUI5
Variant 3 ▪ Segregation of innovation and ▪ Different UIs used
maintenance ▪ Additional systems
▪ Individual processes designed for required
customer ▪ Increased complexity

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 7: New Features Since SP03
What’s New with Focused Build SP4?
Defect Corrections
Defect and Defect Correction – New with SP04
Additional column for Defect Corrections in WP View
Applications
Solution Readiness Dashboard
Feature details
• The new column ‘Defect Corrections’ is available in
the ‘Work Package Detailed View Table’ of the
Solution Readiness Dashboard.
This column displays the number of Defect
Corrections, which have been created during the
Single Functional Test and which have an
assignment to a Work Package.
• If you click on the link (number of Defect
Corrections), detailed information for the selected
Defect Corrections will be displayed in a second
table.

Offer a new tile ‘Defect Corrections in Single Functional Test’
Applications
Solution Readiness Dashboard
Feature details
• The new tile ‘Defect Corrections in Single
Functional Test’ is offered with SP4.
• The tile will have 4 bars:
• Completed: DC User Status = Confirmed,
• To be Done: DC User Status = all Statuses below
‘Confirmed’ except Status ‘Withdrawn’
• Withdrawn: DC Status ‘Withdrawn’
• Overdue: Milestone ‘SFT Finished’ is reached and DC is
not yet set to User Status ‘Confirmed’
• Information Help is available.
• Each Defect Correction, which has been created

during the Single Functional Test and has an
assignment to a Work Package, will be displayed
in one of the bars of the new tile, dependent on its
User Status.

Make tab ‘Documentation’ available for ‘My Defect Corrections’ App
Applications
Generic App
Feature details
• The tab ‘Documentation’ is now available for the
Defect Correction.
• If required,
• Structures from Business Processes, or Libraries can be
assigned a Defect Correction, and
• new/updated Documents can be uploaded via DropDocs.
• In case that a Defect Correction is in the Scope of
a Work Package, assigned Structures and
Documents will be inherited in both directions.

‘My Defect Corrections’ App: Display ‘Project’ and ‘Wave’
Applications
Generic App
Feature details
• In addition to the assignment of a Defect
Correction to the ‘Actual Release’, the
• ‘Project’ and
• ‘Wave’
information is now displayed in the tab ‘Details’.
This information is inherited from the Predecessor
Document (Defect or Work Package).

Enhance ‘Mass Change Operations’ App for Defects
Applications
Mass Change Operations App
Feature details
• The ‘Mass Change Operations’ App has been
enhanced for Defects.
• Defects can be filtered according to various filter
criteria.
• The Focused Build Test Manager can now easily
filter defects based on the following filter criteria:
• Project
• Wave
• The filtered Defects can then be dispatched

to the responsible Focused Build Architect
utilizing the Mass Change capabilities.

What’s New with Focused Build SP5?
Defect Corrections
Defect and Defect Correction – new with Focused Build SP5
Partner Functions in ‘My Defect Corrections’: ’Architect’ instead of ‘Change Manager’
Application
‘My Defect Corrections’ App
Feature details
• In Focused Build ‘Requirement to Deploy’ the
Architect is the appropriate role to create and
process Defect Corrections.
• Focused Build related Partner Functions for Defect
Corrections need to be adjusted:
• Partner Function ‘Architect’ instead of ‘Change Manager’
should be displayed in the tab ‘Details’ of the Generic
App ‘My Defect Corrections’.
Benefits
Adjustment of Focused Build Partner Functions

‘My Defects’: Allow Filtering for ‘Message Processor’
Applications
Generic App ‘My Defects’
Feature details
• Currently only the filter ‘Assigned to’ with the filter
options ‘All’, ‘Me’ and ‘My Team’ is available.
Thereby you can filter Defects to which you, or
your Team, has been assigned to with the Partner
Function ‘Reported by’ (Reporter).
• For the daily work, it is essential to allow filtering of
Defects according to Partner Function ‘Message
Processor’ in the Generic App ‘My Defects’ in
addition.
• After having selected the Partner Function ‘Message
Processor’, you can search for a specific Business
Partner Name on the second filter level.
Benefits
Involved Focused Build Roles as Reporter or
Test Manager can filter Defects according to Partner
Function ‘Message Processor’.

Mass Change for Defect Corrections: New Filter Field ‘Work Package Assignment’
Applications
Mass Change Operations App for Defect Corrections
Feature details
• It is currently not possible to filter all Defect Corrections,
which have been created for the Functional Integration Test
(FIT).
• Enhance the Mass Change Operations App for Defect
Corrections by the new default filter field ‘Work Package
Assignment’.
• It has three options:
• All Defect Corrections,
• Assigned Defect Corrections, and
• Unassigned Defect Corrections
The ‘All Defect Corrections’ option is the default.
• As Defect Corrections, which have been created for the FIT
do not have an assignment to a Work Package, you have to
select the option ‘Unassigned Defect Corrections’ for filter
field ‘Work Package Assignment’ to filter them.
Benefits
Release- and Test Manager can perform tool based filtering of
all Defect Corrections, which have been created for the FIT of
the Actual Release.

Mass Change for Defect Corrections: ‘New Opt. Filter Field ‘Referring Work Package’
Applications
Mass Change Operations App for Defect Corrections
Feature details
• The new optional filter field ‘Referring Work
Package’ is available in the Mass Change
Operations App for Defect Corrections.
• This field only supports comma separated Work Package
ID values. There is no F4 help available for this field.
• The ’Referring Work Package’ can be optionally
displayed in the result table as a read-only field.
It has a link to the Work Package.
Benefits
Allows filtering of Defect Corrections with Work
Package Assignment based on referring Work
Package ID.

What’s New with Focused Build SP6
Defect and Defect Correction
Withdraw Defect Correction in Status ‘Being Corrected’, if no transport with piece list is assigned
Applications
Generic App ‘My Defect Corrections’
Feature details
• So far it was only feasible to withdraw a Defect
Correction in the initial User Status ‘Created’.
• Based on the new Customizing, you can now
withdraw a Defect Correction in User Status ‘Being
Corrected as well, as long as no transport with
piece list is assigned to the document.
Use Case
• Enhanced Flexibility
• A Defect Correction, which is not needed
anymore, can now be withdrawn in User Status
'Being Corrected', and not only in the initial status.

‘My Defect Corrections’ availability of CRM Action ‘Reset to ‘Being Corrected’ only when WP is Predecessor
Applications
Feature details
• The Defect Correction is either set to the User
Status
• ‘Transport to Retesting’, or
• ‘To Be Retested w/o Transport’
• The CRM Action ‘Reset to ‘Being Corrected’ is only
available in the Action Menu, if the Defect
Correction has a Work Package as Predecessor
Document.
• In case that a Defect is Predecessor of the Defect
Correction, the Tester must trigger all actions from
the Defect itself.
Use Case
CRM Action Profile has been adjusted to the Focused
Build Best Practice Use Cases for Defect and Defect
Correction.

Establish Check ‘S1_IMPORT_INTO_T_OK’ to check for successful import of Defect Correction into QAS
Applications
Generic App ‘My Defects’, ‘My Defect Corrections’
Feature details
• ‘My Defects’ App: after successful SFT / AT test, the
Focused Build Tester wants to set the Defect to the User
Status ‘Confirmed’.
• The new Consistency Checks ‘S1_IMPORT_INTO_X_OK’
and 'S1_IMPORT_INTO_T_OK' are executed.
• The Consistency Check ‘S1_IMPORT_INTO_T_OK’ will check, if the
transport(s), which is (are) assigned to the related Defect Correction,
has (have) been successfully imported into the QAS System.
• If this is not the case, the system will reset the Defect to the User
Status ‘Solution Proposal’. The assigned Defect Correction is reset
to the User Status ‘Transport to Retesting’.
• The user will receive an error message with detailed information.
• These new Consistency Checks are also established
for Defect Corrections with Work Package as predecessor.
Use Case
Ensure that the Defect / Defect Correction Workflow is in sync
with import into Target System (QAS).

Establish Check ‘S1_IMPORT_INTO_X_OK’ to check for successful import of Defect Correction into Pre-prod
Applications
Feature details
• ‘My Defects’ App: after successful FIT / RT test, the
Focused Build Tester wants to set the Defect to the User
Status ‘Confirmed’.
• The new Consistency Check ‘S1_IMPORT_INTO_X_OK’ is
executed.
• As first step, it is checked, if the Actual Release Phase is 'Test',
• As next, the new Consistency Check 'S1_IMPORT_INTO_X_OK' will
call the Consistency Check, which has been entered as Parameter
Value for the new Parameter ‘/SALM/IMPORT_PREPROD_CHECK’
in table ‘AGS_WORK_CUSTOM’ in SAP Solution Manager.
• In case that no value is exists, the Consistency Check
‘IMPORT_INTO_1_OK’ is called,
• The called Consistency Check will verify, if the transport(s), which
is (are) assigned to the related Defect Correction, has (have)
been successfully imported into the Pre-prod. System.
• If this is not the case, the system will reset the Defect to the User
Status ‘Solution Proposal’. The assigned Defect Correction is reset
to the User Status ‘Transport to Retesting’.

Establish Check ‘S1_IMPORT_INTO_X_OK’ to check for successful import of Defect Correction into Pre-prod
Applications
Feature details
• The called Consistency Check will verify, if the
transport(s), which is (are) assigned to the related
Defect Correction, has (have) been successfully
imported into the Pre-prod. System.
• If this is not the case, the system will reset the Defect
to the User Status ‘Solution Proposal’. The assigned
Defect Correction is reset to the User Status ‘Transport
to Retesting’.
• the user will receive an error message with detailed
information.
Use Case
• Ensure that Defect / Defect Correction Workflow is in
sync with imports,
• A Defect, created for FIT or RT, can only be set
to 'Confirmed', if the transport, which is assigned to
the related Defect Correction has been imported
successfully to the Pre-prod System.

Adjust Consistency Check ‘S1_RM_CHECK_OPEN_DC’ for switching Release Phase to ‘Deploy’
Applications
Deployment & Release
Feature details
The Consistency Check
‘S1_RM_CHECK_OPEN_DC’ is triggered when you
switch the Actual Release to ‘Deploy’ Phase.
• In case that unfinished Defect Corrections
• with Priority 1 or 2,
• which have been created for the Functional
Integration- or Regression Test
are found, the Focused Build Release Manager will
receive an Error Message in the CRM Web UI and the
Release Phase cannot be set to ‘Deploy’.
• The identified Defect Corrections must be finished and
be set to the User Status ‘Handed Over to Release’ at
first, before you can switch the Actual Release to
‘Deploy’.
Use Case
Ensure, that the Actual Release cannot be deployed,
if Defect Corrections for FIT / RT with Priority 1 or 2
have not been resolved and set to 'Handed Over to
Release'.
‘My Defects’ App: Tab Indicator (Counter) for No. of Attachments
Applications
Feature details
• A new Tab Indicator (Counter) is available for the
tab ‘Attachments’ of the Generic App ‘My Defects’
• The number of uploaded documents is displayed at
tab level.
Benefit
• Convenience for the Focused Build User,
• The number of uploaded documents is visible at a
glance without switching to tab ‘Attachments’.

New (User) Status ‘In Delivery’ for Focused Build Defect Correction Workflow I
Applications
Feature details
• Prerequisite:
• Active Import Feedback must be configured (please refer
to the Config. Guide for FB SP07, Chapter 6.2.7).
• The new status ‘In Delivery’ is introduced for the
Focused Build Defect Correction Workflow.
• When the Focused Build Developer has finished
his correction assigned to a Defect Correction,
created for SFT/AT, he triggers the action ‘Set to
‘Retest with Transport’,
• The original transport request is released,
• The Defect Correction is set to the new status ‘In
Delivery’.
• The import to the QAS System will be performed
via the periodically scheduled Release Batch
Import program with Import Variant /SALM/QAS.
• In case of successful import, the target status ‘Transport
to Retesting’ will be automatically set by the Release
Batch Import program.
New (User) Status ‘In Delivery’ for Focused Build Defect Correction Workflow II
Applications
Feature details
• Regarding a Defect Correction for FIT/RT, please
execute the Release Batch Import program with
• Import Variant /SALM/INTEGRATION_TEST_QAS for the
Import to the QAS System at first, and then with
• Import Variant /SALM_INTEGRATION_TEST_PRE for the
Import to the Pre-production System.
• Activate the Radio Button ‘Check for complete WP Import’ for
Program /SALM/BATCH_IMPORT_TRIGGER with Import
Variant /SALM_INTEGRATION_TEST_PRE
• The target status ‘Transport to Retesting’ will only be set, if the
import to the Pre-production System was successful.
Please note: If you run the Release Batch Import program
in dialogue mode, you must leave the program completely,
after the protocol for the import run is displayed. Otherwise,
the CRM Documents are locked.
Benefit
• Better support of the individual tester.
The Status ‘Transport to Retesting’ indicates that
the import of the assigned transport to the Target
System has been performed successfully.
New Check, when setting DC for SFT/AT to status ‘Handed Over to Release’
Applications
Feature details
• ‘My Defect Corrections’ App: For a Defect
Correction, which has been created for SFT or AT,
and which is set to the user status ‘Confirmed’, the
CRM Action ‘Handover to Release’ is not displayed
in the Action Menu.
Use Case
• Avoidance of Functional Inconsistencies
• Only Work Packages, which should go live with the
Actual Release should be set to the user status
‘Handed Over to Release’ by the Focused Build
Release Manager in Release Phase ‘Build’.
• Confirmed Defect Corrections, which have been
created for SFT or AT, always have an assignment
to a Work Package. When setting the referring
Work Package to the user status ‘Handed Over to
Release’, assigned, confirmed Defect Corrections
will be automatically set to ‘Handed Over to
Release’ as well.
Creation of new Defect Corrections for Defects with withdrawn Defect Corrections
Applications
My Defects
Feature details
• You can create a Defect Correction as Follow up
Document of a Defect, if either
• no Defect Correction has been created yet, or
• no active Defect Correction exists (a Defect Correction,
which is set to status ‘Withdrawn’ is classified as
inactive).
• The ‘My Defects’ app – tile ‘Details’ displays the
active Defect Correction,
• The ‘My Defects’ app – tile ‘Relations’ shows the
entire docflow (active and inactive Defect
Corrections).
Benefit
• In case that a Defect Correction has been
withdrawn, due to a misunderstanding, a new DC
can be created for the same Defect.

’ Withdraw Defect in status “In Process”
Applications
My Defects
Feature details
• A Defect which is set to status ‘In Process’ can
now be withdrawn.
• Prerequisite: The Current User can only withdraw the
Defect, if he is also assigned to the Partner Function
‘Reporter’.
Benefit
• Better Support of the Defect Workflow:
a Defect can be withdrawn in statuses ‘New’,
‘Tester Action’, and ‘In Process’.

Withdraw Defect only when Current Processor is set as Reporter
Applications
My Defects
Feature details
• If you execute the action ‘Withdraw’ for a Defect as
Current User, you are only authorized to withdraw
the document, if you are the Reporter of the
Defect.
• In case that you are not authorized to withdraw the
Defect, you will receive the following Error Messages in
the ‘My Defects’ app’s Message Icon:
• Status was reset by system.
• Withdrawal of Defect is not allowed. Current User is
not the Reporter.
Benefit
• Ensure Process Governance: only the Reporter of
a Defect should be authorized to withdraw the
document, if it is required.

New text type “Proposed Solution” for Defect Corrections
Applications
My Defect Corrections
Feature details
• For a Defect Correction in status ‘Being Corrected’,
the new text type ‘Proposed Solution’ is available.
• For a Defect Correction without Transport Assignment, it
is mandatory to select the new text type ‘Proposed
Solution’ and enter a Long Text, before you can set the
Defect Correction to target status ‘To Be Retested w/o
Transport’.
• The new text type, will be inherited to the related
Defect and will be visible for the Reporter/Tester.
• If no text for text type ‘Proposed Solution’ has been
entered, the status is reset by system and you will
receive detailed Error Messages.
• For a Defect Correction with Transport it is optional to
make use of the new text type ‘Proposed Solution’.
Benefit
• Provide a meaningful text type to describe the
proposed Solution to resolve a Defect.
•
Automatic actions for Defect email notification
Applications
My Defects
Feature details
• Provide automatic Actions for email notification for
the Focused Build Defect:
• S1DM_MAIL_REPORTER, and
• S1DM_MAIL_PROCESSOR.
The required Configuration Steps are described in
Chapter 7.2.9 ‘My Defects: Configuring automatic Actions
for Email Notification’ in the FocusedBuild_ConfigGuide
8.00.
• With the Status Change of the Defect, an

automatic email notification will be sent out to the
relevant Focused Build User, if the required
Configuration has been performed.
Benefit
• Better Support of Focused Build Defect Process
via automatic email notifications.

Release Management
Release Management – new with Focused Build SP6
Integration to the Transport Related Check Framework
Application
Release Batch Import
Feature details
• Enable transport related check
framework for import runs with release
batch import
• Access to additional checks beyond
down grade protection such as cross
reference check, ABAP test cockpit or
custom checks
Benefits
Improved transport security, more checks
available
Release Management
Adjust automatic Reassignment of open Docs in Hypercare Phase
Applications
Release Management
Feature details
• Ensure the smooth, automatic Reassignment
of open Documents when switching the
Actual Release to Hypercare Phase,
• in case that more than one of the Successor
Waves have the same Release assigned.
• in case Defect Corrections for FIT have been
created for the Master Project, the Build Project(s)
or for both,
Use Case
• Automatic Reassignment of open Documents
in Hypercare Phase is enabled for all
Focused Build Scenarios.

UI5 Tile for monitoring batch import
Application
Feature details
• New Ui5 Tile for the Release
Managers Work Center
• Get direct access to monitor SLG1
and extended logs of run batch jobs
Benefits
• Improved user experience
• Better error handling and more
details to easier find potential
issue root cause
Monitoring the asynchronous status set after import
Application
Program: /SALM/BATCH_IMPORT_STAT_BUFFER
Feature details
• New report to check the asynchronous
status set after import run
• Possibility to trigger status set again or
delete
Benefits
• Improved user experience
• Easier access to check correct status
settings after import

Automatically reassign when Release switch to "TEST“
Application
Release Management
Feature details
• Automatically reassign open change
documents to the successor release
already, when the release is switched to
phase “Test”.
Benefits
• More agile processing
• Keep developing your increments
also during release testing

Automatically reassign when Release switch to "TEST“ – Automatic Reassignment options
Optional Mandatory
automatic Reassignment automatic Reassignment
Deployment
Release 1.0 Created Prepare Build Test
Preparation
Deploy Hypercare Operate Completed
Optional Mandatory
automatic Reassignment automatic Reassignment

Deployment
Deploy Hypercare …
Preparation

Deployment …
Preparation

Automatically reassign when Release switch to "TEST“ – Details
Phase dependency for reassignment for Focused Build Release
Optional early automatic reassignment

when release phase switch to “Test”
Deployment
Created Prepare Build Test Deploy Hypercare Operate Completed
Preparation
Manual reassignment allowed Reassignment not allowed
Mandatory automatic reassignment

when release phase switch to “Hypercare”

Status dependency for reassignment to a later release for Work Packages
Handed
Scope To be In To be Successfully
Created Scoping Over to Productive Completed
Finalized Developed Development tested Tested
Release
Reassignment allowed Reassignment not allowed
Handover to Release

Status dependency for reassignment to a later release for Work Items
In Successfully Handed over

Created To be tested Productive Completed
Development tested to Release
Handover to Release

Status dependency for reassignment to a later release for Preliminary Work Items
Preliminary Test for

In Successfully Released for
Created To be tested Import Preliminary Productive Completed
Development tested Production
Requested Import
As soon as Preliminary Import was requested

the Work Item has to be finished
within the current Release
Early Reassignment
When Early Reassignment is switched on, you can automatically
reassign open change documents to the successor release already,
when the release is switched to phase Test.
When Early Reassignment is switched off, the automatic
reassignment of open change documents to the successor release
is executed only, when the release is switched to phase Hypercare.
Note: Only change documents that have not reached status

Handed over to Release can be reassigned to a successor
release.

Cross Project Reassignment

When Cross Project Reassignment is switched on, open change
documents can be reassigned to the successor wave/release of a
project different than the current one. An additional popup will
appear to choose the target project and wave.
When Cross Project Reassignment is switched off, open change
documents will be reassigned to the successor wave/release of the
current project. No additional popup will appear.
Note: Only change documents that have not reached status

Handed over to Release can be reassigned to a successor
release.
Release Dashboard
Release Dashboard – new with Focused Build SP7
Realtime update of Dashboard data
Feature
Refresh Button for Release and
ChaRM-Dashboard
Only on the overview screen
Benefits
Realtime data are displayed in the
dashboards.

New field Defect Corrections
Feature
New field Defect Corrections
Benefits
Answers the question, which Defect
Corrections are assigned to a Work
Package

New field Referring Work Package
Feature
New field Referring Work Package
Benefits
Answers the two questions:
Which Workpackage is assigned to a
defect correction?

Release Management
New fields in result list
Application
Release and Change Request
Management Dashboard
Feature details
Three new fields in the result list:
▪ Classification
▪ Category
▪ Changed By
Benefits / Use Case

Classification, Category and Changed
By fields of Work Packages, Work
Items and Defect Corrections are
displayed on the Release Dashboard.

Cloud TMS integration
Description
• Enable Cloud Transport Management Service (TMS)
• Configure nodes and routes in Cloud Transport
Management Service and use them in Focused Build
• Read-out transport nodes and routes from Cloud
TMS into Focused Build Batch Import
• Integrate Business Technology Platform transports
on Neo or Cloud Foundry)
Benefits
• Similar look and feel like CTS/CTS+
• Governance and auditability
• Prepared for future cloud products
• Higher automation

Reset change documents after system upgrade
Application
Reset Report to be performed after System Upgrade
Feature details
Report /SALM/RESET_CD_OF_CYCLE resets Change
Documents and related Transport Requests after a system
upgrade.
Benefits / Use Case

Customers that are running a Focused Build or Change Request
Management project sometimes face the challenge that the
system landscape must be upgraded in the course of the
project. The recommendation before the upgrade is to clear the
whole landscape from all transports which is often not possible.
The new Reset-report supports customers in this situation
immediately after the upgrade. The report checks to a given
change cycle the related documents (e.g. Work Items, Normal
Changes etc.) and assigned transports. In an Upgrade-case, the
report resets all change documents back to in development and
repacks released transport requests into new transports with the
most recent version from the new System, afterwards import
buffers are cleaned up.

Thank you.
open@sap.com
Follow all of SAP

warranty.
See www.sap.com/copyright for additional trademark information and notices.

OpenSAP Solman2-1 Week 5 All Slides

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenSAP Solman2-1 Week 5 All Slides

Uploaded by

Copyright:

Available Formats

Week 5: Release Management

Unit 1: Change Logistics

Focused Build Processes

SAP’s Central Transport Management Infrastructure

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Manage ABAP and non-ABAP technologies via CTS+

Transport Management System Enhanced Change & Transport System

Create and release transports in direct context of work items

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Get rid of endless spreadsheets through automatic transport tracking for

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

“Transport of copies” is built into standard Change Request Management processes

DEV QAS PRE PRD

Receive warnings before creating potential downgrade situations or creating a

1. Cross-System Object Lock (CSOL) 2. Downgrade Protection Checks

Cross-System Object Lock

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Approve critical objects

Define critical objects via

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Track the status of the imports directly in the work items

Get notifications about potential risks or transport errors

Missing Transports Transport Errors Missing Synchronization Open Transports

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

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

DEV QA PrePRD PRD

Single Functional Test & FIT &

In Develop- To Be Successfully Hand Over

create batch import batch import

Realize Deploy Run

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

1. Simulate the import via test mode to

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Report /SDF/CMO_TR_CHECK – addressing import

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

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

Releases synchronize project go-lives and

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Scope Build Test Deploy Hypercare Operate

Reduce Risks, Simplify Go-Live Process, and Decrease Test Efforts

▪ Master Project Discover & Ex-

▪ Build Project 1 Realize Deploy

▪ Build Project 2 Realize Deploy

▪ Master Project Discover & Ex-

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

To Be Tested Successfully Tested

Import buffer Import buffer Import buffer

DEV QAS PRE PRD

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

Handed Over to Release

Import buffer Import buffer Import buffer

DEV QAS PRE PRD