Everything in the atlas
Type
Domain
Origin
Signals
More: 4
Group by: Capability
Metadata viewer for SAP BW, SAP BPC and SAP BW/4HANA object models
Maps database tables and fields to the CDS views exposing them
Not on the [SAP BTP ABAP environment](artifact:btp-abap-environment) or another cloud ABAP system: the maintainer states the tool is not cloud ready, because the data sources and system tables it reads CDS metadata from are not released for cloud development. It is designed for SAP S/4HANA on-premise or private cloud, and the shipped Fiori application is configured for A4H and developer systems.
SAP skills for the Kiro IDE
Host-specific: outside Kiro the automatic context activation is the part that does not come with it, and what remains is prose you would have to wire in yourself. Breadth over depth by design — thirty-five skills across six product areas is an orientation layer, not a substitute for the focused sets in each.
Forty SAP development plugins for coding agents
GPL-3.0, which is a licence to read before vendoring any of it into something you ship. Forty plugins is also a lot of always-available surface — the ledger is there because breadth and verification pull in opposite directions, and it does not resolve that so much as report it.
Tool mapping BEx queries to the transport requests carrying them
Release and repository quiet for 50 months.
Generic customizing table and reader for ad hoc ABAP parameters
No published releases; repository quiet for 74 months.
Open SQL editor for ABAP with ALV output
Scripts running the ABAP Developer Edition in Docker
No published releases; repository quiet for 83 months.
Report searching ABAP source in methods, enhancements, DTPs and more
No published releases; repository quiet for 58 months.
ALV table view generated from a DDIC structure
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.