Downtime-optimized Conversion

to SAP S/4HANA

October 2022

Public
Knowledge Transfer for SAP User Groups - SAP CLM Webcast Series (extract)
https://webinars.sap.com/sap-user-groups-k4u/en/upcoming

Extract of session list from Cloud & Lifecycle Management (CLM) in 2022 – dates subject to change
Public 2
 “Downtime-Optimized Conversion” in a nutshell

Downtime-Optimized Conversion reduces the technical downtime of the system conversion to SAP S/4HANA

Scenario

▪ System conversion from SAP ERP 6.0 to SAP S/4HANA

Benefit

▪ Relevant downtime reduction

Approach

▪ Move data conversion activities from downtime partially to uptime (also migration, if required)

Availability

▪ Approach can be used by educated consultants (training ADM329 and assessment passed)

Details and more information

▪ SAP Support Portal page on downtime-optimized conversion:
https://support.sap.com/en/tools/software-logistics-tools/software-update-manager/downtime-optimized-conversion-approach.html

Public 3
Downtime-optimized Conversion

Overview on downtime-optimized Conversion

Project Considerations

Architectural Process Steps

Public 4
SAP S/4HANA system conversion – “Realization” for standard approach
High level overview of the downtime (focus on technical downtime)
SAP ECC system SAP S/4HANA

Business Downtime

Technical Downtime

SUM Uptime Ramp Post FI & ML Business Ramp

Down
Technical SUM Downtime Up
Processing Activities Data Conversion Validation
SHD
Migration Update Conversion

FIN data conversion:

IMG activities
1) FIN Customizing
Database Migration 2) FIN Data migration
(if source is not yet SAP HANA) 3) Post activities

Software Update Data Conversion

Add / update components Convert table content to new data model
Partially triggered by SUM, partially after SUM
Public 5
Not true-to-scale: SUM Uptime processing is much longer than Downtime
 Main 3 Approaches for System Conversion to SAP S/4HANA

 Standard approach
using Software update Manager (SUM)

Downtime
with several optimizations

 Downtime-optimized Conversion approach Decision about approach

uses SUM as well, and reduces downtime depends on several factors
by moving data conversion partly to uptime and should be taken after a
migration planning workshop
 Near-Zero Downtime Technology approach together with SAP.

Effort
allows further reduction of downtime
based on a consulting service project (aka NZDT)

Public 6
Downtime-optimized conversion approach

▪ Table conversion moved to uptime processing

▪ Field conversion moved to uptime processing (KONV and VBFA tables)
▪ Uptime migration for selected large application tables (which are not part of the data conversion)

SUM Uptime Ramp Post FI & ML Business Ramp

Technical SUM Downtime
Processing Down Activities Data Conversion Validation Up

Migration Update Conversion

Conversion partially moved to uptime for

− FIN and Material Ledger (MM-ML)
& Inventory Management (MM-IM)
− KONV and VBFA tables Migration part is only relevant for source systems on non-HANA database

Public 7
 Overview on conversion approaches, depending on source database type
Standard conversion
SUM Uptime processing Ramp SUM technical downtime Post FIN and ML Business Ramp
down activities data conversion validation up
Migration Update Conversion

Downtime-optimized DMO aka uptime Migration (source on non-HANA)

Migration ∆
Ramp Post FIN and ML Business Ramp

∆ Migration
SUM Uptime processing SUM Technical downtime
down activities data conversion validation up
Update Conversion

nZDM (source on HANA) update ∆

SUM Uptime processing Ramp SUM tec. downtime Post FIN and ML Business Ramp
down activities data conversion validation up
Update Conversion
∆

Downtime-optimized conversion
Migration Conversion ∆
Ramp Post Business Ramp
∆ Conversion

SUM Uptime processing SUM tec.

∆ Migration

down downtime activities validation up

Update

Public 8
SUM dialog offering strategies
Possible conversion approaches

Source on non-SAP HANA DB Source on SAP HANA DB

• Near-Zero Downtime Maintenance (nZDM)

Move table structure adaptations and import of new table content partly to uptime processing for a system update/upgrade.
• Uptime Migration (Downtime-optimized DMO)
Migrate selected large application tables partly in uptime.
• Downtime-optimized Conversion
Move migration and data conversion partly to uptime processing for a system conversion.

Public 9
 Downtime-Optimized Conversion: Execute long running XCLAs in uptime
Possible for both source on SAP HANA or on non-HANA

SUM on SBX
Conversion run On target, you manually start the tool
SAP SAP Selection of Uptime XCLAs as part of the
XCLA S/4HANA
ERP SUM Toolbox, provide XCLA meta data
6.0 2020* and select appropriate XCLAs

File XCLA_MTDATA.XML Write

Read
contains metadata and execution runtime
File XCLA_UPTIME_MTDATA.XML
of all executed XCLAs
contains selected XCLAs

SAP Note 2778832

explains approach, prerequisites,
and tool usage for XCLA selection SUM on SBX
Downtime-optimized Conversion run
SAP Note 3053586
SAP SAP
contains corrections XCLA
XCLA S/4HANA
for target SAP S/4HANA 2020 ERP
6.0 2020*
SAP Note 3092738
on SUM Toolbox implementation
Public
*: or higher 10
Downtime-optimized Conversion

Overview on downtime-optimized Conversion

Project Considerations

Architectural Process Steps

Public 11
Project aspects for downtime-optimized Conversion

• Approach is used for PRD, but not for all other systems (e.g. not for DEV)

• A standard conversion run is required prior to PRD run to set up FI customizing (see next slide)

• Triggers are set on specific tables (tables affected by new data model)

• Replication in uptime phase creates load on PRD system

• Mass changes/activities have to be avoided during replication (e.g. archiving to be avoided)

• Freeze trigger prevent customizing changes: tables become read-only

• Change rate during replication has to be estimated, e.g. based on ST10 data

• Load-verification run: potential approach to run test on PRD until downtime dialog
to see freeze trigger impact and replication rate

Public 12
Project flow and Customizing Freeze
Downtime-optimized Conversion Approach

Create FIN Customizing

Put into customizing request
Provide customizing
to SUM

Hard Freeze

Standard Conversion run on SBX Downtime-optimized Conversion run on PRD

Soft Freeze (for customizing)

Public 13
Customer buffer system dependencies details
1) Fresh copy of PRD
2) Standard on SBX
SBX SBX 3) Dress rehearsal
S/4HANA 4) PRD conversion
S/4HANA
1

4
PRD
2 S/4HANA
SBX
3 Dress
S/4HANA Hard Freeze
rehearsal
S/4HANA Standard Conversion Run
S/4HANA
Downtime-optimized
S/4HANA Conversion Run
Final Run – Customizing freeze (for FIN) on PRD
FIN customizing

Public 14
Downtime-optimized Conversion

Overview on downtime-optimized Conversion

Project Considerations

Architectural Process Steps

Public 15
 downtime-optimized Conversion (source non-HANA)
Migrate and Convert relevant Tables already in Uptime

Delta Delta
5 migration conversion

Revert to snapshot

Target Release Shadow System

Initial Conversion Final
migration
∆ Migrate
Post Processing
SAP HANA DB SHD REP & CUST Migration
of relevant
relevant tables ∆ Other
Tables
of relevant
Tables TMP System tables
2 3 4 6 7 8 9 10 11 t
1
Start Uptime System Downtime
Release
Short term lock
Source DB for Asset Accounting
Public 16
You start the Software Update Manager (SUM)
Step 1 for downtime-optimized Conversion

PAS Host
PAS
Source
PRD Instance
Kernel
Source on non-HANA

SUM SUM is started

TGT Kernel

PRD REP

Application Data Legende

Target Source
Release Release
Public Source DB Host SAP HANA DB Host 17
Shadow Repository is created
Step 2 for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM
Source on non-HANA

Uptime:
SHD Instance
Shadow system is created
on the target database
TGT Kernel

PRD REP SHD REP

Application Data

Public Source DB Host SAP HANA DB Host 18

Short Downtime
Step 3 for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM
Source on non-HANA

Short term lock

SHD Instance
for Asset Accounting
TGT Kernel

PRD REP SHD REP

Application Data

Public Source DB Host SAP HANA DB Host 19

Initial transfer of relevant tables
Step 4 for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel
SUM
R3load R3load
Source on non-HANA

Uptime:
TMP Instance Initial transfer of
relevant tables
TGT Kernel

PRD REP SHD REP

Application Data Application Data

Public Source DB Host SAP HANA DB Host 20

Revert: set data to consistent state
Step 5 for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM R3load
Source on non-HANA

Uptime:
TMP Instance
Revert: set transferred
data to consistent state
ABAP

TGT Kernel

PRD REP SHD REP

Application Data Application Data

Public Source DB Host SAP HANA DB Host 21

Conversion of transferred relevant tables
Step 6 for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM
Source on non-HANA

Uptime:
TMP Instance Conversion of
relevant tables
ABAP

TGT Kernel

PRD REP SHD REP

Application Data Application Data

Public Source DB Host SAP HANA DB Host 22

Delta Migration of relevant Tables
Step 7 for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel
SUM
R3load R3load
Source on non-HANA

Uptime:
TMP Instance Delta replication of
relevant tables
ABAP

TGT Kernel

PRD REP SHD REP

Application Data Application Data

* Secondary DB connection 23
Public Source DB Host SAP HANA DB Host
Remaining Delta Transfer of relevant Tables
Step 8 for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel
SUM
R3load R3load Downtime:
Source on non-HANA

TMP Instance
Remaining Delta replication
of relevant tables
ABAP

TGT Kernel

PRD REP SHD REP

Application Data Application Data

Public Source DB Host SAP HANA DB Host 24

Conversion of delta
Step 9 for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM
Downtime:
Source on non-HANA

TMP Instance
Conversion of
delta (relevant tables)
ABAP

TGT Kernel

PRD REP SHD REP

Application Data Application Data

Public Source DB Host SAP HANA DB Host 25

Migration of remaining application tables
Step 10 for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel
SUM
R3load R3load Downtime:
Source on non-HANA

TMP Instance
Other application tables
are migrated
TGT Kernel (tables which do not need a
data conversion)

PRD REP SHD REP

Application Data Application Data

Public Source DB Host SAP HANA DB Host 26

Kernel switch for PRD instance
Step 11 for downtime-optimized Conversion

PAS Host
PAS
TGT
Kernel

SUM Downtime:
Source on non-HANA

Target kernel
for PRD instance

PRD REP SHD REP

Application Data Application Data

Public Source DB Host SAP HANA DB Host 27

Update of application tables to new release
Step 12 for downtime-optimized Conversion

PAS Host
PAS
TGT
Kernel

SUM Downtime:
Source on non-HANA

Remaining Application
tables are updated
Procedure finished

PRD REP PRD REP

Application Data Application Data

Public Source DB Host SAP HANA DB Host 28

 downtime-optimized Conversion (source SAP HANA)
Convert relevant Tables already in Uptime

E
Revert to snapshot

Target Release Shadow System D Conversion ∆ Final ∆ Con-

∆ Replication version Post Processing
SHD REP & CUST relevant tables
Re-
B F play

C
copy2shd G H I J t
A
Start Uptime System Downtime
Release
Short term lock
for Asset Accounting
Public 29
You start the Software Update Manager (SUM)
Step A for downtime-optimized Conversion

PAS Host
PAS
Source
PRD Instance
Kernel

SUM SUM is started

TGT Kernel

PRD REP

Application Data Legende

Source already on
Target Source
SAP HANA Release Release
Public
SAP HANA DB Host 30
Shadow Repository is created
Step B for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM Uptime:
Shadow system
SHD Instance
is created
ABAP

TGT Kernel

PRD REP SHD REP

Application Data

Public
SAP HANA DB Host 31
Short Downtime
Step C for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM Short lock

for Asset Accounting
SHD Instance

ABAP

TGT Kernel

PRD REP SHD REP

Application Data

Public
SAP HANA DB Host 32
Copy to shadow
Step D for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM Uptime:
Copy to shadow
SHD Instance

ABAP

TGT Kernel

PRD REP SHD REP

Application Application
Data Data

Public
SAP HANA DB Host 33
Revert: set data to consistent state
Step E for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM
R3load Uptime:
Revert: set transferred
SHD Instance
data to consistent state
ABAP

TGT Kernel

PRD REP SHD REP

Application Application
Data Data

Public
SAP HANA DB Host 34
Conversion of transferred tables
Step F for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM
Uptime:
Conversion of
SHD Instance
relevant tables
ABAP

TGT Kernel

PRD REP SHD REP

Application Application
Data Data

Public
SAP HANA DB Host 35
Uptime replication of delta
Step G for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM Uptime:
Delta replay
SHD Instance

ABAP

TGT Kernel

PRD REP SHD REP

Application Application
Data Data

Public
SAP HANA DB Host 36
Downtime replication of delta
Step H for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM Downtime:
Final replay
SHD Instance

ABAP

TGT Kernel

PRD REP SHD REP

Application Application
Data Data

Public
SAP HANA DB Host 37
Conversion of delta
Step I for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM
Downtime:
Conversion of delta
SHD Instance

ABAP

TGT Kernel

PRD REP SHD REP

Application Application
Data Data

Public
SAP HANA DB Host 38
Update of application tables to new release
Step J for downtime-optimized Conversion

PAS Host
PAS
Source
Kernel

SUM Downtime:
Remaining Application tables
are updated
Procedure finished

Target REP

Application
Data

Public
SAP HANA DB Host 39
Thank you.
Contact information:

Boris Rubarth
boris.rubarth@sap.com

© 2022 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.