BrowseABAP, RAP and ABAP Cloud
Everything in ABAP
4 of 656
Type
Domain
Origin
Signals
More: 4
Group by: Capability
EntryBySignalsLast activity
Agent access to ABAP codeSAP and community
ABAP Development Tools for VS CodeABAP Development Tools for VS CodeSAP's ABAP tools in VS Code: editing, debugging, ABAP Unit, ATC and transports for classes, CDS and RAP objects, over RFC to an on-premise or Private Cloud system and HTTP to a cloud one, with Joule's ADT MCP server and code completion behind an AI-unit licence.sap official, abap
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
Code reviewSAP and community
abapOpenReviewabapOpenReviewA code-review tool for SAP GUI that ties a checklist to a transport request: a transport whose diff contains code must be approved before it can be released.independent, abap
SAP GUI code review tied to transport release
No published releases; repository quiet for 31 months.
Editor supportSAP and community
ABAP Development Tools for VS CodeABAP Development Tools for VS CodeSAP's ABAP tools in VS Code: editing, debugging, ABAP Unit, ATC and transports for classes, CDS and RAP objects, over RFC to an on-premise or Private Cloud system and HTTP to a cloud one, with Joule's ADT MCP server and code completion behind an AI-unit licence.sap official, abap
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
SAP GUI screens and listsSAP and community
abeljohny/ZAPabeljohny/ZAPA tiny DSL included into an ABAP report that replaces a SELECT and an ALV call with a pair of macros, _select to read a table and _display to show the result as an ALV list.independent, abap
Macro DSL turning a one-line select into an ALV list
DocumentationSAP and community
abap-docsabap-docsSAP's ABAP Keyword Documentation scraped from help.sap.com and committed as Markdown in two libraries, Standard ABAP and ABAP Cloud, with keyword and category indexes for the MCP servers and LLMs it is generated for.independent, abap
ABAP Keyword Documentation as Markdown with indexes
The Markdown is a snapshot of whatever help.sap.com served when the pipeline last ran, and the Standard library is scraped from the `latest` index, so which release a page describes follows from the scrape date rather than from anything the corpus states. `package.json` states ISC and the repository carries no LICENSE file, so what the copied SAP documentation may be used for is not stated in it.