Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
IngoH
Active Contributor

In Part 1 of this short blog post series we looked at the option to leverage an existing SAP NetWeaver BW InfoProvider and to generate an Analytical and Calculation View in SAP HANA based on the InfoProvider definition without copying the data.

In the second part we will leverage a BEx Query and generate a snapshot and import the meta-data from the existing BEx query into SAP HANA by generating an Analytical View.

Why would you want to leverage  BEx Query and generate a snapshot of the data ?

  • Because your BEx query might contain elements such as restricted or calculated key figures that are not part of your InfoProvider
  • Because you might have created formulas / calculations that are not part of your InfoProvider
  • Because you might only need a small subset of the data from your InfoProvider
  • Because you need the data from an InfoProvider that you can't leverage with SAP HANA directly yet, such as a MultiProvider

A query result cannot be indexed if the query meets one of the following conditions:

  • It is an input-ready query. An aggregation level is used as the InfoProvider.
  • Input-ready mandatory variables are used in the query. (As indexing runs in the background, no entries can be made.)
  • The query contains a temporal hierarchy join. (The result cannot be stored in a "flat" index.)
  • The query contains more than one structure
  • Calculations in the query cannot be performed before aggregation. Indexing can be performed despite this, but the relevant key figures cannot be used in every context.
  • Local aggregation is used. The system ignores this during indexing. (The query result in the OLAP Engine is not the same as the one that the user sees.)
  • The technical name of the query is more than 20 letters long. An index ID is formed from the query name. There is a technical limitation for this.

So let's generate a query snapshot:

  • Logon to the SAP NetWeaver BW system.
  • Start transaction RSDDB
  • Click Query as InfoProvider in the toolbar.
  • Enter the technical name of the BEx Query into the field Query.

  • Click Release Query as InfoProvider

(sorry - German message even though I was logged on with Language = EN)

  • Click Continue   .
  • Click Create  

  • Click Activate and Fill Index
  • Click Immediate.
  • Click Save.

Now the resultset of the BEx Query is being generated in form of a snapshot inside SAP HANA and we can generate the model in SAP HANA Studio.

  • Start SAP HANA Studio by following the menu Start > All Programs > SAP HANA > SAP HANA Studio.
  • In the left hand panel use a right click and select the option Add System.

  • Enter the system details for the SAP HANA environment:

  • Click Next.



  • Enter you SAP HANA credentials.
  • Click Next.
  • Click Finish.
  • Select the SAP HANA System that we created previously
  • Select the menu File > Import.
  • Open the Folder SAP HANA Content.
  • Select the option Import SAP NetWeaver BW Models.

  • Click Next.

  • Enter the SAP NetWeaver BW Server details.
  • Click Test Connection


  • Click OK.
  • Click Next.
  • In the next screen select the SAP HANA System entry you created previously.
  • Click Next


  • Navigate to the InfoArea.
  • Select the entry for the query snapshot.
  • Click Add.
  • Activate the option Include Display Attributes
  • Activate the option Overwrite existing objects.
  • Select the package for the model.
  • Click OK.
  • Click Finish.

After the import has successfully finished, check if the model was been imported.

  • In the left panel open your system entry.


  • Open the folder Content.
  • You should find in the package now 1 Analytical View following the name of the imported object

In the first two parts of this series we took a BW InfoProvider and a BEx query and generated analytical views for it inside SAP HANA.

In the next part we will then leverage the SAP BusinessObjects BI tools with the generated model.

3 Comments