NewABAP, RAP and ABAP Cloud
In the last 30 days
53 changes
Today
Agent access to your codecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the tool count and the two absence claims about who has built something.Agent access to your code
Agent evalscore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): albertmink-agentic-abap-evals, an independent set of ABAP tasks and a grader for coding agents, was entered after the block was written; the count is dropped and the second kind named. State unchanged.Agent evals
Agent guidancecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): docs/WRITING.md §3 rules out provider counts and absence claims in every capability field.Agent guidance
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
Show 19 more
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
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
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
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
LLM integrationcoverage by ecosystem, core coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): the note claimed who provides the capability behind this flavor, which moves with the corpus. The flavor state is unchanged.LLM integration
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
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
Retrieval-augmented generationcoverage by ecosystem, core coverage revisedReassessed against the graph (check:capabilities): a CAP-door provider reaches Document Grounding through the LangChain vector store interface, a shape the two plugins do not cover.Retrieval-augmented generation
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
Tool governancedescription, core coverage, coverage by ecosystem, framing by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): a count of providers removed.Tool governance
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
Yesterday
Agent access to your codecoverage by ecosystem revisedRewritten at the maintainer's request (2026-10-25): what SAP ships named whole, and what the community adds written from what its ABAP MCP servers state about how they run, connect and sign in.Agent access to your code
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
Sat 17
Agent access to your systemsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Agent access to your systems
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
Code reviewdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Code review
Show 7 more
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
IDE provisioningdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.IDE provisioning
Model visualisationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Model visualisation
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
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
Agent access to your codeframing by ecosystem revisedBeside Agent access to your systems, the ABAP door read as two names for one thing. This one is about the code, development objects reached through ADT; that one is about business data and operations. The atlas maintainer's decision.Agent access to your code
Agent evalscore coverage, coverage by flavor, facets, gap revisedThe note rested on "everyone" and "nobody", which nothing here sources. The replacement says what the material read on the three doors covers and what it leaves to the project, which is checkable.Agent evals
Agent guidancecoverage by ecosystem, framing by ecosystem, facets, coverage by flavor, framing by flavor revisedskillOverflowDanKromp/skillOverflowA collection of 41 agent skills, 37 for CAP, Fiori, BTP, UI5, ABAP, Integration Suite and HANA work and four for creating, reviewing and retiring skills, each with its own eval.independent, cap entered on 2026-09-18, after this flavor was assessed, serves the UI5 door and states no flavor, so by the flavor rule it answers in all of them. Its own skill list names SAPUI5 data binding, custom controls, i18n and testing and nothing about the component library, so it is reported as a fallback rather than read as a community presence here. Saying so is what keeps core-only honest beside the options the page lists.Agent guidance
LLM integrationcore coverage, coverage by flavor, framing by flavor, facets revisedTwo questions the options here answer differently and the page could not show. Which models an option reaches is the first fact a reader needs, because all but one of the CAP options are clients of SAP AI Core; whether the response can be streamed decides whether a chat surface is possible at all. Both are scoped to cap: the ABAP, UI5 and BTP options were not read for them in this pass.LLM integration
Show 2 more
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
Agent access to your codenormative relevance revisedThe policy's agentic provision reaches every server that calls ADT for an agent; it was stated on arc-1 alone and as unsourced prose in several boundaries.Agent access to your code
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
LLM integrationcoverage by flavor revisedThe PromptInput page no longer carries the sentence this rested on. Read again on 2026-10-14 it states "The @ui5/webcomponents-ai package is under development and considered experimental - components' APIs are subject to change. Furthermore, the package supports Horizon themes only", with no version marker in it. The since-2.0 claim had no second source, so it goes rather than stand unsourced; the experimental state and the Horizon-only limit stay, in the words the page now uses, which are the words coverage_by_ecosystem.ui5 already quoted. The flavor's own assessment of who provides it was not redone, so assessed_at stands.LLM integration
Mon 12
Agent access to your systemscore coverage, coverage by ecosystem, description revisedMaintainer requested complementary boundaries so a CAP bridge can connect system access and application MCP exposure, while implementation restrictions remain explicit. Domains, providers and task classifications are unchanged.Agent access to your systems
Fri 9
Agent access to your systemsentry revisedSplit out of MCP servers at the maintainer's decision. That capability named a protocol and carried two concerns: exposing what you built to agents, which stays there under a name that says so, and giving agents a way into an SAP system you run, which is this one. Thirty providers moved with their own sentences; the Commerce and SuccessFactors slots moved with them. Named beside agent access to your code, its development-time sibling.Agent access to your systems
Agent guidanceecosystems revisedSAP Commerce opened as a product door (docs/concepts/product-doors.md, ADR-0033) and sap-commerce-skillsap-commerce-skillAn agent skill for SAP Commerce Cloud 2211-jdk21.1 and later: 21 reference guides, 58 code templates and three shell scripts, installed through the skills CLI.independent, commerce entered behind it with no tile to sit under. Packaged knowledge for the Commerce type system, service layer, ImpEx and OCC API is the same concern the node already holds on four doors, so the key was added rather than the capability forked.Agent guidance
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
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
Local developmentcore coverage revisedcapire audit 2026-09-27, judgement pages read once more: a page this capability owns was cited nowhere.Local development
Retrieval-augmented generationcore coverage revisedcapire audit 2026-09-27, link-only pages read a fourth time: vector embeddings are one of the three things SAP frames as CAP's native AI support, in the one sentence the section's index says of its own.Retrieval-augmented generation