NewABAP, RAP and ABAP Cloud
In the last 30 days
8 changes
Mon 19
What's new with draft handling in RAP?publishedAn ABAP-day session at Devtoberfest 2026 on two additions to draft handlingDraft handlingLetting a user edit a record over several requests before it becomes real — saving unfinished changes, locking, and activating a completed draft.SAP and community, narrow by design in RAP: collaborative draft, where two users work on the same draft instance and a field is locked only while the other is in it, and draft scope, where editing an instance of one draft-enabled business object puts the related instances of a dependent one into draft as well. Andre FischerAndre Fischercreated 5 pieces, contributed to 19 entries shows what each costs in the behaviour definition and projection, the draft query view and its DCL that collaborative draft needs over a table-based business object, and the CDS table entities that remove both the draft query view and the persistence table, with their current restrictions in ABAP analytics and extensibility; the from-scratch generator in ADT grows a checkbox for them. Both demos run against the DMO flight scenario of SAP-samples/abap-platform-refscen-flightSAP-samples/abap-platform-refscen-flightThe Flight Reference Scenario for the ABAP RESTful Application Programming Model, with sample data, RAP services and legacy logic for a flight-booking app, in branches for cloud and on-premise ABAP releases.sap official, abap, and the last part hides the draft-related features of an ODataODataExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.SAP and community, narrow by design V4 app in its manifest, which the session gives as the reason a simple create-update-delete app no longer needs a V2 service binding.Draft handling
Sat 17
From R/3 ABAP to CAP/Fiori Elements on SAP BTP- Deploymentexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
From R/3 ABAP to CAP/Fiori Elements on SAP Cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
RAP - Navigation (App to App)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Step-by-Step Guide to Display System Details on SAP Fiori Launchpad Shellexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Launchpad plugins
Show 1 more
Understanding and Developing Fiori Plugins with Extension API & TypeScriptexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Launchpad plugins
Mon 12
A Guide to CDS Metadata Extensions, Fiori App Generation and SAP UI5 Controller ExtensionspublishedWalks through a RAP-based Fiori elements app end to end: layering UI annotationsFiori annotationsDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.SAP and community, unassessed onto a CDS view through a separate ABAP metadata extension object, gated by
@Metadata.allowExtensions on the base view and ordered across extensions by a required @Metadata.layer value. Generates the app in SAP Business Application StudioSAP Business Application StudioSAP's development environment for business applications, delivered as a cloud service and opened in a browser, where work happens in preconfigured dev spaces.sap official, btp from the published ODataODataExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.SAP and community, narrow by design V4 service's merged $metadata document, then adds an SAP UI5 controller extension — registered in manifest.json against a Fiori elements lifecycle hook — only for behaviour the annotations cannot express.Fiori annotationsSun 4
Step-by-Step Guide to Display System Details on SAP Fiori Launchpad ShellpublishedA step-by-step build of a plugin for the SAP Fiori launchpadLaunchpad pluginsExtending an application launchpad’s shell rather than an individual app: adding header buttons, user-menu entries, frame areas or background behaviour shared across the apps it hosts. A development sandbox for launching an app is a separate concern.SAP and community, unassessed shell that shows the system ID and client on every app it hosts: an OData service modelled in SAP Gateway Service BuilderODataExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.SAP and community, narrow by design (SEGW), its GetEntitySet method redefined to call the function module RSAPI_CTC_GET_SYSTEM_DETAILS, then consumed from a project in SAP Business Application StudioSAP Business Application StudioSAP's development environment for business applications, delivered as a cloud service and opened in a browser, where work happens in preconfigured dev spaces.sap official, btp with the Component.js and manifest.json changes a shell plugin needs instead of a standalone app. It covers the registration step a plugin needs beyond a normal Fiori app: a Catalog and Target Mapping with Semantic Object Shell and Action Plugin, deployed on-premise and assigned to roles.Launchpad plugins