Database independent code to data

Question 1

Name the 3 parts of SQL

Answer 1

DML - Data manipulation
DDL - Data definition
DCL - Data Control

Question 2

What parts of SQL does Open SQL cover?

Answer 2

A small part of DML.

Question 3

What part of SQL is handled in SAP by the data dictionary

Answer 3

Only a small part of DDL

Question 4

How much of DCL is implemented in SAP prior to NW 7.4 sp05?

Answer 4

Almost nothing. The DCL would normally be used for user control but in SAP the database only knows one user

Question 5

What is the single database user of an SAP system

Answer 5

The user is SAP{sid} or SAPR3. All data is stored in this accounts schema

Question 6

What are two examples of differences in new Open SQL

Answer 6

Fields must be comma separated, Host variables must be used

Question 7

In new Open SQL mathematical operations are available on all operand types?

Answer 7

False, there are many limitations. For example, MOD is only allowed on types I and P without decimals. I believe AVG must always be cast to type F

Question 8

The CDS consist of what three things?

Answer 8

DDL
QL (from the ABAP code)
DCL

Question 9

In comparison to ABAP DICTIONARY views, what additional functions do CDS views

Answer 9

Outer joins and unions are supported
Calculation expressions, aggregations, and groupings are supported
Nested views are supported

Question 10

From least to most advanced, list the ways views can be created

Answer 10

SE11
CDS
SQL92
HANA Column views

Question 11

CDS views support all facets of SQL92 and HANA specific features?

Answer 11

That’s a big “NO” on both accounts

Question 12

What is the path in eclipse to create a CDS

Answer 12

From the ABAP project

New->Other ABAP object->Dictionary->Data Definition

Question 13

It is not possible to see the CDS view in the ABAP dictionary?

Answer 13

False, the CDS view shows up in the dictionary as a DDL SQL View with the name given in the CDS definition as the sqlViewName.

Question 14

The sqlViewName is always the same as the name given in the “define view” statement?

Answer 14

It is never the same. Both names must be unique across the system

Question 15

There are two ways to see the native SQL used to create the CDS view on the database. What are they?

Answer 15

From the ABAP dictionary extras->create

From the CDS definition press F3 while on the sqlViewName. Click on the presented link

Question 16

CDS views cannot be buffered!

Answer 16

Of course they can

buffering. status
buffering. type

Question 17

How can reference information, such as currency and unit of measure info be added to a CDS definition?

Answer 17

Using annotations such as
@semantics.amount.currencyCode: ‘CURRENCY’
@semantics.currencyCode: true

Question 18

By default, CDS views are client dependent?

Answer 18

True, but this can be changed on each individual CDS by setting
@ClientDependent: ‘false’

Question 19

In a CDS can CAST expressions be nested?

Answer 19

No

Question 20

What does CDS stand for?

Answer 20

Core Data Services

Question 21

What does the COALESCE do?

Answer 21

Can replace null values in a list

Question 22

Cast types in CDS views are defined using

Answer 22

abap. decfloat34
abap. cuky
abap. fltp……

Question 23

You can use either he CDS view name or the SQL view name in the SELECT clause?

Answer 23

Not anymore, only the CDS view name can be used as of NW7.5

Question 24

When using an exposed association over an adhoc association, what advantage is gained?

Answer 24

The entire exposed association can be referenced by name instead of individual columns

Question 25

I don’t understand how to use exposed associations

Answer 25

It seems like a new view can select from another CDS view and the associations can be addressed simply

Question 26

When using path expressions what must the association names be prefixed with? This seems to be related to addressing association fields from ABAP

Answer 26

A backslash _association-field

Question 27

I don’t understand the difference between exposed and ad-hoc associations

Answer 27

An adhoc is a list of fields from the associated table or view or cds
An Exposed is the entire row. The pre-req for the exposed is to have the “on” field from the left hand side of the association listed as the field above the associated entity in the field list.
This EXPOSES the entire entity row of the associated entity

Question 28

You can use SELECT * when employing a UNION or UNION ALL

Answer 28

No

Question 29

A field of the right table must be included in the ON clause?

Answer 29

It says no but I don’t understand how that works

Question 30

INTO no longer needs to be at the end of the Select

Answer 30

True except in UNIONS where it must still be the last clause

Question 31

DCL source is?

Answer 31

The data control represented in the ABAP dictionary

Question 32

What is the difference between an Association and a View

Answer 32

Associations use foreign key relationships to avaid having to define the view relationship

Question 33

What is the difference between an Association and a View

Answer 33

Associations use foreign key relationships to avaid having to define the view relationship
An Association can specify cardinality

Question 34

Where can an association be used

Answer 34

in all places where table names or column names are used

Question 35

How can exposed associations be used

Answer 35

In data preview, and also in subsequent CDSs. From open SQL they can be addressed thru path expressions

Question 36

Is it possible to extend an existing CDS view without modification?

Answer 36

Yes, use the EXTEND functionality

Question 37

Parameters of a CDS must be of what type?

Answer 37

Predefined or data element
examples
WITH PARAMETERS
FIRSTNAME: type bname
MYAGE: type abap.int8

Question 38

Parameters of a CDS must be of what type?

Answer 38

Predefined or data element
examples
WITH PARAMETERS
FIRSTNAME: type bname,
MYAGE: type abap.int8

Question 39

True or false, the parameters in the parameter list must be comma separated?

Answer 39

True

Question 40

How can a system variable be used as a CDS parameter?

Answer 40

Using the annotation

@Environment.SystemField: #{sys field}

Question 41

How can a system variable be used as a CDS parameter?

Answer 41

Using the annotation
@Environment.SystemField: #{sys field}
THIS ONLY WORKS IF THE CDS IS ACCESSED THRU OPEN SQL

Question 42

When a CDS uses another CDS that has input parameters, how are the parameters passed?

Answer 42

as comma separated value pairs enclosed in parentheses.
e.g.
( firstname ‘Bob’, lastname ‘Heide’)
System filled parameters DO NEED to be passed

Question 43

When Open SQL uses a CDS that has parameters, how are the parameters passed?

Answer 43

as comma separated value pairs enclosed in parentheses.
e.g
( firstname = ‘Bob’,
lastname = ‘Heide’ )
System filled parameters do not need to be passed

Question 44

How can access control be implemented for CDSs?

Answer 44

Access control is implemented by
Defining a role and granting access to the CDS
The values are as an aspect in a standard authority check

Question 45

What is the only current auth aspect that is supported

Answer 45

pfcg_auth

Question 46

For authorizations, two annotations are available in the DCL. What are they and what do they mean?

Answer 46

@EndUserText.label: ‘this is the role text’

@MappingRole: role is assigned to all users regardless of client. Only value allowed is true

Question 47

For authorizations, one annotation with three options is allowed in the DDL of the CDS. Name them and what they do.

Answer 47

@AccessControl.authorizationCheck
#CHECK means perform the access control using the assigned role.  Syntax error if no role assigned
#NOT_REQUIRED is just like #CHECK but does not give a syntax error if no role is assigned
#NOT_ALLOWED gives a syntax check warning if a DCL is assigned

Question 48

What must every CDS role contain?

Answer 48

@MappingRole: true