This document provides an overview of migrating an SAP ECC system to SAP S/4HANA. It discusses: - SAP HANA and S/4HANA capabilities like in-memory processing and a simplified data model. - The key steps in the migration approach, which includes upgrading sandbox, development, QA environments before the final production cutover. - Future landscape with the non-HANA systems retired and S/4HANA production the only system. - Tools used like SUM, compatibility views, and approaches to analyze and address custom code for migration.

1. SAP HANA MIGRATION DECK

2. SAP HANA
SAP HANA is a high-performance in-memory
database that accelerates data-driven, real-
time decision-making actions, and sustains
all workloads, with the broadest advanced
analytics on multi-model data, on the premise
and in the cloud.
SAP HANA based applications offer the best
application efficiency by pressing the
execution into the database as feasible. All
the data is kept in the in-memory data source
so the reading data is much quicker as
compared to a conventional database.
www.fts-pl.com

3. SAP HANA - OVERVIEW
KEY HIGHLIGHTS
• In Memory Data Base
• Column Based Tables
• Mass Parallel Processing
• Light weight Application server included in DB
• Code Maintainability, Portability and
easier Transports Management
• Quick setup and run on Cloud/on-premises

4. S4 HANA - OVERVIEW
Internet
of Things
Business
Networks
Social
Networks
People
Devices
Big
Data
SAP Fiori UX
Role-based User Experience for all
devices
SAP S/4HANA Applications and Extensions
Instant insight-driven applications for all lines of business and
industries
SAP HANA Platform
In-memory platform for all
data
On-premise
edition
Cloud
edition

5. SAP S/4 HANA- JOURNEY

6. S4 HANA ADOPTION (1511)

7. Key focus areas in S/4 HANA System
Migration:
• Migration to HANA infrastructure On-Premise or Cloud
• Technical Custom code analysis, fixing
• Business Transformation required in meeting Functional Pre-
requisites and Adopting mandatory Innovations – Major
challenge faced in S/4 Conversion
1. Classic MM-PUR Transactions replacement
2. RFQ Simplified Transaction
3. Co-Deployment of SAP SRM, SAP SLC
4. Subsequent settlements Vendor Rebates
5. Simplified Pricing Data Model
Well addressed through existing SAP & 3rd Party
Tools
1. Rebates Settlement Management – NF
2. Credit Management FIN-FSCM-CR – FC
3. SD Revenue Recognition RAR – FC
4. Data Model changes in SD Pricing
5. Miscellaneous minor deprecation in SD
Area
6. SD Complaints Handing - FC
1. Inventory Management Data
model changes
2. MB Transactions deprecated
3. Material Ledger Activation Impact
on valuation
4. Goods Movement without
exclusive locking
5. New advanced ATP Check –
Summarized requirements
deprecated
6. EHS Deprecated Transactions
7. Extend of usage of ECC WM and
its transition to EWM
1. MRP Live – NF
2. Sub contracting MRP Areas - NF
3. Storage location level MRP deprecated
4. Planning Horizon – NA
5. Line Balancing and Sequencing in ECC
Simplification items to be
considered, which are applicable
for an instance?
• Size & Scale Data points
• Number of Users impacted
• Average number of impacted
transactions
• Security & Authorization changes
required
• Impact on Compliance and Regulatory
reporting
• Needs Business process change?
1. Preparation and Migration of Customizing
for the General Ledger
(FINS_CUST_CONS_CHK)
2. Add-on Financials Closing Cockpit 2.0
instead of CLOCO, CLOCOC, CLOCOS and
CLOCOT
3. Impact of New Asset Accounting
4. New Bank Account master data in place of
Classic House Banks
5. Technical changes in Material Ledger with
Actual costing
6. Activity Based Costing (CO-OM-ABC)
using delta versions not supported. Only
version ‘O’ supported
7. Currency and valuation profile for CO Area
8. Credit Management (FI-AR,CR) to SAP
Credit Management (FIN-FSCM-CR)
Sales & Distribution
Logistics
Production Planning
Procurement
Finance & Controlling
CONSIDERATIONS FOR S4 HANA
1. Business Partner Approach – NF
2. Material Field length extension – NF
3. Foreign Trade Fields in Material Master –
NA
4. MRP Fields in Material Master-Changed
5. Logistics Batch Master MSC1, MSC2 – NA
6. Customer Classification - NA
Master Data

8. User Interface
Layer
Application
Layer
Database
Layer
Classic
Database
SAP HANA
Database
Presentation
Presentation
Orchestration
Calculation Orchestration
Data
Data
Calculation
• Data and Logic execute in DB Layer - Performance thousand times better than normal SQL DB
• Deploying and Developing Real Time Applications and Performing Real Time Analytics
IN MEMORY DATA BASE ADVANTAGES

9. Emp_no Dept_id Hire_data Emp-in Emp_fn
1 1 2001-01-01 Smith Bob
2 1 2002-02-01 Jones Jim
3 1 2002-05-01 Young Sue
4 2 2003-02-01 Stemle Bill
5 2 1999-06-15 Aurora Jack
6 3 2000-08-15 Jung Leura
1 1 2001-01-01 Smith Bob
2 1 2002-02-01 Jones Jim
3 1 2002-05-01 Young Sue
Row-Oriented Database
1 2 3 4 5
1 1 1 2 2
2001-01-
01
2002-02-
01
2002-02-
01
2002-02-
01
2002-02-
01
Column-Oriented Database
COLUMN BASED VS ROW BASED
 In Row Based tables, search will scan all the columns in the tables
 Columns based tables
 No need to scan all the columns as each column stored as Separate file
 Skip unwanted column files and scan required column files in parallel

10. SAP S/4 HANA On-Premise
Get broad functionality and a high-degree of flexibility with a solution designed for
businesses of all sizes, in all industries. Deployed in the data center or a private cloud
environment, SAP S/4HANA offers maximum control for the enterprise business.
• On-Premise Deployment
• Native integration with Line of Business (LoB)
cloud solutions from SAP
• Leverages SAP HANA, in-memory computing
• Intuitive SAP Fiori user experience
S/4 HANA CLOUD AND ON-PREMISE

11. S4 HANA – SYSTEM CONVERSION OPTIONS

12. FTSPL SOLUTION APPROCH

13. The following considerations from Landscape and database have been taken into perspective for suggesting
the solution/approach:
Present System Landscape
• SAP ECC 6.0 for Pharma Business
• Other applications:
• Collabra- for EXIM related documentation
• E-Way Bill & E-Invoicing (TAXPRO)
Modules in Scope for Pharma business
• Finance and Controlling
• Materials Management
• Sales and Distribution
• Quality Management
• SAP-DMS
By considering above points, FT Solutions suggests to migrate ERP Landscape to S4H in single step:
• SAP ECC to S/4HANA Migration
Oracle
11g
HANA
1.0
SOLUTION APPROCH= UNDERSTANDING

14. Benefits
Company wants to change their pharma
business into a SAP S/4HANA system.
Oracle Database, SAP Net Weaver and
application transition in one step.
+ Migration without reimplementation
+ No disruption for existing business processes
+ Re-evaluation of customization
and existing process flows
(SAP GUI) / SAP Fiori
SAP S/4 HANA
SAP GUI
SAP ERP 6.06
Software
Update
Manager
(SUM)
with
Database
Migration
Option
(DMO)
SAP S/4HANA
On-premiseEdition
Rapid Database Migration of SAP
Business Suite to SAP S/4HANA
(all one step migration, including
SAP S/4HANA Finance and SAP
S/4HANA Logistics conversion)
using SUM with DMO
Installation and
migration
What How
SAPS/4HANA SYSTEMCONVERSION PROCEDURE

15. Existing
Landscape
To-Be
S4/HANA
Landscape
S/4HANA
Sandbox
1
Step 1: Upgrade/Migrate
production copy to a S/4HANA
Sandbox
MIGRATION APPROACH –STEP 1
Development
SAP ERP
QA
SAP ERP
Production
SAP ERP

16. Existing
Landscape
To-Be
S4/HANA
Landscape
Development
SAP ERP
Production
SAP ERP
S/4HANA
Sandbox
S/4HANA
Development
S/4HANA
Sandbox
Developme
nt
Step 1:
Upgrade/Migrate
production copy to
a
Step 2:
Upgrade/Migrate
Dev to S/4HANA
MIGRATION APPROACH –STEP 2
QA
SAP ERP

17. Existing
Landscape
To-Be
S4/HANA
Landscape
QA
SAP ERP
Production
SAP ERP
S/4HANA
Sandbox
S/4HANA
Development
S/4HANA
QA
1
Step 1:
Upgrade/Migrate
production copy to a
S/4HANASandbox
Step 2: Upgrade/Migrate
Dev to S/4HANA
Development
Step 3: Upgrade/Migrate QA
to S/4HANA QA –Perform
User Acceptance Tests
2 3
MIGRATION APPROACH –STEP 3
Development
SAP ERP

18. Existing
Landscape
To-Be
S4/HANA
Landscape
Development
SAP ERP
QA
SAP ERP
Production
SAP ERP
S/4HANA
Sandbox
S/4HANA
Development
S/4HANA
QA
1
Step 1:
Upgrade/Migrate
production copy to
a
Step 2:
Upgrade/Migrate
Dev to S/4HANA
Step 3:
Upgrade/Migrate QA
to S/4HANA QA –
Perform
2 3 4
Step 4:
Practice Production
Cutover in Dry Run –
Execute Performance
Tuning
S/4/HANA
D
P
r
o
y
d
R
u
u
c
n
t
i
o
n
S/4HANA
Sandbox
Developme
nt
User Acceptance
Tests
MIGRATION APPROACH –STEP 4

19. Existing
Landscape
To-Be
S4/HANA
Landscape
Development
SAP ERP
QA
SAP ERP
Production
SAP ERP
S/4HANA
Sandbox
S/4HANA
Development
S/4HANA
QA
1
Step 1:
Upgrade/Migrate
production copy to
a S/4HANA
Sandbox
Step 2:
Upgrade/Migrate
Dev to S/4HANA
Development
Step 3:
Upgrade/Migrate QA
to S/4HANA QA –
Perform User
Acceptance Tests
2 3 4
Step 5: Perform
Production
Cutover
MIGRATION APPROACH–STEP 5
s/4 HANA
Dproyrunction

20. MIGRATION APPROACH –FUTURE LANDSCAPE
Existing
Landscape
To-Be
S4/HANA
Landscape
S/4HANA
Sandbox
S/4HANA
Development
S/4HANA
QA
1
Step 1:
Upgrade/Migrate
production copy to
a S/4HANA
Sandbox
Step 2:
Upgrade/Migrate
Dev to S/4HANA
Development
Step 3:
Upgrade/Migrate QA
to S/4HANA QA –
Perform User
Acceptance Tests
2 3 4
Step 5: Perform
Production Cutover
Retire Non-HANA Landscape
S/4HANA
Production

21. SAP GUI
AnyDB / SAP HANA
SAP ERP Core
(SD, MM, LO, FIN, HR…)
(SAP GUI) / SAP Fiori
SAP HANA
SAP S/4HANA Enterprise Mgmt.
(Sales, Service, ProcurementSupply Chain,
Manufacturing, Financials…) 16.10
SAPS/4HANA
On-premise Edition
Innovation
Compatibility
Simplified
Data Model
Application
Innovation
Increased
Throughput …
Stable
Interfaces
Compatibility
Views
SAPS/4HANA SYSTEMCONVERSION PROCEDURE
SAPGUI for
Windows still
available
Technical Change
Semantical Change
SUM
CustomCode
Analysis
Conversion
Pre-Checks
Maintenance
planner
Simplification
List
DMO

22. SAPS/4HANA SYSTEM CONVERSION
SAPGUI for Windows
SAP FIORI is our User Interface Go-To Architecture, but for compatibility reasons SAPGUI for
Windows is still available (for exception see Simplification List).
Compatibility Views
SAP tries to keep migration effort on custom code as low as possible. Compatibility views
allow to keep read access unchanged. Additional tool support to detect custom Code
Adaption effort.
Stable Interfaces
The interfaces to integrate external systems are adapted in a compatible manner. Same
Inbound Data are mapped to new data structure where required. SAP S/4HANA, on-premise
edition, currently supports the existing published legacy interfaces.
Innovation
Compatibility
Simplified
Data Model
Application
Innovation
Increased
Throughput …
Stable
Interfaces
Compatibility
Views

23. Maintenance Planner
The Maintenance Planner checks the system with regards to business functions, industry solutions, and add-ons. If there
is no valid path for the conversion (for example, the add-on is not released yet), the Maintenance Planner prevents the
conversion.
Software Update Manager (SUM) with Database Migration Option (DMO)
The Software Update Manager (SUM) is the SAP tool that is used to update software. It is the main tool used to convert
your system to SAP S/4HANA, on premise edition. If your source system is not yet running on SAP HANA database, use
the database migration option (DMO) of the Software Update Manager to migrate your database to SAP HANA during
the conversion.
Simplification List
To allow our customers a better planning and estimation of their way to S/4HANA, we have created the “Simplification
list”. In this list we are describing in detail on a functional level what happens in S/4HANA to individual transactions and
solution capabilities. If some transactions or capabilities are falling away, this does not mean that we are
decommissioning functionality, but that we have merged this functionality with other elements or reflected it within a new
solution / architecture.
Pre-Checks
Pre-checks are shipped as SAP Notes to customers that want to convert to S/4HANA . Customers can use these pre-
checks to find out what mandatory steps they have to carry out before converting to S/4HANA. The results list the
instances that need addressing before attempting the conversion process. The checks are run twice again during the
conversion process: both times in the Software Update Manager (SUM). The conversion is stopped if errors persist.
Custom Code Checks
These checks are based on the Simplification list concept. S/4HANA simplifies business processes. Before converting to
S/4HANA, you need to check your custom code against the S/4HANA simplifications. These simplifications are loaded
into the Custom Code Check Tool. After you run the tool, you obtain a list of instances where your custom code does not
comply with the scope and data structure of SAP S/4HANA 1610, on-premise edition.
Technical Procedure
& Semantic Adaption
SAPS/4HANA SYSTEM CONVERSION
Technical Change
Semantical Change
SUM
CustomCode
Analysis
Conversion Pre-
Checks
Maintenance
planner
Simplification
List
DMO

24. Pattern 1:
Activity before migration
+ downtime
Pattern 2:
Activity before or after
migration
Pattern 3:
Activity after migration
Inventory valuation not supported in SAP S/4HANA. Switch to material
ledger can be done before migration (activation of ML supported via
dedicated report) During downtime ML migration to newlogic.
Material Ledger
BOM-
Determination
MM-IM
Simplification of
MRPareas
One logic for all storage location MRP-Logic. In case of using such
logic, program needed to create missing MRP-areas and MRP-File
before running MRP in SAP S/4HANA
Conversion of IM-Tables (MSEG) into new MATDOC
One Logic for BOM-Determination only via production version.
Conversion to new logic via report possible before and after
migration possible, has to run before starting MRP in SAP S/4HANA
Pattern 4: Technical
migration
Example – Activities during the different phases in logistics
SAPS/4HANA SYSTEM CONVERSION

25. BSEG COEP
BSID COSS COSP
BSEG COEP FAGLFLEXA
ACDOCA
BSID_BCK COSS_BAK COSP_BAK
COSS
COSP
BSID
BSEG COEP FAGLFLEXA
BSID_BCK COSS_BAK COSP_BAK
ACDOCA
BSID
COSP
COSS
Technical Upgrade
Persistency layout is prepared
during technical upgrade.
- Rename TotalsTables
- CreateACDOCA
- Create Compatibility Views
Data-Migration
Line Items are merged into the new
Universal Journal (ACDOCA).
Runtime: depends on table size
Line items tables
Index and totals tables
FAGLFLEXA
Merge
SAP S/4HANA SYSTEM CONVERSION

26. SAPS/4HANA MIGRATION PROCESS

27. CUSTOMCODEMIGRATION PROCESS

28. CUSTOMCODEMIGRATION PROCESS
Step 1: Custom Code Evaluation

29. CUSTOMCODEMIGRATION PROCESS
Step 2: Code Inspector Checksfor SAP HANA

30. Step 3: SAPS/4HANA Custom Code Analysis Process
CUSTOMCODEMIGRATION PROCESS

31. Step 4: Functional Adaptation
CUSTOMCODEMIGRATION PROCESS

32. CUSTOMCODEMIGRATION PROCESS
Step 5: Performance Tuning using SQL Monitoring

33. SOLUTION APPROACH:SAP FIORI
• Installation & Configuration of SAP FIORI Landscape
(DEV,QAS, PRD)
• Installation of New FIORI Landscape on New Servers
• Update of Stack to latest Patch Levels
• Perform Initial Setup Activities and configure backend systems
• Deploy patches required for Standard Fiori Apps
• Deployment of Standard Fiori Apps
• Install & Configure Web Dispatcher for accessing Fiori Apps
FT Solutions suggests the following approach for Installation of SAP FIORI
Landscape:

34. PROJECT PRE-REQUISITES
The following are the technical requirements for the project’s execution:
Valid SAP Support License
• Valid SAP Router registered with SAP
• Required SAP Media to be provided
• OS Level, Hardware and Network Support as and when required in
the phases of the Project
• Offshore connectivity to FTSPL premises
Test Servers
• Requires Test Servers for ERP and DMS with configuration equal to that of
existing PRD and a Test HANA Server.
• All the Test Servers should be provided with Tape/Share for taking
Database Backups as and when required .
New Servers
• HANA Appliances for all the SAP ERP Instances
• New Application Servers for all Servers

35. PROJECT DOCUMENTS DELIVERED
The following are the Documents that will be delivered as part of Scope:
• Migration Documents
o S4H Migration Document for SAP ERP PRD Instance
o SAP ERP QAS Refresh Activity using HANA DB Backup / Restore
• Solution Manager Documents
o Installation or Renewal of SAP Router
o Installation and SPS Update of Solution Manager
o Initial and Basic Configuration of Solution Manager
o End User Manuals for Accessing Maintenance Optimizer
and Early Watch Alert
• Installation Documents
o Installation of SAP FIORI PRD on Linux and Sybase
o End User Manuals for Accessing FIORI Apps

36. SAP FIORI OVERWISE

37. SAP FIORI APPLICATION - WHAT IS SAP FIORI?
• Fiori is a New User Experience (UX) for SAP
• Standard Set of Apps delivered in S4 HANA
• Deployable on Cloud and On-Premise
• Offers Single Entry Point for end users using
Multiple Devices
• Fiori Apps are highly Secured

38. KEY BENEFITS OF SAP FIORI
01 02 03 04
Increase productivity Improve Time to Value Lower Risk Reduce TCO
 Employees are able to get
the job done Anytime,
Anywhere
 Managers can streamline
Processes, impact Business
Results
 Additional features
(example: mass approvals)
to accelerate handling
.
 Faster implementation
 Predictable
implementation timeline
 Better Quality
Assurance
 Standards-based, flexible
Software Framework
 Instant roll out
capabilities to different
devices
.
 Implementation aligned to
business value and
feasibility
 Supportability by SAP
 SAP validated and tested
 Future-proof
investment
 Continuous
innovation
 Reduce
customization and
integration complexity via
SAP Fiori toolkit and rapid-
deployment offerings
 Lower maintenance
costs
 Reuse of skill sets
 Intuitive usage significantly
reduces learning effort and
cost
Improving customer’s user experience

39. NEW
UX Design Services
RENEW ENABLE
Usage/reach
New Applications Existing Applications
SAP Fiori
UX
Role Based Responsive Simple Coherent Delightful
Designed for you ,
your needs and how
you work
Supports how and
where you work at
any time
Focuses on what’s
important
Provides one fluid,
intuitive experience
Makes an emotional
Connection
SAP FIORI - UX STRATEGY AND ADVANTAGES

40. Analytical
Insight to Action
Visual overview over a complex topic
for monitoring or tracking purposes
Transactional
Task-based Access
Access to tasks like change, create, or
entire processes with guided navigation
Fact Sheet & Contextual
Navigation
Search and Explore
View on essential information about an
object and contextual navigation
between related objects
Runs on any
DB and
HANA
Runs on
HANA
SAP FIORI APPLICATIONS – CLASSIFICATION

41. FIORI ARCHITECTURE

42. Web-based entry point for SAP business applications across platforms and
devices
• The FIORI Launchpad provides end- users an entry
point to Fiori applications in a role-based, consistent
and user-friendly manner using tiles.
• Tiles show dynamic/live/real-time application
information (like status, KPIs) on the home page.
• Tiles can be selected from catalogs and arranged in
groups.
• Search is integrated.
SAP FIORILAUNCHPAD

43. MM FIORI APP –PURCHASE ORDER (CREATE AND RELEASE)

44. SD FIORI APPS - LAUNCHPAD ON MOBILE VIEW

45. FTSPL Active Methodology for S/4 HANA tailored specifically to accelerate and simplify the adoption of SAP S/4
HANA.
Processes delivered with FTSPL Active Best Practices support core industry requirements and manage Multiple
Geographies, Subsidiaries, Country specific Requirements.
All the Best Practices are pre-Configured and are ready to use for Complex Implementations within short
time.
FTSPL Active Methodology uses SAP Activate and Solution Manager 7.2 for pre-configuration and preliminary
requirements for S/4 HANA Implementation.
Our Solution can be adopted as Agile methodology for All Enhancements.
Benefits to Customer:
• Predefined templates, objects and best practices available in a guided process
• Achieving Faster TIME TO VALUE and reduced COST of Implementation
FTSPL ACTIVE – IMPLEMENTATION FOR SAP S/4 HANA

46. SAP ECC VS SAP S/4 HANA DIFFERENTIATORS
SAP Business Suite
• SAP GUI
• SAP ERP Core
• Any DB/ SAP HANA
• Output Management via NAST
• Material Number Field Length max. 18 Char
• Material Ledger activation optional
• The Storage Location functionality is a subset of
the MRP Area Capabilities
• Customer / Vendor Master ID are separate
transactions
• Cost Elements are two types: Primary and
Secondary Elements
• Generates FI and CO documents
• Credit Management via Sales & Distribution
• Rebate management is in Place
S/4 HANA 1610
• SAP GUI/ SAP Fiori End User Experience
• SAP S/4 HANA Enterprise Management
• SAP HANA
• A New Output Management approach is in Place
• Material Number Field Length Extension up to 40 Char
• Material Ledger Activation Mandatory
• Storage location MRP is not available
• Business Partner ID and Customer / Vendor Master ID
and transactions are combined into new Business
Partner transaction "BP"
• Cost Elements are only one type i.e., Primary Cost
Element
• Generates Single Universal Document
• Credit management via FSCM
• Rebate management is replaced by settlement
management

47. Start with executable
content
Verify solution
scenarios meeting
business needs
Tailor solution in short
time boxed sprints
Template Presentation
to stakeholders
Determination of
solution, scope and
value
Implementation Plan
SAP S/4 HANA
Solution Validation
Gap identification
and Closure
Determination
of config
values
Approval of release
& plan
Configuration
T
esting
Data
migration
Solution walkthrough
Support for
Production
In Production
Cut over
Organizational &
Production readiness
Prepare Explore Realize Deploy
FTSPL ACTIVE - IMPLEMENTATION PROCESS
Cutover and begin
productive use

48. Benefits Of
Migrating To SAP
HANA
With SAP HANA your organization is much better equipped to handle, and even
go beyond, the Big Data trend. Not only will you be able to process a far greater
volume of data, but, thanks to changes in the way it’s stored and accessed,
you’ll also be able to make use of a much wider range of data.
The Power to Handle Bigger Data
Real-Time Analytic Capability
If your organization has a need for up-to-the-moment information or processes
reports that take a long time to generate, SAP HANA can undoubtedly help
you.
In-memory technology means you’ll waste no time loading data from one
location to another, and we’ve seen basic HANA setups process data up to
10-times faster. This drastically reduces the amount of time needed to perform
even the most comprehensive of reports.
Flexibility and Versatility
One of the greatest benefits of SAP HANA is its compatibility with other
databases, hardware and software, making it one of the most versatile data
solutions available. This means your team can achieve greater analytic
capabilities, without giving up the interfaces they trust.
This also means you’re able to apply these new analytic capabilities across
your old systems, allowing you to derive new insights and rethink old
assumptions based on misleading data.

49. Delivering business innovation to.

50. Any questions?
You can find me at:
Glad to assist you with our solutions to improve
ROI and TOO on your SAP Investment
You can reach me at +91 9029523775 or
navinsingh@fts-pl.com