Top Banner
PUBLIC Sizing for SAP S/4HANA and SAP S/4HANA Cloud CAA303
89

CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

Dec 04, 2021

Download

Documents

dariahiddleston
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
Page 1: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

PUBLIC

Sizing forSAP S/4HANA and SAP S/4HANA CloudCAA303

Page 2: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

2PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Speakers

Las VegasSeptember 24–27, 2019

Detlef Thoms

BarcelonaOctober 8-10, 2019

Sebastian Schmitt

BangaloreNovember 13-15, 2019

Sukshatha Rao

Page 3: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

3PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Download the app from iPhone App Store or Google Play.

Take the session survey.We want to hear from you!

Complete the session evaluation for this session CAA303 on the SAP TechEd mobile app.

Page 4: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

4PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related document, or to develop or release any functionality mentioned therein.This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross negligence.All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

Disclaimer

Page 5: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

5PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing introduction and basics

Sizing tools

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud Greenfield Migration Deployment options

Agenda

Page 6: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

6PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing introduction and basics

Sizing tools

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud Greenfield Migration Deployment options

Agenda

Page 7: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

7PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Performance requirements: SizingSizing-relevant KPIs (Key Performance Indicators)

From a customer perspective, sizing is the translation of business requirements (business throughput and user concurrency requirements) into hardware requirements.

From a development standpoint, sizing refers to the creation of a sizing model for the product functionality with a reasonable number of input parameters and assumptions. The goal is to define a sizing guidance for each SAP application.

The sizing procedure helps customers determine the resources (CPU, memory, data growth on disk, disk I/O and frontend network) required by an application within the customer's business context. For on premise applications the sizing procedure is publicly available.

Sizing is not configuration: Actual system configuration is a task performed by the hardware vendor who must ensure the system landscape meets the hardware requirements determined by sizing.

Page 8: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

8PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Universally applicable statements on sizing

20% of the transactions and scenarios create 80% of the load“Reliable sizing can only be done with Scalable application software Scalable hardware Meaningful and nearly complete volume

throughput or active user information

Landscaping and configuration are related, but are separate tasks“

Page 9: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

9PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Ensuring scalability with performance tests – Approaches

– Small test system – (QA, development), one user

– Equivalent to multi-user test, stress test, load test, benchmark

– Quality and implications of accesses to persistence layer

– Linear resource consumption– Parallel processing mechanisms, load

balancing– Memory usage and memory leaks– Disk requirements– Front-end network load

Analyze & measurescalable behavior

Performance predictionsfor high volume environment

Verify assumptions

Single user test

Multi user test (Volume)

Page 10: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

10PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP HANA sizing KPIs

Different sizing approach: SAP HANA sizing vs. sizing of traditional DB

Memory is the leading driver for SAP HANA sizing

Massive parallelization in analytical scenarios will have an influence on Response Times; hence CPU requirement will get more important for analytical scenarios

Mixed transactional and analytic workloads now possible with SAP HANA but compete for shared resources

Disk is required for data persistence and for logging data Sufficient I/O performance required to enable processes to run

with acceptable data throughput and storage system latency.

Disk sizeDisk I/O

Compared to anyDB, more CPU power is required to fully benefit from the parallel processing capabilities of SAP HANA for optimal response times

CPU

Memory sizing depends on the data footprint in SAP HANA (business and meta data in column and row store) Memory is also used by other components (e.g. SAP HANA

caches) and for processing of requests

Memory

Network sizing typically focuses on the bandwidth and is described in gigabits per second (gbps)

Front-endNetwork Load

Page 11: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

11PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Different types of sizing

Hardware budget sizing

Smaller companies Very simple algorithms Assumptions, likelihoods Level setting of project Risk identification

Advanced sizing

Medium to large companies Throughput estimates Questionnaires, formulas Usage of standard tools and

guidelines Focus on core business

processes

Re- / Delta / Upgrade / Migration sizing All projects SAP system monitors and statistics Goal: Extend an existing system by load / function Examples− Re-Sizing: Customer wants to add 100 additional users who'll do the same

as the current productive ones− Delta Sizing: Customer is live with SAP S/4HANA and wants to add EWM− Upgrade Sizing: Customer plans to upgrade to latest EhP− Migration Sizing: Customer want to migrate from ECC to SAP S/4HANA

Expert sizing

Large or complex projects Additional guidelines Custom calculations Analysis of custom

coding Custom sizing guidelines

Page 12: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

12PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Three-party collaboration model

Contributions Certified benchmarks

scalable hardware Different configurations

together with technology partners

Service level agreements Final responsibility for

sizing at customer site if conducted by them

Expectations from benchmarking and sizing Optimal performance Suggestion for HW config.

Contributions Response time

requirements Throughput requirements Provides business input

Contributions Development and provision

of benchmark toolkits Regression testing for new

releases Standard sizing guidelines Sizing verification

processes

Hardware vendors Customer

SAP

Sizing Recommendation CPU (SAPS) Memory (GB) Database space (GB) Disk I/O operations per sec Frontend bandwidth mbps

Sizing is the joint responsibility of customer (LoB), SAP and HW Vendor.

They have to make sure that SAP software runs smoothly at customer site and that customers don’t run into performance or TCO issues due to under-sized or over-sized HW.Examples: Custom coding Different businesses require

different sizings Different applications need

different amounts of CPUs Additional needs might come from

additional not sized usages

Page 13: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

13PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Common factors that influence sizing

HW Platform Processor

technology Disk technology Network technology System infrastructure

SAP Software Release OLTP or OLAP Industry solutions

LEGEND: Responsibility of: Technology Partner | SAP | Customer

Customizing Business process design Set up of business

processes Organizational structures

Customer Profile

System Settings Parameterization Interfaces Security settings Unicode

Customer Coding, 3rd Party Performance impact Scalability Business process design

Document Volume Time for volume

processing Background processing,

parallel jobs Reporting Load from external

systems

User Behavior Concurrency LAN/WAN Internet/intranet Activity, e.g.

− *-Search− Efficient navigation

Reporting

Business & Data Growth Avoiding data Archiving strategies Information Lifecycle

Management New functionality Mergers and acquisitions

Page 14: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

14PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Risks in a sizing project

Challenge to obtain sufficient usage information as sizing input

Often caused by communication issues Insufficient sizing input is compensated by assumptions,

which should be documented

INCOMPLETE INPUT DATA

While it is perfectly ok to work with assumptions you must ensure that a verification process is included in the project plan

ASSUMPTIONS ARE NOT VERIFIED

Are very hard to predict: Make sure there is a verification process Make sizing measurements, if required

CUSTOM CODING & SPECIAL DATA CONSTELLATIONS

Ris

ks in

a S

izin

g Pr

ojec

t

Page 15: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

15PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Page 16: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

16PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing introduction and basics

Sizing tools

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud Greenfield Migration Deployment options

Agenda

Page 17: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

17PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Official SAP sizing page: www.sap.com/sizing

Guidelines Access sizing guidelines Access sizing-related materials

Tools Access quick sizer * Sizing decision tree Others

Training opportunities

FAQs

* Requires login credentials

Page 18: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

18PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Initial calculation methodEducated guess

Questionnaire without formulasFor structured questions

T-Shirt sizingSimple algorithms with many assumptions

FormulasSimple or more complex

Standard sizing methods and tools

Quick sizerSupports user-based and throughput-based sizing

Page 19: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

19PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Example: Quick Sizer, SAP’s online sizing Tool

Structured sizing questionnaires Input for

– Greenfield sizing– GoingLive Check

Hardware vendor contact list

Available online since 1996 New Special Quick Sizer version for SAP S/4HANA Cloud SAP HANA Quick Sizer version available since 09/2014 Free of charge As of 2016: avg. 35,000 new projects per year

Characteristics

Facts and Figures

Scope SAP Key applications

– SAP S/4HANA– SAP HANA Standalone– SAP BW/4HANA– etc.

Sizing by users and/or by throughput

Page 20: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

20PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

4

3

2

1

Sizing and configuration

Check the list of certified AnyDB or SAP HANAhardware to see which hardware providers offer hardware configurations that match the sizing result.

Provide the sizing result (or the Quick Sizer project number) to the hardware vendor and get proposal for appropriate hardware configuration and prices.

The Quick Sizer tool calculates the sizing result (memory, disk space and disk I/O, and CPU) based on the input

Create a Quick Sizer project and provide input on the business usage/requirements of the customer into the Quick Sizer project.

SIZING

CONFIGURATION

Page 21: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

21PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing introduction and basics

Sizing tools

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud Greenfield Migration Deployment options

Agenda

Page 22: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

DemoQuick Sizer

Page 23: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

23PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Two different/separate sizing strategies with different goals

Advantages Users are relatively easy to

determine Memory is driven by user contexts

Challenges Define “user” Determine user load patterns Sizing DB growth by users

Sizing by Users Sizing by Throughput

Advantages Scenario, transaction Based on actual business objects

and scenarios Peak/average sizing

Challenges Obtaining the right figures

Page 24: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

24PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing introduction and basics

Sizing tools

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud Greenfield Migration Deployment options

Agenda

Page 25: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

25PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP HANA sizing

Customer interested in SAP HANA

New SAP HANA system(Greenfield sizing)

Existing SAP system migrated to SAP HANA(Migration sizing)

Use SAP HANA Quick Sizer(www.sap.com/sizing)

Use Migration reports/ procedure(Notes: 1872170, 1793345, 2296290)

Find deployment options: Connect with hardware vendor and check for

configuration

Certified and Supported SAP HANA® Hardware Directory

Link:

Page 26: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

26PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing introduction and basics

Sizing tools

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud Greenfield Migration Deployment options

Agenda

Page 27: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

27PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Methodology and sizing result• Structured questionnaires for key

SAP applications • Sizing results given in SAPS (CPU),

GB (Memory and disk) and disk I/O • Optional: Memory for persistent

Memory (NVRAM)

Greenfield sizing

New SAP HANA system (Greenfield sizing)

Use Quick Sizer• SAP HANA version• SAP S/4HANA Cloud version

Sizing guidelines Expert sizing for SAP HANA native

Services

• Request MAXAttention Service or Sizing Service from Consulting

Sizing document• Overview about architecture and

functionalities for selected business scenarios

• Sizing results given as T-Shirt categories in SAPS (CPU) and GB (Memory & disk)

Page 28: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

Quick Sizer – SAP HANA versionspecial features

Page 29: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

29PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Quick Sizer – special featuresData Aging in SAP HANA Quick Sizer

There are two residence periods. One for memory (aging period) and one for disk (archiving period).

There are aging objects available, if the aging column (residence time in memory) is changeable. Per default the aging period has been set to 24 months. There are no aging objects available, if aging column (residence time in memory) is empty and highlighted in

blue.

Introduction of ‘What if analysis for the retention times (disk/memory)’

Page 30: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

30PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Example what-if analysis data aging

Option 1: SAP HANA memory result – 4,2 TB for SAP S/4HANA server (24 month residence time in memory)

Option 2: SAP HANA memory result – 8,9 TB for SAP S/4HANA server (no data aging)

Page 31: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

31PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP HANA requires adequate I/O performance to support processes such as: Savepoint writing Delta merges Database startup times

Storage systems running with SAP HANA must provide sufficient I/O performance to enable processes to run with acceptable data throughput and storage system latency.

The calculation of the disk I/O requirements with the SAP HANA Quick Sizer is now possible.

SAP HANA Quick Sizer – special features SAP HANA Disk I/O

Page 32: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

32PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP HANA Quick Sizer – special featuresSAP HANA disk and memory areas – Overall picture

Working Memory DRAM

Persistent Memory(NVRAM)

Row Store

Column Store Delta segment

Column Store (Column Loadable Main)

NSE + Hybrid LOBs caches

Column Store (Column Loadable Main)

NSE + Hybrid LOBs

Memory Data

Unloaded columnsLOG

Storage

Row Store

Page 33: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

33PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

What is Persistent Memory: Persistent memory (non-volatile RAM, also referred to as Storage Class Memory) is supported in SAP HANA as a persistent storage type.

Persistent memory (or NVRAM) is an emerging class of memory which combines the qualities of both DRAM and Flash storage and bridges the gap between disk storage and main memory.

Market launch depends on hardware roadmap– SAP HANA-servers with Intel Cascade Lake CPUs

Calculation:Persistent Memory: Amount of memory required for the column store dataDRAM: Total SAP HANA Memory – Persistent memory

SAP HANA Quick Sizer – special featuresPersistent memory

Page 34: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

34PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP HANA Quick Sizer – special featuresSAP S/4HANA Embedded Analytics sizing has been implemented in the SAP HANA Quick Sizer

Greenfield for new small systems

Greenfield for new large systems

Brownfield for new small systems

Brownfield for new large systems

Page 35: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

35PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Quick Sizer – special featuresSizing SAP S/4HANA Embedded Analytics - Greenfield

If the limit of 500 million table lines is exceeded, you’ll get an error message:

You have the chance to define the query response times and the degree of parallelization by setting assumptions.

Refer to the following SAP Note:• 2815376 - Greenfield sizing for SAP

S/4HANA embedded analytics

In this case, you can conduct an SAP S/4HANA embedded analytics sizing with table 2. Quick Sizer is not calculating with fix response times and parallelization degrees

Quick Sizer will calculate a result, if the limit of 500 million table lines in the biggest table is not exceeded!

Page 36: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

36PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Quick Sizer – special featuresSizing SAP S/4HANA Embedded Analytics - Brownfield

If the limit of 500 million table lines is exceeded, you’ll get an error message:

You have the chance to define the query response times, degree of parallelization and the memory per query by setting

assumptions. to conduct own measurements (expert sizing). By measuring the memory per query, response times and

calculating the parallelization degree, you can enter the measured values into table 2.

Refer to the following SAP Note:• 2813738 - Brownfield sizing for SAP

S/4HANA embedded analytics

In this case, you can conduct an SAP S/4HANA embedded analytics sizing with table 2.

Quick Sizer will calculate a result, if the limit of 500 million table lines in the biggest table is not exceeded!

Page 37: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

37PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Steps for an expert sizing

Activity

Identify the most important queries/apps

1b Identify, how they will be used, e.g. filter criteria, authorizations and how often they will be executed

Run these queries on representative test data (ideally on a recent copy of the production data)• Quality of test data• Quantity of test data

Measure resource consumption (CPU/Memory) and response times and calculate the degree of parallelization

Perform a forecast calculation based on the expected usage of the queries/apps

Decide whether optimizations are necessary and if yes analyze and optimize expensive queries and retest

2

1

3

4

5

1b

Page 38: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

38PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Measure resource consumption (CPU/Memory) and response times and calculate the degree of parallelizationDB Response Time = 4 secDB CPU Time = 20 sec

Avg. DoP = 5

Memory per second runtime = 500 MB

𝑨𝑨𝑨𝑨𝑨𝑨.𝑫𝑫𝑫𝑫𝑨𝑨𝑫𝑫𝑫𝑫𝑫𝑫 𝒐𝒐𝒐𝒐 𝒑𝒑𝒑𝒑𝑫𝑫𝒑𝒑𝒑𝒑𝒑𝒑𝑫𝑫𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒑𝒐𝒐𝒑𝒑 =𝐃𝐃𝐃𝐃 𝑪𝑪𝑪𝑪𝑪𝑪 𝒑𝒑𝒑𝒑𝒕𝒕𝑫𝑫 𝒐𝒐𝒐𝒐 𝒑𝒑 𝑸𝑸𝑸𝑸𝑫𝑫𝑫𝑫𝑸𝑸

𝐃𝐃𝐃𝐃 𝑹𝑹𝑫𝑫𝑹𝑹𝒑𝒑𝒐𝒐𝒑𝒑𝑹𝑹𝑫𝑫 𝒑𝒑𝒑𝒑𝒕𝒕𝑫𝑫 𝒐𝒐𝒐𝒐 𝒑𝒑 𝑸𝑸𝑸𝑸𝑫𝑫𝑫𝑫𝑸𝑸

Identify, how they will be used, e.g. filter criteria, authorizations and how often they will be executedNumber of concurrent users = 216Executions per hour per user = 50

Executions per sec per user = 3Avg. number of parallel queries per sec = 12

Queries_per_sec = Number of users per user type * Time spent on each query * # queries per hour per user type /3600= 216 * 100% * 50 / 3600= 3

Avg. number of parallel queries per sec= Executions per sec per user * DB Runtime = 3 * 4 = 12

Page 39: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

39PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Perform a forecast calculation based on the expected usage of the queries/apps

Required Number of Threads = Avg. number of parallel queries * Avg. Degree of Parallelization

= 12 * 5= 60

Required Memory = Avg. number of parallel queries * (Response_Time * Memory per second runtime / 2)= 12 * (4 * 500/ 2)= 12000 MB

Page 40: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

40PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Example

Snapshot

x x x 1x x x 2x x x 3

x x 4x x 5x x 6

x 7x 8x 9

101112

3 3 3 3 32 2 2 2 21 1 1 1 13 3 3 3 3 33 3 3 3 3 32 2 2 2 2 22 2 2 2 2 21 1 1 1 1 11 1 1 1 1 13 3 3 3 3 3 33 3 3 3 3 3 33 3 3 3 3 3 3

3 2 2 2 2 2 2 22 2 2 2 2 2 2 21 2 2 2 2 2 2 23 1 1 1 1 1 1 13 1 1 1 1 1 1 12 1 1 1 1 1 1 12 3 3 3 3 3 3 3 31 3 3 3 3 3 3 3 31 3 3 3 3 3 3 3 3

3 3 3 3 3 3 3 3 3 32 3 2 2 2 2 2 2 2 21 3 2 2 2 2 2 2 2 23 2 2 2 2 2 2 2 2 23 2 2 2 2 2 2 2 2 22 2 1 1 1 1 1 1 1 1

3 2 1 1 1 1 1 1 1 1 12 1 1 1 1 1 1 1 1 1 11 1 1 1 1 1 1 1 1 1 1

UserNumber of concurrent users 216Exec per hour per user 50Exec per hour 10800Exec per sec 3Avg. number of parallel queries per sec 12QueryDB Response Time 4DB CPU Time 20Avg. Degree of Parallelization 5MB per second runtime 500

Page 41: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

Quick Sizer – SAP S/4HANA Cloud version special features

Page 42: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

42PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing for SAP S/4HANA Cloud – Why?

SAP S/4HANA

Cloud Pricing

User Metric

SAP HANA Memory

Page 43: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

43PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Since June 2018, there is a new Quick Sizer for SAP S/4HANA Cloud available

The tool can be used for SAP S/4HANA Cloud greenfield sizings

Main Characteristics of the Cloud Quick Sizer Simplified UI Streamlined Input Navigation Tree (scope items) Documentation in the SAP Help Portal Only two sizing KPI’s (SAP HANA RAM for Business

data & Frontend Network Load) Sizing of API calls

Sizing SAP S/4HANA Cloud Quick Sizer

Page 44: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

44PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP S/4HANA Cloud QS significantly easier than SAP HANA – QSStructure

Page 45: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

45PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP S/4HANA Cloud QS significantly easier than SAP HANA – QSResults

Page 46: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

46PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing introduction and basics

Sizing tools

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud Greenfield Migration Deployment options

Agenda

Page 47: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

47PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Migration sizing Part 1/2Existing NW ABAP system to be

migrated to SAP HANA

SAP Notes 1872170; 1793345

SAP S/4HANA SAP BW/4HANA

SAP Note 2296290

Back to Overview

Methodology and result• Sizing report (note 1872170) which runs on the „legacy“ (anyDB,

anyOS) ABAP system to determine the required SAP HANA RAM and disk on the new HANA-based solution

• Potential areas for housekeeping, cleanup and archiving• Report /SDF/HDB_SIZING (Modification 77) contains enhancement

for persistent memory sizing• CPU sizing: Will be included in the sizing report (type ful in transaction

box). Recommendation: Double-check result with method as described in SAP Note 1793345

Methodology and result• Sizing report (note 229690) which runs on the source BW

ABAP system to determine the required SAP HANA RAM and disk.

• Potential areas for housekeeping, cleanup and archiving• In addition, a SAP HANA CPU requirement assessment is

included • Persistent Memory sizing will be available soon

Page 48: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

48PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing report for SAP S/4HANA

Report /SDF/HDB_SIZING Described in SAP Note 1872170 – Suite on HANA sizing report

Scope Runs on SAP_BASIS 620 and higher Is suitable for sizing of all business suite products (ERP, CRM, SCM, SRM, etc.) Not suitable for BW (Refer to SAP Note 2296290 – New Sizing Report for SAP BW/4HANA)

Functionality Considers SAP S/4HANA data model changes in FI, SD, MM, ML, etc. Estimates the maximum memory consumption of the database, if migrated to SAP HANA Is independent of the source database provider Considers distribution of tables to row and column store Considers differences for secondary indexes Considers compression of legacy database Considers data aging for technical objects

Page 49: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

49PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Results of sizing report /SDF/HDB_SIZING

The sizing report includes the sizing projections, based on the actual table sizes in the legacy system as well as an estimation of how much the memory footprint can be reduced using functionalities that SAP HANA will enable.

Page 50: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

50PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

How to interpret the results of the SAP S/4HANA sizing report

Column store and row store estimations have good enough accuracy (10-20%). Still, do not forget it is an estimation. Work Space (temporary memory) estimation uses a simple formula (data size in memory) * 2. Based on

experiences, if the work space is bigger than 3TB, it might be oversized. Always check the top tables. Very often, you will find basis tables with deletion/archiving potential such as

idoc, workflow, application log tables, etc. See SAP Note 706478 – “Preventing Basis tables from increasing considerably” for more details. The total estimated memory requirement given by the report should not be considered as the final memory

sizing result. Take into account that:– Not all the server physical memory will be available to SAP HANA (OS and other processes are run too). – There should be enough space left for future data growth or functional extension The sizing report takes a snapshot. Any growth between that date and the go-live date should be considered.

Page 51: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

51PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

The sizing report /SDF/SAP HANA_BW_SIZING is a convenient method to estimate the memory requirements of a BW system after migration to SAP HANA. Major advantages of the ABAP report: Easy to deploy and use – no DB administrator required Independent of source database specific compression and data representation Considers user defined future growth and leverages BW semantic information

The report requires ST-PI 2008_1_7xx SP12 or ST-PI 740 SP1 and SAP NetWeaver BW 7.0 SP 4 or higher. Updated versions can be obtained from SAP Note 2296290. Important note for DB2 on iSeries (AS/400): Please implement SAP Note 1677958!

Sizing report for SAP BW/4HANA

Mission statementProvide an easy to use, source database independent tool to predict resource requirements for a BW system on an SAP HANA database.

Page 52: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

52PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Introduced with version 2.5 of sizing report/Tailored Datacenter Integration (TDI) Phase 5 This is not a CPU sizing! Configuration space for SAP HANA hardware opened up to allow for more flexibility in combining memory

and CPU resources by introducing CPU requirements classes SAP BW/4HANA sizing report enhanced by analysis process looking at historical OLAP statistics Customers running this analysis need to comply with side conditions listed in SAP note 2502280 and

confirm this explicitly on the selection screen:

SAP HANA CPU requirements assessment

Page 53: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

53PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Recommended CPU power now part ofsizing results (only if compliance wasconfirmed)

Results can be any of:

CLASS L (100% CPU Req.):SAPS close to the CPU power of a machine with standard configuration

CLASS M (50% CPU Req.):Half of SAPS for CLASS L

CLASS S (25% CPU Req.):Half of SAPS for CLASS M

SAP HANA CPU requirements assessment: Results

Page 54: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

54PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Migration sizing part 2/2

Existing Non-NW-based system to be migrated to SAP HANA

•Analysis of legacy system

•SAP HANA version of Quick Sizer

SAP S/4HANASAP HANA native

•Analysis of legacy system

•SAP Note 1514966•Request a sizing service

Existing NW Java system to be migrated to SAP HANA

Expert SizingSizing Guidelines

Page 55: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

55PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing verification

Existing SAP HANA system

Non-NW products on SAP HANA

SAP Note 1872170

SAP Business Suite powered by

HANA & SAP S/4HANA

Industry solutions

powered by SAP HANA

SAP NW BW powered by

HANA & BW/4HANA

SAP Note 2296290

Early Watch Alert

SAP Note 1969700

SAP Note1698281

Page 56: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

56PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Sizing introduction and basics

Sizing tools

Demo Quick Sizer

Sizing SAP S/4HANA and SAP S/4HANA Cloud Greenfield Migration Deployment options

Agenda

Page 57: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

57PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Deployment options

Virtualization – 1788665 - SAP HANA Support for virtualized / partitioned (multi-tenant) environments

Infrastructure as a Service (IaaS) – Certified and Supported SAP HANA Directory

Physical server – Certified and supported SAP HANA directory

Page 58: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

58PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

APPLIANCE DELIVERY MODEL

SAP HANA TDI Phase 5: Workload-driven SAP HANA system sizingIncreased flexibility, lower TCO

Pre-defined HW sizing

T-Shirt Sizing with best in class performance

Highly optimized hardware setup (only top-bin CPUs)

Low Implementation effort

Pre-configured and pre-installed system setup

SAP HANA TAILORED DATACENTER INTEGRATION (TDI) PHASE 5

Flexible HW sizing (Applies only to newer processor types: Intel Xeon-SP Skylake*, Intel Xeon EX E7 Broadwell*, and IBM Power8 processors)

Tailored customer sizing: System memory & processor sizing are fine-tuned for the specific customer workload

SAP HANA hardware partner translates the sizing results (SAPS, RAM, CPU, and disk I/O**) into customer-tailored system configurations using a wide range of CPUs (incl. lower-end CPUs, not only top-bin CPUs)

Only hardware is delivered – Sizing and installation remains the responsibility of customer and/or partner

*Platinum, Gold, Silver with 8 or more cores** TDI storage KPI´s still need to be met but the I/O sizing takes a higher precedence: If workload requires more I/O than the system / configuration has to be adjusted to meet the higher I/O requirements coming from sizing

The newly enhanced sizing approach for SAP HANA enables workload-driven hardware configurations resulting in increased flexibility and new cost savings for customers

Page 59: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

59PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

www.sap.com/sizing Access to Quick Sizer* Access to sizing guidelines, for example, SAP HANA accelerators

SAP Support Portal SAP Note 1872170 – SAP S/4HANA memory sizing SAP Note 1793345 – Sizing for Suite on HANA SAP Note 2296290 - New Sizing Report for BW/4HANA SAP Note 1969700 - SQL Statement Collection for SAP HANA SAP Note 1698281 - Assess the memory consumption of a SAP HANA System SAP Note 1514966 – SAP HANA: Sizing SAP In-Memory Database SAP Note 2779240 - Workload-based sizing for virtualized environments SAP Note 2815376 - Greenfield sizing for SAP S/4HANA embedded analytics SAP Note 2813738 - Brownfield sizing for SAP S/4HANA embedded analytics

SAP HANA Quick Sizer (for greenfield sizing)YouTube Video

Sizing information and toolsSources of published sizing documentation

* Requires login credentials

Page 60: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

60PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Access SAP TechEd Learning Journeys

Discover related learning content

Watch webinars of SAP TechEd lectures

Learn about SAP’s latest innovations with openSAP

Collaborate with SAP experts

Self-test your knowledge

Earn a SAP TechEd knowledge badge

Continue your SAP TechEd 2019 Learning Experience Join the digital SAP TechEd Learning Room 2019 in SAP Learning Hub

Page 61: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

61PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Access replays Keynotes Live interviews Select lecture sessionshttp://sapteched.com/online

Continue the conversation Read and reply to blog posts Ask questions Join discussionssap.com/community

Check out the latest blogs See all SAP TechEd blog posts Learn from peers and experts

SAP TechEd blog posts

Engage with the SAP TechEd Community Access replays and continue your SAP TechEd discussion after the event within the SAP Community

Page 62: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

62PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

More information

Related SAP TechEd Learning Journeys CAA3 – Move to SAP S/4HANA CAA4 – Get to SAP S/4HANA Cloud

Related SAP TechEd sessions LT103 – How the World’s Largest ERPs Move to SAP S/4HANA….

Public SAP Web sites SAP Community: www.sap.com/sizing SAP Community: www.sap.com/benchmarks

Page 63: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

Feedback Contact for further topic inquiries

Thanks for attending this session.

Please complete your session evaluation for CAA303.

Sebastian SchmittProduct Management Performance & Scalability [email protected]

Detlef ThomsProduct Management Performance & Scalability [email protected]

Page 64: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

Appendix

Page 65: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

65PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

What Is SAPS?

SAP Application Performance Standard (SAPS) is a hardware-independent measurement unit that describes the throughput of hardware in an SAP environment.

Laptop 1 processor Quad-core Approx. 10,000 SAPS

Commodity server 2 processors 40 cores Approx. 90,000 SAPS

High-end server 16 processors 244 cores Approx. 500,000 SAPS

Definition of SAPS:

Derived from Sales & Distribution (SD) Standard Application Benchmark

100 SAPS = 2,000 fully-processed order line items per hour

For more information on SAPS, see www.sap.com/benchmark→ Measuring in SAPS

Page 66: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

DemoQuick Sizer

Page 67: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

67PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Text

Two different/separate sizing strategies with different goals

Advantages Users are relatively easy to

determine Memory is driven by user contexts

Challenges Define “user” Determine user load patterns Sizing DB growth by users

Sizing by users Sizing by throughput

Advantages Scenario, transaction Based on actual business objects

and scenarios Peak/Average sizing

Challenges Obtaining the right figures

Page 68: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

68PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Creating a sizing project

Procedure1. Find your customer number as

default2. Enter a project name 3. Read and accept the disclaimer

Page 69: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

69PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Details on Quick Sizer start page

If you want to create a new project→ Create Project

If you want to change an existing project→ Change Project

If you want to display a project→ Display Project

If you want to get an overview about Quick Sizer→ Quick Sizer for Beginners

If you want to copy your project→ Create with reference function

If you forgot the project name → Project search function ‘Show my Projects’

If you want to take a look at an example for a application → Show examples function

Page 70: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

70PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Structure of Quick Sizer

Questionnaire• Hardware infrastructure (optional)• Per solution/key capability

Project-wide information• Workdays• Status• Owner• Method• Links to hardware

vendors• Documentation• Disclaimer

Input Navigation Tree• Solutions• Key

capabilities

Page 71: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

71PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Navigation

To open a questionnaire, click on the text

Meaning of the icons:

Grey: no input yet

Green: questionnaire filled in, no errors

Yellow light bulb: current questionnaire

Red: questionnaire filled in and contains errors– If there are errors, no results will be calculated

Page 72: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

72PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Navigation — Search

Page 73: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

73PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Project header information

Functions in the project header• Saving of sizing data• Create print page for each page• Calculate result• Set project to GoingLive and Final• Feedback• Quick Sizer tool documentation• Direct access to hardware vendors sizing information• Disclaimer

Page 74: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

74PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Project header information (cont.)

Change the number of workdays per year

Status• Empty project (Without entries)• In progress• GoingLive• In progress after GL• Final• Inactive

Owner• Displays GL version or customer version

Method

Page 75: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

75PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Details on project header information Documenting sizing projects: Print files

Print files• From every page on Quick Sizer, you can create a print file

• Print directly• Save to disk• Helpful for status documentation

Page 76: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

76PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Details on help and online documentation

Quick Sizer tool documentation• General documentation on Quick Sizer

How to fill in the questionnaire• Help per questionnaire

Page 77: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

77PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Structure of sizing questionnaires

Questionnaire-wide information

User-based sizing

Throughput-based sizing

Page 78: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

78PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Details and questionnaire-Wide information

Changing average workday and peak times• Default workday: 9-18• Default peak: 12-13

Check input

Use default values

More Details

Clear questionnaire

Link How to fill in the questionnaire

Page 79: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

79PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

User-based sizing

Concurrently active users

Standard pattern of low, medium, and high activity users

If disk is calculated, you also need to enter the residence time in months

Independence of results

Page 80: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

80PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

User-based sizing tables

Clear and mark functions

Input fields and functions

Page 81: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

81PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Throughput-based sizing

Functions in the input tables• Tray• Mark lines • Delete/ClearEntry fields/non-entry fields/mandatory input fields

Page 82: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

82PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Throughput-based sizing tables

Table selection menu Element A/P – (A)verage or (P)eak TI – Time interval Objects – Number of objects Items % chg / % dsp – changes & displays in

% Mon. – Months – Residence time in

months Arch. – Archiving project planned S.t. / E.t – Begin and end of

processing times ID – Identification Short text – Text field for comments

Page 83: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

83PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Error handling – Check function and messages

Page 84: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

84PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Errors – No sizing result

Page 85: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

85PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Details on result display/result level

Result levels• Project • SAP solution• Software component • Key capability• Sizing elements + choice• Line results + inputs • Results, statistics, inputs

Page 86: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

86PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

There are the following sizing categories and results for Memory, CPU, and Disk space:

Sizing categories and results – I/II

NoteThe results of category XXL may be outside the scope of the Quick Sizer tool, please contact your hardware vendor or SAP for further information.

NotePlease keep in mind that the sizing categories for CPU, Disk space and Memory have to be considered as disjoint result categories (no interdependency between the different sizing categories);

Page 87: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

87PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

There are the following sizing categories and results for Data IO and Log IO:

Sizing categories and results – II/II

NoteThe results of category XXL may be outside the scope of the Quick Sizer tool, please contact your hardware vendor or SAP for further information.

Page 88: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

88PUBLIC© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP HANA tailored data center integration provides you with flexibility regarding the hardware components required to run SAP HANA. Leveraging this approach you will:

– Reduce hardware and operational costs by reusing existing hardware components and operation processes

– Mitigate risks and optimize time-to-value by enabling existing IT management processes for SAP HANA implementations

– Have more flexibility in hardware vendor selection by leveraging the existing ecosystem

SAP started delivering SAP HANA in the form of standardized and highly optimized appliances, offering companies the possibility to choose between several SAP HANA hardware partners. Those SAP HANA appliances are built based on a well-defined hardware specification designed for the performance requirements of a solution which leverages in-memory technology. It is a delivery of a preconfigured hardware setup with preinstalled software packages that can be quickly implemented by your SAP HANA hardware partner of choice.

SAP HANA appliance vs. SAP HANA tailored data center integration

Page 89: CAA303 - Sizing for SAP S/4HANA and SAP S/4HANA Cloud

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission ofSAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation orwarranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, andfunctionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

See www.sap.com/copyright for additional trademark information and notices.

www.sap.com/contactsap

Follow us