10Steps2S4: Technical Conversion with SUM (DMO)

Work Package 05
Sheldon Edelstein
Bern Herold
David Hess
Boris Rubarth
Martin Roth
March 2019
 Phased approach (1/2)

WP 1 WP 2 WP 3 WP 4 WP 5
Date May 29, 2019 June 10, 2019 June 11, 2019 June 12, 2019 June 13, 2019
10:00 am (EST) 10:00 am (EST) 10:00 am (EST) 10:00 am (EST) 10:00 am (EST)

Objective Kick-off call Prepare Phase Prepare Phase Prepare Phase Technical Conversion
(Logistics) (Finance) with SUM (DMO)

Content / Tasks • Overview
• How to get there
• System environment
• Collaboration
• Resource profile
• Readiness Check • Business Partner • Finance preparation • Start system
• Conflicting Business approach • Consistency checks conversion
Functions • Customer Vendor • Reconciliation • Complete uptime
• Conflicting Add-ons Integration (CVI) • Period-end closing phases
• Maintenance Planner • MRP Areas activities • Execute full
• ATC - Custom Code • MATNR Extension • Document posting downtime
• Simplification Item data • Post-activities
Checks

Duration roll-out session 1 hour 1,5 hours 2 hours 1,5 hours 2 hours

Partner additional effort 1 hour (team preparation) 2 – 4 hours 4 – 6 hours 2 – 4 hours 2 days (duration)

Partner Resources Architects Basis Consultant Application Consultant Application Consultant Basis Consultant
required Team Leader Developer (logistic area) (finance area) Developer (SPDD/SPAU)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 2

Customer
 Phased approach (2/2)

WP 6 WP 7 WP 8 WP 9 WP 10
Date June 17, 2019 June 18, 2019 June 19, 2019 June 20, 2019 June 21, 2019
10:00 am (EST) 10:00 am (EST) 10:00 am (EST) 10:00 am (EST) 10:00 am (EST)

Objective Finance Conversion Post Conversion Activities SAP FIORI activation and Additional post conversion Review & Feedback
configuration topics

Content / Tasks • Finance migration • Output Management • Configuration of • Fiori specialties • Project Experience
• Customizing/Data • PP/DS embedded Front-end • Secure communication • Feedback
Model impact • Convert Architecture server • Expose system to the • Q&A
changes • Activation and internet
• Credit configuration of FIORI • Custom code fixes
Management Launchpad
• Activation and
configuration of FIORI
applications
Duration roll-out 2 hours 1,5 hours 1,5 hours 1,5 hours 2 hours
session

Partner additional effort 4 – 6 hours 2 – 4 hours 2 – 4 hours 2 – 4 hours 1 hour pre & post session

Partner Resources Application Consultant Application Consultant Basis Consultant Basis Consultant All Team
required (Finance area) Basis Consultant Application Consultant Developer
(testing)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 3

Customer
Content:

• Review of previous work-package

• Technical conversion with SUM (DMO)

• Introduction to SUM including DMO

• Minimize the downtime
• Additional topics
• The activity guide for WP05

• Closure and Call to Action!

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 4

Customer
Review of previous work-package
Review of previous work-package

Check the consistency of your financial data

Perform period-end closing

Document your posting data

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 6

Customer
Application Specific Preparation
Preparing Application Specific Tasks

Uptime

Downtime

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 7

Customer
Technical Conversion with SUM (DMO)
➢ Introduction to SUM including DMO
➢ Minimize the downtime
➢ Additional topics
➢ The activity guide for WP05
 SAP S/4HANA
System conversion: technical Conversion by Software Update Manager (SUM)

▪ Technical Conversion executed by Software Update Manager (SUM) PAS Host

SUM

▪ Conversion tasks for SUM:

– Software update
Provide new applications and new tables
Source = Target DB Host
– Data conversion
Conversion of table content to new data model
PAS Host
– Database migration
Migrate to SAP HANA database (if required) SUM

Any
DB

Source DB Host Target DB Host

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 9

Customer
 Planung Vorbereitung Realisierung
SAP S/4HANA System Conversion System
requirements
Maintenance
planner
SI
Checks
Custom
Code prep
SUM
Nach-
arbeit
Technical Conversion with SUM 2.0

stack.xml
Prerequisites:

➢ Maintenance Planner: provides stack.xml and software archives

➢ SI Checks: are executed by SUM as well: all issued have to be solved beforehand

Optional Activities (per system type)

➢ Readiness Check: is optional, but always recommended!

➢ Custom Code Check: may be ignored for an early conversion of a sandbox system

➢ SUM Prerequisite Check: Check of OS/DB and SPAM requirements

See SUM conversion Guide: https://support.sap.com/sltoolset -> Maintenance Area

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 11

Customer
SUM Prerequisite Check provided with SUM 2.0

Allows quick and non-invasive check

for requirements, e.g.:

• Source OS version

• Source database version

• SPAM patch level

Uses different URL

(chktool instead of sumabap)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 12

Customer
Checks for the SAP ECC Source System

SAP ECC

Simplification
Application
Item Checks
Business Data
Level Z Objects

Add-Ons
(SAP, Partner)

SAP ERP 6.0

Maintenance
EHP xx, ABAP Planner
Business Functions
Unicode

OS (AppServer)
SUM prerequisite
Database check
Level AnyDB or
SAP HANA 2.0
OS (Database)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 13

Customer
Technical Conversion with SUM (DMO)
➢ Introduction to SUM including DMO
➢ Minimize the downtime
➢ Additional topics
➢ The activity guide for WP05
Downtime-optimization approaches

▪ Standard approach
using Software Update Manager (SUM)

Downtime
with several optimizations
▪ Downtime-optimized conversion approach
uses SUM as well, and reduces downtime
by moving data conversion and migration
partly to uptime (currently only piloted)
▪ Near-Zero Downtime Technology approach
allows further reduction of downtime
by executing the conversion on a clone; Decision about approach

Effort
it is a consulting service project (aka NZDT) depends on several factors
See SAP Note 693168 and should be taken after a
migration planning workshop.
(Service component of SAP Value
Assurance for SAP S/4HANA)

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 16

Customer
Downtime optimization approaches for maintenance activities

Approach Abbreviation Scenario Availability* SAP Note

near-Zero Downtime Unrestricted
nZDM (ABAP) Update/Upgrade 1678565
Maintenance (ABAP) ** available

Zero Downtime Option ZDO Update/Upgrade Pilot 2163060

Migration to
downtime-optimized
downtime-optimized DMO SAP HANA Pilot 2442926
Database Migration Option
database

downtime-optimized Conversion to
Pilot 2293733
Conversion SAP S/4HANA

near-Zero Downtime Unrestricted

nZDM Java Update/Upgrade 2422909
Maintenance (JAVA) available

Near Zero Downtime

NZDT several Service-based 693168
Technology
** This is different to nZDM for SAP HANA database * This is the current state of planning and may be changed by SAP at any time.
© 2019 SAP SE or an SAP affiliate company. All rights reserved. 17
Customer
Main conversion steps with focus on technical downtime

Business Downtime

Technical Downtime

SUM Uptime Ramp FI & ML Business Ramp

Technical SUM Downtime Post Activities
Processing Down Data Conversion Validation Up
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

Data Conversion
Software Update Convert table content to new data model
Add / update components Partially triggered by SUM, partially after SUM

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 18

Customer
Properties of the source system that impact the technical downtime

System SAP Business Suite SAP S/4HANA

performance (Migration) Data Conversion

Quality of data Any

DB

Database size
Source DB SAP HANA

Portion of tables
affected by data conversion
FI conversion:
inconsistencies coming up in FI conversion have to be corrected,
this happens in downtime of test conversion
(not relevant for PRD conversion)

Second run is always faster → decide on approach only after second run
© 2019 SAP SE or an SAP affiliate company. All rights reserved. 19
Customer
Downtime optimization for standard approach

▪ DMO optimization: see blog in SAP Community: https://blogs.sap.com/?p=135725

▪ SAP Note 2351294 – SAP S/4HANA System Conversion / Upgrade: Measures to reduce technical downtime
▪ SAP Note 1616401 – Parallelism in the Upgrades, EhPs and Support Packages implementations

SUM Uptime Ramp Post FI & ML Business Ramp

Technical SUM Downtime
Processing Down Activities Data Conversion Validation Up

Migration Update Conversion

Number of
background processes
DMO
optimization

Database size:
consider archiving
© 2019 SAP SE or an SAP affiliate company. All rights reserved. 20
Customer
Downtime-optimized conversion approach

▪ Table conversion moved to uptime processing

▪ Field conversion moved to uptime processing (KONV and VBFA tables)
▪ Uptime migration for selected big application tables (without 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 SAP Note 2293733 for Prerequisites and Restrictions
© 2019 SAP SE or an SAP affiliate company. All rights reserved. 21
Customer
Project flow and Customizing Freeze
Downtime-optimized Conversion Approach

Create FIN Customizing

Put into customizing request
Provide customizing
to SUM

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

Customizing Freeze

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 22

Customer
Data Migration Activities according to IMG - after SUM run

FI data migration included in downtime-optimized Conversion

GL Migration: manual activity

House Bank Migration: manual activity
Credit Management Migration: manual activity

Accrual Engine Data Migration: manual activity

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 23

Customer
Technical Conversion with SUM (DMO)
➢ Introduction to SUM including DMO
➢ Minimize the downtime
➢ Additional topics
➢ The activity guide for WP05
SUM: Procedure complete -> check LONGPOST.LOG!

In the final part of the SUM run,

the tool will not stop in case of
errors during data conversion,
so check the messages shown -
as described in the guide

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 25

Customer
Platform coverage reduced for Application Server Host

SAP S/4HANA 1809

From SAP ERP (conversion) or ABAP Platform 1809 –

Application Server ABAP
SAP_BASIS 7.53
From SAP S/4HANA (upgrade)
SAP Kernel 7.73

SAP HANA 2.0 SPS 03 rev 33

• Linux on Power Big Endian
• HP-UX on IA64 • Windows
SUM 2.0
• Solaris on SPARC and on x86 • Linux on x86
• IBM I SP 03
• AIX
• IBM z/OS • Linux on Power Little Endian
• Linux on IBM Z

SAP Note 2620910 - SAP S/4HANA … and SAP BW/4HANA 1.0: Recommended Application Server Platforms
© 2019 SAP SE or an SAP affiliate company. All rights reserved. 26
Customer
ASCS Instance Move (1/4)
Overview

▪ ASCS move is an option in SUM 2.0 SP 03 (and higher)

▪ It allows to move the ASCS instance to a different host
▪ This is relevant esp. for SUM scenarios targeting ABAP Platform 1809 (reduced platform covering):
– For upgrades and conversions targeting 1809
– Allows ASCS move to a host with OS supported by 1809

▪ Sequence:
– ASCS runs on host with OS which is not supported by 1809
– SUM to be started on AAS with OS supported by 1809
– SUM will show dialog with option “ASCS move”
– If chosen, SUM will set up ASCS on AAS (previous instance no longer started)

▪ See blog
▪ https://blogs.sap.com/2019/04/12/ascs-instance-move-use-sum-to-switch-your-ascs/

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 27

Customer
Obsolete Data Handling – after System Conversion

▪ SAP S/4HANA with new data model - old tables still existing,
Old data not deleted during system conversion (e.g. to allow error diagnostic)

▪ FIN & MM-IM area have documented how to handle obsolete data manually

▪ SAP S/4HANA 1809 introduces a framework to delete obsolete (customer) application data,
based on application specific rules (content)
Initial shipment of framework with reduced scope, availability on request

▪ Deletion rules delivered by SAP run in PRD without business downtime, if you:
– Successful validated the system conversion
– Tested the deletion rules successfully in an appropriate test system (copy of PRD)
– Created a backup of database

▪ Deletion depends on data model change: rows or columns or entire tables

2661837 - How to enable and use the obsolete data handling tool in SAP S/4HANA
2190137 – sFIN: Reduce memory footprint of obsolete tables
© 2019 SAP SE or an SAP affiliate company. All rights reserved. 28
Customer
DMO with System Move: the possible path to Cloud

▪ DMO not supported for data center migration due to latency issues
(source & target database in separate data center)
DMO with System Move
▪ “DMO with System Move”:
use case to move complete SAP system
– Allows to switch PAS host
SUM
– Allows to migrate across data centers

▪ Requirements:
Migrate Update*
– Target database and target PAS are set up prior to start
Any
– Target database type is SAP HANA DB
HANA

▪ Sequence:
– Start SUM in source, export happens
– Copy and start SUM on target, import happens

▪ Can be combined with “SUM on AAS”

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 29
Customer
 Maintenance Strategy: attached to
Project planning aspects respective SAP Note for SL Toolset

Familiarize Create transports for

custom code adaption
Iterate
Consider dual maintenance
Refine project
plan afterwards
SBX
DEV Business Function Testing
of new/adapted processes

QAS

Desire: SUM SP-Version shall not be switched in critical project phase

4 to 8 months are offered => put relevant systems into this time phase Consider dress rehearsal
PRD

SUM 2.0 SP 05 in maintenance SUM 2.0 SP 05 patch on request

SUM 2.0 SP 04 in maint. SUM 2.0 SP 04 patch on request SUM 2.0 SP 04 out of maintenance

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 30

4 months 4 months Customer
SAP S/4HANA System Conversion or Upgrade
SAP HANA 1.0 to SAP HANA 2.0

SAP S/4HANA 1809

SAP ERP 6.0 SAP ERP 6.0
Step 2: Conversion
SAP HANA 2.0
SAP HANA 1.0 SAP HANA 2.0

Step 1: Database Upgrade

hours

SAP S/4HANA SAP S/4HANA

version X Version X

SAP HANA 1.0 SAP HANA 2.0 Step 2: SAP

S/4HANA Upgrade
Step 1: Database Upgrade

SAP Note 2625407 – SAP S/4HANA 1809: Release Information Note

SAP Note 2655761 - SAP S/4HANA - restrictions and recommendations regarding specific revisions of SAP HANA database for use in SAP S/4HANA
SAP Note 2339267 – SAP HANA client version versus SAP HANA server version
© 2019 SAP SE or an SAP affiliate company. All rights reserved. 31
Customer
Technical Conversion with SUM (DMO)
➢ Introduction to SUM including DMO
➢ The activity guide for WP05
SUM / DMO Introduction

❑ After having read this document, you will be able to

I. Learn how the document is organized
II. Perform the related activities for work package 5
III. Understand how the same document can help you on further
projects

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 33

Customer
Closure and Call to action
The system landscape for 10Steps2S4

The source system The target database

SAP ECC 6.0 EhP 6 HANA 2.0

SID: K<XX> (e.g. K01) Application Server: after execution of

WP05 the application server will still be
running on Windows (during WP07 this will
Main usage: your Business System to be changed).
be converted to S/4HANA

Database: your target HANA database

Activities:
• Technical conversion
Activities:
• Perform the full technical conversion to to
to S/4HANA including
• Uptime phases
• Downtime phases

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 35

Customer
Call to action

• Review this presentation (published in JAM group)

• Execute the activity document and complete the technical conversion to

S/4HANA using SUM (DMO)

• Collaborate using JAM in case of issues or doubts

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 36

Customer
Q&A

Ask your questions

via Chat

via Microphone:

Adobe Connect Menu click on

1. Connect My Audio
2. Select Microphone

© 2019 SAP SE or an SAP affiliate company. All rights reserved. 37

Customer
Thank you.
Contact information:
SAP 10Steps2S4 Team

JAM JAM: 10Steps2S4 Americas – June 2019

Mail: sap10steps2s4@sap.com