cap-java/cds-ai

Bridges CAP Java to SAP AI Core and adds AI-powered field recommendations to Fiori draft UIs, as two alpha Maven modules with mock fallbacks for local development.

Bridges CAP Java to SAP AI Core and adds AI-powered field recommendations to Fiori draft-enabled UIs, as two Maven modules under one repository. com.sap.cds:cds-feature-ai-core covers resource group management, deployment lifecycle, configuration CRUD and the prediction API against AI Core; com.sap.cds:cds-feature-recommendations builds on it to call the SAP RPT-1 foundation model for Fiori smart recommendations. com.sap.cds:cds-starter-ai is an empty aggregator jar that pulls in both modules with a single dependency. Without an AI Core service binding, both fall back to mock implementations for local development, and all three coordinates sit at 0.0.2-alpha on Maven Central. capire's plugin list states that the Java version of the AI plugin is currently in alpha. The Node.js counterpart is @cap-js/ai.

GitHub0 ★

Homepage

Docs

Facts

Last push2026-10-22LicenceApache-2.0

Where it sits

Lives in

CAP

Provides

LLM integration CAP

Flavors

Java

Optional

SAP AI Coremodel provider

Who is behind it

CAPmaintainer3 contributors

Before choosing this

Sources

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 3from LLM integrationCovered SAP materials or a covered CAP customer application are used as training data or to develop or refine an AI model or system.

§ 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.

Calling a model for inference is not automatically AI training. Section 3 matters when the covered material or application participates in training, model development, refinement or the text-and-data-mining uses it names.

SAP Developer License Agreement 3.2 CAP →

What it declares

Sources

Every artifact

Type: Package
Origin: By SAP
Runtime: Java
declared

As a package

Where it runs: does not say
declared, Where the library runs once installed: inside its host (loaded into the CAP application, installed into the ABAP system, loaded by the UI5 application), in a program of your own, or only at build time.
Distributed through: does not say
declared, How it is installed, as its documentation tells a user to get it.

For LLM integration

Models it reaches: SAP AI Core
stated by its maintainer“Bridges CAP Java to SAP AI Core - resource group management, deployment lifecycle, configuration CRUD, and prediction API” cap-java/cds-ai — README, 2026-10-15

Tasks this contributes to1Beta

LLM integration1

Run a CAP service's model calls with no SAP AI Core bindingA CAP project whose handlers call a language model starts, serves and answers on a laptop or in a pipeline where no SAP AI Core instance is bound — either from a mock, or from a model running locally.Covers, under conditionsmock in place of the service

What it does

The same shape on the Java side: the README states that without an AI Core binding the plugins fall back to mock implementations for local development, so both the AI Core bridge and the recommendations module answer with nothing bound.

Conditions

Local development: the README scopes the fallback to it; The answer is a mock implementation's, not a model's; capire's plugin list says the Java version of the AI plugin is currently in alpha

Remaining work

Add the Maven dependency and accept that both modules sit at 0.0.2-alpha on Maven Central, with capire calling the Java version alpha. The README says nothing about reaching a real model without a binding.

All options on the LLM integration page →

Connections3

Group by

NodeRelationBasis

Functional1

LLM integration

provides

stated

Calling a language model with tenant and credential handling solved

Technical2

SAP AI Core

connects to

stated

AI runtime on BTP with the Generative AI Hub

SAP AI Core

optionally needs

stated

AI runtime on BTP with the Generative AI Hub

Download

Where it sits in your app

Download

SAPnot SAP's, or the project's ownstated in the document

README

quoted from cap-java/cds-ai under Apache-2.0, read 2026-10-24

cap-java/cds-ai/README.mdthe maintainer’s wordsOn GitHub

SAP Cloud Application Programming Model - AI Plugins for Java

About this project

This repository contains a collection of AI plugins for CAP Java applications, leveraging SAP AI Core and the SAP-RPT-1 foundation model.

Plugins

Module	Description
`cds-feature-ai-core`	Bridges CAP Java to SAP AI Core - resource group management, deployment lifecycle, configuration CRUD, and prediction API
`cds-feature-recommendations`	AI-powered field recommendations for Fiori UIs in draft-enabled entities

Starter

See cds-starter-ai for the quickest setup.

Prerequisites

Java 17+
Maven 3.6.3+
CAP Java 5.0+
An SAP AI Core service binding (for production use)

The build is hermetic: cds-maven-plugin downloads its own Node runtime and cds-feature-ai-core/package.json pins @sap/cds-dk. A globally installed @sap/cds-dk is not required.

Without an AI Core binding the plugins fall back to mock implementations for local development.

Samples

A runnable CAP Java bookshop demonstrating all plugins together lives in samples/bookshop. It provides an AdminService showcasing recommendations on draft-enabled Books. See the sample's own instructions for how to run it.

Local Development

mvn clean install     # build all modules
mvn test              # run unit tests

For integration tests against a real AI Core instance:

cds bind ai-core -2 <your-ai-core-service-instance>
cds bind --exec mvn verify

See integration-tests/README.md for the full integration-test layout, including the multi-tenancy profile.

Support, Feedback, Contributing

This project is open to feature requests/suggestions, bug reports etc. via GitHub issues. Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our Contribution Guidelines.

Security / Disclosure

If you find any bug that may be a security problem, please follow our instructions at in our security policy on how to report it. Please do not create GitHub issues for security-related doubts or problems.

Code of Conduct

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its Code of Conduct at all times.

Licensing

Copyright 2026 SAP SE or an SAP affiliate company and cds-ai contributors. Please see our LICENSE for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available via the REUSE tool.

Read in full Fold Apache-2.0, read 2026-10-24

History

Latest

v0.0.2-alpha

Features 1, Changed 1

Notes

Added

Working sample application without cap-js dependency

Changed

Upgraded to CAP Java 5 and Spring Boot 4 (minimum CAP Java version is now 5)

All 2 releases

v0.0.1-alpha
Other 6
Notes
Initial release:
- AI Core service integration with automatic resource group management and deployment lifecycle (create, poll, reuse)
- SAP RPT-1 small model deployment and inference via cds-feature-recommendations
- @UI.Recommendations annotation to expose Fiori-compatible recommendations via OData
- Multi-tenancy support with tenant-scoped AI Core resource groups
- Configurable resource group for single-tenant scenarios (cds.ai.core.resourceGroup)
- Retry and backoff logic for transient AI Core errors

Fold On GitHub

Others providing22

Compare all 23 on the LLM integration page →

LLM integration

llm_clientABAP client with one interface to chat-completion LLM APIsfrom ABAP
abap-agent-runtimeABAP-native MCP endpoint that drives opted-in abap2UI5 appsfrom ABAP
abap_btocs_ollamaB-Tocs ABAP SDK plugin connecting to Ollama modelsfrom ABAP
SAP AI CoreAI runtime on BTP with the Generative AI Hubfrom BTP/BAIP
@cap-js/aiValue-help recommendations and SAP AI Core as a CAP servicefrom CAP
cap-llm-pluginGenerative AI in CAP with fields anonymised through SAP HANAfrom CAP
@geertjanklaps/cds-toon-ai-protocol-adapterProtocol adapter serving CAP data as TOON instead of JSONfrom CAP
abap-sdk-nwas-xABAP client library for IBM watsonx.ai APIsfrom ABAP
@jerome-benoit/sap-ai-providerVercel AI SDK provider for SAP AI Corefrom CAP
ui5-cap-ai-featuresCDS plugin and UI5 controls for AI text features via SAP AI Corefrom CAP
Microsoft AI SDK for SAPABAP library for calling Azure OpenAI and OpenAIfrom ABAP
zllmABAP framework for chaining and orchestrating LLM callsfrom ABAP
ABAP AI SDKSAP reuse library for calling large language models from ABAPfrom ABAP
@sap-ai-sdk/ai-apiAI Core control plane API surface of SAP's AI SDKfrom CAP
@sap-ai-sdk/coreShared internals of SAP's AI SDKfrom CAP
@sap-ai-sdk/foundation-modelsClient for foundation models via SAP AI Core and Generative AI Hubfrom CAP
@sap-ai-sdk/orchestrationOrchestration Service client for templating, grounding and maskingfrom CAP
@sap-ai-sdk/prompt-registryClient for prompts kept in SAP's prompt registryfrom CAP
@saptarishi/cds-plugin-llmCAP service kind putting eleven model providers behind one APIfrom CAP
@shahid.la/cds-db-nlquery-mcpMCP server answering plain-English questions against a CDS schemafrom CAP
@ui5/webcomponentsSAP's UI elements as standard custom elementsfrom UI5
abap-sdk-nwasAn ABAP client library for IBM Watson's Discovery, Language Translator, Natural Language Understanding, Speech to Text, Text to Speech and Assistant services, installed through abapGit.from ABAP

Details

Sources3

Added by handdiscovered herechecked 2026-09-19

github.com/cap-java/cds-aitree, pushes, contributors, CIchecked 2026-10-24

README.mdquoted, and what the entry declareschecked 2026-10-24

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance

runtimesjava

discovered viaAdded by hand

first seen in the atlas2026-09-19

ecosystem and domaincap, ai-and-agents

Flavors1

Java

“CAP Java 5.0+” — cap-java/cds-ai — READMEchecked 2026-09-19

Contributors3

Lisa Julia Nebel Samyuktha Prabhu Marvin L

From the repository’s contributor list, 2026-10-24.

History in the atlas5

2026-10-15model_access: SAP AI Core, scoped to the java flavor
2026-10-15capire's plugin list quoted beside them
2026-09-19Bridges CAP Java to SAP AI Core: resource group management, deployment lifecycle, configuration CRUD and the prediction API, through com.sap.cds:cds-feature-ai-core. com.sap.cds:cds-feature-recommendations builds on that same connection to call SAP RPT-1 for Fiori field recommendations, a narrower, UI-facing use of it.
2026-09-19The plugins required SAP AI Core; the connection says what they call it for, and when they do not.
2026-09-19First seen.

For your agent

Ref: artifact:cap-java-cds-ai
JSON: /artifacts/cap-java-cds-ai.json
MCP: Connecting an agent