Semantic Layers in SAP Hana

Semantic Layers 

1. Consumption of HANA views /Tables/NUDT to Prepare BO Semantic buyer

UDT is a (universe designer tool) to prepare structure based on report requirements by using Table structure in HANA DB.  

NOTE:

House we can bring only table structure from the database instead of disturbing data in DB

• We can design structure joining tables band business, so we need to concentrate on cardinality (1-1, many to 1, 1 to many, many to many)
• While property structure will get some complex scenarios like loops & traps
• Loops bring less amount of data rather than actual data in attributes So, we can solve the loops by shortcut, alias, context
• Traps bring more data to the actual date so, we can slow this problem by using context and we can add features like hierarchies, disturb values, cascading disturb values, and cascaded objects based on requirements.

Procedure to create a semantic layer (UDT) Create an ODBC connection

Go to start      settings     content panel         administrator tools       Data source (ODBC)

Select system ADM (tab)     click on sys adm (tab)     click on add     select HDBODBC32 connection

Provide ODBC connection name: __________

Port NO :___________ Click on connect      provide usr name : _________ & Password:_________ and       OK

Log on to the universe design tool create universe click on new connection select the connection type is secured       provide the connection name (universe connection   Select ODBL connection type (SAP    SAP – In __ memory)    ODBC  provide universe parameters and   OK

• Insert the required table & view and prepare the structure and follow above mention methodologies to create classes & objects
• Cheek the integrity
• Save and export to the system repository
• We can create web1, crystal, explore and dashboard

2. Consumption of HANA views | Tables in IDT To prepare BO semantic layer

  It is a semantic layer that contains a business layer to provide data to the reports

Prouder

Log on IDT

• Create a new project
• Create a new connection

NOTE: Connection should be secured & ROLAP type

• Select our HANA ODBC connection
• So will get a connection in the form of.CNS
• After we need to export the connection into the system repository
• Create a Data foundation by selecting our shared connection
• Select the required tables and views and prepare the structure
• We need to join the tables and views with the coordinates based on the business report requirement
• We need to follow rules to design the structure
• Create a business layer
• Select our data foundation, save it, & export it into the system repository
• After exporting our business layer we can create reports like Web 1, explorer, Crystal reports

NOTE: For both UDT & IDT we can create views from ‘ – sys – bic’ for catalog only For tables we can bring from any catalogs  

Reports

website reports: It is a web paged report which provides refreshed values

• We can create web-I reports from UDT & IDT
• We can create web-I reports in Launchpad 

Procedure

Create ODBC connection

create the universe from UDT

Or  Export into the system Repository Business layer from IDT

Log on to Launchpad

create a query from the universe select our universe

Design Query

Based on report requirements, we can use measures, attributes, hierarchies, file, based on report requirement

execute query will get a report

so, based on requirement we can add features like alerts, ranking, variables, filters, build-up drill down, chairs, tables & relative positions ………………. Etc

Save reports & publish them into public folders

We can use web reports for Xceleries & live office

Dashboards

It is which contains tables, charts, & other components

Procedure

create ODBC connection

create IDT

use OLAP connections (BICS)

Create SAP dashboard

Select BW connection      we can take the connection from BICS & cube & views (calculated & analytic)

Select the component to model data

prepared dashboards by using alerts like extra ranking.

3. Crystal reports

• It mainly depends on Xcel, they are mainly cal based on report
• We can create crystal reports from views & tables by using HODBC & TDBC connections directly
• Here no, need to create JDBC & ODBC

Procedure

Create ODBC connection for SAP HANA

Create crystal reports and select the HANA ODBL connection as a source

Select tables & prepare the schema

In a field explorer  select the required column from the table

Apply the cosmetics prompt, alerts, calculated columns, variables, filters, links …… etc

Based on Requirements we need to create sub-queries | reports

Save export into the B.O Enterprise

4. EXPLORER

It is a web-based dashboard

Procedure

• Create ODBC connection
• log on to IDT
• create a project
• Create relational connection (secured) (.CNS)
• Export into the system repository will get in the form of CNX
• Create data foundation by selecting connection Insert required tables & views and the prepare the structure based on the reels
• create a business layer
• select our data foundation, & save our Business layer and export into the system repository
• so, will get in the form of UNX
• Log on to the explorer by providing URL http://sysname:8080/explorer
• log on & click on manage spaces
• click on the new query
• select out business layer
• prepare query
• and save it

NOTE: The query must have at least one attribute measure

• create an index for our query
• we can drill into the report
• based upon the reporting requirement we can apply cosmetics like scenery order, charts alerts tables, and publish into the public folders.

5. Appendix procedure

Procedure

To maintain consistency with SQL standards, functions will be called procedures The following example shows the procedure implemented in SQL script based on the new syntax. 

To better illustrate the high–level concept, we omitted details. CREATE PROCEDURE get output (in-out integer, in currency varchar (3),

Out output – pubs tt – publishers, Out output – year tt – years, LANGUAGE SQL SCRIPT READS SQL DATA as BEGIN Big – pub – ids = SELECT publisher FROM (query1) books Group by publisher HAVING COUNT (brr) .: cnt: Big – pub – books = SELECT title, price ---- Query 2 FROM big – pub –Ids, publishers, books HERE pub – ID = fid and pub = id = publisher AND crcy = currency; Out put-puts = SELECT SUM (Query 3)(price) FROM big – pub – books GROUP by publisher:

Output – year + SELECT SUM (price) FROM big – put – books GROUP by year; END;

The SQL script above defines read-only procedure which has 2 scalar input parameters and 2 output parameters or type table. 

As different languages are supported in the body of the procedure, the Implementation language is supported in the body of the procedure, the Implementation language is defined to be SQL script. Moreover, the procedure is a read-only procedure.

Here it is free of side effects and can be called by other reads–only procedures. The first line contains a SQL query

Q1 which identifies big published  (using the input parameter count). Afterwards, detailed information about these publishers along with their corresponding books is determined in Query

Q2. Finally. This information is aggregated in two different ways queries W3 (aggregated per publisher ) and

Q3 (aggregated per year) respectively. The resulting tables constitute the output of the functions.      

A procedure is a SQL script that only uses declarative constructs that can be completely translated into an acyclic data flow graph where each node represents a data transformation.

The example above could be represented as a data flow graph In the picture similar to SQL queries the graph is analyzed and optimized before execution For optimization the subgraph of the called functions is merged with the graph of the calling function and the resulting graph is the optimized The optimization applies security rules as SQL optimizer use’s for its logical optimization then the plan is translated into a  physical plan which consists of physical database operations.

Get In-Depth Knowledge:

• Predictive Analysis in SAP Hana
• Assumptions in SAP Hana