Field Mapping - Complete List

 

In the most complete form, the mapping contains a full list of all field names, with the CDS element names on the left and the DB table field names on the right.

 

Field Mapping - Addition Corresponding

 

By adding the corresponding keyword, the framework implicitly maps all fields for which the CDS element name and the database table name only differ in upper or lower case. Then, only the fields for which this is not the case need explicit mapping.

 

Behavior Projection

The Behavior Projection

 

The general business object defines and implements the behavior of what can be done in general with the data provided by the data model. The BO projection defines only the behavior that is relevant for the specific service.

 

The projection behavior definition delegates to the underlying layer. The implementation of the individual characteristics is only done in the general BO.

Create a New Behavior Projection (1)

 

The procedure to create a behavior projection is identical to the creation of a behavior definition. The only difference is that you create the repository object based on the projection view of a root entity rather than the data model view.

 

Create a New Behavior Definition (2)

 

When creating a behavior definition based on a CDS view that is of type projection view, the implementation is automatically set to Projection and no other value is supported.

 

Minimal Syntax of Behavior Projection

The minimal syntax of a behavior projection includes key word projection and the behavior definition for at least one projection view, that is the projection view of the BO root entity.

 

If the behavior definition of an entity contains standard operations (create, update, delete), the template for behavior projections adds the standard operations to the projection by default. They are not mandatory and can be commented out or removed if not required.