Migrácia na SAP S4/HANA
Transition to S4/HANA
October 2016
Customer
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other agreement
with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to
develop or release any functionality mentioned in this presentation. This presentation and SAP's
strategy and possible future developments are subject to change and may be changed by SAP at any
time for any reason without notice. This document 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. SAP assumes no responsibility for errors or omissions in this
document, except if such damages were caused by SAP intentionally or grossly negligent.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
2
SAP S/4HANA
Key Business Innovations in SAP S/4HANA
Universal
Journal
Material Requirements
Planning
Inventory
Management
Material
Valuation
Accelerated
Financial Close
Re-architecting for
in-memory platform
> 20
3
Laggards
Sales Representative
Order Management & Billing
Procurement Clerk
Best-in-class
<1
Target
Material Planner
Responsive user
experience design
Central Finance
Available To Promise &
Backorder processing
Capacity Planning
Industry solutions to
core
Unifying functionality
in core
This is the current state of planning and may be changed by SAP at any time.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP S/4HANA Finance
Customer
3
SAP S/4HANA
Main Innovation Pillars of S/4HANA
New User Experience (SAP Fiori)
Simplified Data Model and
Application Innovation
SAP HANA
SAP FIORI AS THE USER EXPERIENCE PARADIGM
• Role-based, web-based, all devices
• Smart Business Cockpits (from KPIs to guided transactions)
• Operational Reporting
 REAL-TIME DECISION-SUPPORT, EFFICIENCY
SIMPLIFICATION OF APPLICATIONS AND UNDERLYING DATA MODEL
• Principle of One: elimination of redundancy on application level
• Single source of truth: new data model w/o redundancies
• Application optimizations
 HIGHER FLEXIBILITY & THROUGHPUT, INNOVATIONS
SAP HANA AS THE UNDERLYING PLATFORM
• OLAP & OLTP Merge
• Data Compression
• Various engines for planning, predictive, text mining, …
 SPEED, SIMPLIFICATION, INNOVATIONS
DEPLOYMENT MODEL OF CHOICE: On-premise, Public Cloud
 BUILT-IN CLOUD QUALITIES for all deployment options available (e.g. guided configuration)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
4
SAP S/4HANA
High level stack architecture SAP S/4HANA – Logical view
Fiori Shell
Fiori Apps
(UI5)
https
 Launchpad / SAP Fiori
(SAPGUI for Windows still available for
compatibility reasons)
Fiori Launchpad
(Homepage)
oData
Search
oData
INA
SAP Gateway
S/4HANA ABAP
 Data structures
Transactional Logic
(Compatibility partly provided by
Compatibility Views and Core Data
Services)
Analytics
SAP MOBILE
PLATFORM
SAP Screen Personas
Web GUI for SAP
Web Dynpro
(Enterprise-)Search
planned
SAP WEB DISPATCHER
SAP S/4HANA Architecture
differs from the classical SAP
Business Suite architecture
CDS View
SAP HANA
Database Tables
This is the current state of planning and may be changed by SAP at any time.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
5
SAP S/4HANA
Overview of Transition Scenarios
System
Conversion
ERP System
On-Premise
 “Uplifting” an existing SAP ERP system
to SAP S/4HANA
– with all its code, configuration and data
ERP System
- Region A -
Landscape
Transformation
ERP System
- Region B -
ERP System
- Region C -
New System
Implementation
On-Premise
ERP System
Cloud
On-Premise
Non-SAP
System
Cloud
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
 Combination of System Conversion or
New System Implementation with
landscape transformation activities
 New implementation of an SAP S/4HANA
system (on-premise or cloud edition) with
– initial data load
– based on SAP model company or import
of (selected) existing configuration
Customer
6
Transition to SAP S/4HANA
Scenario 1 – New Installation
Scenario description
New installation of SAP S/4HANA e.g. for
customers migrating a legacy system.
SAP ERP 6.0 or
higher
Option: Initial data
load from Legacy or
SAP system based
on SAP LT
SAP S/4HANA
SAP S/4HANA
On-premise Edition
Cloud Edition
SAP Fiori
SAP S/4HANA Core
Non-SAP
Benefits for the customer
+
Reengineering and process simplification
based on ready-to-run business processes
and reference solution delivered with the
product
+
New implementation of industry-leading
Business Suite
+
Pre-defined migration objects & Best
Practices available in a guided process
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
SAP HANA
Legacy
Any customers
legacy system
What
How
1
Install S/4HANA
Software Provisioning Manager
2
Initial data load from
source system
SAP Landscape Transformation
•
•
SAP source: system connection
Legacy system: file upload;
SAP Data Services additionally supported
Customer
7
Transition to SAP S/4HANA
Scenario 2 – System conversion
Scenario description
Customers who want to change their current
system into a SAP S/4HANA system.
Database, SAP NetWeaver and
application transition in one step.
Software Update
Manager (SUM)
with Database
Migration Option
(DMO)
SAP GUI
*
SAP ERP Core
AnyDB / SAP HANA
SAP S/4HANA
On-premise Edition
(SAP GUI) / SAP Fiori
SAP S/4HANA Core
SAP HANA
Benefits
+
Migration without re-implementation
+
No disruption for existing business
processes
+
Re-evaluation of customization and existing
process flows
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
*
What
How
Installation and
migration
Rapid Database Migration of SAP Business Suite
to SAP S/4HANA (all one step migration,
including data conversion) using SUM with DMO
Customer
8
Transition to SAP S/4HANA
Scenario 3 – Landscape Transformation
Scenario description
Customers who want to consolidate their
landscape or to selectively transform data
into a SAP S/4HANA system.
Consolidation or selective
data transformation based
on SAP LT
SAP S/4HANA
SAP S/4HANA
On-premise Edition
Cloud Edition
(SAP GUI) / SAP Fiori
SAP S/4HANA Core
Benefits
+
+
+
SAP HANA
Value-based migration: selective data
transformation allows a phased approach
focusing the first S/4HANA migration phase
on parts of the business with highest ROI and
lowest TCI
Agility: stay on current business processes
but move gradually to S/4HANA innovations
(Move to S/4HANA at your own pace!)
TCO reduction: system and landscape
consolidation with harmonized/ simplified
processes and unified master data lead to
lower cost of operations
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
What
How
SAP Landscape Transformation
1
Consolidation
2
Selective Data Transformation
Consolidate clients from different source systems into one new or
existing S/4HANA system (build-up multiple client system)
SAP Landscape Transformation
•
•
Carve-out of single entities or processes
Migration of selected SAP applications (example: central Finance)
Customer
9
SAP S/4HANA landscape transformation scenarios – On premise
SAP LT enabled solutions
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
10
SAP S/4HANA
On-Premise Editions and Adoption Paths
All intermediate steps
can be skipped!
SAP ERP
6.0 EHPx
SAP
S/4HANA
SAP
S/4HANA
Finance
(add-on)
SAP S/4HANA, onpremise edition 1511
SAP S/4HANA 1610
SAP HANA
SAP HANA
SAP Simple Finance,
on-premise edition 1503
SAP S/4HANA
Finance 1605
SAP ERP 6.0 EHP7
SAP ERP 6.0 EHP8
SAP HANA
SAP HANA
SAP ERP 6.0 EHP7
SAP ERP 6.0 EHP8
SAP HANA
SAP HANA
…
 SAP S/4HANA
innovations for
Finance and Logistics
 Speed of SAP HANA
 SAP S/4HANA
innovations for Finance
 Classic SAP ERP
functionality for
everything else
 Speed of SAP HANA
Any DB
Suite on
SAP
HANA
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
…  Classic SAP ERP
functionality
 Speed of SAP HANA
Customer
11
Road Map – Transition to SAP S/4HANA
QG1
Init
Project Mgmt.
Technical
Architecture &
Infrastructure
Implementation Strategy
Design
Review
Data Volume Strategy
Transition Preparation
Analytics & Digital Boardroom Design
Test Planning
Sandbox System Setup
Configuration (General,
Master Data, Core & Delta) *)
Product Enhancements
Cleanup / Archive
Integration Validation
Data Aging Config.
Analytics & Digital Boardroom Configuration
CC. Management Execution
CC. Impact Analysis
CC. Cleanup & Improve
Test Preparation
DEV Setup
Test Execution
Cutover Preparation
Landscape Transformation Design
LT Scenario Implementation *)
Initial Sizing
IT Infrastructure Definition
Sizing & Scalability Verification
Technical
Blueprint
Operations Impact Evaluation
technical and functional
Dress
Rehearsal
Load & Verification
Data Load Preparation
Technical Architecture Definition
Hyper
Care
Support
QAS Setup
Project Delivery
Platform Setup
© 2016
SAP gates
SE or an SAPTask/activity
affiliate company.
All rights functional
reserved.
Quality
type:
QG5
Closing
Central Finance Implementation *
Central Finance Design
Transition Planning
Value and Impact Analysis
Trial System
Provisioning
Fit Gap / Delta Design *)
Data Volume Planning
Transition to
Operations
RUN
End User Training Delivery
Training Enabled
Gap
Validation
Technical
Architecture
System & Data
Migration
Overall Innovation Strategy & Road Map Creation
Application:
Testing
QG4
Execution / Monitoring / Controlling
Activate Solution
/ Sandbox
Custom Code
Extensions
DEPLOY
Organizational Change Management (OCM)
Training Strategy
Application:
Design &
Configuration
QG3
REALIZE
Planning
Team Enablement
Application:
Solution Adopt.
Analytics &
D. Boardroom
QG2
EXPLORE
Handover to Support Organization
PREPARE
Production Cutover
DISCOVER
IT Infrastructure Setup & Test
Operations Implementation
technical
Project Management
IT Infrastructure
Service Finalization
Operations Readiness
Customer
*) Summary node – relates to multiple
activities
13
SAP S/4HANA and System Conversion Overview
System Conversion Project
Discovery / Prepare Phase
t1
System
Requirements
t2
t4
t3
Maintenance
Planner
Realize Phase
Pre-Checks
Custom Code
Migration Worklist
t5
t6
Software Update
Manager (SUM)
t
Application specific
follow-on activities
Database Migration
SAP S/4HANA Simplification List
Software Update
Data Conversion
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
17
SAP S/4HANA and System Conversion Overview
System Conversion Project
One Step System Conversion to SAP S/4HANA, as of release SAP ERP 6.0 and Unicode (1)
SAP S/4HANA Finance(3)
SAP ERP 6.0
EHP 0…8(2)
SAP ERP 6.0 EHP 7/8(2)
SAP ERP 6.0 EHP 7/8(3)
SAP S/4HANA
Any DB
SAP HANA
SAP HANA
SAP HANA
SUM for software update, followed by data model conversion
DMO of SUM for one-step software update and database migration, followed by data model conversion
(1) If a source system is on a release < 6.0 or on non-Unicode, a multi-step conversion approach is required, see also SAP note 2233962.
(2) The conversion from SAP ERP 6.0 EHP8 to SAP S/4HANA 1511 is not possible, only to SAP S/4HANA 1610 or higher.
(3) The conversion from SAP S/4HANA Finance 1605 (on EHP8) to SAP S/4HANA can only be done with target release SAP S/4HANA 1610 or higher.
Be also aware that there are restrictions with respect to the maximum SP-level of the source system for system conversion, see SAP note 2189824.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
18
SAP S/4HANA and System Conversion Overview
System Conversion – One Step vs. Two Steps
System Conversion – One Step or first migrate to SAP HANA?
 Typical result of an evaluation:
Criteria
1. Option:
One Step Conversion to SAP S/4HANA
2. Option:
First Project: Migration to SAP HANA
Second Project: Conversion to SAP S/4HANA
Time to Value
• Faster on target solution which offers: SAP S/4HANA
analytics, higher throughput, new Accounting, new
MRP, SAP Fiori, industry functionality, …
• Fast on first stepping stone (SAP HANA) which offers:
performance, SAP HANA Live, some SAP Fiori, …
• Longer time to get to target solution.
Transition Costs
• Overall lowest costs as only one large project with one
time business testing, …
• Higher costs due to two large projects with each their
own testing, …
• Risk of unnecessary/throwaway effort
Transition Risks
and Impacts
• Higher project complexity
• Potentially longer downtime
• Lower project complexity
• Two potentially long downtimes
• Potentially higher risk because of less testing focus
 In the end the decision depends on:
– Company-specific business requirements / opportunities and desired timeline to get to SAP S/4HANA value
– System-specific transition risks and risk mitigation options
– Other dependencies (e.g. calculated project duration and ability to fit the project into the release calendar of ongoing projects, or availability of
resources)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
19
S/4HANA – Transition Roadmap
Transport Landscape Level Roadmap – Classical Migration Approach Example 1
Original
Transport
Landscape
D01
Q01
2a
P01
3a
1a
5a
Temporary
Systems
(Original Platform)
DT1
QT1
PH1
Retrofit
1b
Targeted
Transport
Landscape
4a
2b
D01
Legend:
Homogeneous Copy
Heterogeneous Migration to HANA
3b
Q01
6
4b
5b
PH1/P01
PH1
P01
Note: The DT1 and QT1 systems are built in order to provide a temporary production support landscape tier, while
the original development and quality assurance systems are being migrated. The changes managed via DT1
and QT1 should be limited to standard (non-invasive) and urgent corrections for the duration of the project.
Transport Path
Retrofit Path
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
20
Transition Roadmap
Project Cycle Definition – Classical Approach – Example 1
Conversion Cycles
Cycle 1
PRD to HANA
“Sandbox”
Source / Target
P01 Copy  P01 HW
Steps
• a) Homogeneous system
copy of P01 to PH1
• b) Conversion of PH1 to
targeted end-state
Purpose
• Test software installation,
HANA migration, S/4HANA
data model conversion with
a production copy
• Configure, Test S/4HANA
• Create a conversion
cookbook
• Execute multiple technical
iterations to become familiar
with the process of
converting the production
system
Cycle 2
DEV to HANA DEV
Cycle 3
QA to HANA QA
Cycle 4
PRD to HANA
“Sandbox”
Cycle 5
PRD to HANA
“Sandbox”
Cycle 6
PRD Conversion
Source / Target
D01 D01
Source / Target
Q01 Q01
Source / Target
P01 Copy  P01 HW
Source / Target
P01 Copy  P01 HW
Source / Target
P01  P01
Steps
• a) Homogeneous system
copy of D01 to DT1
• b) Conversion of D01 to
targeted end-state
Steps
• a) Homogeneous system
copy of Q01 to QT1
• b) Conversion of Q01 to
targeted end-state
Steps
• a) Homogeneous system
copy of P01 to PH1
• b) Conversion of PH1 to
targeted end-state
Steps
• a) Homogeneous system
copy of P01 to PH1
• b) Conversion of PH1 to
targeted end-state
Steps
• Conversion of P01 to
targeted end-state
Purpose
•Build temporary production
support development
environment (DT1)
•Establish S/4HANA
development environment
(D01)
•Configure, Test S/4HANA
•Refine cookbook
Purpose
•Build temporary production
support quality assurance
environment (QT1)
•Establish S/4HANA QA
environment (Q01)
•Enhance cookbook
•Testing environment:
Purpose
•Mock cutover
•Optimize/verify E2E
business downtime
•Finalize cookbook
•Finalize cutover plan
•Testing environment:
Purpose
•Final dress rehearsal
•Validate E2E business
downtime
•Validate final cookbook
•Validate cutover plan
Note
• Conversion steps will differ
from production
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
- Integration
- Functional regression
- Operational readiness
- User acceptance
- Infrastructure testing
- Post-cutover operational
performance testing
Purpose
•Establish new S/4HANA
PRD environment
Note
•Execute end-to-end (E2E)
business downtime
precisely as defined within
the cutover plan
•Execute technical steps
precisely as defined in the
cookbook
Customer
21
Transition Approaches and Tools
Selecting the Right Approach and Tool
Points to Consider
 Pick the conversion approach and toolset based on scope and the
business downtime objective.
 There are many factors that influence the downtime associated with a
system conversion, including:
o Scope (e.g. software changes, Unicode conversion, data center relocation, etc…)
o Source System Performance (e.g. CPU, IO, memory, DB performance, NW release,
etc…)
o Size of the Source System (e.g. size of the database, largest tables, status of
housekeeping, etc…)
o Target System Performance (e.g. CPU, IO, memory, DB performance, NW release, etc…)
o Communication Performance (e.g. network speed, network latency, etc…)
o Toolset(s) Selected (e.g. SWPM, SUM, DMO of SUM, version of the toolset, etc…)
o Conversion Approach (e.g. Standard vs. downtime minimized)
o Ramp-down and Ramp-Up Activities (e.g. interface management, batch job management,
pre & post-migration validation, etc…)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
22
Transition Approaches and Tools
Comparison of Transition Approaches
System Conversion
“Standard” Approach
Description
Near Zero Downtime Approach
Description
 Utilizing generally available tools to implement the required software
changes, OS/DB migration (if required), and data model conversion.
 Using a cloned system based methodology, the transition occurs using
standard tools on a clone of the productive system.
 When the source environment is Unicode, the target product and
version can generally be achieved in a single step.
 Productive transactional activity is captured and recorded for later
replay into the cloned environment.
 There are no special resource requirements necessary to execute this
approach, however experienced resources are highly recommended.
Procedure
 Execution of the Software Update Manager (SUM) variant required to
support the transformation from the source to the target.
Common Drivers
 Downtime: The size of the source system and the allowable business
downtime window permit the use of this approach.
 Cost: This approach does not require additional tools or infrastructure
to support the transformation.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Procedure
 Tables are classified and database triggers capture transactional
changes in the source system.
 A clone of production is created and isolated from change, with the
exception of the intended transformational activities (e.g. software
changes, OS/DB migration, and data model).
 The transactional activity is “replayed” from the source system into the
cloned system to bring the target to a consistent transactional state.
Common Drivers
 Downtime: The size of the system and the available business
downtime window requires additional steps to minimize the downtime.
Customer
23
Transition Approaches and Tools
System Conversion Related Tools
Software Provisioning Manager (SWPM)
• In regards to S/4HANA, if required, this toolset can be used to migrate a system to SAP HANA (at
the required software level required for SAP HANA) prior to a S/4HANA conversion
• Can also be used to execute a Unicode conversion or conduct the installation of a new system
Source
SW Ver.
Source
SW Ver.
Source
SW Ver.
Target
SW Ver.
Source
SW Ver.
Target
SW Ver.
• Additional Information: http://support.sap.com/sltoolset
Software Update Manager (SUM)
• In this context, used to either install and/or update S/4HANA components from Suite on HANA or
SAP S/4HANA Finance, or update the source software level in preparation for a HANA migration
• Generally used to update the software version and/or Support Package Stack of an SAP system
• Additional Information: http://support.sap.com/sltoolset
Database Migration Option of Software Update Manager (DMO of SUM)
• Implement and/or update S/4HANA software components while migrating to SAP HANA in a
single step, when the source is Unicode
• Alternatively, upgrade, Unicode convert, and migrate an existing system to SAP HANA in a
single step, when the source is non-Unicode
• Additional Information: http://support.sap.com/sltoolset,
SAP Note 2257362 - Database Migration Option (DMO) of SUM 1.0 SP17
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
24
Transition Approaches and Tools
System Conversion Related Tools – Additional DMO of SUM Variants
Downtime Optimized DMO
• Upgrade an existing ABAP-based system and migrate to SAP HANA in a downtime
optimized single step
• Leverages SAP Landscape Transformation technology to migrate a subset of tables during
the uptime of the productive instance, thereby reducing the duration of downtime
Source
SW Ver.
Target
SW Ver.
• Currently available as a pilot offering for SAP Business Suite migrations to SAP
HANA. SAP S/4HANA data model conversions are not yet supported.
• Additional Information: http://scn.sap.com/community/it-management/alm/softwarelogistics/blog/2014/09/08/dmo-downtime-optimization-by-migrating-app-tables-duringuptime-preview
DMO to SAP Cloud
• Install S/4HANA software components, migrate to SAP HANA, and move to the SAP HANA
Enterprise Cloud, all in a single step
• Available to SAP employees to support customers moving from an on-premise or hosted
environment to the SAP HANA Enterprise Cloud
• Additional Information: SAP Note 2115372 - DMO to SAP cloud (SAP Internal)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Source
SW Ver.
On-premise
or Hosted
Target
SW Ver.
SAP HANA Enterprise Cloud
Customer
25
Transition Approaches and Tools
“Standard” System Conversion Approach – DMO of SUM Conversion Steps
System Conversion to SAP S/4HANA including HANA Migration with DMO of SUM
Initial Environment
ERP
6.0x
One-step conversion to SAP
S/4HANA with the Database
Migration Option (DMO) of Software
Update Manager (SUM)
Target Environment
S/4
HANA
Unicode
1. Start uptime activities of the software
deployment using DMO of SUM
4. One-step migration to SAP HANA with S/4HANA
software installation using DMO of SUM
2. Start of the business downtime
5. S/4HANA data model conversion using SUM and FIN
data model conversion cockpit (IMG)
3. Ramp-down of production use on the initial
environment
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
6. Post upgrade and migration activities
7. Ramp-up process to reinstate productive operations
Customer
26
Transition Approaches and Tools
“Standard” System Conversion Approach – DMO of SUM Phases
System Conversion to SAP S/4HANA including HANA Migration with DMO of SUM
Downtime minimizing
steps like shadow
repository
DB migration (if req.)
Table replacement
Kernel switch
Data conversion to new data model
Shadow System
Post Processing
Target Release
Start Release
S/4
HANA
Uptime
Downtime
Preparation Phase
Uptime
Pre-Transformation
Checks
ERP
6.0x
Application specific
adaptions on start
release
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
t
Customer
27
Transition Approaches and Tools
“Standard” System Conversion Approach – Downtime Optimized Data Conversion*
System Conversion to SAP S/4HANA including HANA Migration with DMO of SUM
Downtime minimizing
steps like shadow
repository
DB migration (if req.)
Table replacement
Kernel switch
Data conversion to new data model
Shadow System
Post Processing
Target Release
Start Release
S/4
HANA
Uptime
Downtime
Preparation Phase
Uptime
Pre-Transformation
Checks
ERP
6.0x
Application specific
adaptions on start
release
Downtime Optimized Data Conversion is planned for SAP S/4HANA 1610*
The approach is to execute a majority of the data conversion during the uptime, on shadow
system, and only process final delta in downtime.
t
* Available on request for some larger tables for target release S/4HANA 1511 SR1 (FPS2)
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
28
Transition Approaches and Tools
“Standard” System Conversion Approach – Downtime Optimized Data Conversion
System Conversion to SAP S/4HANA including HANA Migration with DMO of SUM
Concept for downtime optimized data conversion planned for SAP S/4HANA 1610
6
Shadow System
SAP HANA DB
1 Source DB SHD REP & CUST
2
Target Release
Start Release
Short
downtime
Uptime
4
Revert to sync point
Conversion
Initial
Migration relevant tables
of relevant
Tables
5
∆
7
Final
migration
∆
of relevant
Post Processing
Migrate
Other
Tables
tables
8
9
10
11
12
t
System Downtime
Sync point
3
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
29
Transition Approaches and Tools
Near Zero Downtime (NZDT) Approach – Overview
Approach Description
 The data model conversion, HANA migration and other required
steps are performed on an isolated clone of the production system.
 Changes to the content of a database table (or set of related tables)
must be isolated to one of the two systems, as the production and
cloned systems are independent and not synchronized.
 To properly isolate the changes, all tables within the production
system are classified. Based on this classification, database
triggers and logging tables are enabled to capture (or restrict)
transactional activity within the production system.
 Once the technical changes have been implemented in the clone
system, the recorded transactional data is then replayed into the
clone system.
 Downtime is required to finalize the delta replay, complete the data
model conversion process for the recorded transactions, implement
any last minute transports, and to set the cloned system as the
productive environment.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Clone Creation
SAP
Business
Suite
SAP
Business
Suite
anyDB
anyDB
SAP
S/4HANA
System Conversion
Customer
30
Transition Approaches and Tools
Near Zero Downtime (NZDT) Approach – DMO of SUM Conversion Steps
1
Recording
ERP
ERP
6.0x
6.0x
Create clone
Delta replay
ERP
Final delta replay
6.0x
2
Software update, database
migration, …
Data model
conversion
3
S/4
HANA
Final data
conversion
4
5
6
7
8
Production
operation
S/4
HANA
S/4
HANA
via DMO of SUM
Uptime
Downtime
Uptime
1. Start recording on PRD
5. Start on-line replay of the recorded data
2. Create the NZDT clone
6. Begin downtime and finalize replay of the recorded data
3. Start converting the clone to S/4HANA – SUM/DMO
7. Convert the remaining data to SAP S/4HANA data model
4. Convert the data to SAP S/4HANA data model
8. Validate the system and go live with SAP S/4HANA
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
31
Transition Approaches and Tools
Near Zero Downtime (NZDT) Approach – Availability of the Approach
Availability of NZDT for System Conversions to SAP S/4HANA
 System Conversions to SAP S/4HANA
– NZDT is planned for target release SAP S/4HANA 1610
o Q4/2016: Data conversion for full delta in downtime,
making the downtime slightly more dynamic
o Q2/2017: Repeated data conversion in uptime and
final data conversion for final delta in
downtime, returning the downtime to a
more consistent and predictable duration
– NZDT approach not available for the target release
of SAP S/4HANA, on-premise edition 1511
 System Conversions to SAP S/4HANA Finance (add-on versions)
– NZDT supported as of target release SAP S/4HANA Finance 1503 with data conversion for full delta in
downtime
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
32
Transition Approaches and Tools
Common Elements of a Planned Business Downtime
Business Downtime
Productive Operations
Productive Operations
Technical Downtime
Productive
Operations
 Uninterrupted End-User
Activity
 Prepare and Uptime Phases
 Suspend Long Running
Batch Jobs
 Start Flushing Queues (e.g.
BW Extractors, etc..)*
Ramp-Down
Technical Downtime
 Terminate End User
Activity
 Execution of Technical Maintenance
Activities (e.g. Upgrade, Migration, etc…)*
 Finish Flushing
Queues*
 Execution of Functional Maintenance
Activities (e.g. Data Model Conversion,
etc…)*
 Monitor/Terminate
Active Batch Jobs
 Manual Tasks*
Ramp-Up
 Backup
 Functional Validation
 Final Go/No-Go
Decision (aka Point of
No Return)
 Disable Interfaces
 Transports*
 Reinstate Batch
Processing
 Pre-Event Functional
Validation Reports
 SGEN*
 Enable Interfaces
 Update Database Statistics*
 Unlock End Users
 Backup
Productive
Operations
 Uninterrupted End-User
Activity on the New
Version/Platform
 Technical Validation
*Note: If required based on the scope of the project.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
33
Transition Approaches and Tools
Migration Throughput
Rules for Assessing the Export/Import Throughput for
HANA Migration
 Depending on the scope, the migration throughput may only be one
factor in the technical downtime.
 Throughput figures for the export/import of the migration can range
from 200GB and 1TB per hour; where 200GB/hour is typically
achievable with minimal effort, 500GB/hour takes a moderate
investment, and 1TB/hour requires a more concentrated effort.
 Results will vary customer to customer and system to system based
on the factors above.
 Based on the influencing factors, the throughput for a specific
customer system must be validated (as part of a project), using a
copy of production, on production-like hardware, and in a productionlike environment.
Numbers are based on experience with uncompressed databases and reference the size of the source system.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
34
Transition Approaches and Tools
Summary
Migration Approach vs. Migration Tool
A migration approach may be supported with more than one migration tool option. For instance a downtime
minimized lift and shift migration (i.e. with NZDT) can be executed with either SWPM (with or without SUM) or
DMO of SUM.
Validation of the Selected Approach and Toolset
Especially when considering the classical lift and shift approach, it is important to validate the runtime of the
technical downtime activities early within the migration project. The best way to conduct this validation is to use a
copy of production, on production-like hardware, in a production-like environment. It is also highly recommended
to use the same migration tool, and version of the tool, throughout the different migration cycles. If a change is
required, it should be carefully considered and thoroughly evaluated before the Go-Live, including at least one
mock migration before the production cycle.
Business Downtime
It is more than just the duration of the export and import. All of the influencing factors need to be assessed in
order to minimize the impact to the business.
© 2016 SAP SE or an SAP affiliate company. All rights reserved.
Customer
35
Thank You!
Jiří Janák
SAP Solution Architect
SAP Digital Business Services
[email protected]