Posts

You have probably seen Joule Work Desktop on LinkedIn by now. Sebastian Steinhaeuser showed how it prepares him for a customer meeting. Philipp Herzig called it the new SAP GUI, with a smile, and demonstrated a workflow across email, a spreadsheet, a Space, and PowerPoint. Joule Work Desktop is now available to SAP employees after a test with more than 6,000 colleagues. Selected customers can also use it through the Early Adopter Care program on macOS and Windows. ...

If you ever wanted to call a remote-enabled ABAP function module from JavaScript or Node.js, you probably discovered quite quickly that this is not as easy as it sounds. There is an RFC protocol. There are remote-enabled function modules. There is an npm package called node-rfc. So you would expect to install the package, add the connection details, and make the call. But npm install node-rfc was never the complete setup. ...

ARC-1 1.0 is here. When I published the first ARC-1 post, I explained why I built an MCP server for ABAP development and why security has to be part of it from the beginning. This post is not another deep dive into every tool. The release notes already do that. For version 1.0 I want to focus on what really changed: ARC-1 became more stable, it can serve multiple SAP systems from one BTP deployment, the BTP and security setup is much better documented, and the project is no longer only one repository. ...

AI can appear in a user interface in several ways. It can add a focused feature such as summarization to a traditional application. It can sit next to the application as a copilot. Or the AI conversation itself can become the main interface. That last case raises an interesting question: if the AI host owns the frame, how can an MCP server provide more than text and JSON? MCP Apps provide an answer. They let an MCP tool return an interactive web interface that a compatible host renders inside the conversation. For our UI5con session, Mike Zaschka and I explored how this model fits SAP user interfaces and built five samples, starting with plain HTML and ending with an ARC-1 transport review. ...

I wanted one practical thing: an editable draw.io diagram for ARC-1 on SAP BTP that looks like it belongs in the SAP Architecture Center. My first attempts with generic diagram prompts were not really useful. They often had dark backgrounds, icons that were too large, and arrows running through boxes. I wanted something closer to the SAP examples: a white canvas, the right BTP areas and service icons, understandable flows, and an editable draw.io file that I could still correct by hand. ...

In April, SAP published a new API Policy (v.4.2026a). If you run SAP integrations of any kind, like middleware, custom extensions, analytics pipelines, RPA, or anything with “AI agent” in the name, you have probably already had the uncomfortable conversation. Are we still allowed to do that, and can we safely start the next project this way? The honest answer is that nobody can fully answer that for you. That is the real problem. ...

Series note: This post is part of my AI ABAP development series. It reuses the legacy UI5 app from the SEGW to RAP migration demo, but this time the focus is only on the UI5 version upgrade problem. In the SEGW to RAP post I used a deliberately old freestyle UI5 app as migration material. It runs on SAPUI5 1.84.59 and contains many patterns that were normal in older projects: jQuery.sap.require, global formatters, synchronous bootstrap, Belize theme, older manifest versions, and a few small controller workarounds. ...

Series note: This post is part of my AI ABAP development series. In the previous posts I introduced ARC-1, then used it from BTP, Copilot Studio, Joule Studio, and a SEGW to RAP migration. This post is about GitHub workflows as an ARC-1 development automation surface. ABAP teams already have strong SAP-side tooling: ATC, Code Inspector, ST22, ADT, and the activated source in the SAP system. GitHub has a different strength: pull requests, review comments, checks, labels, issues, and automation. ...

Series note: This post is part of my AI ABAP development series, where I go from AI development in general, to ABAP-specific problems, and then to ARC-1. In the last posts I introduced ARC-1, explained why I built it, showed the BTP architecture, and then used it from Copilot Studio and Joule Studio. Those posts were mostly about architecture and possible use cases. This one is different. This is the use case ARC-1 was originally built for: making real SAP development easier. ...

Series note: This post is part of my AI ABAP development series, where I go from AI development in general, to ABAP-specific problems, and then to ARC-1. In the previous post, I showed ARC-1 with Microsoft Copilot Studio. The idea was that SAP system context should not be locked inside a local IDE. If ARC-1 runs centrally on SAP BTP, it can also be used from Teams, Microsoft 365 Copilot, SharePoint, Jira, and other places where functional consultants, architects, support teams, and project leads already work. ...