Free SAP C_ABAPD_2309 Übungsprüfungen

Question #1

Which ABAP SQL clause allows the use of inline declarations?

A . FROM
B . INTO CORRESPONDING FIELDS OF
C . INTO
D . FIELDS

Question #2

Which of the following are parts of answers to this question.

A . Partitioning attributes
B . Extension
C . Field list
D . Semantic table attributes

Richtige Antwort: BC
BC

Explanation:

A CDS view is a data definition that defines a data structure and a data selection from one or more data sources.

A CDS view consists of several parts, but two of them are:

Extension: An extension is an optional clause that allows a CDS view to extend another CDS view by adding new elements, annotations, or associations. The extension clause has the syntax EXTEND VIEW view_name WITH view_name. The first view_name is the name of the CDS view that is being extended, and the second view_name is the name of the CDS view that is doing the extension1. Field list: A field list is a mandatory clause that specifies the elements of the CDS view. The field list has the syntax SELECT FROM data_source { element_list }. The data_source is the name of the data source that the CDS view selects data from, and the element_list is a comma-separated list of elements that the CDS view exposes. The elements can be fields of the data source, expressions, associations, or annotations2.

The following example shows a CDS view that extends another CDS view and defines a field list: @AbapCatalog.sqlViewName: ‘ZCDS_EXT’ define view Z_CDS_Extension extend view Z_CDS_Base with Z_CDS_Extension as select from ztable { // field list key ztable.id as ID, ztable.name as Name, ztable.age as Age, // extension @Semantics.currencyCode: true ztable.currency as Currency } The other options are not parts of a CDS view, but rather related concepts:

Partitioning attributes: Partitioning attributes are attributes that are used to partition a table into smaller subsets of data. Partitioning attributes are defined in the ABAP Dictionary for transparent tables and can improve the performance and scalability of data access. Partitioning attributes are not part of the CDS view definition, but rather the underlying table definition3.

Semantic table attributes: Semantic table attributes are attributes that provide additional information about the meaning and usage of a table. Semantic table attributes are defined in the ABAP Dictionary for transparent tables and can be used to enhance the data modeling and consumption of the table. Semantic table attributes are not part of the CDS view definition, but rather the underlying table definition4.

Reference: 1: Extending CDS Views | SAP Help Portal 2: SELECT List – ABAP Keyword Documentation 3: Partitioning Attributes – ABAP Keyword Documentation 4: Semantic Table Attributes – ABAP Keyword Documentation

Question #3

Refer to Exhibit.

When accessing the subclass instance through go_super, what can you do? Note: There are 2 correct answers to this question.

A . Access the inherited private components.
B . Access the inherited public components.
C . Call a subclass specific public method
D . Call inherited public redefined methods.

Lösung einblenden Lösung ausblenden

Question #4

You have two internal tables itab1 and itab2.What is true for using the expression itab1 = corresponding #( itab2 )? Note: There are 2 correct answers to this question.

A . Fields with the same name but with different types may be copied from itab2 to itab1.
B . itab1 and itab2 must have at least one field name in common.
C . Fields with the same name and the same type will be copied from itab2 to itab1.
D . itab1 and itab2 must have the same data type.

Lösung einblenden Lösung ausblenden

Richtige Antwort: B, C
B, C

Explanation:

The expression itab1 = corresponding #( itab2 ) is a constructor expression with the component operator CORRESPONDING that assigns the contents of the internal table itab2 to the internal table itab1.

The following statements are true for using this expression:

B: itab1 and itab2 must have at least one field name in common. This is because the component operator CORRESPONDING assigns the identically named columns of itab2 to the identically named columns of itab1 by default, according to the rules of MOVE-CORRESPONDING for internal tables. If itab1 and itab2 do not have any field name in common, the expression will not assign any value to itab1 and it will remain initial or unchanged1

C: Fields with the same name and the same type will be copied from itab2 to itab1. This is because the component operator CORRESPONDING assigns the identically named columns of itab2 to the identically named columns of itab1 by default, according to the rules of MOVE-CORRESPONDING for internal tables. If the columns have the same name but different types, the assignment will try to perform a conversion between the types, which may result in a loss of precision, a truncation, or a runtime error, depending on the types involved1

The following statements are false for using this expression:

A: Fields with the same name but with different types may be copied from itab2 to itab1. This is not true, as explained in statement

C. The assignment will try to perform a conversion between the types, which may result in a loss of precision, a truncation, or a runtime error, depending on the types involved1

D: itab1 and itab2 must have the same data type. This is not true, as the component operator CORRESPONDING can assign the contents of an internal table of one type to another internal table of a different type, as long as they have at least one field name in common. The target type of the expression is determined by the left-hand side of the assignment, which is itab1 in this case. The expression will create an internal table of the same type as itab1 and assign it to itab11

Reference: CORRESPONDING – Component Operator – ABAP Keyword Documentation

Question #5

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.

A . "Storage Type" to "Column Store"
B . "Load Unit to "Column Loadable"
C . "Storage Type" to "Row Store"
D . "Load Unit‘ to ‚Page Loadable"

Lösung einblenden Lösung ausblenden

Question #6

Which of the following integration frameworks have been released for ABAP cloud development? Note: There are 3 correct answers to this question.

A . SOAP consumption
B . CDS Views
C . Business Add-ins (BAdls)
D . Business Events
E . OData services

Lösung einblenden Lösung ausblenden

Richtige Antwort: A, D, E
A, D, E

Explanation:

The following are the integration frameworks that have been released for ABAP cloud development: SOAP consumption: This framework allows you to consume SOAP web services from ABAP cloud applications. You can use the ABAP Development Tools in Eclipse to create a service consumption model based on a WSDL file or URL. The service consumption model generates the required ABAP artifacts, such as proxy classes, data types, and constants, to access the web service. You can then use the proxy classes to call the web service operations from your ABAP code1

Business Events: This framework allows you to publish and subscribe to business events from ABAP cloud applications. Business events are messages that represent a change in the state of a business object or process. You can use the ABAP Development Tools in Eclipse to create a business event definition based on a CDS view entity or a projection view. The business event definition specifies the event key, the event payload, and the event metadata. You can then use the ABAP Messaging Channel (AMC) framework to publish and subscribe to business events using the AMC API2

OData services: This framework allows you to expose and consume OData services from ABAP cloud applications. OData is a standardized protocol for creating and consuming RESTful APIs. You can use the ABAP RESTful Application Programming Model (RAP) to create OData services based on CDS view entities or projection views. The RAP framework generates the required OData metadata and runtime artifacts, such as service definitions, service bindings, and service implementations. You can then use the SAP Gateway framework to register and activate your OData services. You can also use the ABAP Development Tools in Eclipse to consume OData services from other sources using the service consumption model3

The other integration frameworks are not released for ABAP cloud development, as they are either not supported or not recommended for cloud scenarios.

These frameworks are:

CDS Views: CDS views are not an integration framework, but a data modeling framework. CDS views are used to define data models based on database tables or other CDS view entities. CDS views can have associations, aggregations, filters, parameters, and annotations. CDS views can also be used as the basis for other integration frameworks, such as OData services or business events4

Business Add-ins (BAdls): BAdls are not supported for ABAP cloud development, as they are part of the classic ABAP enhancement framework. BAdls are used to implement custom logic in predefined enhancement spots in the standard SAP code. BAdls are not compatible with the cloud strategy and the clean core paradigm, as they modify the SAP code and can cause upgrade and maintenance issues. For ABAP cloud development, SAP recommends using the key user extensibility tools or the side-by-side extensibility approach instead of BAdls.

Reference: Consuming SOAP Services – ABAP Keyword Documentation, Business Events – ABAP Keyword Documentation, OData Services – ABAP Keyword Documentation, CDS Data Model Views – ABAP Keyword Documentation, [Business Add-Ins (BAdIs) – ABAP Keyword Documentation]

Question #7

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

Lösung einblenden Lösung ausblenden

Question #8

Exhibit:

Which of the following statements are correct? Note: There are 2 correct answers to this question.

A . FOR defines a loop that runs over the content of source_itab
B . source_itab is only visible within the loop.
C . row is a predefined name and cannot be chosen arbitrarily.
D . row is only visible within the loop.

Lösung einblenden Lösung ausblenden

Question #9

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.

Lösung einblenden Lösung ausblenden

Richtige Antwort: 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 #9

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.

Lösung einblenden Lösung ausblenden

Richtige Antwort: 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