Orange County Convention Center

Orlando, Florida | June 3-5, 2014

Real-time Challenges ‒ Migration to SAP Business Suite powered by SAP HANA Praveen Sabbavarapu, ProSoft Technology Group

Why SAP Business Suite on SAP HANA?

Challenges in Migration to Suite on SAP HANA

Migration Options to Choose from & Dual Stack

SAP Business Suite Powered by SAP HANA POC

Scope

Tests & Results

Key Considerations

Partnerships

Q&A

LEARNING POINTS

ProSoft Technology Group

Founded in 1995 Presence across US, Canada and India

Inc. 500 Fastest Growing Companies

(2005, 2006, 2007, 2008, 2011)

Industry Focused Expertise

• Retail

•Consumer Products

•Manufacturing

•Wholesale Distribution

350 + Associates Globally

Management Consulting + Technical Delivery Experience

Industry Retail Manufacturing

Technology ECC

CRM

SAP Life Cycle Phase 2+

SCM PLM

PI EP

Wholesale Distribution

HANA

Mobility

E-Comm

BA

Consumer Products

Why SAP Business Suite on SAP HANA?

SAP HANA is a Next Gen Business Platform leveraging in-memory technology

Brings transactions and analytics together

Dramatically increases the performance of applications

Gives ability to handle structured and unstructured data

Reporting can be done without latency

Open Architecture

Simplification of IT delivery processes

Initial Steps

Budget Business Case Trusted Partnership

Planning

Optimized Sizing & Infra On-premise Vs Cloud Right Migration Strategy

Execution

Manage Downtime Unicode & Dual Stack Split Code Optimization Cutover

Challenges

Initial Steps

Planning

Execution

Application Server

There should be no change to the existing Application Server Sizing

If it is a Greenfield migration/implementation, sizing should be done exactly same as traditional non-HANA application server sizing

Usually about 0% - 5% increase in CPU, Memory and Disk Refer to SAP Note: 1723135 - Resource requirements for SAP

ERP Central Component 6.0 EHP6 (for upgrade considerations)

Sizing

HANA Appliance Memory

If CR is >= 4:1 then HANA Appliance Memory size = ½ source database uncompressed size + 20% + 10% + growth

If CR < 4:1 then HANA Appliance memory size = (½ source database uncompressed size + 20% + 10% + growth) x 2

Refer to cookbook: https://cookbook.experiencesaphana.com/bw/operating-bw-on-hana/hana-database-administration/monitoring-landscape/memory-usage/

Refer to SAP notes: 1793345 (for Greenfield) and 1872170 (ZNEWHDB_SIZE)

Sizing

HANA Appliance CPU

The appliance is configured in such a way that the CPU power and the I/O capacity is sufficient.

For Parallel processing, SAP recommends a factor of 3 to 4 more CPU power

HANA Enterprise Search may require additional CPU resources

HANA Disk Space

SAP recommends to use half of the required disk space that is needed for the Business Suite for disk-based databases

If HANA Enterprise Search is used, an additional 20% disk space is recommended

Sizing

High availability scenarios in a multi-node cluster with a standby-node are released for the Suite on HANA, but are restricted to the simplest case of two servers (one worker, one standby) only

Scale-out scenarios with multiple worker nodes to scale memory are not yet generally released for Suite on HANA. It is recommended to scale-up memory by using a hardware configuration that maximizes the available database memory

High Availability & Scaling

SAP HANA Storage Replication

Synchronous Asynchronous Refer to the SAP Notes for certified solutions: 1755396 -

Released DT solutions for SAP HANA with disk replication

SAP HANA System Replication

Replication Modes

Synchronous

Synchronous in Memory

Asynchronous

Synchronous with Full Sync Option (SPS08)

Disaster Recovery

Backup to file system on Linux

SAP HANA Database backup (data & database configuration files) using the Linux Cron Daemon or other scheduling tools: 1651055 - Scheduling SAP HANA Database Backups in Linux

Backup with third party tools

We can install the third party backup tools in the HANA appliance after meeting the prerequisites.

SAP Notes: 1730932 - Using backup tools with Backint for HANA

Backup

SAP HANA Appliance

SAP HANA: Infra Subscription

SAP HANA: Cloud Platform

SAP HANA Enterprise Cloud

SAP HANA on VMWare

Provider Certified H/W (IBM, HP, Dell, Cisco, Hitachi etc.)

AWS SAP SAP TDI & Certified H/W (vSphere)

Licensing Perpetual BYOL Monthly subscription; license included

BYOL Perpetual

Use case For Real-time transactions and analytics

Quick provisioning of H/W for trials, Prototypes, DEV, QAS & PRD

Extension to cloud and on premise applications (e.g. SAP SuccessFactors)

SAP Business Suite on HANA; SAP BW on HANA; Custom Applications

For Real-time transactions and analytics

Tech. Spec. Single and Multi node available

SAP offers 128 GB, 256 GB, 512 GB, 1 TB AWS

Variety of packages ranging from 1GB to 750GB data

Customized to customer requirements

Single and Multi node available

Deployment Options

Appliance Vs TDI Deployment Model

Fast Implementation

Standardized and highly optimized

Preconfigured hardware set-up

Preinstalled software package

Fully supported by SAP

More flexibility

Reuse existing hardware components and

operation processes

Save IT Budget and existing investment

Customer should get HANA installed

Customer aligns with the hardware partner

on individual support model

The following are the Four approaches to migrate your SAP Business Suite on to SAP HANA.

In-place Migration Copy -> Upgrade -> Migrate New Installation (Greenfield) DMO (Database Migration Option) – this combines upgrade &

database migration in one step

There are two steps to migrate your existing SAP Business Suite on to SAP HANA (for options 1 & 2):

Update to the latest SAP HANA and Netweaver enhancement packs.

Migration from any database to SAP HANA; i.e., export from any database and import to SAP HANA.

Migration Approach

Business value, system performance & hardware cost reduction

Evaluate business value and system performance of key transactions

MRP use-case

Price book creation use-case

Post goods issue (PGI) use-case

SAP HANA-Live analytics instead of SAP BW on SAP HANA

Mobility users’ impact on PRD live system performance

Determine how we may improve PRD performance as we add more burden to the system

Develop a business case

SAP Business Suite on SAP HANA POC: Scope

Optimization

SAP delivered optimizations (2), Optimizations of custom code (2), Custom OLTP reporting based on SAP HANA Live content (1)

System used: SAP ERP 6.0 EHP6 SP02 (for SAP HANA) on SAP HANA Rev 60

Client copy and data volume challenges

Determine a method & tool to enable a 1-day PRD client copy Maintain data, configuration, and code integrity About 9TB PRD into 2TB HANA appliance Different support packs

SAP Business Suite on SAP HANA POC: Scope

ProSoft System Installation

Installed a SAP Business Suite on SAP HANA system (incl. SP01)

Attunity Gold Client Solutions

Targeted and copied data specifically focused on test cases

Brought across client independent custom objects (Z Tables & Programs)

Configuration, programs, and master/transactional data copied from the customer’s live system into EHP6.16

Volume of data moved, only 500 GB

SAP Business Suite on SAP HANA POC: Setup

PRD

Older Support Package

9 TB

Suite on HANA

Select Transactional and Master Data

Repository Custom Objects

500 GB

Suite on SAP HANA POC: Initial Tests

Test parameters and measurement details

Only the main elements of active MRP code were ported to the Suite on HANA system

The MRP code was 10% optimized on HANA

105,000 relevant products

MRP run modifies up to ~90K purchase requisitions in each systems for each plant

Several runs with different parameters performed to avoid accidental results

We ensured apples-apples test comparisons for optimized MRP functionality between a test environment that matched the productive system and the Suite on HANA system

Performance

Results vary with parameters however MRP on HANA was found to be consistently faster than on the test baseline system

The optimized code on HANA executed 10X faster than the test baseline

Total performance gain of up to 20%

Suite on SAP HANA POC: Initial Results

Benchmark SAP delivered optimizations relevant for the customer

Standard Customer Line Item Browser (FBL5H) – Execution times improved by a factor of 6K

Billing Condition Report based on SAP HANA Live content

Current situation: Not able to generate report on non-HANA production system

Proof point: Various end user reporting requirements proved with ~7M records in conditions table, about multiple millions in Billing Items table

Suite on SAP HANA POC: Final Results

Optimization of custom transaction & code in user exit

Custom program result list – Execution times improved by factor of 3

Optimized custom code in SD pricing user exits - Identified and performed optimizations on custom code, considerable optimization potential in standard code identified

Execution time still almost same as there was very little optimization potential in custom code

Suite on SAP HANA POC: Final Results

We can trust the technology

The HANA technology works better than expected Realize value quickly through a “crawl, walk, run” approach Gain business trust quickly

Key Considerations

HANA is an inelastic experience

Organizational change occurs as capabilities increase Enhanced decision-making A different way of implementation (scrum/Agile vs. ASAP)

Key Considerations

Be prepared to go faster than you’re comfortable

Transaction speed increases value Organizational speed increases and job descriptions change Implementation speed is in weeks/months

Key Considerations

Partnerships

Hosting ProSoft, as a trusted partner, hosted the customer’s SAP

Business Suite on SAP HANA Servers

Technical Services ProSoft provided Basis and ABAP Optimization Services for the

SAP Business Suite on SAP HANA Ramp-Up project

Attunity Gold Client Solutions targeted select production data and imported it into SAP Business Suite on SAP HANA

It will help you create & win the business case /budget if you enter into a trusted partnership for a Test Drive/POC with a Systems Integrator.

1865866 - SAP EHP 7 for SAP ERP 6.0 - Release Information

706478 - Preventing Basis tables from increasing considerably

1774566 - SAP Business Suite – Restrictions

1730998 – Un-recommended versions of backup tools

1761546 - SAP ERP powered by SAP HANA – Optimizations

1875197 - Using DMO of SUM for SAP Business Suite systems

1813548 - Database Migration Option (DMO) for Software Update Manager

SAP Notes

FOLLOW US

THANK YOU

THANK YOU FOR PARTICIPATING

Please provide feedback on this session by completing a short survey via the event mobile application.

SESSION CODE: 0507

For ongoing education on this area of focus, visit www.ASUG.com