Scribd
Upload
166 views

The Ultimate C - C - FIORDEV - 21 - SAP Certified Development Associate - SAP Fiori Application Developer

C_FIORDEV_21 - SAP Certified Development Associate - SAP Fiori Application Developer Certification Exam Credential. The sources for the unmanaged reference scenario has been updated with the latest features. You can explore the new features in the sources that you can download from GitHub and in the related description in the guide on how to develop unmanaged transactional apps based on existing application logic. Mapping CDS names to database field names

Uploaded by

Stefan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
166 views

The Ultimate C - C - FIORDEV - 21 - SAP Certified Development Associate - SAP Fiori Application Developer

C_FIORDEV_21 - SAP Certified Development Associate - SAP Fiori Application Developer Certification Exam Credential. The sources for the unmanaged reference scenario has been updated with the latest features. You can explore the new features in the sources that you can download from GitHub and in the related description in the guide on how to develop unmanaged transactional apps based on existing application logic. Mapping CDS names to database field names

Uploaded by

Stefan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
You are on page 1/ 3

The Ultimate C_C_FIORDEV_21 - SAP Certified

Development Associate - SAP Fiori Application


Developer

C_FIORDEV_21 - SAP Certified Development Associate - SAP Fiori Application Developer


Certification Exam Credential. The sources for the unmanaged reference scenario has been updated
with the latest features. You can explore the new features in the sources that you can download from
GitHub and in the related description in the guide on how to develop unmanaged transactional apps based
on existing application logic.
Mapping CDS names to database field names

By defining a mapping specification in the behavior definition, you can use the mapping operator in the
behavior implementation to write records to the database that have a discrepancy between the names of
the database table fields and the CDS view field names.

For more information, see the information for mapping in Adding Behavior to the Business Object and
the implementation in Implementing the CREATE Operation for Travel Instances.

Message handling

The behavior processing framework provides a message object that can be used for message handling in
the behavior pool. New message handling has been added to the unmanaged scenario. The corresponding
methods are implemented in an auxiliary class that inherits from cl_abap_behv and called from the
behavior handler.

For more information, see the information about message handling in Implementing the CREATE
Operation for Travel Instances.

Authorizations Checks for Modifying Operations in Managed Business Objects


To protect data from unauthorized read access, the ABAP CDS provides its own authorization concept
based on a data control language (DCL). The authorization checks for read operations allow you to limit
the results returned by an entity to those results you authorize a user to see.
For business objects that are implemented for managed contract, also modifying operations in such as
standard operations create, update, delete, create by associations, and actions must be checked against
unauthorized access. With the current release, the instance-based authorization control is supported.

For more information, see Authorization Control.

Adding Dynamic Feature Control


Apart from static feature control, you can now also use dynamic feature control. In this case, it depends
on a state of the node instance if certain elements or actions are available.

Dynamic feature control is defined in the behavior definition:


...
define behavior for /DMO/I_TRAVEL_M

field (features : instance ) travel_id;


action ( features: instance ) acceptedTravel result [1] $self;

The implementation for the control must then be implemented in the respective methods in the behavior
pool. For example, for this behavior definition, you can implement that the field travel_id is mandatory on
create, but read-only on the update operation. The action can be implemented as disabled if the travel
entity is already set to accepted, but enabled if it is not yet accepted.
For more information, see Feature Control.

Exploring Business Objects


A business object consists of hierarchical connected entities. The behavior for each entity is defined in the
behavior definition object and implemented in the behavior classes. In the Relation Explorer, you can see
structure and behavior of a certain business object independent of the technical location. You can navigate
to all the entities and the corresponding behavior (definition and implementation).

Sometimes you might be interested in more CDS-specific aspects and want to see access control lists or
test classes. You can achieve this by switching the context from Business Object to Core Data Services
context, as you can see in the following animation.
Service Consumption Model Wizard
In the service consumption model creation wizard:
ETag support can now be selected for any entity set. If ETag support is marked in your edmx file, the
Etag support checkbox is selected by default.

You might also like