Person
Jakub Filak
Capabilities
Contributes to
Agent access to your codeABAPAgent access to your codeLetting 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.Agent guidanceABAPAgent guidancePackaged knowledge you hand a coding agent so it gets a framework right unprompted — skills, rule files, instruction packs. Distinct from agent tooling, which is about building agentic features into your application, and from [agent access to your code](capability:agent-code-access), where the agent reads the real project instead of being handed a file about it.Browsing table dataABAPBrowsing table dataLooking 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.Change promotionABAPChange promotionMoving a change through the environments of a landscape, from development through test to production, and knowing which change has reached which environment. A [CI/CD pipeline](capability:ci-cd) builds and tests on each source change, [deployment](capability:deployment) puts a build onto its runtime, and getting source into git is [source control](capability:abap-source-control).Clean code conventionsABAPClean code conventionsThe naming, structure and language-subset conventions that make source code readable across a team — and the question of which of them a checker can enforce.Code formattingABAPCode formattingMaking source match one layout — indentation, keyword case, the shape of a statement block — by rewriting it rather than by reporting on it. Distinct from [static analysis](capability:abap-static-analysis), which says what is wrong and leaves the source where it is.DebuggingABAPDebuggingSeeing 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.Editor supportABAPEditor supportWorking in source code with the editor helping rather than treating it as text — completion, go-to-definition, inline errors, refactoring and preview.Searching code in a systemABAPSearching code in a systemFinding where a string, pattern or name occurs across source code and development objects held in a system. Raising findings against rules is [static analysis](capability:abap-static-analysis); reading an individual change is [code review](capability:abap-code-review).Source controlABAPSource controlKeeping source code and development objects in version control, comparing their revisions, and moving them between development environments. Managed delivery of changes belongs to [transport management](capability:change-promotion).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.
Entries
Group by
EntrySignals
Contributes to
ABAP remote filesystemABAP remote filesystemA Visual Studio Code extension that opens an ABAP system over ADT as an editable filesystem and exposes system tools to GitHub Copilot and external MCP clients.independent, abap
VS Code extension editing ABAP systems over ADT as a filesystem
abapGitabapGitA Git client written in ABAP that runs inside the system, so objects are cloned, pulled and pushed without leaving it; with no package manager in ABAP, a cloned repository is how code is distributed.community org, abap
Git client written in ABAP that runs inside the system
Clean ABAPClean ABAPSAP's open, versioned style guide for ABAP: the answer to how a piece of ABAP should be written, an agreement a team adopts rather than anything to install.sap official, abap
Open, versioned style guide for ABAP
SAP-samples/abap-alv-google-upload-sheetSAP-samples/abap-alv-google-upload-sheetSample code that exports SAP GUI ALV grid data directly to Google Drive, where it appears in Google Sheets, with the OAuth, endpoint and ALV configuration around it described in SAP's own guide.sap official, abap
Not where SAP's own Google Workspace integration already applies: the README opens by announcing a native integration between Google Workspace and [SAP S/4HANA](external:sap-s4hana), whose first set of features is included in SAP S/4HANA Cloud 2208 and SAP S/4HANA 2022 and needs an additional licence for the SAP Document Management Service. Not where end users cannot each hold a regular Google account, since there is no way to use an enterprise account or to log on to Google Drive through single sign-on, and not where the redirect URL Google calls cannot reach a public top-level domain server. No SAP standard support is provided for it.
Sample exporting SAP GUI ALV grid data to Google Drive
Details
Profile
For your agent
- Ref
actor:filak-sap- JSON
- /actors/filak-sap.json
- MCP
- Connecting an agent