SAP C_ABAPD_2309 - Questions & Answers

A unique secondary key in SAP ABAP ensures that the key combination of rows in a table is unique. Its main purposes are to speed up access to the table and enforce data integrity.
It is created with the first read access of a table (C): This is correct. A unique secondary key is established upon the first read access of the table using a statement like READ TABLE. The system creates an index for each row based on the key fields.
It is updated when the table is modified (D): This is also correct. A unique secondary key will update itself when the content of the table changes, ensuring that data uniqueness is maintained.

Incorrect answers:
"It is created when a table is filled (A):" This is incorrect. A unique secondary key is not created when the table is initially filled but rather upon the first read access.
"It is updated when the modified table is read again (B):" This is incorrect. The unique secondary key does not update based on read operations; it maintains its integrity independently.
References:
1.
"Improving Internal Table Performance Using Secondary Keys" - SAP Learning
2.
"Secondary Key - ABAP Keyword Documentation" - SAP Online Help

In class ZCL_CLASS_A, you use the statement DATA var TYPE *** to declare a data object named var with a data type specified by ***. The data type can be any of the following:
1. A predefined ABAP type, such as i, f, c, string, xstring, etc.
2. A data element from the ABAP Dictionary, such as matnr, carrid, bukrs, etc. A data element defines the semantic and technical attributes of a data field, such as the domain, length, data type, description, and value range.
3. A domain from the ABAP Dictionary, such as matnr_d, carrid_d, bukrs_d, etc. A domain defines the technical attributes of a data field, such as the data type, length, output length, number of decimal places, and value range.
4. A global type defined in a class, interface, or type pool, such as ZCL_CLASS_B=>TYPE_A, ZIF_INTERFACE_C=>TYPE_B, ZTYPE_POOL_D=>TYPE_C, etc. A global type is a type defined in a global repository object and can be used in any program or class.
5. A local type defined within the class, such as TYPE_A, TYPE_B, TYPE_C, etc. A local type can only be used within the class in which it is defined.
Therefore, the possible values for *** are: B: The name of a data element from the ABAP Dictionary.
D: The name of a domain from the ABAP Dictionary.

The other options are not valid because: A: The name of a type defined privately in class ZCL_CLASS_A is a local type and cannot be used with the DATA statement. A local type can only be used with the TYPES statement.
C: The name of a type defined privately in another class is a private type and cannot be accessed from outside the class. A private type can only be used within the class that defines it.

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 itab 1. The following statements are true when 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, following the rules of MOVE-CORRESPONDING for internal tables. If itab1 and itab2 do not have any field names in common, the expression will not assign any value to itab1, and it will remain initial or unchanged.

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

The following statements are false when using this expression:

A: Fields with the same name but different types may be copied from itab2 to itab 1. This is not true, as explained in statement C. The assignment will attempt to perform a type conversion, which may lead to a loss of precision, truncation, or a runtime error, depending on the types involved.

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 itab 1.

References:
CORRESPONDING - Component Operator - ABAP Keyword Documentation