The ABAP RESTful Appli\u00adcation Programming Model (RAP) provides developers with a powerful environment for creating efficient, SAP HANA-optimized OData services. In this blog post we will take a closer look at the various development options and scenarios with RAP.<\/p>\n
In the so-called managed scenario<\/span>completely new business objects (green\u00adfield) can be developed. The RAP framework takes over the procu\u00adrement and management of the business object\u2019s data from the database tables. This includes standard CRUD (Create, Read, Update, Delete) opera\u00adtions. Developers don\u2019t need to worry about imple\u00admenting these basic features because the framework already provides them. Another advantage of the managed scenario is that the framework also takes care of locking the objects to be changed. This greatly simplifies the development process and allows developers to focus on business-specific logic.<\/p>\n In contrast to this is the unmanaged scenario (brown\u00adfield), which can be used to connect existing business objects. In this case, data handling for the business object must be ensured using your own coding. However, this procedure makes it possible to use existing legacy coding (e.g. SAP BAPIs) to access the business objects. The unmanaged scenario is parti\u00adcu\u00adlarly useful when companies want to integrate their existing systems and appli\u00adca\u00adtions into the new RAP environment. Instead of developing every\u00adthing from scratch, developers can leverage their existing resources and skills and seamlessly integrate them into the RAP model.<\/p>\n In addition to the managed and unmanaged scenarios, the ABAP RESTful Appli\u00adcation Programming Model offers other powerful functions: Draft handling<\/strong>: This function can be activated for the managed scenario and enables the temporary storage of created or changed objects. This is parti\u00adcu\u00adlarly useful for Fiori apps, as object changes are not lost when the app is aborted and it is possible to change the device while editing. ABAP Environment Enhance\u00adments<\/strong>: The RAP model extends the ABAP environment with new keywords, annota\u00adtions, and an Entity Manipu\u00adlation Language (EML) for accessing business object data. Developers can customize the behavior of business objects through Behavior Defini\u00adtions and Imple\u00admen\u00adta\u00adtions. With these powerful features, the ABAP RESTful Appli\u00adcation Programming Model provides developers with a modern and efficient environment for building scalable, cloud-ready appli\u00adca\u00adtions. Whether you want to develop new business objects or integrate existing systems, RAP offers the right tools for your needs.<\/p>\n The ABAP RESTful Appli\u00adcation Programming Model (RAP) completely replaces the older ABAP Programming Model for SAP Fiori. In contrast to the old model, the RAP model no longer uses some frame\u00adworks such as the Business Object Processing Framework (BOPF) directly. Instead, OData services are generated automa\u00adti\u00adcally and can no longer be managed manually via transaction SEGW. RAP also offers new concepts such as the managed\/unmanaged scenario, draft handling and exten\u00adsions to the ABAP environment with new keywords, annota\u00adtions and the Entity Manipu\u00adlation Language (EML).<\/p>\n Development with RAP is mainly done using the ABAP Development Tools (ADT) in Eclipse. The classic Development Workbench (SE80) can only be used to edit individual sub-objects such as classes or database tables. The core concepts such as CDS Views, Behavior Defini\u00adtions, Service Defini\u00adtions and Service Bindings are all created and edited in ADT. Overall, development should become more efficient and standar\u00addized through integration in a development environment and the new language exten\u00adsions.<\/p>\n Draft handling allows newly created or changed objects to be tempo\u00adr\u00adarily stored in separate draft tables. This has several advan\u00adtages: First, changes to the object are not lost if the appli\u00adcation is aborted. Secondly, the user can switch devices while editing without losing data. Thirdly, a different locking concept is used with exclusive locks via the lock server that are not tied to the dialog session. This increases flexi\u00adbility and stability when editing objects.<\/p>\n","protected":false},"excerpt":{"rendered":" Development with the ABAP RESTful Appli\u00adcation Programming Model The ABAP RESTful Appli\u00adcation Programming Model (RAP) provides developers with a powerful environment for creating efficient, SAP HANA-optimized OData services. In this blog post we will take a closer look at the various development options and scenarios with RAP. Managed scenario In the so-called managed scena\u00adrio\u00adcom\u00adpletely new [\u2026]<\/p>\n","protected":false},"author":7,"featured_media":2518,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","wp_typography_post_enhancements_disabled":false,"footnotes":""},"categories":[20,27],"tags":[],"class_list":["post-2403","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-insights-en","category-programming-models"],"yoast_head":"\nUnmanaged scenario<\/h4>\n
More functions<\/h4>\n
How does the ABAP RESTful Appli\u00adcation Programming Model differ from the previous ABAP Programming Model for SAP Fiori?<\/h3>\n
What will development with the ABAP RESTful Appli\u00adcation Programming Model look like compared to before?<\/h3>\n
What advan\u00adtages does draft handling offer in the ABAP RESTful Appli\u00adcation Programming Model?<\/h3>\n