tzhana for application consultants

SAP HANA Appliance 1.0

TZHANA for Application Consultants

Material Number: 50104428

Version: 96

© SAP AG 2011

Copyright 2011 SAP AGAll rights reserved

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.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and associated logos displayed 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. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. 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 shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pagesWeitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.Alle Rechte vorbehalten.

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.

© SAP AG 2011

© SAP AG 2011

Agenda

SAP HANA Appliance 1.0Lesson 1: Introduction to HANA

Lesson 3: Architecture

Lesson 2: Look & Feel

Lesson 4: Data Provisioning

Lesson 5: Modelling

Lesson 7: User Management

Lesson 6: Reporting

© SAP AG TZHANA 1 - 1

© SAP AG 2011

Agenda





Lesson 5: Modelling


Lesson 6: Reporting


Lesson 1 Introduction to HANA

New business REALITY

Entirely new POSSIBILITIES

SAP’s IN-MEMORY offering

High-Performance ANalytic Appliance

HANA in CONTRAST to SAP Applications

HANA in DETAIL

© SAP AG 2011


SAP Naming Update: SAP HANA** always refer to “SAP HANA.” Never use “HANA.”

Application

<Application Name>, powered by SAP HANA

Example: SAP Smart Meter Analytics, powered by SAP HANA

Studio

SAP HANA studio

Appliance

SAP HANA appliance software

Database

SAP HANA database

Cloud

SAP HANA application cloud

CategorySAP in-memory computing

PlatformSAP HANA platform

© SAP AG 2011


new business reality / new challenges

© SAP AG 2011

Why wait for data: All customers want to see their current business data immediately in real-time. Nobody wants to wait until data is uploaded into BW.

Why wait for new systems: Latest hardware and latest database technology already now support real-time reporting on massive amount of data


DAILY CHALLENGES

Complex system landscapes

Massive growth of data volume

Immediate results

High flexibility

© SAP AG 2011


Missing opportunitiesCompetitive disadvantage

Reactive business mode

Need for aggregationOutdated figuresGuessing current situation

Lack of transparency

Lack of responsivenessUser frustrationUnsupportable business processes

Sub-optimal execution speed

CONSEQUENCES

© SAP AG 2011


Multicore CPUs

10 Cores / CPU

HARDWARE INNOVATIONS

320 CORES and more!4 TB RAM and more!

© SAP AG 2011

Multi-CPU Boards

8 CUPs / Board

Multi Server Board

x Boards

Massive Memory setups

2 TB/Server

New to SAP HANA Appliance 1.0

SPS02


new business reality / new challenges

The new realityNew possibilitiesSAP’s offeringHANA in ContrastHANA Details

Rethink old paradigmsInnovation enables new ways of thinking

© SAP AG 2011


AVOID BOTTLENECKS - LATENCY

Prevent CPU IDLE TIME

Introduce COLUMNAR DATA STORAGE

SP

EED

YEAR

CPU Clockspeed

Memory Bandwidth

Memory latency!

© SAP AG 2011


UNDERSTAND Columnar Data Storage

Customer Country Product Amount

100 DE 1 100

100 DE 1 110

200 US 1 120

300 US 2 130

Tuple 1

Tuple 2

Tuple 3

Tuple 4

Column1

Column2

Column3

Column4

ROW-BASED Storage

COLUMN-BASED Storage

OPTIMIZEDfor current HW

Easily COMPRESSABLE

© SAP AG 2011


AVOID BOTTLENECKS – DATA TRANSFER

MOVE calculations into database

Only transfer RESULTS

APPLICATION

LAYER

Calculation

DATABASE

LAYER Calculation

Classical Approach

Future Approach

© SAP AG 2011


AVOID BOTTLENECKS – PARTITIONING

SPREAD table contents across blades

Work on smaller sets of Data in PARALLEL

Initial

Data

Table 1Year A

Table 2Year A

Table 3Year A

Table ……

Table 1Year B

Table 2Year B

Table 3Year B

Table ……

Table 1…

Table 2…

Table 3…

Table ……

Table 1

Table 2

Table 3

…

New to SAP HANA Appliance

1.0 SPS02

© SAP AG 2011


DISCOVER NEW POSSIBILITIES

NEW APPLICATIONS

Old processes can be IMPROVED

Feasibility boundaries are SHIFTING

No need for AGGREGATION anymore

© SAP AG 2011


COMBINE BUSINESS & TECHNOLOGY

SAP Business Applications

Integrated Systems

Business Knowledge

SAP In-Memory Applications

Live Cache

BW Accelerator

HANA

Strong HARDWARE Partners

© SAP AG 2011


TODAY‘S SITUATION – CLASSIC EDW

Enterprise Data Warehouse (BW)

Corporate BI

Database

Local BI

Data Mart

DB

BWA

Data Mart

DB

NON SAP

Database

Local BI

SAP ERP 1

Database

SAP ERP 2

Database

Data Mart

DB

Local BI

© SAP AG 2011


SHORT TERM – SAP HANA Appliance 1.0


Corporate BI

Database

BWA

HANA

NON SAP

Database

Local BI

SAP ERP 1

Database

SAP ERP 2

Database

HANA

Local BI

HANA

Local BI

HANA

© SAP AG 2011


MID TERM – SAP HANA Appliance 1.0 SPS03(planned)


Corporate BI

HANA

NON SAP

Database

Local BI

SAP ERP 1

Database

SAP ERP 2

Database

HANA

Local BI

HANA

Local BI

HANA

NEW APPLICATIONS

© SAP AG 2011


VISION – SAP IN-MEMORY ComputingApplication Foundation


Corporate BI

SAP ERP 1

SAP ERP 2

New

APP 1

New

APP 2

HANA

NON SAP

© SAP AG 2011


SAP In-Memory ComputingProduct Strategy

In-Memory Analytics■ HANA 1.0 Real-time operational

analytics with HANA 1.0 ■ Complete BI Suite with BI 4.0

(Aurora) runs on Hana■ SAP Business by Design 2.6 runs

on in-memory

One Store for Data and Analytics

■ HANA only persistence layer for SAP Business Suite

■ SAP Business Suite optimized for In-Memory

■ Flexible real time analysis of operations at non-aggregated

level

■ Real-Time operational planning, simulation and forecasting: link

to execution

■ Reduced landscape complexity■ Value chain transformation

Capabilities

Benefits

Next generationapplications

■ SAP BW fully running on SAP HANA 1.0 SP03

■ SAP HANA 1.0 SP03 platform for In-Memory Apps

■ Business Suite runs on HANA 2.0■ SBOP 4.x (Aurora) unified modeling

with Hana■ Industry and LOB Business Analytics

Solutions “BAS”

Q4 2010“Renovation”

SAP HANA Appliance 1.0

2011-12“Innovation“

SAP HANA Appliance 1.0SP03 2.0

2012+“Transformation”

HANA 2+

© SAP AG 2011


How does SAP HANA compare to BWA?... Probably the wrong question, but let‘s give it a whirl...

TechnicallySAP HANA is far more than BWA

Standard interfaces (SQL, MDX)Real persistence layer (not just flat files) redo/undo logs, backup/recovery, ...

There is a lot of BWA/TREX in HANAColumn store; distributed computing; calculation engine

Beyond BWA:Row store (P*time); persistence, transactions (MaxDB), SQL Parser (P*time), ...

Data Models / ContentLife is simpler for BWA in the short term

You only load InfoCubes into BWATechnically trivial data model; Automatic creation of relations / join conditions

BWA has BW on topComplex logic? Do it in BWDefining the data model? Do it in BWAnalysis authorizations? Do it in BW

SAP HANA 1.0 is intended as a Data Mart (and BWA clearly is not) -> Flexibility (not tied to BW)

© SAP AG 2011


So what do customers get?An empty box „plus“

SAP HANA 1.0 is:The In-Memory Computing Engine

Including SQL and MDX interface, calculation engine, relational stores, persistence, ...SAP HANA Studio

Administration and Modelling

SAP HANA 1.0 does not have…Comprehensive Content The ABAP Data DictionaryNo ‘Application Server’ tier – it will be the application server tier in the future (native applications on HANA like SAP BPC)Front-End Tools (exception: MS Excel)

There are several working front-ends (not included with the In-Memory Appliance)Parallel Ramp ups: SAP BI 4.0, SAP BusinessObjects Analysis 1.1

One consistent administration and monitoring tool for all components

© SAP AG 2011


Creating Models in SAP HANAThe real world (I)

Select the ERP tables you needUnderstand the ERP data modelLocate all required tables

Transactional, master dataand texts...

Load ERP tables into SAP HANAInitial loadImplement some delta mechanism

SAP Landscape Transformation for RealtimeData Services: batch/near realtime...

Recreate table relationships in SAP HANAAll master data modelling (incl. Texts)Join conditions between tablesMore complex logic (may be a decision point for DataServices)

SQL script

© SAP AG 2011


Creating Models in SAP HANAThe real world (II)

Create Analysis AuthorizationsIf not everyone should see everything

No import of users from ERP (let alone authorizations)

Build report(s) on top of data modelWill you do part of the modelling above SAP HANA layer?

Select suitable reporting toolExcel, SAP BusinessObjects Explorer, SAP BusinessObjects Web Intelligence, SAP BusinessObjects Dashboards, SAP Crystal Reports, SAP Business Objects Analysis ...

Create the report

Verify that what you see is correctData in SAP HANA correct?Model correct?SAP HANA computing correctly?

© SAP AG 2011


Agenda

© SAP AG 2011





Lesson 5: Modelling


Lesson 6: Reporting


Lesson Objectives

After completing this lesson, you will be able to:Understand in-memory computing in SAP HANAUnderstand the structure of SAP HANA studioUnderstand how to configure perspectivesUnderstand how to create a package

© SAP AG 2011


Look&FeelSAP HANA Studio

© SAP AG 2011

The SAP HANA studio is delivered in the SAP HANA Appliance and provides an environment for administration , modeling and data provisioning. The studio is an eclipse based environment targeted for use by administrative (v1.0), domain expert – data architect users.

When you start the SAP HANA studio for the first time, you can decide on several perspectives. Perspectives are predefined UI-layouts for several application issues.

The Administration Console is used by SAP HANA administrators to administrate and monitor the engine. The Information Modeler view is used by BI architects. The documentation view links to the current available documentation.


Look&FeelAdministration View

NavigatorView

CheatSheets

© SAP AG 2011

We are starting with the Administration console view. The administration perspective is used to administer and monitor SAP HANA instances.

When you start SAP HANA Studio for the first time, there will be no connection to a SAP HANA system maintained yet. It is possible to integrate several systems into one Studio.

You can select a cheat sheet view via Window -> Show view -> other

Help -> Cheat Sheets creates an additional view on the right side. Using view menu you can choose Adding system and Folders. Now you get the information how to create a new folder or add a new system into the navigator view.

To integrate a SAP HANA system into the studio you need to know the server where the engine is running and the instance number. You need to know a user/password combination as well to get a connection to the instance.

You can import (-> file -> import -> SAP in-memory computing studio -> landscape) a system landscape which has been exported before from another/same studio.

Note: to get the imported landscape working you need to insert the passwords for all connections again.(Mark the system -> properties -> connection properties)


Look & FeelNavigator View - Default Catalog

© SAP AG 2011

After the system has been integrated on the left side you will find the navigator view. Here all systems which have been integrated (manual or via import) are listed.We will have a closer look to the tree structure each system has.

The physical tables are located in the Navigation Tree under the Default Catalog node. Expand this node and one will find a list of schemas. Schemas are used to categorize tables according to customer defined groupings

NOTE: During metadata import one defines which schema to hold created tables. ( Currently the replication server loads the meta data into the system schema.) Different schemas can be quite useful for grouping tables into categories that have meaning to users. This simplifies the process of identifying which tables to use when defining Information Models. One model can incorporate tables from multiple schemas. The schemas do not limit your modeling capabilities.

The created column views are always located in schema _SYS_BIC, their meta data in schema _SYS_BI.

The physical tables are the only storage area for data within SAP HANA. All the information models that will be created in the modeler will result in database views. Therefore SAP HANA does not persist redundant data for each model and does not create materialized aggregates.


Look & FeelSystem Monitor

© SAP AG 2011

There is an integrated system monitor which gives you an administration view about the system landscape.

When you use the system overview button all systems which are listed in the navigator tree are listed by default in the system monitor overview. You get the most important information about your systems. Which information is shown can be configured with configure viewer.

It is also possible to configure which systems will be shown in system overview. Perhaps you have seen that in the slide here we have several systems twice. By default you get for each Connection (System/User) an entry in the overview.Use system filter to configure the monitor.


Look & FeelPre-Delivered Administration Console

NavigatorView

PropertiesView

AdministrationView

© SAP AG 2011

The Administration console is pre-delivered by SAP.

You can access the administration console

by selecting the Administration icon in the top right corner

double click on the system in the system monitor

double click on the system in the navigator view

In the administration console you are administrating HANA instances.

starting and stopping the instance

backup/recovery of the instance

monitor the system

configure the engine instance

doing the problem analysis


Look & FeelPerspectives are built up based on views

Fast Perspective

SwitchChooseperspectivefrom main

menu

© SAP AG 2011

When you want to create data models in HANA you have to switch to the information modeler perspective in the Studio.

With Window -> Open Perspective -> Information Modeler you can switch to the Quick Launch of the Information Modeler.

On the right top edge you find the fast perspective switch.

The studio offers other perspectives e.g. for debugging, resource and team synchronizing.


Look and FeelInformation Modeler

© SAP AG 2011

You are currently looking at the information modeling section of the SAP in-memory computing studio.The SAP in-memory computing studio is delivered in the SAP HANA Appliance and provides also an environment for modeling and data provisioning. The Information Modeler is an eclipse based environment targeted for use by the domain expert – data architect.

Note: The Quick launch of the information modeler is open by default for the first instance in the navigation tree.If you want to change to another system use the left button -> Choose Connection.

In the center of the screen you see a quick launch tab that allows the user to quickly jump to various sections of the tool.

Create new views (Information Models) and analytic privileges

Import and export source schemas, models, data

Configure the tool

Access documentation of the HANA On the left of the screen you see the navigation tree. Note that there are two main sections in the navigation tree. The Default Catalog node navigates to the physical tables, views, etc. The Information Models node navigates to Attribute Views, Analytic Views and Calculation Views


Look&FeelNavigator View - Information Models

Information Models organizedin Packages

Attribute Views, Analytic Views,Calculation Views, Analytic Privilegesorganised in folders

© SAP AG 2011

The Information Modeler node displays the data from a data modeling perspective. Here the user will create Attribute Views, Analytic Views, Calculation Views and Analytic Privileges.

The physical tables are the only storage area for data within SAP HANA. All the information models that will be created the modeler result in database views. Therefore SAP HANA does not persist redundant data for each model and does not create materialized aggregates.


Look & FeelPerspectives are built up based on views

VIEWS!

© SAP AG 2011

Notes:

Views are the basic screen elements. A collection of displayed views combined with their placement within the screen builds a perspective.

Each view can be moved around via drag & drop.


Look & FeelTips & Tricks

RESET PERSPECTIVE

will restore yourscreen!

© SAP AG 2011

Notes:

Reset your perspectives will restore the screen to the default layout…


Summary

You should now:Understand in-memory computing in SAP HANAUnderstand the structure of SAP HANA studioUnderstand how to configure perspectivesUnderstand how to create a package

© SAP AG 2011


© SAP AG 2011

Agenda





Lesson 5: Modelling


Lesson 6: Reporting


Lesson Objectives

© SAP AG 2011

After completing this lesson, you will be able to understand the:Architecture of SAP HANA 1.0Persistence Layer of SAP HANA 1.0Concept of Backup & Recovery


© SAP AG 2011

Agenda

Lesson 3:Architecture

Backup & Recovery

Persistence Layer


ERP

Architecture OverviewIn Memory Computing Engine (IMCE) and Surroundings

LogERP DB

In-Memory Computing Engine

Clients (planned, e.g.) BI4 Explorer

DashboardDesign

SAP BI4 universes(WebI,...)

Request Processing / Execution Control

MS Excel

BI4 Analysis

SQL Parser MDXSQL Script Calc Engine

Transaction Manager

Session Management

Relational EnginesRow Store Column Store

Persistence LayerPage Management Logger

Disk StorageLog VolumesData Volumes

AuthorizationManager

Metadata Manager

IMCE Studio

Administration Modeling

LoadController

Replication Agent

Replication Server

SAP Business Objects BI4

Data Services Designer

SBO BI4 servers

( programfor client)

SBO BI4 Information Design Tool

Other Source Systems

SAP NetWeaver

BW3rd Party

Data Services

© SAP AG 2011

Of the components displayed on this slide, not all are part of HANA. Business Objects Enterprise, the ERP system, the clients etc. are optional components whose presence in the system landscape depends on the customer scenario.

The components listed here are:

The in-memory computing engine itself, which hosts the actual data stores, a persistence layer, a calculation/execution engine, interfaces and other components

The in-memory computing studio which is a front-end delivered with HANA which enables administration of the in-memory computing engine and modeling for the engine.

An ERP system in which a replication agent is installed to enable data transfer from ERP to HANA

Database clients (JDBC, ODBC, ODBO) which allow client tools to connect to HANA.

Optional components

a NetWeaver BW system or third party systems which can be connected to HANA via SAP BusinessObjects Data Services

a BusinessObjects Enterprise system with Data Services installed.

Client tools for reporting off HANA, e.g. MS Excel, SAP BusinessObjects Analysis Office, SAP BusinessObjects BI reporting tools. These tools might need components in a BusinessObjects Enterprise system (such as Information Design Tool).

In the following slides we take a look at several usage aspects of HANA such as data loading, modelling and reporting and discuss which parts of this setup are important for these aspects.


ERP

Architecture OverviewThe engine itself

LogERP DB

Clients (planned, e.g.) SBOP Explorer 4.0

XcelsiusSAP BI universes

(WebI,...)

MS Excel

SBOP Analysis

IMCE Studio


LoadController

Replication Agent

Business Objects Enterprise


SBO server

programsfor clients

SBO Information

Design Tool


SAP NetWeaver

BW3rd Party

Data Services


Request Processing / Execution ControlSQL Parser MDXSQL Script Calc Engine

Transaction Manager

Session Management





Metadata Manager

Replication Server

LoadController

© SAP AG 2011

At the top is the connection and session management which creates and manages sessions and connections for the database clients. For each session a set of parameters is maintained such as e.g. auto commit settings or the curernt transaction isolation level.The client requests are analyzed and executed by the set of components summarized as Request Processing and Execution Control. Once a session is established, database clients typically use SQL statements to communicate with the in-memory computing engine. For analytical applications the multidimensional query language MDX is supported in addition.Features such as SQL Script, MDX and planning operations are implemented using a common infrastructure called calc engine.At the heart of the in-memory computing engine are two relational engines. The row and the column store. These relational engines act as databases. Both are in-memory databases, that is, their primary data persistence is based in RAM.The row store stores data in row based way. In this respect it behaves like traditional relational databases: data is stored and retrieved in records. A major diffenrence to traditional databases is that all data is always kept in RAM.The column store is a relational column based in-memory data engine. That means data is stored and retrieved in columns. This is an optimal concept for analytical queries. The concept is known e.g. From SAP netweaver BW Accelerator (BWA) where this technology has already demonstrated its potential.Even though the relational engines are memory based, a persistence on less volatile media is required for reasons of data safety. Otherwise a power cut or OS reboot would permanently erase all data in the database. The persistency layer handles page management and logging (redo and Undo logs) and permanently stores data in a disk storage. This storage has seperate volumes for data and log.The engine also has a component called transaction management. Transaction management is required in order to provide consistent views of the data at any given point in time (an ongoing transaction must only see that part of the data that was committed before that transaction was started).Replication Server and Load Controller are the engine-side part of the Sybase replication manager.


ERP

Architecture OverviewLoading Data into HANA

LogERP DB



Transaction Manager

Session Management





Metadata Manager

IMCE Studio

Replication Agent



SBO BI4 servers


SBO Information

Design Tool


SAP NetWeaver

BW3rd Party

Data Services


DashboardDesign


MS Excel

BI4 AnalysisAdministration Modeling

LoadController

Replication Server

© SAP AG 2011

One of the promises of HANA is to deliver real-time analytic insight on vast data volumes.

For the real-time aspect, data provisioning in real time is required. This is the task of Sybase Replication Server. Tables from the ERP system are initially loaded into HANA. All subsequent changes to these ERP tables are immediately replicated into the HANA server. To this end, replication server makes use of the database logs in the ERP system.

There is a tool that helps selecting the tables to be loaded and replicated. This tool is integrated into the In-Memory Computing Studio.

Replication Server only allows connecting one SAP ERP system to HANA. Some additional requirements apply regarding the ERP system such as server OS, DBMS system, ERP version, SAP kernel and unicode state (only unicode is supported). Note: 1513496 gives information about Hana restrictions.

Systems not fullfilling these requirements can be accessed via data services. This requires a BusinessObjects installation, with a data services server and data services designer on the client.

Note 1522554 NetWeaver Support Package requirement for Data Services SAP Extractor support .

Note: for practical purposes it will probably not be reasonable to connect to several ERP systems with one HANA box (one via replication, the other(s) via data services) for obvious reasons (same tables existing in all the ERP systems etc).

Note: Loading from NetWeaver BW into HANA via data services technically is an application of OpenHub.


SLT Replication Concept: Trigger-Based ApproachArchitecture and Key Building Blocks

SAP HANA systemSLT system (NW7.02)

Application Tables

Source system

Write Modules

ControlerModules

DBConnection

RFCConnection

Read Modules

LoggingTables

Application Tables

DB Trigger

Initialization of datareplication based on DB trigger

and delta logging concept(as with NearZero downtime

approach)

Flexible and reliable replicationprocess, incl. data conversion

(as used for TDMS and ByDesign) SLT can also be installed on source

system or Solution Manager

Fast data replication via DB connection

(no other interaction)

© SAP AG 2011


ERP

Architecture OverviewData Modeling

LogERP DB



Transaction Manager

Session Management





Metadata Manager

IMCE Studio


Replication Agent



SBO BI4 servers


SBO Information

Design Tool


SAP NetWeaver

BW3rd Party

Data Services


DashboardDesign


MS Excel

BI4 Analysis

LoadController

Replication Server

© SAP AG 2011

Once tables are created in HANA and loaded from the source system, the semantic relationships between the tables need to be modeled.

In an ERP system, these relationships are modeled via database views and ABAP code. In HANA, these relations initially do not exist at all.

Modeling can be done in several places (bottom-up description):

If data services is used to create and fill the table, first modeling decisions can be made here.

Data models can be created within the In-Memory Computing Engine. Models are stored in form of views and associated metadata in the engine. The front-end tool to create these models in the In-Memory computing Studio (Information Modeler within that tool).

Depending on the front-end tool used to retrieve data from the In-Memory Computing Engine, further modeling decisions can be made in universes (SAP BusinessObjects Information Design Tool) or other semantic layers.


Clients (planned, e.g.)

ERP

Architecture OverviewReporting

LogERP DB



Transaction Manager

Session Management





Metadata Manager

IMCE Studio


Replication Agent



SBO BI4 servers


SBO Information

Design Tool


SAP NetWeaver

BW3rd Party

Data Services

BI4 Explorer

DashboardDesign


MS Excel

BI4 Analysis

LoadController

Replication Server

© SAP AG 2011

In reporting, client tools create queries against the database. Where the actual query is generated depends on the tool used.

This slide list some of the possible reporting tools.BusinessObjects Explorer will directly create a call against a HANA interface. Excel will also directly request data via MDX. Front-end tools which report against Universes will have the SQL request against HANA created in the universe layer. BI4 Analysis reports against BICS.

Please note that at the time of creating these transparencies, it is not yet decided which front-end tools will be supported in combination with HANA. The front-end tools listed in these slides are candidates.

The following client side drivers are delivered with HANA:

JDBC ( SQL)

ODBC ( SQL)

ODBO (short for OLEDB for OLAP MDX)

Which of the drivers will be used depends on the front-end tool used (and sometimes even the way in which the front-end tool is used).


ERP

Architecture OverviewAdministration

LogERP DB



Transaction Manager

Session Management





Metadata Manager

IMCE Studio


Replication Agent



SBO BI4 servers

(program for client)

SBO Information Design Tool


SAP NetWeaver

BW3rd Party

Data Services


DashboardDesign


MS Excel

BI4 Analysis

LoadController

Replication Server

© SAP AG 2011

For Administration of the HANA, the In-Memory Computing Studio has an administration component.

Tasks offered by the studio include (but are not limited to):

Starting/stopping the In-Memory Computing Engine (upon start, the in-memory stores are reconstructed from the persistence layer)

User administration including creating/deleting users and authorizations

Table administration, including creating indexes or some part of the configuration for data replication

Creating or replaying a backup


© SAP AG 2011

Agenda


Backup & Recovery

Persistence Layer


Persistence Layer in In-memory Comp. Engine

Why does an in-memory database need a persistence layerMain Memory is volatile. What happens upon

Database restart?Power outage?...

Data need to be stored in a non-volatile way

Backup and restore

IMCE offers one persistence layer which is used by row store and column storeRegular “savepoints” full persisted image of DB at time of savepointLogs capturing all DB transactions since last savepoint (redo logs and undo logs written)

restore DB from latest savepoint onwardsCreate Snapshots ( backup)

Purpose and Scope

© SAP AG 2011

The persistence layer ensures that changes are durable and that the database can be restored to the most recent committed state after a restart.The persistence layer stores data in disk volumes that are organized in pages. Different page sizes are supported, for example 8k, 16k, 64k, 512k, and 4M. Data is loaded from disk and stored to disk page wise. Data pages and before images (Undo log pages) are written on the data volumes. After images (redo log pages) are written on the log volumes.

When data/log entries are written to the disk?

Redo log entries are written to log volumes at latest when a transaction ends

changed data itself is written at latest when a savepoint is performed.

Note: Savepoint is a too complex operation to fully cover here.

An excellent description is given in section 8.5 of the Architecture Bluebook for the In Memory Computation Engine which is accessible in the internal SAP network at https://portal.wdf.sap.corp/irj/go/km/docs/guid/506044d8-61b7-2d10-4698-ff22eb27ec23


SAP In-Memory Computing Engine

Persistence Layer in In-memory Comp. Engine

Memory

Data

Persistent Storage

Regular automaticsavepoints

Information aboutdata changes

LogVolume

DataVolumes

© SAP AG 2011

Data is saved to disk in intervals

Data:

Replicated business data

Additional information,such as modelling data

Kept in-memory to ensure maximum performance

Log:

Information about data changes

Directly saved to persistent storage when transaction is committed

Cyclical overwrite

Savepoint:

Changed data and log is written from memory to persistent storage

Automatic

At least every 10 minutes (customizable)


Persistence Layer in In-memory Comp. EngineSavepoint – writing data in IMCE

© SAP AG 2011

DATA&

Undo

DATA&

Undo

Page Buffer

Log queueData Cache Other

Data PagesData pagesof virtual files

Savepoint Coordinator

DATA&

UndoDATA

&Undo

4712

4713

Converter

The persistence layer (by the savepoint coordinator) periodically writes savepoints to disk. The time interval for writing savepoints can be configured for example to 5 minutes. Savepoints are self-contained consistent states of the database that may be loaded without reading the log volumes.During a savepoint:

all data which has been changed since the last savepoint is marked and will be written to disk. The data which belong to the last completed savepoint won‘t be overwritten (shadow page concept). the redo log entries are written to Log volumeConverter table (mapping of logical pages to physical pages in savepoints)Row store check point (persisting main part of row store data)

The savepoint consists of three phases:In phase one, all modified pages are determined that are not yet written to disk. The savepoint coordinator triggers writing of these pages. In phase two, the write operations for phase 3 are prepared.

a consistent change lock is acquired no write operations are allowed. All pages are determined that were modified during phase 1 and written to a temporary buffer.List of open transaction is retrievedRow store information for uncommitted changes made during phase 1 is written to diskCurrent log position is determined (log position from which logs must be read during restart)Change lock is released

In phase 3, all data is written to disk. Changes are allowed again during this phase.Temporary buffers created in phase 2List of open transactionsRow store check point is invokeLog queue is flushed up to the savepoint log positionRestart record is written (containing e.g. the savepoint log position)


Persistence Layer in In-memory Comp. EngineSystem Restart

© SAP AG 2011

Reboot or Power failure deletes in-memory dataSystem is normally restarted („lazy“ restart to keep downtime short: tables with preload flag + subsequently requested tables are loaded first)System is restored to the state just before the failure (except non-committed transactions)Used for recovery:

Last data savepointLog between the last data savepoint and the time of failure(contains the data changes of all commited transactions up to that point)

Time

Data savepointto persistent storage

1Log written

to persistent storage(committed transactions)

2Power failure

3

Actions during system restart

Last savepoint must be reloaded plus:

Undo logs must be read for uncommitted transactions saved with last savepoint (stored on the data volume)

Redo logs for committed transactions since last savepoint (stored on the log volume)

Complete content of row store is loaded into memory

Column store tables may be marked for preload or not

Only tables marked for preload are loaded into memory during startup

If table is marked for loading on demand, the restore procedure is invoked on first access


© SAP AG 2011

Agenda


Backup & Recovery

Persistence Layer


Backup & Recovery

Data backup:From persistent storage to external backup destinationsUsing database functions (SAP in-memory computing studio)

Log backup:Not supported in SAP HANA 1.0

Configuration backupManual copy of configuation files to external backup destination

Persistent Storage

LogVolume

DataVolumes

conf

Configuration Backup

Save to External Backup Destinations

© SAP AG 2011

Backup:

User starts backup via SAP in-memory computing studio

Database triggers a global database snapshot (backup manager in master name server)

Commits for all transactions on hold

Master name and index servers create snapshots of their persistent storage

Commits allowed again

Master name server and index servers write snapshots to backup destinations

SAP in-memory computing studio monitors progress

Manual configuration backup (recommended: every time a data backup is carried out):

/usr/sap/<SID>/SYS/global/hdb/custom/config

/usr/sap/<SID>/HDB<instance no>/<hostname> (without sub-directories!)


Backup & Recovery

Disk failure (data volumes are damaged)System is restored to the state just before the failure (except non-committed transactions)

Used for recovery:Last data backupLog since the last data backupAssumption: log area undamaged, all log entries still available (not yet overwritten)

Time

Data backupto external backup

destination

1Log written

to persistent storage(committed transactions)

2Disk failure

(data volumes)

3

Recovery scenario – Disk Failure (Data Volume)

© SAP AG 2011

Recovery:

Master name server is restored, then triggers restore of the other index and name servers.

If log is available, transactions are restored.


Data Backup

Log Backup

Recovery to last Data Backup

Point in Time Recovery

Backup & Recovery

SAP HAnA 1.0

Recovery to status before crash ( )If log is not damaged

Feature Overview

© SAP AG 2011


© SAP AG 2011

Summary

In this lesson, you learned about the:Architecture of HANA 1.0Persistance Layer of HANA 1.0Concept of Backup & Recovery


© SAP AG 2011

Agenda





Lesson 5: Modelling


Lesson 6: Reporting


© SAP AG 2011

Agenda

Lesson 4:SAP BusinessObjects Data Services

SAP LT Replication Server


Lesson Objectives

© SAP AG 2011

After completing this lesson, you will be able to:Import metadata from SAP ERP into the SAP HANA DatabaseCreate a simple 1:1 SAP BusinessObjects Data Services batch job and dataflow to extract data from your SAP ERP system and load it into the SAP HANA Database


SAP BusinessObjects Data Services 4.0 and SAP HANA

In-Memory Computing Engine (ICE)

SAPERP

Any Source

BW

Modeler

Data Load

Metadata

Repository Server

Open Hub

SAP BusinessObjectsData Services 4.0

HANA

Designer and Management

Console

Data Services is the engine to load data into ICEThe HANA Modeler will generate initial loading jobs

Modeler will use Data Services to browse and ‘import’ external metadata Modeler will generate initial flows to load data into NewDB tablesFurther modifications to flows done via Data Services Designer

Not yet working

© SAP AG 2011

The SAP HANA Appliance is a hardware and software combination that integrates a number of SAP components (for example, HANA DB, Modeler, Data Services) delivered as an optimized hardware appliance in conjunction with leading hardware partners.

SAP HANA provides a flexible, data source agnostic, multi‐purpose appliance that has many deployment options. For example, customers can directly analyze large volumes of SAP ERP, SAP BW, or non‐SAP data in “real real‐time” without having to create any form of materialized views. This is possible because the software intelligently leverages the native multi‐core support and massively parallel processing capability of the appliance to provide a data source agnostic high performance analytical engine.


Process Flow: SAP HANA and Data Services

© SAP AG 2011


Process Flow: SAP HANA

© SAP AG 2011


Basic Data Services Connection Types

Connectivity options already available in Data Services 3.x:Read tables via ABAP dataflows

For large volumes and transformations inside the SAP source (joins, lookups, and so on)ABAP program generated & executed Data transported via file

RFC_READ_TABLE (SAP Table inside a regular dataflow)For single tables, few lines only

RFC/BAPIs function callsTo utilize SAP logic instead of reading tables and designing the logic in Data Services again (limited number of rows per call)

IDOCsReal-time messages mostly

New to Data Services 4.0Improved ABAP integration to ERPODP – Operational Data Provider

New SAP delivered API implemented on the ERP side

© SAP AG 2011


Full extractor support through ODP

Full extractor support through ODP data replication API : Data Services can use this API to get initial and delta loads, the data can be streamed to Data Services.

Benefits:Only “released” extractors are shown to Data Services. – Business Suite team releases standard extractors as they are certified for ODP– Customer can release custom extractors (created in tx RS02)Delta support through the delta queues (same mechanism as used by BW today)Data is streamed from SAP to Data Services. No ABAP programs created, no staging in files.

Requirements Support package is need on the ECC/NetWeaver.Standard extractors need to be “released” by the Business Suite team

* ODP = Operational Data Provider. NOTE: Release in HANA timeframe on ECC 6.0 EhP1 – Ehp5 is a limited, DS-specific subset of overall ODP functionality to be released with ECC 6.0 EhP6

© SAP AG 2011

* ODP = Operational Data Provider. The full ODP feature will NOT be back ported to NW 7.0 releases, only the data replication API that is needed by Data Services to access the BW datasources.


Create a connection to a SAP ERP target

Create a new DataStore of type “SAP Applications” with specific connection details

© SAP AG 2011


Setup Information Modeler to communicate with Data Services (Configure Import Server)

Click “Import” to import meta data via Data Services or use the menu

© SAP AG 2011

Notes:

This is an example ......


SAP HANA StudioImporting meta data from an ERP System

Select the import of “Source Objects” into a connected target

system

1.2.

© SAP AG 2011


Choose one of the maintained connections

Connections of DataStoretype “SAP Applications”are imported from the specified DataServices

repository

© SAP AG 2011


Select Objects for importSearch vs. hierarchy drill-down

There are two possibilities to select objects for importSearch for objects via the direct input fieldUse applications hierarchy to drill down to a certain table

© SAP AG 2011


Select In-Memory Computing Engine (ICE) target schema for the metadata import

“RKT” catalog in In-Memory Computing

Engine empty

© SAP AG 2011


Validate the target structure

1.

2.Validate the target structure

© SAP AG 2011


View the newly created target structure in the SAP HANA Studio

Table creation status in the deployment log

1.

2.

3.

Refresh the Tables section in the “RKT” catalog and

double click the table to see the structure

2.

© SAP AG 2011


Process Flow: Data Services

© SAP AG 2011


Import the created table structure into Data Services

For modeling of jobs and data flows within SAP Business Objects Data Services the created table structure needs to be imported. The subsequent steps are necessary:

© SAP AG 2011


Create and execute a Data Services job to populate HANA

For creating and executing a simple Data Services job with a 1:1 transfer from the source SAP ERP system to the target HANA system, the following steps are required:

Create a new batch job within Data Services (this is the high-level executable to be started on the fly in Data Services or to be scheduled on a regular basis)Create a new data flow, containing the source table from the SAP ERP system, a query object realizing a basic 1:1 mapping, and the target table which already exists within the HANA system)Execute the newly created Data Services job and preview the records with the in SAP In-Memory Computing Studio

© SAP AG 2011


Create and new Data Services Job and data flow with simple 1:1 mapping

Create a simple job and dataflow with a 1:1 mapping from the SAP EPR source table to the

HANA target

Simple 1:1 query object

ABAP dataflow recommended for large data sets

© SAP AG 2011


Execute the job to populate the HANA target table and monitor the load

Monitor load progress

© SAP AG 2011


View the uploaded data within the In-Memory Computing Studio

© SAP AG 2011


© SAP AG 2011

Summary

In this lesson, you learned:How to replicate metadata from an SAP ERP system via the In-Memory Computing Studio and SAP Business Objects Data Service into HANAHow to use the replicate metadata to fill it with content, i.e. pulling transactional data out of an SAP ERP system and pushing it into HANA with a SAP Business Objects Data Services job


Agenda

Lesson 4:SAP BusinessObjects Data Services

SAP LT Replication Server

© SAP AG 2011


Lesson Objectives

© SAP AG 2011

After completing this lesson, you will be able to:Understand the architectural foundation of LT Replicator and itstechnical pre-requisites.Configure LT Replicator for connectivity to the source SAP ERP system and the target SAP HANA Database.Configure data provisioning in SAP HANA Studio and trigger an initial load and/or replication.


LT Replication Server for SAP HANA Appliance leverages proven SLO Technologies

Application Lifecyle MgmtSLO technologies have been used for over 10 years in several hundredprojects per year

Key offerings foster SAP‘s Application Lifecycle Mgmt concept

LT replication Server as a new usecase leverages several SLO technologies

© SAP AG 2011


LT Replication Server for SAP HANA Appliance

Key benefits of trigger based approachAllows real-time (and scheduled) data replication, replicating only relevant data into the SAP HANA Database

Ability to migrate data into the SAP HANA Database format whilereplicating data in real-time

„Unlimited“ release coverage (SAP R/3 4.6C onwards) sourcing data from SAP ERP (and other ABAP based SAP applications)

Leverages proven SLO technology (Near Zero Downtime, TDMS, SAP LT)

Simple and fast set-up of LT replicator (initial installation and configurationin less than 1day) and fully integrated with SAP HANA Studio (as of SPS02)

© SAP AG 2011


LT Replication Concept: Trigger-Based Approach Architecture and Key Building Blocks

SAP HANA DatabaseLT Replication Server

Application Tables

Source system

Write Modules

ControlerModules

DBConnection

RFCConnection

Read Modules

LoggingTables

Application Tables

Efficient initialization of datareplication based on DB triggerand delta logging concept(as with NearZero downtime approach)

Flexible and reliable replicationprocess, incl. data migration(as used for TDMS and SAP LT)

Fast data replication via DB connectLT replication functionality is fullyintegrated with SAP HANA Studio

LT replication server does not have to be a separate SAP system and can run on any SAP system with SAP NetWeaver 7.02 ABAP stack (Kernel 7.20EXT)

DB Trigger

© SAP AG 2011


LT Replication Concept: Trigger-Based ApproachKey Building Blocks in Detail – Source System

DB Trigger and Table-Based Delta Logging:Only relevant tables considered for DB recording

All relevant changes are recorded in logging tables

Replicated changes are deleted from logging tables

Recording and replication possible for all table classes (e.g. cluster tables)

Read Module:Collects data changes

Declustering of table classes into transparent format

Source system

Read Modules

LoggingTables

Application Tables

DB Trigger

Trigger-based approach has no measureableperformance impact in source system

© SAP AG 2011


Leveraging proven SLO technology, LT replicationserver provides a flexible and reliableinfrastructure to manage the entire process

LT Replication Concept: Trigger-Based ApproachKey Building Blocks in Detail – LT Replication Server

Controler Module:Ensures mapping between HANA DB structure and DB structure of source system

Provides ability to conversion/migration values (e.g. date fields intostrings)

Includes features to manage entire replication process in a holisticmanner, e.g. provides scheduling options to determine the frequencyof data replicationTriggers activities of WRITE module

Write Module:Writes data through DB connection to SAP HANA system

Offers flexibility to switch from single operation (insert – update – delete) to array operations LT Replication Server

Write Modules

ControlerModules

System Requirements:

- SAP Netweaver 702 with Kernel 7.20EXT (currently only available on linux 64 or win64)

- Filesystem: 100 GB- RAM: 16-32 GB- CPU: 2-4 cores- Recommended number of background jobs: 10

© SAP AG 2011


Technical Requirements and System Set-Up Information for LT Replication Server

SAP HANA systemLT Replication ServerSource system


- SAP Basis: Netweaver 702 with Kernel 7.20EXT (currently limited platform availability)

- Filesystem: 100 GB- RAM: 16-32 GB- CPU: 2-4 cores- Recommended number of background jobs: 10

DBConnection

RFCConnection


- SAP Basis 4.6C and higher- All data bases

Installation:

- respective DMIS 2010 version- Minimum support pack level: latest available

Installation:

- Addon DMIS 2010_1_700- Minimum support pack level: SP04

(planned with release of HANA SPS02)

Installation:

- HANA SPS02: includes LT replicationfunctionality fully integrated into the UI ofthe HANA modeler

Basic Configuration:

- Define RFC connection to source system- Define DB connection to HANA system- Define max. number of jobs to be used for data replication


- Optional: define separate table spacefor logging tables

- Define RFC user with appropriate authorization


- Create a DB user (if required)

LT replication server can run on any SAP system with SAP NetWeaver 7.02 ABAP stack (using SAP Kernel 7.20EXT), for example on Solution Manager 7.1 or the source system – it does not have to be a separate SAP system!

© SAP AG 2011


LT Replication Concept: Trigger-Based Approach Configuration of LT Replication Server

RFC Connection

Table space (optional)

Replication mode

Connection to HANA

Number of jobs

A schema defines the configuration ofthe data replication for a source system

© SAP AG 2011


LT Replication Concept: Trigger-Based ApproachSet-up of Data Replication in SAP HANA System (1/2)

Choose Data Provisioning to launch HANA Modeler UI

1. Select source system as defined in LT replication server, related system information and schema will be displayed

2. Use button Load and / or Replicate to set-up the data replication

3. Use button Stop Replication to end or to restart replication

© SAP AG 2011


Select source system

LT Replication Concept: Trigger-Based ApproachSet-up of Data Replication in SAP HANA System (2/2)

Load: starts the initial load of the data from the source system. The data replication is a one-time event - no logging table and triggers are created in the source system.

Replicate: starts the initial load procedure and delta replication as configured in related schema on the LT replication server.

Stop Replication: Stops any current Load or Replicate processes.

Select relevant tables

© SAP AG 2011


Summary and Key Take Aways

LT replication concept is based on the proven SLO technology (used for NearZeroDowntime, TDMS, etc.) used by hundreds of customers with large DBs.

It provides a holistic concept and valuable features to manage the data replication into SAP HANA very efficient and reliable

LT replication server is the ideal solution for all HANA customers who need real-time (and non-realtime) datareplication sourcing from SAP ERP systems into HANA

© SAP AG 2011


© SAP AG 2011

Summary

In this lesson, you learned:What’s required to setup LT Replicator in your system landscape.How to configure LT Replicator to establish connectivity to the source SAP ERP system and the target SAP HANA Database.How to configure the SAP HANA Studio to launch an initial load and/or replication.


© SAP AG 2011

Agenda





Lesson 5: Modelling


Lesson 6: Reporting


Lesson Objectives

After completing this lesson, you will be able to:Understand the purpose of the Information ModelerDescribe the levels of modeling in HANA 1.0Create and display data for an Attribute ViewCreate and display data for Analytical ViewCreate and display data for an Calculation ViewUnderstand the purpose of the Export / Import Functionality

© SAP AG 2011


Aim: Enable Plan/Actual Comparison in SAP HANA, Using Data From COPA

Actual Data Planned Data© SAP AG 2011


Agenda

© SAP AG 2011

Lesson 5:Introduction to CO-PA Scenario

Introduction to Information Modeler

Levels of Modeling

- Attribute Views

- Analytic Views

- Calculation Views

- Export & Import


CO-PA Background

Profitability Analysis (CO-PA) enables you to evaluate market segments, which can be classified according to products, customers, orders or any combination of these, or strategic business units, such as sales organizations or business areas, with respect to your company's profit or contribution margin.

The aim of the system is to provide your sales, marketing, product management and corporate planning departments with information to support internal accounting and decision-making.

Revenue

Costs

Loss

Profit

Sales quantitySales rev.

Direct material costsVariable production costs

Contribution margin IMaterial overhead Fixed production costs

Contribution margin IIVariances

Contribution margin IIOverhead costsOperating profit

Determine and analyze the profitability of market

segments

Sales OfficeBusiness Unit

Reporting Dimensions

Region Customer

© SAP AG 2011


COPA Storage Architecture

Join ProfitabilitySegment Number

Characteristics

CE4xxxx-Segment Table

Fiscal yearPlan/act. Indic.Plan VersionRecord Type

Value Fields

CE3xxxx-Summarrization Level

CE2xxxx

ActualLine Items

CE1xxxx

Plan Line Items

e.g. xxxx = IDEA

© SAP AG 2011

You can view an operating concern (represented by its segment table and segment level) analog to an InfoCube. There is one dimension table (the segment table) and a fact table (the segment level). Contrary to the fact table of an InfoCube, the key of the segment level does not only contain the key field from the segment table, but also some other keys (e.g. the record type).

Characteristics in CO-PA match characteristics (or attributes) in InfoCubes and value fields can be viewed as key figures with additive aggregation in every characteristic.

Summarization levels for an operating concern play the role of the aggregates for an InfoCube with the difference being that aggregates for InfoCubes are maintained together with the InfoCube itself (that is, all aggregates will contain exactly the same figures than the underlying InfoCube at any time), while summarization levels are updated periodically (in most cases once every day).

CO-PA line items are similar to lines in the ODS. You can view them as lines in communication structure just before being posted to an InfoCube. In costing based, as shown, the line items stored in the CE1xxxx and CE2xxxx tables. In Account-based Profitability analysis, the line items are stored in the CO tables (COBK, CO Header and COEP, CO Line item).


HANA and CO-PA as an example

SDSD FIFI COCO--PCPC COCO--OMOMCost centers Orders Processes Product costingPosting to a G/L accountBilling document

CE1XXXXCE1XXXX

CE2XXXXCE2XXXX

CE3XXXXCE3XXXX

CE4XXXXCE4XXXXERPERP

MDX

SQL


Other ApplicationsReal Time Replication Service

BICSSAP BusinessObjects

HANA HANA

In Memory Database

Calc & Planning Engine

Data ManagementData Services

HANA Modeling Studio

Application TableApplication Table

© SAP AG 2011


HANA and CO-PA as an example

SDSD FIFI COCO--PCPC COCO--OMOMCost centers Orders Processes Product costingPosting to a G/L accountBilling document

CE1XXXXCE1XXXX

CE2XXXXCE2XXXX

CE3XXXXCE3XXXX

CE4XXXXCE4XXXXERPERP

Application TableApplication Table

But how can we find the tables and there dependencies for all of the ERP applications?

© SAP AG 2011


HANA - Table Relations in ERP

ERPERP

MoreMore thanthan 50.000 50.000 applicationapplication tablestables

CanCan bebe analyzedanalyzed withwith transactiontransaction codecode SD11 SD11

© SAP AG 2011

Displaying/Printing Data Models Displaying Data ModelsThe procedure to be used varies according to whether you know the full name of the data model, only part of the name of the data model, or whether you do not know the name at all:Complete Name Known1. On the Data Modeler: Initial Screen, enter the name of the data model in the Modeling object field.2. Under Selection, choose Data model.3. Choose Display. The Display Data Model: Definition screen appears.Part of Name Known1. On the Data Modeler: Initial Screen, select Data model under Selection.2. Enter the part of the name you know in the Modeling object. input field. Use * to represent the part

you do not know (for example, uni*).3. Click on the arrow to the right of the entry field.4. A hit list of all objects corresponding to the pattern you entered appears. To copy the name of the

data model you require, select the data model by clicking it and activating the Choose pushbutton. The name now appears on the initial screen.

5. Choose Display. The Display Data Model: Definition screen appears.Name Unknown1. Leave the input field Modeling object empty on the Data Modeler: Initial Screen.2. Under Selection, choose Data model.3. Choose Search. The relevant standard selection screen of the ABAP Repository Information System

appears.Enter your selection criteria and choose Program ®Execute.A hit list is displayed. Select the data model you require from the list and choose Display. The Display Data Model: Definition screen appears.



ERPERP

SD11 SD11

© SAP AG 2011

Hierarchy: Access You can access the hierarchy either from the Data Modeler initial screen or from the data model definition:From the initial screen of the Data ModelerHierarchy of SAP modelsYou can call the hierarchy of the SAP models directly from the initial screen of the Data Modeler. Since this hierarchy contains all application models supplied by SAP, you can quickly gain an overview of all the models or navigate to a specific model.Follow the procedure below:...1. Call the initial screen of the Data Modeler.2. On the initial screen, choose Modeling object → SAP Application mod. or SAP Architecture mod., or

choose the relevant pushbutton. The hierarchy of all SAP models is displayed.Accessing the hierarchy from a specific data modelThe procedure to be used varies according to whether you know the full name of the data model from which you wish to access the data model hierarchy, only part of the name, or whether you do not know the name at all.Complete name known1. On the Data Modeler: Initial Screen, enter the name of the data model in the Modeling object field.2. Choose Modeling Object ® Data Model Hierarchy. The Display Data Model: Hierarchy screen appears.Part of name known1. On the Data Modeler: Initial Screen, select Data model hierarchy under Selection.2. Enter the part of the name you know in the Modeling object. input field. Use * to represent the part you

do not know (for example, uni*).3. Click on the arrow to the right of the entry field.4. A hit list of all objects corresponding to the pattern you entered appears. To copy the name of the data

model you require, select the data model by clicking it and activating the Choose pushbutton. The name now appears on the initial screen.

5. Choose Modeling Object ® Data Model Hierarchy. The Display Data Model: Hierarchy screen appears.



ERPERP

SD11 SD11

© SAP AG 2011


Agenda

© SAP AG 2011



Levels of Modeling

- Attribute Views

- Analytic Views

- Calculation Views

- Export & Import


SAP HANA Studio Preferences

Select Windows Preferences Information Modeler

Allows setting of defaultvalues for information models created by user

Set ‘Default Client’ to the client used incustomer systemOr set the Client on the User Account (preferred)Leave ‘Default Language’on preset value (‘dynamic’)Enable preview of Calculated Attributes

© SAP AG 2011

Prior to creating new models, one must validate that the default ‘language’ and default ‘client’ are appropriately set to align with the models that will be created. Here is where the defaults can be updated.

NOTE:If this step is forgotten upfront, one can always return to this screen, update the defaults and then reactivate the appropriate models.

NOTE:it is also possible to set these settings per information model (per view): while editing a view, click on the background of the modeling area. In the properties view, you can now set the default client and default language for the view.


SAP HANA Studio Features

Modeling Information Models

Information models are used to create multiple views of transactional data that can be used for analytical purposes.

Choice to publish and consume at 4 levels of modelingAttribute View, Analytic View, Calculation View , Calculation View enhanced with Analytical View

Database Views / Column StoresData Preview

Physical tablesInformation Models

Import/Export ModelsData Source schemas (metadata) – mass and selective loadLandscapes

Data Provisioning (both initial load and replication)Analytic Privileges / SecurityTroubleshooting / Trace / Logs

© SAP AG 2011


Terminology

SAP HANA Studio: Information ModelerData

Attributes – descriptive data (known as Characteristics SAP BW terminology)– Calculated Attributes Measures – data that can be quantified and calculated (known as key figures in SAP BW)– Calculated Measures & Restricted Measures

ViewsAttribute Views – i.e. dimensionsAnalytic Views – i.e. cubesCalculation Views – similar to virtual provider with services concept in BW– Graphical– Script (SQL Script, CE Functions)

ProceduresFunctions – re-usable functionality

Analytic Privilege – security objectAnalytic Privileges

© SAP AG 2011

The HANA studio is delivered in the SAP HANA Appliance and provides an environment for modeling and data provisioning. The Information Modeler is an eclipse based environment targeted for use by the domain expert – data architect. A separate environment will be provided for Line of Business (release date TBD) and Administrative users (v1.0).


Agenda

© SAP AG 2011



Levels of Modeling

- Attribute Views

- Analytic Views

- Calculation Views

- Export & Import


Modeling Process Flow

© SAP AG 2011

The diagram depicts the process flow for modeling within SAP HANA. This example focuses on the process of creating Information Models and also demonstrates how to export these models for easy portability.


Modeling for SAP HANA 1.0Using HANA Studio

Step1: (Attribute View)

Separate Master Data Modeling from Fact dataBuild the needed master data objects as ‘Attribute Views’

Join text tables to master data tablesIf required: join master data tables to each other (e.g. join ‘Plant’ to ‘Material’)

Step 2: (Analytical View)

Create Cube-like view by joining attributes view to Fact dataBuild a ‘Data Foundation’ based on transactional table

Selection of ‘Measures’ (key figures) ...Add attributes (docking points for joining attribute views)this is basically your ‘fact table’ (key figures and dimension IDs)

Join attribute views to data foundationLooks a bit like a star schema

© SAP AG 2011



Step 3: (Calculation View) / Optional

If joins are not sufficient create a Calculation View that is something that looks like a View and has SQL Script inside

© SAP AG 2011

Composite view of other views (tables, re-use join, olap views)Consists of a Graphical & Script based editorSQL Script is a HANA-specific functional script language

Think of a ‘SELECT FROM HANA’ as a data flowJOIN or UNION two or more data flowsInvoke other (built in CE or generic SQL) functions



Step 4: Analytic PrivilegesAnalysis authorizations for row-level security

Can be based on attributes in analytic viewsAnalytic privilege is always a concrete implementation

I.e. Specific authorization for specified values of given attributeyou have to create privileges for each group of users

© SAP AG 2011


EXERCISE / COPA

Analytical View 1

Attribute Views Attribute Views

Analytical View 2Calculation View

Analytic Privilege3920-3950

© SAP AG 2011


Agenda

© SAP AG 2011



Levels of Modeling

- Attribute Views

- Analytic Views

- Calculation Views

- Export & Import


Attribute Views...... are the reusable dimensions used for analysis. (Time, Account, Product)

© SAP AG 2011

What is an Attribute View?Attributes add context to data.Can be regarded as Master Data tablesCan be linked to fact tables in Analytical Views


Attribute View

© SAP AG 2011


Attribute View:View Creation Wizard

© SAP AG 2011

Attribute View ParametersThe first step of the creation wizard asks for basic view properties

Enter a name (technical name) and descriptionSelect view type

StandardTime

Either create a new viewOr select Derived (read only)Or copy (writeable)

1. Set Attribute View parameters

Assign a unique name to the model.

Allowed characters: capital letters (A-Z) and numbers (0-9), plus underscore ‘_’

Enter a short description for the view

• No multi-language support for such metadata typically best choice is using English text

Select ‘standard’ as the type of Attribute View

• A ‘Time’ view creates a master data view for time characteristics (calender year, quarter, month, week, day, fiscal year/period, ... With different notations and so on.

Identify if this will be a ‘new’ or ‘copied from’

Determine which package will hold the model.

NOTE: When using the ‘copied from’ option, models can be selected from any package. One is not limited to only models within the selected package. Packages simply organize Information Models similar to how schemas organize physical tables.


Attribute View:Select table(s)

2.

An Attribute View is a join of several tablesThe second step of the creation wizard presents a selector for DB tables

One can either expand a schema and try to find the required table(s) viable method for schemas containing a small number of tablesOr one can enter a search term and hit the search button

Highlight table in selector tree (left-hand side, ‘Available’) then add to list of ‘Selected’ tables

© SAP AG 2011

2. Select tables

NOTE:Tables can be selected from multiple schemas’and are not limited to one schema per Attribute View.


Attribute View:Add additional table

Add additional tables to viewVia “Add table” button search window

One can only add one table at a time using this wizard.

© SAP AG 2011

Once the view has been created, it is possible to add more tables.In the top-right corner of the modeler screen for the view there are two buttons. Counting from the left:

An “Add table” buttonA “Preview” button

To add tables via the “Add table” button, proceed as follows:Click the “Add table” button to display a table search wizardIn the wizard, enter a search string for the tableNote: here you cannot enter “regular expressions”Translation of the above: do not try entering wildcards such as ‘*’ or ‘?’ or …Instead: Simply start typing the table name or a part of the table name.

E.g. if you know you’re looking for a table named “PRODUCT”, you can simply start typing “PRODUCT” and a search list will be populated as you type .If you know you are looking for all CE* tables for operating concern “IDEA”, you might simply start typing “IDEA”.Note: there is no “search button” the system starts searching as soon as there are two characters in the search field. The search is updated as you typeFrom the search result (list of “Matching items”) select the table you are looking for and click “OK”Note: you cannot select multiple table from the result list.Nice option: you can also search for the names of table fields:

Activate the check box “Include column names”Start typing a search stringAll tables whose name contains the search string are displayedAll tables which have one or more columns with column name(s) containing your search string are displayed.


Attribute View:Add table via drag & drop

Add additional tables to viewVia Drag&Drop from Navigator Tree

Set appropriate filter on schemaDrag table(s) into the view

1. Filter on table name

2. Drag table into view

© SAP AG 2011

There is a second option to add additional tables to an existing view:

• You can drag and drop tables from the navigator tree (the tree structure which by default is on theleft-hand side of the studio).

When looking for a table from a schema containing many tables, you want to first filter the list of tablesin the schema:

Right click the „tables“ folder within the schema

Enter a filter string

Note: the filter string here must be the beginning of the table name.

Click “OK”

The list of tables in the schema is now filtered.

Expand the “tables” folder to display the filtered list of tables.

Now you can simply drag a table from the schema into your view.

This is a useful option if you have already found a table you need and for example have displayed thetable definition to make sure it‘s the correct table.


Attribute View:Define join properties

© SAP AG 2011

Table Joins and PropertiesJoin Types

ReferentialInnerLeftOuterrightOuterTextJoin

Cardinality1:1N:11:N

Language Column (for text join)Note: the direction in which you draw the join matters (left table first)

3. Define join conditions


Joins

Inner Join…….. return rows when there is at least one match in both tables.

Inner is used even if it’s not added.

Left & Right Join……. the Left Join (or Left Outer Join) returns all rows from the left

table even if there are no matches in the right table. The Right Join (or Right Outer Join) returns all the rows from the right table, even if there are no matches in the left table.

Full Outer Join…… the Outer Join is neither left nor right - it's both. It includes all

the rows from both of the tables or result sets participating in the Join. When no matching rows exist for rows on the left side or right side of the Join, you see NULL values.

Referential Join…….. used where referential integrity is enforced

Text Join…….. for text join a description mapping must be defined. For each

attribute it is possible to define a description mapping that will be language specific

© SAP AG 2011

Inner Join:

The INNER JOIN combines records from the left and right table exactly when the specified criteria are met. If the criteria are not met, no record is created in the result set.

Left Outer:

A record from the left table is always stored in the result set. If a record from the right table met the criteria, it is combined to the record from the left table, otherwise the columns are empty (zero).

Right Outer:

The Right Outer Join works exactly the opposite as the Left outer join.

Full Outer:

Any record of the right and the left table is in the result set. If record from left and right table fulfill the criteria they are combined, otherwise columns will be empty

Text Join:

Used to join a text table to a master data table. This is a requirement for description mapping (see next slide). The text join always filters on one language and thus one needs to specify a language column in the text table. The language is filtered based on the view settings (which are per default taken from the user profile of the modeler)


Attribute View:Output field selection and filters

4

Select Attributes to show up in viewThe output structure of the view must be explicitly defined

At least one key attribute is required.Any number of non-key attributes may be defined.

Define static filter valuesCan be based on any table columnColumn does not need to be selected for output ([key] attribute)

© SAP AG 2011

4. Select key attributes, attributes, and set filters as needed.


Attribute View:Set description mapping

5

Map texts to (semantic) keysFor each attribute in the output structure one can define a description mapping

Select the attribute in the output structureDescription mapping is configured in the ‘Properties’ view for the attribute.The drop-down menu for the description mapping will show all fields of all tables which are joined in the attribute view.

© SAP AG 2011

5. Define Description MappingsDescription mapping is a technique to consistently connect the description (text) to the semantic key of an attribute value. Is supported e.g. by Excel via MDX and by Explorer.


Attribute Properties

MDX per default only shows key fields

This is governed by anoutput field property ofthe attribute viewIf “Hierarchy Active”= “false” for non-key field,

field does not show upin ExcelExample: “Product” dimension has two attributes, but only “Product_number” appears in Excel

Property “Hierarchy Active” see non-key fields via MDX

© SAP AG 2011

If views are displayed via Excel, each Attribute view is represented in Excel as a Dimension

In our example, we have modelled the“Product dimension“ with attributes "Product Number" and "Product Category".

Product Number is the key

Product Category is a non-key attribute.

Each attribute in the list of output fields has among its properties a setting "Hierarchy Active“. This setting defaults to "false“. If set to “false” the attribute will only show up in Excel (via MDX) if it is a key field of the attribute view

If set to "true", the attribute will show up in Excel also if it is not a key field.


Attribute View:Define a level hierarchy

6.

Hierarchy filter in ExcelHierarchies are only accessible via MDXDefine a level hierarchy

Need one attribute per hierarchy levelSelect column from output structure (drag & drop)Fixed number of levels

© SAP AG 2011

6. Create Hierarchies (level hierarchies)Note: at present, hierarchies defined in the modeler are only accessible via MDX. Which means that at present such hierarchies can only be used from MS Excel.


Attribute View:Define a parent-child hierarchy

7.

Hierarchies are only accessible via MDXDefine a parent-child hierarchy

Variable number of levels for sub-trees within the hierarchy

© SAP AG 2011

6. Create Hierarchies (parent child hierarchies)Note:at present, hierarchies defined in the modeler are only accessible via MDX. Which means that at present such hierarchies can only be used from MS Excel.


Attribute View:Calculated Attributes

© SAP AG 2011

Create a attribute based on a static value or dynamic calculationBuilt in functions (Conversion, String, Math, Date ...)


Attribute View:Save and activate the view

8.

Create executable version of the viewSave the view

Save button in top-left corner of StudioThis saves the information model, i.e. the metadata of the view that has just been defined.This information model itself is not visible to reporting tools

Activate the viewRight-click view and choose ‘Activate’ from context menuThis creates a database view in schema ‘_SYS_BIC’(a so-called ‘column view’)Name of the column view:‘_SYS_BIC.I_<PACKAGE>/<VIEW_NAME>’

This column view can be accessed from reporting tools

© SAP AG 2011

Before a view is visible for reporting, it needs to be ‘activated’ (deployed). The activation process translates the metadata defined in the Information Model into a database object.

A modified version of a view cannot be activated; one always needs to save the view first. There is no implicit ‘save’ performed when a user tries to activate a modified view. It is not necessary to close the modelling editor.

Once view activation is finished, one can see the log of this activation process (button in top-right cornerof the ‚Deployment Log‘ view). This activation log contains among other things the SQL call that has been executed in order to create the view‘s database object. This SQL call can be a good starting point for issue analysis with views. The Deployment Log is also useful if there is an error during viewactivation.

At this point we have deployed for consumption an Attribute View. This enables reporting against this attribute view and allows including this view in analytic views.


Attribute View:Preview the view

Data Preview on the Information Model:

Data Preview on Column View:

9.

© SAP AG 2011

The data preview functionality is useful for confirming that one has modeled the data the way he/she intended. It can be done at the Attribute view, or at the physical tables at the foundation level.

There are three main views one can select from when previewing data.

Raw Data – table format of data

Distinct Values – graphical and text format identifying unique values

Analysis – select fields (attributes and measures) to display in graphical format.

Reporting at this level will not include measures as measures are in Analytic Views not Attribute Views. To conduct analysis on measures according to the attributes in this Attribute View one would include this Attribute View in an Analytic View definition


Attribute View:Time Dimension Attribute Views

© SAP AG 2011

GregorianDate (Timestamp), Year (2007)

FiscalVariance (K4)

_SYS_BI.M_TIME_DIMENSION

_SYS_BI.M_FISICAL_CALENDAR


Attribute View:Time Dimension Attribute Views

© SAP AG 2011

JOIN FACT table to Fiscal Attribute View

JOIN FACT table to Time Attribute ViewDate field


Agenda

© SAP AG 2011



Levels of Modeling

- Attribute Views

- Analytic Views

- Calculation Views

- Export & Import


Analytical View… are the multidimensional views that analyze values from single fact table

© SAP AG 2011

An Analytic View can be regarded as a “cube”Multidimensional reporting modelFact table (data foundation) joined against modelled dimensions (attribute views)

Analytic Views do not store dataData is read from the joined database tablesJoins and calculated measures are evaluated at run timeMaster data for MDX/BICS are stored in system tables


Analytic View

© SAP AG 2011


Analytic ViewView creation wizard

Analytic ViewSet Parameters

Assign unique nameEnter a descriptionCreate new view from scratch (Create New)Or choose an existing view as template (Copy From)

1.

© SAP AG 2011

1. Set Analytic View parameters

Assign a unique name to the model.

Identify if this will be a ‘new’ or ‘copied from’ view. Copied from will use an existing model as a template.

Determine which package will hold the model.


Analytic ViewSelect Table(s)

Tables for the data foundationTable selection wizard.

Same as with attribute views (search and select)Can only select measures from one table (transactional data)Can select attributes from several tables (must be joinable)

It is also possible to add tables laterVia single-table selection wizardOr via drag & drop from navigator tree (same as with attribute views)

2.

© SAP AG 2011

2. Select tables


Dimension selection (Attribute views)Selection wizard.

Select any suitable Attribute View from any packageAnalytic View and Attribute View do not need to be in the same package

It is also possible to add Attribute Views laterVia drag & drop from navigator treeYou can only drop into the ‘logical view’-tab of the view editor

Analytic ViewSelect Attribute view(s)

3.

© SAP AG 2011

3. Select Attribute Views (optional) – One can select which Attribute Views to incorporate in to a model during this wizard OR they can add them in at a later date as enhancing a table with Attribute Views is completely optional


Two steps of view creation reflected in editor tabsTab ‘Data Foundation’ Create the data foundation (‘fact table’)

(Optional: join data base tables)Select attributes and measures from table(s) this defines the data foundation(Optional: create calculated and restricted measures)

Tab ‘Logical View’ Join Attribute Views to the data foundationThis is where you can drag attribute views into the editor

Analytic ViewAnalytic View Editor

© SAP AG 2011

Table FACT Table

Attribute ViewsData Foundation Logical View

4. Join Attribute ViewsNote the difference between the foundation and logical views. The foundation view shows the physical table with all fields that can be incorporated in to the final model.

The logical view displays only those fields which you have chosen to include in this model as well as the restricted and calculated measures that have been defined.


Analytic ViewDefine the Data Foundation

Analytic View (Data Foundation)Attribute and Measures

Can create Attribute FiltersMust have at least one AttributeMust have at least one MeasureCan create Restricted MeasuresCan create Calculated MeasuresCan rename Attribute and Measures on the properties tab

5.

© SAP AG 2011

5. Select attributes, measures, and set filters. Note:If there is a AB in front of the field you can select it as an attribute. If there is a number (12) in front of the field you can select it as a measure.


Analytic ViewJoin Attribute Views to Data Foundation

4.

Define joins between Attribute Views and Data FoundationJoin Attribute View to a private attribute of the data foundation

Private Attribute: attribute selected from a database tableTypically one would include all key attributes of the attribute view in the join definitionDefault join type is ‘inner join’

Non-key fields of attribute view are implicitly added to the analytic view‘navigation attributes’

© SAP AG 2011

Define join conditions and cardinality. The default settings are “inner join” and “n…1”.

Click on the ‘properties’ tab on the lower section of the screen to change these settings if necessary.


Analytic ViewDefining Calculated Measures

© SAP AG 2011

Aggregation (sum, min, max, count), Data Types (decimals, numbers etc)Expressions / Operators Functions (String, Date Math, Conversion…)

6. Create Calculated Measures


Analytic ViewDefining Restricted Measures

© SAP AG 2011

7. Create Restricted Measures


Create executable version of the viewSave the view

Save button in top-left corner of StudioThis saves the information model, i.e. the metadata of the view that has just been defined.This information model itself is not visible to reporting tools

Activate the viewRight-click view and choose ‘Activate’ from context menuThis creates a database view in schema ‘_SYS_BIC’(a so-called ‘column view’)Name of the column view:‘_SYS_BIC.I_<PACKAGE>/<VIEW_NAME>’This column view can be accessed from reporting tools

Analytic ViewSave and Activate the View

8.

8.

© SAP AG 2011

8. Save and Activate.The Column Views that were automatically created for each Analytic and Attribute View can be found in the Default Catalog Navigation Tree.


Use the built-in Eclipse-Preview of HANA StudioLaunch preview from the Information Model (not from the Column View)

Either right-click on Analytic View in Information-Model-part of navigator treeOr click on preview-icon in top-right corner of the view editor

Three preview-modesRaw data (table display)Number of distinct values per columnInteractive graphical analysis

Analytic ViewPreview data of analytic view

9.

© SAP AG 2011

The Column Views that were automatically created for each Analytic and Attribute View can be found in the Default Catalog Navigation Tree.

The data preview functionality is useful for confirming that one has modeled the data the way he/she intended. Preview should always be started from the Information Model. It is not supported based on the column view of Analytic Views.

There are three main views one can select from when previewing data.

Raw Data – table format of data

Distinct Values – graphical and text format identifying unique values

Analysis – select fields (attributes and measures) to display in graphical format.


Analytic View

© SAP AG 2011


Analytic View

© SAP AG 2011

You can display the data in a table format or a a graph. There are multiple graphs types available.


EXERCISE / COPA

Actual DataAnalytical View

Model

Planned DataAnalytical View

Model

Customer / ProductAttribute View

Models

Analytical View Column Stores

Activate Activate

© SAP AG 2011

Prior to creating new models, one must validate that the default ‘language’ and default ‘client’ are appropriately set to align with the models that will be created. Here is where the defaults can be updated.

NOTE:If this step is forgotten upfront, one can always return to this screen, update the defaults and then reactivate the appropriate models.

NOTE:it is also possible to set these settings per information model (per view): while editing a view, click on the background of the modeling area. In the properties view, you can now set the default client and default language for the view.

NOTE: With the studio version used in the RKT trainings in weeks 47/48, the default client must be set to blank in order to get any data returned. This restriction is not valid in more recent builds of the studio.


Agenda

© SAP AG 2011



Levels of Modeling

- Attribute Views

- Analytic Views

- Calculation Views

- Export & Import


Calculation View

© SAP AG 2011

… are used to create your own data foundation using database tables, attribute views, and analytic views to address a complex business requirement.

Calculation views are:A column view that is visible to reporting toolsWhen the view is accessed, a function is implicitly executed

The function within the calculation viewThat function is defined in the HANA-specific language ‘SQL Script’Functions can contain SQL commands

SELECT <FIELDS> FROM <TABLE, VIEW or COLUMN VIEW> ...One can read not only from DB tables but also from column views created for

analytic views or attribute viewsSQL in functions must be ‘read only’ (no insert, update, delete, drop, ...)

Functions can call other functionsModularize the logic within the calculation viewHANA offers pre-defined functions, e.g. for creating a join or union of tables


Two Types of Calculation Views

© SAP AG 2011

Composite views, re-uses Analytical and Attribute viewsSQL / SQL Script / Custom Functions

Analytical View

UNION

GRAPHICAL SQL Script

Analytical View

UNION


Calculation View (graphical)

© SAP AG 2011


Calculation View (Graphical)View creation wizard

© SAP AG 2011

Parameter wizard for calculation view

Enter a view name and descriptionName must be alphanumeric (A-Z; 0-9; _)

Select Graphical or SQL ScriptNote: SQL knowledge required when selecting SQL Script.


Calculation View (Graphical)View creation wizard

© SAP AG 2011

Select any tables, attribute or analytical views to Add to the Calculation View

Either select raw tables or on the next screen select existing views.


Calculation View (Graphical)

Select Nodes from the Tools Palette and draw a data flow graphSelect 2 projection nodes and 1 Union node

Projection nodes will be used to set the Actual versus Planned indicatorDrag a connection line between all the nodesThe output node will represent the data flow graph end

© SAP AG 2011



Select each Projection node and add all the fields to the output nodeDo not select the PLIKZ field, this field will by added with a calculated column

© SAP AG 2011



Create a Calculated Column called KPLIKZ for each Projection nodeActual = 0, Planned = 1

© SAP AG 2011

It is possible to create complex expressions to calculate columns.

Example Expression: midstr(string("ERDAT"),strlen(string("ERDAT"))-9,4



Define the UNION by mapping both Projection Nodes to the target

© SAP AG 2011



Add the Attributes and Measure to the OutputActivation will create the Column view that can be accessed by the front end tools

© SAP AG 2011


Calculation View (scripting)

© SAP AG 2011


SQL Script - New Programming Model

Functional extension - allows the definition of (side-effect free) functions which can be used to express and encapsulate complex data flowsData type extension - allows the definition of types without corresponding tables

Traditional Model:“Data to Code”

DB Server

Application

ServerCode

New Model:“Code to Data”

DB Server

Application

Server

Code

“… is a collection of SQL extensions to push data-intensive logic into the Database”

© SAP AG 2011


Calculation View (Scripting)Calculation View Wizard

Parameter wizard for calculation view

Enter a view name and descriptionName must be alphanumeric (A-Z; 0-9; _)

Select SQL ScriptNote: Select the database Schema where the tables are located.

© SAP AG 2011


Calculation View (scripting)Calc View table type

© SAP AG 2011

Define the Output structure (Table Type) of the Calculation View

Tip:

In order to get the correct data types from existing database tables, one can

right-click the table in the navigator tree and

select ‘Definition’ from the context menu. Then

right-click into the editor that opens up (the tab displaying the list of table fields) and

select ‘Export SQL’ from the context menu

A new editor opens which contains a CREATE statement for the view. One can copy all needed fields from this SQL editor.

Unfortunately this method does not work with column views (e.g. column views generated for an analytic view).


Calculation View (scripting)Function definition

Define Function (with input and output parameters)The input parameter is optional

Can be a scalar value to pass parameters from the front-end tools in order to filter the results (if supported by front-ends).Can be a table type to pass results from one function into another

The output parameter is mandatoryCan be a locally defined table type or a globally existing tableDefines the structure of the function output

© SAP AG 2011

Note:calculation views based on functions with input parameters may not be accessible from all reporting tools.


Calculation View (scripting)Add the SQL Script code

© SAP AG 2011

Write the necessary select statements to query the data and populate the output table structure


Creating the database object for the calculation viewMetadata (the calculation view coding) has to be translated into run-time objects

This is done by executing the coding (green arrow in SQL editor)The defined table type is dropped and createdThe SQL script function is createdColumn views are created in the chosen output schema. View name:<SCHEMA>._SYS_SS_CE_<CALC_VIEW_NAME>_RET

Calculation View (scripting)Creating run-time objects

Verify result (log area of the SQL editor).

Execute the view

© SAP AG 2011


Calculation View (scripting)Calc View output structure

© SAP AG 2011

Select the attributes and measure for the output node. This will represent the definition of the column view that the front end tools will query against


Calculation View (scripting)Save and activate

© SAP AG 2011

Final step: save and activate the calculation viewStore the view metadata etc.

Save the view via the save buttonActivate the view from its context menu

save… … and activate


Calculation View (scripting)Viewing the data

© SAP AG 2011

Viewing the data in a calculation view from the IMCE StudioData Preview

Data preview for calculation views is not available (neither for Information Model nor for Column View)

Alternative: SQL editorUse a SELECT statement of the form:SELECT SUM(<MEASURE_i>), <ATTRIBUTE_j>

FROM <COLUMN_VIEW>GROUP BY <ATTRIBUTE_j>

Hint for viewing data inside of the calculation view:

Locate the column view for the calculation view (in the schema defined when the view was created. There are three column views generated for each calculation view. The relevant one is the one with suffix _RET)

Right-click the column view and select ‘Definition’ this shows a list of all fields in the view. This helps creating a valid SQL statement.


Recommendations - How to build content

© SAP AG 2011


How to build content

Analytical View Attribute View Tables

Calculation View

Recommended

Not recommendedNot recommended

© SAP AG 2011


Calculation View & SQL Script – When to use

Create custom re-usable calculation functionsRe-use standard SQL functions not provided within modeler

Calculation views support UNIONBuilt in SQL Script functions available for union support

Calculation views required if key figures span across tables

Advanced SQL Scripting development within Calculation ViewsSQL Scripting can query existing Attribute & Analytical viewsPerform join between Column and Row store

Complete Control over

SQL

Business Logic

Unions between

tables

Key figures span fact

tables

© SAP AG 2011


Agenda

© SAP AG 2011



Levels of Modeling

- Attribute Views

- Analytic Views

- Calculation Views

- Export & Import


Import and Export

Import and Export

What are the purposes of an the Export and Import Functionality?What are the steps involved in Export and Import Functionality?

© SAP AG 2011


Process Flow

© SAP AG 2011


Exporting and importing with SAP HANA

HANA supports export and import of Information Models, tables and moreExport and Import is handled via SAP HANA Studio

Client-side export/import: to / from client PC running SAP HANA StudioServer-side export/import: to file system of SAP HANA Database server

DB Server

Information Models

Tables

© SAP AG 2011


Start Import / Export wizardsIn SAP HANA Studio

Two options:From Menu:

File ExportFrom “Quick Launch”

Menu “Help” “Quick Launch”

© SAP AG 2011


Process Flow

© SAP AG 2011


Client Side Export / Import of Information Models

What is a client-side Export?Export of Repository Objects

Definitions of Attribute-, Analytic-, Calculation ViewsAnalytic Privileges

To the ClientI.e. to the host on which Studio is running

© SAP AG 2011


Client Side Export of Information Models (I)Creation Wizard

Select client-side exportInformation Modeler

Information Models

Select system/user to export fromThat user needs access to repository

© SAP AG 2011


Client Side Export of Information Models (II)Select views and Analytic Privileges to export

Select Objects to ExportHighlight on left-hand side tree

add to the right-hand side treeSelect individual views / privilegesOr entire packages

© SAP AG 2011


Client Side Export of Information Models (III)Specify the export location

Specify a folder on the client PC to export intoWithin that folder, a folder with the name of the HANA system will be created

Name of HANA System = <SID>; here: GBS

© SAP AG 2011


Client Side Export of Information Models (IV)Verify Export

Check export in Job log

Check output on file systemPackage structure recreated in export path

Objects exported as XML files

© SAP AG 2011


Client-Side Import of Information Models (I)Import Wizard

Choose client-side importof Information Models

Select target system/user combination to import into

© SAP AG 2011


Process Flow

© SAP AG 2011


Client-Side Import of Information Models (II)Select source folder

Select the source folder to import from

This is the <SID> folderMust contain a sub-folder <package>Which in turn has sub-foldersanalyticviewsattributeviews…

© SAP AG 2011


Client-Side Import of Information Models (III)Select objects to import

Choose list of views to importAs before:

Select individual viewsOr entire packages

© SAP AG 2011


Client-Side Import of Information Models (IV)Run the import

Click “Finish” to execute the import

Then: check progress in job log

© SAP AG 2011


Client-Side Import of Information Models (V)Considerations

Client side import cannot overwrite existing objectsFor importing an update to a view into a target system

First delete the view from the target systemThen perform the import

Client side import does not activateRun mass activation following the import

Exported objects (xml files) can be changedDifficult to control editing of objects

It is a way to copy views from one package into anotherNote: quick launch mass copy is the intended tool for this task

© SAP AG 2011


Mass Activation of Information Models (I)Set up quick launch

Important prerequisite:Configure Quick Launch to use the correct system/user combination

Check current configurationUse “Manage Connections”to change

© SAP AG 2011


Mass Activation of Information Models (II)Mass activation wizard

Start mass activation from “Quick Launch”In the wizard

Select entire packageOr individual views / privileges

Click “Activate”This takes careof dependenciesActivates in the correct order

© SAP AG 2011


Summary

In this lesson, you learned:Understand the purpose of the Information ModelerDescribe the levels of modeling in HANA 1.0Create and display data for an Attribute ViewCreate and display data for an Analytical ViewCreate and display data for a Calculation ViewUnderstand the purpose of the Export / Import Functionality

© SAP AG 2011


© SAP AG 2011

Agenda





Lesson 5: Modelling


Lesson 6: Reporting


Lesson Objectives

After completing this lesson, you should be able to:Understand connectivity options for reporting on top of SAP HANAUnderstand the BusinessObjects BI4.0 platform and reporting possibilitiesUse different client tools to report on SAP HANA

© SAP AG 2011


Agenda

© SAP AG 2011

Lesson 6:SAP HANA, reporting layer and connectivity options

Microsoft Excel

SAP BusinessObjects Analysis

SAP BusinessObjects Explorer

SAP BusinessObjects BI 4.0

SAP Crystal Reports for Enterprise, Dashboards and Web Intelligence


ERP

Architecture OverviewSAP HANA Engine and Surroundings

LogERP DB



DashboardDesign


Request Processing / Execution Control

MS Excel

BI4 Analysis

SQL Parser MDXSQL Script Calc Engine

Transaction Manager

Session Management




Authorization Manager

Metadata Manager

IMCE Studio


Load Controller

Replication Agent

Replication Server

SAP Business Objects BI4


SBO BI4 servers

(program)

SBO BI4 Information

Design Tool


SAP NetWeaver

BW3rd Party

Data Services

© SAP AG 2011


Reporting on SAP HANA Client and connectivity options

SAP HANA

SAP In-memory Computing Engine

Web Intelligence

Dashboards

Excel

Crystal Reports

for Enterprise

Semantic Layer (universe UNX)

MDX SQL

ODBO

Analysis Office v1.1

BICS

ODBC

Explorer

JDBCJDBC ODBC

Crystal Reports 2011

JDBC ODBC

SQLSQL

Are part of SAP BusinessObjects BI 4.0

SQL

© SAP AG 2011

Various connectivities exist :

• ODBC / JDBC / ODBO / SQL DBC (native library for SAP HANA DB)• SAP BusinessObjects BI 4.0 client tools can be used to report on SAP HANA.

Crystal Report, 2 versions:

• CR Enterprise included in BI 4.0 with connectivity though BI 4.0• CR 2011 and CR 2008 standalone reporting tool, connectivity through ODBC or JDBC

SAP Business Objects BI 4.0 will not be discussed here. Separate trainings are available. Please contact SAP Education for further details.


Reporting on SAP HANAOpen interfaces

SAP HANA 1.0 provides various interface reporting optionsODBO – OLE DB for OLAP

Microsoft-driven specification for multidimensional (cross-tab style) reportingRequests are sent to the database via MDX (MultiDimensional eXpression language)

ODBC – Open DataBase ConnectivityMicrosoft-driven specification for relational reportingDatabase requests are made via SQL (Structured Query Language)Heavily adopted in industryNo longer Microsoft-centric - Unix and Linux drivers exist for ODBC

JDBC – Java DataBase ConnectivityRelational reporting drivers specified by the Java community. Popular on Unix platforms.

BICS – BI Consumer ServicesSAP Proprietary interface that offers advantages for OLAP access over MDX on multidimensional reporting objectsCommon driver technology used by SAP BusinessObjects Analysis, Office Edition for connectivity to SAP NetWeaver BW

SQLDBC is SAP native database SDK

© SAP AG 2011


Agenda

© SAP AG 2011


Microsoft Excel






SAP BusinessObjects Analysis, Office Edition

Access Analytic and Calculation Views from Analysis Office (MS Excel or Powerpoint) via a locally defined ODBC connection

© SAP AG 2011


SAP BusinessObjects Analysis, Office Edition

© SAP AG 2011


Agenda

© SAP AG 2011


Microsoft Excel






Reporting on SAP HANANative Excel interface - Pivot Tables (ODBO)

Multidimensional reporting is available via Excel Pivot TablesThis has the advantage of „quick and dirty“ cross-tab style reporting via ExcelNumerous disadvantages exist

The report definition is only available locally (workarounds exist)Subject to performance limitations of the desktop machine where Excel runs

Pivot Tables can be initiated in numerous ways but primary entry point is via the Excel DATA menu option.

© SAP AG 2011


Reporting on SAP HANANative Excel interface via ODBO

HANA ODBO drivers is available via the Other/Advanced option of the Data Connection Wizard:

Clicking OK yields HANA Logon:

© SAP AG 2011


Reporting on SAP HANANative Excel interface – the Pivot Table

Standard Microsoft Pivot Table interface is presented.Check Measures, Drag and drop rows/columns

© SAP AG 2011


Agenda

© SAP AG 2011


Microsoft Excel






Bring BI to all business usersSimplicity and speed of searchIntuitive data exploration and visualizationFast response across mountains of data anywhere in the organizationAccelerated version with in-memory technologies

Help IT to be successful Easy and efficient to manageand scaleMore reactive to business with faster deliverySupport for heterogeneous data sources

Data Search and ExplorationSAP BusinessObjects BI4.0 Explorer

© SAP AG 2011


What is BusinessObjects Explorer?It’s search against BI…

Use familiar key-word search to find business information

Answers “on-the-fly” and investigative questions

Searches directly on pre indexed data

No previous reports or metrics need to existProvides fast search and exploration

Searches across all data sources

Any universe accessible sourceAny SAP NetWeaver BW Accelerator accessible sourceAnd of course any accessible HANA system

© SAP AG 2011


…and Then It’s Exploration Of the Results

Intuitively explore on data

No data model or data knowledge required

Automated relevancy of results

Most relevant information is displayed firstBest chart type auto generated

Share insights with othersExport to CSV or imageSave it locally as a browser bookmarkOne-click to send a link to the results by email

© SAP AG 2011


Explorer for HANASetup

In SAP BusinessObjects BI4.0 Central Management Console,Advanced configuration for Explorer ApplicationEnable the use of HANA connections defined from Information Design Tool

http://mybiserver:8080/BOE/CMC-> Applications -> Explorer -> Properties on contextual menu -> Advanced configuration

newdb.connections.enabled = true

© SAP AG 2011

newdb.connections.enabled = true

Enables Explorer to use the JDBC connections to HANA systems defined from the Information Design Tool

Alternate configuration settings (similar to BWA but limits to one HANA instance):

newdb.system.alias in the name that will be visible in the Explorer application

url is the url to the newdb JDBC access point

Authentication.mode here is set to the simpliest mode, that is we give user/password for testing purpose.

Another mode exists that is mode=DatabaseConnection which means that a mapping is defined between BI users and HANA users, this mapping has to be handled by hand by administrator, SSO to come later.

User / password, self speaking


Explorer for HANAInformation Space Creation

© SAP AG 2011


Agenda

© SAP AG 2011


Microsoft Excel






Complete BI Suite to Put Together Information in the Users’ Preferred Format

DIFFERENT NEEDS

Dashboards

Reporting

Interactive Analysis OLAP

AnalysisData

Exploration

How do I visualize key performance

indicators for better decision

making?

How do I answer ad hoc questions and interact with

shared information?

How do I find immediate answers to business

questions?

How do I uncover trends from

historical data and make possible

better forecasts?

How do I turn data into pixel-perfect formatted reports

for greater insight?

© SAP AG 2011

The SAP BusinessObjects philosophy has always been to give each user persona the right BI tool for the way they work. Power users who want to analyze data need a different experience then an executive who wants to track and monitor key metrics. In other words, business users have distinct needs and have different IT skill sets.

Our BI portfolio provide business users with access to information through a broad suite of BI tools on a single, scalable BI platform. The ultimate goal is to empower all users (executives, analysts, staff, suppliers, and partners) so they can make better-informed choices and decisionsOur BI portfolio includes different categories of tools: Reporting, Dashboard, interactive analysis, etc.


Reporting on HANA SAP BusinessObjects BI4.0 Reporting Clients

Web Intelligence (Interactive Analysis)

Web Intelligence (Interactive Analysis)

ExplorerExplorer

Guided

Dashboard Design

(Xcelsius)

Dashboard Design

(Xcelsius)

Search &Exploration Ad-Hoc QRA Dashboarding &

VisualizationEnterpriseReporting

Interactive ExperienceFree

Professionally Informed

Technically Capable

InformationConsumers

Executives &Managers

Business Analysts

Crystal ReportsCrystal Reports

© SAP AG 2011


Explorer is a new BI paradigm: you can explore your business and find answers when you don’t known which question to ask. Indeed, you don’t need to understand how the data is structured, how your queries are built. Explorer searches directly on the pre-indexed data in a very intuitive way.

This tool is for “Casual User”, “Information workers who are seeking easier self-service environment” or “Users who are involved in day-to-day decisions”

SAP BusinessObjects Web Intelligence

Web Intelligence is one of the most advanced ad-hoc reporting solution on the market. It lets end-users design and analyze their own reports and queries. This tool is the one to use for Reporting & Analysis goals, especially for the casual business users.

SAP BusinessObjects Dashboards

Dashboards bridges the gap between data analysis and visual presentation in a very sexy way.

The Target audience is mostly for business users.

SAP Crystal Reports

Crystal Reports allows you to create Operational or pixel-perfect reports

The target audience is IT department for report authoring. It is the tool as well for most business users for report consumption.


“The” Business Intelligence placeSAP BusinessObject BI 4.0 Launch Pad

New self-service BI access making it easier to find all available contentEnhanced filtering and search options reducing page scrollingEnhanced navigation for working with multiple documents at the same time

New self-service BI access making it easier to find all available contentEnhanced filtering and search options reducing page scrollingEnhanced navigation for working with multiple documents at the same time

Self-Service Information Consumption

Self-Service Information Consumption

© SAP AG 2011

BI Workplace – InfoViewEasier Content Navigation for All UsersWe deliver a more engaging user experience across the entire SAP BusinessObjects BI suite, including one of the main user touch points, the BI portal known as SAP BusinessObjects Launch Pad (previously: InfoView). The BI Launch Pad is an important part of our strategy of enabling organizations to access and deliver decision-making information to the majority of employees in corporations who aren’t using it today. It’s often the door to the wealth of existing corporate information and as such it must be able to present the information available in an efficient and visually attractive way so users don’t loose time manually sifting what is relevant from what is not for their particular task or decision. Filtering and pertinent search options are therefore critical to assist users in quickly finding the right trusted information. Companies using SAP BusinessObjects Bi 4.0 and Launch Pad as the means to store and access BI information should expect greater user productivity with a much improved BI portal experience and improved BI search relevancy and usability.BI Launch PadNew modern styling and more intuitive look and feel.For example, it allows users to work multiple documents at the same timeBI Launch Pad had revamped search capabilities and new filtering widgets allowing users to narrow down the content they are looking for.For example, users are able to navigate to a particular folder and use a filter (for this folder only) in order to limit the number of items listed so they can retrieve the report, dashboard, or analysis they are looking for.


User personalized BI WorkspaceSAP BusinessObjects BI 4.0 BI Workspace

Hom

ePage Modules

BI Workspace

Web C

ontent

Agnostic

Crystal R

eports

Analysis

Web Intelligence

Dashboards

Reporting, Analysis Other ContentVisual

Organizing and displaying any BI content with decreased IT dependencySimple WYSIWYG authoring for creating and modifying contentInter-portlet communication enabling information exchange between components

Organizing and displaying any BI content with decreased IT dependencySimple WYSIWYG authoring for creating and modifying contentInter-portlet communication enabling information exchange between components

Personalized Information Consumption

Personalized Information Consumption

© SAP AG 2011

BI workspaces

BI workspaces is a browser-based application that is provided as part of the SAP BusinessObjects Enterprise professional package.

It is an evolution of the Dashboard Builder product and includes most of the capabilities found in its predecessor, especially those related to content layout.

New workspaces can be viewed, created, and modified using the BI launch pad. They can also be viewed via openDocument or in your favorite Enterprise Portal using the Portal Integration Kit.

BI workspaces are most suitable for displaying BusinessObjects reports and applications, such as: Dashboards (Xcelsius), Web Intelligence, Analysis and Crystal Reports. It can also display other content types such as external web pages, Microsoft Office documents and BI launch pad modules.

Note that every content item that is displayed on the page or in the module library is called a module.

The key capabilities of BI workspaces include:

• Organizing and displaying modules

• A simple and intuitive Runtime Authoring environment for designing the workspace pages

• An integrated inter-portlet communication framework for enabling components on the page to exchange information

• And last but not least: Page Preview and the option to print a page or the entire workspace.


Semantic Layer Mission

Enable the business users to freely and securely access, analyze, enrich and share information using familiar business terms

Make business users autonomousEnable single user experience over all data (structured & unstructured)Provide trust and consistency over data by ensuring that the same business terms are used throughout the organizationEnable consumption by all applications and BI tools Allow IT to keep control and ensure security of information

Semantic LayerData Sources

Query and Analysis

Dashboards andVisualizations

Reporting

Full-Spectrum Business Intelligence

© SAP AG 2011


Common Semantic Layer

One consistent user experience across all BI front-endsOne abstraction layer for data sourcesAdapt and leverage data source capabilities without requiring to change data models and/or move dataSmooth evolution from universes for existing customers

PioneerPioneer WebIntelligence

WebIntelligence

CrystalReportsCrystalReports XcelsiusXcelsius

Common Semantic LayerCommon Semantic Layer

InfoProviderInfoProvider

Data SourceData Source DTPDTP DSODSO

XML WS

BI Consumption

Business Semantic Design

Data Access Design

ETLETL

Common semantic layer = one unified approach for meta data support

© SAP AG 2011

TCO, reduction of landscape complexity, and lifecycle management enhancements across SAP’s entire BI and EIM portfolio remain priorities

COMMON because it will be the same semantic layer for all data sources: the best on SAP data, the best in the market for all other vendors’ sources thanks to the agnostic support which comes with the historical Business Objects architecture

COMMON because it will be the single language that will be used by all kinds of client tools to speak about data and metadata: BI clients as well as metadata management or data quality applications will use the Common Semantic Layer to exchange information about data and metadata they need to manipulate. The semantic layer will be open to third parties applications so that the whole enterprise data can be covered by the same concepts and mechanism.

COMMON because independently of the underlying source or of the requesting client, it will provide a unified interface for data and metadata on premise, on demand and on device or a mix of the three.


Semantic Layer deliverables in SAP BusinessObjects BI 4.0

Tools

Information design tool

Universe design tool

New generation design toolAll new projects should use this tool. Most existing

universes can be opened and converted to the new format by this tool.

Universe design as XI3.xStill shipped in this version in order to enable the

smoothest possible transition.

Components

Information engine

Query server Data federation engineThis is the component that enables MSU (Multi-Source

Universe) functionality.

Connection server

Query & computation Behind the scenes, this is the component that enables querying and computational capabilities to BI clients

during report consumption.

ConnectivityThis is the component that establishes the connectivity

to data sources.

© SAP AG 2011


SAP BusinessObjects Information Design Tool

New ProjectDefine Relational ConnectionDefine Data FoundationDefine Business LayerPublish Universe

© SAP AG 2011


Agenda

© SAP AG 2011


Microsoft Excel






Pixel perfect reportingSAP Crystal Reports for Enterprise

New styling with ribbon bar look and feelCommon query design experience across all data sources with new semantic layerAutomated report translation for global deployments

New styling with ribbon bar look and feelCommon query design experience across all data sources with new semantic layerAutomated report translation for global deployments

Next-Generation Report Designer Experience


© SAP AG 2011

Reporting – SAP Crystal Reports for Enterprise

For SAP Crystal Reports, the goals are:

Provide the most powerful report designer for the professional report author with the lowest TCO for the entire report lifecycle (creation, maintenance and delivery)

Support all elements of the reporting lifecycle by integrating tightly with our BI platform and more specifically with our new semantic layer

Global reach with multilingual reporting

Support seamless access to OLAP data (OLAP Client – Crystal Reports Interoperability)


Our intent is to increase report author productivity with:

1. A new CR designer client including new styling with ribbon bar look and feel.

2. Support our new dimensional semantic layer across all data sources

3. Easier, faster, and more consistent query design experience across all data sources since it is based on the same metadata model (the new semantic layer).

4. Improved native access to SAP NetWeaver BW data sources – no universe required.


SAP Crystal Reports for Enterprise 4.0

© SAP AG 2011


Consume attractive, personalized dashboards online or offline

Access to personalized, Flash-based dashboardsSecure visualizations anywhere –portal, reports, PDF, MS Office documents

Empower business users with interactive information

Powerful “what-if” analysis with sliders and other controlsAbility to drill-down into detailsPre-built components, skins, maps, charts, gauges, and selectors

Dashboarding & Data VisualizationSAP BusinessObjects BI4.0 Dashboards (XCelcius)

© SAP AG 2011


SAP BusinessObjects Dashboards 4.0Universe Queries

© SAP AG 2011


Ad Hoc Query, Reporting, Analysis SAP BusinessObjects BI4.0 Web Intelligence

Empower business users with powerful, yet easy to use analysis

Intuitive, Web-based interface with offline capabilitiesStart from a blank slate or use an existing analysis or reportMulti-source accessInteractivity with filtering, ranking, sorting, calculations, etc.Data lineage

Lighten IT workloadSelf-service analysis and reportingControlled and secure access withtight BI platform integrationIntuitive, business-centric view of information with universes

New screen shotneeded

© SAP AG 2011


SAP BusinessObjects BI 4.0 Web Intelligence

© SAP AG 2011


Lesson Objectives

you should now be able to:Understand connectivity options for reporting on top of SAP HANAUnderstand the BusinessObjects BI4.0 platform and reporting possibilitiesUse different client tools to report on SAP HANA

© SAP AG 2011


Agenda

© SAP AG 2011





Lesson 5: Modelling


Lesson 6: Reporting


Lesson Objectives

After Completing this lesson you will be able to:Manage users and roles

Create users and rolesEdit users and roles

Understand the Security Concept of SAP HANA Appliance

© SAP AG 2011


Agenda

© SAP AG 2011

Lesson 7:

User Management

Template Roles

Security Details

Best Practice


4

Manage UsersLock UsersReset PasswordsCheck User PrivilegesIntegration with BI

User Management and Security in SAP HANA

Assign SecurityControl Access to ObjectsRow-Level SecurityRestrict allowed actions

Create UsersAssign Initial PasswordsImportant User

Parameters

© SAP AG 2011

Why is a security concept in HANA required?

Trivial answers:

• Database administration should be restricted to skilled (and empowered) persons

• Access to ERP tables must be restricted

• Editing of HANA data models should only be possible for „owners“ of the model

Not so trivial: user administration plays a big role in HANA

• Several front-end tools offer direct access into HANA

• Object access as well as access to content of data model must be controlled within HANA

• Need to have named users in HANA for Information Consumers

Exceptions: no user management for Information Consumers required if

• Access to data does not need to be controlled

• All data access occurs via BI Semantic Layer andSecurity implemented in BusinessObjects Enterprise


User ProvisioningHow to get Users into the System

Creating Named Users in HANAActual Database Users

Create via SAP HANA StudioOr using standard SQL statements

Authentication MethodsUser / Password

Set up and manage passwords using SAP HANA Studio or SQL

Kerberos AuthenticationCertificate-basedRequires Named User in HANA DB

© SAP AG 2011


User ManagementUser and Role Concept

Roles allow grouping privilegesCreate roles for specific tasks, e.g.

Create data models (on a given subset of the data)Activate data modelsConsume models

All types of privileges can be granted to a roleIndividual privilegesRoles ( create a hierarchy of roles)

Roles / privileges can be assigned to usersUser / Role management are closely related

Reflected in almost identical editor

Role: edit model

Role: activate model

User

Role: edit + activate

Package:create / edit

models

SQL:select

Package:activate

SQL:write

runtimeobject

© SAP AG 2011


Managing Users and RolesStep-by-step overview

© SAP AG 2011


Creating RolesUsing SAP HANA Studio

Graphical UI for Creating / managing rolesIn SAP HANA Studio Navigator Tree

Path: <SID> (<User>) Catalog AuthorizationsRight-Click “Roles” folderSelect “New” “Role” from context menu

Using SQL SyntaxRun the following statement:

CREATE ROLE <ROLE_NAME>;

© SAP AG 2011


Assign Privileges to RolesGeneric background information

Two generally different cases:Object / Privilege combinations. E.g.

grant SELECT (privilege) on <TABLE> (object)grant EXECUTE (privilege) on <PROCEDURE> (object)

Direct Privilege Assignment. E.g.grant USER ADMIN (system privilege)grant EXAMPLE_ROLE (Role)

Concept of Grant OptionAllows granting a privilege to other users/roles

Not available for all types of privileges

© SAP AG 2011


Assign Privileges to RolesSearch for Object or Privilege

On the appropriate privilege tab:Click the green iconIn the search box, start typing

For Object/Privilege combinations: the object nameFor direct privilege assignment: the privilege name

Select the desired object or privilegeClick OK

© SAP AG 2011


Assign Privileges to RolesSave the role

Using the “save” button

Using the “deploy” button (green arrow)

Errors during saveTypically: missing privilege for editing user (USER ADMIN)Or missing grant option:

For Object/Privilege combinations: on objectFor direct privilege assignment: on privilege

© SAP AG 2011


Creating UsersUsing SAP HANA Studio

Graphical UI for Creating / managing roles

In SAP HANA Studio Navigator TreePath: <SID> (<User>) Catalog AuthorizationsRight-Click “Users” folderSelect “New” “User” from context menu

Choose authentication methodsDefine the initial password (user/password)Or define the external User ID (e.g. Kerberos)

Other user settingsDefine default clientThis is used as an implicit filter value whenreading from HANA data models

To save the user:

© SAP AG 2011


Grant Role to User

Using Studio:Switch to tab “Granted Roles” in User Editor

Open search dialog ( )Start typing the role nameAdd the roleAllow/disallow granting the role(note: System Privilege “ROLE ADMIN”supersedes this GRANT OPTION)

© SAP AG 2011


Grant Role to UserSave the user

Using the “save” button

Using the “deploy” button (green arrow)

Errors during saveTypically: missing privilege for editing user

E.g.: System privilege ROLE ADMIN missingOr (without ROLE ADMIN): GRANT OPTION for role missing

© SAP AG 2011


Revoke Role from User

Using Studio:Switch to tab “Granted Roles” in User Editor

Select the role from list of granted rolesClick the iconSave the user(this also revokes a GRANT OPTION)

Note on Cascaded Dropping of PrivilegesIf the user had granted the role to other users, revoking the role (and the grant option) also revokes the role from these grantees

© SAP AG 2011


Agenda

© SAP AG 2011

Lesson 7:

User Management

Template Roles

Security Details

Best Practice


User ManagementUser and Role Concept

Types of Privileges in HANASystem Privileges (restrict actions in the database)

E.g “USER ADMIN”; “CREATE SCHEMA”; …Discussed in detail in SAP HANA Security Guide

SQL Privileges (restrict access to data containers)E.g. “SELECT ON <table>”; “DROP ON <schema>”Discussed in detail in SAP HANA Security Guide

Analytic privileges (row-level security for data models)E.g. see only data for cost center 1000

Package privileges (restrictions around modeling)E.g. edit / activate data models in package sap.ecc.fin

© SAP AG 2011


Analytic PrivilegesThe Concept

Analytic Privileges are used to control access to SAP HANA data models Without Analytic Privilege, no data can be retrieved from

Attribute ViewsAnalytic ViewsCalculation Views

Implement row-level security with Analytic Privileges Restrict access to a given data container to selected Attribute Values

Field from Attribute ViewField from Attribute View used in Analytic ViewPrivate Dimension of Analytic ViewAttribute field in Calculation ViewCombinations of the aboveSingle value, range, IN-list

© SAP AG 2011


Create Analytic Privilege (I)Start creation wizard

Analytic Privileges are repository objectsCreate and manage via SAP HANA Studio

Create in any packageDoes not need to be the same package as views

Call creation wizard:Right-click folder “Analytic Privileges” in package

Enter name and descriptionClick Next

© SAP AG 2011


Create Analytic Privilege (II)Select applicable Information Models

Select applicable Information Models

Views have two functions in privilegeViews you want to grant access toViews from which you want to select fields for restrictions

You can add further views to the privilege later

© SAP AG 2011


Create Analytic Privilege (III)Editor Overview

Views used in Analytic Privilege and to which the privilegegrants access

List of fields for Attribute restrictions

List of restrictions implemented for theselected field from the list above.

© SAP AG 2011


Create Analytic Privilege (IV)Add more views

Restrictions apply to all views in list of “Reference Models”

Choose “Add” in “Reference Models” sectionPick any appropriate viewFrom any package

Do not use the “Applicable to All”-optionReason:

Can have surprising side-effectsYou give away control over model access

© SAP AG 2011


Create Analytic Privilege (V)Select field for attribute restriction

A view must have at least one field in Analytic Privilege to be ReadableField may appear in several views from “Reference Models”

restriction will apply to all these views

© SAP AG 2011


Create Analytic Privilege (VI)Implement Value Restriction

You may implement value restrictions for all selected fieldsIf no value restriction implemented no restriction (wildcard)Otherwise: user will only be allowed to see listed values

UI offers single value or range conditionCan add several conditions per field (combined via “AND”)

© SAP AG 2011


Create Analytic Privilege (VII)Save and Activate

Like views: activation required to create run-time objectOnly run-time object is grantable to users / roles

Name of run-time object: “<package>/<privilege_name>”Note: current bug:

Analytic Privilege can only be activated oncecannot change activated Analytic Privilege

© SAP AG 2011


Considerations for Important rolesFrom reporting to data administration

© SAP AG 2011

What kind of roles might be created

Administrative users

Users that set up the system, create other roles, users, …

• SYSTEM the built-in initial administrative user

• Data administrator: owns ERP data, used in data loads, …

• Repository admin: creates initial structure of packages, grants package privileges to modeling users

• User admin: creates users, roles; grants access to data model

Users who implement SAP HANA data models:

Users who create data models, activate models, import/export, …

• Modeling users (creates/edits data models) (restricted to certain packages)

• Model activation (might be integrated in modeling role)

• Creator of Analytic Privileges (might or might not be same as user admin)

• Activation of Analytic Privileges (might or might not be same as above or user admin)

Information Consumer

User who is allowed to read from certain views


Pre-Delivered Roles in SAP HANA

SAP HANA comes with several pre-defined rolesRoles that should (must) be used unchanged

PUBLIC – minimal privileges for a user to work with the database at allIs implicitly granted whenever a user is created

Role templatesCONTENT_ADMIN – the only role in the system with vital privileges, e.g.:– SQL Privileges on Schema _SYS_BIC – with GRANT OPTION– SQL Privileges on Schema _SYS_BI – with GRANT OPTIONMODELING – a very richly privileged role that enables– Creation and activation of Information Models– Creation and activation of Analytic PrivilegesRegard these roles as “templates” name change coming soon– Do not use these roles – build your own roles instead

© SAP AG 2011


Data ManagementBest Practices (I)

Do not place ERP tables into SYSTEM schemaReason: this is the “home”-schema of user SYSTEMSo SYSTEM would own the data

SYSTEM has all privileges on the dataInstead: create a “data admin” userWith that user create a target schema for ERP data

Create one target schema per source systemIf required, also one data admin user per source system

Seperate DB administration and ownership of data

© SAP AG 2011


Data ManagementBest Practices (II)

Important: _SYS_REPO must have access to these schemasRequired: SELECT including permission to grant to others

As owner of the data schema, run:GRANT SELECT ON SCHEMA <data_schema> TO _SYS_REPO

WITH GRANT OPTION

Grant this directly to _SYS_REPO, not to a role (reason: see next slide)

Without this, nobody will be

able to read from activated views

© SAP AG 2011


User ManagementBest Practices (I)

Do not place critical privileges into rolesReason: anyone with “ROLE ADMIN” can grant rolesExamples for such privileges:

“SELECT ON SCHEMA _SYS_BIC WITH GRANT OPTION”“DROP ON SCHEMA <XYZ> WITH GRANT OPTION”

Instead: Create named users who have such privilegesControl access to these users in a safe manner

Control Access to Privilege ROLE ADMINReason: Anyone with this privilege can grant any role

ROLE ADMIN is also required for creating rolesROLE ADMIN supersedes a missing GRANT Privilege for a role

The „GRANT OPTION“ makesthese privileges

powerful

With „ROLE ADMIN“, you don‘t

need an explicitGRANT OPTION

for a role

© SAP AG 2011


User ManagementBest Practices (II)

Do not work with user SYSTEM

After the preceding slides, the reason should be obvious

© SAP AG 2011

Student Exercise Manual

Name HANA 1.0, SP02

Version: Rev. 13

RKT APPLICATION WORKSHOP FOR HANA 1.0

2

Table of Contents

Contents Table of Contents ............................................................................................................................................. 2 Lesson 2: Overview ........................................................................................................................................ 3

2.1 Exercise: Look and Feel ........................................................................................................................ 3 Lesson 3: Architecture Overview ................................................................................................................. 15

3.1 Exercise: Architecture ......................................................................................................................... 15 Lesson 4: Data Provisioning ......................................................................................................................... 19

4.1 Import SAP ERP Metadata into the SAP HANA Database ................................................................ 19 4.2 Upload Data into HANA Using Data Services .................................................................................... 24

Lesson 5: Modelling Overview ..................................................................................................................... 34 Scenario CO-PA......................................................................................................................................... 34 5.1 Create the Attribute Views ................................................................................................................... 35 5.2 Create the Analytical View for Actuals ............................................................................................... 43 5.3 Create the Analytical View for Plan .................................................................................................... 49 5.4 Create the Calculation View ................................................................................................................ 56 5.5 (Optional) Calculation View: SQL Script ............................................................................................ 64 5.6 Export a Model .................................................................................................................................... 68 5.7 Import a Model .................................................................................................................................... 71

Lesson 6: Reporting ....................................................................................................................................... 74 6.1 Exercise: Excel Pivot Tables (ODBO/MDX access) ........................................................................... 74 6.2 Exercise: SAP BusinessObjects Explorer ............................................................................................ 79 6.3 Exercise: Analysis for Office using a local ODBC connection ........................................................... 83

Lesson 7 – (Optional) User Management and Security ................................................................................. 87 7.1 (Optional) Create New User and Assign Basic Privileges ................................................................... 87 7.2 (Optional) Create and assign Analytic Privileges ................................................................................ 94

Appendix ........................................................................................................................................................ 99 SQL Script Example (UNION) .................................................................................................................. 99 SQL Script Example (JOIN) ...................................................................................................................... 99


3

Lesson 2: Overview This section includes an exercise on look and feel of HANA. In this exercise you will log on to the WTS server, and get familiar with navigating in HANA. You will complete the exercise by creating your own package.

2.1 Exercise: Look and Feel 1. To Logon to the WTS landscape go to:

2. Start-Menu Choose Common-Training

3. The In-Memory Computing Studio On has not yet been installed on the WTS desktop.

For this reason, you have to go via a remote desktop connection to another desktop.

Start the Remote Desktop Connection as shown in the screenshot on the right side.

Use the path: Start Menu -> All Programs -> Accessories.


4

4. In the next screen you have to choose one of the available remote desktop servers.

Note: Choose the server RA-XXXXXX-XX (will be specified by the instructor)

Click > Connect.

5. In the Remote Desktop Connection dialog box enter the following user name and password. User: train-xx (where xx represent your assigned number.) Pwd: will be provided by the instructor

Click > OK.

6. Now you are on the right desktop and can start the In-Memory Computing Studio by going to Start -> Programs -> SAP in-memory computing -> hdbstudio.exe


5

7. Open Administration Console

HINT: Hit ‘x’ to close the overview screen.

8. Register a new System. Right Click > Add System... within the Navigator view.

Enter the Hostname, Instance Number and Description.

Hostname : lt00XX.wdf.sap.corp (XX will be specified by the instructor)

Instance Number : YY (will be provided by the instructor)

(see screenshot for details)

Click > Next.


6

9. Enter your assigned User and Password credentials.

Username: STUDENTxx where xx represents your assigned number

Password: will be provided by the instructor

Click > Finish.

10. Change your initial password

Minimum 8 characters

Must contain capital and small letters

Must contain numbers

Example: Abcd1234

Hint: If prompted for a security fallback for your password, click No.

Hint: If your HANA system is not properly connected to the SAP HANA Studio (red), choose Refresh from the context menu. If necessary, close and reopen the SAP HANA Studio.


7

11. The first customization you should do is now to adjust the default setting of the default client in the studio preferences.

Therefore go in the top menu and choose Window -> Preferences...

12. Next, expand the Information Modeler node in the tree and click on “Default Model Parameters”.

Now ensure that the client is 800.

13. The whole perspective setup can be maintained via the Window menu on top.

You have access via Window -> Open Perspective -> Other to all pre-delivered and saved perspectives.


8

14. To switch easily between different perspectives you can click on the toolbar on top on the corresponding button.

Each open perspective will be shown here.

15. To customize a perspective choose the Window menu -> Customize Perspective.


9

16. In the perspective customization the user can change Tool Bar, Menus, Command Group Availabilities and Shortcuts.

If an element is greyed out it means this element is not available.

Please keep in mind that the studio is running in the Eclipse Framework and not all components of Eclipse are required for HANA.

17. To open a new view just go to the window menu again and drop down menu Show View -> Other...


10

18. In the “Show View” dialog box you can choose which view you want to add to your perspective.

Next, double click on the view or click on “OK” after selecting the view to add it in your perspective.

Then, you can drag the view to a sidebar; put the view as footer or on top of the perspective.

19. For the SAP HANA Studio the central point of Access is the Navigator View, which is usually placed on the left side of the screen.

In the Navigator tree you can incorporate several SAP HANA instances directly connected with the appropriate user.

Note that there are two main sections in the navigation tree.

o The Catalog node navigates to the physical tables, views, etc.

o The Content node navigates to Attribute Views, Analytic Views, Calculation Views, Functions and Analytical Privileges


11

20. The “Catalog” contains all Database schemas which will be automatically created when a user is created.

Each Schema contains a folder for Column Views, Functions, Tables and Views.

Also notice the “Catalog” has a folder for Authorizations and another folder where Public Synonyms will be maintained.

21. The Folder “Content” contains the Information Model packages.

Each package contains a folder for Attribute Views, Analytic Views, Calculation Views, Analytic Privileges and Procedures.

22. The Navigation tree can be customized via a small dropdown icon.


12

23. In the Navigation tree customizing you can select which items should show up in the tree as a node and which should not show up.

So you can show/hide the Information models in the Administration console, show/hide the Administration node, etc.

24. After all customizing and you brought a lot of trouble in your screen – there is an easy way to RESET the perspective!

Reset the Perspective now

25. The Administration console reflects the pre-delivered Administration Perspective.

To get to this screen, choose the Navigate tab followed by a click on the ‘administrative’ icon (looks like tools).

According to your user rights you have in this perspective options to administrate the SAP HANA Instances.


13

26. Create a delivery unit that will contain all your models. Delivery units can be transported.

First Open the Information Modeller perspective.

From the Help menu > Select Quick Launch.

27. Select Delivery Units from the Setup section.

28. Click on Create.

29. Enter STUDENTXX for the Name and Responsible person, enter 1.0 for the Version. Remember to replace XX with your assigned student number.

HINT: In order to create delivery units ensure that your user ID has the following System Privileges assigned: REPO.MAINTAIN_DELIVERY_UNITS or the following Role assigned: REPO_ADMIN_ROLE


14

30. Verify that your Delivery unit is created.

31. Create a new package. Select the Content folder > Right Click > New Package.

32. Enter studentXX for the package name & description. Ensure to select your Delivery Unit (STUDENTXX). Remember to replace XX with your assigned student number.

NOTE: If your newly previously created delivery unit it not displayed close and reopen the Studio.

33. As a result you will see the following folder structure created automatically for you under the newly created package.


15

Lesson 3: Architecture Overview This section includes an exercise on Architecture. The goal is to find out architecture-related information about some tables. In this section you will learn:

How to see whether a table is in row store or in column store How to see what indexes are defined for a table.

We do this example for table “MARA” in the “TRAINING” schema; and for table “P_SCHEMAS_” from the “SYS” schema.

3.1 Exercise: Architecture 1. Log on to the SAP HANA Studio with

your user.

For this exercise it does not matter whether you are using the “Administration” perspective or the “Information Modeler” perspective.

So let’s start looking for table “MARA”.

2. In the “Navigator” Tree, expand the node “Catalog”

3. Expand the node for the “TRAINING”-Schema. You may try what happens when you expand the “Tables” folder within that schema.


16

4. This shows the tables in that schema. We don’t want to search this way. So we collapse the “Tables” folder again.

5. Right-click the “Tables” folder and select “Filter” from the context menu. This opens a dialog box.

6. In that dialog box, you can enter a table name.

Note: you are opening the list of tables within schema “TRAINING”, so we are searching for tables within the TRAINING schema.

Therefore, do not specify the Schema name in the search field.

Enter “MARA” in the input field and confirm with “OK”


17

7. After a short while, this will filter the list of tables by all tables whose names starts with “MARA”.

8. Expand the list of tables. That list should now be filtered.

9. The context menu for a table offers several options. We are interested in the table metadata which we can reach by “Opening” the table Definition (or by double-clicking the table”).

Other options which are not used here include:

Open Data Preview: Explore the table contents

Open Content: simple display of the table contents.


18

10. Once you double-click the table, the table definition is displayed.

This screen shows the table structure, i.e. all fields of the table with their types etc.

Whether the table is in column store or in row store is shown in the top-right corner of this screen.

MARA obviously is a column-table.

11. The key fields of the table are marked in column “Key”.

For MARA, these are the client and the material number, aka “MANDT” and “MATNR”.

12. Let’s now look at the table “P_QUERYPLANS” from the “SYS” schema.

You should be able to verify that:

The table is a row-store table There is one index defined:

IDX_P_QUERY_PLANS which is an index with indexed column “NAME” sorted in ascending order;


19

Lesson 4: Data Provisioning This section includes an exercise on data services.

4.1 Import SAP ERP Metadata into the SAP HANA Database

1. Before importing metadata into the SAP HANA Database, you must verify the connection settings to your SAP BusinessObjects Data Services instance. Please note that the Import Server settings are specific to a single HANA server instance.

Please navigate to Information Modeler Perspective and Open the Quick-Launch view

Click on the Manage Connections... button and connect to the HANA instance into which you wish to import metadata (Select the STUDENTXX instance - Remember to replace XX with your assigned student number)

Click on Configure Import Server

In case the configuration is empty, use the following connection details and hit the apply button.

Server Address: wdflbmt2287.wdf.sap.corp

Repository Name: DSREPOxx

ODBC Data Source: <empty>

NOTE: Make sure to select the correct Repository!


20

2. Select Quick Launch -> Content -> Import

In the import screen you can search an import source by entering the name of the source in the text field or,

Click on Information Modeler folder -> Source Objects -> Next.

3. Select the target system (your HANA-system) and click Next.

SEARCH


21

5. Select the depending objects for Import by two ways:

Use the ERP application hierarchy to drill down to your required table.

Hint: In case of many hierarchy levels you should use the Search function and enter table name directly.

Search for TCURR using the search field.

Select the TCURR in the object list and click on add to put it to target list.

4. You can display connections of DataStore type “SAP Applications” that are imported from the specified DataServices repository. This datastore is already created in Data Services Repository.

In our exercise we want to import metadata from ERP-Table TCURR, therefore you don´t have to change the default settings.

Hint: If no DataSource Connection is displayed, close and reopen the Studio.


22

6. Select your Schema (studentXX) from the default catalog for the metadata import.

Then click on ‘Next’.

Click on Validate.

Make sure the status column has a green checkbox.

Click on Next.

Click on Finish


23

A ‘success message’ in the Job log will confirm the metadata table import.

Right click on the STUDENTXX Schema in the Navigator pane and click on Refresh.

You should now see the TCURR table under the Tables folder.


24

4.2 Upload Data into HANA Using Data Services

Import SAP ERP Metadata into SAP BusinessObjects Data Services

1. Start to SAP BusinessObjects Dataservices Designer

Use the path: Start Menu -> Programs -> SAP BusinessObjects Data Services 4.0 SP1 -> Data Services Designer.

2. Enter your assigned User and Password credentials.

Username: studentXX where XX represents your assigned number.

Password: will be provided by the instructor.

Click > Log On.

3. If the log on process is successful, a list of repositories ‘DSREPOxx’ will appear.

Choose your repository DSREPOxx

Click Ok


25

4. In the pane “Local Object Library” choose the view on the DataStores.

5. Select the DS_ECC Datastore and make sure you can see the Tables child node.

6. Right-click on the Tables node and click on Import By Name...

7. Enter TCURR as the name of the table you want to import.

Click on import.

You can now use the TCURR table from the ‘DS_ECC’ Datastore as either a data source or a data target. For this exercise, it will be your data source.


26

Create a new DataStore for HANA in SAP BusinessObjects Data Services

1. In the Local Object Library, create a new Datastore.

Right-click on the white background.

Choose New

2. In the Local Object Library, create a new Datastore.

Datastore name: HANA_STUDENTXX

Datastore type: Database

Database type: HANA

Database version: HANA 1.x

Data source: HANA_YYY (YYY as provided by the instructor)

User name: STUDENTXX

Password: as you changed it, i.e. Abcd1234


27

Import SAP HANA Database Metadata into SAP BusinessObjects Data Services

1. Right-click on the Tables node of your new Datastore HANA_STUDENTXX and click on Import By Name...

2. Enter the following...

Name - TCURR

Owner - STUDENTXX

3. You can now use the TCURR table from the ‘HANA_STUDENTXX’ Datastore as either a data source or a data target. For this exercise, it will be your data target.


28

Create a batch job in SAP BusinessObjects Data Services to extract data from SAP ERP and load it into SAP HANA Database

1. Click on the ‘Create Project’ link of the Getting Started section.

2. Enter STUDENTXX as the project name

3. Click on Create.

4. In the Project Area located on the left side, right-click on your new project and click on New Batch Job.

5. Enter JOB_STUDENTXX as the name of the new batch job


29

6. Click on the Dataflow icon from the toolbar located on the right side of the main SAP BusinessObjects Data Services Designer window.

7. Click on the canvas to the left of the toolbar to add a new Dataflow to your new batch job.

8. Enter DF_STUDENTXX as the Dataflow name.

9. Double-click on the new Dataflow

10. Click on the TCURR table from the ‘DS_ECC’ Datastore, drag onto the canvas and drop it.


30

11. Click on the TCURR table from the ‘HANA_STUDENTXX’ Datastore, drag onto the canvas, drop it and click on Make Target.

12. Click on the Query transform icon and click on the canvas.

13. Once you have all three items on the canvas placed like this, click on the small square on the right-side of the source TCURR table and drag it to the small square on the left side of the Query.

14. Then click on the small square on the right-side of the Query and drag it to the small square on the left side of the target TCURR table.


31

15. Once you’ve connected all three items, double-click on the Query transform in the middle.

16. From the Schema In located on the left side, select all the fields under the TCURR schema and right-click and click on Map to Output. This will map all fields from the inbound schema to fields of the output schema that have the same name.

17. Close the Query window and go back to the Dataflow.

18. Validate the dataflow by clicking on the Validate icon from the toolbar located above and a little bit to the left of the canvas where you created the Dataflow

The result of the validation should show that there are no errors in your Dataflow. If there are, please notify the instructor.


32

19. Go to the project area in the upper left-hand corner and right-click on your newly created job and click on Execute.

20. If you are prompted to save changes, click on yes.

21. Click OK on the Execution Properties window to accept all defaults.


33

A log is written during the execution of the batch job. If the batch job is successful, you will see the following text at the bottom of the log.

22. Go to the SAP HANA Studio, find your Schema (STUDENTXX), open the Tables folder and right-click on the Exchange Rates (TCURR) table and click on Open Data Preview.

Here are the results of your SAP BusinessObjects Data Services batch job. You’ve successfully extracted data from an SAP ERP system and loaded it into SAP HANA Database. Congratulations!


34

Lesson 5: Modelling Overview Lesson Objectives The SAP HANA 1.0 hosts an application tool called SAP HANA Studio which incorporates the data modeling function within Information Modeler perspective. After completing this lesson, you will be able to

Use the Information Modeller Create Attribute, Analytic, and Calculation views: Add or remove text tables Create basic JOIN operations Activate and deploy views Export and import models

Scenario CO-PA You are at a customer site and have been asked to build an Information Model for HANA for the purpose of displaying CO-PA data. You have been asked to produce the following 3 reports. This section takes you through the process to create the models to be used later in the reporting exercise. Note the details of the CO-PA tables are covered in the presentation. You will only build a model for report 3.


35

5.1 Create the Attribute Views

1. Please navigate in the “Content” to your own package.

NOTE: Please make sure you select your own package (STUDENTXX where XX represents your assigned number).

2. Create a new Attribute View:

Select the Attribute View of your package and using the context menu (right click), New > Attribute View to create new Attribute View.

Name: LOCATION_XX

Description: Customer Location XX.

Press next to Attribute View to the select objects Screen.


36

3. Choose TRAINING and select the table KNA1 to build the Attribute View.

Enter KNA1 then hit the add button.

Hint: Using Search help for selecting the right tables OR use the solution icon on upper right.

4. Repeat the above steps to add T005U.

Click Finish to get into the Attribute View Editor

Hint: If the dialog box disappears and you do not have an Add button – experiment with the Add Tables icon on upper right.

Tip: In case the dialog below "New Attribute View" disappears, you can hit the "Add table" button and continue the table selection.


37

5. The Attribute View editor gets populated with the selected tables.

This is where you will define the relationships of the attributes.

6. User will now select the fields for use in the attribute view

Select the key field KUNNR and right mouse click on field. Choose Add as Key Attribute.

Result: The KUNNR:KNA1.KUNNR shows in the Output frame.

7. Display the properties of KUNNR. Select KUNNR from the Output frame.

On the Property Tab for field KUNNR, select Description Mapping and choose the field TRAINING.KNA1.NAME1 from the drop down list.


38

8. Join field LAND1 from KNA1 to LAND1 of T005U as a text table join.

Click on the join and change the join type in the property view to ”Text Join”.

Select SPRAS for the Language Column.

9. Join field REGIO from KNA1 to T005U field BLAND.

As before set the Join type to ”Text Join”.

Select as “Language Column” -> SPRAS

Save.

10. Add a second text table to the attribute view.

You can do it by selecting the "Add table" button and continue the table selection.

Enter table T005T and select the TRAINING table from the list.

Click OK.

Result: Table T005T is added to the Data Foundation tab.


39

11. Define a text join between field LAND1 from KNA1 to field LAND1 from T005T

Right click on join and change the join type in the property view to ”Text Join”.

At the join “Property” frame select as “Language Column” -> SPRAS

12. Add KNA1.LAND1 and KNA1.REGIO as a attributes with a right click -> “Add as Attribute. Select LAND1 from the Output

frame On the Property Tab for field

LAND1, select Description Mapping and choose the field TRAINING.T005T.LANDX. HINT: Only select or highlight LAND1 to get to the property tab.

13. Select REGIO from the Output. On the Property Tab for field

REGIO, select Description Mapping and choose the field TRAINING.T005U.BEZEI.

Save.


40

14. Add ORT01 as an attribute.

This is a description field for CITY so in this case there is no need to map to a text table.

Save.

15. On the Attribute View LOCATION_XX, right click and select Activate.

Result: The Deployment Log will show successful or give an error message.

16. Choose Attribute View, LOCATION_XX. Right click to choose Data Preview.


41

Note that KUNNR, LAND1 and REGIO have a description displayed in the Data Preview.

17. Navigate to the “Catalog”. Select the folder _SYS_BIC, expand Column Views and locate the prefix studentxx/LOCATION_XX.

18. You may also display the definition

of the Attribute View, by right clicking on the column view, studentxx/LOCATION_XX and choose Definition.

This gives the table definition which will be needed for reference when creating an Attribute View for use on Calculation Views. (We’ll do this in a later exercise.)

19. Next create a new Attribute View for product.

Name it PRODUCT_XX with description PRODUCT_XX.

Choose the tables MARA and MAKT from the Schema TRAINING


42

Join table MARA and table MAKT using the field MATNR

Define the join as a text join on the properties tab.

Define the language column as SPRAS on the Property Tab.

Add MATNR as key attribute to the Output Frame

Define the description mapping for the key attribute MARA.MAKTX.

Save, Activate & Preview.


43

5.2 Create the Analytical View for Actuals 1. Close all open views prior to creating a

new analytical view.

Create an analytical view CEA1_XX (XX being your student number allocated), with the description Contribution Margin for Actuals XX.

Choose your Schema STUDENTxx as default schema.

Click Next

2. Find a table, CE1IDEA and click Add.

Remember you have to find the table by clicking on the arrow next to the input field

Important – Do not click finish or you will have to start over.

Click Next.


44

3. Navigate to your package, expand the folder and select the attribute views for PRODUCT_XX and LOCATION_XX.

Click on Finish.

4. Choose the Data Foundation Tab.

Result: You will see table CE1IDEA in your data foundation tab.

5. Navigate to the Logical View Tab to see the two attribute views.

Note that the Data Foundation is empty.

It will be filled once you select your fields (attributes and measures)


45

6. Navigate to the Data Foundation Tab.

Select the two fields KNDNR and ARTNR and add them as attributes (right click).

7. Navigate to the Logical Tab.

Notice that the Data Foundation now has two fields.

Join DataFoundation.ARTNR to PRODUCT_xx.MATNR.

Join DataFoundation.KNDNR to LOCATION_xx_KUNNR.

8. Navigate to Data Foundation Tab, where we will define further selections.

Apply filters on the fields PALEDGER and VRGAR (record type).

Select PALEDGER > right click > Apply Filter.

o Choose Operator Equal from the Apply Filter dialog box

o Specify the value 01.

For VRGAR, choose Operator Equal and specify the value F.

Save.


46

9. Notice there is now a filter icon next to the PALEDGER and VRGAR.

10. Next select the attributes to be included in the analytical view.

Choose from CE1IDEA the following fields:

o PERIO,

o VKORG,

o PLIKZ.

HINT: To find the fields quickly – enter the name of the filed in the Find Column field.

11. Next select the measures to be included in the analytical view.


o VV010

o VV070

o VV290

o VV960


47

12. Rename the measures in the Name field of the Property Tab for each measure.

Use copy and paste from the table to ensure that use the exact descriptions.

Change From Change To

VV010 GrossRevenue

VV070 SalesDeduction

VV290 ProductionVariance

VV960 OtherExpenses

Save.

13. Next define the calculated measures to be included in the analytical view.

Right click on Calculated Measures and choose New.

14. Create the first Calculated Measure, NETREVENUE.

Select Decimal data type with length 15 and Scale 0

Double click on the desired measure for it to appear in the expression editor. Either type in the minus sign or double click on the Operator.

Continue to create all other needed Calculated Measures.


48

Name Description Data Type Length FormulaNETREVENUE NetRevenue DECIMAL 15 "GrossRevenue"-"SalesDeduction"CM1 Contribution Margin1 DECIMAL 15 "NetRevenue"-"ProductionVariance"CM2 Contribution Margin2 DECIMAL 15 "CM1"-"OtherExpenses"

Save and Activate your Analytical View.

15. Display the data in your Analytical View.

Right click on Analytical View and select Data Preview


49

5.3 Create the Analytical View for Plan

16. Close all open views prior to creating a new Analytical view.

Create an analytical view CEP1_XX with the description Contribution Margin for Planning 09.

17. Find a table, CE2IDEA and click Add.

Remember you can find the table by clicking on the arrow next to the input field

Click Next.

Important – Do not click finish or you will have to start over.

18. Navigate to your package, expand it and select attribute views for PRODUCT_XX and LOCATION_XX.

Click on Finish.


50

19. Choose the Data Foundation Tab.

You will see CE2IDEA in the data foundation tab.

20. Choose the Logical View Tab to see the two attribute views created previously.

Note that the Data Foundation is empty.


51

21. Navigate to the Data Foundation Tab again.

Add KNDNR and ARTNR as attributes (right click).

22. Navigate to the Logical Tab again.

Notice the Data Foundation now has two fields.

Join fields ARTNR and MATNR.

Join KNDNR and KUNNR.

23. Navigate to Data Foundation Tab, where we will define further selections.

Apply filters on the fields PALEDGER and VRGAR (record type).

Select PALEDGER > right click > Apply Filter.

o Choose Operator Equal from the Apply Filter dialog box

o Specify the value 01.

For VRGAR, choose Operator Equal and specify the value F.

Save.


52

24. Notice there is now a filter icon next to the PALEDGER and VRGAR.

25. Next select the attributes to be included in the analytical view.


o PERBL,

o VKORG.

26. Next select the measures to be included in the analytical view.


o VV010001,

o VV070001

o VV290001

o VV960001.


53

27. Rename the measures in the Name field of the Property Tab for each measure.

Ensure the exact names (capital and small letters)

Change From Change To

VV010001 GrossRevenue

VV070001 SalesDeduction

VV290001 ProductionVariance

VV960001 OtherExpenses

Save.

28. Next define the calculated measures to be included in the analytical view.

Right click on Calculated Measures and choose New.


54

29. Create the first Calculated Measure, NETREVENUE.

Select Decimal data type with length 15, 0

Double click on the desired measure for it to appear in the expression editor. Either type in the minus sign or double click on the Operator.

Continue to create all other needed Calculated Measures.

Name Description Data Type Length FormulaNETREVENUE NetRevenue DECIMAL 15 "GrossRevenue"-"SalesDeduction"CM1 Contribution Margin1 DECIMAL 15 "NetRevenue"-"ProductionVariance"CM2 Contribution Margin2 DECIMAL 15 "CM1"-"OtherExpenses"

30. You should have the following Calculated Measures.


55

31. Save and activate your Analytical view. Preview the Analytical view as well to see if you get data.


56

5.4 Create the Calculation View 1. Navigate to the Calculation View

under your student package.

Right click to create a new Calculation View.

Name your calculation view CE_PLAN_ACTUAL_XX

Description: Plan Actual Comparison for CO-PA XX

Specify Graphical for the type of the Calculation View.

Choose your schema STUDENTXX

Click Next.

2. Since we will be reading from existing Analytical Views you do not have to select any tables.

Click Next.


57

3. Select the previously created 2 Analytical Views within the studentXX package.

CEA1_XX

CEP1_XX

Replace XX with your student number.

Click Finish.

4. As a result the Graphical Calculation View editor will open.


58

5. From the Tools Palette select 2 Projection graphical nodes one for each Analytical View. This is where you will set the Actual versus Planned data indicator.

6. Double Click on each Projection node and rename each to Projection_A and Projection_P


59

7. Add a Union Graphical node and Rename the node to Union.

8. With the mouse pointer hover over each graphical node and draw a connection line between the nodes as shown on the right representing a data flow graph.


60

9. Add a new Calculated Column called KPLIKZ.

In the diagram select the Projection_A node. Within the Output right click on Calculated Columns > New.

10. Enter KPLIKZ for the name of the field. Select INTEGER and enter 0 in the Expression Editor as the Planned Indicator value.

Click OK.

11. Ensure the Calculated Column is visible in the Output of Projection_A.


61

12. Add all the fields of CEA1_XX to the Output of the Projection_A node.

Select the Projection A node, within the details view select all the fields > Right Click > Add to Output.

HINT: Use the CTRL key to select multiple fields except !!!

** DO NOT ADD FIELD PLIKZ ***

13. Proceed to work on the Projection_P node. As before add the field KPLIKZ but this time set the Expression value to 1 as an indication for planned data.

14. Since we will eventually use a Union to combine the results from both Analytical views we have to ensure that the field names are identical in both views. After you have added all of the CEP1_XX fields to the Output select the field PERBL (within Output of Projection_P) and then within the properties view rename the PERBL field to PERIO

Hint: If renaming is not allowed, close and reopen the Studio.


62

15. Proceed to select and work with the Union node. Within the details of the Union CTRL select all the fields from the Projection_A node > Right Click > Add to Target.

16. The result will look as follows.

17. Scroll down and select all the fields on the Projection_P node. Since we want to combine the two analytical views we need to map the fields from both views to each other. Right Click > Map to Target.

You can also select each individual field on the left and drag & drop it over the corresponding field on the right hand side.

HINT : You can also use the automatic mapping by name


63

18. The completed Calculation View mapping should look as follows.

Save your work.

19. Click on the Output Node in the main diagram. Within the Details view pane select each field > Right Click > ‘Add the field as Attribute’ or as Measure according to the following.

Activate and Preview

HINT :

Make sure that the Participant Element Check is not selected

Quick Launch tab -> Setup -> Manage Preferences -> Validation Rules

Uncheck the Participant Element Check under the Calculation View section


64

5.5 (Optional) Calculation View: SQL Script

1. Create a Script based Calculation View.

Right click on Calculation views > New > Calculation View...

2. Enter CE_PLAN_ACTUAL_XX2 for the

name of the Calculation view.

Description: Plan Actual Comparison for CO-PA (SQL Script) XX

Select SQL Script for the type and be sure to select the STUDENTxx schema.

Click Finish.

3. The following screen opens.


65

4. In the left side of the diagram double click on the Script Node. Before entering code into the middle section click on the icon Define Output Parameter within the Output section in the right side of the screen.

5. Enter all the output fields according including the corresponding Data Type and Length.

WARNING: While defining the Output for the Data type VARCHAR, DO NOT click on the “Scale” fields.

HINT: List of fields and data types for the output table:

Name Data type Length Scale

1 MATNR VARCHAR 40 0

2 KUNNR VARCHAR 35 0

3 REGIO VARCHAR 20 0

4 LANDX VARCHAR 15 0

5 ORT01 VARCHAR 35 0

6 PERIO VARCHAR 7 0

7 VKORG VARCHAR 4 0

8 KPLIKZ VARCHAR 1 0

9 GROSSREV DECIMAL 15 0

10 SALESDEC DECIMAL 15 0

11 PRODVAR DECIMAL 15 0

12 OTHEREXP DECIMAL 15 0


66

13 NETREV DECIMAL 15 0

14 CM1 DECIMAL 15 0

15 CM2 DECIMAL 15 0

6. Refer to the Appendix (SQL Script Example 1) and copy all the SQL code statements and past it between the BEGIN & END section replacing the “var_out = ...” code.

You find an electronic version of the SQL Script template in

Start -> My Documents -> My Documents -> “01 – Calc View Template – Union.txt”

7. The completed SQL Script. Remember to replace XX with your assigned number at all occurrences.

Save your work.

8. Click on the Output Node in the Scenario on the left hand side. Within the Script View details select all the Attributes > Right Click > Add as Attribute to move the fields into the outputs over to the right hand side of the screen. Proceed to do the same for the measures.

Save your work.


67

9. Activate and Preview.


68

5.6 Export a Model 1. Based on what you’ve learned thus far,

create a new attribute view under your package.

For the purposes of this exercise make the view simple, one table, no joins, etc. Alternatively, you can copy your attribute view LOCATION_XX.

Name your view DUMMYxx, where xx represents your assigned number

Save and activate

2. Export your attribute view.

Select File Export.

Select > Information Modeler > Information Models,

Click > Next

OR

From the Quick Launch screen, under Content, Select EXPORT


69

3. Select your system, Click > Next.

4. Highlight the Attribute View, DUMMYxx, click > Add

Enter the target location for the Export.

HINT: Use the path to the desktop. The process will create a folder on the desktop. The name of the folder should be the same name as the system ID (SID) of the HANA system you are logged into. Within the folder you will find your new exported file.

Click > Finish

The status of the export in the job log should say “Success”.

If you double click on the log entry you can see the details of the job


70

5. Navigate to the location the file was placed.

Open the file to ensure the XML is within the file.

Congratulations, you’ve exported your first file!


71

5.7 Import a Model

6. Now that the export was successful, import the xml file that was created.

Select File IMPORT

OR

From the Quick Launch view, under CONTENT, Select IMPORT


72

7. Select Information Models, Click > Next

8. Select the target system for the import and Click > Next


73

9. Navigate to the file location

Browse to the folder into which you exported your model (named SID with SID = system ID)

In the window “Models for Import” locate the XML document corresponding to your DUMMYxx attribute view and add it.

Click > Finish

10. Look at the Job Log status of the import.

It appears the import of the attribute view failed.

The reason for the failure is because the view already existed.

Delete the view from your package and re-import.

Confirm the status in the Job log is Success

11. In the Navigator window, refresh the folder attribute views in your package studentXX

The DUMMYxx attribute view reappeared

Activate

Preview the data


74

Lesson 6: Reporting This section includes exercises on various BI client tools: Microsoft Excel, SAP Business Objects Explorer, and SAP BusinessObjects Analysis

6.1 Exercise: Excel Pivot Tables (ODBO/MDX access) This exercise focuses on the basics of Excel Pivot Table access to HANA data. Excel Pivot Table access is provided via a native ODBO (OLE DB for OLAP). Any ODBO-enabled client can use this driver so this is just one example from Excel 2007:

1. Initiate the Excel Data Connection Wizard

Open Excel 2007

Click on the DATA menu

Select “From Other Sources”

Select “From Data Connection Wizard”

Result: “Data Connection Wizard” launches

2. Select Other/Advanced drivers then click “NEXT”


75

3. Select “SAP HANA MDX Provider” (Naming as of course development time) Click “Next” (do not click “OK” and do not double-click “SAP NewDB MDX Provider”

4. Enter system logon info provided by your instructor.

Host : lt00XX.wdf.sap.corp

Instance number : YY

User : STUDENTXX

Password : provided by the instructor

Test the connection in order to verify the credentials


76

5. Select a cube (analytic or calculation view) from the “database” selection.

Select studentxx from the dropdown

Select “CE_PLAN_ACTUAL_XX”

Click NEXT

6. Accept the proposed file name for storing the data connection.

Enable “Save password in file” (Saving password is a recommended setting for this RKT exercise)

Carefully read the confirmation dialog : click “Yes” in the confirmation dialog

Click “Finish” in the Data Connection Wizard


77

7. To open the connection, simply accept the proposed Pivot Table report properties. If necessary, re-enter your Password.

8. An empty Pivot Table should appear, and the list of fields available from the right panel “PivotTable Field List”


78

9. Select fields from the right panel and drag and drop them onto the row, column and data items areas of the PivotTable

Analyze the result shown


79

6.2 Exercise: SAP BusinessObjects Explorer In Internet Explorer, connect to SAP Business Objects Explorer on the BI 4 system. Use the connection details provided by the instructor, the URL should look like http://<hostname>:<portnumber>/explorer

Here: http://wdflbmt2268.wdf.sap.corp:8080/explorer

Log on using the credentials provided by the instructor: Language: English (United States) System: <hostname>:<port number> User: STUDENTXX Password: provided by the instructor Authentication: Enterprise

1. Click “Manage Spaces”:


80

2. Expand “SAP High-Performance Analytic Appliance (SAP HANA) 1.0” Expand the Connection that is available (RC_HANA) Select the Calculation View “studentXX/CE_PLAN_ACTUAL_XX”

3. Click on “New” to create a new Information Space on this calculation view.

4. From the Properties tab, enter a name “STUDENTXX_INFOSPACE”, check the option “Show on Home page”, and select the Folder Favorites


81

Go to the next tab “Objects”, add dimensions and measures to the Information Space by double clicking (or drag and drop) on the objects listed in the left pane. Click “OK” when your selection is made.

5. “Index” your newly created information space:

Once the indexing completed, a green tick icon should appear in the status column.


82

6. From the top menu bar, go back to the “Home” tab

7. And refresh the list of information spaces available from the “Home” page :

8. Open the information space you have just created:

9. You are now ready to explore your data set


83

6.3 Exercise: Analysis for Office using a local ODBC connection A pre-beta-version of Analysis for Office (AAO) has been installed in the training system. In this exercise you will use AAO to connect to SAP HANA through a locally defined ODBC connection. The ODBC connection has already been created by the administrator. 1. Start AAO from the Start Menu:

a. Start Menu b. Programs c. SAP BusinessObjects d. Analysis for Microsoft Excel

2. Start the “Select Data Source” wizard:


84

3. In order to use a local ODBC connection (instead of authenticating against BOE and using a relational DB connection published to CMC), click “skip” in the wizard:

4. Select the ODBC connection named “HANA_YYY” (YYY as provided by your Instructor), click “Next”

5. Enter your SAP HANA user name and password, click “OK”:

HINT: Make sure that the schema “_SYS_REPO” and “_SYS_BI” is part of the SQL Privilege or to have the role “INFORMATION_CONSUMER_ROLE” containing the “_SYS_REPO” and “_SYS_BI” schema as a SQL Privilege.


85

6. Find and expand your package (studentXX), select one of the views you have created, click “OK”

7. A report based on that view is shown.


86

8. Drag and drop dimensions and measures in the rows and columns to navigate in that view and build your report

To filter members or measures, right click on the row or column item


87

Lesson 7 – (Optional) User Management and Security Goal: This lesson will demonstrate which minimum set of privileges a user needs in order to read data from one particular data model in SAP HANA. You will create a “reporting” user named “TESTXX” (XX being your group number) which you will supply with sufficient privileges to read data from the data model you have created earlier. In this Exercise you will do the following tasks:

‐ Create a new user TESTXX ‐ Add Package Privileges to user TESTXX these will allow browsing the list of packages and seeing the views inside of the packages it is only needed for preview from inside of SAP HANA Studio. The privilege is not required for using other reporting tools. for simplicity, we collected all require package privileges into one role.

‐ Add SQL privileges to user TESTXX ‐ Create an Analytic Privilege for an Analytic View, based on one of the Analytic Views you created ‐ Assign these Analytic Privileges to user TESTXX ‐ Verify that the security concept works as described.

7.1 (Optional) Create New User and Assign Basic Privileges Add user “TESTXX” to your SAP HANA Studio: 1. In the navigator tree, go to Catalog ->

Authorization -> Users

Right-click and create a new User

HINT: Make sure to have the role “SAP_USER_ADMIN” as a Granted Role.


88

2. Enter user name “TESTXX”

where xx represents your assigned number.

Password: “Init1234”

Session Client: 800

In our ERP tables, the client is 800.

Then SAVE the user.

3. Add a new system with user TESTXX

Right click in the Navigator Tree

Provide the same server hostname given by the instructor.


89

4. Finish and confirm the new password Suggestion: “Abcd1234”

Click “OK”

5. Right-click the new entry for System

HDB and user TESTXX in the Navigator tree Choose “Refresh” from the context menu. This will update the system status in your Navigator tree.

Abcd1234


90

Verify that the user cannot view your Analytic Views or the Calculation View you have created: 6. Work as user TESTXX

Try navigating to the following path HDB (TESTXX) Content studentxx Analytic Views On trying to expand folder “Content” you should receive an error message as shown on the right. This is because access to the content tree (design time versions of Information Models) is restricted by Package Privileges. User TESTXX does not have any Package Privileges assigned.

Add Package Privileges to user TESTXX 7. Switch to the user editor for user

TESTXX Verify that the user who opened the dialog is your user STUDENTXX Within the editor, switch to tab “Granted Roles”

8. There is a predefined role that contains all privileges needed to browse the Content Tree and allow you to attempt a preview.

Click the green -icon to add a new role to user TESTXX. In the search dialog, start typing “REPO_ADMIN_ROLE”. Once the “Search-as-you-type” finds the desired role, highlight role “REPO_ADMIN_ROLE” in the list of “Matching items”, then click “OK”

User who opened the editor

User being edited


91

9. Save the user profile: Either click the “Save” icon Or hit “Ctrl+s” We will continue using this user editor for user TESTXX, so do not close it.

Verify that the user cannot view your analytic views nor the calculation view you have created: 10. Work as user TESTXX

Right-click the Content-folder Select “Refresh” from the context menu. This should now show the list of all packages in the system.

11. Work as user TESTXX Navigate to the following path HDB (TESTXX) Content studentxx Analytic Views Right-click the Analytic View “CEA1_XX” Select “Data Preview” from the context menu. (You may do the same for the other Analytic Views or for the Calculation view)

12. Data preview should give you an error message as in the screenshot to the right. The reason for this message is that the user is missing SQL privileges to access the runtime object of the Analytic View.

Means there is a missing privilege


92

Add SQL Privileges to the user

13. Again make sure the user editor for user TESTXX is opened by user STUDENTXX. Switch to tab “SQL Privileges”.

Click the -icon

14. In the search window, start typing “studentXX/CEA1_XX” (where both occurences of XX must be replaced by your group number). Hint: including the package name in the search will greatly help you find the required view (compared to only trying to search for “CEA1_XX” Select the appropriate cube from the list of “Matching items”. Click “OK”.

15. Now you have selected the object for which you want to grant SQL privileges, you also have to choose what privilege to grant. For reading from an object, we need to grant the SELECT-privilege. Highlight the SQL Object “studentXX/CEA1_XX” Activate the check box for the “SELECT”-Privilege.

16. Save the User TESTXX.


User being edited


93

Verify that the user still cannot read from the views 17. Work as user TESTXX

Navigate to the following path HDB (TESTXX) Content studentxx Analytic Views Right-click the Analytic View “CEA1_XX” Select “Data Preview” from the context menu.

18. Data preview should give you a different error message now, see the screenshot to the right. The reason for this message is the user has SQL access to the run time object, but is still missing an Analytic Privilege. You may test this for the other views as well.

Means there is a missing privilege


94

7.2 (Optional) Create and assign Analytic Privileges Create an Analytic Privilege for the Analytic View CEA1_XX, based on Analytic View CEA1_XX Please be very careful when working on this part. Analytic Privileges can presently only be activated once. If you need to change the Analytic Privilege after it has been successfully activated, you will have to delete it and re-create it from scratch. In the following we are going to grant Analytic Privileges to user TESTXX which will finally allow reporting off the Analytic View. We are restricting access to only Material Number ‘P-103’. In this first step, we will define the restriction directly the MATNR-field of view CEA1_XX.

1. Work as user STUDENTXX Navigate to the following path HDB (STUDENTXX) Content studentxx Analytic Privileges Right-click the folder name “Analytic Privileges” Select “New” “Analytic Privilege” from the context menu.

2. In the creation wizard, type the name: AP_CEA1_P103_XX (replacing XX appropriately) Enter a description : Analytic Privilege for view CEA1_XX - restricting to MATNR - P-103 Click “Next”


95

3. In the second step of the wizard, select your view studentXX/CEA1_XX Highlight that view in the Content tree on the left. Click “Add” this will add the view to the right-hand part of the display. Click “Finish”.

4. Implementing the privilege is now done in three steps:

1) Select further views for which this privilege should be valid (optional) We will not add further views in this step.

2) Select attributes on which a restriction shall be defined (All fields of all views selected in 1) will be offered)

3) Define value restrictions for the attributes selected in 2)

5. Add the field “MATNR” to the list of “Associated Attributes Restrictions”. Click the corresponding “Add” button Select field “MATNR” from the presented field list Click “OK”

1 2

3


96

6. Define the value restriction for field “MATNR” Highlight the MATNR field under “Associated Attributes Restrictions” Click the “Add” button for “Assign Restrictions” (this increases the counter for the number of restrictions for MATNR) Click into the “Value” field in “Assign Restrictions”. Click the “…”-icon. In the search window, search for Material P-103 Select the material from the search list Click OK (Note: if the search dialog does not yield any results, type in the value directly, without opening the search window).

7. Save the Analytic Privilege: Either click the “Save” icon or hit “Ctrl+S”. Then activate the Analytic Privilege


97

Assign Analytic Privilege AP_CEA1_P103_XX to user TESTXX 8. Work as user STUDENTXX

Open the User Editor for user TESTXX In that Editor, switch to tab “Analytic Privileges”

9. Click the green “+”-icon In the search dialog, start typing “studentXX/AP_CEA1_P103_XX” (replacing XX appropriately) From the list of “Matching items”, select privilege “studentXX/AP_CEA1_P103_XX” Click “OK”

10. Save the user profile: Either click the “Save” icon Or hit “Ctrl+S”


User being edited


98

Verify that the user can read from Analytic View CEA1_XX 11. Work as user TESTXX

Navigate to the following path HDB (TESTXX) Content studentxx Analytic Views Right-click the Analytic View “CEA1_XX” Select “Data Preview” from the context menu.

12. Data Preview should now return a list of 474 output values. Verify that the list contains only records with MATNR = P-103. You may verify that preview still does not work for Analytic View CEP1_XX nor for the Calculation View.


99

Appendix SQL Script Example (UNION)

/* Actual */ SQLA_VIEW = CE_OLAP_VIEW ( "studentXX/CEA1_XX", [ "MATNR", "KUNNR", "REGIO", "LAND1", "ORT01", "PERIO", "VKORG", "GrossRevenue", "SalesDeduction", "ProductionVariance", "OtherExpenses", "NETREVENUE", "CM1", "CM2" ] ); SQL_A = CE_PROJECTION ( @SQLA_VIEW@, [ "MATNR", "KUNNR", "REGIO", "LAND1" AS "LANDX", "ORT01", "PERIO", "VKORG", CE_CALC('0',VARCHAR(4)) AS KPLIKZ, "GrossRevenue" AS GROSSREV, "SalesDeduction" AS SALESDEC, "ProductionVariance" AS PRODVAR, "OtherExpenses" AS OTHEREXP, "NETREVENUE" AS NETREV, "CM1", "CM2" ] ); /* Planned */ SQLP_VIEW = CE_OLAP_VIEW ( "studentXX/CEP1_XX", [ "MATNR", "KUNNR", "REGIO", "LAND1", "ORT01", "PERBL", "VKORG", "GrossRevenue", "SalesDeduction", "ProductionVariance", "OtherExpenses", "NETREVENUE", "CM1", "CM2" ] ); SQL_P = CE_PROJECTION ( @SQLP_VIEW@, [ "MATNR", "KUNNR", "REGIO", "LAND1" AS "LANDX", "ORT01", "PERBL" AS "PERIO", "VKORG", CE_CALC('1',VARCHAR(4)) AS KPLIKZ, "GrossRevenue" AS GROSSREV, "SalesDeduction" AS SALESDEC, "ProductionVariance" AS PRODVAR, "OtherExpenses" AS OTHEREXP, "NETREVENUE" AS NETREV, "CM1", "CM2" ] ); /* Union */ var_out = CE_UNION_ALL(@SQL_A@, @SQL_P@);

SQL Script Example (JOIN)

TMP_TABLE_A = CE_OLAP_VIEW ("_SYS_BIC"."studentXX/CEA1_XX",

[ "KUNNR", "KUNNR.description", "LAND1", "LAND1.description", "REGIO",

"REGIO.description", "ORT01", "MATNR", "MATNR.description", "PERIO", "VKORG", "GrossRevenue", "SalesDeduction", "ProductionVariance", "OtherExpenses", "NETREVENUE", "CM1", "CM2"

] ); SQL_A = CE_PROJECTION ( @TMP_TABLE_A@, [ "KUNNR", "KUNNR.description" AS "KUNNRNAME", "LAND1", "LAND1.description" AS "LAND1NAME", "REGIO", "REGIO.description" AS "REGIONAME", "ORT01", "MATNR", "MATNR.description" AS "MATNRNAME", "PERIO","VKORG", "GrossRevenue" AS "GROSSREVENUE_A",

"SalesDeduction" AS "SALESDEDUCTION_A", "ProductionVariance" AS "PRODUCTIONVARIANCE_A",

"OtherExpenses" AS "OTHEREXPENSES_A", "NETREVENUE" AS "NETREVENUE_A", "CM1" AS "CM1_A","CM2" AS "CM2_A"

] );


100

TMP_TABLE_B = CE_OLAP_VIEW ("_SYS_BIC"."studentXX/CEP1_XX",

[ "KUNNR", "KUNNR.description", "LAND1", "LAND1.description", "REGIO", "REGIO.description", "ORT01", "MATNR", "MATNR.description", "PERBL", "VKORG",

"GrossRevenue", "SalesDeduction", "ProductionVariance", "OtherExpenses", "NETREVENUE", "CM1", "CM2"

] ); SQL_P = CE_PROJECTION ( @TMP_TABLE_B@, [ "KUNNR", "KUNNR.description" AS "KUNNRNAME_P", "LAND1" AS "LAND1_P", "LAND1.description" AS "LAND1NAME_P", "REGIO" AS "REGIO_P", "REGIO.description" AS "REGIONAME_P", "ORT01" AS "ORT01_P", "MATNR", "MATNR.description" AS "MATNRNAME_P", "PERBL" AS "PERIO", "VKORG", "GrossRevenue" AS "GROSSREVENUE_P", "SalesDeduction" AS "SALESDEDUCTION_P", "ProductionVariance" AS "PRODUCTIONVARIANCE_P", "OtherExpenses" AS "OTHEREXPENSES_P", "NETREVENUE" AS "NETREVENUE_P", "CM1" AS "CM1_P", "CM2" AS "CM2_P"

] ); var_out = CE_JOIN ( @SQL_A@, @SQL_P@, [ "KUNNR", "MATNR", "PERIO", "VKORG" ], [ "KUNNR", "KUNNRNAME", "LAND1", "LAND1NAME", "REGIO", "REGIONAME", "ORT01", "MATNR","MATNRNAME", "PERIO", "VKORG", "GROSSREVENUE_A", "SALESDEDUCTION_A", "PRODUCTIONVARIANCE_A",

"OTHEREXPENSES_A", "NETREVENUE_A", "CM1_A","CM2_A", "GROSSREVENUE_P", "SALESDEDUCTION_P", "PRODUCTIONVARIANCE_P",

"OTHEREXPENSES_P", "NETREVENUE_P", "CM1_P", "CM2_P" ] );


101

© 2010 by SAP AG. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 S.A. in the United States and in other countries. Business Objects 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. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group 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.

tzhana for application consultants

Documents

sap products

sap netweaver

express permission of

sap hana appliance

deutschland und

business bydesign

partneredge und andere

software products