Tzhana en Col96 Show[1]

SAP In-Memory Appliance(HANA) 1.0

TZHANA for Application Consultants

© SAP AG 2010

Copyright 2010 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 changedwithout 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 theirrespective 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 andassociated 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 documentcontains 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, orother 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 ofmerchantability, 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 limitationshall 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 thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe 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 durchSAP 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 Servicessowie 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ähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. 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 anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrü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 Zwecksowie 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 Verwendungdieser 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 Hotlinkszugreifen, 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 überInternetseiten Dritter ab.Alle Rechte vorbehalten.

© SAP 2011 /Page 3

DISCLAIMER

This presentation outlines our general product direction and should not be relied onin making a purchase decision. This presentation is not subject to your licenseagreement or any other agreement with SAP.

SAP has no obligation to pursue any course of business outlined in thispresentation or to develop or release any functionality mentioned in this presentation.This presentation and SAP's strategy and possible future developments aresubject to change and may be changed by SAP at any time for any reason withoutnotice.

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 aparticular purpose, or non-infringement. SAP assumes no responsibility for errors oromissions in this document, except if such damages were caused by SAPintentionally or grossly negligent.

© SAP AG 2009

Agenda

SAP In-Memory Appliance (HANA) 1.0Lesson 1: Introductions

Lesson 3: Architecture

Lesson 2: Look & Feel

Lesson 4: Data Provisioning

Lesson 5: Replication

Lesson 7: Reporting

Lesson 8: User Management

Lesson 6: Modelling

© SAP AG 2009

Agenda

SAP High-Performance Analytic Appliance 1.0 (HANA 1.0)Lesson 1: Introduction to HANA





Lesson 7: Reporting


Lesson 6: Modelling

© SAP 2011 / Page 2

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

new business reality / new challenges

© SAP 2011 / Page 3

© SAP 2011 / Page 4

DAILY CHALLENGES

Complex system landscapes

Massive growth of data volume

Immediate results

High flexibility

© SAP 2011 / Page 5

CONSEQUENCES

Sub-optimal execution speed

Lack of transparency

Reactive business model

Lack of responsivenessUser frustrationUnsupportable business processes

Need for aggregationOutdated figuresGuessing current situation

Missing opportunitiesCompetitive disadvantage

M

1TB/Server

© SAP 2011 / Page 6

HARDWARE INNOVATIONS

CPU

8 Cores / CPU

C P U B

4 CPUs / Board

S

4 Boards

128 CORES!4 TB RAM and more!

Only SingleServer in HANA

1.0!!!

new business reality / new challenges

The new realityNew possibilitiesSAP’s offeringHANA in ContrastHANA Details

© SAP 2011 / Page 7

Rethink old paradigmsInnovation enables new ways of thinking

© SAP 2011 / Page 8

AVOID BOTTLENECKS - LATENCY

Prevent CPU IDLE TIME

Introduce COLUMNAR DATA STORAGE

SPEED

YEAR

Memory latency!

© SAP 2011 / Page 9

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

EasilyCOMPRESSABLE

© SAP 2011 / Page 10

AVOID BOTTLENECKS – DATA TRANSFER

MOVE calculations into database

Only transfer RESULTS

APPLICATION

LAYER

Calculation

DATABASE

LAYER Calculation

Classical Approach

Future Approach

© SAP 2011 / Page 11

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

…

Not yetimplemented

iin HANA1.0!!!

© SAP 2011 / Page 12

DISCOVER NEW POSSIBILITIES

NEW APPLICATIONS

Old processes can beIMPROVED

Feasibility boundariesare SHIFTING

No need forAGGREGATION anymore

© SAP 2011 / Page 13

COMBINE BUSINESS & TECHNOLOGY

SAP Business Applications

Integrated Systems

Business Knowledge

SAP In-Memory Applications

Live Cache

BW Accelerator

HANA

Strong HARDWARE Partners

TODAY‘S SITUATION – CLASSICAL EDW

Enterprise Data Warehouse (BW)

Corporate BI

Database

Local BI

DataMart

DB

BWA

DataMart

DB

NON SAP

Database

Local BI

SAP ERP 1

Database

SAP ERP 2

Database

DataMart

DB

Local BI

SHORT TERM – HANA 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

MID TERM – HANA 1.0 SP XX


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

VISION – IN MEMORY AS DATA LAYER

Enterprise DataWarehouse (BW)

Corporate BI

SAPERP 1

SAPERP 2

New

APP 1

New

APP 2

HANA

NONSAP

In-Memory AnalyticsHANA 1.0 Real-time operational

analytics with HANA 1.0Complete BI Suite with BI 4.0

(Aurora) runs on HanaSAP Business by Design 2.6 runs

on in-memory

SAP In-Memory StrategyProduct Strategy

One Store for Data andAnalytics

HANA only persistence layer for SAPBusiness Suite

SAP Business Suite optimized forIn-Memory

Flexible real time analysis ofoperations at non-aggregated

level

Real-Time operationalplanning, simulation and

forecasting: link to execution

Reduced landscapecomplexity

Value chain transformation

Capabilities

Benefits

Next generationapplications

SAP BW fully running on HANA1.5

HANA 1.5 platform for In-Memory Apps

Business Suite runs on HANA2.0

SBOP 4.x (Aurora) unifiedmodeling with Hana

Industry and LOB BusinessAnalytics Solutions “BAS”

Q4 2010“Renovation”

HANA 1.0

2011-12“Innovation“

HANA 1.0 SP XX

2012+“Transformation”

How does HANA compare to BWA?... Probably the wrong question, but let‘s try...

TechnicallyHANA 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

And there are other thingsRow store (P*time); persistence, transactions (MaxDB), SQL Parser (P*time), ...

Data Models / ContentLife is much easier for BWA

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

HANA 1.0 is intended as a Data Mart (and BWA clearly is not)

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

HANA 1.0 is:The In-Memory Computing Engine

Including SQL and MDX interface, calculation engine, relational stores, persistence, ...Sybase replication server

Complex limitations apply (DBMS vendor and version, OS)In-Memory Computing Studio

Administration and Modelling

HANA 1.0 does not have…ContentAnything comparable to the ABAP DictionaryAnything really comparable to ‘ABAP’ (‘Application Server’)Front-End Tools (unless you count Excel)

There are several working front-ends (not included with HANA)Many of them present or soon in ramp-up

One consistent administration and monitoring tool for all component.

Creating Models in 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 HANAInitial loadImplement some delta mechanism

Easy if replication server worksOtherwise: well...

Recreate table relationships in HANAAll master data modelling (incl. Texts)Join conditions between tablesMore complex logic?

Use SQLScript

Creating Models in 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 aboveHANA layer?Select suitable reporting tool

Excel, SAP BusinessObjects Explorer, Web Intelligence, Dashboard Design, CrystalReports, Analysis (Office/Web).

Create the report

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

© SAP AG 2009

Agenda






Lesson 7: Reporting


Lesson 6: Modelling

Lesson Objectives

© SAP AG 2010

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

Look&FeelIn-memory Computing Studio

© SAP AG 2009

Look&FeelAdministration View

© SAP AG 2009

NavigatorView

CheatSheets

Look&FeelNavigator View - Default Catalog

© SAP AG 2009

HANA Instance (<USER>)

HANA Server Nameand Instance Number

User Database schema

Schema Content:Column Views,Functions, Tables,Views

Look&FeelSystem Monitor

© SAP AG 2009

AdministrationView

Look & FeelPre-Delivered Administration Console

© SAP AG 2009

NavigatorView

PropertiesView

AdministrationView

Look & FeelPerspectives are built up based on views

© SAP AG 2009

FastPerspective

SwitchChooseperspectivefrom main

menu

Look and FeelInformation Modeler

© SAP AG 2009

NavigatorView

Quick LaunchView

PropertiesView

Look&FeelNavigator View - Information Models

© SAP AG 2009

Information Models organizedin Packages

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

Look & FeelPerspectives are built up based on views

© SAP AG 2009

VIEWS!

Look & FeelTips & Tricks

© SAP AG 2009

RESETPERSPECTIVE

will restore yourscreen!

© SAP AG 2010

Summary

You should now:Understand concepts such as HANA and SAP In-memory computingUnderstand the structure of SAP in-memory computing studioUnderstand how to configure perspectivesUnderstand how to create a package

© SAP AG 2009

Agenda






Lesson 7: Reporting


Lesson 6: Modelling

Lesson Objectives

© SAP AG 2011

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

Backup & Recovery

© SAP AG 2011

Agenda

Lesson 3:

Architecture

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

TransactionManager

Session Management

Relational EnginesRow Store Column Store

Persistence LayerPage Management Logger

Disk StorageLog VolumesData Volumes

AuthorizationManager

MetadataManager

IMCE Studio

Administration Modeling

LoadController

ReplicationAgent

ReplicationServer

SAP Business Objects BI4

DataServicesDesigner

SBO BI4servers

( programfor client)

SBO BI4InformationDesign Tool

Other Source Systems

SAPNetWeaver

BW3rd Party

DataServices

ERP

Architecture OverviewThe engine itself

LogERP DB

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

Xcelsius SAP BI universes (WebI,...)

MS Excel

SBOP Analysis

IMCE Studio


LoadController

ReplicationAgent

Business Objects Enterprise


SBO serverprogramsfor clients

SBOInformationDesign Tool


SAPNetWeaver

BW3rd Party

DataServices


Request Processing / Execution ControlSQL Parser MDXSQL Script Calc Engine

TransactionManager

Session Management





MetadataManager

ReplicationServer

LoadController

ERP

Architecture OverviewLoading Data into HANA

LogERP DB



TransactionManager

Session Management





MetadataManager

IMCE Studio

ReplicationAgent



SBO BI4servers




SAPNetWeaver

BW3rd Party

DataServices


DashboardDesign


MS Excel

BI4 AnalysisAdministration Modeling

LoadController

ReplicationServer

ERP

Architecture OverviewData Modeling

LogERP DB



TransactionManager

Session Management





MetadataManager

IMCE Studio


ReplicationAgent



SBO BI4servers




SAPNetWeaver

BW3rd Party

DataServices


DashboardDesign


MS Excel

BI4 Analysis

LoadController

ReplicationServer

Clients (planned, e.g.)

ERP

Architecture OverviewReporting

LogERP DB



TransactionManager

Session Management





MetadataManager

IMCE Studio


ReplicationAgent



SBO BI4servers




SAPNetWeaver

BW3rd Party

DataServices

BI4 Explorer

DashboardDesign


MS Excel

BI4 Analysis

LoadController

ReplicationServer

ERP

Architecture OverviewAdministration

LogERP DB



TransactionManager

Session Management





MetadataManager

IMCE Studio


ReplicationAgent



SBO BI4servers




SAPNetWeaver

BW3rd Party

DataServices


DashboardDesign


MS Excel

BI4 Analysis

LoadController

ReplicationServer

© SAP AG 2011

Agenda

Lesson 3:Lesson 3:

Architecture

Persistence Layer

Backup & Recovery

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

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

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

© SAP AG 2011

DATA&

Undo

DATA&

Undo

Redo Log

Page Buffer

Log queueData Cache Other

Data PagesData pagesof virtual files

Savepoint Coordinator

DATA&

UndoDATA

&Undo

4712

4713

Converter

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

© SAP AG 2011

Agenda

Lesson 3:Lesson 3:

Architecture

Persistence Layer

Backup & Recovery

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

DDData Backup

Persistent Storage

LogVolume

DataVolumes

conf

Configuration Backup

Save to External Backup Destinations

© SAP AG 2011

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

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 2009

Agenda






Lesson 7: Reporting


Lesson 6: Modelling

© SAP AG 2009

Agenda

Lesson 4:

Replication Server

Data Services

SAP In-Memory: ReplicationProcess

Tool: SAP in-memory computing studio (information modeler)

1. Meta-data transferImport the meta-data of all ERP tables into the SAP in-memory computing engine-> Tables (without content) are created in the engine

2. Data provisioningSelect the tables for which content is to be replicatedStart the data provisioning:Options:

Load: Initial load only (e.g. for development and testing)Replicate: Initial load and subsequent delta replication of changes in the ERP tables

You can later include additional packages of tables in the data provisioning

3. MonitoringThe current replication status is captured in special monitoring tables(RS_STATUS, RS_REPLICATION_COMPONENTS, both in SYSTEM schema)You can display the status in the SAP in-memory computing studio

SAP In-Memory: ReplicationArchitecture

SAP HANA systemERP system

ERP databaseSAP in-memory

computing engine

ERP application

ReplicationAgent

Log

Mining

ReplicationServer ECDA

SQLMeta-data

SAP in-memorycomputing studio

Load Controller

R3Load

Start

Statustable

Sync

hron

ize

Monitor

Export Import

R3Load

Start

Socket / Pipe

© SAP AG 2009

Agenda

Lesson 4:

Replication Server

Data Services

Lesson Objectives

© SAP AG 2010

After completing this lesson, you will be able to:Import metadata and structure from SAP ERP and BW into the In-MemoryComputing EngineCreate a simple 1:1 Data Services job and dataflow to replicate data from yourSAP ERP system

SAP BusinessObjects Data Services 4.0 andHANA

In-Memory ComputingEngine (ICE)

SAPERP

Any Source

BW

Modeler

Data Load

Metadata

Repository Server

Open Hub

SAP BusinessObjectsData Services 4.0

HANA

Designer andManagement

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 metadataModeler will generate initial flows to load data into NewDB tablesFurther modifications to flows done via Data Services Designer

Not yet working

Process Flow: HANA and Data Services

© SAP AG 2009

Createa

connection toa SAPtarget

system

Import themetadata

via ICEstudio

intoHANA

Import themetadataback into

DataServices

Create aData

Servicesjob to

populateHANA

Execute aData

Servicesjob to

populateHANA

Previewuploaded

data

Process Flow: HANA

© SAP AG 2009

Create a connection toa SAP target system

Import the metadata via ICEstudio into HANA

Data Services 4.0 System Support MatrixSAP ERP (core HANA 1.0 Use Case)

Source Extraction Methodfrom Source

Target Supported?

ERP < 6.0

Generated ABAP

Any target supported byData Services 4.0

YES

RFC_READ_TABLE YES

RFC/BAPI call YES

iDocs YES

BW Extractors No plans

ERP6.01 – 6.05

Generated ABAP

Any target supported byData Services 4.0

YES

RFC_READ_TABLE YES

RFC/BAPI call YES

iDocs YES

BW Extractors (ODP) YES

BW Extractors (ODP) HANA YES

Any other sourcesystem supported byData Services 4.0

(specific to source system) Any target systemsupported by DataServices 4.0

YES

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 & executedData 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 Servicesagain (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 2009

Full extractor support through ODP

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

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, nostaging in files.

RequirementsSupport 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

Patch requirements for ODP for Data Services

The ODP data replication API needs to be available on the NetWeaver platform usedby the ECC system.

Thus a combined NetWeaver SP and ERP EhP is required as followsCentral note to follow: https://service.sap.com/sap/support/notes/1522554For ERP 6.0, 6.0 EhP 1, 6.0 EhP 2, 6.0 EhP 3

– NetWeaver 7.0 SP23 (Dec 2010) and following ERP versions certified with this SP:– ERP 6.0 SP19 (Feb 2011)– ERP 6.0 EhP 1 SP12 (Feb 2011)– ERP 6.0 EhP 2 SP9 (Feb 2011)– ERP 6.0 EhP 3 SP8 (March 2011)

For ERP 6.0 EhP4, CRM 7.0, … (Suite 7)– NetWeaver 7.0 EhP1 SP8 (Jan 2011 – CW2) and following ERP version certified

with this SP ERP 6.0 EhP 4 SP9 (March 2011)For ERP 6.0 EhP 5, CRM 7.0 EhP1, … (Suite 7 Innovations 2010)

– NetWeaver 7.0 EhP2 SP7 (April 2011) and following ERP versions certified withthis SP ERP 6.0 EhP 5 SP4 (May 2011)

See https://websmp103.sap-ag.de/sp-stacks for up-to-date release dates.

https://service.sap.com/sap/support/notes/1522554

https://websmp103.sap-ag.de/sp-stacksfor

Released extractors

A first set of 200+ extractors is now officially released for Data Services by theBusiness Suite.

Current list: https://service.sap.com/sap/support/notes/1558737This is done via an SAP note which can be easily deployed by the customer (pre-requisite isthat the SP with ODP is installed).Technically, the only thing that happens is that the released extractor names are added tothe ROOSATTR table

Additional extractor scan be used at the customer’s own risk.We will work with our ramp-up customers to release these additional extractors by addingthem manually into the ROOSATTR table.These additional lists of extractors will be provided to the business suite team and will getreleased in upcoming SAP Notes (after validation by the Business Suite/IMS).

https://service.sap.com/sap/support/notes/1558737

Create a connection to a SAP ERP target

© SAP AG 2009

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

Create a connectionto a SAP target

system

Import the metadata viaICE studio into HANA

Setup Information Modeler to communicatewith Data Services (Configure Import Server)

© SAP AG 2009

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


system


SAP In-Memory Computing StudioImporting meta data from an ERP System

© SAP AG 2009

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

1.2.


system


Choose one of the maintained connections

© SAP AG 2009

Connections of DataStoretype “SAP Applications”are imported from thespecified DataServices

repository


system


Select Objects for importSearch vs. hierarchy drill-down

© SAP AG 2009

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


system


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

© SAP AG 2009

“RKT” catalog in In-Memory Computing

Engine empty


system


Validate the target structure

© SAP AG 2009

1.

2.Validate the target structure


system


View the newly created target structure viathe In-Memory Computing Engine

© SAP AG 2009

Table creation status inthe deployment log

1.

2.

3.

Refresh the Tables sectionin the “RKT” catalog anddouble click the table to

see the structure


system


2.

Process Flow: Data Services

© SAP AG 2009

Import themetadataback into

DataServices

Create aData

Services jobto populate

HANA

Execute aData

Services jobto populate

HANA

Previewuploaded

data

Import the created table structure into DataServices

© SAP AG 2009

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

Import themetadata

back into DataServices

Create a DataServices jobto populate

HANA

Execute aData Services

job topopulate

HANA

Previewuploaded data

Create and execute a Data Services job topopulate HANA

© SAP AG 2009

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

Create a new batch job within Data Services (this is the high-level executable tobe 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, aquery object realizing a basic 1:1 mapping, and the target table which alreadyexists within the HANA system)Execute the newly created Data Services job and preview the records with the inSAP In-Memory Computing Studio

Create and new Data Services Job and data flowwith simple 1:1 mapping

© SAP AG 2009

Create a simple job and dataflow with a 1:1 mappingfrom the SAP EPR source table to the HANA target

Simple 1:1 query object

ABAP dataflow recommended for large data sets

Import themetadata



HANA


job topopulate

HANA


Execute the job to populate the HANA targettable and monitor the load

© SAP AG 2009

Monitor load progress

Import themetadata



HANA


job topopulate

HANA


View the uploaded data within the In-MemoryComputing Studio

© SAP AG 2009

Import themetadata



HANA


job topopulate

HANA


© SAP AG 2010

Summary

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

© 2010 SAP AG. CONFIDENTIAL - FOR INTERNAL USE ONLY – SUBJECT TO TERMS/CONDITIONS/ASSUMPTIONS CONTAINED IN DOCUMENT / Page 1 ------ DRAFT ---------© SAP

Agenda






Lesson 7: Reporting


Lesson 6: Modelling

© 2010 SAP AG. CONFIDENTIAL - FOR INTERNAL USE ONLY – SUBJECT TO TERMS/CONDITIONS/ASSUMPTIONS CONTAINED IN DOCUMENT / Page 2 ------ DRAFT ---------

SAP In-Memory: ReplicationProcess

Tool: SAP in-memory computing studio (information modeler)

1. Meta-data transferImport the meta-data of all ERP tables into the SAP in-memory computing engine-> Tables (without content) are created in the engine

2. Data provisioningSelect the tables for which content is to be replicatedStart the data provisioning:Options:

Load: Initial load only (e.g. for development and testing)Replicate: Initial load and subsequent delta replication of changes in the ERP tables

You can later include additional packages of tables in the data provisioning

3. MonitoringThe current replication status is captured in special monitoring tables(RS_STATUS, RS_REPLICATION_COMPONENTS, both in SYSTEM schema)You can display the status in the SAP in-memory computing studio


SAP In-Memory: ReplicationArchitecture

SAP HANA systemERP system

ERP databaseSAP in-memory

computing engine

ERP application

ReplicationAgent

Log

Mining

ReplicationServer ECDA

SQLMeta-data

SAP in-memorycomputing studio

Load Controller

R3Load

Start

Statustable

Syn

chro

nize

Monitor

Export Import

R3Load

Start

Socket / Pipe


Appendix – Data Provisioning


R3 Load Controller

Modes of Operation…Mass Import of MetadataSelective Initial LoadSelective Table Replication


Modeler – Quick Launch


Mass Import of Metadata….1






R3 Load Controller



Data Provisioning – Quick Launch


Data Provisioning UI


Selective Initial Load…1






Data Provisioning UI…Load Status


R3 Load Controller



Selective Table Replication…1








Data Provisioning UI…Replication Status


Appendix – Operate & Maintain


SAP HANA Operate and MaintainNewDB Studio Update

© SAP AG 2009

Agenda






Lesson 7: Reporting


Lesson 6: Modeling

Lesson Objectives

© SAP AG 2010

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

- Analytic Views

© SAP AG 2009

Agenda

Lesson 6:

Introduction to Information ModelerLevels of Modeling

- Export & Import

- Attribute Views

- Calculation Views

Introduction to CO-PA Scenario

CO-PA Background

© SAP AG 2010

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

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

Revenue

Costs

Sales quantitySales rev.

Direct material costsVariable production costs

Contribution margin IMaterial overheadFixed production costs

Contribution margin IIVariances

Contribution margin IIOverhead costsOperating profit

Determine and analyze theprofitability of market

segments

Sales OfficeBusiness Unit

Reporting Dimensions

Region Customer

COPA Storage Architecture

© SAP AG 2009

Join ProfitabilitySegment Number

Characteristics

CE4xxxx-Segment Table

Fiscal yearPlan/act. Indic.Plan VersionRecord Type

ValueFields

CE3xxxx-Summarrization Level

CE2xxxx

ActualLine Items

CE1xxxx

PlanLine Items

e.g. xxxx = IDEA

HANA and CO-PA as an example

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

CE1XXXXCE1XXXXCE2XXXXCE2XXXX

CE3XXXXCE3XXXX

CE4XXXXCE4XXXXERPERP

MDX

SQL


Other ApplicationsReal Time Replication Service

BICSSAP BusinessObjects

HANAHANA

In Memory Database

Calc & PlanningEngine

Data ManagementData Services

HANA Modeling Studio

ApplicationApplication TableTable

HANA and CO-PA as an example

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

CE1XXXXCE1XXXXCE2XXXXCE2XXXX

CE3XXXXCE3XXXX

CE4XXXXCE4XXXXERPERP

ApplicationApplication TableTable

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

HANA - Table Relations in ERP

ERPERP

MoreMore thanthan 50.00050.000 applicationapplication tablestables

Can be analyzed with transaction code SD11Can be analyzed with transaction code SD11


ERPERP

SD11SD11


ERPERP

SD11SD11

CO-PA table structures

© SAP 2010 /

characteristics value fieldsposting date

value fieldsPAOBJNR period

PAOBJNR period

CE1xxxx: CO-PA line items ( actual data ) e.g. CE1IDEA

CE3xxxx: CO-PA object level ( summarization data )

characteristicsPAOBJNR

CE4xxxx: CO-PA object table ( definition of market segments )

characteristics value fieldsposting datePAOBJNR period

CE2xxxx: CO-PA line items (plan data )

Scenario 1 – Actual Data

© SAP 2010 /

characteristics value fieldsperiod


• Data retrieved on Line Item level• First Scenario for Actual Data• Selection on Period and Characteristics• Aggregation of Value Fields

Report1:

Actual ContributionMargin

Selection: RegionCountryCity

a b c d = b-c e f = d-e g h = f-g

Volume

GrossRevenu

eSalesCosts

NetRevenue

ProductionVariances CM 1

Expenses CM 2

Region 1 Country A City 1 x x x x x x x xCity 2 x x x x x x x x

Total Country x x x x x x x xCountry D City 3 x x x x x x x x

City 4 x x x x x x x xTotal Country x x x x x x x x

TotalRegion x x x x x x x xRegion 2 Country E City 5 x x x x x x x x

City 6 x x x x x x x xTotal Country x x x x x x x xCountry G City 7 x x x x x x x x

City 8 x x x x x x x xTotal Country x x x x x x x x

TotalRegion x x x x x x x xTotal x x x x x x x x

Scenario 2 – Plan Data

© SAP 2010 /


CE2xxxx: CO-PA line items (plan data ) e.g. CE1IDEA

• Data retrieved on Line Item level• Second Scenario for Plan Data• Selection on Period and Characteristics• Aggregation of Value Fields

Scenario 3 – Actual vs. Plan Data

© SAP 2010 /




• Data retrieved on Line Item level• Union of both tables• Selection on Period and Characteristics• Aggregation of Value Fields

Union

CE2xxxx: CO-PA line items (plan data )

Report 3: Plan /Actual Comparison

Selection: Sales orgYear

Plan Actual Variancea Volume x x xb Gross Revenue x x xc Sales Costs x x xd = b-c Net Revenue x x xe Production Variances x x xf = d-e CM 1 x x xg Expenses x x xh=f-g CM 2 x x x

© SAP AG 2010

Summary

In this lesson, you learned:Overview of CO-PA

- Analytic Views

© SAP AG 2009

Agenda

Lesson 6:


- Export & Import

- Attribute Views

- Calculation Views


Features

SAP in-memory computing studio: Information Modeler FeaturesModeling

No materialized aggregatesDatabase ViewsChoice to publish and consume at 4 levels of modeling

Attribute View, Analytic View, Analytic View enhanced with Attribute View, CalculationView

Data PreviewPhysical tablesInformation Models

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

Data Provisioning for SAP Business Applications (both initial load andreplication)Analytic Privileges / Security

Modeling Process Flow

ImportSourceSystemmetadata• Physical tablesare createddynamically (1:1schema definitionof source systemtables)

ProvisionData• Physical tablesare loaded withcontent.

CreateInformationModels• Database Viewsare created• Attribute Views• Analytic Views• CalculationViews

Deploy• Column views arecreated andactivated

Consume• Consume withchoice of clienttools

• BICS, SQL, MDX

Terminology

SAP in-memory computing studio: Information ModelerData

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

ViewsAnalytic Views – i.e. cubesAttribute Views – i.e. dimensionsCalculation Views – similar to virtual provider with services concept in BW

HierarchiesLeveled – based on multiple attributesParent-child hierarchy

Analytic Privilege – security objectAnalytic Privileges are covered in Lecture 7 – “User Management”

Set Information Modeler Preferences

Select Windows PreferencesInformation ModelerDefault Model Parameters

Allows setting of defaultvalues for informationmodels created by user

Set ‘Default Client’ tothe client used incustomer systemLeave ‘Default Language’on preset value(‘dynamic’)

- Analytic Views

© SAP AG 2009

Agenda

Lesson 6:


- Export & Import

- Attribute Views

- Calculation Views


Modeling for HANA 1.0Using In-Memory Computing Studio (I)

Idea 1: separate Master Data Modeling from ‘Fact data’Build 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’)

Idea 2: create ‚Cube-like‘ view by joining attributes view to ‚Fact data‘Build a ‘Data Foundation’ based on transactional table

Selection of ‘Measures’ (key figures) ...... and attributes (docking points for joining attribute views)

this is basically your ‘fact table’ (key figures and dimension IDs)Join attribute views to data foundation

Looks a bit like a star schema

Modeling for HANA 1.0Using In-Memory Computing Studio (II)

Idea 3: If simple joins are not sufficient use SQL ScriptIs a HANA-specific functional script language

Think of a ‘SELECT FROM HANA’ as a data flowYou can move functions into that data flow in order to

Enrich data (e.g. Add columns for calculated measures on the fly)JOIN or UNION two or more data flowsInclude complex logic such as ‘CASE’ statements

This can be compared to ‘piping’ on the Unix command line

Idea 4: Create something that looks like a ‚View‘ and has SQL Script insideThis is a ‘Calculation View’ – Consisting of ...

... A table type definition the ‘transfer structure’ or ‘view’ you can ‘SELECT FROM’

... And a SQL script function (which may invoke other SQL script functions)This is like a ‘fact table’ (key figures and dimension IDs)

Hopefully one can join attributes to this ‘fact table’ in the future.

Modeling for HANA 1.0Using In-Memory Computing Studio (III)

Idea 5: create ‘analytic privilege’ based on viewsAnalysis authorizations for row-level security

Can be based on attributes in analytic viewsShould also work now if defined on attribute views (re-usability)

Analytic privilege is always a concrete implementationI.e. Specific authorization for specified values of given attributeYou have to create privileges for each group of users

- Analytic Views

© SAP AG 2009

Agenda

Lesson 6:


- Export & Import

- Attribute Views

- Calculation Views


Attribute Views

© SAP AG 2009

Attribute ViewWhat is an Attribute View?

Attributes add context to data.Attributes are modeled using Attribute Views.Can be regarded as Master Data tablesCan be linked to fact tables in Analytical ViewsA measure e.g. weight can be defined as an attribute.

Attribute View

© SAP AG 2009

SetParameters

TableSelection

Table joinsand

properties

SelectAttributes

CreateHierarchies

Save andActivate

DataPreview

Attribute View:View Creation Wizard

© SAP AG 2010

1.

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

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

Enter a name (technical name)and descriptionSelect view type

StandardTime view

Either create a new viewOr select an existing attributeview as template

Attribute View:Select table(s)

© SAP AG 2010

2.

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

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

One can either expand a schema and tryto find the required table(s) viablemethod for schemas containing a smallnumber of tablesOr one can enter a search term and hitthe search button

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

Attribute View:Add additional table

© SAP AG 2010

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

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

One can only add one table at a timeusing this wizard.

Attribute View:Add table via drag & drop

© SAP AG 2010

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

Add additional tables to viewVia Drag&Drop from Navigator Tree

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

1. Filter ontable name

2. Drag tableinto view

Attribute View:Define join properties

© SAP AG 2010

Table Joins and PropertiesJoin Types

InnerleftOuterrightOuterfullOutertextTable

Cardinality1:1N:11:N

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

3.

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

Attribute View:Output field selection and filters

© SAP AG 2010

4

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

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

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

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

Attribute View:Set description mapping

© SAP AG 2010

5

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

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

Select the attribute in the outputstructureDescription mapping is configured inthe ‘Properties’ view for theattribute.The drop-down menu for thedescription mapping will show allfields of all tables which are joinedin the attribute view.

Attribute Properties

MDX per default onlyshows 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 twoattributes, but only “Product_number” appearsin Excel

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

Attribute Properties

Enabling display of non-key fields via MDXSet output-field property “Hierarchy active” to “true”

all fields show up in field list for Excel PivotTable

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

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

Attribute View:Define a level hierarchy

© SAP AG 2010

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

Attribute View:Define a parent-child hierarchy

© SAP AG 2010

7.

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

Hierarchies are only accessible via MDXDefine a parent-child hierarchy

Variable number of levels for sub-trees within thehierarchy

Attribute View:Save and activate the view

© SAP AG 2010

8.

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

Create executable version of the viewSave the view

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

Activate the viewRight-click view and choose ‘Activate’ from contextmenuThis 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 reportingtools

Attribute View:Preview the view

© SAP AG 2010

Data Preview on theInformation Model:

Data Preview onColumn View:

9.

SetParamet

ers

TableSelectio

n

Tablejoinsand

properties

SelectAttribute

s andMeasure

s

CreateHierarchies

Saveand

Activate

DataPreview

© SAP AG 2009

Agenda

Lesson 6:


- Export & Import

- Attribute Views

- Calculation Views- Analytic Views


Analytical View

© SAP AG 2009

Analytic ViewAn 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 2009

SetParameters

TableSelection

Table joinsand

properties

SelectAttributes

andMeasures

CalculatedMeasures

RestrictedMeasures

Save andActivate

DataPreview

Analytic ViewView creation wizard

© SAP AG 2009

Analytic ViewSet Parameters

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

SetParamete

rs

TableSelection

Tablejoins andpropertie

s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

1.

Analytic ViewSelect Table(s)

© SAP AG 2009

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.

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

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’-tabof the view editor

Analytic ViewSelect Attribute view(s)

© SAP AG 2009

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

3.

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 2009

Tab ‚Data Foundation‘ Tab ‚Logical View‘Table

DataFoundation

AttributeViews

Analytic ViewDefine the Data Foundation

© SAP AG 2009

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

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

5.

Analytic ViewJoin Attribute Views to Data Foundation

© SAP AG 2009

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

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’

Analytic ViewDefining Calculated Measures

© SAP AG 2009

Analytic ViewCalculated Measures

Data Types (decimals, numbers etc)Field LengthScaleAggregation defined in properties (sum, min, max and count)

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

6.

Analytic ViewDefining Restricted Measures

© SAP AG 2009

Analytical ViewRestricted Measures

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

7.

Create executable version of the viewSave the view

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

Activate the viewRight-click view and choose ‘Activate’ from contextmenuThis 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

© SAP AG 2009

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

8.

8.

Use the built-in Eclipse-Preview of IMCE 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

© SAP AG 2009

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

9.

Analytic View

© SAP AG 2009

Analytic ViewData Preview: Raw Data

Can create filtersOnly for limited number of records

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

Analytic View

© SAP AG 2009

Analytical ViewData Preview: Analysis

Table, Selection of Chart Types and templates .

SetParamete

rs

TableSelection


s

SelectAttributes

andMeasures

Calculated

Measures

Restricted

Measures

Save andActivate

DataPreview

- Analytic Views


© SAP AG 2009

Agenda

Lesson 6:


- Export & Import

- Attribute Views

- Calculation Views

Calculation View

© SAP AG 2009

Calculation ViewWhat is an Calculation View?What are the uses of an Calculation View?

Calculation ViewWhat is a calculation view

© SAP AG 2009

Create a HANA data provider with complex logic insideCalculation 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

Calculation View (scripting)

© SAP AG 2009

SetParameters

DefineTable

OutputStructure

DefineFunction(Input and

OutputStructure)

Write SQLStatement

Execute

AssignAttributes

andMeasures

Save andActivate

DataPreview

Calculation View (scripting)View creation wizard

© SAP AG 2009

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

Parameter wizard for calculationview

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

Function name must be identical toview name (pre-filled per default)!Select schema for column view

For calculation view, theaccessible database object(column view) can be placed into auser-defined schema

Calculation View (scripting)High-level structure of calculation view

© SAP AG 2009

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

Elements of the SQL script for a calculation viewThe definition of the view’s output structure

CREATE TABLE TYPE <out_variable_type>

I.e. The list of fields in the resulting column viewThis is optional (one can also re-use an existing table type)

The definition of the function that provides data for the viewCREATE FUNCTION "D051516"."RB_TEST_CALC_VIEW" (OUT <out_variable><out_variable_type>)

This function contains all logic of the calculation viewA ‘DROP TABLE TYPE’

Optional: only if table typeexplicitly definedImplicitly drops all functionsusing this typeIf included, this is the firststatement of the view

Calculation View (scripting)Calc View output structure

© SAP AG 2009

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

Defining the view output structureIf a table type is defined include ‘DROP TABLE TYPE’

Otherwise changes to the table type cannot be activatedAdd all fields required for the calculation view

All fields that shall be visible to reportingtoolsIf based on analytic view: all required fieldsof that column view must be added (alsodescription mapping fields if applicable)For fields that are based on fields in existingtables/views, the data types must matchexactly.


© SAP AG 2009

TIP: Define Table Output StructureYou can find the structure of an Analytic view by displaying the Definition of thecorresponding Column ViewIn the table listing all fields in the view, right-click and choose ‘Export SQL’ from thecontext menu.

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview


© SAP AG 2009

TIP: Define Table Output StructureA SQL Select Statement also return the structure of Analytical view.

Feature is disabled at present

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

Calculation View (scripting)Function definition

© SAP AG 2009

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 tofilter 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

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

Calculation View (scripting)Function Body

© SAP AG 2009

SQL Script FunctionThe body of the SQL script function is a sequence of

SQL commandsCalls to other SQL script functions

Ensure that the selected fields corresponds to previously defined Output tablestructure of the function.

Example :SQL_A =

SELECT MATNR, KUNNR, …FROM <COPA_ACTUAL_ANALYTICAL_VIEW_1>;

SQL_P =SELECT MATNR, KUNNR, …FROM <COPA_PROJECTED_ANALYTICAL_VIEW_2>;

TABLE_OUTPUT_STRUCTURE =SELECT * FROM <SQL_A> UNION SELECT * FROM <SQL_P>;

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

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

© SAP AG 2009

Verify result (log area of the SQL editor).Set

Parameters

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

Execute the view

Calculation View (scripting)Defining the metadata of the output structure

© SAP AG 2009

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

Define which fields of the output structure are attributes/measuresLike with analytic views, one can define attributes and measures from the view data

Switch to editor tab ‚Logical View‘The output structure (OUT parameter) is our ‚data foundation‘Add some or all of the fields as attributes/measures

Calculation View (scripting)Save and activate

© SAP AG 2009

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

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 2009

SetParamet

ers

DefineTable

OutputStructur

e

DefineFunction

(Inputand

OutputStructur

e)

WriteSQL

Statement

Execute

AssignAttribute

s andMeasure

s

Saveand

Activate

DataPreview

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 forColumn View)

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

- Analytic Views


© SAP AG 2009

Agenda

Lesson 6:


- Export & Import

- Attribute Views

- Calculation Views

Import and Export

© SAP AG 2009

Import and Export

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

Process Flow

© SAP AG 2009

Export InformationModel

Import InformationModel

Exporting an Information Model

© SAP AG 2009

Process Flow

© SAP AG 2009



ExportInformationModel

ImportInformationModel

Export Information Models

© SAP AG 2009

Select the type for export

Select the source systemExportInformationModel


Select Information Model and Source System For Export

© SAP AG 2009



Select Information Model from Package



© SAP AG 2009

Verify that the XML file has been created



Exporting System Landscape

© SAP AG 2009

Select the landscape you want to export



Verification of System Export

© SAP AG 2009



Process Flow

© SAP AG 2009



Import Information Model

© SAP AG 2009

Select the type of importHere ‚Information Models‘

Select target systemSystem/User combination




© SAP AG 2009



Search for Import Files


© SAP AG 2009



Add the components of the model you want to import

Import Information ModelMass activation of views

© SAP AG 2009

After importing a large number of viewsMass activation is available from ‘Quick Launch’Works like the import wizard:

Add entire packages, individual views, ...Activation takes into account dependenciesbetween views


© SAP AG 2009

Agenda

Lesson 6:


- Export & Import

- Attribute Views

- Calculation Views- Analytical Views

© SAP AG 2010

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 Analytical ViewCreate and display data for an Calculation ViewUnderstand the purpose of the Export / Import Functionality

© SAP AG 2010

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 changedwithout 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 theirrespective 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 andassociated 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 documentcontains 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, orother 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 ofmerchantability, 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 limitationshall 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 thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe 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 durchSAP 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 Servicessowie 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ähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. 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 anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrü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 Zwecksowie 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 Verwendungdieser 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 Hotlinkszugreifen, 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 überInternetseiten Dritter ab.Alle Rechte vorbehalten.

© SAP AG 2009

Agenda






Lesson 7: Reporting


Lesson 6: Modeling

Lesson Objectives

© SAP AG 2010

After completing this lesson, you should be able to:Understand connectivity options for reporting on top of HanaUnderstand the BusinessObjects BI4.0 plaform and reporting possibilitiesSet up various connectivity to Hana system for reporting

© SAP AG 2009

Agenda

Lesson 6: Reporting

HANA, Reporting layer and Connectivity options

BusinessObjects BI 4.0 Explorer

Others, Microsoft Excel

Appendix

Exercise

Crystal Reports via ODBC/JDBC connections

BusinessObjects BI 4.0 Enterprise

BusinessObjects BI 4.0

ERP

Architecture OverviewIn Memory Computing Engine (IMCE) and Surroundings

LogERP DB



DashboardDesign


Request Processing / Execution Control

MS Excel

BI4 Analysis

SQL Parser MDXSQL Script Calc Engine

TransactionManager

Session Management





MetadataManager

IMCE Studio


LoadController

ReplicationAgent

ReplicationServer

SAP Business Objects BI4


SBO BI4servers

(program)

SBO BI4InformationDesign Tool


SAPNetWeaver

BW3rd Party

DataServices

Reporting on HANAClients

© SAP AG 2009

SAP HANA

JDBCODBCODBOSQLDBC

SAP In-memory Computing Engine

SAP BusinessObjectsBI 4.0 Enterprise BI4

Repository

SAP BusinessObjects BI 4.0 reporting clients

SQ

L

MD

X

BIC

S

Auth

entic

atio

nC

onte

nt m

gmt

WebIntelligence

Crystal Reports Explorer DashboardDesigner

Excel

Reporting on HANAOpen interfaces

HANA 1.0 provides various interface reporting options during initial Ramp UpODBO – (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 Connectivity) – Microsoft-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 Connectivity) – Relational reporting drivers specified by the Javacommunity. Popular on Unix platforms.SQLDBC is SAP native database SDKBICS – BI Consumer Services (planned)

BICS is a fourth interface planned for the HANA 1.0 PlatformThis is the common driver technology used by SAP BusinessObjects Analysis, OfficeEdition for connectivity to SAP NetWeaver BWBICS offers advantages for OLAP access over MDX on multidimensional reporting objectsCurrent Plan is for late in Ramp Up to provide connectivity for SAP BusinessObjectsAnalysis, Office Edition

© SAP AG 2009

© SAP AG 2009

Agenda

Lesson 6: Reporting




Appendix

Exercise




Complete BI Suite to Put Together Informationin the Users’ Preferred Format

D I F F E R E N T N E E D S

Dashboards

Reporting

InteractiveAnalysis OLAP

AnalysisData

Exploration

How do I visualizekey performance

indicators forbetter decision

making?

How do I answerad hoc questionsand interact with

sharedinformation?

How do I findimmediateanswers tobusiness

questions?

How do I uncovertrends from

historical data andmake possible

better forecasts?

How do I turn datainto pixel-perfectformatted reports

for greaterinsight?

Reporting on HANASAP BusinessObjects BI4.0 Reporting Clients

© SAP AG 2009

WebIntelligence(InteractiveAnalysis)

Explorer

Guided

DashboardDesign

(Xcelsius)

Search &Exploration Ad-Hoc QRA Dashboarding &

VisualizationEnterpriseReporting

Interactive ExperienceFree

ProfessionallyInformed

TechnicallyCapable

InformationConsumers

Executives &Managers

BusinessAnalysts

CrystalReports

Ad Hoc Query, Reporting, AnalysisSAP BusinessObjects BI4.0 Web Intelligence

Empower business users withpowerful, yet easy to use analysisIntuitive, Web-based interface withoffline capabilitiesStart from a blank slate or use anexisting 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 ofinformation with universes

New screen shotneeded

Consume attractive, personalizeddashboards online or offline

Access to personalized, Flash-baseddashboardsSecure visualizations anywhere –portal, reports, PDF, MS Officedocuments

Empower business users withinteractive information

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

Dashboarding & Data VisualizationSAP BusinessObjects BI4.0 Dashboard Design (Xcelcius)

Bring BI to all business usersSimplicity and speed of searchIntuitive data exploration andvisualizationFast response across mountains ofdata anywhere in the organizationAccelerated version with in-memorytechnologies

Help IT to be successfulEasy and efficient to manageand scaleMore reactive to business withfaster deliverySupport for heterogeneous datasources

Data Search and ExplorationSAP BusinessObjects BI4.0 Explorer

Pixel perfect reportingSAP Crystal Reports

New styling with ribbon barlook and feelCommon query designexperience across all datasources with new semanticlayerAutomated report translationfor global deployments

Next-Generation ReportDesigner Experience

“The” Business Intelligence placeSAP BusinessObject BI 4.0 Launch Pad

New self-service BI accessmaking it easier to find allavailable contentEnhanced filtering andsearch options reducingpage scrollingEnhanced navigation forworking with multipledocuments at the same time

Self-Service InformationConsumption

User personalized BI WorkspaceSAP BusinessObjects BI.40 BI Workspace

Hom

ePage Modules

BI Workspace

Web C

ontent

Agnostic

Crystal R

eports

Analysis

Web Intelligence

Dashboards

Reporting, Analysis Other ContentVisual

Organizing and displayingany BI content withdecreased IT dependencySimple WYSIWYGauthoring for creating andmodifying contentInter-portlet communicationenabling informationexchange betweencomponents

Personalized InformationConsumption

© SAP AG 2009

Agenda

Lesson 6: Reporting

Hana, reporting layer and connectivity options



Appendix

Exercise




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

Use familiar key-word searchto find business informationAnswers “on-the-fly” andinvestigative questions

Searches directly onpre-indexed data

No previous reports or metricsneed existProvides fast search andexploration

Searches across all datasources

Any universe accessible sourceAny SAP NetWeaver BWAccelerator accessible sourceAnd of course any accessibleHANA system

…and Then It’s Exploration Of the Results

Intuitively explore ondata

No data model or dataknowledge required

Automated relevancyof results

Most relevant informationis displayed first

Best chart type autogenerated

Share insights with othersExport to Web Intelligence, CSV or image

Save it locally as a browser bookmarkOne-click to send a link to the results by email

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

Explorer for HANAInformation Spaces creation

© SAP AG 2009

Agenda

Lesson 6: Reporting




Appendix

Exercise




Semantic Layer Mission

Enable the business users to freely and securely access, analyze, enrich andshare 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 usedthroughout the organizationEnable consumption by all applications and BI toolsAllow IT to keep control and ensure security of information

SemanticLayerData Sources

Query and Analysis

Dashboards andVisualizations

Reporting

Full-SpectrumBusiness Intelligence

Common Semantic Layer

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

Pioneer WebIntelligence

CrystalReports Xcelsius

Common Semantic Layer

InfoProvider

Data Source DTP DSO

XMLWS

BI Consumption

Business Semantic Design

Data Access Design

ETL

Common semantic layer = one unified approach for meta data support

Semantic Layer deliverables in 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 formatby 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 & computationBehind the scenes, this is the component that enablesquerying and computational capabilities to BI clients

during report consumption.

ConnectivityThis is the component that establishes the connectivity

to data sources.

Information Design ToolHow to set-up a new Connection

© SAP AG 2009

CreateNew

Project

CreateConnection

Selectdriver

Defineconnectionparameters

Test

Information Design Tool

© SAP AG 2009

CreateNew

Project

Createconnectio

n

Selectdriver


Test

Menu>File>New Project


© SAP AG 2009

Create New Connection

CreateNew

Project

Createconnectio

n

Selectdriver


Test


© SAP AG 2009

Select HANA JDBC Driver

CreateNew

Project

Createconnectio

n

Selectdriver


Test


© SAP AG 2009

Define Parameters:

Authentication ModeUser NamePasswordServer

Test connection

CreateNew

Project

Createconnectio

n

Selectdriver


Test


© SAP AG 2009

Create DataFoundation

SelectSource

Type

SelectConnection

Design DataFoundation

How to create a Data Foundation


© SAP AG 2009


SelectSource Type

SelectConnection


Create Data Foundation


© SAP AG 2009


SelectSource Type

SelectConnection


Create Data Foundation Source Type


© SAP AG 2009


SelectSource Type

SelectConnection


Select Connection


© SAP AG 2009


SelectSource Type

SelectConnection


Design Data Foundation

Information Design ToolHow to create a Business Layer (Universe)

© SAP AG 2009

CreateBusiness

Layer

AssignName

Select DataFoundation

DesignBusiness

Layer

ConsumeBusiness

Layer


© SAP AG 2009

CreateBusiness

Layer

AssignName

SelectData

Foundation

DesignBusine

ssLayer

ConsumeBusiness

Layer

Create Business Layer

Information Design ToolBusiness layer creation

© SAP AG 2009

CreateBusiness

Layer

AssignName

SelectData

Foundation

DesignBusine

ssLayer

ConsumeBusiness

Layer

Assign Name


© SAP AG 2009

CreateBusiness

Layer

AssignName

SelectData

Foundation

DesignBusine

ssLayer

ConsumeBusiness

Layer

Select Data Foundation


© SAP AG 2009

CreateBusiness

Layer

AssignName

SelectData

Foundation

DesignBusiness

Layer

ConsumeBusiness

Layer

Design Business Layer

SAP BusinessObjects BI4.0Consuming the business layer

From there, the Business Layer (or Universe) has to be consumed, bycreating for web intelligence reports, or dashboard with Dashboard

Design.

This Business Layer can, and must be, published with itsconnection(s) to the BI 4.0 server.

© SAP AG 2009

CreateBusiness

Layer

AssignName

AssignData

Foundation

DesignBusine

ssLayer

ConsumeBusiness

Layer

© SAP AG 2009

Agenda

Lesson 6: Reporting




Appendix

Exercise




Reporting on HANAODBC drivers installation

Client driver install is included with the HANA Information Modeler installCan be installed at the command line fromthe Studio/Modeler DVDCommand line: hdbinst –a clients

© SAP AG 2009

For ODBCIt is important to synchronize ODBCdriver platform (32bit/64bit) with MS Officeversion (32bit/64bit)

e.g. 64 bit drivers can‘t be used in 32 bit Microsoft ExcelNote that on 64bit platforms the 32bit ODBC Administrator is not in the System Control panel

Configure 32bit drivers under Win64 via C:\Windows\SysWow64\ODBCAD32.exeAfter initial configuration, the DSN will be available in Control Panel-based ODBCAdministrator

Reporting on HANAODBC access

Standard ODBC DSNs is the foundation of reportingDriver appears as HDBODBC or HDBODBC32 dependingon your platform

Note that in early testing, Excel was *not* a good choicefor ODBC-based reporting since ODBC reporting is basedon MSQuery and MSQuery has a limitation of 4,000 tables

Early testing was done with SAP IDES dataso >4,000 tables imported to HANAhttp://support.microsoft.com/kb/115090/en-us

In driver definitions the „database“ is considered to be the HANA SID

© SAP AG 2009

http://support.microsoft.com/kb/115090/en-us

Reporting on HANAODBC access in Crystal Reports (one example)

Tables as seen in Crystal 2008 via HDB ODBC driver

© SAP AG 2009

Reporting on HANAJDBC (Java DataBase Connectivity)

© SAP AG 2009

JDBC provides and alternative to ODBC fordatabase connectivity

Popular in *nix (server) environments as ODBC configon *nix can be difficultFor heavy Java environments, provides „zero config“opportunites via Java Naming and Directory Interface(JNDI)Benefits description here:http://java.sun.com/products/jdbc/overview.html

Note: for environments where the data source onlyprovides ODBC database drivers, a JDBC-ODBCbridge is available from most JDBC driver vendors

http://java.sun.com/products/jdbc/overview.html

Configure JDBC connectivityExample using Crystal Reports 2008

© SAP AG 2009

Pre-requesites for JDBC configuration for Crystal ReportsHDB Client has to be installed including the ngdbc.jar file

Default install location is the <\Program Files\SAP\hdbclient> directory on the clientmachine

Specific JDBC config for Crystal Reports (other JDBC clients would have similar setup)NOTE: This is a clear advantage of Crystal Enterprise in the BI Platform 4.0 release:

connectivity is defined once via Semantic LayerCrystal consumes data via the Semantic Layer, no individual client configuration.

CRConfig.xml file on the client system has to be setup with key parameters for the targetdatabase

Must have selected JDBC support on the Crystal Reports installation to have this fileDefault location of this file <\Program Files\Business Objects\Common\4.0\java>on the client machine where Crystal is installedYour file’s location will vary based on the install directory chosen on the client whereyou’re working

Final parameters to enter in the database connection dialogues of Crystal Reports

JDBC config for Crystal 2008 (2)Configuring CRConfig.xml file

© SAP AG 2009

Configuring CRConfig.xmlFull documentation for Crystal-JDBC connections is found here:http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/e0d98a3c-6764-2b10-e4b7-d55e0178eedb&overridelayout=trueShort version for our purposes

Business Objects installs with a JRE (Java Runtime Engine). If you already have onerunning, you can change settings accordingly (affects <JavaDir> parameter)

Acid test: run „java –version“ from the command line.Settings required

Valid <JavaDir> entryCan point it to the JRE install with Crystal: (default) <\Program Files\BusinessObjects\Common\4.0\java>

<ClassPath> entryMust point to the ngdbc.jar file: <\Program Files\SAP\hdbclient\ngdbc.jar>

http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/e0d98a3c-6764-2b10-e4b7-


© SAP AG 2009

CRConfig.xml parameters (cont)The following two entries are optional– if you don‘t enter them here, you enter at login.<JDBCURL> values can be found in the Client Modeling tool (or, from system admin)Format is: jdbc:sap://<yourserver>:<yourserverport>In the Information Modeler, Right Mouse click on system -> Properties -> System -> JDBC-> Advanced (button)


© SAP AG 2009

CRConfig.xml parameters (cont)<JDBCClassName> parameterAlso found in the console under the „Driver Name“ setting

Default value for SAP HDB - com.sap.db.jdbc.Driver

At this point, CRConfig.xml has basic functionality to provide HDB Connectivity via JDBC

JDBC config for Crystal 2008 (5)Runtime Connection Definition

© SAP AG 2009

Finalize configuration via Crystal Reports interfaceLaunch Crystal Reports and Select JDBC(JNDI) under Create New Connections in theDatabase ExpertConnection parameters filled in from CRConfig.xml entries, Click NEXT.


© SAP AG 2009

Final entriesEnter Database (this is the HDB SID)User/passwordClick Finish


© SAP AG 2009

Select a table inCrystal

Expand Catalogunder the databaseconnection nameSelect a View (ortable of interest)Click on Singlechevron to select thetable for reportingClick OK


© SAP AG 2009

Begin Report Design

© SAP AG 2009

Agenda

Lesson 6: Reporting




Appendix

Exercise




Reporting on 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 avalable locally (workarounds exist)Subject to performance limitations of the desktop machine where Excel runs

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

© SAP AG 2009

Reporting on HANANative Excel interface via ODBO (2)

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

Clicking OK yields HANA Logon:

© SAP AG 2009

Reporting on HANANative Excel interface via ODBO (3)

Analytic/Calculation views (aka “Cubes”) are available per your authorizations:

© SAP AG 2009

These settingsrecommendedduring ramp upphase

Reporting on HANANative Excel interface – the Pivot Table

© SAP AG 2009

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

Not supportedRamp Up phase

© SAP AG 2010

Summary

After completing this lesson, you should be able to:Explain connectivity options for reporting on top of HanaGive an overview of the BusinessObjects BI4.0 plaform and reportingpossibilitiesSet up connectivity to Hana system for reporting

© SAP AG 2009

Agenda

Lesson 6: Reporting




Appendix

Exercise




© SAP AG 2009

Agenda

Lesson 6: Reporting




Appendix

Exercise




Java Testing: setting a trace on the NewDBJDBC database driver (Windows)

© SAP AG 2009

To trace the Java connection:

- Enter command Line interface (Start -> Run -> cmd.exe on most Win platforms)

- Confirm java.exe is in path (run “java –version” from command line)

- Change to folder containing ngdb.jar file (installed with HDB Client installer)

- Type “java –jar ngdbc.jar” on the command line:

Configure trace file

© SAP AG 2009

This forces a popup to define trace file settings:Select Trace EnabledChange the folder to a valid path on your machine (make sure it‘s writeable to your user)Trace file name: trace file results file

Click ApplyIMPORTANT: Click OK for trace to start!

Start application from Command Line

© SAP AG 2009

Now, start the application to be tracedFrom the same command line, start your application.Tracing begins when Java interface is first activatedExample (your environment might vary slightly)

C:\Program Files (x86)\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\crw32.exe

NOTE: TRACING STAYS ON UNTIL YOU EXIT THE APPLICATION. Files get huge. ‘Nuff said.

Lesson Objectives

© SAP AG 2010

you should now be able to:Understand connectivity options for reporting on top of HanaUnderstand the BusinessObjects BI4.0 plaform and reporting possibilitiesSet up various connectivity to Hana system for reporting

© SAP

Agenda






Lesson 7: Reporting


Lesson 6: Modeling

© SAP AG 2009

Agenda

Lesson 8:

User Management

Exercise

Security Details

Lesson Objectives

© SAP AG 2010

After completing this lesson you will be able to create and assign usersand roles in SAP In-Memory Computing Engine 1.0 :

User CreationRole Creation and assignmentAnalytic View (Authorization) Creation

© SAP AG 2010

User Management

SAP In-Memory Computing studio is used for user provisioningCreation of usersCreation of roles and role hierarchyAssignment of users to rolesAuthentication: To check if users really are who they say they areThe SAP in-memory computing engine provides the following options for authentication, also

Direct logon to SAP In-Memory Computing Engine with user name and password– SAP In-Memory Computing Engine authenticates usersAuthentication using third-party authentication providers:Kerberos -> Active Directory, can be integrated into single-sign-on landscape– External services Authenticates users (eg. Active Directory Server)– External sevices then passes logon token to SAP In-Memory Computing Engine

User Creation

User Managerment

User and Role ConceptAllows for a fine granularity of access control, based on the users‘ tasks:

Business end users (consume reports using client tools, e.g. Excel)Modelers (create models and reports using SAP in-memory computing studio)Engine administrators (operate and maintain the engine and users, using studio),SYSTEM administrator created during installationReplication users (carry out data replication on ERP source system and target system)

Free definition of rolesRoles are assigned to users, and roles can also be assigned to roles (role hierarchy)User provisioning is carried out using the SAP in-memory computing studio

User and Role Concept

Process Flow

© SAP AG 2009

Defineand

CreateRoles

AssignPrivilegesto Roles

CreateUsers

AssignUsers to

Roles

Process Flow

© SAP AG 2009

Defineand

CreateRoles


CreateUsers

AssignUsers to

Roles

In The SAP IMC Studio, open the context menu on [Roles] to open new user windows

© SAP AG 2009

User ManagementRole Creation

Specify [Role Name],

Define andCreate Roles

AssignPrivileges toa Role

CreateUsers

AssignUser toRoles

Process Flow

© SAP AG 2009

Defineand

CreateRoles


CreateUsers

AssignUsers to

Roles

IMCE Authorizations

Types of privilegesSystem privileges

Am I allowed tocreate users, ...?

SQL privilegesWhich tables can I readfrom / write to, ...? Am Iallowed to create/droptables in schema XYZ?

Analytic privilegesWhich part ofthe data in a viewmay I see?

Privileges

Define andCreateRoles

AssignPrivilegesto a Role

Create

Users

AssignUser toRoles

IMCE Authorizations

SQL privilegesFixed set of privilegesRestrict access to and modification of database objects such as tablesSchema privileges:

DROP, CREATE [ANY], INSERT, SELECT, UPDATE, DELETE, EXECUTEData Object privileges:

INSERT, SELECT, UPDATE, DELETE, EXECUTE, INDEX, ALTER, DROPSQL privileges are assigned/revoked using the Administration Console Perspective of theSAP In-Memory Computing Studio

SQL Privileges



Create

Users

AssignUser toRoles

Select, [+] on SQL Privileges, Search and select a table to Grant SQL operations

© SAP AG 2009

User ManagementRole Creation – Assigning Privileges

Search

Select

Click, OK



Create

Users

AssignUser toRoles

Grant SQL operations for the selected table by mark the operations

© SAP AG 2009

User ManagementRole Creation – Assigning Privileges



Create

Users

AssignUser toRoles

IMCE Authorizations

System privilegesFixed set of privilegesRestrict execution of administration tasks within the database, such as user managementSystem Privileges

USER ADMIN, ROLE ADMIN, DATA ADMIN, ALTER SYSTEM, ALTER DATABASE,CREATE SCHEMA

System privileges are assigned/revoked using the administration console of the SAP In-Memory Computing Studio

SYSTEM Privileges



Create

Users

AssignUser toRoles

IMCE Authorizations

Analytic PrivilegesEvaluates attributes in Analytic Views

May be defined directly on Analytic ViewOr on Attribute View used within the Analytic View

Used to filter access to business data based on Attributes by RestrictionsExample "country = Germany, year = 2006“

Only applied at processing time of the user queryAnalytic privileges cannot be defined on hierarchies or measures

Analytic Privileges



Create

Users

AssignUser toRoles

In The SAP IMC Studio, open the context menu on [Analytic Privileges], underInformation Models’ Package

© SAP AG 2009

User ManagementAnalytic Privileges Creation

Specify Name, and give it a description.Select an Information Model View



Create

Users

AssignUser toRoles

Assign an Attribute to evaluate privileges by [Add…], and select an Attribute

© SAP AG 2009

User ManagementAnalytic Privileges Creation – Specifying Attributes



Create

Users

AssignUser toRoles

Click on [Add…]

© SAP AG 2009

User ManagementAnalytic Privileges Creation – Specifying Restrictions

Search

Select

Click, OK

*This Analytic Privilege willshow entries with

PRODUCT value = BW



Create

Users

AssignUser toRoles

Confirm the contents, Save and activate,

© SAP AG 2009

User ManagementAnalytic Privileges Creation – Save and Activate

Activate

Successful, ActivationDefine andCreateRoles


Create

Users

AssignUser toRoles

Select [Analytic Privileges] tab in a user or role, Click [+] to add Analytic Privileges

© SAP AG 2009

User ManagementAnalytic Privileges Assignment – repeat from Role

Search

Select

Click, OKDefine and

CreateRoles


Create

Users

AssignUser toRoles

Deploy and confirm Deploy

© SAP AG 2009

User ManagementAnalytic Privileges Assignment – repeat from Role

Successful, Deploy



Create

Users

AssignUser toRoles

Save and Deploy the Role to IMCE

© SAP AG 2009

User ManagementRole Creation – Save and Deploy

Successful, DeployDefine andCreateRoles


Create

Users

AssignUser toRoles

Check New Role have been register to IMCE by drill down [Roles].

© SAP AG 2009

User ManagementRole Creation – Confirm Role Deploy


AssignPrivilegeto a Role

CreateUsers

AssignUser toRoles

Process Flow

© SAP AG 2009

Defineand

CreateRoles


CreateUsers

AssignUsers to

Roles

User Management

In The SAP In-Memory Computing Studio(IMC Studio)’s Information Modeler Perspective, openthe context menu on [Users] to open new user windows

© SAP AG 2009

User Creation Steps


AssignPrivilege

s to aRole

CreateUsers

AssignUser toRoles

Enter [User Name:], [Description:]

Select [internal] Authentication and specify passwordNote: [external] Authentication is used to MAP users with an external authentication provider

© SAP AG 2009

User ManagementUser Creation Steps - User


AssignPrivilege

s to aRole

CreateUsers

AssignUser toRoles

Process Flow

© SAP AG 2009

Defineand

CreateRoles


CreateUsers

AssignUsers to

Roles

Click on the [+] to add Role, Search and Select a role to assign

© SAP AG 2009

User ManagementUser Creation Steps – Assigning Role

Search

Select

Click, OK


AssignPrivilege

s to aRole

CreateUsers

AssignUser toRoles

Confirm the Role have been assigned, and Deploy(register) the user to IMCE

© SAP AG 2009

User ManagementUser Creation Steps – Assigning Role

Successful, DeployDefine andCreateRoles

AssignPrivilege

s to aRole

CreateUsers

AssignUser toRoles

Check New User have been register to IMCE by drill down [Users] and user[SCHEMA] area under Default catalog.

© SAP AG 2009

User ManagementUser Creation Steps – Confirm User Deploy


AssignPrivilege

s to aRole

CreateUsers

AssignUser toRoles

© SAP AG 2009

Agenda

Lesson 7:

User Management

Exercise

Security Details

Reporting and Privileges

What privileges do I need in order to read from a given view?One always needs SQL SELECT for the column viewFor Attribute Views:

No Analytic privilege required / possible(can create them, but they are not evaluated)Need SQL SELECT on the Column View for the Attribute View

For Analytic Views:At least one analytic privilege is needed

Defined on Analytic View itself, or on Attribute View used within Analytic ViewWithout analytic privilege for the view, no data is returnedThere is a „See everything system wide“ privilege: „_SYS_BI_CP_ALL“Need SQL SELECT for the Column View for the Analytic View

For Calculation views:No analytic privilege required for the Calculation View itselfIf Analytic View used in Calculation View: need Analytic Privilege for that Analytic ViewNeed SQL SELECT for all views and tables explicitly used in the Calculation ViewNeed SQL SELECT for the Column View for the Calculation View

Required Privileges for reporting

Creating Analytic Privileges

What privileges do I need in order to create Analytic PrivilegesThe user only needs the ‚ALTER SYSTEM‘ system privilege

No SQL SELECT or other SQL privilege needed

As Modelers require ALTER SYSTEM, tooAny Modeler is allowed to create and activate analytic privileges

Privileges are implicitly assigned to user who activates them

Privileges required

Modeling

What privileges do I need in order to do modeling?SQL Privileges needed:

CREATE ANY, INSERT, UPDATE, DELETE, SELECT on _SYS_BICthe modeler creates column views in that schema

SELECT on the tables used in the viewin RKT system: you have SELECT for the entire SYSTEM schema.

System privileges:ALTER SYSTEM, DATA ADMIN

Analytic PrivilegesStrictly, none requiredFor being able to preview/test views: some analytic privilege

In RKT system: you have „_SYS_BI_CP_ALL“Consequences of these facts:

Any Modeler can create their own analytic privileges, since they have „ALTER SYSTEM“Any Modeler can see all data in the tables they use in the modelAny Modeler can see all data in the views (because they can authorize themselves)

Modeling on confidential data hardly possible in a production systemneed two-system landscape, model on randomized data, then import

Privileges required

Importing

What privileges do I need in order to do modeling?SQL Privileges needed:

CREATE ANY, INSERT, UPDATE, DELETE on _SYS_BICneed to create the column view in that table

But not needed: SELECT on _SYS_BICthe user would not be able to read from the view

Apparently required: SELECT on tables in the viewshould require SELECT/INSERT/UPDATE/DELETE on _SYS_BI (for MDX master dataetc. in BIMC-tables)

System privileges:ALTER SYSTEM

Analytic PrivilegesNone required

Privileges required

Analytic Privileges

How can I combine conditions within one privilege? Several privilegesWithin one Privilege

Can add several conditions for one attributeEach of them may be „EQUAL“, „BETWEEN“, „IN“They are combined using an „OR“ operator

Can add conditions for several different attributesoverall constraint = (constraints on attribute 1) AND (constraints on attribute 2)

Can combine several analytic privileges for one viewOverall constraint = (constraint from privilege 1) OR (constraint from privilege 2)

Current limitation:‚IN‘-list cannot be defined in modeler (but engine could evaluate it if it was defined)

Can only create „EQUALS“ or „BETWEEN“ constraint using modeler.Cannot restrict on columns

users can always see all columns in a table/view (or none)

“Complex authorizations”

Security Concept

What one should keep in mind when using HANA on sensitive dataReplication server places all tables into SYSTEM schema

Schema belongs to built-in admin user „SYSTEM“this admin user has all permissions for all data in all tables of schema SYSTEM

Modelers can read from all tables in view, and can create/activate analytic privileges

Important features of the security concept

Analytic Privileges

Present UI featuresDirect input into the attribute-value field does not work

Is displayed, but lost on save/activation

So have to go through „Value Selection“-dialog:In that dialog, finding values does not work onAnalytic Views

Have to know the value you needDescription mapping is not used in thevalue-selection dialog

need to know the semantic keys

Features of the interface for creation

© SAP AG 2009

Agenda

Lesson 8:

User Management

Exercise

Security Concept

Lesson Objectives

© SAP AG 2010

After completing this lesson you will be able to create and assign usersand roles in SAP In-Memory Computing Engine 1.0 :

User CreationRole Creation and assignmentAnalytic View (Authorization) Creation

Tzhana en Col96 Show[1]

Documents

eine produktstrategie

aber nicht

einen bestimmten

set paramete

set paramet

alle rechte

pa line items

links oder