Document grounding
On this door the question is not how to embed your own records but which document store to point the service at. 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 connects a repository and answers from it, and SAP AI LaunchpadSAP AI LaunchpadThe SaaS front end over SAP AI Core on BTP: a Model Library, Grounding Management for document pipelines, Workspaces that connect AI runtimes, and ML Operations for the lifecycle of a scenario.sap official, btp carries the Grounding Management app for the pipelines.
Overview
Document Grounding, a managed service under the Generative AI Hub 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: a connector to Amazon S3, SharePoint, SAP Document Management Service, SAP Build Work Zone or an SFTP server, and the service does ingestion, chunking, embedding and retrieval itself; a Vector API takes pre-chunked, pre-embedded data for the cases that want that control.
Not covered: At documents in a connected repository. Records in your own database, the CDS entities this capability is named for, are not a grounding source; for those the vector column in SAP HANA CloudSAP HANA CloudThe managed database under most of this: CAP's default target, the store Datasphere and Analytics Cloud sit on, and a service with plans and components.sap official, btp and the pipeline hand-written on the CAP door are still the route.
Community code works on the side the service leaves open: sap-knowledge-pipelinesap-knowledge-pipelineA Python library that reads selected records out of an SAP OData service or an SAP HANA SELECT and renders them as chunked documents, each carrying the entity set and business key it came from.independent, btp by Yassin BahriYassin Bahrimaintains 2 entries, contributed to 2 entries turns records from an OData service or a HANA SELECT into chunked documents that carry the business key they came from.
Artifacts
Content
Show 3 more
Show 2 more
Show 6 more
Seen working
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.
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.
Details
Coverage
Designs that place it
For your agent
- Ref
capability:retrieval-augmented-generation- JSON
- /capabilities/retrieval-augmented-generation.json
- MCP
- Connecting an agent