Embed Size (px)
Citation preview
hellostream 3
hello Kim SimDis-Chem Improves System Health with a Cost-Effective Migration to HANA
Dis-Chem
3
Dis-Chem SAP Timeline…
2009 2012 2013 2014 2015 2016 2017 2018 2019
SAP AIO
including
ERP, WM,
PI and BI
SAP HR
PA, PY
and Leave
SAP BI
on HANA
SAP
EWM
Readsoft SAP CRM
on HANA
SAP F&R
on HANA
BI
Upgrade
on HANA
SAP Org
Mgt
Success
Factors
ERP, EWM,
HR and PI
Migration
to HANA
BEST
Upgrade
SAP
CRM &
F&R
Upgrade
on HANA
SAP C4C
SAP Real
Estate
41 Stores
200968
Stores2012
73 Stores
201384
Stores2014
97 Stores
2015108
Stores2016
129 Stores
2017149
Stores2018 TBC2019
WHAT? - Migrate all non HANA DBs to HANA
WHY? - Needed to invest in new infrastructure & align with SAP roadmap. Also attractive commercial opportunity as a result of previous HANA migration projects. As well as positive commercial impact through the elimination of DB2 license costs on all SAP licenses
HOW? - Considered cloud & on premise options. HEC too costly, therefore decided to go on prem. Considered 2 vendors with different kit & different support service providers
DECISION - First Tech & Epiuse using Hitachi kit – Best commercials and great previous experience with the BI HANA migration as well as the hyperconverged solution which we had implemented in 2016
SCOPE OF PROJECT - EWM, HR, PI, ERP, Print Servers, BOBJ and implemented Fiori & SolMan
PROJECT TIMELINE - Decision end April, 1st Workshop mid May. Project started when kit arrived in June
OTHER - Introduced DNS & had to update all Gui’s to facilitate this project
Extended Warehouse Management
Challenges
24/7 business operation
Performance issues
Growth 500GB/month
Already Unicode system
Used DR instead of TUPS and did test migration, then built QA & Dev from there,
therefore migration was just Prod
Go-Live
Went live in July
12hrs downtime
Conversion from 4TB to 1.2TB, haven’t needed to switch archiving back on yet
Stable and performing
Confirmed Picks | Past 28 Days
9
Human Resources
No major challenges – business driver related to
license benefit through DB2 cost reduction
Smooth migration as already Unicode, and
implementation very standard so testing was limited
Go-Live
Went live in August
Downtime 12hours
System went from 500GB to 200GB
Process Orchestration (PI)
New to all involved parties, no one had implemented PO on HANA before
Business driver related to license benefit through DB2 cost reduction
8 test iterations – lots of housekeeping required before migration
Go-Live
Went live in August
Downtime 1 day
2500 channels switched over, over a 2 week period (stores, partners etc.)
Performance improvement (trickle feed sales)
Experts advised against the migration as they did not believe there would be any technical
benefit as PO is not a DB. Dis-Chem saw great performance benefit
ERP
PREPARATION
Needed to do Unicode conversion
HANA readiness – Relevant for all DB2 migrations, except PO (just a JAVA stack)
EHP Upgrade
Print Servers
Gui Changes
Mail server
GO-LIVE
Went live in September
Cutover was a weekend
6.2TB to less than 3TB
Testing all seemed good, but as soon as volume increased we saw some
issue with purchase orders (around 240 000 pm+/- 7800 PO's per day)
ERP Learnings
We worked with partners and SAP Germany to assist in determining the issue, as this was not experienced
in the Dev or QA environment
Redid all HANA readiness checks twice
Eventually realised it was an availability check issue (volumes)
SAP provided us with a script to change the DB parameters
Had to amend over 900 table parameters to resolve the issue
Deemed by SAP to a known issue - therefore review all notes relating to the version you plan on migrating to,
beforehand
EHP 7 is minimum requirement for moving to HANA. If you are already there, consider going straight to EHP
8 if supported by SAP
ERP Learnings
Performance improvement was realized
Stores reported that they place all category orders
within an hour, this used to take a morning
Response times typically stay under >1000ms on
application
Added additional app servers to EWM & ERP
Bonus Implementations
SOLUTION MANAGER 7.2 – We previously had a syndicated SolMan with our previous provider, so did
not leverage all the benefits
PRINT SERVERS – We previously had 1 shared between ERP and EWM, not dedicated for each
environment (EWM creates around 140 000 spool requests per day)
BOBJ WINDOWS SERVER
FIORI – Implemented a 2 tier environment – enabler to leverage Fiori (on netweaver 7.5) at no cost.
Used as a management tool for real time productivity reporting in the warehouse, leave and payslip
management in pilot
General Lessons Learnt
Housekeeping is Essential – Check your largest tables
and archive or delete as appropriate
Plan your migration approach and don’t be intimidated
by perceived complexity around the set up – look for low
hanging fruit
HANA Readiness checks are critical – allow enough time
to do this thoroughly
DR replication – use for Prod and then used to build Dev
& QA (reduce effort and costs and freeze time)
General Lessons Learnt
Upgrade SAN, need to allow for temp capacity from current provider. Need SUM directories
Need honest and open communication so you can stay solutions focused
Need to consider network bandwidth for most efficient data transfer (we had a 100MB link
shared with other customers)
Test migration is a good estimation of real downtime required to complete prod migration
Overall Benefits Realised
Commercials from new investment &
license reductions
Performance Improvement across our
landscapes
Bonus environments – allowed us to put
building blocks in place to leverage new
technology – business has real-time
reporting – no reliance of batch data loads
Part of the migration to S/4 prepared via
DB migrations
thankyou
