NewABAP, RAP and ABAP Cloud
86 changes
Today
Launchpad pluginscore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed an absence claim and a count of providers (WRITING §3); the flavor states are unchanged.Launchpad plugins
Localizationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): providers arrived after the block was last looked at, an XLIFF editor and an MCP server among them, and the text named none of the kinds.Localization
UI written in ABAPcore coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the claim that abap2UI5 is the sole provider, which went stale as providers arrived.UI written in ABAP
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
XLF Translatorflavors, type properties revisedThe flavor rests on the page's "The tool is mainly used to translate ABAP Cloud Content, which is generated using the 'Maintain Translation' app (XLIFF Version 1.2)." The web-tool block's uploads key carries the one sentence the page gives about the file leaving the machine, "After uploading, all fields that have a translation element are available for translation.", verbatim; access is left out because neither the page nor the site's FAQ says what it takes to use the tool. The prose no longer says the file is opened in the browser, which the word "uploading" does not support, no longer treats XLIFF 1.2 as what the tool accepts (the page states the version of the ABAP Cloud content it is mainly used for), and attributes "without installing an additional tool" to the maker. when_not_to_use was "One file per session, translated by hand, field by field", none of which the page states.Localization
Sat 17
@abap2ui5/embed-controladded to the atlasUI5 custom control that runs an abap2UI5 app inside a host app
abap-cloud-guiadded to the atlasReport-style programming model for abap2UI5 on ABAP CloudUI written in ABAP
abap2UI5 for Exceladded to the atlasOffice add-in running an abap2UI5 app in Excel's task paneUI written in ABAP
abap2UI5 frontendadded to the atlasabap2UI5 frontend as ABAP artefacts installed with abapGitUI written in ABAP
Show 20 more
abap2UI5 frontend-webcomponentadded to the atlasabap2UI5 frontend rendering with UI5 Web ComponentsUI written in ABAP
abap2UI5 mobile shelladded to the atlasNative iOS and Android shell for one abap2UI5 endpoint
abap2UI5 protocoladded to the atlasVersioned specification of the abap2UI5 roundtrip protocolUI written in ABAP
abap2UI5-addons/popupsadded to the atlasReady-made dialogs for abap2UI5 appsUI written in ABAP
abap2UI5-localadded to the atlasabap2UI5 folded into the local classes of one HTTP handlerUI written in ABAP
abap2UI5/samples-stackadded to the atlasabap2UI5 apps in front of OData, RAP, events and other technology
custom-controlsadded to the atlasThirteen custom UI5 controls for abap2UI5 appsUI written in ABAP
custom-controls-customeradded to the atlasTemplate repository for own UI5 artefacts served to abap2UI5
http-connectoradded to the atlasForwards abap2UI5 roundtrips to another system over HTTPUI written in ABAP
layout-managementadded to the atlasTable and form layouts with saved variants for abap2UI5UI written in ABAP
rap-extadded to the atlasFloorplans rendered from CDS UI annotations as abap2UI5 appsFiori annotations
selection-screenadded to the atlasSelect-options with saved variants for abap2UI5 appsUI written in ABAP
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
Launchpad pluginsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Launchpad plugins
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
SAP GUI screens and listsdescription revisedKeep the technology that defines the concern in the default; move implementation detail to framing_by_ecosystem.abap. Maintainer-requested scope audit.SAP GUI screens and lists
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
UI written in ABAPdescription revisedKeep the technology that defines the concern in the default; move implementation detail to framing_by_ecosystem.abap. Maintainer-requested scope audit.UI written in ABAP
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
Thu 15
open-abap-guiadded to the atlasGUI controls for ABAP transpiled to JavaScript
Fiori annotationscore coverage, coverage by flavor revisedThe door has two flavors and neither was assessed, so both were derived from the options alone. Java reads core-only: the three community providers are cds-plugins @sap/cds loads, and the Java side's own facts are the compiler running under the Maven build and the one hierarchy annotation the Java runtime reads itself.Fiori annotations
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
LISAadded to the atlasMCP server for reading and writing ABAP object translationsLocalization
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
LISAentry revisedEntered by intake from the README, found through ARC-1's extensions page, which names it in its example of driving a custom ABAP HTTP service.Localization
Sun 27
Localizationcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Localization
Sun 20
Fiori annotationscore coverage revisedThree independent cds-plugins now provide this capability on CAP beside SAP's own packages: @mpah/enum-value-help, cap-js-geoloc-plugin and urp-vocab. The relationship is unassessed: no retrieved document gives the history between them and the core.Fiori annotations
Fri 18
RAP - Navigation (App to App)publishedWalks through app-to-app navigation from a RAP list report and object page: the @Consumption.semanticObject annotation and its semanticObjectMapping.element and additionalBinding variants for links, against the inline @UI.lineItem WITH_INTENT_BASED_NAVIGATION and @UI.identification FOR_INTENT_BASED_NAVIGATION for buttons. Each variant is added through a CDS metadata extension and traced into the target app, showing which fields end up in the filter and how the two annotation styles differ in the list report's formatting. Annotation-driven navigation on a RAP service is part of what Fiori 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 covers on the ABAP door: CDS annotations, carried in a metadata extension, driving the Fiori elements UI.Fiori annotations
Localizationecosystems, coverage by ecosystem, framing by ecosystem revisedBehind the UI5 door the texts are files in the app rather than model elements in a service, which is what the CAP framing describes.Localization
Thu 17
CALL BAPI IN CUSTOM ENTITY THROUGH RAPpublishedBuilds a read-only RAP Custom Entity, ZCE_BANK, whose query provider class calls BAPI_BANK_GETDETAIL directly instead of reading a CDS-based persistency, handling filtering, sorting, paging and the total count from the request object in IF_RAP_QUERY_PROVIDER~SELECT. It walks through the @UI annotations — headerInfo, presentationVariant, lineItem, selectionField, identification — that drive the entity's Fiori Elements list report, which is Fiori 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 on the ABAP door.Fiori annotations
Wed 16
XLF Translatoradded to the atlasEditor for the translations in an uploaded XLIFF fileLocalization
XLF Translatorentry revisedEntered from software-heroes.com's tools page.Localization
Tue 15
SAP Translation Hubadded to the atlasTranslation service for software texts and documentsLocalization
Key-user adaptationecosystems, coverage by ecosystem, framing by ecosystem revisedOn BTP the changes live in a service the application adds, where the ABAP framing places them in the system's layered repository.Key-user adaptation
Localizationecosystems, coverage by ecosystem, framing by ecosystem revisedOn BTP the concern includes getting texts translated by a service, where the CAP framing is serving texts per locale and the ABAP framing is translating repository objects in the system.Localization
Mon 14
abap_btocs_deepladded to the atlasDeepL translation plugin for the B-Tocs ABAP SDKLocalization
abap_btocs_libtrladded to the atlasLibreTranslate plugin for the B-Tocs ABAP SDKLocalization
ABAP_DeepL_clientadded to the atlasABAP client for the DeepL translation serviceLocalization
abap_gui_boilerplateadded to the atlasTemplate for ABAP applications with an HTML UI
Show 26 more
abap_mustacheadded to the atlasMustache template engine for ABAPUI written in ABAP
ABAP_TRANSLATION_HUBadded to the atlasReport pushing ABAP objects to SAP Translation Hub and backLocalization
abap-alv-struc-vieweradded to the atlasALV table view generated from a DDIC structureSAP GUI screens and lists
abap-form-translatoradded to the atlasRuntime translation layer for SAP form labels, kept in a tableLocalization
abap-ui-toolboxadded to the atlasABAP classes for classic SAP GUI development: ALV, screens, treesSAP GUI screens and lists
abap-ui-toolsadded to the atlasHelper class for classic ABAP dynpro field handling and popupsSAP GUI screens and lists
abapEasyALVadded to the atlasWrapper classes over classic ALV and SALV reportingSAP GUI screens and lists
abapMermaidadded to the atlasRenders Mermaid diagrams inside an SAP GUI containerSAP GUI screens and lists
abeljohny/ZAPadded to the atlasMacro DSL turning a one-line select into an ALV listSAP GUI screens and lists
alv_gridadded to the atlasDemo programs for the classic CL_GUI_ALV_GRID control
alv_utilitiesadded to the atlasABAP class wrapping SALV to set column properties in one callSAP GUI screens and lists
cds2alvadded to the atlasGenerator for ALV list reports from a CDS view's field definitionsSAP GUI screens and lists
Creating a Custom F4 Help for Currency Fields in ABAP Using F4IF_INT_TABLE_VALUE_REQUESTpublishedWalks through building a custom F4 help popup for a currency selection-screen field: an AT SELECTION-SCREEN ON VALUE-REQUEST handler reads currency codes and texts from TCURC and TCURT into an internal table, then passes it to F4IF_INT_TABLE_VALUE_REQUEST to render the popup list. It is offered as a replacement for the field's standard search help when that does not fit the business requirement.SAP GUI screens and lists
guidrasiladded to the atlasVisual designer generating ABAP code for classic SAP GUI screensSAP GUI screens and lists
onurakca/SAPUI5-Adaptation-Project-Downloaderadded to the atlasABAP report downloading SAPUI5 adaptation project artifactsKey-user adaptation
s4hana-avc-ui-extension-templateadded to the atlasTemplate and mock runtime for S/4HANA Variant Configuration UIs
SAP-samples/abap-platform-fiori-feature-showcaseadded to the atlasShowcase of Fiori elements for OData V4 features on RAP
ZABAP_TRANSLATIONSadded to the atlasExcel export and import of ABAP package or program textsLocalization
ZOTR_UTILITYadded to the atlasABAP framework reading texts from SAP's online text repositoryLocalization
ZwdDynscreenadded to the atlasSelection screens and popups generated from ABAP objects, no dynproSAP GUI screens and lists
Fiori annotationsecosystems revisedWidened to ABAP: SAP-samples/abap-platform-fiori-feature-showcase demonstrates annotation-driven Fiori elements for OData V4 on RAP, the same concern as CAP's annotations.Fiori annotations
Key-user adaptationecosystems revisedSAPUI5-Adaptation-Project-Downloader reads adaptation-project changes out of the layered repository in an ABAP system, so the flexibility concern has an answer behind the ABAP door.Key-user adaptation
Launchpad pluginscoverage by flavor revisedA launchpad plugin is an SAPUI5 component sap.ushell loads through its Extension service; UI5 Web Components' own README states the library is not built on top of UI5 and names UI5 itself as what remains the choice for a complete application, and none of the three UI5-door artifacts behind this capability state the web-components flavor.Launchpad plugins
Localizationecosystems revisedSeven repositories translate ABAP texts: they push object lists to SAP Translation Hub, call DeepL or LibreTranslate, export a package's texts to a spreadsheet, keep form labels in a table, and read texts from the online text repository.Localization
SAP GUI screens and listscoverage by flavor revisedSAP's own ABAP Cloud documentation excludes classic UI technology syntax (dynpro) from ABAP for Cloud Development and names Fiori as its UI technology instead, and neither ABAP-door provider of this capability states abap-cloud support.SAP GUI screens and lists
UI written in ABAPcoverage by flavor revisedSAP's own ABAP Cloud UI answer is RAP generating a Fiori elements service, not ABAP rendering a UI itself; the one ABAP-door provider, abap2UI5, is community-org and states it runs up to ABAP Cloud, so the door-level state carries over unchanged.UI written in ABAP
Sun 13
fiori-fullscreen-pluginadded to the atlasFiori launchpad plugin adding a fullscreen toggle button
generator-ui5-ts-flp-pluginadded to the atlasEasy-UI5 generator for a TypeScript Fiori launchpad pluginLaunchpad plugins
Understanding and Developing Fiori Plugins with Extension API & TypeScriptpublishedDescribes a launchpad plugin as a UI5 component without views that the shell loads for every app, SAPUI5 only, and compares extending the shell through the renderer with the
Extension service from 1.120 and FrameBoundExtension from 1.124, down to the placement options each allows. It builds fiori-fullscreen-pluginfiori-fullscreen-pluginA SAP Fiori launchpad plugin in TypeScript that adds one header button, created through the Extension API, which toggles the browser's fullscreen mode; it needs SAPUI5 above 1.120.independent, ui5 as the sample, and ends with activation: globally through /UI2/FLP_CONF_DEF and /UI2/FLP_CUS_CONF or per role through a Shell-plugin target mapping on an ABAP launchpad, and as an HTML5 app assigned to a role in SAP Build Work Zone.Launchpad pluginsZFPM_TOOLSadded to the atlasEdits, copies and transports a whole FPM hierarchy at onceUI written in ABAP
Show 1 more
ZWD_CALENDAR_VHadded to the atlasWeb Dynpro ABAP calendar value help for date fieldsUI written in ABAP
Tue 8
From R/3 ABAP to CAP/Fiori Elements on SAP BTP- DeploymentpublishedThe doing half: the steps and the code that got the application from the first post deployed and working. Shorter, and it assumes the argument has already been made.Fiori annotations
From R/3 ABAP to CAP/Fiori Elements on SAP CloudpublishedWritten by an ABAP developer of fourteen years explaining what changed and what did not — the argument being that CAP kept the focus on business logic that ABAP had, where learning UI5 and a framework or two had not. The reasoning half of a pair.Fiori annotations
Mon 31
abap2UI5added to the atlasUI5 apps written as one ABAP class, rendered by a generic shellUI written in ABAP
Fiori annotationscore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Fiori annotations
Localizationcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Localization
Fri 26
LISAreleased 0.8.1Install steps that import one ABAP handler class into every kind of system.Localization