2025 Realistic Verified Free SAP C_ABAPD_2507 Exam Questions
C_ABAPD_2507 Real Exam Questions and Answers FREE
SAP C_ABAPD_2507 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
NEW QUESTION # 10
Which statement can you use to change the contents of a row of data in an internal table?
- A. MODIFY
- B. UPDATE
- C. INSERT
- D. APPEND
Answer: A
NEW QUESTION # 11
Which function call returns 0?
- A. find( val = 'FIND Found found' sub = 'F' occ = -2 case = abap_true )
- B. find( val = 'find Found FOUND' sub = 'F' occ = -2 )
- C. find( val = 'FIND FOUND Found' sub = 'F' )
- D. find( val = 'find FOUND Found' sub = 'F' occ = -2 case = abap_false )
Answer: C
NEW QUESTION # 12
Which of the following are reasons to use the side-by-side extensibility pattern? (3 correct)
- A. An extension uses its own data model with occasional consumption of data in SAP S/4HANA
- B. An extension enhances an existing SAP Fiori UI
- C. An extension is managed independently from SAP S/4HANA
- D. An extension implements reactive (event-based) process extensions
- E. An extension runs in the same logical unit of work (LUW) as an SAP S/4HANA application
Answer: A,C,D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
* Decoupled/independent management (A): RAP and ABAP Cloud allow extension providers to develop and expose their own services based on released interfaces-reflecting independent lifecycle and management, typical of side-by-side.
* Own data model with occasional consumption (B): The platform supports consuming remote services and exposing APIs-patterns consistent with side-by-side extensions that keep their own data model and integrate when needed.
* Event-based/reactive (C): RAP natively supports an event-driven architecture with asynchronous, decoupled communication-ideal for side-by-side process extensions reacting to business events.
* Not same LUW (D is wrong): Remote communication is asynchronous and keeps LUWs separate- indicative of side-by-side, not in-app (same-stack) processing.
NEW QUESTION # 13
Given the following Core Data Service view entity data definition:
@AccessControl.authorizationCheck: #NOT_REQUIRED
DEFINE VIEW ENTITY demo_cds_param_view_entity
WITH PARAMETERS
p_date : abap.dats
AS SELECT FROM sflight
{
key carrid,
key connid,
key fldate,
price,
seatsmax,
seatsocc
}
WHERE fldate >= $parameters.p_date;
Which of the following ABAP SQL snippets are syntactically correct ways to provide a value for the parameter on line #4?
Note: There are 2 correct answers to this question.
- A. SELECT * FROM demo_cds_param_view_entity( p_date = `20230101` ) ...
- B. SELECT * FROM demo_cds_param_view_entity( p_date = '20230101' ) ...
- C. SELECT * FROM demo_cds_param_view_entity( p_date = :$session.system_date ) ...
- D. SELECT * FROM demo_cds_param_view_entity( p_date = @(
cl_abap_context_info=>get_system_date( ) ) ) ...
Answer: B,D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Parameters in CDS view entities (WITH PARAMETERS) must always be supplied when querying. In ABAP SQL, the syntax rules are:
* A. CorrectSupplying a literal date ('20230101') directly is valid because the parameter p_date is of type abap.dats.
* B. CorrectSupplying a value via an ABAP expression using @( ... ) is syntactically correct. Here, cl_abap_context_info=>get_system_date( ) returns the current system date in ABAP Cloud-compliant way, and is wrapped with @() for expression embedding. This is the best practice in ABAP Cloud development.
* C. IncorrectBackticks (`...`) are used in ABAP for string templates, not for literals in this context. A date literal must be in quotes '...'.
* D. Incorrect:$session.system_date is not valid in ABAP SQL. Session variables like $session.* are supported in HANA SQL, but in ABAP CDS view consumption via ABAP SQL, this is not allowed.
Therefore, only A and B are correct.
Reference:ABAP CDS Development User Guide - section on CDS View Entity Parameters and ABAP SQL parameter passing rules; ABAP Cloud development guidelines on cl_abap_context_info=>get_system_date.
NEW QUESTION # 14
How can you execute test classes? (Select 3)
- A. Interactively during the release of transport request.
- B. As a mass test when releasing a transport request with the ABAP Transport Organizer.
- C. As a mass test when executing an ABAP Test Cockpit (ATC) check variant.
- D. Interactively by calling function "Run as a unit test" from within the test class.
- E. Interactively by calling function "Run as a unit test" from within the tested object.
Answer: C,D,E
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
* Interactive runs from the tested object or its test class in ADT: In RAP/ABAP Cloud test guides, you specify a test relation, which then lets you run unit tests directly from the context menu of the behavior definition (tested object) in ADT. This is the "Run as unit test" interaction from the tested object.
* Interactive runs from the test class itself: Test classes are declared with FOR TESTING, and the same RAP guides show the canonical test-class structure used for ABAP Unit. In ADT, you can execute the test class via its context menu ("Run as Unit Test").
* Mass execution with ATC: The same document set prescribes governance via ABAP Test Cockpit (ATC) check variants applied across many objects, supporting mass test/check execution. ATC is used broadly to enforce ABAP Cloud rules and quality gates across developments, which covers running checks/tests at scale (mass).
* There is no built-in mechanism to execute unit tests during transport release; the recommended mass execution path is via ATC, not via the Transport Organizer. (Hence B and E are not correct.)
NEW QUESTION # 15
Which of the following enforce ABAAP Cloud rules? Note: There are 2 correct answers to this question.
- A. ABAP platform reuse services
- B. ABAP runtime checks
- C. ABAP compiler
- D. ABAP release contracts
Answer: B,C
NEW QUESTION # 16
What are advantages of using a field symbol for internal table row access? Note: There are answers to this question.
- A. A MODIFY statement to write changed contents back to the table is not required.
- B. Using a field symbol is faster than using a work area.
- C. The row content is copied to the field symbol instead to a work area
- D. The field symbol can be reused for other programs.
Answer: A,B
Explanation:
A field symbol is a pointer that allows direct access to a row of an internal table without copying it to a work area. Using a field symbol for internal table row access has some advantages over using a work area, such as12:
A MODIFY statement to write changed contents back to the table is not required: This is true. When you use a work area, you have to copy the row content from the internal table to the work area, modify it, and then copy it back to the internal table using the MODIFY statement. This can be costly in terms of performance and memory consumption. When you use a field symbol, you can modify the row content directly in the internal table without any copying. Therefore, you do not need the MODIFY statement12.
Using a field symbol is faster than using a work area: This is true. As explained above, using a field symbol avoids the overhead of copying data between the internal table and the work area. This can improve the performance of the loop considerably, especially for large internal tables. According to some benchmarks, using a field symbol can save 25-40% of the runtime compared to using a work area12.
You cannot do any of the following:
The field symbol can be reused for other programs: This is false. A field symbol is a local variable that is only visible within the scope of its declaration. It cannot be reused for other programs unless it is declared globally or passed as a parameter. Moreover, a field symbol must have the same type as the line type of the internal table that it accesses. Therefore, it cannot be used for any internal table with a different line type12.
The row content is copied to the field symbol instead to a work area: This is false. As explained above, using a field symbol does not copy the row content to the field symbol. Instead, the field symbol points to the memory address of the row in the internal table and allows direct access to it. Therefore, there is no copying involved when using a field symbol12.
NEW QUESTION # 17
You want to document a global class with ABAP Doc.
What do you need to consider? Note: There are 3 correct answers to this question.
- A. The documentation can be translated.
- B. The documentation starts with "!
- C. The documentation can contain links to other repository object's documentation.
- D. The documentation may contain tags like <strong></strong>.
- E. The documentation has to be positioned directly after the declarative statement.
Answer: A,C,E
NEW QUESTION # 18
After you created a database table in the RESTful Application Programming model, what do you create next?
- A. A projection view
- B. A data model view
- C. A metadata extension
- D. A service definition
Answer: A
Explanation:
After you created a database table in the RESTful Application Programming model (RAP), the next step is to create a projection view on the database table. A projection view is a CDS artefact that defines a view on one or more data sources, such as tables, views, or associations. A projection view can select, rename, or aggregate the fields of the data sources, but it cannot change the properties of the fields, such as whether they are read-only or not. The properties of the fields are inherited from the data sources or the behaviour definitions of the business objects12. For example:
The following code snippet defines a projection view ZI_AGENCY on the database table /DMO/AGENCY:
define view ZI_AGENCY as select from /dmo/agency { key agency_id, agency_name, street, city, region, postal_code, country, phone_number, url } The projection view is used to expose the data of the database table to the service definition, which is the next step in the RAP. The service definition is a CDS artefact that defines the interface and the binding of a service. A service is a CDS entity that exposes the data and the functionality of one or more business objects as OData, InA, or SQL services. A service definition can specify the properties of the fields of a service, such as whether they are filterable, sortable, or aggregatable12. For example:
The following code snippet defines a service definition ZI_AGENCY_SRV that exposes the projection view ZI_AGENCY as an OData service:
define service ZI_AGENCY_SRV { expose ZI_AGENCY as Agency; }
You cannot do any of the following:
A . A metadata extension: A metadata extension is a CDS artefact that defines additional annotations for a CDS entity, such as a business object, a service, or a projection view. A metadata extension can specify the properties of the fields of a CDS entity for UI or analytical purposes, such as whether they are visible, editable, or hidden. However, a metadata extension is not the next step after creating a database table in the RAP, as it is not required to expose the data of the database table to the service definition. A metadata extension can be created later to customize the UI or analytical application that uses the service12.
C . A data model view: A data model view is a CDS artefact that defines a view on one or more data sources, such as tables, views, or associations. A data model view can select, rename, or aggregate the fields of the data sources, and it can also change the properties of the fields, such as whether they are read-only or not. The properties of the fields are defined by the annotations or the behaviour definitions of the data model view. A data model view is used to define the data model of a business object, which is a CDS entity that represents a business entity or concept, such as a customer, an order, or a product. However, a data model view is not the next step after creating a database table in the RAP, as it is not required to expose the data of the database table to the service definition. A data model view can be created later to define a business object that uses the database table as a data source12.
D . A service definition: A service definition is a CDS artefact that defines the interface and the binding of a service. A service is a CDS entity that exposes the data and the functionality of one or more business objects as OData, InA, or SQL services. A service definition can specify the properties of the fields of a service, such as whether they are filterable, sortable, or aggregatable. However, a service definition is not the next step after creating a database table in the RAP, as it requires a projection view or a data model view to expose the data of the database table. A service definition can be created after creating a projection view or a data model view on the database table12.
NEW QUESTION # 19
You want to extract date information of a flight date (f_info) and format it like yyyy-dd-mm using the following code:
For the extract_*functions to work,, what can be the data dictionary types of f_info? Note: There are 3 correct answers to this question.
- A. DATS
- B. TIMS
- C. TIMN
- D. TIMESTAMP
- E. UTCLONG
Answer: A,B,D
NEW QUESTION # 20
Given the following code,
DATA gv_text1 TYPE string. "#EC_NEEDED
DATA gv_text2 TYPE string ##NEEDED.
What are valid statements? Note: There are 2 correct answers to this question.
- A. ##NEEDED is checked by the syntax checker.
- B. #EC_NEEDED is not checke d by the syntax checker.
- C. The pragma is not checked by the syntax checker.
- D. The pseudo-comment is checked by the syntax checker.
Answer: A,B
NEW QUESTION # 21
Which of the following are reasons that SAP recommends developing Core Data Services view entities as opposed to classic Core Data Services DDIC-based views?
Note: There are 2 correct answers to this question.
- A. Simplified syntax check
- B. Simpler and stricter syntax
- C. Elimination of the need for a database view
- D. Automated client handling
Answer: B,C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
SAP recommends using CDS view entities over classic CDS DDIC-based views due to the following benefits:
* Simpler and stricter syntax: CDS view entities enforce a clearer separation of concerns and reduce ambiguity, which helps ensure consistency across the stack. This makes Option C correct.
* Elimination of the need for a database view: With CDS view entities, there's no dependency on a separate DDIC SQL view object, reducing redundancy and improving activation performance. This makes Option D correct.
Incorrect options:
* Automated client handling (Option A) is supported in both CDS view entities and classic CDS views via annotations like @ClientHandling.
* Simplified syntax check (Option B) is not a distinct feature of CDS view entities. Syntax checking is part of ABAP Development Tools regardless of the CDS flavor used.
Reference: ABAP CDS Development User Guide, section 2.2 - Data Definitions and advantages of using CDS view entities over classic CDS views.
NEW QUESTION # 22
Why would you use Access Controls with CDS Views? Note: There are 2 correct answers to this question.
- A. You do not have to remember to implement AUTHORITY CHECK statements.
- B. Only the data corresponding to the user's authorization is transferred from the database to the application layer.
- C. The system field sy-subrc is set, giving you the result of the authorization check
- D. All of the data from the data sources is loaded into your application automatically and filtered there according to the user's authorization.
Answer: A,B
Explanation:
You would use Access Controls with CDS Views for the following reasons:
A . Only the data corresponding to the user's authorization is transferred from the database to the application layer. This is true because Access Controls allow you to define CDS roles that specify the authorization conditions for accessing a CDS view. The CDS roles are evaluated for every user at runtime and the system automatically adds the restrictions to the selection conditions of the CDS view. This ensures that only the data that the user is authorized to see is read from the database and transferred to the application layer. This improves the security and the performance of the data access1.
C . You do not have to remember to implement AUTHORITY CHECK statements. This is true because Access Controls provide a declarative and centralized way of defining the authorization logic for a CDS view. You do not have to write any procedural code or use the AUTHORITY CHECK statement to check the user's authorization for each data source or field. The system handles the authorization check automatically and transparently for you2.
The following reasons are not valid for using Access Controls with CDS Views:
B . The system field sy-subrc is set, giving you the result of the authorization check. This is false because the system field sy-subrc is not used by Access Controls. The sy-subrc field is used by the AUTHORITY CHECK statement to indicate the result of the authorization check, but Access Controls do not use this statement. Instead, Access Controls use CDS roles to filter the data according to the user's authorization2.
D . All of the data from the data sources is loaded into your application automatically and filtered there according to the user's authorization. This is false because Access Controls do not load all the data from the data sources into the application layer. Access Controls filter the data at the database layer, where the data resides, and only transfer the data that the user is authorized to see to the application layer. This reduces the data transfer and the memory consumption of the application layer1.
NEW QUESTION # 23
What describes multi-column internal tables?
- A. They are based on a structured row type.
- B. They must contain nested components.
- C. They use one incomplete data type.
- D. They use one complete data type.
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
Multi-column internal tables are defined using a structured row type, meaning each row is defined by a structure (either defined inline or as a global structure type in the Dictionary).
* Option B is correct because it describes how internal tables with multiple fields are built using structured rows.
* Option A is incorrect because the row type must be complete and consistent.
* Option C is incorrect because nested components are not a requirement.
* Option D is misleading. Though "complete data type" may sound correct, it lacks specificity. The correct technical description is that the row type is a structure.
Reference: ABAP CDS Development User Guide, section on internal table handling in ABAP objects and syntax examples.
NEW QUESTION # 24
While debugging an ABAP program, you want the program to stop whenever the value of a variable changes. Which of the following do you use?
- A. Exception breakpoint
- B. Conditional breakpoint
- C. Watchpoint
Answer: C
NEW QUESTION # 25
You want to join two database tables, T_CARRIER, and T_CONNECTIONS, to retrieve all carriers, whether they have corresponding connections or not.
Which statements would achieve this? Note: There are 2 correct answers to this question.
- A. SELECT FROM carrier INNERR JOIN t_connections ON...
- B. SELECT FROM connections RIGHT OUTER JOIN t_carrier ON...
- C. SELECT FROM carrier LEFT OUTER JOIN t_connectionsON...
- D. SELECT FROM carrier LEFT INNER JOIN t_connectionsON..
Answer: B,C
NEW QUESTION # 26
Which type of legacy code does SAP recommend you eliminate when you review modifications as part of an SAP S/4HANA system conversion? Note: There are 2 correct answers to this question.
- A. Code that can be redesigned as a key user extension
- B. Code that now is identical to a standard SAP object
- C. Code that supports a critical business process
- D. Code that has less than 10% usage according to usage statistics
Answer: A,B
Explanation:
SAP recommends that you eliminate the following types of legacy code when you review modifications as part of an SAP S/4HANA system conversion:
Code that now is identical to a standard SAP object. This type of code is redundant and unnecessary, as it does not provide any additional functionality or customization. It can also cause conflicts or errors during the system conversion, as the standard SAP object may have changed or been replaced in SAP S/4HANA. Therefore, you should delete this type of code and use the standard SAP object instead.
Code that can be redesigned as a key user extension. This type of code is usually related to UI or business logic adaptations that can be achieved using the in-app tools provided by SAP S/4HANA. By redesigning this type of code as a key user extension, you can simplify and standardize your code base, reduce maintenance efforts, and avoid compatibility issues during the system conversion. Therefore, you should migrate this type of code to the key user extensibility framework and delete the original code.
The other types of legacy code are not recommended to be eliminated, as they may still be relevant or necessary for your business processes. However, you should still review and adjust them according to the SAP S/4HANA simplification items and best practices. These types of code are:
Code that supports a critical business process. This type of code is essential for your business operations and cannot be easily replaced or removed. However, you should check if this type of code is compatible with SAP S/4HANA, and if not, you should adapt it accordingly. You should also consider if this type of code can be optimized or enhanced using the new features and capabilities of SAP S/4HANA.
Code that has less than 10% usage according to usage statistics. This type of code is rarely used and may not be worth maintaining or converting. However, you should not delete this type of code without verifying its relevance and impact on your business processes. You should also consider if this type of code can be replaced or consolidated with other code that has higher usage or better performance.
NEW QUESTION # 27
In ABAP SQL, which of the following can be assigned an alias? Note: There are 2 correct answers to this question.
- A. database table
- B. field (from field list)
- C. order criterion (from order by clause)
- D. group criterion (from group by clause)
Answer: A,B
Explanation:
In ABAP SQL, an alias is a temporary name that can be assigned to a field or a database table in a query. An alias can be used to make the query more readable, to avoid name conflicts, or to access fields or tables with long names. An alias is created with the AS keyword and is only valid for the duration of the query1.
The following are examples of how to assign an alias to a field or a database table in ABAP SQL:
B . field (from field list): A field is a column of a table or a view that contains data of a certain type. A field can be assigned an alias in the field list of a SELECT statement, which specifies the fields that are selected from the data source. For example, the following query assigns the alias name to the field carrname of the table scarr:
SELECT carrid, carrname AS name FROM scarr.
The alias name can be used instead of carrname in other clauses of the query, such as WHERE, GROUP BY, ORDER BY, and so on2.
C . database table: A database table is a collection of data that is organized in rows and columns. A database table can be assigned an alias in the FROM clause of a SELECT statement, which specifies the data source that is selected from. For example, the following query assigns the alias c to the table scarr:
SELECT c.carrid, c.carrname FROM scarr AS c.
The alias c can be used instead of scarr in other clauses of the query, such as WHERE, JOIN, GROUP BY, ORDER BY, and so on3.
The following are not valid for assigning an alias in ABAP SQL:
A . order criterion (from order by clause): An order criterion is a field or an expression that is used to sort the result set of a query in ascending or descending order. An order criterion cannot be assigned an alias in the ORDER BY clause of a SELECT statement, because the alias is not visible in this clause. The alias can only be used in the clauses that follow the clause where it is defined1.
D . group criterion (from group by clause): A group criterion is a field or an expression that is used to group the result set of a query into subsets that share the same values. A group criterion cannot be assigned an alias in the GROUP BY clause of a SELECT statement, because the alias is not visible in this clause. The alias can only be used in the clauses that follow the clause where it is defined1.
NEW QUESTION # 28
Setting a field to read-only in which object would make the field read-only in all applications of the RESTful Application Programming model?
- A. Projection view
- B. Service definition
- C. Behaviour definition
- D. Metadata extension
Answer: C
NEW QUESTION # 29
When you work with a test class you can set up some prerequisites before the actual testing.
In which sequence will the following fixtures be called by the test environment?
- A. setup()
- B. teardown()
- C. class_setup()
- D. class_teardown()
Answer: A,B,C,D
NEW QUESTION # 30
You want to define the following CDS view entity with an input parameter:
define view entity Z_CONVERT
with parameters i_currency : ???
Which of the following can you use to replace ????
(Select 2 correct answers)
- A. A built-in ABAP type
- B. A built-in ABAP Dictionary type
- C. A data element
- D. A component of an ABAP Dictionary structure
Answer: B,C
Explanation:
Comprehensive and Detailed Explanation from Exact Extract:
CDS view parameters must be defined with types that are visible in the ABAP Dictionary.
* A. Built-in ABAP Dictionary type # # Supported (e.g., CURR, CHAR).
* D. Data element # # Supported, as data elements are dictionary-level types.
* B. Built-in ABAP type (like i, string) # # Not supported directly, CDS requires dictionary-compatible types.
* C. Component of a structure # # Not supported directly; parameters cannot reference structure components.
This ensures that CDS definitions remain database-compatible and semantically rich, which is critical for RAP services.
Verified Study Guide Reference: ABAP CDS Development Guide - Defining View Parameters.
NEW QUESTION # 31
Which of the following ON conditions must you insert in place of "???"?
- A. ON Sprojection. Carrier Source2.carrier
- B. ON Sprojection.carrier_id=Z_Source2.carrier_id
- C. ON Z_Sourcel.camer_id = 7_Source2 carrier_id
- D. ON Sprojection Camer=Source2 carrier_id
Answer: B
Explanation:
The correct ON condition that must be inserted in place of "???" is:
ON Sprojection.carrier_id=Z_Source2.carrier_id
This ON condition specifies the join condition between the CDS view Sprojection and the database table Z_Source2. The join condition is based on the field carrier_id, which is the primary key of both the CDS view and the database table. The ON condition ensures that only the records that have the same value for the carrier_id field are joined together1.
The other options are not valid ON conditions, because:
A . ON Z_Sourcel.camer_id = 7_Source2 carrier_id is not valid because Z_Sourcel and 7_Source2 are not valid data sources in the given code. There is no CDS view or database table named Z_Sourcel or 7_Source2. The correct names are Z_Source1 and Z_Source2. Moreover, the field camer_id is not a valid field in the given code. There is no field named camer_id in any of the data sources. The correct name is carrier_id.
B . ON Sprojection Camer=Source2 carrier_id is not valid because Sprojection and Source2 are not valid data sources in the given code. There is no CDS view or database table named Sprojection or Source2. The correct names are Sprojection and Z_Source2. Moreover, the field Camer is not a valid field in the given code. There is no field named Camer in any of the data sources. The correct name is carrier_id. Furthermore, the ON condition is missing the dot (.) operator between the data source name and the field name, which is required to access the fields of the data source1.
C . ON Sprojection. Carrier Source2.carrier is not valid because Carrier and carrier are not valid fields in the given code. There is no field named Carrier or carrier in any of the data sources. The correct name is carrier_id. Moreover, the ON condition is missing the dot (.) operator between the data source name and the field name, which is required to access the fields of the data source1.
NEW QUESTION # 32
When processing an internal table with the statement LOOP AT itab... ENDLOOP, what system variable contains the current row number?
- A. sy-subrc
- B. sy-index
- C. sy-linno
- D. sy-tabix
Answer: D
Explanation:
When processing an internal table with the statement LOOP AT itab... ENDLOOP, the system variable that contains the current row number is sy-tabix. The sy-tabix variable is a predefined field of the system structure sy that holds the index or the row number of the current line in an internal table loop. The sy-tabix variable is initialized with the value 1 for the first loop pass and is incremented by 1 for each subsequent loop pass. The sy-tabix variable can be used to access or modify the current line of the internal table using the index access12.
NEW QUESTION # 33
In a CDS view, where can a value help be defined?
- A. In an annotation
- B. In a view definition
- C. In an association
- D. In the SQL console
Answer: A
NEW QUESTION # 34
Which of the following actions cause an indirect change to a database table requiring a table conversion? Note: There are 2 correct answers to this question.
- A. Renaming a field in a structure that is included in the table definition.
- B. Deleting a field from a structure that is included in the table definition.
- C. Changing the field labels of a data element that is used in the table definition.
- D. Shortening the length of a domain used in a data element that is used in the table definition.
Answer: B,D
NEW QUESTION # 35
......
Exam Dumps C_ABAPD_2507 Practice Free Latest SAP Practice Tests: https://www.testsimulate.com/C_ABAPD_2507-study-materials.html