Free SAP C_ABAPD_2309 Practice Exams - Page 2 of 5

Question #11

In class ZCL_CLASS_A, you use the statement DATA var TYPE ***

What may stand in place of ***? Note: There are 2 correct answers to this question.

A . The name of a type defined privately in class ZCL_CLASS_A
B . The name of a data element from the ABAP Dictionary
C . The name of a type defined privately in another class
D . The name of a domain from the ABAP Dictionary

Reveal Solution Hide Solution

Question #12

Refer to the exhibit.

The class zcl_demo_class is in a software component with the language version set to "Standard ABAP". The function module "ZF11 is in a software component with the language version set to "ABAP Cloud". Both the class and function module are customer created. Regarding line #6, which of

the following is a valid statement?

A . ‘ZF1’ can be called whether it has been released or not for cloud development.
B . ‘ZF1’ can be called via a wrapper that itself has been released for cloud development.
C . ‘ZF1’ can be called via a wrapper that itself has not been released for cloud development.
D . ‘ZF1’ must be released for cloud development to be called.

Reveal Solution Hide Solution

Correct Answer: B
B

Explanation:

The function module ZF1 is in a software component with the language version set to “ABAP Cloud”. This means that it follows the ABAP Cloud Development Model, which requires the usage of public SAP APIs and extension points to access SAP functionality and data. These APIs and extension points are released by SAP and documented in the SAP API Business Hub1. Customer-created function modules are not part of the public SAP APIs and are not released for cloud development. Therefore, calling a function module directly from a class with the language version set to “Standard ABAP” is not allowed and will result in a syntax error. However, there is a possible way to call a function module indirectly from a class with the language version set to “Standard ABAP”:

Create a wrapper class or interface for the function module and release it for cloud development. A wrapper is a class or interface that encapsulates the function module and exposes its functionality through public methods or attributes. The wrapper must be created in a software component with the language version set to “ABAP Cloud” and must be marked as released for cloud development using the annotation @EndUserText.label. The wrapper can then be called from a class with the language version set to “Standard ABAP” using the public methods or attributes2.

For example, the following code snippet shows how to create a wrapper class for the function module ZF1 and call it from the class zcl_demo_class:

@EndUserText.label: ‘Wrapper for ZF1’ CLASS zcl_wrapper_zf1 DEFINITION PUBLIC FINAL CREATE PUBLIC. PUBLIC SECTION. CLASS-METHODS: call_zf1 IMPORTING iv_a TYPE i iv_b TYPE i EXPORTING ev_result TYPE i. ENDCLASS.

CLASS zcl_wrapper_zf1 IMPLEMENTATION. METHOD call_zf1. CALL FUNCTION ‘ZF1’ EXPORTING a = iv_a b = iv_b IMPORTING result = ev_result. ENDMETHOD. ENDCLASS. CLASS zcl_demo_class DEFINITION. METHODS: m1. ENDCLASS.

CLASS zcl_demo_class IMPLEMENTATION. METHOD m1. DATA(lv_result) =

zcl_wrapper_zf1=>call_zf1( iv_a = 2 iv_b = 3 ). WRITE: / lv_result. ENDMETHOD. ENDCLASS.

The output of this code is: 5

Reference: 1: SAP API Business Hub 2: Creating an ABAP Cloud Project | SAP Help Portal

Question #13

As a consultant you are posed the following question from a client who is using SAP S/4HANA Cloud, public edition and also SAP BTP, ABAP environment.

"We are currently using an SAP Fiori app based on SAP Fiori elements that analyzes open orders. We have determined that it should be extended via a new button on the UI which will perform an on-the-fly calculation and display the result in a quick popup for the enduser. We have been informed by SAP that all underlying stack layers for the SAP Fiori app have been extensibility enabled."

Based on this which of the following extension types would you recommend to the customer to add

the new button?

A . RAP BO Behavior Extension
B . SAP HANA database table extension
C . RAP BO Node Extension
D . Business Service Extension

Reveal Solution Hide Solution

Question #14

Which function call returns 0?

A . Count_any_of ( val – ‘ABAP ABAP abap’ sub "AB" )
B . Count (val – ‘ABAP ABAP abap’ sub – ‘AB’ )
C . find_any_of (val = "ABAP ABAP abap’ sub = "AB")
D . find_any_not_of( val ‘ABAP ABAP abap’ sub = ‘AB’)

Reveal Solution Hide Solution

Question #15

What RESTful Application Programming object contains only the fields required for a particular app?

A . Database view
B . Metadata extension
C . Projection View
D . Data model view

Reveal Solution Hide Solution

Question #16

What are some characteristics of secondary keys for internal tables? Note: There are 3 correct answers to this question.

A . Secondary keys must be chosen explicitly when you actually read from an internal table.
B . Multiple secondary keys are allowed for any kind of internal table.
C . Hashed secondary keys do NOT have to be unique.
D . Sorted secondary keys do NOT have to be unique.
E . Secondary keys can only be created for standard tables.

Reveal Solution Hide Solution

Correct Answer: A, B, D
A, B, D

Explanation:

Secondary keys are additional keys that can be defined for internal tables to optimize the access to the table using fields that are not part of the primary key. Secondary keys can be either sorted or hashed, depending on the table type and the uniqueness of the key. Secondary keys have the following characteristics1:

A) Secondary keys must be chosen explicitly when you actually read from an internal table. This means that when you use a READ TABLE or a LOOP AT statement to access an internal table, you have to specify the secondary key that you want to use with the USING KEY addition. For example, the following statement reads an internal table itab using a secondary key sec_key:

READ TABLE itab USING KEY sec_key INTO DATA(wa).

If you do not specify the secondary key, the system will use the primary key by default2.

B) Multiple secondary keys are allowed for any kind of internal table. This means that you can define more than one secondary key for an internal table, regardless of the table type. For example, the following statement defines an internal table itab with two secondary keys sec_key_1 and sec_key_2:

DATA itab TYPE SORTED TABLE OF ty_itab WITH NON-UNIQUE KEY sec_key_1 COMPONENTS field1 field2 sec_key_2 COMPONENTS field3 field4.

You can then choose which secondary key to use when you access the internal table1.

D) Sorted secondary keys do NOT have to be unique. This means that you can define a sorted secondary key for an internal table that allows duplicate values for the key fields. A sorted secondary key maintains a predefined sorting order for the internal table, which is defined by the key fields in the order in which they are specified. For example, the following statement defines a sorted secondary key sec_key for an internal table itab that sorts the table by field1 in ascending order and field2 in descending order:

DATA itab TYPE STANDARD TABLE OF ty_itab WITH NON-UNIQUE SORTED KEY sec_key COMPONENTS field1 ASCENDING field2 DESCENDING.

You can then access the internal table using the sorted secondary key with a binary search algorithm, which is faster than a linear search3.

The following are not characteristics of secondary keys for internal tables, because:

C) Hashed secondary keys do NOT have to be unique. This is false because hashed secondary keys must be unique. This means that you can only define a hashed secondary key for an internal table that does not allow duplicate values for the key fields. A hashed secondary key does not have a predefined sorting order for the internal table, but uses a hash algorithm to store and access the table rows. For example, the following statement defines a hashed secondary key sec_key for an internal table itab that hashes the table by field1 and field2:

DATA itab TYPE STANDARD TABLE OF ty_itab WITH UNIQUE HASHED KEY sec_key COMPONENTS field1 field2.

You can then access the internal table using the hashed secondary key with a direct access algorithm, which is very fast.

E) Secondary keys can only be created for standard tables. This is false because secondary keys can

be created for any kind of internal table, such as standard tables, sorted tables, and hashed tables. However, the type of the secondary key depends on the type of the internal table. For example, a standard table can have sorted or hashed secondary keys, a sorted table can have sorted secondary keys, and a hashed table can have hashed secondary keys1.

Reference: 1: Secondary Table Key – ABAP Keyword Documentation 2: READ TABLE – ABAP Keyword Documentation 3: Sorted Tables – ABAP Keyword Documentation : Hashed Tables – ABAP Keyword Documentation

Question #17

When does SAP recommend to use a sorted or a hashed table respectively? Note: There are 2 correct answers to this question.

A . A hashed table, when you read a single record and specify the complete key.
B . A hashed table, when you read a subset in a loop and specify a part of the key from the left without gaps.
C . A sorted table, when you read a subset in a loop and specify a part of the key from the left ^ without gaps.
D . A sorted table, when you read a single record and specify non key fields.

Reveal Solution Hide Solution

Question #18

What are the effects of this annotation? Note: There are 2 correct answers to this question.

A . The value of sy-langu will be passed to the CDS view automatically both when you use the -1 CDS view in ABAP and in another CDS view entity (view on view).
B . You can still override the default value with a value of your own.
C . The value of sy-langu will be passed to the CDS view automatically when you use the CDS view in ABAP but not when you use it in another view entity
D . It is no longer possible to pass your own value to the parameter.

Reveal Solution Hide Solution

Correct Answer: A, B
A, B

Explanation:

The annotation @Environment.systemField: #LANGUAGE is used to assign the ABAP system field sy-langu to an input parameter of a CDS view or a CDS table function. This enables the implicit parameter passing in Open SQL, which means that the value of sy-langu will be automatically passed to the CDS view without explicitly specifying it in the WHERE clause. This also applies to the CDS views that use the annotated CDS view as a data source, which means that the value of sy-langu will be propagated to the nested CDS views (view on view)12.

For example:

The following code snippet defines a CDS view ZI_FLIGHT_TEXTS with an input parameter p_langu that is annotated with @Environment.systemField: #LANGUAGE:

define view ZI_FLIGHT_TEXTS with parameters p_langu : syst_langu @<Environment.systemField: #LANGUAGE as select from sflight left outer join scarr on sflight.carrid = scarr.carrid left outer join stext on scarr.carrid = stext.carrid { sflight.carrid, sflight.connid, sflight.fldate, scarr.carrname, stext.text as carrtext } where stext.langu = :p_langu

The following code snippet shows how to use the CDS view ZI_FLIGHT_TEXTS in ABAP without specifying the value of p_langu in the WHERE clause. The value of sy-langu will be automatically

passed to the CDS view:

SELECT carrid, connid, fldate, carrname, carrtext FROM zi_flight_texts INTO TABLE @DATA(lt_flights).

The following code snippet shows how to use the CDS view ZI_FLIGHT_TEXTS in another CDS view

ZI_FLIGHT_REPORT. The value of sy-langu will be automatically passed to the nested CDS view

ZI_FLIGHT_TEXTS:

define view ZI_FLIGHT_REPORT with parameters p_langu : syst_langu @<Environment.systemField: #LANGUAGE as select from zi_flight_texts(p_langu) { carrid, connid, fldate, carrname, carrtext, count(*) as flight_count } group by carrid, connid, fldate, carrname, carrtext

The annotation @Environment.systemField: #LANGUAGE does not prevent the possibility of overriding the default value with a value of your own. You can still specify a different value for the input parameter p_langu in the WHERE clause, either in ABAP or in another CDS view. This will override the value of sy-langu and pass the specified value to the CDS view12. For example:

The following code snippet shows how to use the CDS view ZI_FLIGHT_TEXTS in ABAP with a specified value of p_langu in the WHERE clause. The value ‘E’ will be passed to the CDS view instead of the value of sy-langu:

SELECT carrid, connid, fldate, carrname, carrtext FROM zi_flight_texts WHERE p_langu = ‘E’ INTO TABLE @DATA(lt_flights).

The following code snippet shows how to use the CDS view ZI_FLIGHT_TEXTS in another CDS view ZI_FLIGHT_REPORT with a specified value of p_langu in the WHERE clause. The value ‘E’ will be passed to the nested CDS view ZI_FLIGHT_TEXTS instead of the value of sy-langu:

define view ZI_FLIGHT_REPORT with parameters p_langu : syst_langu @<Environment.systemField: #LANGUAGE as select from zi_flight_texts(p_langu) { carrid, connid, fldate, carrname, carrtext, count(*) as flight_count } where p_langu = ‘E’ group by carrid, connid, fldate, carrname, carrtext Explanation:

Reference: 1: ABAP CDS – parameter_annot – ABAP Keyword Documentation – SAP Online Help 2: ABAP CDS – session_variable – ABAP Keyword Documentation – SAP Online Help

Question #19

Refer to the exhibit.

Which of the following types are permitted to be used for <source> on line #4? Note: There are 2 correct answers to this question.

A . A database table from the ABAP Dictionary
B . A CDS DDIC-based view
C . An external view from the ABAP Dictionary
D . A database view from the ABAP Dictionary

Reveal Solution Hide Solution

Correct Answer: AB
AB

Explanation:

The <source> clause in the CDS View Entity Data Definition can be used to specify the data source for the view entity. The <source> clause can accept different types of data sources, depending on the type of the view entity1.

A database table from the ABAP Dictionary: This is a valid type of data source for a CDS View Entity Data Definition. A database table from the ABAP Dictionary is a table that is defined in the ABAP Dictionary using the keyword TABLE or TABLE OF. The name of the database table must be unique within its namespace and must not contain any special characters2.

A CDS DDIC-based view: This is also a valid type of data source for a CDS View Entity Data Definition.

A CDS DDIC-based view is a view that is defined in the Core Data Services using the keyword DEFINE

VIEW ENTITY. The name of the CDS DDIC-based view must be unique within its namespace and must

not contain any special characters3.

You cannot do any of the following:

An external view from the ABAP Dictionary: This is not a valid type of data source for a CDS View Entity Data Definition. An external view from the ABAP Dictionary is a view that is defined in an

external application using any language supported by SAP, such as SQL, PL/SQL, or Java. The name of the external view must be unique within its namespace and must not contain any special characters4.

A database view from the ABAP Dictionary: This is not a valid type of data source for a CDS View Entity Data Definition. A database view from the ABAP Dictionary is a view that is defined in an external application using any language supported by SAP, such as SQL, PL/SQL, or Java. The name of the database view must be unique within its namespace and must not contain any special characters4.

Reference: 1: CDS DDL – DEFINE VIEW ENTITY – ABAP Keyword Documentation – SAP Online Help 2:

ABAP Dictionary Tables – SAP Online Help 3: CDS DDL – DEFINE VIEW ENTITY – ABAP Keyword

Documentation – SAP Online Help 4: ABAP Dictionary Views – SAP Online Help

Question #19

Refer to the exhibit.

Which of the following types are permitted to be used for <source> on line #4? Note: There are 2 correct answers to this question.

A . A database table from the ABAP Dictionary
B . A CDS DDIC-based view
C . An external view from the ABAP Dictionary
D . A database view from the ABAP Dictionary

Reveal Solution Hide Solution

Correct Answer: AB
AB

Explanation:

The <source> clause in the CDS View Entity Data Definition can be used to specify the data source for the view entity. The <source> clause can accept different types of data sources, depending on the type of the view entity1.

A database table from the ABAP Dictionary: This is a valid type of data source for a CDS View Entity Data Definition. A database table from the ABAP Dictionary is a table that is defined in the ABAP Dictionary using the keyword TABLE or TABLE OF. The name of the database table must be unique within its namespace and must not contain any special characters2.

A CDS DDIC-based view: This is also a valid type of data source for a CDS View Entity Data Definition.

A CDS DDIC-based view is a view that is defined in the Core Data Services using the keyword DEFINE

VIEW ENTITY. The name of the CDS DDIC-based view must be unique within its namespace and must

not contain any special characters3.

You cannot do any of the following:

An external view from the ABAP Dictionary: This is not a valid type of data source for a CDS View Entity Data Definition. An external view from the ABAP Dictionary is a view that is defined in an

external application using any language supported by SAP, such as SQL, PL/SQL, or Java. The name of the external view must be unique within its namespace and must not contain any special characters4.

A database view from the ABAP Dictionary: This is not a valid type of data source for a CDS View Entity Data Definition. A database view from the ABAP Dictionary is a view that is defined in an external application using any language supported by SAP, such as SQL, PL/SQL, or Java. The name of the database view must be unique within its namespace and must not contain any special characters4.

Reference: 1: CDS DDL – DEFINE VIEW ENTITY – ABAP Keyword Documentation – SAP Online Help 2:

ABAP Dictionary Tables – SAP Online Help 3: CDS DDL – DEFINE VIEW ENTITY – ABAP Keyword

Documentation – SAP Online Help 4: ABAP Dictionary Views – SAP Online Help