SAP HANA Introduction SAP HANA Date Training Center instructors Education Website Participant Handbook Course Version: 07 Course Duration: 2 Day(s) Material Number. 6012133;Copyright Copssight © 2014 SAP AG ov an SAP allfiae company. All ights served No part ofthis publication may’ be reproduced oF transmitted in any fom oF fr any purpose ‘thot the express perssion of SAP AG, The information contained hein may be changed Some sftare products mat s1 by SAP AG and is dishibors contain proprietary sofvare Trademarks Adal the Aduby logo, Acraat PostScript, aad Rewer are tadentrks or rgistred trademarks Ase Ssstems sinporated in he United Stes a er somntss Apple, pp Store, Faseime.iouks, iPad Phe. ‘Photo. iPod Tunes: Muli-Touel, Okjeotve Retin, Saini, Siri, and Neo are trademarks or resitved radenaeksof Apple Ine DBluctonth isa repistered trademark of Bluetooth SIG Ine itv. ICA, Program Neighborioad, MetaFrame ow XenApp, WiaP ante, VideoPrame and Mullin are eee roisterd inna itis Sestems he Comput is. registered teak of Conputop Wirtchasinoematik inh Edgar Calne isa fered trademark of EDM Online ne ah BR, Donley && Sons Compe, Facebok, the Facebok and F lg, FF, Fae, Poke, Wall, an 82665 are rademarks of Facebok Gowgle App Eagin, Giogle Apps, Gale Checkout, Giogle Data AU. Gnghe Maps, Gil Mote Ads, Google Mabile Updater Google Mobile, Gane Sloe, Geotle Sine, Gove Ute Google fe Mail Gana, Youlube. Daluk, and Adio are waar or remarks of Gove I HP isa regitered alemak ofthe Howlet-Picknd Development Company LP. IML XML. NHUMI. ond WAC are Wadena. re tems the Bassas Insite af Tecioloay (M1, Farpenn Rexcarsh Connon Fe Intormotics ard Materaties RIM), or Kei (Invert tradematss orslainid as sonetic iM, DH2, DH2 Univers Database, Sten, Stem 5, Ses p, Sytem pS, Spstem %, System 2, System 710, 710, 2 VAI. 7 OS, ON 390, 7Enerpive, AWeIVM, Power Amdatetute, Power Sestens, POWERT, POWHRO:, POWERS, POWER, Powe, pareSese, PowerPC, BhaleCente, Sestent Sage, Stamize. XIV, GPES, ACME, RLIAIN, DAZ Connset RACE. Redbooks (08 2. AIX, cllizent Mines WebSphere Tivol, Iniormgs, and Sauter Manet eademacks of IM Corporation, cor resstered Micros, Windows, #scel, Ouok, Poser, Silvetligh, al Vise Sais ate resistred Irademarks of Microofl Corpraton INTERMEC is registered fraderark of Entermes Tesh! + Conportion 10S is sopstred trademark of Cis System Ins Ie Klowt name a! logos are tiemaris Klot Ine iss the veined taemark of Linus Torvalds the Unite States and ther counties Motonsla is registra tremor of Moola Tndema Holdings LL ‘Movil ad iret aa thet logos ae register ademahs ot the Mois Foundation, [Novell and SUSE: Linus Eateeprise Server are reuistred trademarks of Noval Ie 920141306260OpesTex isu reuistered tademark of OpenTent Cospraton ‘Ocaste and Java ave repstered trademarks of Oracle alts ilies, OR Code sa regione inalmrh of Denso We Incorsated RIM, iach, HIM, Dlackltery Cone takers Wok Blacker Perl. lackDemy Tc PlackPerr Storm, Hlackevty Storm. Blackery Play Rk, and lackerry Append are tnadematks or rexitered trademarks of Research in Miao ited SAVO isa ropistred trademark of The Savo Grogp La The Skype name is edema of Skype or relat entities Titer and eet ate tadeachs 0° teuntened trans of Titer UNIX, Open, OSF and Motif ae negstered trademarks of the Open Group, Wii isa registred trdema of WiFi Alliance SAP R, ADAP DAPI, SAP Netenr Duo, Prtet Explorer Steam Work, SAP HANA. the Buses Objet og {Crt Decisions, Web [nlligenwe, Nees, Sybase. Adanive Server Adaplive Sener nts ByDesign, SAP Busines Objects Hnusines0ijccts: Crostal Reports iAnbere Sve 368, SQL Ansuhere, Crosga. 2K 8 and FDDY. Anis the Ariba logo, Quarem, bsprocess, Ariba Discovery. Suoeess isthe Ditfeerce, Hic Mobile Tinshase fs sie tele ork agai, SuecessFastors fm and Fass Sia and other SAP products snd services ents bere as el as thet respective A ina at SAP ali lags ate talenars or registered talemarks oT SAP AG it Ci Alter predict and sersice names mented are the trademarks a hei respective companies Data i this dace serves snarsational parses mls: National product spect Disclaimer Those mattis ae subject 0 shange without nates, These materials are provide by SAP AG and itsathhted eonspanes SAP Grosp or nfoenational purposes onl, withovt reesenttin ‘sorts ofan hi aid SAP Cron shall ot bebe rates Th ls arantigs fi SAL Grp pats as sevice ae those tha nest fhm sc practi services. i any. Nolin he the express array sisertens accompany osiuting ana 920141305260920141306260‘This handbook is intended 10 complement the instructor-led presentation of this course, and serve asa source of reference. Its not suitable For self-study Typographic Conventions tandard used in this handbook, The Following niventions are also used Words or characters that appear on the sereen, These inelude field names, screen titles. pushbuttons as well as menu names, pats, and options Also used for cross-references to other documentation both internal and extsrnal, Example text Emphasized words or phrases in bod text. titles of aphics, and tables EXAMPLE TEXT | Names of elements in the system, These include 28, transaction codes. table report names, program 1 names, and indis dual key words of a pre Janguage, when surrounded by bods text, for example SELECT and INCLUDE Example text Sereen output, This includes file and diseetory names and their paths. messages. names of variables and parameters, and passages of the source test of a pr Example text Fxact user entry, These are words and characters that ‘sou enter in the system exactly as they appear inthe Socwmentaion, | Variable user entry, Pointed brackets indicate that you replace these words and characters with appropriate nis, 20a 2014 SAP AG or an SAP affiliate company. All ights reserved‘About This Handbook A100 Icons in Body Text ‘The following icons are used in this handbook £ For more information. tips. or background Note or further explanation of previous point Exception or caution = A w Procedures © Indicates that the item is displayed in the instructor's presentation, vi © 2014 SAP AG or an SAP afflate company All ights reserved 2014Course Overview Course Goals, ix Course Objectives ix Unit 4: Introduction and Positioning Introduction to SAP HANA 2 SAP HANA Scenarios 20 Rapid Deployment Solutions 28 Deployment Options 42 Unit 2: SAP HANA Studio SAP HANA Studio 48 Unit 3: Architecture. Architecture. 80 Persistence Layer. 98 Backup & Recovery 100 Unit 4: Modeling Introduction to the CO-PA Scenario 110 Introduction to the SAP HANA Modeler Perspective 118 Levels of Modeling 123 Unit 5: Data Provisioning 203 Uploading Data from Flat Files 205 SAP Data Services 214 SAP Landscape Transformation Replication Server 207 SAP Direct Extractor Connection 240 SAP Replication Server 24d 284 Unit 6: Reporting SAP HANA Database Connectivity Options. 283 Microsoft Excel 287 SAP BusinessObjects 266 SAP BusinessObjects Analysis for Office 278 SAP BusinessObjects Analysis for OLAP 284 SAP BusinessObjects Explorer 289 SAP Crystal Reports for Enterprise, Dashboards and Web Intelligence 299 20a 2014 SAP AG o° an SAP afflate company. Allright reserved viContents HAt00 Appendix 1: SAP HANA Links .........000. cesses 20329 &Y viii 2014 ights reserved=) SAP HANA enables business departments to analy ze business as it happens Individuals can create Hlesible anal tical models based on real-time data originating from business applications. ERP operational analytics is farther enhanced with SAP HANA interfaces to BI chent reposting tools, such as SAP BusinessObjects Explorer. SAP Crystal Reports, SAP BusinessObjects Dashboards. and SAP BusinessObjects Web Intelligence ‘This two-day 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 fools such as SAP Data Services or SAP Replication Server. and ereating Mevible analy ie models based ‘on real-time data originating from SAP ERP applications, In order to cover an ‘end to end scenario, the participants will also lean how to conncet to SAP HANA, from SAP BusinessObjects BE 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 + SAP ERP reporting and anals ves + General business modeling experience + Basic understanding of business stem landscapes Course Goals This course will prepare you to + Geta good understanding and overview of SAP HANA 20a 2014 SAP AG or an SAP affiliate company. All ights reservedCourse Overview @ A100 Course Objectives After complet his course, you will be able to Explain SAP HANA conoepts Use SAP HANA Studio Create simple information models Understand how data ean be loaded inte HANA Get an overview of how to report on HANA using client tools © 2014 SAP AG or an SAP afflate company All ights reservedIntroduction and Positioning Unit Overview This unit gives an overview of SAP HANA benefits. positioning. and deploy ment options. e Unit Objectives Afler completing this unit, you will be able «© ‘+ Explain the common pain points in a sy stem using a classic database = Explain how SAP HANA can handle the pain points and help to improve profit + Byplain the architecture of SAP HANA as an accelerator in a side-car scenario + Explain the architecture of SAP HANA as an In-Memiory Database + Explain what an RDS is, © Understand how you ean ‘Land use an RDS to speed up and secure an implementaion of SAP HANA + Explain SAP HANA deploy ment options Unit Contents Lesson: Introduction to SAP HANA 2 Lesson. SAP HANA Scenarios 20 Lesson: Rapid Deployment Solutions 28 Lesson: Deployment Options 42 20a 2014 SAP AG o° an SAP afflate company. Allright reserved 1Unit 1: Introduction and Positioning A100 Lesson: 8 Introduction to SAP HANA Lesson Overview ‘This lesson explains why SAP HANA has been developed and how this new technology can help inereasing business opportunities Lesson Objectives Aer 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 profit 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 duc to data volume The purpose of SAP HANA, |S to enable easy stors ng of these data. In pasticular, SAP HANA combines in-memory data storage and columnar data storage. two modern and exiwomely powerful features, Information Explosion COPA Data i Mot Invento' \ 2 8 gg re rer Planning Wi ! Opportuniti Figure 1: Reality #1: Information Explosion ‘The first ch created ie is the information explosion, Massive amounts of data is bei sy year. and how fast your business reacts to it determines whether ‘sou sucoced or fail ay 2 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Introduction to SAP HANA IDC. in its 2013 Top 10 predictions (released in November 2012) estimates that the “digital universe” will reach 4 ZB (1 zettabyte = L trillion gigabytes). ‘On the horizon of 2020, IDC projects that the digital universe will reach #0 zeitaby (es oF data, which is also 40 cnllion 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 Farth and Mars kilobyte (kB) > ntewaby te (MB) = gigaby te (GB) > terabyte (TB) > petabyte (PB) cevabs te (EB) = zettabyte (ZB) > youtaby te ¢YB) To learn more about the IDC forecast on the d 2070p Ina Sloan Management survey in 2010, 60% of executives said their companies have more data than they know how to use effectively, With data doubli: 18 months, that percenta to keep grav Expectation to make decisions in realtime, at moments of rsk and ‘opportunity Customers expect business ‘experience to be as satisfying as personal experience People expect instant, correct answers fo any question Figure 2: Reality #2: Consumerization of IT At the same time, the consumerization trend is divi svhat enterprise IT can help the business to do, People w information in the moment whether that isa moment of risk ora moment of ‘opportunity. If the moment has passed and your business has not taken the right action, ithas failed People want instant answers. They want thent to be right ‘They want them anywhere. any time 1p expectations as (0 Instant access to 20a (© 2014 SAP AG or an SAP atflae company. Allrights reserved 37Unit 1: Introduction and Positioning A100 Current and Complete Informati Figure 3: Reality #3: IT Cannot Deliver e, IT cannot deliser what the business needs. Why"? Because there ‘This puts IT in a tough Because the cost of managing tat data explosion is too high no practical way to instantly analy e every thing that is woiny on relative to the business. IT can deliver some of the information. The most critical slice of information ean be delivered in near real time. But itis not enough, Data is growing. Demand is increasing. We must find a way (0 deal with this —a way to process and analy ze massive amounts of data in real time: @ CMs ' eo (eee eens Figure 4: The Daily Challenges of Data Volume and Complexity. ava ©2014 SAP AG or an SAP afte company All ighs reserved 2014A100 Lesson: Introduction to SAP HANA e ee Lack of responsiveness User fustration LUncupportable business processes Need for agcregation Outdated figures ‘Guessing current situation Se Miesing opportunities ‘Competitve disadvantage Figure §: ... and the Main Drawbacks =) ah XE. “Transactional Data Figure 6: Your Reality with SAP HANA To resolve the difficult equation of data volume, speed, and flexibility, here comes SAP HANA. Using groundbreaking in-memory hardware and software, you can ‘cale, analy 7eit at amazing speed, and give the business not only instant access to real ine transactional information and analysis, but alse more Mesibility. Flesibilits to analy ze new types of data in different ways, without creating custom data warehouses and dala marts, Even the Nesibility © build new applications which were not passible before 2014 ©2014 SAP AG oan SAP affilate company. Allrights reserved sayUnit 1: Introduction and Positioning A100 SAP HANA Architecture © wemeal| | Sa) Sh hana~ cine | apation | ar ste + arnre (ei gta Coc Bee, EC) | | SEE Toe = ealtme Data Repleatin SAP ata Sovcos for ET capacities tom SAP Bosnees Suite GA ater uenees Narchouse (SAP hesepver Bt), ard id Panty Syston Capabilities Enabled = -alyze ntormatonin rata at upreederts ‘Syents on sngevoumes strom sogeosed ona © reat exible analyte modes Dass on ase ae Foundation for nw eategor of applications fea. plone amustan to agreay spear Sire oppestors age ee = Minimize data dupetion Cot c ‘iano Figure 7: SAP In-Memory Appliance (SAP HANA) So. wha is insde HANA? This arise dag explains the ain components and capabiss, Whatkinis fscale sped and improvement ae cstomer oo 3600x 460B 21% Fasterrepring _Datarecords nayzedin Average increase ‘speed less than a second inrevenue Figure 8: SAP HANA Proof Points a76é ©2074 GAP AG or an SAP affiete company All ights reserved 2014A100 Lesson: Introduction to SAP HANA Here are some proof points + Amari peed. ‘One of our pilot customers reduced the time it wok to run a report from one hour to one second. That is 3600 times faster. Let's pat that in perspective SAP talks about helping you 1a “run better”, so lets uso that as an example When an average person runs, thes move at about 7 miles per hour, 3600 times faster would be about 25,000 miles per hour. That is the Fast Fhuman being has ever travelled, and it was only done once - by the astronauts ‘on poll 10, on their return from the moon in 1969. + Amazing amounts of data During testing for HANA we executed queries ayganst 460 billion rows of dda fess than one second, ‘That is like bein and service visit for every car on earth in the last 12 months. in one second. Or to process every address that every one alive today has ever lived at in nd. Or to calculate the amount of taxes paid by everyone on the planet, since 1950, in one sovond able to analy ze every repair + Amaving value Having the ability (o create new real-time processes and simplify your IT Iscape has a big impact. According (© a study by Oxford Economics, ‘companies that implement real-time systems see anaverage 21% revenue growth, and a 19% reduction in IT cost. & — Compression No Schema Changes ove nee (oman conga Same SAL, Immediate Benents —— —————.- Ce es 369x Average Query Speed-Up Figure 9: Query Acceleration Example ~ Large Bank ~ 1 Month of Customer Information 2014 ©2014 SAP AG oan SAP affilate company. Allrights reserved 7aUnit 1: Introduction and Positioning A100 Why wait for data? + Allcustomers want fo see their current business data in real-time. Nobody wants to wait until data is uploaded into a data warehouse Why wail for new systems? © Latest hardware and latest database technology already support real-time reporting on massive amount of data Pa on PU Seen Pett) de mE aUy Figure 10: SAP Naming Update: SAP HANA SAP HANA = SAP HANA isa flexible, data-souree-agnostic appliance, that enables customers to analy 7¢ large volumes of data from SAP and non-SAP systems I4ime, 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 sy stems; SAP Landseape Transformation, SAP HANA Direct Extractor Connections (DXC). SAP Data Services or SAP Sybase Replication Server. +The SAP HANA database is a hybrid in-memory database that combines roys-based. column-based. and object-based database technology. It is, ‘optimized to exploit the parallel processing capabilities of modern multi-core CPU architectures. With this architecture. SAP applications can benefit from current hardware technolo ays ©2014 SAP AG or an SAP afte company All ighs reserved 2014A100 Lesson: Introduction to SAP HANA 320 CORES and more! Multicore CPUs 4.TB RAM and more! 10 Cores / CPU Mult-CPU Boards 8 CUPS | Board Multi Server Board eee a Massive Memory setups 2 TB/Server Figure 11: Hardware Innovation 1 was initially formulated in 1965. Aceordin of transistors i a chip doubles every year”, In 1975, however. this was adjusted bby David House. an executive at Intel, who said it will double every two years Moores to this law, “the number Avwidesproad variant of Moores law stat to double every 18 months, hip performance is Technology Drivers 005 74544 Moron 0.02 8 250% “foray” 212A ewok Sieed 40010 100% beater ce Figure 12: Improvements in Technology Historically. database systems were designed to perform well en computer systems \with limited RAM. As a consequence. slow disk }Q was the main bottleneck in data throughput. ‘The architecture of those systems was designed! with a focus on optimizing disk access, for esample by minimizing the number of disk blocks tor pages} to be road into main memory when proce a query 20a (© 2014 SAP AG or an SAP atflae company. Allrights reserved omyUnit 1: Introduction and Positioning A100 @ PAST FUTURE - €ee0ee00 otetetetetetetatet or @ ii ae ae = =i ti ows [oo sms, ~~ 8 8 8 = ‘Solid State Flash ‘OD Figure 13: Computer Architecture is Changing Computer architecture has changed in recent sears, Now, multi-core CPUS ‘onultiple CPUs on one chip or in one package) are standard, and extremely fast communication bewveen 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 4 cores... and 128-core processors will soon be available With the increasing number of cores. CPUS are able to process much more data peer time interval, This shifis the performance bottleneck from disk LO to the data transfer between CPL cache and main memory Data Storage and Processing In addition to a classical row-based data store, SAP HANA is able fo store tables in its column-based data store. [tis important t0 understand the differences between these two methods, and why column-based storage can highly inerease certain types of data processing = 70 © 2014 SAP AG or an SAP atftte company All ights reserved 2014A100 Lesson: Introduction to SAP HANA e@ [ESIGN © ROw-BASED storage et Tuple 1 SERENE es ‘alana 2 (coumn 4» OPTIMIZED for current HW Easily + COMPRESSIBLE COLUMIN-BASED Storage Figure 14: Column Data Storage ‘The concept of column data storay ‘example. the first version of SAP Sybase IQ. a column-based relational database. cased in 1999, Historically. columa-based storage was mainly used for analy tics and data warehousing, where aggregate Tunetions play an important vole, ve has been used for quite some time Fer jon Processi ‘On the other hand, using column stores in Online Trans applications requires a balanced approach to msertion and mdexing of column data, in order to minimize cache misses ‘The SAP HANA database allows the developer to specif whether a table is to be stored column-wise or row vise. IL is also possible to alter an existing column-based table to row-based, and vice versa CConvortonal dstabaces store rocards in ows Storing data in columns enables faster in-memory exocessing cof operations such a aggregates CColurnar layout supports sequential memory access ‘Acie aggregate can be processed in one linear scan Massive lel Processing posible per column a well, cexganze by row Aliope] e [35] s Teyaepoopevetzts) ‘xganze by column Als le[ole [io] 35 [aol rey s Peers) memory adress Figure 15: Software Optimization for Data Processing 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 1Unit 1: Introduction and Positioning A100 Conceptually, a database table is a two-dimensional 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. to options exist: + Arow-based approach stores a table as a sequence of records. each of which ain the fields of one ross column are stored in cont + Ina column-based table. the entries of memory locations No aggregation or search required ‘Table has a minor number of records > Some system tables ae storedin the row-store Figure 16: Key Facts: When to Use Row Store or Column Store? + Row Store I you want fo report on all the columns of a table, then the ro¥ store is more suitable because reconstructing the complete row is one of the most expensive operation for a column-based table + Column Stor If you to want to store im a table huge amounts of data that should be aggregated and analyzed, then a column-based storage is more suitable Ey 12 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Work on smaller sets of data in PARALLEL Figure 17: Partitioning Data for Faster Processing QO [ens |[ owe Lesson: Introduction to SAP HANA ° SRA -ys t 45 > SPREAD table contents across blades =a i ==3| } Cameaim >| cos me) Ege sel > Comer) cues = Ce Figure 18: Parallel Processing With column-based storage, data is only partially blocked. Therefore, individual ccollumus can be processed at the same time by different cores. 20a 2014 SAP AG or an SAP afflale company. All ights reservedUnit 1: Introduction and Positioning A100 @ Technology Innovations HW Technology Innovations Must Core Architecture (@cPUx t0Cores por Se] Rowand coum sexe Bie) A she compression mary bass A BEE eon tot ate spe 78a alt, fas Nofoweote ates Drama deco wart non Data preperemance m J | L-TIME ENTERPRISE Figure 19: SAP HANA Database Performance With dramatically improved hardware economies and technology innovations, Busine Strong HARDWARE Par Bo ke nis © 8 emon SS SAP In-Mem P s Knowledge BW Ac HANA Figure 20: Combining Business and Technology With strong partnership with hardware vendors. SAP suceseds in combiating its business Knowledge with the best-of-breed technologies. ey 14 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Lesson: Introduction to SAP HANA SAP HANA and Enterprise Data Warehouse In the domain of Enterprise Data Warehousing (EDW), SAP HANA is a hey techuioloyy to stieamline data storage and processing. The followi ‘an example of the possible evolution of an EDW + A traditional enterprise IT organization. with «vo SAP ERP systems and a third-party ERP. Each ERP has its own database and there are as many Data Mart (o support local Business Intelligence needs. An additional EDW with tls own database supports corporate BI needs. + Amintenmediary stage where SAP HANA is used as the technology layer For all he Data Marts and central EDW ‘+ A final implementation stage where HANA is the foundation forall the applications (ERP. data warehouse, new applications). e Tore Comprate BI sam ERP? >| Encererice Data Warehouse (BW) WA Figure 21: A Classic Enterprise Data Warehouse 20a 2014 SAP AG or an SAP afflale company. All ights reservedUnit 1: Introduction and Positioning A100 Qe fz corporate BI L—>] Enterrse Data Warehouse (BW) THEW APPLICATIONS. Figure 22; SAP HANA Appliance © Copperas BI Figure 23: Planned SAP HANA Platform 2.0 + EY 16 © 2014 SAP AG or an SAP atftte company All ights reserved 2014A100 e@ Lesson: Introduction to SAP HANA ‘SAP HANA is far more than BWA s Standard intecaces (SQL. HTTP, REST. MOX) = Real persistence layer not ut lt les) > redolunda loge, backupecovery, ‘There is @ lot of BWAMTREX in HANA * Column store; cstribued computing; caleulation engine Beyond BWA: 1 Row sore (Prin); persistence, transactions (MaxDB), SAL Parser (P*tme), BWA relies completely on SAP BW = You ony load InfoCubes into WA “5 Tachnealy tril data model Automate creation of rlatone | join condone = BWAhas BW on top > Complex ogi? Doitin BW > Detrng the data model? > doit in BW 3 Analisis aahoratons? > do tin BW ‘SAP HANA 1.0 is intended as a Data Mart (and BWA clearly isnot) > Flexibility {not ted to BWW) Figure 24: SAP HANA vs. SAP NetWeaver BW Accelerator SAP HANA database includes components from various other software applications For example: + Row Siore and SQL Parser has some code From Pketime database + Column Store has code fiom BWA Trex Engine + Porsistence Layer (Data and log volumes) has code fiom MAX DB Rapiel Deploy ment Solutions allow sou to implement a predefined and preconditioned content on several different functional or technical scopes. They permit to respond quiekly to expectations through SAP delivered coment 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 7Unit 1: Introduction and Positioning A100 ‘SAP Bank Analyzer rapid-deployment solution for financial reporting with SAP HANA ‘SAP Deposits Management rapid-deployment solution for transaction history analysis with SAP HANA Figure 25: Rapid Deployment Solutions £ Hint: Additional use cases can be find on hup./svwwysaphana.cov Ey 18 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: Introduction to SAP HANA e 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 hanelle the pain points and belp to improve profit 2014 2014 SAP AG o° an SAP afflate company. Allright reserved 19Unit 1: Introduction and Positioning A100 Lesson: SAP HANA Scenarios Lesson Overview This lesson discusses the differemt sy stem configuration and possible SAP HANA. scenarios e Lesson Objectives Afier completing this lesson, you will be able to + Explain the architecture of SAP HANA as am accelerator in a side- + Explain the architecture of SAP HANA as an In-Memory Databa Business Example \ migration fiom SAP Netweaver BW to SAP Netweaver BW, powered by SAP HANA. needs earefil pkamning and adherence technical requirentents A side-car scenario can be a firs slep 10 answer to urgent and important business, needs. The CO-PA (Controlling Profitability Analysis) a fof a side-car scenario, SAP HANA 1s used asa secondary database where dats js replicated in real-time, Information andl results can be consumed on an SAP Business Objocts platform or directly in SAP ECC sralor is an example Then, once the BW migration is effective, the side-ca perm: rated toa schema of the SAP HANA Database used with BW can be int ‘The thied stage consist using SAP HANA as the main data store for the whale SAP Business Suite Ey 20 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 Lesson: SAP HANA Scenarios Applications on SAP HANA Scenarios HANA Innovation Overview HANA Has AWA Apps (No Business sue pecatrator ap Sewteat ‘on AWA site se econrion o> Integttedscanation Inseconds: Morsinsgiti Supercharged Innowation: =A in Ora = Uta: ‘Reclerating Exploring dla Functional Busines Suite sauion cnt foacedtvon | Fasten up you applications ‘fly integrated vith ana ananctons of usinas Suite BW thou suey baton opined for HANA ss Seances Suanyialot Suipdon Vn vahand Gass ‘Sue intgeation Figure 26: HANA Innovation Scenarios Overview This diagram wives a few examples uf how SAP HANA can play a role in the Enterprise laformation System. 20a 2014 SAP AG or an SAP afflale company. All ights reservedUnit 1: Introduction and Positioning A100 t ar ‘operational asics Powered by SAP HANA over hy SAP HANA Bonet: Bonet: Various appteations bait on Fast insight ino business Simplifications lexbity, ‘SAP HAMA Extended ‘actly. mah modeling Teadingand ausry speed’ Appleton Services (XS) enti Figure 27: SAP In-Memory Strategy @ PAO eames: eocees Te ae Scan ae ae HANA as modeling platform 2 wo » Saoerseaerte oe Applications platform = New Applications eee ee 1. Data Provisioning en) Figure 28: SAP HANA Sidecar Scenario In this example of an SAP HANA sidecar scenario, he information views are 100% virtual, Without HANA, the data would typically be stored physically in a cube Ey 22 © 2014 SAP AG oran SAP afflate company All nights reserved 2014"SAP HANA Scenarios A100 Lessor e tao Seiwa | Ale Data Warts tH, Saseden arts tase — Ly rons == Data entin te orgal eepe tt hae rey Sn wanted befor nang into HANA . » of dt dla mat typcly sre bins poten hans Te warner fale data mart aly contin o tine Brace Ciel data and htt ize vations ro en Direc Extractor Connections (0X0) or ai SaP Binnese Sune arabe com Core Value Proposition of SAP HANA More testy compared to EDW cnvrenment Figure 29: SAP HANA Scenarios: Agile Data Marts Data Warehouse environments are typically inflexible against change. Some be only vo to four slols, during a year. wh, customers report that thers am models can be cl inged Businesses, however. are exposed to constant change, Sales reyons change. product bundling may change. and cost centers are subject to almast constant take place, In these eases, 1 is helpful to have an environment in which models can be adapted easily without impacting the data models in production. and vomnbine it with h angernal i may as well be interesting for business to load external ingernal data sources. These may be benchmarking scenarios in wh data such as sales data is compared tomarket indices ebtained from external sncies, Such data is typically not loaded inte the central data warehouse, but ather gets used by analysts or managers in local env izonments SAP HANA provides a kind of sandbox environment for rapid pratoty ping of new models Example of Agile Data Marts 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 23Unit 1: Introduction and Positioning A100 SAP HANA can host standard anals tie models, pically implemented as a star ‘or snow-flake-schema. A star schema consists of one fact table, and a set of dintension tables (currently SAP HAN. can not support versioned master data that would require a temporal join) + Step! Load the tables into SAP HANA. All transformations take place before Foading the data inte SAP HANA + siep2 Create tribute views for the different dimension tables + Step 3 Create an analy tic view by selecting the Tact table as data foundation. and join dhe aueibute views to the data foundation e — > CT oo = « Data model reflects the level of detail in tata wish cota inthe aka seotaaton —+ ‘No vantoeaton dung oa step ony ae wz Sslecton of velevart dla apa) Realtime repleaten of tect! ta a (GaP Landscape Tantoraton) «Standard oad routines for data whichis rot tm ciel (SAP Data Services) Views calcu results for reports in eal time onthe actual operational data Core Value Proposition of SAP HANA Fal im reporting on operational data Figure 30: SAP HANA Scenarios: Operational Data Marts Ey 24 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: SAP HANA Scenarios You can get several benefits from operational data maris = Most of the technol really suitable for the task at hand, Classie Enterprise Data Warehouse environments are comple and may require significant effort to model ‘operational data marts ss currently used for operational repostin, + operational reports quot directly the database which rans the core business applications. ll the people working on the system may espenence reduced performance. This issue s caused bythe heasy ssorklond foat multiple Wins oon many simall tables, hike itis the standard in ighls normalized data moos + SAP HANA-based operational data marts take the workload of stich reports away fromthe main database, ‘The replication guranices thatthe data in memory reloct te last transactions which took place. And finally in-memory comput Lh solumes of he option o retrieve every detail which is 1g provides very fast results even on hi detailed data, sll prov ida ccomained in the data ¢ SAP HANA can provide r |-ime insights into what is going on in business Example of Operational Data Marts SAP HANA is perfectly suited to hest operational data marts. In contrast to previous example, operational data marts are not based on analy tie (cenormalized) data models, but rather sun directly on top of the operational data, The operational data gets transformed in a way that is suita query hits the system. The transformed data is never stored in the database. fe 1o answer a query eight when that = Sep i Load the needed tables into SAP HANA. There are s Teading the data al options for Use SAP Landscape Transformation or SAP Sybase Replication Server to enable real-time replication, where changes in the original tables are propagated to SAP HANA instantaneously Use SAP Data Services, standard ETL tool, to load the tables on a regular basis Use the SAP Direet Extractor Connections to extract preprocessed data from SAP Business Suite = Load data from Flat Files + Step 2 Create attribute views forthe different dimension tables + Step 3 Create an analy tie views incorporating the attribute views 2014 (© 2014 SAP AG or an SAP afflate company. Allrights reserved 257Unit 1: Introduction and Positioning A100 ° aoc ‘SAP HANA bs sense) Figure 31: SAP BW on HANA @ I + Migration of atbane o SAP HANA requled SAP HANA only runs on SUSE Linux (SLES) Figure 32: Consequences on Existing Landscape when Migrating to SAP HANA + SAP Netwcayer BW on HANA 7-4 SPS is available since the end of 2013, + Before database migration to HANA DB. the SAP Netweaver BW pplication has to be updated to 7.31 > Note: The recommended migration process i 0 ase Data Migaaion Option (DMO) 35 part of Soriware Update Managsr (SUN, Ths nfo process ean be applied ko BW'as well a the SAP Business Ste om ponents Ey 26 © 2014 SAP AG oran SAP afflate company All nights reserved 2014A100 "SAP HANA Scenarios ae Soe ee BSL" for SAP HANA «= Classic Stier architecture «= No change to familiar frontend necessary (though possible) «= Code optimization: Push data- Intensive logic to the database Applications: = SAP Business Suit, powered by SAP HANA = SAP Netweaver BW, powered by SAP HANA ‘DaSL: Dtabee Shared Lary Figure 33: SAP HANA as a Primary Database — Business Suite on SAP HANA, Tew ons | [New Apps (eoue, (Hn tove toee | [Soi 2 Next Generation HANA Apps: = NetWeaver Application Server ABAP leveraging HANA = JOS appe running againet HANA «= Java applications running against HANA Core Value Proposition of SAP HANA = Simplifcation: lean code, ightweight applications Figure 34: SAP HANA as an Application Platform 20a (©2014 SAP AG or an SAP afflate company. All ights reserved 7Unit 1: Introduction and Positioning A100 e Lesson Summary You should now be able to + Explain the architecture of SAP HANA as an accelerator in a side-car seenatio = Explain the architecture of SAP HANA as an In-Memory Database Ey 28 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 Lesson: Rapid Deployment Solutions Lesson: Rapid Deployment Solutions Lesson Overview In this lesson sou will learn about what an RDS means and how you can use it e Lesson Objectives Afier completing this lesson, you will be able to + Explain what an RDS is + Understand how you ean yet and use an RDS to speed up and secure an implementation of SAP HANA, Business Example You want to quickly gain busin implementing a Rapid Deploy ss value from your SAP HANA deployment by ent Solution, Rapid Deployment Solutions Overview SAP RAPID DEPLOYMENT S26 eked (uct adress hemos! ugert bane processes ‘sepeneaser Figure 35: Rapid Deployment Solutions to Meet Specific Business Needs SAP and a Global Partner Evosy stem offer Rapid Deploy ment Solution packages that consist of SAP Software and SAP Predefined services combined with pre-configured content and enablement content With SAP Software, SAP Rapid Deployment solutions provide a reads-to-vonsuime combination of SAP Predefined services. pre-configured ‘content, and enablement content to accelerate the implementation and lower Fish Implementation is supported by standardized methodology and best practices, 2014 2014 SAP AG o° an SAP afflate company. Allright reserved 297Unit 1: Introduction and Positioning A100 improved over decades An optimized mix of global resources, remote support and on-site consulting gives you aceess t© experts who can help you implement Your solution on time and within the allocated buds Each of these solutions includes educational material and training seripts for the functionality that matiers most far users, so that they & te delay s associated wath customized taining, SAP Rapid Deploy ment solubons bring i all together pre-configured software. fived-scope implementation services. and the materials you need for a ful implementation... all ata predicta effectively elimmating cost oversuns and project delays With these solutions, you receive the best oF Uaditional and subscription licensing, models, so you will know Ue cost and scope ef your solution up front. These complete solutions enable the fesibility to accommoda Because SAP Consulting uses pre-config ‘what sou need fo tun your business out of the bos. delivered quickly This pre-configured coment is adding value because if gives you powserful functionality based on the leading SAP ERP rapid-deplovment solution for operational repostin with SAP HANA, ured content, you as a business get SAP consultants only install what yeu need so that you ean start faster with ‘what's more important, and expan as you need fatet. And the bigwest bereft 10 ‘our customers is that SAP Consulting can provide seamless access to SAP ERP. back office mnfornration ‘The pre-configured content allows the preyeet to be quick and lean be: the clearly det methodology. Finals. the flesible software pricing and fixed priced. low cost ees, ensures that your SAP ERP rapi tional reporting, with SAP HANA project will be cost effective, both monetarily as well in torms of Business and UT resourees, Information in realtime se of ied seope, the know ledge transfer to users and the fast-irack ploy ment solution far ope Create flexible analytic models based on real-time and historic business data Minimize data duplication Foundation for new category of applications Figure 36: SAP HANA - Time Becomes Your Competitive Advantage Ey 30 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: Rapid Deployment Solutions ‘Time becomes your competitive advantage Analy information in real-time at unprecedented speeds on large volumes, of non-ageregated dain = Create flesible analy tic models based on real-time and historie business data + Foundation for new eategors of applications = Minimizes data duplication © And sometimes is it not quite easy. Like the following example shows Joi inside calculation view cot perfomance, thu al the joins of attribute views to analyte views {are removed into anajytie views decty in HANA ERP V3. The below diagrams may help yout Understand the change of CA_STOCK_OVERVIEW trom HANA ERP V2 to HANA ERP V3, Figure 37: To be so Fast Like a Cheetah you Have to Know How is the Shortest Way to Your Prey (the Data} 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 31Unit 1: Introduction and Positioning A100 @ et src fA STOOL VERNER Figure 38: The New Quite Faster Model SAP ERP rapid-deploy ment solution for accelerated finance and controlling with SAP HANA is a combination of sofware with the rapid deploy ment solution consulting deliverable to produce the oxerall solution There are the four individual accelerators + Financial Accounting Accelerator + Controlling Acvek + Material Ledger Accelerator aor + Production Cost Analy sis There is also specific coment deli ered. for example + Implementation content like configuration guide + Service content like project plan. consultant guide, or hick off presentation + Enablement content like customer facing material The service has + Fised-soope and fixed-price ser ices for the individual implementation ‘The Service Delivery can be performed by SAP or qualified partner Ey 32 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Rapid Deployment Solutions © ‘Models, Dashboard and Reports, Shipsag 8 Sales Finance Purchasing meee ssosonsbort Fe aoe PorchngDastord > SkeOwven SictOderrione «Now Ueto Frc pendper = Vert race esate vee tne at Se pion Suen Tupentroyineke Sse at rae Top Tntne Pach Oe Orr tnesteate —* Open en eat ‘ace Noerntard nae OrrtetersRenee See tes odlamoniss Feb Cine dpmr Pathe rs. Serge foe sateg Or Hy rove ‘Sacred Fone Yn pon ‘deen oe zai Figure 39: SAP ERP Rapid-Deployment Solution for Operational Reporting with SAP HANA Implementation Content To give our customers as much flexibility as possible we have redesigned our service package by creating a modular oiTenng, With the base package of this rapid deployment solution you can choose up to 5 reports to be implemented. If you need additional reports you can add as many as needed The SAP HANA business content for Sales and Distribution (SD) enables sales managers and sentatives 19 check basic hey figures for sales in real-time. Whereas sales managers use sales analytics to get instant every ring the various performance indicators far their sales te ines focus on detailed checks of the results of their sales a: sales repr information ec salos representa 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 33Unit 1: Introduction and Positioning A100 Reporting templates available for | === Ez ‘all models, Delivered using a = ‘combination of = SAP Explorer Web ntetigence = Crystal Reports = Dashboards ‘Additional delivery options (documented in RDS) = Exporation Views Figure 40: Flexible Reporting Getting Information about the RDS. 8 > tp tservice sap com/SOLUTIONPACKAGE Figure 41: Information about RDS Packages EY 34 © 2014 SAP AG or an SAP afflate company All ights reservedA100 =) Lesson: Rapid Deployment Solutions rn nye oO Raa Se Figure 43: The Way to Get an RDS (2/4) 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 35 ayUnit 1: Introduction and Positioning EY 36 A100 | Seewirom ane ead a Te nee (STEP GUIDE Discover Communicate the Value jure 44: The Way to Get an RDS (3/4) sre etme ate st 6 | eT a ae aa ae eee % Figure 45: The Way to Get an RDS (4/4) (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Rapid Deployment Solutions @ Deploy Solution ‘Activate Solution — Development Landscape CCheck instalation and Landscape Reptcate Tables Import Data Models and SBO BI Repets Pecorm Inia! Data Loas Confirm Activation ‘SAP performs Functonal Test Knowledge Transfer ‘SAP provides knowledge transfert I and Koy Business Users Customer Acceptance Testing CCustomor executes Acceptance Testing Customer performs Acceptance Testing Figure 46: Service Overview - Deploy (1/2) You will quickly. yenerate a meticulous project plan. imcluatin breakdown of activities, deliverables, the kickolT workshop and how much lat finement? What about user acceptance solutions inelude the content to take the guesswork out of scheduling, substituting transparency and predictability that inspite key stakeholders to get on board and pput their support belnind your project. e Deploy Solution Switch to Production ~ Productive Landscape Replicate Tables Import Data Models and SBO BI Reperts & Dashboards pies) Pecorm Ini! Data Loas cut over Create Cutover Pian Execute Cutover Pian Figure 47: Service Overview ~ Deploy (2/2) a detailed ines. When should you schedule should you plan scoping and A Real-life Example of an SAP HANA Implementation with an RDS To complete this overview of Rapid Deploy ment Solutions, here is a short presentation of a real-life business case of an HAN Implementation levera the SAP ERP RDS fos Operational Reporting 2014 (© 2014 SAP AG or an SAP afflate company. Allrights reserved 37 oyUnit 1: Introduction and Positioning A100 @ Industry + Industrial machinery and components *Location + 60 countries + Headquarters in the US “Employees + 15,000 worldwide +Annual Revenue + USS 3 billion Figure 48: Customer Presentation Context: + Customer is using SAP Business Suite + High data volumes * About 2 milion items in Material master data + 1078 of enterprise data in the ERP, increasing by 30% yeor over year Company's top objectives: + Unlock business value of large and growing deta volumes + Support complex business requirements with detailed data analysis at multiple levels + Eliminate IT bottlenecks from reporting processes Figure 49: Project Context and Key Objectives + Implement the SAP HANA platform to support a realtime data environment. + Choose an IBM Systems solution for SAP HANA based on IBM x3950 XS servers. + Provide High-Availabilty with IBM General Parallel File System (GPFS) + Leverage the SAP HANA Operational Reporting rapid-deployment solution + Deploy SAP BusinessObjects Analysis, edition for Microsoft Office, to perform multidimensional ad hoc analysis Figure 50: Project Scope + The RDS supports business analysis for Sales, Financial, Shipping, Purchasing and Master Data, + Itprovides: ‘+ SAP HANA information models + SAP Business Objects reports, dashboards and views + The data models are imported on one appliance and provided ready to run with regular real-time replication of ERP data. + The front-end tool used for reporting is SAP BusinessObjects Analysis, version for Microsoft Office Figure 51: The SAP ERP RDS for Operational Reporting EY 38 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 & Lesson: Rapid Deployment Solutions race set Figure 53: Project Timeline Before SAP HANA Limited report aril-down flexibility Post SAP HANA ‘Top to bottom drill-down in less than 2min Pricing analysis took 6 to 8 months to model Pricing modeling takes 3 to 4 days Loading 600M record in BW took Tworking days ‘The same data load takes 20 hours In SAP HANA. ABAP-bated Inventory reports took | ONY apo WIT SAP HANA eienn fi Multiple sources of reporting Cycle time to reporting is zero Se | Extended population of report Limited report bullding skil set oem Reactive Proactive Figure 54: Before and After the SAP HANA Implementation 20a (©2014 SAP AG or an SAP afflate company. All ights reserved 397Unit 1: Introduction and Positioning A100 Qualitative + Realtime business visibility and an expanded population of report builders. + Broader business insight with top-to-bottom data drill-down capabilties + Suppor for exible analvcal models without IT involvement Quantitative + 10x shorter data oad times + 90x faster report development + 18 reeks from project kckof to go-ive + G weeks to implement the SAP ERP ROS for Operational Reporting on HANA Figure 88: Key Benefits EY 40 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: Rapid Deployment Solutions e Lesson Summary ‘You should now be able to, + Explain what an RDS is Understand how you can yet and use an RDS to speed up and seoure a implementation of SAP HANA 2014 (© 2014 SAP AG or an SAP afflate company. Allrights reserved 41Unit 1: Introduction and Positioning A100 Lesson: Deployment Options Lesson Overview ‘This lesson discusses the different SAP HANA deploy ment options available e Lesson Objectives -Afier completing this lesson, sou will be able to + Explain SAPIIANA deploy ment options Business Example ‘You want to understand the different deploy ment eptions that are available. SAP HANA Deployment Options SAP HANA is available in several deployment options depending on scenarios and business azeds Onpremise = Bare meta /Appianee = Vitualized wth Viware Sphere 1 HANA taores datacenter Integration ondanand coud 7 HANA Erne Cou * paar Eaten 1 hana One + vt emmy 1 Wh prema sab eel 1 HABA TEAaptance orotate (SAP store), cectes TEA Test an Eaton Agere mac Figure 56: Overview of Deployment Options ry on-premiselPrivate Virtual pvaPublic aed ered rors Cio Ey 42 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Deployment Options 6 SS. =a students, data xoloration projets te = = Software's tree, developers pay loud Shut provider for eorver usage erers a Focused on smalltomid-sized deta ‘eotpi, wth non predutve use only = = Community supported through = ‘ntputsaphana comcloud — Avaliable on 4 diferent pubie clus http:/idevelopers.sap.com/hana providers Ket covroe liane EB Figure 87: SAP HANA Developer Edition @ zen ee erasers = — peta sais selmi sr 0D) See creates = a Ate Reaunden @ Public, VEC ce we beet | Cored ¥ seth anes Cnacener OBEY ec Netcore Figure 58 SAP WANA One 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved BaarUnit 1: Introduction and Positioning A100 Enterprise ctica, global ‘lacticty = Glotal avaibity (4 datacenters in US and Europe, 2 mere planned in APJ} Custom data center arangements fr compliance Advanced business centiruty and support ® Standards-based cloud operation "© Monty external penetration tests ‘Open for any data footprint Ea eed = Any vad SAP HANA rac] ‘Tahir se posesenest onteeahns ‘sgnton ‘SAP HANA Cloue Platform oad tg 8 ange secs canon Seis Figure 59: SAP HANA Enterprise Cloud Ey 44 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Deployment Options eo Lesson Summary You should now be able 10: + Explain SAP HANA deploy ment options 2014 2014 SAP AG o° an SAP afflate company. Allright reserved 45 SyUnit Summary A100 @ Unit Summary You should now be able 10 + Explain the commen pain points in a system sie database + Explain how SAP HANA can handle the pain points and help to improve profit = Explain the architecture of SAP HANA as an accelerator in a side-car + Fyplain the architecture of SAP HANA as an In-Memory Database = Explain what an RDS is = Understand how you can get and use an RDS to speed up and secure an implementation of SAP HARA = Explain SAP HANA deployment options EY 46 © 2014 SAP AG or an SAP affliate company All ights reserved 2014SAP HANA Studio Unit Overview ‘This unit is an introduction to SAP HANA Studio e Unit Objectives Alter completing this unit, you willbe able 0 + Understand the structure of SAP HANA Studio jure Perspectives cry Unit and a Package Unit Contents Lesson: SAP HANA Studio 48 Procedure: Exercise 1: Getting Started with the SAP HANA Studio .62 2014 (© 2014 SAP AG or an SAP afflate company. Allrights reserved 47 oyUnit 2: SAP HANA Studio A100 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. Developers. @ Lesson Objectives After completing this lesson, you will be able to + Understand the structure of SAP HANA Studio + Coni sure Perspectives + Create Delivery Unit and a Package Business Example You are a consultant ata cl Studio site, and itis the first time you launch SAP HANA, ‘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 SAP HANA Studio © PO Overview Pe ee eee [camera or SAP Hann storm ED Travan re te [piven teqiernttataincalners Figure 60: The SAP HANA Studio EY 48 ©2074 GAP AG or an SAP affiete company All ights reserved aoeA100 Lesson: SAP HANA Studio ‘The SAP HANA Studio is delivered as part of the SAP HAN. installation package. and provides an environment for administration, modeling. development and data provisioning. I can be installed on any client PC that has a connection 16 the SAP HANA system ‘The SAP HANA studio is Java-based application that rans on the Eclipse platform, For more information on the Felipse IDE (Integrated Development Environment). hupywwcclipe.ore) 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 Ul 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 the SAV” HANA Administration Console perspective Each view can be moved around via drag & drop. You eam also customize @ perspective by adding or removing views, seo Teer Figure 61: Perspectives are Based on Views 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 497Unit 2: SAP HANA Studio A100 Hore is an example of some perspectives that are available in the SAP HANA Stuutio, + SAP HANA Modeler ie SAP HANA Modeler perspective is used by Data Architects to ereate Information Models, + Administration Console The Adminisiration Console perspective is used by SAP HANA, Administrators to administrate and moniter the whole SAP HANA system + Ressourees The Ressonrves perspective is used to organize files, such as test files. sul scripts. and so on. by projeel + Other perspectives Some perspectives in the SAP HANA Stuclio are designed for HANA applications development, Java development and Lifecycle Management eae Figure 62; Opening a Perspective “To opon a perspective, choose Windows — Skuse Perspective, then select a perspoctive from the lis, or choose Osi Ini possible ro have several perspective open at the same time, and to switeh from ‘one perspective to another To do so. inthe perspective switcher in the upper-right comer of the screen, choose the perspective You want f0 open Sy 50 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: SAP HANA Studio Figure 63: Adding a View to a Perspective “To add a view to a perspective. choose Windous —+ Show Hew; then select a view from the list. oF choose Oer wx Note: The SAP HANA Studio is base on Felipse. For this reason. you will sce a lot of views inthe Sow Few dialog box. The most relevant ‘views to use when vou start working with SAP HANA Studio are located in the Following folders + SAP HANA + SAP HANA Modeler + Halp (Chea Sivets and Help views) + General (Project Explorer and Properties views) 20a 2014 SAP AG or an SAP afflale company. All ights reservedUnit 2: SAP HANA Studio A100 @ fo Sates 1 oo Gu-mseses © mo gnnemoa serra © (Catalog! 8S Gate oa 8 B stoemo Sef sytemoal 8 8 vonra Gh mesonosete ‘© © powers ®@ samy Figure 64: Customizing the Systems View Some views can be customized. To do so. choose the View Mer bution and choase Cusiomize View Figure 65: Resetting a Perspective Aany perspective cam be reset to its default views and defimlt layout To do so, choose Hinudow — Reset Perspect Sy 52 ©2014 SAP AG or an SAP afte company All ighs reserved aoeA100 Lesson: SAP HANA Studio Adding a System to the SAP HANA Studio ‘When you sart the SAP HANA Studio for the first time, there is no connection fo any SAP HANA system available, You mus create a first connection to an SAP HANA system Toadd a system to SAP HANA. you must open a perspective in which the Systems view is included, For example +The SAP HANA Adminisir +The SAP HANA Modeter ran Console perspective. pective. To add an SAP HANA system, you need the Following information umber This is a ings the communication port to the SAP HANA system For example, iPyou connect 0 an SAP HANA system with instance OM. the port used {0 communicate with the server will be 3015 + The credentials of a user that is define user must be ative => Note: + eispossibl to cannget o several SAP HANA systems within one single instance ofthe SAP TIANA Stu + You can connect to the same SAP HANA system with to different inthe SAP HANA system. This 2014 (© 2014 SAP AG or an SAP afflate company. Allrights reserved 537Unit 2: SAP HANA Studio A100 ‘There are to main methods to add a system fo the SAP HANA Studio, + Manually With this method. you add one SAP HANA system ata time Inthe Sisients view. I-click any blank area and choose Aad usta. Fill n the server name, instance number and system description, and choose Next = Fill nthe user name and password. and choose Fntsi + By importing a Landscape This method allows you to connect to several SAP HANA sy stems atthe ume time. by importing an xml file generated previously by a landscape export from the SAP HANA Stugio installed on your computer or another one: — Choose f Specify the and choose ah undscape file location, the destination folder for the import ort and choose SAP HANA — Landscape. Note: The landscape smi file does mot contain any password, You will have to specify the user and password for any system axlded 10 the Sistem view The Systems View Oo Wrorenzans HANA Instance () = SSowem User Database Schema rf camese serene content Figure 66: The Systems View ‘The Susien view lists all the systems that have been 1 landseape import), For each istered (manually. or by a sfem, the content is organized as Follows Ey 54 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: SAP HANA Studio In the SAP HANA Studio, one central point of acce is usually placed on the left side of the sereen, isthe Sistems View, whieh + Catalog As in many database structures, the ‘ontains tables, views, indexes and so on. All these objects are orga {0 categorize a database content ed into schemas. Schemas are used lined that have a particular meaning for users, Schemas also help (© d isto the database objcets cori customel Note: From a modeling standpoint, schemas ean help to identify which tables to use when defining information models. But a model mas. Schemas do not limit n incorporate tables from multiple scl your modeling capabrhities, The column views that you ereate are always located in schema SYS BIC their metadata in sehema SYS BE + Content ‘The Contevt Folder of the modeling objects, Note; The physica tables are the only storage ara for data within SAP HANA, All the information models dha will be ereated in the modeler will sult in database views. As such, SAP HANA docs not persist redundant data for each model. and daes nat create materialized ayerevates, atalog is where you store all the HANA-specific + Provisioning The Provisioning folder is essentially related to Smart Data Access. a data provisioning approach in which you can combine data from remote sources (Hadaop, SAP ASF, SAP 1Q) with data of your SAP HANA phy sical tables, by exposing them as virtual tables. Security In the Security folder, the System Administrators define users and roles Workspace SAP IIANA Studio stores your projects in a folder called a worhspase A workspace 1s an ennsironment that maps a local directory (o a pachage hierarchy in the SAP HANA repository. This folder is used by the SAP HANA Studio to sfore design-time objects, such as information views, when sou edit them 2014 (© 2014 SAP AG or an SAP afflate company. Allrights reserved 55 SyUnit 2: SAP HANA Studio A100 ‘There can be several workspaces defined in the configuration of the SAP HANA. ‘Studio installed on your computer. This is relevant when vou work on different projects Note: During this taining, you will only use one workspace, whieh is stored by default in C> PSers train student narnbae) Adbstuctie (where #4 is your System Administration and Monitoring To administer and monitor one or several SAP HANA systems, you can use the Following views, + The Stsvem Monitor view ©The Aadininsiratian view Figure 67: The System Monitor View The Spsteyn Mo landscape By default, all the systems that are listed in the Systems view appear in the Si Monor view. You get the most important information abouts} stem status. 3 as welll as disk space, memory and CPU usa es, You can customize this view by adding or removing columns. To do so, choose: the C re Fewer button, Alternativels. you ean right-click in the Syste Monitor view and choose Configure Table Ifyou want to filter the list of systems that are shown in the view. righteliek in the Sisiem Monitor view and choose Susiem Fitter Ey 56 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 Lesson: SAP HANA Studio systems View Properties Vie Figure 68: The SAP HANA Administration Console Perspective ‘The SAP HANA Administration Console isa perspective that is pre-delivered by SAP ‘This is the main view to administer HANA systems. For example. you can do the follow ing tasks. + Start and stop a spsiem + Cont + Monitor a gystem jure a system, + Backup and restore a system + Perform a problem analysis To open the vlnantstratian jew. you can + Double-click the system an the Sestenr Monitor view + Double-click the system in the Ss The SAP HANA Modeler Perspective ‘When you want to create data models in the SAP HANA Studio. you need to open (or switch to) the SAP HANA Modeler perspective. To do $0, choose Window’ —+ Open Perspective — SAP HANA Model ‘Tho Quick Lameh view is a practical entry point, dedicated to the modeler perspective. From dhs view, you ean create, manage and! transport information ‘models (packages. information views. and so on). define or execute data provisioning. configure the server. access SAP HANA documentation, and so on 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 57aUnit 2: SAP HANA Studio A100 Ee —<—— Figure 89: The SAP HANA Modeler perspective By default, when the Onick Farwich view opens. tis connected to the first SAP HANA system in the Sysfemy view. IFyou want fo change to another sysiem, oF if System You are not currently connected to any system, choose Se The SAP HANA Studio offers other persp synehironizing and more ves for debugging, resource. team mm) Note: I'sou hae cose the Quick Lach view and want to rope you can do one of the following ations + Choose Help > Quick Launch, + Reset the Modeler perspective Sy 58 © 2014 SAP AG or an SAP affliate company All ights reserved 201420a A100 Lesson: SAP HANA Studio a Information Models are orgenized inPockages 2 fom tion ven (2) sear Casoteosty Sess ica a Information views, oot nes soos ot ‘naytc regen, See Procedures, essen a Decision Tables douseco ee home 2S teenie td tate Figure 70: The Systems View ~ Modeling Content The Convent node of the Sistem view displays the data from a data model perspective ‘The information views, alony with other modeling objects such as analy tie privileges or procedures, are organized in packages. Each package is « repository that you can assign to a delivery unit in order to transport the objects it contains The SAP HANA Development Perspective Tho f P HANA Studio includes a development perspective with debugging ietionality 2014 SAP AG or an SAP afflale company. All ights reservedUnit 2: SAP HANA Studio A100 Figure 71: The SAP HANA Development Perspective From the development perspective itis possible to check in and out development ‘objects. connecting to a repository SAP HANA Studio Eclipse) Figure 72: Development Repository Integration x” 60 © 2014 SAP AG oran SAP afflate company All nights reserved 2014A100 Lesson: SAP HANA Studio Getting Help within the SAP HANA Studio The 1 holp when you use the SAP HANA Studio fe several ways +The SAP HIANA Studio Help This 16 classic online help, with steuctured content and search capabilities The content corresponds to the SAP HANA documentation, To open the Heip view within the SAP HANA Studio, choose Help — Help Cantents of Help — Search Note: You can also display the Help content in an external window. To do so. choose the Sens on ar external windine baatton in the Help sioss +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 ean find unler Ad formasion several links to other information source: AP Community Nenwork, Centeal SAP Notes, and so on, To access the SAP Help Portal, fiom the Help section of the Qniek Leanct view. choose Documentation + The SAP HANA Cheat Sheets view A cheat sheet is @ guided procedure « perfiorm some actions in SAP HANA Studio, Each step can be cheeked off when completed Tis display the Citeat Sheets view. choose Window —> Show view — Orher and choose Help — Cheat Sheets There crs. Itcaw guide you to create a new folder or add a mew system to the Systems view. sheet called Aeldiy New Spstemn end Fo 2014 2014 SAP AG o° an SAP afflate company. Allright reserved 61 yrUnit 2: SAP HANA Studio A100 Use TThe purpose of this exereise is to disoover and customize the SAP HANA Studio user interface. After logging on to a Windows Remote Desktop session, you will perform the following tasks + Stat the SAP HANA Studio + Add an SAP HANA System to the Syst + Define SAP HANA Studio preferences + Work with Views and Perspectives vw Exercise 1: Getting Started with the SAP HANA Studio + Create a delivery untt and a package to store the modeling content that you will wate during the course ven by this course Note: As a preliminary step. fill out the missing details below. a the instructor. and use this information or all exereises duri Remote Desktop Alias Remote Desktop User name Remote Desktop Password SAP HANA System Host SAP HANA System Instance ‘SAP HANA System User name P HANA System Password SAP BusinessObjex SAP BusinessObjeet ‘SAP BusinessObjects Password User name Procedure ea Note: Los fie Ge in via WTS is not required for all uaining locations nany 1S using VDD. 1 Log an to the WTS taining, landscape: + From your Windows desktop, choose Start = Common fi Connect to the SAP HANA training landscape + From the Windows desktop af she W'TS taining lanscape, choose Start = Remote Desktop Connection + Enter the Remote Desktop alias and choose Connect Continued on next Ey 62 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 Lesson: SAP HANA Studio Figure 73: Remote Desktop Connection choose Other User, + Inthe target system to + Emter sour Remote Desktop username and password, und choose the Log on) button. Figure 74: Logon Screen You are now in the right desktop to star! working with SAP HANA Start the SAP HANA Studio + Choose Start — Al! Paugramy SAP HANA Siuio 4. Opon the S4P HANA Administration Console perspective Continued! on nex 20a (©2014 SAP AG or an SAP afflate company. All ights reservedUnit 2: SAP HANA Studio A100 Overview {5} oem san tr o-—_. Sepmipnaa Mrmoemeten nee Figure 75: SAP HANA Studio ~ Overview Screen + Choose Oper SAP HANA Administration Console. S. Register a new system, + Inthe Sistemns view, tight System ick in the blank area and choose dd + Enter the Host Name and Jnstance Number as given by the instructor. + Inthe Peseription fickd, enter SAP RANA, + Inthe Locate dropdown list, choose Fnnglish (United States), + Choose Next Continted on next pose Sy 64 ©2014 SAP AG or an SAP afte company All ighs reserved aoeA100 Lesson: SAP HANA Studio Figure 76: Registering a New System 6, Enter your credentials as given by your instructor + Soleet the Anthemticaion hy daaasenser checkbox + Finer your user name ang password as eiven by sour insructor =P Note: Optionally. 1 store your password in he Windows score storage, seleot the Siore nser name and password snsecnre siorage checkbox. This will avoid entering vour password each ime sou start he SAP HANA Studio + Dono use SSL or HTTPS. = Choose Nev = Select the Anto-Recannecs checkbox Choose Fin! Continued! on nex 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved ayUnit 2: SAP HANA Studio A100 ‘tec te pcos race ain, © pantry negate seni 6 pantry abn ete ET 1 Soeurin donned wore Fora 9 5 Figure 77: Connection Properties Change your intial password + Minimum length: 8 characters + Must contain capital and small letors + Must contain numbers + Example: Abed!234 £ Hint: If prompted for a ses No. Note: [your HANA system ss not properly connected to the SAP. HANA Studio (status is red). choose Refrevh from the contest ments IPnecossary. close and reapen the SAP HANA Studio. rity Fallback for sour password, choose Figure 78: Changing Initial Password Continued on next EY 66 © 2014 SAP AG or an SAP atftte company All ights reservedA100 9. Lesson: SAP HANA Studio ferences Cheek the Det i Client parameter in the SAP HANA Studio px. Note: SAP HANA supports modeting using multiple clients in SAP source data, You will lear more about the concept of elem later on in this course + Choose Window — Preferences + Expand the preference te (0 select the SAP HANA = Modeler —+ Derails Model Parameter item. ig in the SAP HANA Studio a | semeti|_ ee z = Figure 79: Default Model Parameters Open the SAP HANA Modeler perspective + Choose available perspectives. 1n Perspective — Other to display all the ‘This includes the pre-delivered perspectives and the ones that you may have created + Choose the S4P HANA Modeler perspective. Continued! on nex 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 67aUnit 2: SAP HANA Studio A100 Ww ao Figure 80: Opening a Perspective Switeh to the SAP HANA Acininissration Console persp In the perspective switcher, located in the upper-right comer of the screen choose SAP HANA Adnan Note: The perspective switcher shows a list af all the open perspectives. Figure 81; The Perspective Switcher Navigate the Sisiems view to display the main seetions of the SAP HANA, system tee, +The Catalog node ©The Content node + Tho Security node Continued on next EY 68 © 2014 SAP AG or an SAP afflate company All ights reservedA100 @ te Syms 5 =o GU-s6a58% ° Lesson: SAP HANA Studio SAP HANA Instance () NAME — Database Objects (Tables. £20 rm rseen 10 has ¢ —— # caaeg ¢_—— Scot <—§ Information Models, 3S moder coat Security Settings 8 oa) ~ Another connection on the same boc SAPHANA Instance 8. seaty Figure 82: The Systems View y stem Administrator has created a ma name is the same as your user name Note: In the Catalog node, the S schema for you. The seh 12. Customize the Sistems view to remove the Secrrity node from the Systems + Inthe Stsiems view, choose the Hew Men button and choose Customize View + Inthe Content tab, deselect the Antiarization checkbox and choose OK Figure 83: Customizing the Systems View Continued on next page 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 69Unit 2: SAP HANA Studio A100 13. Reset the SAP HANA Aulministeation Console perspective + Choose Window + Reset Perspective + Note that the Cheat Sheets view has been closed. Caution: The customized Sestems view has nat been reset So sou must change the customized view to display aygain the Security node in the wee. © In the Spstem view, choose the Hew Merny button and choose Cisiomice View © Inthe Comer tab, select the Authorization checkbox and choose OK Figure 84: Reset Perspective 14. Open the seb ‘ration view for your SAP HANA system + Inthe Systemes view, select the HH ISTUDENT:°) system, + Chouse the Avininisiratian button = 70 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: SAP HANA Studio Figure 85: The Pre-Delivered Administration Perspective 15. Switch back t0 the SAP HANA Madeter perspective and ereate a new Delivery Unit = Ln the perspective switcher, located in the upper-right comer of the serven, choose SAP FENA Madeler Inthe Quick Lanwieh view. in the Seip section, choose Delivery Untts Note: [Fhe Quick Launeh view is not displayed, choose Hs = Quick Leranch Continued on next page 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved nyUnit 2: SAP HANA Studio A100 0 ES Stet Set enn TINE see WL Figure 86: Delivery Units Choose Create Enter the following information Name: STUDENT Ha Responsible: STUDENT## — Version: 2 Support Packaye Version: 7 Choose OK Check that your delivery unit appears in the List, Choose Clove. Continued on nest page Ey 72 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: SAP HANA Studio ——— al fd eee ee — oe SS eee Se SS | [sate Se ot = — sr ee ———— SF —————— mene Se = = = Figure 87: Creating a Delivery Unit 16. Create a new package, Continued on nest page 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 3Unit 2: SAP HANA Studio A100 Figure 88: New Package (1) + Inthe Srsvems view, rightclick the Content Folder and choose New = Package + Pver the follows ing information Name: STUDENTH# Description STODENTH# Ds very unit: STUDENT: (sap.tronsing) Note: Ifyour newly created delisery unit it not displayed in the Pefivers wit dopdown list, you may need to close and reapen the SAP HANA Studio + Choose OK Figure 89: New Package (2) + Check that the new package is now listed in the Content Folder Continued on next page Ey 74 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: SAP HANA Studio Figure 90: New Package (3) 20a 2014 SAP AG or an SAP afflale company. All ights reservedUnit 2: SAP HANA Studio A100 e Lesson Summary You should now be able to + Understand the structure of SAP HANA Studio jure Perspectives very Unit and a Package EY 76 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 Unit Summary e Unit Summary You should now be able to + Understand the structure of SAP HANA Studio + Configure Perspectives + Create a Delivery Unit and a Package 2014 2014 SAP AG o° an SAP afflate company. Allright reserved 71Unit Summary A100 Ey 78 © 2014 SAP AG or an SAP affliate company All ights reserved 2014Architecture Unit Overview ‘This unit provides an overview to the architecture behind SAP HANA, e Unit Objectives Aicr completing this unit, you will be able 10 + Understand the architecture of SAP HANA + Explain the necessity of'a persistence lay er + Understand the difference between data and log volumes + Describe the reboot proce: + Explain the principles of shadow pa + Explain the Concept of Backup & Revovery in SAP HANA + Understand how an SAP HANA database can another pied from one system to Unit Contents Lesson’ Architecture, 80 Procedure. Exercise 2: Working with Catalog Objects 89. Lesson’ Persistence Layer 95 Lesson: Backup & Recovery 100 20a 2014 SAP AG o° an SAP afflate company. Allright reserved 79 SyUnit 3: Architecture A100 Lesson: Architecture Lesson Overview This lesson introduces description of SAP HANA Database architecture and components e Lesson Objectives Afer completing this lesson, you will be able t0 + Understand the architecture of SAP HANA Business Example is to transform his landscape to improxe his global performance and lessen his IT administration tasks, He need to tun to the SAP HANA technology and learn the new architecture of the SAP HANA Appliance Acustomer HANA System Architecture ee co rete or ae ‘unstructured data. SAP RANA Dut ‘ oer. NY —— Settee reer Es Ss Ce ee = eer] |[ate Siceertar™ he SAP Host Age SAPCAR tru |] AP HecAgen) [SAP ost Ago ae (sx? SUD Aa SF UASeas00- ey | Repost HANA 7 Sica feemaermennr| Somme Sharper aw marcvey Figure 91: System Architecture This diagram shows the main components of an SAP HANA. The contig can rely on a single-host running all the components, or several hosts, for performance andor high-ayailabilily purposes. ‘Phe components include the SAP HANA database, that comprises four servers \with specific roles: Index Server. Preprocessor. Name Server and Statisties Server. I'there are several nodes (clustered configuration), the Statistics Server tuns only ‘on the MASTER. not on the of er cluster nodes. EY 80 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 Lesson: Architecture Other componems are dedicated to the landscape configuration and sofware maintenance (Lifecycle Manager. SAP Solution Manager. and so on). Some of them rua only on the MASTER server, Another core component is the shared persisteney layer that enables fail-over and sysiom recovery Figure 92: Index Server Architecture The Indes Server of the SAP HANA database is a core component that orchestrates the database's eperations The Connection and Session Management which creates and manages s and connections for the database clients such as SAP BusinessObjects Reporting tools or appheations The Transact isolation, and ke -oordinates transactions. controls transactional 1s wack of running and closed transactions. The client requests are analy zed and executed by a sct of specialized en and processors that handle Request Processing and Execution Control, Ouee a session is established. the database client typically uses SQL statements 10 communicate with this module, For analytical applications. the multidimensional ‘query language MDX is also supported Incoming SQL requests are received by the SQL Processor. This component excoutes the Dats Manipulation Languaye (DML) statements. such as INSERT, SELECT, UPDATE oF DELETE, Other types of requests are delegated to other 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 31Unit 3: Architecture A100 components. For esample, Data Definition Language (DDL) statements, such as the definition of relational ables, columns, views. ineleses and procedures. are dispatched to the Metadata Manager. Planning commands are routed to the Planning Engine that allows financial planning applications (o execute basic planning operations inthe datalase layer The SAP HANA database offers programming capabilities to execute application-specilic calculations inside the database system, The SAP HANA database has ils own programming languages. SQLScript is used to write database stored procedures. Procedure calls are forwarded to the Stored Procedure processor Incoming MDX requests are processed by the MDX engine and alse forwarded 10 the Calculation Engine. which is @ common infrastructure that also supports SQL Seripi, MD and Planning operations the communication between the that store the Data volume and Transaction The Persistence Layer component man: Index Server and the File Syste Log volume epSIPERP eg.ponSkP oq SAPERP Figure 93; SAP HANA System Landscape Connectivity Overview Ey 82 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Architecture High Availability and Disaster Recovery e Business Continuity High Availability Disaster Tolerance per DataCenter between DsteCenters / ‘SAP HANA Host Auto-Fallover ‘SAP HANA Storage Replication (Scale-Out with Standby) SAP HANA System Replication Disaster Recovery. Recovery of HANA as a rebuld of a server Figure 94: SAP HANA High Availability - High Availability ~ Disaster Tolerance High Availability per Data Center ~ Seale-Out with Standby Available today HW partners: Fujitsu, HP. IBM. mare to come, High Availability across Data Centers — Disaster Tolerance Planned for General Availability of BW on HANA, HW partners, plannod: Fujitsu, HP. IBM. more to come. Solutions depend on HAW pariner technology e High Availability configuration = N active servers in one cluster = M standby server(s) n one cluster = Shared file system for all servers Services Name and index server on all nodes ® Statistics server (only on one active server) = Name server active on Standby Failover ‘Shores Storage = Server X falls it ‘Standby Server = Server N+1 reads indexes from shared storage ‘and connects to logical connection af server X Figure 95: Scale Out ~ High Availability 2014 2014 SAP AG ov an SAP afilate company. Allright reserved 33Unit 3: Architecture A100 =» Name server | Het Index Server + Statstc Server Name Server LA Index Server Host Name Server Index Server Name Sener (active) Index Server (standby Distributed HANA database & even on a single host with shared nothing (SN) concept Standby Host Standby without own persistence Figure 96: Scale Out - SAP HANA Database Landscape High- Availability enables the failover ofa node within ane distributed SAP HANA appliance, Failover uses a cold standby node and automatically Landscape Lip to 3 master name-servers can be defined. During startup one server jets clocted as active master The active master assigns a volume to cach starting nde server oF no volume in case of standhy servers Master name-server allure In ease ofa master name-server failure, another of the remaining name-servers will become active master Indey-server failure The master name-server detects an index-server failure and executes the fatlover During the failover the master name-server assigns the volume of the Failed indox-server to the standby server SY 84 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Architecture @ Different implementation of High Availabilty by HW partners HP, Fujitsu, ete. tem ax Name) Mame Mame] some Inde | aden der | se “saner | sever saver Sever ame | Name Name | sms Sener |Servr Serve Sony Fe | rn | en | insen Figure 97: SAP HANA High Availability ~ Node Failover (Standby) ‘The General Parallel Fi developed by IBM. system (GPFS) is a shared-disk clustered file system ‘Secondary HA Solution Partner HA Solution Partner Figure 98: HANA Disaster Tolerance ~ Cluster Across Data Centers The mirroring is offered on the storage system level. IL will be offered together svith the appliance by an HA-certified partner. The hardware paraer will define hhow this cancept is finally realized with his operation possibilities, moa ©2014 SAP AG oan SAP affilate company. Allrights reserved 35 ayUnit 3: Architecture A100 Performance impact is 10 be expected on data changing operations as soon as the synchronous mirvoring is activated, The impact depends strongly on a lot of external factors like distance, connection between data centers, ete. The synchronous writing of the log, ith the concluding COMMITS is the crucial part here Incase of emergency. the primary data genter is not available any more and a process or the take-over must be initiated, So far a ToL of customers wished fo have 4 mamual 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 disks to the alreads mstalled HANA software and instances, and start up the secondary database side of the cluster. Ifthe host names and instance names on both sides of the cluster are identical. no Further steps with Aubrename are necessary 11 would be possible to run a development and/or QA instance of the thre: tier installation on this secondary cluster hardware, simply 10 wtlize it until the take-over is executed, The take-over then would stop these dev. and/or QA. instances and mount the production disks to the hosts. It would requure an additional set of disks for the des. and QA instance, So far no hot standby via log shipping is available or even log shipping by recovering of log backups on a standby host. This needs some changes in the engines of HANA database which needs time to be realized. Both solutions ae of the agenda of HANA'S future development Data Provisioning Overview " a e ra ewe Figure 99: Data Replication Methods EY 86 © 2014 SAP AG oran SAP afflate company All nights reserved 2014A100 Lesson: Architecture ‘There are different technologies to load data into SAP HANA (different data provisioning scenarios) which are covered in a dedicated unit inthis course: Pa The methods are + Flat fle uplead + SAP Landscape Transformation Replication Server + SAP Data Services + Direct Extractor Connection (DXC) SAP Replication Server eae (SLES 11 $4 = SAP HANA, databace = SAP HANA cent Replication = SAP HANA etulo ‘Agent (HP UNIK = SAP HANA oad SLES, AIX) contaler SAP Host Agent 720 ceed = Sybase Replestion Server 155+ ECOA Figure 100: SAP HANA System Landscape SAP HANA Components 1 SAP HANA studio = SAP HANA cent = Data Services Decioner «= Inforsation Designer Ms Excel 2010 = Web aeoess to BI ‘min ole "= MS Excel 2010 © SAP HANA database: cients 1.0 = Web access to Bl elierss The following tables show whieh components will be installed in an SAP HANA, landscape. depending on the actual scenario, These technologies are rellected inthe different editions of SAP HANA, and correspond to a diferent range of requirements from the customer. 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 37Unit 3: Architecture @ 8 a ia. [SAP HANA databace . . ore initemery Computing dats plato 'SAPHANA sto / suc epostony . . {GUI/upaatvepoctory for Administration and Liteycle anogemert ‘SAP Host Agent 720 . 5 Enter Li remote service ik startstop through HANA ‘Studia LVI frter SAP Soiaion Managorimtegraion ‘SAP Solution Manager Diagnostics Agent 7.20, . a Provides monitering tao SAP Solution Manager ‘Software Update Manager for SAP HANA . . ‘tows dowriond and implementation of SAP HANA updates ‘rom wity SAP HANA se Lut smuctare . . Machine readable product eeseipter, stored ne system WLS chen itares end UI bling leks for seach and rates ‘SAP HANA Appleton Function Linaies sos ftom SaLSergt ‘SAP HANA rect Extractor Connector . Ester ‘SAP HANA lent . Provides standarezedintrfaces for programming aginst SAP HANA, ‘SAP HANA let package for MS Exes! a Cptimizes SAP HANA cient package fo ue wih Mieroro Excel {GU for Administration Modeling andLifecyee Management of SAP HANA SAP HANA studio SAPUIS plugin . [SAP WANA stuto Ut Dovelpmant Took for HTALS ‘SAP HANA studio epenitory 5 -Evpse Upaterepostiony to dstibut Stuaio updetes ina andscope |SAP HANA Inermation composer . ‘Wo tnce rontond for end-sers LET Rep Serer (7.2031 Kore ‘Spports SAP snd non SAP source systems Yo oad dats into SAP HANA Lr Replication Assn Tobe nstaled on source system ‘SAP bata Servicer [ETL Tool or loading data info SAP HANA Figure 102: Bill of Material / SAP HANA Peripheral Components A100 EY 88A100 Lesson: Architecture Exercise 2: Working with Catalog Objects Use Aer complet this exercise, sou will be able to + See whether the content of a able stored in rows or in columns in the SAP HANA stores + Display the stmetre of a table + Identify what indexes are defined for a table + Proview the content ofa table During this exercise, you will use ua tables fon the TRATNING schema + Table MARA. This is the table that contains all the proxduets in. an SAP ERP databas + Table HANA SEARCH DATA Procedure 1 Start the SAP HANA Studio and log on to the SAP HANA system, + For this exercise you can use either the SAP HANA Administration Console perspective or the SAP HANA Modeler perspecti + So let’s start looking for table MARA 2. Display table A/4/e4 inthe Catalog tho the HANA system Hint: To find the MARA table easily. you will apply a filter to the list of abies. = Inthe Spvvemy view, expand the catalog to display the content of the ales node for the FRAINING schema = Rightslick the les node and choose Fiters Continued on next 20a 2014 SAP AG o° an SAP afflate company. Allright reserved 39 SyUnit 3: Architecture A100 © fe the filter pattern Mand choose OR + Double-click the fables node The table list is now filtered and displays only tables a few tables. including table MARA. EE Wome Figure 104: List of Tables 3. Open the definition of table MARA and identify the storage spe + Rightlick table MARA and choose Open Det Continued on next page 7 90 © 2014 SAP AG or an SAP atftte company All ights reserved 2014A100 Lesson: Architecture @ wre meee _ a = | Figure 106: Table Definition + This sereen shows the table structure that is, al dhe columns of the table with their pes length, and so on + The table type (Column store oF row store is display inthe top-right ‘comer of this screen + Here, you soe that table MARA is using the column-hased storage pe 4. Identify the key columns of table MARA The Key fields of the table sre marked in the Key columa, + For table A/4RA, the hey columns are MANDI? (elient) and MAINE (material number) Continued on nest page 2014 2014 SAP AG ov an SAP afilate company. Allright reserved 1Unit 3: Architecture A100 6 00 (STUDENTED) waeisnt eon aleve Figure 107: Key Fields Preview the data of table MARA In the context menu for the table, you ean use one of the follow ing options + Opes Content. to simply display the table content + Oper Pata Preview to explore the table avy data (at table view), build a quick report on distnet values. or build an analysis (such asa chart or table) based on the data like in @ BI tool yatents Hore, you will use the data preview and display raw data LARAtab nd choose Open Date Preview ‘Open the definition of table HANA SRARCH DATA and identify the table type and indexes + Right-click the Febles node and choose Filters + Enter the filter patton HANA and choose OK. + TF needed. to display the filtered table list, double-click the Zabes node: Right-click table HANA. SEARCH DATA and choose Open Defination, — = ot Figure 108: Table HANA_SEARCH_DATA + Identify the ype of the HANA SEARCH DATA table + ‘To display the list oP indeses created on the table, select the Indexes tab, Continued on nest page Ey 92 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Architecture Your observations should be as follows + The table is a row-store table + There are no indexes defined 2014 (© 2014 SAP AG or an SAP afflate company. Allrights reserved 93 SyUnit 3: Architecture A100 © Lesson Summary You should now be able to necture of SAP HANA + Understand the Ey 94 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 Lesson: Persistence Layer Lesson: Persistence Layer Lesson Overview ‘This lesson explains how the data persistence works in SAP HANA and present the role of each component of the persistence storage layer, Lesson Objectives After completing this lesson, you will be able te + Explain the necessity ofa persistence layer + Understand the difference between data art leg volumes, af + Describe the reboot pro a power fiilure + Explain the prinsiples of shadow pi 5 Business Example Asa SAP HANA Datibas, persistence works, to be ah of a power Failure Administrator, you need to understand how the data o know how the system will recover in the event Persistence Layer Components The persistence liver of SAP HANA relies on Data and Log Volumes. The in-memory daia is regularly saved to these volumes 20a 2014 SAP AG o° an SAP afflate company. Allright reserved 95 SyUnit 3: Architecture A100 Data: SOI sta and undo og hnformation Acstonal HANA information, such 3¢ modeling data Kept in-memory to ensure maximum Memory performance Woe process is asynchronous, ‘ ee FE + Dray svediopenitt sage an IMermation soit Reg automate rareaton ome ° Oyslial orerwite (only ater backup) exert Tcpremcivenemne | A oe reenact cee = Automatic Persistent Storage Atleast evry 5 minutes (customizable) Figure 109: SAP HANA Persistence ~ Data and Log Volumes SAP HANA folumes are used as follows Data and log + Ona regular basis, data pages and before images (undo log pages) are written in the data volumes. This process is called a Savepoint = Betcen two savepoints. after imayes (redo log pages) are written in the log volumes, This is done cach time a transaction is committed ‘The savepoint process rel @ ns tevtt awe 5 to a concept called Shadow Memory ‘Acute kta revert medion orpones ‘etemine og poston amemoer oan vansoctons IE SoraPoae ‘copy mated pags na nigger wre & rosrnpage ti? ted age At Irresesovepot veson a. ava" ae om ea “Savepoin i sina to Copy en vite Figure 110: SAP HANA Persistence - Shadow Memory Concept, EY 96 © 2014 SAP AG or an SAP atftte company All ights reserved 2014A100 Lesson: Persistence Layer Fach savepoint consists of 3 phases Phase #1: Identify the maviified pages = The system determines which pages hve been modified since the last saivepounl., The sav epoint coordinator triggers writing of these pages. Phase #2: Prepare write operations to the disks + Aconsistent change lock is acquired — na write operations are allowed, + All die modified pages identified danny plase #1 are written to a temporary butler +The list of open transactions is retrieved + Row store information for uncommitted changes made during phase 1 is written 10 disk + Current log position is determined (log position from whieh logs must be read in case of restat) + Change lock is released» write operations are allowed again Note: The purpose of phase #2 is to Jock write operations in the system for as little time as possible Phase 43: Write to the disks +The following cata is written to the disks Temporary bulfers created in phase 2 List of open transactions + Row store ch point is invoked = Log queue is Hushed up to the sevepomnt log position + Restart record is written (containing, for example. the savepoint log positio ‘Shadow paying is used to undo changes that were persisted since the last savepoint. With the shadow page cone: fare not overwritten unt the nest savepoint is ‘pt. physical disk pages written by the last savepoint sfully completed. Inste new physical pages are used to persist changed lo, saavepoint is complete. tivo phy sical pages may exist for one logical page: al pages, Limi the next + The shadow page, which still contains the version of the last sav epoint + The current phy sical page which contains the changes written to disk after the last savepoint 20a (© 2014 SAP AG or an SAP atflae company. Allrights reserved 97 SyUnit 3: Architecture A100 System Restart Procedure Aor a restart the spstem is restored from the savepoint versions of the date pages. This wy all data changes written since the last savepoint are not restored Afier the savepoint is restored, the log 18 replayed 10 restore the most recent committed state @ Reboot or Power failure deletes in-memory data ‘System is normally restarted (jazy restart to keep downtine short {ables with preload flag + subsequent requested tables are loads frst) System i restored to the ela jut Before the fale (except non-committad ‘wansections) “The recovery uses: 1 Last data savepont 1 Log between the last data savepoirt and the time of falure (Contains the data changes ofa committed traneactions upto that point) Data savepoint Log writen Powe faire to persistent storage to pesitent storage (commites warssctione) Figure 111: Persistence Layer in SAP HANA Database ~ System Restart ‘The system restart includ the followin actions, + Restore data Reload the k Seach the undo log for uncommitted transactions saved with last saxepoint (stored on the data volume) and soll them back: 1 sav epoint = Searels the redo log for committed transactions since last savepoint {stored on the log volume) and re-execute them + Loael all the tables of the row store into memory + Load the tables of the column store that are marked for preload into memory Note: Only tables matked for preload are loaded into memory during startup. Tables marked for load memory al first access nt demanel will only be loaded ito Ey 98 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: Persistence Layer e Lesson Summary You should now be able to + Explain the ne + Understand the difference between data and log volumes ity ofa persistence Ia + Describe the reboot process after a power failure + Explain the principles of shadow pag 2014 2014 SAP AG o° an SAP afflate company. Allright reserved 99 7Unit 3: Architecture A100 Lesson: Backup & Recovery Lesson Overview ‘This lesson explains the concepts of backup and recovery in SAP HANA. and the methods to copy an SAP HANA Database e Lesson Objectives After completing this lesson, you will be able to + Fyplain the Concept of Backup & Recovery in SAP HANA + Understand how an SAP HANA database can be copied from ane «stem fo another Business Example In case you need 10 create, of efiesh, a copy of another environment, for esample, to refresh a testing environment based on the productive environment, vou can use the SAP HANA Backup and Recovery Features. Additionally. ia disk failure happens. you need to Know wfiae data can be recovered Database Backup © From persistent storage to externa backup destinations Using database futons (GAP HANA studio) From porsctnt storage to extemal backup detinations Using database functions (GAP HANA studio) Manual copy of eoniguraten fies o extemal backup destination Persistent Storage Daa cont vvoumes cn Log Backup Data Backup Sera Figure 112: Content of a Full Database Backup Ey 100 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Lesson: Backup & Recovery A database backup consists of the following steps + User starts backup with the SAP HANA studio + Database triggers a global database snapshot (backup manager in master name server) + Commits forall ta ction ate put on hold + Master name and indes serversicreate snapshots oftheir persistent storage + Commits are allowed again + Master name sorver and index servers write snapshots to backup destinations ‘The SAP HANA studio monitors the progress of the backup. ‘To ensure an easier recovery. we tecammend that you doa manta backup of the configuration files every time a data backup is earried out, This must include the following folders + Jusr/sap! (without sub-dizectories) Figure 113: Backup Information in the SAP HANA Studio 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 101Unit 3: Architecture A100 ‘The SAP HANA studio provides information on the backup overview tab. + Progress of the currently running data backup, with information on the services included in the backup + Last successfial data backup with information on startiend tine. duration, size, and throughput + Detaled information on this last data backup (choose More sformation i @ ‘Some <= = oi aes Bombe ween aN ay | Bameo? mmm mote igi | 2S (tone he bap Figure 114: SAP HANA Backup Catalog in SAP HANA Studio The Bachup catalog provides detailed information on data and log backups, such arviend time, duration, size, throughput + From the Sustems view of the SAP HANA studio, you can double-click the Backup folder. whiek is visible only if your user has the BACKUP ADMIN System Provilege + Perdefaul, only data bachups are displayed. ‘There isa check box ta also display log backup + More detasted formation, suel as status. destination type. leeation, and serviees ineluxed in the backup. are available and can be selected Ey 102 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Backup & Recovery Database Copy Prerequisite (until HANA 1.0 SPS5) = Physical layout (number of host) isthe sare for both source and target sytors Procedure = create the target system (tis anew instalation) ® Copy the rogues backups tothe target system backup folder {using operating system ‘commands) = Recover the database onthe target eyster othe desired point in time Poe corey ee oes aS ven backups copy nectar Figure 115: Database Copy Using Backups (Source Database Online) From version 1.0 SPS6 onwards, SAP HANA is able to recover a database on system with less nodes than the source system, This is sometimes referred 10 as “n fom copy”, (with m=) ‘This is useful. for example, when you want to use a copy of a scale-out production system toa smaller QA system, => Noe Before version 19 SPS6, it wats only possible to recover @ database running on a multiple-node s3 stem to a single-node system + IPthe target sp stem has less resourves. for example less CPU and/or RAM. you camnot expect the same performances as in the source system. To copy a database, you must do as follows 1. Create a data backup of the source database 2. Inthe target database, configure {n-m) additional index servers go mateh the souree system configuration ( ini file parameter). You can decide how vou ‘want o disiribute these ines servers aeross the available nodes Recover the data backup of the source database into the target database Note: Before the recovery is executed on the target system, SAP HANA will check why nn configured appropriately 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 103 7Unit 3: Architecture A100 @ 7 ee Node 2 Notes Node = ey 7S : a Data Source HANA databose ecitpe ‘Torget HANA databese ‘wih anode ‘win 2 nodes (eg. PROD) (e9, 0A) Figure 116: Database copy from m nodes to n nodes For more information about Backup and Recovery. see SAP Note 1612148. F4Q. SAP HANA De wave Backup & Recover Database Recovery In case of a disk failure, the system cannot recover by Follow a recovery process. ist a restart You must Disk failure (data volumes are damaged) ‘Syston is rostrodt the sat just before the falure (except non-commited transactions) sod for recovery = Last data backup Log since the lst data backup ‘Assumption: log afea undamaged allog enties stil avalabe (net yet overwritten) Data backup Log weten Dick ature to enernal backup fo persistent storage (data volumes) ‘destination (committed transactions) Figure 117: Recovery Scenario ~ Disk Failure (Data Volume) ‘ample assumes that thore was a disk failure on the dala volume but log volumes were not damaged and not yet overwritten, In this cas, you can consider a database recovery based on last data backup an the online log, Sy 704 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: Backup & Recovery In goneral there are thnoe data sources involved in the recovery process + Data backups stored! inthe file sy stent + Log Backups stored in the file system + Online logs Depending on which data source can be used and what your requirements for the recovery are. the Following scenarios are possible, [Onton Prerequisites [Steps 1 [Restore to state | Data backup | Import savepoint from data backup files nto In data backup data area of databace oosing changes loosing chang Restart database from restored savepoint data backup) Clear ontine log 2 [Recover to last [Data backup Import savepoint from data backup files into committed state |andiog since | data area of database backup Restart database from restored savepoint Replay log trom log backup files available) and online log 3 [Pointintime [Data backup Import savepoint from data backup files into recovery = from time < ty, data area of database Fecovery to state analog for time - ; peeoeery basta for Ue | Restart database from restored savepoint time 4 Replay log from log backup and ontne log unt fi Figure 118: Main Recovery Scenarios The Following diagram gives an overview of the backup and recovery capabilities of SAP HANA Lt Data Backup Log Backup Recovery to last Data Backup Recovery to status before crash 8 §8\8 sig Point in Time Recovery Figure 119: Backup & Recovery: Feature Overview 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 105 7Unit 3: Architecture A100 e Lesson Summary You should now be able to of Backup & + Understand how an SAP HANA database can be copied from one system fo another + Explain the Con ecovery in SAP HANA, Ey 106 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Unit Summary @ Unit Summary You should now be abe 10 1 ihe architecture of SAP HANA + Underst + Eyplain the m sity of a persistence layer + Understand the difference between data and log volumes + Deseribe the reboot process after @ power failure + Explain the principles of shadow pay e Concept of Backup & R sovery in SAP HANA, + Understand how an SAP HANA database can be copied from one sy stem 60 another + Explain d aor © 2014 SAP AG or an SAP affllate company. All rights reserved 107 SFUnit Summary A100 Ey 108 © 2014 SAP AG or an SAP affliate company All ights reserved 2014Modeling Unit Overview In order (o report on SAP HANA you need to create Information Models. This unit will guide you on how to model your Information Models. e Unit Objectives Afier completing this unit, you will be able 10 + Explain the CO-PA HANA ease studs + Describe different levels of modehny + Understand the features of SAP HANA Studio Modeler perspective + Describe the levels of modeling in SAP HANA and understand how the different type of models support eaeh other = Create an Autribute View + Create an Analytic View = Create a Calculation View Display the Data from Information Views Unit Contents Lesson’ Introduction to the CO-PA Scenario 110 Lesson: Introduction to the SAP HANA, Modeler Perspective 8 Lesson’ Levels of Modeling 123 Procedure: Exercise 3: Create the Attnibute Views 141 Procedure. Exercise 4. Create the Analytic View for Actuals 162 Procedure Exercise 5: Greate the Analytic View forthe Plan......173 Procedure: Exercise 8: Create the Calculation View 194 aor © 2014 SAP AG or an SAP affllate company. All rights reserved 109 SFUnit 4: Modeling A100 Lesson: 8 Introduction to the CO-PA Scenario Lesson Overview This lesson looks at introducing the case study for exercises, and a big overview of the different types of models in SAP HANA. Lesson Objectives Air completing this lesson, you will be able to + Explain the CO-PA HANA ease study + Describe ditferomt levels of model Business Example ‘You want to create Information Models to report on CO-PA dlata using SAP HANA, Introduction to the CO-PA Scenario Proftablty Analysis (CO-PA) enables you to evaluate market segments, which can be lassie according to products, customers, orders of any combmnation of tee, of Strategie business unts, uch as sales orgaizations of business areas, vith recpect to your companys peat of contrbsion margin “The sim of the systom sto provide your sales, marketing, produt management and corporate planning dopartments with nfrmatin fo supper infal accounting and decision mating ‘Sis gusty ‘rest mater ost arabe protucton oom Centoxten nargn ati vemead xed proaicton cots (Convbcten rar Dalai nd er tha esse > prota of mrt ren margn mene rene oe el a (Opwatra pt Figure 120; CO-PA Background Two forms of Profitability. Analysis are supported: costing-based and account-based, Costi sased Profitability Analysis is the form of profitability analysis that groups costs and revenues aecording 0 value fields and cost approaches. both of which vou cam deline yoursell, I times to a complete, short-lerm profirtbilily report .ased valuation varaniees you access al all = 110 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Lesson: Introduction to the CO-PA Scenario Account-based Profitability Analysis isa form of profitability analy sis organized in accounts and using an accoua-based valuation approach. The distinguishing characteristic ofthis form is its use of cost and revenue clements, It provides vou with a profitability report that is permanently reconciled with financial accounting, @ (CE4xox-Segment Table 2.9. moe = IDEA (CESxxxx-Summarrization Level Join Profitability ‘Segment Number Cet CEZKaxx Figure 121: COPA Storage Architecture ‘You can \iew an operating concen (reproseated by its segment table and segment level) which is similar to an Infacube, There is one dimension table (the segment table) and a fact table (the segment level) Unlike the fact table ofan Infocube. the key of the seyment level does not only contain the key field from the segment table, but also some other hers (eg. the record type) Characteristics in CO-PA match characteristics (or attributes) in [nfecubes and value fields can be viewed as hes figures with additive aggregation in every characteristic. ‘Summarization levels for an operating concer play the role of the aggrewates for an Infocube with the difference bing, tha mainiwned together with the Infacube itself «that is, all aggregates will contain esactls the same figures than the underlying [nfocube at any tame). while semmarization levels are updated periodically (an most cases once every day) iygreyates For neues ar CO-PA line items are similar f Lines in the QDS, You can view thent as lines in communication structure just before being posted (© ant InfCube. In costing based. as shown, the line items stored in the CELsxxs and CE20xx tables, In Account-basod Profitability analysis. the line items are stored in the CO tables (COBK, CO Header and COFP. CO Line item), 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved iyUnit 4: Modeling A100 @ Product contng Cort conters Orders = © acct ae i =o & ‘igh 3 fi Sal come Vc ERP But how can we find the tables and there dependencies. for all of the ERP applications? Figure 123: HANA and CO-PA as an Example Ey 712 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Introduction to the CO-PA Scenario ERP More than 50,000 applisation tables ‘Can be analyzed with transaction code SO11 Aorgene donne 88 Figure 124: HANA ~ Table Relations in ERP (1) Display 1g/Primting Data Models ‘The procedure 10 be used varies according to whether you know the fall name of the data model. only part of the ne of the data model. or whether sou do not know the name at all Complete Name Known (On the Data Modeler Initial Sereen, emter the name of the data model the Modeling object field Under Selection, choose Data model Choose Dryptay. The Display Data Model Definition sereenappears, of Name Know On the Data Model Enver the part of the name you know in the Modeling object input field Use 10 represent the part you do nat Know (For example, uni Click on the arrow to the right ofthe entry field Initial Sereen, sole Data model under Selection A hit List of all objects corresponding to the pattem sou entered appears To copy the name of the dats model vou require. select the data model by Jing i and activating the Choose pushbutton. The name now appears fon the initial screen Choose Diyptem: The Display Data Model. Definition sereen appears 20a T2014 SAP AG @ an SAP alate conpany Al ighsesened 137Unit 4: Modeling A100 Name Unknown + Leave the input field Modeling object empty on the Data Modeler. Initial Soreen. = Under Selection, choose Dato mace! = Choose Searei, ‘The relevant standard selection sereen of the ABAP Repository Information System appears Enter your selection criteria and choose Program — Execie, A bit list is displayed. Select the data model you require trom the list and choose Display. The Display Data Model Definiticn sereen appears. Dip Oats Moo Hera Start view POG Se eae A tree ERP ee Figure 125: HANA - Table Relations in ERP (2) ey 114 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Introduction to the CO-PA Scenario Hierarchy: Access cess the hierarchy either from the Data Modeler initial screen for fron the dass mode! definition From the initial sereen of the Data Modeler Hierarchy of SAP models You can a ‘You can call the hierarchy of the SAP models directly from the inital sereen of the Data Modeler. Since this hierarchy contains all application models supplied by SAP. you can quickly gain an overview ofall the models or nay gate 0 @ specific model Follow the procedure below Call the initial sercca of the Data Modeler. On the initial sercen. choase Modeling object > S4P Appliconon SAP Avchitecture soe or choose the relevant pushbutton, The hierarchy of all SAP models is displayed Accessing the hierarchy from a specific date model The procedure to be used varies according 10 whether you know the fall name of the data model from which you Wish to a a model hierarchy. only part of the name. oF whether you do not know the name at al Complete name hnown the = On the Data Modeler: Initial Sereen, enter the name of the data model in the Modeling object field Choose Mavieting Object — Dat Model Hierarchy. The Di Moxie}. Hierarchy screen appears. [SD11 | biepey Ont tod: Dstntion Seas cme” a ERP aaa eee Om Oman weet ne Figure 126: HANA - Table Relations in ERP (3) 20a 2014 SAP AG or an SAP affllate company. All rights reserved 115Unit 4: Modeling A100 Part of name known + On the Data Modeler: Initial Screen, select Data model hierarchy under Selection Enter the part of the name you know in the Modeling object input field, Use * to represent the part you do mot know {for example. uni" + Click on the arrow to the right of the entry fick + A hit list ofall objects corresponding to the pattern you entered appears To copy the name of the data mode! you require. select the data model by clicking it and activating the Choose pushbutton The name now appears fon the initial sereen = Choose Maxiefing Object = Datu ode! Hierarchy. The Display Data Model. Hierarchy screen appears Using data from COPA in HANA. Using the knowledge about the Data Model. you will be able to create Information Models basedl on COPA data. Figure 127: Exercise: Enable Plan/Actual Comparison in SAP HANA, Using Data From COPA Ey 116 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Introduction to the CO-PA Scenario eo Lesson Summary You should now be able 10 + Pyplain the CO-PA HANA case study + Deseribe different levels of modeling aor 2014 SAP AG or an SAP affiliate company. All rights reserved 17Unit 4: Modeling A100 Lesson: Introduction to the SAP HANA Modeler © 8 Perspective Lesson Overview ‘This lesson will cover an overview of SAP HANA Studio Modeler perspective. Lesson Objectives Mer completing this lesson. you will be able to: + Understand the features of SAP HANA Studio Modeler perspective Business Example ‘You want to understand the features of SAP HANA Studio Modeler perspective so hat you can build Information Models The SAP HANA Modeler Perspective sar eainseojets | ce ‘isautons | Apteatons Eclipse based modeng environment which Is designed fr technical and power uso. ‘The SAP HANA Modeler & one component am ofthe SAP HANA Studio 1 Modeling "No materialized aggregates oes Suppot for technical and power usere et eel Import ard Export of Data Models ‘sane 1 Anatte Prvieges/ Securty Pesctowes sar = 08 Adminitation Figure 128: SAP HANA Overview xy 118 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Introduction to the SAP HANA Modeler Perspective Figure 129: SAP HANA Studio Modeler SAP HANA Studio is intended for persons with extensive technical knowledge and can therefore be regarded as the mare powerful tool, It oflers more extensive functions as shown below + Creating information objects such as Ausibute Views, Analytic Views, Calculation Views, Stored Procedures and Analytic Privil information models content by perform lofinitions from the source ERP = Processin = Man nultiple administration activ ities imo SAP HANA, ing modeling, = Importing «ah Suudio Loading data into these table definitions 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 119 7Unit 4: Modeling A100 @ © Allows setting of dofaut Valles for tematon Imo created by wer Set‘DetautClen' tothe aa chert sed Se ineastomer ester a rset tne lent onthe User ee Accourt. Sosa Chet a (preterea) *Toceron » Or set he lent n the sc inermaton mac! properties =< == ate al parse Seo ® Ce | Figure 130: SAP HANA Studio Preferences. For data previews you need to add a client fier, ‘There are several ways Set a default client on the model itself + Set dhe default cliont in the Modeler preferences jon properties. (You will need the USER, 1210 change your user session properties) + Seta default client in the user ADMIN privile eo ae eae are enter Saas oasures ~ data that con be quantified and cleisted (non as key figures in SAP BY) Ccatulsted Messures & Restricted Meseurce Views Atrioute Views — i. dmensione ‘Anaiic Views ie. cubes Calculation Views ~ simi t vtual provider wih series concent in BW Graphical ‘Script (SAL Ser, CE Functions) Procedures Functons — re-usable funetonalty ‘Anat Priviege~ scout object ‘Anat Privileges Figure 131: Terminology Ey 120 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Introduction to the SAP HANA Modeler Perspective Modeling Information Moots Information moses aro used to eroste multiple viows of ransational data that can be used for analytical purposes Choice to publish and consume at 4 levels of modeling ‘tote Views, Analy View, Clelation View, Cleat View enhanced wih ‘raitcal Vw Database View / Column Stores Data Preview Physical tables Information Models ImportiExport Models Data Source schemas (metadata ~ mass and selective load Landscapes Data Provisioning (both intial load and replication) Figure 132; SAP HANA Studio Features aor © 2014 SAP AG or an SAP affllate company. All rights reserved 121Unit 4: Modeling A100 e Lesson Summary You should now be able to + Understand the features of SAP HANA Studio Modeler perspective Ey 122 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 Lesson: Levels of Modeling Lesson: Levels of Modeling Lesson Overview ‘This lesson deals with the different levels of information models that you ean c in SAP HANA, You will learn how these models car be ercated und together in order to build a data model that can be consumed by clical applications, e Lesson Objectives Alter completing this lesson, you will beable to + Describe the levels of modeling in SAP HANA and understand how the different iype of models support cach other = Create an Auribute View = Create an Anal tie View = Create a Calculation View Display tho Data from Information Views Business Example ‘You have a yood understanding about the data on which you want to create reports, and you are ready to create new Information Models Before you start. you want to know what types of information models you liave to create in SAP HANA, Overview of Information Models create information Import Source Models System metadata aes ews Phys abe we ‘ee Cons fsa oan 1 nea * Sone te Provision Data Figure 133: Modeling Process Flow ‘The diagram depicts the process flow for modeling within SAP HANA aor 2014 SAP AG or an SAP affiliate company. All rights reserved 123Unit 4: Modeling © © A100 ‘This example focuses on the process of creating Information Nodels and also demonstrates how to export these models for easy portability Stopt: Attribute View Separate Master Data from Fact Data ‘= Buldthe required master data objects a ‘Atibute Views 1 Join txt tables to master daa tables 1 Tfrequed, join master data ables to each ‘other (for example, jin Plato Matera) Step 2: Analytical View Create Cubedtke view by joining attributes Vlew to Fact Data ‘Bul a Date Foundation based on transactional tables s Select Meosures (ey fgures) 1 Select atirbutes IDs (docking pots for Joining attribute view) Join tribe views to dat foundation 1» The Analy View sa kind of star schema Figure 134: Overview of Information Models (1) Step 3 (Optional): Calculation View Ifjoins are not sufficient Create a Calculation Sm View that is something that looks like a View and has SQL Script inside pa = Composit view of other views tables, re-use join, OLAP [a views) Consists ofa graphical an eciptbased eater Cams SOL Scripts a HANA-specf functional script language cares ss Thnk of @ SELECT FROM HANA’ JOIN or UNION two or more data owe = Invoke other functions (bitin CE or generic SL) [pains data tow - apy cena cere ae Figure 135: Overview of information Models (2) Ey 124 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Levels of Modeling Used fr rorievelsecurty me Can be Based on atittes in analyte views seo Can specify values for aparteulr role oom Figure 136: Overview of Information Models (3) ror ‘os "ests Figure 137: Exercise Case Study During the course, sou will work on different exercises in order to create Attribute Views, Analstic Views and one Calculation View, These views are based on data from the CO-PA (Controlling - Profitability Analysis) module of the SAP ERP. ‘The Calculation View will then be used by several reporting tools such as SAP BusinessObjects BI wools and Eseel, 9 analy ze dhe das 2014 ©2014 SAP AG oan SAP affilate company. Allrights reserved 125Unit 4: Modeling A100 © Attribute Views Nhat is an Attribute View? ‘Attioutes 248 content to data, ‘Can be regarded as Master Data tables ‘Can be linked to fac tables in Anaiial Views Figure 138: Attribute Views Overview ‘The main steps to create an Attribute View are as follows, “Table joins sot and Create Data Parameters properties Hierarchies Preview Table Select Save and Selection Attributes ‘Activate Figure 139; Attribute View 1, Set Attribute View parameters EY 126 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Levels of Modeling 6° = echoes reo oe ora pcces Fa a eee 2 Ce Table Joins ate = aes Hieraracties: 4 ates Popatier new = Table ‘Select ‘Save and vy 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 127Unit 4: Modeling A100 Figure 140: Creating a New Attribute View igh a umique name fo the model The allowed characters are- capital letters (A-Z). aumbers (0-9), and underscore Enter a short description for the view There is no multi-language support for this kind of metadata, Select the type of Attribute View Beyond the Stamdard Attribute View (spe. a Fim view creates a mast data view or time cl nnder year. quarter. month, week, day fiscal yeariperiod, and so on), ADs attribute views with exactly dhe same definision in the acteristics ( Auribuce View is a linked copy that allows you ( use evo ‘ame Ana Calculation views mx Note: An Ausibute View car be used more than ange in another ie IPmceded. you can ereate one or several ved Atibute Views You can use an evisting Auribute View asa template For the new one, Use the Copy From Feature. Afier the copy. the two views are independent Note: When using this option, models ean be selected fiom any ppackaye, You are not limited to the models within the selected simply organize Information Models. bit like schemas organize phy sical tables. You must decide which package will contain the Aucibute View. Select tables Ey 128 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Levels of Modeling ‘An Attribute View is based on one or several joined tables The second step is to add tables to the data foundation view. forte neetntnnetomeciie elegance (geet orem a o > a Figure 141: Attribute View - Select Table(s} Note: Tables can be selected thom multiple schemas, and are not linvted to one schoma per Attribute View Add Tables can also be added tothe data foundation by éagging them from the relevant ‘enema the Dtais pane. \alitional tables to view sateton ities whale Figure 142: Attribute View - Add Additional Table 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 1297Unit 4: Modeling A100 ‘To find a table in a schema containing many tables, youcan filter the list af tables + Right click the They folder within the schema, + Fater a filter pattern, + Choose OK The list of tables in the schema is now filtered, + Expand the Trhles folder to display the filtered list of tables, This is a uscfil option if you want to display the table definition first, 1o make sure you add the corsset (able able Joins and Properties = Join Types = = amour = Tet son = Cardinatty = Language Column (fr txt jin) Nat: the ecton which you caw tha jon ates et ile rt) Y Figure 143: Attribute View - Define Join Properties 3. Define join conditions EY 130 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 The Lesson: Levels of Modeling Is used where referential inter i enforces return ros when there is atleast one mach in both tables, inner used even fs nt added the Let Join (or Lett Oxte Jin returns a rows rom the Jot table even ithere are no mathe in the night table ‘The Right Jen (or Right Outer Joi) returns all the rows trem the ‘ight table, even If there ar ne matches nthe lft, forthe test jin, a desertion mapping must be defied For each atibute tis possible to define @deseripton mapping that wil be language-speie Figure 144: Joins Types SAP HANA database supports the following types of joins Amer doer table exactly when lis created 1¢ Inner Join combines records from the left alr the specified criteria are met, Ite enteria are not met, no see in the resale set Left Outer doi A record from the left table is abvays stored in the result set, [fa record fiom the right table meets the criteria, is combined to the record from the lett table, otherwise the columns are empty (null) Right Outer Join A record from the right ble is ahvavs stored in the result set, Ha record from the lef table meets the criteria, i is combined to the record from the right table, otherwise the colunins are empty (aul) Text Join 1s used to join a desertion table fo a master data table. This is ‘a requirement for description mapping. The text join always filters on on language and thus vou need to specily a language column im the text table ‘The language is filtered hased on the view settings (which are per default taken from the user profile of the modeler) 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 131Unit 4: Modeling A100 Text Join J rabie: counray 1 Table: COUNTRY_TEXT ESE US AMERICA US EN. Unite states DE EMEA DE EN Germany Paes EN Jopan P US DE _Vereinigten Staaten DE DE Deutschland JP DE Japan US FR Etats-Unis DE FR Allemagne JP FR Japon 1 Language Column | Text Join on columns COUNTRY KEY and COUNTRY_TEXT. DESCRIPTION ‘we Language column = LANG willbe pefermed according tothe user's or session language, and wil retieve the county description inthe corresponding language Figure 145; Text Join + Rel ‘Tho Referential Join Is semantically an inner join tha integrity is given. which means that the left (able always has a matching contry in the night table. It can be seen as an optimized inner join where the lable isnot checked ino field fiom the right able ws requested assumes that referential in be used, for example, in the Following scenarios: In an Attribut View. 19 join the master data tables nan Analytic view. «9 join the Data Foundation with the relevant Attribute Views (in the Logiea! Jo node) Rete tial Joins are only executed when columns from both tables are requested, Therefore, fa field is selected from the right table it will act similar to inner join, and if no fields from the right table 1s selected it will act siemlar to a Yelk outer Jou. Caution: Referential joins must be used carefully: you have to check tha the database model enforces the referential integrity between the joined ables, 4. Select key attributes, attributes, and set filters as needed. Ey 132 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Levels of Modeling Select Attributes to show up in view = Tho output structure ofthe viow must bo xpi defines s Atleat one hay atrbute fe required = Any number of nonkey tributes may bevetnes Dofine state iter values 1 Canbe based on any table column ' Column does natnaed tobe selected {or output (key tribute) Figure 146: Attribute View ~ Output Field Selection and Filters 5. Define Description Mappings e Map texts to (semantic) keys oat orca tre inthe euptetetre OE Gre ca ste aeeeton mapsng ie 1 Aa ne ot tb an art Hom he aaa ibe res 1 Youcan care pao ion [== oN = Aa the column label nthe Semantics view ee (row one sce) a JODO Necoya Figure 147: Attribute View - Set Description Mapping 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 133Unit 4: Modeling A100 cei ose Figure 148: Map Texts Description mapping is tehnigue to consistently connect the deseription (GoN0 to the semantic hey of an ateibute value MDX per detault only shows key fields ‘= This is governed by an output field property of he atbute = Hlrarchy Active" “fale fornoney fk, 5 field does not show up in Eee! ‘= Example: Product” dimonsion has vo attbutes, but only “Product_rumber appears in excel Figure 149: Attribute Properties ~ Property Hierarchy Active - See Non-Key Fields via MDX Ey 134 ©2014 SAP AG or an SAP afte company All ighs reserved aoeA100 Lesson: Levels of Modeling It views are displayed via Excel, each Adsibure View is represented in Excel as Dimension, For example, you have modeled the Pradnr dimension with attributes Prodct Number and Product Category + Product Numnber is the key + Product Category is a monkey attribute Bach attribute in the list of output elds has among its properties @ seu! Hierarchy Active. This setting is False by default, [Vitis set co False, the attribute will only show up in Excel (via MDX) iP itis a key field of the attribute view. Iv'the property is set 10 1 not a key fle the attribute will show up in Fycel although it is 6. Create Hierarchies (level hierarchies) @ carne Dene aleve Neary a et 1 Need ane atibute per — a herarhy level oa 3 1 Select calumn fom ouput enters SE a structure (49 8 00) ae f= Feed number tev ———— ———— J os = =| oe =e | oe Tate ine crate ae Parameters Properties MMMM prt, Figure 150: Attribute View - Define a Level Hierarchy Note: Currently. hierarchies defined in the modeler are only aocessible ia MDX, 7. Create Hierarchies (parent child hierarchies) 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 135 7Unit 4: Modeling A100 OQ “eas 1 Variable numberof eve for eub-ree within the herarhy ox “eps ant rarmaton een Figure 151: Attribute View - Define a Parent-Child Hierarchy Note: Currently, hierarchies defined in the modeler are only accessible via MDX, 8, Create Caleulated Attributes EY 136 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: Levels of Modeling © Create 2 attibute based on 2 static value or dynamic ccaculation ‘Bult in functions (Conversion, String, Math, Date.) Figure 152: Attribute View ~ Calculated Attributes 9, Saye and Activ e aaa 1 Save button in opt corm of Studio 1» This saves the informaticn model. the metadata ofthe view tht ha just been defined 1 This information modal sels rot visite to reporting tools = Aetvate the view Save (Cnt! +S) 1 Right-lek view and choose “Activate! rom contest menu 1 Tis creates a database view in schema SYS_BIC (so-called ‘olumn view) 1 Name ofthe column vet “SYS_BIC / 1 This column view ean be sezeaeed from reponing ool we the At ribute Tene me rate te patie ecmcie eee ae ‘ie ‘i va sation iio ‘he Figure 153: Attribute View - Save and Activate the View 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 137Unit 4: Modeling @ A100 ‘Save and Activate: Dect activation of an object expects all sub objects to be ‘atvated aeady. ‘Save and Activate al Wil activate sub objets and dependencios as wel oOo- wm|S &~ aes sole a Figure 154: Save and Activate Before a view is visible for reporting, it needs to be activated (deployed), The activation process transtates the metadata defined i the Information Model into a database abject (a so-called column view) A modified version ofa view cannot be a tivated, You always need fo save the view first, There is no implicit save performed when a user tries to activate a modified view, Its not necessary to close the modeling editor ‘Once the view activation is finished. you can see the log of this activation process Cutton in fop-right comer oF the Log view), This aetivation log cher things. the SQL call that has been exceuted in order to er the database. This SQL. call can be a good! start issues with views, The Deployment L view activation ontains, amo ke the views in saint to analy ze technical jl if there is an ereor durin At this point, you have deplosed am Attribute View. You are now able fo report f2et data on this auicibuce, especially by inelucling this v 10. Preview the Data ew in an Analytic Views EY 138 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: Levels of Modeling © Data Preview on the Information Model: I i IAAT | ula o = = oom a o> Figure 155: Attribute View ~ Preview the Data The data preview functionality is useful For confirming that ene has modeled the data the way heishe intended, It ean be done at the Auribute view oF at the physical tables at the Foundation level ‘Thore are three main views one can select from when previewing data + Raw Data ~tab format of data + Distinet Values graphical and tex! Format idemtit§ ing unique values + Analysis — select fields (attributes and measures) to display in graphical format Reporting at this level will not include measures as measures are in Analy tie Views not Auribute Views. To conduct anals sis on measures aecording to the attributes in this Auribute View. you must include this Auributc View in an Analytic View definition 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 139 7Unit 4: Modeling A100 = Gregorian 1 Date (Timestam), Year (2007) = Fecal Figure 157: Attribute View - Time Dimension Attribute Views (2) Ey 140 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 =) Lesson: Levels of Modeling Exercise 3: Create the Attribute Views Use Mier completing this exercise. you will be able to + Add cables 10 an Attribute View + Join tables with a relevant join type + Specify the output columns + Proview the data of an attribute view ‘You are at a customer site and have been asked to build Information Models in SAP HANA in ardor to display CO-PA data, fo be able to display plan ys. actual comparisons by product and country. You will need to create bx Attribute Views: + An Antibute View for the produets + An Antibute View for the locations ‘These Attribute Views, based on several elementary tables from the source SAP ERP. will be jomed later on fo the fact tables of Plan and Act Prerequisites Before you start. review the following diagram to identify whieh tables and columns you will use during this exercise, and how the tables must be joined ‘Customer number (aun) p> Country anon) Region (Recto) ‘iy (ORTeH) i “county key ANDI) 1 Nt coset KT) ‘Material nue QATAR) Language hey (SPAAS). strat desertion (aacr Attibut Terenure ele td Figure 158: Creating the Attribute View - Overview Continued on nest page 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 141Unit 4: Modeling A100 Procedure 1 Start the SAP HANA Studio and open the SAP FLANA Modeler perspective. 2. Inthe STUDENT: package that you created earlier. create a new Attribute ‘View for the Customers with the follow ing properties Field Value Name LOCATION ## Label Customer Location #¥ View Type Attribute View Subis pe Standard + Inthe Content node of the Sistemry view, right-click the STUDENT## package and choose New > Anribate Ties + Enter the required dats + Choose Miish Figure 159: Create an Attribute View Add the following tables from the TRAINING schema to the data foun Table name Content KNAT Customers “Twos! Regions TOOST Couniries Continued on next Ey 142 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 Lesson: Levels of Modeling rm = 5 | Beatin [ swome e SSTUDENT00.LOCATION Figure 160: Adding the KNA1 Table In the Scena pane, click the + sign-on the right of the Mute Foundation nod = Inthe Sere field. enter FNAL = Select the KAA! (PRANVINGH table and choose OK. Click the + sign on the right of the Pata Fowndevion node = Inthe Searei field . enter 7005, = While pressin: = Choose ON 1005U and 10057 tho CtxL key. soleet table Hint: You can also choose date Objects from the contest menw of | the Darr Foradation node. or simply drag the relevant tables from the IRAINING Schema of the eatalog to the Data Konndation node 4. Join the tables as follows, using for each join a ext Join type based on the SPRAY column, and a 1.1 cardinality KNAL is considered as the left table. others as night table Join field LANDI of the left table to field LANDI of table THOSU (country code) Join field LANDI of the left table to field LANDI of table TOOST (country code) Continued on next page 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 143Unit 4: Modeling A100 Join field REGIO of the left table to fiek! BLAND of table THOSU (1 coke), + Inthe Petals pane, dea a connector from the KNALLANDI column tw the THOSU.LAND column, Vo edit the join properties, double-click the new connector In the doin Lupe dropdown list, choose ext Join > Note: The cardinality is automatically set to /:4 In the Femrgviage coftunn dropdown list, choose the SPRAS column + Chose OK + Repeat the previous steps forthe remain 5. Add the Follow ing columns tothe output, The AUINNR column from table KNA! must be defined asa Key Attribute Source Table ‘Columns KNAL + KUNNR [Key attribute)(customer mumber) + LANDI (country) + ORTO! (county) + REGIO wesion) Continued on next Sy 144 © 2014 SAP AG or an SAP affiliate company All rights reserved.A100 @ Lesson: Levels of Modeling Figure 161: Adding Columns to the Output ieelick the KUNR column and + Inthe PRAINING.KNA/ table, vil choose Add Tr Ou Note: Alternatively, you can either double-click the columa name or elick the rounded selector atthe left of the column ame, + Repeat the previous step for all the columns to include in the ouput = Todefine the key attribute, im the Ouipas pane, select the KUNNR column and. in the Properties pame, set the Kev Aniribute property 16 Tre ‘Soest see) a fea r 4 be Figure 162: Adding KUNNR as a Key Attribute 6. Add the following columns (est columns) to the eutput These columns will bbe used as Label columns for other columns, so they must be hidden. Continued on next page 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 145Unit 4: Modeling A100 Source Table ‘Column Content KNAI NAME Customer name THOS BEZEL Region name THOST LANDN. Country name + Inthe TRAINING KNAL table, right-click the NAME? column and choose Auld Tir Ouypt + Inthe Onipur pans, select the VAME columa and, in the Properties pe, sot the Hidden property te Tine mp Note: Hiding dhese columns can also be done inthe following step. inthe Semantics node details. Repeat the previous steps for the other coluinns, Figure 163: Adding Text Fields as Hidden Fields 7. Inthe Semantics, define the Lahef and Label cahuansas follows em) Note: Defining a abo column in an atsibue view allows SAP HANA to map cods fo descriptions Tor example, “US and "United States" ina teanngl manne, Ths mapping can be mrpreted by some Bl chen, suchas nfontaion Desig Too Continued on next Ey 146 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Lesson: Levels of Modeling ‘Column name Label Label Column KUNNR, Customer Number | NAMEL LANDI Country LANDX ORTOI City REGIO Region BEZEL NAMEL Castomer Name! BEZEL Region Name TANDX Coutry Name + Inthe Scenario pane, select the Semantics node + Inthe Colinas pane. for the KUNNR 10M. click the Zabel Coste field and choose NAME! in the dropelown List + Repeat the last step for the nxo other columns. e ea a ponte an ere = = [ote HESS | nae Figure 164: Add Column Labels 8. Save. validate, and activate the Auribute View OR hn-elick the LOCAHON Attribute View and choose Vaticate + Inthe Joh Fog view. on the Curr Model vati ht-click the LOCATION Autribute View and choose Aen + Inthe Joh Log view. om the Current tab, check the status of the last Activation job tab, check the status of the last Continued on next 20a 2014 SAP AG or an SAP affiliate company. All rights reserved 147Unit 4: Modeling A100 ob Log — FE eu Figure 165: Activate the Attribute View. 9. Preview the data of the LOCATION. # Attribute View + Inthe Sestemy view. right-click the JOCATION Attribute View and choose Data Peview + Select the Row Dara tab. Continued on nest page Ey 148 ©2014 SAP AG or an SAP afte company All ighs reserved aoeA100 Lesson: Levels of Modeling Figure 166: Data Preview - LOCATION_## Attribute View => vo ‘The KUNNR. LAND. and REGIO columns have a label colt in displayed in the Data Preview 10, Close the Data Proview tab and the Definition tab of the Attribute View LOCATION 11. Inthe STUDENT package, ete vith the following propertcs a new Attribute View for the Products Field Name Value PRODUCT ## Label Products Description ## View Type Autribure View Subtype. Stanedav In the Content node of the Systenrs view package and choose New — ieclich the STUDENT#!# Few Enter the required dats = Choose His 12, Addl the following tables from the TRALNING schema to the data Foundation. Com ted on next 20a 2014 SAP AG or an SAP affiliate company. All rights reserved 149 SyUnit 4: Modeling A100 Table name Content MARA Product master data MART Product description + In the Scenario pane. click the + Found + Inthe Search field . enter Ma. the Ctx key. select tables MARA and MART em on the right of the Date nv node + While pressi + Choose OK £ Hint: You can also choose Au! Oiyeers from the context menu of the Dato F ony node, or simply drag the relevant tables from the FRAINENG Schema of the catalog to the Date # node. 13, Join the tables as follows, using for each join a Zex1 Join type based on the SPRAS column, anda {:1 cardinality MARA is considered as the left table, MAK as the right table Join ficld MATNR of the left table to field MATNR of table MAKT {product number). + Inthe Derorts pane, draw a connector from the MARA.MATNR column to the MART MATNR column + Tocdit the join properties. double-click the new connector + Inthe fon Tipe dropdown list, choose Jext Join + Inthe Zamguaage eotuma dropdown list, choose the SPRAS column + Choose OK 1M. Ad the following columns to the output. The MA7NR column from table Mai must be dotined as a Key Attribute Source Table ‘Columns’ MARA MATNR [Key attribute] (product MAKT MAKTX (product name) + Inthe TRAINING MARA table, rightclick the MATNR column and choose Add To Onipt + Repeat the previous step for the other colume, + To define the key attribute, in the Onpur pane, select the MAPNR column and, in the Properties pane, set the Key Arrrehate property to Trve ca ned on next page Ey 150 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Lesson: Levels of Modeling In the Semantics. define the Lobel and Labet columns as follows. Column name Label Label Column MATNR Product Number MARTX MAKTX Product Name + Inthe Scenario pane, select the Semantics node © Inthe Columns pane, for the MATNR row. chick the Label Co sm field and choose MAK EY in the dropdown list Save, validate, and activate the Adsibute View. © Right-click the PRODUCT + Auribute View and choose Fitika Inthe’ Lag view. on the Current tab, cheek the status of the last Modeb on job, + Right-click the PRODUCT Attribute View and choose Activate + Inthe Job Fo view, on the Current tab, check the statis ofthe last Activation job. Proview the data of the PRODUCT. ## Attribute View + Inthe Si choose Data Preview eelich the PRODUCT Attribute View and + Select the Ren Pare tab, 1 toss | Blt tes [ROD ommreNONS ark Owdig ‘ommrsommnos emis sane commrormnn07s Congr Fer See Sommmsromnons RSet Doren Baie ter: pas somorenrnsss ey Figure 167: Data Preview - PRODUCT_## Attribute View Cominied on nes 20a 151 (©2014 SAP AG or an SAP afflate company. All ights reservedUnit 4: Modeting Hatoo IS. Close the Data Proview tab and the Definition tab of the Atribute View PRODUCT Analytic Views @ Gets “ Facttabe (date foundation) joined against madeled dmeneions (tiie views) "Data road trom tho joined database tables doing and calculated measures ae evaluated at run time = Mastr date for MOXIBICS are lord in system tables Figure 168: Analytical Views - The multidimensional Model Table joins set ana Calculated Save and Parameters properties Measures, ———Ativato Data Table Select Restricted Selection atnbutes Measures Preview Measures Figure 169: Creating an Analytic View 1, Set Analytic View parameters. Ey 152 ©2074 GAP AG or an SAP affiete company All ights reserved aoeA100 eo x Assign unique name Lesson: Levels of Modeling Ener adescrptin = Mme (GE Serv faa 1 Choose the View TYP® tee a = Orcopy From anata io T] Analy View F cmp [| see st nn ‘ates seen aes ropa ‘eure ‘ea 2 Figure 170; Analytic View - View Creation Wizard 2, Select tables @D reoossoms — = Create a fact table by adding and joining the tables Join attribute views to these tables inthe Logical Join node, ‘Classify the Columns and Calculates Columns, as attributes and measures. You can also create variables/input parameters, and assign variables to the columns in the Semantics node. ropetee 2 sant sant Figure 171: Analytic View ~ Select Table(s) od t "22 Lopiea Join © 0F Oma Featon © % tocanon 26 (ee rronvcr ‘The Analytic View editor helps you create a Fact table by adding and joining the lables in the Data Foundation nade. In addition, you can join attribute views 10 these tables in the Logical Join node, You us the 0! put pane to model various 20a (©2014 SAP AG or an SAP afflate company. All ights reserved 1537Unit 4: Modeling A100 view elements; Columns, Calculated Columns, Restricted columns and Inpat Parameters. In the Sewiortics node, you can classify these Columns and Calculated Columns as attributes and measures, You can also create variablestinput paranteters, and assign variables to the columns in the Semantics node 3 =) rete Prepetes Sen ‘cha oe Figure 172: Analytic View ~ Select Attribute View(s) + Attribute Views can be added (0 the Logical Join Ey 154 © 2014 GAP AG oran GAP alate company Al nights reserved 2014A100 Lesson: Levels of Modeling sof view creation reflected In editor tab Tab Data Foundaton'> Crestethe data foundation (fat able) (Data Foundation) Logical Join —— View —_f \ (Atribute Views) . «Feet Tbe) Figure 173: Analytic View ~ Analytic View Editor 4. Join Attribute Views + The Data Foundation view shows the physical table with all fields that can be incorporated in the final model = The Logical Join view displays only the fields that y eu have chosen to inelude in the output of the Pater Foundation node, as well as the restricwed and calculated measures that have been defined, e ‘Analytic View (Data Foun Festus 1 Add columns Create column ttre ation view) "Croat joins it more than one table “tena sa ‘es sasates Pate Prepotiee teases Figure 174: Analytic View - Define the Data Foundation, 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 155 7Unit 4: Modeling A100 &. Select the columns and set filters 0m “es apna eranetes Proper o Figure 175: Analytic View ~ Join Attribute Views to Data Foundation Define nin conditions and cardinality. ‘The default settings For joins are Referential. Click on the properties tab on the lower section of the sereen to change these settings if necessary Ey 156 ©2074 GAP AG or an SAP affiete company All ights reserved aoeA100 e@ Lesson: Levels of Modeling Aggregation (sum, min, max, [RE aT aunt baa Sypee = ==; Coca, romber z «Expressions Opertre fame FSR ‘= Functions (String, Date TE Mah convreton ye Ss 4 am t= Set med Calculated ‘Save and rantits ——moputies —ameues, Sahat @ > Figure 176: Analytic View ~ Defining Calculated Columns 6, Create Caleulated Columns. 8 Petre patie tease te act Fests aa sien snot fare rv Figure 177: Analytic View — Defining Restricted Columns 20a 2014 SAP AG or an SAP affllate company. All rights reserved 157Unit 4: Modeling A100 7. Create Restricted Measures a oe > ees oe Figure 178: Analytic View - Save and Activate the View In the Semantics view you can classify the Columns and Calculated Columns as attributes ane measures. You can also create variableslinput parameters, and assign variables tothe columns, Figure 179: Semantic View 8, Saye and Activate The Analyte View ean be validated. saved and activated as shown in the slide. When saving, just the metadata of the model is saved but this canmot he viewed from the reporting tools like SAP BusinessObjcets, ‘Once activated it creates a column view (database view) in schema _SYS_BIC Ey 158 ©2014 SAP AG or an SAP afte company All ighs reserved aoeA100 Lesson: Levels of Modeling 6 == 1 Raw data (table diplay) 1 Number of deine values per column = Interactive graphical analysis Figure 180: Analytic View ~ Preview Data of Analytic View ar be used for verification of the designed model. ‘The data preview functionality It has three tabs + Raw Data table fosmat of data + Distinet Values graphical and text Format identf§ ing unique values + Analysis ~ select fields (attributes and measures) to display in graphical format 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 159 7Unit 4: Modeling A100 1 Can ereate fits 1 Oni fer imited rumter of records (but can be changes to united inthe SAP HANA Studio preferences) IESE SUTURE Figure 181: Analytic View Analytical View ‘= Data Preview: Analysis 1 Table, Selection of Chart Types and Temelates JODDDOUS Figure 182: Analytic View You can display the data in a table format ora graph There are multiple graphs types available. Ey 160 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Levels of Modeling Figure 183: EXERCISE - Creating Analytic Views for the CO-PA Scenario 2014 2014 SAP AG ov an SAP afilate company. Allright reserved 161Unit 4: Modeling A100 v Exercise 4: Create the Analytic View for Actuals Use After completing this exercise. you will be able to: + Use fact tables and Attribute Viows in an Analytic View +Join tales and views + Filter the rows of a faot table + Rename columns + Create aleulated columns Now you have created the Attribute Views for Products and Customer locations. you need to create the Analstic View based om Actual data from the CO-PA model, The comesponding fact table is CEIIDEA, The columns directly extracted fiom the Fact table. as well as calculated columns to determine the net revenue and the contebution margin Prerequisites Before you start, review the Follow ing diagram to identity whieh tables, views and columns you will use during this exercise, and how they must be jointed aly tic View will dis ‘cestomernamber KHOR) Hotel BNR) Pari PERIO). Facts ¥ rae + ions Revenve(WOr0) ‘Attribute | ustomer me AMES) ttl nme 8K Views, aunty (LAND) - Region RECIO) ‘yore Coe eon gn) Figure 184: Creating the Analytic View for Actuals - Overview Procedure Continued on nest page Ey 162 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Levels of Modeling In the STUDENT pac! properties. age, create anew Analytic View with the Following Field Value Name CEAL_## Tabet Contribution Margin for Actuals View Type + Inthe Content node of the Sistemis view. rightclick the STUDENT#¥ package and choose New — Analvsie View + Emer the remumad data + Choose Hints z u + x A 5) P20. Reroute iw... 8S mf re Cao Refresh Ss ? (eens EG com ae © a © ana CEmamasn 4 vanin) eer ©) Dedson Table. AB oh Es Figure 185: Create Analytic View CEA1_## Add the Following table fiom the TRAINING schema to the data foundation. Table name ‘Content CENDEA Actual data from the CO-PA model + Inthe Scenario pane, elick the * sign on the right of the Dati Foundation node. + Inthe Score field enter CEL + Select the CAYIDEA (/RAINING) table and choose OR 3, Add the following columns to the output Continued on next 20a 2014 SAP AG or an SAP affiliate company. All rights reserved 163 7Unit 4: Modeling A100 Source Table ‘Columns’ CENDEA + KNDNR (Customer number) = ARTNR (Ma = PERIO (Period) © VKORG (Sales organization) + PLIKZ (Actuals Plan flag) number} + Inthe TRAINING CELDEA table, rig and choose Add To Owapnt A the ANDAR column Hint: To find easily the columns, you ean use the Find Cofiamn button in the upper-right comer of the main pane: Repeat the prev ious step for all the columas to inelude in the output Fron: Fania: . penta: ince Fone: 5 pun: nt Paenetes ‘Swaoar ii ‘Sra | eet] ‘Seat sot abe Sarre oe is Foadoen| SEO eletty Sante Figure 186: Adding Fields to the Output Column 4. To reivieve relevant information, you must filter the CEHDEA table on the Following columns: Consinved on next Ey 164 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Lesson: Levels of Modeling ‘Column Objective PALEDGER [= 01 Use the comect currency type VRGAR =F Use Billing Data Note: Except fiom Billing Data, the CEIDEA table also contains, data from Incoming Sales Order (A), Direct Posting from FI (B). ete + Inthe TRAINING CELIDEA table. ri and choose Apply Filter sht-lick the PALEDGER column + Inthe Operator dropdown list, choose Kael + Inthe Fistwe field, enter 02 = Repoat hese steps for the PRGAR column and enter value F ° ee Figure 187: Data Foundation Tab Add the PRODUCT © and LOCATION > aucibute views to the Logical foun node, + Inthe Se the + sign oa the right of the Lai “iy pane, node In the Search field. enter PRODUCT + Scleotthe PROBUCT ©» STUDENT) auribate view and choose OR: + Repeat these steps to add the LOCATION 6, Joi the data foundation and Attribute Views as follows, using for each join a Referential join wpe and a 1-4 cardinality Data Foundation is considered as the left table. ethers as right tables. Jom field KNDNR of the left table ( field KUNNR of Attribute View LOCATION. ## (Customer number) Continued on next 20a 2014 SAP AG or an SAP affiliate company. All rights reserved 165 SFUnit 4: Modeling A100 Join fick! ARTNR of the left table 10 field MATNR of Attribute View PRODUCT_## (Material number) + Inthe Perais pane, draw a connector from the KNDNR column of the data foundation to the KUNNR column of the LOCATION Attribute View. + Tocdit the join properties. double-click the new connector + Inthe Join Tipe dropdown list. choose Refereatial + Inthe Car = Choose 0K nadity dropeiown list, choose 4° plume, seat the provious steps for the other join. a [> —sruvereexsexnonso >] ea Cistomer Number Figure 188: KNDNR and ARTNR as Attributes Add the follow ing columns (measures) from the data foundation to the output Source Table ‘Columns’ CENDEA + VOLO Gross Reve = VV070 (Sales Deduction) + VV200 (Production Variance) + VV960 (Other Expenses) + Select the Dae: Foundation node + Inthe TRAINING CEDEA table, right-click the F700 column and house Ail fs Onpnt Hint: To find easily he columns, you ean use the Had ( bution in the upper-right comer of the main pane: Ey 166 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: Levels of Modeling Use the search feature to make it easier to find the fields inalarge — # , table | Figure 189: Using the Find Column feature + Repeat che previous step For the other columns to inelude in the ouput 8. Rename the Iv and other columns to give them a meaningtil name sand add a label Name New Name Label PERIO PERIOD Period VKORG SALESORG Sales Organization PLIRZ PLANACTUAL Plan/Actual Indicator Wore GROSSREVENUE | Gross Revenue, Contined on nest aor 2014 SAP AG or an SAP affllate company. All rights reserved 167 SFUnit 4: Modeling A100 vor SALESDEDUCTION [Sales Deduction VvV290 PRODVARIANCE _[ Production Variance W960 OTHEREXPENSES [Other Expenses = Select the Logica! Jain node, = Inthe Or put area (on the right of the sereen), select th In the Properties area (on the right ef the sen TH t0 column em. in the Nome ficld, enter GROSSREVENUE and, in the Lutes field, enter Gross Revenue et the I Repeat the previous steps For the other columns to rename £ Hint: Aliornatively, you ean the Re nue button ia the top of the Output area, and enter the ne gical Join noite, choose names and labels forall the columns atthe same time Figure 190; Rename the Measures Continued on next Ey 168 © 2014 SAP AG or an SAP affiste company All ights reserved.A100 Mo Lesson: Levels of Modeling assign the correct column type to each column in the ‘output the four FFexx columas are measures. other columns are attributes. : tes node + Inthe top-nght comer of the Caunrn area, choose the Auto Assign bution + Check that the fipe columa displays the correct type For each ron + Inoeded, modily the auto-assigned eoluran 1 pes Figure 191 Note: In the Details of the Semantics node, the columns are ied on to different tabs: © On the Loca! tab, you find columns that come fiom the data foundation = On the Shaved tab, you find cs jumas that come from attribute Create three calculated columns as Follows. Fach new columa isa measure and its data type is DECIMAL (15.2), 1 page 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 169 7Unit 4: Modeling A100 ‘Column name Label Formula (measures from Elements) NETREVENUE Net Revenue ‘GROSSREVENUF SALESDEDUC- TION CMARGINI Contribution Margin | | “NETREVENUE® - PRODVARIANCE MARGIN? Contribution Margin 2 ["CMARGINTT - ‘OTHERENPENSES' Select the Logie! Join node eate the NETREVENUE column, in the Oniput area, right-click the Calewlared Coluimas folder and choose New Catendted Column Enter the Name, Label, Dato type. Lengtit, Scale, and Cohann Fype as specified Enter the specified formula, or ereate it graphically based on the available Elements and Operators P Hint: Ifyou enter the formula members manually. each member appears in bold when it has been validated against an available elament Choose OK Repeat the previous steps for the other ca ulated columns. In the Semantics node details, check the type of h column, Ey 170 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Lesson: Levels of Modeling Figure 192: Creating Calculated Columns In the Semantics. change the order of the measures se that they logically represent the ealeulation order. That is, NETREVENUE aller SALESDEDUCTION. and so on, ‘The columns should be erder as follows PERIOD. SALESORGANIZ ATION PLANACTUAL GROSSREVENUE SALESDEDUCTION NETREVENUE PRODVARIANCE CMARGINT OTHERENPENSES, MARGIN? + Inthe Semnatics node details, select the NETREVENUE item and elich the Move Up bation to put the it just afer the SALESDEDUCTION column, ‘© Repeat this step for the other columns. Continued on nest page 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 71Unit 4: Modeling A100 + Righbelick the CAA! Analytic View a ju Log view, on the Current ralidenion jobs tab. check the status ef the last + Rightclick the CEAJ_° Analy tie View and choose Activate jab Log view, on the Current tab. chegh the status af the last Activation job. Preview the data of the CFA * Analytic View sem view, right-click the CRAY Analytic View and a Preview + wd choose Di + Solect the Ren Date tab. + Optionally. create a pie chart with attribute LANDY in Label avis and measure NETREVENUE (sum) in Values avis: go to the Chart tab. drag the LANDY atiribure to the Label axis and the NPTREVENUE measure to the Fine avis, Then choose the chart spe £ Hint: To split a portion of a pie chart you must right-click ic and choose fxplocte Figure 193: Preview the Data yy 172 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Levels of Modeling Exercise 5: Create the Analytic View for the Plan Use Afier completing this exercise. you will be able to: + Use fact tables and Adribuie Views in an Analy tie View + Join tables and views fet table + Filer the rows of a + Rename columns + Create calculated columns ‘Afler creating the Analytic Viow for Actuals. sou must create the Analy tic View based on Planning data, ‘The eoresponding fact table is CF2EDE4. The structure of this Analytic View ts very similar to the one for the Actwals. eveepta Few slight differences that will be bi inthe Following instructions Prerequisites Bofore you start, review the following diagram to identify which tables, views and columns you will use during this exercise, and how they must be joined. ‘Customer number (NONE) att nner (ATH). Period (PERBL) Facte = rac ‘+ oss Revenue (wot) Atabute Customer Name (NAME) Natorl name AKA) Analytic vie Cameco} Figure 194: Procedure 1 Inthe STUDENT package. create a new Analy tic View with the Following properties Contied om next page 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 173Unit 4: Modeling Hai00 Field Value Name cEPL_#F Label Contribution Margin for Plan ## View Type Analviic View + Inthe Content node of the Sysiews view, righeelick the STUDENT package and choose New — Analvvie Vow + Eimer the required dats + Choose Finish Add the following table from the TRAINING schema i the data foundation. Table name Content CEIDEA Plan data from the CO-PA model + Inthe Scenario pane, lich the + sign on the right of the Dara Pond + Inthe Se node. fy field, onter CE2 + Select the CR2IDEA (FRAMING! table and choose OR Add the following columas to the output Source Table ‘Columns’ CERIDEA + KNDNR (Customer number) + ARTNE (Material number) + PERBL. (Period) = _VKORG + Inthe TRAINING CE2IDEA table, rightclick the KNDNR column and choose Add To Owpnt P Hint: To find easily the columns, sou ean use the Fad Caen Dutton in the upper-right comer of the main pane Repeat the prev ious step for all the columns to inelude in the output ‘To retrieve relevant information. you must filter the CE2IDEA table on the follow ing columns, as you did For the Actuals Continued on next Sy 174 © 2014 SAP AG or an SAP afflate company All ights reservedHato Lesson: Levels of Modeling ‘Column Filter condition | Objective PALEDGER [=a Use the comect currency type VRGAR =F Use Billing Data + Inthe TRAINING CEHDEA table, right-click the PAZEBGER column and choose Apptv Fitter + Inthe Operator dropdown list, choose anal + lovthe Fave field, enter 01 + Repeat these steps for the FRGAR column and enter value F 5. Add the PRODUCT © and LOCATION © atwibute views to the Logical Jun node + Inthe Seenarioy pane, click the + sign on the right of the Logica! node, + Inthe Search fiold . enter PRODUCT, + Scleetthe PRODUCT © (STUDENT) attribute view and choose OK + Repeat these steps to add the LOCATION 6. Foun the data Foundation and Attribute Views as follows. using For each join a Referential jom type . and a 1 candy Data Foundation is considered as the lel table, others as right tables, Join fick! KNDNR of the lefi table to fold KUNNR of Attribute View LOCATION. ## (Customer number) Join ficld ARTNR of the [eft table to fold MATNR of Attribute View PRODUCT. ## (Material number + Inthe Perests pane. drass a connector from the KNDNR column of the data foundation to the KUNNR column of the LOCATION. ## Attribute View + Toei the join properties, double-click the new connector + Inthe Jair Tipe dropdown list, choose Referentat + Inthe Cardinatity dropdown list, choose /-F column + Click OK + Repeat the provious steps for tho other join 7. Add the following columns measures) from the data foundation to the compan Contined on nex aor © 2014 SAP AG or an SAP affiliate company All ights reserved 175 ayUnit 4: Modeling 8 A100 Source Table ‘Columns CEAIDEN + VVOL0001 (Gross Revenue) + VWOAIUDL Sales Deduction) + Vw290001 @Pzodution Variance) : 101 (ther Exper + Select the Pte Hondo node + Inthe TRAINING CE2IDEA table right-click the #710007 column and choose Ade lo Opn Hint: To find easily the columns, you can use the F button in the upper-right comer of the main pane id Column Repeat the previous step for the other columns to include in th output Rename the J and aad a label 004 and other columns to them a meaningfal name Name New Name Label PERBL, PERIOD Period VRORG ‘SALESORG Sales Organization’ Vwaron0) GROSSREVENUE | Gross Revenue VWa70001 SALESDEDUCTION | Sales Deduction Vy200001 PRODVARIANCE —_ | Production Variance Vvuson0! OTHERENPENSES [Other Expenses’ Select the Law = Inthe Ougput area ¢ Revenue seal Joan wos. In the Properties area (on the right of the sereen) in the ficld, enter GROSSREVENUE and, in the Lobe! field the right of the soreen), select the FF Wer Gross Repeat the previous steps for the other columns to rename Alternatively, you can select the Fogicat Join noite, choose me button in the top of the Output area, and enter the new names and labels forall the columns atthe same time Cominuedton next Ey 176 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Lesson: Levels of Modeling assign the correct column type to each column in the ‘output the four FFexx columas are measures. other columns are attributes. tes node + Inthe top-nght comer of the Caunrn area, choose the Auto Assign bution + Check that the fipe column d plays the correet type fr each row Figure 195: Object Types Note: In the Details ofthe Semuuies node, the columns prescnted on two differen tabs © Onthe Focal tab, you find columns that come from the data foundation = On the Shored tab, you find columns that come from an attribute views, Follows Fach new oi gpe is DECIMAL (15.2 Create three calculated columns and its d 1 page 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 7Unit 4: Modeling A100 ‘Column name Label Formula (measures from Elements) NETREVENUE Net Revenue ‘GROSSREVENUF SALESDEDUC- TION CMARGINI Contribution Margin | | “NETREVENUE® - PRODVARIANCE MARGIN? Contribution Margin 2 ["CMARGINTT - ‘OTHERENPENSES' Select the Logica Jon node. + Tocreate the NETREVENUE column, in the 0: the Calculated Cofusnry folder and choose New Calcitated € Enter the Name, Label. Pater Tipe. Ler as specified Seate, and Cottam Tipe Enter the specifi aacalable Ele od formula, or create it graphically based on the sand Operators Hint: Ifyou enter the formula members manually. each member appears in bold ashen it has been validated against an available elamant, Choose OK Repeat the previous steps for the other calculated columns, In the Semantics node details. cl sach column, eck the type of Continued on next Ey 178 © 2014 SAP AG or an SAP afflate company All ights reservedA100 Lesson: Levels of Modeling Figure 196: Creating Calculated Columns In the Semantics. change the order of the measures se that they logically represent the ealeulation order. That is, NETREVENUE aller SALESDEDUCTION. and so on, ‘The columns should be erder as follows PERIOD. SALESORGANIZATION GROSSREVENUE SALESDEDUCTION NETREVENUE PRODVARTANCE, MARGIN] OTHERENPENSES, MARGIN? + Inthe Seminites node details select the NETREVENUE item and click the Move Up button to put the it just ater the SALESDEDUCTION, column Repeat this step For the other columns Continued on nest page 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 179Unit 4: Modeling A100 12, Save, salidate, and activate the Analytic View + Rightelick the CEPY + Analytic View and ehoose Fulidate © Inthe Job Log view, on the Current tab, check the status of the last + Rightclick the CEP! ° Analy tie View and choose Aetivase + Inthe Job Log view, om the Current tab. check the status af the last Activation job. 13, Preview the data of the CP ° Analytic View + Inthe Sisiems view. rightclick the CAT ° Analytic View and choose Data Preview © Soleot the Rew Date tab. Figure 197: Preview the Data Ey 180 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Levels of Modeling Calculation Views are used to create your own data foundation using database tables, attribute views, and analytic views to address a complex business uirement 1 column viw that i visible to reporting tools 1 When the view ie acoossed, a functions imply executed The function within the caution view 1 That functions defnedin the HANA-specfic language ‘SQL Script 1 Functions can contain SOL commands SELECT FROM + One can read nt only rom DB tables but ale rom column views created fer analyc ews orate views SQL in functions musi be ‘readonly (no inser, update, delete, drop, .) Functions can eal ether functions 1 Medularize the loge within the calculation vew 1 HANA offers ore-defned functions, efor ereatng a join or union of abies Figure 198: Calculation View = Composite views, e-uses Analytical and Attribute views = SQL/SAL Script / Custom Functions Se OA Figure 199: Two Types of Calculation Views 2014 © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 181Unit 4: Modeling A100 set Deine net Save and Parameters etivate Detine anahg2tind —eatidied cupid review sate ‘columns Figure 200: Calculation View (Graphical) =) Eno vew name an description 1 Name must be aanumere ot SS a SEI @zes. a Sole Grapricaler SOL Sort sgn Eg coer] rae o Cao | Figure 201: Calculation View (Graphical) - View Creation Wizard In SAP HANA version 1.0 SPS07. there are three types of a graphical Calculation Views + Dimension This type of view is 1d to build the equivalent of an Attribute View No multidimensional reporting 1s enabled. and the last node is @ Projection ode: = Cube In the calculation view of type Ce. the final node is an Aggregation node In this se, malltidimensional reporting. #8 possible + Cube with Star Join Ey 182 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Levels of Modeling This new type of Calculation View (fiom SAP HANA 1.0 SPS07 onwards) allows the modeler to join one or several calculated views of ty pe Dimension in the very last stage of the Model calculation, mm Note: With te intotucton of the third t)pe of Caleulaton View Cube with Star fon highs different nodeing approach is posib ‘where moltidimensional reporting would be based on complex trasformation calculations done only on the fet ables (and no the ‘Anat c views) and he atbutes would be joined at the ery end of the caleulton process, ins Sar oi, © Projection nodes can be added to add extra fields For example, setting the Actual versus Planned indicator Drag a connection line between al'the nodes ‘Tre outout node wil represent he dataflow ara end Figure 202: Calculation View (Graphical) - Adding Nodes This editor helps you to build view logic graphically using the tools available in the Designer view for join. union, projection and aggregation operations, You can perform these operations on data sources and/or on (op of ether operations, In the Details view. you define the ouipat of the selected nodes. You use the Output iew to model various view elements. atiibutes, calculated attributes, measures, calculated measures, hierarchies, counters, variables. and input parameters ‘There are different fixe different wspes of nodes aor © 2014 SAP AG or an SAP affllate company. All rights reserved 183 7Unit 4: Modeling A100 ‘View Description | Descriptio Union Used fo combine the result set of ove or more data sources, For example. to know the names of all the emplogees of a store with different branches maintaining their ova employse records table Join Used t0 query data from ive or more data sources. based on some condition. For example. to retr sales of two stores mraintainin sales hasedl on the customer id the lnc idl tables for Projection Used to filer or ereate a subset with only the columns of able of view that are requized For your model For example. selecting the employee name and sales quantity Troma table that eludes many more columas tion Used to sum calculating values ina column, For example, to retrieve total sales of some product ina month, The supported tion types are sum, Min, and MAS ive the data oPa group of rows by Star Join Used only in Caleulation Views of type Cube with Stay Join, and oly as the last caleulation step Gust befare the Semantics node) Note: These node types can be used! at any stage of the calculation view. except the Siar Jor node that 1s only available as the final node ef 2 calculation view of type Cube with Star Join e Select each Projection node and add all the fields tothe output node Ey 184 © 2014 SAP AG or an SAP affliate company All ights reserved 2014A100 Lesson: Levels of Modeling e@ =) Figure 203: Calculation View (Graphical) - Output Node Create a Caloulted Coun called KPLIKZ or each Projotion node "= Actual= 0, Panned Figure 204: Calculation View (Graphical) is possible to create comples expressions to calculate columns Example Expression: midstrstring(* ERDAT”) strlen(string(“ERDAT"))-24 «= Define the UNION by mapping both Projection Nodes tothe target Figure 205: Calculation View (Graphical) 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 185 7Unit 4: Modeling A100 Add the Attributes and Measure to the Output = Activation will ereate the Column view that can be accessed by the frontend tools Figure 208: Calculation View (Graphical) Define Function (input ana set Sutput Save and Parameters Structure) Activate Define Table Write SL Assign ‘Output Sielewert —_Atibutes Preview Structure and Measure Figure 207: Calculation View (Scripting) EY 186 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 Lesson: Levels of Modeling Tradtional Model New Modet “Data to Code” “Code to Data" nN vu bf Code | | n vu code Figure 208: Calculation Views ~ SQL Script Introduction Most often. applications only oflload very limited functionality into the database ng SQL: most of the application logic is normally executed in an application server As a consequence, the data that you want to process needs to be copied from the database into the application server and vice versa, When executing data intensive logic. this data flow between the database server and the application server is very expensive in terms of processor usage, and extremely time-consumi ‘On the contrary, SQL-Seript offers another modeling approaeh, by pushing data-intensive application logic into the database The SAP HANA database exposes a very sophisticated mterfave to the application consisting of many languages. The espressiveness of these languages Far exceeds that attainable with Open SQL ex Note: SQL Script is covered in more detail im course HA30 20a 2014 SAP AG ov an SAP afilate company. Allright reserved 187Unit 4: Modeling A100 e@ Soe Sen si a 6 a e ¢ a g a Se ore Figure 209: Calculation View (Scripting) - Calculation View Wizard Ey 188 © 2014 SAP AG or an SAP afflate company All ights reserved 2014A100 Lesson: Levels of Modeling = Define the Output stuctur (Table Type) af the Calculation View Figure 210: Calculation View (Scripting) ~ Calc View Table Type HP Mint tn onder to get the correct data ps from existing database als, you can do the following + Right-click the table mn the Sisiews and choose Definition + Right-click imo the editor that opens up de tab display in the Hist of table fields) and choose port SOF Define Function (with input and output parameters) The input parameters optiona 1 Can be a scalar valu to pats parameter from the front-end tool inorder to mtr the results (supported by fen-ends). 1 Can bo attie type > to pass results trom ane function nto anather The euput parameters mandatory "= Can be aocaly defined table ype ora global exising tate 1 Defines the structure ofthe turction output emi Figure 211: Calculation View (Scripting) ~ Function Definition 20a © 2014 SAP AG or an SAP alias compery. Allnghs wesenved 189 7Unit 4: Modeling A100 e 1 White the necessary soles statements o query the data and populate the output stuetre SIstudniO4 CF PLAW_ACTUAL SCRIPT 0«_HDB estupewion) necam[——|0 0/28 z Sas Figure 212: Calculation View (Scripting) ~ Add the SQL Script Code Creating the database object for the calculation view |= Metadata (the calcultion vaw coding) has fo be translated inte runtime ‘objects 1 This is done by executing the coding (green arow in SQL editor) 1» Tho defined table type is dropped and created 1» The SAL sero function ie created "= Column views ae crested inthe chosen output schema, View name: > execute the view Figure 213: Calculation View (Scripting) - Creating Run-Time Objects Ey 190 (© 2014 SAP AG or an SAP affiliate company All ights reserved 2014A100 e@ =) Lesson: Levels of Modeling = Select the attributes and measure fo the output node, This wl represent the defeiton ‘ofthe calumn view thatthe frnt end tools wil uy agains. Figure 214: Calculation View (Scripting) ~ Calc View Output Structure Final step ve and activate the calculation view Store the view metadata et Save the view va the save button ave > and ainle = tra coeesaes Figure 215: Calculation View (Scripting) - Save and Activate (©2014 SAP AG or an SAP afflate company. All ights reserved 191