onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
NewABAP, RAP and ABAP Cloud

New in ABAP

7 days30 days90 daysAll time
In the last 90 days
21releases453added to the atlas203new pieces of content207revisions
Change
Kind: 2
Origin
Domain
Clear all
884 changes
DayCapability
Kind ArtifactsKind Content

Today
3 changes
Cloud ALM Link for ADTadded to the atlasEclipse plugin linking ABAP transports to SAP Cloud ALM featuresIDE extension,
SAP TCode Runneradded to the atlasVS Code sidebar that opens SAP transactions through WebGUIIDE extension,
ZASISadded to the atlasRegex RuleSets that read barcode strings into named fieldsPackage,
Yesterday
1 change
ABAP Syntax Highlightingadded to the atlasVS Code syntax highlighting for .abap filesIDE extension,
Fri 23
1 change
EPOD ADT MCP Serveradded to the atlasMCP server for ABAP on the ADT session, in Eclipse or standaloneMCP server,
Thu 22
5 changes
B-Tocs ABAP SDKadded to the atlasWeb service client and connector layer for calling out of ABAPPackage,
Klystronadded to the atlasMCP server in ABAP inside the application server, with agent skillsMCP server,
pyapi4abapadded to the atlasTemplate pairing a FastAPI service with ABAP reports that call itSample,
Skybuffer AI MCP serveradded to the atlasABAP add-on serving business data and transactions as MCP toolsMCP server,
Show 1 more
@mcp-abap-adt/corereleased 20.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
Wed 21
2 changes
abap-ai/mcp2added to the atlasStateless ABAP MCP server SDK for the 2026-07-28 protocol draftMCP server,
@mcp-abap-adt/corereleased 19.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
Tue 20
2 changes
Joule for Developers with SAP BTP ABAP Environment-Setup GuidepublishedA step-by-step setup guide for SAP Joule for Developers, ABAP AI capabilities under its Q2 2026 limited-promotion licence: creating a BTP subaccount, adding ABAP environment and HANA compute-unit entitlements, enabling Cloud Foundry, configuring trust to Cloud Identity Services, creating the ABAP environment instance and assigning the developer role, then pointing ABAP Development Tools for Eclipse at the new system. It walks through the resulting Joule chat, predictive code completion, explain, ABAP Unit and CDS test-generation features inside a newly created ABAP Cloud project.Blog,
What an AI infra engineer sees when opening SAP's AI stack (1/3): the model gatewaypublishedA first look at SAP AI Core's Generative AI Hub from someone who builds gateways outside SAP for a living: the orchestration service harmonizes provider calls onto one API (a model name string switches providers, and SAP Note 3437766 carries the current model list, token rates and deprecation dates), runs a fixed, non-reorderable module pipeline — templating, masking through SAP Data Privacy Integration, grounding, content filtering, then the model call — and retries down an ordered fallback list whose entries can each carry their own model and rules. It places @sap-ai-sdk/orchestration among the official JavaScript, Java and Python SDKs, and notes SAP's own LiteLLM provider as a way to put a different gateway in front of it.Blog,
Mon 19
35 changes
🟣 Bring AI into Your ABAP Applications with ISLM: Build, Integrate, and Consume AI NativelypublishedDevtoberfest 2026 session AI-11, from the product manager and product owner of Intelligent Scenario Lifecycle Management: ISLM as the place an AI use case is registered, deployed and operated inside an SAP S/4HANA system, and what has been added to it for generative AI. The demo builds a custom scenario end to end — an intelligent scenario of type generative AI, a connection to SAP AI Core, a GPT-5 mini model, an orchestration flow template that configures data masking, input and output filtering and translation into the user's logged-in language, then prompts with a grounding query over five companies' return-policy documents — and consumes it from an ABAP report through the ABAP AI SDK, which calls the orchestration API and returns the summary as JSON. Two newer pieces follow: SAP RPT, the relational pre-trained transformer for tabular prediction, called with context rows and query rows and answering with a confidence value and no training step; and system-triggered agents, where an application job in the ABAP system starts a billing-creation agent that reaches S/4HANA OData APIs as tools through the agent gateway with principal propagation. The closing availability matrix states the generative AI capabilities for on-premise and private cloud from the 2021 release, with SAP notes to implement on lower ones.Talk,
🟣 Enable Your AI application to Run on Multiple Models to Ensure Resilience and CompliancepublishedDevtoberfest 2026 session AI-21. A cross product owner on the SAP AI Core team gives the reasons an AI application ends up on more than one model — a model down at the hyperscaler, a data centre that is not allowed to run it, a version being deprecated — and runs a joke app that answers from Gemini 2.5 Flash in EU10 and from Claude 4.5 Haiku in Asia-Pacific. The walk through AI Core's parts is where the edges hold: prompts kept as templates in the prompt registry, imported through the launchpad and the APIs or synced as YAML from a git repository (Prompt management); the evaluation service scoring one prompt across up to four models per run on built-in or model-as-judge metrics, and the prompt optimizer generating variants against one metric (Agent evals); and the orchestration service harmonising the providers behind one message format with a priority-sorted fallback list (LLM integration). The session also states where a metric has to be designed rather than picked: an exact-JSON match scores an email generator at zero, so the joke app's custom metric judges topic and family-appropriateness instead.Talk,
ABAP AI SDK powered by ISLM - How to implement your own AI use cases in ABAPpublishedA Devtoberfest 2026 ABAP-track session (ABA-44) on the ABAP AI SDK: an intelligent scenario development object holds the model and its version, so the ABAP code asks for an API, sends a prompt and reads the completion with its token counts and finish reason, and swapping the model is a change to that object rather than to the code. Four demos go through the ABAP line by line — a bare completion, a system prompt with the temperature set to 0.2, tool calls where the model asks for order details and the result goes back into the message container, and a JSON response schema that returns category, severity and goodwill as fields a program can act on — and a fifth replaces the API with the SDK's own mocks so unit tests run with no network call, which is what the LLM integration edge on the ABAP door rests on. The closing availability matrix separates base scenarios, available across SAP S/4HANA on-premise, private edition, public cloud and the SAP BTP ABAP environment, from the orchestration service and SAP RPT, shown for on-premise and private cloud with transport-based correction instructions back to release 2022 and not yet for the public cloud editions.Talk,
ABAP Call Hierarchyadded to the atlasEclipse plugin showing the call hierarchy of ABAP membersIDE extension,
Show 31 more
ABAP Code Searchadded to the atlasEclipse plugin searching ABAP sources from the search dialogIDE extension,
ABAP Development Tools for VS CodepublishedA Devtoberfest 2026 session on ABAP Development Tools for VS Code: where the extension sits after the ABAP Workbench and ABAP Development Tools for Eclipse, the ADT language server both editors share, and what the releases since May 2026 cover. The demo installs the extension, creates a destination, opens, creates and activates objects, runs ATC and ABAP Unit, and names the object types, domains among them, for which a developer still goes to Eclipse or SAP GUI. It also opens the extension's settings to turn on the ADT MCP Server and shows the tools a chat can call, with the object search and source code search tools listed as planned.Talk,
ABAP Search and Analysis Toolsadded to the atlasEclipse plugin for ABAP object search and CDS view analysisIDE extension,
ABAP Tagsadded to the atlasEclipse plugin for tagging ABAP repository objectsIDE extension,
Agentic Loop with Joule for Developers and ADT MCP ServerpublishedA Devtoberfest 2026 session from SAP's ABAP AI team that generates a RAP issue-tracker application by prompting a coding agent. It covers what SAP Joule for Developers, ABAP AI capabilities now ships as MCP tools and which assistants can reach an ABAP system's virtual filesystem, then does the setup twice: turning on the ADT MCP Server and pasting the Joule side-by-side tenant link in ABAP Development Tools for VS Code, and again in ABAP Development Tools for Eclipse, where the custom agent becomes custom instructions. The demo's subject is the guardrails around the loop — an agent.md of phases and human checkpoints, skill files cloned from a GitHub repository for naming, ATC compliance and UI annotations — run through GitHub Copilot until the generated objects are activated, unit-tested and in a transport.Talk,
agentic-abap-evalsadded to the atlasABAP navigation tasks and a grader for coding agentsCLI,
AI-assisted SAP development with MCPpublishedA Devtoberfest 2026 session (UI-41) that traces AI-assisted SAP development from pasting code into a chat window to coding agents with built-in connectors, and sorts the MCP servers around SAP development into SAP's own, the community's and the hosted ones, where the agent cannot change what the server allows. Four demos follow: GitHub Copilot alone explaining an ABAP report from a Git repository, @ui5/mcp-server reading an OpenUI5 sample app and converting it to TypeScript, mcp-sap-docs grounding Terraform files for a BTP subaccount the presenter had not written before, and arc-1 with Copilot in Eclipse tracing why a title longer than 40 characters is rejected and proposing the DDIC-allowed length instead. It ends on a skill that migrates an SAP Gateway project on an ECC system to RAP on S/4HANA step by step, and on a rule Marian Zeis gives for servers written for internal use: keep them read-only, because what the agent is short of is context.Talk,
Always in Sync — Field-level and event-driven side effects for reactive UIs in RAPpublishedA Devtoberfest 2026 session on side effects in RAP — the declarations in a behaviour definition that tell a draft UI to reload what a change affected, instead of leaving the user to refresh the browser. Field-level side effects recalculate a total price from a determination when a booking fee is entered, including across the association from a child item up to the root entity, and a permissions side effect toggles a description field between read-only and editable; a global side effect is attached to a determine action, fires when the user presses Enter, and only one may exist per business object, which is why the prepare action and a second determine action cannot both carry it. The last part starts a long-running calculation through the background processing framework and raises a business event that the behaviour definition lists as a side effect source and the projection makes public, so the Fiori app is updated with a notification when the work finishes, whether it was triggered by the user or by an application job — the transactional model and the async processing side the edges rest on.Talk,
Bridging Python and SAP HANA: Inside the sqlalchemy-hana Open-Source DialectpublishedA Devtoberfest 2026 data-track session (DAT-21) in which one of the maintainers of sqlalchemy-hana, the open-source SQLAlchemy dialect published in SAP's GitHub organisation, opens up what sits between Python and SAP HANA. It walks the five dialect classes that render statements, types, DDL, identifiers and sequences, and the HANA specifics they absorb: the FROM DUMMY a bare SELECT needs, a limit injected when only an offset is given, string compiled to NVARCHAR, and quoted case-sensitive identifiers against Python's lowercase. The rest covers schema migrations with Alembic on HANA's transactional DDL, the recently added async support and vector types, and that HANA Cloud and HANA 2 are supported while HANA 1 is not.Talk,
Bring "developers.sap.com" Into Your Dev Environment: SAP Developer Context for AI Coding AgentspublishedDevtoberfest 2026 session FA-11: a tour of the rebuilt developers.sap.com by the team that runs it, from the administration screens behind the home page to the agent interfaces in front of it. The site is a CAP application on SAP HANA Cloud and SAP BTP, open-sourced in full, and the half of the session that places it here is how its content reaches an agent: every tutorial is also served as markdown, a coding agent is detected and given that version instead of the HTML, a well-known agent card advertises what the site offers, and SAP Developers MCP answers questions about tutorials, news and a reader's own completion history in Claude Code and Joule Desktop, over OAuth or a personal access token. Behind the answers sit two things working together: a knowledge graph in the HANA database over 1400 tutorials and 11,000 concepts, and SAP AI Core for the Joule interactions and the embeddings, with the agent harness written for the site rather than taken off a shelf. Where neither MCP nor A2A is available, the same content is published as skills.Talk,
Building Agentic Workflows with n8n in Joule StudiopublishedA Devtoberfest 2026 session, JS-31, on SAP-managed n8n inside Joule Studio, shown as a labs preview on a blocked-invoice scenario: a solution made of assets, an intent refined by the web agent into requirements and then a specification, and the generated workflow opened in the n8n editor that Joule Studio connects to its own n8n tenant, with the generated files committed through GitHub. The nodes carry the other edges — the human-in-the-loop node is built on SAP Task Center, and SAP AI Core is where model providers are configured centrally instead of per developer. It ends in Joule chat, where the approval task the workflow created is listed, opened and completed.Talk,
Building Code-Based AI Agents on the BAIPpublishedA Devtoberfest 2026 session on writing the agent yourself rather than configuring one, which is the agent tooling 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 Core 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-webui 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.Talk,
CDS Associations & JoinspublishedA Devtoberfest 2026 session from SAP's performance and scalability team on what an ABAP CDS association becomes on SAP HANA, taken as an excerpt from their internal performance training. The CDS edge rests on the three ways an association is used: a path expression and an explicit join both put a left outer join into the generated view, while exposing the association leaves the view without one and adds the join only for a query that asks for its fields, which the session calls join on demand. The data modelling edge is the advice that follows and the demo under it — cardinality written as precisely as the data allows, because the optimiser trusts it, shown with a view whose missing cardinality let SELECT COUNT(*) prune the join and return 18 rows where selecting the columns returned 56, plus the left-hand, right-hand and left-outer-to-inner rewrites that correct cardinalities make possible.Talk,
Developing authorizations for business users in SAP Business AI Platform, ABAP environmentpublishedA Devtoberfest 2026 session that walks the places an authorization check has to be written when a RAP business object is implemented, which is the whole of the authorization edge: read restrictions as DCL access controls that become a filter at query time, a child entity inheriting its parent's conditions through an association, the projection layer inheriting rather than changing them, and the same check repeated on the draft side. The ABAP CDS edge holds on that draft half — until 2608 a draft query view was needed above the draft table so a DCL had something to attach to, while a draft table entity is already on CDS level and takes the DCL directly, as long as the associations used in the inherited conditions are redefined on it. Create, update and delete are then taken handler by handler, including the trap that instance authorization reads the buffer and so cannot see the new value a pre-check would reject, and the session closes on in local mode and privileged EML calls.Talk,
Edge Integration Cell - what's new?publishedA Devtoberfest 2026 integration-track session (INT-41) on Edge Integration Cell, the runtime of SAP Integration Suite a customer runs on their own Kubernetes cluster while design, configuration and monitoring stay in the cloud tenant. It names what the customer has to provide — a supported Kubernetes platform, SAP HANA or PostgreSQL, Redis or Valkey as data store, a load balancer — then the Edge Lifecycle Management cockpit with its monthly rolling updates, the inbuilt and the external Cloud Connector options and why a DMZ placement calls for the second, and the adapters available only on Edge: RFC sender, NFS, OFTP2 and UNF. The demo deploys an OFTP-to-file flow to the Edge runtime and shows the same flow rejected when its runtime profile is switched to cloud, which is where the Integration flows edge holds.Talk,
How to Build Application Jobs in SAP Business AI Platform, ABAP environmentpublishedA Devtoberfest 2026 session on the application job framework in the cloud ABAP environment, built from the repository objects outwards: a class implementing the new application job interface, whose public attributes become the parameters and select options, the application log object it writes to, a job catalog entry that lays out sections, groups and value helps, and a job catalog template that works like a report variant. The demo schedules and monitors runs in the Application Jobs Fiori app, starts a job from a RAP action through the scheduling API under a job user of its own, and debugs one through the template's run-for-testing entry. It closes on the alternatives for work that should not be a job — the background processing framework for short-running work, and RAP events consumed locally or sent over the event mesh — which is the async processing this session covers for SAP BTP ABAP environment.Talk,
How to implement business AI capabilities in ABAP CloudpublishedA Devtoberfest 2026 session (ABA-32) on embedding AI in an ABAP Cloud application and on making SAP Joule aware of what that application can do. The first demo implements two features of a RAP travel app with the ABAP AI SDK: a determination on an uploaded receipt that sends the image together with the allowed categories and transaction types to a model reached through an intelligent scenario, then writes the extracted description, category, currency and amount back to the expense entity; and a recommendation function, triggered by a side effect on the trip title, that proposes a trip type with a score the Fiori UI sorts the proposals by and leaves the business user to accept — which is LLM integration from ABAP code. The second demo builds a capability for SAP Joule in the Joule Studio code editor in VS Code, with a scenario that extracts a trip title from the user's intent and calls an OData service in the ABAP backend through a BTP destination, deploys it and asks the Joule test UI for the trip's details; the session states that agents reach ABAP only over governed remote APIs — OData, SQL and MCP — and that automatic grounding of custom OData services in the knowledge graph is upcoming rather than available.Talk,
Intelligent App Development at Scale: SAP Fiori Elements + ABAP Development Tools for VS CodepublishedA Devtoberfest 2026 session (UI-33) that builds a RAP service and the SAP Fiori elements app over it from one VS Code workspace, with a coding agent driving two of SAP's MCP servers. The ABAP Development Tools for VS Code edges hold on the demo itself: its virtual file system keeps the ABAP package beside the Fiori project, the ADT MCP Server inside it creates, changes and activates the ABAP objects, and a version not yet released publishes the service binding from the agent instead of by hand. The @sap-ux/fiori-mcp-server edge covers its generators and the three-step workflow it uses for changes — list the functionality available for the application, ask for its JSON schema, then execute it — and the agent guidance edge rests on the skills the Fiori team publishes beside it, on the session's account of what a skill adds that a server does not, and on the analytical chart demo where a skill orchestrates both servers in one task.Talk,
News from Custom Code Migration: ECC to SAP S/4HANA Powered by Agentic AIpublishedA Devtoberfest 2026 session (ABA-23) on what SAP has added to the ECC to SAP S/4HANA custom code migration tools, demonstrated across a live ECC and an S/4HANA system. The first half stays deterministic and explains static analysis in that process: the custom code migration app's scoping over ABAP test cockpit findings, an explain of a legacy report and of an S/4HANA simplification finding, and transferable quick fixes exported from the app and applied on the ECC system through the SAP GUI ATC transaction before conversion. The second half runs the S/4HANA custom code migration agent in ABAP Development Tools for Eclipse: GitHub Copilot drives the ADT MCP Server's ATC and quick-fix tools in a loop, SAP Joule for Developers, ABAP AI capabilities produces the AI code proposals behind it, and only the high-confidence ones are written into the code, the rest left as comments in one transport request.Talk,
S/4HANA Custom Development - What happens in case of errors in BAPIs or RAP BOs?publishedA Devtoberfest 2026 session on what a custom S/4HANA process does when a BAPI or a RAP business object fails. It is framed from project work rather than product development, with the same issues and challenges turning up on project after project, and it offers the ABAP Processing Center, ABAP-PRC, as what fills the gap it names in modern ABAP development. The edges rest on the opening, which states the session's subject as errors in S/4HANA custom development, read as error handling on the ABAP door, and names that framework.Talk,
SAP BAIP, ABAP environment – How to build partner solutions and get them certifiedpublishedA Devtoberfest 2026 session on the two ways a partner ships an ABAP Cloud solution built on SAP BTP ABAP environment, which the session calls the ABAP environment of SAP Business AI Platform: software delivery, where an add-on product is published with the solution ID from SAP Store onboarding and the customer discovers and deploys it into their own system, and service delivery, where the partner operates the same add-on as a multi-tenant SaaS and a new version is deployed rather than published again. That is the ABAP environment edge; the static analysis edge rests on the quality steps shown in the landscape portal, where the Manage Continuous Testing app released with 2608 runs an ATC check variant against a configured system on a recurrence pattern, beside test product version builds and managed test tenants. The second half walks through the SAP Integration and Certification Center process and the three BTP certification options open to an add-on product.Talk,
Supply Chain Rescueadded to the atlasCAP and SAPUI5 demo of recovery from a supply disruptionSample,
Unlocking Tabular Foundation Models: From Experimentation to ProductionpublishedA Devtoberfest 2026 session (AI-41) on taking tabular prediction from a playground to a deployment. It sets tabular foundation models against a model trained per use case and against language models reading rows as text, explains in-context learning as examples plus the rows whose target column is missing, and tries SAP RPT 1.6 on a train-delay dataset in the RPT playground, including the column and row importance it returns with the prediction. The same prediction is then rebuilt on SAP AI Core, where the tabular orchestration service plays the part the orchestration service plays for language models: a data destination, a table artifact with its CSN schema and a scenario configuration registered once at design time, after which a predict call passes only the query rows, the scenario configuration and a context-selection strategy. The last demo runs those same calls in natural language through the aicore-skills plugin in a coding agent, and one of them only resolves once the agent is told which scenario configuration to use.Talk,
Updates on Embedded Analytics in ABAP Cloud for DeveloperspublishedA Devtoberfest 2026 session (ABA-33) on the generator wizards for Embedded Analytics in ABAP Cloud, run by right-clicking a data definition in the ADT Project Explorer. It first names the artefacts a star schema needs, all of them ABAP CDS — cube view at its centre, dimension, text and hierarchy views reached by association, a hierarchy directory, and an InA service definition and binding — and then generates them: the star schema generator reads a view entity's metadata, sorts its fields into dimensions and measures, asks about the ones it cannot decide, offers the dimension views it found and writes an activated cube view; the hierarchy generator produces directory, node, base and definition views plus a maintenance business object with a generated app, which is used to group airlines into alliances before the hierarchy is switched on in the layout of the multi-dimensional analysis app. That is analytic modelling on the ABAP platform, which is what the edges rest on; the outlook names time-dependent hierarchies, translatable texts and dimensions generated from database tables.Talk,
What's new with draft handling in RAP?publishedAn ABAP-day session at Devtoberfest 2026 on two additions to draft handling 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 Fischer 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-flight, and the last part hides the draft-related features of an OData 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.Talk,
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-actions 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.Web tool,
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.Web tool,
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.Web tool,
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.Skill,
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.Desktop app,
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.Web tool,
Sun 18
8 changes
abapsmithadded to the atlasABAP MCP server over ADT with a local journal that can undo writesMCP server,
CAP in the age of AI #3 - from MCP to A2ApublishedThe episode that finishes @cap-js/mcp with authorisation and then crosses to agents. @requires and @restrict are the same annotations CAP already has, and the plugin reads them to filter the tool list and the describe output per user and per request, so a model is not told about entities the caller cannot reach — where the OData metadata of the same service lists every exposed entity regardless. The second half annotates a service with @agent from @cap-js/agents, which serves it over A2A with an agent card and a chat preview, runs first against a mocked response and then against SAP AI Core bound with cds bind and a hybrid profile, and reuses the MCP adapter's tools rather than defining new ones.Video,
CAP in the age of AI #6 - vector embeddingspublishedVector embeddings put to work in the incident management sample, answering whether this problem has been seen before. An embedding element of type Vector is calculated and stored from the vector_embedding function, so the database refreshes it whenever the text behind it changes, and cosine_similarity compares it with a freshly embedded string; because a title says little, a scheduled action first summarises each incident's conversation through a model on SAP AI Core and the embedding is taken from that summary. The similar-incidents list is a view joining incidents to themselves, with order and limit set in a before handler on the expanded query, and the vector element excluded from the service, since OData knows nothing about vectors — on SAP HANA Cloud the function is native, while SQLite needs packages added to the project.Video,
CAP in the age of AI #7 - vector embeddings wrap-uppublishedThe same embeddings model taken from SQLite to SAP HANA Cloud, then handed to an agent. Locally it is @cap-js/ai that adds the vector functions SQLite lacks and downloads an all-MiniLM L6v2 ONNX model on first start; on HANA natural language processing has to be switched on, the model name is a mandatory argument, the vectors it returns are 768 dimensions, and dimensions must match on both sides of a comparison. HANA itself can be given SAP AI Core as a remote source for other embedding models, which a CDS.ql expression has to inject because the postfix notation only takes what the CDS model holds, and the hour ends with a search function over cosine similarity exposed over @cap-js/mcp, so an agent asked about low output from solar panels calls semantic search instead of writing the query itself.Video,
Show 4 more
Modernization Agents for SAP on AWSadded to the atlasAWS agents for ABAP, PI/PO and BW modernisation workApp,
SAP Developers MCPadded to the atlasHosted MCP server of developers.sap.com tutorials and missionsMCP server,
SAP S/4HANA Cloud: Scheduling Background Jobs Using Application Job TemplatespublishedWalks through moving S/4HANA Cloud and ABAP Environment job scheduling off ECC's SUBMIT and JOB_OPEN/JOB_SUBMIT/JOB_CLOSE pattern onto the Application Job Framework: a job template built from an ABAP class that implements IF_APJ_DT_EXEC_OBJECT and IF_APJ_RT_EXEC_OBJECT, then scheduled through the Manage Application Job Templates Fiori app or programmatically with CL_APJ_RT_JOB_SCHEDULING_API's SCHEDULE_JOB method. The resulting job is tracked in the Monitor Application Jobs app, where status, logs and failed runs are reviewed.Blog,
SAP Developers MCPentry revisedNEIGHBOURS §5.1 named the hosted MCP as a companion to index as an artifact, and the graph had no entry for it. ecosystem: umbrella because its content covers SAP technologies across stacks (llms.txt names ABAP Cloud, CAP, Fiori, HANA Cloud and integration) and no single door holds it. No read_only: the anonymous mounts are read-only, but the signed-in tier writes progress (complete_step). No tool_count: the quickstart and the API page list different tools per mount. The site also serves a GraphQL API, not recorded as an interface here for want of a page read. /mcp/homepage is left out of the description: the quickstart lists it as anonymous and the API page as signed-in.MCP server,
Sat 17
112 changes
@abap2ui5/embed-controladded to the atlasUI5 custom control that runs an abap2UI5 app inside a host appPackage,
@abap2ui5/linteradded to the atlasCommand-line checker for abap2UI5 app classes and their viewsCLI,
@abap2ui5/mcp-serveradded to the atlasMCP server for the abap2UI5 check, deploy and run loopMCP server,
abap-agent-runtimeadded to the atlasABAP-native MCP endpoint that drives opted-in abap2UI5 appsMCP server,
Show 108 more
abap-cloud-guiadded to the atlasReport-style programming model for abap2UI5 on ABAP CloudPackage,
abap2UI5 for Exceladded to the atlasOffice add-in running an abap2UI5 app in Excel's task paneApp,
abap2UI5 for VS Codeadded to the atlasVS Code extension to preview, activate and lint abap2UI5 appsIDE extension,
abap2UI5 frontendadded to the atlasabap2UI5 frontend as ABAP artefacts installed with abapGitPackage,
abap2UI5 frontend-webcomponentadded to the atlasabap2UI5 frontend rendering with UI5 Web ComponentsPackage,
abap2UI5 headless frontendadded to the atlasDrives abap2UI5 app classes from ABAP Unit testsPackage,
abap2UI5 Layout Editoradded to the atlasDrag-and-drop UI5 view editor that writes an abap2UI5 app classWeb tool,
abap2UI5 mobile shelladded to the atlasNative iOS and Android shell for one abap2UI5 endpointDesktop app,
abap2UI5 Playgroundadded to the atlasIn-browser ABAP editor beside the abap2UI5 app it buildsWeb tool,
abap2UI5 protocoladded to the atlasVersioned specification of the abap2UI5 roundtrip protocolPractice,
abap2UI5 samplesadded to the atlas129 abap2UI5 sample apps, one ABAP class eachSample,
abap2UI5-addons/open-source-libsadded to the atlasEleven abap2UI5 apps, one per open-source ABAP librarySample,
abap2UI5-addons/popupsadded to the atlasReady-made dialogs for abap2UI5 appsPackage,
abap2UI5-localadded to the atlasabap2UI5 folded into the local classes of one HTTP handlerPackage,
abap2UI5/samples-controlsadded to the atlasUI5 Demo Kit samples rebuilt as abap2UI5 appsSample,
abap2UI5/samples-stackadded to the atlasabap2UI5 apps in front of OData, RAP, events and other technologySample,
admin-cockpitadded to the atlasUsage, error and response-time monitor for abap2UI5App,
app-templateadded to the atlasStarter repository for an abap2UI5 app with CI and agent setupSample,
Clean-Core.ioadded to the atlasHosted workspace redrawing custom ABAP as BPMN and grading itWeb tool,
Cloud-Native with ABAP Cloud – The Transactional Outbox PatternpublishedImplements the transactional outbox pattern in ABAP Cloud's background processing framework (bgPF): a RAP business object's save sequence registers a bgPF handler implementing IF_BGMC_OP_SINGLE, and the RAP runtime runs it, and only then emits the message, after the database commit succeeds, so a rolled-back transaction emits nothing. The post walks through the full working example published as SAP-samples/abap-platform-rap-transactional-outbox-with-bgpf.Blog,
Cloudification Repositoryadded to the atlasSAP's list of released APIs for SAP Cloud ERP with successorsWeb tool,
config-managementadded to the atlasTheme, CSS and CSP settings of abap2UI5 pages kept in tablesApp,
custom-controlsadded to the atlasThirteen custom UI5 controls for abap2UI5 appsPackage,
custom-controls-customeradded to the atlasTemplate repository for own UI5 artefacts served to abap2UI5Sample,
ERPLadded to the atlasDuckDB extension reading SAP ERP tables, CDS views and BW queriesPackage,
erpl-node-rfcadded to the atlasRFC client for Node.js and TypeScript without the NW RFC SDKPackage,
http-connectoradded to the atlasForwards abap2UI5 roundtrips to another system over HTTPApp,
launchpad-kpiadded to the atlasPuts a number from an abap2UI5 app on a Fiori launchpad tilePackage,
layout-managementadded to the atlasTable and form layouts with saved variants for abap2UI5Package,
lock-manageradded to the atlasHolds SAP locks across stateless abap2UI5 roundtripsPackage,
rap-extadded to the atlasFloorplans rendered from CDS UI annotations as abap2UI5 appsPackage,
rfc-connectoradded to the atlasForwards abap2UI5 roundtrips to another system over RFCApp,
sapguiadded to the atlasThirty classic transactions rebuilt as abap2UI5 appsApp,
se16nadded to the atlasTable content browser in abap2UI5, for ABAP Cloud and on premiseApp,
selection-screenadded to the atlasSelect-options with saved variants for abap2UI5 appsPackage,
web-abap2UI5added to the atlasabap2UI5 transpiled to JavaScript and run in a browser tabWeb tool,
abap-adt-apireleased 9.0.01 content item in the atlas was written against an earlier version. Nothing is recorded about what changed.Package,
[Blog Post] SAP Event Mesh - Consuming S4 events simultaneously in CAP-based applications and SAP Integration Suiteexplains 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).Blog,
052: 10 Minutes from Start to Launchpadexplains 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).Blog,
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).Blog,
ABAP + MCP: Let AI Do Real Development in Your SAP Systemexplains 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).Blog,
ABAP code to wait for the end of "inbound bgRFC type Q" unitsexplains 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).Blog,
ABAP development tools for Visual Studio Code: Patch 1.0.1 releasedexplains 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).Blog,
ABAP development tools for Visual Studio Code: Version 1.1 releasedexplains 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).Blog,
Agentic CAP: Build MCP servers and enterprise AI agentsexplains 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).Talk,
Agentic memory: Knowledge graph engine and recall in SAP HANA Cloudexplains 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).Talk,
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).Talk,
AI-native North Star architecture — Platform Layerexplains 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).Reference architecture,
Analyze and optimize ABAP Cloud model apps built on core data servicesexplains 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).Talk,
Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]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).Blog,
AWS Mail configuration for SAP ABAP Systemsexplains 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).Blog,
BTP - Authorization Objectexplains 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).Blog,
BTP - Restriction Typeexplains 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).Blog,
Building agentic applications with SAP HANA Cloudexplains 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).Talk,
Building an Attachment Upload and Download Solution Using UploadSetwithTable Controlexplains 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).Blog,
Calculating IBP Technical Week "Key Figure Date" in S/4HANA Using CDS Viewexplains 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).Blog,
Calling Claude from ABAP: How I Wired SAP AI Core into a Real Business Scenarioexplains 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).Blog,
Capturing Background Job Errors in SAP Using the Application Log (SLG0/SLG1)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).Blog,
Claude Code via MCP: Poor man's Joule, or a practical tool?explains 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).Blog,
Cloudification Repository Viewerrequires, connects revisedSAP's Cloudification Repository entered the graph, so the repository this reads is a node rather than a name in a sentence. Both edges rest on the viewer's own documentation: the repository "lists released standard APIs that can be used to build the TIER 1 layer", and the Repository field is a "Selection of the different release statuses that are made available by SAP in different JSON files". No protocol, direction or condition: the documentation states none.Web tool,
Configure Journal Entry Posting Approval from Store Template in Build Process Automationexplains 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).Blog,
Configuring SAP Cloud Integration for an IBP to S/4HANA (on prem / private cloud) integrationexplains 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).Blog,
Consume ABAP RFC Function Modules in CAPexplains 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).Blog,
Consume Remote Services in a Full-Stack CAP Applicationexplains 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).Workshop,
Creating an SAP SD Billing Document Using a BAPI in SAP Build and Accessing It Through 'Joule Work'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).Blog,
Custom Form with Custom Data Source in SAP Public Cloud (Grow with SAP)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).Blog,
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).Blog,
Document Groundingexplains 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).Doc,
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).Talk,
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).Blog,
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).Blog,
From SEGW and Legacy UI5 to RAP with ARC-1explains 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).Blog,
Generating Adobe Form Using RAP framework OData Servicesexplains 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).Blog,
How I Use AI for Development and Why Context Mattersexplains 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).Blog,
How to Check Fiori Apps Related Authorization Object Massexplains 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).Blog,
How to Connect Claude Code to ABAP with Zero-Config MCPexplains 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).Blog,
How to rename an OData V4 service?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).Blog,
How to use SAP Data Intelligence with SAP Cloud Connectorexplains 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).Blog,
Integrating SAP S/4HANA Invoicing with KSeF Using SAP Event Mesh and CAPexplains 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).Blog,
Introducing ARC-1: A Secure ADT MCP Server for Enterprise SAP Developmentexplains 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).Blog,
Knowledge graph and agent memory: Build an agent that remembersexplains 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).Talk,
Merge multiple PDF forms into a single document for download or printing.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).Blog,
Modernizing RFC/BAPI-based Integrations for a Clean Core with SAP Integration Suiteexplains 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).Blog,
OData $batch Deleting Records Across Multiple Tables in Single Transactionexplains 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).Blog,
OData Deep Insert: Implementation and Real-Life Examplesexplains 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).Blog,
OData to outcomes—Build AI-enabled SAP Fiori apps using SAP Fiori elementsexplains 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).Talk,
Part 3: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]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).Blog,
Part2: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]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).Blog,
Patterns for using LLMs in ABAP developmentexplains 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).Doc,
Principal Propagation from BTP Web App to S/4HANA via SAP Integration Suiteexplains 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).Blog,
Print Preview from RAP Action with v4 OData and Multiple Selectionexplains 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).Blog,
RAP - Feature Control (Part 2)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).Blog,
RAP - Native File Uploadexplains 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).Blog,
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).Blog,
Running AI agents against SAP ECC 6.0: lessons from building an in-system MCP serverexplains 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).Blog,
S/4HANA Observability: Streaming SAP Cloud ALM & LogServ Telemetry to BigQuery & Vertex AIexplains 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).Blog,
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).Talk,
SAP IAM integration with SAP Cloud Identity Servicesexplains 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).Reference architecture,
SAP's API Policy on AI Agents: What It Prohibits, Allows, and Leaves Openexplains 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).Blog,
Scheduling a Background Job for the BDC Session Method Using RSBDCSUBexplains 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).Blog,
Set up the SAP Cloud Connector: Integrating On‑Premise Systems with Cloud Servicesexplains 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).Blog,
Spec first: The disciplined way to develop ABAP with agentsexplains 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).Talk,
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).Blog,
Transform your configuration of SAP S/4HANA Cloud with agentic AIexplains 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).Talk,
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).Blog,
Using Claude for SAP ABAP development on RFC-only / SAProuter systems (even ECC R/3)explains 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).Blog,
Using RFC Function Modules and BAPIs in SAP Build Process Automationexplains 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).Blog,
Why SAP Cloud Identity Matters for SAP Task Center: It’s About Trust and Global User IDexplains 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).Blog,
Fri 16
4 changes
Extending Standard S/4 HANA OData API'spublishedWalks through extending a standard S/4HANA OData API with a custom field, preferring OData V4 over V2 for its closer OASIS compliance and simpler service enablement, then tracing the extensibility objects documented for the entity before touching any code. The custom field reaches the API by layering three CDS view extensions — extendView on I_Product, extendViewEntity on R_ProductTP and on A_Product_3 — following the projection chain down to where the base table is first selected, built in ABAP Development Tools for Eclipse.Blog,
Hammer Core Servicesadded to the atlasABAP-side component for the Hammer editorApp,
open-steamgateadded to the atlasLocal ABAP server serving /IWBEP/ OData v2 without an SAP systemApp,
Tools for abapGitadded to the atlasHelper programs around abapGitApp,
Thu 15
32 changes
@abaplint/transpileradded to the atlasTranspiles ABAP to JavaScript to run on Node.jsBuild tool,
cross-http-clientadded to the atlasHTTP client for classic on-premise ABAP and ABAP CloudPackage,
express-icf-shimadded to the atlasShim running an ABAP ICF handler behind an Express 4.x serverPackage,
How to Create an Application Job (APJ) in SAP S/4HANA ABAP — With Single Values & Select OptionspublishedWalks through implementing an Application Job end to end on the ABAP door: a class implements IF_APJ_RT_EXEC_OBJECT for runtime execution and IF_APJ_DT_EXEC_OBJECT to define parameters, covering both single-value parameters and select options, then registers the class as a job catalog entry and template in ADT for scheduling through the Application Jobs Fiori app. Frames Application Jobs as the class-based, ADT-defined successor to the classic SM36/SM37 background job transactions.Blog,
Show 28 more
How to extend ABAP Test Cockpit on SAP BTP for custom use casespublishedWalks through the released, C1-contract APIs and CDS views for extending ABAP Test Cockpit on SAP BTP: the single entry point CL_SATC_API=>CREATE_API_FACTORY, reading a run's findings and headers through SATC_API_FINDINGS and SATC_API_RESULT_HEADERS, starting synchronous local ATC runs for a transport, approving or rejecting exemptions programmatically, configuring approver responsibility areas without a UI, and implementing a custom check through IF_CI_ATC_CHECK. Code snippets show each API in use, including the CDS views that join ATC results to the Custom Code Migration app's own findings.Blog,
How to Implement SAP Change DocumentpublishedBuilds SAP's Change Document framework on two custom tables, ZZCUSTOMER and ZZCUSTOMER_BANK: creating the Change Document Object in transaction SCDO, then wrapping each INSERT, MODIFY and DELETE on the Z-tables together with a call to the generated WRITE method inside one ABAP class, so both commit in the same Logical Unit of Work. Because the generated method cannot read old values back from the database itself, the class reads them before the update and holds them in memory; a Managed RAP application skips this step by specifying the Change Document Object directly in its Behaviour Definition instead. This is the ABAP side of change tracking: a change document object logs who changed a field, and when, into CDHDR and CDPOS.Blog,
On‑the‑Fly Excel Download in a RAP Fiori App — No Database Table, No Persistence, Pure CDS + ABAPpublishedBuilds a CDS custom entity backed by an ABAP class that implements IF_RAP_QUERY_PROVIDER and assembles an XLSX workbook at request time — hand-built from Open XML parts with cl_abap_zip for multiple sheets, or in one line via cl_salv_table=>to_xml for one — then streams it to the browser through the @Semantics.largeObject annotation. The same annotation makes Fiori annotations render the field as a download link with no backing database table, trading the usual persisted-blob approach to document output for a file rebuilt fresh on every click.Blog,
open-abap-baladded to the atlasApplication logging for ABAP transpiled to JavaScript on Node.jsPackage,
open-abap-coreadded to the atlasCore ABAP artifacts for code transpiled by @abaplint/transpilerPackage,
open-abap-guiadded to the atlasGUI controls for ABAP transpiled to JavaScriptPackage,
open-abap-lockadded to the atlasConcurrent and cross-session locking for open-abap on PostgreSQLPackage,
open-abap-odataadded to the atlasOData and Gateway shims serving SEGW-style services on Node.jsPackage,
open-abap-pdfadded to the atlasStandalone PDF generator written in ABAPPackage,
open-table-maintenanceadded to the atlasTable maintenance over HTTP for a table fixed in codePackage,
Patterns for using LLMs in ABAP developmentpublishedLars Hvam compares eight ABAP development setups: assistance in SE80 or Eclipse, virtual files and MCP over ADT, a centrally managed MCP service, sandboxes, local Git, Git with read-only system context, and temporary ABAP systems for development and CI. The overview describes where source changes, review and system access happen, including abapGit synchronization and abaplint checks. It is dated March 2026; its risk, cost and autonomy ratings are the writer’s assessments.Doc,
sap-mcp-serveradded to the atlasReads SAP ECC and S/4HANA for an agent over Gateway OData and RFC, with a Node bridge that speaks the RFC protocol without the proprietary SAP NetWeaver RFC SDK.MCP server,
Werkbankadded to the atlasLocal desktop workspace for AI conversations with SAP connectorsDesktop app,
abap-offstack-aunitprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 names four clients beside its install command and adds "and others", so the four named ones are the value and the open end is not read as a fifth. This is the only entry behind the door that states the third system_reach state, in a sentence of its own: nothing requires a provisioned SAP system. The boundary it states elsewhere, that shimmed-out classes stay an on-stack concern, is the entry's own warning and not a qualification of that value.Skill,
abap-skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door. The README read on 2026-10-15 names the five clients the skills command line supports and adds "and other compatible agents", so the five named ones are the value; the README also documents separate routes for Claude Code, OpenCode and GitHub Copilot in VS Code, which name no client the sentence does not. system_reach is left out: the repository states nothing about needing a system or bringing one, and absent is not a no.Skill,
ADT MCP Serverdescription, provides[0] revisedSAP's launch post for the re-invented Joule for Developers points to the ADT MCP Server's available MCP tools in ADT for Eclipse and says the server drives the developer's own coding agent; it does not describe how the server is enabled in Eclipse. The Help page now reads "launches" where the quote said "starts".MCP server,
ARC-1 Skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The skills README read on 2026-10-15 names each client one at a time in its manual-install table, with a directory per client, which is why each value carries its own row; the plugin routes it documents beside that are for Claude Code and Agent Plugins, and the skills command line it offers states "any agent" rather than a list. system_reach rests on the prerequisite the README already states, which the entry's own warning repeats: the server is required for every skill that touches ABAP, and the reader connects it.Skill,
claude-abap-devprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. Both answers were already quoted on this entry: the README calls it a Claude Code plugin and names no other client, and the sentence about detecting servers by tool name is the clearest statement of the third state on this door, since the reader supplies the servers and the skills do not care what they are called. Re-read on 2026-10-15 and unchanged.Skill,
claude-abap-skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 lists Claude Code as the first prerequisite and names no other client the plugins install into, so the one value is the whole answer; the AGENTS.md template it ships is for agents that are not Claude and is not an install route the README states. system_reach rests on the sentence the entry's own warning already turned on: there is no connector here, and the reach comes from servers the reader connects.Skill,
Cloud Connectorprovides[capability:authentication] revisedThe edge read as though the connector propagated the user by itself. SAP's own page names three authentication types towards an internal system and says the calling application's destination configuration picks one, and that trust to the cloud entities whose tokens are accepted has to be configured explicitly. The property the BTP door compares on rests on the same sentence.App,
DanKromp/skillOverflowprovides revisedThe entry's own prose said the collection covers UI5 and Fiori work and the edge cited only the total count. The UI5 pass needed to know what that coverage is, because this entry states no flavor and so answers in all of a door's flavors; the two rows name the skills the fallback rests on, which is what the capability's freestyle and web-components readings now cite.Skill,
rap-skillsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The skills are cloned into a Claude Code skills directory and the README names no other client, so the one value is the whole answer. system_reach rests on the README's own sentence about VSP, which the reader downloads and configures with their own SAP credentials: the bridge is named and not supplied.Skill,
SAP Power for Kiroprovides, description revisedThe entry said it is packaged as a Kiro power and not how it gets there or which Kiro it needs; the README read on 2026-10-15 states both.Skill,
sap-basis-opsprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 says the repository is a Claude Code plugin marketplace and names no other client. system_reach rests on the sentence the entry's own description already paraphrased, and it is the clearest statement of that state on this door: the shell server is the reader's to supply, and the skills carry no credentials of their own.Skill,
sap-mcp-serverentry revisedHanded over in a chat as one address and written from the repository's own README, read raw. Placed on the ABAP door and on agent access to your systems, the concern split out of MCP servers on 2026-10-09: it reaches into a system you run from outside, as the door's two existing providers of that capability do. The README never says ABAP, so the placement rests on the system it reaches and the protocols it names — Gateway OData services, RFC/BAPI, RFC_READ_TABLE and DDIF_FIELDINFO_GET — rather than on a development model it states. Not umbrella: it names ECC and S/4HANA and reaches them through one stack's own protocols, so a door holds it. No tool_count: the README lists its tools in a table and states no count. No flavors: nothing read states standard ABAP or ABAP Cloud. No compat.runtimes: the server is Python with an optional Node bridge, which that enum cannot say.MCP server,
secondsky/sap-skillslinks, flavors, requires, provides, description revisedThe same correction as description.what_it_solves, on the edge that carries this artifact's answer to the capability, so the two do not state the repository's evidence model differently. The rewording also removes the two em dashes the prose scan reported in this field.Skill,
SuperClaude for SAPprovides revisedcapability:agent-guidance widened installs_into to the ABAP door and declared system_reach there. The README read on 2026-10-15 calls it a Claude Code plugin in its own subtitle and names no other client; the installation steps are documented in a separate file that was not read, which does not change the client. system_reach is the state this entry defines: the server it depends on is installed, configured and connection-tested by its own setup command, which is the fact the entry's own warning about being a stack rather than a component already rests on.Skill,
Werkbankecosystem revisedThe project homepage describes "A small, curated shelf of MCP servers and SAP development skills." Its own catalog spans ABAP (ARC-1 and ABAP Cloud), CAP (CAP Upgrade), and UI5 skills; the workspace is not specific to one stack. This intake follows the maintainer’s explicit request after the September source sweep passed it over for lacking a workspace capability; that concern now exists as Agent workspaces. The served views describe which users the project-owned install catalog addresses. Werkbank provides the workspace; each selected connector or skill supplies the stack-specific behavior. No SAP implementation capability is attributed to Werkbank itself.Desktop app,
Wed 14
11 changes
Capturing Background Job Errors in SAP Using the Application Log (SLG0/SLG1)publishedWalks through ABAP's Application Log framework for recording errors from a background job that has no screen to show them on: defining an Object and Sub-object in SLG0, then building the log in code with BAL_LOG_CREATE, adding a free-text or message-class entry with BAL_LOG_MSG_ADD_FREE_TEXT or BAL_LOG_MSG_ADD, and persisting it with BAL_DB_SAVE so it survives after the job finishes. The worked example is a report inserting student records into a custom table, scheduled via SM36 and reviewed afterwards in SLG1, filtered by the Object and Sub-object that created it.Blog,
Mastering Internal Actions in SAP RAP: Automatic Header Calculation in ABAP CloudpublishedWalks through a sales-order BDEF where an item-level determination triggers a header-only internal action by EML in local mode, so a quantity or price change recalculates the order total and applies a 10% discount above $10,000 without a UI button or external OData call reaching the logic directly. Argues for an internal action over inline determination code on reusability and separation of concerns: a determination decides when logic runs, the action decides what runs, and marking it internal keeps Fiori Elements and external OData clients from invoking it.Blog,
Running AI agents against SAP ECC 6.0: lessons from building an in-system MCP serverpublishedNicolasHernandez recounts building and running, over two years, an MCP server written in plain ABAP behind a single ICF node, for SAP ECC 6.0 and S/4HANA on-premise customers that the ADT MCP Server and SAP Joule for Developers, ABAP AI capabilities do not reach. Authorization runs as the calling user rather than a technical RFC user, a choice forced by a customer security team after an earlier version used a technical RFC user, and a later security review found a display-authority check applied uniformly across every write endpoint. The failure modes that cost the most time sat in RFC connectivity itself: RFC_READ_TABLE's empty-table exception collapsed into a false success, a where-used filter was applied only after the row limit, and BAPI calls treated an empty string and an absent parameter as different, silently wrong inputs.Blog,
Scheduling a Background Job for the BDC Session Method Using RSBDCSUBpublishedWalks through uploading data with GUI_UPLOAD, building a BDC session with BDC_OPEN_GROUP, BDC_INSERT and BDC_CLOSE_GROUP, then scheduling the standard program RSBDCSUB as a background job with JOB_OPEN, SUBMIT ... VIA JOB and JOB_CLOSE so the session processes without manual SM35 intervention. Shows the resulting job's status and spool read back through SM37, the way a reader confirms afterwards that a scheduled job actually ran.Blog,
Show 7 more
aibap.mcpdescription revisedThe README's own constraint is now its explicit SAP API Policy relation, quoted.MCP server,
arc-1description revisedThe licensing side is its explicit SAP API Policy relation, sourced to its README; the rest restated what any server in front of ADT is. Removed at the atlas maintainer's request on 2026-10-14.MCP server,
kts982/mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.MCP server,
mcp-sap-guidescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.MCP server,
midasol/sap-mcp-serverdescription revisedThe whole paragraph was the policy, which Agent access to your systems carries as a condition sourced to the policy.MCP server,
sapgui.mcpdescription revisedThe policy is now a condition of GUI automation, sourced to the policy itself.MCP server,
vibing-steampunkdescription revisedThe policy is now a condition of Agent access to your code for ABAP, sourced to the policy itself.MCP server,
Tue 13
3 changes
ABAP + MCP: Let AI Do Real Development in Your SAP Systempublishedabap-adt-mcp is an open-source MCP server that gives an AI agent full ABAP development capability over ADT: it searches, reads, edits, activates and unit-tests objects, and runs ATC checks, on a connected S/4HANA Cloud or on-premise system, acting as the signed-in developer. It runs on abap-adt-api, the same REST client Eclipse's own ADT tooling uses, and sits beside SAP's own ADT MCP Server, shipped with ADT for VS Code and Eclipse under a different server key, and marianfoo's abap-docs, a read-only server over the ABAP Keyword Documentation and Clean ABAP. Each destination carries a policy — read-only, allowed packages, denied tables and tools — the server checks before every call, and an optional audit file logs each tool call with its outcome and policy gate.Blog,
How to rename an OData V4 service?publishedRenaming an OData V4 service binding changes its Service Alias and the resulting service URL, breaking any app already deployed against the old one — shown on a /DMO/TRAVEL-based example in the SAP BTP ABAP environment by unpublishing, renaming and republishing the binding, then reading the new URL back from the OData V4 service catalog's ServiceGroups entry. It weighs that against two alternatives: adding a second service definition and publishing it as a new service version under the same binding, or creating an entirely new service definition and binding, which keeps the original URL live during the cutover.Blog,
How to use SAP Data Intelligence with SAP Cloud ConnectorpublishedWalks through reaching an on-premise network from SAP Data Intelligence Cloud with Cloud Connector: installing the client, assigning the Cloud_Connector_Administrator role, registering the subaccount, and mapping on-premise systems as ABAP, HANA or HTTP back-ends in Data Intelligence's Connection Manager. For an ABAP back-end it names the function-module whitelist and the gateway port format RFC access needs, per SAP Note 2835207.Blog,
Mon 12
8 changes
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 annotations 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 Studio from the published OData 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.Blog,
abap-transport-reviewadded to the atlasTransport release check gated by GitHub pull request approvalApp,
pam-mcp-serveradded to the atlasLocal MCP server on support status from an SAP PAM exportMCP server,
SAP Support Radaradded to the atlasBrowser app checking SAP product support status from a PAM exportWeb tool,
Show 4 more
@mcp-abap-adt/corereleased 18.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
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".App,
pam-mcp-serverentry revisedStaged as its own entry beside the app (ADR-0063, two entries) because an agent reaches for the server and a person opens the app. part_of rests on the README's project layout. ecosystem: umbrella and serves_ecosystems: abap for the same reasons as the app: it reads the same matrix, and its documentation's worked example queries SAP S/4HANA 2022 and SAP NetWeaver 7.5. No tool_count: the README lists three tools and states no count. Its package is private and not on npm.MCP server,
SAP Support Radarentry revisedStaged with the capability Knowing the maintenance status of a release and the external SAP Product Availability Matrix. ecosystem: umbrella (ADR-0063) because its documentation is about SAP products as such and names no single stack it serves: "Check the support/maintenance status of the SAP products and versions you actually use against the official SAP Product Availability Matrix (PAM)". OpenUI5 is what it is built with, not whom it serves. serves_ecosystems: abap because the releases its documentation checks are SAP S/4HANA and SAP NetWeaver, as in the worked example in docs/mcp-server.md ("SAP S/4HANA 2022 On-Premise", "SAP NetWeaver 7.5"). use_as: reference because it is consulted at its own address. The README names no contributors besides the maintainer. Named SAP Support Radar, the title the maker gives it in the README, by the maintainer's decision on 2026-10-12; serves_ecosystems: abap confirmed by the maintainer the same day.Web tool,
Sun 11
36 changes
Agent-led custom code migration: From planning to mass adaptationpublishedThe Custom Code Migration Agent in SAP Joule for Developers, ABAP AI capabilities, applied to moving custom code from SAP ERP Central Component to SAP Cloud ERP Private: the abstract describes a toolchain that starts with planning in SAP Cloud ALM and ends in mass remediation by the agent, with newer custom code management features shown alongside. Which findings the agent remediates, and how far it goes without a developer, the abstract does not say. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Marco Matha and Olga Dolinskaja, written here from SAP's abstract; the recording is not yet published.Talk,
Agentic CAP: Build MCP servers and enterprise AI agentspublishedCAP applications become AI agents over the Model Context Protocol and the Agent2Agent protocol, which is the serve your application over MCP concern, and SAP AI Core is the LLM integration through which AI is embedded in a CAP app, with recommendations from the SAP-RPT-1 model as the abstract's example. The abstract names the two protocols and the one model and does not say which packages carry them. A two-hour TechEd 2026 session in a hands-on room (Tuesday 27 October, Berlin), presented by Daniel Hutzel, Daniel Schlachter, Marc Huber and Sami Lechner, written here from SAP's abstract; the recording is not yet published.Talk,
Agentic memory: Knowledge graph engine and recall in SAP HANA CloudpublishedThe knowledge graph engine in SAP HANA Cloud as an agent's memory: what the engine, the graph side of graph, spatial and document data, does in an agentic workflow, how an agent keeps what it learns there, the state agent tooling holds between turns, and the SAP AI Core integration through which the database calls LLMs and tabular foundation models such as SAP-RPT-1. The abstract names the engine, the memory role and the AI Core link and does not say how the memory is written or read. DA263 on Wednesday 28 October is a two-hour hands-on on the same engine with a different cast. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Markus Fath and Shraddha Shetty, written here from SAP's abstract; the recording is not yet published.Talk,
AI-enabled administration: Automating log analysis with generative AI hubpublishedA log analysis tool for incident work, built in SAP Business Application Studio with the generative AI hub feature, which SAP AI Core ships as its LLM integration by its own documentation: it automates root-cause analysis over system errors and masks sensitive data. SAP's abstract states the tool's jobs and not how the hub is called, what the masking covers or which model answers. A TechEd 2026 session (Wednesday 28 October, Berlin), with no speaker listed in the catalogue at the time of writing, written here from SAP's abstract; the recording is not yet published.Talk,
Show 32 more
AI-first, API-first: What changes when AI becomes the userpublishedWhat changes in an architecture when an AI agent is the caller: AI-first and API-first principles, SAP's API governance, extensibility and the composable enterprise, with lessons the speaker draws from SAP's and other enterprise AI initiatives. The extensibility edge rests on the abstract naming extensibility as a principle and nothing more specific; no API, product or tool is named, so the talk is attached to the broadest concern it touches. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Tomasz Wilk, written here from SAP's abstract; the recording is not yet published.Talk,
Analyze and optimize ABAP Cloud model apps built on core data servicespublishedPerformance anti-patterns in data models built with ABAP CDS under ABAP Cloud applications, and the tools that find them: the abstract names ABAP cross trace, the SQL analyzer (PlanViz) in Visual Studio Code and the SAP HANA database explorer as what the session uses to follow a bottleneck from the application to the database. The anti-patterns are taken from real business applications, which is where the data modelling edge holds; which ones are shown is not in the abstract. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Ingo Braeuninger, Robert Werlich, Steffen Siegmund and Thomas Fiedler, written here from SAP's abstract; the recording is not yet published.Talk,
Behind the Autonomous Enterprise: SAP Knowledge Graph and SAP Domain ModelspublishedThe strategy behind SAP Business AI's intelligence layer: SAP Knowledge Graph for enterprise context, SAP Domain Models for SAP-specific expertise and tabular AI for predictions, unified on SAP AI Core with SAP Document AI. Knowledge Graph and Domain Models are not atlas entries, so the edges rest on the two products the abstract names as the infrastructure and on Predictive models for the tabular AI; nothing is stated about what any of them does in the layer. A TechEd 2026 session (Tuesday 27 October, Berlin; also ST103V, virtual), presented by Jan Portisch and Richard Grandpierre, written here from SAP's abstract; the recording is not yet published.Talk,
Build agentic SAP extensions with Google CloudpublishedGoogle Cloud's architectures for agentic AI apps on SAP with a clean core: SAP Business AI Platform, SAP S/4HANA and SAP Business Data Cloud joined with BigQuery, Gemini and Google's Agent Development Kit. The abstract names zero-copy data agents, developer API workflows and ABAP extensions for AI integration, the last of which is the Extensibility concern; Business Data Cloud is the one atlas entry it names, and how any piece connects to another is not stated. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Ekaterina Kruse, Ian Moria and Stany Winkler, written here from SAP's abstract; the recording is not yet published.Talk,
Build AI agents and applications natively on SAP HANA CloudpublishedSAP HANA Cloud as the base for agentic applications on SAP Business AI Platform: the session goes through CAP, the SAP HANA Cloud vector engine and SAP AI Core, with architecture patterns and lessons learned from building AI-supported applications. SAP's abstract names the three parts of that stack and the vector engine as the database's feature in it, and describes none of the patterns. A TechEd 2026 session (Wednesday 28 October, Berlin; also DA113V, virtual), presented by Christoph Morgen and Shraddha Shetty, written here from SAP's abstract; the recording is not yet published.Talk,
Build business differentiation with SAP AI CorepublishedSAP AI Core as the orchestration layer for enterprise AI, worked through with SAP's engineers: extend Joule Agents with models from its library, ground them in SAP Business Data Cloud products, embed them in SAP S/4HANA flows, then govern, scale and monitor them from prototype to production. The abstract says what the layer does for an agent and not which services carry each step. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by David Knaack, Franziska Dobrigkeit, Hadi Hares and Jonas Israel, written here from SAP's abstract; the recording is not yet published.Talk,
Building agentic applications with SAP HANA CloudpublishedA CAP application extended with semantic search and agent features on top of SAP HANA Cloud's vector engine and SAP AI Core, built in a hands-on workshop. The abstract names the parts, CAP, the vector engine and AI Core, and the two additions: semantic search, the retrieval half of retrieval-augmented generation, and LLM-supported agent capabilities inside the application, which is agent tooling. Which embedding model, which CAP runtime and how the agent calls its tools are not stated. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Hui Li, Ritty Joseph, Shraddha Shetty and Tanuja Jadhav, written here from SAP's abstract; the recording is not yet published.Talk,
Deploy, review, break, fix: Govern cloud transports with agility and AIpublishedFive BTP services in one delivery chain, as the abstract lays it out: a transport is triggered in SAP Content Agent Service, tested in SAP Cloud Transport Management, its failure is raised by SAP Alert Notification service for SAP BTP and remediated by a SAP Joule agent with SAP Automation Pilot, and SAP Cloud Logging keeps the history for root-cause analysis. The chain from alert to remediation is the operations automation concern; what the Joule agent decides on its own is not in the abstract. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Biser Simeonov, Daniel Funkert, Sven Rullmann and Thorsten Sandfuchs, written here from SAP's abstract; the recording is not yet published.Talk,
Enriching AI models with SAP AI Core in SAP Business Data CloudpublishedThe integration between SAP Business Data Cloud and SAP AI Core, through which data products with their semantics feed AI models for benchmarking, custom AI development and agentic analytics and applications. The abstract names the two products and the three uses and states nothing about how the data reaches AI Core or what the integration consists of. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by San Tran and Sandy Tran, written here from SAP's abstract; the recording is not yet published.Talk,
Explore SAP Fiori elements for ABAP developerspublishedSAP Fiori elements for an ABAP developer who now builds the UI as well as the RAP business object behind it, the transactional model of ABAP Cloud, in SAP Business Application Studio; the abstract calls the UI side new territory for that developer, and a Fiori elements app is rendered from the service's Fiori annotations rather than hand-written UI code. The abstract names the tool and the stack and does not say which floorplan or annotations are shown. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Björn Schulz, written here from SAP's abstract; the recording is not yet published.Talk,
Extending SAP Autonomous SuitepublishedExtensibility across SAP Autonomous Suite: AI-enabled development in SAP Build solutions, the ABAP Cloud model among them, as the way extensions are designed, generated and deployed, and a direction for making extensions ready for agentic AI. The abstract names the suite, SAP Build and the ABAP Cloud model and no single feature, so the edges are to Extensibility, the concern, and to SAP Build Code, the SAP Build solution held here in which Joule generates and deploys development; which other SAP Build solutions the session shows is not stated. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Alexander Rother and Khaled MUSILHY, written here from SAP's abstract; the recording is not yet published.Talk,
From intent to extension: Joule and the future of solution extensibilitypublishedHow Joule turns natural-language intent into extensions across SAP Autonomous Suite: intent-based agent extensions, enriching the agents SAP delivers, packaging options for partners and what SAP calls a harmonised extensibility experience. The edges are to SAP Joule, which does the translating, and to Extensibility, the concern; the abstract names the directions and no feature that ships today. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Amitha Kamath, Oren Shatil and Richard Kuba, written here from SAP's abstract; the recording is not yet published.Talk,
Joule and SAP Knowledge Graph: Context-aware AI across SAP solutionspublishedThe catalogue carries RA107's abstract under this title, and what it describes is SAP AI Core as the management and orchestration layer of an AI architecture: extending Joule Agents in SAP Joule, the model library in Joule Studio for contextual reasoning, connecting data products from SAP Business Data Cloud, and embedding AI in SAP S/4HANA. The SAP Knowledge Graph the title names does not appear in that text, so the edges rest on the abstract as published, and whether the session follows the title or the abstract is not known until it is recorded. A TechEd 2026 session (Wednesday 28 October, Berlin; also RA110V, virtual), presented by Jan Portisch and Pavithra G K, written here from SAP's abstract; the recording is not yet published.Talk,
Knowledge graph and agent memory: Build an agent that rememberspublishedThe knowledge graph engine in SAP HANA Cloud as an agent's memory: what the engine, the graph side of graph, spatial and document data, does in an agentic workflow, how an agent keeps what it learns there, the state agent tooling holds between turns, and the SAP AI Core integration through which the database calls LLMs and tabular foundation models such as SAP-RPT-1. The abstract names the engine, the memory role and the AI Core link and does not say how the memory is written or read. DA205 on Tuesday 27 October is the 45-minute talk on the same engine, with a near-identical abstract and a different cast. A two-hour hands-on TechEd 2026 session (Wednesday 28 October, Berlin), presented by Christoph Morgen, Jan Zwickel, Markus Fath and Thomas Hammer, written here from SAP's abstract; the recording is not yet published.Talk,
Level up app development: ABAP Cloud model innovations and Joule solutionpublishedThe ABAP RESTful application programming model, in SAP's abstract, generates multi-node business objects and adds event-driven side effects, collaborative draft, background processing and analytical tables, with the SAP Joule for Developers, ABAP AI capabilities add-on used to speed development up. The generated business objects are the transactional model concern; the abstract names each feature and says nothing about how it is used. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Anne Keller, Carine Tchoutouo Djomo, Frank Jentsch and Marina Blank, written here from SAP's abstract; the recording is not yet published.Talk,
Migrate and modernize your custom code using RISE with SAP and agentic AIpublishedThe Custom Code Migration Agent in SAP Joule for Developers, ABAP AI capabilities, shown on the RISE with SAP path that moves custom extensions from SAP ERP Central Component to SAP Cloud ERP Private: the abstract says the agent adapts the code through MCP tools and the AI for ABAP features in the custom code tools, and that the adapted code is then reworked along the clean core approach, the concern ABAP Cloud readiness covers. Which MCP tools, and what the clean core step changes in the code, the abstract leaves open. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Hitesh Bindal, Ingo Braeuninger, Jonas Helin of GitHub, Olga Dolinskaja and Thomas Fiedler, written here from SAP's abstract; the recording is not yet published.Talk,
Navigating the road map for SAP Cloud ERP: Today, next, and beyondpublishedSAP's near-term and long-term plans for SAP Cloud ERP by theme: embedded AI, process automation, lifecycle management and extensibility, with timelines and adoption paths toward what SAP calls the Autonomous Enterprise. SAP Cloud ERP has no artifact here, so the edges are to the two concerns the road map names, Extensibility and Process automation; the abstract names no product or feature under either, and whether its process automation is SAP Build Process Automation is not stated. A TechEd 2026 session (Tuesday 27 October, Berlin; also TM815V, virtual), presented by Lawrence Martin and Sasa Markovic, written here from SAP's abstract; the recording is not yet published.Talk,
OData to outcomes—Build AI-enabled SAP Fiori apps using SAP Fiori elementspublishedA Fiori elements app built through SAP's MCP servers: the OData V4 service comes from the MCP server for RAP, which the atlas holds as the ADT MCP Server, or from @cap-js/mcp-server for CAP, and the UI from @sap-ux/fiori-mcp-server, with annotations and actions added before the app is tied to SAP's AI features. Agent access to your code on both the service and the UI side; SAP's abstract names the servers and the steps and says nothing about which AI features or which agent host. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Benedikt Schoelch, Sebastian Steinhauer, Sebastian Werner and Stefan Engelhardt, written here from SAP's abstract; the recording is not yet published.Talk,
Rethinking security for modern SAP solution landscapespublishedWhere risk goes when clean core moves custom logic out of SAP S/4HANA: into integration flows, CAP extensions, ABAP Cloud code and platform configuration, told through real attack stories, then scanning code, modelling attack paths, adding security gates to CI/CD pipelines and automating safely with Terraform. The scanning edge is to static analysis, the atlas's concern for security findings in ABAP code; the abstract lists the four surfaces and the four practices and describes none of them. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Tsovinar Chugaszyan, written here from SAP's abstract; the recording is not yet published.Talk,
SAP AI Core deep dive: Models, agents, and business context at scalepublishedSAP AI Core read as the management and orchestration layer of an AI architecture, beyond the model runtime: SAP's abstract lists extending Joule Agents, the model library in Joule Studio for contextual reasoning, connecting data products from SAP Business Data Cloud, and embedding AI in SAP S/4HANA. It names the connections and not the APIs behind them. A TechEd 2026 session (Tuesday 27 October, Berlin; also RA107V, virtual), presented by Franziska Dobrigkeit and Hadi Hares, written here from SAP's abstract; the recording is not yet published.Talk,
SAP BAIP, ABAP environment: Monitoring and troubleshootingpublishedMonitoring and troubleshooting a side-by-side application written in the ABAP Cloud model on SAP BTP ABAP environment, which SAP's title calls SAP BAIP, ABAP environment, and which the abstract files under a clean core strategy at level A: the environment's technical monitoring tools for the monitoring half, and ABAP Development Tools for Eclipse for the troubleshooting half, the debugging concern. The abstract names the environment and the Eclipse tools, leaves the monitoring tools unnamed, and does not say what is shown of either. A TechEd 2026 hands-on session (Thursday 29 October, Berlin), presented by Frank Jentsch, Robert Werlich, Steffen Siegmund and Wolfgang Woehrle, written here from SAP's abstract; the recording is not yet published.Talk,
SAP Event Mesh: S4 HANA On-Prem and SAP CI(BTP IS) through WebSocket and WebhookspublishedA step-by-step walkthrough of wiring Event Mesh to publish and consume events between an on-premise S/4HANA system and Cloud Integration, contrasting persistent queues (one subscriber, kept until consumed) against unpersisted topics, and WebSocket's AMQP transport against webhook delivery for the same queue. Two tested findings support it: a queue consumer running in continuous consumption mode receives a message ahead of a webhook on the same topic, and a message stays queued and is retried (almost 8770 times in under a minute, in the author's test) until the consumer processes it successfully.Blog,
SAP Joule for Consultants: Unified knowledge for requirements and designspublishedFit-to-standard analysis as a consultant on a cloud transformation project: connecting an organisation's data to SAP Joule for Consultants through SAP AI Core, getting answers from SAP knowledge and that content, then building an expert, loading project files and running guided prompts. The edges are to SAP Joule, of which Joule for Consultants is a part, and to SAP AI Core, named as the connection path; how the data is grounded is left to the session. A TechEd 2026 hands-on session (Wednesday 28 October, Berlin), presented by Anantharaman Ravi, Natalie Han, Sachin Kaura and Yi Hsuan Lin, written here from SAP's abstract; the recording is not yet published.Talk,
SAP-RPT and TabPFN: Get started with tabular foundation modelspublishedTabular foundation models, SAP-RPT and TabPFN, in a hands-on with SAP and Prior Labs: the model families first, then predictions run through SAP AI Core with a workflow built on tabular orchestration and connected to the participant's own data for real-time predictions. A predictive models session with the models as the subject; the abstract does not name the SDK or API the workflow is built with. A TechEd 2026 hands-on session (Thursday 29 October, Berlin), presented by Eliott Kalfon, Janick Zaehringer-Frasch, Johannes Hoehne, Katharina Schell, Nilay Mehta and Sherene Tan, written here from SAP's abstract; no recording is announced.Talk,
Ship your own sandboxed AI operations agent to Kyma in two hourspublishedAn operations agent built and then broken on purpose: the abstract has participants deploy a reasoning agent to SAP BTP, Kyma runtime, connect it to SAP AI Core, give it observability over the runtime and cause a failure for it to diagnose, the operations automation concern with an agent doing the diagnosis. Patterns for cost control and monitoring are promised at the end; the agent framework and how the sandbox is drawn are not named. A TechEd 2026 session (Tuesday 27 October, Berlin, two hours), presented by Christian Lechner, Piotr Tesny, Thorsten Sandfuchs and Vipin VijayKumar, written here from SAP's abstract; the recording is not yet published.Talk,
Spec first: The disciplined way to develop ABAP with agentspublishedSpec-driven ABAP development with a new AWS Toolkit for Eclipse plug-in powered by Kiro, in SAP's words, working inside ABAP Development Tools for Eclipse: SAP's abstract says it reads the codebase, helps with new features, explains legacy code, refactors and generates tests, for S/4HANA modernisation or a new business feature. It answers agent access to your code from inside Eclipse; the plug-in itself is not yet in the atlas, and the abstract does not say how it reaches the ABAP system. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Jon Friesen and Stephan Kremer, written here from SAP's abstract; the recording is not yet published.Talk,
Strategy for agent-led development in ABAPpublishedSAP Joule for Developers, ABAP AI capabilities moving ABAP development in ADT from AI-assisted to agent-led, across greenfield work and the migration and modernisation of existing solutions: SAP's strategy session for its ABAP AI add-on. The abstract states the direction and names no feature or release date. A TechEd 2026 session (Tuesday 27 October, Berlin; also ST124V, virtual), presented by Alexander Rother and Sonja Lienard, written here from SAP's abstract; the recording is not yet published.Talk,
The journey with clean core continues for SAP Cloud ERP PrivatepublishedClean core in SAP S/4HANA Cloud Private Edition as it stands in 2026: what is new in extensibility, new capabilities in the dashboard for the RISE with SAP Methodology, how AI helps make custom code compliant with clean core, and new guidance on data, integration and clean core in relation to SAP's API policy. The edges are to Extensibility, the concern the session is about, and to ABAP Cloud readiness, the concern behind making custom code compliant; the abstract names no tool for either and the dashboard is not held here. A TechEd 2026 session (Wednesday 28 October, Berlin; also TM108V, virtual), presented by Markus Goebel and Olga Dolinskaja, written here from SAP's abstract; the recording is not yet published.Talk,
Transform your configuration of SAP S/4HANA Cloud with agentic AIpublishedThe Configuration Assistant for SAP Cloud ERP, hands-on: an agent that validates insights from an organisation's data and maps toward a target business configuration, under the heading of agentic data management, with data preparation, transparency and governance as the stated aims. The atlas holds no entry for the Configuration Assistant and no concern for business configuration of an ERP, so the edge is to Agent access to your systems, the nearest concern, an agent working on a system's data and configuration; the abstract's configuration is not the per-environment application settings the atlas files under that word. The abstract is the same text as TM100 and states aims and no exercise detail. A TechEd 2026 hands-on session (Thursday 29 October, Berlin), presented by Felix Peter, Joerg Rupprecht, Joerg Singler and Simone Mundt, written here from SAP's abstract; the recording is not yet published.Talk,
Use change and deployment management in an ABAP environment with confidencepublishedSAP Cloud Transport Management with SAP Cloud ALM as the governed way to move changes from a cloud-optimised ABAP environment into production: the abstract says the session sets out the process, where it differs from classic transport mechanisms, the current state of every content type it carries, and an outlook on deploying agents through it, which is the transport management concern on the cloud side. What each content type covers, and when agent deployment arrives, is not stated. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Moritz Gysler and Sven Rullmann, written here from SAP's abstract; the recording is not yet published.Talk,
WebSocket RFC to Cloud Using SAP Business ConnectorpublishedWalks through wiring RFC connectivity between an on-premise ABAP system and a cloud ABAP system (SAP S/4HANA Cloud or Steampunk) through SAP Business Connector, which tunnels classic RFC over a WebSocket/HTTPS connection past firewalls. Covers the RFC destination of type T on the source system, the Communication User, Communication Scenario and Communication Arrangement needed on the cloud side to allow-list the function modules being called, and the three configuration steps on the Business Connector itself, closing with a list of common connection errors and their fixes.Blog,
What's next in extensibility for SAP Autonomous SuitepublishedAgent-driven extensibility across SAP Autonomous Suite as SAP sees it ahead: what is coming for making extensions ready for agentic AI and how SAP's assistants are meant to help with it. The edge is to Extensibility, the concern; the abstract names no assistant, no feature and no date. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Alexander Rother and Oren Shatil, written here from SAP's abstract; the recording is not yet published.Talk,
Sat 10
5 changes
A Natural Choice: SAP AIF can now expose events to Advanced Event Mesh to power your EDApublishedAnnounces AIFAEM, a new software component of SAP Application Interface Framework that lets SAP ECC and older SAP S/4HANA backends create custom events from BOR objects and IDocs, in CloudEvents format, and publish them to SAP Integration Suite, advanced event mesh — closing the gap for backends that predate S/4HANA's own RAP-based standard events. It ships as the ABAP add-on AIFAEM731 (SAP NetWeaver 7.31, i.e. ECC) or AIFAEM800 (NetWeaver 7.55 and later), and its usage is included in an advanced event mesh subscription.Blog,
Clean Core Measurementadded to the atlasReports Clean Core ATC results per system as Level A to D KPIsApp,
Communicate from a Java Application to ABAP via WebSocket RFC using JCo - Migration GuidepublishedWalks a JCo setup from classic CPIC-based RFC to WebSocket RFC: swap the application- or message-server logon properties for jco.client.wshost and jco.client.wsport, and implement DestinationDataProvider's getSSLContext (and, for mTLS, getClientCertificate) since the new connection runs over TLS. It covers building the PKI trust on both sides — a local PKCS12 keystore for the Java side, STRUST's SSL-Server Standard certificate exported and imported for mutual trust on the ABAP side — and notes that on BTP, JCo paired with the Destination service already implements this via the Connectivity service, so the custom SSLContext work can be skipped there.Blog,
How to mass upload from a spreadsheet file into an SAP Fiori app in SAP BTP ABAP Environment Part 1publishedPart 1 of a three-part series on mass-uploading records from a spreadsheet into a RAP business object in the SAP BTP ABAP environment, using the XCO XLSX module to parse an uploaded Excel file without any open-source library. It reads a named worksheet by its column-and-row coordinates into an internal table through the row-stream operation, then creates or updates records with the EML MODIFY ENTITIES statement, and reserves the Fiori elements custom-action wiring and the download/template generation for Parts 2 and 3.Blog,
Show 1 more
Recommendations for Customers on using the Direct Push-Based IntegrationpublishedExplains SAP's direct push-based integration, where two ABAP systems (SAP BTP ABAP environment, SAP S/4HANA Cloud or SAP S/4HANA on-premise) exchange business events by calling each other over RFC connectivity, carried over CPI-C or WebSocket depending on the release, through a sender channel on one side and a matching receiver channel on the other that lists which events it wants. It recommends the mechanism only between systems in the same location or subaccount, without public exposure, and for prototyping event-driven scenarios before moving to Event Mesh or SAP Integration Suite, Advanced Event Mesh at a larger scale.Blog,
Fri 9
12 changes
SAP: Email Functionality in SAP with a Custom Function ModulepublishedA custom ABAP function module, ZFM_SEND_EMAIL, sends mail through Business Communication Services' CL_BCS and CL_DOCUMENT_BCS classes, adding TO/CC/BCC recipients and multiple attachments by building the HTML document in application code on top of what CL_BCS delivers, which is how ABAP's notifications capability describes mail going out. The send sits in a TRY structure whose three CATCH blocks for CL_BCS's class-based exceptions are empty, so what reaches the caller is a BAPIRET2 table that BAPI_MESSAGE_GETDETAIL fills on the paths without an exception: no recipients given, sent to all, or not sent. That conversion into a caller-facing message table is what ABAP's error handling capability leaves to the application.Blog,
Unleashing ABAP Potential: An introduction to Extension Libraries (XCO)publishedIntroduces ABAP's Extension Libraries (XCO), a library framework that puts reusable functionality behind one interface. The post places it as part of the ABAP RESTful Application Programming Model but versatile enough for other ABAP contexts, and says it works in both on-premise ABAP and the ABAP environment on SAP Business Technology Platform. It walks through a worked Logging example: xco_log=>factory->create_new_log opens a log keyed by object, subobject and external ID, logger->add_message appends a typed message, and logger->add_last_symsg attaches a problem class and level of detail for later traceability.Blog,
abap-offstack-aunitentry revisedIn the SAP AI Skills Library registry snapshot since the baseline of 2026-09-18 and never drafted; the registry record for skills/abap-offstack-aunit changed before the 2026-10-09 check, so it enters as a new entry rather than a revision. Written from the repository's own README; hard rule 7: skills are indexed, never authored here. The registry's skillspector scan is its own dated claim and is not carried as a field.Skill,
abap-skillsentry revisedA repository the SAP AI Skills Library collection cache carries as processedBy baseline-2026-09-18 and that was never drafted into the atlas, so the changed registry record of 2026-10-09 is the first occasion to enter it; first_seen keeps the baseline date and no revises flag applies, since there is no published entry to revise. Written from the repository's README, its SKILLS_INDEX.md, the skills directory listing and the abap-cloud SKILL.md; hard rule 7: skills are indexed, never authored here.Skill,
Show 8 more
AI-native North Star architecture — Platform Layerparts revisedFilled from SAP's own pages at the maintainer's request (docs/concepts/product-doors.md was the occasion; the AI-native door reads these designs). Every part names what the graph holds; what it lacks is listed as candidates in the curation note.Reference architecture,
btp-sap-odata-to-mcp-serverprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
midasol/sap-mcp-serverprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
odata_mcpprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
odata_mcp_goprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
pyrfc-mcpprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
sap-security-mcpprovides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
sapskillsentry revisedIn the SAP AI Skills Library registry snapshot since the baseline of 2026-09-18 and never drafted; the registry record for skills/clean-abap changed before the 2026-10-09 check, so it enters as a new entry rather than a revision. Represented once at repository level, as skillOverflow is: the registry registers one skill, clean-abap, while the repository documents and installs three, so the repository's count is used for the entry and both remain in the crawl record. Written from the repository's own README; hard rule 7: skills are indexed, never authored here.Skill,
Tue 6
4 changes
Basic code's of ABAPpublishedNine standalone ABAP reports built around REUSE_ALV_GRID_DISPLAY and CL_SALV_TABLE, covering display, screen validation, spool creation, Excel upload and table maintenance without SM30. One report raises and catches a custom exception class with RAISE EXCEPTION and TRY/CATCH, the class-based mechanism error handling names for ABAP; another submits a job to spool, converts it to PDF with CONVERT_ABAPSPOOLJOB_2_PDF and exports a CL_SALV_TABLE result to Excel before mailing both, producing document output from spool rather than Form Builder.Blog,
claude-abap-devadded to the atlasFive ABAP workflows for Claude Code on existing MCP serversSkill,
claude-abap-deventry revisedHanded over as a URL in a chat session and written from the repository's own README. Hard rule 7: skills are indexed, never authored here, and the guardrails are reported as the maintainer states them rather than as anything the atlas has run. when_not_to_use and to_build_on_it are left for an editor.Skill,
sap-ai-dev-toolkitdescription, provides, requires, connects, type properties revisedRe-read against the README, tools.md and inventory.md at 0.9.3, published the same day; the entry was written on 2026-10-01 against 0.7.9, and npm records 41 releases in the eleven days since 0.2.5. Three cited sentences no longer exist in the source: the feature row now reads "Discover BAS destinations or local SAP GUI systems", the architecture flow now names "VSP + configured route (BAS, CF, or local SAP GUI)", and the row quoted for authentication ("No credentials in mcp.json") has become "Credential-aware setup", which states the BAS and local halves separately. So Business Application Studio is now a conditional requirement rather than an unconditional one, and the single destination authentication mode is joined by the local ones the README documents. The fourteen facets, the curated ADT surface and every other guardrail quote were re-verified unchanged.MCP server,
Mon 5
5 changes
ABAP-PRCadded to the atlasFramework for multi-step ABAP processes with monitoringPackage,
Connecting SAP S/4HANA On-Prem Directly to Advanced Event Mesh using Cloud Connector - finally!publishedPackage Integration 1.4.0 for the Advanced Event Mesh Adapter adds official support for routing through SAP Cloud Connector, so an on-premise SAP S/4HANA system can produce events that SAP Advanced Event Mesh distributes without exposing a public endpoint. The same release changes the adapter's default acknowledgment mode from Automatic Immediate to Automatic On Exchange Complete, altering delivery semantics and error handling. The release notes warn against mixing proxy configurations within one tenant, since that causes unpredictable routing in complex hybrid tenants.Blog,
@mcp-abap-adt/corereleased 17.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
fr0ster/mcp-abap-adtreleased 17.0.0Setups against a system with a self-signed or company-CA certificate that worked without any TLS setting.MCP server,
Show 1 more
ABAP-PRCentry revisedEntered by intake from the repository README, the repository description and the maintainer's landing page.Package,
Sun 4
17 changes
arc-1-bopf-enhadded to the atlasarc-1 extension for reading and maintaining BOPF enhancementsMCP server,
arc-1-extension-sampleadded to the atlasSample arc-1 extension in TypeScript with ten custom toolsSample,
BEHAVIOR_ILLEGAL_STATEMENT dump | Technical workaroundspublishedThe BEHAVIOR_ILLEGAL_STATEMENT dump fires in SAP RAP when an explicit COMMIT WORK or ROLLBACK WORK, or a direct database write, collides with RAP's own transactional model: a Logical Unit of Work split into an interaction phase, where changes sit in a transactional buffer, and a save sequence that validates and persists them. The post then names four ways to move the offending statement into a separate task instead — the Background Processing Framework, parallel processing, Application Jobs, or, on-premise only, a wrapper RFC function module called with DESTINATION 'NONE' — pointing to further reading for each rather than working through any of them here.Blog,
BO Interface APIs : An alternative to BAPIs and traditional FMspublishedWalks through updating an S/4HANA Purchase Order's line items through a released BO interface instead of a BAPI, using EML against the underlying CDS entity and a COMMIT ENTITIES statement because the call sits outside a behavior class. Argues the BO interface route avoids a RAP behavior class's restriction against calling COMMIT WORK directly, and covers finding a released interface's CRUD operations on api.sap.com and extending the same approach to a custom field or a custom RAP-based Fiori app's own BO.Blog,
Show 13 more
Clean Core IndexpublishedDescribes a company-built KPI, the Clean Core Index, that scores existing custom ABAP code by object type — reports, function modules, SAPScript/Smartforms, ATC S/4 readiness-check findings, user exits and modifications — each weighted by a severity the author sets for redesign effort and upgrade risk, with counts read off CDS views built for the purpose. The index is the author's own definition rather than an official one and does not by itself certify public-cloud readiness, but tracking it weekly shows where custom code still blocks a move to ABAP Cloud and lets progress be read per module or per object type.Blog,
eclipsADT-o-matadded to the atlasPowerShell wizard installing Eclipse with ADT and pluginsCLI,
LISAadded to the atlasMCP server for reading and writing ABAP object translationsMCP server,
Merge multiple PDF forms into a single document for download or printing.publishedFaced with bundling several Adobe-Forms-generated PDFs into one file, where FP_JOB_OPEN could not handle the parameters a bundled FP_GET_PDF_TABLE output needed and the forms themselves could not be changed, the author merges the individual PDFs at runtime with the CL_RSPO_PDF_MERGE class instead. Walks through opening the spool job with FP_JOB_OPEN, generating each form via its FP_FUNCTION_MODULE_NAME-resolved function module, adding each result's xstring to the merger with add_document, then calling merge_documents and converting the result for GUI_DOWNLOAD or printing.Blog,
Set up the SAP Cloud Connector: Integrating On‑Premise Systems with Cloud ServicespublishedA step-by-step walkthrough of installing Cloud Connector, adding a subaccount, managing identity and trust certificates in STRUST, and mapping cloud-to-on-premise paths for an SAP HANA backend. It ends by creating a Destinations entry in SAP BTP with proxy type OnPremise and basic authentication, then testing it from SAP Business Application Studio.Blog,
Step-by-Step Guide to Display System Details on SAP Fiori Launchpad ShellpublishedA step-by-step build of a plugin for the SAP Fiori launchpad shell that shows the system ID and client on every app it hosts: an OData service modelled in SAP Gateway Service Builder (SEGW), its GetEntitySet method redefined to call the function module RSAPI_CTC_GET_SYSTEM_DETAILS, then consumed from a project in SAP Business Application Studio 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.Blog,
ZARC1_EXTENSION_FORMSadded to the atlasarc-1 extension for SAPscript and Smart Forms objectsMCP server,
arc-1description revisedRe-read against the README, the npm registry record, the extensions page and the release notes on 2026-10-04, with arc-1 at 1.5.0 published 2026-10-02. Every claim the entry already carried still holds word for word, so the checked dates move and the text does not, except where the documentation says something the entry did not. Two such things: Custom_* tools an operator registers without forking, which the corpus already recorded on claude-sap-kit and not on the server those tools run in, and one agent plugin that installs the server together with ARC-1 Skills. The seven guardrails added were stated when the entry was written and left out of it; they are quoted, not counted. The run_code facet stays absent: the extensions page gates class and report execution behind two flags and a plugin the operator writes, which is not the server stating that it runs code.MCP server,
arc-1-bopf-enhentry revisedEntered by intake from the repository README after the admin had routed the URL to a refresh of arc-1, which reported it as a candidate of its own. Written from the README and the repository description.MCP server,
arc-1-extension-sampleentry revisedEntered by intake from the README, found through ARC-1's extensions page, which links it as the worked sample.Sample,
eclipsADT-o-matentry revisedEntered by intake from the repository README and description.CLI,
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.MCP server,
ZARC1_EXTENSION_FORMSentry revisedEntered by intake from the repository README and description.MCP server,
Sat 3
13 changes
A simple example of a SAP RAP Application based on Legacy API without UUID keyspublishedWalks through building a managed RAP business object over the Flight Reference Scenario's Travel and Booking entities with unmanaged save and late numbering, so CRUD operations route through the legacy /DMO/FLIGHT_TRAVEL_CREATE, _UPDATE and _DELETE function modules instead of generated persistence, a worked case of ABAP's transactional model. Covers the ADJUST_NUMBERS and SAVE_MODIFIED saver methods that map preliminary draft keys to the legacy-assigned travel and booking IDs, and a GetDefaultsForBookings action that proposes the next booking ID during draft handling.Blog,
ABAP code to wait for the end of "inbound bgRFC type Q" unitspublishedWalks through inbound bgRFC type Q — ABAP's queue-based flavor of async processing built on background remote function calls — and gives a helper ABAP class that polls cl_qrfc_client_inbound for each unit's and queue's state until every unit submitted across a set of parallel qRFC queues has finished. The method assumes no single unit spans more than one inbound queue, and the author flags the classes it relies on, cl_qrfc_client_inbound=>get_unit_state and get_queue_state, as unverified for this use.Blog,
ABAP's Parallel Processing Frameworks: Practical Guide to Performance Tuning of Mass Data ProcessingpublishedSurveys ABAP's two parallel processing technologies, asynchronous RFC (aRFC) and the queued, exactly-once background RFC (bgRFC), and the six frameworks built on top of them, SPTA, SHDB, CL_ABAP_PARALLEL, the Background Processing Framework, the Parallel Processing Framework and the Mass Data Framework, each by its own entry point: a function module, a factory class or a Customizing transaction. A Qualitative Weight and Summ matrix then compares the frameworks across criteria such as package creation, load balancing and documentation quality, stated as the author's own subjective scoring for one project rather than a ranking.Blog,
Configuring SAP Cloud Integration for an IBP to S/4HANA (on prem / private cloud) integrationpublishedWalks through creating the two BTP destinations an Cloud Integration iflow needs for an IBP-to-S/4HANA integration: one of type RFC with a WebSocket RFC server host and port for the IBP tenant, and one of type RFC with the on-premise proxy type, a Cloud Connector location ID and a virtual host for the S/4HANA system. It then has the reader copy SAP's prebuilt IBP integration packages into the Design workspace and deploy every reusable iflow in them before a business iflow can call the S/4HANA extractor through SAP Connectivity service.Blog,
Show 9 more
Debugging in ABAP Development Tool (Part 1)publishedA walkthrough of the ABAP Debugger inside ABAP Development Tools: setting a toggle (hard) breakpoint versus a soft breakpoint that only fires once a session is already active, running up to four debugging sessions on the same program, reading the call stack, and debugging an update function module. It also covers watchpoints with their recent and current values, conditional and user-specific breakpoints, activating and deleting breakpoints, and adding variables such as SY-INDEX to the variables tab.Blog,
Enhancing Standard BAPIs: When and How to Do ItpublishedWalks through why a standard BAPI needs enhancing — a missing field, an extra validation, logic before or after the call, or a performance tweak — and five ways ABAP offers to do it: a BAdI found in SE18/SE19, an append structure for extra fields, a classic user exit wired through SMOD/CMOD, a wrapper function module copied from the original, or an implicit enhancement when no other extension point exists. Each technique gets its own steps, and two carry a short ABAP code example.Blog,
How to Check Fiori Apps Related Authorization Object MasspublishedA structured, table-driven method for mass-checking which authorization objects back a set of Fiori apps: map each Fiori App ID to its OData service, look up that service's hash in USOBHASH, then resolve the hash to its authorization objects (S_SERVICE, S_RFC, among others) in USOBTC. The author reports the method's limits in practice — apps built on a transaction code are already findable directly in USOBTC, and the same approach resolved only 5 of 300 Web Dynpro apps, which needed a manual catalog-and-hash workaround instead.Blog,
Maherd18/sap-mcp-serveradded to the atlasPolicy-checked MCP server for ABAP development over ADTMCP server,
Modernizing RFC/BAPI-based Integrations for a Clean Core with SAP Integration SuitepublishedWalks a BAPI-based interface from SAP PO through three paths to SAP Integration Suite: lift-and-shift, which keeps the RFC connection to the ABAP system as-is and calls it through Integration Suite's RFC adapter; protocol modernization, which re-exposes the same BAPI as a SOAP web service; and clean core modernization, which replaces it with an SAP-managed API surfaced by the migration assessment report. Follows a BAPI_MATERIAL_AVAILABILITY interface through the first and third paths, showing the generated RFC-adapter iFlow against the OData API found for it.Blog,
OData Deep Insert: Implementation and Real-Life ExamplespublishedWalks through implementing OData Deep Insert on classic SAP Gateway: two entity types joined by an association in SEGW, and a redefined CREATE_DEEP_ENTITY method in the DPC_EXT class that unpacks the header and item payload and calls BAPI_SALESORDER_CREATEFROMDAT2 to create a sales order with its line items in one request instead of separate calls per item. Gives a sample JSON payload to test with Postman or /IWFND/GW_CLIENT and names the usual failure points — an unmapped association, a method that was never redefined, or a commit left out after the BAPI call.Blog,
@mcp-abap-adt/corereleased 16.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
fr0ster/mcp-abap-adtreleased 16.0.0Descriptions of five authentication methods including client certificates and Kerberos, and setups that rely on a .env in the directory the server starts in.MCP server,
Maherd18/sap-mcp-serverentry revisedHanded over as a URL. Behind the ABAP door because the objects it reads and changes are ABAP ones in a system reached over ADT. Two edges: agent access to your code for the eight tools over ADT, with create_objects entered as false because the README states that choice rather than leaving it out, and tool governance for the policy file, the allow-lists, the read-only switch, the approval and separation-of-duties rules, the dry-run mode and the audit log, which the README's own opening makes the point of the server. MCP servers was considered and left off: that capability is a protocol adapter on a running application service, and this one helps somebody write code, which its own description sends here. No flavor is stated, since the README names no ABAP release or cloud edition; tool_count is left out because the README names no number, and the eight in the prose is a count of its own Tools table. The second tool governance provider on the ABAP door, where the reading was community-only with one; the coverage note is left to revisit by hand.MCP server,
Fri 2
9 changes
A method to create an Adobe form attachment for a work item using the class concept.publishedWalks through an ABAP workflow class, ZCL_WF_PDF, whose methods call an Adobe form through a Form-Builder-generated function module, convert the returned PDF between hexadecimal string and binary with SCMS_XSTRING_TO_BINARY and SCMS_BINARY_TO_XSTRING, and attach it to a work item via SAP_WAPI_ATTACHMENT_ADD and SAP_WAPI_WRITE_CONTAINER, with the class, background-task and SWDD workflow steps shown in full. It explains document output's ABAP route, rendering a PDF through the Form Builder and getting it back into the program, and a route into attachments's ABAP side distinct from Generic Object Services: a file attached to an SAP Business Workflow work item instead.Blog,
Beyond READ_TEXT: Decoding SAPscript Long Texts (STXL) with SQLScript in CDS/AMDPpublishedSTXL stores a SAPscript long text as a compressed ABAP cluster container — LZ77 plus canonical Huffman — so the only official reads are READ_TEXT, one call per text, and its mass variant READ_TEXT_TABLE, both of which ship every decompressed line to the application server and stay invisible to ABAP CDS. The author reverse-engineered that on-disk format and ported the decoder into SQLScript, wrapped in an AMDP procedure and exposed through CDS table functions, turning long texts into a joinable, filterable column read directly in the database. On ABAP 7.56 a table function needs the driver-and-filter pattern shown because a parameter cannot bind to a calling column; on ABAP 7.58/S/4HANA 2023 the same result becomes a parameter-less CDS scalar function with true filter push-down.Blog,
Clean Core清洁核心概况介绍publishedExplains Clean Core as SAP's architecture methodology for decoupling custom code from standard code, and walks through the A-D grading SAP uses for a single extension's cleanliness: D for direct modification of standard tables, programs, classes or functions, or disallowed patterns such as implicit enhancements; C for internally developed functions calling unreleased APIs; B for using only SAP's classic or released APIs (BAPI, ALV Grid, BAdI); A for side-by-side extensions reached only through released interfaces onto the SAP Build extension suite. It lays out a six-step roadmap for reaching Clean Core — inventorying existing extensions, setting a reduction target, surveying SAP's extension routes (SAP GUI SE80, Fiori custom fields and logic, BTP high/low-code, workflow/RPA), writing a decision tree, splitting new development from legacy migration, and reviewing periodically — while noting that in-app development is not inherently unclean and that real decisions should weigh ROI rather than follow the theory absolutely.Blog,
Enhancing SAP Business Events with Custom Payload Fields using RAPpublishedWalks through enriching an outbound Business Partner event for Event Mesh that by default carries only the partner ID: a derived RAP business event, raised from a behaviour definition with RAISE ENTITY EVENT and bound through SWE2 event linkage to a receiver function module, adds first and last name to the payload. The custom event is defined on a root view entity over BUT000 and verified in /IWXBE/EVENT_MONITOR, where the enriched JSON payload shows the extra fields reaching subscribers without an additional callback to the source system.Blog,
Show 5 more
Invoking Business Agent Foundation Agents from ABAP: A Step-by-Step GuidepublishedWalks through calling a Business Agent Foundation agent's chat endpoint from an on-premise ABAP report: an OAuth 2.0 client profile configured in SE80/SOAUTH2_CLIENT with client-credentials grant against the service key, an HTTP (type G) RFC destination in SM59 bound to that profile, and an ABAP report using CL_HTTP_CLIENT=>CREATE_BY_DESTINATION to POST a JSON message to the agent's sendMessage endpoint and extract the reply by splitting the response string. The destination and client code are the same shape as any outbound REST call from ABAP; nothing here is specific to the agent service beyond the request body and URL.Blog,
Pattern Function for RFCpublishedA custom ABAP Editor pattern, defined once under SE38 > Utilities > More Utilities > Edit Pattern as Z_RFC_FUNCTION, that generates a CALL FUNCTION ... DESTINATION block for a chosen remote-enabled function module: an EDITOR_EXIT function on the calling system reaches the target system over RFC to fetch that function's generated source, then inserts the DESTINATION clause before handing the pattern back to the editor. It automates writing the RFC call itself rather than explaining RFC destinations as a concept, and the destination name in the sample is hardcoded to the author's own system.Blog,
S/4HANA公有云版的内部ABAP拓展publishedArgues that S/4HANA Cloud public edition's in-app ABAP extensibility is still real ABAP development, just under stricter rules: developer extensions require ABAP Development Tools rather than SAP GUI transactions, data models are defined as CDS views instead of SE11 tables, business logic is a RAP behavior definition instead of a function module, and service exposure is an auto-generated OData service from a Service Definition instead of a hand-built RFC/BAPI. The piece walks a worked example — a Fiori app that triggers the Purchase Requisition API — through CDS, RAP, OData activation on SAP Gateway, and authorization via business catalogues, and frames the whitelist of released APIs and CDS views as upgrade-safety rather than a restriction.Blog,
Taking Control of Clean Core: When to Use Project Kernseife in addition to Standard SAP ToolspublishedWalks through how SAP's standard path classifies custom ABAP extensions into Clean Core Levels A through D, running ABAP Test Cockpit against the Cloudification Repository's release status for each SAP object an extension touches, then feeding results into the RISE with SAP Methodology Dashboard in SAP Cloud ALM. Contrasts that with Project Kernseife, an open-source custom ATC check that lets a team override SAP's classification with project-specific rules, define its own successor objects (including custom wrappers), and expose a Score and Potential Score per finding through a CDS view for prioritizing cleanup — at the cost of owning and maintaining that classification. States which situations favor each: Kernseife where the standard rules are too rigid for the project's reality, the standard dashboard where cross-system comparability and low maintenance effort matter more.Blog,
Using Communication Targets for Outbound RFC Communication in ABAPpublishedWalks through calling a remote-enabled ABAP function module through a communication target instead of a direct RFC destination: on-premise, the APPLDEST transaction creates an application destination (client, CPIC type, host from SM51, authentication); in the cloud, saving a communication arrangement for an outbound-RFC communication scenario creates one automatically. ABAP code reaches the function with CALL FUNCTION (...) IN REMOTE SESSION, naming the application_destination parameter when a communication target has more than one assigned destination, and the piece walks a worked call to RFC_SYSTEM_INFO.Blog,
Thu 1
8 changes
ABAP Architectadded to the atlasEclipse plug-in turning JSON or XML into ABAP types and DDIC objectsIDE extension,
abaprapunmanagedadded to the atlasPractice repository for the unmanaged RAP scenarioSample,
abaprapunmanagedsaveadded to the atlasPractice repository for managed RAP with unmanaged saveSample,
abapthemesadded to the atlasThree colour themes for ABAP source in ADT for EclipseIDE extension,
Show 4 more
abapwuluadded to the atlasRefreshes the where-used list for objects in one packageCLI,
sap-ai-dev-toolkitadded to the atlasMCP proxy pinning an agent's ABAP tools to one SAP systemMCP server,
Bellasources, interfaces revisedThe entry recorded the MCP connection Bella opens to ARC-1 and not the one it answers: on the two subscription routes Bella starts a CLI with its built-in tools switched off and hands it the adt_* tools over an MCP server of its own. The README states the server, the address and the token in both of those sections. An interface is a fact about the node and belongs on the thing that offers it (docs/concepts/design-roles-and-interfaces.md §3), so it is entered here rather than left to be read off the CLI's side.IDE extension,
sap-ai-dev-toolkitentry revisedDrafted from the repository's own README and LICENSE after the URL was handed over directly. Typed as an MCP server because what it gives an agent is a generated stdio entry per BAS destination; the setup command and the HANA inspector ship in the same package.MCP server,

Wed 30
4 changes
Bellaadded to the atlasEclipse plugin bringing Claude into ABAP Development ToolsIDE extension,
@mcp-abap-adt/corereleased 15.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
fr0ster/mcp-abap-adtreleased 15.0.0Instructions that start a test run with CreateUnitTest and poll GetUnitTestStatus.MCP server,
Bellaentry revisedHanded over as a repository URL in an intake request. It is the first entry on the ABAP door that puts the assistant inside the ADT editor rather than in front of ADT as a separate server, and its README compares its own tools with those of ARC-1, which the graph already holds.IDE extension,
Tue 29
7 changes
ABAP Statistical Toolsadded to the atlasABAP class for descriptive statistics over an internal tablePackage,
Hammeradded to the atlasNative macOS code editor for ABAP and CDSDesktop app,
pyrfc-mcpadded to the atlasMCP server calling RFC-enabled function modules behind an allowlistMCP server,
S/4HANA Observability: Streaming SAP Cloud ALM & LogServ Telemetry to BigQuery & Vertex AIpublishedWalks through pulling SAP Cloud ALM's Outbound Logs, Metrics and Traces APIs — OAuth 2.0 client-credentials auth, protobuf-encoded OTLP payloads, and the guardrails needed against its rate limits and 24 GB/30-day retention baseline — plus SAP LogServ's infrastructure logs, into Google BigQuery for multi-year, cross-domain storage. A time-window SQL join then correlates ABAP exceptions, health metrics, infrastructure events and ITSM tickets, with the joined record passed to Vertex AI (Gemini) to draft a structured incident dossier.Blog,
Show 3 more
ui5-tcode-finderadded to the atlasBrowser page searching SAP transaction codesWeb tool,
pyrfc-mcpentry revisedHanded over as a URL. Filed behind the ABAP door because the system it reaches is an ABAP one and the reader who points it at theirs is working on that system, which is the opposite case from open-rfc, a client an ABAP developer would never install. Three edges: MCP servers for the tool surface over function modules, agent access to your code for read_abap_source alone, and tool governance for the allowlists, the table guard, the result limits and the audit log, which the README states as the point of the server rather than as a footnote. RFC connectivity was considered and left off: the RFC client here is PyRFC, so nobody installs this to call a function module from their own code. No flavor is stated, since the README names no ABAP release or cloud edition, and auth and tool_count are left out because the README names neither a mechanism nor a number.MCP server,
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.Web tool,
Mon 28
4 changes
claude-sap-kitadded to the atlasClaude Code plugin adding Custom_* tools to arc-1Skill,
@mcp-abap-adt/corereleased 13.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
@mcp-abap-adt/corereleased 14.0.0ABAP ADT MCP server published as an npm scope and pluginMCP server,
claude-sap-kitentry revisedHanded over as a URL. Typed skill rather than mcp-server or package: what a reader installs is a Claude Code plugin of three SKILL.md directories, and the tool surface it brings belongs to arc-1, which serves MCP — one artifact_type per entry (hard rule 9), the same shape ARC-1 Skills takes beside that server. It answers agent access to your code through the five Custom_* tools and agent guidance through the three skills, and states the standard-abap flavor by its requirements, which rule out the two public-cloud ABAP targets by name.Skill,
Sun 27
8 changes
Calling the Sales Order (A2X) OData V2 API from BTP Using a Service Consumption ModelpublishedWalks through ABAP's Service Consumption Model for OData V2 in ABAP Development Tools for Eclipse: generating a client proxy from the Sales Order (A2X) API's downloaded EDMX, then using it from an ABAP console class to create a deep sales order with items, texts, partners and pricing elements, read it back and patch a field. The client itself is built the way HTTP clients describes for SAP BTP ABAP environment: a communication arrangement resolved through cl_http_destination_provider=>create_by_comm_arrangement, handed to cl_web_http_client_manager=>create_by_http_destination, reaching the inbound SAP_COM_0109 scenario configured on the SAP S/4HANA Cloud Public Edition side.Blog,
Calling the Sales Order (A2X) OData V4 API from BTP Using a Service Consumption ModelpublishedWalks through calling SAP S/4HANA Cloud Public Edition's Sales Order (A2X) OData V4 API from an ABAP class on SAP BTP ABAP environment: a communication arrangement on each side, a Service Consumption Model built in ADT from the API's downloaded EDMX, and a client proxy wired through cl_http_destination_provider=>create_by_comm_arrangement and cl_web_http_client_manager=>create_by_http_destination, the same HTTP clients pattern for ABAP for Cloud Development. The sample class creates a deep sales order with an item, a text, a partner and a pricing element, reads it back, then updates a field guarded by its ETag.Blog,
Generating Adobe Form Using RAP framework OData ServicespublishedModels a RAP root view entity and consumption view over a custom sales-order table, built with ABAP CDS, and exposes it through a service definition and an OData V2 UI service binding. A separate SEGW project implements GET_STREAM to call an Adobe Form driver class and stream the rendered PDF back as the response, with a computed link field added to the CDS view so the UI can open it. The PDF is generated in the backend and returned to the calling program rather than sent straight to a printer.Blog,
Usage of Expand Entity in OData Service Consumption ModelpublishedExplains how to use OData's $Expand option when SAP BTP, ABAP Environment consumes a remote service through a generated client proxy, the way HTTP clients describes it, using stubs ABAP Development Tools for Eclipse generates from the service's $metadata. The expanded association only comes back from get_business_data when the caller supplies its own ABAP type that redeclares the association as a nested table, in place of the generated CDS entity type. The same workaround still applies from release 2311 on, where the consumption model generates flat ABAP types rather than abstract CDS entities.Blog,
Show 4 more
ADT MCP Serverpart of, description revisedThe server is a preference inside the extension, and the connection to an ABAP system is the extension's, stated on its own entry with the protocols SAP's marketplace page names (docs/concepts/design-roles-and-interfaces.md, P3); a part points up at its whole and enters the fact once.MCP server,
arc-1connects, requires, description revisedThe connection is what the README states the server fronts (docs/concepts/design-roles-and-interfaces.md, P1), and it attaches the system's entry. The two BTP connections are stated under the README's Cloud Foundry deployment heading, so they carry that condition; the Destination service's sentence states identity forwarding and no data flow, and the ABAP environment's sentence names no protocol. The README's credits table names abaplint as what the linter uses. Two older defects go with it: a nested link that rendered its outer bracket as text, and abap-adt-api named in the same quoted sentence as the other two inspirations and carried by no edge.MCP server,
fr0ster/mcp-abap-adtconnects, description, provides[0], lineage revisedThe README's acknowledgment names the project it started from; the graph holds it, and the edge is the maintainer's own sentence.MCP server,
vibing-steampunkconnects revisedThe connection is what the README states the server fronts (docs/concepts/design-roles-and-interfaces.md, P3): the sentence each ABAP server carries and nobody had entered, which the tool role of the ABAP pilot reads as the arrow from the server to the system.MCP server,
Sat 26
3 changes
AWS Mail configuration for SAP ABAP SystemspublishedWalks through routing an SAP ABAP system's outbound mail through Amazon SES instead of an on-premises mail server or a dedicated EC2 SMTP instance: verifying a sender address and generating SMTP credentials in SES, creating the SMTP node in transaction SCOT, importing the SES endpoint's certificate into the SSL client via STRUST, and testing delivery through SO01 and SOST. It covers the SMTP relay underneath ABAP's mail delivery, the layer Notifications marks as where the core stops and where a channel like this is written on top.Blog,
Configure Journal Entry Posting Approval from Store Template in Build Process AutomationpublishedWalks through deploying SAP's Journal Entry Posting Approval template from the SAP Build Process Automation Store against an on-premise S/4HANA system that has no Secure Network Connection: destinations for S/4HANA via Cloud Connector, for SAP Document Management service, integration option to hold the approval's supporting documents, and for the BPA service and its SMTP mail. It then swaps the template's SNC action groups for basic-connection BAPI calls and deploys the approval's UI5 applications so the task lands in My Inbox, with a Desktop Agent registered to run the unattended document-check and document-post automations.Blog,
Why SAP Cloud Identity Matters for SAP Task Center: It’s About Trust and Global User IDpublishedA step-by-step configuration walkthrough for wiring SAP Cloud Identity Services as the trust and user-correlation layer behind SAP Task Center: establishing Identity Authentication as the sole trusted identity provider for the BTP subaccount, and generating the Global User ID — carried in the token's user_uuid claim rather than the SAML name identifier — that Task Center uses to match logged-in users to their tasks. It also covers syncing that ID between Microsoft Entra ID, the Identity Directory and SAP S/4HANA through Identity Provisioning jobs, and the principal-propagation trust the cloud connector needs to pass it through to an on-premise task provider.Blog,
Fri 25
6 changes
abap-docsadded to the atlasABAP Keyword Documentation as Markdown with indexesDoc source,
LLM-Benchmark-ABAP-Code-Generationadded to the atlasBenchmark of LLM ABAP code generation against a real SAP systemCLI,
local-llm-client-for-sap-consultants-librechatadded to the atlasLibreChat fork with four SAP MCP servers preconfiguredSample,
abap-docsentry revisedEntered as the repository behind two sentences the corpus already rests on. capability:documentation's abap framing says "The ABAP keyword documentation, the cheat sheets and the RAP tutorials are public repositories", and for the keyword documentation the public repository is this one, not SAP's: mcp-sap-docs carries it as the abap-docs submodule (https://github.com/marianfoo/abap-docs.git in .gitmodules), which is where its abap-docs-standard and abap-docs-cloud offline sources come from. doc-source rather than a provider, because that same capability's abap note states publishing a corpus is not answering the concern. identity.license is the license field of package.json; the GitHub API reports no licence for the repository, which is the second sentence of when_not_to_use.Doc source,
Show 2 more
AVEdescription revisedNeither "Simple Data Explorer" nor "SDE" appears in this README, and VERTEX's own README now states "Nothing but this repository's src/ has to be installed", so the claim that VERTEX needs Simple Data Explorer on the system is unsupported. The replacement rests on this README's own sentence: the version history, the diff and the saved code review, "including approving, declining and commenting on a block", are available in Eclipse ADT and in VS Code through VERTEX. "has no blame yet" was a claim about VERTEX that this README does not carry and that was not re-verified against VERTEX; it is dropped rather than restated.App,
Simple Data Explorerdescription revisedThe README no longer says this repository holds the ADT resources VERTEX reads through: two commits on 2026-09-18 removed the ADT resources section and the construction-phase note, leaving only "The table grid with its select-options, the join builder and the pivot are available in Eclipse ADT and in VS Code through VERTEX". VERTEX's own README now states "Nothing but this repository's src/ has to be installed" and that of the former /zsde/ prefix "that hub is gone". The replacement keeps what this README still states and drops the dependency claim neither README supports. ADT.md is still in the repository and still describes the resources under /sap/bc/adt/zsde/ in the present tense, which conflicts with both READMEs and is left for an editor.App,
Thu 24
2 changes
SAP MCP Connection Manageradded to the atlasWindows desktop manager handing SAP connections to assistants over MCPMCP server,
SAP MCP Connection Managerentry revisedHanded over as a URL and drafted from the repository's own README and the GitHub repository record: MIT, JavaScript, created 2026-09-20, not a fork, not archived.MCP server,
Wed 23
3 changes
Clean Core maturity and the new Extensibility LevelspublishedSets out SAP's Clean Core Level concept, the successor to the 3-Tier Development Model, which grades extensibility by how upgrade-safe it is rather than by where it runs: Level A covers on-stack extensions on released RAP and CDS views plus side-by-side apps on BTP, Level B covers upgrade-stable classic APIs listed in the Cloudification Repository, Level C covers internal-object use flagged through SAP's Changelog for SAP Objects, and Level D covers direct modifications and implicit enhancements that ABAP Test Cockpit checks must block. Choosing between an on-stack and a side-by-side implementation is left to the SAP Application Extension Methodology, and the official Level classifications are filed under SAP Note 3578329.Blog,
SAP's API Policy on AI Agents: What It Prohibits, Allows, and Leaves OpenpublishedReading SAP's API Policy v.4.2026a and its FAQ against the reference architectures, the piece narrows the widely repeated claim that SAP bans AI to what Section 2.2.2 actually restricts: an agent planning and chaining API calls outside an SAP-endorsed route, closed off further by Section 3's block on bypassing API Controls through custom code. It compares the endorsed and allowed paths — the MCP Gateway on SAP Integration Suite reaching S/4HANA and ECC through RFC-based back ends under a 15-tool, 200,000-token limit, SAP-provided MCP servers through Joule Studio, the A2A protocol, customer-operated MCP servers allowed under FAQ Question 56, and the ADT MCP Server, whose 18 tools work only on development artifacts and are documented as not intended for productive use. It leaves open whether Section 2.2.2 covers ABAP code that calls a model from inside the system, since enforcement is defined at the API-traffic level rather than by a list of tools.Blog,
arc-1released 1.4.0ctx.run.programRun(name) lets an ARC-1 extension run an active classic ABAP report and return its list output.MCP server,
Tue 22
1 change
off-stack-abapadded to the atlasDemonstration of off-stack ABAP development on Node.jsSample,
Mon 21
5 changes
From SEGW to @OData.publish: Expose Your CDS View as OData in S/4HANApublishedWalks through exposing an ABAP CDS view as an OData service in an on-premise S/4HANA system by adding the @OData.publish: true annotation, then registering and activating the generated service in SAP Gateway (transaction /IWFND/MAINT_SERVICE) before testing it with $filter, $top and $count. It sets this against the manual route through transaction SEGW, since the annotation generates the service, its navigation properties and its OData properties straight from the CDS view without a Service Builder project.Blog,
Multi-Origin Service Testing and Troubleshooting in SAP GatewaypublishedWalks through testing a multi-origin OData service in SAP Gateway by passing the $system parameter against a System Alias defined in /IWFND/MAINT_SERVICE, verified with the SAP Gateway Client (/IWFND/GW_CLIENT) and from outside the system with a browser or Postman. Covers three recurring failures — an ignored $system, a 500 from an unconfigured RFC destination or inactive backend service, and a 403 from a missing backend authorization — and how to confirm which alias and backend a request actually hit with /IWFND/TRACES.Blog,
OData $batch Deleting Records Across Multiple Tables in Single TransactionpublishedWalks through implementing a multi-table DELETE inside a single OData v2 $batch changeset on SAP Gateway: setting cv_defer_mode = abap_true in CHANGESET_BEGIN so more than one delete is collected per change set instead of being executed immediately, looping the collected operations in CHANGESET_PROCESS to delete from each backend table in turn, and issuing one COMMIT WORK in CHANGESET_END so all tables commit or roll back together. The example is a supplier master spread across basic, address, identification and purchasing-organisation tables, deleted as one logical unit of work instead of one HTTP call per table.Blog,
Outbound Integration from SAP BTP, ABAP to SAP S/4HANA Cloud via Service Consumption ModelpublishedWalks through ABAP's Service Consumption Model for OData in ABAP Development Tools for Eclipse: generating a V4 client proxy from a remote service's EDMX metadata, then calling one of its bound actions by hand because the 2311 release's ADT tooling does not yet generate that code. The client itself is built the way HTTP clients describes for SAP BTP, ABAP Environment — a communication arrangement resolved through cl_http_destination_provider=>create_by_comm_arrangement, handed to cl_web_http_client_manager=>create_by_http_destination to create the client.Blog,
Show 1 more
vscode-tabl-ddicadded to the atlasVS Code syntax highlighting for .tabl.ddic table definitionsIDE extension,
Sun 20
1 change
Principal Propagation from BTP Web App to S/4HANA via SAP Integration SuitepublishedWalks through configuring principal propagation from a BTP web app, through SAP Integration Suite and Cloud Connector, to an on-premise S/4HANA system, so the backend receives calls as the logged-in user rather than a shared service account. The BTP Destination service uses OAuth2JWTBearer to exchange the user's Cloud Identity Services JWT for an Integration Suite token, and the iFlow's OData V2 receiver adapter reaches S/4HANA through Cloud Connector with Principal Propagation authentication. The Cloud Connector Subject Pattern builds the outbound certificate's CN from the token's user_name claim, which is populated from the IAS email rather than the sub claim, so identity resolution on S/4HANA hinges on that email matching a resolvable logon name.Blog,
Sat 19
2 changes
abap_cloud_platformadded to the atlasTypeScript library reaching ABAP service instances on Cloud FoundryPackage,
Cloud Connectorconnects revisedThe Connectivity service required the Cloud Connector, and nothing said which of the two opens the connection. SAP's documentation does: the connector registers with the service.App,
Fri 18
38 changes
@arc-mcp/adt-lsadded to the atlasTypeScript SDK over SAP's headless adt-ls language serverPackage,
@root3287/cap-segwadded to the atlasCompiler from a CDS service to SEGW model and data provider classesBuild tool,
050: Clean Core Measurement (Preview)publishedWalks through Clean Core Measurement (CCM), an open-source tool for tracking ABAP Cloud readiness across a system landscape: a dashboard showing Cloud Ready and Upgrade Stable status and a Technical Debt Score per system, runs recorded under administration, and a process area where custom APIs not released by SAP can be documented and excluded from the score. Reporting breaks the score down to individual objects, the unreleased APIs behind them, and which team or product cluster carries the most outstanding work.Blog,
051: ABAP Cleaner in VS Code - Installation and GuidepublishedWalks through installing ABAP Cleaner inside ABAP Development Tools for VS Code and setting it as the default formatter in place of ADT's Pretty Printer, then using its interactive rule view to compare unformatted and cleaned code and configure which rules run, at class, component or method scope. A worked example applies Clean ABAP rules to one method: removing a redundant me-> self-reference and an unneeded EXPORTING keyword, and restructuring a CHECK statement that the styleguide disallows once other statements precede it.Blog,
Show 34 more
052: 10 Minutes from Start to LaunchpadpublishedWalks a RAP application from a root CDS view entity through a consumption projection and its associations to a metadata extension: a facet per field group, a hidden field via UI.hidden, and a selection field on the ABAP package, all in a Customer-layer DDLX source read by the generated Fiori elements app. It then covers the parts ABAP CDS modelling and annotation stop short of — service definition and binding, generating the UI in Business Application Studio, and wiring the deployed app into the Fiori Launchpad through an IAM App and business catalog.Blog,
ABAP in Practice - Creating a Setup ApppublishedWalks through an unmanaged custom entity behind a static Fiori Elements setup app: a factory maps step IDs to implementation classes behind one interface, and the transactional model sets every CRUD operation internal while adding CheckStep and ExecuteStep actions instead of generated persistence. It buffers the executed step for the save sequence and moves an API that issues a COMMIT to a background process via bgPF, since a COMMIT inside the action is forbidden in strict mode.Blog,
ABAP remote filesystemadded to the atlasVS Code extension editing ABAP systems over ADT as a filesystemIDE extension,
ABAP Spreadsheet Importeradded to the atlasABAP component importing XLSX or CSV files into RAP business objectsPackage,
abap_trial_dockeradded to the atlasScripts running the ABAP Developer Edition in DockerCLI,
abap-adt-apiadded to the atlasJS/TS client for the ADT resources of an ABAP systemPackage,
abap-offstack-aunitadded to the atlasAgent skill for off-stack ABAP Unit tests and an abaplint gateSkill,
abap-skillsadded to the atlasSeventeen agent skills for ABAP developmentSkill,
abapcdsgrammaradded to the atlasANTLR4 grammar, lexer and parser for ABAP CDSPackage,
abapfs_extensionsadded to the atlasABAP objects enabling ADT updates on systems older than 7.51Package,
abapgraphadded to the atlasABAP library for creating Graphviz graphsPackage,
abapPrettyadded to the atlasCommand-line ABAP pretty printer over ADTCLI,
ActiveControl Transport form creatoradded to the atlasVS Code extension automating ActiveControl transport formsIDE extension,
adt-bundle-builderadded to the atlasWindows build packaging Eclipse with ADT as a portable IDEBuild tool,
arc-mcp-hubadded to the atlasHub on SAP BTP putting several arc-1 instances behind one loginMCP server,
arc1-abap-bridgeadded to the atlasVS Code bridge between arc-1 and ADT for VS CodePackage,
BTP - Authorization ObjectpublishedWalks through building a classic ABAP authorization object for the ABAP environment — an authorization field, the object itself created in ABAP Development Tools rather than the classic SU21 transaction, and its activities (01 create, 02 change, 03 display, and others) — then wires it into a CDS role's access control with the pfcg_auth aspect on the WHERE condition, which is authorization's ABAP form: CDS access control limiting what a view entity returns to the conditions in a CDS role. The check inherits down to a consumption view and even the Data Preview, and the piece notes the WITH PRIVILEGED ACCESS addition developers use in the SQL console to bypass it while testing.Blog,
BTP - Restriction TypepublishedWalks through creating a Restriction Type and Restriction Field for an ABAP RAP authorization object, so the values an IAM app would otherwise fix as static entries can instead be maintained per Business Role in the Fiori Launchpad. Read and Write access on the restriction still follow the activities defined on the authorization object itself (03 for read, 01/02/06 for write), and the piece shows the effect end to end: a Fiori app narrowed to only the business partners assigned on the role. This is the ABAP door's authorization mechanism made dynamic — an access decision moved from the IAM app's fixed values onto the role, without touching the underlying CDS access control.Blog,
CCM - Calculate Key FigurespublishedExplains how the Clean Core Measurement (CCM) project turns ABAP Test Cockpit findings into the Technical Debt Score shown on its Clean Core Dashboard: messages from the ABAP_CLEAN_CORE_READINESS check are weighted by severity level (B/C/D) and summed per object, while the object's overall classification follows its highest message level rather than the point total. Covers where the calculation can be tuned — configurable weights, an exemption process, and additional metrics for documented but unreleased API use — and how the resulting score and classification drive the object list and per-object processing views.Blog,
DanKromp/skillOverflowadded to the atlasCollection of 41 agent skills, 37 for SAP development tasksSkill,
decodesapsso2added to the atlasTypeScript decoder for MYSAPSSO2 logon ticketsPackage,
Graphviz-browseradded to the atlasStatic page drawing Graphviz graphs for the ABAP debugger extensionWeb tool,
personal-application-studioadded to the atlasTheia distribution with ABAP and UI5 support as a Docker imageDesktop app,
RAP - Feature Control (Part 2)publishedImplements a reusable AUTHORITY-CHECK wrapper class and wires it into a RAP behaviour implementation's Feature Control, both the static global check on Create and the instance-based, partner-scoped checks on Update and Delete, so that an authorization decision greys out an action in the Fiori UI rather than only rejecting it after the save. Part two of the author's Sales App series, it also flags a newer, more strictly typed Feature Control flag SAP introduced since the first article, since using the older type produces a warning and can leave a flag silently without effect.Blog,
RAP - Native File UploadpublishedA workaround for uploading a file into a RAP application ahead of SAP's own upload and download solution, which is still pending: two abstract root entities — one holding the file's bytes, MIME type and filename, one for a popup dialog — joined by an association flagged with hierarchy, exposed through a static action declared with DEEP PARAMETER so the nested structure reaches the handler. The trade-offs are stated plainly: the popup takes no default values, only one file uploads at a time, and the UI annotation on the attachment field is ignored because its label is read from the sub-entity's own name.Blog,
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 annotations covers on the ABAP door: CDS annotations, carried in a metadata extension, driving the Fiori elements UI.Blog,
RAP - Singleton PatternpublishedBuilds the RAP Singleton pattern: a root CDS view entity constrained to always return exactly one row, its composition child for line items, and a transactional model behaviour definition — managed with unmanaged save, a determination that fills the user ID, and an EML update inside SAVE_MODIFIED to write the saved data elsewhere. Generates the Fiori elements object-page app from that service and adjusts Component.js so preferredMode lands the user in edit mode against the fixed semantic key, since the app always has exactly one record to open.Blog,
sap-note-search-mcpadded to the atlasMCP server searching and fetching SAP Notes and KBAsMCP server,
sapdumpmcpadded to the atlasMCP server reading ABAP short dumps over ADTMCP server,
sapskillsadded to the atlasAgent skills for Clean ABAP, ADT in VS Code and guardrailsSkill,
urbani-saplinkadded to the atlasSE16 clone shipped as SAPlink filesApp,
DanKromp/skillOverflowentry revisedDiscovered through the SAP AI Skills Library and represented once at repository level. The registry listed 37 contained skills when checked; the canonical repository contained and documented 41, so the repository count is used for the artifact while both snapshots remain in the crawl record.Skill,
SAP API Policy Evidence Skillrequires revisedThe entry described the skill as gathering evidence "through MCP servers" without naming one, because four of the five were not in the corpus. Three entered in the same batch as their own packages, and mcp-sap-docs and arc-1 were already here, so the README's own prerequisites table becomes edges. Conditional rather than required: the README states the skill degrades gracefully when one is missing and names which two raise confidence to high.Skill,
sap-note-search-mcpentry revisedThe decline recorded for candidate:marianfoo/mcp-sap-notes on 2026-09-10 named this as the successor and as an open gap: "SAP Notes search is a real gap in the corpus and the thing that fills it has to be found some other way." Entered from the monorepo package rather than the archived repository, and from the package's own README.MCP server,
Thu 17
8 changes
abap-adt-cliadded to the atlasCLI that pulls and pushes ABAP packages as local files over ADTCLI,
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 annotations on the ABAP door.Blog,
Creating Material Master Data in SAP S/4HANA Using RAP and EML .publishedBuilds an unmanaged Transactional model RAP business object for Article (Material) master data on top of the standard interface views I_Product, I_ProductDescription and I_ProductPlant, replacing BAPI_MATERIAL_SAVEDATA with EML operations in the create, update and custom extendplant behaviour methods. A CDS metadata extension adds the Fiori annotations — headerInfo, facets, line items and value helps — that drive the generated Fiori elements UI.Blog,
Enhancing Business Processes with SAP BTP AI in SAP Integration SuitepublishedWalks through a post-exit iflow in SAP Integration Suite that calls an LLM through SAP AI Core's Generative AI Hub to turn a customer's free-text return comment into one of a fixed set of SAP rejection-reason codes, so an inbound ORDERS05 IDoc carries a decision (E1EDP01-ABGRU) the ERP can act on without pausing for manual review. The worked example is a Commerce Cloud returns flow into S/4HANA; the piece argues the same bounded-classification pattern fits other narrative fields — delivery-exception remarks, expense-claim justifications — where the cost of an LLM call is repaid by removing a human review step, and points to a colleague's post on the Generative AI Hub orchestration workflow for the guardrailing (prompt templating, data masking) it only names.Blog,
Show 4 more
Extract Rev-Trac requests by custom program and Rev-Trac APIpublishedA custom ABAP report that does a full-text search across custom long-text fields of Rev-Trac change requests — a search the change-management tool has no built-in feature for — by calling Rev-Trac's own RFC-enabled function modules from a separate connected ABAP system. It walks through the mechanics of RFC connectivity on the ABAP side: looking up the RFC destination at runtime from a system table via a remote-enabled function module, then calling further remote function modules with CALL FUNCTION ... DESTINATION, including the read/update APIs' parameter-naming convention and their commit-on-connection-end behaviour.Blog,
How to create a Purchase Order through BAPI in the SAP through program ( SE38 ) T-CODE .publishedWalks through creating a purchase order from an ABAP report (SE38) by filling the BAPIMEPOHEADER/BAPIMEPOITEM structures and their X-indicator counterparts, then calling BAPI_PO_CREATE1 within the same session. Its error handling centres on the BAPIRET2 return table: looping over entries typed E or A, skipping BAPI_TRANSACTION_COMMIT when one is found, and displaying the returned message text rather than assuming success once the function module returns.Blog,
How to Merge Two Separate Smart Forms into a Single PDF in SAPpublishedWalks through generating two separate Smart Forms as OTF, converting each to PDF with CONVERT_OTF, then combining them into one file with cl_rspo_pdf_merge before downloading the result to the frontend. The whole flow runs inside the ABAP system that holds the data, from SMARTFORMS-built forms to a single merged PDF on the local device.Blog,
SAP HANAadded to the atlasSAP's relational database platform, on-premise and in HANA CloudPlatform,
Wed 16
18 changes
A Handy Custom Report to Scan SAP CDS Views for Usage of Search StringspublishedA custom SE38 report, ZSCAN_CDS_VIEWS, reads each Z-prefixed CDS view's DDL source through the function module /ABEX/SEFW_MOD_CVA_HANA and scans it for a list of search strings, listing the view and matching code line in an ALV grid. The author built it because ABAP Development Tools for Eclipse's ABAP Source Search, the code search SAP ships, is unwieldy for scanning many custom views at once or searching several strings together.Blog,
ABAP - Create dumppublishedShows how to terminate an ABAP program on purpose with RAISE SHORTDUMP — from a freshly created exception instance, or one already caught in a TRY/CATCH where continuing no longer makes sense — so a hard-to-diagnose failure leaves a dump behind instead of running on silently. The second half reads that dump back in ABAP Development Tools for Eclipse: the Feed Reader notification, the compressed view against the classic ST22-style view, and sections such as Active Calls and Source Code Extract, the same ADT troubleshooting path debugging places alongside the ABAP Debugger for ABAP Cloud.Blog,
ABAP Select Converteradded to the atlasConverts classic Open SQL SELECTs to released CDS entitiesWeb tool,
ARC-1 Skillsadded to the atlasTwenty-two agent skills shipped with arc-1Skill,
Show 14 more
Calculating IBP Technical Week "Key Figure Date" in S/4HANA Using CDS ViewpublishedA custom ABAP CDS view entity, selecting from the standard I_CalendarDate view, to derive the first date of an SAP IBP "technical week" — the split IBP applies when a calendar week crosses a month boundary, a date S/4HANA does not expose natively. The calculated field is built with a case/when expression over dats_add_days, giving any calendar date's technical-week key figure date.Blog,
CDS Field Mappingadded to the atlasMaps classic dictionary tables and fields to CDS entities and fieldsWeb tool,
Cloudification Repository Vieweradded to the atlasBrowser form over SAP's Cloudification Repository for ABAP CloudWeb tool,
Custom Form with Custom Data Source in SAP Public Cloud (Grow with SAP)publishedBuilds a custom Adobe-based output form for SAP S/4HANA Cloud Public Edition when SAP ships no standard data source: a RAP business object exposes header and item CDS views through a service definition, one view marked as the form's data provider, and the layout is designed offline in Adobe LiveCycle Designer against the exported XML schema before upload and rendering back in the tenant. It draws the line against SAP Forms Service by Adobe on BTP, which the post sets aside in favour of building the form inside the S/4HANA Cloud system itself.Blog,
OData Batch Creatoradded to the atlasBuilds OData batch request payloads from an uploaded $metadata fileWeb tool,
Print Preview from RAP Action with v4 OData and Multiple SelectionpublishedA RAP action's implementation calls SAP Interactive Forms by Adobe through cl_fp for each of several selected keys, merges the resulting PDFs into one file, and returns it as base64 from the action result. A Fiori elements list report invokes the action for the current selection through a controller extension's editFlow.invokeAction, grouped as a single ChangeSet so every selected document is generated and merged in one round trip before the merged file is offered back to the user.Blog,
XLF Translatoradded to the atlasEditor for the translations in an uploaded XLIFF fileWeb tool,
abap-cloud-loggerreleased 2.0.0Examples that keep writing to a logger after free( ), or display a log with zcl_cloud_logger_view_alv.Package,
ABAP Select Converterentry revisedEntered from software-heroes.com's tools page. artifact_type web-tool is new to the schema as of this run, added for exactly this shape: a hosted, no-install utility rather than a package, CLI or BTP service.Web tool,
ARC-1 Skillsentry revisedEntered from the sap-ai-mcp-servers catalogue, which lists the skills bundle as its own "ARC-1 SAP Skills & Claude Plugin" row, separate from the ARC-1 MCP server row already in the corpus as arc-mcp-arc-1. Entered as its own artifact rather than folded into that entry, the same shape the UI5 Web Components skills take beside the UI5 Web Components library — one artifact_type per entry (hard rule 9), and the skills are a distinct install path from the server.Skill,
CDS Field Mappingentry revisedEntered from software-heroes.com's tools page; its data lives in a public GitHub repository the page links as 'Extract and further information', unlike its sibling tools here which are hosted only.Web tool,
Cloudification Repository Viewerentry revisedEntered from software-heroes.com's tools page, as the first artifact_type web-tool in the corpus alongside xexer-abap-select-converter, xexer-cds-field-mapping, xexer-odata-batch-creator and xexer-xlf-translator.Web tool,
OData Batch Creatorentry revisedEntered from software-heroes.com's tools page. ecosystem: abap is an editorial placement rather than a stated fact — the tool's own page names nothing ABAP-specific (it takes any OData $metadata XML) and capability:odata covers both cap and abap doors. Placed on abap for now because it sits among seven other explicitly ABAP tools on the same site and page; worth revisiting if a CAP use turns up.Web tool,
XLF Translatorentry revisedEntered from software-heroes.com's tools page.Web tool,
Tue 15
30 changes
A Clearer View of Your SAP Integrations Under the New API PolicypublishedThe SAP API Policy Evidence Skill assesses one SAP interface or usage pattern at a time against SAP API Policy v.4.2026a, reading evidence from five MCP servers, among them servers for the Business Accelerator Hub and SAP Notes, mcp-sap-docs and a read-only ARC-1, and returns one of four labels with a confidence level, an evidence table, residual risk and questions for SAP. It gives no compliant or not compliant answer on purpose, because SAP's FAQ (Q49) declines to publish a binding decision matrix, and it sends legal, commercial and roadmap questions to SAP and lowers its confidence when a source is not connected. Four sample runs show the method, among them ODP-RFC extraction labelled likely not aligned under SAP Note 3255746 and the same API_SALES_ORDER_SRV assessed differently for an autonomous agent behind a custom gateway and for a Boomi middleware flow; the SAP Notes and Business Accelerator Hub servers read SAP sites through a browser login, which the post says to use at your own risk.Blog,
ABAP and Agentic AI: The Hidden Problem in Real ProjectspublishedAI in SAP development splits on three questions, how the model gets context, where writing happens and who controls the setup: UI5 and CAP work in local files where git, reviews, tests and pipelines already gate a change, while on-stack ABAP writes land directly in a shared development system. Six patterns follow, framed after a paper by Lars Hvam, from AI in the IDE to off-stack development with abapGit, and the post settles on a hybrid where the agent reads the system over ADT or MCP and writes through a gated git flow. Read access alone is put at maybe 80 percent of the work, and what agent access to your code still lacks is named as tool governance: read-only defaults, package restrictions, blocking free SQL, per-user identity and auditing.Blog,
ABAP Development Automation with ARC-1 and GitHub WorkflowspublishedA sample repository puts an ABAP package into GitHub with abapGit and connects GitHub Actions to ARC-1 on BTP through an API key with no write tools, so abaplint on the diff, ABAP Unit and ATC through SAPDiagnose, label-triggered Copilot and Claude reviews, and ST22 dump triage all run as checks on a pull request. The review case is PR #14, where a SAPRead of the activated method let Claude state that a direct SELECT from MARA was new in the PR and not yet active in SAP, which a diff-only review cannot know. The test gate reads activated objects, so a team that pushes before activation needs a sandbox or a pull-and-activate step, and pulling a merged change back into SAP is named as the next step, not built.Blog,
ABAP Development Tools for Eclipseadded to the atlasSAP's Eclipse plugins for ABAP development over ADTPackage,
Show 26 more
ADT resourcesadded to the atlasHTTP endpoint under /sap/bc/adt exposing ABAP development objectsPlatform,
ARC-1 1.0: One Deployment, Multiple SAP SystemspublishedThe release post for ARC-1 1.0, whose largest addition is an experimental multi-system mode: one BTP Cloud Foundry deployment attaches the SAP systems or clients an administrator selects through destinations, each with its own MCP address and an optional combined one, beside 22 included skills, an extension framework for company-specific tools, the BTP login code split out as @arc-mcp/xsuaa-auth, and a move to the ARC MCP organisation. It names the contributions behind the release: Wouter Lemaire for the first Cloud Foundry deployment and the first multi-backend implementation, Sami Bouguerra for NetWeaver 7.50 fixtures and activations that looked successful but were not, Clément Ringot for BTP login and Cloud Connector fixes, and Geert-Jan Klaps for S/4HANA Public Cloud support. It places SAP's own ADT MCP Server as the choice for a developer inside VS Code or Eclipse and ARC-1 as a shared service on BTP, and it stops short of a licence answer: the ADT web endpoints are not listed as published APIs in the SAP Business Accelerator Hub, so readers are told to ask SAP whether their agreement allows third-party tools to use them before a broader or production rollout.Blog,
ARC-1 on SAP BTP: Secure ABAP Agentic Development Beyond the LaptoppublishedThe BTP deployment of ARC-1: one Cloud Foundry app per SAP system, reached by MCP clients through XSUAA and reaching the backend through the SAP Destination service, the SAP Connectivity service and Cloud Connector, with a BasicAuth destination for startup probing and a Principal Propagation destination for per-user requests, and SAP_PP_STRICT=true so a propagation problem fails instead of falling back to the shared user. Tool governance is the three gates it spells out, the server ceiling set by environment variables, the user's permission from XSUAA role collections, OIDC scopes or API-key profiles, and the SAP backend authorisation, all of which must allow an action, and the staged rollout from read-only to writes in $TMP, then selected packages, then transport writes. It recommends the MTA deployment over Docker on Cloud Foundry or a buildpack push, treats BTP ABAP Environment as a separate service-key scenario with no Cloud Connector, and is not a full setup guide: the commands are left to the ARC-1 deployment docs.Blog,
ARC-1 with Copilot Studio: SAP System Context Beyond DeveloperspublishedTakes the BTP-deployed ARC-1 endpoint into Microsoft Copilot Studio, added as an existing MCP server with OAuth 2.0 against XSUAA and published to Teams or Microsoft 365 Copilot, so SAP system context reaches project roles that do not work in an IDE. The test agent combines SharePoint specifications, Jira tickets and mcp-sap-docs with ARC-1 in six scenarios: a patch for a Jira bug proposed before it is applied, the impact of widening a domain from CURR 13,2 to CURR 23,2, a two-layer CDS view built from a specification, an ATC and abaplint quality report, a short dump diagnosis, and a clean core check that proposes released successors for direct selects on USR02 and BUT000. The access path and security model are those of the BTP part unchanged; the advice is to start this audience read-only, although the showcase itself enabled the read and write tools.Blog,
ARC-1 with Joule Studio: Bringing Real ABAP System Context into JoulepublishedBrings the same BTP-deployed ARC-1 endpoint into Joule through a Joule Studio, classic edition agent configured with Anthropic Claude Sonnet 4 and two MCP servers, ARC-1 and mcp-sap-docs, for work that starts in SAP where the previous part started in Microsoft 365. Two read-only showcases carry the ABAP Cloud readiness edge: a clean core check of one class that reports it is not released, uses USR02 and BUT000 directly and has no ATC findings, and a modernisation backlog for package ZSD_LEGACY which, as that package did not exist, grouped 28 ZSD* objects into risk buckets instead. The route through SAP Integration Suite API Management or a future MCP gateway is presented as a target architecture and not yet a productive setup, because Joule Studio's documentation requires streamable HTTP destinations and does not support MCP servers that need interactive OAuth user authorisation.Blog,
Before You Upgrade S/4HANA: Static UI5 Checks with MCPpublishedA UI5 version upgrade checked against one app by pairing two MCP servers: the ui5_version_diff tool added to mcp-sap-docs, which reads a bundle from ui5-lib-diff downloaded once at setup and filters it by version range, change type, library or query text, and @ui5/mcp-server, whose get_project_info, get_version_info, run_ui5_linter and run_manifest_validation say what the app uses and what fails. Run with a ui5-versions-upgrade.md skill on the legacy app from From SEGW and Legacy UI5 to RAP with ARC-1, from SAPUI5 1.84.59 to 1.147.2, the diff range held 985 deprecations and 961 What's New entries, and the linting and manifest validation narrowed that to findings in this app, among them jQuery.sap.require, synchronous bootstrap, the sap_belize theme, sap.m.MessagePage and an old manifest _version. The checks read the source in a local checkout and never the deployed app, so the report is a first pass: a changelog entry is not proof that a workaround can be deleted, and the app still has to be run and tested.Blog,
Building an Enterprise-Ready SAP AI Agent with Open SourcepublishedA self-hosted chat agent for SAP systems: LibreChat as UI and orchestrator with Entra ID sign-in and SharePoint connected, a local LLM through Ollama, and two MCP servers, mcp-sap-docs for public documentation and the ADT MCP server vibing-steampunk for the system itself. The ADT server runs in its read-only mode under a technical user with display authorisations only, so the agent can find a function module and pull its source, or locate a RAP business object with its behaviour definition and projection view, but cannot change anything. Two workflows show it, explaining what BAPI_DISPUTE_CREATE does in one system and planning a RAP action from a PDF specification, where the generated ABAP is copied into Eclipse by hand; the full setup is in the marianfoo/llm-client-sap-system-integration-sharepoint repository.Blog,
Claude ported ABAP functions to new APIpublishedA first-person account of using Claude Code, driven through the sapcli command line, to install and repair RFC function modules that let a CI pipeline control abapGit and gCTS remotely, rather than treating git as a way to read ABAP source. Instead of trusting a local checkout, Claude read the abapGit login manager class and queried the target system's own type catalogue through sapcli, then used what it found to update a renamed API method and swap a TABLES parameter's structure for the table type BAPIRET2_T.Blog,
Cloud Connectoradded to the atlasSAP's on-premises agent linking SAP BTP to customer-network systemsApp,
Finally: An MCP Server for ABAPpublishedAnnounces the ABAP variant of mcp-sap-docs, published at mcp-abap.marianzeis.de for GitHub Copilot's Agent Mode in ADT for Eclipse, which the post names as the trigger, with ABAP knowledge still a recurring problem in the models. Documentation irrelevant to ABAP was removed from the SAP docs server and the ABAP Keyword Documentation, the DSAG ABAP Development Guidelines and the ABAP Style Guide were added, with search reaching past the local index to SAP Community posts and SAP Help. Copilot in Eclipse is where the post puts the weight, because SAP Joule for Developers, ABAP AI capabilities in Eclipse is not available for S/4HANA on-premise systems; an update of 2026-02-05 adds Software Heroes as an online source and an abap_feature_matrix tool that checks feature availability across releases and ABAP Cloud, and the server runs hosted or locally with Node or Docker.Blog,
From SEGW and Legacy UI5 to RAP with ARC-1publishedThree ARC-1 skills, run in Cursor with Composer-2 against a deliberately rough demo on an S/4HANA 2023 trial system, turn the SEGW service ZDEMO_MIG_PROJECTS_SRV into a managed, draft-enabled RAP business object published as OData V4, replace its ApproveProject function import and its direct UPDATE ... COMMIT WORK with the action approve_project written in EML in local mode, and rebuild the freestyle UI5 JavaScript app once in UI5 TypeScript and once as a Fiori elements list report and object page driven by metadata extensions. What the published transcripts add is how the agent got there: it found the generated MPC class names and the custom logic in DPC_EXT only by reading the system, the skills made it print the extracted model and stop for confirmation before writing, and @ui5/mcp-server, mcp-sap-docs and @sap-ux/fiori-mcp-server each had their own job beside it. The demo is small on purpose, and the post says a productive SEGW service that calls BAPIs, carries custom authorisation logic or supports deep inserts is not solved with one prompt.Blog,
How I Use AI for Development and Why Context MatterspublishedPart one of the AI ABAP development series traces a move from pasting ChatGPT output and error messages back and forth to tools that search, read docs and inspect files themselves, and holds that the context around a model decides more in real projects than benchmark results do. In SAP work the grounding comes from mcp-sap-docs, which brings SAP Help, GitHub repositories, style guides and DSAG guidelines into the session, and context for changing a class also means the tables it uses, the classes it calls and similar implementations. Agentic autonomy is a slider set per project, with the time saved on typing moved into planning and review, and the post stops before ABAP: SAP's MCP servers for UI5, CAP and Fiori (@ui5/mcp-server, @cap-js/mcp-server, @sap-ux/fiori-mcp-server) sit in off-stack work that git and pipelines already gate, and the harder ABAP case is left to the next part.Blog,
Introducing ARC-1: A Secure ADT MCP Server for Enterprise SAP DevelopmentpublishedWhy ARC-1 exists beside earlier ADT MCP servers such as vibing-steampunk, fr0ster/mcp-abap-adt and dassian-adt: one centrally deployed instance per SAP system instead of a server on each developer laptop, with the MCP client to ARC-1 hop and the ARC-1 to SAP hop authenticated separately. It sets out the restrictive defaults (read-only, no free SQL or named table preview, writes confined to $TMP), the layering in which ARC-1's configuration, the user's role and SAP's own authorisation must all allow an action, Principal Propagation so SAP sees the real user, and audit events to the SAP Audit Log service; that is tool governance as much as agent access to your code. It leaves the BTP setup to the next part, and places ARC-1 beside SAP's ADT MCP Server, which SAP's configuration guide describes as a local HTTP server hosted by the IDE, and beside SAP API Policy 4.2026a, where ARC-1's stated position is to stay close to documented ADT behaviour and ask SAP before production use.Blog,
Microsoft AI SDK for SAPadded to the atlasABAP library for calling Azure OpenAI and OpenAIPackage,
Moving from Hub Gateway to Direct S/4HANA OData V4: A Customized Reusable RAP Processing FrameworkpublishedA generic base class for RAP custom-entity query providers — one implementation of IF_RAP_QUERY_PROVIDER~SELECT, subclassed per entity — lets a service expose OData V4 directly from S/4HANA instead of through a separate Gateway Hub. The framework loads entity configuration, extracts the request context, fetches and transforms backend data into the target entity shape, and returns it through the RAP response object, with field mapping and conversion exits left for each subclass to fill in.Blog,
Object Release State in Cloudification Repository Viewer for Clean Core ExtensibilitypublishedWalks through the five release states the Cloudification Repository Viewer assigns to an object — Released, Deprecated, Classic API, Not to be Released, and No API — and what each means for ABAP Cloud readiness: the clean core level it maps to and the ATC check priority it triggers. Explains why the same object can carry two states at once, such as a Classic API that later also becomes Released, and why the check has to be run against the specific release being developed on rather than assumed to hold across releases.Blog,
SAP BTP ABAP environmentadded to the atlasABAP runtime on BTP for the ABAP Cloud modelService,
SAP CI to ABAP Integration: Seamless XML to Internal Table MappingpublishedShapes an XML payload in SAP Cloud Integration with the mandatory abap/values wrapper tags so ABAP can deserialise it straight into an internal table with CALL TRANSFORMATION id, the same identity transformation ABAP uses for asJSON. Derives the XSD for that shape from an RFC-enabled function module's WSDL instead of writing it by hand, then exchanges the XML over a plain HTTP client call to a destination.Blog,
SAP Cloud Transport Managementadded to the atlasMoves MTA archives and content between SAP BTP accountsService,
SAP Forms Service by Adobeadded to the atlasAdobe Document Services on BTP for print and interactive PDFsService,
SAP Translation Hubadded to the atlasTranslation service for software texts and documentsService,
Triggering Background Jobs from RAP Actions – A Practical GuidepublishedWalks through a RAP business object whose Saver Class calls a function module IN BACKGROUND TASK from the save phase, and that function module in turn uses JOB_OPEN, SUBMIT ... VIA JOB and JOB_CLOSE to schedule a classic background job that finishes the long-running work, so the triggering UI transaction stays lightweight. The mechanism shown — an asynchronous function-module call plus a submitted executable report — is Standard ABAP background processing rather than ABAP Cloud's released scheduling APIs.Blog,
abapsmithreleased 0.6.0Configurations that set ABAP_TOOL_SURFACE=v2, and prompts written against the six consolidated v2 tools.MCP server,
aibap.mcprequires revisedPointed at the ADT nodes that entered the graph on 2026-09-15, from the project's own documentation.MCP server,
VERTEXrequires revisedPointed at the ADT nodes that entered the graph on 2026-09-15, from the project's own documentation.IDE extension,
vibing-steampunkrequires revisedPointed at the ADT nodes that entered the graph on 2026-09-15, from the project's own documentation.MCP server,
Mon 14
225 changes
abaKadded to the atlasLibrary for managing ABAP constants from registered sourcesPackage,
ABAP AI SDKadded to the atlasSAP reuse library for calling large language models from ABAPPlatform,
ABAP Cloud LoggerpublishedWraps ABAP Cloud's cl_bali_* Application Log classes in ZCL_CLOUD_LOGGER, an open-source, MIT-licensed logger installed via abapGit. One fluent entry point takes free text, sy-msg-style messages, exceptions, BAPIRET2 tables or arbitrary data serialised to JSON, and multiton instances keyed on object/subobject/external number let unrelated code share a logger without passing instances around. It adds sticky per-iteration context, built-in timing, and a readable trail of the cx_bali_runtime errors the class swallows internally.Blog,
ABAP CSV Manageradded to the atlasConfigurable CSV reader and writer for ABAPPackage,
Show 221 more
ABAP development tools for Visual Studio Code is now available on the VS Code marketplace!publishedAnnounces the marketplace release of ABAP development tools for Visual Studio Code, an extension that works against any ABAP system already reachable from ADT for Eclipse and is focused on RAP UI service development, so the Fiori/SAPUI5 frontend and the ABAP backend can be built in the same tool. It ships a built-in ADT MCP Server, disabled by default and switched on from the extension settings, and points readers to a documentation template for capturing ABAP-specific rules in a project's AGENTS.md file for chat agents such as Microsoft Copilot.Blog,
ABAP Development Tools for VS Codeadded to the atlasSAP's ABAP tools in VS Code for editing, debugging, ATC and transportsPackage,
ABAP development under the Clean Core paradigm: From BAPIs to BO and CDSpublishedSAP's Level Based Clean Core classification (2025) grades ABAP APIs A through D by cloud readiness, and this piece uses the S/4HANA Cloudification Repository's own count — of 3,847 BAPI function modules for SAP Cloud ERP Private, only 23 are Level A — to show how much Classic API (Level B) code needs to move to RAP business objects instead. A worked Bank Master example matches each BAPI to its EML statement or ABAP CDS SELECT equivalent, and states when that move is actually required: mandatory once on SAP Public Cloud, optional but advisable on Private Cloud/On-Premise as BAPIs stop gaining new fields.Blog,
ABAP JSON APIadded to the atlasJSON renderer and parser for ABAP with camelCase conversionPackage,
ABAP JSON Encoder/Decoderadded to the atlasJSON encoder and decoder for ABAP, modelled on Go's encoding/jsonPackage,
ABAP OpenAPI UIadded to the atlasSwagger UI for SAP NetWeaver Gateway servicesApp,
ABAP SDK for Azureadded to the atlasABAP classes for calling Azure services from SAP processesPackage,
ABAP to JSON serializer and deserializeradded to the atlasOpen-source Z* version of /UI2/CL_JSON for ABAP to JSONPackage,
abap_btocs_deepladded to the atlasDeepL translation plugin for the B-Tocs ABAP SDKPackage,
abap_btocs_libtrladded to the atlasLibreTranslate plugin for the B-Tocs ABAP SDKPackage,
abap_btocs_ollamaadded to the atlasB-Tocs ABAP SDK plugin connecting to Ollama modelsPackage,
ABAP_DATABASE_MANAGERadded to the atlasABAP report running custom SQL queries into an ALV gridApp,
abap_db_preparatoradded to the atlasReplays stored database snapshots in ABAP unit testsPackage,
abap_debugger_object_graph_extensionadded to the atlasABAP debugger extension drawing objects as a Graphviz graphApp,
ABAP_DeepL_clientadded to the atlasABAP client for the DeepL translation servicePackage,
abap_fm_jsonadded to the atlasJSON adapter exposing ABAP function modules over HTTPPackage,
abap_gui_boilerplateadded to the atlasTemplate for ABAP applications with an HTML UISample,
abap_jwt_generatoradded to the atlasGenerates signed JSON Web Tokens in ABAPPackage,
ABAP_LOGGINGadded to the atlasObject-oriented wrapper around the Business Application LogPackage,
abap_mustacheadded to the atlasMustache template engine for ABAPPackage,
ABAP_TRANSLATION_HUBadded to the atlasReport pushing ABAP objects to SAP Translation Hub and backApp,
abap-alv-struc-vieweradded to the atlasALV table view generated from a DDIC structurePackage,
abap-aws-sigv4added to the atlasSigns outbound HTTP calls to AWS APIs with AWS Signature Version 4, directly from ABAP.Package,
ABAP-CACHE-BOXadded to the atlasGenerates singleton ABAP cache classes from a macro callGenerator,
abap-call-hierarchyadded to the atlasADT backend for the ABAP Call Hierarchy Eclipse pluginPackage,
abap-cloud-loggeradded to the atlasChainable logger for ABAP Cloud around CL_BALI_LOGPackage,
abap-code-search-toolsadded to the atlasIn-system ABAP source search by string or regular expressionPackage,
abap-data-validatoradded to the atlasValidation library for ABAP checking dates, emails and GUIDsPackage,
abap-db-browseradded to the atlasSAP GUI browser for tables, views, CDS views and joinsApp,
abap-dynamic-assignmentadded to the atlasFramework for runtime parameters, ranges and value mappings in ABAPPackage,
abap-feature-toggleadded to the atlasFeature toggle for ABAP read via is_active on view ZFEAT_TOGGLEPackage,
abap-file-uploaderadded to the atlasSample uploading a JSON file into an ABAP table on BTP ABAPSample,
abap-fluentdadded to the atlasFluentd client in ABAP for sending log lines to a collectorPackage,
abap-fm-loggeradded to the atlasLogger storing RFC function module call parameters as JSONPackage,
abap-form-translatoradded to the atlasRuntime translation layer for SAP form labels, kept in a tablePackage,
abap-gencustadded to the atlasGeneric customizing table and reader for ad hoc ABAP parametersPackage,
abap-logadded to the atlasABAP logging library with one interface across output targetsPackage,
abap-log-exporteradded to the atlasExports Business Application Log entries to Graylog or LokiApp,
ABAP-Loggeradded to the atlasLogging library for ABAP over the Application LogPackage,
abap-message-loggeradded to the atlasMessage logger for ABAP Cloud that saves to the Application LogPackage,
abap-metricsadded to the atlasSoftware-engineering metrics for an ABAP class or packageApp,
abap-metrics-provideradded to the atlasExposes ABAP stack metrics to a monitoring toolApp,
ABAP-Object-Visualizeradded to the atlasDebugger script exporting an object hierarchy as GraphvizApp,
abap-odata-testadded to the atlasABAP client for calling and asserting on OData servicesPackage,
abap-openapiadded to the atlasGenerates ABAP client classes and server stubs from OpenAPIGenerator,
abap-opentelemetryadded to the atlasOTLP serialisation of traces, metrics and logs in ABAPPackage,
abap-platform-refscen-flight-soap-serveradded to the atlasServer side of the flight reference scenario for SOAP in ABAP CloudSample,
abap-platform-reuse-servicesadded to the atlasRAP sales order using number ranges, change documents and Adobe formsSample,
abap-point-gateadded to the atlasFramework activating custom ABAP enhancements through a Fiori appPackage,
abap-prometheusadded to the atlasPrometheus client for ABAP, installed with abapGitPackage,
abap-protobufadded to the atlasProtocol Buffers (proto2) implementation in ABAPPackage,
abap-pwnedpasswordsadded to the atlasChecks passwords against Have I Been Pwned from ABAPPackage,
abap-sdk-nwasadded to the atlasAn ABAP client library for IBM Watson's Discovery, Language Translator, Natural Language Understanding, Speech to Text, Text to Speech and Assistant services, installed through abapGit.Package,
abap-sdk-nwas-xadded to the atlasABAP client library for IBM watsonx.ai APIsPackage,
abap-search-toolsadded to the atlasADT backend for the ABAP Search and Analysis Tools pluginPackage,
abap-senchaadded to the atlasBDD/TDD assertion library for ABAP Unit, styled after Chai.jsPackage,
abap-soql-queryadded to the atlasABAP report that runs Salesforce SOQL queries and exports resultsApp,
ABAP-Swaggeradded to the atlasExposes ABAP class methods as REST services with Swagger UIPackage,
abap-system-fieldsadded to the atlasInjectable wrapper for SY fields and date functions in ABAP CloudPackage,
abap-tags-backendadded to the atlasADT backend for the ABAP Tags Eclipse pluginPackage,
abap-tasks-trackeradded to the atlasTask tracker on a BOPF-backed CDS view with a Fiori list reportSample,
abap-test-containeradded to the atlasGitHub-hosted test data container for ABAP CloudPackage,
abap-tvarvcadded to the atlasHelper class for reading TVARVC parameters and select-optionsPackage,
abap-ui-toolboxadded to the atlasABAP classes for classic SAP GUI development: ALV, screens, treesPackage,
abap-ui-toolsadded to the atlasHelper class for classic ABAP dynpro field handling and popupsPackage,
abap-unit-runneradded to the atlasApplication job that runs and schedules ABAP Unit tests in the cloudApp,
abap-utesthelpadded to the atlasHelper classes for ABAP Unit tests and test doublesPackage,
abap2gappsadded to the atlasABAP API for Google Apps, with upload to Google DocsPackage,
abap2gsheetadded to the atlasABAP framework wrapping the Google Sheets API for SAP S/4HANAPackage,
abap2oauth2added to the atlasABAP API for OAuth 2.0 authenticationPackage,
abap2UI5-addons/table-content-loaderadded to the atlasUpload, edit and download ABAP table content as JSON, CSV or XLSXApp,
abap2xlsxadded to the atlasLibrary that reads and generates Excel spreadsheets from ABAPPackage,
abapCovadded to the atlasUploads ABAP Unit code coverage to codecov.ioApp,
abapDataToTableImportadded to the atlasMaps clipboard, Excel or text data onto a declared ABAP structurePackage,
abapdocs-code-scanneradded to the atlasReads the abapDoc comments of a class or interface's public methods and type definitions and returns their text at runtime.Package,
abapDomCheckadded to the atlasChecks field values against domain fixed values and check tablesPackage,
abapEasyALVadded to the atlasWrapper classes over classic ALV and SALV reportingPackage,
abapFakeradded to the atlasFake data generator for ABAPPackage,
ABAPFireadded to the atlasABAP client for Firebase's Realtime Database REST APIPackage,
AbapGeneratoradded to the atlasABAP transaction generating an MVC-style project from a templateGenerator,
abapGitServeradded to the atlasGit server implemented in ABAP for abapGit clientsApp,
abapify/fetchadded to the atlasFetch API-style HTTP polyfill for cloud and classic ABAPPackage,
abapify/fetch-cloudadded to the atlasCloud-compatible plugin for the abapify Fetch API polyfillPackage,
abapify/fetch-legacyadded to the atlasLegacy-release Fetch API implementation for outbound HTTP in ABAPPackage,
abapify/promiseadded to the atlasPromise and async/await implementation for ABAPPackage,
abaplint-Ext-for-abapGitadded to the atlasShows abaplint results inside abapGitPackage,
abaplint-sci-clientadded to the atlasABAP client surfacing abaplint checks in Code Inspector and ATCPackage,
abapMermaidadded to the atlasRenders Mermaid diagrams inside an SAP GUI containerPackage,
abapNTLMadded to the atlasHTTP NTLM client for ABAPPackage,
abapOAuthAzureadded to the atlasOA2C_SPECIFICS implementation for Microsoft Azure OAuth 2.0 in ABAPPackage,
abapOpenChecksadded to the atlasOpen-source rule pack for SAP Code Inspector and ATCPackage,
abapOpenReviewadded to the atlasSAP GUI code review tied to transport releaseApp,
ABAPParallelizationServiceadded to the atlasFramework for running ABAP work units in parallel tasksPackage,
abapPGPadded to the atlasOpenPGP implementation in ABAP, scoped to signingPackage,
abapPM/ABAP-Strustadded to the atlasClass-based wrapper around STRUST certificate managementPackage,
abapTimeMachineadded to the atlasShows a whole ABAP object as it stood at a past versionApp,
abapToCadded to the atlasSAP GUI transaction for one-click transports of copiesApp,
abeljohny/ZAPadded to the atlasMacro DSL turning a one-line select into an ALV listPackage,
adash-servicesadded to the atlasBackend exposing ABAP Unit runs and coverage over REST and ODataPackage,
ADELE RFC APIadded to the atlasRFC-callable ABAP API for SAP data extraction for ADELEPackage,
aditheos/ApplicationLogsNotificationToFioriadded to the atlasFiori launchpad notification for application log errorsApp,
agiguere/SCPmsPushNotificationREST_APIadded to the atlasABAP classes sending push notifications to Mobile ServicesPackage,
AI-native North Star architecture — Platform LayerpublishedThe platform layer of SAP's North Star architecture, the chapter that says where agents run and what a developer builds them with. It names an AI Golden Path built on the SAP Cloud Application Programming Model, the ABAP Cloud development model with RAP and the SAP Fiori design system, and a managed agent runtime on SAP BTP that is designed to provide software development kits for building agents in any framework, an agent sandbox, container-hosted execution, a skills registry and continuous evaluations, which is the ground agent tooling covers. Agents are extended without changing their code through four patterns, the first of them tool extensibility through the Model Context Protocol, the concern MCP servers is named for; the process-layer chapter adds that a pro-code path with a standardised agent SDK and a prompt-driven path through the Joule Studio solution produce the same code artifact on the same runtime. It describes a design SAP intends rather than products that exist, and the SDK and the registry it names have no entry here yet.Reference architecture,
ajsonadded to the atlasJSON parser and serialiser for ABAP with a node treePackage,
alv_gridadded to the atlasDemo programs for the classic CL_GUI_ALV_GRID controlSample,
alv_utilitiesadded to the atlasABAP class wrapping SALV to set column properties in one callPackage,
alwinvandeput/zscv_search_cds_viewsadded to the atlasIn-system search tool for CDS viewsApp,
AnyTabUpdateTaskadded to the atlasUtility for update task database changes and internal tables in ABAPPackage,
aqoadded to the atlasABAP application options as a structure with a generated editorPackage,
assertadded to the atlasFluent assertion helper for ABAP Unit testsPackage,
ATC-Best-Practice-Guideadded to the atlasATC check classes accompanying DSAG's ATC best-practice guideSample,
AttachmentCommentODataServiceadded to the atlasABAP OData service for attachments and comments via GOSPackage,
BenjaminWeisheit/ABAP-2-CODE-CHARTAadded to the atlasConverts ABAP code metrics into Code Charta's JSON formatPackage,
bothzoli/ABAP-IoC-Containeradded to the atlasInversion-of-control container for ABAPPackage,
boy0korea/abap2jsonadded to the atlasExports and imports ABAP table content as zipped JSONApp,
boy0korea/ABAP2XLSX_HELPERadded to the atlasHelper methods over abap2xlsx for Excel, JSON and tablesPackage,
boy0korea/ZWD_CODE_SCANNERadded to the atlasCode scanner for Web Dynpro ABAPApp,
bryanmcain/zcode_scanneradded to the atlasEnhancement extending ECC's code scanner to more object typesPackage,
btp-abap-cnaadded to the atlasRAP bonus-calculation extension across Cloud Foundry, ABAP and KymaSample,
building_gateway_servicesadded to the atlasABAP code and slides from a talk on building SAP Gateway servicesSample,
By-passing function modules in aunitspublishedWalks through registering a function module as a test double with CL_FUNCTION_TEST_ENVIRONMENT inside an ABAP Unit test class: class_setup names the function module to replace, an input configuration matches on the importing parameters, and an output configuration sets what the double returns before the calling class is asserted against it. The Function Test Double Framework is presented as ABAP Unit's way of testing code that calls a function module — procedural, without a class's native test-double support — without triggering the database, RFC or BAPI calls the real function module would make.Blog,
cacamber-BDD-for-ABAPadded to the atlasBDD framework turning Given/When/Then into ABAP Unit stepsPackage,
cds2alvadded to the atlasGenerator for ALV list reports from a CDS view's field definitionsPackage,
cdsanalyseradded to the atlasMaps database tables and fields to the CDS views exposing themApp,
cesar-sap/abap_kafka_rest_proxyadded to the atlasABAP connector to Kafka through the Confluent Kafka REST ProxyPackage,
Clean Core by Design: Event Enablement Cockpit as a Core Integration Enabler in SAP S/4HANApublishedWalks through wiring an on-premise SAP S/4HANA system into Event Mesh as an event producer, using the Enterprise Event Enablement framework: creating the service instance and its service key, then an RFC destination and OAuth 2.0 client configuration in SPRO so a channel can publish native S/4 business events over AMQP or MQTT. Covers the channel's reconnect and quality-of-service parameters and activating the Event Discovery Service, and notes that SAP ECC needs a third-party add-on for the same events since S/4's native Business Events are not available there.Blog,
codepageadded to the atlasPolyfill for CL_ABAP_CODEPAGE under Clean CorePackage,
Content FilteringpublishedContent filtering screens a large language model's input and output for low-quality, irrelevant or unsafe content: the four categories it names being hateful, violent, sexual and vulgar content, checking a request once on the way in and once on the way back. The page states smaller models can do this filtering efficiently, reading perplexity scores to flag anomalies, with the aim that SAP AI Core produces content meeting a stated safety standard, which is the ground content filtering covers on the BTP door.Doc,
coreline/ZDDIC_FINDERadded to the atlasFinder for ABAP Dictionary objectsApp,
COROUTINES4ABAPadded to the atlasCoroutine framework for ABAP with awaitable resultsPackage,
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.Blog,
cuteadded to the atlasCustom Table Editor editing table rows in an editable ALV gridApp,
Data MaskingpublishedData masking replaces identifiable or confidential text in a prompt with placeholders such as <Person_0> or <Organization_1> before it reaches a large language model, using pattern matching and machine learning to find what to replace. The page states SAP AI Core supports it as a feature and sets out five steps for applying it, defining the masking scope, choosing a technique, preserving the prompt's intent, checking compliance and risk, then testing and monitoring the result. That is the shape data masking takes on the BTP door.Doc,
dbg_value_statementadded to the atlasDebugger script generating a VALUE statement for a variableGenerator,
Document GroundingpublishedDocument Grounding is a managed retrieval-augmented-generation service under the Generative AI Hub on BTP, which SAP's page on SAP AI Core places inside that service: it ingests documents from Amazon S3, SharePoint, SAP Document Management Service, SAP Work Zone or an SFTP server, and handles chunking, embedding and retrieval itself, refreshing content automatically when a source document changes. The page states this managed path is recommended for most enterprise scenarios because it covers the whole lifecycle end to end, and offers a separate Document Grounding Vector API for data that is already chunked and embedded, for cases that need finer control over chunking and metadata.Doc,
DryDumbHead/easyHtmlEmailadded to the atlasABAP helper class building HTML emails from templatesPackage,
DSTadded to the atlasIrreversibly anonymises PII and PHI data in non-production SAP systems, against a scrambling template the user creates.App,
dump_infoadded to the atlasDisplays the variables of ABAP short dumpsApp,
EITHER-FOR-ABAPadded to the atlasABAP class implementing the Either patternPackage,
Enhancing Customer Master with a Custom Tab Using SAP TAXI Framework (BAdI + SE80)publishedWalks through adding a custom "Repayment" tab to the Customer Master (XD01/XD02/XD03) using SAP's TAXI framework: an append structure on table KNB1, a subscreen built in SE80, and two BAdI implementations — CUSTOMER_ADD_DATA and CUSTOMER_ADD_DATA_CS — registered through SPRO. The BAdIs are the released extension points that keep the tab upgrade-safe without modifying standard code, the developer-extension half of the capability's tiered model.Blog,
Featuretoggleadded to the atlasFeature toggle framework for ABAP with a UI5 GUIPackage,
FORMfactoradded to the atlasGenerates local classes from FORM-based ABAP programsGenerator,
furkancosgun/Transport-Management-Tooladded to the atlasUploads, downloads and imports ABAP transport requests as filesApp,
furkancosgun/ZWARPadded to the atlasAdds a program's dependent objects to a transport requestApp,
gladiusadded to the atlasABAP project for learning the ABAP Unit Test FrameworkSample,
gregorwolf/AWS_SNS4ABAPadded to the atlasICF handler receiving Amazon SNS notifications in an ABAP systemPackage,
guidrasiladded to the atlasVisual designer generating ABAP code for classic SAP GUI screensGenerator,
HandlebarsABAPadded to the atlasSingle-file Handlebars templating for ABAP 7.40 SP02 and upPackage,
hhelibeb/blowfish-abapadded to the atlasBlowfish cipher in ABAP, ECB and CBC modesPackage,
INVIXO/abapMQadded to the atlasMQTT 3.1.1 client implemented in ABAPPackage,
JSON2ABAPTypeadded to the atlasGenerator of ABAP type definitions from JSON structuresGenerator,
llm_clientadded to the atlasABAP client with one interface to chat-completion LLM APIsPackage,
MBT Logical Object Listeradded to the atlasMetadata viewer for SAP BW, SAP BPC and SAP BW/4HANA object modelsApp,
mkysoft/xlsxreaderadded to the atlasReader for Excel spreadsheets in OpenXML format from ABAPPackage,
mockAadded to the atlasA free mocking framework for ABAP, published under the Apache License 2.0.Package,
mockup_loaderadded to the atlasLoader of Excel-prepared ABAP unit test data, with stub generationPackage,
MQBAadded to the atlasMQTT publish/subscribe in ABAP with an external broker bridgeApp,
my-ide-actionsadded to the atlasCollection of ABAP Development Tools IDE ActionsIDE extension,
odata-fwadded to the atlasABAP framework for OData services with one class per entityPackage,
odbc-driver-for-abap-examplesadded to the atlasExample programs for the ODBC driver for ABAP in several languagesSample,
onurakca/SAPUI5-Adaptation-Project-Downloaderadded to the atlasABAP report downloading SAPUI5 adaptation project artifactsApp,
pawelwiejkut/bw_remove_charactersadded to the atlasABAP class stripping invalid characters in BW end routinesPackage,
pawelwiejkut/bw_trfn_pocketknifeadded to the atlasFramework for BW transformation start routines from a tablePackage,
peterlangner/zrssadded to the atlasRSS feed publisher for content from an SAP NetWeaver ABAP systemPackage,
pokrakam/abapDevSysInitadded to the atlasABAP report setting up a new ABAP Developer Edition or trial systemApp,
Prompt TemplatingpublishedPrompt templating replaces a static prompt with a structured, reusable template whose placeholders are filled in at runtime, which the page says helps LLM responses stay consistent and lets the same instructions be adapted across tasks. On SAP AI Core this is implemented through the Prompt Registry, and the page states that storing prompts as plain strings in code is possible but not recommended. That is prompt management as a stored and managed object rather than a string embedded in the caller.Doc,
qttadded to the atlasTool mapping BEx queries to the transport requests carrying themApp,
regression_testadded to the atlasSnapshot testing library for ABAP, from debugger or unit testPackage,
RESULT-for-ABAPadded to the atlasResult pattern for ABAP instead of exceptions for expected failuresPackage,
RFC_TOOLSadded to the atlasA wrapper class for calling asynchronous RFC function modules in parallel from ABAP, one instance per parallel task.Package,
s4hana-avc-ui-extension-templateadded to the atlasTemplate and mock runtime for S/4HANA Variant Configuration UIsSample,
SAP AI Coreadded to the atlasAI runtime on BTP with the Generative AI HubService,
SAP Joule for Developers, ABAP AI capabilitiesadded to the atlasSAP's AI for ABAP development in ADT for Eclipse and VS CodeService,
SAP Spool PDFadded to the atlasSubmits an ABAP report to the spool and converts the output to PDFPackage,
SAP-easy-AIadded to the atlasABAP report sending a prompt to a local LLM via an SM59 destinationSample,
sap-russia/ZRS_ABAP_SOURCE_SCANadded to the atlasA report that searches code inside modifications and enhancements without depending on SAP HANA.App,
SAP-samples/abap-alv-google-upload-sheetadded to the atlasSample exporting SAP GUI ALV grid data to Google DriveSample,
SAP-samples/abap-platform-application-jobsadded to the atlasRAP sample scheduling a class as a background application jobSample,
SAP-samples/abap-platform-fiori-feature-showcaseadded to the atlasShowcase of Fiori elements for OData V4 features on RAPSample,
SAP-samples/abap-platform-refscen-flight-soap-clientadded to the atlasClient side of the flight reference scenario for SOAP in ABAP CloudSample,
SAP-samples/forms-service-by-adobe-samplesadded to the atlasProjects integrating SAP Forms Service by Adobe with ABAP EnvironmentSample,
sap-usi-authority-checkadded to the atlasAuthority check helper class used across SchwarzIT's USI reportsPackage,
sap-usi-exceptionadded to the atlasShared root exception class and text getter for USI developmentsPackage,
sap-usi-logging-apiadded to the atlasObject-oriented wrapper around SAP's Application Log (SLG1)Package,
SAP2Mooseadded to the atlasAn ABAP program that extracts model data from a system as a SOMIX model, for Moose2Model to draw as a dependency diagram.App,
sbcgua/text2tabadded to the atlasParser of TAB-delimited text into ABAP internal tables and backPackage,
Source Code Finderadded to the atlasReport searching ABAP source in methods, enhancements, DTPs and moreApp,
srijan9864/zrfcreadadded to the atlasAn RFC-enabled ABAP function module that counts the entries of any table against dynamic where and join criteria.Package,
striezl/VariScanadded to the atlasSearch over ABAP program variants for a value or patternCLI,
Sumu-Ning/AESadded to the atlasAES and Rijndael encryption utilities for ABAPPackage,
swixfort/Sdw.Abap.Diadded to the atlasA dependency-injection container for ABAP: register classes or interfaces, then resolve an object with its dependencies already constructed.Package,
table-maintenanceadded to the atlasBrowser-based table maintenance UI built on abap2UI5App,
teched2023-DT187vadded to the atlasTechEd 2023 tutorial on an analytical data model in ABAP CloudSample,
teched2025-AD162added to the atlasTechEd 2025 workshop on a Fiori app with ABAP Cloud and JouleSample,
The Future of ABAP is Here: VS Code ADT, Zero-Config MCP, and AI Co-pilotspublishedA walkthrough of ABAP Development Tools for VS Code's general-availability release: connecting to an on-premise or BTP ABAP system, editing classes, CDS and RAP objects, and turning on the extension's built-in ADT MCP Server. Enabled, it lets a co-pilot such as GitHub Copilot or SAP Joule for Developers, ABAP AI capabilities read code, trace dependencies, and run ABAP Unit and ATC checks against the real system rather than guessing from training data.Blog,
throwadded to the atlasRaises an ABAP exception from a text or the last system messagePackage,
tool-biadded to the atlasChained-call builder for ABAP batch input transactionsPackage,
trm-serveradded to the atlasServer-side component of TRM for importing and exporting transportsPackage,
upDOWNciadded to the atlasUploads and downloads Code Inspector check variants as XMLApp,
Vise_for_ABAPadded to the atlasA characterisation-test helper: ZCL_VISE=>GRIP records a field's value once and fails a later run if it has changed.Package,
XTTadded to the atlasABAP template engine for Excel, Word, HTML and PDFPackage,
ZABAP_SAP_ENHANCEMENTSadded to the atlasReport listing user-exits, BAdIs and enhancement spots of a programApp,
ZABAP_TABLE_EDITadded to the atlasGeneric ABAP table editor writing its own change documentsApp,
ZABAP_TRANSLATIONSadded to the atlasExcel export and import of ABAP package or program textsApp,
ZC8A_001added to the atlasABAP, Python and C code for similarity search over field descriptionsSample,
zcl_docxadded to the atlasABAP class filling a tagged Word .docx template with dataPackage,
zcl_mdp_jsonadded to the atlasABAP library generating and parsing JSON stringsPackage,
zcl_pdfadded to the atlasStandalone ABAP class drawing PDFs without Adobe Document ServerPackage,
zconcurrency_apiadded to the atlasParallel task library for ABAP over the SPTA frameworkPackage,
ZCTS_BROWSERadded to the atlasReport creating transports of copies without a new versionApp,
zllmadded to the atlasABAP framework for chaining and orchestrating LLM callsPackage,
ZOTR_UTILITYadded to the atlasABAP framework reading texts from SAP's online text repositoryPackage,
zstrustadded to the atlasUpdater for root CAs in SAP NetWeaver from Mozilla's certificate storePackage,
ZTCTadded to the atlasA transport checking tool that analyses ABAP transports at object level before they move to production, determining a safe order and flagging risks.App,
zthreadadded to the atlasThreading library for ABAP modelled on Java's Thread and RunnablePackage,
ztoadadded to the atlasOpen SQL editor for ABAP with ALV outputApp,
ZUML_DIAGRAMadded to the atlasABAP program drawing UML class diagrams through PlantUMLApp,
zvdbadded to the atlasVector database implemented in ABAP for document chunk retrievalPackage,
ZwdCSVadded to the atlasRFC 4180 CSV parser and generator for ABAPPackage,
ZwdDynscreenadded to the atlasSelection screens and popups generated from ABAP objects, no dynproPackage,
AttachmentCommentODataServicename, description, provides[capability:attachments] revisedThe ecosystem abap and the business-object binding rested on the platform the README names. The repository is ABAP source in abapGit format, and the cited class is the ABAP that does the binding.Package,
Sun 13
58 changes
ABAP AI Codeadded to the atlasAgentic coding assistant in ABAP that runs as an SAP GUI reportApp,
ABAP development tools for Visual Studio Code: Patch 1.0.1 releasedpublishedA patch to SAP's ABAP development tools for Visual Studio Code, released after two weeks of user feedback: RFC destinations with password logon return, undoing what the first release had dropped, and the extension now ships the AGENTS.md template its documentation already carried, so a project gets agent guidance built in rather than copied by hand. The author still recommends duplicating the template and adding project-specific instructions, since the time spent on that onboarding is what the agent's results depend on.Blog,
ABAP development tools for Visual Studio Code: Version 1.1 releasedpublishedVersion 1.1 of ABAP development tools for Visual Studio Code adds two tools to the extension's local ADT MCP Server: a unified, git-like diff for a transport request, and a runner for ABAP Test Cockpit checks, both meant for an agent to call rather than a person to click through. Both are new instances of what agent access to your code already covers for ABAP — reading and acting on a real system through ADT — reaching now into a transport's changes and a check run rather than only source and objects.Blog,
ABAP-AI-CODE-TOOLSadded to the atlasabapGit package adding create, modify and delete tools to ABAP AI CodePackage,
Show 54 more
abap-docadded to the atlasNode.js command writing PDF documentation for an ABAP packageCLI,
abap-platform-yyadded to the atlasDemo RTTI-style library for the ABAP Environment, built to show APACKSample,
abapconf2026-custom-entitiesadded to the atlasabapconf 2026 talk materials on RAP custom entitiesSample,
abapgit-commitlintadded to the atlasabapGit user exits checking commit messages against repository rulesPackage,
ACEadded to the atlasSAP GUI tool for static analysis of ABAP call flow and code metricsApp,
AVEadded to the atlasSAP GUI version explorer and code reviewer for transport requestsApp,
Calling Claude from ABAP: How I Wired SAP AI Core into a Real Business ScenariopublishedA proof of concept wiring SAP AI Core's Claude deployment directly into ABAP with no CAP layer between them: two SM59 HTTP destinations, a hand-written OAuth 2.0 client-credentials exchange, and a regex to unwrap Claude's system/messages response envelope. Most of the effort goes into a system prompt that constrains the model to return one fixed JSON schema of filter fields, which ABAP deserialises with /UI2/CL_JSON and exposes through a RAP custom action so a Fiori search field can drive an OData V4 filter.Blog,
Creating an SAP SD Billing Document Using a BAPI in SAP Build and Accessing It Through 'Joule Work'publishedWalks through the two pieces of connectivity a SAP Build Process Automation action needs to call an on-premise BAPI: mapping the virtual host to the internal S/4HANA host in Cloud Connector over the RFC protocol, and creating an RFC-type destination in the BTP cockpit so BAPI_BILLINGDOC_CREATEMULTIPLE becomes a selectable action. The resulting process creates an SD billing document from a sales document number and is reached through SAP Build Work Zone, including from the Joule Work mobile app.Blog,
fiori-fullscreen-pluginadded to the atlasFiori launchpad plugin adding a fullscreen toggle buttonSample,
generator-ui5-ts-flp-pluginadded to the atlasEasy-UI5 generator for a TypeScript Fiori launchpad pluginGenerator,
How to Connect Claude Code to ABAP with Zero-Config MCPpublishedWalks through wiring Claude Code, via its VS Code extension, to a live SAP system through an ABAP remote-filesystem extension built by Marcello Urbani and its built-in MCP server — a single toggle rather than a hand-rolled Node.js setup — so the agent searches, reads, writes, activates and assigns transports for ABAP objects over the same ADT REST API Eclipse uses, instead of guessing at tables and function modules it has never seen. The demo carries one plain-English prompt through to a real, activated ABAP program on a live S/4HANA system, including a transport-request dialog Claude worked through on its own.Blog,
How to Scan Custom ABAP for Security Issues in Eclipse (Step-by-Step)publishedWritten by someone who works on the tool, this is a setup walkthrough for the RedRays ABAP Scanner Eclipse plugin: get a demo API key, install the plugin via an update site, point it at a backend, and scan an ABAP object from the Project Explorer. Findings for SQL/ADBC injection, OS command execution, path traversal, missing AUTHORITY-CHECK and similar are grouped by severity with a CVSS score and an automated exploitability check, and a REST API extends the same scan to a CI/CD allow/block gate on a transport.Blog,
HR_DMEadded to the atlasRead-only SAP GUI report listing where HCM object data is storedApp,
ODAPUadded to the atlasUI5 app for OData test requests and ABAP Push ChannelsApp,
Recommendations for Wrapper Interface DesignpublishedWalks through designing a wrapper interface that encapsulates a classic BAPI (BAPI_USER_GET_DETAIL) behind a C1-released interface, so the code released for ABAP Cloud stays limited to types and structures ABAP Cloud can actually access. Covers when a non-released SAP structure can still be referenced safely, when it cannot, and how the API_CONSISTENCY and API_COMPATIBILITY ATC checks catch the difference before an upgrade breaks it.Blog,
SAP-samples/abap-cheat-sheetsadded to the atlasABAP syntax cheat sheets with executable demo classesDoc source,
SAP-samples/abap-partner-reference-applicationadded to the atlasMultitenant S/4HANA Cloud extension built with RAP on BTP ABAPSample,
SAP-samples/abap-platform-analytics-data-modelingadded to the atlasAnalytical ABAP CDS models for the ABAP Flight Reference ScenarioSample,
SAP-samples/abap-platform-bgpf-appl-log-events-side-effectsadded to the atlasRAP sample with bgPF, business events and side effectsSample,
SAP-samples/abap-platform-ccm-workshopsadded to the atlasWorkshop material on adapting custom ABAP code for S/4HANASample,
SAP-samples/abap-platform-codejam-latest-features-2602added to the atlasCodeJam on RAP features from cloud releases 2502 to 2602Sample,
SAP-samples/abap-platform-jakadded to the atlasJSON-to-ABAP conversion library sample showing what APACK can doSample,
SAP-samples/abap-platform-nominated-apis-consumptionadded to the atlasTier 2 wrapper pattern for consuming a nominated API from RAPSample,
SAP-samples/abap-platform-rap-transactional-outbox-with-bgpfadded to the atlasTransactional outbox pattern in ABAP Cloud with bgPFSample,
SAP-samples/abap-platform-rap-workshopsadded to the atlasMaterials for the RAP400 to RAP620 ABAP Cloud workshopsSample,
SAP-samples/abap-platform-rap100added to the atlasBeginner RAP workshop building a draft-enabled Fiori elements appSample,
SAP-samples/abap-platform-rap110added to the atlasIntermediate RAP workshop on late numbering, side effects and eventsSample,
SAP-samples/abap-platform-rap120added to the atlasRAP travel app workshop using SAP Joule for DevelopersSample,
SAP-samples/abap-platform-rap130added to the atlasRAP travel app workshop built from VS Code via the ADT MCP ServerSample,
SAP-samples/abap-platform-rap200added to the atlasGuided workshop building a Travel Processing app in ABAP CloudSample,
SAP-samples/abap-platform-rap620added to the atlasWorkshop on a side-by-side S/4HANA extension on BTP ABAP EnvironmentSample,
SAP-samples/abap-platform-rap630added to the atlasWorkshop on developer extensibility of released RAP business objectsSample,
SAP-samples/abap-platform-rap630-extadded to the atlasExtension project for the RAP630 developer-extensibility workshopSample,
SAP-samples/abap-platform-rap640added to the atlasWorkshop on wrapping a non-released SAP API for use in ABAP CloudSample,
SAP-samples/abap-platform-refscen-flightadded to the atlasFlight Reference Scenario with sample data and services for RAPSample,
SAP-samples/cloud-abap-rapadded to the atlasRAP business object that generates other RAP business objectsSample,
SAP-samples/cross-stack-partner-reference-extensionadded to the atlasCross-stack extension pairing on-stack RAP with a side-by-side CAP appSample,
SAP-samples/joule-gui-automation-and-integrationadded to the atlasJoule capabilities driving SAP GUI sessions via Business ClientSample,
SAP-samples/on-stack-partner-reference-extensionadded to the atlasLoyalty Hub on-stack RAP extension for S/4HANA Cloud Public EditionSample,
SAP-samples/s4hana-gcts-badiadded to the atlasBAdI wiring the transport organizer to gCTS on task releaseSample,
SAP-samples/teched2025-AD163added to the atlasTechEd 2025 workshop modelling a RAP object in SAP Build CodeSample,
SAP-samples/teched2025-AD164added to the atlasTechEd 2025 workshop rebuilding an ALV app as a RAP-based Fiori appSample,
SAP-samples/teched2025-DT260added to the atlasTechEd 2025 workshop modernising a classic app to ABAP CloudSample,
SAP-samples/teched2025-DT261added to the atlasTechEd 2025 workshop extending an SAP-delivered RAP business objectSample,
SAP-samples/teched2025-DT266added to the atlasTechEd 2025 workshop on troubleshooting ABAP Cloud extensionsSample,
Simple Data Exploreradded to the atlasMulti-window SAP GUI explorer for tables, views and CDS SQL viewsApp,
Smart Debuggeradded to the atlasSAP GUI debugger script recording steps so execution can run backwardsApp,
sql-consoleadded to the atlasBrowser-based SQL console built on abap2UI5App,
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-plugin 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.Blog,
Using Claude for SAP ABAP development on RFC-only / SAProuter systems (even ECC R/3)publishedvibing-steampunk gives Claude read, search, edit and check access to ABAP source over ADT's REST API, but some SAProuters permit only SAP's native RFC and DIAG routes and block raw HTTP to the ICM, so that link can't reach them even though Eclipse ADT can. Eclipse gets through because it tunnels ADT over RFC through the standard SADT_REST_RFC_ENDPOINT function module instead of HTTP, a path the post traces by capturing a live Eclipse session. adt-rfc-bridge reproduces that tunnel as a local HTTP-to-RFC proxy built on PyRFC, put in front of vsp, and the author reports it working on both S/4HANA and classic ECC/R/3 systems where Eclipse ADT already connects.Blog,
Using RFC Function Modules and BAPIs in SAP Build Process AutomationpublishedWalks through calling an S/4HANA BAPI (BAPI_BILLINGDOC_CREATEMULTIPLE, to create a billing document) from an SAP Build Process Automation action: mapping the virtual host to the internal system in SAP Cloud Connector over the RFC protocol and exposing the needed function modules, then creating an RFC-type destination in the BTP cockpit with the virtual message server and SMLG logon group. Once those two are in place, SAP Build lists the exposed BAPIs and RFCs for use in an action.Blog,
VERTEXadded to the atlasADT extension for Eclipse and VS Code showing three SAP GUI toolsIDE extension,
ZFPM_TOOLSadded to the atlasEdits, copies and transports a whole FPM hierarchy at onceApp,
ZWD_CALENDAR_VHadded to the atlasWeb Dynpro ABAP calendar value help for date fieldsPackage,
Sat 12
1 change
Claude Code via MCP: Poor man's Joule, or a practical tool?publishedThe author drives Claude Code against a live ABAP system through vibing-steampunk, an ADT-to-MCP bridge that locks and unlocks objects on the agent's behalf so the model can concentrate on the change: extending an ALV report, turning its SELECT into a CDS view, and answering ad-hoc questions over the report's own data. Where Claude got it wrong — a RAP scaffold missing the fields RAP's locking mechanism needs, ORDER as a reserved word — the piece asks where that knowledge would go as a Skill, and concludes Skills' filesystem basis has no home in a system reached only through MCP.Blog,
Fri 11
15 changes
@mcp-abap-adt/corereleased 10.0.1ABAP ADT MCP server published as an npm scope and pluginMCP server,
fr0ster/mcp-abap-adtreleased 10.0.0Embedding code that imports from @mcp-abap-adt/core/handlers, /utils or /server, and statements that the project is MIT or GPL-licensed as a whole.MCP server,
ABAPDocMCPdescription revisedCorrected against the README: it states MIT (GitHub reports no licence file), and it does not state that it builds on vibing-steampunk — that sentence had no source.MCP server,
arc-1description revisedCorrected against the README, which documents a shared-credential mode (technical user) beside per-user identity.MCP server,
Show 11 more
arc1-adt-abap-mcp-extrequires[0] revisedThe cited sentence is no longer in the README: from 0.5.1 the plugin only contributes tools to SAP's supported server; waking the dormant one was 0.3.x.MCP server,
erpl-adtdescription revisedCorrected against the README: prebuilt binaries per platform and pip/uvx installs exist, and telemetry is on by default — neither was stated.MCP server,
fgalastri/MCP_ABAPdescription revisedCorrected: the README states MIT; GitHub still reports no licence file in the repository (checked 2026-09-11).MCP server,
fr0ster/mcp-abap-adtdescription revisedCorrected against the README: SAP_AUTH_TYPE takes basic, JWT/XSUAA, service key, certificate and kerberos; RFC is a connection type, not an authentication method. 'Four' matched neither count.MCP server,
kts982/mcp-sap-guidescription revisedCorrected against the README: 'HTTP transport (for team/remote use, binds to localhost)', with 'Unattended multi-user production orchestration' under Not yet available.MCP server,
mcp-abap-adtdescription revisedCorrected against the README: it never mentions the second server — only mcp-abap-abap-adt-api's README describes the split — and it does not call itself read-only; its tool table does list only reads.MCP server,
mcp-sap-docsdescription revisedCorrected against the README: its offline-sources table lists seventeen repositories, abap-docs-standard through wdi5.MCP server,
mcp-sap-guidescription revisedCorrected against the README: it works from coordinates and screenshots and never mentions the Scripting API. 'Still the most used' was an unsourced popularity claim (hard rule 1); 'the first' is now the GitHub creation date, 2025-02-19, against the other GUI servers.MCP server,
midasol/sap-mcp-serverdescription revisedCorrected against the README: the four tools it documents (sap_authenticate, sap_query, sap_get_entity, sap_list_services) only read.MCP server,
ROSAdescription revisedCorrected against the README: 'The previously hosted public instance (on Railway) has been retired'.MCP server,
sap-security-mcpdescription revisedCorrected against the README, whose Deployment section documents running server.py yourself with OAuth.MCP server,
Thu 10
76 changes
@mcp-abap-adt/coreadded to the atlasABAP ADT MCP server published as an npm scope and pluginMCP server,
ABAP Accelerator MCP Serveradded to the atlasAWS's ABAP MCP server for Amazon Q Developer and KiroMCP server,
abap-ai/mcpadded to the atlasMCP server SDK written in ABAPMCP server,
ABAPDocMCPadded to the atlasMCP server turning a transport request into a WRICEF specificationMCP server,
Show 72 more
ABAPilotadded to the atlasMCP connector for ECC and on-premise S/4HANA with a licensed SAP sideMCP server,
aibap.mcpadded to the atlasGo MCP server that writes, activates and runs ABAP classes via ADTMCP server,
arc-1-lspadded to the atlasEdition of ARC-1 that runs ADT calls through adt-lsMCP server,
arc1-adt-abap-mcp-extadded to the atlasEclipse add-on enabling the ADT MCP server with read-only toolsMCP server,
btp-sap-odata-to-mcp-serveradded to the atlasExposes S/4HANA or ECC OData services as MCP toolsMCP server,
bw-modeling-mcpadded to the atlasMCP server for BW/4HANA modelling objectsMCP server,
chandrashekhar-mahajan/abap-mcp-serveradded to the atlasABAP MCP server with ADT tools and five authentication strategiesMCP server,
claude-abap-skillsadded to the atlasClaude Code plugins with Clean ABAP rules and templatesSkill,
dassian-adtadded to the atlasFork of mcp-abap-abap-adt-api with 25 tools and session recoveryMCP server,
erpl-adtadded to the atlasC++ binary speaking the ADT REST API as a CLI and MCP serverMCP server,
fgalastri/MCP_ABAPadded to the atlasValidates an ABAP class before it is deployed by converting the global class to a local one and syntax-checking that — plus CDS DDL and table metadata retrieval.MCP server,
fr0ster/mcp-abap-adtadded to the atlasABAP MCP server with full CRUD on on-premise and ABAP CloudMCP server,
kts982/mcp-sap-guiadded to the atlasMCP server for SAP GUI for Windows via the Scripting APIMCP server,
MarkWuRY168/SAP_MCPadded to the atlasMCP server publishing SAP functions as tools from config tablesMCP server,
mcp-abap-abap-adt-apiadded to the atlasWrite-oriented MCP server over abap-adt-apiMCP server,
mcp-abap-adtadded to the atlasRead-oriented MCP server fetching ABAP programs, classes, tablesMCP server,
mcp-sap-guiadded to the atlasMCP server working SAP GUI by screen coordinatesMCP server,
midasol/sap-mcp-serveradded to the atlasPython MCP server for SAP Gateway OData operationsMCP server,
odata_mcpadded to the atlasPython bridge generating MCP tools from OData v2 metadataMCP server,
odata_mcp_goadded to the atlasGo binary bridging any OData v2 or v4 service to MCPMCP server,
rap-skillsadded to the atlasRAP skills delivered branch-per-target for each deploymentSkill,
ROSAadded to the atlasMCP server answering whether SAP objects are released for ABAP CloudMCP server,
SAP API Policy Evidence Skilladded to the atlasSkill assessing API usage against the SAP API PolicySkill,
SAP Power for Kiroadded to the atlasSAP skills for the Kiro IDESkill,
sap-basis-opsadded to the atlasRunbook skills for Basis operations at the OS and database layerSkill,
sap-odata-exploreradded to the atlasRust CLI and desktop app for exploring SAP OData servicesDesktop app,
sap-security-mcpadded to the atlasRead-only security analysis MCP server for SAP audits and SoD reviewMCP server,
sapcli Claude Code Pluginadded to the atlasAgents and skills that drive sapcli instead of ADTSkill,
sapgui.mcpadded to the atlasMCP server driving SAP GUI and Web GUI for end-to-end testingMCP server,
SAPient MCPadded to the atlasSAP GUI automation MCP server built on RoboSAPiensMCP server,
secondsky/sap-skillsadded to the atlasForty SAP development plugins for coding agentsSkill,
SuperClaude for SAPadded to the atlasClaude Code plugin with an ABAP MCP server and write guardsSkill,
vibing-steampunkadded to the atlasADT-to-MCP bridge in Go reaching past what ADT exposesMCP server,
workskong/mcp-abap-adtadded to the atlasLight MCP adapter for ABAP over ADT, documented in KoreanMCP server,
@mcp-abap-adt/coreentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
ABAP Accelerator MCP Serverentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
abap-ai/mcpentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
ABAPDocMCPentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
ABAPilotentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
aibap.mcpentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
arc-1-lspentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
arc1-adt-abap-mcp-extentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
btp-sap-odata-to-mcp-serverentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
bw-modeling-mcpentry, provides, requires revisedBW/4HANA entered as an external rather than a service — it is installed software with releases, not something you subscribe to and bind — which finally gave this edge something to point at.MCP server,
chandrashekhar-mahajan/abap-mcp-serverentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
claude-abap-skillsentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
dassian-adtentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
erpl-adtentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
fgalastri/MCP_ABAPentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
fr0ster/mcp-abap-adtentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
kts982/mcp-sap-guientry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README.MCP server,
MarkWuRY168/SAP_MCPentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README. Filed on the BTP door because there is no door for the SAP product it fronts and hard rule 9 allows one — the same strain recorded on the LeanIX entries.MCP server,
mcp-abap-abap-adt-apientry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
mcp-abap-adtentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
mcp-sap-guientry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README.MCP server,
midasol/sap-mcp-serverentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
odata_mcpentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
odata_mcp_goentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
rap-skillsentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
ROSAentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
SAP API Policy Evidence Skillentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
SAP Power for Kiroentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
sap-basis-opsentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
sap-odata-explorerentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Desktop app,
sap-security-mcpentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README. Filed on the BTP door because there is no door for the SAP product it fronts and hard rule 9 allows one — the same strain recorded on the LeanIX entries.MCP server,
sapcli Claude Code Pluginentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
sapgui.mcpentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README.MCP server,
SAPient MCPentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README.MCP server,
secondsky/sap-skillsentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
SuperClaude for SAPentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
vibing-steampunkentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
workskong/mcp-abap-adtentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused.MCP server,
Wed 9
8 changes
ADT MCP Serveradded to the atlasLocal HTTP MCP server started from ABAP Development Tools for VS CodeMCP server,
arc-1added to the atlasMCP server over the ADT REST API for ABAP objectsMCP server,
code pal for ABAPadded to the atlasATC and Code Inspector checks for Clean ABAPPackage,
code pal for ABAP — Cloud Editionadded to the atlasClean ABAP check set for ABAP CloudPackage,
Show 4 more
mcp-sap-docsadded to the atlasMCP server searching seventeen SAP documentation repositoriesMCP server,
ADT MCP Serverentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it. Carries no repository or package because SAP ships none: it is a setting in the VS Code extension, which is the fact worth recording about it.MCP server,
arc-1entry, provides revisedabap-agent-tooling generalised into agent-code-access: the same concern exists in CAP, and the ABAP framing keeps the local name.MCP server,
mcp-sap-docsentry revisedNamed in docs/NEIGHBOURS.md §3.1 as a project of the bestofcapjs author but never entered. It is a documentation retrieval server, not an index of options — the complement posture the same section assigns ARC-1, and hard rule 5 makes it exist here only as an attached entry.MCP server,
Tue 8
13 changes
[Blog Post] SAP Event Mesh - Consuming S4 events simultaneously in CAP-based applications and SAP Integration SuitepublishedOne S/4HANA event, two consumers at once: a CAP Java application and SAP Integration Suite. Late in a long Deep Dive series and written as such — the queues, the S/4HANA connection and the Integration Suite side were all established in earlier posts, so this is the part where they meet.Blog,
ABAP CDSadded to the atlasModelling layer of ABAP Cloud above database tablesPlatform,
Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]publishedThe opening of a three-part series on reaching more than one S/4HANA system from one CAP application with the user's identity carried through. This part sets up the business problem; the propagation itself is in the parts that follow.Blog,
Building an Attachment Upload and Download Solution Using UploadSetwithTable ControlpublishedThe successor control to UploadSet posts the file in one request by default, and against CAP that is wrong: the record has to be created first and the content put to it afterwards. The author states the two-step shape plainly and notes it may not apply to an ABAP backend, which is the kind of boundary that usually goes unsaid. Written during a proof of concept for a reusable attachment component, and it carries the problem they hit with the control.Blog,
Show 9 more
Consume ABAP RFC Function Modules in CAPpublishedCalling an existing RFC function module from CAP instead of asking somebody to build an OData service for it — which is the actual decision, since the alternative is custom development on the ABAP side for a function that already works.Blog,
Consume Remote Services in a Full-Stack CAP ApplicationpublishedExtending the Developer's Guide application with a remote S/4HANA service — connectivity, importing the Business Partner API, and running against it. SAP publishes this as four separate paths: mock server or real S/4HANA Cloud, times Cloud Foundry or Kyma. One entry covers all four, because the difference between them is which backend and which runtime, not what you learn.Workshop,
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.Blog,
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.Blog,
Integrating SAP S/4HANA Invoicing with KSeF Using SAP Event Mesh and CAPpublishedA concrete regulatory deadline rather than a demo topic: every Polish invoice has to pass through KSeF, the national e-invoice platform, and this proposes the route — S/4HANA business events onto Event Mesh, a CAP application consuming them and talking to KSeF. Short, and offered as an example to argue with.Blog,
Part 3: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]publishedThe final part, and the one with the most CAP in it — the service consuming the propagated destinations, and what the handler sees. Read the three together; the series is one piece.Blog,
Part2: Architecting Complex Real Life Business Scenario on SAP BTP with ease [ Targeting Multiple backend S/4HANA Systems utilizing Principal Propagation ]publishedThe middle part: the destinations and the trust that make principal propagation work against several backends rather than one, which is where the configuration stops being a copy of the tutorial.Blog,
@abapify/acdsprovides revisedPlaced on data modelling because it deals in ABAP CDS definitions. Reading the capability again moved it: acds does not help you define data, it parses definitions somebody else wrote into a typed AST — which is the substrate static analysis is built on, and it lives in the adt-cli repository. The mistake surfaced when repointing a CAP package away from the ABAP capability left this one holding it alone.Package,
ABAP CDSartifact type revisedEntered as package for want of anywhere better on the day the enum had no word for a platform component. Nothing publishes or versions ABAP CDS independently, and there is no adoption decision to make about it, which is what the new value is for.Platform,
Mon 7
1 change
@abapify/acdsadded to the atlasParser for ABAP CDS DDL source with a typed ASTPackage,
Sun 6
2 changes
SAP IAM integration with SAP Cloud Identity ServicespublishedIdentity and access management for SAP SaaS in a landscape where SAP is one vendor among several: SAP Cloud Identity Services as the designated interface, single sign-on over SAML 2 and OIDC, identity lifecycle through SCIM 2 replication of users and groups, and authorization designed per domain — an S/4HANA role and a BTP role collection are different objects that both have to reach the user. Drawn from customer projects, and the source of what authentication here says about Cloud Identity Services.Reference architecture,
Transitioning Architectures from SAP NetWeaverpublishedA community contribution from Glencore, an SAP customer, on what replaces NetWeaver-based products as their standard maintenance ends in 2027: the scenarios where NetWeaver-era solutions fall short — integration with cloud-based landscapes, extensibility — and the successor options per use case, pointing at SAP's product availability matrix and note 1648480 for the official successors. Customer-authored, so the framing is a migration decision rather than a product description.Reference architecture,
Fri 4
1 change
pyrfc-mcpreleased 0.1.0Earlier setups in which read calls ran without a configured allowlist.MCP server,

Mon 31
5 changes
abap-file-formatsadded to the atlasSAP's specification for serialising ABAP objects to filesPractice,
abap2UI5added to the atlasUI5 apps written as one ABAP class, rendered by a generic shellPackage,
abapGitadded to the atlasGit client written in ABAP that runs inside the systemApp,
abaplintadded to the atlasStatic analysis for ABAP source outside a systemCLI,
Show 1 more
Clean ABAPadded to the atlasOpen, versioned style guide for ABAPPractice,
Sun 23
1 change
SuperClaude for SAPreleased 0.6.17Instructions that call /sc4sap:team or /sc4sap:release, or set SAP_SYSTEM_TYPE to onprem or legacy in a new profile.Skill,
Tue 18
1 change
arc-1released 1.1.0Tool descriptions or prompts that call SAPGit with the commit action.MCP server,
Wed 5
1 change
abap-dynamic-assignmentreleased 2.0.0Adds the authorization object ZDA_VAR (fields ACTVT, ZDA_PROG), the authorization class ZDA and a DCL role on the root view entity.Package,
The last 90 days. Older changes stay in each entry's history.
AtomJSON