Driving the SAP GUI

Operating SAP's own user interface as a program rather than as a person — the desktop GUI or the Web GUI, driven through the Scripting API. Reached for when a transaction has no API at all, and increasingly when a change needs testing against the real screen rather than against the layer beneath it. Distinct from agent access to your codeAgent access to your codecapabilityLetting a coding agent read the project or the system you actually have, reach its model, its objects and its checks, and act on it. In file-based environments that works out of the box; complex systems need dedicated access capabilities. Whatever the environment, the agent also needs project- and framework-specific context, so it understands the thing in front of it rather than guessing from what it remembers of its training data. The transport is incidental: an MCP server, a language server or a CLI answer the same question, and what differs between them is how much of the real thing the agent can see. Distinct from MCP servers, which is a protocol adapter on your own running service, and from agent guidance, which is knowledge handed over as files rather than read from the thing itself.SAP and community, unassessed, which reaches the objects through ADT and never sees a screen.

Showing artifacts, examples and content with confirmed Standard ABAP applicability. View All ABAP