Person

Yurii Sychov

Capabilities7

Provides 5
Agent access to your codeABAPAgent 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](capability:mcp-servers), which is a protocol adapter on your own running service, and from [agent guidance](capability:agent-guidance), which is knowledge handed over as files rather than read from the thing itself.Browsing table dataABAPBrowsing table datacapabilityLooking at what a system holds while developing or supporting it: the rows behind a key, the reference data a field points at, the tables that carry data for one object. Editing configuration records through maintenance screens is a different job, even where the same transaction does both.Code reviewABAPCode reviewcapabilityReading a change before it moves on: which files or objects a change contains, what changed in each since an earlier version, and what a reviewer decided about each part. Comparing two versions of one object is where it starts; the review is the record kept of the decision.DebuggingABAPDebuggingcapabilitySeeing what running code did between an input arriving and a result coming out: which code ran, what the values were at each point, and why a value ended up as it did.Static analysisABAPStatic analysiscapabilityCatching 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.
Demonstrates 1
LLM integrationABAPLLM integrationcapabilityCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.
Contributes to 1
SAP GUI screens and listsABAPSAP GUI screens and listscapabilityBuilding screens, lists and interactive controls for the SAP GUI. Producing a web interface is [UI written in ABAP](capability:abap-ui-from-abap); operating an existing screen programmatically is [GUI automation](capability:gui-automation).

Entries10

Group by10 of 10 entries
EntrySignals
Maintains8
ABAP AI Code
none

Agentic coding assistant in ABAP that runs as an SAP GUI report

ABAP-AI-CODE-TOOLS
none

abapGit package adding create, modify and delete tools to ABAP AI Code

ACE
none

SAP GUI tool for static analysis of ABAP call flow and code metrics

AVE
none

SAP GUI version explorer and code reviewer for transport requests

HR_DME
none

Read-only SAP GUI report listing where HCM object data is stored

Simple Data Explorer
none

Multi-window SAP GUI explorer for tables, views and CDS SQL views

Smart Debugger
none

SAP GUI debugger script recording steps so execution can run backwards

VERTEX
none

ADT extension for Eclipse and VS Code showing three SAP GUI tools

Maintains: samples, sketches and references1
SAP-easy-AI
none

ABAP report sending a prompt to a local LLM via an SM59 destination

Contributes to1
abapMermaid
none

Renders Mermaid diagrams inside an SAP GUI container

Details

History4
  • AVEdescription.what_it_solves → Versions, diffs and saved reviews also show in Eclipse ADT and VS Code through [VERTEX](artifact:ysichov-vertex), where a block can be approved, declined and commented on as well.Neither "Simple Data Explorer" nor "SDE" appears in this README, and VERTEX's own README now states "Nothing but this repository's `src/` has to be installed", so the claim that VERTEX needs Simple Data Explorer on the system is unsupported. The replacement rests on this README's own sentence: the version history, the diff and the saved code review, "including approving, declining and commenting on a block", are available in Eclipse ADT and in VS Code through VERTEX. "has no blame yet" was a claim about VERTEX that this README does not carry and that was not re-verified against VERTEX; it is dropped rather than restated.
  • Simple Data Explorerdescription.what_it_solves → The table grid, the join builder and the pivot are also available outside SAP GUI, in Eclipse ADT and VS Code, through [VERTEX](artifact:ysichov-vertex).The README no longer says this repository holds the ADT resources VERTEX reads through: two commits on 2026-09-18 removed the ADT resources section and the construction-phase note, leaving only "The table grid with its select-options, the join builder and the pivot are available in Eclipse ADT and in VS Code through VERTEX". VERTEX's own README now states "Nothing but this repository's `src/` has to be installed" and that of the former `/zsde/` prefix "that hub is gone". The replacement keeps what this README still states and drops the dependency claim neither README supports. ADT.md is still in the repository and still describes the resources under `/sap/bc/adt/zsde/` in the present tense, which conflicts with both READMEs and is left for an editor.
  • VERTEXrequires → artifact:ysichov-simple-data-explorer, artifact:ysichov-ave, artifact:ysichov-ace, artifact:sap-adt, artifact:sap-adt-eclipsePointed at the ADT nodes that entered the graph on 2026-09-15, from the project's own documentation.
  • First entry seenDiscovered via Added by hand.
Profile1
For your agent