ha100-en-col98-fv-inst-a4.pdf

HA100SAP HANA Introduction

SAP HANA

Date

Training Center

Instructors

Education Website

Instructor HandbookCourse Version: 98Course Duration: 2 Day(s)Material Number: 50116131Owner: Jrg Weishaar (D038879)

An SAP Compass course - use it to learn, reference it for work

Copyright

Copyright 2012 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout 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 softwarecomponents of other software vendors.

Trademarks

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, Systemz, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, PowerSystems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter,System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarksor registered trademarks of IBM Corporation.

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

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks ofAdobe Systems Incorporated in the United States and other countries.

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

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin aretrademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C, World WideWeb Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina,Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch,BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World aretrademarks or registered trademarks of Research in Motion Limited.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, GoogleMobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater,Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registeredtrademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

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

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

g2013031640

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of Business ObjectsSoftware Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase productsand services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of CrossgateAG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National product specificationsmay vary.

Disclaimer

These materials are subject to change without notice. These materials are provided by SAP AG andits affiliated companies (SAP Group) for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to thematerials. The only warranties for SAP Group products and services are those that are set forth inthe express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.

g2013031640

g2013031640

About This HandbookThis handbook is intended to complement the instructor-led presentation of thiscourse, and serve as a source of reference. It is not suitable for self-study.

Typographic ConventionsAmerican English is the standard used in this handbook. The followingtypographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. Theseinclude field names, screen titles, pushbuttons as wellas menu names, paths, and options.

Also used for cross-references to other documentationboth internal and external.

Example text Emphasized words or phrases in body text, titles ofgraphics, and tables

EXAMPLE TEXT Names of elements in the system. These includereport names, program names, transaction codes, tablenames, and individual key words of a programminglanguage, when surrounded by body text, for exampleSELECT and INCLUDE.

Example text Screen output. This includes file and directory namesand their paths, messages, names of variables andparameters, and passages of the source text of aprogram.

Example text Exact user entry. These are words and characters thatyou enter in the system exactly as they appear in thedocumentation.

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

2012 2012 SAP AG. All rights reserved. v

About This Handbook HA100

Icons in Body TextThe following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructorspresentation.

vi 2012 SAP AG. All rights reserved. 2012

Contents

Course Overview .......................................................... ixCourse Goals .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixCourse Objectives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Unit 1: Introduction and Positioning .................................. 1

Introduction to SAP HANA.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2SAP HANA Scenarios .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Rapid Deployment Solutions RDS... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Unit 2: SAP HANA Studio .............................................. 39

SAP HANA Studio .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Unit 3: Architecture...................................................... 71

Architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Persistence Layer.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Backup & Recovery.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Unit 4: Data Provisioning ............................................. 101

Uploading Data from Flat Files .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103SAP Data Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111SAP LT Replication Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120SAP Direct Extractor Connection (DXC)... . . . . . . . . . . . . . . . . . . . . . . .131

Unit 5: Modeling......................................................... 139

Introduction to CO-PA Scenario.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140Introduction to Modeler perspective ... . . . . . . . . . . . . . . . . . . . . . . . . . . . .148Levels of Modeling... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

Unit 6: Reporting........................................................ 233

SAP HANA Database Connectivity Options... . . . . . . . . . . . . . . . . . . .235Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239SAP BusinessObjects .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247SAP BusinessObjects Analysis for Office ... . . . . . . . . . . . . . . . . . . . . .257SAP BusinessObjects Analysis for OLAP ... . . . . . . . . . . . . . . . . . . . . .266SAP BusinessObjects Explorer .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280SAP Crystal Reports for Enterprise, Dashboards and Web

Intelligence ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290

2012 2012 SAP AG. All rights reserved. vii

Contents HA100

Appendix 1: SQL Script Example (UNION) ..................... 321

Appendix 2: SQL Script Example (JOIN) ....................... 323

viii 2012 SAP AG. All rights reserved. 2012

Course OverviewSAP HANA enables business departments to analyze business as it happens.Individuals can create very flexible analytical models based on real-time dataoriginating from business applications. ERP operational analytics is furtherenhanced with SAP HANA interfaces to BI client reporting tools, such asSAP BusinessObjects Explorer, SAP Crystal Reports, SAP BusinessObjectsDashboards and SAP BusinessObjects Web Intelligence.

This two day introductory course is for consultants, project team members andmodelers seeking to learn about this exciting new technology. The course explainshow to perform basic modeling and administrative tasks in SAP HANA Studio.Tasks include data provisioning using SAP BusinessObjects Data Services andcreating flexible analytical models based on real-time data originating fromSAP ERP applications. In order to cover the full spectrum, delegates will alsolearn about connectivity interfaces from SAP BusinessObjects BI 4 tools suchas SAP BusinessObjects Explorer, SAP BusinessObjects Analysis and SAPBusinessObjects Web Intelligence into SAP HANA for reporting purposes, inorder to cover an end to end scenario.

Target Audience

This course is intended for the following audiences:

Application Consultants

Project team members

Course Prerequisites

Required Knowledge

Essential: None

Recommended: SAP ERP reporting and analytics, General BusinessModeling experience, Basic understanding of business system landscapes

Course Duration DetailsUnit 1: Introduction and PositioningIntroduction to SAP HANA 30 MinutesSAP HANA Scenarios 30 MinutesRapid Deployment Solutions RDS 15 Minutes

Unit 2: SAP HANA StudioSAP HANA Studio 15 Minutes

Unit 3: Architecture

2012 2012 SAP AG. All rights reserved. ix

Course Overview HA100

Architecture 40 MinutesPersistence Layer 25 MinutesBackup & Recovery 30 Minutes

Unit 4: Data ProvisioningUploading Data from Flat Files 15 MinutesSAP Data Services 30 MinutesSAP LT Replication Server 15 MinutesSAP Direct Extractor Connection (DXC) 15 Minutes

Unit 5: ModelingIntroduction to CO-PA Scenario 15 MinutesIntroduction to Modeler perspective 15 MinutesLevels of Modeling 15 Minutes

Unit 6: ReportingSAP HANA Database Connectivity Options 15 MinutesMicrosoft Excel 15 MinutesSAP BusinessObjects 15 MinutesSAP BusinessObjects Analysis for Office 15 MinutesSAP BusinessObjects Analysis for OLAP 15 MinutesSAP BusinessObjects Explorer 15 MinutesSAP Crystal Reports for Enterprise, Dashboardsand Web Intelligence 15 Minutes

Course GoalsThis course will prepare you to:

Get a good understanding and overview of SAP HANA

Course Objectives

After completing this course, you will be able to:

Explain SAP HANA Concepts

Use SAP HANA Studio

Create Information Models

Understand how data can be loaded into HANA.

Get an overview of how to report on HANA using client tools

x 2012 SAP AG. All rights reserved. 2012

HA100 Course Overview

Important Information

It is strongly recommended to check necessary information publishedon the SAP Service Market Place. All information essential for coursepreparation like instructor guides, system setup guides, trouble shootingguides, logon information, and so on, you will find under the alias /curr-info(http://service.sap.com/curr-info).

In case you cannot access this site please ask the responsible education coordinator(the sender of this document) to make the relevant information available to you.

2012 2012 SAP AG. All rights reserved. xi

Course Overview HA100

xii 2012 SAP AG. All rights reserved. 2012

Unit 11 Introduction and Positioning

Unit OverviewThis unit provides an overview to SAP HANA positioning.

Unit ObjectivesAfter completing this unit, you will be able to:

Explain the current existing pain points in a system using a classic database

Explain how SAP HANA can handle the pain points and help to improveprofit

Explain the architecture of SAP HANA as an accelerator in a side-carscenario

Explain the architecture of SAP HANA as an In-Memory Database

Understand, what is an RDS

How you could get and use an RDS

Unit ContentsLesson: Introduction to SAP HANA .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Lesson: SAP HANA Scenarios .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Lesson: Rapid Deployment Solutions RDS ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2012 2012 SAP AG. All rights reserved. 1

Unit 1: Introduction and Positioning HA100

Lesson:

2

Introduction to SAP HANALesson Duration: 30 Minutes

Lesson OverviewThis lesson presents why SAP HANA has been developed and how this newtechnology can help increasing business opportunities.

Lesson ObjectivesAfter completing this lesson, you will be able to:



Business ExampleToday, a lot of companies need to deal with an amazing amount of data and are notable to report on them efficiently due to data volume.

Information Explosion

Figure 1: Reality #1: Information Explosion


HA100 Lesson: Introduction to SAP HANA

First, the information explosion. Massive amounts of data is being created everyyear, and how fast your business reacts to it determines whether you succeed orfail.

This is a big problem and it is getting bigger.

IDC estimates that worldwide digital content added up to 487 billion gigabytes in2009. They predict this will double in 18 months, and every 18 months thereafter.

Its like a stack of DVDs all the way to the moon and back.

In a Sloan Management survey in 2010 60% of executives said their companieshave more data than they know how to use effectively. With data doubling every18 months, that percentage is going to keep growing.

According to EMC, by the end of 2011 there was 1.8 Zetabyte of digital data. 1Zetabyte is a trillion gigabytes.

Kilobyte>Megabyte>Gigabyte>Terabyte>Petabyte>Exabyte>Zetabyte>Yottabyte

http://germany.emc.com/collateral/about/news/idc-emc-digital-universe-2011-infographic.pdf

Figure 2: Reality #2: Consumerization of IT

At the same time, the consumerization trend is driving up expectations as towhat enterprise IT can help the business to do. People want instant access toinformation in the moment whether that is a moment of risk or a moment ofopportunity. If the moment has passed and your business has not taken the rightaction, it has failed. People want instant answers. They want them to be right.They want them anywhere, any time.



Figure 3: Reality #3: IT Cannot Deliver

This puts IT in a tough place. IT cannot deliver what the business needs. Why?Because the cost of managing that data explosion is too high. Because there isno practical way to instantly analyze everything thats going on relative to thebusiness. IT can deliver some of the information. The most critical slice ofinformation can be delivered in near real time. But its not enough. Data isgrowing. Demand is increasing.

We must find a way to deal with this a way to process and analyze massiveamounts of data in real time.

Figure 4: Your Reality with SAP HANA

That is the role of SAP HANA. Using groundbreaking in-memory hardware andsoftware we can manage data at massive scale, analyze it at amazing speed, andgive the business not only instant access to real time transactional information



and analysis but also more flexibility. Flexibility to analyze new types of data indifferent ways, without creating custom data warehouses and data marts. Even theflexibility to build new applications which were not possible before.

Figure 5: SAP In-Memory Appliance (SAP HANA)

So, whats inside HANA? This architecture diagram explains the main componentsand capabilities.

We keep throwing around words like massive amounts of data and amazing speed.What kinds of scale, speed and improvement are customers seeing?

Figure 6: SAP HANA Proof Points



Here are some proof points:

First, amazing speed. One of our pilot customers reduced the time it took torun a report from one hour to one second. That is 3600 times faster. Letsput that in perspective. SAP talks about helping you to run better, so letsuse that as an example. When an average person runs, they move at about7 miles per hour. 3600 times faster would be about 25,000 miles per hour.That is the fastest any human being has ever travelled, and it was only doneonce - by the astronauts on Apollo 10, on their return from the moon in 1969.

Amazing amounts of data. During testing for HANA we executed queriesagainst 460 billion rows of data in less than one second. That is like beingable to analyze every repair and service visit for every car on earth in the last12 months, in one second. Or to process every address that everyone alivetoday has ever lived at, in one second. Or to calculate the amount of taxespaid, by everyone on the planet, since 1950, in one second.

And finally, amazing value. Having the ability to create new real-timeprocesses and simplify your IT landscape has a big impact. According to astudy by Oxford Economics, companies that implement real-time systemssee an average 21% revenue growth, and a 19% reduction in IT cost.

Figure 7: Query Acceleration Example - Large Bank - 1 Month of CustomerInformation

Why wait for data?

All customers want to see their current business data immediately inreal-time. Nobody wants to wait until data is uploaded into BW.



Why wait for new systems?

Latest hardware and latest database technology already now supportreal-time reporting on massive amount of data.

Figure 8: SAP Naming Update: SAP HANA

SAP HANA

SAP HANA is a flexible, data-source-agnostic appliance that enablescustomers to analyze large volumes of SAP ERP data in real-time, avoidingthe need to materialize transformations.

SAP HANA appliance software is a hardware and software combination thatintegrates a number of SAP components including the SAP HANA database,SAP LT (Landscape Transformation) Replication Server, SAP HANA DirectExtractor Connection (DXC) and Sybase Replication technology.

The SAP HANA database is a hybrid in-memory database that combinesrow-based, column-based, and object-based database technology. It isoptimized to exploit the parallel processing capabilities of modern multi-coreCPU architectures. With this architecture, SAP applications can benefit fromcurrent hardware technologies.



Figure 9: DAILY CHALLENGES

Figure 10: CONSEQUENCES



Figure 11: HARDWARE INNOVATIONS

Moores law was initially forumulated in 1965. According to this law, the numberof transitors in a chip doubles every year. However, in 1975 this was adjusted byDavid House who said it will double every two years.

A widespread variant of Moores law states that the transistors wil double every 18months.

Figure 12: Improvements in Technology

Historically database systems were designed to perform well on computer systemswith limited RAM, this had the effect that slow disk I/O was the main bottleneckin data throughput. Consequently the architecture of those systems was designedwith a focus on optimizing disk access, e. g. by minimizing the number of diskblocks (or pages) to be read into main memory when processing a query.



Computer architecture has changed in recent years. Now multi-core CPUs(multiple CPUs on one chip or in one package) are standard, with fastcommunication between processor cores enabling parallel processing. Mainmemory is no-longer a limited resource, modern servers can have 2TB of systemmemory and this allows complete databases to be held in RAM. Currently serverprocessors have up to 64 cores, and 128 cores will soon be available. With theincreasing number of cores, CPUs are able to process increased data per timeinterval. This shifts the performance bottleneck from disk I/O to the data transferbetween CPU cache and main memory.

Figure 13: UNDERSTAND Column Data Storage

The concept of column data storage has been used for quite some time. Historicallyit was mainly used for analytics and data warehousing where aggregate functionsplay an important role. Using column stores in OLTP applications requires abalanced approach to insertion and indexing of column data to minimize cachemisses.

The SAP HANA database allows the developer to specify whether a table is to bestored column-wise or row-wise. It is also possible to alter an existing table fromcolumnar to row-based and vice versa.



Figure 14: Fast - SW Side Optimization for Memory

Conceptually, a database table is a two-dimensional data structure with cellsorganized in rows and columns. Computer memory however is organizedas a linear structure. To store a table in linear memory, two options exist, arow-oriented storage stores a table as a sequence of records, each of which containthe fields of one row. On the other hand, in a column store the entries of a columnare stored in contiguous memory locations.

Figure 15: Key Facts: When to Use Row Store, when Column Store?

Row Store

If you want to report on all the columns then the row store is more suitablebecause reconstructing the complete row is one of the most expensivecolumn store operations.



Column Store

If you to want to fill the table with huge amounts of data, that should beaggregated and analysed then a column store is more suitable

Figure 16: Partitioning

Figure 17: Parallel Processing

Data is only partially blocked, so parallel processing is possible. Therefore,individual columns can be processed by different cores.



Figure 18: Performance

Figure 19: COMBINE BUSINESS & TECHNOLOGY



Figure 20: CLASSIC EDW

Figure 21: SAP HANA Appliance



Figure 22: PLANNED - SAP HANA PLATFORM 2.0 +

Figure 23: How Does SAP HANA Compare to BWA?

SAP HANA database has components from various other software applications.For example:

Row Store and SQL Parser has some code from P&time database

Column Store has code from BWA Trex Engine

Persistence Layer (Data and log volumes) has code from MAX DB

Rapid Deployment Solution allow you to implement a predefined andpreconditioned content on several different functional or technical perimeter. Theypermits to respond quickly to expectations through SAP delivered content.



Figure 24: Rapid Deployment Solutions

Hint: Additional use cases can be find on http://www.saphana.com.



Lesson Summary

You should now be able to:





Lesson:

18

SAP HANA ScenariosLesson Duration: 30 Minutes

Lesson OverviewThis lesson discusses about the different system configuration and possiblelandscape deployment scenarios.




None

Business ExampleA migration from BW to BW powered by SAP HANA needs careful planningand adherence technical requirements. A side-car scenario could be a first stepto answer to urgent and important business need. Then, once the BW migrationis effective, the side-car perimeter could be integrate to a schema of the SAPHANA Database used with BW.

CO-PA accelerator is an example of a side-car scenario. SAP HANA is used as asecondary database where data is replicated in real-time. Information and resultscould be consumed on an SAP Business Objects platform or directly in SAP ECC.


HA100 Lesson: SAP HANA Scenarios

Applications on SAP HANA Scenarios

Figure 25: HANA Innovation Scenarios Overview

Figure 26: SAP In-Memory Strategy



Figure 27: Application Server ABAP Based Scenarios - HANA as PrimaryDatabase (for AS ABAP)

Example: CO-PA Accelerator, Cash Forecast Accelerator

Figure 28: Non Application Server ABAP Scenarios - Data Marts with SAPHANA



Figure 29: SAP HANA Scenarios: Agile Data Marts

Data Warehouse environments are typically in-flexible against change. Customershave reported that there may be only two or four slots during a year, where modelsare allowed to be changed.

Businesses however are exposed to constant change. Sales regions change,product bundling may change, and cost centers are subject to almost constantchange. Sometimes it may be interesting to simulate these changes before theytake place. In these cases it is helpful to have an environment in which modelsmay be adapted easily without impacting the data models in production.

It may as well be interesting for business to load external data and combine it withinternal data sources. These may be benchmarking scenarios in which internal data(like sales data) is benchmarked against market indices obtained from externalagencies. Such data is typically not loaded into the central data warehouse, butrather gets used by analysts or managers in local environments.

SAP HANA provides a kind of sandbox environment for rapid prototyping ofnew models.



Figure 30: Example for Agile Data Marts

Figure 31: SAP HANA Scenarios: Operational Data Marts



Figure 32: Example for Operational Data Marts

Why would you want an operational data mart?

Most of the technologies currently used for operational reporting are notreally suitable for the task at hand. Classic DWH environments are complexand may require significant effort to model operational data marts.

If operational reports hit the database directly, which run the core businessapplications, reduced performance may be the experience for all peopleworking on the system. This performance hit is caused by the heavyworkload from joins on many small tables, like it is the standard in highlynormalized data models.

SAP HANA based operational data marts take the workload of such reportsaway from the main database. The replication guarantees that the data inmemory reflects on the last transactions which took place. And finally, thein memory computing provides very fast results even on high volumes ofdetailed data, still providing the option to touch on every detail which iscontained in the data.

SAP HANA can provide real time insights into what is going on in business.



Figure 33: SAP BW on HANA

BW on HANA was delivered with SPS04 in 2012.

Before database migration to HANA DB the BW application has to beupdated to 7.31.

The system usage is the same like BW 7.31 on non SAP databases.



SAP HANA Database Scenarios

Figure 34: SAP HANA unified data platform

Figure 35: SAP HANA Scenarios: Transformation scenario / SAP HANAas platform



Lesson Summary





HA100 Lesson: Rapid Deployment Solutions RDS

Lesson:

27

Rapid Deployment Solutions RDSLesson Duration: 15 Minutes

Lesson OverviewIn this lesson you will learn about what an RDS means and how you can use it.




None

Business ExampleYou want to quickly gain business value from your SAP HANA deployment byimplementing a Rapid Deployment Solution.

Rapid Deployment Solutions to meet specific businessneeds

Figure 36: SAP and a Global Partner Ecosystem Offer Rapid DeploymentSolutions to Meet Specific Business Needs.



SAP Software and SAP Predefined services combined with pre-configuredcontent and enablement content

With SAP Software, SAP Rapid Deployment solutions provide aready-to-consume combination of SAP Predefined services, pre-configuredcontent, and enablement content to accelerate the implementation and lower risk.Implementation is supported by standardized methodology and best practices,honed over decades. An optimized mix of global resources, remote support, andonsite consulting give you access to experts who can help you implement yoursolution on time and on budget.

Each of these solutions include educational material and training scripts for thefunctionality that matter most users start right away, without the delays associatedwith customized training. SAP Rapid Deployment solutions bring it all togetherpreconfigured software, fixed-scope implementation services, and the materialsyou need for a successful implementation... all at a predictable price, effectivelyeliminating cost overruns and project delays.

With these solutions, you receive the best of traditional and subscription licensingmodels, so you will know the cost and scope of your solution up front. Thesecomplete solutions enable the flexibility to accommodate future growth.

Because SAP Consulting uses preconfigured content, you as a business get whatyou need to run your business out of the box, delivered quickly. This preconfiguredcontent is value adding because it gives you powerful functionality based on theleading SAP ERP rapid-deployment solution for operational reporting with SAPHANA. SAP consultants only install what you need so that you can start fasterwith whats more important and expand as you need later. And the biggest benefitto our customers is that SAP Consulting can provide seamless access to SAPERP back office information.

The preconfigured content allows the project to be quick and lean because ofthe clearly defined scope, the knowledge transfer to users and the fast-trackmethodology. Finally, the flexible software pricing and fixed priced, low costservices, ensures that your SAP ERP rapid-deployment solution for operationalreporting with SAP HANA project will be cost effective, both monetarily as wellas in terms of Business and IT resources.



Figure 37: SAP HANA - Time Becomes Your Competitive Advantage

Time becomes your competitive advantage

Analyze information in real-time at unprecedented speeds on large volumesof non-aggregated data

Create flexible analytic models based on real-time and historic business data

Foundation for new category of applications

Minimizes data duplication



Figure 38: To be so fast like a cheetah you have to know how is the shortestway to your prey (the data) . And sometimes is it not quite easy. Like thefollowing example shows.

Figure 39: The new quite faster model



SAP ERP rapid-deployment solution for accelerated finance and controlling withSAP HANA is a combination of software with the rapid deployment solutionconsulting deliverable to produce the overall solution:

There are the four individual accelerators:

Financial Accounting Accelerator

Controlling Accelerator

Material Ledger Accelerator

Production Cost Analysis

There is also specific content delivered, for example:

Implementation content like configuration guide

Service content like project plan, consultant guide, or kick off presentation

Enablement content like customer facing material

The service has:

Fixed-scope and fixed-price services for the individual implementationscenarios

The Service Delivery can be performed by SAP or qualified partner.

Figure 40: SAP ERP Rapid-Deployment Solution for Operational Reportingwith SAP HANA Implementation Content

To give our customers as much flexibility as possible we have redesigned ourservice package by creating a modular offering. With the base package of thisrapid deployment solution you can choose up to 5 reports to be implemented. Ifyou need additional reports you can add as many as needed.



The SAP HANA business content for Sales and Distribution (SD) enablessales managers and sales representatives to check basic key figures for sales inreal-time. Whereas sales managers use sales analytics to get instant overviewinformation regarding the various performance indicators for their sales teams, thesales representatives focus on detailed checks of the results of their sales activities.

Figure 41: Flexible Reporting

Figure 42: Information about RDS Packages



Figure 43: The Way to get an RDS (1/4)




Figure 47: Service Overview - Deploy (1/2)

You will quickly generate a meticulous project plan, including a detailedbreakdown of activities, deliverables, and timelines. When should you schedulethe kickoff workshop and how much later should you plan scoping andrefinement? What about user acceptance testing? End-user training? Thesesolutions include the content to take the guesswork out of scheduling, substitutingtransparency and predictability that inspire key stakeholders to get on board andput their support behind your project.

Figure 48: Service Overview - Deploy (2/2)



Lesson Summary





HA100 Unit Summary

Unit SummaryYou should now be able to:








Unit Summary HA100


Unit 239 SAP HANA Studio

Unit OverviewThis unit provides an overview to using SAP HANA Studio.


Understand the structure of SAP HANA Studio

Understand how to configure Perspectives

Understand how to create a Delivery Unit and a Package

Unit ContentsLesson: SAP HANA Studio .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Procedure: Exercise 1: Look and Feel .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50


Unit 2: SAP HANA Studio HA100

Lesson:

40

SAP HANA StudioLesson Duration: 15 Minutes

Lesson OverviewIntroduction to the SAP HANA graphical user interface SAP HANA Studio.





If a participant has used SAP Business Objects Information Design Tool they mayhave had exposure to Eclipse previously.

Business ExampleYou are a consultant at a client site and need to launch SAP HANA Studio forthe first time.

You need to add the customers SAP HANA instance to your Studio installationso that you can work on the server and create a new Delivery Unit and Packagefor your Information Models.

Figure 49: SAP HANA Studio


HA100 Lesson: SAP HANA Studio

The SAP HANA Studio is delivered in the SAP HANA Appliance and providesan environment for administration, modeling, development and data provisioning.It can be installed on a local client PC.

SAP HANA studio is a Java based application that runs on the Eclipse platform(More information: http://www.eclipse.org).

When you start the SAP HANA studio for the first time, you can decide onseveral perspectives. Perspectives are predefined UI-layouts or views for severalapplication uses.

TheModeler Perspective is used by Data Architects to create Information Models.

The Administration Console is used by SAP HANA administrators toadministrate and monitor the engine.

The Documentation Overview links to the current available documentation.

Additionally, you also have perspectives for Development (HANA Applications),Java Development and Lifecycle Management

Figure 50: Look & Feel - Administration View

The Administration Perspective is used to administer and monitor SAP HANAinstances.

When you start SAP HANA Studio for the first time, there will be no connectionto a SAP HANA system maintained yet.

Note: It is possible to integrate several systems into one Studio.

You can select a Cheat Sheet view via Window Show view Other.



Help Cheat Sheets creates an additional view on the right side. Here you canchoose Adding system and Folders. Reading the Cheat Sheets can provide youinformation on how to create a new folder or add a new system into the navigatorview.

To integrate a SAP HANA system into the studio you need to know the serverwhere the engine is running and the instance number. You need to know auser/password combination to get a connection to the instance.

You can import (File import SAP HANA Studio Landscape) a systemlandscape which has been exported before from another or the same studio.

Note: To get the imported landscape working you need to insert thepasswords for all connections again. This can be done by right clicking onthe instance, and amending the password in Database Logon User

Figure 51: Look & Feel - Navigator View - Default Catalog

On the left side you will find the navigator view. Here all the systems which havebeen registered (manual, or via import) are listed.We will take a closer look to the tree structure each system has.



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

Note: During metadata import one defines which schema to hold createdtables. Different schemas can be useful for grouping tables into categoriesthat have meaning to users. This simplifies the process of identifyingwhich tables to use when defining Information Models. One model canincorporate tables from multiple schemas. The schemas do not limit yourmodeling capabilities.

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

The physical tables are the only storage area for data within SAP HANA. All theinformation models that will be created in the modeler will result in databaseviews. As such, SAP HANA does not persist redundant data for each model anddoes not create materialized aggregates.

Figure 52: System Monitor

There is an integrated System Monitor which gives you an administration viewabout the system landscape.

When you use the System Monitor button all systems which are listed in thenavigator tree are listed by default in the system monitor overview. You get themost important information about your systems. Which information is shown canbe configured by right clicking in the System Monitor view selecting ConfigureTable

It is also possible to configure which systems will be shown in system overviewby right clicking and selecting System Filter.



Figure 53: Look & Feel - Pre-Delivered Administration Console

The Administration console is pre-delivered by SAP.

You can access the administration console by

Selecting the Administration icon in the top right corner

Double click on the system in the System Monitor

Double click on the system in the Navigator view

In the administration console you are administrating HANA instances:

Starting and stopping the instance

Backup/recovery of the instance

Monitor the system

Configure the engine instance

Doing the problem analysis



Figure 54: Look & Feel - Perspectives are Built up Based on Views

When you want to create data models in HANA you need to switch to the modelerperspective in the Studio.

With Window Open Perspective Modeler you can switch to the QuickLaunch of the Information Modeler.

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

The SAP HANA Studio offers other perspectives for debugging, resource, teamsynchronizing and more.



Figure 55: Modeler

Above is the modeling section of the SAP HANA Studio.

Note: The Quick launch of the modeler is open by default for the firstinstance in the navigation tree.

If you want to change to another system, click on Select System.

In the center of the screen you see a quick launch tab that allows the user toquickly jump to various sections including tools to:

Create new Information Models

Import and export source schemas, models, data

Configure the server

Access SAP HANA documentationOn the left of the screen you see the navigation tree. Note that there are twomain sections in the navigation tree. The Default Catalog node navigates tothe physical tables, views, etc. The Content node navigates to AttributeViews, Analytic Views, Calculation Views, Analytic Priviliges, Proceduresand Decision Tables.



Figure 56: Navigator View - Models

The Content node displays the data from a data modeling perspective.

Here the user will create:

Attribute Views

Analytic Views

Calculation Views

Analytic Privileges

Procedures

Decision Tables



Figure 57: Look & Feel - Perspectives are Built up Based on Views

Note:

Views are the basic screen elements. A collection of displayedviews combined with their placement within the screen builds aperspective.

Each view can be moved around via drag & drop.



Figure 58: Look & Feel - Tips & Tricks

Note: Reset your perspectives will restore the screen to the default layout.



50Exercise 1: Look and FeelUse

Note: You can fill out the details below, as given by the instructor, and usethese for all exercises during this course:

Remote Desktop Alias

Remote Desktop Username

Remote Desktop Password

SAP HANA Database Host

SAP HANA Database Instance

SAP HANA Database Username

SAP HANA Database Password

SAP BusinessObjects Server

SAP BusinessObjects Username

SAP BusinessObjects Password

This section includes an exercise on look and feel of SAP HANA Studio.In this exercise you will log on to the WTS server, and get familiar withnavigating in SAP HANA Studio. You will complete the exercise bycreating your own Information Package.

Procedure

1. Logon to the WTS landscape:

Go to Start-Menu

Choose Common-Training

2. Remote Desktop into Server

Create a remote desktop connection to another desktop (connectioninformation will be given by the instructor)

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

Use the path: Start Menu All Programs Accessories.

Continued on next page



Figure 59: Remote Desktop into Server

3. In the next screen you have to choose one of the available remote desktopservers.

Note: Type the name of the Server (specified by your instructor).

Click Connect.

Figure 60: Remote Desktop Connection

4. In the Remote Desktop Connection dialog box enter user name and passwordgiven by the instructor.




Figure 61: Logon

5. Now you are on the right desktop and can start the SAP HANA Studio bygoing to Start Programs SAP HANA SAP HANA Studio.

6. Open Administration Console

Figure 62: Overview Screen

7. Register a new System. Right Click Add System... within the Navigatorview.

Enter the Hostname, Instance Number and Description and Locale asgiven by the instructor.

Do not use HTTPS.

Click Next.




Figure 63: Register a New System

8. Enter your credentials as given by your instructor.

Figure 64: Connection Properties




9. Change your initial password

Minimum 8 characters

Must contain capital and small letters

Must contain numbers

Example: Abcd1234

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

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

Figure 65: Change Initial Password

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

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




Figure 66: Studio Preferences

11. Next, expand the Modeler node in the tree and click on Default ModelParameters.

Note: HANA Studio supports modeling using multiple clients inSAP source data. You will now set your default client.

Now ensure that the client is dynamic.

Press the button Apply.

Figure 67: Default Model Parameters




12. The overall perspective setup can be maintained via the Window menu ontop.

You have access via Window Open Perspective Other to allpre-delivered and saved perspectives.

For the next step, open the Administrator Console Perspective

Figure 68: Administration Console

13. To easily switch between different perspectives you can click on the toolbaron top on the corresponding button.

Each open perspective will be shown here.

Figure 69: Open Perspectives




14. To customize a perspective choose the Window menu CustomizePerspective.

Figure 70: Customize Perspective (1)

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

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

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

Figure 71: Customize Perspective (2)

16. To open a new view just go to the window menu again and drop down menuShow View Other...




Figure 72: Show View (1)

17. In the Show View dialog box you can choose which view you want to addto your perspective.

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

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

Figure 73: Show View (2)




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

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

Note that there are three main sections in the navigation tree:

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

The Content node navigates to Attribute Views, Analytic Views,Calculation Views, Procedures, Analytical Privileges andDecision Tables.

The Security node navigates to User and Role settings.

Note: The Content node is only visible inside the Modelerperspective.

Figure 74: Navigator Tree

19. The Catalog contains all Database schemas which will be automaticallycreated when a user is created.

Each Schema contains a folder for Column Views, Procedures, Tablesand Views.




Figure 75: The Catalog

20. Content folder contains the Information Model packages.

Package contains a folder for Attribute Views, Analytic Views,Calculation Views, Analytic Privileges, Procedures and DecisionTables.

Note: If you do not see folders for all the types of InformationModels, this may be because none are created.




Figure 76: Content Folder

21. Security folder contains Security settings for Users and Roles.

Figure 77: Security Folder

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




Figure 78: Customize Navigation Tree (1)

23. Using this functionality you can decide what you want to see as folders inthe Navigator.

Figure 79: Customize Navigator Tree (2)

24. Should too much customization have left you lost there is an easy wayto RESET the perspective!

Reset the Perspective




Figure 80: Reset Perspective

25. The Administration Console reflects the pre-delivered AdministrationPerspective.

In this perspective, you can administrate the SAP HANA Instances,depending on your user rights.

Figure 81: Pre-Delivered Administration Perspective

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

First Open the Modeler perspective.

From the Help menu Select Quick Launch.




Figure 82: Delivery Unit (1)

27. Select Delivery Units from the Setup section.


28. Click on Create.





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

The other entries can be left blank.


30. Verify that your Delivery unit is created.





31. Create a new package. In the Navigator Select the Content folder RightClick New Package.

Note: Make sure you are in the Modeler Perspective

Figure 87: New Package (1)

32. Enter studentXX for the package name and description.

Ensure to select your Delivery Unit you created earlier.

Accept the original language proposed and select your STUDENTXX nameas Person Responsible.

Note: If your newly created delivery unit it not displayed, you mayneed to close and reopen the SAP HANA Studio.





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




Lesson Summary






HA100 Unit Summary






Unit Summary HA100


Unit 371 Architecture

Unit OverviewThis unit provides an overview to the architecture behind SAP HANA.


Understand the architecture of SAP HANA

Explain the necessity and uses of the Persistence Layer of SAP HANA 1.0

Concept of Backup & Recovery

Unit ContentsLesson: Architecture.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Procedure: Exercise 2: Architecture .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Lesson: Persistence Layer .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Lesson: Backup & Recovery .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93


Unit 3: Architecture HA100

Lesson:

72

ArchitectureLesson Duration: 40 Minutes

Lesson OverviewThis lesson introduces a description of SAP HANA Database architecture andcomponents.



None

Business ExampleA customer need to transform his landscape to improve his global performanceand lessen his IT administration task. He needs to turn to SAP HANA technologyand learn the new architecture of SAP HANA Appliance.

Figure 90: System Architecture


HA100 Lesson: Architecture

Figure 91: Index Server Architecture

At the top is the Connection and Session Management which creates and managessessions and connections for the database clients such as SAP BusinessObjectsReporting tools or applications.

The Transaction Manager is the component that coordinates transactions, controlstransactional isolation and keeps track of running and closed transactions.

The client requests are analyzed and executed by the set of componentssummarized as Request Processing and Execution Control. Once a sessionis established, database clients typically use SQL statements to communicatewith Request Processing and Execution Control. For analytical applications themultidimensional query language MDX is supported in addition.

Incoming SQL requests are received by the SQL Processor. Data manipulationstatements are executed by the SQL Processor itself. Other types of requests aredelegated to other components.

For example, Data definition statements, such as definitions of relational tables,columns, views, indexes and Procedures are dispatched to the Metadata Manager.



Figure 92: Network Connectivity

Planning commands are routed to the Planning Engine that allows financialplanning applications to execute basic planning operations in the database layer.

The SAP HANA database offers programming capabilities for runningapplication-specific calculations inside the database system. The SAP HANAdatabase has its own programming languages. SQLScript is used to writedatabase stored procedures. Procedure calls are forwarded to the Stored Procedureprocessor.

Incoming MDX requests are processed by the MDX engine and also forwarded tothe Calc Engine.

Features such as SQLScript, MDX and planning operations are implementedusing a common infrastructure called Calc Engine.



Figure 93: SAP HANA High Availability - High Availability - Disaster Tolerance

High Availability per Data Center Scale-Out with Standby Available today HWpartners: Fujitsu, HP, IBM, more to come.

High Availability across Data Centers Disaster Tolerance Planned for GeneralAvailability of BW on HANAHW partners, planned: Fujitsu, HP, IBM, more to come.

Solutions depend on HW partner technology.

Figure 94: Scale Out - High Availability



Figure 95: Scale Out - SAP HANA Database Landscape

High-Availability enables the failover of a node within one distributed SAP HANAappliance. Failover uses a cold standby node and gets triggered automatically.Landscape Up to 3 master name-servers can be defined. During startup one servergets elected as active master. The active master assigns a volume to each startingindex server or no volume in case of standby servers.

Master name-server failure

In case of a master name-server failure, another of the remaining name-serverswill become active master.

Index-server failure

The master name-server detects an index-server failure and executes the failover.During the failover the master name-server assigns the volume of the failedindex-server to the standby server.



Figure 96: SAP HANA High Availability - Node Failover (Standby)

The General Parallel File System (GPFS) is a shared-disk clustered file systemdeveloped by IBM.

Figure 97: HANA Disaster Tolerance - Cluster Across Data Centers

The mirroring is offered on the storage system level. It will be offered togetherwith the appliance as an special offering by our partners. The hardware partnerwill define how this concept is finally realized with his operation possibilities.



Performance impact is to be expected on data changing operations as soon asthe synchronous mirroring is activated. The impact depends strongly on a lotof external factors like distance, connection between data centers, etc. Thesynchronous writing of the log with the concluding COMMITs is the crucial parthere.

In case of an emergency the primary data center is not available any more and aprocess for the take-over must be initiated. So far a lot of customers wished to havea manual process here, but an automated process is also able to be implemented.This take-over process then would end the mirroring officially, will mount the disksto the already installed HANA software and instances, and start up the secondarydatabase side of the cluster. If the hostnames and instance names on both sides ofthe cluster are identical, no further steps with hdbrename are necessary.

It would be possible to run a development and/or QA instance of the three tierinstallation on this secondary cluster hardware, simply to utilize it until thetake-over is executed. The take-over then would stop these dev. and/or QAinstances and mount the production disks to the hosts. It would require anadditional set of disks for the dev. and QA instance.

So far no hot standby via log shipping is available or even log shipping byrecovering of log backups on a standby host. This needs some changes in theengines of HANA database which needs time to be realized. Both solutions are onthe agenda of HANAs future.

Figure 98: Data Replication Methods

There are different technologies how to load data into SAP HANA (different dataprovisioning scenarios) which are covered in the Unit Data Provisioning.



The methods are:

SAP Landscape Transformation

SAP Data Services

Flat file upload

Direct Extractor Connection (DXC)

Figure 99: SAP HANA System Landscape

More technical, the following components will be needed to be installed next toSAP HANA, depending on the actual scenario.

These technologies are reflected in the different editions of SAP HANA dependingon the needs of the customer:



Figure 100: Bill of material / SAP HANA appliance software components

Figure 101: Bill of material / SAP HANA peripheral components



81Exercise 2: ArchitectureUse

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

How to see whether a table is in row store or in column store

How to see what indexes are defined for a table

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

Procedure

1. Log on to the SAP HANA Studio with your user.

For this exercise you can use either the Administration perspective orthe Modeler perspective.

So lets start looking for table MARA.

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

Figure 102: Catalog

3. Expand the node for the TRAINING-Schema and then expand the Tablesfolder within that schema.




Figure 103: Tables (1)

4. This shows the tables in that schema.

Figure 104: Tables (2)

5. Right-click the Tables folder and select Filter from the context menu. Thisopens a dialog box.

Figure 105: Filter




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

Note: You are opening the list of tables within schemaTRAINING, so we are searching for tables within theTRAINING schema.

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

Enter MARA in the input field and confirm with OK.

Figure 106: Table Name

7. This will filter the list of tables with names starting with MARA.

Figure 107: List Filter

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




Figure 108: List of Tables

9. The context menu for a table offers several options. We are interested in thetable metadata which we can reach by Opening the table Definition (or bydouble-clicking the table). Other options which are not used here include:

Open Data Preview: Explore the table contents.

Open Content: simple display of the table contents.

Figure 109: Table Metadata

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

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

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

MARA as you can see is using column-based storage.




Figure 110: Table Definition

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

For MARA, these are the client and the material number, MANDT andMATNR.

Figure 111: Key Fields

12. Lets now look at the table P_QUERYPLANS from the SYS schema. Youshould be able to verify that:

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

IDX_P_QUERY_PLANS which is an index with indexed columnUSER_NAME sorted in ascending order.




Figure 112: Table P_QUERYPLANS



Lesson Summary





Lesson:

88

Persistence LayerLesson Duration: 25 Minutes

Lesson OverviewThis lesson explains components composing the persistence storage layer andpurposes of each components in case of power failure.



Business ExampleIn case of power failure and restart of the system, we need to know if the systemis able to recover data or not.

Figure 113: Persistence - In-Memory Data Is Regularly Saved to Disk

Data pages and before images (Undo log pages) are written on the data volumes.


HA100 Lesson: Persistence Layer

After images (redo log pages) are written on the log volumes.

Figure 114: SAP HANA Persistence: Shadow Memory Concept - Details

The savepoint consists of 3 phases:

Phase #1:

All modified pages are determined that are not yet written to disk. Thesavepoint coordinator triggers writing of these pages.

Phase #2:

The write operations for phase 3 are prepared.

A consistent change lock is acquired no write operations are allowed.

All pages are determined that were modified during phase 1 and writtento a temporary buffer.

List of open transactions is retrieved.

Row store information for uncommitted changes made during phase 1 iswritten to disk.

Current log position is determined (log position from which logs must beread during restart).

Change lock is released.



Phase #3:

All data is written to disk. Changes are allowed again during this phase.

Temporary buffers created in phase 2.

List of open transactions

Row store check point is invoke

Log queue is flushed up to the savepoint log position

Restart record is written (containing e.g. the savepoint log position)

Shadow paging is used to undo changes that were persisted since the lastsavepoint. With the shadow page concept, physical disk pages written by the lastsavepoint are not overwritten until the next savepoint is successfully completed.Instead, new physical pages are used to persist changed logical pages. Until thenext savepoint is complete, two physical pages may exist for one logical page: Theshadow page, which still contains the version of the last savepoint, and the currentphysical page which contains the changes written to disk after the last savepoint.

After restart, the system is restored from the savepoint versions of the data pages.This way all data changes written since the last savepoint are automatically rolledback. After the savepoint is restored, the log is replayed to restore the most recentcommitted state.

Figure 115: Persistence Layer in SAP HANA Database - System Restart


HA100 Lesson: Persistence Layer

Actions during system restart

Last savepoint must be reloaded plus:

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

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

Complete content of row store is loaded into memory

Column store tables may be marked for preload or not

Only tables marked for preload are loaded into memory during startup

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



Lesson Summary




HA100 Lesson: Backup & Recovery

Lesson:

92

Backup & RecoveryLesson Duration: 30 Minutes

Lesson OverviewThis lesson explains the concept of the backup and recover strategy. We can alsouse backups and recoveries processes to copy SAP HANA Database.



The procedure and all parameters to implement and maintain backups andrecoveries are detailed in HA200. HA100 presents only an overview.

Business ExampleIn case if we need to refresh an environment with another one, like refreshingtesting environment with productive environment, we can use backup andrecovery procedure to do so. Or if a disk failure appends, we need to know whichdata will be recovered.

Backup & RecoveryDatabase copy:



Figure 116: SAP HANA Backup/Recovery - Database Copy Using Backups(Source Database Online)

Figure 117: Database copy from multi-node to single-node system



Figure 118: Database copy : Steps to perform and limitations

FAQ: SAP-HANA-Database - Backup and Recovery

Note: 1642148

Figure 119: Backup & Recovery - Save to External Backup Destinations



Backup:

User starts backup via SAP HANA studio

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

Commits for all transactions on hold

Master name and index servers create snapshots of their persistent storage

Commits allowed again

Master name server and index servers write snapshots to backup destinations

SAP HANA studio monitors progress

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

/usr/sap//SYS/global/hdb/custom/config

/usr/sap//HDB/ (without sub-directories!)

Figure 120: Backup & Recovery - Recovery Scenario - Disk Failure (DataVolume)

Recovery:

In general there are three data sources involved in the recovery process:

Data backups stored in the file system

Log Backups stored in the file system

Online logs



Figure 121: 3 Recovery Scenarios

Figure 122: Backup & Recovery: Feature Overview



Lesson Summary




HA100 Unit Summary






Unit Summary HA100


Unit 499 Data Provisioning

This unit is a high level overview of data provisioning for SAP HANA, thereforedo not go into details, as they are covered in HA200 and HA300 courses. Thereare no exercises in this unit but you can do demonstrations which are includedin the Instructor guide.

Unit OverviewThere are several ways of loading data into SAP HANA. This unit describes thedifferent methods.


Understand the capabilities and positioning of the Flat file data loadfunctionality

Load data from Flat Files into the SAP HANA Database

The main features of the SAP Data Services solution for SAP HANA

Describe the process of loading data from ECC to SAP HANA using theETL method

Understand the architectural foundation of LT Replicator and its technicalpre-requisites

Configure LT Replicator for connectivity to the source SAP ERP systemand the target SAP HANA Database

Configure data provisioning in SAP HANA Studio and trigger an initialload and/or replication

Explain an additional data acquisition technique for working with data fromSAP Business Suite systems that has been added to the existing techniquesfor HANA data acquisition

Unit ContentsLesson: Uploading Data from Flat Files .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103


Unit 4: Data Provisioning HA100

Lesson: SAP Data Services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Lesson: SAP LT Replication Server .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120Lesson: SAP Direct Extractor Connection (DXC) ... . . . . . . . . . . . . . . . . . . . . . . .131


HA100 Lesson: Uploading Data from Flat Files

Lesson:

100

Uploading Data from Flat FilesLesson Duration: 15 Minutes

Lesson OverviewOne of the options available for data provisioning is to simply upload data fromflatfiles. The lesson shows you the steps required to upload your own data from acsv file.




You can use the file VKORG.txt in the resources perspective to do thedemonstration

Business ExampleYou want to upload Sales Organisation texts from a flat file to an SAP HANAtable, so you can use the data in modeling afterwards



Figure 123: Data Replication - Definition

There are different technologies for loading data into SAP HANA (differentreplication scenarios).

Figure 124: Data Replication Methods

There are different technologies how to load data into SAP HANA (differentreplication scenarios).

Figure 125: Features of uploading data from Flat Files



Figure 126: Process Flow: Uploading Data from Flat Files

Figure 127: Select Import Source



Figure 128: Select Target System

Figure 129: Select File for Upload



Figure 130: Select Target Table

Figure 131: Manage Table Definition and Data Mapping (1)



Figure 132: Manage Table Definition and Data Mapping (2)

Figure 133: Check Target Table



Figure 134: Check Target Table



Lesson Summary





HA100 Lesson: SAP Data Services

Lesson:

107

SAP Data ServicesLesson Duration: 30 Minutes

Lesson OverviewSAP Data Services 4 enables you to integrate disparate data sources to delivermore timely and accurate data that end users in an organization can trust. Thislesson will look at the fundamentals of how to provision data from SAP DataServices into SAP HANA.


The main features of the SAP Data Services solution for SAP HANA

Describe the process of loading data from ECC to SAP HANA using theETL method

Although SAP Data Services is a big topic, this lesson will give a high leveloverview in the context of SAP HANA only. For detailed training on SAP DataServices please refer the delegates to the course BODS10. There are no exercisesin this Unit but the instructor should at least do the demonstration from theinstructor guide.

Business ExampleYou are working in an organization where data is stored in various disparatedatabases like Oracle, DB2 and other legacy systems. You are asked to recommendthe best application for consolidating and replicating data into SAP HANA fromSAP and Non SAP sources using the ETL method. Therefore, you need tounderstand the benefits of using SAP Data Services over other methods.



Figure 135: Data Replication - SAP Data Services

Figure 136: Data Landscape

Most likely you face similar data challenges limiting your ability to know yourbusiness.

Siloed With data scattered across your organization in different ERP, database,or homegrown systems; you may likely find different versions of the truth limitingyour ability to gain a complete view of the business.

Inaccurate Have you ever received a promotion mail addressed to someonein your mailbox? Consider the wasted marketing costs (in printed materialand postage) for a company that leverages customer promotions as a source ofrevenue generation. Data is inherently inconsistent because things change and


HA100 Lesson: SAP Data Services

your business requirements continue to evolve to meet your goals. As a result,you need ongoing maintenance of your data quality by both the business andIT stakeholders. Common issues like incorrect customer names, addresses, andproduct names only add to the challenge for organizations to resolve before theycan leverage their corporate data as an enterprise asset.

Inconsistent Definitions of common business entities like customers, products,supplier, material names and codes vary from system to system creatinginconsistencies that data access alone can not address. You need a better wayto reconcile this.

Incomplete Another common data challenge is incompleteness. A customerrecord may be missing a postal code or country code and would be unusable unlessit is appended with the correct data.

Inaccessible Connectivity will allow you to get access to the data in yourenterprise systems but often times, this is only the beginning. Making inaccuratedata accessible does not necessarily help you leverage that information for abusiness goal. Sometimes the data is in a format that is unstructured like a freeform text coming from a CRM call log. The challenge lies in how to unlockinsights and the potential from all of your data sources.

Figure 137: Challenge: Disparate - Information Management Tools

Yet, the main challenge faced by organizations is the explosion of tools managingthe explosion of data sources. In this scenario, we see a typical IT environmentwhere multiple information management tools from multiple vendors increasethe complexity of managing information consistently and effectively across theenterprise. Each tool has its own metadata repository, development environment,administrative environment, runtime architecture requirements that you need tosupport and maintain making the overhead of keeping up with all of these tools



extremely costly from a time and resource perspective. Many of these tools arecommonly used in an end-to-end solution supporting the requirements from dataextraction, transformation, cleansing, matching, and metadata management.

For example, data integration and data quality have a deep symbiosis that needscoordination. Data integration ferrets out data quality issues, whether problemsto be fixed or opportunities to be leveraged for improvement. Likewise, dataquality reaches more data and systems that need improvement when it employsdata integrations numerous interfaces.

Figure 138: Data Services Is Your One-Stop Solution - Data Integration, DataQuality, Data Profiling, Metadata Management, and Text Analytics

SAP Data Services is the first and only, all-in-one solution for data integration(ETL), data quality management, information stewardship (data profiling andmetadata management), and text analytics.

With Data Services, you have a one-stop shop solution for 5 core criticalinformation management capabilities (ETL, DQ, Profiling, Metadata Management,Text Analytics) that helps you:

Move and integrate enterprise data to and from almost any data source and targetwith market-leading extract, transform, and load (ETL) capabilities.

Improve data from any data domain (e.g. customer, product, supplier, material)with market-leading data quality management to

ha100-en-col98-fv-inst-a4.pdf

Documents