SAP Solution Manager for SAP S/4HANA upgrade projects

SAP Solution Manager

for SAP S/4HANA

upgrade projects

Robert Garcia Jr

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

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


If you have questions during the session, please use

the Q&A functionality in Zoom.

We will answer your questions during our Demo and

Q&A time slots.

Questions?


➢ Scope and Effort Analyzer – How to Use

➢ Business Process Change Analyzer – How to Use

➢ Upgrade Project – Reset Report

➢ Demonstrations and Q&A

Agenda

Scope and Effort Analyzer (SEA)How To Use


Business Process

Change Analyzer

(BPCA)

Test Execution

• Manual Test Execution

• Automated Test Execution

• Defect Management

Test Suite Analytics

• Gap reports

• Status reports

• Progress reports

• Dashboard

other 3rd party

Change Impact Analysis

SAP Test Suite - CBTA (Component Based Test Automation)

Test Plan Management

• Test Plan

• Test Packages

• Test Sequences

• Tester assignment

Scope and Effort

Analyzer (SEA)

Test scope estimation

before upgrade

Test scope optimization

during change events (fix,

enhance, innovate, upgrade)

Solution Documentation

• Executable Library

• Process Step Library

• Business Processes

Test Automation Framework

Test Data Test Data Container (TDC)

Test data storage for manual and automated tests

Test Cases

• Manual Tests

• Automated Tests

Solution

Documentation Test Planning Test Execution and Analytics

Change Impact

Analysis

Tricentis Test Automation for SAP

SAP Enterprise Continuous Testing by Tricentis

Test Data Provisioning

in SAP Enterprise Continuous Testing by Tricentis

SAP Change Impact

Analysis by Tricentis

Test Data Services

in Tricentis Test Automation for SAP

SAP Solution Manager – Test SuiteCapabilities in details

SAP Enterprise Support Additional license required


Scope and Effort Analyzer (SEA) helps to resolve Project Issues

Usage and Procedure

Logging (SCMON /

UPL)

▪ SAP Kernel based logging

technology with no manual effort

▪ Transparency about usage

information of ABAP procedure units

▪ Clear statements about system

usage

No

Transparency

What custom code and

modifications are used

in PRD?

Sandbox

upgrade

required

Sandbox update or test

installation always

required to evaluate

change impact and

implementation effort

SAP object lists now

obtainable with

Maintenance

Optimizer procedure

▪ Transparency about SAP

objects implemented with S/4

Release Upgrade before

physical installation

Set-up efforts

for existing

analysis tools

Excellent capabilities

of BPCA, but

significant

implementation efforts

for setting-up Solution

Documentation

Semi-dynamic TBOM

generation based on

SCMON / UPL

Automated Generation

of Documentation (SAP

Module oriented)

▪ Simplified set-up of BPCA

▪ Test scope optimization with

significant reduced test scope and

test effort

Issue Solution Benefits


SEA / BPCA - Implementation approach within SAP Solution Manager

regarding a S/4HANA Release Upgrade

Install SAP

Solution Manger

7.2 system

Basic setup

including System

Landscape

connection

Setup the generation job

(usage data from ST03)

for:

- Executables

- Developments

Set Up UPL/ SCMON

to collect TBOM

Usage Information

Create business processes

- decide on modules to document

- Represent E2E processes

Set Up CCLM and

Test Management

Import structures for

libraries by Excel

upload (step library)

Import Best Practice

content (S/4HANA)

Create MP Transaction

for new S/4HANA

Release

Run Scope and Effort

Analyzer Transaction

Create TBOMs –

dynamically / semi-

dynamically


How To Use SEA for an effort estimation during a S/4HANA Release Upgrade

Business Process Change Analyzer (BPCA)How To Use


Business Process Change Analyzer

Risk-based Test Scope

„Can I get a recommendation

for regression tests?“

Business Process Change Analyzer

✓ Identification of business processes impacted by software changes

✓ Support decision making whether planned change shall be executed

✓ Automatic test plan generation

Change Impact Analysis

„Which critical Business Processes

will be affected by planned changes?“

Planned Change

SP/ EhP S/4 HANA Transport Change Object

Release Request Document List

Business Processes

Preparation

„What have to be prepared

in the system before I can

use Business Process

Change Analyzer?“

Business Processes Technical Bill of Material (TBOM)

Tables Code UI

…

System Landscape

DEV QAS PRD

ERP

EPCRM


TBOM:

List of technical objects

involved in the processing of

the executable

BPCA Overall Concept

Executable 1

Test Cases:

Manual and automated

TBOM:

List of technical objects

involved in the processing of

the executable

Executable 2

Test Cases:

Manual and automated

Incoming Software Change,

e.g.:

• SAP Support Package

• SAP note (s)

• Customer Development (transports)Change

Impact

Executable 1 is identified as impacted.

It will be added to the test scope proposal

using the associated test cases (if available)


Test Scope Optimization - OverviewTest Scope Optimization Ranking

Targeted test coverage and

effort

Expected effort for automated

tests

Expected effort for manual

tests

Selected processes to be

tested

Cumulated coverage of

changed objects

Ranking of impacted Process

Steps


BPCA and SEA – TBOM Usage

Best Practice

• Mission critical business processes, process steps and assigned executables

• Make use of dynamic TBOMs

• Flag processes with custom attribute „Business Process Priority“ with value „Prio 1“

• All other non-mission critical business processes and process steps

• Whenever possible make use of dynamic TBOMs

• Generate semi-dynamic TBOMS using SCMON data


Description

• Generation of all Fiori Apps based on their usage from SAP backend system

Details

• Upload Fiori reference data from Fiori Refernce Library (Optional: Enhance with custom fiori data)

• Using Library generation to detect all used Fioris (Odata services) in ST03N of managed System (e.g. S4HANA)

• In Executable Library get the Application Component Hierarchy (ACH) with all Fiori Apps (incl. Fiori ID, Name, Semantic Object, Action)

Benefits

• Simplified Fiori App data creation

• Reflects real system data

Process Management innovations

Automated generation of Fiori Executables

SAP Solution Manager

Managed System (Fiori Odata usage in ST03N)

Lib

rary

Ge

ne

ratio

n

Fio

ri

Re

fere

nce

Data

up

loa

d

Application Component Hierachy &

Fiori Data

SAP Fiori Apps Reference Library

Available today with

SP14

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/home


BPCA – Links

BPCA – Best Practices:

https://support.sap.com/content/dam/support/en_us/library/ssp/alm/sap-solution-

manager/knowledge-transfer/BPCA%20Best%20Practices.pdf

SAP Solution Manager WiKI – Test Suite:

https://wiki.scn.sap.com/wiki/display/SM/SAP+Solution+Manager+WIKI+-+Test+Suite

https://support.sap.com/content/dam/support/en_us/library/ssp/alm/sap-solution-manager/knowledge-transfer/BPCA%20Best%20Practices.pdf

https://wiki.scn.sap.com/wiki/display/SM/SAP+Solution+Manager+WIKI+-+Test+Suite

SAP Solution Manager for SAP S/4HANAUpgrade Projects – Reset Report


Example for a Focused Build Project Setup

Wave 1: Exit

criteria fulfilment

Wave 1

Create Prepare Build TestPrepare

for DeployDeploy Hypercare

Project Phases

Sprint Sprint Sprint

Sprint

Review*

Sprint

Review*

Sprint

Review*

Deploy RunDiscover

& PrepareRealizeExplore

Phases of Release Cycle

= Project Q-Gates

= Decision Point

Upgrade required


▪ Open transports can contain SAP-objects that block the upgrade

▪ Released Transport Requests containing SAP-objects of the old release version can harm the

system if imported in the new release version

▪ Table Definitions can be changed during the upgrade

➢ General recommendation before an upgrade: Release all Transport Requests from the

Development System and transport them through the whole landscape or revert changes which

should not be transported.

Challenges of a System Upgrade


If the SAP Best Practice does not work…

▪ Because you do not have a Preproduction and/or Production System yet available

▪ Because your Project Timeline does not allow a clean-up of the landscape

➢ Solution: New report /SALM/RESET_CD_OF_CYCLE

▪ resets Change Documents and related Transport Requests

▪ Should be executed immediately after system upgrade of Development System

▪ Is valid for Focused Build Release Cycles as well as for Change Request Management Cycles


▪ Checks for appropriate authorizations to perform the reset

▪ Checks whether the specified system was really upgraded

▪ Collects all change documents with transport requests of the specified, upgraded system of a given change

or release cycle

▪ Resets change documents back to in development

▪ Released Transport Requests from the old system version will be repacked into new Transport Requests

from the new system version

▪ Old Transport Requests will be decoupled from the change documents and will be replaced by the new

Transport Requests

▪ Old Transport Requests are deleted and also removed from Import Buffers

▪ Information about executed steps are documented in change document text log and Application Log

What the report does


Selection Screen:

Screenshots

Available Logs:

Use the Q&A panel in the Zoom webinar

to ask your questions.

Questions?

Stay connected. Share your SAP experiences

anytime, anywhere. Join the ASUG conversation

on social media: @ASUG365 #ASUG

Thank you.

SAP Solution Manager for SAP S/4HANA upgrade projects

Documents

Transcript of SAP Solution Manager for SAP S/4HANA upgrade projects