In a subclass sub1, you want to redefine a component of a superclass super1.
How do you achieve this?
Note: There are 2 correct answers to this question.
To redefine a component in a subclass:
The component (method) in the superclass must be defined with the FOR REDEFINITION addition.
In the subclass, you use the REDEFINITION clause in the method declaration and implement the method in the subclass to override the superclass behavior.
Thus:
Option A is correct because the method declaration in sub1 must include the REDEFINITION addition.
Option D is correct because the actual redefined method implementation must be provided in the subclass sub1.
Option B is incorrect because the component is not re-implemented in the superclass.
Option C is incorrect because REDEFINITION is not added in the superclass, but FOR REDEFINITION is.
===========
Which language is used to add or change data of a business object in RAP?
In RAP, changes to business object data are performed using Entity Manipulation Language (EML).
It provides ABAP statements such as READ ENTITIES, MODIFY ENTITIES, CREATE, and DELETE for RAP BOs.
EML is the cloud-compliant equivalent of SQL DML (insert/update/delete) but tailored to RAP's transactional consistency.
Verified Study Guide Reference: RAP Programming Model -- Entity Manipulation Language (EML).
In RESTful Application Programming, a business object contains which parts?
Note: There are 2 correct answers to this question.
In the RAP model, a Business Object (BO) is composed of the following key parts:
A CDS view, which defines the data model layer (entity structure, projections, associations).
A Behavior Definition (BDEF), which defines the behavior layer -- what operations can be performed (create, update, delete, validations, determinations).
Therefore:
Option B and C are correct.
Option A is incorrect because 'Process definition' is not a RAP construct; process logic is handled via behavior implementation and determinations.
Option D is incorrect because 'Authentication rules' are managed externally (e.g., via IAM, authorizations), not inside the BO.
===========
Which of the following rules apply for dividing with ABAP SQL?
Note: There are 3 correct answers to this question.
In ABAP SQL, the handling of arithmetic operations --- especially division --- is handled with care for data types and precision. Here's how each applies:
B . Numeric function division(numerator, denominator, decimal places) accepts decimal input
This is correct. The division function is designed for decimal-based calculations, where precision control is needed via the third parameter (number of decimal places). It supports packed numbers (DEC).
C . Numeric function div(numerator, denominator) expects only integer input
This is correct. The div function is an integer division operator, returning an integer result and only accepts integers as input types.
E . Numeric function division(numerator, denominator, decimal places) accepts floating point input
This is correct. In addition to decimals, division() can also work with floating point types (FLTP), enabling flexible division where decimals are not sufficient.
A . The division operator ''/'' accepts decimal input
This is incorrect in the context of ABAP SQL. The / operator is not available as a built-in operator in Open SQL; arithmetic operations like this are not supported with native operators --- only via functions.
D . The division operator ''/'' accepts floating point input
Again, this is incorrect, as / is not valid syntax in ABAP SQL queries. Only built-in functions like div or division are supported in the CDS/Open SQL layer.
ABAP CDS Development Guide, section 2.2 -- Built-in functions in ABAP SQL and CDS expressions for numerical calculations, specifically division() and div().
You have the following CDS definition (aliases shown):
define view entity Z_ENTITY
as select from Z_SOURCE1 as _Source1
association to Z_SOURCE2 as Source2 on ???
{
key carrier_id as Carrier,
key connection_id as Connection,
cityfrom as DepartureCity,
cityto as ArrivalCity,
Source2
}
(The data sources are joined by the field carrier_id. The corresponding field in Z_SOURCE2 is also carrier_id.)
Which ON condition must you insert?
In a CDS view entity defined AS SELECT FROM, the association ON condition must use the source aliases defined in the FROM clause.
$projection is used in projection views (AS PROJECTION ON ...), not in a basic select view entity. Therefore, options using $projection (B, C) are invalid here.
Using global names (Z_SOURCE1, Z_SOURCE2) in the ON (A) ignores the declared aliases and is not the recommended/valid form within the view definition.
The correct ON clause uses the aliases _Source1 and Source2 with the matching key fields:
ON _Source1.carrier_id = Source2.carrier_id (D).
This aligns with CDS modeling rules in RAP: use aliases consistently and model associations with precise ON conditions based on keys.
Study Guide Reference: ABAP CDS Development---Associations & ON conditions; RAP Data Modeling.
Rossana
1 month agoErick
2 months agoFairy
2 months agoLyda
2 months agoMona
2 months agoTyisha
3 months agoTamar
3 months agoNida
3 months agoTambra
3 months agoCherilyn
4 months agoLorean
4 months agoAnnamae
4 months agoAnnett
4 months agoMauricio
5 months agoStevie
5 months agoHorace
5 months agoMerlyn
5 months agoHelga
6 months agoCaitlin
6 months agoJanessa
6 months agoMaile
6 months ago