Embed Size (px)
Citation preview
© 2016 Cognizant © 2017 Cognizant
November 2017
S/4HANA Migration Strategy
Aksel Oland
‹#› © 2016 Cognizant 2
Motivation for customers to migrate to S/4HANA
• Business Suite (ECC/ERP): end of mainstream
maintenance 31.12.2025
• No new functionality in BS, only S/4
• +++++
‹#› © 2016 Cognizant 3
Starting steps
• A natural step is to start with SAP Transformation Navigator
– The SAP Transformation Navigator is a self-service road-mapping tool to help you chart your digital transformation with SAP S/4HANA and other SAP Product offerings
– Marketing video (https://vimeo.com/216039186/59a263394a)
– Try it out: SAP Transformation Navigator (http://sap.com/transformationnavigator)
– You need a “S-User”
• After a lot of decision points, you’ll get a set of guides:
– A lot of “marketing”
– but also a lot of useful information on the road ahead
• Also useful:
– https://www.sap.com/services/transition-to-s4hana.html
‹#› © 2016 Cognizant 4
How to move to S/4HANA?
• Start with reading: Getting Started Guide 1709 Link
– Documentation of the typical ways of going from Business Suite to S/4
– Basically 3 ways:
‹#› © 2016 Cognizant 5
Regardless of Scenario: Run a Readiness Check to get an idea of the new world
‹#› © 2016 Cognizant 6
1 New Implementation: A struggle to move the legacy data:
• How to migrate your data
– https://blogs.sap.com/2017/05/29/migrating-data-to-your-new-sap-s4hana/
‹#› © 2016 Cognizant 7
1 Migration tools
‹#› © 2016 Cognizant 8
2. System Conversion
‹#› © 2016 Cognizant 9
2. System Conversion: Hurdles
• Business partner https://launchpad.support.sap.com/#/notes/2265093 (CVI activation in BS)
• Custom Code must be adapted
• Data Volume Is downtime Sat-Sun enough?
– Archive data before
– NearZeroDownTimeOption
– Alternatively a 2 or 3 step approach
• BS SoH S/4 1605 S/4 18xx
‹#› © 2016 Cognizant 10
2. System Conversion: Practical Examples (2015-2016)
1. Fix Custom Code
2. Migrate to SoH ( 30 hr downtime)
3. Convert to S/4 in sandbox
4. Correct data in SoH QA and PRD
5. Convert to S/4 in DEV and QA
6. Convert to S/4 in PRD (24 hr downtime
for 11 years data ( 300 mill ACDOCA
records)
See Conversion Guide for SAP S/4HANA
1709 - SAP Help Portal
‹#› © 2016 Cognizant 11
3. Landscape Transformation (LT)
• Read about it https://www.sap.com/documents/2016/09/e26b67aa-8c7c-0010-82c7-
eda71af511fa.html#
‹#› © 2016 Cognizant 12
New installation vs. Conversion
Do a…if New Installation Conversion
Non Unicode or <ECC6.0 X
Long running Production/Projects X
A “good” source system X
Big data volume X
Sensitive to downtime X
Sensitive to Big Bangs & chaos X
Highly customized/modified X
Redesign processes and Financial Model X
See also Blog
‹#› © 2016 Cognizant 14
Cognizant S/4HANA Related Service Offerings
Strategy Workshops / Assessments
Approach to Move to S/4HANA/SOH
Landscape Assessments
Business Process Transformation
Business Process Optimization
Cloud Deployment Advisory
Organizational Change Management
Services
Technical Code Assessments and
Optimizations
Upgrade / Migrate to SOH/S/4HANA
Landscape Assessments
Landscape Consolidations
OS Upgrade / Migration
Database Migrations
Testing Capabilities
Remove ABAP Code Redundancies
by Code Optimizations
Identify Reporting to be Moved on
SOH/S/4HANA
Performance Optimizations
S/4HANA Implementation
Implementing S/4HANA
BPC for S/4HANA
Implementing FIORI services for
Simplified User Experience
ABAP Code Optimizations for
Simplified Data Models
‹#› © 2016 Cognizant 15
Appendix: Fun ACDOCA Facts
• 361 Fields (Excluding CI_COBL and COPA customer dimensions)
• Since totals are gone (GLT0), Yearly balances stored in ‘B*’ Documents, populated with
FAGLGVTR
• Migration creates a lot of strange documents: Look for ACDOCA-BSTAT and ACDOCA-
MIG_SOURCE
• Document number prefixes:
– B Balance
– C Old CO documents
– D Migration corrections
• Group Currency!
• FICO document integration in newGL in BS; Archive them all before migration
