Everything in the atlas
Type
Domain
Origin
Signals
More: 5
Group by: Capability
ABAP code and slides from a talk on building SAP Gateway services
Task tracker on a BOPF-backed CDS view with a Fiori list report
Practice repository for the unmanaged RAP scenario
Practice repository for managed RAP with unmanaged save
CAP service serving Northwind's external OData Products as its own
MTA deploying CAP, HDI container and a Fiori elements app
CAP service serving Northwind's external OData Products as its own
LibreChat fork with four SAP MCP servers preconfigured
Starter repository for an abap2UI5 app with CI and agent setup
ABAP report sending a prompt to a local LLM via an SM59 destination
CAP service computing embeddings with HANA Cloud vector_embedding
Authenticating a CAP service against Azure AD B2C
CAP project built and deployed to Cloud Foundry by GitHub Actions
MTA deploying CAP, HDI container and a Fiori elements app
CAP project built and deployed to Cloud Foundry by GitHub Actions
Starter repository for an abap2UI5 app with CI and agent setup
CAP project simulating S/4HANA Private Edition OData APIs locally
ATC check classes accompanying DSAG's ATC best-practice guide
CAP service in TypeScript using types from @cap-js/cds-typer
Starter repository for an abap2UI5 app with CI and agent setup
ABAP project for learning the ABAP Unit Test Framework
MTA deploying CAP, HDI container and a Fiori elements app
Template repository for own UI5 artefacts served to abap2UI5
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
Demo programs for the classic CL_GUI_ALV_GRID control
Template for ABAP applications with an HTML UI
The declared repository is archived.
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.