Everything in BTP/BAIP
Type: 3
Domain
Origin
Signals: Last 30 days
More
Group by: Capability
Distributed through
Form
Tutorials and use cases for SAP HANA database and analytics products
TechEd 2025 workshop on Just Ask natural-language questions
TechEd 2025 workshop on seamless planning for xP&A in BDC
Developer-centric command line for SAP HANA
Spring Boot apps messaging over SAP Event Mesh's Java JMS client
CAP and Fiori elements app for managing Cloud Integration datastores
Developer-centric command line for SAP HANA
Seventeen agent skills for ABAP development
Agent skill generating Java boilerplate for SAP GenAI Hub
Java and Kotlin only: JavaScript and TypeScript go to [aicore-sdk-js](artifact:sap-aicore-sdk-js), and nothing here covers Python. It writes code and stops there: the first rule hands a missing deployment to the AI Core console or an administrator before any code is generated, so a session without one gets code and no way to run it.
Agent skill generating TypeScript for SAP GenAI Hub on AI SDK v2
JavaScript and TypeScript only: Java goes to [aicore-sdk-java](artifact:sap-aicore-sdk-java), and a request for Python is declined with a pointer to SAP's own SDK documentation, since the repository has no Python skill. Creating, listing and deleting deployments is stated as outside it, and its code is v2 code, so a project still on version 1 of the SDK gets shapes that do not compile against what it has installed.
Four agent skills for SAP AI Core in SAP's AI Skills Library
Claude Code skills for BTP architecture diagrams in draw.io
The README tells you to fork before cloning, because Claude rewrites `references/` and `SKILL.md` in place as you use it, so a clone shared between people changes under all of them. Installing means `git` and `ln` on macOS or Linux and a symlink into `~/.claude/skills`. Fine positioning stays manual: the coordinates Claude writes can be rough apart from the centre coordinates of elements joined by a straight arrow and the containment relationships.
Agent skill for the Pipeline Concept in SAP Cloud Integration
It stops before the artifact: in the README's own words it does not generate or deploy complete iFlow artifacts, so building and shipping the integration flows themselves stays with a person and a tenant. Knowledge beside the work rather than a generator, and it reads nothing from a running tenant.
Agent skill mapping Fiori iOS UI Kit nodes in Figma to SwiftUI
Agent skill for Mobile Development Kit projects
Claude Code plugin with skills migrating HTML5 apps to appFront
CLI adding SAP developer knowledge and MCP servers to AI coding tools
Agent skill mapping the developers.sap.com content API
Eight skills for writing and operating SAP Automation Pilot content
It works against a tenant, through the REST API, with credentials in the environment — so these skills act rather than advise, and the review skill is a check on generated content rather than a substitute for one. Nothing here is useful without an Automation Pilot tenant to point at.
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.
CLI for Joule digital assistants and Joule Studio solutions
Two runnable industry AI agent projects built around Joule
CodeJam on code-based AI agents in Python or TypeScript on SAP BTP
CAP samples comparing SAP AI Core responses with content filtering
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
CAP samples generating email through SAP AI Core with anonymization
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
CAP samples embedding CSV rows into the SAP HANA Cloud vector store
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples running RAG similarity queries over SAP HANA Cloud vectors
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
Sample apps for SAP AI Core's Generative AI Hub capabilities
CAP samples calling SAP AI Core through the SAP Cloud SDK for AI
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
CodeJam on code-based AI agents in Python or TypeScript on SAP BTP
SQL examples for the HANA APL APIs plus scoring runtimes
Code examples for predictive and ML scenarios on SAP HANA
CAP samples using SAP AI Core's Prompt Registry for templates
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples filling a prompt template sent to SAP AI Core
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Sample implementations for AI-powered applications on SAP BTP
Java apps showing policy-based authorization with AMS on SAP BTP
Node.js apps showing policy-based authorization with AMS on SAP BTP
Terraform samples for the SAP BTP Administrator's Guide account model
Samples for the Terraform Provider for SAP BTP
Guide to the first setup tasks on a new SAP BTP enterprise account
TechEd 2024 session on Terraform setup of SAP Build services
TechEd 2025 hands-on on SAP BTP advanced administration tools
CAP and React dashboard for SAP AI Core capacity unit consumption
Never as the figure a billing decision rests on: the repository states this is not a replacement for the official billing documents, that the information it provides is purely indicative, and that it recommends verifying against the official BTP Cockpit usage reports. It is published as a sample or reference implementation and says it is not intended for production use without review, testing and hardening.
TechEd 2025 hands-on on SAP BTP advanced administration tools
MTA examples for SAP BTP, Cloud Foundry, one per deployment topic
Cloud Foundry routing samples: HTTP/2, gRPC, IP allow-lists
CLI to build, deploy, migrate and validate MDK projects
Specific to MDK metadata projects — nothing here builds or deploys a CAP service or a plain Fiori app. Closed-source, under SAP's own developer licence rather than a public repository.
Spring Boot reference implementing the SPFI V2 tenant lifecycle API
Not as the provider behind a live tenant estate: tenant state is kept in a file-based store for demonstration, and the README's own operations notes say a production implementation should use a reliable database so that state survives restarts.
Importable SAP Automation Pilot commands for operations scenarios
TechEd 2025 session on migrating SAP PO scenarios to Integration Suite
Guide to migrating XS Classic content to XS Advanced
Seventeen agent skills for ABAP development
Claude Code skills for BTP architecture diagrams in draw.io
The README tells you to fork before cloning, because Claude rewrites `references/` and `SKILL.md` in place as you use it, so a clone shared between people changes under all of them. Installing means `git` and `ln` on macOS or Linux and a symlink into `~/.claude/skills`. Fine positioning stays manual: the coordinates Claude writes can be rough apart from the centre coordinates of elements joined by a straight arrow and the containment relationships.
Sample projects referenced by the mobile development kit tutorials