Getting SAP Business Suite and BW Ready for HANA
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Getting SAP Business Suite and BW Ready for HANA
AGENDA
Proceed a brief introduction
Rightsizing on the way to HANA
Why it is important
Case Study Business Suite & BW
Q&A
ABOUT PROCEED
We are SAP Data Management Specialists
250+ Customers in the UK
Many FTSE 100 clients
Barclays,Burberry, Capita, GKN, GSK, Kingfisher,
M&S, National Grid, Serco, Vodafone, Severn Trent
A portfolio of Data Management projects in most industries
THE ROAD TO HANA
THE QUESTION IS“DOES SIZE MATTER”
IN THE CASE OF HANA IT DOES
RIGHTSIZING FOR HANA – WHY IT IS IMPORTANT?
Not spending money on appliances that are not needed
Getting the sizing right first time
Migration times
Your best opportunity of getting the business to buy into data management
RIGHTSIZING HANA – WHY IS IT IMPORTANT?
With HANA you get some fantastic compression ratios
1TB of tables in Oracle in HANA 200GB to 150GB depending on which tables
Some tables vanish completely
SAP Note 1872170 shows memory and disk requirements for Business Suite
SAP provides many tools to enable customers to size Hana here is the link to one of them: https://websmp109.sap-ag.de/quicksizer
SAP S/4 HANA massively reduces complexity in IT landscapes
BSEGACDOCA MSEG MARCMaster
Data
MSEG
New
Traditional database SAP HANA platform SAP S/4HANA
593 GB
118.6 GB
42.4 GB
BKPF BSIS BSIK BSET
COBK COEPLFC1 GLT0 COSP
MSTQH MSTEH
MSTBH
MSSQH MSSAHMSPRHMSLBH MSKUH
MSKAH
MKOLH
MCHBH
MARDH
MARCH
MSTQ MSTE
MSTB MSSQ MSSA
MSPR MSLB
MSKU MSKA MKOL
MCHBMKPF MARD
Logistics with aggregates and indexesSAP Simple LogisticsFinance with aggregates and indexesSAP Simple Finance
Simplified data model
Semantically rich data model
Drop performance workarounds
Keep all information
RIGHTSIZING HANA – WHY IS IT IMPORTANT?
We see many large customers with ECC6 systems in excess of 20TB
Talked to a customer recently BW 261TB
It is really important to get your Hana sizing correct
Undersized:
Performance problems
You will need to buy more memory
Oversized:
Waste of Resources
Useful Link:
http://news.sap.com/users-guide-journey-sap-s4hana-six-steps/
RIGHTSIZING FOR HANA – HANA APPLIANCE COSTS
The great news is that Hana appliance costs are coming down all the time
Example prices based on Intel E7 Ivy Bridge processors:
256GB Single-node HANA Appliance from: £32K
512GB Single-node HANA Appliance from: £37K
1TB Single-node HANA Appliance from: £62K
2TB Single-Node HANA Appliance from: £122K
3TB Single-Node HANA Appliance from: £148K
4TB Scale-out Cluster (3+1) HANA from: £363K
8TB Scale-out Cluster (7+1) HANA from: £632K
Then multiply by the landscape you need
DR, PreProd, QA, TST, DEV
RIGHTSIZING FOR HANA – MIGRATION TIMES
Hana needs your data to be Unicode
So if on non Unicode at point of migration you can do conversation
The larger the database the longer migration will take
The more heavily fragmented your source tables the longer it will take
Example CDCLS at 850GB (Cluster Table) from Oracle 11g Heavily fragmented
Unicode 12.2 hours
Non-Unicode 15.1 hours
No fragmentation
Unicode 3.6 hours
Non-Unicode 4.7 hours
Great news! cluster tables go in Hana
One of the Worlds largest brewer
21 Billion euros revenue 2014
1.7 Billion euro profit
165 breweries in over 70 countries
Employ in excess of 90,000 people
CASE STUDY
CASE STUDY
SAP Landscape
In excess of 300 productive SAP Servers
Most on ECC6 and BW 7
Most use Oracle
Looking to rationalise onto smaller number of servers
Hana employed for some BW systems
Looking towards Hana for larger businesses – reasons
Reduction in Hardware Costs
Complexity of landscape
Month end closing issues – takes up to 15 days to close
OUR CHALLENGE – HANA POC ECC6
1st Qtr 2015
Given a copy of one of their larger ECC6 systems – 21TB
System had been running since 1999
No data management done
So in this landscape 1 full copy for DR, Pre Prod, ½ size copies for 2 X QA, Dev and Test
Full suite FI/CO, SD, MM, PP, WM, QM
Given a 1TB Hana box
Told get system into Hana
you have 12 weeks
no reduction in access to data
this had to be a repeatable exercise
RIGHTSIZING FOR HANA
THE ANALOGY↓
Moving from a 5 bedroom house into a luxury studio flat!
January 2015
Analysed the ECC6 system in GB’s
Calculated what this would be on Hana 3.7TB
We needed to get 21TB down to 5.6TB
Table Size
Basis 9,210
Bespoke 232
FI/CO 7,210
LO 421
MM 788
PP 475
QM 27
SD 1,729
Various 648
Total 20,739
RIGHTSIZING HANA – WHAT WE DID
WHAT WE DID
January to February 2015
Installed Open Text Archive Server
Moved 2.2TB of SAP Office to OpenText
Installed SAP ILM using Sybase IQ
Deleted 2.6TB data more than 10 years old
Archived 11.1TB to ILM and moved archive indexes to Sybase
Calculated what was left on ECC6 to Hana 512GB
Migrated data to Hana in 38 hours using Database Migration Option (DMO)
WHAT WE FOUND
Response times on most SAP supplied interactive transactions 50% to 1000% improvement
Some transactions blisteringly fast MB51 before 20 seconds with Hana .2 of a second
Why SAP have rewritten thousands of transactions to optimise for Hana ----- You must test
Custom code a DISASTER transaction A55 before 4.5 seconds with Hana 11.2 seconds
Need to optimise custom code typically the SQL calls + Bad design OR rewrite
We optimised A55 .8 seconds
SAP supplied dialogue programs (what was batch programs) tuned for Hana
WHAT WE FOUND
SAP Fiori – intuitive user experience and a responsive designToday
Functional-based applications
TargetRole-based applications
To: One entry point for the user and a user experience
that follows common design directions
From: Multiple entry points for the user and an inconsistent
user experience
From: One transaction for multiple roles with too
much complex functionality
To: Decomposed apps for each role with simple functions
Disclaimer: This is the current state of planning and may be changed by SAP at any time.
WHAT WE FOUND
Not all users happy with the new interface
See: https://websmp209.sap-ag.de/~sapidb/011000358700000215472013E.pdf
Systems needed thorough testing and users trained in the new interface
Did some further archiving on Hana – 22 times faster than Oracle and we could archive in the production window and no reorganisation's needed of the database.
Also used TDMS to create smaller 256GB systems for QA, TST and DEV
RIGHTSIZING HANA ANALYSIS TOOL
Software to install on the customers ECC6 to provide what if analysis
What can be deleted
What are the easiest tables to archive
What archive objects to use
What is the smallest I can get my database to if I just delete
What is the smallest I can get my database to if I delete and archive
If I have this size Hana device what do I need to delete and or archive
If I just delete the technical tables what size can I get my database to
What sequence to delete and or archive to shrink my database the quickest
Once the customer had decided the best fit for their “rightsize” a blueprint is automatically created on what needs to be completed. This automated process speeds up the analysis phase by up to 80% of doing it the normal way.
RIGHTSIZING HANA ANALYSIS TOOL
RIGHTSIZING HANA ANALYSIS TOOL
22.2 TB
7.9TB Infocubes
9.7TB DataStoreObjects
4.6TB PSA Data
12 Infocubes larger then 200GB
27 DSO’s larger than 200GB
24 PSA tables larger than 200GB
Infocubes held 8 years of data analysed access:
Younger than 24 months 83% access
25 to 36 months 11% access
37 to 50 months 6% access
3.7TB never accessed
CASE STUDY – WE ALSO LOOKED AT BW
WE ALSO LOOKED AT BW
We moved the following to NLS
9.7TB DSO
3.7TB of Infocubes
Total 13TB compressed to 1.4TB in NLS on Sybase IQ
Archived 4.6TB of PSA Data to 800GB of Archive
Reconnected the NLS to Hana
Moved the rest to a 256GB Hana box
PERFORMANCE
On average queries 16 times faster than on Oracle
Query that took 32 seconds down to 2 seconds with Hana
Fastest we saw was 696 seconds before down to 2.3 seconds
Stats using NLS
32 million rows
Without NLS and Hana on Oracle Query time 37 seconds
Split 16 million rows in Hana and 16 million in NLS
Query time from Hana .7 seconds from NLS 1.9 seconds
LESSONS LEARNT
RightSize the source systems first
Look at custom code
Gain experience on HANA – give it to someone who knows what they are doing
If you have BW start with that first
Do some form of POC, to gain knowledge
Its not as simple as a database migration
HANA gives you great flexibility, but it needs looking after – its not easy you need to understand it
Testing and Training needed
Q&A
THANK YOU !
T: +44 (0) 121 629 7830
F: +44 (0) 121 629 7701
W: proceedgroup.com
Proceed Group Headquarters
Regus House
Fort Dunlop
Fort Parkway
Birmingham
B24 9FE
UK
Related Documents
