SAP BTP AI Best Practice Demo - Prompt Registry - CAP
A CAP backend-sample and fullstack-sample that create, use and delete a template in SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp's Prompt Registry instead of embedding the prompt in code.
createPromptTemplate registers a named askCapitalOfCountry template under an ai-best-practices scenario, askCapitalOfCountry answers from that template, and deletePromptTemplate removes it again: three CDS actions split across a prompt-registry and an orchestration service, implemented, the README says, with the SAP AI SDK, and @sap-ai-sdk/prompt-registry@sap-ai-sdk/prompt-registryA package for keeping prompts in SAP's prompt registry rather than in the codebase, so changing a prompt is not a deployment.sap official, cap and @sap-ai-sdk/orchestration@sap-ai-sdk/orchestrationThe Orchestration Service client of SAP's AI SDK, which applies templating, grounding, filtering and masking around a model call rather than in the application.sap official, cap are in the fullstack-sample's dependencies. The fullstack-sample pairs the same services with a UI5 app under app/ask-capital, and its README notes the create step has to run first or the app has no template to query. Both bind to a SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp service instance with cds bind.
Facts
Where it sits
Who is behind it
In the atlas: maintains 222@SAP-samplesmaintainerLuís MarquesContributes to this
In the atlas: contributes to 8@luismarques-io1 contributor
Before choosing this
Conditions
PracticalFunctional boundary
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.
What it declares
Every artifact
- Type
- Sample
- Origin
- By SAP
- Use as
- A reference
- Runtime
- Node.js
As a sample
- Form
- A reference application
Connections
Prompt templates stored and versioned apart from the code
AI runtime on BTP with the Generative AI Hub
AI runtime on BTP with the Generative AI Hub
Download
README
quoted from SAP-samples/sap-btp-ai-best-practices under Apache-2.0, readCAP Implementations for Prompt Registry
This directory contains Cloud Application Programming (CAP) model implementations that demonstrate best practices for prompt registry with AI models through SAP BTP services.
Available Samples
- backend-sample: Standalone CAP backend service implementation
- fullstack-sample: Complete CAP application with UI5 frontend
Overview
These samples showcase how to:
- Connect to generative AI services from CAP applications
- Structure service layers for AI orchestration
- Implement proper error handling
- Deploy applications to SAP BTP
Getting Started
Each subdirectory contains a comprehensive README.md with detailed setup instructions, deployment guides, and usage examples.
Details
Sources
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
Flavors
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:sap-samples-btp-ai-bp-prompt-registry-cap- JSON
- /artifacts/sap-samples-btp-ai-bp-prompt-registry-cap.json
- MCP
- Connecting an agent