Mario WeigendSenior Consultant TechnologyCons Unit Platform TechnologySAP (Schweiz) AG
Migration Pathscenarios and success factors
INFO DAY
Customer
» Overview• Transition Scenarios• Implementation Roadmap
» Details per Transition Scenario• System Conversion• Landscape Transformation• New Implementation
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3Customer
NewImplementation
On-Premise
Cloud
• Example: New or existing SAP customerimplementing a new SAP S/4HANA system
ERP System
Non-SAPSystem
LandscapeTransformation
ERP System- Region A -
ERP System- Region B -
ERP System- Region C -
ü Example: Consolidation of current regionalSAP Business Suite landscape into oneglobal SAP S/4HANA system
On-Premise
Cloud
The Move to SAP S/4HANAThe Transition Scenarios
SystemConversion
ü Example: Complete conversion of anexisting SAP Business Suite system to SAPS/4HANA
ERP System
On-Premise
Cloud
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 4Customer
Transition to SAP S/4HANAScenario 1 – System conversion
Scenario descriptionCustomers who want to change their currentsystem into a SAP S/4HANA system.
Change Database, SAP NetWeaver andapplication transition in one step.
(SAP GUI) / SAP Fiori
SAP HANA
SAP S/4HANA Core
SAP GUI
AnyDB / SAP HANA
SAP ERP Core
Software UpdateManager (SUM)with DatabaseMigration Option(DMO)
SAP S/4HANAOn-premise Edition
What How
Installation andmigration
Rapid Database Migration of SAP Business Suiteto SAP S/4HANA (all one step migration,including data conversion) using SUM with DMO
*
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. 5Customer
Scenario descriptionCustomers who want to consolidate theirlandscape or to selectively transform datainto a SAP S/4HANA system.
(SAP GUI) / SAP Fiori
SAP HANA
SAP S/4HANA Core
SAP S/4HANACloud Edition
SAP S/4HANAOn-premise Edition
Consolidation or selectivedata transformation basedon SAP LT
What How
ConsolidationSAP Landscape TransformationConsolidate clients from different source systems into one new orexisting S/4HANA system (build-up multiple client system)
Selective Data TransformationSAP Landscape Transformation• Carve-out of single entities or processes• Migration of selected SAP applications (example: central Finance)
1
2
Transition to SAP S/4HANAScenario 2 – Landscape Transformation
Benefits+ Value-based migration: selective data
transformation allows a phased approachfocusing the first S/4HANA migrationphase on parts of the business withhighest ROI and lowest TCI
+ Agility: stay on current businessprocesses but move gradually to S/4HANAinnovations (Move to S/4HANA at yourown pace!)
+ TCO reduction: system and landscapeconsolidation with harmonized/ simplifiedprocesses and unified master data lead tolower cost of operations
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 6Customer
Transition to SAP S/4HANAScenario 3 – New Implementation
Scenario descriptionNew installation of SAP S/4HANA e.g. forcustomers migrating a legacy system.
LegacyAny customerslegacy system
SAP Fiori
SAP HANA
SAP S/4HANA Core
SAP S/4HANACloud Edition
SAP S/4HANAOn-premise Edition
What How
Install S/4HANA Software Provisioning Manager
Initial data load fromsource system
SAP Landscape Transformation• SAP source: system connection• Legacy system: file upload;
SAP Data Services additionally supported
1
2
SAP ERP 6.0 orhigher
Option: Initial dataload from Legacy orSAP system basedon SAP LTNon-SAP
Benefits for the customer+ Reengineering and process simplification
based on ready-to-run business processesand reference solution delivered with theproduct
+ Pre-defined migration objects & BestPractices available in a guided process
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 7Customer
Transition to SAP S/4HANAcompare transition scenarios
The transition scenarios differ withrespect to amount & type of datataken overü New installation: Master Data & selected
transactional dataü System conversion: ‘entire’ repository
Deg
ree
ofSi
mpl
ifica
tion
Amount of transferred data
Cloud „Quadrant“
On-premise
Rule of thumb:ü Cloud deployment model when
simplification is ultimate goalü On-premise deployment model is
universally suited
SystemConversion
LandscapeTransformat
ion
NewImplementa
tion
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 9Customer
New ImplementationOn S/4 HANA on premise and cloud
Landscape TransformationBusiness driven migration offerings
Prepare Explore
Migrate Existing
Implementadditional
industry / LOBpackages
+Technical
Architecture& Migration
Planning
All ImplementationScenarios
Dependent onImplementation
Scenarios
Strategy &Roadmap
Implement newinnovations
Installation and datatransition for SAP
S/4HANA
ValueDiscoveryWorkshop
Realize / Deploy
New Install
System ConversionTechnology driven migration offerings
SAP Support andPremium Engagement (optional)
SAP S/4HANAImplementation Roadmap
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 10Customer
The Road to
SAPACTIVATE
● is the unique combination of SAP Best Practices,Methodology, and Guided Configuration tosimplify the adoption of SAP S/4HANA
● delivers ready-to-run business processes optimizedfor SAP S/4HANA
● provides best practices for migration, integrationand configuration for SAP S/4HANA
● is geared for a speedy initial implementation ofSAP S/4HANA and is designed for continuousinnovation
● supports different starting points for customers toadopt SAP S/4HANA - new implementation, systemconversion and landscape transformation
NewImplementation
LandscapeTransformation
SystemConversion
SAP S/4HANAOn-Premise Edition
SAP S/4HANACloud Edition
Details?
In Breakout Session:SAP Solution Manager
» Overview• Transition Scenarios• Implementation Roadmap
» Details per Transition Scenario• System Conversion• Landscape Transformation• New Implementation
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 12Customer
NewImplementation
On-Premise
Cloud
• Example: New or existing SAP customerimplementing a new SAP S/4HANA system
ERP System
Non-SAPSystem
LandscapeTransformation
ERP System- Region A -
ERP System- Region B -
ERP System- Region C -
ü Example: Consolidation of current regionalSAP Business Suite landscape into oneglobal SAP S/4HANA system
On-Premise
Cloud
SystemConversion
S/4HANA
ü Example: Complete conversion of anexisting SAP Business Suite system to SAPS/4HANA
ERP System On-Premise
The Move to SAP S/4HANAThe Transition Scenarios
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 13Customer
SAP S/4HANA System ConversionSupported Start Releases
ERP 6.0 withEhP (0-7)
ERP 6 andSuite on
HANASuite on
HANAincl. sFIN 1.0
& 2.0
Move to SAP S/4HANA On-Premise
• move from different start releases tothe SAP S/4HANA On-Premise Edition.
• migrate to SAP S/4HANA On-Premisebased on pre-configuredimplementation content(implementation and migration contentpackages)
SAP S/4HANA CoreInnovation Packages (sFIN / sLog / …)
SAP HANA
SAP Fiori
One
-Ste
pPr
oced
ure
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 14Customer
PreparationPhase
ConversionPhase
PostProcessing
MaintenancePlannerChecks
SoftwareInstallation
(SUM&DMO)
• Simplification List• Custom Code
Adaption
ApplicationTesting
Pre-Checks/Transition
Checks
CustomCode
Checks
XPRARUN
Application SpecificPreparations
Application SpecificFollow-UpActivities
SPAU/SPDD
SAP S/4HANA System ConversionProject Phases
• SolMan: TestCases, Test Plan
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 15Customer
SAP S/4HANA System ConversionTechnical Details
Uptime
Start ReleaseTarget Release
Shadow System
Downtime
Preparation Phase
UptimePost Processing
Pre-Transformation Checks
Application specific adaptionson start release
Downtimeminimizing stepslike shadowrepository
DB migration (if req.)
Table replacement
Kernel switchAIM, XPRA …
Time
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 16Customer
Welcome to the world of Unicode!
• SUM creates a shadow system to reduce downtime processing
• Shadow system is based on target release kernel
• Shadow system has to be non-UC for non-UC source systems
not possible for target systems based on SAP NetWeaver 7.5
SAPS/4HANA
Based onSAP NetWeaver 7.5:only Unicode (UC)No non-UC kernel
System Conversion requires a Unicode (UC) source system
Non-Unicode source systems will require a two-step approach
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 17Customer
Source system is Unicode:One-step system conversion possible
1503 | 1602
SUMw/ DMO
SAPS/4HANA
AnyDB
SAP ERP 6.0EHP x…7
SAP ERP 6.0EHP 7 / 8
SAP SimpleFinance 1503
SAP S/4HANAFinance 1602
7.407.40 / 7.50 7.507.50EHP 7 / 8* EHP 7 EHP 8 S/4CORE
AnyDB
From Suite From S/4HANAFrom ERP on HANA
SUMSUM
AnyDB
SAP ERP 5.0&
SAP R/3 4.7
May be onUnicode, but
CVI notavailable,so 2 steps
CVI: Customer-Vendor-Integration,prerequisite for System Conversion
SAP HANA DB
non-HANA DB
Legend
6.20 / 6.40 7.0x … 7.40EHP 0 … 7
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 18Customer
SAP S/4HANA System ConversionDetails of simple Finance
BSEG COEP
BSID COSS COSP
Technical Upgrade
BSEG COEP FAGLFLEXA
ACDOCABSID_BCK COSS_BAK COSP_BAK
COSS
COSP
BSID
Data-MigrationBSEG COEP FAGLFLEXA
BSID_BCK COSS_BAK COSP_BAKACDOCA
BSIDCOSP
COSS
Persistency layout is preparedduring technical upgrade.- Rename Totals Tables- Create ACDOCA- Create Compatibility Views
Technical Downtime: few hours
Line Items are merged into the newUniversal Journal (ACDOCA).Runtime: depends on table size
Line items tables
Index and totals tables
Data model of classic Finance
FAGLFLEXA
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 19Customer
NewImplementation
On-Premise
Cloud
• Example: New or existing SAP customerimplementing a new SAP S/4HANA system
ERP System
Non-SAPSystem
LandscapeTransformation
ERP System- Region A -
ERP System- Region B -
ERP System- Region C -
ü Example: Consolidation of current regionalSAP Business Suite landscape into oneglobal SAP S/4HANA system
On-Premise
Cloud
SystemConversion
S/4HANA
ü Example: Complete conversion of anexisting SAP Business Suite system to SAPS/4HANA
ERP System On-Premise
The Move to SAP S/4HANAThe Transition Scenarios
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 20Customer
SAP S/4HANA Landscape TransformationProject Phases
1
Prepareü Analyze involved systems to collect
project relevant information tosupport project scoping andselection of the rightTransformation Solutions
2
Exploreü Determine and pick required
business from BusinessObject Directory (BOD) orcreate newü Execute context based
analysis to identify activeobjects and customer tablesü Define selection criteria and
assign transformation rules
3
Realize in n-Test cyclesand Deployü Generate runtime objects in
the test and productivelandscapeü Execute (test-) migrations
and conversions
Technology Foundation – SAP LT Platform running on SAP Solution Managerü Analysis, Design, Execution and Process Control functionsü Integrated Transformation Solutions: Migration (OBMIG), Conversion (OBCNV) and Posting (OBPOE)
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 21Customer
SAP S/4HANA Landscape TransformationSystem Consolidation
Consolidation frommultiple dimensions
Start Release
AnyDB or SAP HANA
SAP ERP Core
Start Release
AnyDB or SAP HANA
SAP ERP Core
SAP Fiori
SAP HANA
SAP S/4HANA Best Practices
SAP S/4HANACloud Edition
SAP S/4HANAOn-premise Edition
Example: System Consolidation• Consolidation and harmonization
of two or more SAP source systemsinto one (central) SAP S/4HANAsystem
• Significant simplification effectscan be realized using this approach
• Initial analysis needed to determinebusiness related descisions
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 23Customer
NewImplementation
On-Premise
Cloud
• Example: New or existing SAP customerimplementing a new SAP S/4HANA system
ERP System
Non-SAPSystem
LandscapeTransformation
ERP System- Region A -
ERP System- Region B -
ERP System- Region C -
ü Example: Consolidation of current regionalSAP Business Suite landscape into oneglobal SAP S/4HANA system
On-Premise
Cloud
SystemConversion
S/4HANA
ü Example: Complete conversion of anexisting SAP Business Suite system to SAPS/4HANA
ERP System On-Premise
The Move to SAP S/4HANAThe Transition Scenarios
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 24Customer
SAP S/4HANA New ImplementationGuided Configuration
Data Migration• The data migration activities can be executed based on the cloud implementation
cockpit• Based on the selected Business Scenarios relevant data migration objects are
proposed• Existing customer can connect their SAP Business Suite system. For new customer a
template based approach can be used
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 25Customer
SAP Business Suite(Source System)
S/4HANA Cloud(Target System)SL
T
SLT
Customer Master(classic)
…
Customer Master(S/4HANA)
…Transfer into new datastructure
(a)
DataExtraction
DataMapping
API/BAPICall
SLT
Virtual private network (VPN)
(a) SAP Landscape Transformation(SLT) Tool required on customersOP system
(b) Customer need to establish VPNconnection to OP System
(c) For new customers (legacymigration) a template-basedapproach is used (XLS).
(b)
(c)
SAP S/4HANA Cloud System• SAP Cloud Operations: provision of cloud instance• Customer: Implement configuration in target• Customer: Implement integration to SAP Business Suite System or use
template-based approach• Service Center: Re-Implement customer enhancements
SAP S/4HANA Cloud Data Migration• Consulting Service:
• Maintain data mapping (Business Objects to be transferred) in SLT• Transfer of master data; Transfer of transactional data
• Customer: Data Validation
SAP S/4HANA New ImplementationData Migration Functionality (Cloud)
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 26Customer
Extra
ct&
Prof
ile
Reconciliation
SAP ConfigurationExtraction
Flat Files, XML,HTML, CSV,Mainframe, MicrosoftExcel
Legacy Databases(ODBC)
Legacy Applications& Cloud Applications
Validate & LoadBusiness Validation Rules,Automatic SAP Configurationvalidation
TransformTransform data into SAP structure
CleanseName Parsing, Address Parsing andCorrection, Material/ProductParsing, Matching
Legacy DataEnvironment
Data Staging and TestEnvironment Loading Target
Environment
WebService
IDocs
Staging Area
Dashboards andBusiness Reporting
Performance Analysis
Transparency, Governanceand Communication
1
2
3
4
5
6
7
SAP S/4HANA New ImplementationData Migration based on SAP Data Services
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Thank you
Mario WeigendSenior Consultant TechnologyCons Unit Platform TechnologySAP (Schweiz) AG
© 2016 SAP SE or an SAP affiliate company. All rights reserved. 28Customer
© 2016 SAP SE oder ein SAP-Konzernunternehmen.Alle Rechte vorbehalten.
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftlicheGenehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.
SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder eingetragene Marken derSAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Ländern weltweit.Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx.
Die von SAP SE oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.
Produkte können länderspezifische Unterschiede aufweisen.
Die vorliegenden Unterlagen werden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich zu Informationszwecken.Die SAP SE oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation.Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligenProdukte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren.
Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehörigen Präsentation dargestellteGeschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Diese Publikation oder eine zugehörige Präsentation,die Strategie und etwaige künftige Entwicklungen, Produkte und/oder Plattformen der SAP SE oder ihrer Konzernunternehmen können von der SAP SE oder ihrenKonzernunternehmen jederzeit und ohne Angabe von Gründen unangekündigt geändert werden.Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oderFunktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatsächlichen Ergebnisse von denErwartungen abweichen können. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder, zu dem sie getätigt wurden. Dem Leser wird empfohlen,diesen Aussagen kein übertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen nicht auf sie zu stützen.