So you receive an invitation to the SAP HANA Developer Access Beta program, but then what? Information on how to use HANA is floating around the net, but as always, you need to know where to look. I did all the research for you. The result is written in this document: 7 steps towards your first HANA report!
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com
SAP HANA Developer Access Beta program - 7 steps towards your first HANA report
Applies to:
HANA 1.0
Summary
So you receive an invitation to the SAP HANA Developer Access Beta program, but then what? Information on how to use HANA is floating around the net, but as always, you need to know where to look. I did all the research for you. The result is written in this document: 7 steps towards your first HANA report!
For those of you not aware what the SAP HANA Developer Access Beta program is, there is an excellent FAQ on SDN which you can find here:
Ronald has been an SAP consultant for over 15 year. He is a Principal Business Intelligence Consultant at Logica, specialised in Consolidation, Planning, BW and BOBJ. He is currently involved in two Business Objects implementations and is SAP BI Practice lead for Logica. In that role he follows the latest SAP trends on Cloud, Mobility and HANA.
SAP HANA Developer Access Beta program - 7 steps towards your first HANA report
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com
Step 2 – Getting big data ........................................................................................................................... 3
Step 3 – Create your table in HANA ........................................................................................................... 4
Step 4 – FTP and import your files into the HANA system .......................................................................... 5
Step 5 – Create an Analytic view for reporting ............................................................................................ 7
Step 6 – Using Explorer to report on your data ......................................................................................... 11
Step 7 – Using Excel to report on your data ............................................................................................. 14
SAP HANA Developer Access Beta program - 7 steps towards your first HANA report
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com
A couple of days ago I was Lucky enough to receive an invitation to the SAP HANA Developer Access Beta program. For those of you not aware what that is, there is an excellent FAQ on SDN which you can find here:
The following paragraphs will describe 7 steps towards your first HANA reporting by using SAP HANA Sandbox.
Step 1 – Cloudshare
In your invitation mail there is a link to cloudshare.com. Create a new account, log on to the desktop and follow the following YouTube video on how to set up your own HANA system:
http://www.youtube.com/watch?v=9NKSYgt5eX4
A great tip is given on how to use remote desktop instead of using the web version which comes with Cloudshare. This is highly recommended as navigation is much easier in the remote desktop.
Logon details for your RDP session are given on the Cloudshare page each time you activate the environment:
Step 2 – Getting big data
So you managed to set up a system and created a RDP session. Good job! Now to find some “big data”. In this article I’m using data which I downloaded from the guys over at Infochimps. I’ve used the following data sources which in total will give me about 20 million records.
The files contain stock exchange data. Great recipe for finding something interesting.
You will be getting a bunch of separate csv files. Use the daily prices ones. For simplicity sake I have merged all files into three separate csv files. Good old DOS can help you with that by using the following command:
copy *.csv importfile.csv
Make sure to execute the command in the same directory your files are placed. Replace importfile.csv with something recognisable (like AMEX.csv, NASDAQ.csv, NYSE.csv).
SAP HANA Developer Access Beta program - 7 steps towards your first HANA report
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com
Step 4 – FTP and import your files into the HANA system
The guys over at SAP will make you do a little treasure hunt in order to find the user id and password for the FTP server. Go into you HANA system and execute the following SQL statement:
Select * from SYSTEM.FTP_SERVER
Et voila, a username and password (masqued for obvious reasons):
Take note of what is mentioned on where to store the files. More specifically you should create a folder on the server equal to your SCN number (in my case S0001432066).
Fire off your favourite FTP client (mine is FileZilla):
SAP HANA Developer Access Beta program - 7 steps towards your first HANA report
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com
Take note that next to my files containing the data there is a so called “ctl” file. These files are required in order to be able to load data in your created (NASAQ) table. The files have the following content:
Import data
into table S0001432066."NASDAQ"
from 'AMEX.csv'
record delimited by '\n'
fields delimited by ','
optionally enclosed by '"'
error log 'Text_Tables.err
NASADAQ is the name of my created table, AMEX.csv the file I will load.
If required, additional information can be found in this post:
Drag your objects into the attributes and measures sections:
Validate, save and activate your view. Well done! We can use this view in Explorer and Excel. Note that you can preview your data and even auto document if by using these buttons:
Important! In case preview fails it is likely you have to “grant” your schema by executing this statement:
grant select on schema s0001432066 to _SYS_REPO with grant option
Replace s0001432066 with your own namespace ofcourse.
SAP HANA Developer Access Beta program - 7 steps towards your first HANA report
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com
As an extra step your could create an extra table which holds the stock names. If you follow the same procedure as for creating the table with the stock records, you can join your two tables and have texts together with the stock names. Sequence for this would be:
1. Create and load your text table
2. Create an attribute view
3. Link your analytic view together with your attribute view
Result would be:
Preview:
SAP HANA Developer Access Beta program - 7 steps towards your first HANA report
SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BA - boc.sap.com | UAC - uac.sap.com
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Oracle Corporation.
JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.