Category: SAP

Preface – This post is part of the SAP ABAP RAP series.

Introduction

In this article, we will see how to create services in SAP RAP (RESTful Application Programming) and consume the same in UI5/Fiori using the given steps:

1. Create service definition
2. Expose entities in the Service Definition
3. Create Service Binding
4. Publish OData service
5. Implement OData in UI5/Fiori

Create Service Definition

Right-click on Package >> New >> Other Repositories Objects >> Service Definition.
Provide the details to create a Service Definition.

Once the Service Definition is created, expose the required entities and activate it.

 

Create Service Binding

Right-click on Package >> New >> Other Repositories Objects >> Service Binding.
Provide Package details, Name, Description and Service Definition name. Additionally, select the Binding Type to create Service Binding.

Verify the information. To expose the service, click on activate.

You can access the metadata details by following the Service URL provided in Service Binding. To preview the application, click on provided Preview button.

How to consume OData create by SAP RAP

Like any other OData created by CDS or SEGW, the OData of SAP RAP can be used similarly in UI5/Fiori Applications. Read more about OData here.

Preface – This post is part of the SAP ABAP RAP series.

Introduction

This article will provide the step-by-step enabling of existing code in RAP. Using the steps below we will learn “Dealing with Existing Code in SAP RAP”.

Steps:

1. Create data model with CDS views
2. Create Behavior Definition
3. Add transactional behaviour in Behavior Definition
4. Create Behavior Pool
5. Implement transactional behavior of the existing application

Create data model with CDS views

Click here to follow step 1

Create Behavior Definition

Procedure

1. Right-click on root CDS view
2. Select New Behavior Definition
3. Provide the details (Name, Description).
4. Select implementation type as unmanaged
5. Click Next and provide the Transport Request number.
6. Select Finish.

Add transactional behaviour in Behavior Definition

Add transactional behavior (Create/Update/Delete/Actions) of business objects.

Create Behavior Pool

You can assign any number of behavior pools to behavior definition. Within a single global class, you can implement multiple local classes which defines the transactional behavior of the business object.

 

Procedure

Behavior Definition >> Right-click >> select New Behavior Implementation >> Provide details >> Finish

Figure 1:Splitting implementation into different behavior pools

 

Figure 2: Behavior Pool

When you go to Local Types in Behavior Pool, you can see below local classes.

Within these local implementation classes, you can implement the business logic of existing behavior objects and test the end-to-end scenario using EML (Entity Manipulation Language) syntax.

Preface – This post is part of the SAP ABAP RAP series.

Introduction

This article will provide a step-by-step guide to enable the transactional behaviour of an application in SAP RAP.

1. Create data model with CDS views
2. Create Behavior Definition
3. Add transactional behaviour in Behavior Definition
4. Create OData service
   1. Create a Service Definition
   2. Expose CDS view
   3. Create Service Binding
   4. Publish OData service
5. Application preview

Create data model with CDS views

Procedure

1. Launch ADT (ABAP Development Tool).
2. Select package for your development.
3. Right-click on package and choose NEW > Other Repository Objects > Core Data Services > Data Definition.
4. Provide the details (Name, Description).
5. Select Next and provide the Transport Request number.
6. Select Finish.
7. Provide the data source name and add the elements in the CDS views.
8. Provide the root statement to the top node as shown below.
   
9. Similarly, create consumption views and add required annotations.

 

Result Screen

Figure 1: Interface view

Figure 2: Consumption view

Create Behavior Definition

Procedure

1. Right-click on root CDS view
2. Select New Behavior Definition
3. Provide the details (Name, Description).
4. Select Next and provide the Transport Request number.
5. Select Finish.

Add transactional behaviour in Behavior Definition

Add transactional behaviour to Behavior Definition as shown below.

Create OData service

a.       Create Service Definition

Procedure

1. Right-click on root CDS view
2. Select New Service Definition
3. Provide the details (Name, Description).
4. Select Next and provide the Transport Request number.
5. Select Finish.

b.      Expose CDS view

 

c.       Create Service Binding

Procedure

1. Right-click on Service Definition
2. Select New Service Binding
3. Provide the details (Name, Description).
4. Select Next and provide the Transport Request number.
5. Select Finish.

d.      Publish OData Service

Application Preview

 

Preface – This post is part of the SAP ABAP RAP series.

Introduction

SAP ABAP RAP provides the intrinsic approach to build SAP Fiori based applications that are optimized for S/4 HANA and can run over on-premise as well as on the cloud. In this article we will learn how to create a SAP ABAP RAP Project.

Prerequisites

Before we start with the development of our first project using SAP ABAP RAP, we need a few things ready:

SAP Cloud Platform ABAP Environment

You should have access to and an account for SAP Cloud Platform ABAP Environment.

Development Environment (IDE)

• Install ABAP Development Toolkit (ADT).

SAP recommends the latest version of the client installation. The download is available on https://tools.hana.ondemand.com/.

• Access to and an account for the relevant space in SAP Cloud Platform Cloud Foundry.

Authorization

To create development artifacts, you need to have a developer role in the ABAP environment.

Basic knowledge

• ABAP Core Data Services (CDS)
• ABAP Objects
• ABAP Syntax

Steps to create a SAP ABAP RAP Project

1. Create an ABAP CDS View enabled with OData. Follow the steps mentioned here. This ABAP CDS View can be either basic, composite or consumption based upon the use case. The basic view is just a simple view created based upon ABAP table, the composite views are the ones that are created using multiple basic views or existing composite views. The consumption is the one that is consumed by the Fiori Apps (other views too can be consumed, it is created with final annotations such that UI5 has to call just this view and not the others).
2. The very next thing that we create in ABAP RAP is a behavior definition. You can read the steps here. A behavior definition is an ABAP repository that represents the behavior of business objects in the context of SAP ABAP RAP. This is the place where we define the CRUD operations for the CDS Views.
3. The last and important step is behavior Implementation. The steps to implement the same is mentioned here. This is the place where business logics are written.

Thus in above steps we have created an ABAP CDS View, an ABAP OData, behavior definition and behavior Implementation.

That’s it, this is how we create a SAP ABAP RAP Project. In our next articles, we will show you the implementation, step by step.

Preface – This post is part of the SAP ABAP RAP series.

Introduction

Using persistent data sources, we are going to implement a query for the OData service to get an application with the read-only feature. This OData service will be consumed by the Fiori Element application.

This article will provide the step-by-step guide to build a read-only list reporting application.

1. Create data model with CDS views.
2. Add associations to CDS views for navigation purpose.
3. Add relevant annotations.
4. Changing UI field labels and description
5. Create OData service
   1. Create a Service Definition
   2. Expose CDS views
   3. Create Service Binding
   4. Publish OData service
6. Application preview

Create data model with CDS views

Procedure

1. Launch ADT (ABAP Development Tool).
2. Select package for your development.
3. Right-click on package and choose NEW > Other Repository Objects > Core Data Services > Data Definition.
4. Provide the details (Name, Description).
   
5. Select Next and provide the Transport Request number.
6. Select Finish.

Result Screen

An inactive version of the data definition is created. You need to provide the data source name and add the elements in the CDS views. Similarly, create all the required CDS views.

Figure 2: Generated Template code

 

Add associations to CDS views for navigation purpose

1. Define association and cardinality
   
2. Define mapping condition
   
3. Add association element list in CDS view
   

Add relevant annotations

Add required annotations to fields (see the below figure).

Changing UI field labels and description

UI field labels and description allows you to customize your UI application. You can add text annotation (@ObjectModel.text.association:'<_AssocToTextProvider>’),value help (@Consumption.valueHelpDefinition: [{ entity: { name: ‘<target_view>’ , element: ‘<target_element>’ }}]), search capability ( @Search.searchable: true ) and as many functionality to your field element.

Create OData service

a.       Create a service definition

In service definition, we will expose our data models.

Procedure

1. Launch ADT (ABAP Development Tool).
2. Select package for your development.
3. Right-click on package and choose NEW > Other Repository Objects > Business Service > Service Definition.
4. Provide the details (Name, Description).
   
5. Select Next and provide the Transport Request number.
6. Select Finish.

 

b.      Expose CDS views

In service definition, add the CDS view that you want to expose to UI. You can provide an alias also for the same. Once the CDS views are exposed, activate the service definition.

c.       Create Service Binding

In service definition, we will expose our data models.

Procedure

1. Launch ADT (ABAP Development Tool).
2. Select package for your development.
3. Right-click on the package and choose NEW > Other Repository Objects > Business Service > Service Binding.
4. Provide the details (Name, Description).
   
5. Select Next and provide Transport Request number.
6. Select Finish.

When you open the created service binding from editor you can see the below screen. As soon as the service binding is created, it is registered in your local system.

Activate the service binding and it is ready for consumption.

d.      Publish OData service

Once you activate the service binding, the OData service is published and is activated in SAP Gateway. Now it can be consumed by UI5 application.

The service URL on the right side will provide the metadata information of OData service. Preview button will navigate you to the resulting UI service.

Application preview

The resulting UI5 application will look like this:

Preface – This post is part of the SAP ABAP RAP series.

Introduction

SAP ABAP CDS View is used for defining and consuming semantic data models on standard tables or dictionary views. The abbreviation for CDS is Core Data Services. Although SE11 dictionary view and CDS views both create database views at the backend, the ABAP CDS view supersedes the dictionary view in so many ways.

Difference between dictionary view and CDS View

Dictionary View	CDS View
Can be created from SAP GUI or Eclipse.	Can only be created from Eclipse or SAP HANA Studio.
Cannot define Annotations.	Annotations are provided to enrich metadata.
Aggregation is not possible.	Can provide Aggregation function.
Grouping is not possible.	Grouping can be provided.
Join can be used.	Join and Union both can be used
	Case Expressions can be used.
	Input parameters can be allowed for filtering data and column calculations
	Operators can be used.

CDS view Types

There are three different VDM view types:

• Basic view
• Composite view
• Consumption view

Figure 1: CDS view types

1.      Basic View

VDM Basic views are created on the top of DDIC tables or views. It is the only view that interacts directly with the database.

Annotation: @VDM.Viewtype : #BASIC

Properties for Basic View:

1. Basic views can directly access the database tables and other basic views.
2. They have an association with other basic views.
3. Free of redundancies.
4. They expose all business data.

 

2.      Composite view

The composite view is created on top of the VDM Basic view. It interacts with Basic views for the result set and does not interact with the database directly.

Annotation: @VDM.Viewtype : #COMPOSITE

Properties of Composite View:

1. They can access other Composite views but not database tables.
2. They can have an association with other composite views and basic views.
3. Redundancies might be possible.
4. They should be reusable.

 

3.      Consumption view

The consumption views are built on top of Interface views. By the name Consumption, we can assume that this view is meant to be consumed by SAP UI5 through OData, Analytical queries, Transactional service models.

Annotation: @VDM.Viewtype : #CONSUMPTION

How to create CDS views in ADT?

To create a CDS view follow the below steps:

1. Navigate to New ABAP Repository.
   
2. Select Data Definition.
   
3. Provide Package, Name, Description of CDS view.
4. Now from the given options, select Define View.
   
5. Define data source name, SQL view name, required annotations and other properties.
   
6. Define data selection Query.
   
7. Save and activate.

How to view the data from CDS Views?

1. In the DDL source object, navigate to your CDS view.
2. Right-click and select OPEN DATA PREVIEW. Also, you can open the CDS view and press F8 to view the data.
3. The output will show you the retrieved data from CDS View.

Tutorial Video

You can watch the video below to learn implementation:

[embedyt] https://www.youtube.com/watch?v=CwWbauSyD4s[/embedyt]