0% found this document useful (0 votes)
57 views2 pages

The Ultimate C - C - SEN - 2011 - SAP Certified Application Associate - SAP Enable Now

You are on page 1/ 2

The Ultimate C_ C_SEN_2011 - SAP Certified

Application Associate - SAP Enable Now

C_SEN_2011 - SAP Certified Application Associate - SAP Enable Now Certification Exam Credential.
You can now change the value of a variable while debugging an AMDP method, for example, to test the
subsequent SQLScript code.

You can trigger this function from the Change Value dialog in the Variables view while debugging an
AMDP. To open this dialog, select the relevant variable and choose Change Variable... from the context
menu.
Dialog to change the value of scalar variables
For more information, see Changing Scalar Variables

Installing ADT on the Open Eclipse 2019-09 (4.13) Platform*


You can now install the ADT client on the latest Eclipse 2019-09 (4.13) platform.

This ADT client version supports the following Eclipse platforms:

2019-09 (4.13)
2019-06 (4.12)
For more information, see
Installing ABAP Development Tools
Eclipse 4.13 - New and NoteworthyInformation published on non-SAP site.
ABAP RESTful Programming Model
Defining the Service Namespace for OData Services
You can now define the OData service namespace in service definitions with the annotation
@OData.schema.name.

For more information, see OData Annotations.

Filling the Result Parameter for Actions


A runtime check is introduced to enforce the proper assignment of result values in action implementations
when result parameters are declared in the corresponding action definition. Whereas actions returned the
input entity if the result parameter was not filled in the action implementation before 1911, they now
return the value of the result parameter as specified in the action definition and exactly according to its
implementation.

To avoid that a Fiori UI shows initial values, if nothing is returned, you must fill the result parameter for
all actions.

For more information, see Developing Actions and Implementing the SET_STATUS_BOOKED Action.

Navigating More Than One Step in OData Requests


It is now possible to navigate to associated entities using more than one navigation for both, V2 and V4
services.
You can link an unlimited number of entities in one OData request.
Outsourcing UI Metadata in Metadata Extensions
You can now use metadata extensions to define CDS annotations outside of the corresponding data
definition of the CDS projection view. The use of metadata extensions allows the separation of concerns
by separating the data model from domain-specific semantics, such as UI-related information for UI
consumption.

For more information, see Adding UI Metadata to the Data Model.


Using Type and Control Mapping
You can now define a mapping contract for applications that include unmanaged or managed business
objects based on CDS entities on the one hand, and legacy data types that are generally older and
implement the behavior or parts of it.

The general syntax for field and control (information) mapping in a behavior definition is the following:
For more information, see Using Type and Control Mapping.

Integrating Additional Save in Managed Business Objects


You can now integrate Additional Save for each entity of a given business object with managed
implementation type. This is done in the behavior definition of the business object by adding the keyword
with additional save. The actual implementation of Additional Save takes place in a local saver class as
part of the behavior pool.

You might also like