Sap

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. ...

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 wrote about running ARC-1 on SAP BTP. That was the architecture part: central deployment, XSUAA, destinations, Cloud Connector, Principal Propagation, roles, and auditability. This post is the next step. If ARC-1 is already deployed centrally on BTP, then it does not have to be used only from developer tools like VS Code, Claude, Cursor, or Eclipse. It can also be used from Microsoft Copilot Studio and then published into Teams or Microsoft 365 Copilot. That changes the audience quite a bit. ...

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 introduced ARC-1 as a secure ADT MCP gateway for ABAP systems. The main point was not only that ARC-1 can expose ABAP development functionality to AI clients. The main point was that this access needs a place in the architecture. This post is about that place. If ARC-1 should not run uncontrolled on every developer laptop, then SAP BTP is the most natural enterprise option for me. Not because BTP makes the problem disappear, but because it already has the pieces you need for this kind of setup: XSUAA, destinations, Cloud Connector, role collections, audit logging, and the normal BTP operating model. ...

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 first post of this series, I wrote about context and how I use AI in development. In the previous post, I then moved that discussion into ABAP and ended more or less with one question: what would an ADT MCP setup need to look like if you take control, identity, and security seriously from the beginning? ...

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 first post of this series, I wrote more generally about how I use AI today, why context matters so much, and why I am still not fully convinced by the more maximalist agentic hype. Here I want to get more concrete. Because SAP development is not one thing, and that matters a lot for AI. ...

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. When it comes to AI, I do not really think about magic. I think more about another colleague helping me out. Sometimes that means architecture. Sometimes implementation. Sometimes testing, review, CI/CD, or deployment. But this only works with trust, and trust needs communication. If I do not know something, I ask. If code looks strange, I ask. If tests fail, I ask. ...

If you work with SAP Fiori Elements, you have probably run into this problem before: it is hard to see in which UI5 version a specific feature was introduced. Bjorn Schulz already built a strong matrix for ABAP: ABAP Feature Matrix. For Fiori Elements and RAP/CAP, there was no comparable matrix yet. So I created an Influence request to close this gap: influence.sap.com/sap/ino/#idea/351729 The new Developer Portal would be a great home for a matrix like this but so far, there still is no official version. The closest alternative is the SAP Fiori Elements Feature Map in the SAPUI5 documentation. ...

If you are searching for SAP MCP Servers (Model Context Protocol), you quickly run into the same problem: Which SAP MCP servers exist (official and community), and what other SAP AI tooling should you know about? That is why I like this new repo: marianfoo/sap-ai-mcp-servers: SAP MCP Servers and SAP AI Skills list It is a curated list of SAP MCP servers, SAP AI skills, and adjacent developer tools. The README is structured as tables so you can scan by category, compare licenses, and see what is actively maintained. ...