bods_bw_hana_bo

8/10/2019 bods_bw_hana_bo

1/38

About this Document

Business Case

This document is based on Sales Business case scenarios.

Purpose

This manual aims to help you to understand the modeling of HANA

views into BW and reporting based on BW providers in SAP BW on

HANA. This ind of processing is done in SAP BW on HANA. Thismanual also provides details of the steps involved in creating

and modeling HANA views and migrating to BW and creating a report

based BW providers. This document is created solely with the

intention of sharing information.

Pre-requisites

!ollowing are the pre"re#uisites for performing the tass

presented in this manual$

SAP BW on HANA %.& installed on the server with pacages sp4(SAPKW74004).

SAP BW on HANA %.'.( installed on the server with

pacages sp9 (SAPKW73109). SAP BW on HANA %.' installed on the server with

pacages sp10 (SAPKW73010). HANA database upgraded to version HANA SPS )* and above.

BW authori+ation and Analytic privileges.

,nowledge of B- -bects.

,nowledge of B- /ata services.

Contents

1 Overview of Transient provider, irt!a" provider and #o$posite provider in%W 7.4
http://scn.sap.com/docs/DOC-53352#__RefHeading__722_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__722_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__722_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__722_705700879


2/38

1.1 Transient Provider 1.& #o$posite Provider 1.3 irt!a" Provider

& So!r'e ata *tra'tion (!sin+ %O ata Servi'es)3 So!r'e ata *tra'tion (O *tra'tion)4 -ode"in+ %W O/e'ts in %W 7.4 -ode"in+ in A2A -ode"in+ in %W on A2A

.1 Transient Provider .& #o$posite Provider .3 irt!a" Provider .4 %* !er5 esi+ner

.4.1 Transient Provider .4.& #o$posite Provider .4.3 irt!a" Provider

7 6eportin+ in We nte""i+en'e8 #on'"!sion

1 Overview of Transient provider, Virtuaprovider and Composite provider in B! "#$

/S- and 0nfo1ube in BW %.& are HANA"-ptimi+ed by default. This

reduces the activation time and has a huge impact on the

performance .Similarly modeling HANA 2iews in BW on HANA into

Transient providers3 1omposite Providers and 2irtual Providers

also has a huge impact on performance if the underlying database

is HANA.
http://scn.sap.com/docs/DOC-53352#__RefHeading__724_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__726_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__728_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__730_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__732_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__734_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__736_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__738_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__740_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__742_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__744_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__746_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__748_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__750_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__752_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__754_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__756_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__724_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__726_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__728_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__730_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__732_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__734_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__736_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__738_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__740_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__742_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__744_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__746_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__748_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__750_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__752_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__754_705700879http://scn.sap.com/docs/DOC-53352#__RefHeading__756_705700879


3/38

1.1 Transient Provider

,ey features

0ts metadata in BW is not persisted3 but always generated at

runtime.

B45 6ueries built on top can adapt to changes automatically

as far as possible.

Navigational attributes of an assigned 0nfo -bect can7t be

used .

0t cannot be used in 8ulti provider.

0t can only be used in 1omposite Provider in order to merge

with other 0nfoProvider.

0t is e5posed to B45 and B0 tools.

1.2 Composite Provider


4/38

0ts biggest advantage that it performs both union and oins

operation which overcomes the limitation of 0nfo Sets and 8ulti

provider in BW .

1.3 Virtual Provider

,ey features

0t offers a very fle5ible way of integrating data not stored

in BW -bects into the consistent BW world.

We can turn on Navigational Attributes for the 2irtual

Provider as usual. Then we can map the Navigational Attribute

also to a field in the HANA model in the 9Provider specific

properties: ; if you do not map it3 the data comes from the

8aster data tables in BW.

2irtual Provider can be transported as usual3 it can be used

in a 8ulti Provider and B45 6ueries can be built on top3 ust

lie for any other 2irtual Provider.

The data read access at 6uery runtime is not via S6


5/38


6/38

2e*t we i$port s'e$a and "oad te data .


7/38

Ne5t we create a new BW on HANA /ata store that connects to

HANA database.

2e*t we 'reate a at' /o and te$p"ate ta"e in %W on A2A.


8/38

2e*t we a"so $apped te :e"ds in !er5 transfor$.


9/38

We run a batch ob by right clicing it.

Ne5t we see the data in the template table and import the

table by right clicing it.


10/38

3 Source Data Extraction (" Extraction!

We will now see the basic feature of 45traction for Sales Header

data from 41* system.


11/38

We will activate the data sources using a transaction code

=SA>.

Ne5t we have to fill up the set up tables for the data

sources. !or doing this first we need to delete the contents that

are already present in that setup tables.

?o to the transaction code


12/38

To 'e'; weter te set!p ta"e is de"eted or not +o to te transa'tion'ode 6SA3 and +ive te data so!r'e na$e and it wi"" sow 6e'ord 0 fo!ndwi' $eans data as een de"eted fro$ te set!p ta"e.

Now using the transaction code


13/38

1lic on


14/38


15/38

2e*t we wi"" 'reate te info pa';a+e for te data so!r'es&S=11=A6 and a'tivate it so tat we 'an see a"" te data tat arese"e'ted in te e*tra't str!'t!re wi"" e in te PSA ta"e.


16/38

2e*t we wi"" 'reate te SO for data so!r'e and "oad a"" te data into it!sin+ te data transfer pro'ess and a'tivate ot te SO.

% &odein' in (A)A

We will now see the basic steps of modeling in HANA.


17/38

Analytic view is created on item table 2BAP replicated by

B- /ata Services. )OT*+8ae sure to mention the measure type CAmount with

1urrency7 for measure attribute lie for 1-ST3 2TA>3 2TP6#to

avoid mismatch problem with the predefined 0nfo -bects while

creating transient or virtual provider.

1D== is a currency field of 0tem table 2BAP.


18/38


19/38

) $odeling in B% on *+,+

We will now see the basic steps of modeling /ata marts in BW on

HANA.

#1 Transient Provider


20/38

>sin+ T #ode 6SS=-=P>%S, we 'reate Ana"5ti' nde* wi' isTransient Provider in %W on A2A .

>sin+ T #ode 6SS=TP, we see te transient provider tat we avea"read5 'reated.

Se"e't te Ana"5ti' nde* and '"i'; disp"a5.


21/38

Wi"e 'reatin+ it, $ention te nfo Area.

Now we can mention the reference 0nfo-bect for the

attributes.

=eference 0nfo-bect are used to copy the metadata structure

to attribute.


22/38

)OT*+6eferen'e nfoO/e't is not $andator5 in transient provider.

).2 Composite Provider


23/38

2ow we 'reate a 'o$posite provider on Sa"es eader ata (A2A?Opti$i@ed SO) and Sa"es te$ ata (Transient provider).

)OT*$ We can model a 1omposite Provider either by usingthe T 1ode =S


24/38

).3 Virtual Provider

2e*t we 'reate a virt!a" provider on A2A Ana"5ti' view.


25/38


26/38

2e*t we '"i'; te Assi+n A2A -ode" Attri!tes !tton in !pper ri+t'orner in order assi+n te attri!tes to nfo O/e'ts.

Select propose mapping checbo5 and clic continue


27/38

Select the re#uired attributes and 0f not found then 1lic

continue.


28/38

Cor -an!a" $appin+, ri+t '"i'; te di$ension and '"i'; providerspe'i:'?nfo O/e'ts properties.

Si$i"ar"5 do te sa$e for Ke5 i$ensions. Note$ 8ae sure measure attributes lie 1-ST3

N4TP=0143N4T2A


29/38

Cina""5 irt!a" provider is 'reated and we now 'e'; te data .


30/38

).# B Ex -uer Designer

#$#1 Transient Provider

2e*t we 'reate a % e* !er5 on Transient provider and report it !sin+6S6T.


31/38


32/38

).#.3 Virtual Provider

We a"so 'reate a % e* !er5 on irt!a" provider and report it !sin+6S6T.


33/38

/eporting in %e& 0ntelligence

We will now see basic steps of reporting on B45 #uery in Web

0ntelligence.

We create an -


34/38

2e*t we open a % "a!n' pad and ten we inte""i+en'e . We select B45 6uery as datasource and then the re#uired -


35/38

We also selected the re#uired obects and run the #uery.

We can also preview the data using refresh in data preview

tab.


36/38

We a"so 'reated 'o"!$n 'art a"on+ wit ta!"ar disp"a5 of data for'o$posite provider !er5.


37/38

We a"so 'reated 'o"!$n 'art a"on+ wit ta!"ar disp"a5 of data forirt!a" provider !er5.

We can also save the report as a different file lie pdf3

e5cel.


38/38

Conclusion

The concept of the Transient Provider has the biggest appeal in

the conte5t of ad"hoc models with fre#uent changes and a limited

durability. But we can7t transport a Transient Provider and so we

have to publish the HANA model in each system where we want to

use it.

!or the more long term and stable re#uirements we instead propose

the new 2irtual Provider3 based on HANA model.

So as a general recommendation we state3 that we should eep the

model in HANA as simple as possible and model the calculations

instead in the B45 6uery.

bods_bw_hana_bo

Documents