Grounding Joule on Enterprise Data
As of 2026-10-10
Grounding Joule is a routing decision across four SAP-shipped routes: delivered Joule capabilities (activate and govern), document grounding in the generative AI hub (Pipeline, Vector and Retrieval APIs over SharePoint, S3 or SFTP), structured grounding through tools (SAP Build actions, OData/consumption APIs, MCP servers — the backend enforces authorisations) and custom RAG or pro-code A2A agents on SAP AI Core orchestration and SAP HANA Cloud. Since Sapphire 2026, SAP Knowledge Graph sits at the core of the SAP Business AI Platform and Joule Studio agents (GA December 2025) speak MCP and A2A. The release gate is a two-user permission test with zero leakage.
What you will learn
- Assign any business question to one of the four SAP grounding routes (delivered Joule, document grounding, tool-based structured grounding, custom RAG/A2A) and justify the choice in one sentence.
- Configure document grounding end to end in the generative AI hub: extended plan, resource group label, generic secret, pipeline, Retrieval API test and orchestration grounding module.
- Demonstrate permission enforcement per route with two test users and explain where enforcement is not automatic (technical users, unsegmented document indexes).
- Build a 30-question golden set and report retrieval hit rate, citation rate, freshness and permission leakage before a pilot.
- Write the operating model for a grounded assistant: repository owners, re-sync cadence, deletion procedure, AI-unit consumption tracking and audit logging.
Grounding is what turns Joule from a fluent assistant into an enterprise assistant. A language model that has not been grounded answers a question about last quarter's supplier spend with a plausible sentence, because predicting plausible text is what it was trained to do. A grounded Joule answer is different in kind: the figure comes from a governed SAP system, the policy excerpt comes from an approved document repository, the person asking only sees what their authorisations allow, and every claim can be traced back to its source. This module teaches the grounding routes SAP actually ships as of September 2026, how each one is configured, and how a senior consultant chooses between them, tests them and runs them after go-live.
What you will be able to do
By the end of this module you should be able to:
Prerequisites
- Hands-on experience with an SAP BTP subaccount (entitlements, destinations, roles)
- Review core concepts first: C027, C024, C008
- Recommended: module M053 (SAP AI Core & AI Launchpad)
Outcomes
- Explain to a sponsor why grounding, not model choice, decides whether a Joule answer can be trusted and audited.
- Set up and test a document-grounding pipeline and wire it into an orchestration configuration with masking and content filtering.
- Design principal propagation or repository segmentation so that no user receives content they are not entitled to.
- Run and document a two-user permission test and a golden-set evaluation as formal go-live criteria.
- Hand over a runbook covering re-sync, deletion, ownership and consumption monitoring.
Full module available to members. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the code blocks · the knowledge check · the diagrams.