ABAP RESTful Application Programming Model Part-1(Architecture explanation and Build one RAP Model application and deploy to the SAP Cloud platform)

[prashanth01]

Hi All,

welcome back to one of my blogs.

I would like to share my RAP learning journey in detail and also provide one application with an

example.

In this blog series, We shall learn about RAP architecture and Real-time RAP-based application.

 

RAP Model Architecture

In the above architecture, we could see 3 layers of the RAP model

1. Data modeling and behavior

Data modeling is a collection of different entities involved in a business scenario, RAP uses the

CDS  to define the organize the data model.

The behavior describes what can be done with the data model for example,: Create, update, and

delete.

2. Business Service

Service Definition ->is used to define what part of the CDS / Behavior definition will be exposed to

the next layer

Service Binding -> defines a specific communication protocol such as OData V2 / OData V4

Service Definition is used to define the part of the CDS

3. Service Consumption

Service can be consumed as a UI element like a list report, Object page reports, etc.,

 

In this blog, I would like to show the case as the Fiori application Business partners in the List report

element.

Step 1–> Create Root CDS Entity ZBPHEADER

Right-click on the package –> New –> Other ABAP Repository Object –> Select Data Definition and

enter the name of Root CDS Entity –> Select Define Root View Entity.

 

 

Below is a code snippet providing Business partners' details from I_BusinessPartner in this

scenario I am going to create a List report read-only so that’s the reason I am using the standard

CDS (I_BusinessPartner) business partner.

We can see in the code snippet UI annotations with labels, and positions mentioned.

Once we create the root view entity, we can see the preview of the data.

now we have to create second-layer steps Business service->1. Service Definition and 2. Service Binding

Step 2–> We have to Create a Service Definition

Right-click on root view entity –> Select New Service Definition

Code Snippet:

 

Step 3 –> Now we have to Create a Service Binding

Right-click on service definition –> Select New Service Binding.

 

Once we click on Finish it will open the next screen like below.

 

We have to click on the publish button:

 

The RAP model process is done, and now we can preview our application.

In the above screen once we published the service we can preview the button we should have to

select Entity name and then click on the preview we can see below

Summary:

In this blog, I have used standard CDS for my practice purpose based on the requirement we have to create a Custom table.