System Landscape Requirements and Essential Considerations to Prepare Your SAP Landscape for SAP S/4HANA

Lon BlakeYASH Technologies

We will take a critical look at the wide range of technical landscape considerations you need to think about when considering an upgrade to or an implementation of SAP S/4HANA. We’ll discuss hardware needs (CPU, memory, and disc requirements) as well as the need for Unicode and take a look at the landscape that SAP recommends in order to provide full productive support during the project.

In This Session

Overview of SAP S/4HANA

Migration options

S/4HANA requirements

Supported hardware platforms

Scalability

Landscape approach

Wrap-up

What We’ll Cover

SAP HANA

OPERATIONAL – Process Optimization

ANALYTICAL – Real Time with VDM

TECHNICAL – In-Memory Execution

UPDATES – New functionality via EHPUPDATES – New functionality via EHP

Fiori

INNOVATION – Perfect Enterprise

sFIN sLOG sERP…

SAP HANA

Suite on Hana (SoH)

SAP ERPSAP ERP

Suite on anyDB

SAP ERP

Any DB

Fiori

UPDATES – New functionality via EHP

OPERATIONAL – Process Optimization

ANALYTICAL – Real Time with HanaLive

TECHNICAL – In-Memory Execution

Fiori

An Evolutionary Path with Incremental Benefits:S/4HANA – The Next Generation Business Suite

Source: SAP

SAP S/4HANA

SIMPLIFICATION – Landscape SIMPLIFIC. – Landscape & Processes

Some Facts About SAP S/4HANA

10xsmaller data footprint

4xless process steps

1800xfaster analytics & reporting

7xhigher throughput

1. Built on SAP HANA

2. ERP, CRM, SRM,SCM, PLM in onesystem

3. No locking, parallelism

4. Actual data (25%) and historical (75%)

5. Unlimited workload capacity

6. Predict, recommend, simulate

7. SAP HANA Cloud Platform extensions

8. SAP HANA multi-tenancy

9. All data: social, text, geo, graph processing

10.New SAP Fiori UX for any device (mobile, desktop, tablet)

Three deployment options: on-premise, public cloud, managed cloud

Source: SAP

S/4HANA Application Design Reduces the Overall Data Footprint

S/4HANA

Suite on Traditional

DBSuite on

SAP HANA S/4HANA

S/4HANAwith split into

Actual/Historical data

Traditional

DB

ERP 6.0

HANA

ERP 6.0

HANA

HANA

S/4HANA

5x

up to

2.5x

up to

4 x

up to

593 GB

118.6 GB

42.4 GB

8.4 GB

less than 10%

How Landscape Simplification Enables TransformationS/4HANA – Single Real-Time OLTP and OLAP Environment

ETL

OLTP

Aggregate

OLAP

Day 1- 10:00 AM Day 2 - 10:00 AM

OLTP + OLAP

in SAP HANA

ImmediateDay 1 - 10:00 AM Day 1- 10:00 AM

Decisions and Actions on Old Data Instant Insight to Action on LiveData

>24Hours

TCO Reduction: Hardware

TCO Reduction: IT Effort:

TCO Reduction: Support:

Business Improvement:

Dismantle Data Mart infrastructure

Eliminate data replication and related efforts

Eliminate annual Oracle maintenance fee (ERP and Data Mart)

Real-Time Insight on business KPIs Better Real-Time decisions & User satisfaction

Source: SAP

Overview of SAP S/4HANA

Migration options

S/4HANA requirements

Supported hardware platforms

Scalability

Landscape approach

Wrap-up

What We’ll Cover

System Considerations – What Changes and What Doesn’t?Hardware Impact – Migration of Database Server Only and Benefits

AnyDB/AnyOS

An

yOS

SAP HANA/ SUSE Linux

(SLES)

SAP HANA migration

No Change No change of front

ends

Re-use of available application servers

Sizing of current application servers remains valid

Change Migration of database

to SAP HANA appliance required

Co-deployment ofapplication servers(e.g., central instances)on database hardwarenot possible with SAP HANA

Frontends

Application Servers

No Functional Changes: IMG, Customization, Modifications, Connectivity, Security, Transports, Monitoring (DBA Cockpit & SolMan) all stay the same

Application and Reporting Benefits: No dialog process in batch, acceleration/elimination of batch, run operational reports in real-time inside Suite

Source: SAP

Migration Options

Option 1: New installation

Clean installation, take chance to tidy up

Not suited for replacement of current production system

Data migration may be required

Option 2: In-place migration

Avoids changes to the overall landscape – keep SID, host-name, application server, connectivity

Downtimes during upgrade and migration

Option 3: Copy, upgrade + migrate

Ideal setup for PoCs and pilots: compare before and after, keep fallback

Short downtime of production system

BW-only: good option to run BW powered by SAP HANA parallel to original BW system productively

Source: SAP

Migration Support

DMO for SUM

Any DB

AS ABAP 7.0xKernel 7.x

ERP 6.0x

BW 7.0x

HANA 1.0 SPS6

AS ABAP 7.?? SP01Kernel 7.??

ERP 6.??

BW 7.??

Traditional System HANA powered System

One-Step Migration via Database Migration Option (DMO) for Software Update Manager (SUM)

Overview of SAP S/4HANA

Migration options

S/4HANA requirements

Supported hardware platforms

Scalability

Landscape approach

Wrap-up

What We’ll Cover

SAP provides choices for your SAP HANA deployments: Pre-installed SAP HANA system by a SAP HANA certified hardware partner as

part of the SAP HANA appliance delivery model

SAP HANA TDI tailored data center integration as an alternative to the SAP HANA appliance delivery model

SAP S/4HANA System Landscape

Source: SAP

What is the difference between the SAP HANA Appliance Delivery and the SAP HANA tailored data center integration approach?

Using the SAP HANA Appliance Delivery, the Solution validation is performed by SAP and the SAP partner including preconfigured hardware set-up and preinstalled software.

The TDI approach enables the Installation and validation to be performed by the customer’s SAP Certified Technology Specialist, and the customer is in charge to align with the hardware partner on the individual support model.

SAP HANA Appliance Delivery and SAP HANA TDI

Which hardware options are available for SAP Business Suite powered by SAP HANA?

SAP recommends the use of SAP HANA certified servers as described in the SAP Product Availability Matrix, and provides choice for storage, so customers can re-use existing enterprise storage and also use the same storage for multiple systems besides SAP HANA-based systems.

Do we need the same specs for non-production systems? SAP has relaxed the SAP HANA infrastructure requirements for non-production

usage, such as development and testing. This enables a majority of commodity infrastructure components available for SAP HANA non-production usage, either in a virtualized or bare metal environment, without certification.

Are we limited to use Intel Ivy Bridge processors for SAP HANA? SAP supports multiple choices from Intel, from low-cost non-productive

systems to Haswell, as well as IBM Power Systems. Please contact your HW vendor of choice.

TDI Hardware Options

For an SAP HANA system on Intel-based hardware platforms the following operating systems are available:

Operating Systems for SAP HANA on Intel-Based Hardware Platforms

SUSE Linux Enterprise Server (SLES) 11.x: SLES for SAP Applications 11 SP2

SAP Note 1824819 - SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP2

SLES for SAP Applications 11 SP3SAP Note 1954788 - SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP3

SUSE Linux Enterprise Server (SLES) 12 SAP Note - 2205917 SAP HANA DB: Recommended OS settings for SLES 12 / SLES for SAP

Applications 12

Red Hat Enterprise Linux (RHEL) 6.x: Red Hat Enterprise Linux (RHEL) 6.5

SAP Note 2013638 - SAP HANA DB: Recommended OS settings for RHEL 6.5 Red Hat Enterprise Linux (RHEL) 6.6

SAP Note 2136965 - SAP HANA DB: Recommended OS settings for RHEL 6.6

For an SAP HANA system on IBM Power servers the following operating system is available:

Operating System for SAP HANA on IBM Power Servers

SUSE Linux Enterprise Server 11 SP4 for IBM Power (plus additional Packages)

SAP Note 2240716 - SAP HANA DB: Recommended OS settings for SLES 11 / SLES for SAP Applications 11 SP4

SAP Note 2055470 - HANA on POWER Planning and Installation Specifics - Central Note

Dual-Stack Systems

“[A]s of SAP Business Suite 7i2011, it will no longer be possible to upgrade an SAP dual-stack system to a higher release” (SAP Note 1655335)

Suite on HANA is based on NetWeaver® 7.40 and does not support dual-stack installations

Dual-stack systems have to be split before a SAP HANA migration

A dual-stack split tool is included in the SL toolset, available on SAP Support Portal

Java stack stays on current database, since Java is not yet supported to run on SAP HANA

Unicode SAP HANA runs natively on Unicode only Unicode conversion can technically be done during the database migration, but

preparatory steps are required

Prerequisites: Dual-Stack/Unicode

Overview of SAP S/4HANA

Migration options

S/4HANA requirements

Supported hardware platforms

Scalability

Landscape approach

Wrap-up

What We’ll Cover

There are nearly 500 certified appliances on the Certified SAP HANA Hardware Directory.

In addition, it’s possible to certify almost any sane configuration with Enterprise Storage like Violin or EMC VMAX, and it’s possible to use almost any Intel server for non-production use cases, with almost any configuration.

This provides fantastic flexibility – as a customer you can choose the vendor, storage, networking of your choice and for non-production scenarios, it is possible to build systems which are much more cost-effective. The most important thing though, is to get your production hardware correctly provisioned: it can be an expensive mistake.

SAP HANA Hardware

The SAP HANA Hardware Directory lists all hardware that has been certified or is supported under the following scenarios:

Hardware that has been certified within the SAP HANA hardware certification program

Previously validated hardware based on Westmere technology - as reflected earlier in the Product Availability Matrix – PAM.

Supported Entry Level Systems: Only Intel Xeon E5 v2/v3 based 2-socket single node systems with minimum 8 cores per CPU and is valid for particular SPS releases

The certification is valid for a particular group of appliances/storage family of the hardware manufacturer wherein multiple models might be included. For further details, like released CPU types, please compare the scenario pages in SCN:

SAP HANA Hardware Certification - Appliance (HANA-HWC-AP SU) for SUSE Linux Enterprise Server (SLES) details & disclaimer

SAP HANA Hardware Certification - Appliance (HANA-HWC-AP RH) for Red Hat Enterprise Linux (RHEL) details & disclaimer

SAP HANA Hardware Certification – Enterprise Storage Senario (HANA-HWC-ES) details & disclaimer

SAP HANA Hardware

Overview of SAP S/4HANA

Migration options

S/4HANA requirements

Supported hardware platforms

Scalability

Landscape approach

Wrap-up

What We’ll Cover

Setting the stage

Scalability is the ability of a computer hardware/software to take full advantage of its changed context in a re-scaled situation, e.g., by adding or reducing resources

Vertical Scalability (Scale-up)

Adding resources within the same computing unit, e.g., #CPUs, #DRAMs

Horizontal Scalability (Scale-out)

Adding multiple computing units and making them work as one logical computing unit

SAP HANA has been designed for scale-up and scale-out since the beginning

Scalability

Source: SAP

Parallelism in HANA

HANA is heavily optimized for state-of-the-art hardware architectures

HANA uses massive intra-plan and intra-operator parallelism for query execution

HANA tries to use all available resources for maximal parallelization

Challenge: NUMA-effects on large multi-socket systems

Remark: Virtualization of CPU resources can reinforce NUMA-effects

Job Scheduler

Central place in HANA to execute plan-operator jobs

Re-adjust dynamically the concurrency level avoiding “over-parallelization”

Can consider additional .ini configuration data to limit the concurrency level

Vertical Scalability in HANA (Scale-Up)

Source: SAP

General

Scale-out means expanding to multiple servers rather than a single, bigger server in one database system

Multiple servers (nodes) are switched together to one logical, but physically distributed database system

When to scale-out?

Overcome hardware limitations of one single server (memory, CPU)

Scale-out aims to distribute data and workload

Attention

Scale-out requires deep knowledge about data, application, and hardware

Scale-out increases data center operation costs

Scale-out affects your scaling factor by inter-node communication

Horizontal Scalability (Scale-Out)

Source: SAP

Scale-up first!

Scale-up

Most common and easiest way for databases to scale

No changes in the database or application required

HANA parallelism strongly supports latest multi-CPU, multi-core HW architectures

HANA NUMA-aware scheduling and memory allocation is under development

Scale-out

Requires deep knowledge about data and workload to achieve good scaling

Scale-out works good in static distribution environments, like OLAP

Scale-out in mixed OLAP/OLTP environments can be challenging

Optimizing scale-out performance is an iterative task

Takeaways

Source: SAP

Overview of SAP S/4HANA

Migration options

S/4HANA requirements

Supported hardware platforms

Scalability

Landscape approach

Wrap-up

What We’ll Cover

Understand all dependencies in the system landscape

Dependencies and compatibility issues in a system (released DB, OS, and UI combinations in target release [vertical stack])

Dependencies between different SAP products and software components

Identify compatibility issues with other software and hardware products (e.g., third-party software, SAP partner add-ons or printers (horizontal stack), back-up and monitoring software)

Ensure Smooth System Landscape Transition

Vertical Stack

Horizontal direction

SAP Components, UI,

DB, OS, …Source: SAP

Four key questions need to be asked

Is the current version supported on SAP ERP 6.0?

Is the current version supported for the latest enhancement package?

Is it supported for Unicode?

Can I replace it with standard functionality?

You must contact the vendor very early in your planning process in order to understand your situation

SAP will not have this information

Many of these companies may have been bought or gone out of business

This can be a major source of unexpected costs if not addressed

Third-Party Prerequisites

SBX

SAP ERP 6.0

EHP6

ABAP

DEV

SAP ERP 6.0

EHP6

ABAP

QAS

SAP ERP 6.0

EHP6

ABAP

PRD

CI

SAP ERP 6.0

EHP6

ABAP

SAP

Solution Manager

ABAP / Java PRD

DI

SAP ERP 6.0

EHP6

ABAP

PRD

DI

SAP ERP 6.0

EHP6

ABAP

CI = Central Instance, DI = Dialog Instance (application instance)

Pre-Upgrade/Migration SAP ERP Landscape

SBX

SAP S/4HANA

ABAP

DEV

SAP S/4HANA

ABAP

QAS

SAP S/4HANA

ABAP

PRD

CI

SAP ERP 6.0

EHP6

ABAP

SAP

Solution Manager

ABAP/JAVA

PRD

DI

SAP ERP 6.0

EHP6

ABAP

PRD

DI

SAP ERP 6.0

EHP6

ABAP

Legend

= new release

= old release

= project work

= transport route

DEV’

SAP ERP 6.0

EHP6

ABAP

QAS’

SAP ERP 6.0

EHP6

ABAP

Project Landscape

Overview of SAP S/4HANA

Migration options

S/4HANA requirements

Supported hardware platforms

Scalability

Landscape approach

Wrap-up

What We’ll Cover

Erich Schneider, “SAP S/4HANA System Landscape” (SCN, August 2015).

http://scn.sap.com/docs/DOC-59900

“SAP HANA Tailored Data Center Integration – Frequently Asked Questions” (SAP, August 2014).

http://hcp.sap.com/content/dam/website/saphana/en_us/Technology%20Documents/SAPHANAtailoreddatacenterintegration_FAQ_Aug082014.pdf

SAP Note 2235581 – SAP HANA: Supported Operating Systems

Certified SAP HANA Hardware Directory

http://global.sap.com/community/ebook/2014-09-02-hana hardware/enEN/appliances.html

Where to Find More Information

SAP S/4HANA provides you with a 10x smaller data footprint, 7x higher throughput, 1800x faster analytics and reporting, and 4x fewer process steps

SAP provides multiple migration options, including the option to combine an upgrade and a Unicode Conversion with the Migration to HANA

You have the option of utilizing either SAP HANA Tailored Data Center Integration (TDI) or SAP HANA Appliance Delivery

Supported Operating Systems are SUSE Linux Enterprise Server (SLES) 11.x, SLES 12, and Red Hat Enterprise Linux 6.x

7 Key Points to Take Home

There are nearly 500 certified appliances on the Certified SAP HANA Hardware Directory and it’s possible to use almost any Intel server for non-production use cases

It is possible to scale-up (add CPU, RAM to single server) or scale-out (database distribution across multiple servers)

Ensure a smooth migration project by validating all dependency and compatibility (SAP components, third-party applications, printers, etc.)

7 Key Points to Take Home (cont.)

Your Turn!

How to contact me:

Lon Blake

Lon.Blake@yash.com