The Ultimate C_C_S4CSC_2105 - SAP Certified

Application Associate - SAP S4HANA Cloud (public) -

Supply Chain Implementation

C_S4CSC_2105 - SAP Certified Application Associate - SAP S4HANA Cloud (public) - Supply
Chain Implementation Certification Exam Credential. Reporting Messages in ADJUST_NUMBERS
and SAVE
The implicit returning parameter REPORTED is now available for the methods adjust_numbers and save.
By filling this parameter you can report information or success messages after the point of no return in the
save sequence.

For more information, see ADJUST_NUMBERS and SAVE.

Documenting Behavior Definitions

Now you can document behavior definitions in the Knowledge Transfer Document editor.

From the Project Explorer, select the behavior definition you want to document. Use the context menu to
create a knowledge transfer document.
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.
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:
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.

For more information, see Integrating Additional Save in Managed Business Objects.

Integrating Unmanaged Save in Managed Business Objects

You can now integrate Unmanaged Save within the transactional life cycle of managed business objects.
In order to integrate Unmanaged Save into the save sequence as a part of the managed runtime, you must
first add the corresponding syntax (with unmanaged save) to the behavior definition and then implement
the saver handler method as a part of the behavior pool.
For more information, see Integrating Unmanaged Save in Managed Business Objects.

Using Groups for Large Implementations

Until now, the implementation of business object entity's operations and actions had to be done in the
Local Types include of the behavior pool associated with that entity. Since the Local Types include can
only be changed by one developer at a time, the efficiency of development would be significantly reduced
in case of larger implementations. As a solution, the groups can be now used to divide operations, actions
and other implementation-relevant parts of the business logic into several groups for behavior
implementation.