SAP S/4HANA 1709 OP:

System Conversion – Phases and Steps

Legal Disclaimer

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.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 2
Introduction

This document is an approach document for customers who are trying to carry out the system conversion
of their Business Suite in their landscape. This document provides the sequence of steps that are defined
logically and are technically important to follow during the system conversion. The definition of the
sequence, the phases and steps in each of the phase are highlighted in the document. This document
provides a overview of possible transition paths for a customer to convert ERP 6.0 system to S/4HANA
1709 including information regarding HANA 1.0 to HANA 2.0 upgrade. Also this document will provide
information for a source system with non-HANA DB to be converted to target S/4HANA 1709.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 3
Transition to SAP S/4HANA
Three Different approaches to move to SAP S/4HANA

SAP Community Blog: How to find my path to SAP S/4HANA

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 4
SAP System Conversion
Overview Technical Process Steps

Preparation phase Realization phase

Maintenance Software Update Application specific

Application specific
System requirements Pre checks Custom
Custom code
code preparation
preparation
planner Manager (SUM) follow-up activities
follow-up activities

Unicode conversion Database migration

Software update
Cross-application & application specific preparation activities
Data conversion

Simplification List

**)
incl. migration of FI
Customizing and Data

*) incl. preparation of
financial data

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 5
SAP System Conversion
Overview of Technical Process Steps

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 6
 SAP S/4HANA Family and Conversion Paths

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 7
SAP S/4HANA
System Conversion – Transition Paths Overview (1/2)

Conversion requirements incl. min./max. SP level on source system:

2482453 - SAP S/4HANA 1709: Release Information Note
2346431 - SAP S/4HANA 1610: Release Information Note
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 8
SAP S/4HANA
System Conversion – Transition Paths Overview (1/2)

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 9
 SAP S/4HANA System Conversion or Upgrade
SAP HANA 1 to SAP HANA 2

SAP Note 2524661 – SAP S/4HANA 1709 - SAP HANA Database Requirements
Note: S/4HANA 1709 requires min. HANA2.0 SPS01 Rev.12
SAP Note 2339267 – HANA client version versus HANA server version

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 10
SAP S/4HANA Conversion or Upgrade in Two Steps
With Upgrade from SAP HANA 1 to SAP HANA 2

Conversion

SAP ERP on SAP ERP on SAP S/4HANA

SAP HANA 1 SAP HANA 2 on SAP HANA 2

Upgrade

SAP S/4HANA v.X SAP S/4HANA v.X SAP S/4HANA v.Y

on SAP HANA 1 on SAP HANA 2 on SAP HANA 2
Step 1: Database Upgrade Step 2: Application Upgrade
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 11
Project planning aspects
Further important aspects and considerations
Perform sizing of SAP HANA
– See http://service.sap.com/sizing
 Sizing guidelines  SAP In-Memory Computing
▫ See SAP Note 1793345 (Sizing for SAP Suite on HANA/SAP Simple Finance)
– ABAP sizing reports for migration to SAP HANA:
▫ SAP Business Suite as well as SAP Simple Finance : SAP Note 1872170

Define overall target system landscape

– Example: put development and QA system on one appliance?
– Scale-up (scale vertically by increasing size of hardware) vs.
scale-out (scale horizontally by adding nodes)

Trigger SAP HANA hardware provisioning in time

– Start hardware procurement early – lead times can be 4-6 weeks

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 12
Size is important
Minimize & optimize data volume of SAP system landscapes & control data growth

For System Conversion:

Focus on "relevant" tables
Trim down source Trim target operation
• Archive data • Consider data aging
• Check data quality • Monitor data growth
Any
DB

Use SAP DVM: Data Volume Management Work Center in SAP Solution Manager
Archived Data are still accessible after conversion; data conversion happens during access to archive

i ABAP sizing reports for move to SAP HANA

SAP Business Warehouse: SAP Note 1736976

i Memory sizing report for SAP Business Suite

and SAP S/4HANA: SAP Note 1872170

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 13
 SAP System Conversion
Sizing

Existing customers
(System Conversion)
sizing
– Sizing report for SAP
HANA Note 1872170
▫ Available for SoH, S/4
HANA Simple Finance, and
S/4HANA OP
▫ ABAP report
/SDF/HDB_SIZING
▫ Once on S/4HANA OP,
used to verify memory
sizing.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 14
Version Interoperability for SAP S/4HANA
Central NetWeaver Systems 7.31 Version as Basis and Central Fiori Front-End Server
SAP Note: 2251604 for version interoperability Front-end server deployment

Fiori for S/4HANA

Netweaver 7.50/7.51 on
SAP S/4HANA 1709
HANA/MaxDB/ASE
SAP HANA 2.0

Enterprise Search
Enterprise Search
Models
Models
S/4HANA 1511/1610/1709
SAP Business Suite ABAP
SAP Business Suite ABAP
On-Premise Backend

• For existing front end server customers -

S/4HANA 1511/1610/1709 requires SAP
NetWeaver 7.50/7.51/7.52 as front-end
server
• Only supported databases are SAP HANA,
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL
SAP MaxDB, or SAP ASE 15
SAP System Conversion
Overview of Technical Process Steps

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 16
 SAP Readiness Check for SAP S/4HANA
Available for all customers
• Customers can initiate their SAP ERP system
analysis themselves, getting an overview on the
most important aspects and potential requirements
of an SAP S/4HANA system conversion (e.g.
Simplifications, Custom Code, Business Functions,
Add-ons and Transactions).

• A new cloud solution based on SAP Solution

Manager is available for all customers included in
maintenance as of May 29th 2017.

• A Minimum source release is SAP ERP 6.0 EHP 0,

any database.

• Supports all SAP S/4HANA releases as target.

• Using the SAP Readiness Check is optional but

highly recommended.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 17
SAP Readiness Check for SAP S/4HANA
Approach

1. Prepare source system

– Minimum release: SAP ERP 6.x EhP0 on any database
– Help portal: https://help.sap.com/viewer/p/SAP_READINESS_CHECK
– SAP Readiness Check tool preparation note: SAP Note 2290622

2. Execute program SAP Readiness Check

– Via your local SAP Solution Manager system (recommended)
– Via our direct cloud upload

3. Explore results to start Conversion project

– Recommendations dashboard per system, sent via email as url link
– Engage SAP Digital Business Services or your preferred implementation partner

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 18
SAP Readiness Check for SAP S/4HANA
Setup

Solution Manager Requirements

 Solution Manager 7.1 SPS12 or higher
 Solution Manager 7.2 SPS3 or higher
 For No Solution Manager or Other Scenarios --> follow SAP Note 2310438

Preparation in Managed System (SAP Note 2290622)

For Custom Code Analysis
 Create a back RFC destination to Solution Manager system
 Insert Customizing (Appl. = SMRC_BCK; RFC connection = <RFC Dest.> in view BCOS_CUST (SM30)
 Implement Notes 2185390 and 2310438
For All other Analysis
 Create a back RFC destination to Solution Manager system
 Insert Customizing (Appl. = SMRC_BCK; RFC connection = <RFC Dest.> in view BCOS_CUST (SM30)
 Implement Notes 2462288, 2399707, 2443236, 2310438
Preparation in Solution Manager (SAP Note 2290622)
 Create TMW RFC destinations to the managed systems (SAP Note 2257213)
 Assign Authorizations to users to run report AGSRC_START_ANALYSIS
 Make sure SAP-OSS connection is operational

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 19
SAP Readiness Check for SAP S/4HANA

AddOn’s & Business Functions

• SAP AddOn’s and Business Functions as well
as 3rd party AddOn’s have to be checked for
Custom Code & Custom Dev their compatibility with SAP S/4HANA S/4HANA Sizing
• Custom Code must be analyzed with respect • SAP software is listed and rated • To prepare for SAP S/4HANA, a system
to SAP S/4HANA compliance, based on the sizing is the baseline for further discussions
• 3rd party software is listed only
SAP simplification database regarding the future target size
• SAP Readiness Check provides BOM of • SAP Readiness Check summarizes the
affected objects as well as SAP Custom technical sizing result so that SAP
Development Projects (CDP‘s) INTERNALs can further engage internally,
• An in-depth custom code management with SAP or with partners to discuss the
activities to follow during project execution future target system size

Simplification items
• Simplification Items represent application or
architecture changes in comparison to ERP
Recommended Fiori Apps
• About 470 Simplification Items exist for
• Fiori apps recommended based on the
S/4HANA 1610
transaction usage history in the evaluated
• They are grouped by business priority (e.g. system
Core Finance) and industry, respectively
Transactions
• SAP GUI transactions replaced or
deprecated in SAP S/4HANA, such as
Classic MM-PUR GUI transactions
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 20
SAP Readiness Check for SAP S/4HANA
Two Examples of Detailed Output – Accessible via the Dashboard

1. How is my custom code impacted when I want to convert my SAP ERP 6.0 system to SAP S/4HANA?

2. Which SAP S/4HANA simplifications impact me when I want to convert my SAP ERP 6.0 system to SAP S/4HANA?

SAP Help Portal: SAP Readiness Check and SAP note 2290622
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 21
SAP System Conversion
Overview of Technical Process Steps

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 22
 SAP System Conversion
Simplification List

• List contains Simplification Items describing the

change with SAP S/4HANA on solution and on
transaction level

• Activities on Application Level required before,

during, and after conversion

• Available as PDF & XLS, and as catalog Not all

items are relevant for all customers. See
help.sap.com/s4hana, SI catalog:
https://launchpad.support.sap.com/#/sic

• Supports all SAP S/4HANA releases as target.

• List is foundation for other tools: Maintenance

Planner, Pre-Checks, Custom Code Migration
Worklist, SAP Readiness Check

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 23
Transition DB  Simplification Item Catalog

With SAP S/4HANA 1709 the webbased UI for searching and displaying Simplification Items that has so far only been
available SAP internally (Transition DB) will also become externally.

 https://launchpad.support.sap.com/#/sic/

Externally it will be known unter the name

„Simplification Item Catalog“ and allow
customers to directly search and browse
the Simplification Items.

Also other products (e.g. BW/4HANA) are

going to join the Simplification Item Catalog.

In parallel the Simplification List for SAP S/4HANA 1709 will still be available as PDF document.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 24

SAP System Conversion
Simplification List and Pre-Checks

Preparation phase Realization phase

Maintenance Software Update Application specific

Application specific
System requirements Pre-Checks Custom
Custom code
code preparation
preparation
planner Manager (SUM) follow-up activities
follow-up activities

 Pre-checks are shipped as SAP Notes to customers that plan to convert to SAP S/4HANA. Pre-Checks

 Pre-checks are executed on the (SAP Business Suite) start system (preparation phase)
to determine relevant Simplification Items.
 Pre-Checks are executed again as step in the Software Update Manager (SUM). In case
dedicated Simplification Items require mandatory preparation steps the conversion procedure can stop to ensure a consistent system
conversion.

Customer-specific Simplification List

Pre-Check S-Item Title Area Relevancy Business Impact Note
The pre-check framework will be COST ELEMENTS FIN - Controlling 2270419
delivered via one SAP Note and all Pre-Check Currencies in Universal Journal FIN - General 2344012
coded pre-check classes will be Report Business Partner Approach Master Data 2265093
delivered with one TCI Note
(Transport-Based Correction … … …
Instructions)
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 25
SAP System Conversion
Simplification Item Checks

• Replace the old Pre-Check Framework (check classes) to

be run before the conversion to SAP S/4HANA.

• Can (and should) be run by the customers manually in

advance and will be run by SUM when starting the
conversion

• Check if serious issues exist in the system which could

cause the system conversion/upgrade to fail.

• Compared to the old Pre-Check Framework the

Simplification Item Checks
• Are easier to implement (2 SAP notes instead of >50 SAP notes)
• Support not only system conversions to SAP S/4HANA, but also
upgrade within SAP S/4HANA
• Provide improved handling of the check results (e.g. exception For more information see SAP Notes
handling)
• Also include relevancy checks for Simplification Items (same like • 2399707
the SAP Readiness Check for SAP S/4HANA)
• 2418800
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 26
SAP System Conversion
Overview of Technical Process Steps

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 27
 SAP System Conversion
Maintenance Planner

• The Planning tool (successor for MOpz) for update,

upgrade, migration, conversion, installation
http://apps.support.sap.com/sap/support/mp

• Preparations for Conversion: Check and Plan

• Checking Source System concerning Add-Ons,

Business Functions, Industry Solutions
License for SAP S/4HANA not required for check

• Planning for Conversion Provides Software

Archives & Stack.xml Backend and Frontend Server
(FIORI) are considered

• Un-installation of Add-Ons can be planned now; 3rd

Party Add-Ons may have to be checked separately

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 28
SAP System Conversion
Maintenance Planner
Maintenance Planner
 Solution hosted in SAP Support Portal at:
http://apps.support.sap.com/sap/support/mp
 Define changes (based on your landscape data in customer profile)
 Explore Systems  {SID}  Verify  Plan
 Select files
 Push all required tools, archives and stack.xml to your download basket

More information on Maintenance

Planner:
http://help.sap.com/maintenanceplanner
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 29
System Conversion
Planning for S/4HANA Conversion
Logon to Maintenance Planner 1 3

2 4

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 30

System Conversion
Planning for S/4HANA Conversion

5 7

6 8

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 31

SAP System Conversion
Overview of Technical Process Steps

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 32
 SAP System Conversion
Simplification Item Checks
• Replace the previous Pre-Check Framework (check
classes) to be run before the conversion to SAP
S/4HANA for target SAP S/4HANA 1709

• Can (and should) be run by the customers manually in

advance and will be run by SUM when starting the
conversion

• Check if serious issues exist in the system which could

cause the system conversion/upgrade to fail.

• Compared to the previous Pre-Check Framework the

Simplification Item Checks
Are easier to implement (2 SAP notes instead of >50 SAP
notes)

Support not only system conversions to SAP S/4HANA, but

also upgrade within SAP S/4HANA
For more information:
Also include relevancy checks for Simplification Items (same SAP Note 2399707
like the SAP Readiness Check for SAP S/4HANA)
SAP Note 2418800
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 33
SAP System Conversion
Overview of Technical Process Steps

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 34
What is ABAP Test Cockpit?

Standard Code Inspector checks incl. SLIN

Central infrastructure for functional,
performance, security code checks
Security Checks (CVA)
Extensible infrastructure for customer
specific checks
ABAP ABAP Unit Tests
Uniform quality criteria for your whole system
Test
landscape Cockpit
(ATC) SAP HANA Checks
New quality assurance processes minimize
errors in productive systems
SAP S/4HANA Checks
Smooth migration of ABAP code to SAP
HANA and SAP S/4HANA
Customer specific checks

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 35
SAP S/4HANA readiness checks in
AS ABAP 7.51

Simplification use cases S/4HANA checks

 Functionality no available anymore
 Data model changes
 Data type changes

HANA use cases

 Use of DB vendor specifics (native SQL) HANA checks
 DB operations on pool/cluster tables
 SELECT/OPEN CURSOR statements without
ORDER BY

Use check variant S4HANA_READINESS

S4HANA_READINESS includes
S/4HANA and HANA checks
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 36
Check custom code with ABAP ATC transaction
Test Cockpit (ATC)

 Use the ATC transaction

 Create and schedule ATC run series for S/4HANA
readiness for your custom objects
 Display and filter ATC result
 Get detailed information on an ATC finding
 Navigate to source code from ATC result
 Work with ATC Statistics View

ATC Statistics View

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 37
SAP System Conversion
Custom Code Related Process

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 38
SAP System Conversion
Overview of Technical Process Steps

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 39
 SAP System Conversion
Technical Conversion by Software Update Manager (SUM)

 Technical Conversion executed by Software Update Manager (SUM)

 Conversion tasks for SUM:

Database migration
Provide SAP HANA database (if required)

Software update
Provide new applications and new tables

Data conversion
Conversion of table content to new data model

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 40
 SAP System Conversion
SUM 2.0 for all Conversion Paths
• Software Update Manager (SUM) 2.0 introduced in Q3 2017 (part of SL Toolset 1.0 SPS 21)
• SUM 1.0 and SUM 2.0 will be offered in parallel, exclusive scenarios (other version will reject to run)

• Maintenance Planner will provide the respective version for maintenance activity

• SUM 2.0 includes R3load already (LOADTOOLS.SAR), no need to download separately SAP note
2472835 - Embedding load tools in Software Upgrade and Software Provisioning Manager

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 41
 SAP System Conversion
Procedure (source is non-HANA DB)

SUM Activities
Uptime:
Pre-checks

SHD repository created

SHD repository migrated

Downtime:
 Application data migrated

 System update

 Application data converted

FI Data converted (IMG)

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 42
SUM Prerequisites 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)

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 43
Automatic Load of Table Placement
Introduced with SUM 1.0 SP 20

“Automatic load of table

placement statements” =
attachment of SAP Note
1899817 is applied by SUM

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 44
SAP System Conversion
Overview on required and optional tools

Tool Required for SUM Comment

conversion run?

Transformation Navigator - Focus on complete Suite

Roadmap Viewer - Focus on all transition scenarios

Readiness Check - Requires SAP Solution Manager, includes other tool checks

SUM prerequisite check -

Maintenance Planner Checks Req. for SBX, DEV, QA Requires SAP Solution Manager (workaround possible)
& PRD

Maintenance Planner Plan Req. for SBX, DEV, QA Requires successful Maintenance Planner checks
& PRD

Pre-Checks Req. for SBX, DEV, QA Manual run optional, but SUM run will stop for issues
& PRD

Custom Code Worklist Req. for SBX, DEV, QA Not required for SBX, but will lead to inconsistent target state
& PRD
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ EXTERNAL 45
SAP System Conversion
Overview About Phases and Tools

Preparation phase Realization phase

Add-On Deletion New framework SUM 2.0 (Q3/2017)

System Maintenance Software Update Application specific

Application-specific
Pre-Checks Custom code preparation
Custom Code Preparation
Requirements Planner Manager (SUM) Follow-up Activities
follow-up activities

Cross-Application & Application-specific Preparation Activities

New SUM
Prerequisites Check

Simplification List Simplification Item

Catalogue

**)incl. migration of
Readiness Check FI Customizing and
*) incl. Data
preparation of Transformation Navigator
financial data
Roadmap Viewer
© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 46
 SAP S/4HANA system conversion
Sample Mock Process

Preparation phase Realization phase

Basis Basis Conducting SUM of DMO uptime User lockout and ramp-down business operation Basis conducting SUM of DMO downtime

Functional Project Team executes Pre-Check Tasks Fin Migration Validations

Go Live
Business Uptime Quiet Time and Ramp Down Business Downtime
Business Impact
Extraction Configuration Checks Preprocessing Execution (Downtimes) Postprocessing
SUM Phases

This is where the customer will execute the Pre-Checks:

• R_S4_PRE_TRANSITION_CHECKS (1511/1610)
• /SDF/RC_START_CHECK (1709)
• RASFIN_MIGR_PRECHECKS CVI Sync
• FINS_MIG_PRECHECK_CUST_SETTNGS Fin period lock
Run FIN consistency
checks of
transactional data and
During the Configuration roadmap step in totals
SUM tool executes the program
R_S4_PRE_TRANSITION_CHECKS
(1511/1610) or /SDF/RC_START_CHECK
(1709) and ensures all errors are resolved
before it will continue

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 47
 SAP S/4HANA – System Conversion
APPROACH – A BIG PICTURE - EXAMPLE( 3 TIER LANDSCAPE )
SAP Business Suite SAP S/4HANA
Prepare Phase
SAP ERP 6.0, EHP xx SAP S/4HANA, on- FES B1 Maintenance Planner
12 Prepare Phase 13 Realize Phase premise edition 1709 P
R
AnyDB or SAP HANA SAP HANA O F1 Pre- Check
F1 D1 B2 F2 D
6 11 14 D1 Custom Code Check And Analysis

Realize Phase
SUM- Data Migration, Software Update,
SAP ERP 6.0, EHP xx 8 Prepare Phase 9 Realize Phase SAP S/4HANA, on- FES B2 Data Conversion
premise edition 1709 Q
A Application Preparation/ Post
AnyDB or SAP HANA F1 D1 B2 F2 SAP HANA U F2 Processing and Testing
L
7 10 D2 Custom Code Adaption

Realize Phase
SAP S/4HANA, on- FES F3 Delta Process / Functionality
SAP ERP 6.0, EHP xx 4 Prepare Phase 5 Realize Phase premise edition 1709
D Delta Development – Fiori / Report/
E D3
1
AnyDB or SAP HANA
B1 F1 D1 F2 B2 F2 D2 F3 D3 SAP HANA
V
Enhancement

S
Transport Request B Basis Activity/Effort
A
N
F Functional Activity/Effort
SAP ERP 6.0, EHP xx 2 Prepare Phase 3 Realize Phase SAP S/4HANA, on-
FES D
B System Copy
premise edition 1709

B2 F2 D2 F3 D3 O D Development Activity/Effort
AnyDB or SAP HANA B1 F1 D1 F2 SAP HANA X

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 48
SAP S/4HANA – System Conversion
Steps & Details

1 Create ERP Sand Box using Production Data  Customer should be aware that when approaching the ERP Quality system conversion, ERP
Development and ERP Quality system will not be available for fixes to be carried in current ERP
Prepare Phase in Sand Box System-Maintenance Planner, Readiness Check, Pre-Check, Production system(Customer Code Freeze)
2 Custom Code Check and Analysis and Application Preparation
Prepare Phase in Quality System- Readiness Check, Pre-Check, Custom Code
 As a best practice stack file for all the system in landscape should be created on 8 Check and Analysis and Application Preparation, Release Transport requests from
the same day as there are solution updates happening very frequently in the ERP Quality system
maintenance planner
Realize phase – SUM- Data Migration, Software Update, Data Conversion, Application
9 Realize phase – SUM- Data Migration, Software Update, Data Conversion,

3 Preparation/ Post Processing, Custom Code Adaption, Delta Process / Functionality, Delta
Development – Fiori / Report/ Enhancement. System converted to S4HANA and Testing Import Transport Requests in S4HANA Quality environment Application Preparation/ Post
10 Processing, Custom Code Adaption, Delta Process / Functionality, Delta Development – Fiori
 Customer does practice and capture learning of System Conversion steps involved / Report/ Enhancement and Testing, Release Transport requests
 Estimate time taken for the different steps involved in System Conversion
11 Import Transport Requests in ERP Production environment
 Effort Estimate matrix – Resource – Basis , Functional and Development
 Detail project planning of System conversion of customer landscape Prepare Phase in Production System- Readiness Check, Pre-Check, Custom Code
12 Check and Analysis and Application Preparation,
 Customer should be aware that when approaching the ERP Development system
conversion, ERP Development system will not be available for fixes to be carried in current 13 Realize phase – SUM- Data Migration, Software Update, Data Conversion,,
ERP Production system (Customer Code Freeze)
Import Transport Requests in S4HANA Production environment Application Preparation/ Post
Prepare Phase in Development System-Maintenance Planner, Readiness Check, Pre-Check,
4 Custom Code Check and Analysis and Application Preparation, Release Transport requests from
14 Processing and Testing, Custom Code Adaption, Delta Process / Functionality, Delta
Development – Fiori / Report/ Enhancement,
ERP Development system
Realize phase – SUM- Data Migration, Software Update, Data Conversion, Application  Any Miss-match found between configuration and development objects between S4HANA
5 Preparation/ Post Processing, Custom Code Adaption, Delta Process / Functionality, Delta Development System and S4HANA Quality system should be redone in S4HANA Development
Development – Fiori / Report/ Enhancement and Testing, Release Transport requests system and transport requests should be generated for same all the way into S4HANA Quality and
Production system
6 Carry out a Refresh of Production data into the Quality System
 Testing in S4HANA solution with/without Fiori need to be done extensively by Customer Users in
7 Import Transport Requests in ERP Quality environment different systems

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ SAP INTERNAL 49
 Contact information:
Thank you. Venkata Tanguturi
S/4HANA RIG Americas

Venkata.tanguturi@sap.com
© 2017 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 platform 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 http://global.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.