1.SAP BASIS Material Keylabs1

IBM Global Business Services
SAP High-Performance Analytics Appliance (HANA)

Overview
SAP HANA Overview © Copyright IBM Corporation 2012.

Welcome
 Presenters – Vijay Vijayasankar and Guillermo Vazquez
2 SAP HANA Overview © Copyright IBM Corporation 2012.

Webinar session objectives
At the end of this session, you should be able to:
 Describe the technical components and licensing

of HANA
 Identify where HANA fits in the technology stack
 Discuss the technical use cases for HANA
 Identify industries and customers that could
benefit from HANA
 Understand the implications of HANA for
business users

Agenda
 What is HANA?
 The three technical use cases for HANA
 What’s inside HANA?
 Upcoming business solutions for HANA
 Wrap-up

Question: What is HANA?
A. A business application solution

B. An overpriced database
C. The answer to world peace
D. Vaporware
If you are listening to SAP’s sales team talk about

it, the correct answer is C.
5 SAP HANA Overview © Copyright IBM Corporation 2012

What is SAP HANA: The simple answer …
SAP HANA is the sum of … You can compare it to …

 A database  IBM DB2 database
 A server with storage to run it on  An x-Series server with attached
 PC client software to administer the disks
database and develop SQL code  The database transactions and
 Middleware to extract, transform, Developers’ Workbench in SAP GUI
and load data (ETL)  IBM InfoSphere® DataStage

What is SAP HANA: The simple answer …
SAP HANA is the sum of … You can compare it to …

 A database  IBM DB2 database
 A server with storage to run it on  An x-Series server with attached disks
 PC client software to administer the  The database transactions and
database and develop SQL code Developers’ Workbench in SAP GUI
 Middleware to extract, transform, and  IBM InfoSphere® DataStage
load data (ETL)
Answer: The database is the key message.

Functionally, HANA does what Oracle,
DB2, or SQL Server does, but 100x faster.
It is starting to replace those databases
in SAP’s technology stack. (But, do not
tell customers to throw out their old
databases yet)

How HANA changes the technology landscape:

The world before HANA
Reporting is done in ERP and BW; “Big Data” challenges are
handled with BW Accelerator (BWA)


HANA 2012 – A sidecar for transactional
applications
Tactical and operational reporting is still done in BW; Some advanced analytics and “Big Data”
challenges moved to HANA

BW on HANA Engagement Model

Three Categories of Activities (2 of 2)
BW on HANA Solution Planning
Current State BW 7.3 BW7.3 on HANA
BW 3.x / 7.x BW 7.3 SP7 BW 7.3 SP7

(Legacy DB/HW) (Legacy DB/HW) (HANA)
BW on HANA BW on HANA BW on HANA

Assess Prepare Migrate
Use Case Identification BW Technical Upgrade HANA Readiness
BW Technical Upgrade
Unicode Upgrade OS/DB Migration
Unicode Planning
BW Authorizations BW Authorizations
BW Data Volumes
BW Data Volumes
BW In-Memory
Conversion Analysis Functional Upgrade
As-Is Analysis including In-Memory
conversion
SAP HANA Overview © Copyright IBM Corporation 2012


HANA 2012 – A sidecar for transactional
applications
Tactical and operational reporting is still done in BW; Some advanced analytics and “Big Data”
challenges moved to HANA SAP BusinessObjects Other
BI Solutions Applications
SAP HANA™
SAP SAP
HANA Information
Studio Composer
SAP HANA Database
Calculation Row & Column

Engine In-Memory
Real-Time SAP
Data BusinessObjects
Replication Data Integrator
SAP Non SAP Data

Applications sources

Key architecture drivers behind SAP’s current vision
1. Improve performance by replacing the traditional relational database:

– Columnar, in-memory technology is up to 100x faster, uses 60% to 80% less storage,
and scales horizontally on cheap-ish hardware (Intel / Linux blade server).
2. Improve performance and reduce cost by eliminating application servers:
– Today, SAP’s application servers provide horizontal scalability, because databases were
historically the bottleneck.
– HANA permits horizontal scaling of the database, similar to Oracle RAC or DB2
PureScale. By leveraging the technology behind BWA, it is already robust.
– Moving the application logic and complex queries into the database eliminates network
traffic and allows faster performance.
3. Provide true real-time analytics and lower ETL costs by merging all
transaction processing and reporting into one database:
– The improved processing power eliminates the problems we traditionally had with
putting reporting loads in the operations database.
– The ETL code to shuttle data between databases goes away.

Agenda
 What is HANA?
 Wrap-up

The three technical use cases for HANA
1. Operational Data Store (ODS) database:

- HANA is a sidecar to SAP ECC and/or other business applications
- Mirrors a portion of one or more transactional databases
- Enables and accelerates real-time operational analytics
- Supported in HANA 1.0 – released June 2011
2. Online Analytic Processing (OLAP) database:

- HANA in the backend database for SAP Netweaver BW
- Accelerates data loads, consolidation, harmonization, and complex querying for analytical reporting
across many systems
- available
3. Online Transaction Processing (OLTP) database:

- The backend database for SAP ECC, CRM, PI, EP, or other applications
- Accelerates transaction processing, batch jobs, and complex queries in business applications
- Not available now – support planned longer-term, perhaps in 2013

HANA as operational data store
Use case: Synchronize data from SAP ERP (or other business applications) for
operational reporting or real-time decision-making:
 Operational queries run 100x faster; reports can be run in real-time on much larger volumes
of data.
 Decisions that require churning through large volumes of data can be made in real-time:
– Available-to-promise inventory
– Last-minute production planning
– Advanced material requirements planning (MRP) algorithms
– Reconciling financials during month-end
 Moving reporting off the transactional database improves ERP performance.
 A few standard business solutions are available and more are coming.
Except for a few standard solutions, the reporting and queries require custom
development.

Case study for HANA as ODS
The Goal
- A large retailer wants to analyze all of their point-of-sale (POS) data to predict demand, particularly
during promotions when inventory levels are particularly volatile
- They want to target re-stocking shelves with a 48 hour turnaround
Inputs needed
- Current inventory balances in real-time
- Transportation routes ad timelines
- Upcoming promotions and geography information
- POS records in near-real-time
The solution
- Deploys a high performance in-memory analytics solution in concert with existing systems
- The in-memory system chews through the massive data volumes while leaving existing solutions for
others, less-data-intensive analysis ad reporting
Results
- Shelf turnaround decisions improved from 5 days to 2 days
- Significant reductions in out of stock situations during promotions
- 20x faster analysis

HANA as OLAP database
Use case: Replace the database of SAP BW with HANA:

 Accelerate all queries, including calculations and others that the Business Warehouse
Accelerator (BWA) cannot. Reports run up to 100x faster.
 Accelerate data loads and roll-up calculations by several times:
– Significant I/O is eliminated and calculations are accelerated during data loads.
– Loading for the layered scalable architecture (LSA) is similarly accelerated.
 Reduce storage requirements about 80% versus uncompressed Oracle.
 Drive near-real-time analytics.
 Accelerate all the standard SAP business content of SAP BI and Business Objects reports,
as well as custom reporting.
By the end of 2012, you should be able to combine use cases in a single
instance of HANA. A BW running on HANA will be able to support an
operational data store for ECC and other business apps as well.

Agenda
 What is HANA?
 Wrap-up

Revisiting: What is SAP HANA?
SAP HANA is the sum of …

 A database
 A server with storage
 PC client software
 ETL middleware
HANA is offered as one of three packages that include hardware, software,

and configuration services. It requires purchasing a license from SAP, and an
appliance from a hardware vendor.

The HANA database
HANA is a proprietary columnar database that combines technology from Sybase

and the old Business Warehouse Accelerator:
 The core is fundamentally different from the relational databases we are accustomed to:
DB2, Oracle, SQL Server, or MaxDB.
 The database API is fundamentally the same as those databases:
– SQL programming language with full support of stored procedures (based on ANSI SQL
’92)
– JDBC and ODBC drivers for connectivity (standards-compliant for interoperability)
– Security is role-based and equivalent to the relational databases
 The database architecture is massively parallel processing (MPP):
– Data is distributed across many physical blade servers.
– Behind the scenes, the engine splits a query into pieces, sends part of the work to each
blade, and assembles the finished result.
 All of the data and logic is stored in RAM.
 During startup, operations can start while the system is still loading data into RAM.

The HANA server
The server appliance consists of:

 Intel x86 blades
 A lot of RAM – all of the database data is stored in RAM:
– 1TB appliances were used in the ramp-ups. Up to 8TB is reasonable in the short-run.
Larger systems are coming.
– Only half of the server’s RAM should be used for data, but the columnar format is ~
80% more efficient than an uncompressed relational database. Eight TB RAM in HANA
is roughly 20TB in Oracle or DB2 without compression.
 Solid state disk (SSD) storage for pre-loaded software and for backing up the data:
– Non-volatile flash memory is used, because it is up to 30x faster than spinning hard
drives. Speed-to-recovery after a restart was an issue in BWA.
 Pre-installed, factory-configured software:
– This includes SUSE LINUX, proprietary Intel microcode, the hardware vendor’s system
management tools, and SAP’s stack of HANA software.
 BWA appliances generally cannot be repurposed for HANA:
– Nothing is stopping a hardware vendor from offering services to reconfigure existing
hardware, but there is little justification to certify hardware for both solutions.

The rest of the HANA software

SAP HANA studio and client
Developers and administrators use the

HANA studio and client to do:
 Model-driven, drag-and-drop config that
generates SQL behind it
 Direct editing of SQL and stored
procedures
 System administration
 Sybase Replication Server (SRS)
configuration
The studio uses Eclipse as the development client - same as WebAS Java (and ABAP 7.3). It
is relatively intuitive, if you have worked with the advanced tools from other database
vendors. It is not like SAP’s data dictionary.

The remaining HANA software
 Sybase Replication Server:  optional

– This ETL tool enables easy replication directly with a database, bypassing the API layer.
– It is supported for accessing ERP and other SAP applications.
– It is not supported for applications running on Oracle database (including ERP).
 SAP’s software configuration management tools:

– It includes out-of-the-box integration with Solution Manager for software patches, solution
deployment, and monitoring, as well as the SAP Java Virtual Machine (JVM) to run these
tools. Your BASIS administrators are already familiar with these.

Differences between the three HANA license options
Three different SAP HANA licenses are available. The only difference is what SAP
data integration software is included:
1. SAP HANA Platform Edition  Preferred when you own BOBJ DS and do not need SRS
– No ETL is software installed. This is for customers, who have existing ETL capabilities
and only plan to use their existing tools to integrate with the database.
2. SAP HANA Enterprise Edition  Preferred for SAP on Oracle customers
– This includes everything in Platform Edition, plus BOBJ DS 4.0 licenses.
3. SAP HANA Enterprise Extended Edition  Preferred for SAP on DB2 / SQL / MaxDB
– This includes everything in Enterprise Edition, plus SRS for HANA pre-installed.
– This includes licenses for the SRS agents that you will install on the business
applications’ databases.
IBM Information Server and other vendors’ data integration suites can be
used in lieu of BOBJ DS, using HANA’s JDBC or ODBC connectivity. They
cannot compete with the ease-of-use or automation in SRS for HANA.

Agenda
 What is HANA?
 Wrap-up

What does HANA do for business users?
HANA can power a transformation in business processes. It is not just about speed - it lets a
business think of solutions that cannot be imagined today.
 Operational decision processes:
– A user can do ad-hoc analysis on terabytes of real-time data, without waiting for it to be
loaded into BW. For example, gross profit calculations that typically are done at month-
end, can now be done on demand, supporting immediate adjustments to pricing, and
so on.
 Tactical response to business events:
– An organization can make real-time adjustments using correct and current information
in lieu of “intuition.” For example, routing of trucks can be changed based on real-time
information from complex event processing.
 Strategic execution:
– An executive can have real-time dashboards that provide up to the second updates on
data that drives the business. Examples: inventory levels, current and forecast
utilization of plants and machinery and people, end-to-end supply chain impact of order
changes and supply disruptions, and so on.

Business solutions for HANA

available now
 SAP ERP Rapid-Deployment Operational Reporting:
– 24 report models for A/P, A/R, purchasing, sales, and shipping
 SAP CO-PA Accelerator:
– Real-time profit analysis; faster analysis of cost and profit
 SAP Finance and Controlling Accelerator:
– Accelerate month-end close and improve financial performance
 SAP Sales Pipeline Analysis:
– CRM: Analyze sales pipeline; quotes, opportunities, contracts
 SAP Customer Segmentation Accelerator:
– CRM: Identify target groups for campaigns through data mining
 SAP Smart Meter Analytics:
– IS-U: Plan and deliver real-time load-management services
 SAP BW powered by HANA:
– GA
* Additional industry solutions are available or in ramp-up

Proposed business solutions for HANA

Order Management Utilities
 Available-To-Promise  Smart Metering
 Price Optimization  Demand Side Management
Supply Chain  Balance and Demand Forecasting
 Transportation Planning  Churn Management
 Inventory Management  Business Analytics
 Demand and Supply Planning (Profitability, Re-Bill, Risk and so on)
 Supply Network Planning and  Outage Management
Manufacturing  Investment Planning
 Production Planning  Grid Management
 Operational Performance Retail / CP
Management  POS / Fraud Detection
 Real-Time Asset Utilization  Business Planning
Sales and Marketing Financial Services
 Marketing analytics  Risk Analysis
 Customer segmentation  Hedge Fund Trading Analysis
 Trade Promotion Management Telecom
Finance  Investment Planning CP
 Planning and Budgeting  Supplier Risk Management
 Consolidation  Track and Trace: Product Recall
 Product Cost Calculation  Product Lifecycle and Cost Management
 Dynamic Cash Management HR  EPA Standards Compliance
 Strategic Workforce Planning IT  Real-Time Warranty and Defect Analysis
 Landscape Optimization Banking
Manufacturing Industry  Liquidity Risk Management
 Sales and Operations Planning  High-Tech (focus area–solution not
announced yet)
Note: These reflect SAP’s product planning

on a fairly long roadmap, and are subject
to change.

Proposed business solutions for HANA (Continued)

Utilities
Order Management  Smart Metering
 Available To Promise  Demand Side Management
 Price Optimization  Balance and Demand Forecasting
Supply Chain  Churn Management
 Transportation Planning  Business Analytics (Profitability, Re-Bill, Risk…)
 Inventory Mgt.  Outage Management
 Demand and Supply Planning  Investment Planning
 Supply network planning  Grid Management
Manufacturing Retail/CP
 Production Planning  POS/Fraud Detection
 Operational Performance Mgt.  Business Planning
 Real-Time Asset Utilization Financial Services
Sales and Marketing  Risk Analysis
 Marketing analytics  Hedge Fund Trading Analysis
 Customer segmentation Telecom
 Trade Promotion Management  Investment Planning
Finance CP
 Planning and Budgeting  Supplier Risk Mgt.
 Consolidation  Track and Trace: Product Recall
 Product Cost Calculation  Product Lifecycle and Cost Mgt.
 Dynamic Cash Management  EPA Standards Compliance
HR  Real-Time Warranty and Defect Analysis
 Strategic Workforce Planning Banking
IT  Liquidity Risk Management
 Landscape Optimization High-Tech
Manufacturing industry (focus area - solutions expected)
 Sales & Operations Planning Note: These reflect SAP’s product planning on a fairly
long roadmap, and are subject to change

Agenda
 What is HANA?
 Wrap-up

IBM GBS offers for HANA

1. SAP HANA Value Identification Workshop:
 Description: Workshop with the business to identify HANA opportunities and develop the roadmap
 Tasks:
- Analyze existing BI architecture
- Conduct workshop with business representatives
- Identify scenarios that could benefit from HANA
- Assess business case for each scenario
- Define high-level roadmap for HANA
 Major Deliverables: HANA value quadrant and HANA project roadmap
 Duration: 1 week
2. SAP Analytics Jumpstart for HANA:

 Description: Assess BI vision and reality; derive an analytics roadmap with focus on HANA opportunities
 Tasks:
- Identify high-value opportunities for BI
- Assess technical and organizational readiness for HANA
- Determine actionable next steps and the fastest path to value
- Prepare HANA value case
 Major Deliverables: current state assessment, design diagrams, HANA value case, and analytics roadmap
 Duration: 3 to 5 weeks

IBM GBS offers for HANA (continued)

3. SAP HANA Technical PoC
 Description: Define and implement a PoC with HANA based on a previously identified analytics opportunity
 Tasks:
- Define analytical problem
- Define scope
- Install HANA at the client site
- Implement ETL
- Implement analytics frontend
- Conduct business review of PoC
- Review HANA roadmap
 Major Deliverables: HANA installation, analytics solution, and revised HANA value case and roadmap
4. SAP HANA Technical PoC

 Description: SAP HANA production pilot; implement use cases with intent to go live
 Tasks:
- Requirements definition
- Business blueprint
- Technical specifications
- Design and set up technical architecture
- Implementation (backend + frontend)
- Testing
- Rollout
- Documentation
 Major Deliverables: Business blueprint, technical specs, HANA solution, and documentation

Key points to remember
 To a technologist, HANA is just a really fast database, with a few other

components thrown in.
 HANA is an OLAP (reporting) database today – it is not yet ready for transaction-
processing applications.
 Business value is created by solutions running inside HANA, not by HANA itself.
 SAP has three different license options; the only difference between them is the
ETL middleware you use.
 HANA can accelerate analytics as a sidecar to any business application–it is not
limited to SAP.
 If you are not using one of the HANA-specific solutions, or SAP BW powered by
HANA, then using HANA is 100% custom development.

Summary
Now you should be able to:
 Describe the technical components and licensing

of HANA
 Identify where HANA fits in the technology stack
 Discuss the technical use cases for HANA
 Identify industries and customers that could
benefit from HANA
 Understand the implications of HANA for
business users

For more information …
 IBM-SAP alliance Web site:

– A good source for IBM STG solutions for HANA
– IBM SAP HANA link
 SAP TechEd 2011:

– A dozen decks showing the case for HANA, current roadmaps, and how HANA
works in detail
– Cattail link for TechEd HANA

Any questions?

Thank You
 Vijay Vijayasankar
 Guillermo Vazquez

1.SAP BASIS Material Keylabs1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1.SAP BASIS Material Keylabs1

Uploaded by

Copyright:

Available Formats

IBM Global Business Services

SAP High-Performance Analytics Appliance (HANA)

SAP HANA Overview © Copyright IBM Corporation 2012.

 Presenters – Vijay Vijayasankar and Guillermo Vazquez

2 SAP HANA Overview © Copyright IBM Corporation 2012.

Webinar session objectives

At the end of this session, you should be able to:

 Describe the technical components and licensing

3 SAP HANA Overview © Copyright IBM Corporation 2012.

 The three technical use cases for HANA

 What’s inside HANA?

 Upcoming business solutions for HANA

4 SAP HANA Overview © Copyright IBM Corporation 2012.

Question: What is HANA?

A. A business application solution

If you are listening to SAP’s sales team talk about

5 SAP HANA Overview © Copyright IBM Corporation 2012

What is SAP HANA: The simple answer …

SAP HANA is the sum of … You can compare it to …

6 SAP HANA Overview © Copyright IBM Corporation 2012

What is SAP HANA: The simple answer …

SAP HANA is the sum of … You can compare it to …

Answer: The database is the key message.

7 SAP HANA Overview © Copyright IBM Corporation 2012

How HANA changes the technology landscape:

8 SAP HANA Overview © Copyright IBM Corporation 2012

How HANA changes the technology landscape:

9 SAP HANA Overview © Copyright IBM Corporation 2012

BW on HANA Engagement Model

Current State BW 7.3 BW7.3 on HANA

BW 3.x / 7.x BW 7.3 SP7 BW 7.3 SP7

BW on HANA BW on HANA BW on HANA

SAP HANA Overview © Copyright IBM Corporation 2012

How HANA changes the technology landscape:

SAP HANA Database

Calculation Row & Column

SAP Non SAP Data

11 SAP HANA Overview © Copyright IBM Corporation 2012

Key architecture drivers behind SAP’s current vision

1. Improve performance by replacing the traditional relational database:

12 SAP HANA Overview © Copyright IBM Corporation 2012

 The three technical use cases for HANA

 What’s inside HANA?

 Upcoming business solutions for HANA

13 SAP HANA Overview © Copyright IBM Corporation 2012.

The three technical use cases for HANA

1. Operational Data Store (ODS) database:

2. Online Analytic Processing (OLAP) database:

3. Online Transaction Processing (OLTP) database:

14 SAP HANA Overview © Copyright IBM Corporation 2012

HANA as operational data store

15 SAP HANA Overview © Copyright IBM Corporation 2012

Case study for HANA as ODS

16 SAP HANA Overview © Copyright IBM Corporation 2012

HANA as OLAP database

Use case: Replace the database of SAP BW with HANA:

17 SAP HANA Overview © Copyright IBM Corporation 2012

 The three technical use cases for HANA

 What’s inside HANA?

 Upcoming business solutions for HANA

18 SAP HANA Overview © Copyright IBM Corporation 2012.

Revisiting: What is SAP HANA?

SAP HANA is the sum of …

HANA is offered as one of three packages that include hardware, software,