Everything in the atlas
Type
Domain
Origin
Signals
More: 7
Group by: Capability
Spreadsheet upload into a CDS entity, parsed on the server
CAP service serving Northwind's external OData Products as its own
CAP service serving Northwind's external OData Products as its own
AWS's ABAP MCP server for Amazon Q Developer and Kiro
Written for Amazon Q Developer and Kiro, and the central deployment path is ECS Fargate — the further you are from AWS, the more of it is scaffolding you do not need. Python rather than the Node most of this group uses. Its README says the repository is no longer maintained and that the latest version of ABAP Accelerator is shared after registering with AWS for [Modernization Agents for SAP on AWS](https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS).
CAP service computing embeddings with HANA Cloud vector_embedding
CAP project built and deployed to Cloud Foundry by GitHub Actions
CAP project built and deployed to Cloud Foundry by GitHub Actions
CAP service in TypeScript using types from @cap-js/cds-typer
Common.DefaultValuesFunction pointed at a CAP service function
Mass edit enabled in a Fiori elements list report over CAP
Common.DefaultValuesFunction pointed at a CAP service function
Mass edit enabled in a Fiori elements list report over CAP
Singleton entity whose flags drive Fiori elements feature control
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.