FromthebusinessrequirementtoABAPinyourSAPsystem-withapersondecidingateverygate.
AgentOS is the operating system for AI-powered SAP engineering. Specialist agents analyse the request, design the change, write and review the ABAP, test it and bring it into your development system - inside a governed process your company owns: named approvers, isolated runtime, least-privilege access to SAP, and a knowledge graph of your ABAP estate that grows with every request.
Onerequirement,starttofinish.
Global Manufacturing Corp, request REQ-2841: sales orders for blocked customers must be stopped when a restricted material group is on them. Anna from order management writes it down; the agents and her colleagues take it from there. Recorded on the AgentOS demo environment with fictional data.








Sixsteps,eachwrittenup,threesignedoffbypeople.
The SAP Change template. Every step reads and writes the same request folder, so each one starts from what the previous one proved rather than from the ticket again.
Analyse
SAP Requirements Consultant · functional.md
Turns the request, its attachments and the earlier incidents into an evidence-backed functional analysis: facts, affected interfaces and objects, fit-to-standard, solution variants, effort.
Design
ABAP Architect · technical.md · test-plan.md
Names every object before any code exists: package, repository, BAdI, classes, tables, messages, authorisation objects, delivery path, transport plan and the test cases a tester will run.
Implement
ABAP Developer · Branch · implementation.md
Builds exactly the objects the design lists, as Clean ABAP with ABAP Unit tests, on a branch in the customer's abapGit repository. Static checks with abaplint before the commit.
Review
ABAP Reviewer · code-review.md
A separate, read-only agent reviews the branch against Clean ABAP and the design, grades every finding and changes nothing.
Test
SAP Tester · test-report.md
Executes the test plan, records syntax and activation, ABAP Unit and ATC results as evidence, and reports per case what passed, what failed and what could not be verified.
Release
A person · Deployment into SAP
The approved branch is brought into the development system through abapGit - by the SAP deploy connector on a transport request, with the activation log on the request - or pulled by a developer. Release is always a person's decision.
Writingthecodeisnotthehardpart.Thequestioniswhocontrolstheagent.
Architecture, delivery paths into SAP, the agent roster, engagement options and FAQ are on the AgentOS site.
YourAIworkforce.Underyourcontrol.
Bring one real request. We will run it through AgentOS on your conventions and show you the specification set, the branch and the gates - in a session with your SAP team.