The document outlines the journey of TCS customers moving to SAP HANA, detailing multiple stages involving various appliances and landscapes over several years. It highlights experiences, challenges, and lessons learned throughout the migration process, specifically regarding capacity, replication, and system upgrades. The final landscape includes an ERP S/4 system and SAP BW on HANA, emphasizing the strategic approach taken to adopt this technology.

1. A HANA Journey
Move to TCS Cloud
Darren Mitchell
Senior Platform Architect - SAP COE, TCS

2. 2
Objectives
Overview
TCS customer’s
journey to HANA
Manufacturing company in
Midwest
Progressive in new technology
with planned approach
Multiple steps and a
journey over many
years
Multiple HANA
appliances - Multiple
HANA appliance
vendors
Running on TCS Cloud
with separate DR site -
2014
More applications
running on TCS Cloud,
focus only on HANA
instances

3. 3
Presenter profile
Darren Mitchell
Senior Platform Architect – TCS SAP COE
18 years of SAP experience focusing on SAP Basis
Working in HANA since 2012
Multiple HANA migrations using DMO and export/import options

4. Landscape journey

5. 5
 Financial data was loaded into HANA sidecar so important financial reports could run
 2 system Landscape (Non Prod/Prod) and each have 256GB Memory
 Challenge: Resume replication after ECC QA refresh from Prod Data
 Lesson learning: DMIS version dependency when upgrading HANA SPS revision
 Appliance not able to scale up
2012 Entry into HANA & cloud
LT
SAP Landscape
Transformation
Enterprise HANA
(SideCar)
256G Appliance
(SPS9)
ERP
ECC 6.0
EHP6

6. 6
Next step into HANA, SAP BW 7.40 running on
HANA.
Greenfield approach to migration
License cost were less for BW on HANA than SoH
 5 system Landscape
 Sbx and Dev: 1 TB
 QA:1.5 TB
 Pre-prod: 2TB
 Prod: 3.5 TB
 Challenges: Maintaining one single ECC
source system for 2 reporting target systems
(SQL BW and BW on HANA) until Go-Live
 Lesson learned: HANA DB revising upgrade in
Scale-out Multi node scenario
2014 project
BW/BPC on HANA
NW 740
SAP BW on
HANA
3.5TB Scale Out
(7 node + 1 HA) (SPS9)

7. 7
HANA is database of choice, if possible
Repository for multiple applications
Backend data for Salesforce
 2 system Landscape
 Non Prod: 256 GB
 Prod: 256 GB
2015 Enterprise entry
Enterprise HANA
256G Scale up
(SPS9)

8. 8
DMO approach to move to EHP7 and Suite on HANA
 5 System Landscape
 Sbx, Dev, QA, Pre-Prod, Prod & HA/DR
 Each have 6 TB Memory
 No Scale out option
 Challenges: ECC DB Sizing
 Lesson Learned: CRC check during Migration
2016 – Suite on HANA
ERP
ECC 6.0
EHP7
Suite on HANA
Suite on HANA (DR)
6TB Scale up TDI (SPS9)

9. 9
Move to SoH first to prepare for this step
DMO allows one step move but felt like risks were too
great for one step
 5 System Landscape
 Sbx, Dev, QA, Pre-Prod, Prod & HA/DR
 Each have 6 TB Memory
 Using Sandbox as test field for migration
 S/4 Simple Finance focused
Fall 2016/2017 – S/4
ERP
S/4
Suite on HANA (DR)
S/4
6TB Scale up TDI (SPS9)

10. 10
Final HANA landscape
ERP
S/4
Suite on HANA (DR)
6TB Scale up TDI (SPS9)
Enterprise HANA
256G Scale up
(SPS9)
BW/BPC on HANA
NW 740
SAP BW on
HANA
3.5TB Scale Out
(7 node + 1 HA) (SPS9)

11. Thank You!