Learn powerful SAP S/4HANA System Conversion and Implementation strategies for continuous and speedy business innovation.

1. “Infinite possibilities with technology”
How to Prepare for SAP S/4HANA System Conversion

2. 2

3. 3
Digital Transformation Strategy and Advisory Services
Business - IT Strategy &
Planning
Enterprise Reference
Architecture
IT Portfolio
Management
Governance Digital Tech Trends
And Design Thinking
• Digital Commerce & Marketing
• Enterprise Mobility
• Digital Governance
• IoT, Big Data & Analytics
• Software R&D Labs
• Outsourced Product Development
• Enterprise Resource Planning. • Product Lifecycle Management
• Supply Chain Management. •Customer Relationship Management
Digital Enterprise Solutions
Systems of Record and Core IT
Successful S/4 HANA migration
implementation for enterprise clients
• API Strategy & Management • Enterprise Integration
• Enterprise Analytics. • IoT System Integration
• OT-IT Integration
Standalone Applications &
Interconnections
Integrated Enterprise
Environment
Digital Transformation
Systems of Engagement
Digital Integration (DI)
Systems of Insight and Integration
Go Digital with Kellton Tech

4. Speakers
Dr. Srinivas Bandi – Vice President & Head, SAP BU
Email: Srinivas.bandi@kelltontech.com
Ramesh Srinivasan – Head, SAP S/4HANA CoE Technical
Email: Ramesh.Srinivasan@kelltontech.com
4

5. • Introduction
• S/4HANA System Conversion Overview
• Key Considerations for System Conversion
• Impact areas & dependencies
• Conversion Phases
• Key Preparation Areas
• Pros and Cons
• Conversion Best Practices
• Next Steps
• Q&A
5
Agenda

6. S/4HANA Transition Options
Implement (Greenfield)
New or existing SAP ERP customer implements new
S/4 HANA system
Convert (Brownfield)
Existing SAP ERP customer converts an ECC system to
S/4 HANA system
Transform (Blackfield)
Existing SAP ERP customer with one or more ECC
systems transforms fully or selective data into a central
S/4 HANA system
New
Implementation
SAP ERP
Non SAP ERP
Implement
System
Conversion
SAP ERP Convert
Landscape
Transformation
SAP ERP 1
SAP ERP 2
Consolidate
6

7. • System Conversion (Brown field)
 Convert an existing SAP ECC 6.0 System entirely into S/4 HANA system
 Entire system along with historical data is migrated
 Reuse existing implementation, customizations, custom objects
 Add innovations in future (New Fiori apps, AI/ML, LoB etc.)
 Only supported for On-Premise editions (Any Premises)
 Suitable for On-premise, hosting, private cloud target environments
7
System Conversion - Overview
System
Conversion
SAP ERP Convert
Migrate without re-implementation
Minimal business disruption
Review customization and code
S/4HANA System Conversion

8. S/4 HANA Conversion Paths
Notes on source system
• Unicode is required
• ABAP single stack required
• SAP HANA database not required
Refer Release Information Note for
Conversion requirements to the relevant
target S/4HANA release
• 2884313 - SAP S/4HANA 2020: Release
Information
8

9. • Source system Pre-requisites for single step
Conversion to S/4 HANA 1909 / 2020
9
System Conversion - Requirements
Should be ECC 6.0 EhP 0 to 8
Only ABAP Stack supported
Should be Unicode
Any DB – Check supported source DB
versions
Check unsupported OS platforms
Check deployment location
System not meeting any pre-requisite may
need a multi-step upgrade and conversion
 Older version to be upgraded to ECC 6 EhPx
 Dual stack system (ABAP + Java) should be split
 Unicode Conversion should be performed
 OS/DB platforms may need to be upgraded or migrated
to PAM supported releases

10. One step vs Two step Conversion to S/4 HANA
10
Two step conversion will be required if source ECC system does not meet any of the technical pre-requisites
R/3 or
ECC 6.0
Non Unicode /
Dual Stack
Unicode
ABAP Stack
ECC 6.0 EHPx
Unicode
ABAP Stack
One step conversion can be done where source ECC system meets all the pre-requisites
S/4 HANA
S/4 HANA
 Single Downtime (typically weekend)
 Moderate testing efforts
 Technical dependency
 Phased approach
 Multiple Downtime windows
 Higher testing efforts

11. System Conversion – Key Considerations
Key questions?
Is your move to S/4 HANA driven by business or IT?
Can you adopt SAP Best Practices? Do you need to redesign current business processes for long term strategy?
Do you need the customizing and custom code from the existing system?
Do you need past historical data in the new system?
Do you need all or partial (selective) historical data?
What is the extent and complexity of external interfaces?
Do you have multiple ERP source systems? Is consolidation or process harmonization a requirement?
Does your system meet pre-requisites for single step Conversion?
What is your innovation roadmap – short, medium and long term?
What is the expectation on project timeline and business involvement?
Listed below are some of the key questions which can help to define the high level approach for S/4 HANA adoption
11

12. • System Conversion is not a Technical Upgrade
12
System Conversion Impact
• In memory HANA DB
• New data models
• ABAP coding compliance
• Fiori UI
Technology
Stack
• New business process model
• New Data structure
• HANA optimized Coding
• New and obsolete transactions
Application
Stack
Major impact areas
ABAP adjustment
Data migration
Fiori Adoption
Simplification Items
CVI Data Conversion
Custom Code adaptation

13. Hardware &
Performance
Complex
Environment
Functional
Changes
Impacted code
and data
Transition
Approach
Project Time &
Cost
13
Size, Scale and
Redundancy
Custom Code
Interfaces
Adaptation
Assess, Convert,
Test, Deploy
Adoption
Data Volume
Conversion Dependencies
Downtime

14. 14
System Conversion - Activate Phases
Sandbox DEV QAS PRD
System Landscape
Prepare Explore Realize Deploy
Discover Run
ANALYSE
Assess:
• Analyze Source System
• Pre-requisites check
• Dependencies
• Housekeeping
• Identify Impact areas
Use a recent Prod copy Use a recent Prod copy

15. SAP S/4HANA CONVERSION
• Technical Readiness
• Application Readiness
• Simplification Item Check
• Application Data Readiness (CVI)
• Custom Code Analysis
System
Requirements
Maintenance
Planner
Custom Code
Analysis
Pre-Checks
Post Activities
Technical
Simplification
Items Check
Finance
Conversion
Software
Update
Manager
Post Activities
Application
Cutover
Finalization
Preparation Phase
Realization Phase
• Technical Execution (SUM) • Post Conversion Adaptation
• Technical environment
• Finance specific Tasks
• Logistics specific Tasks
• Custom Code Adaptation
• Cutover activities
15

16. 16
Key Preparation Areas
Technical Hardware
Compatibility
Custom Code
Interfaces
UI Adoption
Application Simplification Check
Data Structure changes
Application Data (CVI)
Customizing & Process changes
Testing
ABAP Test
Cockpit
Fiori Apps Library

17. Simplification List for SAP S/4 HANA OP provides information on the simplifications on each technical and application item
in the standard product, compared to the source ERP ECC 6.0
• Information on each simplification item:
• Description, Business impact and Recommendation
• Relevant SAP Notes
• Example:
17
Simplification List and Catalog
URL: https://launchpad.support.sap.com/#/sic/

18. 18
Simplification Item Check *
* SI Check is a mandatory activity.
• Any Items with Error status can prevent the System Conversion process and needs to be addressed prior to conversion
Show stopper
Roadblock / optional exemption
To evaluate
Conditions met

19.  SAP provided tool to check and analyse source system
 Analyses technical and software readiness
 Hardware sizing and infra requirements
 S/4 HANA functional impact – SI Checks
 Custom code adaptation verification
 Application data migration / conversion check
 SAP Fiori app recommendations
19
SAP Readiness Check 2.0
Perform Readiness Check in Production well ahead of the project
http://rc.cfapps.eu10.hana.ondemand.com
Comprehensive tool to check Source system Readiness Dashboard

20.  What size of SAP HANA server do I need?
 Are my add-ons compatible with target S/4 HANA?
 Are my activated Business functions compatible with S/4 HANA?
 Which Fiori Apps are available and relevant to my release?
 Which Simplification Items are relevant to my current release?
 Will my Custom Code work with target S/4 HANA, What remediation actions are required?
 What is the extent of Testing required? Can I restrict testing scope?
20
SAP Readiness Check 2.0 – Key Information

21. Pros
• Quicker transition to S/4 HANA
• Minimal business disruption
• Retain entire historical data
• Prepare phased innovations
• No external data loading or cleansing
Cons
• Technical Pre-requisites are critical
• Housekeeping required for risk reduction
• Custom code & interface adaptation is key
• Process re-engineering is difficult
• Downtime depending on DB size and complexity
• Multiple iterations may be required
21
System Conversion-Pros & Cons
S/4 HANA System Conversion

22. Validate Version, Add-ons and Business Functions
Reduce Data Volume
Evaluate Simplification Item Check and fixes
Analyse Custom Code / Remove Waste
Analyse Interfaces
Business Partner Approach - Perform CVI Integration
Adapt mandatory Application settings (Finance & Logistics)
22
System Conversion Preparation – Best Practices
Assessment Workshop
PoC in Sandbox
Best Practice
Recommendations
Housekeeping in
Production
Kellton Recommendation
Start planning in advance

23. 23
How can Kellton Tech Assist in Conversion Preparation?
S/4HANA Assessment & Advisory Service
Discover Analyze Categorize Recommend
SAP Applications
Add-ons & Bolt-Ons
Dependent Non-
SAP Application
Complexity
Dependency
Business Criticality
Conversion Ready
Requires Additional
Preparation
Requires
Transformation
Impact assessment
Indicative Timeline &
Effort
Technical & Application
Readiness
PoC & Roadmap for S/4HANA
Conversion
Best Practices

24. Q & A
24

25. Thank You
For any queries please contact:
Brad.Williams@kelltontech.com
Srinivas.bandi@kelltontech.com
Ramesh.Srinivasan@kelltontech.com