Person
Tobias Hofmann
Capabilities
Provides
IDE provisioningABAPIDE provisioningGetting the IDE onto a developer's machine with the required plugins already in it, at a version the team can name. Distinct from [editor support](capability:editor-support), which is what the editor does once it is there: this is the download, the update site, the install and how the result reaches machines a developer does not administer.Knowing the maintenance status of a releaseABAPUI5Knowing the maintenance status of a releaseKnowing whether a release a solution runs on is still maintained, and until when: which versions get fixes, which get critical fixes only, and when maintenance ends. Upgrading to a newer release once that is known is a different job.
Demonstrates
DocumentationABAPUI5DocumentationFinding the answer in what has already been written, and writing it where it has not — first-party documentation made searchable by something other than a person scrolling it, including by an agent, and a document of custom code produced from the code itself.Static analysisABAPStatic analysisCatching problems in code before it runs: naming, obsolete statements, security findings, and compatibility with a target environment. Style linting, security scanning and cloud-readiness checks are often treated as one concern.Unit testingABAPUnit testingTesting application logic without a running business process — and the test doubles that make dependencies on the database and on framework services tractable.
Contributes to
Editor supportABAPUI5Editor supportWorking in source code with the editor helping rather than treating it as text — completion, go-to-definition, inline errors, refactoring and preview.
Entries
Group by
EntrySignals
Maintains
adt-bundle-builderadt-bundle-builderA Windows build that downloads Eclipse, installs ABAP Development Tools and four more ADT plugins with the Eclipse p2 director, and zips the result as a portable IDE.independent, abap
Windows build packaging Eclipse with ADT as a portable IDE
pam-mcp-serverpam-mcp-serverA local MCP server that answers an agent's questions about the support status of SAP product versions from the reader's own export of the SAP Product Availability Matrix.independent, umbrella
Local MCP server on support status from an SAP PAM export
Maintains: samples, sketches and references
off-stack-abapoff-stack-abapA demonstration of off-stack ABAP development: one class with an add method, linted by abaplint, transpiled to JavaScript and run with its ABAP Unit tests on Node.js.independent, abap
Demonstration of off-stack ABAP development on Node.js
SAP Support RadarSAP Support RadarA browser app that checks the support and maintenance status of the SAP product versions a person runs against their own export of the SAP Product Availability Matrix.independent, umbrella
Browser app checking SAP product support status from a PAM export
Contributes to
my-ide-actionsmy-ide-actionsA collection of eight ABAP Development Tools IDE Actions covering class creation, conversion of classic Open SQL to ABAP SQL, code snippets and RAP tooling.independent, abap
Collection of ABAP Development Tools IDE Actions
Details
History
- pam-mcp-serverStaged as its own entry beside the app (ADR-0063, two entries) because an agent reaches for the server and a person opens the app. part_of rests on the README's project layout. ecosystem: umbrella and serves_ecosystems: abap for the same reasons as the app: it reads the same matrix, and its documentation's worked example queries SAP S/4HANA 2022 and SAP NetWeaver 7.5. No tool_count: the README lists three tools and states no count. Its package is private and not on npm.
- SAP Support RadarStaged with the capability Knowing the maintenance status of a release and the external SAP Product Availability Matrix. ecosystem: umbrella (ADR-0063) because its documentation is about SAP products as such and names no single stack it serves: "Check the support/maintenance status of the SAP products and versions you actually use against the official SAP Product Availability Matrix (PAM)". OpenUI5 is what it is built with, not whom it serves. serves_ecosystems: abap because the releases its documentation checks are SAP S/4HANA and SAP NetWeaver, as in the worked example in docs/mcp-server.md ("SAP S/4HANA 2022 On-Premise", "SAP NetWeaver 7.5"). use_as: reference because it is consulted at its own address. The README names no contributors besides the maintainer. Named SAP Support Radar, the title the maker gives it in the README, by the maintainer's decision on 2026-10-12; serves_ecosystems: abap confirmed by the maintainer the same day.
- First entry seenDiscovered via Added by hand.
Profile
For your agent
- Ref
actor:tobiashofmann- JSON
- /actors/tobiashofmann.json
- MCP
- Connecting an agent