You are on page 1of 208


SAP HANA has two parts
1. SAP HANA Database – SAP HANA Database is a hybrid in–memory database.
SAP HANA Database is the heart of SAP in-memory technology. In SAP HANA,
Database table are of two types.
1. Row Store
2. Column Store
2. SAP HANA Platform – SAP HANA Platform is a development platform with an
in-memory data store which allows the customers to analyze a large volume of
data in real time. SAP HANA Platform works as a development platform, which
provides infrastructure and tools for building a high-performance application
based on SAP HANA Extended Application Services (SAP HANA XS).
There are different types of SAP HANA edition, some of them as below

SAP HANA Platform Edition – It provides Core database technology. It
Integrate SAP component like SAP HANA database, SAP HANA Studio and SAP
HANA clients. It is for customers who want to use ETL-based replication and
already have a license for SAP Business Objects Data Services.

SAP HANA Enterprise Edition – It contains data provisioning (SLT, BODS,
DXC) component including core database technology. It is for customers who
want to use either trigger-based replication or ETL-based replication and do not
have the entire necessary license for SAP Business Objects Data Services.

SAP HANA Extended Edition – It contains data provisioning (Sybase) features
more than Platform and Enterprises edition. It is for customers who want to use
the full potential of all available replication scenarios including log-based

The following diagram shows difference between all editions:

Why to choose SAP HANA?
SAP HANA is a next-generation in-memory business platform. It accelerates
analytics and application on a single and in-memory platform.
Mentioned below are the few reasons why to choose SAP HANA –

Real Time – SAP HANA Provides Real-Time Data Provisioning and Real-time

Speed – SAP HANA provide high speeds processing on massive data due to
In-Memory Technology.

Any Data/Source- SAP HANA can access various data source including
Structured and Un-Structured data from SAP or Non-SAP data source.

Cloud- SAP HANA database and application can be deployed to the Cloud

Simplicity – SAP HANA reduce efforts behind ETL process, Data Aggregation,
Indexing, and Mapping.

Cost – SAP claims that SAP HANA Software can reduce Total IT cost of a

Choice Option – SAP HANA is supported by different hardware vendor and
Software provider, so based on the requirement, the user can choose the best

SAP HANA In-Memory Strategy
SAP HANA has many processes running on the SUSE Linux Server. SUSE Linux
server manages the reservation of memory to all process.
When SAP HANA starts up, Linux OS reserves memory for the program code,
program stack, and static data. OS can dynamically reserve additional data memory
upon request from the SAP HANA Server.
SAP HANA creates a memory pool for managing and tracking the consumption of
memory. The memory pool is used to store all the in-memory data and system
tables, thread stack, temporary computations and all other data structure required
for managing the database.

When more memory is required for table growth or temporary computations, the
SAP HANA memory manager obtains this from the pool.
For an overview, check out the Memory Overview feature of the SAP HANA studio.
To access it, right-click on a System ->Configuration and Monitoring -> Open
Memory Overview in the context menu, as follows:

SAP HANA Advantages

Below are advantages of SAP HANA 

By In-Memory Technology user can explore and analyze all transactional and
analytic data in real time from virtually any data source.

Data can be aggregated from many sources.

Real-time replication services can be used to access and replicate data from

SQL and MDX interface from third party support.

It provides information modeling and design environment.

SAP HANA Compare to BWA (Business Warehouse Accelerator)

SAP BW Accelerator: It is an in-memory accelerator for BW. BWA is focused
on improving the query performance of SAP Net Weaver BW. BWA is
specifically designed to accelerate BW queries reducing the data acquisition
time by persisting copies of the info cube.

SAP HANA: SAP HANA is in-memory database and platform for highperformance analytic reports and application. In SAP HANA data can be
loaded from SAP and non-SAP Source System through SLT, BODS, DXC, and
Sybase and can be viewed using SAP BO/BI, Crystal Reports, and Excel, etc.

Currently, SAP HANA also works as in-Memory database for SAP BW, so in this way
SAP HANA able to improve the overall performance of SAP Net weaver BW.

SAP HANA is an in-memory database and application, which runs on SAP
authenticated hardware and Software.

SAP HANA has three versions – platform, enterprises and extended.

SAP HANA can load data from SAP and Non-SAP data source through SLT,
BODS, DXC, and Sybase.

SAP HANA provides real-time provisioning and reporting.

SAP HANA provides high-performance real-time analytic reporting.

SAP HANA reduces Total IT cost.

OLAP Engine. In this tutorial. Row type storage (For Row Table). SAP HANA Advantages are as mentioned below SAP HANA is useful as it's very fast due to all data loaded in-Memory and no need to load data from disk. Relational database table resides in column or row store. SAP HANA Database consists of a set of in-memory processing engines. Text data and Graph data resides in Text Engine and Graph Engine respectively. SAP HANA can be used for the purpose of OLAP (On-line analytic) and OLTP (On-Line Transaction) on a single database. Calculation engine is main in-memory Processing engines in SAP HANA. It works with other processing engine like Relational database Engine (Row and Column engine). 2. Column type storage (For Column Table). There are two storage types for SAP HANA table. SAP HANA Database runs on SUSE Linux Enterprises Server and builds on C++ Language.Sap Hana Architecture SAP HANA Database is Main-Memory centric data management platform. SAP HANA Database can be distributed to multiple machines. etc. The data is allowed to store in these engines as long as enough space is available. There are some more engines in SAP HANA Database. you will learn SAP HANA Architecture  SAP HANA Landscape  SAP HANA Sizing SAP HANA Architecture . 1.

run length encoding. the whole database objects ( right-clicking and selecting the option "Unload/Load". SAP HANA Server consists of 1. Index Server 2. the user can load and unload data from individual table manually by selecting a table in SAP HANA studio in respective Schema. view. Preprocessor Server 3. dictionary encoding.Data is compressed by different compression techniques (e. When main memory limit is reached in SAP HANA. Statistics Server 5. indirect encoding) in SAP HANA Column store. sparse encoding. Under normal circumstances SAP HANA database manages unloading and loading of data automatically. XS Engine .) that are not used will be unloaded from the main memory and saved into the disk. These objects names are defined by application semantic and reloaded into main memory from the disk when required again. Name Server 4. cluster encoding. However. etc.

Below is the architecture of Index Server. .1.  Index Server processes incoming SQL or MDX statement. Detail of each server is as below It's the main SAP HANA database component  It contains actual data stores and the engine for processing the data. SAP HANA Index Server SAP HANA Database Main server is index server.

5. 4.g. Persistence layer: This layer uses in-built feature "Disaster Recovery" of SAP HANA database.(Attribute view. Repository: Repository maintain the versioning of SAP HANA metadata object e. Stored procedure). MDX Processor queries and manipulates Multidimensional data (e. SQL and MDX Processor: SQL Processor component queries data and send to them in query processing engine i. . Analytic View. 2. In distributed server. SQL / SQL Script / R / Calc Engine: This Component executes SQL / SQL script and calculation data convert in calculation model. 3. 2. Preprocessor Server This server is used in Text Analysis and extracts data from a text when the search function is used. the name server contains information about each running component and location of data on the server. Backup is saved in it as save points in the data volume. This server contains information about the server on which data exists. SQL/SQL Script / R / Calc Engine. Session and Transaction Manager: Session Component manage sessions and connections for SAP HANA database. 3. Name Server This Server contains all information about the system landscape.SAP HANA Index Server overview 1.g.e. Analytic View in SAP HANA). Transaction Manager coordinates and control transactions.

XS Server XS Server contains XS Engine. Below are SAP HANA Innovation in the field of Hardware/Software. in which all data is stored in Main Memory and no need to frequently transfer data from disk I/O to main memory.  Due to change in computer architecture. The external client application can use HTTP to transmit data via XS engine for HTTP server. resource allocation / consumption and performance of SAP HANA system. The only difference is that all data is stored in row storage area in memory of SAP HANA.g. unlike a traditional database.4. SQL Server). There are two types of Relational data stores in SAP HANA: Row Store and Column Store. It allows external application and developers to use SAP HANA database via the XS Engine client. Statistic Server Statistic server is responsible for collecting the data related to status. 5. RAM. (Oracle. and Hard Disk. SAP HANA Landscape "HANA" mean High Performance Analytic Appliance is a combination of hardware and software platform. Row Store  It is same as Traditional database e. the more powerful computer is available in terms of CPU.  SAP HANA is the solution for performance bottleneck. Column Store . where data is stored in Hard Drive.

 In main storage write operations on compressed data will be costly. suitable data compression Method (Dictionary Encoding. Instead. Column store is the part of the SAP HANA database and manages data in columnar way in SAP HANA memory. all changes are written in a separate area in column storage known as "Delta Storage. Read and write operation performance optimized with below two data structure."  Delta storage is optimized for a write operation and uses normal compression. Sparse Encoding. In Main Storage. . We can manually load data in Main memory by option "Load into Memory" and Unload data from Main memory by "Unload from Memory" option as shown below. so write operation do not directly modify compressed data in main storage. Main Storage Main Storage contains the main part of data. Column tables are stored in Column store area. The Column store provides good performance for write operations and at the same time optimizes the read operation.) is applied to compress data with the purpose to save memory and speed up searches. etc. Cluster Encoding. Read operations are allowed on both storages. The write operations are not allowed on main storage but allowed on delta storage. Run Length encoding.

When we want to move these changes into Main Storage.Delta Storage Delta storage is used for a write operation and uses basic compression. which is collected in delta storage to main storage. the content of main storage is saved to disk and compression recalculated.  After performing Delta Merge operation on sap column table. All uncommitted modification in Column table data stored in delta storage. Process of moving Data from Delta to Main Storage during delta merge . then use "delta merge operation" from SAP HANA studio as below –  The purpose of delta merge operation is to move changes.

So in SAP HANA. 1. Data first go to L1. 2.Committed data) 4. Then data goes to L2-delta buffer. L1-Delta contains all uncommitted data. Column storage is both Write-optimized and Read-optimized due to L1-Delta and main storage respectively. When L2-delta process is complete. From main store data goes to the persistence layer (The arrow indicating here is a physical operator that send SQL Statement in Column Store).Uncommitted data) 3. column table acts like row store due to L1-delta.g. Committed data moves to Main Store through L2-Delta. (L2. When L1 moves data further (L1. E. The user runs update / insert query on the table (Physical Operator is SQL statements. which is column oriented. After Processing SQL Statement in Column store.There is a buffer store (L1-Delta) which is row storage. So. data goes to Main storage. below is row-based table- . data goes to the persistence layer.).

So. and the second important sizing component is CPU. etc. data is stored on disk as – Memory address Data is stored column-wise in the linear format on the disk. one of the critical tasks is to determine the right size of a server according to business requirement. SAP HANA Sizing Sizing is a term which is used to determine hardware requirement for SAP HANA system. Data can be compressed by compress technique. so below is format how data is stored on disk for row and column table In SAP HANA memory. Hard Disk and CPU.Table data is stored on disk in linear format. The third main component is a disk.  Disk Space Requirement for SAP HANA ( Is calculated for data persistence and for logging data) . this table is stored in Row Store on disk as format – Memory address And in Column. In SAP HANA implementation. such as RAM. The main important sizing component is the Memory. SAP HANA DB differ in sizing with normal DBMS in terms of –  Main Memory Requirement for SAP HANA ( Memory sizing is determined by Metadata and Transaction data in SAP HANA)  CPU Requirement for SAP HANA (Forecast CPU is Estimated not accurate). Column store has an advantage of memory saving. but sizing is completely dependent on Memory and CPU.

SAP HANA Studio runs on client/developer machine and connects to SAP HANA Server.The Application server CPU and application server memory remain unchanged. . integrated development environment (IDE) for development and administration of SAP HANA Database in the form of GUI tool. For sizing calculation SAP has provided various guidelines and method to calculate correct size. SAP HANA Studio can access local or remote SAP HANA Database. 3. By using SAP HANA Studio we can –  Enables user to manage the SAP HANA Database. Requirement will be displayed in below format- SAP HANA Studio is an Eclipse based. Sizing using DB Script. Sizing using ABAP report. By using Quicksizer tool. We can use below method1. 2. Sizing using Quicksizer Tool.

 Create and authorizations. you will learn Pre-Requisite for SAP HANA Studio  Supported Platform  Download & Install SAP HANA Studio  Installation Path  Software Download  Installation on Microsoft Window  Run SAP HANA Studio  Administration Console Perspective  Modeler Perspective  Development Perspective  Lifecycle Management Perspective  Add System in SAP HANA Studio  Work With SAP HANA Studio  Catalog  Provisioning  Content  Security Pre-Requisite for SAP HANA Studio user existing . modify In this tutorial. manage  Create New or models of data.

 SAP HANA Client – It is software. a JVM is installed or updated. Red Hat Enterprises Linux (6. o SAP HANA Client can be installed on UNIX / Linux and Microsoft Windows and also on SAP HANA Server host during server installation. Software Download You can download SAP HANA Studio and SAP HANA Client from here Select File To Download according to your OS – . SAP HANA Client installed separately from SAP HANA studio. by which you will be able to connect any other database./user / sap / hdbstudio.  Mac OS 10. 64 bit .Supported Platform SAP HANA Studio runs on below platform – Microsoft Windows x32 and x64 versions Window XP  Window Vista  Window 7  Window 8  SUSE Linux Enterprises Server: x86 64 Bit version. 64 bit .  Mac OS . Download & Install SAP HANA Studio Installation Path The default installation on system path according to OS and their version is as below –  Microsoft Window (32 & 64 bit). System Requirement  JAVA JVM – During Installation and updating of SAP HANA Studio.5)./Applications / sap / hdbstudio.9 or Higher.C:\Program files \sap\hdbstudio.  Linux x86.

Step 1) Define Studio Properties .exe for installing SAP HANA studio. Click on hdbsetup.Installation on Microsoft Window Install SAP HANA Studio in the default directory with administration privileges or in user home folder without administration privileges. Default installation folder is C:/Program Files / SAP / hdbstudio. A SAP HANA Lifecycle Management Screen appears.

2. Select Features screen appear as below – Step 2) Select features . Click on Button.1. Select install new SAP HANA Studio.

1. Select Feature as below  SAP HANA Studio Administration – Toolset for various administration task.  SAP HANA Studio Application Development – Toolset for developing SAP HANA native Applications (XS and UI5 Tools excluding SAPUI5).  SAP HANA Studio Database Development – Toolset for content development. 3. Excluding Transport. Step 3) Review and Confirm . Select Features screen are used to select features. 2. Click button.

Click on Button. 1.1. Summary of SAP HANA Studio Installation display. . Installation Progress screen appear and after it goes to finish page. Step 4 & 5) Install Software and Finish. Review & Conform Screen appears. 2. 3.

There is hdbstudio. Run SAP HANA Studio Now. 3.exe file.exe" file. A Message "You have successfully installed the SAP HANA Studio". When you click "hdbstudio. it will open Workspace Launcher screen displayed below. you can create a shortcut on the desktop. by right clicking on it. .2. go to Default installation folder is "C:/Program Files / SAP / hdbstudio". Click on button.

Workspace is used to store studio configuration settings and development artifacts. Select "Use this as the default and do not ask again" option to prevent popup this screen every time for workspace selection when we open SAP HANA Studio. 2. Click Button.1. We can change Workspace location by Browse option. 3. Workspace is selected by default. SAP HANA Studio Welcome screen appear – .

administration and monitoring the SAP HANA Database. System View Toolbar is used for Administration.In the Welcome screen different perspective is displayed. Detail of each perspective is as below – 1. it looks like as below – . Several View and editor are available in SAP HANA Administration Console. Administration Console Perspective This screen is used to configure.

image . of the individual system in System Monitor by drill down. either No SQL Mode 2. This is used for 1.Below is a Table showing System-level editors and views available in SAP HANA Administration Console. By double click monitoring task. choose backup. System View We can see the detail Toolbar. From The Administra performing System Toolbar. tion administration and 2. etc.) System Monitor System Monitor is an editor which provides an overview of all SAP HANA Database Button on at one screenshot. Backup Used in performing Expand the Backup and system and Administration. on System. This editor is used in case of emergency to perform monitor and Administra 1. content.Ctrl+Shift + O connection available or the SQL connection overload. From click operation on the tion Administration system in which Diagnosis tool list icon. View/ Editors Detail Path Systems The System view provides hierarchical view of all the SAP HANA System Window-> Show managed in SAP View -> System HANA Studio with their contents (catalog.

Analytic Privileges. Calculation View. In this Perspective programming language is used – JAVA Script. Lifecycle Management Perspective This screen is used to Install and Update software regarding SAP HANA Database and SAP HANA Studio. Functions. 4.  Data Provisioning to SAP HANA database from SAP / NonSAP Source through SLT. Modeler Perspective This perspective is used to create modeling objects. J Query. Views. database object management in SAP HANA System. So we build a connection to SAP HANA DATABASE as below – .Data Volume system. Development Perspective This Perspective is used to develop an application on HANA for the web environment. DXC. Add System in SAP HANA Studio To work with SAP HANA Database user needs to be connected with SAP HANA database from SAP HANA Studio. Encryption SQL Console Used for Executing analyzing statement Console. ODATA. Entering. Sequences. 3. Synonym. etc. Indexes.  Create Modelling object like Attribute View.Security This editor is used for Security option managing below from Security topic1. View.Password views of the Policy 2. Lifecycle management is also used to transport an object from one HANA system to another HANA System. Procedures and Decision Table. Trigger. This perspective used by modelers for the following activity –  Create / Modify Tables. Analytic View. BODS. and From the System SQL Toolbar Choose in SQL SQL 2.

Host Name – Enter SAP HANA database here. .Step 1) Click on "Add System" icon from System Toolbar as below- Step 2) Provide the following detail as below – 1. Description – Description of the system for better understanding 4. 3. Click on button. Instance Number – Two Digit Instance number. 2.

A connection properties screen appears in which we need to enter SAP HANA Database User and Password. 1. and System name is added in SAP HANA Studio under System Node. Enter Username and Password for SAP HANA Database for access it from SAP HANA Studio. then the connection is successful. Click button. If there is no error. 2. follow below steps- . Work With SAP HANA Studio To login in SAP HANA Database through SAP HANA Studio.

Indexes. Schema of the same name will be created in SAP HANA Database by default. Procedure. Enter User Name and Password for HANA Database. Synonyms. This is a default schema of user when a user creates any database object. View. After Login to SAP HANA Studio. Trigger. Index. Views. Schema defines a container that hold database objects such as Table. 3.1. Click on Ok button. 2. Synonyms. In Hana Studio under HANA System following sub-nodes exits Catalog SAP HANA Studio Catalog node represent SAP HANA data dictionary. Procedure. etc. A popup screen for User Name/ password. Here" DB (HANAUSER)". etc. Click on Added System. We get below screen for selected HANA System. When the user is created in SAP HANA. . Trigger.) stores in Schema Folder. Function. in which Database object (Table. Schema is used to group database object. Sequence.

External Tools (SLT. BODS. . "Smart Data Access" which is Built in Tool. All Database Object are stored in respective folder of Schema as below –  Provisioning Provisioning is used for selecting source Meta data and importing metadata and data into SAP HANA. etc. There are two categories of provisioning. they are 1. I have created Schema "DHK_SCHEMA" by it in-front SQL.Schema can be created in SQL Editor by below SQLCREATE SCHEMA "SCHEMA_NAME" OWNED BY "USERNAME". SAP uses a new feature called. etc.) In SAP HANA Studio Provisioning node. After Refresh Catalog Node Newly Created Schema will be displayed. DXC. Smart Data Streaming. Here "SCHEMA_NAME" AND "USERNAME" Should be changed according to Requirement. Smart Data Access. SAP HANA In-Built Tool (Flat file.) 2.

and Sybase.(Attribute View. SAP HANA SQL . Data Type.g. vendor independent and standardized. it can be only used to build calculation views in SAP HANA. 2. The restriction with virtual tables is. Oracle. Operator. Password Policy. Security – Used for Create User Audit Policy. Role and Privileges will also grant to user from this screen. In SAP HANA. Privileges are added/deleted from here to Role. The package is used for grouping related information object in a structured way. etc. Function. Sequence. which hold all information of data models in the package. . Roles – Used for Create/Modify/ delete Roles. All information view e. SAP HANA also supports SQL.SQL Script. Analytic View. Teradata. etc. the reason of being popular is – it is powerful.  Security Security Node in SAP HANA Studio contain 3 Sub-node. The package can be created by clicking right click on Content Node ->New->Package. SQL is the main database language. 3. Trigger. Data from different sources will store in SAP HANA database as "Virtual Table".Smart Data Access combines data from heterogeneous data sources like Hadoop. Users – Used for create/Modify/Delete user. Calculation View. they are – 1.  Content Content Node is Design Time Repository.) will be created in Package under Content Node. Identifiers Most RDBMS database uses SQL as database language. Expression.

MySQL etc. It is a Standard Language for communicating with Relational database like Oracle. UPDATE. retrieve and modify the data in the database. you will learn–  What is SAP HANA SQL  SAP HANA Identifiers  SAP HANA Data Type  SAP HANA Operator  SAP HANA SQL FUNCTIONS  SAP HANA SQL EXPRESSIONS  SAP HANA SQL Stored Procedure  SAP HANA Create Sequence  SAP HANA Create Trigger  SAP HANA SQL DATA Profiling  SAP HANA SQL SCRIPT  SAP HANA Calculation View What is SAP HANA SQL SQL Stands for Structured Query Language. ALTER .In this tutorial. INSERT). we can perform following job Schema definition and use (CREATE SCHEMA).  DDL Statement ( CREATE .  DML Statement (SELECT. DROP ) . SQL is used to store. By using SQL in SAP HANA.

SAP HANA Data Type In SAP HANA Database. index name. view name. synonym name. DCL Statement ( GRANT .g. The identifier can contain any character including special character.) There are two types of identifiers – delimited identifiers and undelimited identifiers.  Multiple Line Comment – "/* */ ". column name) must start with a letter and cannot contain any symbols other than a digit or an underscore '_'.It is used for delimiting identifiers. etc.  Delimited Identifiers – It is enclosed in the delimiter. function name. table name. SQL Data Type is as below – Classificat SubSQL ion Classificat Type Data Column Store Type Default Format . Double Quotes "". SAP HANA Identifiers Identifiers are used to represent name in SQL statement (e. There are two types Quotation mark for delimit as below Single Quotation Mark (' ') – It is used to delimit the string.  Undelimited Identifiers – Undelimited identifiers (table name.Double Hyphens "—".  Double Quotation Mark (" ").REVOKE)  System Management  Session Management  Transaction Management Comment in SQL We can add a comment to improve the readability and maintainability of SQL Statements. column name. Comment can be put on SQL in two ways Single Line Comment . procedure name. All Commented text is ignored by SQL Parser. This is one line comment.

648 To 2. Real Number REAL single-precision 32-bit floatingpoint number Decimal CS_FLOAT .s) CS_FIXED(pp-Precision ss. Range -32. The scale s can range from 0 to p. depending on the stored value. -9.854.036.807 DECIMAL(p. Range -2.854.147. Small Decimal SMALLDECIM CS_SDFLOAT AL It is a floating-point decimal number.483.ion Date Times Date Types DATE CS_DAYDATE 'YYYY-MM-DD' Time TIME CS_SECONDTI 'HH34:MI:SS' ME Second Date SECONDDATE CS_LONGDAT 'YYYY-MM-DD HH34:MI:SS' E Numeric Types Time Stamp TIMESTAMP CS_SECONDD 'YYYY-MM-DD HH34:MI:SS.483.775. If precision and scale are not specified.767 CS_INT 32-bit signed integer. Range CS_FIXED(18.223.775.372.372.808 0) To 9. SMALLDECIMAL is only supported for column store Table. Range 0 To 255 Small Integer CS_INT 16-bit signed integer .036.s) scale Precision p can range from 1 to 38.768 To 32.223.FFn' ATE Tiny Integer TINYINT CS_INT 8-bit unsigned integer. The precision and scale should be within the range 1~16 for precision and -369~368 for scale.647 Integer SMALLINT INTEGER Big Integer BIGINT 4-bit signed integer . DECIMAL becomes a floating-point decimal number.147.

VARBINARY(n CS_RAW ) Store binary data of a specified maximum length in bytes. Boolean Boolean BOOLEAN CS_INT TRUE. where n indicates ) M the maximum length and is an integer between 1 and 127 Short Text SHORTTEXT(n CS_STRING ) It is Variable-length character string which provide text search and string search features. where n indicates the maximum length and is an integer between 1 and 5000. where 'n' specified the maximum length in bytes and this is an integer between 1 and 5000. Character String VariableLength Character String Binary Types VARCHAR(n) CS_STRING It is a Variable-length character string. Binary Text LOB Types(Larg Binary LOB BLOB e Object Types) CS_RAW Large amounts of binary data .Double Number DOUBLE CS_DOUBLE a double-precision floating-point number 64-bit Float FLOAT(n) CS_DOUBLE It is 32-bit or 64-bit real number. where <n> indicates the maximum length in characters and is an integer between 1 and 5000 Alpha Numeric Character Variable length alpha-numeric ALPHANUM(n CS_ALPHANU characters. VariableLength Unicode character NVARCHAR(n) CS_STRING Variable-length Unicode character set string. FALSE And UNKNOWN (NULL). but not for row tables. This data type can be defined for column store tables. Where n specifies the number of bits and should be in the range between 1 and 53.

CS_STRING The BINTEXT data type is similar to data type TEXT and thus supports text search features. but not for row store tables. but it is possible to insert binary data. SAP HANA Operator SAP HANA Operator can be used for calculation. but not for row tables. value comparison or to assign value. TEXT TEXT BINARY Text BINTEXT Data Multivalued Types Array ARRAY It stores collections of values of the same data type where each element is related with exactly one position. Arrays can contain NULL values as in the absence of a value. This data type can be defined for column Store tables.Character LOB CLOB CS_STRING ASCII character data Unicode Character LOB NCLOB CS_STRING Large Unicode character object CS_STRING The TEXT data type provide text search features. SAP HANA Contain below operators Unary and Binary Operator  Arithmetic Operator  String Operators  Comparison Operator  Logical Operator  Set Operator Unary and Binary Operator . This data type can be defined for column tables.

expressions or constants into one.>..>=) operand Logical operators ( AND. Two Vertical Bar "||" is used as the concatenation operator. Comparison Operator Comparison operator is used to compare two operand.<=.) Comparison operators ( =. OR ) Arithmetic Operator  Addition (+)  Subtraction (-)  Multiplication ( * )  Division ( / ) String Operator A String Operator is a concatenation operator which combines two items such as strings. <> ) Logical Operator .!=. Below are list of Comparison Operator Equal to ( = )  Greater Than ( > )  Less Than ( < )  Greater than or equal to ( > = )  Less than or equal to ( < = )  Not Equal (!= . / ) Additive operators Binary applies on two ( +.Operat Operation or Unary Description A Unary operator Unary plus operator(+) Unary negation operator(-) applies to one Logical negation(NOT) operand A Binary Operator Multiplicative operators ( *.<.

Set Operators  UNION .  EXCEPT . WHERE condition1 AND condition2) If both Condition1 AND Condition2 are true.g.Takes the output from the first query and removes row selected by the second query. including all duplicate row.  UNION ALL .g. .(e.  NOT .  OR – (e. WHERE NOT condition) NOT condition is true If Condition is false.Combines two or many select statements or query.  INTERSECT .g. and return all common rows.g.Logical operator is used in search criteria. I have two tables (table1. then Combine condition is true else it will false. E.Combines two or many select statements or query without duplicate.g. then combine condition is true or false if both Conditions are false. WHERE condition1 OR condition2) If Condition1 OR Condition2 is true. WHERE condition1 AND / OR / NOT condition2 Below is list of logical operator –  AND .Combines two or many select statements or query.(e. E. table2) in which some values are common.



TABLE 2 ) ORDER ELEMENT. BY EXCEPT SELECT * FROM ( SELECT ELEMENT FROM DHK_SCHEMA.) ORDER ELEMENT. BY SELECT * FROM ( SELECT ELEMENT FROM DHK_SCHEMA.TABLE 1 EXCEPT Takes output from first query and removes row selected by the second query .TABLE 1 INTERSE INTERSECT CT Combine Result of two or more query with all common rows. SELECT ELEMENT FROM DHK_SCHEMA.

TO_BIGINT. RANK (). ROW_NUMBER ().Number Functions take a numeric value. TO_BINARY etc. BY SAP HANA SQL FUNCTIONS SAP HANA Provides following SAP HANA Functions1. POWER. ADD_SECOND. 2. etc.g. E. E.g. – ADD_DAYS. (ASCII.g. – SCORE etc.TABLE 2 ) ORDER ELEMENT. E.) 6.Fulltext Functions is used for text search. . Date Time Functions . etc.g. 4. Window Functions – Window Functions let user divide result set of a query into groups of rows named window partition. String Functions . Below are list of Data Type Conversion functionE. E.g. etc. process them and return value according to function. Fulltext Functions . – ABS. CAST. or string with numeric characters. Data Type Conversion Function – Data Type conversion function are used to convert one data type to another. ADD_MONTHS. DENSE_RANK (). Number Functions .g. CHAR. ROUND. etc. as input and return numeric values.String Functions take a string as input. 5. 3.SELECT ELEMENT FROM DHK_SCHEMA. TO_ALPHANUM. E.Date Time Function are used to convert Date/ Time in a different format. CONCAT.

Aggregate Name Description COUNT Count the Number of rows returned by the query. MAX Return the maximum value of the expression.7. STDDEV Return the Standard Deviation of given expressions as the square root of VARIANCE function.g. CURRENT_SCHEMA. – CONVERT_CURRENCY. which are used for the miscellaneous job. VAR Return the variance of expressions as the square of standard deviation  Subqueries in Expression – A subquery is a select statement enclosed in parentheses and used in a main select statement as input. SUM Return the sum of expressions. etc. A procedure can be invoked by another procedure which is called the calling program.There are some more functions.  Aggregate Expressions – In This Expression aggregate functions is used to calculate a single value from the values of multiple rows for a column. E.  Function Expressions – SQL built-in-functions can be used as Expressions. Miscellaneous Function. This procedure can be combined to form larger programs. . AVG Return the arithmetical mean of expressions. MIN Return the minimum value of the expression. This basically forms the 'Modular Design'. There are 4 types of SQL Expressions Case Expressions – In this expression the user can use IF – THEN – ELSE logic without write procedure. SAP HANA SQL Stored Procedure A procedure is a unit/module that perform a specific task. SAP HANA SQL EXPRESSIONS SQL Expressions is a clause that can be used for return values.

An SQL Procedure can be created at –  At Schema Level(Catalog Node)  At Package Level(Content Node) Stored Procedure syntax in SAP HANA is as shown below – SYNTAX CREATE PROCEDURE <proc_name> [(<parameter_clause>)] [LANGUAGE <lang>] [SQL SECURITY <mode>] [DEFAULT SCHEMA <default_schema_name>] [READS SQL DATA [WITH RESULT VIEW <view_name>]] AS {BEGIN [SEQUENTIAL EXECUTION] <procedure_body> END | HEADER ONLY } The CREATE PROCEDURE statement creates a procedure using the mention programming language <lang>. The procedure can have multi-input/output parameters. It is Read <parameter_clause> Only parameter. SYNTAX ELEMENTS ELEMENTS DESCRIPTION <proc_name> Procedure Name The parameter is defined here. • OUT – Used for Return Value from Procedure as OUTPUT. The procedure can be created as read-only or read-write.Procedures are re-useable processing block with a specific sequence of data transformation. LANGUAGE <Lang> Defines the programming language used in the procedure. INOUT parameter is there. • INOUT – Used for Pass and Return Value To Procedure by same parameter. Default: SQLSCRIPT . OUT. Each parameter is marked using the keywords IN/OUT/INOUT • IN – Used for Pass Value To procedure as INPUT. IN.

It defines the result view to be used as the output of a readonly procedure. . HEADER ONLY If Header Only is used. <procedure body> It defines the main body of the procedure based on the programming language selected.Specifies that the execution of the procedure is performed with the Privileges of the invoker of the procedure. SAP HANA Create Sequence A sequence is a database object that automatically generates the incremented list of numeric values according to rule as specified in sequence specification. If nothing is defined. SEQUENTIAL EXECUTION This statement will force sequential execution of the procedure logic. <default_schema_na me> It defines the schema for unqualified objects in the procedure body. it means the procedure does not modify the database data or its structure and that the procedure does not contain DDL or DML statements.Specifies that the execution of the procedure is performed with the SQL <mode> SECURITY Privileges of the definer of the procedure. then it can be called by an SQL statement in the same process as a table or view. READS SQL DATA It marks the procedure as being read-only. No parallelism takes place.Specifies the security mode of the procedure. Default: DEFINER • DEFINER . then the current schema of the session is used for the procedure. This procedure only calls other read-only procedures. • INVOKER . then only procedure properties are created with OID. WITH RESULT <view_name> VIEW If a result view is specified for a procedure.

then we use sequence. they are used by the application. [<sequence_parameter_li It specifies one or more sequence parameters. MINVALUE <min_value> / It specifies the minimum value that a sequence can NO MINVALUE generate. the maximum value will be 4611686018427387903 and the minimum value for a descending sequence will be -1. SYNTAX CREATE SEQUENCE <sequence_name> [<sequence_parameter_list>] [RESET BY <subquery>] SYNTAX ELEMENTS ELEMENTS DESCRIPTION <sequence_name> It is the name of the sequence. There are two values in sequence –  CURRVAL – Provide Current value of Sequence. NO MAXVALUE When the NO MAXVALUE is specified.  NEXTVAL – Provide Next value of sequence.For example to insert employee number automatically in column (EMPLOYEE_NO) of Table. st>] START <start_value> INCREMENT <increment_value> WITH BY It describes the starting sequence value. for an ascending sequence. Sequence values are generated in Ascending or Descending order.which can be generated MAXVALUE <max_value> by the sequence. The default is 1. When the NO MINVALUE is used. when a new record is inserted in the table. This specifies maximum value . This specifies the value to be incremented from the last value assigned for each time when new sequence value generated. Sequences are not associated with tables. <min_value> can be between -4611686018427387904 and 4611686018427387902. <max_value> can be between -4611686018427387903 and 4611686018427387902. the minimum value for .

EMP_NO. NO CYCLE Default option.EMP_NO START WITH 100 INCREMENT BY 1. NO CACHE directive specifies that the sequence number will not be cached in a node. the database automatically executes the <subquery> and the sequence value is restarted with the returned value. which will create incremented value of the sequence by +1 each time. given . In the query. RESET BY <subquery> It specifies that during the restart of the database.102………So on every execution of above select query. The database users only having the TRIGGER privilege for the <subject_table_name> are allowed to create a trigger for that table or view. <cache_size> must be unsigned ascending sequence is 1 CYCLE CYCLE directive specifies that sequence number will be restarted after it reaches its maximum or minimum value. the "nextval" can be used for serial number generation or same type of requirement. Example – We will create a sequence with named DHK_SCHEMA. Use of Sequence – SELECT DHK_SCHEMA.EMP_NO. Sequence Script CREATE SEQUENCE DHK_SCHEMA. Here we will use object "sequence" in below example to increment the value of employee no by +1 each time the select query is executed. OUTPUT – 100.nextval FROM DUMMY. NO CACHE Default option.NO CYCLE directive specifies that sequence number will not be restarted after it reaches its maximum or minimum value. SAP HANA Create Trigger A trigger is also a stored procedure that automatically executes when an event happens on a given table or view.101. CACHE <cache_size> / The cache size specifies which range of sequence numbers will be cached in a node. when the sequence is used.

Specifies that the trigger will be executed instead of the DML operation on a view.Specifies that the trigger will be executed before the DML Operation on a table. with the optional schema name.Specifies that the trigger will be executed after the <trigger_action_ti DML operation me> on a table. • INSTEAD OF . . BEFORE | AFTER | INSTEAD OF • BEFORE . Syntax CREATE TRIGGER <trigger_name> <trigger_action_time> <trigger_event_list> ON <subject_table_name> [REFERENCING <transition_list>] [<for_each_row>] BEGIN [<trigger_decl_list>] [<proc_handler_list>] <trigger_stmt_list> END SYNTAX ELEMENTS ELEMENTS DESCRIPTION <trigger_name> It specifies the name of the trigger to be created. SAP HANA SQL DATA Profiling Data profiling is the process of analyzing the data available in an existing data source and collecting statistics and information about that data. A view with INSTEAD OF trigger becomes updatable. • AFTER .The CREATE TRIGGER command defines a set of statements that are executed when a given operation (INSERT/UPDATE/DELETE) takes place on a given subject table or subject view.

implementation cycle of major projects may be shorten. we can analyze data effectively. finding data problem late in the project can lead to delay and cost excess. Advantage of SQL DATA Profiling is as below –  It helps to understand the source data. SQL script can also be used in Calculation view. . It can be used in stored procedure in place of plain SQL.  By data profiling.  Typical Statement like SELECTs.  Understand data challenge early in the project. It determines the functional and procedural extensions.  By Data Profiling. SAP HANA SQL SCRIPT SQL Script is a collection of extensions to SQL. of data  User Defined Function (The User Defined Function container is separated into Scalar User Defined Function and Table User Defined Function). By Data profiling process user can remove incorrect and incomplete data before loading to the data warehouse. description. SQL Script Language elements are as below – Declarative SQL Script Logic (Functional Extension)  It allows the definition of table types without referencing database tables. In SQL Script user can define local variables for structure and tables that are primarily used for the creation of stored procedure. incomplete and improve data quality.  By Data Profiling.SQL DATA profiling task is used to understand and analyze data from different data source. we can remove incorrect. there are two different logic containers Procedure (Procedures allows you to describe a sequence transformations on data passed as input and database tables).  Improve the ability to search the data by adding keywords. In SQL Script.  Calculation Engine (CE) Functions.

FOR (Loop) and Exceptions. Imperative SQL Script Logic (Procedural Extension) Imperative logic splits the logic among several data flow. SAP HANA Calculation View CE Functions also known as Calculation Engine Plan Operator (CE Operators) are alternative to SQL Statements. Key points of SQL Script. DML and SQL Query Statements and control flow logic using imperative language constructs such as loops and conditionals. E.  In SQL Script.  SQL Script is executed and processed in the calculation engine within the HANA database. Insert).  SQL Script is able to perform complex calculations. Importance of SQL Script Only SQL Script provides the necessary elements to migrate data-intensive logic or the operation of the application server to the database server. By using SQL Script.  SQL Script Procedure can return more result by using "OUTPUT Parameter" while Normal SQL Procedure can return only one. CE function is two types – Data Source Access Function .g. parallel processing mode can be achieved. Create Schema. E.g. you can define global or local tables types which can be used as parameters.  In SQL Script.Orchestration SQL Script Logic (Functional Extension) Orchestration logic is used to implement data flow by using DDL.  Data Definition Language Statement.g.  Data Manipulation Language (E. IF. CASE. ELSE. a local variable can be declared to hold the interim result. ELSEIF.

)  CE_CALC (It is used to calculate additional columns based on the business requirement. Below is some data Source Access Function list –  CE_COLUMN_TABLE  CE_JOIN_VIEW  CE_OLAP_VIEW  CE_CALC_VIEW Relational Operator Function By Using Relational Operator. It provides column name aliase features also. the user can bypass the SQL processor during the evaluation and communicate with calculation engine directly.)  CE_LEFT_OUTER_JOIN (It is used to perform left outer join between the sources and display the queried columns to the output). Below is some Relational Operator Function list –  CE_JOIN (It is used to perform inner join between two sources and Read the required columns/data.This function binds a column table or a column view to a table variable.) Below is a list of SQL with CE function with some ExampleQuery Name SQL Query CE-Build in Function .  CE_PROJECTION (This function display the specific columns from the source and apply filters to restrict the data.)  CE_RIGHT_OUTER_JOIN(It is used to perform right outer join between the two sources and display the queried columns to the output. This is same as calculated column in graphical models.

 SAP HANA has an own data type.SQL Script is used for better performance. D. on Analytic "ANALYTIC_VIEW" Group By [C.D]) Select Query SELECT C. Where Having "ANALYTIC_VIEW" Where C = 'value' CE_PROJECTION(:var1.Select Query SELECT C. D On Column "COLUMN_TABLE". preparing. All these processes are referred as ETL (Extract.  SAP HANA provide CE function.D].[C."C" ="value"/ Summary:  SAP HANA Supports SQL. SUM(E) From ).g.[C.D Select Query SELECT C.D]) View By C. D On Attribute "ATTRIBUTE_VIEW" View From CE_JOIN_VIEW("ATTRIBUTE_VIEW". and detail is as below- . and enabling a network to provide data to its user. D. D. and SQL Script is an extension of SQL. Data needs to be loaded to SAP HANA before data reaches to the user via a front-end tool. SUM(E) From CE_CALC_VIEW("CALCULATION_VIEW" on Calculation "CALCULATION_VIEW" Group . [C.  SAP HANA also support SQL function e. which is executed in calculation engine. Table From CE_COLUMN_TABLE("COLUMN_TABLE" . Data Provisioning in SAP HANA DATA Provisioning is a process of creating. SUM(E) From CE_OLAP_VIEW("ANALYTIC_VIEW".D]) View C. and Load).[C.D Var1= CE_COLUMN_TABLE("COLUMN_TABLE" SELECT C. aggregate function.D]) Select Query SELECT C. Transform.

you will learn Overview of Replication Technology  SLT (SAP Landscape Transformation Replication Server)    SAP SLT Connection Architecture overview between SAP System and SAP HANA  Configure SAP SLT Server for SAP Source System  Import SAP Source Data to SAP HANA through SLT  SAP SLT Connection between non-SAP System and SAP HANA SAP DS (SAP DATA Services)  Features of Data Services  Component of Data Services  Data Services Architecture –  Data Services example by load data from SAP Source Table SAP HANA Direct Extractor Connection (DXC)  Advantage of SAP DXC  Limitation of SAP DXC .  Extract – This is first and sometimes most difficult part of ETL. in which data are extracted from the different source system.  Transform – In the Transformation Part. series of rules or functions is defined for the data extracted from the source system. for loading data into the target system. In this tutorial. Load – The Load phase loads the data in the target system.

SAP HANA Built-In Provisioning Tool 1. there are main methods of data provisioning for SAP HANA. Remote data 2. Flat File 2. SAP Business Objects Data Services 3. these are – Methods of Data Description Provisioning .  Configure SAP DXC DATA Replication Flat file Upload to SAP HANA  Create the table in SAP HANA  Create file with data in our local System  Select the file  Manage the Mappings  Load the data Overview of Replication Technology SAP HANA supports two type of Provisioning tool – 1. SAP Landscape Transformation 2. Enterprise Information Management(EIM) 5. External tool supported by SAP HANA 1. SAP Direct Extractor Connection 4. Sybase Replication Server At present. Smart Data Streaming 3. Smart Data Access (SDA) 4.

SLT (SAP Landscape Transformation Replication Server) SLT is the SAP first ETL tool that allows you to load and replicate data in real-time or schedule data from the source system and Non-Source System into SAP HANA Database. . On SAP SLT server we define Mapping and Transformation. SAP HANA SLT Road Map is as below – DATA Provisioning through SLT require RFC/DB connection to SAP/Non-SAP Source System and a DB connection for SAP HANA database.SLT ("SAP Landscape Transformation Replication Server") running on the SAP Net Weaver Platform.xlsx) to SAP HANA.csv. DXC DXC stand for Direct Extractor Connect is a batch driven ETL tool. SLT is an ideal solution for RealTime and Schedule time replication for SAP and non-SAP source system. . . Benefit of SLT system is as below Allows real-time or schedule time data replication. SAP SLT server uses a trigger-based replication approach to pass data from source system to target system. Below is a roadmap for data provisioning through SLT. Flat Upload File This option used to Upload data (. SLT server can be installed on the separate system or on SAP ECC System. SLT SAP DATA SAP DATA Services is a platform for designing of ETL processes Services with a graphical user interface.xls.

Architecture Overview of SAP SLT server with SAP / Non-SAP System is as belowSAP SLT Connection Architecture overview between SAP System and SAP HANA SAP SLT Replication Server transforms all metadata table definitions from the ABAP source system to SAP HANA. During replicating data in real-time. A database user with the same authorization as user "SYSTEM" can create a connection between SAP SLT and SAP HANA Database. we can migrate data in SAP HANA Format.  SLT handles Cluster and Pool tables. .  SLT have monitoring capabilities with SAP HANA Solution Manager. (Unicode is a character encoding system similar to ASCII.  The connection between SAP SLT and SAP HANA is established as a DB connection.  This support automatically non-Unicode and Unicode conversion during load/replication. Non-Unicode is encoding system covers more character than ASCII).  Read engine is created in the SAP Source System.  This is fully integrated with SAP HANA Studio. For SAP source. SAP SLT Replication server creates logging tables in the source system. the SLT connection has the following features  When a table is replicated.  SLT have table setting and transformation capabilities.  The connection between SAP SLT and SAP Source is established as RFC connection.

and Call transaction "LTR" from SAP SLT replication server. A Web-dynpro pop-up screen will appear for login to SAP SLT server. T-code. 1. Click on logon tab . There is no need to create it manually. Configure SAP SLT Server for SAP Source System First we need to configure SAP SLT replication server for connection between SAP Source and SAP HANA database.SAP SLT Connection between SAP System and SAP HANA DATABASE SAP SLT Server automatically create DB connection for SAP HANA database (when we create a new configuration via transaction LTR). LTR is used for creating a connection between SAP Source and SAP SLT. Enter Client / User id / password 2. Step 1) Login to SAP SLT server.

. of data Transfer Jobs.A pop-up screen for Configuration will appear as below- Click on "New" Button for the new configuration. 4. Enter Username / Password / Host Name and Instance number. 1. 2. Step 2) In this step. Enter Configuration name and description. 3. 5. Enter RFC connection for SAP System. Select SAP System as the source system. Enter Job options detail –  No.

6. 7. Of calculation jobs. . Select Replication option as Real Time. Once all the settings are maintained click on 'OK' to create a new schema in SLT. A Configuration Name "SLTECC" will be added and active. No.

1 Schema . There is no need to create it manually.After configuration SAP SLT server successfully. Import SAP Source Data to SAP HANA through SLT Once we have successfully configured SAP SLT server. 4 Role  SLTECC_DATA_PROV  SLTECC_DATA_POWER_USER  SLTECC_DATA_USER_ADMIN  SLTECC_DATA_SELECT 6. a SCHEMA as configuration name above in SAP SLT is created in SAP HANA Database. 2 Procedures . SAP SLT Server automatically create DB connection for SAP HANA database (when we create a new configuration via transaction LTR). 8 Tables –  DD02L (SAP Tables Name )  DD02T (SAP Table Texts)  RS_LOG_FILES  RS_MESSAGE  RS_ORDER  RS_ORDER_TEXT  RS_SCHEMA_MAP  RS_STATUS. we import data to SAP HANA from SAP Source. 1 User – SLTECC. This Schema contains following objects1. In next step. 1 Privileges 4.SLTECC. 5. 2. 3.

Step 2) A screen for SLT Based Table Data Provisioning will be displayed. . Database trigger and related logging table will be created for Delta each table. follow below steps1. 3. Replicate (Full + Load) It start initial load (if not done earlier). Select SAP HANA System. Step 1) To load tables from SAP ECC to SAP HANA database. which starts an initial load of data from Load) source system. 2. RS_GRANT_ACCESS  RS_REVOKE_ACCESS All configuration is completed. Go to Data provisioning from Quick View. There are 5 options for data provisioning as belowProvision Option Detail Load (Full This is a one-time event. Click on Finish Button. and also consider delta Load change. now we load a table from SAP ECC (ERP Central Component).

Resume Resume restarts the replication for a suspended table. Click on Load Button and select the table (LFBK) which we need to load/replicate in SAP Hana. Related Information is stored in the related logging table in the source system. Source and Target system details are selected according to SAP SLT configuration. 3. Suspend It pause a running replication process of a table. We use the first option from the table "Load option" for initial load of the table (LFBK) data from source to SAP HANA table. After resume. 2. It removes Replication database trigger and logging table completely." .Stop It stops the current replication process for a table. Table (LFBK) will be added to Data Load Management Section with Action "Load" and Status "Scheduled. The database trigger will not be deleted from the source system. the suspended replication process will resume. and recording of changes will continue. Step-by-step is as below1.

SAP SLT Connection between non-SAP System and SAP HANA SAP SLT Replication Server transforms all metadata table definitions from the nonABAP source system to SAP HANA. Login in SAP HANA Database through SAP HANA Studio and select SAP HANA System HDB (HANAUSER). Loaded Data through SLT process will be displayed in Data preview screen. Step 3) Check Data in the table (LFBK) by Data Preview from Schema "SLTECC" as below -. Right click on Table (LFBK) and click on Open data preview option. 2. Status will be changed to "Executed". Now we have successfully loaded data in table "LFBK". We will use this table future in Modelling. Select Table (LFBK) under Table node. 4.After data load. the SLT connection has following features  When a table is replicated. 3. SAP SLT Replication server create logging tables in the source system. . The table will be created in "SLTECC" schema with data. For Non-SAP source. 1.

 It supports multi-users. Data quality. Read engine is created in the SAP SLT Replication server. . SAP DS (SAP DATA Services) SAP Data services is an ETL tool which gives a single enterprises level solution for data integration. (Latest version of SAP BODS is 4.  It has comprehensive administrative tools and reporting tool. so for complex transformations. We can create applications (job) in which data mapping and transformation can be done by using the Designer.  The connection between SAP SLT and SAP Source / SAP HANA is established as a DB connection.2). Data profiling and text data processing from the heterogeneous source into a target database or data warehouse. we need another ETL tool such as SAP Data services.  SAP BODS is very flexible with web-service based application. Transformation.SAP SLT Connection and SAP HANA System/DATABASE SAP SLT can only do simplest transformations. SAP SLT Connection between Non . Features of Data Services  It provides high-performance parallel transformations.

XML. o Any Databases with bulk loading and changes data capture o Files: fixed width. comma delimited. To Open Data Service Designer go to Start Menu -> All Programs -> SAP Data Services (4. o Any Applications (e. test. with the Trigger-based technology. SAP). It allows the developer to create objects and configure them by selecting an icon in a source-to-target flow diagram. Excel.  Administration tool with scheduling capabilities and monitoring/dashboards.g.  SAP BODS support Broad source and target.2 here) -> Data Service Designer. COBOL. Designer. . It can be used to create an application by specifying workflows and data flows. and execute a job that populates a data warehouse. SLT adds delta-capabilities to every SAP or non-SAP source table Which allows for using data capturing for change and transferring the delta data of the Source table.  Data validation with dashboards and process auditing. Component of Data Services SAP DATA services have below component – 1.It is a development tool by which we can create.  Data Services can integrate with SAP LT Replication Server (SLT) .  Debugging and built-in profiling and viewing data. It allows scripting language with rich sets of functions.

data services job server and engines. Job Server. .Data Service engine executes individual jobs which are defined in the application. 6. transformation rules). 3.  Publishing batch jobs and real-time services via Web services  Configuring and managing adapters. and Repository usage.2. Engine.Repository is a database that stores designer predefine objects and user defined objects (source and target metadata.It is an application that launches the data services processing engine and serves as an interface to the engine and Data Services Suite. starting and stopping real-time services.Access server passes messages between web applications. monitoring and executing batch jobs.  Configuring Job Server. Access Server. Repository.Web Administrator provides browser-based administration of data services resources detail is as below –  Configuring.  Managing users. 4. Repositories are of two types –  Local Repository (Used by Designer and Job Server). Administrator.  Scheduling. Access Server.  Central Repository ( Used for object sharing and version control) 5.

it is used for repositories configurations to jobs servers. workflow. version control and object sharing  Designer – Used for Create Project. security management. data flow and run. Job.  Local repository (here you could create change and start jobs. . In below image. Data Services and there component relationship is shown.Data Services Architecture – Data Services architecture have the following component Central Repository .  Access Server – It is used to execute the real-time jobs created by developers in the repositories. dataflow). Workflow.  Job server & engine – It manage the jobs.

SAP BODS Architecture
Designer Window Detail: First we look into the first component of SAP data
service- Designer
Detail of each section of data service designer is as below1. Tool Bar (Used for Open, Save, Back, Validate, Execute, etc.).
2. Project Area (Contains the current project, which includes Job, Workflow,
and Dataflow. In Data Services, all entities are objects.
3. Work Space (The Application Window area in which we define, display, and
modify objects).
4. Local Object Library (It contains local repository objects, such as
transforms, job, workflow, dataflow, etc.).
5. Tool Palette (Buttons on tool palette enable you to add new objects to the

Object Hierarchy

The below diagram shows hierarchical relationships for the key object types within
Data Services.



Workflows and Conditional* are optional
Objects used in SAP Data services detail is as below Objects Description
A project is a highest-level object in the Designer window. Projects
provideyou with a way to organize the other objects you create in Data
Services.Only one project is open at a time (where "open" means "visible in
the projectarea").

A "job" is the smallest unit of work that you can schedule independently

Scripts A subset of lines in a procedure.
A "work flow" is the incorporation of several data flows into a coherent flow
of work for an entire job. Workflow is optional. Workflow is a procedure.


Call data flows

Call another work flow

Define the order of steps to be executed in your job

Pass parameters to and from data flows.

Specify how to handle errors that occur during execution.

Define conditions for executing sections of the project.

Dataflo A "data flow" is the process by which source data is transformed intotarget
data. A data flow is a reusable object. It is always called from a work flow

or a job. in which we need to create a data store for source and target and map to them.  Identify the target table to which you want to load data.  Configure Import Server  Import the metadata to HANA system. Logical channel that connects Data Services to source and Datastore target databases. Data Services example by load data from SAP Source Table Everything in Data services is an object.  Define the transformations that you want to perform on the data.  Create Data Store between BODS to HANA.  Create Job (Batch/Real time)  Create Work Flow  Create Data Flow . Datast ore  Must be specified for each source and target database.  Create Project.  Identify the source data that you want to read. Steps for loading data from SAP source table . We need to separate data store for each source and target database.SAP BODS have many steps.  Create Data Store between Source and BODS  Import the metadata (Structures) to BODS.  Are used to import metadata for source and target databases into therepository  Are used by Data Services to read data from source tables and load datato target tables Target Table or file in which Data Services loads data from the source.

enter detail as below 1. 6. we need a data Store. Add Object in Dataflow  Execute the job  Check the Data Preview in HANA Step 1) Create Data Store between SAP Source and BODS 1. Select Data store type name as "SAP Applications". Enter data store name "ds_ecc". User name and password. So we create a Data store first as shown below – Project -> New . 2. Enter database server name 4. 3. Click on "Apply" button. Click on "OK" button. 5.> Data Store 2. To Load data from SAP Source to SAP HANA through SAP BODS. A pop-up for Create new data store will appear. .

Select DataStore tab. Go to Local Object Library 2. . Data store "ds_ecc" will be displayed. Data Store will be created and view the created datastore as below1.3. 3.

We have created a data store for ECC to BODS. To import follow below steps 1. Select Data store "ds_ecc" and right click. A pop-up for Import by Name will be displayed. Select Type as a table.Step 2) Import Metadata (Structure) to BODS Server. Enter detail as below – 1. . Select Import by Name option. now we import metadata from ECC into BODS. 2.

Click On "Import" Button. 3. which we want to import.2. To do this go to Quick View-> Configure Import Server as below - . in datastore ds_ecc as below – Step 3) Configure Import Server Till now we have imported table to data stored "ds_ecc" created for ECC to SAP BODS Connection. Table Metadata will be imported. Here we are importing KNA1 table. To import data into SAP HANA. Enter Name of Table. 1. KNA1 table will appear under table node of "ds_ecc" data source. we need to configure Import server.

SAP BODS server Address (here BODS:6400 ) 2. Enter ODBC Data Source (ZTDS_DS). 4. Click on "Next" button. Enter Default port for SAP BODS server(8080).2. Select SAP HANA (HDB here) System as below- 3. . Enter SAP BODS Repository Name ( HANAUSER Repositery Name ) 3. Another Pop-Up for data service credential will appear. enter following details 1. A pop-up for Select System will appear.

A pop-up for Import option will be displayed. Select "Selective Import of Metadata" option. .Click on "Finish" button. now we will import metadata from SAP BODS server. 2. Till now we have Configured Import Server. 1. Step 4) Import the metadata to HANA System 1. Click Import option in Quick View.

in which we select target System. Select SAP HANA System (HDB here). .Click on "Next "Button. 2. 1. A pop-up for "Selective Import of Metadata" will be displayed.

Step 5) Create Data Store between BODS and HANA As we know. So.Click on "Next" Button. . 2. Go to Project -> New -> Data store. now we need to create a data store for the target (between BODS and HANA). in BODS we need to create a separate data store for source and target. We have already created a data store for the source. A screen for Create new Datastore will appear as below. we create a new data store with name"DS_BODS_HANA". 1. 1. Enter Datastore name (DS_BODS_HANA).

6. 3. Enter Database type as SAP HANA. Enter Datastore type as Database. Click on "Apply" and then "OK" button. Tick on "Enable automatic data transfer". Enter Port name for SAP HANA Database. Data store "DS_BODS_HANA" will be displayed under datastore tab of Local Object Library as Below- . 4.2. 7. Select Database Version. 8. Enter Username and password. 5. Enter SAP HANA Database server name.

3. 1. A pop-up for Import by Name will appear as be below- . 2. Now we import table in data store "DS_BODS_HANA". Select data store "DS_BODS_HANA" and right click. Select Import By Name. 4.

4. Data will be displayed IN TABULAR Format. Click on Import Button. 2. 2. Step 6) Define Project: Project group and organize related objects. 3. to view data in table follow below steps – 1. Enter Name as KNA1. The Project can contain any number of jobs. Owner will be displayed as Hanauser. Select Type as Table. and dataflow. Table will be imported in "DS_BOD_HANA" datastore.1. Workflow. . Click on table "KNA1" in data store "DS_BODS_HANA".

To Execute BODS Process we need to define the job.1. We create a Job as JOB_Customer. Jobs can be executed manually or as a schedule. 3. Select new option. Enter Project Name and Click on Create Button. Step 7) Define Job: A Job is a reusable object. Go to Designer Project menu. It contains workflows and dataflow. Select Project option. . 2. It will create a project folder in our case BODS_DHK. A POP-UP for New Project Creation appears as below. Select Project (BODS_DHK) created in step 1. 1. Right click and select "New Batch Job".

3. 2. Click the Dataflow button on the tool palette. Click On Workflow "WF_Customer". A Dataflow icon will appear in the workspace. A workflow icon will appear in the workspace. Click on the Black Workspace area. Click the name of workflow. Select Job "JOB_Customer" in project area. Click on the Black Workspace area.2. Step 8) Define Workflow: 1. . Change the name of the workflow as "WF_Customer". Click the workflow button on the tool palette. Rename it to "JOB_Customer". Step 9) Define Dataflow: 1. 2. an empty view for the workflow appears in the workspace.

Step 10) Add Object in Dataflow: Inside data flow. 3.Select Data store "DS_BODS_HANA" from the repository and select table KNA1.  An object for the target table.) Click on the dataflow DF_Customer . Specify object for Target. (Query transform maps the columns from source to target. . There will be two table for source and target. Change the name of the Dataflow as "DF_Customer".3. Specify object from Source – Go to Data store "ds_ecc " and Select table KNA1 and drag and drop to data flow blank screen as below screen2. The Dataflow also appears in the project area on the left under job name. A blank workspace will appear as below - 1.  An object for Query transform. We will see below object –  An object for the source. we can provide instruction to transform source data into the desired form for the target table. Drag and drop to the workspace and select "Make Target "option. 4. Here we will define the table as source and target.

1. . Link Query Object to Target table. Select Query Transform icon from tool Palette. Link Query object to Source. 3. and drag and drop it between source and target object in workspace as below 2.4. Query Transformation – This is a tool used to retrieve data based on input schema for user specific condition and for transport data from source to target.

we map a column from input schema to output schema. Select all column from the source table and right click and select a map to output. Save and Validate project. 3. 2. Click on validate Icon. a next window for mapping will appear. A pop-up for validation success appear. . By this. 5. Source Table KNA1 is selected.1 Double Click On Query Icon. 1. Target Output selected as Query. in which we do the following steps 1. When we click on Query icon. 2. and column will be mapped.

. and select created Project. to execute Job. follow the below path1. Select Execute option.Step 11) Execute Job – To execute Job. Select Project Area icon to open Project. 3. Select Job and right click. 2.

a Job Log window is displayed. . Select KNA1 table in Table node. 6. 5. Right Click on table KNA1 and Select Open Data Preview. After Executing Job. 4. Table (KNA1) Data loaded by BODS processes as above will be displayed in data preview screen. in which all message regarding Job will be displayed. 3. 2.1. Step 12) – Validate / Check Data in SAP HANA Database. The last message will be Job < > is completed successfully. Login to SAP HANA database through SAP HANA Studio. and select HANAUSER schema.

In SAP Business suite application content Data Source Extractors have been available for data modeling and data acquisition for SAP Business Warehouse. and Load) method of SAP Business Suite Application via a HTTPS connection.  It extracts semantic rich data from SAP Business site and provide to SAP HANA. SAP DXC uses this Data Source Extractor to deliver data directly to SAP HANA.e. Advantage of SAP DXC  SAP DXC requires no additional server or application in the system landscape. SAP HANA DXC is batch driven data replication technique i. as it sends the data to SAP HANA after applying all business extractor logic in the source system. Limitation of SAP DXC  Data Source must have pre-defined ETL method. if not then we need to define them. Transform.  It reduces the complexity of data modeling in SAP HANA. . it can execute after a time interval.SAP HANA Direct Extractor Connection (DXC) SAP HANA DXC uses existing ETL (Extract.  It speeds up SAP HANA Implementation time lines.

0 or higher (e. Go to SAP HANA webdispatcher.ini Studio -> Select System -> Configuration -> . SAP DXC requires a Business Suite System on Net Weaver 7. ECC) equal or below SP level: Release 700 SAPKW70021 (SP stack 19.  Enabling ICM Web Dispatcher Service .ini. Configure SAP DXC DATA Replication Step 1) Enabling XS Engine and ICM Service  Enabling XS Engine Go to SAP HANA Studio -> Select System -> Configuration -> xsengine.It enables ICM Web Dispatcher service in HANA system. from Nov 2008). Set instance value to 1 in Default filed.g.  A procedure with a key field defined must exist in Data Source. Web dispatcher uses ICM method for data read and loading in HANA system.

Set instance value to in default column 1. Test the DXC Connection. Import the delivery unit using Import Dialog in SAP HANA Content Node ? Configure XS Application server to utilize the DXC ? Change the application container value to libxsdxc.  Verify the DXC is working. Step 2) Setup SAP HANA Direct Extractor Connection  Set DXC Connection in SAP HANA – To create a DXC connection we need to import delivery unit in SAP HANA as below -  Import Delivery Unit.  Configure XS Application server to utilize the DXC. You can import the unit in the location "/usr/sap/HDB/SYS/global/hdb/content". . You need to download the DXC delivery unit from SAP into SAP HANA database. then append it). Modify the application container value to libxsdxc (if any value existed.

 Data Sources in BW need to configure to Replicate the Structure to HANA defined schema.xscfunc . which pass value to call screen.We can check DXC Connection by using below path in Internet Explorer – http://<hostname>:80<instance Number>/sap/hana/dxc/dxc.RFC Connection equal Name of RFC Connection -. PSA_TO_HDB: This three object values are shown as below  GLOBAL – This is used for replicate all data source to HANA . We Need to Setup the SAP_RSADMIN_MAINTAIN Following Parameters in BW Using Program (T-code SE38 or SA38) Parameters List in Program – Parameter list contains value .Service Number equal 80 <Instance Number > Log on Security Tab Maintain the DXC user created in HANA studio which has basic Authentication method.Enter a user name and password to connect.  User and Schema need to be defined in HANA Studio  http connection in SAP BW for HANA need to define through SM59.Target Host equal HANA Host Name -. So create a http connection in SAP BW Using T-code SM59. Input Parameters will be -.

which having the List of data sources which are used for DXC. SYSTEM – It Specified clients to Use DXC  DATASOURCE –It specified Data Source. First we need to Replicate the Meta data Using Specified application Component (data source version Need to 7. it will create the following table in the Defined schema. we need to migrate that first. Active the data Source in SAP BW. If we have 3. enter the name of the table you created. Flat file Upload to SAP HANA . ) Once data source loaded and activated in SAP BW.IMDSO related table. And we can preview data from table /BIC/A0FI_AA_2000 in SAP HANA Studio.5 version data source. o In the VALUE field. PSA_TO_HDB_DESTINATION: In this we need to Move the Incoming data (in this we need to Give the value which we create in SM59) ( here XC_HANA_CONNECTION_HANAS) PSA_TO_HDB_SCHEMA: It specifies which schema the replicated data need to assign Data Source Replication Install data source in ECC using RSA5. Now data is successfully loaded into Table /BIC/A0FI_AA_2000 once it is activated.  /BIC/A<data source>00 – IMDSO Active Table  /BIC/A<data source>40 – IMDSO Activation Queue  /BIC/A<data source>70 – Record Mode Handling Table  /BIC/A<data source>80 – Request and Packet ID information Table  /BIC/A<data source>A0 – Request Timestamp Table  RSODSO_IMOLOG . and only specified can be used. we have taken data source 0FI_AA_20 ( FI-AA: Transactions and Depreciation).0 version. Stores information about all data sources related to DXC. PSA_TO_HDB_DATASOURCETABLE: In this we need to give the Table Name.

SAP HANA Support following type of files which will be available on client system as below –  . To upload data in SAP HANA. then we can create a table by SQL Script or by this process by selecting "NEW" option. We will use "NEW" option for creating a new table. BODS.SAP HANA support uploading data from a file without ETL tools (SLT. This application suggests column name and data type for the new tables.XLS  . It is a new feature of HANA Studio Revision 28 (SPS04).CSV (Comma Separated value files)  .xls file for it on local system. SalesOrg Name Currency CoCode Address Country Ref_Sorg .CTL file). so we have created a file SalesOrg. records will be appended at the end of the table. If table exits.csv file and . We are going to upload SalesOrg. table need to exist in SAP HANA. if table not present then table need to be created. the user needs to create control file (.xlsx file into SAP HANA. Create file with data in our local System We are going to upload Sales Organization master data.XLSX Prior to this option. So create a . and DXC). Steps for upload data from flat file to SAP HANA is as below Create the table in SAP HANA  Create file with data in our local system  Select the file  Manage the mappings  Load the data Create the table in SAP HANA If table are not present in SAP HANA.xlsx in the local system.

A Quick View screen appears as below- . USD 1000 NEW YORK USA 1000 2000 ABC Enterprises INR 2000 INDIA INDIA 2000 Select the file Step 1) Open modeler perspective ? 'Main Menu' ? 'Help' ? 'Quick View' as shown below.1000 ABC Pvt. Ltd.

A pop-up for import option will be displayed.Select 'Import' option from Quick View. .

Go to SAP HANA Content? 'Data from Local File'. .A Pop-Up for import screen is displayed.

follow below steps for the select file. Select SalesOrg. . 2.Click Next. 1. Click on "Open" button. A pop-up for File selection will be displayed.xls file.

otherwise mention Start Line and End line for specific data load from file. 3. Select File – Selected file path will be displayed here. .xls file has a header (column Name). Ignore leading and trailing white space Tick this option for ignoring leading and trailing white space in the file. they are  Source File Section  File Details Section  Target Table Step 2) In this step we have to enter following detail which we can select a file for loading data from local system to SAP HANA database. Import All Data – Tick this option if you want to import all data from a file. 4. So. Available options can be categorized into three main areas. Header Row Exits – If SalesOrg. 2.A screen for file selection for import will be displayed . we have ticked it.

then choose this option. then choose this option. 6.5. Select Schema name and Table. Data will be appended to end of the table. Click on "Next" button Manage the Mappings A mapping screen will be used for performing the mapping between source and target columns. Target Table – In this section two option – New – If the table is not present in SAP HANA. and provide Exiting schema name and table name to be created. . Exiting – If the table exist in SAP HANA.

Click File name and drag to target field. The field can be mapped automatically by one to one or map By Name option. This can be used if we know that the columns names are same. we can also see how the data looks in the source file for all the columns.  Map by Name: By using this option. 2. 1. 5.File data section displays data of SalesOrg file.There are two different types of mapping available. we can change target table definition. File will be mapped. Mapping of Source to Target – We will map here Source File column to Target Table. Proposed Table structure from Source File. This option can be used if we know all the columns are in sequence. we can manually do the mapping using drag and drop option could not be mapped with the above options. If our column name 4. Click on "Next" file. we can map the source and target columns based on the name.When we click on option as below - we get two  One to One: By using this option. 3. and also. Target Table Structure: Target Table store type is selected as column store by default. . In the File data section of the same screen. we can map column to column based on the sequence.Table column Name is supposed from excel file Column Name (Header).

3. By this screen data that already exist in the table will display and also the information about the schema and table to which we are going to load the data will display. click 'Finish' to Start loading the data to the table. Data from File: It will display data extracted from the file. If displayed data in Data from file section has been verified. Detail Sections: In this section Selected Source File name. Target Table Name. Load the data It is final screen before we start the loading process. 1.A window for import data from the local file will appear. 2. . and Target Schema Name detail will be displayed.

we should see the entry in the job log view with status 'Completed Successfully.'  Once the data importing job is successful. After successful import option completing. 2. We can see the data in table of by selecting the table of respective schema and right click on Table ? 'Data Preview' as shown below. 1. Data of table will display in Data preview screen as below- Summary: We have learned following things for SAP Hana- .

In this tutorial. cube or information provider of BW.  Load Data from Flat file to SAP HANA Table. you will learn SAP HANA Modelling Overview  Types of Attribute  Types of Measure  Privileges Required for Modelling  Join Method in SAP HANA  SAP HANA Best Practices for Creating Information Models   SAP HANA Attribute View   Create Standard Attribute View SAP HANA Analytic View   Creating a Package in SAP HANA Studio SAP HANA Analytic View Creation SAP HANA Calculation View .  Load data in SAP HANA from SAP ECC through BODS with an example. Information View is similar to dimension. SAP HANA Modeling SAP HANA Modeling is an activity by which we create information view.  SAP DXC overview. This information view is used for creating the multi-dimensional data model. SAP DATA Provisioning Method Overview  Load data in SAP HANA Table through SAP System Landscape Transformation with an example.

Information view is made from various combinations of content data to create a model for a business scenario. SAP HANA Graphical Calculation View  SAP HANA Analytic Privileges  SAP HANA Information Composer  SAP HANA Import and Export  SAP HANA Performance Optimization Technique SAP HANA Modeling Modelling is an activity in which user refine or slice data in the database table by creating information view based on the business scenario. E. Arithmetic calculation or derive the full name from the first and last name. so it is local to Modelling view and cannot access from outside of Modelling . This information views can be used for reporting and decision-making purpose. Vendor Name.g. etc. City. Revenue.g. Content Data in information view are of two types –  Attribute: Descriptive and Non-Measureable Data. Quantity Sold and Counters. E. Local Attribute It is used inside modelling views (analytic View / calculation view) for Customize the behavior of attribute. E. The measure cannot be created in Attribute view.g. Calculated Attribute It is derived from one or more existing attributes and constants.  Measure: Data can be quantifiable and calculated. Vendor ID. The measure is derived from analytic and calculation view. Types of Attribute SAP HANA Support three Type of attributes Types of Attributes Activities    Simple Attribute It is derived from data foundation.

This is used for master data context. It is used in count the one or more attributes columns. Types of Measure SAP HANA Support four Type of Measure – Types of Attributes Activities  Simple Measure  Calculated Measure  Restricted Measure  Counter It is derived from data foundation. Arithmetic calculation. It is derived from one or more exiting measure.view. Object Privileges – Object privileges are SQL privileges which are used for providing read/write access on database objects.g.  Calculation View – This is used for creating a complex view and similar to multiple Provide in BW. It is used to filter value based on user-defined rules for attribute values. Below are object privileges are required for Modelling. by which authorized user can access authorized content only. It is Special types of the column that display unique number for attributes Columns (Analytic View/ Calculation View). below are privileges required for SAP HANA Modelling Privileges Required for Modelling Privileges provide security to SAP HANA database. privileges are required by user.  Analytic View – This is used for creating fact tables and similar to Cube of BW. Information Views are of three types as below –  Attribute View . constants and function. In order to work in SAP HANA. E. .

Package Privileges – Package Privileges are required to authorize action on individual packages. Analytic Privileges – To Access SAP HANA Information View Analytic Privileges are required  For Full data access to all information view in SAP HANA System.READ.MAINTAIN_NATIVE_PACKAGES privilege on Root Package. "_SYS_BI_CP_ALL" analytic privileges required. analytic privileges need to be created and assign to the user. For restricted data access.EDIT_NATIVE_OBJECTS & REPO. SELECT privilege on _SYS_BI Schema.  REPO. REPO.  SELECT privilege on Table Schema.  SELECT privilege on _SYS_BIC Schema.  REPO.ACTIVATE_NATIVE_OBJECTS on package used for Content Objects.  REPO. Other Privileges Provide Grant on Own Schema to _SYS_REPO user as 'GRANT SELECT ON SCHEMA " Schema name" TO _SYS_REPO WITH GRANT OPTION'.  EXECUTE privilege on REPOSITORY_REST (SYS).WORK_IN_FOREIGN_WORKSPACES for work in foreign workspaces.EXPORT for Import / Export of delivery Units.MAINTAIN_DELIVERY_UNITS for creating delivery Units.  REPO.IMPORT. There are following types of Join method to Join SAP HANA tables – Join Type Uses Comment . REPO. SAP HANA Join Types Join in SAP HANA is used to Join table and information view and select values as per the requirement. Below are package privileges are required for data modelling REPO.

 More sub-package also can be created.  The custom table should be in a separate schema. TABLES:  Table that will be used in reporting or OLAP should be Column store type. view. FI_SCHEMA. (DS_SCHEMA. Right Outer Join selects the complete set of If no match from the first RIGHT records from the second table. Null value JOIN matching record from the second table (If select from the second Available). SAP HANA Best Practices for Creating Information Models SAP HANA Best Practice is standard while creating an object in SAP HANA Database. SCHEMA:  Design your Schema Layout before start the project. Null value select OUTER JOIN matching record from the first table (If from the first table. FULL OUTER Full Outer Join selects all records from both JOIN the table. SLT_SCHEMA. INNER Left Outer Join selects the complete set of If no match from the LEFT OUTER records from the first table. with table.). Available). etc.g. TEXT JOIN Text Join are used to select language For Getting Description of specific specification the column it is used.Inner Join selects the set of records that match in both the table. .E. Below are best practice for object – PACKAGE:  Create a top-Level package like "Development" for development work. with a second table. if required. It is same as inner join by assuming that It is available for only REFERENTIA referential entity is maintained between attribute view and analytic L JOIN the two tables. table. SD_SCHEMA.  Create a sub-package under top-Level package for each developer.

. analytic view... Privileges means Analytic AP_REST_CA(Calculation View) HI_BNAME_PC(Parent Child) HIERARCHY HI_.... etc. Stored Procedure INPUT PARAMETERS IP_PARA_NAME IP_.. etc..means variable name Creating a Package in SAP HANA Studio Package: It is a container that contains all information about the model (attribute view.) can be created in Structural package..... Table that will be used in Transaction or OLTP should be as Row Store type.. analytic view.... NAMING CONVENTION: OBJECTS Format Description ATTRIBUTE VIEWS AT_PRODUCT AT_. means parameter VARIABLES VA_VNAME VA_. calculation view.. .means Analytic view CALCULATION VIEWS CA_SALES CA_. means Calculation view AP_REST_AT(Attribute View) ANALYTIC PRIVILEGES AP_REST_AN(Analytic View) AP_... which is as below – Type Description Structur In Structural package.. Icon .  Give comment / description for table and column name properly for clarity. . means Hierarchy HI_BNAME_LV(Level) PROCEDURE SP_PROCEDURENAME SP_. No al Information view (Attribute view. means Attribute View ANALYTIC VIEWS AN_SALES AN_.. Types of package: Package are of two types.) in a group. only sub-package can be created...

2. Go to Content folder. and make model transporting easier. 1.E. system-local. . This is default package. here it is HDB. al Uses of Package: Package group are all information model. Generated. Select Package option. system-local. Private. Steps for creating Structural Package in SAP HAN StudioSTEP 1) In this step. 1. STEP 2) In this step. Non The Non-Structural package can contain information object and subStructur packages. 2. Both packages can be used in transporting. Select New. system-local. of Structural package – SAP.g. Select Hana System.

1. Original language and Person Responsible is selected by default. .STEP 3) In this step. "DHK_SCHEMA". E. 3.g. 2. Enter Description for Package. Enter Package Name.

STEP 5) In this step. convert Non-Structural Package to Structural Package. Select package "DHK_SCHEMA" and right click on it. 2. 2. 1.Non-Structural Package with Name "DHK_SCHEMA" will be created in Content node as below- STEP 4) Now. Select "Yes" in for Structural Options field. . Go to edit option for the package. Click on OK Button. 1.

It is better to first create a structural package. . other Package and information object can be created. The package is created by default as Non-Structural. STEP 1) In this step.Our "DHK_SCHEMA" when changed from Non-Structural to Structural package the icon style will be changed from to . Step for Creating Non-Structural package under Structural Package as sub-package. This is an indication that non-structural package is now converted to the structural package. In Non-Structural Package. and then create a sub-structural package in it.

3. STEP 2) In this step. Enter Sub-package name in Name field. Enter description for it. Select New -> package. 2. Select Structural Package "DHK_SCHEMA" and right click on it. 2. . 1. Click on "OK" Button.1.

A new Non-structural package will be created as sub package under DHK_SCHEMA

SAP HANA Attribute View
Attribute View: Attribute view acts like a dimension. It join multiple tables and act
as Master. Attribute view is reusable objects.
Attribute view has the following advantage

Attribute View act as Master data context, which provides Text or Description
for Key/Non-key field.

Attribute View can be reuse in Analytic View and Calculation View.

Attributes View is used to select a subset of columns and rows from a
database table.

Attributes (fields) can be calculated from multiple table fields.

There is no measure and aggregation option.

Attribute View Type: Attribute View are 3 typesAttribute

It is a standard attribute which is created by table fields.


It is Time attribute view, which is based on default time table –
For calendar type Gregorian 





For calendar type Fiscal 



It is an attribute view which is derived from another existing attribute
view. Derived attribute view will be opened in read-only mode. The only
editable field is its description.
Copy From – When you want to define an attribute view, by copying an
existing attribute View, then you can use "Copy From" option.

Note: Difference between Derived and Copy from is, in the case of derived, you can
only edit the description of new attribute view while in the case of copy, you can
modify everything entirely.
Create Standard Attribute View
Standard view creation has pre-define step as below-

Table Creation for Attribute View
Here we are going to create Standard Attribute View for product table, so firstly we
create "PRODUCT" and "PRODUCT_DESC" Table.
SQL Script is shown as below for table creation –


INTO "DHK_SCHEMA"."PRODUCT" VALUES ('A0001','10000','A', 500.00);
INTO "DHK_SCHEMA"."PRODUCT" VALUES ('A0002','10000','B', 300.00);
INTO "DHK_SCHEMA"."PRODUCT" VALUES ('A0003','10000','C', 200.00);
INTO "DHK_SCHEMA"."PRODUCT" VALUES ('A0004','10000','D', 100.00);
INTO "DHK_SCHEMA"."PRODUCT" VALUES ('A0005','10000','A', 550.00);



Now table "PRODUCT" and "PRODUCT_DESC" is created in schema "DHK_SCHEMA".
Attribute View Creation
STEP 1) in this step,
1. Select SAP HANA System.
2. Select content Folder.
3. Select Non-Structural Package Modelling under Package DHK_SCHEMA in the
content node and right click->new.
4. Select Attribute view option.

STEP 2) Now in next window,
1. Enter Attribute Name and Label.
2. Select View Type, here Attribute View.
3. Select subtype as "Standard".
4. Click on Finish Button.

Scenario Pane: In this pane the following node exists Semantics  Data foundation 2. Detail of each part in Information Editor is as below 1.STEP 3) Information view editor screen will open. Detail Pane: In this pane following tab exists –  Column .

etc. Data Foundation (Scenario Pane): This node represents the table that we use for defining attribute view. Here we drop table for creating attribute view.This is a toolbar for Performance analysis. Tab (columns. 3. 10. validate. 6. STEP 4) To include database table for creating attribute view. data preview. . Drag table "PRODUCT" and "PRODUCT_DESC" from TABLE node under DHK_SCHEMA 2. 5. Hierarchies) for details pane will be displayed. 4. 8. view Properties. click on data foundation node and follow the instruction step by step as below 1. Semantics (Scenario Pane): This node represents output structure of the view. View Properties  Hierchery 3. Select field from "PRODUCT_DESC" Table as Output in the detail pane. Show: Filter for Local Attribute. Here it is Dimension. Drop "PRODUCT" and "PRODUCT_DESC" to data foundation node. Detail of attribute. Local: Here all Local attribute detail will be displayed. 9. Field Icon color change from grey to orange. Find column. 7. activate. Select field from "PRODUCT" Table as Output In detail pane. Field icon color changes from grey to orange. 4.

A screen for Edit Join Condition will appear 1. The field selected as output from both the table appear Under Column list in Output Pane. Select cardinality as "1. STEP 5) Select Join path and Right Click on It and choose Edit option..5. 2. . Join "PRODUCT" table to "PRODUCT_DESC" by "PRODUCT_ID" field.1". Select Join Type as Type "Inner".

. Go to DHK_SCHEMA->MODELLING Package. Click on validate Button. 4. i. 3. refresh the Attribute View folder. In next step. Select "PRODUCT_ID" as Key. Job Log section as below - STEP 7) An attribute view with name "AT_PRODUCT" will be created. click on activate Button. 6. Check Hidden option for field PRODUCT_ID_1 (PRODUCT_DESC table field). After successful validation. Select Semantic Panel.e. we select the column and define a key for output. Column tab will appear under Detail pane. 2.After selecting join type click on "OK" button. Job Log for validation and activation activity is displayed on bottom of screen on the same page. we will select column and define the key for output 1. STEP 6) In this step. To view. 1. 5.

it will display in Label axis(X Axis). (This will display output as only SQL query Output). There will be two option for data view from attribute view –  Open in Data Preview Editor (This will display data with analysis option). Drag and drop attribute in label axis. .2. 3. we select Attributes for Label and Axis format view. 2. it will display in value axis (Y Axis). Distinct and Raw data Analysis: This is a Graphical representation of the attribute view. STEP 8) To view data in Attribute view. STEP 9) To see View Attribute data in data Preview editor – There are 3 options – Analysis. By selecting Analysis tab.  Open in SQL Editor. 2. Drag and drop attribute in value axis. 1. Select data Preview option from the toolbar. 1. AT_PRODUCT Attribute view display under Attribute view folder.

The output will be available in the format of Chart. This will show total no. Table. and HTML. Click on Raw data tab 2.4. records for selected attribute. Raw Data tab: This option display data of attribute view in table format. Distinct Values: The distinct value of the column can be displayed here. It will display the data in table format . Grid. 1.

This is used to see SQL query used for displaying data from the view. when we run Data Preview. A column view with name "will created after activation of attribute view "AT_PRODUCT". Display output. Attribute View when activated. So. 2. a column view under _SYS_BIC schema is created. system select data from column view under a _SYS_BIC schema. Screen shot of column view "AT_PRODUCT" under "_SYS_BIC" Schema of catalog node is as below - . 1. Display SQL Query for data selection.STEP 10) View Attribute data in from SQL editor as below – This option display data through SQL Query from the column view under "SYS_BIC" schema.

Product. Example: Here we create an analytic view for Purchase Order based on earlier created attribute view "AT_PRODUCT". PO_CATEGORY NVARCHAR(2). CREATED_BY NVARCHAR(20). which is used for analysis of data. (E. CREATED_AT DATE . etc.  Analytic View is mainly used in a scenario where we need aggregated data from the underlying table. PO_STATUS VARCHAR(1). dimension table are joined with the fact table that contains transaction data. Product Name.  SAP HANA Analytic view forms a cube-like structure. CURRENCY NVARCHAR(5).). customer. SQL Script for Create Table "PURCHASE_ORDER" in "DHK_SCHEMA" CREATE COLUMN TABLE "DHK_SCHEMA".g. QUOTATION_NO NVARCHAR(10). A dimension table contains descriptive data. PUR_ORG NVARCHAR(4). TERMS NVARCHAR(4).). etc.SAP HANA Analytic View SAP HANA Analytic view is based on STAR Schema Modelling. PUR_GRP NVARCHAR(3). PRODUCT_ID NVARCHAR(10). and it represents OLAP/Multi-Dimensional Modelling objects. Vendor."PURCHASE_ORDER" ( PO_NUMBER NVARCHAR(10) primary key. In SAP HANA Analytic view. VENDOR NVARCHAR(10). Fact Table contains both descriptive data and Measureable data (Amount. COMPANY NVARCHAR (4). Tax. We use Table Purchase Order Header and Purchase Order Detail table for it.

00. 'HANAUSER'.'2016-01-07').'A0002'.'A0001'. INSERT INTO "DHK_SCHEMA".1000.'INR'.'MM'."PURCHASE_DETAIL" VALUES(1000003.'V000001'.00."PURCHASE_ORDER" VALUES(1000001. QUANTITY_UNIT VARCHAR(3).'CASH'.10.1002.'A0002'. 'V000001'.'CASH'.00.1001.00.).2). 'V000002'.'CASH' .'A0001'.00.1000.'GR1'. 1000. COMPANY NVARCHAR(4).'INR'.103.101.50000.'UNIT'.00.00 ).20.'GR1'."PURCHASE_ORDER" VALUES(1000004.'UNIT'.'GR1'.1000012. ORDER_PRICE DECIMAL(8. NET_AMOUNT DECIMAL(8.32000."PURCHASE_DETAIL" VALUES(1000002.50000. 'V000001'. INSERT INTO "DHK_SCHEMA".'2016-01-06').'MM'.1000014.2).'V000001'. QUANTITY SMALLINT.60000.2000. PLANT NVARCHAR(4).'GR1'. VENDOR NVARCHAR(10).2). PRODUCT_ID NVARCHAR(10).1000.102.'MM'.'GR1'.1003.'INR'.'2016-01-07'). INSERT INTO "DHK_SCHEMA". PUR_ORG NVARCHAR(4). CURRENCY NVARCHAR(5).1000.1000013.'A'. STORAGE_LOC NVARCHAR(4).00. INSERT INTO "DHK_SCHEMA".1000011.60000.40000."PURCHASE_ORDER" VALUES(1000003. PUR_GRP NVARCHAR(3).2000.'MM'.1000. 'HANAUSER'.1000.2000.'INR'.'CASH'.8000.'GR1'.'MM'.00 ).'INR'. PO_CATEGORY NVARCHAR(2).2000.40000.'A0004'.'INR'.'A'."PURCHASE_DETAIL" VALUES(1000001. .'CASH'. TAX_AMOUNT DECIMAL(8.48000.'CASH'. INSERT INTO "DHK_SCHEMA".'MM'.00.'A'. SQL Script for Create Table "PURCHASE_DETAIL" in "DHK_SCHEMA" CREATE COLUMN TABLE "DHK_SCHEMA".'CASH'.'V000001'.00. INSERT INTO "DHK_SCHEMA".'INR'.2) ).'2016-01-07')."PURCHASE_ORDER" VALUES(1000002."PURCHASE_DETAIL" ( PO_NUMBER NVARCHAR(10) primary key.00).'UNIT'.1000.10.2000. 'HANAUSER'.'V000001'.'MM'.40000.'A0003'.1000.12000. GROSS_AMOUNT DECIMAL(8. INSERT INTO "DHK_SCHEMA".'A'.'HANAUSER'.'GR1'. TERMS NVARCHAR(4).10000.'A0003'.

INSERT INTO "DHK_SCHEMA".00. Select View type as "Analytic View".20000.20.'MM'.00. With this table script.1004.'A0004'.1000.16000. 2. 1. . STEP 1) In this step.00). Select Modelling sub-package under DHK_SCHEMA package. Select Analytic View option. two Table will be created "PURCHASE_ORDER" and "PURCHASE_DETAIL" with data. Right-Click ->New.'CASH'. SAP HANA Analytic View Creation We are going to create a SAP HANA Analytic View with name "AN_PURCHASE_ORDER". tables "PURCHASE_ORDER" and "PURCHASE_DETAIL". 'V000002'.'UNIT'."PURCHASE_DETAIL" VALUES(1000004. STEP 2) Information View editor will display for Analytic View – 1. 3.'GR1'.2000.4000.20000.104. with the already created attribute view "AT_PRODUCT".00. 2. Enter Analytic View Name as "AN_PURCHASE_ORDERS" and Label for it.'INR'.

Information View editor will be displayed for analytic view. . 4. Start Join: This node create join in order to join the attributes view with the fact table. Multiple tables can be added. 2. but measure from only one table can be selected. STEP 3) Add Table from Schema in Data Foundation node under Scenario pane. Drag and Drop table "PURCHASE_ORDER" and "PURCHASE_DETAIL" From DHK_SCHEMA to Data Foundation Node of Scenario pane. we add FACT table for Analytic View.Once data is selected. 3. click on Finish Button. There will be three nodes under Scenario Pane1. Data Foundation: In this node. Semantics: This node represents output structure of the view.

1. STEP 5) In the same window in detail panel do as directed. 1. To Table "PURCHASE_DETAIL" ON . Drag and Drop Attribute View in Star Join Node.STEP 4) Add attribute view in Star join Node. 2. Click on data foundation node. 2. Table added in data foundation node will display in Detail section. Select "AT_PRODUCT" Attribute view from Modelling package. Join Table "PURCHASE_ORDER" "PO_NUMBER" Field.

STORAGE_LOC from "PURCHASE_DETAIL" Table. 1. Select CURRENCY Column From "PURCHASE_DETAIL" Table.3. COMPANY. PRODUCT_ID. STEP 6) in the same window. Select GROSS_AMOUNT. Select PO_NUMBER. 4. Select PO_STATUS. "PURCHASE_HEADER" Table. TAX_AMOUNT. Enter Join type and Cardinality. 2. PLANT. 3. CREATED_BY. CREATED_AT Column From . PO_CATEGORY. Click on OK Button.

as below – Attribute view and fact table will be displayed in the detail pane. . STEP 7) Now we join attribute view to our fact table (data foundation).All selected column (Orange color) will display in the output of Analytic view. Now we Join attribute view to fact table as below Join Attribute View with Data Foundation on "PRODUCT_ID" Column. Click on Star join Node in semantic pane.

measure and key for the view. . Click On OK Button. Define Join type as "Referential" and Cardinality 1. we define attribute. 1. which is defined as a measure. 2.Click on Join link.. STEP 8) In this step. Select Columns Tab under Details pane. Define column type as attribute and measure. Select Semantics Node in Scenario Pane.. a Pop-Up for Edit Join will be displayed. 3. I have defined all column as attribute except "GROSS_AMOUNT".1.

Now analytic view "AN_PURCHASE_ORDERS" will be created and activated in Analytic Folder of Modelling Sub-package as – STEP 10) Preview Data in Analytic View.STEP 9) Validate and Activate Analytic view 1. . Go to the toolbar section and click on "Data Preview" Icon. 2. Activate Analytic view. Validate the analytic view. 2. Select Open in Data Preview Editor. 1.

and HTML format. We can select only one attribute at a time. We can see the output in Chart. Analysis – In this tab. Grid. Distinct values – Distinct values show distinct value for selected attribute. we have to drag and drop Attribute and measure in Label Axis and Value axis. . table.Again we use 3 options to see data in Data Preview Editor – 1. 2.

analytic views and calculation views. When there is need of More Fact table in information view then calculation view came in the picture. Raw Data – It will show in Table format from Raw Data tab as below – Note: SAP HANA Analytic view can contain only Attribute view and does not support Union. We can create Joins. column views. SAP HANA Analytic view measure can be selected from only one fact table. Unions. Aggregation. for . and Projections on data sources. Calculation View can contain multiple measures and can be used multidimensional reporting or no measure which is used in list type reporting. Calculation view supports complex calculation. SAP HANA Calculation View SAP HANA calculation view is a powerful information view.3. The data foundation of the calculation view can include tables.

we can select a measure from one table only. Aggregation.  Support OLTP and OLAP models. So in this case. Rank. we can use two different analytic view for each table and join them in calculation view. Projection. SAP HANA Calculation View are of two types – 1. STEP 1) In this step. .Characteristic of SAP HANA Calculation View as below –  Support Complex Calculation. So when there is a requirement for a view which contains measure from the different table then it cannot achieve by analytic view but by calculation view. 2. We are going to create a graphical Calculation View "CA_FI_LEDGER" by joining two Analytic View "AN_PURCHASE_ORDER" And "AN_FI_DOCUMENT". SAP HANA Graphical Calculation View (Created by SAP HANA Studio Graphical editor). SAP HANA Graphical Calculation View In SAP HANA Analytic view.  Support Union. CA_FI_LEDGER will display finance document detail related to a purchase order. Go to package (Here Modeling) and right click. language. 2. 3. Select Calculation View. 1. etc. currency conversion.  Support Client handling. Select New Option. SAP HANA Script-based calculations Views (Created by SQL Scripts by SAP HANA Studio).

right outer and text join. Join: This node is used to join two source objects and pass the result to the next node. The source can be n number of objects. Union: This is used to perform union all operation between multiple sources.A Calculation View Editor will be displayed. they are 1. in which Scenario Panel display as below – Detail of Scenario panel is as below –  Palette: This section contains below nodes that can be used as a source to build our calculation views. We have 5 different types of nodes.Note: We can only add two source objects to a join node. The join types can be inner. . left outer. 2.

6. 5. filter the data and create additional columns before we use it in next nodes like a union. We can define the partition and order by clause based on the requirement. 3. Rank: This is the exact replacement for RANK function in SQL. 7. 8. STEP 2) 1. 5. Click Aggregation node from palette and drag and drop to scenario area. Click Join Node from Palette and drag and drop to scenario area. Aggregation: This is used to perform aggregation on specific columns based on the selected attributes. Drag and drop analytic View "AN_PUCHASE_ORDER" "AN_FI_DOCUMENT" and from Content folder to Projection node and "Projection_FI" respectively. Renamed it to "Projection_PO". Join Join_1 node to Aggregation node. Join Projection_PO node to Join_1 node. . Click Projection node from palette and drag and drop to scenario area for FI Document analytic view. Note: We can only add one source objects in a join node.3. 4. 2. Join Projection_FI node to Join_1 node. aggregation and rank. Projection: This is used to select columns. 4. Click Projection node from palette and drag and drop to scenario area from Purchase order analytic view. Renamed it to "Projection_FI".

3. Select all column from Projection_FI node for output. .PO_NO. 2. PO_Number = Projection_FI. STEP 3) Click on Join_1 node under aggregation and you can see the detail section is displayed. Select all column from Projection_PO Node for output. 1.We have added two analytic views. for creating a calculation view. Join Projection_PO Node to Projection_FI node on column Projection_PO.

2. STEP 5) Now. Select Column for output from the Join_1 displayed on the right side in the detail window. click on Semantics Node. Click on Aggregation node and Detail will be displayed on right side of the pane. 1.STEP 4) In this step. .

from the top bar of the window. Mark ACC_DOC_NO as key. Mark PO_Number and COMPANY as Key. 1. STEP 6) Validate and Activate calculation View. Calculation View will be activated and will display under Modelling Package as below – .Detail screen will be displayed as below. mark key for this output. 1. Click on Activate Icon. 2. 2. 3. Define attribute and measure. Define attribute and measure type for the column and also. Click on Validate Icon.

SAP HANA Analytic Privileges are used to provide authorization on below information view –  Attribute View  Analytic View  Calculation View . SAP HANA Analytic Privileges is used for Security purpose.Select calculation view and right click ->Data preview We have added two analytic views GROSS_AMOUNT) from both analytic view. and select measure (TAX_AMOUNT. Data Preview screen will be displayed as below – SAP HANA Analytic Privileges Analytic Privileges restrict the user to view data for which they authorize. SQL Privileges provide authorization on object level not at a record level. so provide a record or row-level authorization "Analytic Privileges" will be used.

Click on 'OK' button. Enter Analytic Privileges Name / Label. by this Analytic we restrict the user to view data only for a company with value 1000. Package name is automatically selected. Step 3) Analytic Privileges editor will open as below1. 2. Step 1) Go To option as belowModelling package (Right Click) --> New -> Analytic Privileges. 3. In General Section name and Label is displayed. Selection option creates new. in next step Analytic Privileges editor will be displayed for add and edit privileges.Now we are going to create an Analytic Privileges and will assign to user "ABHI_TEST". . Step 2) New Analytic Privilege popup appear 1.

3. Click on Add button for selecting attribute for assign restriction. Click on the add button to assign a value to attribute for restriction. 4. 6. Select Calculation View (CA_FI_LEDGER) which we created earlier. Select Attribute Company. Assign Privileges validity. Assign Value by selecting Type / operator and value. 5. Validate and Activate Analytic Privileges. Click on Add Button for create validity of privileges. 7. 8.2. 9. an analytic privilege is created in Analytic Privileges folder under Modelling package as below - . Click on "Add Button" in Reference Models Section. Here we want to restrict to user see data of calculation view for the only company (1000).

A pop-up for Select Analytic Privileges will be displayed. . Click on Ok Button. 3.Step 4) Now we are going to assign Analytic Privileges to User "ABHI_TEST". 1. Analytic Privileges is added as below - Step 5) Now. we deploy this changes in user by clicking deploy button. Click on "+" Button. Select Analytic Privileges tab. Double click on User "ABHI_TEST" from Security -> Users. Select Analytic Privileges. 4. 2. 5. Enter Name of Analytic Privileges which we have created earlier. "ABHI_TEST" user have privileges to access modelling package.

3. Login to "ABHI_TEST" user by select HANAUSER system as below – 1. Step-6) Check Analytic Privileges Assign to user "ABHI_TEST" is working or not. Data Preview screen will be displayed as belowData in calculation view will be restricted for company code– 1000. A System HDB (ABHI_TEST") will be added to system list. and enter User Name/ password for user "ABHI_TEST". 2. Select "Add System with Different User". . Go to Content Folder -> Select Package -> Calculation View (CA_FI_LEDGER) ->Right Click -> Data Preview. ABHI_TEST user has no full access of data of Calculation view created by HANAUSER. as HANAUSER has created analytic privileges for restriction on this calculation view for the company -1000 and assign to ABHI_TEST user. Select HDB (HANAUSER) Current System and right click.A message is displayed as below – User 'ABHI_TEST' changed. So.

Information View. . Information Composer works same as SAP HANA Modeler and used by Business user with less technical knowledge. landscape to other or on the same system. see workbook and information views. Export: STEP 1) Go To File Menu->Choose Export. SAP HANA Import and Export Import and Export option of SAP HANA Provide features to move tables.SAP HANA Information Composer SAP HANA Information composer is a web application that allows us to do modelling and upload local data to SAP HANA database. Load data and create information view. This is Modelling environment for non-technical people like an end user. Role required for work with SAP HANA Information Composer –  IC_MODELLER: Used to allow the user to work with Information composer. A Large amount of data (up to 5 million of cell) can be uploaded using Information Composer.  IC_PUBLIC: Used to allow the user to work with information composer.

 Delivery Unit: Delivery Unit is a single unit. SAP HANA Content  Change and Transport System (CTS): Used for export information view with ABAP program.  Landscape: Used for an export landscape from one system to another. etc.). view. .  Developer Mode: This option can be used to export individual objects to a location in the local system.A Pop-Up for Export will be displayed – There are two Export options for SAP HANA Object will be displayed – 1. 2. SAP HANA  Catalog Objects: Used for export catalog objects (table. This option is used to export multiple package which is mapped to single delivery unit. procedure.

 SAP Support Mode: This can be used to export the objects with the data for SAP support purposes. . Import: STEP 1) Go To File Menu->Choose Import.

Procedure.xls.A pop-up for Import Option will be displayed – There are two Import option for SAP HANA Object will be displayed – 1.csv. This option is used to import multiple package which is mapped to single delivery unit.xlsx file in table. SAP HANA o Catalog Objects: Used for import catalog objects (table. o ESRI Shape files: Environmental System Research Institute. . o Delivery Unit: Delivery Unit is a single unit. SAP HANA Content o Data from Local file: Used for import data from . view. o Landscape: Used for import landscape from one system to another.). . (ESRI) shape file format are used to store geometry data and attribute information for the spatial features in a data set. 2. Inc. etc. .

o Selective Import of Metadata: This can be used to import the Metadata of Single objects into SAP HANA. SAP HANA Performance Optimization Technique There are the following rule for performance Optimization Technique – . o SAP Net weaver BW models: This can be used to import BW Models into SAP HANA. o Mass Import of Metadata: This can be used to import the Metadata of Mass objects.o Developer Mode: This option can be used to import individual objects to a location in the local system.

Use UNION instead of it. We need to Re-Map it. Hierarchies of attribute view is not visible in calculation view.  SAP HANA Attribute Creation for Product Table.  Avoid JOIN nodes in calculation view. Analytic Privileges. User.  SAP HANA Analytic View creation for Purchase Order.  SAP HANA Calculation View creation on two analytic views. All Information View and Table view should be used with a projection node.  The calculation should be done before aggregation.  SAP HANA Analytic Privileges creation and assign to other user. Information view.  Creating Package (Structural / Non-Structural) in SAP HANA. we have learnt about Modelling Concept (Joins.  Hierarchies of attribute view is visible in Analytic view.  The label of attribute and description of measure defined in Attribute view.  SAP HANA Modelling Best Practices. and Role.  Do Not Mix CE Function and SQL script in Information model. Summary: In this tutorial of SAP Hana.  Use Input Parameters / Variable to restrict the dataset within Analytic / Calculation View.  Hierarchies need to re-define in Calculation view.). Projection Node improves performance by narrowing the column set. etc. .  SAP HANA Modelling  Different type of Joins in SAP HANA.  By applying filters at projection nodes.  SAP HANA Information composer Overview. Package. Analytic view and Calculation view will not display in calculation view. Apart from these we have learned in details about.

In this tutorial.  How to use SAP HANA Performance Optimization Technique. SAP HANA Security Security in SAP HANA means protecting important data from unauthorized access and ensures that the standards and compliance meet as security standard adopted by the company. in which multiple databases can be created on single SAP HANA System. you will learn  SAP HANA Security Overview  SAP HANA Authentication  SAP HANA Authorization  SAP HANA User and Role Administration  SAP HANA License Management  SAP HANA Auditing SAP HANA Security: Overview SAP HANA provides a facility i. So SAP HANA provide all security related feature for all multitenant database container. Multitenant database. It is known as multitenant database container. Different method of SAP HANA Import and Export. SAP HANA Provide following security-related feature –  User and Role Management  Authorization  Authentication  Encryption of data in Persistence Layer  Encryption of data in Network Layer SAP HANA User and Role .e.

SAP application (ERP.) connects to database only with the help of a technical user or database administrator (Basis Person). In this architecture. SAP HANA can be used as a relational database in a 3-Tier Architecture. The end-user cannot directly access to database or database server. and auditing) are installed on application server layers. BW.SAP HANA User and Role management configuration depend on the architecture as below – 1. etc. 2-Tier Architecture. security features (authorization. Web Server and Development Environment are embedded in a single system. in which Application server. . SAP HANA Extended Application Services (SAP HANA XS) is based on 2 –Tier Architecture. authentication. 3-Tier Architecture. encryption. 2.

 Security Assertion Markup Language(SAML) SAML can be used to authenticate SAP HANA User. It is a process of mapping external user identity to the internal database user. which is configured and issued to the user for creating a ticket.SAP HANA Authentication Database user identifies who is accessing the SAP HANA Database. who is accessing SAP HANA Database directly through ODBC/JDBC.  SAP Logon and Assertion Tickets The user can be authenticated by Logon or Assertion Tickets. then SAP HANA Database authenticate the user. SAP HANA supports following authentication method   Kerberos: It can be used in the following case – o Directly from JDBC and ODBC Client (SAP HANA Studio). o When HTTP is used to access SAP HANA XS. so user can login in sap database with the external user id. . Single Sign-on (SSO) are used to integrate several Authentication method. User Name / Password When the user enters their database username and password." SAP HANA support many authentication methods. It is verified through a process Named "Authentication.

HANA System performs authorization check on the user through user roles and directly grants the privileges. Depending on the authorization provided to the user. HANA system skips further checks and grant access to request database objects. Client certificates signed by a trusted Certification authority (CA) can be used to authenticate the user. All Privileges assign to users are combined as a single unit. When a user tries to access any SAP HANA Database object. X. "privileges. In SAP HANA following privileges are their Privilege Description s Types System It controls normal system activity. SAP HANA Authorization SAP HANA Authorization is required when a user using client interface (JDBC. it can perform database operations on the database object. or HTTP) to access the SAP HANA database. ODBC." The Privileges can be granted to the user directly or indirectly (through roles). When requested Privileges found. Privileges System Privileges are mainly used for –  Creating and Deleting Schema in SAP HANA Database  Managing user and role in SAP HANA Database  Monitoring and tracing of SAP HANA database  Performing data backups  Managing license  Managing version  Managing Audit . This authorization is called.509 Clients Certificates When SAP HANA XS Access by HTTP.

TRIGGER. SELECT. DEBUG. Object Privileges Object Privileges are as below –  CREATE ANY  UPDATE. DROP. Analytic View. Package Package Privileges are used to provide authorization for actions on Privileges individual packages in SAP HANA Repository.  Analytic Privileges grants different user access on different part of data in the  Same information view based on user role. etc. INSERT. calculation View). Application Privileges are required in In SAP HANA Extended Application Services (SAP HANA XS) for access application.) or non-catalog objects (development objects). which can grant by the user on own user. Object privileges can be granted to catalog objects (table. To access database objects user needs object privileges on database objects or on the schema in which database object exists. on User .  Analytic Privileges are used in SAP HANA database to provide row level data Control for individual users to see the data is in the same view. Importing and Exporting content  Maintaining Delivery Units Object Privileges are SQL privileges that are used to give authorization to read and modify database objects. REFERENCES Analytic Privileges are used to allow read access on data of SAP HANA Information model (attribute view. Applicatio n Application privileges are granted and revoked through the Privileges proceduresGRANT_APPLICATION_PRIVILEGE and REVOKE_APPLICATION_PRIVILEGE procedure in the _SYS_REPO schema. DELETE. EXECUTE  INDEX. ALTER. Analytic Privileges  This privilege is evaluated during query processing. view. Privileges It is an SQL Privileges.

Restricte Restricted User has no full SQL RESTRICTED_USER_ODBC_ACCESS or d User Access via an SQL Console and RESTRICTED_USER_JDBC_ACCESS created with "CREATE RESTRICTED role required to user for Full Access of USER" statement. Standard User d User system views. Database or Real User: Each user who wants to work on SAP HANA database.ATTACH DEBUGGER is the only privilege that can be granted to a user. These users are created for an administrative task such as creating an object and granting privileges on database object or on the application. SAP HANA Database system provides following user by default as standard user–  SYSTEM  SYS  _SYS_REPO 2. these users don't get deleted from the database. If Privileges ODBC/JDBC functionality required for use of any application. created with "CREATE USER" statement. Depending on the different security policy there are two types of user in SAP HANA as below – 1. SAP HANA User Administration and Role Management To Access SAP HANA Database. Normally. need a database user. There are two types of Database user as below – User Type Description Role assigned This user can create objects in an own schema and reads data in Standar PUBLIC role is assigned for read system views. Technical User (DBA User) – It is a user who directly work with SAP HANA database with necessary privileges. Database user are a real person who works on SAP HANA. then they are provided through the . users are required.

4.  ODBC/JDBC access for client connection must be enabled with SQL statement. Define and Create Role. Go to security node. Step 1) To create new user in SAP HANA Studio go to security tab as shown below and follow the following steps.role. Create/delete User.  Restricted User connects to database through HTTP Only. . 1. 1.  Restricted User cannot create database objects. SAP HANA User Administrator have access to the following activity – 1. Grant Role to the user. 3. 2. Step 2) A user creation screen appear. Select Users (Right Click) -> New User. 3. Enter User Name.only database user with ROLE ADMIN privileges can create user and role in SAP HANA. Resetting user password. 5.  Restricted User cannot view data in the database. Re-activate / de-activate user according to requirement. Create User in SAP HANA. 2.

4. A role can contain following privileges –  System Privileges for administrative and development task (CATALOG READ. 5. DELETE. etc. It is a standard mechanism to grant privileges. by default User name / password is used for authentication. 2. etc.)  Analytic Privileges for SAP HANA Information View  Package Privileges on repository REPO.g. MODELLING.)  Object Privileges for database objects (SELECT. Define and Create Role A role is a collection of privileges that can be granted to other users or role. INSERT. AUDIT ADMIN. etc. By Clicking on the deploy Button user will be created. etc. These are authentication mechanism. We can use the standard role as a template for creating a custom role. MONITORING.)  Application Privileges for SAP HANA XS applications. . packages (REPO.) available in SAP HANA database. The role includes privileges for database object & application and depending on the nature of the job. There are many standard roles (e. Enter Password for the user.EDIT_NATIVE_OBJECTS.READ. Privileges can be directly granted to the user.

Privileges on the user (For Debugging of procedure).

Role Creation
Step 1) In this step,
1. Go to Security node in SAP HANA System.
2. Select Role Node (Right Click) and select New Role.

Step 2) A role creation screen is displayed.

1. Give Role name under New Role Block.
2. Select Granted Role tab, and click "+" Icon to add Standard Role or exiting
3. Select Desired role (e.g. MODELLING, MONITORING, etc.)
STEP 3) In this step,

1. Selected Role is added in Granted Roles Tab.
2. Privileges can be assign to the user directly by selecting System Privileges,
object Privileges, Analytic Privileges, Package Privileges, etc.
3. Click on deploy icon to create Role.

Tick option "Grantable to other users and roles", if you want to assign this role to
other user and role.
3. Grant Role to User
STEP 1) In this step, we will Assign Role "MODELLING_VIEW" to another user
1. Go to User sub-node under Security node and double click it. User window will
2. Click on Granted roles "+" Icon.
3. A pop-up will appear, Search Role name which will be assign to the user.

STEP 2) In this step, role "MODELLING_VIEW" will be added under Role.

STEP 3) In this step,
1. Click on Deploy Button.
2. A Message " User 'ABHI_TEST" changed is displayed.

4. Resetting User Password
If user password needs to reset, then go to User sub-node under Security node and
double click it. User window will show.
STEP 1) In this step,
1. Enter new password.

2. Enter Confirm password.

STEP 2) In this step,
1. Click on Deploy Button.
2. A message "User 'ABHI_TEST" changed is displayed.

5. Re-Activate/De-activate User
Go to User sub-node under Security node and double click it. User window will show.
There is De-Activate User icon. Click on it

A confirmation message "Popup" will appear. Click on 'Yes' Button.

A message "User 'ABHI_TEST' deactivated" will be displayed. The De-Activate icon
changes with name "Activate user". Now we can activate user from the same icon.
SAP HANA License Management

Authorization of License Management "LICENSE ADMIN" privileges are required for License Management.  Temporary License Key: This is automatically installed with a new SAP HANA Database Installation. Authorization for SAP HANA Auditing "AUDIT ADMIN" System Privileges required for SAP HANA Auditing. Summary: In this tutorial. we have learned following topic  SAP HANA Security overview. SAP HANA Auditing SAP HANA Auditing features allow you to monitor and record action which is performed in SAP HANA System.  SAP HANA Authorization in detail. It is valid for 90 days and later can apply for Permanent key from SAP. SAP HANA HDBSQL Command Line tool.  SAP HANA Role Auditing Process.  SAP HANA Role Administration method  SAP HANA license Management process. and HANA SQL Query editor.The license key is required to use SAP HANA Database. If license key expires then Temporary License Key are is automatically installed for 28 days. . This features should be activated for the system before creating audit policy.  SAP HANA User Administration method. We need to request and apply license key before expire. SAP HANA database support two types of license key –  Permanent License Key: Permanent license keys are valid till expiration date. A license key can be installed and deleted using SAP HANA Studio.  SAP HANA Authentication in detail.

ODBC.SAP HANA Reporting We have till now loaded data from SAP Source. So by installing SAP HANA Client software (*. In this tutorial. The choice of reporting tool depends upon the type of reports that are required. and Calculation View). Analytic View. and Flat file through SAP SLT.exe file) will make all the drivers available on the PC for connecting to reporting tools to SAP HANA. and ODBO in reporting tool are part of SAP HANA Client. SAP BODS and created information view (Attribute View. and Microsoft Excel to access SAP HANA information view in this tutorial. Now we will discuss the information view in reporting tools –The drivers like JDBC. Non-SAP. SAP Lumira. We will use SAP BO. you will learn Reporting In SAP BI (Business Intelligence) Overview  Reporting In Webi of SAP Business Objects (BO) on HANA  Reporting In Crystal Report .

ODS. Database Server – In this. Infocube. In BI (Business Intelligence) raw data will be cleaned.It displays the data to the user. 3. data is physically stored in PSA. which provides the user friendly environment. SAP Bex Query Designer (Component of SAP BI) can access SAP HANA View as info provider and display data in Bex. processed and provide meaningful information to the user. Application Server – It is used to access data from database server and process data for Presentation server. BI is a SAP Product. Presentation Server. . but when we migrate from source data to SAP HANA then architecture will be as belowSAP BI is three tier architecture – 1. Reporting In SAP Lumira  Reporting In Microsoft Excel Reporting in SAP BI (Business Intelligence) Overview SAP BI is a data warehousing and reporting tool. 2. business logic applied. SAP BI support many databases.

These drivers act as an intermediate between SAP HANA and client reporting tools when presenting data to the user.Reporting in Webi of SAP Business Object (BO) from HANA SAP Business Objects Web Intelligence (SAP BO WebI) is part of the SAP Business Objects Platform (SBOP) client tools family.  Webi display the result in tabular or graphical formats.  Webi is used for detail level report. . Features of SAP BO WebI is as below –  Webi is adhoc reporting tool.  User can create / modify their own queries for the report. SAP Business Objects tool use the JDBC/ODBC driver to connect to the source system. After installing SAP HANA client. JDBC/ODBC driver will be installed on PC.

SAP BO Server and SAP BO Platform (SBOP) client tools. Create Universe using Information Design Tool Step 1) In this step. we will create a universe Using Information Design Tool (IDT). HANA can be accessed via ODBC and JDBC drivers. 1. and its tables can be defined and queried with SQL language. Launch IDT by navigating to Start Menu -> SAP Business Intelligence -> SAP Business Objects BI platform 4 Client Tools -> Information Design Tool . Tables are managed with a tool called HANA Studio.

2. Click on New option. Select Project. enter following details: 1.Information Design tool screen will appear. . To create a universe we need a project in IDT.In this pop-up. 3. 2. Select Project option. Click on finish button. Enter name of project 2. 2. Or 1. Click On New File Icon. Click On File. Navigate to Project Option as below1. A pop-up for New Project will appear.

Oracle. Microsoft. There are two connections available.> New -> Relational Connection. A Pop-Up for New Relation Connection source name appear- . detail of each is as below – 1. So go to Project . 2. OLAP Connection – To access data from the application (SAP. Relational Connection – To access data from a table and access regular RDBMS use Relational Connection. Step 2) Now we create a Relational connection. A project is a local workspace where you store the resources used to build one or more universes. SAP BO) and data stored in Cube / Information View use OLAP connection.Project Name "WEBI_DHK_HANA" will appear under Local Projects Tab as below.

A Pop-Up for Database Middleware Driver Selection will appear1. 2.1. 2. . Enter Resource Name. Click on Next Button. Select JDBC Drivers option under SAP HANA Database 1.0. Click on Next Button.

4. Select Single server in DATA Source section. 1. Enter Password. Enter Instance Number. enter following details into it. Click on Test Connection button to verify the connection. 3. Enter HANA User Name.A pop-up for New Relational Connection parameter will be displayed. 2. 6. . Enter Host Name (here best: 30015). 5. Authentication Mode will be selected as "Use Specified User Name and Password".

Step 3) To consume Universe by Web Intelligence. now we publish connection for SAP HANA. So.A pop-up for Test Connection successful will be displayed. Select SAP HANA. we need to publish the connection.cnx will be created. a connection with name SAP HANA. After successful Connection.cnx.cnx connection under Project "WEBI_DHK_HANA" and right click. Dashboards or Crystal Report for Enterprise. . 1.

A pop-up for publishing connection to repository appears – 1.2. . A Publish connection with name SAPHANA. 3. 2. Select Business IDT.cns will be created after successful publish in the repository. Click on finish button. Select Publish Connection to a repository.

we use SAP HANA Business Layer as below SAP HANA Business Layer . Universe allow the user to interact with data without knowledge of complexities of the database). To create universe.A pop-up "The connection was published successfully" will be displayed. Now we create Universe by using SAP HANA Business Layer. Step 4) Create Universe (Universe is a business representation of your data warehouse or transactional database.

Enter Description. SAP HANA Business Layer automatically detects the input parameter and variables. SAP HANA Business Layer automatically creates a data foundation and business layer based on selected SAP HANA Views. 2. Enter Business Layer Name. Select Project Created "WEBI_DHK_HANA". 3. 4. 3. We Create Universe through SAP HANA Business Layer as below1. 2. Click On Next Button. Select option "SAP HANA Business Layer".1.From SAP BOBI 4. Right click the project and select a new option. . we need to create a derived table while building data foundation and map the variable and input parameters. A Pop-up for SAP HANA Business Layer appears1. Enter Data Foundation Name. SAP provides a new option "SAP HANA Business Layer" while creating the universe using Information Design tool.1 version. Before SAP BOBI 4.

Tick on Connection "SAPHANA. 2. .cnx". 1. A Pop-up for selecting SAP HANA Information Model will be displayed. 2.A Pop-up for Select SAP HANA Connection displayed1. Click on Finish Button. Now Select Analytic View (AN_PURCHASE_ORDERS) Created under HANAUSER Package. Click on Next Button.

object (Connection. Business Layer shows Business view of Analytic view.) stored in the repository will be displayed. In repository resource section. . etc. Under Project. Data Foundation shows table and column name. 2. and Data Foundation will be displayed. Business Layer. 4.The analytic view will open in Information Design tool. Step 5) Detail of Information Design tool will be as below1. 3. It is for Technical Person.all Relational Connection. It is for Functional Person. Business Layer.

Select data foundation section. 2.Step 6) In this step. Now follow points as below1. Select Business layer section. displayed under Analytic View . Dragged field will be (AN_PURCHASE_ORDER). It will display objects under Analytic View 4. Drag and drop column to Analytic View 3. go to the folder with the name of Analytic View.

. save all object. Go to file and click on "Save All" option to save all objects.Step 7) In this step.

Drag and drop them to "Result object for Query #1 "section. 4. 3.After that. 2. . follow the step below. Step 8) Create a Query and view output. Go to Queries option. 1. Result will be displayed. 5. A Query panel will be displayed. Select the field to which you want to include in Query. Click on Refresh Button on Result set section.

explore. which can be run on web or enterprises applications. visualize and provide report. With SAP Crystal Report we can create simple report or complex report. .Reporting in SAP Crystal Report SAP Crystal Report help us to design.

 If you want to create SQL Expressions  If you want to execute a view with parameters or variables and submit nondefault values 2. Crystal Report for Enterprises: This will be used when  If there are Universe available or needed. then use SAP Crystal Reports Enterprises. Step 1) Login into Crystal Report for Enterprises. Crystal Report 2011 /13 /16: This will be used when –  If you want to call a HANA stored procedure from Crystal Reports. We will use crystal reports for enterprises.There are two types of SAP Crystal Reports – 1. SAP Crystal reports for Enterprises will be displayed as below- .

It is Report Formatting section. Group tree. etc. 5. Detail of Data Explorer. This is an icon for the window (Data Explorer. Find). Work Area for Report. will be displayed. outline. 4. Report Page Formatting option.1. Find. Step 2) Now we create a connection for the data source. Group tree. outline. which provides a different tool for formatting. 3. Click on Choose data Source option from Data Explorer- . 2.

A pop-up for Choose a data source type will be displayedSelect Browse option from SAP HANA Platform Section. Enter Connection Display Name (saphana). Click on Add Button. . Click on "New Server" Button. A window for Server connection will be displayed as below1. A pop-up for connecting to the server will be displayed. 2.

Click on the OK button. Enter HANA Server Instance Name. A pop-up for Test connection logon. Step 3) In this step. A message for connection successful will be displayed. 6. We will do the following thing . Enter HANA username. 8. Enter HANA Server name. Enter password for SAP HANA user. 9. Click on "Test Connection "Button. 5.3. A connection Name will appear in the connection list. A pop-up for connecting to the Server will display. 4. 1. Click on OK Button. 7.

2. 1. . Select server "saphana." 2. Click on OK button A pop-up for entering a password will be displayed. 2) In this step. One more pop-up will appear for selecting HANA View. Select HANA View (Analytic View AN_PURCHASE_ORDERS). enter the password and then click OK.1. Click on OK Button. we select SAP HANA View.

Click on Refresh button. Drag and Drop required field in Query. 2. a window for Query will open. Select required column from the list for the query. Click on button.3. 5. The result set will be displayed. . 4. In this step. 3. Follow below point to create a query1.

and charts. and other source. In SAP Lumira. the following steps need to be done to visualize data. SAP Lumira can import data from Excel. SAP HANA Perform visual BI analysis using dashboard.Report Output will be displayed as below- Reporting in SAP Lumira SAP Lumira is new software by SAP to Analyze and Visualize data. SAP Lumira can access information view of SAP HANA directly. . infograpg. By SAP Lumira user can create a beautiful and interactive map.

Stories 4. Detail about this screen as below1. and Help. so firstly we login in SAP Lumira by Click on SAP Lumira Client icon on desktop as below- Step 1) Create a Document and acquire a data set After open SAP Lumira.Now we visualize SAP HANA View in SAP Lumira. SAP Lumira Cloud – By using this option. View. Data. 3. Application Toolbar – It contains toolbar like File. Home Link – By using this option we can go to home screen. 2. Connections – W can see all connection here. Edit. Visualizations 3. My Document Sections 1. we can use cloud options. screen open for work on SAP Lumira. 5. . Datasets 4. Documents 2.

click on Document option on My Items section to create a Documents – 1. SAP Lumira supports below dataset –  Microsoft Excel .. click on file option 2. Go to file application Toolbar.So. Select New Option.

Click on Next Button. 1. 2. So select Connect to SAP HANA. . Text  Copy from clipboard  Connect to SAP HANA  Download From SAP HANA  Universe  Query With SQL  Connect to SAP Business Warehouse  SAP Universe Query Panel Step-2) Connect to SAP HANA Here we will connect to SAP HANA and access SAP HANA Information View.

A pop-up for SAP HANA Server Credential will be displayed as below1. 2. Enter SAP HANA Password. Enter SAP HANA Server name. Select SAP HANA View ("AN_PURCHASE_ORDERS" here). Click on "Connect" Button to Connect to SAP HANA Server. Step 3) Access SAP HANA Analytic View A window for select SAP HANA View will appear as below1. 3. . we will connect to SAP HANA and able to access SAP HANA view. Click on Next Button. 2. 4. Enter SAP HANA User Name. Enter SAP HANA Instance no. After clicking on Connect button. 5.

2. The next window for select Measures and Dimensions will be displayed – 1. All Measure will be grouped under Measure sections. All Dimension will be grouped under Dimension Sections. Click on Create Button. .Step 4 ) Define Dimension and Measure. 3.

We can access it only from "_SYS_BIC" Schema. . A Visualize screen will appear. a Column View with the similar name of information view. Different Chart Type can be selected from Chart Builder Section. which select column view under "_SYS_BIC" Schema – 1. 1. Select Column Chart option. After activating Information View in SAP HANA. Click On Chart Builder Icon.Step 5) Visualize SAP HANA Analytic View in SAP Lumira. 2. under "_SYS_BIC" Schema created in SAP HANA catalog node. When we need to access any SAP HANA Information View outside from SAP HANA.

Click on the icon in front of "DIMENSIONS" Section. 5. "PRODUCT_ID". 3. 4. Click On "+" icon in front of MEASURES Section to Add Measure in Y Axis format. Select "CATEGORY". "PRODUCT_NAME" from Dimension List to display on X Axis. We have added "GROSS_AMOUNT" AND "TAX_AMOUNT" Measure. A list of all available dimension appear. .2.

Clear. we can create report quickly by pivot tables and charts. We can access only SAP HANA information view which has a property as 'CUBE' in semantic. 2. etc. By Only MDX Query we can access sap Hana hierarchies. Ranking. MS Office uses MDX language ((Multi Dimension Expression language) to access data from SAP HANA. MDX Language is used by reporting tool to access data from a multi-dimensional object in a database environment. so we cannot access attribute view by MS Excel.SAP HANA Analytic view will be displayed in visualize tab of SAP Lumira. The output of SAP HANA Analytic views in SAP HANA lumira. Reporting in Microsoft Excel Microsoft excel has powerful reporting inbuilt option. Tool for Ascending / descending. 3. Connecting Drivers. refresh. This can be used for Filtering. in which we have different screen as below1. .MS Excel uses ODBO (OLE DB FOR OLAP) drivers for connecting to SAP HANA database.

Click on "From Other Sources" Icon. Open MS Excel. 2. Select From Data Connection Wizard. Go to Data Tab.Now we will access SAP HANA database from SAP HANA as shown in steps below – Step 1) Connect To SAP HANA Excel1. 3. .

Select "Other / Advance" option. . Click on Next Button.A screen for Data connection wizard will be displayed as below1. 2.

A window for "Data Link Properties "will be open as below1. Select "SAP HANA MDX Provider "under Provide Tab.
2. Click on Next Button.

A window for data link properties will be displayed –
Enter the following detail as below –
1. Enter Host Name of SAP HANA Database.
2. Enter Instance number of SAP HANA database.
3. Enter Username / password for SAP HANA database.
4. Enter Language name.
5. Click on "Test Connection" to test the connection to SAP HANA Database from

A message "Test connection succeeded" will be pop-up.

Click on the OK button.
Step 2) Till now we had created a connection from EXCEL to SAP HANA and tested
the connection. Now we access SAP HANA Information View from Excel.
Now a window for "Data connection wizard" will be displayed.

1. Select the package in which contains SAP HANA Information View.
2. Select Information View (Analytic View, Calculation View).
3. Click on Next Button.

A new window for data connection File will appear, enter following details.
1. Give File Name (AV_SALES).
2. Tick option "Save password in file", for avoid to enter a password while
open excel file.
3. A Pop-up for save password security related will be displayed.
4. Click on Finish Button.

Step 3) Now SAP HANA Information View will be displayed in Excel as pivot table as below – Summary: We have learned in this tutorial below topic –  Reporting in SAP BI overview  Reporting in SAP BO Webi with an example of SAP HANA information View. .

 Reporting in SAP Lumira with an example of SAP HANA information View.  Reporting in Microsoft Excel by consuming SAP HANA Information view. Reporting in SAP Crystal Report Enterprises with an example of SAP HANA information View. .