You are on page 1of 2

The Ultimate C_ C_TFIN22_67 - SAP Certified

Application Associate - Management Accounting with


SAP ERP 6.0 EhP7

C_TFIN22_67 - SAP Certified Application Associate - Management Accounting with SAP ERP 6.0 EhP7
Certification Exam Credential Using Wildcards for Code Completion in the CDS Source Code Editor

You can now use wildcards like the asterisk (*) to limit the list of relevant entries if you do not know the
qualified name of the identifier.

To benefit from this feature, start typing a character in the CDS source code editor and add the asterisk
to complete your search string. Finally, trigger code completion ( Ctrl + Space ) and takeover the relevant
proposal from the code completion list. The selected finding will then be added.

Using the asterisk at the leading position is not supported.

If you use several segments within a identifier path, only the asterisk in the last segment is supported.

For more information, see Code Completion

Using Troubleshooting Tools

Changing Scalar Variables While Debugging an AMDP

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:

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.

You might also like