http://scn.sap.

com/docs/DOC-53083

Step-by-step guide to implement

Modeling Scenarios in SAP BW 7.4 on
HANA
created by Mohammad Safiullah on Mar 7, 2014 7:13 AM, last modified by Mohammad Safiullah on Mar 7, 2014
9:30 AM
Version 1
inShare

About this Document

Business Case
This Document is based on SALES Business use case scenario.

Purpose
This manual aims to help you to understand the modeling of BW
objects in HANA and reporting based on HANA models in SAP BW on
HANA. This kind of processing is done in SAP BW on HANA. This
manual also provides details of the steps involved in importing
and modeling BW objects in HANA and creating a report based on
HANA views. This document is created solely with the intention of
sharing information.

Pre-requisites

Following are the pre-requisites for performing the tasks

presented in this manual:
SAP BW on HANA 7.4 installed on the server with packages sp4
(SAPKW74004).
SAP BW on HANA 7.3.1 installed on the server with
packages sp9 (SAPKW73109).
SAP BW on HANA 7.3 installed on the server with
packages sp10 (SAPKW73010).
HANA database upgraded to version 1.00.48.372847 and above.
BW authorization and Analytic privileges.

Knowledge of BO Objects.
Knowledge of Lumira

Contents
1
2
3
4
5
6

Overview of HANA-Optimized DSO and InfoCube in BW 7.4.

Source Data Extraction (LO Extraction).
Modeling BW Objects in BW 7.4.
3.1
Releasing BEx Query as InfoProvider.
HANA-Optimized InfoCube and DSO
Importing and Modeling in HANA.
5.1
Modeling in HANA of DSOs.
5.2
Modeling in HANA of InfoCube.
Visualization in Lumira.

1 Overview of HANA-Optimized DSO and

InfoCube in BW 7.4
DSO and InfoCube in BW 7.4 are HANA-Optimized by default. This
reduces the activation time and has a huge impact on the
performance .Modeling BW objects in BW on HANA into Analytic
/calculation views is only possible if the underlying database is
HANA .This is because tables are physically stored in HANA and
views are created with respect to the tables .

Key features

SAP HANA-optimized objects help you to achieve significantly

better performance in load and activation processes. Up to 80%
faster for loading in HANA Optimized Cubes.
With its high compression rate, the column-based HANA
datastore requires less data be materialized.
Data modeling is simplified. Using in-memory-optimized
objects you do not need to load a BWA index, for example. In

addition, the architecture of the HANA database allows you to

delete characteristics from an InfoCube that still contains data.
With BW in-memory-optimized objects, complex analysis and
planning scenarios with unpredictable query types, high data
volume, high query frequency, and complex calculations can be
processed with a high degree of efficiency.
Loading SAP HANA-optimized BW objects can also be done more
efficiently.
The SAP HANA database replaces both any previous database and SAP
NetWeaver BWA, reducing infrastructure costs. Instead of both database
administration tools and additional SAP NetWeaver BWA administration tools,
the SAP HANA database requires just a single set of administration tools for
monitoring, backup and restore, and other administrative tasks.

2 Source Data Extraction (LO Extraction)

We will now see the basic feature of Extraction from EC6 system.

Login to EC6 with proper username and password

We activate the data sources using a transaction code RSA5.

Next we have to fill up the set up tables for the data sources. For doing this first we need to
delete the contents that are already present in that setup tables.

Go to the transaction code LBWG and select the application component whose
content has to be deleted.

To check whether the setup table is deleted or not go to the transaction code RSA3 and give
the data source name and it will show Record 0 found which means data has been deleted from the
setup table.

Now using the transaction code LBWQ delete the extraction queue of the data source.

Also delete the delta queue for the data sources using the transaction code RSA7.

Next is to fill the setup table using the transaction code SBIW or OLI*BW where * denotes the
application component

Click on Logistics under Settings for Application-Specific Data Sources--> Managing Extract
Structures --->Application-Specific Setup of Statistical Data.

Now click on the execute button of Perform setup Sales and do it for delivery.

We will now see the set up table contents using transaction code RSA3.

3 Modeling BW Objects in BW 7.4

We will locate the application component and replicate both the data sources.

Next we will create the info package for the data sources 2LIS_11_VAHDR and 2LIS_11_VAITM
and activate it so that we can see all the data that are selected in the extract structure will be in the
PSA table.

Next we will create the DSO for each data sources and load all the data into it using the data
transfer process and activate both the DSOs.

3.1 Releasing BEx Query as InfoProvider

We create the BEx Query in Query Designer for the InfoCube and display it using transaction
code RSRT.

Next we will set the Query as InfoProvider in the properties tab or using t-code RSDB in order
to use it in HANA.

4 HANA-Optimized InfoCube and DSO

In order to find out whether InfoCube is HANA-Optimized or not. In BW 7.4, by default it is

HANA-optimized.

In order to find out whether DSO is HANA-Optimized or not, this can be find out after activation

5 Importing and Modeling in HANA

We will now see the basic steps of importing and modeling from BW into HANA.

Login to HANA Database via HANA Studio by clicking add system.

Go to File->import->import SAP Netweaver BW models.

Next we enter the credentials of BW on HANA choose the target system.

Note: target system has to be the underlying database.

Next we see that it imports, generates, transforms, saves and activate BW objects into views.

Next select the package for the views.

DSOs are imported as analytic views.

InfoCubes are imported as internal analytic views and graphical calculation view.

BEx query released as infoprovider is imported as analytic view

5.1 Modeling in HANA of DSOs

Next we created calculation view on top two analytic views.

We selected the fields which we need for analysis in projection

We used union since the metadata structure is same in projection and it increases the
performance and aggregated it.

Next we check the value of calculation view.

5.2 Modeling in HANA of InfoCube

Next we also check the data of calculation view of infoCube imported.

6 Visualization in Lumira

Login to Lumira using HANA credentials.

Next select the calculation view to prepare the visualization.

Next, select the measures and dimensions to prepare visualization

Next, we can add filter or restrict in order to visualize the data

Finally we visualize and save the dataset either in local folder or in Excel or in HANA or in
Lumira cloud.

5102 ViewsProducts: sap_hana, sap_netweaver_business_warehouse_7.3_powered_by_hana Topics: business_intellig

ence Tags: hana,bw, sap_netweaver_bw, bw7.3, bw_on_hana, sap_netweaver_bw_on_sap_hana, bwonhana, sap_bw_
hana, bw_migration,bw_on_sap_hana

Average User Rating

(3 ratings)
inShare

12 Comments

Antony Jerald J Mar 13, 2014 7:42 AM

Hi,
Thanks for sharing, nicely explained.
I've a query here:
Since BW is running on Hana, what is the necessity in bringing the model again to Hana DB for
modeling? It's again duplicating model/data right? We can directly build BO Reports from BEx
query which is from BW on Hana right?
(One correction: The view you've created is analytical view and it's not the calculation View)
Kindly suggest.
Regards,
Antony Jerald.

Like (1)

o
Mohammad Safiullah Mar 13, 2014 8:43 AM (in response to Antony Jerald J)

Hii Antony ,
Yeah you are completely right .We can build BO reports from Bex Query directly .
It also depends on requirements .If you need to create analytic view/calculation view
on top of HANA-Optimised dso (imported as analytic view) and analytic view/attribute
view created on tables present in HANA schema or on flatfile data or on tables
imported from other sources, then you have build BO reports on HANA views .
If there is a complex calculation needs to be done in BEX , then it would be better if
you do it in HANA side rather than on BEx using HANA engines because performance
is much faster .

I have created calculation view on top of two analytical view (i.e on top of two HANAOptimised DSO) .You can see that in 5.1 and calculation view is created as infocube is
imported which is described in 5.2.
Like (1)

Ramakrishnan Azhagappan Apr 1, 2014 8:59 AM

Hello Mohammad,
This is useful for the entry level HANA Developers. Thanks for the awesome blog.
Like (0)

kamal M Apr 30, 2014 8:55 AM

HI Mohammad,
thanks for sharing ...
thanks,
kamal
Like (0)

Chandra Sekhar Apr 30, 2014 8:42 AM

Very good information.

Thanks & Regards,
Chandra Sekhar.
Like (0)

o
Mallikarjuna Gande May 24, 2014 7:08 PM (in response to Chandra Sekhar)

Hi,

When we have HANA as DB for BW 7.4, no manual import of DSO or Cube to HANA
studio.
If you enable following option for DSO/Cube, system will create views in HANA studio.
its like auto importing.
And the only disadvantage with this, after transporting to Production/next system we
need re-active all views manually

if anybody know, how to activate all views @time After transport, please do share.
thanks.

Like (1)

Mohammad Safiullah Jun 3, 2014 3:10 PM (in response to Mallikarjuna Gande)

Thank you Mr Mallikarjuna Gande.

This option is available in BW 7.4 SP 6 and above .I didn't see this option in
BW 7.4 SP 4.
Indeed I have checked this option and activated the DSO/Infocube and the
following view is automatically imported and created. Then I manually
activated the view to analyse the data further .
Thank you once again for this information.
Like (0)

Sanjay gupta Sep 28, 2014 1:41 PM

Hi Mohammad,
Thanks for the nice information.
I have a small doubt here, for importing the BW models into SAP HANA, you are going into
option file ---> import... etc...
But i heard that we have a T Code for importing the models into SAP HANA.
Do you have any idea about the Tcode for importing the models into SAP HANA?
Thanks & Regards,
D. Sanjay Gupta.
Like (0)


Vikrant Soni Sep 29, 2014 7:48 AM

Nice Document, explaining the complete Use Case..

Regards,
Vikrant
Like (0)

Chandra Sekhar Sep 29, 2014 12:03 PM

Hi,
Very useful document.
Thanks & Regards,
Chandra Sekhar.