The Ultimate C_ C_TS460_1909 - SAP Certified

Application Associate - SAP S4HANA Sales 1909

Upskilling

C_TS460_1909 - SAP Certified Application Associate - SAP S4HANA Sales 1909 Upskilling Certification
Exam Credentials. You can now use mandatory: create to assure that a field is filled in during a create
operation and read only: update to assure that the field value isn't changed during modify operations.

For more information, see Feature Control Definition: Fields

Possibly Incompatible Changes for ABAP RESTful Application Programming

You can find an overview of possibly incompatible changes for the ABAP RESTful Application
Programming in SAP Note 2943761 Information published on SAP site.

Implementing Own Locking Logic for Managed Business Objects

You can now define an unmanaged lock in a managed scenario. The unmanaged lock mechanism must
be defined in the behavior definition with the syntax lock master unmanaged and implemented in the
behavior pool in the method FOR LOCK, just like in an unmanaged scenario. The method is then invoked
during runtime.

For more information, see Pessimistic Concurrency Control (Locking).

Using dependent by _Association in Behavior Definition

You can now use the syntax dependent by _Association for lock, ETag, or authorization dependent
entities. The association to the respective master entity must be explicitly specified in the behavior
definition and implemented when using the unmanaged scenario.

 For more information, see Defining Elementary Behavior for Ready-to-Run Business Object or Adding
Behavior to the Business Object.

Using Client-Independent Tables in Managed Scenarios

The RAP managed BO runtime now supports client-independent database tables.

 For more information, see Using Client-Independent Database Tables in Managed Transactional
Apps.

Dynamic Operation Control for Create By Association

You can now dynamically control the create by association operation. The syntax for defining dynamic
feature control is the following:

_association {create (features: instance); }

Like other feature controls, the control for the create by association must be implemented in the
behavior pool with the method FOR FEATURES.

 For more information, see Dynamic Feature Control: Operations.

New Read-Only Associations in CDS Projection Views

It is now possible to define new read-only associations in the projection view. These associations can be
reused to display additional information in a UI service, for example analytical data which is not part of
the transactional basic business object. With associations in projection views, you can model new
service-specific relationships.

The syntax for the association definition is the same as in CDS views:

association [min..max] to TargetEntity [as _Alias] on OnCondition

 For more information, see CDS Projection View.

Filtering for Null Values in OData V2 Services

OData does not foresee initial values for the following EDM data types: Fiori Elements UIs offer the
empty operator in filter bars for these fields. Although they appear as visually empty in the UIs, the
actual value sent to the client is null.

To be able to select records with empty values for these data types, the client filters null values and the
filter is transformed to filter for initial values for the backend. Real null values cannot be retrieved from
the database by filtering for them in OData V2.