HA100_EN_Col09

(1)

HA100

SAP HANA Introduction

SAP HANA Date Training Center Instructors Education Website

Participant Handbook

Course Version: 09 Course Duration: 2 Day(s) Material Number: 50128319 An SAP course use it to learn, reference it for work

(2)

Copyright Copyright © SAP SE or an SAP affiliate company. All 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. Trademarks Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries. Apple, App Store, FaceTime, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, MultiTouch, ObjectiveC, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc. Bluetooth is a registered trademark of Bluetooth SIG Inc. Citrix, ICA, Program Neighborhood, MetaFrame now XenApp, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc. Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH. Edgar Online is a registered trademark of EDGAR Online Inc., an R.R. Donnelley & Sons Company. Facebook, the Facebook and F logo, FB, Face, Poke, Wall, and 32665 are trademarks of Facebook. Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik, and Android are trademarks or registered trademarks of Google Inc. HP is a registered trademark of the HewlettPackard Development Company L.P. HTML, XML, XHTML, and W3C are trademarks, registered trademarks, or claimed as generic terms by the Massachusetts Institute of Technology (MIT), European Research Consortium for Informatics and Mathematics (ERCIM), or Keio University. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation. Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation. INTERMEC is a registered trademark of Intermec Technologies Corporation. IOS is a registered trademark of Cisco Systems Inc. The Klout name and logos are trademarks of Klout Inc. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Motorola is a registered trademark of Motorola Trademark Holdings LLC. Mozilla and Firefox and their logos are registered trademarks of the Mozilla Foundation. g201516105457

(3)

Novell and SUSE Linux Enterprise Server are registered trademarks of Novell Inc. OpenText is a registered trademark of OpenText Corporation. Oracle and Java are registered trademarks of Oracle and its affiliates. QR Code is a registered trademark of Denso Wave Incorporated. RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry AppWorld are trademarks or registered trademarks of Research in Motion Limited. SAVO is a registered trademark of The Savo Group Ltd. The Skype name is a trademark of Skype or related entities. Twitter and Tweet are trademarks or registered trademarks of Twitter. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. WiFi is a registered trademark of WiFi Alliance. SAP, R/3, ABAP, BAPI, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, Sybase, Adaptive Server, Adaptive Server Enterprise, iAnywhere, Sybase 365, SQL Anywhere, Crossgate, B2B 360° and B2B 360° Services, m@gic EDDY, Ariba, the Ariba logo, Quadrem, bprocess, Ariba Discovery, SuccessFactors, Execution is the Difference, BizX Mobile Touchbase, It's time to love work again, SuccessFactors Jam and BadAss SaaS, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany or an SAP affiliate company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. Disclaimer These materials are subject to change without notice. These materials are provided by SAP SE and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. g201516105457

(4)

(5)

About This Handbook

This handbook is intended to complement the instructorled presentation of this course, and serve as a source of reference. It is not suitable for selfstudy.

Typographic Conventions

American English is the standard used in this handbook. The following typographic conventions are also used. Type Style Description Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for crossreferences to other documentation both internal and external. Example text Emphasized words or phrases in body text, titles of graphics, and tables EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

Example text

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text

Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.

<Example text>

v

(6)

About This Handbook HA100

Icons in Body Text

The 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 instructor's presentation.

vi

(7)

Course Overview

_...

ix

Course Goals

_...

ix Course Objectives

... x

Unit 1: Introduction and Positioning.

...1

Introduction to SAP HANA.

... 2

SAP HANA Scenarios.

...

35 Unit 2: SAP HANA Studio.

... 4

5 SAP HANA Studio

...

46

Unit 3: Architecture

... 7

7 Architecture.

...

78

Persistence Layer

_...

86

Unit 4: Modeling

...1

01 Introduction to the COPA Scenario

... 1

02 Introduction to the SAP HANA Modeler Perspective.

... 1

06 Levels of Modeling.

... 1

13

Unit 5: Data Provisioning

...2

05 Uploading Data from Flat Files

... 2

07 SAP BusinessObjects Data Services

... 2

22 SAP Landscape Transformation Replication Server

_... 2

33 SAP Direct Extractor Connection

... 2

40 SAP Replication Server

... 2

45

Smart Data Access

_... 2

51 Smart Data Integration and Smart Data Quality

_... 2

64

Smart Data Streaming

_... 2

72

Unit 6: Reporting

...2

87 SAP HANA Database Connectivity Options

... 2

88

SAP BI

_... 2

92 SAP BusinessObjects Analysis for Office

_... 3

01

SAP BusinessObjects Design Studio

_... 3

vii

(8)

Contents HA100

SAP Lumira.

... 3

19

Appendix 1: Useful Resources about SAP HANA .

...3

37

(9)

Course Overview

SAP HANA enables business departments to analyze business as it happens. Individuals can create flexible analytical models based on realtime data originating from business applications. ERP operational analytics is further enhanced with SAP HANA interfaces to BI client reporting tools, such as SAP BusinessObjects Explorer, SAP Crystal Reports, SAP BusinessObjects Dashboards, and SAP BusinessObjects Web Intelligence. This twoday introductory course is for consultants, project team members and modelers who want to learn about this new technology. The course explains how to perform basic modeling and administrative tasks in the SAP HANA Studio. These tasks include data provisioning using several tools such as SAP Data Services or SAP Replication Server, and creating flexible analytic models based on realtime data originating from SAP ERP applications. In order to cover an end to end scenario, the participants will also learn how to connect to SAP HANA from SAP BusinessObjects BI 4 tools such as SAP BusinessObjects Explorer, SAP BusinessObjects Analysis, and SAP BusinessObjects Web Intelligence.

Target Audience

This course is intended for the following audiences: • Application consultants • Project team members

Course Prerequisites

Required Knowledge

• None

Recommended Knowledge

ix

(10)

Course Overview HA100

Course Goals

This 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 simple information models • Understand how data can be loaded into HANA • Get an overview of how to report on HANA using client tools

x

(11)

Unit 1

Introduction and Positioning

Unit Overview

This unit gives an overview of SAP HANA benefits, positioning, and deployment options.

Unit Objectives

After completing this unit, you will be able to: • Explain the common pain points in a system using a classic database • Explain how SAP HANA can handle the pain points and help to improve performance • Explain benefits of application development, spatial and text analysis • Explain the architecture of the main SAP HANA implementation scenarios

Unit Contents

Lesson: Introduction to SAP HANA ... 2

Lesson: SAP HANA Scenarios ...

35

1

(12)

Unit 1: Introduction and Positioning HA100

Lesson: Introduction to SAP HANA

Lesson Overview

This lesson explains why SAP HANA has been developed and how this new technology can help increasing business opportunities.

Lesson Objectives

After completing this lesson, you will be able to: • Explain the common pain points in a system using a classic database • Explain how SAP HANA can handle the pain points and help to improve performance • Explain benefits of application development, spatial and text analysis

Business Example

Today, a lot of companies need to deal with an amazing amount of data and are not able to report on them efficiently due to data volume. The purpose of SAP HANA is to enable easy storage and efficient processing of these data. In particular, SAP HANA combines inmemory data storage and columnar data storage, two modern and extremely powerful features.

Information Explosion

Figure 1: Reality #1: Information Explosion

2

(13)

HA100 Lesson: Introduction to SAP HANA The first challenge is the information explosion. Massive amounts of data is being created every year, and how fast your business reacts to it determines whether you succeed or fail. IDC, in its 2013 Top 10 predictions (released in November 2012) estimates that the “digital universe” will reach 4 ZB (1 zettabyte = 1 trillion gigabytes). On the horizon of 2020, IDC projects that the digital universe will reach 40 zettabytes of data, which is also 40 trillion gigabytes. It represents 50 times the volume of the digital universe in 2010. And a stack of DVD boxes containing all the digital universe data would be twice as high as the distance between Earth and Mars. kilobyte (kB) > megabyte (MB) > gigabyte (GB) > terabyte (TB) > petabyte (PB) > exabyte (EB) > zettabyte (ZB) > yottabyte (YB) To learn more about the IDC forecast on the digital universe in 2020, see: http://www.emc.com/collateral/analystreports/idcthedigitaluniversein2020.pdf In a Sloan Management survey in 2010, 60% of executives said their companies have more data than they know how to use effectively. With data doubling every 18 months, that percentage is going to keep growing. Figure 2: Reality #2: Consumerization of IT At the same time, the consumerization trend is driving up expectations as to what enterprise IT can help the business to do. People want instant access to information – in the moment – whether that is a moment of risk or a moment of opportunity. If the moment has passed and your business has not taken the right action, it has failed. People want instant answers. They want them to be right. They want them anywhere, any time. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

3

(14)

Unit 1: Introduction and Positioning HA100 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 is no practical way to instantly analyze everything that is going on relative to the business. IT can deliver some of the information. The most critical slice of information can be delivered in near real time. But it is not enough. Data is growing. Demand is increasing. We must find a way to deal with this – a way to process and analyze massive amounts of data in real time. Figure 4: The Daily Challenges of Data Volume and Complexity...

4

(15)

HA100 Lesson: Introduction to SAP HANA Figure 5: ... and the Main Drawbacks To resolve the difficult equation of data volume, speed, and flexibility, here comes SAP HANA. Using groundbreaking inmemory hardware and software, you can manage data at massive scale, analyze it at amazing speed, and give the business not only instant access to real time transactional information and analysis, but also more flexibility. Flexibility to analyze new types of data in different ways, without creating custom data warehouses and data marts. Even the flexibility to build new applications which were not possible before.

SAP HANA Value Proposition

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 2015 © SAP SE or an SAP affiliate company. All rights reserved.

5

(16)

Unit 1: Introduction and Positioning HA100 Here are some proof points: • Amazing speed. One of our pilot customers reduced the time it took to run a report from one hour to one second. That is 3600 times faster. Let's put that in perspective. SAP talks about helping you to “run better”, so lets use that as an example. When an average person runs, they move at about 7 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 done once by the astronauts on Apollo 10, on their return from the moon in 1969. • Amazing amounts of data. During testing for HANA we executed queries against 460 billion rows of data in less than one second. That is like being able to analyze every repair and service visit for every car on earth in the last 12 months, in one second. Or to process every address that everyone alive today has ever lived at, in one second. Or to calculate the amount of taxes paid by everyone on the planet, since 1950, in one second. • Amazing value. Having the ability to create new realtime processes and simplify your IT landscape has a big impact. According to a study by Oxford Economics, companies that implement realtime systems see an average 21% revenue growth, and a 19% reduction in IT cost.

6

(17)

HA100 Lesson: Introduction to SAP HANA Figure 7: Query Acceleration Example – Large Bank – 1 Month of Customer Information Why wait for data? • All customers want to see their current business data in realtime. Nobody wants to wait until data is uploaded into a data warehouse. Why wait for new systems? • Latest hardware and latest database technology already support realtime reporting on massive amount of data. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

7

(18)

Unit 1: Introduction and Positioning HA100 Figure 8: SAP Naming Update: SAP HANA SAP HANA • SAP HANA is a flexible, datasourceagnostic appliance, that enables customers to analyze large volumes of data from SAP and nonSAP systems in realtime, avoiding the need to materialize transformations. • SAP HANA appliance software is a hardware and software combination that integrates a number of SAP components, including the SAP HANA database and several data replication systems: SAP Landscape Transformation, SAP HANA Direct Extractor Connections (DXC), SAP Data Services or SAP Sybase Replication Server. • The SAP HANA database is a hybrid inmemory database that combines rowbased, columnbased, and objectbased database technology. It is optimized to exploit the parallel processing capabilities of modern multicore CPU architectures. With this architecture, SAP applications can benefit from current hardware technologies.

8

(19)

HA100 Lesson: Introduction to SAP HANA Figure 9: Improvements in Technology Historically, database systems were designed to perform well on computer systems with limited RAM. As a consequence, slow disk I/O was the main bottleneck in data throughput. The architecture of those systems was designed with a focus on optimizing disk access, for example by minimizing the number of disk blocks (or pages) to be read into main memory when processing a query. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

9

(20)

Unit 1: Introduction and Positioning HA100 Figure 10: SAP's Path to SAP HANA SAP HANA is the result of inmemory experiences within SAP applications, further software innovations in regards of database management systems as well as general hardware innovation in the market.

10

(21)

HA100 Lesson: Introduction to SAP HANA

SAP HANA Architecture

Figure 11: SAP HANA Architecture So what is SAP HANA exactly? First of all, SAP HANA is a database. But it is not just a database like many others in the market: SAP HANA provides a unique combination of hardware and software innovations which have a huge potential to optimize business applications running on SAP HANA. In the following, both dimensions –hardware and software optimizations– will be explained in more detail. 1. HARDWARE OPTIMIZATION 2015 © SAP SE or an SAP affiliate company. All rights reserved.

11

(22)

Unit 1: Introduction and Positioning HA100 Figure 12: Computer Architecture is Changing Computer architecture has changed in recent years. Now, multicore CPUs (multiple CPUs on one chip or in one package) are standard, and extremely fast communication between processor cores enables parallel processing. Main memory is no longer a limited resource: modern servers can have 2 TB of system memory, and this allows complete databases to be held in RAM. Currently, server processors have up to 64 cores... and 128core processors will soon be available. With the increasing number of cores, CPUs are able to process much more data per time interval. This shifts the performance bottleneck from disk I/O to the data transfer between CPU cache and main memory. In the next slides, you will understand the four main concepts of the SAP HANA database: • Column Store • Compression • Partitioning • Insert only on Delta

12

(23)

Row and Column Store

In addition to a classical rowbased data store, SAP HANA is able to store tables in its columnbased data store. It is important to understand the differences between these two methods, and why columnbased storage can highly increase certain types of data processing. The concept of column data storage has been used for quite some time. For example, the first version of SAP Sybase IQ, a columnbased relational database, was released in 1999. Historically, columnbased storage was mainly used for analytics and data warehousing, where aggregate functions play an important role. On the other hand, using column stores in Online Transaction Processing (OLTP) applications requires a balanced approach to insertion and indexing of column data, in order to minimize cache misses. The SAP HANA database allows the developer to specify whether a table is to be stored columnwise or rowwise. It is also possible to alter an existing columnbased table to rowbased, and vice versa. Figure 13: Software Optimization for Data Processing 2015 © SAP SE or an SAP affiliate company. All rights reserved.

13

(24)

Unit 1: Introduction and Positioning HA100 Conceptually, a database table is a twodimensional data structure with cells organized in rows and columns. Computer memory, however, is organized as a linear structure. To store a table in linear memory, two options exist: • A rowbased approach stores a table as a sequence of records, each of which contain the fields of one row. • In a columnbased table, the entries of a column are stored in contiguous memory locations. Figure 14: Key Facts: When to Use Row Store or Column Store? • Row Store If you want to report on all the columns of a table, then the row store is more suitable because reconstructing the complete row is one of the most expensive operation for a columnbased table. • Column Store If you to want to store in a table huge amounts of data that should be aggregated and analyzed, then a columnbased storage is more suitable.

14

(25)

HA100 Lesson: Introduction to SAP HANA Figure 15: Column and Row Store Tables in SAP With columnbased storage, data is only partially blocked. Therefore, individual columns can be processed at the same time by different cores.

Compression

15

(26)

Unit 1: Introduction and Positioning HA100 Apart from performance reasons, column store offers much more potential leverage stateoftheart data compression concepts. For example, SAP HANA works with bit encoded values and compresses repeated values, which results in much less memory requirements than for a classical row store table.

Partitioning

Figure 17: Partitioning Data for Faster Processing of Data in parallel

16

(27)

Insert Only on Delta

Figure 18: Management of inmemory columnstore tables Updating and inserting data into a sorted column store table is a very costly activity, as the sort order has to be regenerated and thus the whole table is reorganized each time. For this reason SAP has tackled this challenge by separating these tables into a Main Store (readoptimized, sorted columns) and Delta Stores (writeoptimized, non sorted 2015 © SAP SE or an SAP affiliate company. All rights reserved.

17

(28)

Unit 1: Introduction and Positioning HA100 columns or rows). There is a regular database activity which merges the delta stores into the main store. This activity is called “Delta Merge”. This diagram shows the different levels of data storage, and distinguishes the main store from the delta stores. • MAIN Storage After a merge (=reorganization), SAP HANA stores all data in a main storage organized by columns. • DELTA 1 Storage New or changed entries are initially stored in a delta storage, which is organized by columns. However, for speed purposes, the delta storage is not sorted (contrary to the main storage). Note:If the delta reaches a certain size, it merged back into the main storage completely sorted. • DELTA 2 Storage For recording of high speed event like formula one sensor recording or mass RFID reading, data entry can go to a second delta storage, which is organized as a row store. This storage works as a very short term input buffer in order not to loose any sensor signal. This second delta storage is frequently merged into the first delta storage and thus into the main storage. Queries run against all storages simultaneously. The main storage being the largest, but because of the sorted data also is the fastest. DELTA 1 is slightly slower for read queries, but much faster for inserts. DELTA 2 is very fast for insert, but much slower for read queries, and therefore kept relatively small. To learn more about the Main and Delta storage of SAP HANA, you can consult the How to Guide How to Delta Merge for SAP HANA and SAP NetWeaver BW POWERED BY SAP HANA , available athttp://scn.sap.com/docs/DOC27558.

18

(29)

Software Optimization

Figure 19: SAP HANA Software Optimization (1) Figure 20: SAP HANA Software Optimization (2) The fact that SAP HANA comes with different engines to process calculation logic and execute programming code is a great opportunity to push dataintensive calculations from the ABAP application layer into the SAP HANA database. For this reason, SAP ABAP has been enhanced with NetWeaver 7.30 and 7.40 to exploit the advanced inmemory features of SAP HANA. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

19

(30)

Unit 1: Introduction and Positioning HA100 This results in less data transfer between application layer and database layer, and a much better usage of resources. The application layer focuses more on orchestration and triggering the processing within the database. In the end, complex logic can be processed in very little time which results in great performance improvements. Thus the main concepts of software innovations can be summed up as follows: 1. Bring the logic to where the data is 2. Calculate first, then only move results Figure 21: SAP HANA Software Optimization (3) SAP applications are, of course, required to support not only SAP HANA but all the database management systems that are certified for ABAP. For this reason, there is an enhancement in those ABAP programs which are SAP HANA optimized. In a Business Addin (BAdI), those programs first check for the database in place. In case of SAP HANA, the optimized version is triggered; in the other case the classical ABAP flow is executed. Thus there is two versions of certain processes on the application layer • Standard ABAP code working on every supported database • Optimized ABAP code working on SAP HANA only

20

(31)

HA100 Lesson: Introduction to SAP HANA Figure 22: SAP HANA Software optimization: Example of SAP BW SAP BW provides a good example of how certain dataintensive and performancecritical processes have been optimized for SAP HANA in the recent versions. This concept has been followed very strictly in the current version of SAP NetWeaver BW 7.40.

Geospatial Data

Silos of information create an incomplete picture. Data has no shape, form or geographic context that can be visually understood. Data is incomplete and not in sync with business systems, as it is not linked to the business process. By combining business data with geographical data you can identify new opportunities and root causes by leveraging spatiallyenabled business applications on the SAP HANA platform. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

21

(32)

Unit 1: Introduction and Positioning HA100 Figure 23: The Challenge of Information Silos SAP HANA includes a multilayered spatial engine and supports spatial columns, spatial access methods, and spatial reference systems. Spatial data is data that describes the position, shape, and orientation of objects in a defined space. Spatial data is represented as 2D geometries in the form of points, line strings, and polygons. For example, a map of a state, representing the union of polygons representing zip code regions.

22

(33)

HA100 Lesson: Introduction to SAP HANA Figure 24: SAP HANA a Spatial Enabled Database The shape of the geographical data you want to store determines which datatype you want to use. A geographical column can be defined at table creation or added to an already existing table. Geospatial data is typically entered using the WKT (Well Known Text) format. This format is maintained by the Open Geospatial Consortium (OGC) as part of the Simple Features defined for the OpenGIS Implementation Specification for Geographic Information. Additionally, there are other ways of entering geographical data, for example WKB (Well Known Binary) and ESRI shapefiles (a popular geospatial vector data format). Two common operations performed on spatial data are calculating the distance between geometries, and determining the union or intersection of multiple objects. These calculations are performed using predicates such as intersects, contains, and crosses. The software provides storage and data management features for spatial data, allowing you to store information such as geographic locations, routing information, and shape data. These information pieces are stored as points and various forms of polygons and lines in columns defined with a corresponding spatial data type (such as ST_Point and ST_Polygon). You use methods and constructors to access and manipulate the spatial data. The software also provides a set of SQL spatial functions designed for compatibility with other products. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

23

(34)

Unit 1: Introduction and Positioning HA100 Figure 25: Geographical Data Types Calculation Views now support spatial operations like calculating the distance between geometries and determining the union or intersection of multiple objects. These calculations are performed using predicates such as intersects, contains, and crosses. A predicate is a conditional expression that, combined with the logical operators AND and OR, makes up the set of conditions in a WHERE, HAVING, or ON clause, or in an IF or CASE expression, or in a CHECK constraint. In SQL, a predicate may evaluate to TRUE, FALSE. Spatial predicates are implemented as member functions that return 0 or 1. Spatial operations are modeled as “Spatial Joins” to query data from database tables that contain spatial data.

24

(35)

HA100 Lesson: Introduction to SAP HANA Figure 26: Calculation View Spatial Join Operations The relate predicate has the greatest flexibility and specifies the spatial relationship between two spatial types, using a small two dimensional table. You can specify multiple spatial conditions at once, like wether the interiors of two columns relate or not. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

25

(36)

Figure 27: Calculation View Spatial Operations Examples (1/2)

The following examples illustrate the usage of the predicates Touches,Within Distance and Contains.

The value entered for the distance in the Within Distancepredicate, represents the values corresponding to the geometry used in the projection, like 12 meter.

(37)

HA100 Lesson: Introduction to SAP HANA Figure 28: Calculation View Spatial Operations Examples (2/2)

SAP HANA Native Application Development

In the traditional 3tier applications (especially from SAP), the database is largely used as a data store mechanism only. Massive queries bring large amounts of data back to the application server for processing. Lots of application execution time is spent in the application server looping over records and performing exclusions, calculations, etc. This leads to the need for database buffers at the application server level. This also creates a situation where most of the computing resources are allocated to several, large application servers since the bulk of all the logic is performed at this level. With HANA, the key to the best application performance is pushing as much of the logic execution into the database as possible. We now “trust” the database. Keep all the data intensive logic down in the database as SQL, SQLScript, and HANA Views. Lightweight imperative logic, flow logic, and service enablement can be down at the Extended Application Services level (XS). XS is not like the traditional application service – no database buffering, stateless only – it should be treated as a light, passthrough layer only. Finally, the complete UI rendering and processing should be done in the client device. Any client side UI development model can be used, although SAP provides SAPUI5 (HTML5 libraries and development tools) as well as UI Integration Services (Open Social based, lightweight portal). HANA 2015 © SAP SE or an SAP affiliate company. All rights reserved.

27

(38)

Unit 1: Introduction and Positioning HA100 should serve out static HTML content and JavaScript libraries as well as expose data and logic via pure REST data services. The UI creation, presentation logic and data injection should all happen on the client side. Figure 29: 3tier Application (Java, ABAP) vs. Native SAP HANA Figure 30: Code to Data

28

(39)

Figure 31: SAP HANA Extended Application Services Overview

(40)

Unit 1: Introduction and Positioning HA100 Using the SAP HANA Platform has the following advantages: • Simplicity at runtime A major advantage of a 2tier architecture is simplicity, leading to higher efficiency. Native HANA applications have reduced cost of ownership, as no additional application server needs to be installed and administrated. As stated before, HANAbased applications often have no need for a traditional application server, because the presentation logic moves to the client and the dataintensive processing is pushed to the database layer. • Simplicity at design time The development landscape has a single development environment and a single repository. This eliminates the risk of inconsistencies that can arise when parts of the application need to be stored in different repositories. • Strategic and futureproof Other important aspects are strategic alignment, the chance to participate in innovation and to be prepared for the future. With the decision to build a native HANA application, you support SAP’s inmemory strategy. As HANA is the strategic new SAP platform, you ensure that your architecture is sustainable. You also benefit from continuous technology innovations, as the HANA platform is enhanced and constantly improved at high speed. • Speed of Development With HANA XS, you can develop webbased access to data in HANA very fast. HANA views and tables can be exposed via OData services in declarative way without coding. As the OData service is generated from metadata, you don’t have to change any code, for example after you add new fields to a view. • Access to HANA APIs The XS JavaScript API contains interfaces that are otherwise not available, or in a less convenient way, for example the repository API. • Performance Further performance optimizations can be expected, because the XS engine is an integrated part of HANA, developed by the HANA core team.

30

(41)

HA100 Lesson: Introduction to SAP HANA In a development model for SAP HANA based native applications, the extended application services offer: • Easy access to the SAP HANA database via HTTPbased consumption. • Attractive, dynamic HTML5 UI applications via OData services or by writing native applicationspecific code that runs in SAP HANA context. • Powerful search services. • Builtin web server to access static content stored in SAP HANA repository. The application development is following a layered approach: • UI rendering completely in the client (browser, mobile apps). • Serverside procedural logic in JavaScript. • All artifacts stored in the SAP HANA repository.

Full Text Search and Text Analysis Overview

A typical challenge in today's business is to search for information among huge amounts of data, constantly collected in structured and unstructured form in different areas in or outside your company. You may need then to extract meaningful information out of your data, to be able to analyze it properly. Figure 32: Text Search, Text Analysis, and Analytics For example you may need to perform “faulttolerant” searches, e.g when looking for duplicate master data where mistyped names are common; or you may need to perform so called “linguistic” searches, e.g you search for the string “computed” and you would like to see also “compute”, “computing”, “computes”, ... in your search results. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

31

(42)

Unit 1: Introduction and Positioning HA100 You may also have additional search requirements, like ranking your search results or search one string at once over all the fields of a table. SAP HANA offers native search capabilities to support these and other business needs with the “Full Text Search”. Figure 33: SAP HANA Text Searching Among the search capabilities in SAP HANA, the “Fuzzy Search” offers the possibility to search for approximate matches to a given string. For example you could search for the string

_Walldorf

and find all exact and approximate (to a degree that you can specify in your search) matches, like

_Walldorf

,

Wadlorf

,

_Valldorf

,

Wahldorff

, ... . In general a Fuzzy Search will look for all strings matching the given one exactly or differing by missing, added or mistyped characters. The behavior is similar to what you experience when you search for a web page in internet on a search engine: you do not want to see only exact matches of your search string. The “Text Analysis” allows the extraction of structured information from unstructured information. For example it allows linguistic markup, like for example identifying the part of a speech (verbs, nouns, adjectives and so on). It allows also to identify entities (locations, persons, dates, ...) in an unstructured text.

32

(43)

HA100 Lesson: Introduction to SAP HANA Figure 34: SAP HANA Text Analysis The results of a Text Analysis are stored in a table and can therefore be consumed through all supported HANA Scenario, for example in information models, in R language scripts, via the Predictive Analytic Library functions or via the HANA Information Access toolkit for HTML5 by building a search UI. Figure 35: Text Search and Analysis Use Cases / Scenarios 2015 © SAP SE or an SAP affiliate company. All rights reserved.

33

(44)

Lesson Summary

You should now be able to: • Explain the common pain points in a system using a classic database • Explain how SAP HANA can handle the pain points and help to improve performance • Explain benefits of application development, spatial and text analysis

34

(45)

HA100 Lesson: SAP HANA Scenarios

Lesson: SAP HANA Scenarios

Lesson Overview

This lesson discusses the different system configuration and possible SAP HANA scenarios.

Lesson Objectives

After completing this lesson, you will be able to: • Explain the architecture of the main SAP HANA implementation scenarios

Business Example

A sidecar scenario can be a first step to meeting urgent and important business needs. The COPA (Controlling – Profitability Analysis) accelerator is an example of a sidecar scenario. SAP HANA is used as a secondary database where data is replicated in realtime. Information and results can be consumed on an SAP Business Objects platform or directly in SAP ECC. Then, once the SAP Business Suite or BW migration is effective, the sidecar perimeter can be integrated to a schema of the SAP HANA Database used with Business Suite or BW. The third step corresponds to the situation, when SAP HANA is the unique platform for all SAP applications in an organization. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

35

(46)

Technical Architecture Patterns and Use Cases

Figure 36: Technical Architecture Patterns

Figure 37: SAP HANA Use Cases

(47)

HA100 Lesson: SAP HANA Scenarios This diagram provides all the use cases of how SAP HANA can play a role in the Enterprise Information System. • HANA Platform (Datamart) Build all kind off applications like OLAP, predictive or text mining. • HANA apps for Suite Apps bound to the Suite, that run on HANA, based on data replicated from the Suite Any DB to HANA DB. • HANA accelerators Accelerate the Suite by replicating the data from any DB to HANA DB. In case HANA data is available a ABAP case statements decides, to run processing on the HANA Server instead of the ABAP stack. In addition BI clients can leverage the data in SAP HANA and accelerate the reporting. • Business Warehouse, Business One, Business Suite on HANA Take advantage of SAP HANA without disruption for smarter innovations, faster business processes and simpler interactions. • Cloud on HANA A public Service platform to PlatformAsAService offering that allows SAP partners and SAP customers to build, deploy and operate nonABAP applications in an open and standardsbased cloud environment. • New Apps New SAP applications based on SAP HANA. This HA100 course uses the second scenario “HANA platform” in the training system: There are some replicated source tables from an ERPsystem in a standalone SAP HANA environment.

SAP Cloud powered by SAP HANA

SAP is the only company, which can integrate SAP public cloud solutions including Ariba & Successfactors to SAP HANA solutions, including Suite on HANA (SoH) & Business Warehouse (BW) running either on HANA Enterprise Cloud (HEC) or on premise. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

37

(48)

Unit 1: Introduction and Positioning HA100 Figure 38: Cloud Portfolio SAP’s cloud portfolio is the most comprehensive on the market today. It is designed to unlock all of the new possibilities of cloud computing, as well as help speed adoption of HANA innovations. At its center is a set of public cloud applications and cloud suites. These provide cloud line of business applications that give the ability to manage core business with increased agility, while bringing them SAP’s best practices and 40+ years of business process management experience. To bring the benefits of cloud economics and HANA for existing SAP landscapes, the SAP Cloud Portfolio includes managed cloud services. SAP’s managed cloud offering has full integration with SAP Apps (Ariba, Successfactors). In fact, SAP can truly integrate SuccessFactors, Ariba, Suite and other SAP Applications. You can migrate your SAP Business Suite and SAP BW licenses onto the SAP HANA Enterprise Cloud and take advantage of HANA optimized infrastructure as well as tailored professional services delivered by SAP or certified partners. The key advantage of the SAP HANA Enterprise Cloud is, it is the fastest and easiest way to access HANA based innovations for mission critical applications. You can take advantage of cloud economics and subscription pricing to access HANA through the SAP HANA infrastructure subscription offering. These can be purchased and provisioned via the SAP HANA Marketplace. The SAP HANA Marketplace is also the store through which you can purchase ecosystem innovations that run stand alone or extend SAP applications.

38

(49)

HA100 Lesson: SAP HANA Scenarios Spanning across the portfolio is set of business network applications for business to business collaboration as well as social applications for people to people collaboration. All of the portfolio is built on a common platform, the SAP HANA platform. Through this approach, SAP makes available the entire portfolio, the application, development, and integration services, as well as the HANA database and analytics and foundational capabilities of the SAP HANA Cloud Platform to speed the development and delivery of innovations, both from SAP and from partners. Figure 39: Overview Cloud Offerings 2015 © SAP SE or an SAP affiliate company. All rights reserved.

39

(50)

Lesson Summary

You should now be able to:

• Explain the architecture of the main SAP HANA implementation scenarios

(51)

HA100 Unit Summary

Unit Summary

You should now be able to: • Explain the common pain points in a system using a classic database • Explain how SAP HANA can handle the pain points and help to improve performance • Explain benefits of application development, spatial and text analysis • Explain the architecture of the main SAP HANA implementation scenarios 2015 © SAP SE or an SAP affiliate company. All rights reserved.

41

(52)

Unit Summary HA100

(53)

(54)

(55)

Unit Summary HA100

(56)

Unit Summary HA100

(57)

Unit 2

SAP HANA Studio

Unit Overview

This unit is an introduction to SAP HANA Studio.

Unit Objectives

After completing this unit, you will be able to: • Understand the structure of SAP HANA Studio • Configure Perspectives • Create a Package

Unit Contents

Lesson: SAP HANA Studio ...

46

Procedure: Exercise 1: Getting Started with the SAP HANA Studio ...

₆₂

45

(58)

Unit 2: SAP HANA Studio HA100

Lesson: SAP HANA Studio

Lesson Overview

This lesson is an introduction to the SAP HANA graphical user interface. The SAP HANA Studio is the main entry point to SAP HANA for system administrators, modelers and developers.

Lesson Objectives

After completing this lesson, you will be able to: • Understand the structure of SAP HANA Studio • Configure Perspectives • Create a Package

Business Example

You are a consultant at a client site, and it is the first time you launch SAP HANA Studio. You need to add the customer's SAP HANA instance to your SAP HANA Studio installation, so that you can work on the server. You also have to create a new Delivery Unit and Package in which you will store your Information Models. Information Models in SAP HANA are a combination of attributes, dimensions, and measures, created by different types of modelling views.

46

(59)

HA100 Lesson: SAP HANA Studio

SAP HANA Studio

Figure 40: The SAP HANA Studio The SAP HANA Studio is delivered as part of the SAP HANA installation package, and provides an environment for administration, modeling, development and data provisioning. It can be installed on any client PC that has a connection to the SAP HANA system. The SAP HANA studio is a Javabased application that runs on the Eclipse platform. For more information on the Eclipse IDE (Integrated Development Environment): http://www.eclipse.org) .

Perspectives in the SAP HANA Studio

When you start the SAP HANA Studio for the first time, you must choose a perspective. Perspectives are predefined User Interface (UI) layouts with several views. One or several perspectives address the needs of a particular SAP HANA user role. For example, a System Administrator would typically use theSAP HANA Administration Console perspective. Each view can be moved around via drag & drop. You can also customize a perspective by adding or removing views. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

47

(60)

Figure 41: Perspectives are Based on Views

Here is an example of some perspectives that are available in the SAP HANA Studio. • SAP HANA Modeler

TheSAP HANA Modeler perspective is used by Data Architects to create Information Models, as a combination of attributes, dimensions, and measures, included in different types of modelling views.

• Administration Console

TheAdministration Console perspective is used by SAP HANA Administrators to administrate and monitor the whole SAP HANA system.

• Resources

The Resourcesperspective is used to organize files, such as text files, sql scripts, and so on, by project.

• Other perspectives

Some perspectives in the SAP HANA Studio are designed for HANA applications development, Java development and Lifecycle Management.

(61)

Figure 42: Opening a Perspective

To open a perspective, choose Windows → Open Perspective , then select a perspective from the list, or choose Other.... It is possible to have several perspective open at the same time, and to switch from one perspective to another. To do so, in the perspective switcher in the upperright corner of the screen, choose the perspective you want to open. Figure 43: Adding a View to a Perspective 2015 © SAP SE or an SAP affiliate company. All rights reserved.

49

(62)

To add a view to a perspective, chooseWindows → Show View, then select a view from the list, or chooseOther....

Note:The SAP HANA Studio is base on Eclipse. For this reason, you will see a lot of views in the Show View dialog box. The most relevant views to use when you start working with SAP HANA Studio are located in the following folders:

• SAP HANA

• SAP HANA Modeler

• Help (Cheat Sheets and Help views)

• General (Project Explorer and Properties views)

Figure 44: Customizing the Systems View Some views can be customized.

To do so, choose the View Menu button and chooseCustomize View....

(63)

HA100 Lesson: SAP HANA Studio Figure 45: Resetting a Perspective Any perspective can be reset to its default views and default layout. To do so, choose Window → Reset Perspective... .

Adding a System to the SAP HANA Studio

When you start the SAP HANA Studio for the first time, there is no connection to any SAP HANA system available. You must create a first connection to an SAP HANA system. To add a system to SAP HANA, you must open a perspective in which theSystems view is included. For example:

• TheSAP HANA Administration Console perspective. • TheSAP HANA Modeler perspective.

(64)

Unit 2: SAP HANA Studio HA100 To add an SAP HANA system, you need the following information: • The name of the server that runs the SAP HANA Engine. • The instance number. This is a twodigit number, that determines the communication port to the SAP HANA system. For example, if you connect to an SAP HANA system with instance 00, the port used to communicate with the server will be 3 0015 • The credentials of a user that is defined in the SAP HANA system. This user must be active. Note: • It is possible to connect to several SAP HANA systems within one single instance of the SAP HANA Studio. • You can connect to the same SAP HANA system with two different users. There are two main methods to add a system to the SAP HANA Studio: • Manually With this method, you add one SAP HANA system at a time.

– In the

Systems view, rightclick any blank area and chooseAdd system.... – Fill in the server name, instance number and system description, and chooseNext. – Fill in the user name and password, and choose Finish. • By importing a Landscape This method allows you to connect to several SAP HANA systems at the same time, by importing an xml file generated previously by a landscape export from the SAP HANA Studio installed on your computer or another one.

– Choose

File → Import and chooseSAP HANA → Landscape. – Specify the landscape file location, the destination folder for the import, and choose Finish. Note:The landscape xml file does not contain any password. You will have to specify the user and password for any system added to the Systemsview.

52

(65)

The Systems View

Figure 46: The Systems View

TheSystemsview lists all the systems that have been registered (manually, or by a landscape import). For each system, the content is organized as follows:

(66)

In the SAP HANA Studio, one central point of access is theSystems View, which is usually placed on the left side of the screen. • Catalog As in many database structures, the catalog contains tables, views, indexes, and so on. All these objects are organized into schemas. Schemas are used to categorize a database content according to customer defined groupings that have a particular meaning for users. Schemas also help to define access rights to the database objects. Note:From a modeling standpoint, schemas can help to identify which tables to use when defining information models. But a model can incorporate tables from multiple schemas. Schemas do not limit your modeling capabilities.

The column views that you create are always located in schema_SYS_BIC, their metadata in schema _SYS_BI.

If you run an SAP Application directly on SAP HANA, then the schema will always beSAP<SID of the system> . For example, if your productive CRM System is calledCRP, the corresponding schema will beSAPCRP.

• Content

The Content folder of the catalog is where you store all the HANAspecific modeling objects. Note:The physical tables are the only storage area for data within SAP HANA. All the information models that will be created in the modeler will result in database views. As such, SAP HANA does not persist redundant data for each model, and does not create materialized aggregates. • Provisioning

The Provisioning folder is essentially related to Smart Data Access, a data provisioning approach in which you can combine data from remote sources (Hadoop, SAP ASE, SAP IQ) with data of your SAP HANA physical tables, by exposing them as virtual tables.

• Security

In the Securityfolder, the System Administrators define users and roles.

(67)

Workspace

SAP HANA Studio stores your projects in a folder called a workspace. A workspace is an environment that maps a local directory to a package hierarchy in the SAP HANA repository. This folder is used by the SAP HANA Studio to store designtime objects, such as information views, when you edit them. There can be several workspaces defined in the configuration of the SAP HANA Studio installed on your computer. This is relevant when you work on different projects. Note:During this training, you will only use one workspace, which is stored by default in C:\Users\train##\hdbstudio (where ## is your student number).

System Administration and Monitoring

To administer and monitor one or several SAP HANA systems, you can use the following views:

• TheSystem Monitor view • The Administration view

Figure 47: The System Monitor View

TheSystem Monitor view gives you a summarized view of the system landscape. By default, all the systems that are listed in the Systems view appear in theSystem Monitor view. You get the most important information about system status, alerts, as well as disk space, memory and CPU usage.

You can customize this view by adding or removing columns. To do so, choose the Configure Viewerbutton. Alternatively, you can rightclick in the System Monitor view and chooseConfigure Table.

If you want to filter the list of systems that are shown in the view. rightclick in the System Monitor view and chooseSystem Filter.

(68)

Unit 2: SAP HANA Studio HA100 Figure 48: The SAP HANA Administration Console Perspective The SAP HANA Administration Console is a perspective that is predelivered by SAP. This is the main view to administrate HANA systems. For example, you can do the following tasks: • Start and stop a system • Configure a system • Monitor a system • Backup and restore a system • Perform a problem analysis

To open the Administration view, you can:

• Doubleclick the system in theSystem Monitor view • Doubleclick the system in theSystemsview

The SAP HANA Modeler Perspective

When you want to create Information Models in the SAP HANA Studio, you need to open (or switch to) the SAP HANA Modeler perspective. To do so, choose Window →

Open Perspective → SAP HANA Modeler .

(69)

TheQuick View is a practical entry point, dedicated to the modeler perspective. From this view, you can create, manage and transport information models (packages, views), define or execute data provisioning, define schema mapping, and so on.

Note:You can define your favorite actions (for example, Export, Import, and Validate, and display only a custom list of these favorites.

Figure 49: The SAP HANA Modeler perspective

When you want to perform an action from theQuick View , you must first select the SAP HANA system on which the action will be executed. Note:You actually select both a System and a User logged on to the System. If you are logged on to the same SAP HANA system with two (or more) different users, the action will be authorized based on the privileges of the user you have selected. The SAP HANA Studio offers other perspectives for debugging, resource, team synchronizing and more. 2015 © SAP SE or an SAP affiliate company. All rights reserved.

57

(70)

If you have closed the Quick View and want to reopen it, you can do one of the following actions:

• ChooseHelp → Quick View. • Reset the Modeler perspective.

Note:TheQuick View can only be displayed within the Modeler perspective.

Figure 50: The Systems View – Modeling Content

The Content node of the Systemsview displays the data from a data modeling perspective. The information views, along with other modeling objects such as analytic privileges or procedures, are organized in packages. Each package is a repository that you can assign to a delivery unit in order to transport the objects it contains.

The SAP HANA Development Perspective

The SAP HANA Studio includes a development perspective with debugging functionality.

58

(71)

Figure 51: The SAP HANA Development Perspective

From the development perspective it is possible to check in and out development objects, connecting to a repository

(72)

Unit 2: SAP HANA Studio HA100 Figure 52: Development Repository Integration SAP HANA Extended Application Services (also known as XS Server) is a key aspect of SAP HANA as a platform. XS is an application server, web server, and basis for an application development platform, that resides inside SAP HANA. XS is not a completely separate technology that happens to be installed on the same hardware server as SAP HANA; XS is actually an extension of, and tightly integrated into, the SAP HANA database. Since the release of SAP HANA SPS05, XS is available for customers and partners who want to develop their own SAP HANAbased applications. Examples of applications developed with SAP HANA XS are the SAP HANA Live Browser or SAP Operational Intelligence .

60

(73)

Getting Help within the SAP HANA Studio

There are several ways to get help when you use the SAP HANA Studio. • The SAP HANA Studio Help This is a classic online help, with structured content and search capabilities. The content corresponds to the SAP HANA documentation.

To open the Help view within the SAP HANA Studio, choose Help → Help Contents ,Help → Search or choose F1.

Note: You can also display the Help content in an external window. To do so, choose the Show in an external window button in the Helpview. • The SAP Help Portal

You can access directly all the SAP HANA documentation available on the SAP Help Portal from the SAP HANA Studio. In addition to the documentation, you can find underAdditional Information several links to other information sources, such as the SAP Community Network, Central SAP Notes, and so on.