Building and Extending SAP HANA Live Views.pdf

Akash Kumar

Building and Extending SAP HANA®Live Views

~ Rheinwerk® Pub is'1ing Bonn • Boston

What You'll Learn Nowadays, the connected wor.ld generates a vast amount of data at a significant rate. With the right tools, this data can help companies answer many questions about their customers and their products, such as who they are, what they do, and how they do it. SAP HANA can provide real-

time analytics on both structured and unstructured data, and SAP HANA Live enhances these capabilities even more. In this E-Bite, you'll get step-by -step instructions on working with SAP HANA Live views. Start by learning how to build private, reuse, query, and value help views, and then find out how to extend these views for common requirements such as including or excluding fields or including custom tables. Finally, you'll round off your knowledge with steps on how to integrate SAP HANA Live with SAP BusinessObjects BI and SAP BW. 1

Introduction to Virtual Data Models 1.1 1.2 1.3 1.4 1.5

2

3

5

Architecture . . . . . . . . . . . . . . . . . . . . . . . . . Types of Virtual Data Models . . . . . . . . . . . . Viewing SAP HANA Live Virtual Data Models Basic Virtual Data Modeling Rules . . . . . . . . . Basic Virtual Data Modeling Terms . . . . . . . .

.. .. .. .. ..

5 7 9 11 12

Building SAP HANA Live Views . . . . . . . . . . . . . . . . . . . . . . . . .

13

2.1 2.2 2.3 2.4

. . . .

15 19 23 26

Extending SAP HANA Live Views . . . . . . . . . . . . . . . . . . . . . . . .

29

3.1 3.2 3.3 3.4

30 34 38 41

Private Views . . . Reuse Views . . . . Query Views . . . . Value Help Views

. . . .

. . . .

. . . .

. . . .

. . . .

. . . .

.. . ... .. . ...

. . . .

. . . .

. . . .

.. .. .. ..

. . . .

. . . .

. . . .

. . . .

.. .. .. ..

. . . . .

.. .. .. ..

. . . . .

. . . .

. . . . .

. . . .

.. .. .. .. ..

.. .. .. ..

In cluding Unexposed Fields from a Standard Model Exclud ing Unnecessary Fields from t he Query View In cluding Custom Tables ............... In cluding Custom Fields . . . . . . . . . . . . . . . . . . . .

. . . . .

. . . .

. .. .. ..

. . . . .

. . . .

. . . .

. . . . .

. . . .

. . . .

. . . .

. . . .

. . . .

4

4

Integrating SAP HANA Live Views with SAP Business Intelligence Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 4.2

5

1

45

Integrating SAP HANA Live and SAP BusinessObjects 81 . . Integrating SAP HANA Live a nd SAP BusinessObjects Bl Tools with SAP BW . . . . . . . . . . . . . . . . . . . . . . . . . . . .

46

What's Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

61

53

Introduction to Virtual Data Models

SAP HANA Live, which is built on top of SAP HANA, provides new highquality analytics and reporting capabilities to SAP Business Suite. Its purpose is to provide virtual data models (known as SAP HANA Live views) that expose data for reporting to SAP BusinessObjects BI tools via OData, HTTPS, or SQL/MDX.

In this section, we 'll introduce you to the basics of virtual data models: their architecture, their types , options for viewing them, basic modeling rules to fo llow, and basic terms that you should be familiar with.

1.1

Architecture

SAP HANA Live allows real-time operational analytics and is based on a two-tier architecture as shown in Figure 1. » Tier 1 consists of SAP HANA as the database system, application , and web server. » Tier 2 consists of user interface (UI) clients such as SAP BusinessObjects BI tools that are connected to SAP HANA from OData, SQL, or HTTPS.

5


Real -Time Business Intell igence Specific Analytical Ul (HTML5 Based)

Generic Analytical Ul (BOBJ, etc.)

OData, HTTPS

SQUMDX

SAP HANA Platform SAP HANA Live

Calculation Engine and Search

Security

History and Hierarchy Handling

Broadcast and Documents

Predictive Analysis

Cross-System Analytics

Fi gure 1 SAP HANA live's Two-Tier Arch itecutre

SAP HANA Live delivers more than 2,000 virtual data models, which are preconfigured and easy for you to use. The included virtual data models are optimized for data throughput and the best performance in transactional scenarios. The virtual data models are present in the SAP HANA database. SAP HANA Live's detailed architecture, including virtual data models, is shown in Figure 2.

6

I

1

I

1

-J,

I

Introduct ion to Virtual Data Models

HTML5 -based (Web and Mobile) Other SAP Solutions

SAP BusinessObj ects Bl

Third Party

Open Interfaces: HITPS, OData, SQL, MDX

Web Resource

SAP-

OData Service

Delivered Query Views

SAP HANA XS Engine Application Services

Customer Extensoons Value Help Views Reuse Views Private Views

SAP HANA Platform

Physical Tabl es SAP HANA Live (VOM)

Database Layer

•

L - - - - - - - - - - - - - - - - -Ph -_y_ sic_a_ l l_a_bl-es________________

Custom-built Open Interface

[Q

Out of the Box Support

Fi gure 2 SAP HANA Live Architecture

1.2

Types of Virtual Data Models

Virtual data models (Figure 3) are accessed through the UI client using OData, SQL, MDX, or HTTP$ and are built entirely with SAP HANA calculation views. These calculation views can be broken down into the following types:

» Query views Query views are created for direct consumption by analytical applications such as SAP BusinessObj ects BI tools. Query views must not be subsumed by another view and are always the top view in the hierarchy. A query view mainly fulfills one or more analytical scenarios.

7


Consuming App licat ion (BOBJ, HTML5 Application, etc.)

\

SAP HANA Database

/

----------- ------------------------- ' Semantic View Layer Query Views Query views are designed for direct consumpt ion by an analytical application. They must not be cons umed by another view.

t Reuse Views Intended to be reused in other views by customers and partners. Can reuse other reuse views and private views.

''

-----

-

-----------j----------

~----- ~

I

Private Views Intended to be reused in other views internally.

"

SAP HANA Database Tables

I

Fields

I

\_ Figure 3 SAP HANA Li ve Virtual Data Model Views

» Reuse views Reuse views are the most important view in virtual data models. A reuse view exposes the business data present in the SAP HANA database to the query views. It does not fulfill any specific analytical scenario and can be reused in any other reuse view or in a query view to facilitate development. You can also use these views to create your own extended models to fulfill custom scenarios. Reuse views should not be consumed directly by analytical tools.

8

I

1


» Private views A private view consists ofSQL scripts on one or more database tables or views. Private views are not consumed directly by or reused in other views, including reuse views or other private views.

» Value help views Value help views provide possible valid values for a field. In a virtual data model, the value help view provides possible valid values to the fields in SAP BusinessObjects BI tools such as SAP BusinessObjects Design Studio. This feature lessens the probability of an incorrect value being entered by end users.

1.3

Viewing SAP HANA Live Virtual Data Models

You can view SAP HANA Live virtual data models via SAP HANA Studio and the SAP HANA Live Browser. In SAP HANA Studio, SAP HANA Live's virtual data models are present in the hba subpackage in the sap main package as shown in Figure 4. For example, the sap . hba . ecc package contains all of the SAP ECC ·Content. You can view the package under a CoNTENT folder, which is present for every SAP system; in our case, the SAP HANA System is DE3 (Figure 4). You can view the existing model or extend the model according to your business needs. The SAP HANA Live Browser is an SAP UI5-based web application that allows accessing, searching, and tagging SAP HANA Live models. The browser can be used both by the business end user and the developer to analyze or extend the virtual model. The SAP HANA Live Browser (Figure 5) can be accessed by entering the SAP HANA server host and instance number (which can be viewed from SAP HANA's system properties or provided by your SAP Basis team) in the following URL: http:II
ServerHost>:BO/sap/hba!explorer.

9

I

1


I

1

.

- ,. nf.o ~5tflnl 13 • !lil • I IJ II • • 18 " 1o e {fb oo

0 v

iJ IOf))PlOOAll O
-

0

,i Q

a: -

0

,a PRODALLOCREP

(i.l ie (~log

®., ,,...,_, $ Wt C
mDtmo
~ o....

:!: fi 6UI!I">I»M (!: IJI, donognsll.odto.~>«Oftl

tc-
'"'" Oener

~ &; t;ty.~j«t 5 ~

(hcJ.Of,.~IFS•ukrtftk· ) P.dlcloflto rclo~tttc rt~.our
~ Conti{;

:E

..

Btl up

dJ Ot11f

"' "' l!) fli bo

~ tnport

S tl boc® ifl: c~p

~ (Jpo1

® ti luo~

X, W,»t

eel.,.•

®at ....

0

® $ «< ® $ ~tt

"'t$! Ill: • Q lofonl'to

.. .c fi1 8h6

VIIIda

O AcMt Q

.!.I...J

.:J

Figure 4 The SAP HANA Live Package

HANA Log i n

L

Figure 5 SAP HANA Live Browser Credential Screen

You must enter your credentials to access SAP HANA content either by the package or by the application component (Figure 6). The SAP HANA Live Browser can be useful to the business user, who may not have enough detailed knowledge of SAP HANA Studio to explore metadata, to view live transactional data, or to visualize the relationships between vir-

tual data model objects. You can even select a view and use it in various SAP BusinessObjects BI tools such as SAP Lumira, SAP BusinessObjects Analysis (edition for Microsoft Office), SAP Crystal Reports, and SAP BusinessObjects Design Studio for detailed analysis . The only prerequisite is to have the relevant SAP BusinessObjects BI tools installed on your local machine.

10

Rtat~

£

In t rod uct ion t o Virtual Data Mod els

• MM • Ma!enals MMagetneft

BillingOoc...

J•

• PA • Per5omet t.tanagement ' PM • AaM Maineenanot • PP .

DD07T rn e

$.Jhs0rgMt... :~ •

Proauellon P~a~Wng ano

' PS • PtoiOCt S\'SI«ll .. SO · S<*!SancJDiSirlbUtion

VBRK.COM

,J•

VBUK_COM

."J•

• RwSie(
TVFKffi e

• VM.ltt~IP (1)

BllllngDoc....

:J•

MtKT ffi •

· $().81l-KNA1. COM

- """Y(2)

.' J•

J ........COCI( TVTW ffi e

Wt£·'·"'-·§:

TVrNT ffi •

• Reuse(12) . ~a~(2)

• SD.aiL-cA • AcccuAt k

ADRC

' SQ.elt,..()l! . Basic ru

PA0001

ffi e

ill e

VBPA..HDR ] • SAPCtientV...

:J •

SAPCIIent

J•

Figure 6 SAP HANA Live Browser

1.4

Basic Virtual Data Modeling Rules

Before we get any further into the discussion of SAP HANA Live views, you should know the following basic SAP HANA Live model rules, which apply to all views: » For design reasons, graphical calculation views are the preferred SAP HANA view for SAP HANA Live. )) If there are complex calculations that cannot be implemented from a graphical calculation view, then a script-based calculation view must be used. » You should not use attribute or analytic views in virtual data models as their functionality is too restricted. » Views that are based on client-dependent tables should expose SAPC l ient as the first column of the view output.

11

I

1

Introduct ion to Virtual Data Models

I

1

» The flag ENFORCE SQL ExECUTIONS should be set to true for all graphical calculation views (Figure 7). Sc:enano
·;)

Pak ..

(otumns(l.&)

jv.ew Prop~rtiu

Ht~rarchtts Paramettrs.Nanablu

G~~r~

(ll) Join

8

Unfon .ill Proj-t
o'

Aggregn...

.

· o· - .......,

r

~

v..cc..

- ~ v_cc

j;J R.ll'll.

·I

=

Figure 7 SQL Engine Execution

» You should not modify SAP delivered views; instead, use the SAP delivered view as a template andl create a custom view with your enhancements.

1.5

Basic Virtual Data Modeling Terms

Before we dive into the nitty-gritty details of building and extending SAP HANA Live views, let's establish and define some basic terms you should know:

» Variables A variable is an element entered manually by the user in the UI of a view. It defines the filter on the attribute of the view and can be specified before executing a query on the view. » Counters Counters are special types of columns that display the distinct count of attribute columns. They are defined only on query views and not on private or reuse views.

12

Building SAP HANA Live Views

» Hierarchies A hierarchy is an ordered list of levels or a collection of items. Each query item in a hierarchy must have a unique name.

2


SAP HANA Live provides prebuilt models to help you use the functionality quickly and easily by directly consuming the virtual data model in SAP BusinessObjects BI tools; this gives the business user the flexibility to consume data models without involving IT. However, it is also possible for developers to build SAP HANA Live views from scratch. In this section, we will show you how you can develop virtual data models using a detailed example. In our example, which is representative of most virtual data models, the virtual data model consists of the following views (Figure 8): » Query views » Reuse views » Private views » Value help views SAP Query V iews

Incl. Value Help Views

I

SAP Reuse View s

SAP Private Views

Physical SAP Tables of SAP Business Suite Applications SAP HANA Live VDM

Figure 8 SAP HANA Live Virtual Data Model

13

I

2


In this section, we will create a model view for the creation of daily production allocation reports. After seeing the steps in this example, you will have a basic understanding of how to create SAP HANA Live views for multiple purposes. Production allocation is done in the upstream oil and gas industry and is the process of allocating the actual production of crude oil at upstream nodes (i.e., well completion) after taking into consideration downtime, network loss, and so on. The daily report helps the user analyze production trends and also helps them to conduct future forecasting. Figure 9 shows a high-level process diagram for production allocation, and Figure 10 shows the virtual data model for creating daily production allocation reports. Model Production Network

----+

Field Data Capture

~ Production Allocation

~ Daily Reporting

Fi gure 9 Upstream Oil and Gas Production Allocation

Figure 10 shows the production allocation data model. The model consists of multiple database tables , several private and reuse views, and only one query view, which exposes the data to the analytical tools. The basic design principle is that data aggregation is performed first and then calculations, joins, or unions are performed on the aggregated data. In this scenario, the virtual data model is kept simple so that it is easy to understand.

14

I

2


Specific Frontend Adaptations: Gen erated to

make a view consumable by J'eports OJ' analytical applications (e.g .• currency conversion. input vAriables, t&Jd joins. user-specific calculations, SAP Que()' Views

I Incl . Value Help Views I

-

or data type conversions)

-

Semantic Integration: Enhanced with key business logic (e.g .. caltulated fields. j oins of related obj ~ts. or constant filters)

SAP Reuse Views

-

-

0

I

I e I I

-

Physical SAP Tables

-

o f SAP Business Suite App lications

Te<:hnlcal loss

Weii_Data Volume_Oata

might be relevant for business reporting , basic calculatio ns, o r joins (only where needed, i.e., for maj or OLTP tables)

SAP HANA Live VDM

0

Fi gure 10 Explanation of Virtual Data Model Scenario

Each view in the virtual data model has its own specific task (Figure 10): For example, a private view only takes the relevant fields from the database table required for reporting to, for instance, a reuse view. The reuse view then enhances those fields by combining them with other reuse or private views to provide the key business logic, whereas the query views acts as the single point of contact for the analytical or business application. Now that we have created the model design (Figure 1 0), the next steps are to create the individual virtual data model views that will make up the complete SAP HANA Live virtual data model. The first view that is created in the virtual data model is the private view.

2.1

2

Volume Query

Syntactic Integration: (Selection of fields that SAP Ptivate Views

I

Private Views

Private views are the most basic views that can access database tables or other private views. These views can be reused in reuse views or in query views. The main task of a private view is to expose the data of database

15

I I I I

Building SAP HANA Li ve Views

I

2

tables to other views. Only the fields that are to be used in a report, a calculation, or a join are selected in the view. Private views are required when you want to encapsulate some logic but are not mandatory and can be compared to private methods in programming languages. The steps to create private views are as follows: 1. Right-click on the package (Figure 11) under which the view will be cre-

ated and then go to NEw • CALCULATION VIEW .... You should create your own package for the virtual data model and should not create the model in the SAP namespace. For our scenario, we selected the package Demo Cont ent .

"'

.. . "~ ~ '""""'·" Pfoxtduft-

......

•

o~-r.t~lc

'if IILHICOP't

" c; ... - c

llmI Ust4~

._.

..::"·~=~.---';'~;::::c:,_=_:::------'-f::J Dt$<'fl'IIOII

,..l ot tl

Ho
,_,..~,

~l'i1tol}'

1B Oen'lo(ofi, C'nl

Job t't!N

I sri(""

()~--

_,._.._'"_" "' _"'_______, £

.!.l

.!1 ' ---------'

Figure 11 Opening the Calculation View in SAP HANA

2. Once the calculation view is created, then you can select the relevant

tables or another private view that will be consumed in the calculation view (Figure 12). In our example, table Y_CC_WELL_DETAILS is selected because it contains all the fields required for the production allocation report.

16


J

2

tmp.OemoContent::Y_CCC_WELL VSA " . . . ...

....
8 Union

....... .:1

••

Aggr...

.... ,g

(I)

T

Z••X

w MAKOT

ClttM

e oH.,.NO e w l_NO e wc_NO

Delivery network..._

e MAn flt

Mlterial Nu •~ C.ontr~t ,._,mber s~~te PAAowntf

e o _oo

e s.a...o1

Weii Onv11ber

wco:n Co•pkt.ion Nt.L-

wO\'YN_NO e OWNJ NT_fYP(JDP.r..,..,.t lntelt>t t 610WNJSQ.NO 0wnt'l' ~~er~t Seq...

e ORtG.MP. NO • r lt:NSP_NO w FRI:Q.CO w AC1'l.VOt.U AC fl. VOl HEAT_V.U._U w HEAT. V.U

O.ic}INI •u•:uure•Tr.,'fO'IHno.tmbfor

fltquttK)'

Actu.- \lolumt UnrtJ Artua \!olumt

:t! + •

li-t &

I ON_NO: r_cc_;•.nt_DfTAU-0 ... 1 ON_NO_t: .,.._ cc_wr~~-orrA.tS I WC.._NO: .CC.Mh_OG'A .s.··· I MATNR: Y_(c_,•lfti._OE:r'AQ.S.~ I CT_HO: V_CC'. WHLOEiA'LS.(f I SA_OT: ycc Mtt.D£7.A1!S.~

Y.CC..Wtu,.DETAJlS

l

I

owH,.IHT. 1YJ>t..a>. r.cc..wu

owH,.ISQ..NO: r.cc_.-.m..oo OlliG. MP. HO:

."'-""'

1 ~~:

Mn~t~gVl<~tU'I•t

tu'tlngvtlt.e

Y

CC MH 0(7 "' >

Value

Filter

ACTL.EXER.GV.U

Attua Ent,gyU"tt

ACTL. EN"EilGY WG.OVRD.PC

At:Na f<'~t19'1 ~>t G'' Ov.m
HITt...CT. VOl

ff'trtled Co.~tn
~.o.!·'~'-':1'·"''

""' ''""'~·•<•

L.tn~h

'""" 1'

10

Scale

(!)

'0

•

0

~ Tom...

ts

..

Figure 12 Addi ng Objects to Calculation Views in SAP HANA Live

3. Now, we have to assign the virtual data model properties under the VDM PROPERTIES tab (Figure 13) of the calculation view by clicking on the PROPERTIES tab in the lower-left corner of the calculation view. These properties are as follows: CATEGORY: Here, developers can select which view category should be used: private, reuse, query, or value help. APPLICATION COMPONENT: This property assigns the virttual data model to the specified application component. This must be assigned specifically by the developer and is assigned on the basis of business domain (such as Controlling, etc.). TERMINOLOGY DoMAIN: This property tells us the domain of the virtual data model view and is automatically derived from the application component. For example, if a view contains information about the controlling domain, then it will be assigned to CO - CONTROLLING. PERSON RESPONSIBLE: This field names the person responsible for the development of the view. This information is not delivered to the customers with the product and is not visible to users.

17

-

0


LJ Properties !::!

'

2

"tg Neighbor

~ Note: Changes are Saved Directly!

Gen era I Global Field Names

Category

VOM Properties

l

Unassigned

d

Requested by' NGMAN' t o be
J

Apphcatoon Component Unassigned [J Term1nology Domain

Unassigned

Person Respons1ble

unass;gned Ass1 n t o Me

Q

Figure 13 SAP HANA Live: VDM Properties

4. Since we are creating a private view, then we will select the PRIVATE category from the dropdown menu (Figure 14). Once you click on the FINISH button, the calculation view type will be set to PRIVATE. 5. The private virtual data model view is created, as shown in Figure 15. lmp.DomoConloni .:Y_CCC_WELl VSA

""""' <1

C..tout

•• s

i $ • li• St D ON_IIo. •. CC_Wf(Ul!TAUD •

'.1 ·-

., _

(I)

0 ON~N0_1 ~ I'_CC_t•.tu_OfTA lS:

Cll> ,.;.

~ Wc..,HO:

r

'"f'_MU..O(TA'

to•,

0 MATNR: Y.CC•••.tfl!_OC1A!t$. 6 CT_HO: ,-_((_\'.:.~.oErA ..S.Cl

; SA.OT~ Y..CC. ,Vfi(_ O(TA ~s.SA

D owtt.INTJYK..co. vcc_.~n

n OWN_ISQJ«); Y..CC.I'4-U..Ot fi

ORIG..MP..NO:

·-

...... TRNSP..NO

f4•fi';C: o~-. T)'IM

H'IAACHAit

,..,.. ""' fllttt

: Neoghbor Not ~ Changfl owe Swed Directf)'!

Globf,1 f iddN.mu

YOM Propcrtin

C.fltgOI)'

10

'

~ned ·-

APfl, ution Component Unassigned l trminoiOgy Orom.»in

lMMsiginH

Fi gure 14 Select ing the Private View in SAP HANA

18


2

lmp.De moCOnle ni ..Y_CCC_W Ell VSA

.,._ .. I ·.i ·-

n oN.. Y_cc ..iUO!TA ~so ... HC).

'"tWtANGMAN".Y_«._Wtu_0£TAII.S w~:n

J Se•anCiu I-

!-

' PTOftC:I~

-=-v_ee_~

~ ON..H0.. 1: ~".CC..>'.'Ell.. OtTA..lS ~ WC..NO: Y r-r- lifa Dfi.A'l.S ,•, D MATNR: Y..cc_ ..ru:_DC7A s ...

un, ~''1..-:IJ'IICIWOi k -

. DIN..NO ttWl,.NO

Wf'll>t10•b"

8 W(..NO e MATNIR NO ~SA..DT

*Cf..

WdiC-ompkticlnt-.k&.. t..._loi•l Nu•lkf (en1rKI ......bfof Solk$&ote

wOWN.NO

I'AAc..,. r•!!

n CT.. CC.O'l!..L..DVA3C1 ~ SA.,.OT: CC ,'If J Df1A. '>.SA n OWN_IHT_TYP(_CO: Y_CC_.~t~ n OWN)SQ._HO: Y..CC.. l'.:.(_Di' HC). ' ..

C OR.IG_MtJ_NO: '

..0WN_INT..T"''ft_(0P¥""'¥ltlnt~~ct ..O'WNJSQ...NO Own.er lnte1e't Seq._

4fOIRIG.,MP..NO Vl llN$PJ.:>

Ork)m~ •f'•U.Iff'111r,.,..tp«,~

., fR!Q..CO

I C:'~"'c t
wACTI..,.\IOI..,.U wACTI..,.\101. w HtAT..VAJ..U HlAT..VAl

A-nal Vc o--r• UM. AtW41'>etu!T.c-

• ACTI.,.ENtltGY..U ACTLJ:mR.GY

Act~.~~l {rc

nu"'bft

:::r

''''"~:JV~I:." lf'l,t

l

oa.. t)'pe:

t-•l'•"~J"'
fllttl

g•,-Ur t

,).;.t~,~lfno!'~)

10

'"'~~'"

x••

\vG..OYRO..PC · tt c,l, lNtPICiot J!., ENTl._CT_YOL E •Wtd Ccr ~· %

c

• ;J :J C!o€

'

Requested by 'NARAHGMAN' tlO be Sod to 'Prfo.o~t e' (St«\11 •neW). The tpp!O\'tf is " -

VOM Propertin 4pplout101'1 ( ompol'ltnt

t/AHsltned G)

Tt~minoJogyOomtWI

~Md

13 Consolt tl

c...-

Figure 15 SAP HANA Live: Private Virtual Data Model View

The new private view contains the database table containing details for W ELL ID NUMBER (WL_NO), WELL COMPLETION (WC_NO), VOLUME

and other required parameters. The newly created private view will now be consumed by the reuse views. QUANTITY (ACTL_VOL_U),

2.2

Reuse Views

Reuse views, the most important views in the virtual data model, expose

the business data present in the SAP system to the query view in a wellstructured and comprehensive way. Reuse views should not be directly consumed by the analytic tools and are created to work for multiple analytical scenarios. Some of the general guidelines for reuse views are as follows:

19

,..., NrU OCT. ., >


I

2

» The interfaces of reuse views should be kept stable so that the existing consumption scenario for the delivered view is not disrupted by view changes in subsequent deliveries. » You should not modifY the reuse view delivered by SAP; instead, use the SAP delivered view as a template and create a custom reuse view. » Variables should not be used in reuse views or private views as they do not directly interact with analytic tools. » Counters should not be defined in reuse or private views. Instead, counters should be defined only on the output node of the query view. The steps to create a reuse view are as follows: 1. Right-click on the package under which a view will be created and then

go to NEw • CALCULATION VIEW ... (Figure 16). You should create your own package for the virtual data model and should not create the model in the SAP namespace. For our scenario, we have selected the package OemoCo ntent . • SAt HAt iA IAodel«

~ Contoute IMOott SeMJ

"

Anatybc\\tw. .

¥

r•e¥56 -M

0,~ PtOW$1ont'lg

0 • AI'I~,_~fC ··•

ll Proc..,c...

s& E~~;~OI'I

+

'0 MastCO{If

~OJIOnlablor

......

O "'*'•
£ ·I

- " ~

Sclt
fluMbff ol Uu."":

,

~

...... -

~;.::~~:.

..:l .!.J__ __ _ J tJ I . I.Pi x

0

~ "

~~ostol)'l

1B D~mo<:o ntMt

_J~ '"l':m.

Job log $3

0

'0' ...

o Reoevor

I v.ew

OtmOConlltnt

OcmoCorotcnt

I

::J

-= " "::..:Tu::"'' ----'1-"'"""l tcm ::...._---" 1u,w,_ . - - -'-' ! ""'="""="•:::.. •__ -

.:!)

f

f

~"~-----~~~ ~·---------' -------1

I Oo

Figure 16 Creating the Reuse View in SAP HANA Live

20


I

2

2 Once the calculation view is created, then you can select the database

tables, private view, or another reuse view that will be consumed in the calculation view (Figure 17). You can select the table or the view on the basis of attributes that fulfill the requirements. In our example, we have selected table Y_CC_ALLOCATED because it contains the allocatted oil at each of the nodes, and we have selected view Y_CCC_WELL because it contain all the attributes of the well. Reuse views expose all the relevant attributes for a business entity. lmp.OemoConleni::Y_CC_WELLALLOCATION VSA

J;,: ... . ... .. . "--.....8' ..

1 ' .1

8 .,.,_

X

.... il

d
$0

Y_O::_,f.U,()CATS)

Jv_c:::e_v.e..L

~ ·

e. - .; •, ·

«"

3 !P

"

Sl>ow.AI

... "'"" [J [J [J

"

....••.

~ o -

'"'"

l yl)t

~jt.•

ilt d6

0

HU11ngVa-.11

""" Hutong'lalut

lnttWUnill

fntl~

AttutNdurne

Aclwi'/OMY!~

A9911f9M.c>n

''"' ''"'

<~111Y

(ntilll~(f'oO'ty

[J

VoiRed'ucnUtul

Vclttck.lclll.kVt

a:::J

Wt1Complet10r1

WdiC:OfTipk¢10n

Wtll

Wtll

WttG•~ct

\\'ttGnO...tmcttP<1

Entitkdt:nv,«eceuc.n

fnlitl
[J [J [J

v......

0 0

ActwEntr~dv
A
AautNciR.t.ducft

[J

(nt
A.(tu•IVoiP.•ducl'l (nh!l.cf'loiRotducll

0 0

Adjus.ltdEI'IUitdVOI

Ad)VSttd£ntflkocNct

A~tcd£t«tc:d£ft9Y

Ad~tc:d(t

•

Adjwt«
Figure 17 SAP HANA Live: Reuse View

3. Since we are creating a reuse view, then we will select the REUSE category from the dropdown menu. Once you click on the FINISH button, the calculation view type will be set to reuse (Figure 18). 4. The reuse view is created as shown in Figure 19.

21


2

tmp.DomoContont::Y _CC_WELL_ALLOCATION VSA x~rwrio

4

W.bf

~ --

~

L

·=- ...

Columnst)6) Y•tw Pt-optrt.-s Hltr.c.l'lltS Pl t¥flttMIV¥'*'"

C)

'"'~

(!!)

Jon

•

-

c VtNI:IIt

Union

Sci'IWI'ItoC l ypt

Lfbtl Cohtmn

Mi "'

• ------------------------~~~. . 0

..

Hc.1e: {Nnge-5 •re s.-d Ditertlyl ClttgOfY

UnHJigii«S -

.I. I Job Typt

VOM Pf~'tiet

""'

~iutiOt\(O~ U~ Ttf!nin~Oo~n

IC

'"''tftC KslOtY

VNS~

Figure 18 Selecting the Reuse View in SAP HANA live

I! ~ O O ·

tmp.OemoContent::Y _CC_W ELL_ALLOCATION VSA

It • F' Iii1t ·

~ •, •

«'

0 'i1 Columns(J6) VitwPropcrtteS Hitr¥ thtei

'"'" ,_ t~

.. l «y

0 0

0 8 Joln_1 ~n - v_et:._lld.J./:JCATtJ:J.

>r..cce_Y.fll

~mt

P•rM~tttn/V.n.blts

,....

Ht.l'tlngVIIUt

Muttn.gV• k.lt

ftloH'f)4Uf..l

f ntrgyUn!t

Anwft/OII.II'M

A
0 0

ltltiUcdtntrgy VoiRtd'u cnUnll

(l'lti41
0

Wt iiComplttiotl Wd WttGn.Ov.,ricte9ct

a:::J 0 0 0 0 0

£ndtlc«~uc"

Ac:t\l~Ener9)'tttdu
_, ........ Sum Sum

•

VciU:~

w...Comjiii«IOI'I WetGuOYtrridePd (ntitled£"9)-fttducn A
0

ACIMttdE,.._~ItdVol

Adjusttd(t~tidtd'Jcl

0

A~tc
Adj.t$ttd£t

AdJ;~ne«nc•~tct~ot

1

Figure 19 SAP HANA Live: Reuse View

22


2.3

Query Views

Query views expose the data to the outside world and are consumed directly by an analytical application or tool such as SAP BusinessObjects Web Intelligence, SAP BusinessObjects Dashboards, SAP Crystal Reports, SAP BusinessObjects Analysis, and SAP BusinessObjects Design Studio. The query view is a single entry point for the analytical application to access data from an SAP HANA database. The query view can consist of database tables, reuse views, and private views. Some general guidelines about query views are as follows: » A query view should not be consumed by any other view and should always be at the top of the hierarchy. » A query view can have multiple input parameters according to the business logic, and values can be assigned from analytical applications or business tools. You can also define new analytic privileges according to business scenarios and assign them to a new role. » The output field provided by a query view should be in a format that is consumable by Uls. » You should not modify the query view delivered by SAP; instead, use the SAP delivered view as a template and create a custom query view. The custom query view can then be consumed by analytical applications or SAP BusinessObjects BI tools. » Query views are visible to SAP BusinessObjects BI tools only when the MULTIDIMENSIONAL REPORTING flag is enabled. This flag is also enabled automatically as soon as a measure or counter exists. » Define analytic privileges and assign them to roles or users to ensure proper authorization checks. » Amount fields must have correct decimals. » Description fields should be available for all IDs and codes.

23

I

2

I


2

The steps to create a query view are as follows: 1. Right-click on the package under which the view should be created and then go to NEw· CALCULATION VIEW .... You should create your own package for the virtual data model and should not modify the model in the SAP namespace. For our scenario, we have selected the package DemoCon t ent . Ct.. -

.tllotg

$ .

PfCMIIotlln9

~ Qt Co~ttn'll

...

IBilDCII:' $ Bl~•>tvllto $ 8l~\tvdto_

g tilpubli<

"'' ... &. d

s.tp·;~mpl•t:

-

<; #

t:fltcm-Nul

&t VGTCC(J AOl 0

(i) .iii S.
""'"'

Autol>oc.~

® II l H\,.LOJod.0• 0 $

·I W hck~-

.. . .--d

t9 1-W~

"

fdit

)( D"'t< RtmoYtfllt"

3- f41:tt0tftc·u•.. p

..

Rtb
rJ

AnllytltVotw~·

¥

•

DM• P101Hi0Mg

&:;,11'1'-t"OI'I

AA~Pmlltgot-

ti

AUNltt Rtlttplo
t:;. Con'lg~e IIT'CICI'I 8eNef

An1obUII't'lo...,_

CIJI••

~ &pot!

Pr.ctot.MtO«llotOI'If~

~ Man COPY

......

...

~ ..!..I

O ReG~ r

AI.IOOOCIMY!tf'll&lion

.:.J •

I

tl Scl«tcd:

1·"0.

ill OemoCont«\t

~ ~

1

ProP!'tr Ibm,

(V41ut O~o,.t'flt

I Ui.-f

~~~~~~-=_:_~~_·_o_-_r._M~-·--~~~ ~·~--------------~~

I 0. ooCo

Figure 20 Creating the Query View i n SAP HANA Live

2. Once the calculation view is created, then you can select the database tables, the private view, or another reuse view that will be consumed in the calculation view. You can select the table, private view, or reuse view based on attributes that fulfill the business requirement. In our example, we have selected reuse viewY_CC_WELL_ALLOCATION, as it contains all the information we need on allocated volume. 3 Since we are creating a query view, we will select the QUERY category from the dropdown menu. Once you click on the FINISH button, then the calculation view type will be set to query.

24

·' I X

~ ~ ~

c


2

tmp.OomoConteni::Y _CC_VOLU ME VSA

"' . O
Ow""

610tw!'Wf'l ~ermT,.

0wJ-In1Hf'dl•pN>

X ..,.,. % , 0> • • •

Columns Wl_t.O:

!

A

,._,..._v.,u_ALLOCA •· 1'14_ -..o

= OH_N<>. Y_(':_V.1U_AU0CA"JJ'•·C'l_N0 m YK_NQ; Y_CC_l'tfLL.I1iLLOCA~. NC_NO

•aownerl nter~qutMe

Ow~lnttte:tt~

• Alloc.-lotlfrlt(!Ufncy

Alloc:•tioof•~r

6/0flgkwltingMe-..rtmeMPt

Owigifwlingt·~•'"'~...

•tr~~

T1.n,pcwt"'

• 'VII:IUtMtJnil

e ON:_NO_t: r_CC.. •'•UVUOCA~.,I¥_ <\t e CTJt(); Y.CC_Wf •.-'HOCAOO.'J-C'T.NO

Yo;d•f•...Jnil Ut.ttingYAMit H••l '. ,. Ftw-1q•Uoit

e OWfUS
illoi HieMing~nill

He•tii'IQVt t..lc: ~rqyllnit 9Aot~OC!

t

~DT: YCC_>'I!4L.Al!~T(;USA_OT

~ OWN_IN l _fVPl_CD.: "· •• l"od'. AU.OCA

&ldtlc:d&lc:t~

(t~lith:&l'lll:'l ln

~nUnit

VoiAf'ciiKfiUnit

We~tion

Ylcl(o•pktion

Wd

Wo·l

WdG~n-idePct

\'ll'~Ovcni~cl

• &.Ol"'4lnf11le~n

[n\itl(.d(ncnA~n

>

.......,. No~

Act....,.&wr~clucn

Atluo~FroMqrftf'
o..t.T>l'"

~dutn

Aclu.ll'lfoll:t'diJm

f iltfl'

• £1ntitk-4VOiftcoOJtn Adfustt.tltitttciYol .,.Ar.d;ated&ttitkdEngJ

""" • • :::l · i ~

.trl()CAT"CW.()I. "'

kh.1•1Yofio.!•c

(nliti«
l tngtl\

A4tKII"
""'

11Xl" -

Fi gure 21 Creating the Query View in SAP HANA Live

tmp.OomoContont::Y _CC_VOLU ME VSA f'RAControtel

s..~~O•tc Jse m~

_--=t

Jon

a

. ....
Unloft

~--

I ''

'JI Orrn~:rtntcraUfll'olt: IK c

J

W AIIoc.C.iol!lfr~y

•• ......

....

1-

];;)

g ON. NO: l'_Ct"_WW....aOC.UJO'•.ON_NO G

Aao<.o liot'.f-f~~oc:r

• Tr.-portcr

fr~•tcor

W VOI.Im~UNt

v-..m!'Vnit

WHu ting'hiUM H-u tinqV•'Iuco

HNtin9V~t

... wrcMJM

fnHfi'I'Onit Mhul'lolu•e

w Aoctu.IVolume

[ntillt-df•ot!tC)f'

Vt)lltt,cll("f\VM

Vl)ltM:IU(I\II..WI

W~'ott

\"ldK-ompktlon Wt
EMOtte~Mfl

---·

Aoc~gyR~n Ac~n

Nlt..afW'r~Rt'dl•n Ati• ..WoiK~

Entlttt~du
(nti t\r(IY.;Mirduln

AldjmtdEntltl.tdVol

AdjoniHI'nlit~lf\IQI

~cdEntklitd&lgy

Adjust.cdlntitkdln.q\

wc._Nel r_cc.vmL.ALLOCATION.wc.NO

6 Dt( N0_'1: '1'.CC.t.'o'ft._.A.LOCATJON.Do\I.II
B OWHJNIT_JYP(._(:[); I'.CC.WEU.ALLOCArJC. H OWN. IS
H~o1r'4"' J

EntiekdErl.trf'l

Wei WrtGIIIOvetricltP
G$ob.l f'.tdd Nfm~

B W\) 0. 'I'_Cl..• WEll,.AUOCA1JON.I"i:_o\'O

O..,.t>crlntctclt~qy..

'~i O rigiNtiftgMe-tmtntf't Oricjn•tingMN,Uit'-

~_O:_'h!U...,.AUO

c;..,.,.,

" ... Cok.wnn.5

""'""

OwnHinlt'lf'~tl,fW'

toO-rtntcrm lypt"

I

!

...,.._

<

Gcftutl Ptopcrtf

Nom• o.tt T)'Pc ...H

l"'9'h

""'

'""' Job Type:

User

~ted by'NARAHGMAN' to be ~d. to '
YOM ,t~UH

Apptu!i&ft(Ofnpotlenl

On.HsigMd -·

Fi gure 22 Selecting the Query View in SAP HANA Live

4 The query view is created as shown in Figure 23 .

25


2

tmp.Oomocontont .:Y _cc_ VOLUME VSA Ovt..t PRA(ontr.cl Cal s..&ed>•t~

S61eo~D•tc-

t.! Owncr

Owtlil!f

~ OWi'M'tlnt~redT)t»

Qow,...,ffl1f'ff'ft IJfM" Owntrlntco:r t:t\.S(:qu,_ Aloc.. tior.FI<'Qllt'lltf

4W 0wncftt~tt:r~S~oti'ICC lliJAAoutioftFr~I'IC)'

A X ..,. % , . •

I I I

'"

WVotlmcUnlt w HutingV....Nt

...,._

Hu fnqV•'uc

tl

....

-

~

H t n Nt o· lnH~t

wAc~

Ac:tu#lohJ•e

\II£Mitk d£Mrov

[,,titkJ(,oe;'JJ

.-\\llltecLcnUnk • Wd!Compktion

Voltl"dtKnUni1

W tt

WeiKGIIIplction

w w.tG.OVf'fridePrt

\'lf'll \'lf't(loHOvNfillt
~ Erotitk~duc.n

(ntidcd[t"tq'~Rcducn

N.~rgyRe«Kn

w lvttwNoiRcducn Entitk~ducn

....... ~ftllfdVol ~cd<lt.....

I CT_NO: Y_CC).'If.u ..AUOCAiJON.CT..NO 1 SA...OT: y_cc_Mu.ALLOCA~~-or g OWNJNT..TYPt..ro.- v-. ...... v.m.A.u.cx.:.u~t I OWN_ISQ._HO: YCC_/,.f, ...... UOC'A10' o. ...

V•••m..unll fl.....tin')V.aiUnit

w Erwr~nit

Acl•~rr,.Rf'duc"n Act~H~Vo!RC'du(n

OtU«); 1 l'"r_llt'Hl.A!tOC.CrJO!.:.Cn NO W(.,Na Y_CC_W1H_AlLOCA1JOI".'.NC_NO

g ON_HO_.,: ' ..cc.~·.lu...AuOCATIO\I o~¥_.._,

t~~ O rlgJNt~.wemeMPt Orlgin•tif141.,~•SUff'WTr~cr Tr.o118pcul~

PfOJt••

---

"' ... Colutnni W\..HO: ...._.. .;litU_AUOCAOO!O:.O'Ii._ 'fO

,'

>

Gcnut l

i ,,.,.,.,.

I D•tt T)JIC Ntmt

f •lttt

(ntiiWIf'dbotit.,.d\ltll Adjl.Ktf'Ciiontldrdl.nq\·

100!< -

. 1.

........

x

Note: CNngft ..-e Swed Direct¥

Gklb-.1Held ~nus

( t(tg
U"'"slgMd ... ~ted by•NARANGMAN" to

VDM f>ropeftiH

bcJd to '
~.:lon(omponent Vn.Ksign.td - · Te~rirlclogyO~tnein

u~

Figure Z3 SAP HANA Live; Query View

2.4

Value Help Views

A value help view provides a list of all the valid values that can be entered in a specified field. Instead of entering the value in the field, t he user selects a value from a list of valid values, which generally helps to prevent typos. A value help view provides an efficient data selection mechanism and also increases user convenience. Some of the general guidelines are as follows: » Value help views should on[y contain the required fields and not contain any unnecessary fi elds. » Value help views should be assigned analytical privileges so that the proper authorization can be granted to the end user.

26

'1;11'-

c


I

2

» The value help view should not contain measures, which are quantifiable data (such as revenue, sales, etc.), and consist of attributes, which are descriptive data (such as Customer ID, city, etc.). » If a value help view contains a logical key consisting of multiple attributes, then an appropriate variable of the value help should be assigned to each key attribute part to get the correct data. For example: Assume COSTCENTERVALUEHELP consists of attributes SAPCLIENT, COMPANY CODE, COST CENTER, and COST CENTER NAME. The logical key will consist of attributes SAPCLIENT, COMPANY CODE, and COST CENTER. In this case, variables are defined for the key elements SAPCLIENT and COMPANY CODE. The steps to create a value help view are as follows: 1. Right-click on the package under which the view will be created and

then go to NEW • CALCULATION VIEW .... You should create your own package for the virtual data model and should not create the model in the SAP namespace. For our scenario, we have selected the package DemoContent.

~ COnfi)orelr11CIOI'ISerrel

(tfi of

"

..,

r 'flf'MffH u

QI •

......

8

~v;..,._

O
Alulytoc '"''''9'·PIO
O 'htiOale

Rtf!IO'IItfllt~

~roltttOt,cru-

"

ltcfl>(to<

0 AC""'IIIt

~

O R:ecl~

~I

NNJO~

j ., t1

I

Typ.. ! u.«~ ...

'

~

! . l .. l • ""• o

..

Figure 24 Creating Value Help Views in SAP HANA live

2. Once the calculation view is created, then you can select the database

tables, the private view, or another query view based on the fields that

27


2

will be consumed in the calculation view. Usually, the value help view will be a projection of the reuse view of the respective business entity. In our example, we have selected the reuse view Y_CC_WELL_ALLOCATION. lmp.OomoContont ::Y_CC_WELl_Al lOCATIOH VSA Sct.uric oQ

v ...

(OfU!'I'W'I4{36) V.ew ,.,Opofftii!S KtfMChits P•t.-t~tUflJV~ti

.,.,

.. ,,.

'""" ,.,_

3 (ID Join_1

aDO

• -Y.O:,.ALL~'lln

Jv.occ..- .

'Kf Nomt

1.411:1tl

0 0 0 0 0

Ht-'Mg'l•lue fnttgyUnle

Dl 0 0 0 0 0 0 0 0

Ht.tw~gV.eut

f:nttg)'Uft.t t.ct.....Wolll'ft.'lt

Actu.r.'c""'-t

Entitltdlnttgy

(lltitl(d[ntl'gy

Vol~ecfU
Vo~uc.nUn.t

Wti Com,lotclot
W~ICOftlplcbotl

Wol

Wt!ll Yl'ttGt SOvtnidtPC't (l'ltitfc
\'lttG-'~'ttl'i6tP
Artu.N'ollteducft

Am,..CV~

EncJtlt'dVOIRtducn

(tlbtffd'/otR.d"'" Alf;usttcJEI\Cltlt
AcJ)IIstdntc)td!IOI Adjlntdrd:k«l'9f

Adj..l~cd[t

AdjusttdEI'Uit
• I

Figure 25 Creating the Reuse View in SAP HANA live

3 Since we are creating a value help view, then we will select the VALUE HELP category from the dropdown menu. Once you click on the FINISH button, the calculation view type will be set to value help.

-

iCi Soloct Ce.togory

Scl«t the requested U ttgOty

Un•»ignocd

v

"-· lS

Erforcc pn,ttc .. ,C'W v•ml<~tJon

Priv.ttc

-·

R
j~

(i)

L

r.noh

I

C•ncel

Figure 26 Creating the Value Help View in SAP HANA Value Help

4. The value help view is created as shown in Figure 27.

28

Extend ing SAP HANA Live Views

Sct:nario ~

GU ~

Oetalh:

Output

·:: ...

~ -··

, .- - -

3

~

4

co

Cl!> Jo'n

8

.).

Columns ~ WL_NO: Y_ CC_ ~'ELL_ALLOCAt'ON.Wt_NO D DN_N(), r. cc. wELL.ALlOCAr;o,o,:oN.NO ~ WC.,NO: Y,.CC.WE~L..ALLOCATION NC..NO

Union

.:.

Proj~..

a•

Aggr...

~

Ra.nlc Vatu~

·-Figure 27 SAP HANA Live: Value Help View

3

I

Extending SAP HANA Live Views

As you know, SAP delivers developed virtual data models consisting of private, reuse, query, and value help views with SAP HANA Live. However, often the standard views are not able to fulfill all business requirements, and therefore, an existing model must be enhanced. Some of the most common ways of enhancing predelivered models are as follows: » Including an unexposed field from a standard model » Excluding unnecessary fields from a query view » Including custom tables » Including custom fields

29


We'll discuss the steps for each of these custom enhancements next. Before we get into the details, though, remember the following important points about extending SAP HANA Live views: » Do not extend SAP-delivered views directly. Use query or reuse views for extensions by copying them over to your own namespace. » Graphical calculation views are recommended for all enhancements. However, if your business requirement consists of a complex calculation that goes beyond the capability of graphical views, use script-based calculation views.

3.1

Including Unexposed Fields from a Standard Model

In some scenarios, some unexposed fields present in the views are not shown in the query view, but your business requires showing those fields for reporting reasons. Let's say, for example, you want to do a trend analysis of the allocation volumes discussed in Section 2. The model already contained the YEAR and DESCRIPTION fields in the reuse view, but they were not included to the query view, which made trend analysis impossible. In the following steps, we include the fields by creating a new custom query view: 1. Open the query view (in our example, Y_CC_VOLUME) from the Demo Content package in SAP HANA Studio (Figure 28). 2. Check if any fields required for reporting are not exposed in the query views. A field may not be selected in either the reuse or the private view and, therefore, is not visible in the query view. In our scenario, we need the YEAR and DESCRIPTION fields, which are not present in the query view (Figure 29). In our scenario, we will assume that all the fields are included in private and reuse views but not included to the query view, which is the most common situation.

30

I

3


3

tmp.Oomoconteni:.Y _cc_VOLUME VSA B4 S t

Oet.h

4 ••• -·

"

X • "" x ' " •

Cl!)

Jon

610rwnHI ~erti1T,.,.

OwMf lnt~f~ (fl·~

•Oownt rl nler~qutMe

Ow~lnttt e:tt~

• A:Jioc:.-lotlfrlt(!Ufnty

A.lloc:4tioofr~r

tiOf~Mti!Wrtlt'leMPl Or igifwtingt•\e•'uf~... fWlr~~ Tt.tn~opcwt"'

W¥oUme\Jnil WHiu4ift9V. . nill He•tii'IQVt ll.lc &wrqot~Jnit

¥o!Rif'Wc:nllnit w W dCorlllpktion Wd

Ylcl(o•pktion Wo·l

WetG.OWrridePct w &.titlc4("9)'1tcdlitc:n

Wl'~Ovnfidoi'cl

&ldtlc:d&lc:r~

ActUolllll'ltr~ducn

""" - " :::l - :! >8

~ OWtf_IN l .TYPl._CO: "· , _ Vod'. AI.. :A A!l()CA~()I. "'

e OWtUS~N(); Y CC >'If

>

£ntiU,d(ncnA~n Atluo~l-roHq,ftNiutn

~durn

Actu.ll'ltollt'dum

&.titlc~OoKn

lnlitkdV. .h::-bn

~tdltltilttciYol

A+Ktl"
-~tdlmitkdEngJ

e

YohfMI'UIIit Ut.ttingYAMi t H••l ' ,.

f rw1q•Uoit kh.1•1Yofio.!•c (fll;tlc&f'lll:'lln VoiA<'ciiKfiUnit

•A<~"'

+ "'

ColumM ~ Wl...HC>. ,._,.._v.:u_..w.OCA •· w~._ -..o ~ OH. N<>. ,. r- v.tu._..t..UX:.4l'JO'•·C'I_,..'O ~ W<.NQ. Y_((_l'ffU_,i11L.I.OCA~.NC_f.IO ~ ON_HO_t: r_C\,_ .',fL4_AH0CATJO,'i"~"-'C Cl.JfO; Y.CC_','Jf••-'UOCAOOr'lC'TNO C 9._01: v CC_ o•,f~, t_.A.H~ "t)IJ tA_OT

~tedlntilkdl"9'1'

""'

100% -

Fi gure 28 SAP HANA Live Qu ery Vi ew

V PRAContract

PRAContract

-.r S.anDat~

Satc-s.Oate Owne r

" Ow noer ~ OwnetlnterestType " Ow nc.r-l ntc:restSc: q~ncc:

titAio
Owne-rlntere~t lfpe OwncrlnlerestScqu... Alloc:itionfrequen( '/

- OriginatingMeasurementPt Originatir9,1c.uure... w Transportcr

TrarHJ)Oftcr

w VolumeUnit

Voto•eVnit

• HutingVaM.Jnit

HcatingV•IUnit

Hc4bnqV6tue

HulrqV•I ~ ~

w Enerq;Onit

~rwrqrUnit

w ActuaiVobnt:: w Ent htedEnergy

Actuo~IVolumc

VoiR
Fntitlc:dfntrru \'outeducnUnit

We:IJ(omplction

Well

w..n

WetG.OnrridcPct

Wrtch•tn

£nt~tedEngyflc dutn

ActuoiEnorgyR
A
EntillwiVoiRt-du( rl Adjustrdfntit~Vol

Adjustec!lintltted!ncn

Figure 29 Qu ery View Fields

3. Since the field is not exposed in the query view, copy the already existing view to a new view in your own namespace (Figure 29). To copy the original reuse view, right-click on the view name (in this case, Y_CC_ VOLUME) and select COPY (Figure 30). 4. Navigate to the package where you are going to write the copy, rightclick on the package name, and select PASTE (Figure 31).

31


fd~

[ itt

View

frojt
,tiavigatt

.

·~

[j · 9,0 Sj
[01

Bun Window

• ~ <> . Ntw

-

· I liill il

ll!l V_CC_WELL_D

ICP Triggers

GOP Vitws ~ .,!g ZZ.MDM Jg _svs_AFL ~ ~

~ _SYS_BI

~

;;lli, _SYS_BIC

Ctri+Shift+V

Actwate

( ti1 +Sh•ft +A

Rtdtploy

q

Data Preview

~ Vlhtrt·Ustd

!g _SYS_TASK

t> G:P Provisioning .. (.:7 Content

,. til

Validate

Revert To A
~ r.~ _SYS_REPO ~

~ Q

~

'

Optn

ffil NETWORK_OO

:m v_cc_wELL_A ~

l:ftlp

.

.!)

History

)(

Otlett and Act ivate

n

Auto Oocurnttltatio n Demo(ontent Copy Calculation Views .!] V CCC WELL Rtfactor v=cc_vot Utif :0 V_C(WELL_ALLOCATION

C t~ + C

~

..

'

\J

~ ~

~

£B Modifitd_Vitws !lf l>ublic £B REP

=

.:ii.

Figure 30 Copy Query View

fdit

f ile

froj tct

View Mavigatt

.

(8 '

c:1 ·

~ Sj
•a

Tables [!ll NE l' ~ fH' Y_C fH' v_c f)

~ ~ Vitws ~

i: lZ_MOM ,.g _SYS_AFL

~

.g _SYS_Bl

~

;: _SYS_BIC

~

_.g _SVS_REPO

~

~ _svs_TASK

1> Q. Provision ing

.. @to Content ~

f9

~

£B Modifitd_V Sf public £B REP

~

~ t>

Win dow

j~Ntw

~ ~ Triggm ~

Bun

• ~ <> .

' '

Ntw Find Refresh

~

Auto Docum entation

c

Activate

Q

!:!t ip

.

I

C t~+F

F5

Rtdtploy

I

Edit )(

Delete

Delete

•

Remove Filter

:w

Otmo( ont •

Filter Objects...

Paste R~actor

Ct~+V

'

af sap

d. sap-templat es

Figure 31 Pasting a Copied Query View

32

3


I

3

5 In the dialog box, enter a n ew appropriate name for the custom view. In our example, we used Y_CC_ VOLUME_M_QUERY_VIEW (Figure 32). liQ Copy Object Enter a name:

Y_C(_VOl UME_M_QUERY_VIEW

Jl

OK

C•n<
Figure 32 New Custom Query Vi ew

6. Once your new namespace view is created, include all the fields in the view required in reporting. The YEAR and DESCRIPTION fields are included in the custom query view (Figure 33). Modifi•d_Vi•ws::Y_CC_VOLUME_M_QU ERY _VIEW Sct.'nario

~

1!.1+ 8 t

". .

Oe-Uils

-

Gr ... .,

J somanti
Join

1:

8

Umon

.

\ill

Proje...

Output .. e ADJ_ENTl_CT_VOI. .. ~ ENTL _CT_VOl ~ WG_OVRD _PC CIFREQ..CD

CIORIG_MP_NO

.

...

1

0~

Aggr...

Ranl.

•

• • m

~

100%

>.:\. <.!\

I ~ Propert•es 0 Error log

ADJ_ENTL_CT_VOL ENTl_CT_VOL WG_OVRO_PC FREQ..CO

·"' W

• TRNSP_NO TRNSP_NO ,.OWNJNT_TYPE_CO OWN_INT TYPE ..CD "'OWNJSQ..NO OWN ISQ..NO ,.OWN_NO OWN_NO "'WC_NO WC_NO " MATNR MATNR .. sA_DT SA_OT w YEAR YEAR w OESCRIP110N DESCRIPTION w ACTL_Vot. ACTL ..VOL w ACTL_Vot._U ACTL ..VOL..U w HEAT_VAL_U HEAT_VAL_U ..,HEAT_VAL.,l HEAT_VAL_l HEAT_VAl HEAT_VAl ACTL_ENERGY_U ACTL ..ENERGY U

-

!3 ~

Job log t3

',-

Properties

,..

.@

rT Hi'\1 ,

_

• •

t

=

E~

'------,

Property

Value

Name

ACTL_ENERGV_U NVARCHAR

Data Typt f•lttr

-

lOO% -

C:UTI

e ~'

•

;:j

I..Oi llllltlS

~ ENTL_CT_ENER_U: w ENTL_CT_ENER: _(t ,.. ADJ_ENTL_CT_VOl: - ENTL_CT_VOL_U: _ ... WG_OVRO_PC : _(<

ORIG_MP_NO

~ ,;j ~

Sl!!

l ength Scale

l

L __ _ _ _ _ ___J

~ liil

l'.. IJ.ili

X v=o

Figure 33 Customer Query View

7 Activate the view by clicking on the ACTIVATE button (Figure 33) and then test the view by clickin g on the DISPLAY DATA button to visualize the data (Figure 34).

33

3


JlJ All1tysis

1-.

LI] DirtlftCtvWes ~._,---------------------------'-.:...._-~---, ' !Mwlog I Max rows: 200 : .1.. C'J ~ lOO r~ retrlcvtod · l se<. .Ul ms

Orig•nlbngMenuremtnt9t

« : : :: ::DC7 cc :: :: :::: :: coe c: :: : ::: :o1 occom: oo:: :oe occom :oo:: CC1

_, -7 m.

~7 OOC«''XX(OU I h

~ ~()()8

«: :::c::: )(IC)C)000006

« :::cc:: :XKXl000006

«:::m: :'XX#.'/JIXI07

••••o•oll)•())0•••7

.

OOOO
cc:mcc:

~

c::mc: oo ~(ICI(O
oc:::c::ooc:,i::ooe oc::m: oocc"i:: ooe

"""""""'' """""""'' """""""'' """""""'' 2000000C01

"""""""' '' """""""' """""""' """""""''' """""""' '' """""""' """""""' '' """""""' """""""' """""""''' lOOO()c))6)1

"""""""'' """""""'' """""""'' """""""''

0

Kc.et.!g\'a!UM

Volumdlnll

Tun$p0rtt l

Mel Mel Mel Mel Mel Mel Mel Mel Mel M<:l Mel Mel Mel Mel Mel Mel Mel Mel Mel Mel

BCl BCl BCl BCl BCl BC3 BC3 BC3 BC3 SCl BC3 BC3 Btl Btl Btl Btl BCl BC3 BC3 BCl

Artu"fVolumc

57.6

f.u<\lte .,. Add filter

an.m

MBD

l•B

1,046.196 MBD

1. 8 lUll

"·'

1.048.913 MBD

Sl.Q67

037.696 1,04$..913

l.S lOU lOU 11.2

an.m an..,. 1.044.913 1.04$.913 lll.lll

12.8

m.m

101.2 101.2 S7.6

1,046.196

1.04.913

m.m

Sl.Q67 119.6

1.048.913

037.696

110.4

"·'

1.()48.913

101.2 3<8

1,046.196

833.)33

1.()46.196

. ..0

Sott tnt11e .S.U set

EnergytJmt

Hu tingValue

MBD MBD MBD MBD MBD MBD MSD MBD MBD MBD MBD MBD MBD MBD MBD MBD MBD

c:: :: o::

)II

000000000000007

c:

::::

•

cmomcomoe 000000000000007 000000000000007

...............

-

000000000000008 (l(O()I)('(I()OOX()8

000000000000008 000000000000007 000000000000008

:::cc:;OC((((()8

000000000000007 000000000000008

cmc:oocc:me cmc:oocc:me 000000000000007 000000000000007 >

Fi gure 34 Activated Custom SAP HANA Live Query View

3.2

. .ll

Well

Excluding Unnecessary Fields from the Query View

Sometimes, the query view contains many fields that you may not require. You can hide those fields and use only the fields you need by creating a new query view in your own namespace. This helps increase performance because unwanted data will not be sent to the reporting tools. For example, SAP-delivered views often contain fields that are not required in a final report, such as date or timestamp. To remove unnecessary fields, create a new query view with the following steps: 1 Create a new query view in your own namespace or copy the existing

query view into your own namespace (Figure 35). 2. Include the SAP-delivered view in the new query view or paste the copied view to your own namespace (Figure 36).

34

·J

Ext ending SA P HANA Live Views

Eil ~

~avi gat ~

Vi.w

fdit

C'!l ·

froj~ct

.

@

~ S\'st
Bun

• ~ <> .

-

l:l

:m v_cc_wEll..A

() Validate

Ctri•Stuft +V

t _o

A
( tri+Shrft+A

'Ill v_cc_vm

1.3 Triggers llitws

"

R•d•ploy

4

Oita Prtvi(W

~

Whtrt· Ust
w

~ ~ :Z.Z_MOM

,:! _SYS_Afl ;g _svs_BI ~ ;: _svs_mc ~ ~ .,;: _SYS_REPO ~ _SYS_TASK ~ e> D Provrsronmg ~

f9

4

R•v••t To Act•v•

~ History

Sir Content

4

'

Open

:Ill NElWORK_OO

~

!:!•lp

.

N.w

ttt · l !:.!! n

t>

~nd ow

Demo( onttnt

)(

Otlttt and Activate

r

Auto Docurntrltation

Copy

• W. Calctrlation ViMs

.!'J v_ccc_wELL

Ctri• C

Rthctor

'

'] Y_CC_VOLUM

:.J Y_CC_I'IEll_ALLOCATION t>

~

~

£B

Modifitd_Vitws

mpubloc

=

f2 REP

Figure 35 Copying the Query Vi ew

[ dit View

f ilt

~avig att

C'!l ·

(9

?.o Systems ~

~

Glr Trigg C.. Vitws 0 .!g zz._MOM ~

,Jg _svs_AFL ~ .i!I _SYS_BI ~ ~ _SYS_BIC ~ -Jg _SYS_REPO ~ -!g _SYS_TASK t>

fd. Provisioning

• ~ Cont •llt t> OtmoCOllt •

"

~

fB

Modifi
fB

REP

Fir\d

Rdrtsh

-

~

' ' Ctd+F

F5

Auto Documentation Activate

R•
)(

Dtltu

:it>

filttr Objects...

Otlttt

•

Rtmovt Fitttr

e

~

!::!•lp

.

Ntw

1IIJ NET' 1IIJ Y_C ~ 1lll v_c t)

~

~in dow

• ~ <> .

Ntw

_

• Glr Tabl
~

Bun

.erojtct

Pant

Rtfactor

mpublic

~

!If: sap

1>

f1t..e sap·tun )latts

Ct~•V

'

Figure 36 Pasting the Copied Query View

35

3


I

3

3 Select only the required fields and remove the unnecessary fields from the copied query view. In our example, the custom query view Y_CC_ SALES_M _QUERY_VIEW does not require the fields SA_DT or WG_ OVRD_PC. Accordingly, we removed the fields in the OuTPUT tab by right-clicking on the field to be removed and then selecting the REMOVE option (Figure 37). Modified_Views::V_CC_SALES_M_QUERV_VIEW Xtn;~no

L·OUI

<;how: c.AJ:I::..'- - -·'1

Join

8

..

Typt

Umon

a• ;j,J

N11mt

0 0

Projt... Aggr.M

Kty

- , Join_t

(I)

w
I

Jv _OC_\1\fl.l._ALLO

R.1nk

t -

w

1

JR.OCCJ)COSTlfS ..; R_OCC.)RCIOOS.

•

0 0 0 0

0 0 0

labtl

hbtl (t>lurnn

H1ddtfl

t.tATNR ACn_VOL_U

DES<:RJPn.. FIS<:Al. VI •.

DES<:RIPTIOtl

0

VEAl<

0 0

ACn yOL

SA_OT_l

SA_DT

ACllJ fiiE ~.

ACn . ENERGV,_

HEAT...VAl HEAT_VAl_t

HtAT...VAl HEAT_VAL_l

Sum

Sum Sum

Valut htlp v .. ""

0 0 0

MATtJR ACn_VOL. ACll...VOl

0 0 0

SA_OT SA_DT 0 0 OWN.NO... l OWN.NO 0 0 ORIG..MP••. ORIG_MP_tiO 0 0 WG_OIIItD•. WG_OVItD_P( 0 0 TRN~_NO TRNSP_NO 0 0 llWN NO n OWN NO , r,-LL~~~-~~--~-~-------~ ~~L-,

1011% -~ . ;j :..::l ~

Fi gure 37 Required Fields for Query View

4. In the AGGREGATION node, add the necessary columns to the OuTPUT

tab by right-clicking on the field and then selecting ADD TO OuTPUT (Figure 38). 5. Activate the view by clicking on the ACTIVATE button (Figure 38) and then test the view by clickin g on the DISPLAY DATA button to visualize the data (Figure 39).

3

Ext ending SAP HANA Live Views

~ ·
Modified_Viows::Y_CC. SALES_M_QUERY_VIEW

0tHpot W nrv.~\...1.11::>\.fl.

8

HITl.CT.vot IVG. OVRO_I'( TRNSP NO OWN_NO

00 OWNJSQ_IIO

OWNJSQ.JIO

•%

~

Prc>Jt...

o•

Aggr...

wCIIlJoru

.:Jv .OC.Y'oEU_AU.O.

Jbnl..

t -

. IR_ccc_DCOSTTES •. I

R_CCC_[)RCTCOS

.. FR£Q_CO S ORIG_I.w>.)¥:) MA.TNR tiSAJ>T SlOWN_NO_l

fREQ_CO ORIG_,..,. NO MATNR SA. OT OWN_NO

w WC_NO

WC_NO

e AC1l_VOl_U • •cn_vOt

AC:TL_VOl_U ACTL_VOt

Sl DESCRFTION

DESCRIPTION

e YEAR e SA.OT). e ACTL_ENERGY_U S HEAT.VAl S HEAT. VAl.l tiHEAT_VAl.U tiENTL. CT.VOt. U tiENTL_CT_ENER

YEAR SA. OT ACTL_ENERGY _u HI:AI.VAl HEAT. VAl. l HEAT_VAt_U ENTL.CT. VOt. U ENTL_CT_ENER

, + •

1il+ 9 't

,. . . Columns ' MAUlR: •. ' ACTL. VOL. U: .' - ACfl,.VOl: :~ •.... ,. :~.. DESCRIPTION::;, •.... ::. FJ.S(Al..VEAR: '•. •.... C..:

tll OWN_~T.TYPE_
Union

.g)

w ENTl. CT. VOl • wG.OVROJ'C \ITRNSP.NO t.JOWN_NO

- Sfl..DT,..l: ' •.... :.:.. :'l·...

' ACTL. ENERGY.U: -

••• •

HEAT VAL: '.:-. •. i"!t."' , ...

~ ~ "~--

Nam t

hbtl

Typt

Aggrc-guion

lnputsfl)

Jo•l..l (Nodt)

Figure 38 Custom Query View Output

~tn•ri~

lil•

~: ·--

e•

Del .lib

.... " (Jl)

Join

8

um~m

~

Projt...

a•

Aggr...

~ b nl..

Output

----

-ll'frv_~\..ut::lo'.rt

~

oBIHIf' e. · l !t ~ • . . "' , + ·

~ • <1!1 1

Modified_Views :Y_CC_SALES_M_QUERY_VIEW

,

w ENTl..CT.VOl

Js.mlf'ltk•

. 1

.18~- .j ;.,:

'=]
(I)

W'
.

I

.

t

-:I Join_1

JR.OCCJ>COSTTES .. ...., R..OCC~TCOS

tOO'.O

<.:\ 1.!\

;:j

!..:!

~

ENT\.CT.\/Ot IVG OVRO I'( tiWG_OVRD_PC WTRNSP.J
sr-• -

i!ll 8t

X

• . . Columns ' ' '

·-·

'

"" ~'d

''

MATNfl' ACTL. VOL. U: ' • ..! .. A( Tl_VOL: ':-· ·-·.. ._ DESCRIPTION: ._: ~E f iS
-

HEAT VAl

[l.~ j '

..

•_:..

·~

Prop~• tie-s

•~

• :;.reA-, ...

-

Ptoptrty

V• lut

Namt

Aggttga\IOn

hbtl

Typ< lnputsl ll

Aggregatioo Jo•1..2: INodtl

. @

'!! ;j :..:i

1::: ~

Figure 39 Custom Query View Data

37

.

E


3-3

J

3

Including Custom Tables

Custom tables are required when the existing SAP-delivered tables or default functionalities are not able to fulfill your requirements. Say you want to generate reports on the relative downtimes of objects in your network; if not reduced, downtime can result in hundreds of thousands of dollars lost per day in - for example - the oil and gas industry. However, SAP-delivered tables are not able to fulfill this requirement, and therefore, Z* tables must be created. The steps to include a custom table in a view are as follows: 1 In our scenario, we require table Y_CC_DOWNTIME to store the down-

time information for network objects. The table is created by pressing the green button, which executes the SQL shown in Figure 40.

I~ - CR~ EA~T~ E ~co=L~U~ ~N~ TA~B~ L E~ .. z= z~ _L~C~ !"~ • .~ .. Y ~_~ CC~_~ OO =f~ lii= Tr=v= E·~ · 7. ("~ ' ~~ AI~ ID~ T"~ NV~A7 RC~H~ AR~(73~ ) ~D= EF~ A~ U L~T-.~~ ~.. ---------------A-''Dl_IIO'' NVARCHAR( 20) DEFAULT ' ' ''Jifl 110'' NVARCHAR( 20) DEFAULT ' ' , '''.'ATIIR'' NVARCHAR(18) DEFAULT ' ' , ''CT_110'' r..'VARCHAR( 10) DEFAULT ' ' , ''SA_DT'' NVARCHAR(8) DEFAULT '00000000' , .. DATE .. NVARCHAR(8) DEFAULT ' 00000000' ..Oflll 110.. NVARCHAR( 10) DE FAULT ' ' , ..Oflll-IIIT TYPE CD.. NVARCHAR( 2) DEFAULT ' ' ..Ofiii=I~JJO.. NvARCHAR ( 2) DEFAULT " , ..ORIG_''P_110.. r..'VARCHAR (20) DEFAU!.T ' ' , .. TRIISP_110.. r..'VARCHAR( 10) DEFAULT .. , .. FREQ_CD.. NVARCHAR( 1 ) DE FAULT ' ' , .. ACTL_\A?l_U.. NVARCHAR (3) DEFAULT ' ' , .. ACTL_\A?l .. DECIMAL( l3, 3) CS_FIXED DEFAULT 0, .. HEAT_VAL_U.. NVARCHAR ( 3) DEFAULT ' ' , .. EJJTL CT IIOL ll' NVARCHAR (3) DEFAU LT '' , .. EIITL=C(EIIER.. DECIMAL( 13, 3) CS_FIXED DEFAULT 0, .. ADJ_EIJTL_CT_EIIER.. DECIJ.IAL( 13, 3) CS_FIXED DE FAULT 0, .. EIITL_CT_EJJER_ll' NVARCHAR(3) DEfAULT ' ' , ..OIU_ CRUSER.. r..' VARCHAR (12) DEFAU!.T ' ' , ..OIU f iVESTA" P.. D ECI~IAL (1S, 0) (S FIXED DEFAULT 0, PRIMARY KEY ( .. ''AllOT .. ' .. DL_IJO" . -

,I

..HL_IIO.. ,

Fi gure 40 Custom Tab le

r


I

3

2 Create a private view for the downtime table and select only the required fields by right-clicking and then selecting ADD TO OUTPUT. In our example, we have selected fields such as DL_NO, DATE , CT_NO, and MATNR for showing reports on object downtime (Figure 41). ~ · d\\ I O O · I~ · I rr e. · l ~ ~ -

DemoContent::Y _CC_DOWNTIM E Sum~r'io

q

®•

·..-...

--'" d

e'

Jom

8

Union

...

Proje...

••

Output

5 DL_NO ~ NW_NO

...

5 MATNR ~.NO 5 SA, DT

] Se.-;.o

.

l

.

~ DATE

{W . ;:-} ... . I

Ag9r...

~

Rank

1-

Oet.1il$

$ OWN,NO tiOWNJNT_TYPE_
l"lo0%1:\~ ;_j .,_,j :g

~I

j

·+ H ·:1 "I.... ·Ie. e•

8

~ C olumns

I Dl_NO: I I I I I

Add To Out put

Propagm to Stomarrtrcs $elect All Tables ~le ctAJI

Joms

NW. NO:

_((_~·

:~.

MATNR: _(.:_:·,.., SA_DT: _c.:_.:t.; .. CT_NO: _((_:·v DATE: . C ~- ~C ..

-• I

Cc:sdc:ctAII

-~

...

:::." ..... T

-

-

-

~

~optrties

Propc-rtt~s

Genttal)

Proe!!!l

-

Name hbtl Type

J Value Projection ProJtct1on

_:::] l•o~~ o

(l)

~;j ::::J I? 4

Figure 41 SAP HANA Live Private Down t ime View

3. Create a reuse view (in our example, Y_DOWNTIME_ALLOCATION) by creating a join between the private view Y_CC_DOWNTIME (created in the above step) and the Y_CC_WELL_ALLOCATION allocation reuse view created in Section 2.2. The join is required to get the information on the downtime for the allocated network objects (Figure 42). 4. Create a new query view from the reuse view and include all the fields present in the reuse view, except the fields TRNSP_NO, SA_DT, and CT_ N0_1, which are not required for reporting. Right-click on the field and then select ADD TO OUTPUT to include the field in the view (Figure 43).

39

I

3


DemoContent::V_DOWNTIME_ALLOCATION Sctn.ano

Outp.rt

•

Jorn

-

8

Umon

DI•OCOitttt:'I'.CC..WRt_Alloc;.ATJ:)H w EHT'L_Cf.£HEl.,.U 91Tl_Cl .ENEILU w am...CT.fHEl 9lTI,.Cl.ENEl w fHTLCTJ •OLU 9lTLCT.VOLU WAQI..(Hl\..CT,\Q AOI..OtTt..CT.vot

fl(Q_CO

.......

• oWN.NO

Oo'iHJSQ..NO

wWC.IOO WMATHct

... s.t.._or

~

R.tnk

wCTJ«)

e oATE

OMUSQ..NO

UATMR

SA..ar YfAl

DESCilP'ti)N

OESCIIrmoti

ACTt..VOl ACll...\'Ol.U t§AT. VAl,.U

ACTI,_VOl ACTI..\'0\..U 1€1\.T V.QU

t«A.I'. VAU

l
~'I.VAl

'-tAf.VA.l 1..01

lob Log

¥ 0 WHJSQJIO

VTAHSt. HO w FOlQ..CD • ACrl.'JCH. U

WC.Ml

~

• o WH_lNT. TYPE.CO ~ ORICi.MP.NO

OWN.fCI

.t(:TL._ENUGY.U

Proptrt•ts 0 tnor log

w tlW..HO e N.ATlfR

OIIIG..M='.~

" OW'N,.'IO

Aggr...

e ou«>

wrt.IQ_CO

EHTl.Cl.VOI. 'I!IG.OilD.K

TIJfSP.NO Ormt.JHT.l"f'J(.C D
a•

. tu.HO T

• OD:i!..MPJI()

wfHTL,.CT. YOt

• .,.,'G..OII.OJ( w TtHg_HO

.1 PrOJt...

'"Zl_tcX.Y.cc_DOwtmME

WAC'Tl.'«H WH£1\T.VAI..U

:z •

,.. z --4' + •

~ AI>J~NTL.
r ENIUUNER: • ••• ~ r ENIUI.VOl.V: • ' . : r HI'AT.VAL.V: • "<". ' r OlJ'IO: . cc. • ' ri: ""~· .......

EHn_cr_vcn_u

Property

V•lue

EHTl.CJ.IiHER

Namt hbtl

Jo•\..1

Typ< Join Typt

Join

AOJ.Etm.CT.EN(R

• fHTl,CT. tMCR..U OIU.CRUSER au.llld:ST.u&P

1!1+ 8 '

.-. ;a. Columns

_!J

Inn«

. 1 .1

!3

X

VC>

0

Figure 42 Custom Reuse View Join

Otn>oConttnt::Y_DOWNTIME_QU ERY_VIEW Sun.ario

4 ·.) ... (:> ...

rlf

.,

Dl"mo( ontr nt Y I>OWN i lMI AI I ()(A I ION

.. Ol..NO

01.)'10

• NW.,NO

NW~NO

OWN.)SQ..NO: .~. ..

•

8

WMATNR "'CTJ«J -..CT_NO_l wSA_OT

cr..NO

- OWNJNT..TYPE..CD: .. =' I ORIGJ.

CT_NO_l SA..DT

t.IOATE

OAT£

I ACTL. VOL. V).:

.;J

Union ProJt•••

~~· Aggt...

&J

Rank

MATNR

-

8 0WN..NO OWN.NO e oWN)SQ)'IO OWN_ISQ_NO _!OWNJNT_Tm_ro OWN INT TYPE CO e ORIG ORIG tv'F NO

-.,. TRNSP_NO e FREQ.CO

TRNSP_NO FREQ.CD

P1op>trty

e ACTL..VOl.U

ACTL YOI. _U

e ACTl.VOl

ACTL. VOl

N.amt

e ENTL.CT..VOl..U

ENTL..CT..VOl..U

o~t.a Typt

e ENTl.CT.ENER e H:AT..VAL..U

ENTL_CT_FNFR HEAT..VAL..U

Fil'ttf length

ACIL..VOL..U: .. ~ _ ,

.,.

.,. J

ACJL,.VOL: ..:

ORIG MP NO trYARCHAR

20

Suit

Figure 43 SAP HANA Query View Fields

5. In the SEMANTICS node, mark all the included columns in the query as attributes or measures by selecting the column and then clicking on MARK AS ATTRIBUTE or MARK AS MEASURE (Figure 44).

40


D•m oCont• nt:: Y_DOWNTIM E_QU ERY_VIEW

q " ...

.....

"'

(olumns(l9) View Prop~rtiu

Hitr~rchiu

ParamtttrsjVariablu

loc:Jil

Jom

a ...

Union

lhow. c..:I AI::...'_ _..J · I Typt

Kty

0

Ag9r...

0 0 0

(Y

0

Rank

0 0

PrOJt ...

o•

0 0 0 :-

_

0 r:l.

Namt

Dl ..NO NW..NO MAn~R

CT.NO CT.NO.l

SA.DT DATE O'NN..NO

OWNJSQ..,.. OWNJNT.... ORIG_MP_...

Labtl

AggrtgatH>n

Vanablt

Dl,NO

tr.•.•_NO MATrtR CT_NO

CT..NO.. l SA.OT DAlt OWN..NO OWNJSO_NO OWNJNT_TV ... ORIG_MP_NO .....

~~·~"'--~'"_Y." ' ~f"'J>t

Fi gure 44 SAP HANA Query View Semantic Model

3.4

Including Custom Fields

Sometimes, one or more custom fields must be added to the standard table, which is then added to the model. For example, consider a situation where a customer wanted to classifY downtime types so that proper proactive action could be taken. The most straightforward way would be to create a new reuse view using a modified table and then create a new query view that combines the new reuse view with the old standard query view (if required). To do this, the steps are as follows: 1. Create a new graphical calculation reuse view in the customer-specific

package with an appropriate unique name that conforms to your custom object naming convention (Figure 45). 2. Locate the table with the custom field(s) in the appropriate schema and drag and drop it into the new view. In our example, the table Y_CC_ DOWNTIME, which has custom field DOWNTTMETYPE, is added to the reuse view. You can include the fields such as DOWNTIMETYPE, MATNR, NW_NO, and many more in the view by right-clicking on the field and selecting ADD TO OUTPUT (Figure 45).

41

I

3


3

3 Switch to PROJECTION node by right-clicking on AGGREGATION and then selecting the SWITCH TO PROJECTION option (Figure 45). D•moCont•nt::Y_CCC_DOWNTIM E_TYPE Iii+ S 't

O~tails

4 ·.L . . , ...

-I:::~.:~: ::~.~- ~

...NW_NO WMATNR.

<0

• cr_NO _,SAJ>T

aD

.. oAn

Join

NW.NO: _t _;•
"'OWN..NO e,.,a.nd/CoUa.pst

SAJ>T: _, ._: , • 00\VNT...E_TYPE: _( • •

OU.l!Puvif'W

"" o•

Projt.-

, ,-,

Otstlt
Aggr...

~ Auto·l a.yout

~

Rank

!.w'lt
( tri •O

'---.,.---, ........,..,...,_,....._- =' "'OIIJ.CRUS!R WOW..TIMESTAMP

<[

10 ~+

-

Figure 45 Reuse View and Projection Node

4. In the SEMANTICS node, select the individual columns and dick on

MARK AS ATTRIBUTE (Figure 46). ~

D•moCont•nt ::Y_CCC_D OWNTIME_TYPE

• IN! I 0 0

· I ~ · I r1 Iii!> · I !) 'd •

SctnllnO

4 ,;• ...

....

(olumm( l l) View Prope-rties Hitrlll'
aD Join

8

Umon

Type

l: PrOJf'···

o• ,y

Aggr... lhn~

Kty

0 0 0 0 0 0 0 0 0 0 0

Name

DL.fOWNTIM... OWN_INT_...

..

"

----l ·l

Show: L:I AI ::... I

hbd DL_tffiME_T•.. OWN_INT_TY... ACTt..VOl..U AClt_VOL

Aggregation

Vari11ble

label (ol\unn

Hidckn

0 0 0 0

H~I\T_YAI -.

H~AT_VA.I _V

HEAT.VAl. . .

HEAT. VAl.U.l

0

AClt.VOl

Vah.a help Vflt'N/

0 0 0

0 0 0

ACll..VOl ...

Sum

- wd.

Figure 46 Custom Field Reuse View

42


Now, copy the standard SAP query view and then paste the development objects to a customer-specific package with an appropriate and unique name that conforms to your custom object naming convention. The steps to do this are as follows: 1. To copy the original calculation view, right-dick on the view name and select COPY (Figure 47). f ilt

fdit

['l ~

View

Mavigate

i(.J

·rs

~indow

froje·ct Run ~ ~

~

¢r

~

= 1:1

'I<> Sj<
Ill'> I t:l! t>

!:!:elp ~

U · II:I ~ d ~

fa. Synonyms

"'

.

HlJ NElWORK_D !Ill v_cc_oow~ ~ ~ ~ ~

~

~

: ZZ_MOM J _SYS_AFL ~ _SYS_BI

_svs_Bic

~

•

J _svs_REPO ~ _$YS_TASK

b Provisioning liP Content ~

tB ~

Open

0

;.;;; v;..,.,

~

~

t>

v_cc_wm_

Oemo(ontent

... Calc\rlation Vit'W

'J v_ccc_oow .!] V CCC 'NELL

:F] v~cc_Oowr.

•

Now

'IIJ Y_((_I.'IEll

(?;. Triggers

DemoContent::Y_CCC Scenario

• fill. Tabl"

1>

OtmoConttnt.·Y_OOW~

Co'>

Validate

Ctr1+Shift•V

~

Actrvate

Ctd+Shrft•A

r-'

~ cc

Redeploy Rtvtrt ToActl\'t

!---,

~

Data Preview

~ \AJhert· Used

Jj

History

X

Delete and Activate

f'

Auto Documentation (t~ + (

Copy

•

Rdactor

:'J Y_CC_VOLUME :!'J Y_CC_WELL_ALLOCATION

II

J

lOO%

Figure 47 Copying the Query View

2. Navigate to the package where you are going to write the copy, rightclick on the package name, and select PASTE (Figure 48). 3. In the dialog box, enter an appropriate name for the new custom view. In our example, we used Y_CC_CUSTOM_DOWNTIME_QUERY (Figure 49).

43

I

3


~ SAP HANA Administration Console- o.mo<:ontent:Y_CCC_DOWNTIME_TY

f ilt

fdit

~:· · 4

~avig1tt

View

~ ~ ~

ii':<,

tl

"'ll svs

['J

,'l UPLO 0

J

:zz_t

,C: ZZ..M

"

_svs_ _svs_l X _svs_l ~ ~ svs ~ J ~svs~ ~ ~ .~g

~ ~ ~ ~

~

1

e. Provosoo"J,

liP Content·

~indow

l::ftfp

New

:;::j ~

Bun

= El

[

Catalog ~ lOr Publoo

;,.

frojtct

New Find

(tri• F

FS

Rtfrtsh Auto Do
Activate

Rtdtploy Edit

Dtlttt

Otlttt

Remove Filter Fi~tr

Objt
Paste Rtfa
~ ffi Modot ~

I

f!i. Smority

Figure 48 Pasting the Copied Query View

ICi Copy Object Enttr a namt:

V_CC_CUSTOM_DOWNllME_QUERvj

CoK~

I

Canctl

Figure 49 New Query View Name

4. In the AGGREGATION node, add the necessary columns and the customer field DOWNTIMETYPE by right-clicking on the columns and then selecting ADD TO OUTPUT (Figure 50). 5. In the SEMANTICS node, mark all the included columns in the query as attributes or measures with the MARK AS AITRIBUTE and MARK AS MEASURE buttons (Figure 50). 6. Save and activate the view by clicking on the icon shown in the green rectangle in Figure 50.

44

I

3

Integrating SAP HANA Live Views with SAP Business Intell igence Solutions

J

4

Modifitd_VItws::Y_CC_CUSTOM_DOWNTJME_QUERY Sctnario <1

·::•

Palt ...

Join

(olumns{l.S) VitwProptrtits Hrtrar
I

Js.o=o. 't

8

Union

• 0' - : -

l oul

rl

Sl>ow' ,__I AI_I _ _

91 ~,:P• ~8<)' "'

o·

Aggrtgat...

;g) Ranl.

- , a•

_, •I

o

•

N";NjlO

0

t-rn_NO

()'NN_f..IO

OWN_NO

0

Tl\IISP_NO

TRI'ISP_NO

u

o

•m.vot... •cn_vol_u

i

0 0 0 0 0

FREQ..CD 0WNJ5Q_...

FREQ..CD

0 0 0

O'I.'N_M"_. ~

OWN_INT_TY...

0 0

DOWN'TlM..

OOWNllME.T•.•

I

R

. '

0 0 ,..,__

•

h btl

OWNJ~NO

OWN.J'IT.... OWNJNT..lY... ACTL.VOL... Affi.VOl.U ACn _VOL

ACTl_VOL .._.~ ... ,{}0.

0 0 0 0

,._-'""' _ _ _ _ _ _ _ -.r:->

Figure 50 SAP HANA Query View

4

Integrating SAP HANA Live Views with SAP Business Intelligence Solutions

These days, customers have various business needs for reporting, such as taking action on real-time information or even future forecasting. All analytical business requirements can be broadly classified into three categories:

» Operational reporting is used for day-to-day business operations (i.e., task-oriented, line-item information on individual transactions).

» Tactical reporting uses trend analysis to identify potential risks. » Strategic reporting focuses on key performance indicators (KPis) and helps companies recognize trends and patterns. Currently, SAP HANA Live provides you with the transactional data present in SAP HANA without any redundancy or latency and is best suited for operational reporting. This approach, which simply involves integrating SAP HANA Live with the SAP BusinessObjects 81 toolset, is discussed in Section 4.1. Ifyou require tactical and strategic reporting, SAP Business

45

[!].- 'b


J

4

Warehouse (BW) is more suitable, and SAP HANA Live is not necessary. In situations where all three types of reporting are required, our suggestion would be to adopt a hybr id model, which is a combination of SAP HANA Live, SAP BW, and SAP BusinessObjects BI. This approach is described in Section 4.2.

4.1

Integrating SAP HANA Live and SAP BusinessObjects 81

SAP HANA Live can be integrated directly with all the SAP BusinessObjects BI tools (SAP BusinessObjects Web Intelligence, SAP BusinessObjects Dashboards, SAP Crystal Reports, SAP BusinessObjects Analysis, and SAP BusinessObjects Design Studio) and SAP Lumira via SQL and ODBC connections (Figure 51) to fulfill reporting requirements.

Analysis for MS Office/ Design Studio

SAP Crystal Reports Enterprise

SAP Crystal Reports Enterprise/ Dashboards

Explorer

SAP Lumira Desktop

SOL

SOL

SOL. Calc Scenarios

ODBC

JDBC

JDBC

SAP HANA Database

Figure 51 SAP HANA live and SAP BusinessObjects Integration

In Section 2, we created a virtual data model to examine production allocation. We will now explain how to expose the production allocation


virtual data model to SAP BusinessObj ects Design Studio to showcase the data in a visualization. Please note that, although we use SAP BusinessObjects Design Studio as our example, the steps in this process are the same as for any of the other SAP BusinessObjects BI tools and SAP Lumira . First, we need to check if an HDBODBC connection is available by following this path: START • CONTROL PANEL • ADMINISTRATIVE TOOLS • DATA SOURCES (ODBC) • SYSTEM DSN (Figure 52). ~

~ OOBC Data Soor
u..,. ~!illJ SyttemDSN ~ DSN ~iveo ...!] To~ ComeclionPool<>g_iAboutj_

System Oata Scuces: Name

.

OWer

0

~ IBMDB20DBCDRIVER·DB2VIOO

BACKLOGN IBM DB2 0DBC DRIVER · DB2V100 DB2DKERB IBM DB2 0DBC DRIVER · DB2V100 D82DSP IBM D820DBC DRIVER · DB2V100 D82EKERB IBMDB2 0DBC DRIVER · DB2V100 DB21KERB IBM DB20DBC DRIVER · D82V100 D82MKER8 IBM D820DBC DRIVER · D82V100 DB20KERB IBM DB2 0DBCDRIVER· DB2V100 --Ol:L.~-'~o.nc....o.n"" trO on.,.t~N__:_

U1

I I

Add... Remove

I I

I Conlig
An OOBC System data $0ll'ce stOfes infOti'Mtrln abol.A how to connect to

the i'dcated data P'Ovideu. A System data $0UI'ce is visible to al use~ s on this machine. inclldng NT $8rvice&

I

OK

II

Concel

I

Apply

,I

Hoi>

I

Figure 52 HDBODBC Connections

If an HDBODBC connection is not available, then you have to create the connection by following the below steps: 1. In the ODBC DATA SOURCE ADMINISTRATOR, select the SYSTEM DSN tab

and choose ADD (Figure 53). 2 Choose the SAP HANA database driver HDBODBC64 (Figure 54). If this HDBODBC connection is not available, then you need to install the SAP HANA Client Software from the SAP Software Download Center.

47

I

4

Integrat ing SAP HANA Live Views with SAP Business Intell igence Solut ions

'i' OOBC Oata Source Administrator u,., DSt!] System DSN FleDSN Drivel$

~ Tr~ Corneotial Poolin9 About

System Data Sruce<

.

Name

Driver

~ BACKJ.OGN DB20HRB DB2DSP OB2EKERB DB21KERB OB2Ml<.ERB OB20KERB

IBMDB2 0DBCDRMR · DB2V1~ IBM 0B2 OOBC DRMR · 0B2V1~ IBM 0B200BCDRMR ·OB2V 1 ~ IBMDB2 0DBCDRMR · DB 2V1 ~ IBM OB200BCORMR ·08 2'/1~ IBM 082 ODBC DRMR · D B2V1 ~ IBM 082 OOBC DRMR · 082'11 ~ IBM OB200BCORMR ·OB2V1 ~ n•

01

0

II Add.., II I Reroove I I Codigure... I

-

"

An ODBC System data S:OUrce stores inforrnaOOn abol.A how to connect to the i'dc~ted data PfOvidet A System d8ta $0UJte it visible to !I use.s

on tM machne. ird.ldng NT service$.

I

01(

II

Concel

I

Apply

,I

Hop

I

Figure 53 Adding an HDBODBC Connection

Create New Data Source

Select a drive~ for which )0.1 want to set up a data $0(.1ce.

Venion l l!!\r:1'iTir:lil J SQ[Te

Com

1.00.55.48833 SAP 6.01.7601.17514 Micr 2009.100.1617.00 Micr

~I

Cancel

Figure 54 HDBODBC Driver

3. For this example, enter the data source name and description as "VS5". The server and port is hana.sap.edu:30015 (Figure 55). 4 To test your new connection, choose CoNNECT, enter your SAP HANA user name, password , and server port (hana.sap.edu:30015), and choose OK (Figure 56).

I

4


X

SAP HOB (1.00.li>.OO.l86119)

~len

S
Figure 55 Entering the Server Name and Port

SAP HOB (1.00.83.00.395324) Server and Port Server

User and Password

Password

•••••I

fJ Connect usng SSL

Figure 56 User Credentials

5. You will see a popup that says

CONNECT SUCCESSFUL!

(Figure 57).

SAP HOB ODBC Connect ~

Connect successful!

OK

Figure 57 SAP HDB ODBC Connect

6 The new connection is now added to the (Figure 58).

SYSTEM DATA SOURCES

list

49

I

4


~ OOBC Data Sowce Adi'Yiinii:tratot (64-bit)

X

U... OSH S,.Oom OSN flo OSN 0...... T"""" ~ P....... Hx>J.

:i>J«... o.tos.ue..: "4
MOOBC Sy«etn&ta sout:e teotMWOIII'IilbOtl abol.t how to<:Onf'l«t to lhe hCScated di!ta l)ft:Md«. AStslem data eouoels vistlle to al u.s of this COfi'IPIJ.et, l'lc:ludrlo t'TteMoes.

Figure 58 HDBODBC Connection

Once the connection is established, you can now analyze information models developed with SAP HANA as data sources in SAP BusinessObjects BI tools. In the following steps, we will use SAP BusinessObjects Design Studio for development: 1. Start SAP BusinessObjects Design Studio from the START PROGRAMS

menu (Figure 59). D:J wo,d20U

.

I"'.UOll

Figure 59 SAP BusinessObjects Design Studio from t he Start Programs Menu

50

I

4


2 Once SAP BusinessObjects Design Studio is open, then click on APPLICATION • NEW to create a template for the report (Figure 60). !f:!J>IIUtiOtl

Larout St•(h

ptarWI•ng fdtt

"HI

:o -·

. ..,

!l,lfW

Ioob t;ltlJ'

a·

-,,. ,-----------.,Cil;---;:1:!,......,

c::o

t'"'li-:N..., - ... - .. ,

1y1~-tflfttl h>:t ~ AnJiyt•c Compontnh

0

I:J P109«rtltS

tl

P•opt11y

Appllc.atlon

0 Bane Comi)Of'ltnu

( rutt ~n ~•s ~pl•<•bon

l ~ Contwltt Compontnu

-

~ Cunon\(ompontnu

-

1&-st . .l

~ Scn(OII'II'nl.lrllll}'6t
g:; OWnt ci

~

\1\P. Prtn. H.t!...J wt. Rtport

0

SA.PJ>•tu.Ha•\l_lwt.ltt-port

An Outhnt IS not IIYJIIJblt,

I~

Ttmplltt

Catt9~lc~>< ::.:•':::'"':!C"'::::-="----------' ·I [

J!>
=

Fi gure 6o New Report Temp late in SAP BusinessObjects Design Studio

3. This creates a blank template to which we will add SAP HANA Live views as data sources. To do this , click on the ADD DATA SOURCIE button (Figure 61). :-) SAP_Pre-s:s_H a.na_U~_R.e-port ·SAP Bu ~iMssObj-ect Ot-~ig n Studio Pla,,ning fdit ).a.yout ~arc h ~tw Iools !:!.~lp

~pplication

i ~ !!!

rH~

-.-: Componenh

IJ i

:

'0 . ;.

t:3

008

c

0

c

0

typt fJit u u xt

1-

f!>. Analyti< Compontnts (!:> BasK Compontnts ~ Containtr ~ Custom

e

CompontnU

Compontnts

Xn (ommunrty GtoVI S

-

~ Sen Community Prototyp~s

~

Outlint

ti '\...

338

..,.

'YI•t hlttr ttxt

• li] SAP_Prtn.Hant~_L ivt_lt~po11 ~ o ... ~

~ Pl•nn;~ ~ Add o... Sou«<... Qt. L t~yout •

Add CurtomOiltll Sour

~ Ttchn·

'll co~

-

.

Past<

Figure 61 SAP BusinessObj ects Design Studio Data Source

You can connect SAP BusinessObjects Design Studio with SAP HANA Live virtual data models using an OLAP connection, which allows us to view

51

4


4

the virtual data models (Figure 62). The OLAP connection is created by your SAP Basis team (Figure 62). !J>pltutJon

n :;;

"'-*"

C· (0Wip~1

="' ..

(.tot L-n So-M(h ~· 10?1> Help

0 ·'

'
._,

si

~

-i •

0

til t..

(i]'SAP.Pt~~.HN\I,JNt._R#I_.. i3

I '"' ~C-.-!ltl

l

.... B.I'IO<(OnopcHI«
• . (Ofttilnoro ~I'CJ

~-- -... c'"'""'··~ Gnwot ~ ~~~C~PtO'~I"'

=

1~ Outllllt u tvl)c nil:~• t tl( ~

L
r)j'-""' - "''• _ c...c...• '- _ _ _ _ _ _ _ _ _ "'_"--, y l l ~ F
~- CUJtom~J

[I) SAP.frtti_HI~h·;c__R~on Qt O.ota'j,oouoct't

a. Pt-.g ObJ«tf

•

Conn.to<-1!1~t

~ N.Ia upt-e.1

l&r...tL.. I O.ot• SoulctAiiu •

OS_t

Qt. tymtn-loul ·

tt<~~k
(dd'I'Jit)

..........

~ l~ovt ~ . . f.C~.oji(OO"f''"~

~ CONTlXT..MfllU

~======~==========~ ! ~ I .......,. Figure 62 SAP HANA Live Virtual Data Models

Once you have added multiple data sources to SAP BusinessObjects Design Studio, you can use SAP BusinessObjects Design Studio to design a report like our example production allocation report shown in Figure 63. !iili

Production Allocation Reports

USO, ive••ge lnOtlth •ate, .-tl'lol.oo

ACWI YIO 2014

,,.

•

"'

r

Not ~

--

--

,,

.

"

10

1 •

1

2)45071fl0t112

Ac;Jwl2014

Aclllll2015

Ttf9t12015

23

• Jdull2014

4

5678f

Aclual2015

10H12

1

234$67ff10

Ttf911201S

Figure 63 Production Allocation Report

52

11

11

Integrat ing SAP HANA Live Views with SAP Business Intel ligence Soluti ons

4.2

Integrating SAP HANA Live and SAP BusinessObjects 81 Tools with SAP BW

SAP HANA Live, together with SAP BW, provides a best-in-class suite of analytical services. SAP BW offers multiple advantages that are not present in SAP HANA Live, such as:

» Hierarchy support Only simple hierarchy features are supported in SAP HANA. For more complex hierarchy needs (t ime/version dependencies, sign r eversal, etc.), SAP BW is required.

» Complex data transformations Only simple data transformations are supported in SAP HANA. For more complex transformations, SAP BW is required.

» Authorizations The authorization concept in the SAP HANA core is simple and covers many use cases in most situations you may encounter. If specific func tionalities are needed (such as authorization variables and hierarchyrelated features), SAP BW is required.

» Report-to-report interface The report-to-report interface is a functionality that enables j umping from one report to another or to an SAP Business Suite transaction. SAP BW offers a wide range of report-to-report capabilities, which work in tight integration between BEx queries and various backends or target reports.

» Planning scenarios Simple planning scenarios via (stored) procedures can be created in SAP HANA. On the other hand, the standard functionality of planning in SAP BW (PAK/IP/BPC) is also rich. In this section , we will take the same production allocation report that we created earlier with SAP HANA Live and SAP BusinessObjects Design Studio (Figure 63), but instead, we will use SAP BusinessObjects Design Studio on top of SAP BW to create the report. When an SAP BW system is

53

I

4


running on an SAP HANA database, then the SAP BW data is stored in a special schema known as an SAP BW managed schema, as shown in Figure 64. Master data from SAP BW and transactional data from SAP HANA is combined together in a composite provider, which is then exposed to a BEx query for the creation of reports. -

SAP BW on SAP HANA

I

I

BEx Query

I

+ Composite Provider

Master Data

Master Data

I

Transactional Data

/ \

/

I

SAP HANA l ive Calcu lation View (Reuse layer)

SAP BW Schema

'-

'-

SAP HANA Schema(s)

/

SAP HANA

'Figure 64 SAP HANA Live and SAP BW M anaged Schema

In this example, we want to use a Composite Provider, which will allow us to merge data from classic SAP BW InfoProviders with data from SAP HANA models using unions or joins. The first thing we need t o do in order to create a Composite Provider is to create an SAP BW project (Figure 66). To create a project, execute the following steps: 1 Open SAP HANA Studio.

2. Click on WINDOWS • OPEN PERSPECTIVE • SAP HANA MODELER (Figure 65). 3. This will open the SAP HANA BW MODELER PERSPECTIVE. The developer

can then create an SAP BW p roject as shown in Figure 66.

54

I

4


r=

SAP HANA Modeler SAP H4NA Stud1o

,.-r"

f ilt

f dit

Navigate f_rojt
Window Htlp

NewWindow Editor

~ Sl'•t•m• !:3

H;d• Toolbar

lit ~ I E!l I ftl,

8

<::> ~

SAP HANA O
> ~ SAP HANA Mod
Show v;.w

DEl (Sle

4

-----Customize Ptrsptdtvt ... Sivt Ptrspt
Othtf...

Rtstt Ptrspt
Navigation Prtftrtn
Fi gure 65 Opening t he SAP HANA Modeler Perspective

8\V Modrhnq 5.AP HANA Studio

i!1

E8 I ~ 9-P I-IAtiA Adnlii\IStrMJOn Contolot

~

SAP WANA Modtlt;

iO .•. ..

. . ;.,..

•;r:;~••••••••••• c.~ h i( 6olnto 0

CtrhShdt•O X Dtlttt Ro:mo•~ fr

~ ew Qutry-

'::1 OptnOOSV1ew... G DattSt01ot ~ct (•dv.ti'Kcd),_

(JOPort...

t} RtfrHh

{ lou Projt
£J CompouttProYidff-

trhAJt• !ft.-D m

• Import...

0

CJ f-oldtr

Otktt

m Contt
(I) fffl Moddng = 0

0 ~

X

" L9 0tlur...

V. .d11tt

ProfiltAJ OtbugAs

Run A$ R«tort from Loc~ 1-MtOI)'···

tion .-.

~ Atu
Conf•gu•t

S...«

Fi gure 66 The SAP HANA BW Project

Once the project is created, the n we need to create a Composite Provider by executing the following step s (Figure 67):

55


1!1 Iii

Back End Favoritu

i:l Favoritu

e-arl lnfoProvidtrs

at r;:9 II lOOESIIOTCOIItiECTEO) Unassigned Nodes

~ ~ f•lB'.'.') Business In fonnation Warehouse · . ~ l1lB'.\'8P( '.'.'SIInfo-aru for V•/ork Statm System I I'JBWTCT] Techmcal Content

1/ CompouteProv1der et Open ODS Vitw

Op
e

IOFS
Figure 67 The SAP HANA Composite Provider

1. Enter the BW PROJECT, NAM.E, and DESCRIPTION for the Composite Provider as shown in Figure 68. - I o 1..2LJ M a ndatory Information

Browse ...

J OEl_LOO

InfoAru:•

r

Srowse...

Add to Favorites J PRODAllOCRE~

Description:

J PROOALLOCREP

Browse ...

Copy From:

Root Operation:

r.

Union

r

Lmtdoin

r

ltft OuttrJoin

tj

II

finish

Canul

Figure 68 Creating t he Composite Provider

2. Click on the SCENARIO tab and then left-click on U1/UNION to select the ADD button to add the SAP HANA virtual data model as shown in Figure 69.

4

Integrat ing SAP HANA Live Views with SAP Business Intelligence Solutions

B

Scenario: PRODALLOCREP

/ ® U1

\ ~

~ Till get

Sou<«

m

-I I

Print... Delett

., .

I

4

C!i ~ · I X

!I \ 11 .G

J

Jy

Jy

e

<±1 8

Iii CD IU1J N••l•1))

~ Rc:prace.

(f) Join with..•

e un on

.mh

r'~ S. rtch Inputs

Sort E~ort OUJgram ..,

Ctrl• 0

Gen~7Jl Sc~nano [butputj

Fi gure 69 Add ing the Composite Provider

3. Now add the SAP HANA virtual data model to the Composite Provider as shown in Figure 70.

l

Graphicall Form ·Based Source

T

• :!'J (SalesOrderltem) Reuse voew for sales order rtems n45•12) ~ ~

Ia (!CharactuisticsJ Charactenst1CS (125•10) 12:> (IKeyfigures) Key f1gures (20•2)

[T

Target

1±1 8

•
• Ia JGENERICJ Generated Group (0•0•10)

Ill

(ODOC_CURRCYJ Transaction Currency (0•1)

t.. (OASCPER) Fiscal year/ period (0•1) &. (OFJSCVARNT] F"cal year vanant (0•1) &. (OASCYEARJ F1scal year (0•1) ~ (OMATERIAL) Material (0•1)

r: (OSALE.s_GRPJ Sales gr«>up (0•1) ~ (OSALES_OFF) Sales OffiCe (0+1) ~ (OSALESORG) Sales Organizatron !0•1)

jJ )OSOLD_TO) Sold-to p•rty (0•1)

Ill • lao

(OUNIT) Bm Un1t (0•1) JiKeyFiguresJ Key F1gures (0•0•2) jj )ONET_VALUE) Net Amount (0•1) (OOPENORDQTV) Ope11 Delivery Qty In Base Un1t (0•1)

if Ill

Fi gure 70 The SAP HANA Composite Provider

4. Create the output structure for the Composite Provider (Figure 71) by moving the SAP HANA Live virtual data model fields from the left-hand side SouRCE column to the right-hand side TARGET column (Figure 70). The output structure fields will then be exposed to the BEx query.

57


~ •JOEl) PRODALLOCREP

~

4

t:l

Output: PRODALLOCREP

"" ComposrteProvider Fi~kls

• ~ (GENERIC) Generated Group ~ (OSALESORG) S.los Organi:atron ~ (OSOLD_TO) Sold·to party tf IOUNITJ Bose Umt li (ODOC_CURRCY) Transactron Curroncy ~ (OSALES_OFFJ Sales Offrce ~ (OSALES_GRP) S.les group ~ (MATERIAL) Material j. (OASCYEAR) FIScal year 1Ji (OFJSCVARNT] F1scal y~ar variant & (OASCPER) fiSc.l year I penod

*

• (0 (!Keyf i gures) K
(OOPENORDQTY) Open Oelr.ery Qty In Base Unrt

jp (ONET_VALUE) Net Amount

Figure 71 Composite Provider Outpu t Structure

5. Create the BEx query (Figure 72) according to your requirements from

the recently created Composite Provider. The BEx query will then be exposed to SAP BusinessObJects Design Studio to create the production allocation report.

.

=.

8b Q\IC1)' Dts.g~ · ~ PI'Od11C1lot\ AiocWon F'.q)M 1

...,.

'"" ..... · 0 ~ 8 .- l oht l!!l' I X Ill e

.,

E61.

v-

Kerrogur~•

"'"-.......,

,u. .

s f~~·Y

~~... ~,($~ '9~ 1 ~ ·

.......,....,_,

9- iij -

flNAiiCIA.LMOIHH

e o..n..Mw~.

Aetu.IIY02015

Our.~ipllian

r~~

r~-·

• La ·

r u.~d t...,

recllniu!N.. ~ A-•

.......wor """'........

. "'ff~ l

• 'W.Jec.de'on 2 f8 \o/et~ 3

(

.... .... (

~ "'el~4

(

Wlti~S

"' f ilt:r

fl lO'o'r\/Coh,lf'Ml

I

Pi cvicw

~lit:.eoJf".go..M

""' (.... WoT ( ....

Actl.llf ~

~ 'RO

t

I

1)1'

, ..O't: Y\0

....

T

~

J

Figure 72 BEx Query for Production Allocation Report

6. Now, start SAP BusinessObjects Design Studio from the START PRoGRAMS

-"

................., ......, ,....... J"""'-1

Ttf901Yl02015

' it Oifl'.oiMoOftt

G' tt

I Pl'opcr'li>es

fi .-·i A.:IwiY0201•

:: !J f - ChclreK:4erUtiet

a 0

a

<) jl ~ [ljl ll I:!' Q i'fm]'SI I,tl]..:. l 'bl l ~ ·

l~owsiColumns

lnloProvider

m enu as shown in Figure 73.

Integrat ing SAP HANA Live Views with SAP Business Intelligence Solutions

DJ

VJord ltlB

•

f X(tl 20l3

Ill

Powt1P04tlt 20 U

4

~ Qu~l)' Du•gntr (;SAP Logon

~

SlliPI)I09 TOOI

®

SJ..ypt for &ts• l tsS lOlS

)

D •.J

f.lottpad

SAP HANA 'Studto rtv~6

Pamt

Fi gure 73 Start Programs Menu

7. Once SAP BusinessObjects Design Studio is open, click on NEW to create a template for the report. Afii>IICUIOon .;1 ~

P!Jtl!WU)

f~

,._

~~ Compont~lt1

11

Lavo~a

Stardt

!+ 9

•

APPLICATION ·

·a · ·

0

-

~-o

0

-

1111 ~ AtiJiytl( COtl'lpontnu

l

I~

AppliG:Iitio1t

& s•<(ompot'lci'IU

(Jtatt '" •n•IY'Iolt •pphc•t•on

(ontMMW (ompontnu

~ (unon'l (ompont•nu

~ Sen (onwnu~ GtO¥it

e

Sen (OI'I'In'IU~ Prototyptt

i

O!Aklt l3

An outhnt ts not 11\'Jdablt.

j -

0

SflP_PttU_H;oonJ_l~_Rtj.Ort

SAP_Plns_H•n•_l~Yt_Rtport

!:ltJC )

II

f n•ush

)I

(al'l
Figure 74 SAP BusinessObject s Design Studio Templat e

Now, we have a blank template to which we can add SAP HANA Live views as data sources for SAP BusinessObjects Design Studio.

59


4

!i: SAP_Press_Hana_li'le_Report ~SAP BusinessObjec:t ~sig n Studio ~pli cati on

rH~

Planning

~~

•.:• ( ornpontnt:s

l!l

fdit

l,.ayout

I:l~

~a rch

Y.i~

:o .: .

a ~

I ools !:!
a: tfl8 ~

-

1:1

t}' l)~ flkfr hxt

--

(('7 AAalytic Col'nponents

G:> Basic Compontnts

C> Container ( Oillf)Ontnts ~ Custom

Components

(5. Sen Community Gtovis ~ Sen

Community Prototypes

~ o uttint ~x t}' l)~

l:fJ El

...

~

1:1

frfttr t t>t

• [il

•

SAP_Prtss_Hanl _l ivt_Rtpo r1

(;:,. Data So ·" ' (;:,. PlamJ. ~ Add Dn a Souret ... (;:,. L•yout Add Ctrstom Data Sourct e; Tt d m i P;uu (0

•

'a

Fi gure 75 Adding Data Sources to SAP Bu sinessObjects Design Studio

W e will now add multiple BEx queries to SAP BusinessObjects Design Studio as data sources (Figure 76). !J>ploOn

PI~

r3 ~

.. . D

•.:.• (onoptonti'C.I

(dol

L-•

~a.dl

·o ··

y,.,. t ..e. ti•IJ>

.,

~-t

tJ

e ~c~ ~ 8oiOC(-'f'~

~ conu.." <~nt' ~ Cu$~Compot~mu

~ ~... c~Gc..o.. O S~"<~~o~y~

1• -1

O•'*-u:• tvp~fllldlt•l

O•~Se..uAII~·

OS.l

,.....,

• [il W J'•mJ4.,.•.J-Jt•poot a. ~~(t~

]j

&. flbniWigObJ«U

ll> t -

. QJ, Ttdw<• C~ ~(OtntX'T_MEr~

F o;

..

~

Fi gure 76 Add ing a BE x Query t o SAP BusinessObjects Design Studio

We will add multiple data sources and also perform customizations in SAP BusinessObjects Design Studio to create the production allocation report. The report will look like the one shown in Figure 77.

60

What's Next?

Production Allocation Reports USD. awnge month

I

5

:iili ••t•. WI miiiOt'l

- -"'"

..

,, 10

I

2

3

4

5

6

1

8

9

10

II

12

1

23

45

&78910

11

12

1

2

3

..

5

6

1

•

9

Fi gure 77 Production Allocation Report

5

What's Next?

If you've mastered SAP HANA Live, it's time to take your skills to the next level. Are you taking advantage of all of SAP HANA's advanced modeling capabilities, such as predictive, simulation, optimization modeling, and more? For your next challenge, learn what SAP HANA has to offer in the realm of advanced data modeling. Recommendation from Our Editors Ready to up the ante? Visit www.sap-press.com/3863 and check out SAP HANA Advanced Data Modeling. With step-bystep instructions and sample code, th is book wil l tea·ch you how to build and design predictive, simulation, and optimization models. From information views to A FL models, you'll learn to scale for large datasets and performance-tune your models to perfect ion.

In addition to this book, our editors picked a few other SAP PRESS publications that you might also be interested in. Check out the next page to learn more!

61

10

11

12

More from SAP PRESS Implementing SAP BW on SAP HANA: If you're using SAP HANA Live in

conjunction with SAP BW, here's another resource you'll want to add to your library. In this comprehensive guide, learn migration, modeling, and more for SAP BW on SAP HANA. 477 pages, p ub. 04/2015 E-book: $69.99 1 Print: $79.95 www.sap-press.com/3609

1

Bundle: $89.99

SAP BusinessObjects Design Studio-The Comprehensive Guide: In-

trigued by the SAP BusinessObjects Design Studio examples in this E-Bite? Find out what the tool can do and master all of its advanced capabilities in this comprehensive guide. 739 pages, 2 nd edition, pub. 02/2016 I Print: $79.95 I Bundle: $89.99 www.sap-press.com/3951 E-book: $69.99

SAP HANA Administration: Programmer or otherwise, everyone should

have a working knowledge of the SAP HANA database. In this book, get the complete picture on SAP HANA administration, from bootstrapping to maintenance. 722 pages, pub. 08/2014 I Print: $69.95 www.sap-press.com/3506 E-book: $59.99

I Bundle: $79.99

SAP PRESS E-Bites SAP PRESS E- Bites provide you with a high-quality response to your specific project need. If you're looking fo r detailed instructions on a specific task; or if you need to become familiar with a small, but crucial sub-component of an SAP product; or if you want to understand all the hype around product xyz: SAP PRESS E-Bites have you covered. Authored by the top professionals in the SAP universe, E-Bites provide the excellence you know from SAP PRESS, in a digestible electronic format, delivered (and consumed) in a fraction of the t ime!

Akash Kumar PlanViz: Improving SAP HANA Performance ISBN 978-1-4932-1300-9

I $14.99 I 75 pages

Eric Du SAP HANA Smart Data Streaming and the Internet of Things ISBN 978-1 - 4932-1303-0

I $9.99 I 85 pages

Wojciech Lukowski Data Aging for SAP Business Suite on SAP HANA ISBN 978-1 - 4932-1346-7

1

$14.99

1

101 pages

The Author of this E-Bite Akash l

Building and Extending SAP HANA Live Views.pdf

Recommend Documents