AGENTIC DEVELOPMENT INSIDE SAP
Give your AI agents the means to act inside your SAP system. From code to operations, with the authorizations and traceability your teams expect.
“Add a test for the discount calculation, check the code and prepare the transport.”
01 / THE PLATFORM
Klystron connects your MCP client to the SAP application server. Native tools to act, a team of agents to deliver, shared knowledge to improve. Each pillar is detailed below.
The MCP server is written in ABAP and runs inside your system. Code, dictionary, CDS and RAP, ATC and ABAP Unit checks, transports, roles and diagnostics, exposed as typed tools. Every object is also a file in SAP’s format, ready for Git.
The server inside SAPA plugin for your MCP client. Agent teams per scenario, from development to incidents; domain skills that carry the SAP procedures and expose to each agent only the tools of its mission.
The agentic pluginThe Central Hub turns field findings into verified, signed documentation redistributed to participating systems. You choose your contribution scope.
The Central Hub02 / USE CASES
Read the context. Propose a change. Verify it. Four scenarios; the first will be replayed from a real session, code included.
“Implement the IPP protocol (RFC 8011) in NetWeaver, in pure ABAP, with no external dependency: a client able to query a printer and send a job. Package ZIPP, unit tests, transport.”
Four-phase plan. No existing object under ZIPP: the Understand phase covers the release, the available HTTP classes and IPP’s binary encoding.
Checks the target package, the release’s HTTP client classes and the locks. Gate criterion: package created, no conflict.
abap_read_packageabap_code_searchabap_where_usedCreates the headers, then writes the sources: IPP attribute encoder and decoder, HTTP client, Get-Printer-Attributes and Print-Job operations. Mass activation.
abap_write_class_headerabap_write_file zcl_ipp_codec.clas.abapabap_write_file zcl_ipp_client.clas.abapabap_activate_objectsRuns the encoder’s unit tests against reference frames, then ATC. Gate criterion: tests green, no priority 1 error.
abap_write_file zcl_ipp_codec.clas.testclasses.abapabap_run_unit_testsabap_run_atcChecks the locks, simulates the release, exports. The package files are pushed to the public repository.
abap_read_transportsap sync zipp/“Add a test for the discount calculation, check the code and prepare the change in my transport.”
03 / HOW IT WORKS
Three mechanisms, in the order of the pillars: the server that exposes the tools, the agents that use them, the hub that builds on what they learn.
An ICF service exposes the tools. Execution, checks and log stay on the SAP side.
zsd_pricing/one folder = one packagezcl_discount.clas.jsonheader · SAP formatzcl_discount.clas.abapsourcezcl_discount.clas.testclasses.abaptestszsd_price.tabl.jsontable · SAP formatzi_sd_price.ddls.acdsCDS viewzi_sd_price.bdef.abdlRAP behaviorzsd_price_var.vari.jsonKlystron formatEvery object has a file name and a format: the one SAP publishes, ABAP File Formats, where it exists; a Klystron format in the same convention otherwise, distinguishable by its version (formatVersion 900). Serialization is SAP’s own: transformations generated from the ABAP types, canonical JSON identical to the SAP handler’s.
A defined scope for each domain and activity. Reading, changing and executing are separate permissions, checked on the server.
Typed inputs and outputs, in the vocabulary of the files. The agent knows what to send, what to expect and why a request is refused.
Syntax check before anything is saved; fingerprint and conditional write against concurrent overwrites; read-back after writing.
The AI model remains your client’s: the choice of provider and the data sent to it are governed by your policy.
A plugin for your MCP client: agent teams, domain skills, and the server’s tools.
Why this stack. Loading every SAP tool into an agent’s context wastes context and says nothing about ordering rules or risks. Skills bring the procedure and a restricted tool catalog; each agent only reaches the domains its mission needs; SAP controls frame the execution.
An orchestrator holds the gate criteria; each agent hands verifiable evidence to the next.
The analyst · skills sap-abap-dev, sap-transports
Explores the repository, dependencies and scope of the change.
The developer · skills sap-abap-dev, sap-ddic
Changes ABAP objects, prepares tests and checks activation.
The QA agent · skill sap-quality
Runs ABAP Unit and ATC, then links the results to the change.
The release agent · skill sap-transports
Checks locks and prepares the transport under the delivery rules.
A loop: what one customer learns comes back to all the others.
Findings, incidents, release quirks: every mission leaves documentation behind.
Signed, encrypted contributions, within the scope you chose.
Triage, reproduction on reference systems, human review, signed publication.
Business documentation, known limits and verified solutions, for the teams and their agents. Then the loop starts again.
The hub is optional: the native SAP tools work without it. Sharing is enabled as you need it.
04 / WHY NOW
Teams need to modernize code, prepare the transition and keep systems running. Our approach: give agents practical access to the system, within a framework SAP teams can examine.
Mainstream maintenance for core Business Suite 7 applications ends in late 2027; optional extended maintenance runs through the end of 2030.
SAP maintenance strategyMCP connects your agents to SAP. Klystron gives them the tools, the method and the knowledge to act.
SAP on the agentic evolution05 / THE RIGHT QUESTIONS
Data, rights, hosting and its place in your toolchain.
No. The MCP server is written in ABAP and runs inside the SAP application server, behind an ICF service. You then connect your MCP client. The agent and its model keep their own hosting and network requirements.
Results your MCP client sends to the model may contain code or system data. A server inside SAP does not mean the model is local. The client, AI provider, authorized domains and accessible data are part of the pilot scope.
The SAP identity used by the client, the applicable native permissions and the server’s authorizations by domain and activity. Any technical account must be explicitly authorized. Validate the pilot scope with the account that will actually be used.
You can use the native SAP tools independently of the Central Hub. Enable knowledge exchange as needed, with an explicit configuration and contribution scope.
The Central Hub shares verified knowledge. Agents work in their own environment, under your system’s SAP controls. The hub collects contributions, coordinates reproduction and review, then distributes signed documentation. Your teams retain control of execution and shared data.
Klystron provides tooled access to the system through MCP, plus agents and skills to use it. Your assistant remains responsible for reasoning; abapGit and your pipelines remain your versioning and delivery tools, and the files in SAP formats fit into them. Connection options depend on the MCP client you choose.
Deployment is scoped to your release, components and use cases, on ECC or S/4HANA. A development or test pilot validates scenarios and permissions with your teams. Production rollout follows your change management and operations processes.
Choose a release, a domain and a measurable scenario: an ABAP test, findings analysis or a role proposal.
06 / LET’S START WITH A REAL USE CASE
One system. One scope. One first use case.