SAP E-Bites - 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 sig-

nificant 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 5

1.1 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . .. 5
1.2 Types of Virtual Data Models . . . . . . . . . . . . . . . .. . . . .. 7
1.3 Viewing SAP HANA Live Virtual Data Models . . . .. . . . .. 9
1.4 Basic Virtual Data Modeling Rules . . . . . . . . . . . . .. . . . .. 11
1.5 Basic Virtual Data Modeling Terms . . . . . . . . . . . .. . . . .. 12
2 Building SAP HANA Live Views . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.1 Private Views . . . . . . . . . .. . . . . .. . . . . .. .. . . .. . . . . . 15
2.2 Reuse Views . . . . . . . . . . ... . . . .. . . . . .. .. . . .. . . . . . 19
2.3 Query Views . . . . . . . . . . .. . . . . .. . . . . .. .. . . .. . . . . . 23
2.4 Value Help Views . . . . . . ... . . . .. . . . . .. .. . . .. . . . . . 26
3 Extending SAP HANA Live Views . . . . . . . . . . . . . . . . . . . . . . . . 29
3.1 In cluding Unexposed Fields from a Standard Model . . . . . 30
3.2 Exclud ing Unnecessary Fields from t he Query View .. . . . . 34
3.3 In cluding Custom Tables ............... .. . . . . 38
3.4 In cluding Custom Fields . . . . . . . . . . . . . . . . . . . . .. . . . . 41
4
4 Integrating SAP HANA Live Views with SAP Business
Intelligence Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4.1 Integrating SAP HANA Live and SAP BusinessObjects 81 . . 46
4.2 Integrating SAP HANA Live a nd SAP BusinessObjects
Bl Tools with SAP BW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5 What's Next? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
1 Introduction to Virtual Data Models

SAP HANA Live, which is built on top of SAP HANA, provides new high-
quality analytics and reporting capabilities to SAP Business Suite. Its pur-
pose 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
Introduction to Virtual Data Models I 1
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 Security History and Hierarchy

and Search Handling
Broadcast and Predictive Analysis Cross-System Analytics

Documents
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 transac-
tional 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
Introduct ion to Virtual Data Models I 1
HTML5 -based (Web and Mobile)

SAP BusinessObj ects Bl Third Party
Other SAP Solutions
Open Interfaces: HITPS, OData, SQL, MDX
Web
Resource
OData Service SAP-
Delivered
Query
SAP HANA XS Engine Views Customer Extensoons
Application Services
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________________ -J, I
• 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 calcu-
lation views. These calculation views can be broken down into the follow-
ing types:
» Query views
Query views are created for direct consumption by analytical applica-
tions such as SAP BusinessObj ects BI tools. Query views must not be
subsumed by another view and are always the top view in the hierar-
chy. 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.
I
'' - -----
-----------j---------- ~----- ~
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 data-
base to the query views. It does not fulfill any specific analytical sce-
nario 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
» 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<HANA-
ServerHost>:BO<SAPHANA!nstanceNumber>/sap/hba!explorer.
9
- ,. .
n-
f.o ~5tflnl 13 • 0 iJ IOf))PlOOAll O<RLP 13 - 0 ,i Q a: - 0
!lil • I IJ II • • 18 " 1o v ,a PRODALLOCREP
e {fb oo
(i.l ie (~log
®., ,,...,_,
$ Wt C<iW~t~
(! mDtmo<onw" ~ o....
:!: fi 6UI!I">I»M
(!: IJI, donognsll.odto.~>«<m>Oftl tc-<ch.onobu$1<Hdfrom~c b.odo ~. '"'" Oener
~ &; t;ty.~j«t
:E5 ~ (hcJ.Of,.~IFS•ukrtftk· ) P.dlcloflto rclo~tttc rt~.our<t. ~ Conti{;
Btl up
..
"' "'
l!) fli bo
S tl boc-
dJ Ot11f
~ tnport
® ifl: c~p ~ (Jpo1

® ti luo~
eel.,.• X, W,»t
®at .... 0 VIIIda
® $ «<
® $ ~tt O AcMt
"'t$! Ill: •
Q lofonl'to Q Rtat~
.. .c -
fi1 8h6 .:J .!.I...J £
Figure 4 The SAP HANA Live Package
HANA Log i n
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
In t rod uct ion t o Virtual Data Mod els I 1
• MM • Ma!enals MMagetneft BillingOoc... J•

DD07T rn e
• PA • Per5omet t.tanagement
' PM • AaM Maineenanot

• PP . Proauellon P~a~Wng ano
$.Jhs0rgMt... :~ •
' PS • PtoiOCt S\'SI«ll

VBRK.COM ,J•
.. SO · S<*!SancJDiSirlbUtion VBUK_COM ."J•
• RwSie(<l)
• VM.ltt~IP (1) TVFKffi e

BllllngDoc.... :J• MtKT ffi •
· $().81l--
- """Y(2) KNA1. COM .' J•
J ........COCI(
Wt£·'·"'-·§: TVTW ffi e
• Reuse(12) TVrNT ffi •
. ~a~(2)
• SD.aiL-cA • AcccuAt k ADRC ffi e

' SQ.elt,..()l! . Basic ru PA0001 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 i-
ent as the first column of the view output.
11
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
<J ·;) Pak ..
(otumns(l.&) jv.ew Prop~rtiu Ht~rarchtts Paramettrs.Nanablu
G~~r~
(ll)
Join v..cc..
- ~ v_cc
8
Unfon
.
· o· - .......,
r
~
.ill
Proj-t<tion
o'
Aggregn...
·I
j;J
R.ll'll.
=
Figure 7 SQL Engine Execution
» You should not modify SAP delivered views; instead, use the SAP deliv-
ered view as a template andl create a custom view with your enhance-
ments.
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 speci-
fied 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 I 2
» 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 Building SAP HANA Live Views

SAP HANA Live provides prebuilt models to help you use the functional-
ity quickly and easily by directly consuming the virtual data model in SAP
BusinessObjects BI tools; this gives the business user the flexibility to con-
sume 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
In this section, we will create a model view for the creation of daily pro-
duction 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 produc-
tion 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
----+ Field Data Capture
Network
Production Allocation
~
Daily Reporting
Fi gure 9 Upstream Oil and Gas Production Allocation
Figure 10 shows the production allocation data model. The model con-
sists 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
-
Specific Frontend Adaptations: Gen erated to
make a view consumable by J'eports OJ' analytical
applications (e.g .• currency conversion. input 0 I Volume Query I
vAriables, t&Jd joins. user-specific calculations,
SAP Que()' Views - or data type conversions)
I I
I Incl . Value Help Views I
SAP Reuse Views
-
Semantic Integration: Enhanced with key
business logic (e.g .. caltulated fields. j oins of
related obj ~ts. or constant filters)
Syntactic Integration: (Selection of fields that

- e I
I
Te<:hnlcal loss
Weii_Data
Volume_Oata
I
I
might be relevant for business reporting , basic
SAP Ptivate Views - calculatio ns, o r joins (only where needed, i.e.,
for maj or OLTP tables)
Physical SAP Tables
o f SAP Business Suite App lications -
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 data-
base 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 applica-
tion.
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 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
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 ,..l ot tl Ho<t..., ,_,..~,
1B Oen'lo(ofi, C'nl ~l'i1tol}'
llmI Ust4~ ._. ..::"·~=~.---';'~;::::c:,_=_:::------'-f::J Job t't!N I sri(""

Dt$<'fl'IIOII ()~--
_,._.._'"_"
"' _"'_______, £ .!1
' ---------' .!.l
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
Building SAP HANA Live Views J 2
tmp.OemoContent::Y_CCC_WELL VSA
" Z••X :t! + • li-t &

. . . ... (I)
T Y.CC..Wtu,.DETAJlS
I ON_NO: r_cc_;•.nt_DfTAU-0 ...
1 ON_NO_t: .,.._ cc_wr~~-orrA.tS
....
<lD w MAKOT
e oH.,.NO
e w l_NO
ClttM
Delivery network..._
Weii Onv11ber
I WC.._NO: .CC.Mh_OG'A .s.···
I MATNR: Y_(c_,•lfti._OE:r'AQ.S.~
8 e wc_NO wco:n Co•pkt.ion Nt.L- I CT_HO: V_CC'. WHLOEiA'LS.(f
l
Union
e MAn flt Mlterial Nu •~ I SA_OT: ycc Mtt.D£7.A1!S.~
.......
.:1 e o _oo
e s.a...o1
C.ontr~t ,._,mber
s~~te
I owH,.IHT. 1YJ>t..a>. r.cc..wu
owH,.ISQ..NO: r.cc_.-.m..oo
••
Aggr...
wO\'YN_NO PAAowntf
e OWNJ NT_fYP(JDP.r..,..,.t lntelt>t t -
OlliG. MP. HO: Y CC MH 0(7 "'
>
....
,g 610WNJSQ.NO
e ORtG.MP. NO
• r lt:NSP_NO
w FRI:Q.CO
0wnt'l' ~~er~t Seq...
O.ic}INI •u•:uure•-
Tr.,'fO'IHno.tmbfor
fltquttK)' ."'-""'
w AC1'l.VOt.U Actu.- \lolumt UnrtJ
1 ~~:
Value
AC fl. VOl Artua \!olumt
HEAT_V.U._U Mn~t~gVl<~tU'I•t
w HEAT. V.U tu'tlngvtlt.e
ACTL.EXER.GV.U Attua Ent,gyU"tt Filter
ACTL. EN"EilGY At:Na f<'~t19'1 L.tn~h 10
WG.OVRD.PC ~>t G'' Ov.m<t• Pn Scale
HITt...CT. VOl ff'trtled Co.~tn<! Vo
~.o.!·'~'-':1'·"'' ""' ''""'~·•<•

'""" -
1' (!) '0 • 0 ~ Tom... ts .. - 0
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 vir-
tual data model view and is automatically derived from the applica-
tion component. For example, if a view contains information about
the controlling domain, then it will be assigned to CO - CONTROL-
LING.
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
Building SAP HANA Live Views 2
LJ Properties !::! "tg Neighbor
'
Gen era I
~ Note: Changes are Saved Directly!
Global Field Names Category Unassigned d
VOM Properties Requested by' NGMAN' t o be <et t o ' Private' (Status 'new'). The approver is " ... J
Apphcatoon Component Unassigned [J
l 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 cat-
egory from the dropdown menu (Figure 14). Once you click on the FIN-
ISH 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 '.1 ·-
C..tout
•• s i $ • li• St
., _ (I)
D ON_IIo. •. CC_Wf(Ul!TAUD •
Cll>
0 ON~N0_1 ~ I'_CC_t•.tu_OfTA lS:
,.;. ~ 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:
·-
f4•fi';C:
o~-. T)'IM
,..,..
fllttt
......
TRNSP..NO
H'IAACHAit
10
""'
: Neoghbor
Not ~ Changfl owe Swed Directf)'!
'
C.fltgOI)' ~ned ·-
Globf,1 f iddN.mu
YOM Propcrtin APfl, ution Component Unassigned
l trminoiOgy Orom.»in lMMsiginH
Fi gure 14 Select ing the Private View in SAP HANA
18
lmp.De moCOnle ni ..Y_CCC_W Ell VSA
.,._ ..
I ·.i ·-
'"tWtANGMAN".Y_«._Wtu_0£TAII.S
n oN.. Y_cc ..iUO!TA ~so ...
HC).
w~:n un, ~ ON..H0.. 1: ~".CC..>'.'Ell.. OtTA..lS

J Se•anCiu
. DIN..NO ~''1..-:IJ'IICIWOi k -
~ WC..NO: Y r-r- lifa Dfi.A'l.S ,•,
I-
!-
' PTOftC:I~
ttWl,.NO
8 W(..NO
Wf'll>t10•b"
WdiC-ompkticlnt-.k&..
D MATNR: Y..cc_ ..ru:_DC7A s ...
n CT.. CC.O'l!..L..DVA3C1
HC). ' ..
-=-v_ee_~
e MATNIR t..._loi•l Nu•lkf ~ SA.,.OT: CC ,'If J Df1A. '>.SA
*Cf..NO (en1rKI ......bfof n OWN_IHT_TYP(_CO: Y_CC_.~t~
~SA..DT
wOWN.NO
Solk$&ote
I'AAc..,. r•!!
n OWN)SQ._HO: Y..CC.. l'.:.(_Di'
C OR.IG_MtJ_NO: ' ,..., NrU OCT. .,
..0WN_INT..T"''ft_(0P¥""'¥ltlnt~~ct -
>
..O'WNJSQ...NO Own.er lnte1e't Seq._
4fOIRIG.,MP..NO Ork)m~ •f'•U.Iff'111-
Vl llN$PJ.:> r,.,..tp«,~ nu"'bft
., fR!Q..CO I C:'~"'c t</
wACTI..,.\IOI..,.U
wACTI..,.\101.
w HtAT..VAJ..U
A-nal Vc o--r• UM.
AtW41'>etu!T.c-
''''"~:JV~I:." lf'l,t
:::r
l
HlAT..VAl t-•l'•"~J"' <a oa.. t)'pe:
• ACTI.,.ENtltGY..U Act~.~~l {rc g•,-Ur t fllttl
,).;.t~,~lfno!'~) 10
ACTLJ:mR.GY
'"'~~'"
\vG..OYRO..PC
ENTl._CT_YOL
· tt c,l, lNtPICiot J!.,
E •Wtd Ccr ~· <t I
x••
~-E~l-C.T..\'~)l A ·~H ·d C
1X>% c • ;J :J C!o€
'
VOM Propertin Requested by 'NARAHGMAN' tlO be Sod to 'Prfo.o~t e' (St«\11 •neW). The tpp!O\'tf is " -
4pplout101'1 ( ompol'ltnt t/AHsltned G)
13 Consolt tl
Tt~minoJogyOomtWI ~Md 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
QUANTITY (ACTL_VOL_U), and other required parameters. The newly cre-
ated private view will now be consumed by the reuse views.
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 well-
structured and comprehensive way. Reuse views should not be directly
consumed by the analytic tools and are created to work for multiple ana-
lytical scenarios. Some of the general guidelines for reuse views are as fol-
lows:
19
» 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. . " 0,~ PtOW$1ont'lg

r•e¥56 -M
0 • AI'I~,_~fC ··•
ll Proc..,c... s& E~~;~OI'I
+ ~OJIOnlablor
'0 MastCO{If
...... O "'*'•<Sale
0 AC!M'!e
£ ·I o Reoevor
..:l .!.J__ __ _ J
- "
~ , ~ '0' ... 0 Job log $3 tJ I . I.Pi x 0 ~ "
Sclt<ttlt 1B D~mo<:o ntMt ~~ostol)'l
_J~ '"l':m. ::J

fluMbff ol Uu."":
I v.ew I -=
" "::..:Tu::"'' ----'1-"'"""l
tcm
::...._---"
1u,w,_ ! ""'="""="•:::..
. - - -'-' •__
...... - OtmOConlltnt -
~;.::~~:. OcmoCorotcnt .:!) f f
~"~-----~~~ ~·---------' --------

1
I Oo
Figure 16 Creating the Reuse View in SAP HANA Live
20
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 ilt d6 ~ o - ~ · e. - .; •, · «"
3
!P
1
' J;,:
.1... . "--.....8' ..
. ...
.. '"'"
Sl>ow.AI
"
.,.,_
8
X
l yl)t ... "'""
[J HU11ngVa-.11 """
Hutong'lalut
A9911f9M.c>n v......
"
~jt.• [J lnttWUnill fntl~
....••. [J
0
AttutNdurne
&lt~111Y
Aclwi'/OMY!~
(ntilll~(f'oO'ty ''"'
''"'
....
il d <J»JoiiU $0
Y_O::_,f.U,()CATS)
Jv_c:::e_v.e..L
[J
a:::J
[J
VoiRed'ucnUtul
Wt1Complet10r1
Wtll
Vclttck.lclll.kVt
WdiC:OfTipk¢10n
Wtll •
[J WttG•~ct \\'ttGnO...tmcttP<1
[J Entitkdt:nv,«eceuc.n fnlitl<d[ng)~edlKn
0 ActwEntr~dv<n A<tu•t(n(lgyltc:ducn
0 AautNciR.t.ducft A.(tu•IVoiP.•ducl'l
[J (nt<dfcNoiRtcho~cn (nh!l.cf'loiRotducll
0 Adjus.ltdEI'IUitdVOI Ad)VSttd£ntflkocNct
0 A~tcd£t«tc:d£ft9Y Ad~tc:d(t Adjwt«<ltit~OI I
Figure 17 SAP HANA Live: Reuse View
3. Since we are creating a reuse view, then we will select the REUSE cate-
gory 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
tmp.DomoContont::Y _CC_WELL_ALLOCATION VSA

x~rwrio W.bf ~
4 ·=- ... Columnst)6) Y•tw Pt-optrt.-s Hltr.c.l'lltS Pl t¥flttMIV¥'*'" L

~ -- C)
(!!) '"'~
Jon
•
Union
- c
VtNI:IIt Sci'IWI'ItoC l ypt Lfbtl Cohtmn Mi "'
.. ------------------------~~~. . 0
Hc.1e: {Nnge-5 •re s.-d Ditertlyl
'"''tftC KslOtY
.I. I IC
ClttgOfY UnHJigii«S -
Job Typt
VOM Pf~'tiet ~iutiOt\(O~ U~ - ""'
Ttf!nin~Oo~n VNS~
Figure 18 Selecting the Reuse View in SAP HANA live
tmp.OemoContent::Y _CC_W ELL_ALLOCATION VSA I! ~ O O · It • F' Iii1t · ~ •, • «'

0
'i1
Columns(J6) VitwPropcrtteS Hitr¥ thtei P•rM~tttn/V.n.blts
'"'"
,_ .. ,....
_,
t~ l «y ~mt ........
0 Ht.l'tlngVIIUt Muttn.gV• k.lt
0 ftloH'f)4Uf..l f ntrgyUn!t
0 Anwft/OII.II'M A<t,..Wo...,.t Sum
0 ltltiUcdtntrgy (l'lti41<d(~ty Sum
8 <Il>Joln_1 ~n 0
•
VoiRtd'u cnUnll VciU:~
- v_et:._lld.J./:JCATtJ:J. a:::J Wt iiComplttiotl w...Comjiii«IOI'I
>r..cce_Y.fll 0 Wd
0 WttGn.Ov.,ricte9ct WetGuOYtrridePd
0 £ndtlc«~uc" (ntitled£"9)-fttducn
0 Ac:t\l~Ener9)'tttdu<fl A<tvti(I\.0'9"JRedu<.l'l
0 ActuaNdR.fllucn A<tueiVoiReducn
0 lllttdt<NoiRtcl\ltn Enb41tdVoiRtdv<n
0 ACIMttdE,.._~ItdVol Adjusttd(t~tidtd'Jcl
0 A~tc<IEI'Cll~ 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 busi-
ness 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 applica-
tions 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
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
... ·I
$ 8l~\tvdto_ W hck~- t:;. Con'lg~e IIT'CICI'I 8eNef
g tilpubli<
"'' ...
&. d s.tp·;~mpl•t:
-.. . .--d CIJI••
¥
An1obUII't'lo...,_
AnllytltVotw~· rJ DM• P101Hi0Mg
t9 1-W~
<; # t:fltcm-Nul
""'"'
Autol>oc.~
" AA~Pmlltgot-
&:;,11'1'-t"OI'I
® II l H\,.LOJod.0• 0 AUNltt ti Pr.ctot.Mt- ~ &pot!

$ &t VGTCC(J AOl 0 Rtlttplo<y • O«llotOI'If~
~ Man COPY
(i) .iii S.<utC)' fdit
)( D"'t< ......
RtmoYtfllt"
3- f41:tt0tftc·u•..
p ..
Rtb<too
... ~ O ReG~
..!..I r AI.IOOOCIMY!tf'll&lion
.:.J • I ~
tl 1·"0. ·' I X ~ ~ c
Scl«tcd: ill OemoCont«\t
~ ProP!'tr (V41ut I Ui.-f
~ Ibm, O~o,.t'flt
1 ~~~~~~-=_:_~~_·_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
tmp.OomoConteni::Y _CC_VOLU ME VSA
"' X ..,.,. % , 0> •

A
. O<wntf Ow"" • • Columns
610tw!'Wf'l ~ermT,. 0wJ-In1Hf'dl•pN> ! Wl_t.O: ,._,..._v.,u_ALLOCA •· 1'14_ -..o
•aownerl nter~qutMe Ow~lnttte:tt~ = OH_N<>. Y_(':_V.1U_AU0CA"JJ'•·C'l_N0
• Alloc.-lotlfrlt(!Ufncy Alloc:•tioof•~r m YK_NQ; Y_CC_l'tfLL.I1iLLOCA~. NC_NO
6/0flgkwltingMe-..rtmeMPt Owigifwlingt·~•'"'~... e ON:_NO_t: r_CC.. •'•UVUOCA~.,I¥_ <\t
•tr~~ T1.n,pcwt"' e CTJt(); Y.CC_Wf •.-'HOCAOO.'J-C'T.NO
• 'VII:IUtMtJnil Yo;d•f•...Jnil t ~DT: YCC_>'I!4L.Al!~T(;USA_OT
illoi HieMing~nill Ut.ttingYAMit
~ OWN_IN l _fVPl_CD.: "· •• l"od'. AU.OCA
He•tii'IQVt t..lc:
~rqyllnit
H••l '. ,.
Ftw-1q•Uoit
e OWfUS<l_N(); Y CC.Wf .trl()CAT"CW.()I. "'
>
9Aot~OC! kh.1•1Yofio.!•c
&ldtlc:d&lc:t~ (t~lith:&l'lll:'l ln
~nUnit VoiAf'ciiKfiUnit
We~tion
Wd
WdG~n-idePct
Ylcl(o•pktion
Wo·l
\'ll'~Ovcni~cl
.......,.
No~
• &.Ol"'4lnf11le~n [n\itl(.d(ncnA~n
Act....,.&wr~clucn Atluo~FroMqrftf'<lurn o..t.T>l'"
~dutn Aclu.ll'lfoll:t'diJm f iltfl'
• £1ntitk-4VOiftcoOJtn (nliti«<V~ebn l tngtl\
Adfustt.tltitttciYol A4tKII"<II-ntii ...dV<lt
.,.Ar.d;ated&ttitkdEngJ l\4ntedlnti:tkdl"9'J ""'
""" • • :::l · i ~ 11Xl" -
Fi gure 21 Creating the Query View in SAP HANA Live
tmp.OomoContont::Y _CC_VOLU ME VSA
f'RAControtel
s..~~O•tc " ... Cok.wnn.5
<!I) Jse m~ toO-rtntcrm lypt" ""'""
OwnHinlt'lf'~tl,fW'
B W\) 0. 'I'_Cl..• WEll,.AUOCA1JON.I"i:_o\'O
g ON. NO: l'_Ct"_WW....aOC.UJO'•.ON_NO
Jon
a
Unloft
_--=t
. ....<tlo• J
'JI Orrn~:rtntcraUfll'olt: IK c
W AIIoc.C.iol!lfr~y
O..,.t>crlntctclt~qy..
Aao<.o liot'.f-f~~oc:r
'~i O rigiNtiftgMe-tmtntf't Oricjn•tingMN,Uit'-
G wc._Nel r_cc.vmL.ALLOCATION.wc.NO
6 Dt( N0_'1: '1'.CC.t.'o'ft._.A.LOCATJON.Do\I.II<C
I '' ~_O:_'h!U...,.AUO
• Tr.-portcr fr~•tcor 8 CT.NO: .,. CC, ','lr...AUOG1.1lON:CT.NO
~--
W VOI.Im~UNt v-..m!'Vnit G SA_DT: Y_CC_NEU_AUOCA;noJSA_OT
WHu ting'hiUM HNtin9V~t
B OWHJNIT_JYP(._(:[); I'.CC.WEU.ALLOCArJC.
••
...... H-u tinqV•'Iuco
... wrcMJM
H~o1r'4"' J
fnHfi'I'Onit
H OWN. IS<t.NO: .cc. .~'t L,.l lOC.AT'O" o. "'
....
];;)
1- w Aoctu.IVolume
EntiekdErl.trf'l
Vt)lltt,cll("f\VM
Mhul'lolu•e
[ntillt-df•ot!tC)f'
Vl)ltM:IU(I\II..WI
I
!
...,.._
<
Gcftutl
W~'ott \"ldK-ompktlon
Wei Wt<ll Ptopcrtf
WrtGIIIOvetricltP<t Wt'ttH,OV«-rriclePCI
EMOtte~Mfl rnti tll:-drncnRcdu«\ Nom•
Aoc~gyR~n Nlt..afW'r~Rt'dl•n o.tt T)'Pc
Ac~n Ati• ..WoiK~ ...H
Entlttt~du<n (nti t\r(IY.;Mirduln l"'9'h
AldjmtdEntltl.tdVol AdjoniHI'nlit~lf\IQI
~cdEntklitd&lgy Adjust.cdlntitkdln.q\
""'
'""' -
c;..,.,.,
G$ob.l f'.tdd Nfm~
YOM ,t~UH
Apptu!i&ft(Ofnpotlenl
---·
~ted by'NARAHGMAN' to be ~d. to '<luery' (St4hn 'new'). The • PPfOYU IS" -
On.HsigMd -·
Job Type: User
Fi gure 22 Selecting the Query View in SAP HANA Live
4 The query view is created as shown in Figure 23 .
25
tmp.Oomocontont .:Y _cc_ VOLUME VSA

Ovt..t
PRA(ontr.cl A X ..,. % , . •
Cal s..&ed>•t~ S61eo~D•tc- ---
"' ... Colutnni
t.! Owncr Owtlil!f
~ OWi'M'tlnt~redT)t» Qow,...,ffl1f'ff'ft IJfM"
I
W\..HO: ...._.. .;litU_AUOCAOO!O:.O'Ii._ 'fO
4W 0wncftt~tt:r~S~oti'ICC Owntrlntco:r t:t\.S(:qu,_ I OtU«); 1 l'"r_llt'Hl.A!tOC.CrJO!.:.Cn NO
lliJAAoutioftFr~I'IC)' Aloc.. tior.FI<'Qllt'lltf I W(.,Na Y_CC_W1H_AlLOCA1JOI".'.NC_NO
t~~ O rlgJNt~.wemeMPt Orlgin•tif141.,~•SUff'- g ON_HO_.,: ' ..cc.~·.lu...AuOCATIO\I o~¥_.._,
WTr~cr Tr.o118pcul~ I CT_NO: Y_CC).'If.u ..AUOCAiJON.CT..NO
1 SA...OT: y_cc_Mu.ALLOCA~~-or
'" WVotlmcUnlt V•••m..unll
...,._
PfOJt••
tl
w HutingV....Nt
Hu fnqV•'uc
w Erwr~nit
fl.....tin')V.aiUnit
H t n Nt o·
lnH~t
,'
g OWNJNT..TYPt..ro.- v-. ...... v.m.A.u.cx.:.u~t
I OWN_ISQ._HO: YCC_/,.f, ...... UOC'A10' o. ...
>
....
~
- wAc~
\II£Mitk d£Mrov
.-\\llltecLcnUnk
Ac:tu#lohJ•e
[,,titkJ(,oe;'JJ
Voltl"dtKnUni1
Gcnut l
• Wd!Compktion
W tt
WeiKGIIIplction
\'lf'll i ,,.,.,.,.
w w.tG.OVf'fridePrt
~ Erotitk~duc.n
\'lf't(loHOvNfillt<P(:t
(ntidcd[t"tq'~Rcducn I D•tt T)JIC
Ntmt
N.~rgyRe«Kn Acl•~rr,.Rf'duc"n
w lvttwNoiRcducn Act~H~Vo!RC'du(n f •lttt
Entitk~ducn (ntiiW<!Vollr'dutn
....... ~ftllfdVol A.cljoJ>If'dbotit.,.d\ltll
~cd&ltlt..... Adjl.Ktf'Ciiontldrdl.nq\·
100!< -
. 1. x '1;11'- c
........ Note: CNngft ..-e Swed Direct¥
( t(tg<lf)' U"'"slgMd ...
Gklb-.1Held ~nus
VDM f>ropeftiH ~ted by•NARANGMAN" to bcJd to '<Notry'('Stttus · ~·). Tht~•c' is·· -
~.: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 con-
tain 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
» The value help view should not contain measures, which are quantifi-
able 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 attri-
butes, 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
.., ~v;..,._ 8 O<tliPJIM$10nlf19
" r 'flf'MffH
u Alulytoc '"''''9'·-
QI PIO<tcluft-
• ~IIIOftf.blt
...... O 'htiOale
Rtf!IO'IItfllt~
0 AC""'IIIt
~roltttOt,cru-
~ O R:ecl~
"
ltcfl>(to<
~I NNJO~
j ., ~
t1 ! . l .. l • ""• o
I Typ.. ! u.«~ ...
' ..
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
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_ALLO-
CATION.
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
.,.,
'"""
,.,_
,,.
..
'Kf Nomt 1.411:1tl
0 Ht.tw~gV.eut Ht-'Mg'l•lue
0 f:nttg)'Uft.t fnttgyUnle
0 t.ct.....Wolll'ft.'lt Actu.r.'c""'-t
0 Entitltdlnttgy (lltitl(d[ntl'gy
3 (ID Join_1 aDO 0
•
Vol~ecfU<rtlkut Vo~uc.nUn.t
• -Y.O:,.ALL~'lln Dl Wti Com,lotclot<i W~ICOftlplcbotl
Jv.occ..- . 0 Wol Wt!ll

0 \'lttG-'~'ttl'i6tP<t Yl'ttGt SOvtnidtPC't
0 Udl~n (l'ltitfc<l[ng)ft.cdl.tctl
0 .Act~grRcdvcf'l Acho~..(M"9'.fRt6\Kt1
0 Artu.N'ollteducft Am,..CV~
0 EncJtlt'dVOIRtducn (tlbtffd'/otR.d"'"
0 AcJ)IIstdntc)td!IOI Alf;usttcJEI\Cltlt<fVol
0 Adjlntdrd:k«l'9f Adj..l~cd[t AdjusttdEI'Uit<Nol 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
-
"-· lS
Un•»ignocd v Erforcc pn,ttc .. ,C'W v•ml<~tJon
Priv.ttc
R<o.. -·
Qu"Y
V11ut Ht_lp _
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 I 3
Sct:nario GU ~
, .- - -
Oetalh: Output
~ ·:: ... ~
~ -·· co 4 .). Columns

~ WL_NO: Y_ CC_ ~'ELL_ALLOCAt'ON.Wt_NO
Cl!> D DN_N(), r. cc. wELL.ALlOCAr;o,o,:oN.NO
Jo'n
~ WC.,NO: Y,.CC.WE~L..ALLOCATION NC..NO
8
Union
.:.
Proj~..
a•
Aggr...
~
Ra.nlc
Vatu~
Figure 27 SAP HANA Live: Value Help View

·--
3 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. How-
ever, often the standard views are not able to fulfill all business require-
ments, 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 calcula-
tion 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
Extending SAP HANA Live Views 3
tmp.Oomoconteni:.Y _cc_VOLUME VSA

B4 S t Oet.h
4 ••• -· " X • "" x ' + "'
" • ColumM
~ Wl...HC>. ,._,.._v.:u_..w.OCA •· w~._ -..o
Cl!) 610rwnHI ~erti1T,.,. OwMf lnt~f~ (fl·~
Jon •Oownt rl nler~qutMe Ow~lnttt e:tt~ ~ OH. N<>. ,. r- v.tu._..t..UX:.4l'JO'•·C'I_,..'O
• A:Jioc:.-lotlfrlt(!Ufnty A.lloc:4tioofr~r ~ W<.NQ. Y_((_l'ffU_,i11L.I.OCA~.NC_f.IO
tiOf~Mti!Wrtlt'leMPl Or igifwtingt•\e•'uf~... ~ ON_HO_t: r_C\,_ .',fL4_AH0CATJO,'i"~"-'C
fWlr~~
W¥oUme\Jnil
Tt.tn~opcwt"'
YohfMI'UIIit
e Cl.JfO; Y.CC_','Jf••-'UOCAOOr'lC'TNO
C 9._01: v CC_ o•,f~, t_.A.H~ "t)IJ tA_OT
WHiu4ift9V. . nill Ut.ttingYAMi t
~ OWtf_IN l .TYPl._CO: "· , _ Vod'. AI.. :A
He•tii'IQVt ll.lc
&wrqot~Jnit
H••l ' ,.
f rw1q•Uoit
e OWtUS~N(); Y CC >'If A!l()CA~()I. "'
>
•A<~"' kh.1•1Yofio.!•c
&ldtlc:d&lc:r~ (fll;tlc&f'lll:'lln
¥o!Rif'Wc:nllnit VoiA<'ciiKfiUnit
w W dCorlllpktion Ylcl(o•pktion
Wd Wo·l
WetG.OWrridePct Wl'~Ovnfidoi'cl
w &.titlc4("9)'1tcdlitc:n £ntiU,d(ncnA~n
ActUolllll'ltr~ducn Atluo~l-roHq,ftNiutn
~durn Actu.ll'ltollt'dum
&.titlc~OoKn lnlitkdV. .h::-bn
~tdltltilttciYol A+Ktl"<ll-ntii ...<'IW!t
-~tdlmitkdEngJ ~tedlntilkdl"9'1'
""'
100% -
""" - " :::l - :! >8
Fi gure 28 SAP HANA Live Qu ery Vi ew
V PRAContract PRAContract
-.r S.anDat~ Satc-s.Oate
" Ow noer Owne r
~ OwnetlnterestType Owne-rlntere~t lfpe
" Ow nc.r-l ntc:restSc: q~ncc: OwncrlnlerestScqu...
titAio<a;t ionf requoency 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:: Actuo~IVolumc
w Ent htedEnergy Fntitlc:dfntrru
VoiR<GxnUnlt \'outeducnUnit
.. w.tiComplet..., We:IJ(omplction
Well w..n
WetG.OnrridcPct Wrt<aas0v<"rridt'Pct
£nt~tedEngyflc dutn [ntitlc:d(nq, Rcdue;n
ActuoiEnorgyR<Gxn Attu•rf:r...r9JRt>ch•tn
ActuoiVoiR<ducn A<tuo~lVoiRt'ducn
EntitlecfVoiReduc.n EntillwiVoiRt-du( rl
Adjustt dEnthtedVo4 Adjustrdfntit~Vol
Adjustc dEntltledEngy Adjustec!lintltted!ncn
Figure 29 Qu ery View Fields
3. Since the field is not exposed in the query view, copy the already exist-
ing 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, right-
click on the package name, and select PASTE (Figure 31).
31
[ itt fd~ View ,tiavigatt frojt<t Bun Window l:ftlp

[j · ·~ . • ~ <> . .
9,0 Sj<sttms l:l Ntw
- '
[01 · I liill il Optn
ffil NETWORK_OO
:m v_cc_wELL_A ~ Validate Ctri+Shift+V
ll!l V_CC_WELL_D Actwate ( ti1 +Sh•ft +A
~ ICP Triggers
Q Rtdtploy
~
GOP Vitws
~ .,!g ZZ.MDM
Revert To A<tove
~ Jg _svs_AFL q Data Preview
~ ~ _SYS_BI
~ ;;lli, _SYS_BIC ~ Vlhtrt·Ustd
~ r.~ _SYS_REPO .!) History
~ !g _SYS_TASK
t> G:P Provisioning )( Otlett and Act ivate
.. (.:7 Content
,. til Demo(ontent n
Auto Oocurnttltatio n
.. ~ Calculation Views Copy C t~ + C
.!] V CCC WELL Rtfactor

\Jv=cc_vot Utif '
:0 V_C(WELL_ALLOCATION
~ £B Modifitd_Vitws
~ !lf l>ublic =
~ £B REP
.:ii.
Figure 30 Copy Query View
f ile fdit View Mavigatt froj tct Bun Win dow !:!t ip
c:1 · (8 ' . • ~ <> . .

~ Sj<stoms l:l j~Ntw ' I
•a Tables Ntw
'
[!ll NE l' ~
Find C t~+F
fH' Y_C
fH' v_c f) Refresh F5
~ ~ Triggm
~ Auto Docum entation
~ ~ Vitws
~ i: lZ_MOM c Activate
~ ,.g _SYS_AFL Q Rtdtploy I
~ .g _SYS_Bl Edit
~ ;: _SYS_BIC )( Delete Delete
~ _.g _SVS_REPO
~ ~ _svs_TASK Remove Filter •
1> Q. Provision ing
.. @to Content
:w Filter Objects...
Paste Ct~+V
~ f9 Otmo( ont •
R~actor
£B Modifitd_V '
~ Sf public
~ £B REP
~ af sap
t> d. sap-templat es
Figure 31 Pasting a Copied Query View
32
Extending SAP HANA Live Views 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
OK Jl C•n<<l
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 Output
~ ". . - .. e ADJ_ENTl_CT_VOI. ADJ_ENTL_CT_VOL
.. ~ ENTL _CT_VOl ENTl_CT_VOL
Gr ... ., - ~ WG_OVRD _PC WG_OVRO_PC ·"' W I..Oi llllltlS ,..
<ID J somanti<o CIFREQ..CD
CIORIG_MP_NO
FREQ..CO
ORIG_MP_NO
~ ENTL_CT_ENER_U: .@
Join
1: • TRNSP_NO TRNSP_NO
w ENTL_CT_ENER: _(t
Umon
8 ,.OWNJNT_TYPE_CO OWN_INT TYPE ..CD ,.. ADJ_ENTL_CT_VOl:
"'OWNJSQ..NO OWN ISQ..NO - ENTL_CT_VOL_U: _
. .
1
\ill
Proje... ... ,.OWN_NO
"'WC_NO
OWN_NO
WC_NO
e ~'
... WG_OVRO_PC : _(<
- C:UTI rT Hi'\1 , • •
t
_
0~ " MATNR MATNR

.. sA_DT SA_OT
',- =
Aggr... Properties
w YEAR YEAR
w OESCRIP110N DESCRIPTION E~
Ranl. • w ACTL_Vot. ACTL ..VOL
'------,
Property Value
w ACTL_Vot._U ACTL ..VOL..U
w HEAT_VAL_U HEAT_VAL_U Name ACTL_ENERGV_U
• ..,HEAT_VAL.,l HEAT_VAL_l Data Typt NVARCHAR
• HEAT_VAl HEAT_VAl f•lttr
ACTL_ENERGY_U ACTL ..ENERGY U l ength l
~ m • - Scale
100% >.:\. <.!\ ;:j !3 ~ lOO% - ~ ,;j ~ Sl!! L __ _ _ _ _ ___J
I ~ Propert•es 0 Error log Job log t3 ~ 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
' !Mwlog I Max rows: 200 : .1..

LI] DirtlftCtvWes ~._,---------------------------'-.:...._-~---,
. ..0
JlJ All1tysis
1-. C'J ~ lOO r~ retrlcvtod · l se<. .Ul ms
Orig•nlbngMenuremtnt9t Tun$p0rtt l Volumdlnll Kc.et.!g\'a!UM Artu"fVolumc
0 f.u<\lte .,. Add filter
Hu tingValue EnergytJmt
Sott tnt11e .S.U set
Well
. .ll
« : : :: ::DC7 BCl an.m MBD c:: :: o::
cc :: :: :::: :: coe """""""'' Mel
Mel BCl
57.6
1,046.196 MBD 000000000000007
)II
c: :: : ::: :o1 """""""'' l•B

an.m •
_,
c: ::::
occom: oo:: :oe """""""''
2000000C01
Mel
Mel
BCl
BCl "·'
1. 8 1.048.913 MBD
MBD
cmomcomoe
occom :oo:: CC1 Mel BCl lUll an..,. MBD 000000000000007
~7
m. """""""'' Sl.Q67 037.696 MBD
...............
000000000000007
"""""""' '' Mel BC3
-
MBD
"""""""' l.S 1,04$..913
OOC«''XX(OU I h
Mel BC3
~ lOU 1.044.913 MBD
"""""""'
"""""""'''
Mel BC3 000000000000008
-7
~()()8 Mel BC3 lOU 1.04$.913 MBD (l(O()I)('(I()OOX()8
lOOO()c))6)1 M<:l SCl 11.2 lll.lll MSD
m.m MBD
«: :::c::: )(IC)C)000006 """""""'
"""""""' '' Mel
Mel
BC3
BC3
12.8
101.2 1,046.196 MBD
000000000000008
000000000000007
« :::cc:: :XKXl000006 101.2 MBD
«:::m: :'XX#.'/JIXI07
••••o•oll)•())0•••7
"""""""'
"""""""' '' Mel
Mel
Btl
Btl S7.6
Sl.Q67
1.04.913
m.m
037.696
MBD
MBD
000000000000008
:::cc:;OC((((()8
000000000000007
.
OOOO<Xc«m 0 (I) o ~ """""""'
"""""""'''
Mel
Mel
Btl
Btl 119.6 1.048.913 MBD 000000000000008
cc:mcc: cmc:oocc:me
"""""""'' Mel BCl
"·' 833.)33 MBD
MBD cmc:oocc:me
c::mc: oo ~(ICI(O<l08
oc:::c::ooc:,i::ooe """""""'' Mel BC3 110.4

101.2
1.()48.913
MBD
oc::m: oocc"i:: ooe """""""'' Mel BC3 1,046.196 000000000000007
"""""""'' Mel BCl 3<8 1.()46.196 MBD 000000000000007

> ·J
Fi gure 34 Activated Custom SAP HANA Live Query View
3.2 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 cre-
ating a new query view in your own namespace. This helps increase per-
formance 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 unneces-
sary 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
Ext ending SA P HANA Live Views 3
Eil ~ fdit Vi.w ~avi gat ~ froj~ct Bun ~nd ow !:!•lp
C'!l · @ . • ~ <> . .
~ S\'st<ms l:l
-
ttt · l !:.!! n
N.w
Open
'
:Ill NElWORK_OO
:m v_cc_wEll..A () Validate Ctri•Stuft +V
'Ill v_cc_vm t _o A<trvatt ( tri+Shrft+A
t> 1.3 Triggers
~
~ ~ :Z.Z_MOM
w llitws
" R•d•ploy
R•v••t To Act•v•
,:! _SYS_Afl
~
;g _svs_BI 4 Oita Prtvi(W
~
~ ;: _svs_mc ~ Whtrt· Ust<l

~ .,;: _SYS_REPO
~ History
~ ~ _SYS_TASK
e> D Provrsronmg )( Otlttt and Activate
4 Sir Content
4 f9 Demo( onttnt r Auto Docurntrltation
• W. Calctrlation ViMs Copy Ctri• C

.!'J v_ccc_wELL Rthctor
'] Y_CC_VOLUM '
:.J Y_CC_I'IEll_ALLOCATION
t> £B Modifitd_Vitws
~ mpubloc =
~ f2 REP
Figure 35 Copying the Query Vi ew
f ilt [ dit View ~avig att .erojtct Bun ~in dow !::!•lp
C'!l · (9
~
• ~ <> . . - ~
Ntw
?.o Systems ~ _ '
• Glr Tabl<s Ntw
1IIJ NET' '
1IIJ Y_C ~ Fir\d Ctd+F
1lll v_c t) Rdrtsh F5

~ Glr Trigg<rs ['I Auto Documentation
C> C.. Vitws
~ .!g zz._MOM 0 Activate

~ ,Jg _svs_AFL R•<l•ploy
~ .i!I _SYS_BI
~ ~ _SYS_BIC
"
)(
Edit
Dtltu Otlttt
~ -Jg _SYS_REPO
~ -!g _SYS_TASK Rtmovt Fitttr •
t> fd. Provisioning :it> filttr Objects...
• ~ Cont •llt Pant Ct~•V
t> e
OtmoCOllt •
Rtfactor
fB Modifi<d_V '
~ mpublic
~ fB REP
~ !If: sap
1> f1t..e sap·tun )latts
Figure 36 Pasting the Copied Query View
35
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
Join
<;how: c.AJ:I::..'- - -·'1
8
..
Umon
Projt...
Typt Kty
0
0
N11mt
MATtJR
ACn_VOL.
labtl
t.tATNR
ACn_VOL_U
hbtl (t>lurnn H1ddtfl
0
0
Valut htlp v .. ""
a• - ,<JI> Join_t (I)

0 ACll...VOl ACn yOL Sum 0
Aggr.M 0 DES<:RJPn.. DES<:RIPTIOtl 0
;j,J w<IDJOin_1 I •
0 FIS<:Al. VI •. VEAl< 0
R.1nk Jv _OC_\1\fl.l._ALLO 0 SA_OT_l SA_DT 0
t 0 ACllJ fiiE ~. ACn . ENERGV,_ 0
- <lD Join_1
1
<J)
0 HEAT...VAl HtAT...VAl Sum 0
0 HEAT_VAl_t HEAT_VAL_l Sum 0
w JR.OCCJ)COSTlfS 0 SA_OT SA_DT 0
..; R_OCC.)RCIOOS.
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
n
, r,-LL~~~-~~--~-~-------~
llWN NO OWN NO
~~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).
Ext ending SAP HANA Live Views 3
Modified_Viows::Y_CC. SALES_M_QUERY_VIEW ~ · <l!l l e[!3 1 ,Hi r· liH -t ~ ·

0tHpot
W nrv.~\...1.11::>\.fl.
•% , + • 1il+ 9 't
w ENTl. CT. VOl HITl.CT.vot
• wG.OVROJ'C IVG. OVRO_I'( ,. . . Columns
\ITRNSP.NO TRNSP NO ' MAUlR: •.
t.JOWN_NO OWN_NO ' ACTL. VOL. U: .'
00 OWNJSQ_IIO OWNJSQ.JIO - ACfl,.VOl: :~ •.... ,. :~..
Union
8 tll OWN_~T.TYPE_<DOWNJNT_TYPf_CO
DESCRIPTION::;, •.... ::.
.. FR£Q_CO fREQ_CO
FJ.S(Al..VEAR: '•. •.... C..:
~
S ORIG_I.w>.)¥:) ORIG_,..,. NO
MA.TNR MATNR - Sfl..DT,..l: ' •.... :.:.. :'l·...
Prc>Jt...
tiSAJ>T SA. OT ' ACTL. ENERGY.U: ••• •
o• SlOWN_NO_l OWN_NO - HEAT VAL: '.:-. •. i"!t."' , ...
Aggr... w WC_NO WC_NO ~ ~ "~--
.g) wCIIlJoru e AC1l_VOl_U AC:TL_VOl_U
Jbnl.. .:Jv .OC.Y'oEU_AU.O. • •cn_vOt ACTL_VOt
Sl DESCRFTION DESCRIPTION
t e YEAR YEAR
- <lD ....._. <ll e SA.OT). SA. OT
e ACTL_ENERGY_U ACTL_ENERGY _u Nam t
• . IR_ccc_DCOSTTES •.
S HEAT.VAl HI:AI.VAl hbtl
I R_CCC_[)RCTCOS
S HEAT. VAl.l HEAT. VAl. l Typt Aggrc-guion
tiHEAT_VAl.U HEAT_VAt_U lnputsfl) Jo•l..l (Nodt)
tiENTL. CT.VOt. U ENTL.CT. VOt. U
tiENTL_CT_ENER ENTL_CT_ENER
Figure 38 Custom Query View Output
Modified_Views :Y_CC_SALES_M_QUERY_VIEW ~ • <1!1 1 oBIHIf' e. · l !t ~ •

~tn•ri~
~: ·-
~
lil• e• Del .lib
-ll'frv_~\..ut::lo'.rt ---- . . "' , + ·
,
Output
i!ll 8t
.... "
X
-- w ENTl..CT.VOl ENT\.CT.\/Ot
tiWG_OVRD_PC IVG OVRO I'( • . . Columns '
(Jl)
Join
. 1
Js.mlf'ltk• WTRNSP.J<O
4.110WN..NO
.. OWNJSQ,.NO
TRNSP.NO
OWN NO
OWNJSQ_NO -
'
'
MATNfl' ·-· "" ~'d
ACTL. VOL. U: ' • ..! ..
A( Tl_VOL: ':-· ·-·.. ._
E
.18~- .j
um~m
8 6IOWN..~T..TYPE..<DOWNJNT ..TYP£,J O ' DESCRIPTION: ._: ~E
S FREQ_CO fR£Q_CO
f iS<Al.YIAR: · ._:. iJl
~
Projt... ;.,:
" ORIG_,..,.)¥:)
MATNR
ORIG. MP.NO
MATNR
'' SA. DT..J: · •...: :tl_:--_.
•_:..
.
5 SA.OT SA_DT A( TlJNERGV.U:
a•
Aggr...
'=] <Jl) Join_l
W'<lDJcin_1
(I)
I
• owN. NO).
• we_NO
OWN.)¥:)
WC_NO
[l.~
j ' -
..
HEAT VAl
·~
• :;.reA-, ...
-
~
.
e ACTL. VOt.U ACTL..YOl..U
Prop~• tie-s
b nl.. Jv _oc_v.et.L..AU.O. e ACTL_VOl ACTL_VOl
t •~
5 DESCRPTION OESCRI'TION
e n AR YEAR
.
Ptoptrty V• lut
-:I <II> Join_1 <ll S SA.OT.) SA.OT
e ACTL_ENERGY.U ACTL_ENERGV. U Namt Aggttga\IOn
JR.OCCJ>COSTTES .. tiHEAT_VAl HEAT_VAt hbtl
...., R..OCC~TCOS 5 HEAT. VAl). HEAT. VAl). Typ< Aggregatioo
tiHEAT. VAl.U HEAT. VAL_U lnputsl ll Jo•1..2: INodtl
tiENTL.CT_VOt_U ENTI_CT_VOl_U
S ENTL. CT.ENER ENTL CT ENER
.
tOO'.O <.:\ 1.!\ ;:j !..:! ~ sr-• - @ '!! ;j :..:i 1::: ~
Figure 39 Custom Query View Data
37
Extending SAP HANA Live Views J 3
3-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 net-
work; 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 there-
fore, 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 AR~(73~
RC~H~ ) ~D=
EF~
A~U L~T-.~~
~.-
. ---------------A--
''Dl_IIO'' NVARCHAR( 20) DEFAULT ' ' r
''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' ,I
..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" . -
..HL_IIO.. ,
Fi gure 40 Custom Tab le

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).
DemoContent::Y _CC_DOWNTIM E ~ · d\\ I O O · I~ · I rr e. · l ~ ~ -

Sum~r'io ®• e' Oet.1il$ Output
--'"
q ·..-... 5 DL_NO ~I ·+ H ·:1 "I.... ·Ie. e•
d ...
<ll> ] Se.-;.o
~ NW_NO
5 MATNR
~.NO
j 8 ~ C olumns
I Dl_NO: _((_~· ...
-~
Jom 5 SA, DT Add To Out put I NW. NO: :~. :::." .....
. l . ~ DATE I MATNR: _(.:_:·,.., T
8
Union
... {W
. ;:-}
... .
$ OWN,NO
tiOWNJNT_TYPE_<D
• DOWNTlME_TYPE
Propagm to Stomarrtrcs
$elect All Tables
~le ctAJI
I
I
I
SA_DT: _c.:_.:t.; ..
CT_NO: _((_:·v
DATE: . C ~- ~C ..
-
-
-
~
Proje... Joms
• OWN)SQ_NO
••
Ag9r...
I "'ORIG_MP,NO
w TRNSP..NO
Cc:sdc:ctAII
Propc-rtt~s
-• I
~optrties
"'FREQ._CD
~ w ACTl. YOL_U
Genttal)
Rank
.. ACTl.YOL Proe!!!l J Value I
"'HEAT.VAL.U Name Projection
"'ENTl.CT_VOl_U hbtl
"'ENTl.CT_ENER
w AOJ_ENTl_CT_ENER
ENTL_CT_ENER_U
- Type ProJtct1on
OIU_CRUSB\ _:::]
1-
l"lo0%1:\~ ;_j .,_,j :g 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
DemoContent::V_DOWNTIME_ALLOCATION
Sctn.ano Outp.rt
DI•OCOitttt:'I'.CC..WRt_Alloc;.ATJ:)H '"Zl_tcX.Y.cc_DOwtmME :z • ,.. z --4' + • 1!1+ 8 '
w EHT'L_Cf.£HEl.,.U 91Tl_Cl .ENEILU . tu.HO T
• w am...CT.fHEl 9lTI,.Cl.ENEl e ou«> .-. ;a. Columns
w fHTLCTJ •OLU 9lTLCT.VOLU w tlW..HO ~ AI>J~NTL.<T_ENER: · ' _!J
WAQI..(Hl\..CT,\Q AOI..OtTt..CT.vot e N.ATlfR
r ENIUUNER: • ••• ~
Jorn
8
- wfHTL,.CT. YOt
• .,.,'G..OII.OJ(
wrt.IQ_CO
EHTl.Cl.VOI.
'I!IG.OilD.K
fl(Q_CO
.......
wCTJ«)
e oATE
r ENIUI.VOl.V: • ' . :
r HI'AT.VAL.V: • "<". '
Umon
.1
• OD:i!..MPJI()
w TtHg_HO
OIIIG..M='.~
TIJfSP.NO
• oWN.NO
• o WH_lNT. TYPE.CO
r OlJ'IO: . cc. •
' ri: ""~·
Ormt.JHT.l"f'J(.C D <MWJNT.TYP(.CO ¥ 0 WHJSQJIO
PrOJt... Oo'iHJSQ..NO OMUSQ..NO ~ ORICi.MP.NO .......
a• " OW'N,.'IO
wWC.IOO
OWN.fCI
WC.Ml
VTAHSt. HO
w FOlQ..CD
Aggr... WMATHct UATMR • ACrl.'JCH. U
... s.t.._or SA..ar
~ ~ YfAl
WAC'Tl.'«H
WH£1\T.VAI..U
R.tnk DESCilP'ti)N OESCIIrmoti EHn_cr_vcn_u Property V•lue
ACTt..VOl ACTI,_VOl EHTl.CJ.IiHER Namt Jo•\..1
ACll...\'Ol.U ACTI..\'0\..U AOJ.Etm.CT.EN(R
t§AT. VAl,.U 1€1\.T V.QU
• fHTl,CT. tMCR..U hbtl
t«A.I'. VAU l<oloT.\I,,Ll OIU.CRUSER Typ< Join
~'I.VAl '-tAf.VA.l au.llld:ST.u&P
.t(:TL._ENUGY.U 1..01 Join Typt Inn«
Proptrt•ts 0 tnor log lob Log !3 . 1 .1 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
(:> ... ., OWN.)SQ..NO: .~. .. •
.. Ol..NO 01.)'10
• NW.,NO NW~NO - OWNJNT..TYPE..CD: .. ='
<ll> I ORIGJ.<P )'10 : .:
WMATNR MATNR
"'CTJ«J cr..NO ' FREQ_CD: -~-. - ! - i
8 -..CT_NO_l CT_NO_l - ACIL..VOL..U: .. ~ _ , .,.
Union wSA_OT SA..DT I ACTL. VOL. V).:
.;J t.IOATE OAT£
.,. J
- ACJL,.VOL: ..:
ProJt••• 8 0WN..NO OWN.NO
e oWN)SQ)'IO OWN_ISQ_NO
~~·
Aggt... _!OWNJNT_Tm_ro OWN INT TYPE CO
e ORIG ORIG tv'F NO
&J -.,. TRNSP_NO TRNSP_NO
Rank e FREQ.CO FREQ.CD P1op>trty
e ACTL..VOl.U ACTL YOI. _U
e ACTl.VOl ACTL. VOl N.amt ORIG MP NO
e ENTL.CT..VOl..U ENTL..CT..VOl..U o~t.a Typt trYARCHAR
e ENTl.CT.ENER ENTL_CT_FNFR Fil'ttf
e H:AT..VAL..U HEAT..VAL..U length 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
<lll
Jom lhow. c..:I
AI::...'_ _..J
· I
a
Union Typt Kty Namt Labtl AggrtgatH>n Vanablt
...
PrOJt ...
0
0
Dl ..NO
NW..NO
Dl,NO
tr.•.•_NO
o• 0 MAn~R MATrtR
Ag9r... 0 CT.NO CT_NO
(Y 0 CT.NO.l CT..NO.. l
Rank 0 SA.DT SA.OT
0 DATE DAlt
0 O'NN..NO OWN..NO
0 OWNJSQ..,.. OWNJSO_NO
0 OWNJNT.... OWNJNT_TV ...
ORIG_MP_... ORIG_MP_NO
:- _ 0
r:l. ~~·~"'--~'"_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 pro-
active 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 cus-
tom 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
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
-I:::~.:~: ::~.~- ~
4 ·.L . ...NW_NO
WMATNR.
. , ... <0
• cr_NO
aD _,SAJ>T
Join .. oAn
"'OWN..NO NW.NO: _t _;- •
<T ..NO: - ''· -~ ., "'
e,.,a.nd/CoUa.pst SAJ>T: _, ._: , •
OU.l!Puvif'W 00\VNT...E_TYPE: _( • •
""
Projt.-
o•
, ,-,
Aggr... Otstlt<tAII
~ ~ Auto·l a.yout
Rank !.w'lt<h to PrOJt<bon
( 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'<hies Pllr.ai"''W:tersN arillblts
loc~
aD
Join
8
Show: L:I
AI ----l
::...
I ·l " .. - wd.
Umon Type Kty Name hbd Aggregation Vari11ble label (ol\unn Hidckn Vah.a help Vflt'N/
l: 0 DL.f<IO DL_t<O 0
PrOJf'··· 0 MATNR MATNR 0
o• 0 tM'_NO NW_NO 0
Aggr... 0 CT..NO CT..NO 0
,y 0 SA. DT SA_DT 0
lhn~ 0 l>OWNTIM... OOW>ffiME_T•.. 0
0 OWN_INT_... OWN_INT_TY... 0
0 ACll..VOl ... ACTt..VOl..U 0
0 AClt.VOl AClt_VOL Sum 0
0 H~I\T_YAI -. H~AT_VA.I _V 0
0 HEAT.VAl. . . HEAT. VAl.U.l 0
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 View Mavigate froje·ct Run ~indow !:!:elp
['l ~ i(.J ·rs ~
~ ~ ¢r ~ ~
'I<> Sj<<ltm< l:l = 1:1 OtmoConttnt.·Y_OOW~
Ill'> I t:l! U · II:I ~ d ~ "'

t> fa. Synonyms . DemoContent::Y_CCC
Scenario
• fill. Tabl"
HlJ NElWORK_D
!Ill v_cc_oow~
Now •
'IIJ Y_((_I.'IEll Open
~ v_cc_wm_
0 Validate Ctr1+Shift•V ~
1> (?;. Triggers
Actrvate Ctd+Shrft•A
~ ;.;;; v;..,., r-'
~
~ : ZZ_MOM Co'> Redeploy
~ J _SYS_AFL Rtvtrt ToActl\'t cc
~ _SYS_BI !---,
~
~ ~ _svs_Bic ~ Data Preview
• J _svs_REPO
~ _$YS_TASK
~ \AJhert· Used
~
t> b Provisioning Jj History
~ liP Content X Delete and Activate
~ tB Oemo(ontent
~ ... Calc\rlation Vit'W f' Auto Documentation
'J v_ccc_oow Copy (t~ + (
.!] V CCC 'NELL
:F] v~cc_Oowr.
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, right-
click 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
~ SAP HANA Administration Console- o.mo<:ontent:Y_CCC_DOWNTIME_TY

f ilt fdit View ~avig1tt frojtct Bun ~indow l::ftfp
= El
~:· · [ New
New
:;::j
4 ;,. Catalog
~ lOr Publoo ii':<, Find (tri• F
Rtfrtsh FS
tl
~ "'ll svs ['J Auto Do<umtntauon
~ ,'l UPLO 0 Activate
~ J :zz_t Rtdtploy
~ ,C: ZZ..M
_svs_
~ .~g
" Edit
Dtlttt
~ ~ _svs_l X Otlttt
~ ~ _svs_l Remove Filter
~ ~ svs
~ J ~svs~ ~
1 Fi~tr Objt<t s...
e. Provosoo"J, Paste
~ liP Content· Rtfa<tor
~ ffi Modot
~ f!i. Smority I
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 MEA-
SURE buttons (Figure 50).
6. Save and activate the view by clicking on the icon shown in the green
rectangle in Figure 50.
44
Integrating SAP HANA Live Views with SAP Business Intell igence Solutions J 4
Modifitd_VItws::Y_CC_CUSTOM_DOWNTJME_QUERY
Sctnario
<1 ·::• Palt ...
(olumns{l.S) VitwProptrtits Hrtrar<hits PuamtttrVVariablu
l oul
<Jl)
Join
I Js.o=o.
't
rl
Sl>ow' ,__I
AI_I _ _ _,
•I - , a• o • • [!].- 'b
8
Union
• 0' - : - 91 ~,:P• ~8<)' N";NjlO
h btl
t-rn_NO 0
"' ()'NN_f..IO OWN_NO 0
o· Tl\IISP_NO TRI'ISP_NO 0
Aggrtgat... u o •m.vot... •cn_vol_u 0
;g) I 0 FREQ..CD FREQ..CD 0
Ranl. i 0 0WNJ5Q_... OWNJ~NO 0
R 0 O'I.'N_M"_. ~ OWN_INT_TY... 0
0 DOWN'TlM.. OOWNllME.T•.• 0
0 OWN.J'IT.... OWNJNT..lY... 0
0 ACTL.VOL... Affi.VOl.U 0
'
. 0
,..,__ ACn _VOL ACTl_VOL
.._.~ ... ,{}0. ' _ _ _ _ _ _ _ -.r:->
,._-'""-
0
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 cat-
egories:
» 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 pres-
ent in SAP HANA without any redundancy or latency and is best suited
for operational reporting. This approach, which simply involves integrat-
ing SAP HANA Live with the SAP BusinessObjects 81 toolset, is discussed
in Section 4.1. Ifyou require tactical and strategic reporting, SAP Business
45
Integrating SAP HANA Live Views with SAP Business Intell igence Solutions 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 sugges-
tion 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 Business-
Objects BI tools (SAP BusinessObjects Web Intelligence, SAP Business-
Objects 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 SAP Crystal SAP Crystal Reports

SAP Lumira
MS Office/ Reports Explorer Enterprise/
Desktop
Design Studio Enterprise Dashboards
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 allo-

cation. We will now explain how to expose the production allocation
Integrating SAP HANA Live Views with SAP Business Intell igence Solutions I 4
virtual data model to SAP BusinessObj ects Design Studio to showcase the
data in a visualization. Please note that, although we use SAP Business-
Objects 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 follow-

ing this path: START • CONTROL PANEL • ADMINISTRATIVE TOOLS • DATA
SOURCES (ODBC) • SYSTEM DSN (Figure 52).
~ OOBC Data Soor<e Administrator ~

u..,. ~!illJ SyttemDSN ~ DSN ~iveo
...!] To~ComeclionPool<>g_iAboutj_
System Oata Scuces:

Name OWer . I Add... I
~ IBMDB20DBCDRIVER·DB2VIOO 0
BACKLOGN IBM DB2 0DBC DRIVER · DB2V100
I Remove I
DB2DKERB IBM DB2 0DBC DRIVER · DB2V100 I Conlig<Me... I
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__:_
An OOBC System data $0ll'ce stOfes infOti'Mtrln abol.A how to connect to

U1 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
Integrat ing SAP HANA Live Views with SAP Business Intell igence Solut ions I 4
'i' OOBC Oata Source Administrator ~

u,., DSt!] System DSN FleDSN Drivel$ Tr~ Corneotial Poolin9 About
System Data Sruce<
Name Driver . II Add.., II

~ IBMDB2 0DBCDRMR · DB2V1~ 0
BACKJ.OGN IBM 0B2 OOBC DRMR · 0B2V1~
I Reroove I
DB20HRB IBM 0B200BCDRMR ·OB2V 1 ~ I Codigure... I
DB2DSP IBMDB2 0DBCDRMR · DB 2V1 ~
OB2EKERB IBM OB200BCORMR ·08 2'/1~
DB21KERB IBM 082 ODBC DRMR · D B2V1 ~
OB2Ml<.ERB IBM 082 OOBC DRMR · 082'11 ~
OB20KERB IBM OB200BCORMR ·OB2V1 ~
n•
"
-
An ODBC System data S:OUrce stores inforrnaOOn abol.A how to connect to
01 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 Com
l l!!\r:1'iTir:lil J 1.00.55.48833 SAP
SQ[Te<ver 6.01.7601.17514 Micr
SQLSe~verN ativeeiert10.0 2009.100.1617.00 Micr
<Back ~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).
Integrating SAP HANA Live Views with SAP Business Intelligence Solutions I 4
SAP HOB (1.00.li>.OO.l86119) X
~len
S<Mt...t Port
Server:Port
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 SYSTEM DATA SOURCES list
(Figure 58).
49
Integrating SAP HANA Live Views with SAP Business Intelligence Solutions 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<J ,.
HOB008C
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 Business-
Objects 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
Integrating SAP HANA Live Views with SAP Business Intelligence Solutions 4
2 Once SAP BusinessObjects Design Studio is open, then click on APPLI-

CATION • NEW to create a template for the report (Figure 60).
!f:!J>IIUtiOtl ptarWI•ng fdtt Larout St•(h !l,lfW Ioob t;ltlJ'

"HI . .., :o -· a·
c::o 0 I:J P109«rtltS tl
1y1~-tflfttl h>:t t'"'li-:-
N...,
- ...
- ..
, -,-
,. ,-----------.,Cil;---;:1:!,......, P•opt11y
~ AnJiyt•c Compontnh
Appllc.atlon
0 Bane Comi)Of'ltnu
( rutt ~n ~•s ~pl•<•bon
l ~ Contwltt Compontnu
~ Cunon\(ompontnu - -
~ Scn(OII'II'nl.lrllll}'6t<MS 1&-st . .l
~ Sen (ommunill:y Prototypts
\1\P. Prtn. H.t!...J wt. Rtport

g:; OWnt ci ~ 0
An Outhnt IS not IIYJIIJblt, SA.PJ>•tu.Ha•\l_lwt.ltt-port
I~ Ttmplltt Catt9~lc~><
::.:•':::'"':!C"'::::-="----------'
·I
[ J!><l
=
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
~pplication Pla,,ning fdit ).a.yout ~arc h ~tw Iools !:!.~lp
:
rH~ i ~ !!! IJ i '0 . ;.
c
-.-: Componenh t:3 008 0
typt fJit u u xt
1-
f!>. Analyti< Compontnts
(!:> BasK Compontnts
~ Containtr CompontnU
~ Custom Compontnts
e Xn (ommunrty GtoVI S
~ Sen Community Prototyp~s
-
~ Outlint ti '\... 338
..,. c
0
'YI•t hlttr ttxt
• li] SAP_Prtn.Hant~_L ivt_lt~po11
~ o ... ~ -
•
~ Pl•nn;~ ~ Add o... Sou«<...
Qt. L t~yout
~ Ttchn·
Add CurtomOiltll Sour<t> .
'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
Integrat ing SAP HANA Live Views with SAP Business Intell igence Solut ions 4
the virtual data models (Figure 62). The OLAP connection is created by
your SAP Basis team (Figure 62).
!J>pltutJon "'-*" (.tot L-n So-M(h ~· 10?1> Help

="' ..
n :;; ' <t. ID ' ~ 0 ·' ._, til t..
C· (0Wip~1 si ~ -i • 0 (i]'SAP.Pt~~.HN\I,JNt._R#I_.. i3
I '"' ~C-.-!ltl
.... B.I'IO<(OnopcHI«<U
• . (Ofttilnoro ~I'CJ
~- CUJtom~J
l L <il ...._
r)j'-""'
- "''•
_ c...c...• "'_"--, y l l ~ F<llclm l=.;
'- _ _ _ _ _ _ _ _ _ .4' S.:::•o::
••~----------,
~-- -... c'"'""'··~ Gnwot
~ ~~~C~PtO'~I"' , _._,, W_M....I ler--1 ~ w.:;;;~Ht'COf'
1~ Outllllt u
= • Conn.to<-1!1~t ~ N.Ia upt-e.1
l&r...tL.. I Qt. tymtn-loul · tt<~~k<ol
tvl)c nil:~• t tl(
O.ot• SoulctAiiu • OS_t (dd'I'Jit)
~ [I) SAP.frtti_HI~h·;c__R~on
Qt O.ota'j,oouoct't
a. Pt-.g ObJ«tf ..........
~ 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.
Production Allocation Reports !iili

USO, ive••ge lnOtlth •ate, .-tl'lol.oo
ACWI YIO 2014 ,,. • "' .

Not ~
r
,,
10
-- --
"
1 2)45071fl0t112 1 23 4 5678f 10H12 1 234$67ff10 11 11
• Ac;Jwl2014 Aclllll2015 Ttf9t12015 • Jdull2014 Aclual2015 Ttf911201S
Figure 63 Production Allocation Report
52
Integrat ing SAP HANA Live Views with SAP Business Intel ligence Soluti ons I 4
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 pres-
ent 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 hierarchy-
related 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 Stu-
dio (Figure 63), but instead, we will use SAP BusinessObjects Design Stu-
dio on top of SAP BW to create the report. When an SAP BW system is
53
Integrat ing SAP HANA Live Views with SAP Business Intell igence Solut ions 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 BEx Query I
+
Composite
I Master Data
Provider
I
Master Data Transactional Data
/
/ \
SAP HANA l ive
Calcu lation View
I SAP BW Schema
(Reuse layer)
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
,.-r"
f ilt
SAP HANA Modeler SAP H4NA Stud1o
f dit
~ Sl'•t•m• !:3
Navigate f_rojt<t B.\•n
NewWindow
Editor
H;d• Toolbar
r=
Window Htlp
<::> ~
lit ~ I E!l I 8 SAP HANA O<Vtlopm<nt

ftl, DEl (Sle Show v;.w > ~ SAP HANA Mod<ltr
------
Customize Ptrsptdtvt ... Othtf...
Sivt Ptrspt<tivt As ...
Rtstt Ptrspt<tivt...
Cion Ptrspt<tivt
Clost All Perspectives
Navigation
Prtftrtn<ts
Fi gure 65 Opening t he SAP HANA Modeler Perspective
8\V Modrhnq 5.AP HANA Studio i!1 X
E8 I ~ 9-P I-IAtiA Adnlii\IStrMJOn Contolot ~ SAP WANA Modtlt; (I) fffl Moddng
0 = 0
~ iO .•. ..
•;r:;~•••••••••••
6olnto
c.~ h i(
CtrhShdt•O
0
. . ;.,..
CJ f-oldtr
X Dtlttt Otktt ~ ew Qutry-
Ro:mo•~ fr m Contt<t trhAJt• !ft.-D m £J CompouttProYidff-
• Import... '::1 OptnOOSV1ew...
(JOPort...
G DattSt01ot ~ct (•dv.ti'Kcd),_
t} RtfrHh
{ lou Projt<t "
0 UnreltUd PrOJKb L9 0tlur...
V. .d11tt
ProfiltAJ
OtbugAs
Run A$
R«tort from Loc~ 1-MtOI)'··· tion .-.
~ Atu<h W HAI-.lA ~tm
Complllotwltl\
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
Integrat ing SAP HANA Live Views with SAP Business Intell igence Solut ions 4
1!1 Back End Favoritu

Iii 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
Op<n et Open ODS Vitw
l•lCAI ( ross-Applicat • .
fi)(RM) CustorntrRt e
GttWhtrt--Ustd l•st. ..
IOFS<f.f) Financial Su (I Refresh FS
{ 1lH( t.l} Human Reso . . . ; : : . - - - - - - - - - -1
!•1111(oUSTRIES) lnduSI i? Add to Favoril"

fY6TI.I XXJOQH) SR !r i? Add to Back End hvorilts
Figure 67 The SAP HANA Composite Provider
1. Enter the BW PROJECT, NAM.E, and DESCRIPTION for the Composite Pro-
vider as shown in Figure 68.
- I o 1..2LJ
M a ndatory Information
<D SV•cify obj•ct n•m•
BWProject• J OEl_LOO Browse ...
InfoAru:• Srowse...
r Add to Favorites
J PRODAllOCRE~
Description: J PROOALLOCREP
Copy From: Browse ...
Root Operation: r. Union r Lmtdoin r ltft OuttrJoin
<flack tj<Xt > 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.
Integrat ing SAP HANA Live Views with SAP Business Intelligence Solutions J 4
B Scenario: PRODALLOCREP C!i ~ · I X

!I ~
/ ® U1 \ 11 Sou<« Till get
\ ~ m Jy e Jy <±1 8
.G Print... -I Iii CD IU1J N••l•1))
Delett
., .
I
I
~ 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.
Graphicall Form ·Based l

Source T Target [T 1±1 8
• :!'J (SalesOrderltem) Reuse voew for sales order rtems n45•12) • <JI) (U1 I !O•O•llJ
~ Ia (!CharactuisticsJ Charactenst1CS (125•10) • Ia JGENERICJ Generated Group (0•0•10)
~ 12:> (IKeyfigures) Key f1gures (20•2) 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 (OUNIT) Bm Un1t (0•1)
• lao JiKeyFiguresJ Key F1gures (0•0•2)
jj )ONET_VALUE) Net Amount (0•1)
if (OOPENORDQTV) Ope11 Delivery Qty In Base Un1t (0•1)
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 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<y Frgures
(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

...,. '"" .....
E61. v-
· 0 ~ 8 .- l oht l!!l' I X Ill e <) jl ~ [ljl ll I:!' Q i'fm]'SI I,tl]..:. l 'bl l ~ ·
=.
.,
lnloProvider l~owsiColumns
:: !J f - ChclreK:4erUtiet
fi .-·i A.:IwiY0201• I Pl'opcr'li>es
~~... ~,($~ -"
a 0 Kerrogur~•
"'"-......., s f~~·Y
flNAiiCIA.LMOIHH
9- iij -
.......,....,_,
'9~ 1 ~ ·
a
,u. .
e o..n..Mw~.
' it Oifl'.oiMoOftt
G'
tt r~~
Aetu.IIY02015
Ttf901Yl02015 ................., ......, ,....... J"""'-1
Our.~ipllian
r~-·
• La ·
r u.~d t...,
recllniu!N..
~ A-• I
~lit:.eoJf".go..M
Pi cvicw
Actl.llf ~ ~ 'RO , ..O't: Y\0 1)1' ....
. "'ff~ l
.......wor """'........
t
• 'W.Jec.de'on 2 (
f8 \o/et~ 3
~ "'el~4
Wlti~S
.... .... (
( T
""' (....
WoT ( ....
~
J
"' f ilt:r fl lO'o'r\/Coh,lf'Ml I
Figure 72 BEx Query for Production Allocation Report
6. Now, start SAP BusinessObjects Design Studio from the START PRo-
GRAMS m enu as shown in Figure 73.
Integrat ing SAP HANA Live Views with SAP Business Intelligence Solutions 4
DJ VJord ltlB
• f X(tl 20l3
Ill Powt1P04tlt 20 U
~ Qu~l)' Du•gntr
(;SAP Logon
~ SlliPI)I09 TOOI
® SJ..ypt for &ts• l tsS lOlS
) f.lottpad
D SAP HANA 'Studto rtv~6
•.J Pamt
Fi gure 73 Start Programs Menu
7. Once SAP BusinessObjects Design Studio is open, click on APPLICATION ·

NEW to create a template for the report.
Afii>IICUIOon P!Jtl!WU) f~ Lavo~a Stardt

.;1 ~ ,._ ·a · ·
~~ Compont~lt1 11 !+ 9 • 0 - 0 ~-o
-
1111
~ AtiJiytl( COtl'lpontnu
AppliG:Iitio1t
l & s•<(ompot'lci'IU
I~ (ontMMW (ompontnu (Jtatt '" •n•IY'Iolt •pphc•t•on
~ (unon'l (ompont•nu
~ Sen (onwnu~ GtO¥it

e Sen (OI'I'In'IU~ Prototyptt
j SflP_PttU_H;oonJ_l~_Rtj.Ort
i O!Aklt l3 - 0
An outhnt ts not 11\'Jdablt. SAP_Plns_H•n•_l~Yt_Rtport
!:ltJC ) II f n•ush )I (al'l<tl
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
!i: SAP_Press_Hana_li'le_Report ~SAP BusinessObjec:t ~sig n Studio

~pli cati on Planning fdit l,.ayout ~a rch Y.i~ I ools !:!<lp
rH~ ~~ l!l a ~ :o .: . a:
•.:• ( ornpontnt:s I:l~ 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 l:fJ El ... ~

1:1
t}' l)~ 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
'a
(0
P;uu
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>plo<M>On PI~ (dol L-• ~a.dl y,.,. t ..e. ti•IJ>

r3 ~ .. . D ·o ·· ., ~-t
•.:.• (onoptonti'C.I tJ
e ~c~
~ 8oiOC(-'f'~
~ conu.." <~nt'
~ Cu$~Compot~mu
~ ~... c~Gc..o..
O S~"<~~o~y~
O•'*-u:• 1• -1
tvp~fllldlt•l
O•~Se..uAII~· OS.l ,.....,
• [il W J'•mJ4.,.•.J-Jt•poot
a. ~~(t~
&. flbniWigObJ«U
ll> t -
. QJ, Ttdw<• C~
~(OtntX'T_MEr~
]j
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? I 5
Production Allocation Reports :iili

USD. awnge month ••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 10 11 12
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-by-
step instructions and sample code, th is book wil l tea·ch you
how to build and design predictive, simulation, and optimiza-
tion 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 publi-
cations that you might also be interested in. Check out the next page to
learn more!
61
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 1 Bundle: $89.99
www.sap-press.com/3609
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
E-book: $69.99 I Print: $79.95 I Bundle: $89.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
E-book: $59.99 I Print: $69.95 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<umar works at HCL India and has seven years of experience
as an SAP consu ltant, trainer, and author. He is an SA P HANA-
certified technical consu ltant with experience in prod uct devel-
opment, implementation, and support. He specializes in SAP ABAP, SAP
HANA, and SAP Fiori. He is an active speaker and has organized multiple
barcamps in Delh i, India. Learn more about Akashat https://www.sap-
press.com/building-and-extending-sap-hana-live-views_4060/author/.

SAP E-Bites - Building and Extending SAP HANA Live Views PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SAP E-Bites - Building and Extending SAP HANA Live Views PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Akash Kumar

Building and Extending

Nowadays, the connected wor.ld generates a vast amount of data at a sig-

1 Introduction to Virtual Data Models 5

1 Introduction to Virtual Data Models

SAP HANA Live allows real-time operational analytics and is based on a

» Tier 1 consists of SAP HANA as the database system, application , and

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 Security History and Hierarchy

Broadcast and Predictive Analysis Cross-System Analytics

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

HTML5 -based (Web and Mobile)

Open Interfaces: HITPS, OData, SQL, MDX

• Custom-built Open Interface [Q Out of the Box Support

Fi gure 2 SAP HANA Live Architecture

1.2 Types of Virtual Data Models

Consuming App licat ion

SAP HANA Database \

SAP HANA Database Tables

Figure 3 SAP HANA Li ve Virtual Data Model Views

1.3 Viewing SAP HANA Live Virtual Data Models

® ifl: c~p ~ (Jpo1

Figure 5 SAP HANA Live Browser Credential Screen

• MM • Ma!enals MMagetneft BillingOoc... J•

' PM • AaM Maineenanot

' PS • PtoiOCt S\'SI«ll

• VM.ltt~IP (1) TVFKffi e

• SD.aiL-cA • AcccuAt k ADRC ffi e

Figure 6 SAP HANA Live Browser

1.4 Basic Virtual Data Modeling Rules

Figure 7 SQL Engine Execution

1.5 Basic Virtual Data Modeling Terms

2 Building SAP HANA Live Views

SAP Query V iews

Incl. Value Help Views I

SAP Private Views

Physical SAP Tables

SAP HANA Live VDM

Figure 8 SAP HANA Live Virtual Data Model

Fi gure 9 Upstream Oil and Gas Production Allocation

Syntactic Integration: (Selection of fields that

Fi gure 10 Explanation of Virtual Data Model Scenario

2.1 Private Views

" c; ... - c ,..l ot tl Ho<t..., ,_,..~,

1B Oen'lo(ofi, C'nl ~l'i1tol}'

llmI Ust4~ ._. ..::"·~=~.---';'~;::::c:,_=_:::------'-f::J Job t't!N I sri(""

Figure 11 Opening the Calculation View in SAP HANA

" Z••X :t! + • li-t &

~.o.!·'~'-':1'·"'' ""' ''""'~·•<•

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

LJ Properties !::! "tg Neighbor

l Term1nology Domain Unassigned

Person Respons1ble unass;gned Ass1 n t o Me Q

Figure 13 SAP HANA Live: VDM Properties

l trminoiOgy Orom.»in lMMsiginH

Fi gure 14 Select ing the Private View in SAP HANA

lmp.De moCOnle ni ..Y_CCC_W Ell VSA

w~:n un, ~ ON..H0.. 1: ~".CC..>'.'Ell.. OtTA..lS

Figure 15 SAP HANA Live: Private Virtual Data Model View