Free SAP C_ABAPD_2309 Übungsprüfungen - Seite 3 von 4

Question #20

What are some properties of database tables? Note: There are 2 correct answers to this question.

A . They store information in two dimensions.
B . They may have key fields.
C . They can have any number of key fields.
D . They can have relationships to other tables.

Lösung einblenden Lösung ausblenden

Question #20

What are some properties of database tables? Note: There are 2 correct answers to this question.

A . They store information in two dimensions.
B . They may have key fields.
C . They can have any number of key fields.
D . They can have relationships to other tables.

Lösung einblenden Lösung ausblenden

Question #23

Class super has subclass sub.

Which rules are valid for the sub constructor? Note: There are 2 correct answers to this question.

A . The method signature can be changed.
B . Import parameters can only be evaluated after calling the constructor of super.
C . The constructor of super must be called before using any components of your own instance.
D . Events of your own instance cannot be raised before the registration of a handler in super.

Lösung einblenden Lösung ausblenden

Question #24

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

A . SELECT FROM /dmo/connection FIELDS carrid O airpfrom,
MAX(distance) AS dist_max, MIN( distance) AS dist_min GROUP BY carrid, airpfrom INTO TABLE @DATA(It_hits)
B . SELECT FROM /dmo/connection FIELDS / O carrid, airpfrom,
MAX( distance) AS dist_max, MIN(distance) AS dist_min INTO TABLE @DATA(It_hits)
C . SELECT FROM /dmo/connection FIELDS V D MAX(distance) AS dist_max
MIN(distance) AS dist_min INTO TABLE @DATA(It_hits).
D . SELECT FROM /dmo/connection FIELDS r―i carrid, airpfrom u GROUP BY carrid, connid INTO TABLE @DATA(It_hits).

Lösung einblenden Lösung ausblenden

Question #25

What is the sequence priority when evaluating a logical expression?

A) NOT 1

B) OR 3

C) AND 2

A . ABC
B . CAB
C . ACB
D . BAC

Lösung einblenden Lösung ausblenden

Question #26

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.

Lösung einblenden Lösung ausblenden

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

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.

Lösung einblenden Lösung ausblenden

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

Which of the following results in faster access to internal tables? Note: There are 3 correct answers to this question.

A . In a sorted internal table, specifying the primary key partially from the left without gaps.
B . In a sorted internal table, specifying the primary key completely.
C . In a standard internal table, specifying the primary key partially from the left without gaps.
D . In a hashed internal table, specifying the primary key partially from the left without gaps.
E . In a hashed internal table, specifying the primary key completely.

Lösung einblenden Lösung ausblenden

Question #29

In RESTful Application Programming, a business object contains which parts? Note: There are 2 correct answers to this question.

A . CDS view
B . Behavior definition
C . Authentication rules
D . Process definition

Lösung einblenden Lösung ausblenden

Richtige Antwort: A, B
A, B

Explanation:

In RESTful Application Programming, a business object contains two main parts: a CDS view and a behavior definition1.

A) CDS view: A CDS view is a data definition that defines the structure and the data source of a business object. A CDS view can consist of one or more entities that are linked by associations or compositions. An entity is a CDS view element that represents a node or a projection of a business object. An entity can have various annotations that define the metadata and the semantics of the business object2.

B) Behavior definition: A behavior definition is a source code artifact that defines the behavior and the validation rules of a business object. A behavior definition can specify the standard CRUD (create,

read, update, delete) operations, the draft handling, the authorization checks, and the side effects for a business object. A behavior definition can also define custom actions, validations, and determinations that implement the business logic of a business object3.

The following are not parts of a business object in RESTful Application Programming, because:

C) Authentication rules: Authentication rules are not part of a business object, but part of a service binding. A service binding is a configuration artifact that defines how a business object is exposed as an OData service. A service binding can specify the authentication method, the authorization scope, the protocol version, and the service options for the OData service4.

D) Process definition: Process definition is not part of a business object, but part of a workflow. A workflow is a business process that orchestrates the tasks and the events of a business object. A workflow can be defined using the Workflow Editor in the SAP Business Application Studio or the SAP Web IDE. A workflow can use the business object’s APIs to trigger or consume events, execute actions, or read or update data5.

Reference: 1: Business Object | SAP Help Portal 2: CDS View Entities | SAP Help Portal 3: Behavior

Definition | SAP Help Portal 4: Service Binding | SAP Help Portal 5: Workflow | SAP Help Portal

Question #30

Which statement can you use to change the contents of a row of data in an internal table?

A . Append table
B . Modify table
C . Insert table
D . Update table

Lösung einblenden Lösung ausblenden

Richtige Antwort: B
B

Explanation:

The statement that can be used to change the contents of a row of data in an internal table is MODIFY table. The MODIFY table statement can be used to change the contents of one or more rows of an internal table, either by specifying the table index, the table key, or a condition. The MODIFY table statement can also be used to change the contents of a database table, by specifying the table name and a work area or an internal table. The MODIFY table statement can use the TRANSPORTING addition to specify which fields should be changed, and the WHERE addition to specify which rows should be changed.

The other statements are not suitable for changing the contents of a row of data in an internal table, as they have different purposes and effects. These statements are:

APPEND table: This statement can be used to add a new row of data to the end of an internal table, either by specifying a work area or an inline declaration. The APPEND table statement does not change the existing rows of the internal table, but only increases the number of rows by one. INSERT table: This statement can be used to insert a new row of data into an internal table, either by specifying the table index, the table key, or a sorted position. The INSERT table statement does not change the existing rows of the internal table, but only shifts them to make room for the new row. The INSERT table statement can also be used to insert a new row of data into a database table, by specifying the table name and a work area or an inline declaration.

UPDATE table: This statement can be used to update the contents of a database table, by specifying the table name and a work area or an internal table. The UPDATE table statement can use the SET addition to specify which fields should be updated, and the WHERE addition to specify which rows should be updated. The UPDATE table statement does not affect the internal table, but only the corresponding database table.

Reference: MODIFY table – ABAP Keyword Documentation, APPEND table – ABAP Keyword Documentation, INSERT table – ABAP Keyword Documentation, UPDATE table – ABAP Keyword Documentation