NewABAP, RAP and ABAP Cloud
In the last 30 days
65 changes
Today
Browsing table datacore coverage revisedReassessed against the graph (check:capabilities): the note described the providers as SAP GUI programs only, and browser apps, an IDE extension and a desktop editor have arrived; the state stays core-and-community.Browsing table data
Calling a service by handcore coverage revisedReassessed against the graph (check:capabilities): abap-odata-test arrived after the block was assessed and changes the kinds of community answer; the state stays core-and-community.Calling a service by hand
Clean code conventionscore coverage revisedReassessed against the graph (check:capabilities): FORMfactor, an independent ABAP generator, provides this capability, so the community is present on the door.Clean code conventions
Code formattingcore coverage revisedReassessed against the graph (check:capabilities): the abap2UI5 playground provides this capability and the text never named it; ABAP FS named for the kind of VS Code integration.Code formatting
Show 18 more
Code reviewcore coverage revisedReassessed against the graph (check:capabilities): providers that arrived after the 2026-09-13 assessment (abapTimeMachine, abapOpenReview, a transport review app) shape the answer; state unchanged, core-and-community.Code review
Debuggingcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): seven ABAP providers newer than the block were never named. State stays core-and-community.Debugging
Documentationcore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): absence claims about providers go stale as providers arrive. The flavor states are unchanged.Documentation
Driving the SAP GUIcore coverage revisedReassessed against the graph (check:capabilities): removed the count and the popularity wording, and named the kinds, including batch input (jrgkraus-tool-bi) and SAP's sample, which the text never named.Driving the SAP GUI
Editor supportcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): the providers behind the UI5 door are SAP's (UI5 Language Assistant, and SAP Build Code and SAP Web IDE Full-Stack, which serve ui5). The community SAPUI5 Extension is an entry in the graph but has no provides edge to this capability.Editor support
Finding a transaction codecore coverage revisedReassessed against the graph (check:capabilities): sapgui arrived as a second kind, one that reads the system's own menu, and the prose counted entries.Finding a transaction code
Generatorscore coverage, coverage by ecosystem, framing by ecosystem revisedReassessed against the graph (check:capabilities): the atlas holds these entries, so the links point at them and not at their repositories (docs/WRITING.md section 4).Generators
IDE provisioningcore coverage revisedReassessed against the graph (check:capabilities): eclipsadt-o-mat arrived after the last look and the text never named it; state unchanged.IDE provisioning
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
Local developmentcoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): the note counted providers and claimed an absence about who has built something, which goes stale as providers arrive.Local development
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
Model visualisationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): abapGraph and abap-search-tools-ui arrived after the ABAP block was last looked at and the text never named them. No state changed.Model visualisation
Searching code in a systemcore coverage revisedReassessed against the graph (check:capabilities): the note named no kind of provider, and five providers newer than the 2026-09-14 assessment shape the answer. State unchanged.Searching code in a system
Seed datacore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): no artifact provides seed-data for the UI5 door; the two tools the sentence named provide ui5-testing. The core stays present on the sourced what_core_does. The tools stay on the graph under ui5-testing.Seed data
Source controlcore coverage revisedReassessed against the graph (check:capabilities): providers added since 2026-08-31 change the kinds the community adds beyond the in-system git client; the state stays core-and-community.Source control
Static analysiscore coverage revisedReassessed against the graph (check:capabilities): the block named none of the providers that arrived after 2026-08-31. State unchanged, core-and-community still matches the providers.Static analysis
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
Unit testingcore coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): the note counted the artifacts and said they were in staging; both are in the graph now and are named.Unit testing
Mon 19
Editor supportecosystems revisedUI5 Language Assistant, SAP's VS Code extension for UI5 XML views and manifest.json, and the SAPUI5 Extension by iljapostnovs were staged in intake-20261019-bestofui5 with this concern as their best fit, and the capability was not open on the UI5 door. The UI5 reading comes from the UI5 Language Assistant README.Editor support
Seed dataecosystems revisedvscode-ui5-odata-mock-generator and openui5-smart-mockserver were staged in intake-20261019-bestofui5 under ui5-testing; the first one's drafter noted that seed-data fit better but was not open on the UI5 door. The UI5 reading comes from the OpenUI5 mock server pages and SAP's ui5-middleware-fe-mockserver README.Seed data
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
ABAP - Create dumpexplains 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).Debugging
AI-enabled administration: Automating log analysis with generative AI hubexplains 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).Editor support
Browsing table datadescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Browsing table data
Calling a service by handdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Calling a service by hand
Show 20 more
Clean code conventionsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Clean code conventions
Code reviewdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Code review
Debugging in ABAP Development Tool (Part 1)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).Debugging
Driving the SAP GUIdescription revisedKeep the technology that defines the concern in the default; move implementation detail to framing_by_ecosystem.abap. Maintainer-requested scope audit.Driving the SAP GUI
Explore SAP Fiori elements for ABAP developersexplains 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).Editor support
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
IDE provisioningdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.IDE provisioning
Launchpad pluginsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Launchpad plugins
Model visualisationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Model visualisation
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 BAIP, ABAP environment: Monitoring and troubleshootingexplains 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).Browsing table data
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
Searching code in a systemdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Searching code in a system
Source controlname, description revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Source control
Static analysisdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Static analysis
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
Unit testingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Unit testing
Thu 15
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
Local developmentcore coverage, coverage by flavor, framing by flavor, facets revisedNine options answered this capability with nothing to compare them by, and they are not variants of one tool: the first question a reader has is which part of the local stack an option starts. The two flags separate the hybrid-testing helpers, where cds bind states that only the location of the credentials is stored on the machine and @sang2x/captools states that it writes the resolved VCAP_SERVICES into default-env.json.Local development
Unit testingcore coverage, coverage by flavor revisedTwo staged options state abap-cloud and provide this capability; the gate reads them as providers once this capability is revised.Unit testing
Wed 14
Driving the SAP GUInormative relevance revisedThe GUI servers' boundaries each restated the policy in the atlas's own words; it belongs to the concern, sourced to the policy.Driving the SAP GUI
kts982/mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.Driving the SAP GUI
mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.Driving the SAP GUI
sapgui.mcpdescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.Driving the SAP GUI
Mon 12
abap-transport-reviewentry revisedEntered by intake from the repository README and the repository's own facts. Placed on the ABAP door in the standard-abap flavor only, because the README states the tools are classic ABAP using the CTS_REQUEST_CHECK BAdI, background jobs and the cluster table INDX, "none of which is part of ABAP Cloud".Code review
Sun 4
eclipsADT-o-matentry revisedEntered by intake from the repository README and description.IDE provisioning
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
Tue 29
Finding a transaction codeentry revisedA browser tool for searching transaction codes had nowhere to attach, and the nearest nodes are all about something else: browsing table data is the rows a system holds rather than the way into a task, GUI automation drives screens rather than finding them, abap-classic-ui builds them, and documentation is what to read. Named on the ABAP door because a transaction code is an entry point of a classic SAP system, and marked not-applicable in ABAP Cloud, where there is no SAP GUI and so no command field to enter one into. The coverage rests on SAP's own documentation for the in-session routes; nobody has surveyed what else answers this from outside a system, which is why the relationship is unassessed.Finding a transaction code
ui5-tcode-finderentry revisedStaged with the capability Finding a transaction code, drafted in the same batch because the corpus held no concern for it. ecosystem: abap is a placement rather than a stated fact: the repository is an OpenUI5 and TypeScript application, but its subject is the transaction codes of a classic SAP system and the only stack its features name is SAP GUI for HTML. serves_ecosystems: ui5 rests on the overview sentence naming the T-Codes a UI5 or Fiori project needs. use_as: reference because it is consulted at its own address rather than installed into a project.Finding a transaction code
Sun 27
Debuggingcore coverage revisedPackage pass 2026-09-27: the paragraph named one of the four SAP packages and cited the plugins index only; cds debug and the Java developer dashboard were cited nowhere.Debugging
Documentationcore coverage revisedPackage pass 2026-09-27: the capability had no paragraph and no source at all.Documentation
Local developmentcore coverage revisedcapire audit 2026-09-27, judgement pages read once more: a page this capability owns was cited nowhere.Local development
Localizationcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Localization