Which of the following ABAP SQL aggregate functions accept an ABAP SQL expression (e.g., f1 + f2) as input?
(Select 2 correct answers)
Answer : A, D
avg(expr) Allows numeric expressions (e.g., (f1 + f2) / 2).
sum(expr) Accepts numeric expressions.
max() Requires a single column, not expressions.
count(*) Counts rows only, doesn't accept expressions.
Study Guide Reference: ABAP SQL Documentation -- Aggregate Functions.
Which of the following is a technique for defining access controls?
Answer : A
In ABAP CDS access controls, the technique used is inheritance, which allows one access control object to reuse rules defined in another.
This makes authorization definitions consistent, reusable, and maintainable, which is essential in RAP applications where business objects require layered and reusable authorization concepts.
Options such as Redefinition, Singleton, or Casting belong to OO concepts, not to access control in CDS.
Verified Study Guide Reference: ABAP Cloud Documentation -- Defining Access Controls in CDS and RAP BOs.
What can be translated?
(Select 3 correct answers)
Answer : B, D, E
In ABAP Cloud, translation is supported for:
Data element texts (short, medium, long descriptions).
Message class texts (used in MESSAGE statements).
Text symbols (defined in programs).
Not translatable:
String variables runtime values, no translation.
Text literals hard-coded, not translatable via translation tools.
Study Guide Reference: ABAP Documentation -- Text Elements and Translation in ABAP Cloud.
What are some features of ABAP SQL?
Note: There are 2 correct answers to this question.
Answer : A, B
ABAP SQL (also known as Open SQL):
Is fully integrated in the ABAP language and supports embedded use with host variables, making Option B correct.
Is first processed by the ABAP Database Interface, which translates Open SQL into the database-specific native SQL. Hence, Option A is also correct.
Option C is incorrect because ABAP SQL is not directly executed on HANA or any database; it is interpreted and adapted by the ABAP layer.
Option D is incorrect because ABAP SQL is not restricted to HANA; it is database-agnostic and works across different supported DBs.
===========
Given the following ABAP SQL statement excerpt from an ABAP program:
SELECT SINGLE *
FROM spfli
WHERE carrid = 'LH' AND connid = '0400'
INTO @DATA(wa).
You are given the following information:
The data source spfli on line #2 is an SAP HANA database table.
spfli will be a large table with over one million rows.
This program is the only one in the system that accesses the table.
This program will run rarely.
Based on this information, which of the following general settings should you set for the spfli database table?
Note: There are 2 correct answers to this question.
Answer : A, D
In SAP HANA, the choice of storage type and load unit depends on access patterns, table size, and usage frequency.
Here's how each part applies:
A . 'Storage Type' to 'Row Store' -- This is correct.
Since:
The table is accessed by only one program.
The program runs rarely.
The access pattern is row-oriented (SELECT SINGLE with filters).
Row store is more suitable for rare access with small result sets and no aggregation.
D . 'Load Unit' to 'Page Loadable' -- This is correct.
Since the program runs infrequently, loading the entire column into memory (column loadable) is not efficient. Page-loadable units load only required parts into memory on demand, which reduces memory footprint.
Incorrect options:
B . 'Storage Type' to 'Column Store' -- Incorrect here. Column store is ideal for frequent reads, aggregations, or analytics, not for rarely accessed tables with simple lookups.
C . 'Load Unit' to 'Column Loadable' -- Also not optimal for rarely accessed data. Column loadable preloads entire columns into memory, which is memory-intensive and unnecessary in this case.
ABAP CDS Development Guide and SAP HANA Table Storage Guidelines -- Recommended storage strategies based on access pattern, frequency, and usage role.
Given the following code excerpt that defines an SAP HANA database table:
DEFINE TABLE demo_table
{
KEY field1 : REFERENCE TO abap.clnt(3);
KEY field2 : abap.char(1332);
@Semantics.quantity.unitOfMeasure : 'demo_table.field4'
field3 : abap.quan(2);
field4 : abap.unit(2);
}
Which field is defined incorrectly?
Answer : A
Let's evaluate each field:
field1: Defined as REFERENCE TO abap.clnt(3) --- this is correct. It follows standard definition for client fields.
field2: Defined as abap.char(1332) --- this is incorrect. In ABAP CDS view entities, the maximum length for CHAR fields is limited to 1333 bytes total row size for all fields in a view or table. A single CHAR(1332) is almost the full limit and considered impractical or invalid in real implementations.
field3: Defined as abap.quan(2) --- this is correct, representing a quantity field with 2 decimal places.
field4: Defined as abap.unit(2) --- this is correct and compatible with the @Semantics.quantity.unitOfMeasure annotation used in field3.
Therefore, field2 is the invalid field due to its excessive length, likely breaching the allowable memory layout in the HANA table or violating SAP CDS limits.
ABAP CDS Development Guide, section 2.1 -- Table definitions and ABAP type length constraints; SAP Help 3, page 6 -- maximum lengths for data elements and supported annotations.
Which of the following are reasons that SAP recommends developing Core Data Services view entities as opposed to classic Core Data Services DDIC-based views?
Note: There are 2 correct answers to this question.
Answer : C, D
SAP recommends using CDS view entities over classic CDS DDIC-based views due to the following benefits:
Simpler and stricter syntax: CDS view entities enforce a clearer separation of concerns and reduce ambiguity, which helps ensure consistency across the stack. This makes Option C correct.
Elimination of the need for a database view: With CDS view entities, there's no dependency on a separate DDIC SQL view object, reducing redundancy and improving activation performance. This makes Option D correct.
Incorrect options:
Automated client handling (Option A) is supported in both CDS view entities and classic CDS views via annotations like @ClientHandling.
Simplified syntax check (Option B) is not a distinct feature of CDS view entities. Syntax checking is part of ABAP Development Tools regardless of the CDS flavor used.