RAP Series: Let’s Build a RAP Application End to End Scenario – Version(V4) | 2023.


HI SCN People, Hope you guys are doing great!

This Blog was divided into 03 Parts.

Part – 01: Scenario, Introduction, Pre-Requests, Terms to Know. (This Blog)

Part – 02: Steps for Development, with total Implementation. (Click Here)

Part – 03: How to make use of the RAP Application in Fiori Tile. (Click Here)


Scenario:

An Organization Plans to maintain records of an Employee which Performs CRUD Operations,
**Information be like:
**
General Information
Address Information
Designation

In General Information,
Age – Should be less than 55 Years.

In Designation,
Based On Role Experience should be taken

In this blog, covering things in technical aspects as well:
• determination
• validation

Note: This blog is used to create a user interface without using Fiori elements.

Let’s have a simple definition of RAP:

RAP (ABAP RESTful Application Programming Model):

• The ABAP RESTful Application Programming Model (in short RAP).

• It is used to create a service, API and UI without using the Fiori element.

• It uses on technology CDS (Core Data Service) for defining semantically rich data models and a service model infrastructure for creating OData services with bindings to an OData protocol and ABAP-based application services for custom logic and SAPUI5-based user interfaces.

The ABAP RESTful Application Programming Model is available for the following products:

• SAP BTP ABAP environment.
• SAP S/4HANA Cloud.
• Application Server ABAP 7.56.

Overview Of an RAP Application:

Prerequisites:

Development Platform: ADT (ABAP Development Tools).

Basic Knowledge:
ABAP Core Data Services (CDS), ABAP Objects.

Know the Specific Terms: Before Moving Forward

Business Object:

• A Business Object (BO) is a collection of tree Nodes (Entities) where each Node (Entity) represents one CDS View.

• It is a term to represent a real-world artifact such as the Product, Travel, or the Sales Order.

• In general, a business object contains several nodes such as Items and common transactional operations such as creating, updating and deleting data and additional application-specific operations

The behavior of a Business Object:

• The behavior definition is a crucial aspect of any CDS data model as it defines the actions that can be performed on the data, such as creating, updating, and deleting records.

• Every Entity of the Business Object offers standard operations such as Create, Read, Update and Delete.

• A behavior definition always refers to a CDS data model. As shown in the figure below, a behavior definition relies directly on the CDS root entity. One behavior definition refers exactly to one root entity and one CDS root entity has at most one behavior definition (0 to 1 Relationship), which also handles all included child entities.

**Business Object Implementation Types:
**
There are 2 types of business object implementation type:

1) Managed.
2) Unmanaged.

Managed Implementation type:

• The managed implementation type addresses use cases where all essential parts of an application must be developed from scratch.

• We can perform all the CURD Operations can be managed by the framework itself.

Unmanaged Implementation Type:

• In unmanaged business objects, the application developer must implement essential components of the REST contract.

• There is no standard functionality provided by the RAP framework.


The End | Blog Part – 01 | Stay Tuned for Part – 02


Team LinkedIn Profiles:


Thank You,
SAP MDG Team.

Happy Learning :) | SAP - The Best Run