RAP Unmanaged Save Implementation (save_modified)
The concept name was not provided (marked as "undefined"), and the supplied source snippets do not contain enough specific, attributable detail to construct a grounded 2–4 sentence prose definition for an unnamed concept. A valid concept name is required to produce an accurate and source-supported reference definition.
Tutorials that teach this
- Tutorial Integrate the Wrapper into the Shopping Cart Business Object
- Tutorial How to Create RAP Business Events in an On-Premise system
- Tutorial Create Behavior and Service in SAP BTP, ABAP Environment
- Tutorial Replace Wrapper by Released API
- Tutorial Integrate released purchase requisition API into Shopping Cart Business Object
Prerequisites
- Concept RAP Behavior Definition and Projection The concept name is not defined in the provided sources, so a precise definition cannot be grounded solely in the supplied snippets. Based on the available sources, the topics covered relate to [modeling and implementing protection against unauthorized write activities](https://help.sap.com/docs/btp/sap-business-technology-platform/fb6a6213fced4fe8af8466e25fa73035?locale=en-US&state=PRODUCTION&version=Cloud) and [providing write access using privileged mode](https://help.sap.com/docs/btp/sap-business-technology-platform/c33599391557415896921ace44f2ba73?locale=en-US&state=PRODUCTION&version=Cloud) within the ABAP RESTful Application Programming Model (RAP). Privileged mode, invoked with the keyword `PRIVILEGED`, allows developers to bypass standard authorization checks to grant write access in specific controlled scenarios. These mechanisms together enable developers to secure business object operations against unauthorized modifications while still accommodating legitimate privileged use cases.
- Concept Entity Manipulation Language (EML) in RAP The concept provided is **undefined** — no specific SAP developer concept was supplied for definition. Based on the available sources, a general definition can be offered: the [ABAP RESTful Application Programming Model (RAP)](https://help.sap.com/docs/btp/sap-business-technology-platform/630ab6dcd7064ad3b9bf7d51b78711a2?locale=en-US&state=PRODUCTION&version=Cloud) is a framework for building SAP Fiori apps and OData services on SAP BTP using ABAP. Developers use it to create and enhance business objects with behaviors such as actions and feature control, and to integrate released APIs into custom applications. Custom ABAP logic can be authored using the [ABAP Cloud Editor](https://help.sap.com/docs/btp/sap-business-technology-platform/8f62c414203546faa96542ad723f932e?locale=en-US&state=PRODUCTION&version=Cloud), which supports writing code for key use cases on SAP Business Technology Platform.
- Concept ABAP RAP Behavior Definitions and Implementations
- Concept RAP Behavior Implementation The concept name was not provided, so a precise definition cannot be generated from the available sources. The supplied snippets cover topics such as protection against unauthorized write activities, transport handling for business configuration content, determinations, ABAP Unit Tests, and dynamic feature control within the ABAP RESTful Application Programming Model (RAP), but without a specific concept to define, no accurate and source-grounded definition can be produced.
- Concept RAP Business Objects (Managed/Unmanaged) The concept name was not provided, so a precise definition cannot be produced. Based on the available sources, which cover ABAP Unit Tests for RAP Business Objects and RAP Business Events in on-premise systems, the concept appears to relate to the [ABAP RESTful Application Programming Model (RAP)](https://help.sap.com/docs/abap-cloud/abap-rap/abap-restful-application-programming-model). RAP is a framework developers use to build SAP Fiori apps and OData services, supporting capabilities such as unit testing of business objects and the creation of business events in on-premise systems.
- Concept RAP Managed Business Objects with Late Numbering The concept name was not provided (marked as "undefined"), and the single source snippet supplied — a tutorial title referencing Purchase Orders and Purchase Contracts — does not contain enough factual detail to write a grounded, accurate definition. A valid concept name and richer source content are required to produce a reliable reference entry.
- Concept RAP (Restful ABAP Programming) Model The provided sources do not contain enough grounded information to write a reliable 2–4 sentence definition for an **undefined** concept. Please supply a valid concept name and ensure the source snippets contain substantive descriptions of that concept so the definition can be accurately grounded.
- Concept ABAP Behavior Definition (BDEF) The concept name provided is "undefined," and the supplied sources do not contain sufficient information to define a specific SAP developer concept. A meaningful definition cannot be grounded solely in the available snippets without introducing unsupported claims. Please provide a valid concept name and relevant source material so an accurate definition can be written.
- Concept ABAP RESTful Application Programming Model (RAP) The concept name was not provided (marked as "undefined"), and the supplied source snippets cover several broad SAP BTP and ABAP topics — such as the ABAP Environment, RAP development, authorization basics, and system workload analysis — without converging on a single, specific concept to define. There is insufficient information to produce an accurate, source-grounded definition.