{"id":3407,"date":"2024-08-21T15:14:28","date_gmt":"2024-08-21T13:14:28","guid":{"rendered":"https:\/\/www.clavis.biz\/?page_id=3407"},"modified":"2025-07-08T10:52:30","modified_gmt":"2025-07-08T08:52:30","slug":"abap-restful-application-programming","status":"publish","type":"page","link":"https:\/\/www.clavis.biz\/en\/sap-technologies\/abap-restful-application-programming\/","title":{"rendered":"ABAP RESTful Application Programming (RAP)"},"content":{"rendered":"\n
<\/span>
\n
\n

Modern programming model specifically for the development of business applications in SAP<\/h2>\n\n\n\n

RAP (ABAP RESTful Application Programming Model) is a programming model from SAP that was developed specifically for mapping business applications in SAP S\/4HANA. It enables the creation of end-to-end applications that run on the ABAP stack and are based on principles such as RESTful services and the use of SAP Fiori. <\/p>\n\n\n\n

Among other things, RAP is used to develop modern user interfaces with SAP Fiori that offer an improved user experience. RAP is particularly useful for developing applications in the SAP Cloud Platform as it supports cloud-native development paradigms. In addition, RAP requires little to no SAPUI5 experience. Developers who are already proficient in ABAP or CDS views therefore have a simplified entry into the development of Fiori apps. At the same time, RAP unmanaged also allows you to retain control and develop all content independently. <\/p>\n\n\n\n

<\/div>\n<\/div><\/div>\n<\/div><\/div>\n\n
<\/span>
\n
\n
<\/div>\n\n\n\n

RAP: Advantages and disadvantages<\/h2>\n\n\n\n

RAP (ABAP RESTful Application Programming Model) is a programming model from SAP that was developed specifically for mapping business applications in SAP S\/4HANA. It enables the creation of end-to-end applications that run on the ABAP stack and are based on principles such as RESTful services and the use of SAP Fiori. <\/p>\n\n\n\n

Advantages <\/th>Disadvantages <\/th><\/tr><\/thead>
RAP offers usability and consistency checks for fields and locks that would have to be developed manually by the developer in SAPUI5 apps. <\/td>RAP apps offer the possibility to create list and object pages and therefore have their limits.<\/td><\/tr>
It offers automated CRUD methods for managed RAP apps<\/td>Not all controls are available and it is not possible to create custom controls.<\/td><\/tr>
Easy extensibility<\/td>Less flexibility<\/td><\/tr>
Simple solution for backend development.<\/td>Not all functions are available on all systems (cloud, on-premise) and therefore severely restricts use without offering an alternative.<\/td><\/tr>
By using Core Data Services (CDS) and standardized annotations, developers can create consistent and reusable business logic.<\/td><\/td><\/tr>
Integrated security mechanisms, such as authorization and authentication, that make it easier to develop secure applications.<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

RAP uses modern development paradigms such as RESTful services, which enable easier integration and better scalability. By using Core Data Services (CDS) and standardized annotations, RAP enables consistent and reusable data modeling and business logic. With UI annotations and RAP managed, it is possible to spin up an app with simple CRUD methods within a very short time. <\/p>\n\n\n\n

RAP offers flexible extension options that allow developers to customize applications to specific business requirements without changing the SAP core.<\/p>\n\n\n\n

<\/div>\n<\/div><\/div>\n<\/div><\/div>\n\n
<\/span>
\n
<\/div>\n\n\n\n

RAP Unmanaged<\/h2>\n\n\n\n

In unmanaged scenarios, the methods must be implemented manually, in contrast to managed RAP apps, where some methods are automatically provided by the framework.<\/p>\n\n\n\n

The developer is responsible for implementing the entire logic, including managing the transaction buffer and the memory sequence. This provides more flexibility and control, especially when migrating existing ABAP code and functions. <\/p>\n\n\n\n

The structure of mananged and unmanaged apps is basically the same, but there are different options for developers:<\/p>\n\n\n\n

Customized logic:<\/strong> In unmanaged RAP, developers write their own custom logic for data retrieval, manipulation and persistence. This offers more flexibility in the processing and storage of data. <\/p>\n\n\n\n

Direct database access<\/strong>: Developers can directly access the database tables and define their own data models using Core Data Services (CDS) views or ABAP classes.<\/p>\n\n\n\n

Explicit service definition:<\/strong> In contrast to managed RAP, with the automatic generation of service definitions based on annotations, unmanaged RAP requires developers to explicitly define the service implementations and behaviors.<\/p>\n\n\n\n

Manual CRUD operations<\/strong>: CRUD (Create, Read, Update, Delete) operations must be explicitly implemented in unmanaged RAP, giving developers complete control over how data is managed.<\/p>\n\n\n\n

Integration with existing system<\/strong>s: Unmanaged RAP is often used when integration with existing systems is required or when there is complex business logic that is difficult to implement with the managed approach.<\/p>\n\n\n\n

Flexibility<\/strong>: Developers have more freedom to implement complex validation rules, authorization checks and other custom requirements directly in the application logic.<\/p>\n\n\n\n

Structure: <\/strong>Some methods are provided by the system so that the functions can be implemented. These are divided into two classes and described below. <\/p>\n\n\n\n