+ All Categories
Home > Travel > Best practices reporting on hana

Best practices reporting on hana

Date post: 10-May-2015
Category:
Upload: emceemouli
View: 2,471 times
Download: 1 times
Share this document with a friend
Popular Tags:
35
Best Practices for Universe Modeling and Web Intelligence Reporting Against SAP HANA Romaric Sokhan, Vishal Dhir CSA October 31, 2012
Transcript
Page 1: Best practices reporting on hana

Best Practices for Universe Modeling and Web

Intelligence Reporting Against SAP HANA

Romaric Sokhan, Vishal Dhir – CSA October 31, 2012

Page 2: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 2

Disclaimer

This presentation outlines our general product direction and should not be relied on in making a

purchase decision. This presentation is not subject to your license agreement or any other agreement

with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to

develop or release any functionality mentioned in this presentation. This presentation and SAP's

strategy and possible future developments are subject to change and may be changed by SAP at any

time for any reason without notice. This document 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. SAP assumes no responsibility for errors or omissions in this

document, except if such damages were caused by SAP intentionally or grossly negligent.

Page 3: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 3

Agenda

SAP HANA Overview

SAP HANA and SAP BI4

BI4 Universes with SAP HANA

Web Intelligence with SAP HANA

Demo

Key Takeaways

More Information

Page 4: Best practices reporting on hana

SAP HANA Overview

Page 5: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 5

SAP HANA in a nutshell

SAP HANA is a super-fast in-memory database and platform enabling

new possibilities in terms of analytical reporting and real-time data

acquisition and consumption.

• Real-time Analytical reporting : HANA is designed for on-line analysis. It

can calculate and execute millions of data at sub-second speed.

• Real-time data acquisition : HANA is shipped with ETL and replication

tools that brings loads data from operational systems to HANA in near

real-time

• Real-time consumption: HANA solves the issue of maintaining

aggregate tables for performance. You don’t need aggregate tables

anymore.

Page 6: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 6

SAP HANA Pushing calculations down to the database layer

Avoid movement of detailed data

MOVE calculations into HANA

Only transfer RESULTS

APPLICATION

LAYER

Calculation

DATABASE

LAYER Calculation

Classic Approach

HANA Approach

Page 7: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 7

HANA models

• Today HANA is consumed mostly by BI4 client tools using SQL interfaces, directly or via Universes (Semantic Layer)

• The modeling of HANA models can done in an authoring tool called “HANA Studio” where you will be able to design an Analytic View or a Calculation View.

• The most performing and optimal way to consume data in HANA is by using Analytic / Calculation Views.

Analytical Cubes (ROLAP) - Recommended

• Facts spread amongst several tables

• More complex joins

• Available for reporting like other RDBMS

Classical Models

Page 8: Best practices reporting on hana

SAP HANA and SAP BI4

Page 9: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 9

HANA Connectivity

Web

Intelligence

Dashboards

Exce

l

Crystal Reports

for Enterprise

Semantic Layer (universe UNX)

SQL

ODBO

An

aly

sis

Off

ice

v1

.1

BICS

ODBC

Exp

lore

r

JDBC JDBC ODBC

CR

2

01

1

JDBC ODBC

SQL SQL

Are part of SBO BI 4

SQL SQL

CR

2

00

8

JDBC ODBC

SAP HANA

Outside or as part of SBO BI 4

Outside of SBO BI 4

Page 10: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 10

The Semantic Layer in the BI Architecture

10

Semantic Layer Data Sources

Query and Analysis

Dashboards and

Visualizations

Reporting

Connectivity

Universe

Information

engine

Data Foundation Business Layer

Page 11: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 11

HANA and the Semantic Layer

Web

Intelligence

Dashboards

Crystal Reports

for Enterprise

Semantic Layer (universe UNX)

JDBC ODBC

SQL

Are part of SBO BI 4

SAP HANA

Page 12: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 12 Public

HANA and the Semantic Layer

Support of HANA by the Semantic Layer via Relational Universes

New BI4 Universe format (UNX) via a JDBC or ODBC relational connection

Access to Tables (row or column store) and SQL views

Access to Analytic and Calculation Views

New SQL features in HANA are immediately available for universes

Universes do not store data from HANA or add any performance overhead

Universes are just a translation layer

Universes are just like any other client tool using SQL to access HANA

The latest data from HANA is sent to the client tool on query refresh

Page 13: Best practices reporting on hana

BI4 Universes with SAP HANA

Page 14: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 14

Business answers can be spread over several HANA views

HANA Analytic / Calculation Views

Where can I find the answer to my business question?

Page 15: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 15

Business answers can be spread over several HANA views

HANA Analytic / Calculation Views

What is the actual revenues of my product for this year?

What are the planned profits for this product for the next year?

Page 16: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 16

Business answers can be spread over several HANA views

What do I want to do

Product

Time

Planned

Product

Time

Actual

Geography

Time

Planned

Geography

Product

Actual

Time

Actual

• I can choose any object that will help to answer my business question

• I don’t know the content of each view and I can mix objects that are not common to the selected views

• I can specify which view(s) I want to use

• I can filter my query

• I can see the result in a single table/chart whenever possible

• I can create as many queries as I want

Page 17: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 17

What is I need one or more HANA views to answer my business questions?

Product

Time

Planned

Product

Time

Actual

Geography

Time

Planned

Geography

Product

Actual

Time

Planned

Calculation view Universe Federated Universe

Answer to

multiple

business

questions

Business answers can be spread over several HANA views

No impact on

HANA

performance

Page 18: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 18

Solution: Use Universes with HANA views for flexible reporting

Leverage the Semantic Layer for flexible ad-hoc query

Access multiple HANA Views and synchronize the datasets locally without impacting performance.

Use advanced Universe features like contexts, aggregate awareness to navigate through HANA views seamlessly

Create your Navigation Paths to enable drill-down analytical reporting in Information Design Tool

Benefits

Answer to multiple business questions from the same Universe federating multiple HANA views

Optimize how users ad-hoc queries are sent to HANA

No joins between HANA Views = No impact on performance

Page 19: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 19

How to write a performing universe on SAP HANA?

Fine tune the connection options for best performance

Default Array Fetch Size changed to 1000

Make sure that query synchronization is performed in HANA and not in the

client tool

The Join_by_SQL data

foundation parameter will

force a single query to the

server with COALESCE

Page 20: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 20

HANA Variables and Input Parameters

HANA variables

Are used to filter the content of an information model. They

don’t impact the execution workflow of the information model and

are applied to a query to filter out some values

Applied to the where clause

Input Parameters

Are used to manipulate the execution of the information model

In SQL, parameters values are passed via the PLACEHOLDER reserved word

Page 21: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 21

Contexts in IDT

Contexts

Defines the path between tables

Is a set of joins

In HANA, it’s used to send different SQL to each view

Sales View Inventory View

Page 22: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 22

Aggregate Awareness in IDT

Steps involved in using Aggregate Awareness

Define the aggregate aware object

Define objects that are incompatible with that object

Page 23: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 23

Index Awareness in IDT

Helps create more efficient SQL

The universe can substitute IDs for descriptions

Primary and foreign keys must be programmed and must be done for every object to be made

“index aware”

Which is faster?

Without Index Awareness With Index Awareness

Page 24: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 24

Hierarchies in IDT

Hierarchies defined in HANA are not accessible in IDT. However, you can create a hierarchy using IDT

An example of a time hierarchy is

Year > Quarter > Month > Week

Prompting “Equal To” vs “In List”

“Equal To” allows only the lowest level to be selected

“In List” allows multiple levels to be selected

Page 25: Best practices reporting on hana

Demo

Page 26: Best practices reporting on hana

Web Intelligence with SAP HANA

Page 27: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 27

SAP Web Intelligence

Web Intelligence is an interactive reporting tool that can access relational as well as

multidimensional datasources via the concept of Universes. The reports can be viewed

online or offline thanks to the microcube, an embedded local in-memory cache engine

(microcube). In case of Hana, WebI will access it through relational access using SQL,

• Enables off-line (microcube) as well as interactive analysis

(e.g,HANA)

• Access to heterogeneous data sources

• Basic dashboarding capabilities (Drill, CVOM charts, dynamic

filters)

• Advanced Reporting capabilities (Desktop Rich Client, DHTML,

Mobile)

Page 28: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 28

SAP Web Intelligence with SAP HANA

Recommendations

• Avoid querying high volume of detailed data

• Push calculations down to HANA

• Retrieve only the results the Webi report needs (Summary data)

• Create reports on summary data with refresh on open

• Let your users explore the data using drill actions in real-time

Page 29: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 29

SAP Web Intelligence with SAP HANA : Benefits

Benefits

With traditional databases, when huge volume of data needs to be queried, aggregate tables might need to be created

to overcome performance degradations, not with SAP HANA

Another inconvenient is that you might wait for the next ETL load to have up-to-date data.

Thanks to SAP HANA in-memory engine and replication capabilities, the data is aggregated on-the-fly in real-time and

the user gets “live” data every time he/she accesses or drills into the report.

Page 30: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 30

SAP Web Intelligence - Microcube

Why Web Intelligence is using a microcube / local cube?

The micro cube is mandatory and an important part of the Webi architecture design. Having a microcube

has a lot advantages when designing and consuming a Web Intelligence reports, and it has been designed

for a vast majority of databases. The main benefit is that it can offer offline analytical capabilities like report

viewing, drilling, quick filtering, local calculations:

The WebI calculation compensates missing data source expressiveness (cross table, multi-context

evaluation, advanced functions like Previous, …) . It requires to fetch raw data first before performing local

data processing

It enables Multi-data Provider support, which requires local data materialization for data synchronization

It enables data historization (if not available from the data source) which allows users to create data

snapshots, and make features like Track Data Change possible.

Page 31: Best practices reporting on hana

Demo

Page 32: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 32

Key Takeaways

Leverage the Semantic Layer for flexible ad-hoc query

Access multiple HANA Views and synchronize the datasets locally.

Use advanced Universe features like contexts and aggregate awareness to navigate through HANA views seamlessly

Create your Navigation Paths to enable drill-down analytical reporting

Use index awareness

Don’t

Join HANA views in the data foundation

Optimize your Web Intelligence reports for HANA

Make sure your report is HANA optimized by “stripping” your query. Push calculations down to HANA and retrieve only

the results.

Enable drill workflows to make the most of with SAP HANA performance.

Page 33: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 33

More Information

SAP Public Web

Frequently Asked Question: WebIntelligence on HANA

Best Practices: WebIntelligence on HANA

Creating a universe on SAP HANA: Best Practices

SAP Education and Certification Opportunities

www.sap.com/education

Watch SAP TechEd Online

www.sapteched.com/online

Page 34: Best practices reporting on hana

Thank You!

Romaric Sokhan – [email protected]

Vishal Dhir – [email protected]

SAP Customer Solution Adoption

Page 35: Best practices reporting on hana

© 2012 SAP AG. All rights reserved. 35

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express

permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of

other software vendors.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of

Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System

z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7,

POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize,

XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere,

Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe

Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or

registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri,

and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry

Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered

trademarks of Research in Motion Limited.

© 2012 SAP AG. All rights reserved.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads,

Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice,

Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork,

SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web

Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their

respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects

is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services

mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc.

Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG

in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data

contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied,

or transmitted in any form or for any purpose without the express prior written permission of SAP AG.


Recommended