Everything in the atlas
Type
Domain
Origin
Signals
More: 3
Group by: Capability
Metadata viewer for SAP BW, SAP BPC and SAP BW/4HANA object models
Read-only MCP server for exploring SAP Datasphere
Business Source License 1.1, which is source-available rather than open source: reading and evaluating are fine, and production use is restricted until the licence's change date. That is a procurement question, not a technical one, and it is the thing to settle first. Read-only also means read-only — no modelling, no loads.
MCP tooling for SAP Business Data Cloud discovery and contracts
Business Source License 1.1: source-available, with production use restricted until the change date — settle that before anything technical. And the governed execution path in v0.2 does act on data, which is a different grant from the discovery the v0.1 baseline offered.
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.
UI5 component adding a spreadsheet upload dialog to Fiori apps
RFC client for Node.js and TypeScript without the NW RFC SDK
BUSL-1.1 rather than node-rfc's Apache-2.0, so a product you distribute has to be read against the licence and its Additional Use Grant first, and the source is closed: the GitHub repository is the issue tracker and the documentation, nothing else. `RfcServerOptions.bgRfcHandlers` raises instead of accepting handlers, so a server receiving inbound bgRFC units is outside what this does. An ABAP `MESSAGE`-raised failure still arrives with its T100 template rather than the rendered sentence, and the dump name is not reported as `key` for that case.
Read-only MCP server for exploring SAP Datasphere
Business Source License 1.1, which is source-available rather than open source: reading and evaluating are fine, and production use is restricted until the licence's change date. That is a procurement question, not a technical one, and it is the thing to settle first. Read-only also means read-only — no modelling, no loads.
MCP tooling for SAP Business Data Cloud discovery and contracts
Business Source License 1.1: source-available, with production use restricted until the change date — settle that before anything technical. And the governed execution path in v0.2 does act on data, which is a different grant from the discovery the v0.1 baseline offered.
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.
CLI converting UI5 i18n properties files to Excel and back
Release and repository quiet for 39 months.
ALV table view generated from a DDIC structure