SAP C_ABAPD_2309 Practice Test - Questions Answers, Page 2

When accessing the subclass instance through go_super, you can do both of the following:

Access the inherited private components: A subclass inherits all the private attributes and methods of its superclass, unless they are explicitly overridden by the subclass.Therefore, you can access the inherited private components of the superclass through go_super, as long as they are not hidden by other attributes or methods in the subclass12.

Access the inherited public components: A subclass inherits all the public attributes and methods of its superclass, unless they are explicitly overridden by the subclass.Therefore, you can access the inherited public components of the superclass through go_super, as long as they are not hidden by other attributes or methods in the subclass12.

You cannot do any of the following:

Call a subclass specific public method: A subclass does not have any public methods that are not inherited from its superclass.Therefore, you cannot call a subclass specific public method through go_super12.

Call inherited public redefined methods: A subclass does not have any public methods that are redefined from its superclass.Therefore, you cannot call inherited public redefined methods through go_super12.

The ABAP Cloud Development Model requires that only public SAP APIs and extension points are used 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 an ABAP Cloud class is not allowed and will result in a syntax error. However, there are two possible ways to call a function module indirectly from an ABAP Cloud class:

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 ''Standard ABAP'' and must be marked as released for cloud development using the annotation @EndUserText.label.The wrapper can then be called from an ABAP Cloud class using the public methods or attributes2.

Use the ABAP Cloud Connector to call the function module as a remote function call (RFC) from an ABAP Cloud class. The ABAP Cloud Connector is a service that enables the secure and reliable communication between SAP BTP, ABAP environment and on-premise systems. The function module must be exposed as an RFC-enabled function module in the on-premise system and must be registered in the ABAP Cloud Connector. The ABAP Cloud class can then use the class cl_rfc_destination_service to get the destination name and the class cl_abap_system to create a proxy object for the function module.The proxy object can then be used to call the function module3.

ABAP SQL arithmetic expressions have different restrictions depending on the data type of the operands. The following are some of the restrictions:

Floating point types and integer types can be used in the same expression, as long as the integer types are cast to floating point types using the cast function. For example,CAST ( num1 AS FLTP ) / CAST ( num2 AS FLTP )is a valid expression, where num1 and num2 are integer types.

The operator / is allowed only in floating point expressions, where both operands have the type FLTP or f. For example,num1 / num2is a valid expression, where num1 and num2 are floating point types. If the operator / is used in an integer expression or a decimal expression, a syntax error occurs.

Decimal types and integer types can be used in the same expression, as long as the expression is a decimal expression. A decimal expression has at least one operand with the type DEC, CURR, or QUAN or p with decimal places. For example,num1 + num2is a valid expression, where num1 is a decimal type and num2 is an integer type.

The operator ** is allowed only in floating point expressions, where both operands have the type FLTP or f. For example,num1 ** num2is a valid expression, where num1 and num2 are floating point types. If the operator ** is used in an integer expression or a decimal expression, a syntax error occurs.

Both statements are valid in ABAP, but they have different effects on the program.

##NEEDED is a pragma that can be used to hide warnings from the ABAP compiler syntax check. It tells the check tools that a variable or a parameter is needed for further processing, even if it is not used in the current statement.For example, if you declare a variable without assigning any value to it, you can use ##NEEDED to suppress the warning about unused variables12.

The pragma is not checked by the syntax checker means that you can use any pragma to hide any warning from the ABAP compiler syntax check, regardless of its effect on the program logic or performance.For example, if you use ##SHADOW to hide a warning about an obscured function, you can also use it to hide a warning about an invalid character in a string12.

You cannot do any of the following:

#EC_NEEDED is not checked by the syntax checker: This is not a valid statement in ABAP.There is no pseudo-comment with #EC_NEEDED in ABAP3.

The pseudo-comment is checked by the syntax checker: This is false. Pseudo-comments are obsolete and should no longer be used in ABAP.They were replaced by pragmas since SAP NW 7.0 EhP2 (Enhancement Package)4.