Cds View Performance

Download as pdf or txt
Download as pdf or txt
You are on page 1of 8

CDS Views

Performance
improvement
Annotations
for CDS View
Performance
Anubhav Oberoy
www.anubhavtrainings.com
CDS Performance
Annotations
Learn from Standard
CDS Performance Annotations
There are three categories of characteristics which have to be assigned the annotations usageType for the domain
@ObjectModel.

These are:
@ObjectModel.usageType.serviceQuality - #A,#B, #C, #D, #X, #P
@ObjectModel.usageType.sizeCategory - #S, #M, #L, #XL, #XXL
@ObjectModel.usageType.dataClass - #TRANSACTIONAL, #MASTER, #ORGANIZATIONAL, #CUSTOMIZING, #META, #MIXED
serviceQuality - expected performance of the CDS view

A > B > C > D – KPI Quality


X – no KPI but certain Test Cases demanded
P – reserved for Hierarchy CDS only
sizeCategory

this classification is that the size of the involved tables has a significant impact on the resource
consumption within HANA
expected number of rows is < 1.000 S
expected number of rows is < 100.000 M
expected number of rows is < 10.000.000 L
expected number of rows is < 100.000.000 XL
expected number of rows is >= 100.000.000 XXL
dataClass
To support the decision on cache strategies for higher layers
The view contains data which is written or changed in high volume transactions (also for background TRANSACTIONAL
processing). Examples are header and items for Sales Order processing or Financial Postings.

Master data is read but not written or changed in high volume transactions (also for background MASTER
processing). It typically drives the business process decisions when business logic is executed. It is also
shown to the user as context information and to enable user decisions when these transactions are
executed manually. Examples are material, business partner or account.
The data describes the organizational structure of a company and its business processes. It can be seen as ORGANIZATIONAL
a special type of master data. This data is only written or changed when organization changes are
implemented at the customer. Examples are sales unit, distribution channel and cost center.

The data describes how a concrete business process is executed at the customer. It consists typically of CUSTOMIZING
content delivered by SAP enriched and extended by the customer. This data is typically even less common
changed. Examples are countries, unit of measures, currency.
Meta data specifies how the system is configured or describes the technical structure of entities. Typically META
this is part of shipped content. Changes are done in fixes or upgrades. Examples are DDIC structures, field
control, authorization objects.
This label shall be chosen if the CDS view contains data of several of the above data classes MIXED
What can you expect?

KPI 2: SELECT
KPI 1: SELECT SINGLE *
Aggregates on
service Number of Contains SINGLE (1stkeyfld) FROM
Where to be used? size Category data Class huge number of Buffering
Quality Tables Functions FROM cdsview cdsview
table rows
WHERE fullkey WHERE
fullkey

within business logic for high


TRANSACTIONAL, MASTER, CUSTOMIZING,
A volume transactions or background S – XXL ≤3 no no yes, all <1ms <2ms
ORGANIZATIONAL, META but not MIXED
processing

within business logic for


TRANSACTIONAL, MASTER, CUSTOMIZING, partial
B transactions or background S – XXL ≤5 no no < 2ms < 5ms
ORGANIZATIONAL, META but not MIXED yes
processing

from the UI in transactions for


C S – XXL MIXED expected ≤ 15 can no can < 10ms < 20ms
single object retrieval

D for analytical reporting XL-XXL expected MIXED expected ≤ 100 can can can < 500ms

is built to push down application


X XL-XXL expected MIXED expected ≤ 15 can can can < 500ms
code to HANA

only to structure the SQL View


P model; CDS view may not be Hierarchy CDS MIXED expected ≤5 can can can
consumed outside view hierarchy
Anubhavtrainings.com (91) 84484 54549 [email protected]

Thank You
Click on Subscribe button for more free videos

You might also like