<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>S4hana on Marian Zeis Blog</title>
    <link>https://blog.zeis.de/tags/s4hana/</link>
    <description>Recent content in S4hana on Marian Zeis Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 18 Nov 2026 22:56:24 +0100</lastBuildDate>
    <atom:link href="https://blog.zeis.de/tags/s4hana/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Siemens Uses ARC-1 for SAP Development and Analysis</title>
      <link>https://blog.zeis.de/posts/siemens-arc-1-sap-development-analysis/</link>
      <pubDate>Wed, 18 Nov 2026 22:56:24 +0100</pubDate>
      <guid>https://blog.zeis.de/posts/siemens-arc-1-sap-development-analysis/</guid>
      <description>&lt;p&gt;Before I change an ABAP method, I want to know what else calls it. In SAP, I’d open the where-used list. At Siemens, a developer can ask an AI assistant the same question. &lt;a href=&#34;https://github.com/arc-mcp/arc-1&#34;&gt;ARC-1&lt;/a&gt; lets it look up the answer using that developer’s own SAP permissions.&lt;/p&gt;&#xA;&lt;p&gt;On 7 October 2026, Daniel Dorst, Development Factory Lead at Siemens AG, and I presented &lt;em&gt;SAP und KI richtig einordnen: Zwischen Kontext, Kontrolle und Nutzen&lt;/em&gt; at the DSAG Jahreskongress. I built ARC-1 as an open-source server for ABAP systems. Daniel showed how his team uses it in everyday development.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-code-before-changing-it&#34;&gt;Understanding code before changing it&lt;/h2&gt;&#xA;&lt;p&gt;From Eclipse or VS Code, a developer can ask the assistant to read a method and follow its dependencies in SAP. If two programs call the same method, what does each expect it to return? Sometimes that answer is all the developer needs.&lt;/p&gt;&#xA;&lt;p&gt;When a change is needed, the assistant can check SAP’s documentation for the relevant release and the team’s coding guidelines. The team can also save its usual review steps in a reusable skill.&lt;/p&gt;&#xA;&lt;p&gt;The developer decides whether to accept the change after running syntax checks, the ABAP Test Cockpit (ATC) and ABAP Unit tests.&lt;/p&gt;&#xA;&lt;h2 id=&#34;reviewing-a-transport-task&#34;&gt;Reviewing a transport task&lt;/h2&gt;&#xA;&lt;p&gt;In our &lt;a href=&#34;https://blog.zeis.de/posts/2026-05-12-arc-1-abap-cicd-review/&#34;&gt;ABAP review workflow&lt;/a&gt;, an integration opens a GitHub pull request when a developer releases a transport &lt;strong&gt;task&lt;/strong&gt;. The diff shows the changed lines. What else might the reviewer need to test?&lt;/p&gt;&#xA;&lt;p&gt;Suppose a method now returns a different value. A program that expects the old value can break even if its code never appears in the diff. The assistant can use ARC-1 to find that caller in SAP and flag it for testing.&lt;/p&gt;&#xA;&lt;h2 id=&#34;investigating-a-short-dump&#34;&gt;Investigating a short dump&lt;/h2&gt;&#xA;&lt;p&gt;Did the error start before or after the latest transport? The ABAP short dump in ST22 points to the code that failed. With ARC-1, the assistant can look for earlier occurrences and find transports that touched the affected objects.&lt;/p&gt;&#xA;&lt;p&gt;On SAP 7.50, ARC-1 can read dump summaries through a feed that can omit dumps older than 24 hours. If you need to know when an error first occurred, check ST22 itself. Support for the feed arrived in &lt;a href=&#34;https://docs.arc-1-mcp.com/release-notes/&#34;&gt;ARC-1 1.10.0&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Daniel and I discussed what that would mean for an incident in Siemens’ myIT process. The next person would get the affected object, the dump history and a reason to check a particular transport. They could pick up where their colleague left off.&lt;/p&gt;&#xA;&lt;h2 id=&#34;whose-sap-permissions-does-the-assistant-use&#34;&gt;Whose SAP permissions does the assistant use?&lt;/h2&gt;&#xA;&lt;p&gt;Siemens uses &lt;strong&gt;Principal Propagation&lt;/strong&gt; for all developer access to SAP through ARC-1. SAP BTP forwards the developer’s identity, and the SAP backend checks that person’s authorizations on each request. If a developer can’t read an object in SAP, their assistant can’t read it either.&lt;/p&gt;&#xA;&lt;p&gt;ARC-1 runs on BTP and uses the Model Context Protocol (MCP) to give assistants tools such as ABAP source lookup. Our architecture slide shows where Eclipse, GitHub Copilot in VS Code and Copilot Studio fit in, and how Azure API Management exposes selected APIs.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img alt=&#34;Architecture slide from our DSAG session showing how developer tools reach SAP systems, SAP documentation and internal knowledge sources.&#34; loading=&#34;lazy&#34; src=&#34;https://blog.zeis.de/posts/siemens-arc-1-sap-development-analysis/images/siemens-hybrid-architecture.png&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Say a developer asks Copilot whether a replacement API fits a custom program. Three sources contribute different parts of the answer.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;ARC-1&lt;/strong&gt; shows how the program calls the existing API.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;SAP Docs MCP&lt;/strong&gt; supplies SAP’s documentation for the replacement.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Internal connectors&lt;/strong&gt; provide the team’s guidelines on which approaches it accepts.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;where-joule-for-developers-fits&#34;&gt;Where Joule for Developers fits&lt;/h3&gt;&#xA;&lt;p&gt;At our October session, Siemens was evaluating Joule for Developers. The team hadn’t seen an added benefit for these workflows and left the question open.&lt;/p&gt;&#xA;&lt;p&gt;Later that month at TechEd, SAP outlined agents for ABAP custom code migration, clean-core adaptation and application modernization. Those scenarios give the team something specific to compare in a future evaluation. &lt;a href=&#34;https://community.sap.com/t5/technology-blog-posts-by-sap/agentic-ai-for-abap-development-what-s-new-at-sap-teched-2026/ba-p/14512694&#34;&gt;SAP’s ABAP update from TechEd&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;who-can-enable-changes-in-sap&#34;&gt;Who can enable changes in SAP?&lt;/h2&gt;&#xA;&lt;p&gt;Daniel described Siemens’ approach to sharing knowledge as &lt;em&gt;Share Unless&lt;/em&gt;. Colleagues should have access unless there’s a specific reason to restrict it. For an assistant to change code, the developer needs permission in SAP and the administrator needs to enable the tool in ARC-1.&lt;/p&gt;&#xA;&lt;p&gt;An administrator can keep ARC-1 read-only even for developers who can edit code in SAP. Enabling repository changes and activation takes an explicit opt-in, and writes can be limited to selected packages.&lt;/p&gt;&#xA;&lt;p&gt;Table previews, free SQL and transport writes have separate controls. If a call fails or is denied, operators can check the audit events. &lt;a href=&#34;https://docs.arc-1-mcp.com/authorization/&#34;&gt;ARC-1 authorization guide&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;For teams connecting several SAP systems to one ARC-1 service, version 1.8.0 added a more specific option. An administrator can allow class and interface changes on a Principal Propagation connection pinned to one system and client. The shared connection stays read-only.&lt;/p&gt;&#xA;&lt;p&gt;To use that option, the administrator must enable writes for the destination and grant the developer write access to that target. &lt;a href=&#34;https://docs.arc-1-mcp.com/multi-target-writes/&#34;&gt;Write access to a pinned SAP target&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;With XSUAA OAuth, users also approve the client application requesting access. ARC-1’s October advisory recommends upgrading XSUAA instances to 1.9.0 or later for explicit approval. &lt;a href=&#34;https://github.com/arc-mcp/arc-1/releases/tag/v1.9.0&#34;&gt;XSUAA release notice and upgrade guidance&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img alt=&#34;Governance slide from our DSAG session showing where ARC-1 limits actions, SAP BTP passes identity and the SAP backend checks permissions.&#34; loading=&#34;lazy&#34; src=&#34;https://blog.zeis.de/posts/siemens-arc-1-sap-development-analysis/images/siemens-governance.png&#34;&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;how-much-traffic-reaches-the-sap-backend&#34;&gt;How much traffic reaches the SAP backend?&lt;/h2&gt;&#xA;&lt;p&gt;Investigating a single dump can trigger several SAP requests in parallel. ARC-1 gives operators two controls over that traffic.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Tool calls per user.&lt;/strong&gt; Operators can set a quota on how often each user can call tools. It’s off by default.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Concurrent SAP requests.&lt;/strong&gt; Operators can cap the requests each ARC-1 process sends at once. If several instances share a backend, their combined traffic matters. &lt;a href=&#34;https://docs.arc-1-mcp.com/rate-limiting/&#34;&gt;ARC-1 rate-limiting guide&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;SAP’s reference architecture, updated on 26 October, places a custom MCP server in a customer-managed SAP Business AI Platform subaccount. The operator is responsible for identity, monitoring and downstream API limits. &lt;a href=&#34;https://architecture.learning.sap.com/docs/ref-arch/137800&#34;&gt;SAP reference architecture&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;For ARC-1, counting tool calls alone would understate the load on SAP whenever a tool makes multiple backend requests. Teams also need to clarify how SAP’s API policy applies to direct ABAP Development Tools (ADT) access. &lt;a href=&#34;https://docs.arc-1-mcp.com/sap-api-policy-and-architecture/&#34;&gt;ARC-1’s assessment of SAP’s architecture and API policy&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;where-this-helps-on-ecc-and-s4hana&#34;&gt;Where this helps on ECC and S/4HANA&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;On ECC&lt;/strong&gt;, start with a custom program the team already maintains. Trace its dependencies and ask another developer to check the explanation against the running system. That’s useful even if the team leaves the code as it is.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;During S/4HANA preparation&lt;/strong&gt;, start with an ATC migration finding. Which usage did the check flag? Which custom objects depend on it, and where would a replacement need testing? ARC-1 provides &lt;a href=&#34;https://docs.arc-1-mcp.com/skills/&#34;&gt;skills for investigating migration findings&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;What a developer can check in either system depends on its ABAP release, enabled services and user permissions. &lt;a href=&#34;https://docs.arc-1-mcp.com/deployment/&#34;&gt;ARC-1 deployment guide&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;For a team evaluating ARC-1, I’d pick one familiar task, such as reviewing a transport, and use the three questions from our closing slide.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;How long does it take to reach a change the developer has checked?&lt;/li&gt;&#xA;&lt;li&gt;How much rework remains?&lt;/li&gt;&#xA;&lt;li&gt;What does the review cost once we include model use, operation and developer time?&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;feedback-from-developers&#34;&gt;Feedback from developers&lt;/h2&gt;&#xA;&lt;p&gt;Feedback on older SAP releases, permissions and BTP deployments helped shape &lt;a href=&#34;https://blog.zeis.de/posts/2026-08-03-arc-1-update/&#34;&gt;ARC-1 1.0&lt;/a&gt;. Developers have also built their own tools on top of it. LISA, for example, can run on its own or add three ABAP translation tools to an existing ARC-1 deployment. &lt;a href=&#34;https://github.com/ClementRingot/LISA&#34;&gt;LISA project&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;One recent improvement is handy when tracing dependencies. ARC-1 can now find function-group includes that SAP’s search misses when filtering by include type. That shipped on 7 November in &lt;strong&gt;1.10.1&lt;/strong&gt;, the latest public release as of 18 November. &lt;a href=&#34;https://github.com/arc-mcp/arc-1/releases/tag/v1.10.1&#34;&gt;ARC-1 1.10.1 release notes&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Thanks, Daniel, for sharing how your team works. After the session, many people came over to thank me for ARC-1, ask questions and suggest improvements. I usually see those conversations in GitHub issues. It was great to have them in person.&lt;/p&gt;&#xA;</description>
    </item>
  </channel>
</rss>
