Everything in the atlas
Type
Domain
Origin
Signals
More: 5
Group by: Capability
Eclipse plug-in turning JSON or XML into ABAP types and DDIC objects
On an [SAP BTP ABAP environment](artifact:btp-abap-environment) system only the generated code is left: DDIC creation is not supported on ABAP Cloud, because classic DDIC object creation over REST is not available there. Create DDIC is also disabled where ADT is not installed in the same Eclipse, and Insert into Editor then works with any editor implementing `ITextEditor` instead of the ABAP one.
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.
ABAP, Python and C code for similarity search over field descriptions
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
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
SAP's ABAP tools in VS Code for editing, debugging, ATC and transports
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.