Professional Documents
Culture Documents
Step-By-Step Guide of Modeling HANA Views Into BW in SAP BW 7.4 On HANA
Step-By-Step Guide of Modeling HANA Views Into BW in SAP BW 7.4 On HANA
Contents
1 Overview of Transient provider, Virtual provider and Composite provider in BW 7.4 on page
1.1 Transient Provider on page
1.2 Composite Provider on page
1.3 Virtual Provider on page
2
3
4
5
6
Key features
We create new Excel type format to load Sales Item data (VBAP Table).
Next we create a new BW on HANA Data store that connects to HANA database.
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.
Next we will create the info package for the data sources 2LIS_11_VAHDR 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 data source and load all the data into it using the data transfer
process and activate both the DSO.
5 Modeling in HANA
We will now see the basic steps of modeling in HANA.
Log in to HANA Database via HANA Studio by clicking add system.
6 Modeling in BW on HANA
We will now see the basic steps of modeling Data marts in BW on HANA.
6.1 Transient Provider
Using T Code RSSDD_HM_PUBLISH, we create Analytic Index which is Transient Provider in BW on
HANA .
Using T Code RSSDD_LTIP, we see the transient provider that we have already created.
We can use either UNION or JOIN operands in modeling of Composite Provider based on
requirements which is an advantage over Multi Provider (only union) and Infoset (only join).
Drag and Drop HANA-Optimized DSO from left panel to right panel and use binding type
as "UNION.
Drag and Drop Transient provider from left panel to right panel and use binding type as
"Inner JOIN.
NOTE: In composite provider, there has to be one provider with binding type as
UNION.
Next we click the Assign HANA Model Attributes button in upper right corner in order assign the
attributes to Info Objects.
Select propose mapping checkbox and click continue
Select the required attributes and If not found then Click continue.
For Manual mapping, right click the dimension and click provider specific-Info Objects properties.
We also created column chart along with tabular display of data for composite provider Query.
We also created column chart along with tabular display of data for Virtual provider Query.
We can also save the report as a different file like pdf, excel.
8 Conclusion
The concept of the Transient Provider has the biggest appeal in the context of ad-hoc models with
frequent changes and a limited durability. But we cant transport a Transient Provider and so we
have to publish the HANA model in each system where we want to use it.
For the more long term and stable requirements we instead propose the new Virtual Provider, based on HANA
model.
So as a general recommendation we state, that we should keep the model in HANA as simple as possible and
model the calculations instead in the BEx Query.