NewABAP, RAP and ABAP Cloud
In the last 7 days
25 changes
Today
Cloud ALM Link for ADTadded to the atlasEclipse plugin linking ABAP transports to SAP Cloud ALM featuresEditor support
SAP TCode Runneradded to the atlasVS Code sidebar that opens SAP transactions through WebGUIFinding a transaction code
ZASISadded to the atlasRegex RuleSets that read barcode strings into named fieldsSerialisation
Yesterday
ABAP Syntax Highlightingadded to the atlasVS Code syntax highlighting for .abap filesEditor support
Fri 23
EPOD ADT MCP Serveradded to the atlasMCP server for ABAP on the ADT session, in Eclipse or standaloneAgent access to your code
Thu 22
B-Tocs ABAP SDKadded to the atlasWeb service client and connector layer for calling out of ABAPHTTP clients
Klystronadded to the atlasMCP server in ABAP inside the application server, with agent skillsAgent access to your code
pyapi4abapadded to the atlasTemplate pairing a FastAPI service with ABAP reports that call it
Skybuffer AI MCP serveradded to the atlasABAP add-on serving business data and transactions as MCP toolsAgent access to your systems
Show 1 more
@mcp-abap-adt/corereleased 20.0.0ABAP ADT MCP server published as an npm scope and pluginAgent access to your code
Wed 21
abap-ai/mcp2added to the atlasStateless ABAP MCP server SDK for the 2026-07-28 protocol draftServe your application over MCP
@mcp-abap-adt/corereleased 19.0.0ABAP ADT MCP server published as an npm scope and pluginAgent access to your code
Mon 19
ABAP Call Hierarchyadded to the atlasEclipse plugin showing the call hierarchy of ABAP membersEditor support
ABAP Code Searchadded to the atlasEclipse plugin searching ABAP sources from the search dialogSearching code in a system
ABAP Search and Analysis Toolsadded to the atlasEclipse plugin for ABAP object search and CDS view analysisSearching code in a system
ABAP Tagsadded to the atlasEclipse plugin for tagging ABAP repository objectsEditor support
Show 9 more
agentic-abap-evalsadded to the atlasABAP navigation tasks and a grader for coding agentsAgent evals
Building Code-Based AI Agents on the BAIPpublishedA Devtoberfest 2026 session on writing the agent yourself rather than configuring one, which is the agent toolingAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.SAP and community, unassessed edge: an agent is a model with tools, skills, memory and context around it, and the session reads the code of one built in CAP as a LangGraph state graph, with an agent node that calls the model, a tools node holding the MCP clients, and the edge between them looping until no tool is needed. It then shows the shorter route, a CDS service annotated for the agent protocol with its instructions and skills in an agent.md file. SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp carries both, with the CAP service in front of it as middleware so the credentials never reach the browser, and that is what cap-agent-ui5-webuicap-agent-ui5-webuiGives a CAP agent a UI5 web interface out of the box, so an agent built in the service has somewhere to be talked to without a separate frontend project.independent, cap is demonstrated against: added as a dependency, it gives the annotated service a UI5 chat interface that can be deployed rather than only previewed. A Python multi-agent application on Cloud Foundry, where an orchestrator delegates to per-stack specialists so no single model sees every tool, closes the session.Agent tooling
Supply Chain Rescueadded to the atlasCAP and SAPUI5 demo of recovery from a supply disruption
ABAP Select Converterflavors, description, links revisedThe flavor rests on the page's own "It is primarily used to migrate existing code to ABAP Cloud."; nothing on either page places the tool in standard ABAP. The page's "Additional infos" link was read for the first time and is now links.docs: it states the beta and lists what the converter supports and does not, which replaces the earlier "nothing for a batch of statements", a limit read off what the form does not show. The my-ide-actionsmy-ide-actionsA collection of eight ABAP Development Tools IDE Actions covering class creation, conversion of classic Open SQL to ABAP SQL, code snippets and RAP tooling.independent, abap sentence now follows that repository's own words, "The basis is the SwH tool" and the security table's "SELECT Converter | Software-Heroes API | -> Full SELECT Statement", and calls it an IDE Action rather than a package, which is the type that entry carries.ABAP Cloud readiness
CDS Field Mappingdescription revisedSAP's Cloudification Repository is in the graph, so the README's source is named by its entry rather than by a URL none of this entry's sources gave. The README's sentence is "Source will be the Cloudification Repository, where the mapping old table to new Core Data Services is listed.", so the prose reports it as what the README names and not as how the mapping file is produced today: the file in the repository comes from an extractor class you copy and run in your own system. The CAST, CASE and ABS gap is attributed to the tool's page, which is where that sentence stands, rather than to the README.Data modelling
Cloudification Repository Viewerflavors revisedThe documentation's Introduction places what the viewer shows in one flavor: "The Cloudification Repository is part of the new ABAP Cloud development model and lists released standard APIs that can be used to build the TIER 1 layer." Neither page states a standard ABAP use, so that flavor is left unstated.ABAP Cloud readiness
secondsky/sap-skillstype properties, flavors revisedRead today in the two plugins that answer the CAP and the UI5 door, which the ABAP pass had not opened. The sap-cap-capire skill's frontmatter states that it covers Node.js and Java runtimes, so CAP's two flavors rest on the maintainer's sentence where the entry previously answered in both by the serves-another-door fallback, which is the same reading off an absence. The sapui5 skill's frontmatter names freestyle apps and Fiori elements apps in one clause, so freestyle is stated, and fiori-elements moves onto that sentence from the README line about which request activates sap-fiori-tools, which said what triggers a plugin rather than what it covers. Nothing read names UI5 Web Components, so that flavor stays unstated. Stating freestyle changes an answer: the entry answered no there while it stated one UI5 flavor and now answers yes, which a reader comparing that flavor's options will see. The ABAP pair is unchanged.Agent guidance
Werkbankprovides revisedWhat Werkbank adds for ABAP, CAP and UI5 is its catalog of development skills; the workspace itself is not specific to any of those stacks. Agent workspaces is narrowed back to BTP.Agent guidance
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