STRATEGY & CREATIVITY

SAP HANA In Memory Database.

PORTFOLIO

We pride ourselves on bringing a good technology and effective knowledge to every perfect one.

  • Bi 4.0 Connectivity to Hana Views

    Reporting Tools

    Web Intelligence and Crystal Reports are most common BI tools that are used for reporting. WebI uses a semantic layer called Universe to connect to data source and these Universes are used for reporting in tool. These Universes are designed with the help of Universe design tool UDT or with Information Design tool IDT. IDT supports multisource enabled data source. However, UDT only supports Single source.
    Main tools that are used for designing interactive dashboards- Design Studio and Dashboard Designer. Design Studio is future tool for designing dashboard, which consumes HANA views via BI consumer Service BICS connection. Dashboard design (xcelsius) uses IDT to consume schemas in HANA database with a Relational or OLAP connection.
    SAP Lumira has an inbuilt feature of directly connecting or loading data from HANA database. HANA views can be directly consumed in Lumira for visualization and creating stories.
    Office Analysis uses an OLAP connection to connect to HANA Information views. This OLAP connection can be created in CMC or IDT.
    Reporting Tools
    In the picture given above, it shows all BI tools with solid lines, which can be directly connected and integrated with SAP HANA using an OLAP connection. It also depicts tools, which need a relational connection using IDT to connect to HANA are shown with dotted lines.

    Relational vs OLAP Connection

    The idea is basically if you need to access data from a table or a conventional database then your connection should be a relational connection but if your source is an application and data is stored in cube (multidimensional like Info cubes, Information models) then you would use an OLAP connection.
    • A Relational connection can only be created in IDT/UDT.
    • An OLAP can be created in both IDT and CMC.
    Another thing to note is that a relational connection always produces a SQL statement to be fired from report while an OLAP connection normally creates a MDX statement

    Information Design Tool

    In Information design tool (IDT), you can create a relational connection to an SAP HANA view or table using JDBC or ODBC drivers and build a Universe using this connection to provide access to client tools like Dashboards and Web Intelligence as shown in above picture.
    You can create a direct connection to SAP HANA using JDBC or ODBC drivers.
  • SAP HANA - Reporting View

    We know that with the use of Information Modeling feature in SAP HANA, we can create different Information views Attribute Views, Analytic Views, Calculation views. These Views can be consumed by different reporting tools like SAP Business Object, SAP Lumira, Design Studio, Office Analysis and even third party tool like MS Excel.
    These reporting tools enable Business Managers, Analysts, Sales Managers and senior management employees to analyze the historic information to create business scenarios and to decide business strategy of the company.
    This generates the need for consuming HANA Modeling views by different reporting tools and to generate reports and dashboards, which are easy to understand for end users.
    Reporting and Analysis
    In most of the companies, where SAP is implemented, reporting on HANA is done with BI platforms tools that consume both SQL and MDX queries with help of Relational and OLAP connections. There is wide variety of BI tools like − Web Intelligence, Crystal Reports, Dashboard, Explorer, Office Analysis and many more.
  • SAP HANA

    In Memory Computing.


    SAP HANA Tutorial                                                                

    SAP HANA - Home

    SAP HANA Introduction                                                        

    SAP HANA - Overview

    In-Memory Computing Engine

    SAP HANA - StudioStudio Administration View

    SAP HANA - System Monitor

    SAP HANA - Information Modeler

    SAP HANA - Core Architecture

    SAP HANA Modeling                                                              

    SAP HANA - Modeling

    SAP HANA - Data Warehouse

    SAP HANA - Tables

    SAP HANA - Packages

    SAP HANA - Attribute View

    SAP HANA - Analytic View

    SAP HANA - Calculation View

    SAP HANA - Analytic Privileges

    SAP HANA - Information Composer

    SAP HANA - Export and Import

    SAP HANA Reporting                                                            

    SAP HANA - Reporting View

    Bi 4.0 Connectivity to HANA Views

    SAP HANA - Crystal Reports

    SAP HANA - Excel Integration

    SAP HANA Security                                                               

    SAP HANA - Security Overview

    User Administration & Management

    SAP HANA - Authentications

    SAP HANA - Authorization methods

    SAP HANA - License Management

    SAP HANA - Auditing

    SAP HANA Data Replication                                                 

    SAP HANA - Data Replication Overview

    SAP HANA - ETL Based Replication

    SAP HANA - Log Based Replication

    SAP HANA - DXC Method

    SAP HANA - CTL Method

    SAP HANA - MDX Provider

    SAP HANA Monitoring                                                           

    SAP HANA - Monitoring and Alerting

    SAP HANA - Persistent Layer

    SAP HANA - Backup & Recovery

    SAP HANA - High Availability

    SAP HANA - Log Configuration

    SAP HANA SQL                                                                      

    SAP HANA - SQL Overview

    SAP HANA - Data Types

    SAP HANA - SQL Operators

    SAP HANA - SQL Functions

    SAP HANA - SQL Expressions

    SAP HANA - SQL Stored Procedures

    SAP HANA - SQL Sequences

    SAP HANA - SQL Triggers

    SAP HANA - SQL Synonym

    SAP HANA - SQL Explain Plans

    SAP HANA - SQL Data Profiling

    SAP HANA - SQL Script

    SAP HANA Useful Resources                                               

    SAP HANA - Questions and Answers

    SAP HANA - Quick Guide

    SAP HANA - Useful Resources

    SAP HANA - Discussion

  • SAP HANA - Export & Import

    HANA Export and Import option allows tables, Information models, Landscapes to move to a different or existing system. You do not need to recreate all tables and information models as you can simply export it to new system or import to an existing target system to reduce the effort.
    This option can be accessed from File menu at the top or by right clicking on any table or Information model in HANA studio.
    Explain and Import

    Exporting a table/Information model in HANA Studio

    Go to file menu → Export → You will see options as shown below −
    Explain Destination

    Export Options under SAP HANA Content

    Delivery Unit

    Delivery unit is a single unit, which can be mapped to multiple packages and can be exported as single entity so that all the packages assigned to Delivery Unit can be treated as single unit.
    Users can use this option to export all the packages that make a delivery unit and the relevant objects contained in it to a HANA Server or to local Client location.
    The user should create Delivery Unit prior to using it.
    This can be done through HANA Modeler → Delivery Unit → Select System and Next → Create → Fill the details like Name, Version, etc. → OK → Add Packages to Delivery unit → Finish
    Delivery Unit
    Once the Delivery Unit is created and the packages are assigned to it, user can see the list of packages by using Export option −
    Go to File → Export → Delivery Unit →Select the Delivery Unit.
    You can see list of all packages assigned to Delivery unit. It gives an option to choose export location −
    • Export to Server
    • Export to Client
    Export Through Delivery Unit
    You can export the Delivery Unit either to HANA Server location or to a Client location as shown.
    The user can restrict the export through “Filter by time” which means Information views, which are updated within the mentioned time interval will only be exported.
    Select the Delivery Unit and Export Location and then Click Next → Finish. This will export the selected Delivery Unit to the specified location.

    Developer Mode

    This option can be used to export individual objects to a location in the local system. User can select single Information view or group of Views and Packages and select the local Client location for export and Finish.
    This is shown in the snapshot below.
    Developer Mode

    Support Mode

    This can be used to export the objects along with the data for SAP support purposes. This can be used when requested.
    Example − User creates an Information View, which throws an error and he is not able to resolve. In that case, he can use this option to export the view along with data and share it with SAP for debugging purpose.
    Support Mode
    Export Options under SAP HANA Studio −
    Landscape − To export the landscape from one system to other.
    Tables − This option can be used to export tables along with its content.

    Import Option under SAP HANA Content

    Go to File → Import, You will see all the options as shown below under Import.

    Data from Local File

    This is used to import data from a flat file like .xls or .csv file.
    Import
    Click on Nex → Choose Target System → Define Import Properties
    Select Source file by browsing local system. It also gives an option if you want to keep the header row. It also gives an option to create a new table under existing Schema or if you want to import data from a file to an existing table.
    Data from Local File1
    When you click on Next, it gives an option to define Primary Key, change data type of columns, define storage type of table and also, allows you to change the proposed structure of table.
    Data from Local File2
    When you click on finish, that table will be populated under list of tables in mentioned Schema. You can do the data preview and can check data definition of the table and it will be same as that of .xls file.
    Import Data from Local File

    Delivery Unit

    Select Delivery unit by going to File → Import → Delivery unit. You can choose from a server or local client.
    You can select “Overwrite inactive versions” which allows you to overwrite any inactive version of objects that exist. If the user selects “Activate objects”, then after the import, all the imported objects will be activated by default. The user need not trigger the activation manually for the imported views.
    Import Through Delivery Unit
    Click Finish and once completed successfully, it will be populated to target system.

    Developer Mode

    Browse for the Local Client location where the views are exported and select the views to be imported, the user can select individual Views or group of Views and Packages and Click on Finish.

    Mass Import of Metadata

    Go to File → Import → Mass Import of Metadata → Next and select the source and target system.
    Configure the System for Mass Import and click Finish.
    Mass Import of Metadata

    Selective Import of Metadata

    It allows you to choose tables and target schema to import Meta data from SAP Applications.
    Go to File → Import → Selective Import of Metadata → Next
    Choose Source Connection of type “SAP Applications”. Remember that the Data Store should have been created already of type SAP Applications → Click Next
    Selective Import of Metadata1Selective Import of Metadata2
    Select tables you want to import and validate data if required. Click Finish after that.

  • SAP HANA - Information Composer

    SAP HANA Information Composer is a self-service modeling environment for end users to analyze data set. It allows you to import data from workbook format (.xls, .csv) into HANA database and to create Modeling views for analysis.
    Information Composer is very different from HANA Modeler and both are designed to target separate set of users. Technically sound people who have strong experience in data modeling use HANA Modeler. A business user, who does not have any technical knowledge, uses Information Composer. It provides simple functionalities with easy to use interface.

    Features of Information Composer

    • Data extraction − Information Composer helps to extract data, clean data, preview data and automate the process of creation of physical table in the HANA database.
    • Manipulating data − It helps us to combine two objects (Physical tables, Analytical View, attribute view and calculation views) and create information view that can be consumed by SAP BO Tools like SAP Business Objects Analysis, SAP Business Objects Explorer and other tools like MS Excel.
    • It provides a centralized IT service in the form of URL, which can be accessed from anywhere.

    How to upload data using Information Composer?

    It allows us to upload large amount of data (up to 5 million cells). Link to access Information Composer −
    http://<server>:<port>/IC
    Login to SAP HANA Information Composer. You can perform data loading or manipulation using this tool.
    To upload data this can be done in two ways −
    • Uploading .xls, .csv file directly to HANA database
    • Other way is to copy data to clipboard and copy from there to HANA database.
    • It allows data to be loaded along with header.
    On Left side in Information Composer, you have three options −
    Select Source of data → Classify data → Publish
    Upload Data
    Once data is published to HANA database, you cannot rename the table. In this case, you have to delete the table from Schema in HANA database.
    “SAP_IC” schema, where tables like IC_MODELS, IC_SPREADSHEETS exists. One can find details of tables created using IC under these tables.
    Spreadsheet

    Using Clipboard

    Another way to upload data in IC is by use of the clipboard. Copy the data to clipboard and upload it with help of Information Composer. Information Composer also allows you to see preview of data or even provide summary of data in temporary storage. It has inbuilt capability of data cleansing that is used to remove any inconsistency in data.
    Once data is cleansed, you need to classify data whether it is attributed. IC has inbuilt feature to check the data type of uploaded data.
    Final step is to publish the data to physical tables in HANA database. Provide a technical name and description of table and this will be loaded inside IC_Tables Schema.

    User Roles for using data published with Information Composer

    Two set of users can be defined to use data published from IC.
    • IC_MODELER is for creating physical tables, uploading data and creating information views.
    • IC_PUBLIC allows users to view information views created by other users. This role does not allow the user to upload or create any information views using IC.

    System Requirement for Information Composer

    Server Requirements −
    • At least 2GB of available RAM is required.
    • Java 6 (64-bit) must be installed on the server.
    • The Information Composer Server must be physically located next to the HANA server.
    Client Requirements −
    • Internet Explorer with Silverlight 4 installed.
  • SAP HANA - Analytic Privileges

    Analytic Privileges are used to limit access on HANA Information views. You can assign different types of right to different users on different component of a View in Analytic Privileges.
    Sometimes, it is required that data in the same view should not be accessible to other users who do not have any relevant requirement for that data.

    Example

    Suppose you have an Analytic view EmpDetails that has details about employees of a company- Emp name, Emp Id, Dept, Salary, Date of Joining, Emp logon, etc. Now if you do not want your Report developer to see Salary details or Emp logon details of all employees, you can hide this by using Analytic privileges option.
    • Analytic Privileges are only applied to attributes in an Information View. We cannot add measures to restrict access in Analytic privileges.
    • Analytic Privileges are used to control read access on SAP HANA Information views.
    So we can restrict data by Empname, EmpId, Emp logon or by Emp Dept and not by numerical values like salary, bonus.

    Creating Analytic Privileges

    Right Click on Package name and go to new Analytic Privilege or you can open using HANA Modeler quick launch.
    Creating Analytic Privileges
    Enter name and Description of Analytic Privilege → Finish. New window will open.
    You can click on Next button and add Modeling view in this window before you click on finish. There is also an option to copy an existing Analytic Privilege package.
    Once you click on Add button, it will show you all the views under Content tab.
    Adding Views to Analytic Privileges
    Choose View that you want to add to Analytic Privilege package and click OK. Selected View will be added under reference models.
    Now to add attributes from selected view under Analytic Privilege, click on add button with Associated Attributes Restrictions window.
    Select Object
    Add objects you want to add to Analytic privileges from select object option and click on OK.
    In Assign Restriction option, it allows you to add values you want to hide in Modeling View from specific user. You can add Object value that will not reflect in Data Preview of Modeling View.
    Assigning Restrictions to Object
    We have to activate Analytic Privilege now, by clicking on Green round icon at top. Status message – completed successfully confirms activation successfully under job log and we can use this view now by adding to a role.
    Now to add this role to a user, go to security tab → User → Select User on which you want to apply these Analytic privileges.
    Adding Analytic Privileges to User Roles
    Search Analytic Privilege you want to apply with the name and click on OK. That view will be added to user role under Analytic Privileges.
    To delete Analytic Privileges from specific user, select view under tab and use Red delete option. Use Deploy (arrow mark at top or F8 to apply this to user profile).
  • CONTENT

    We are providing SAP HANA Administration Materials.

    CONTACT US

    For enquiries you can contact us in several different ways. Contact details are below.

    VENKAT SAP HANA

    • Street :Hyderabad
    • Person :Venkat
    • Country :INDIA
    • Email :venkatsaptraining@gmail.com

    For any Query,Please leave message

    Learn SAP HANA Be with latest update.