Build AI agents on SAP and non-SAP data and context in an open lakehouse
SAP Business Data CloudSAP Business Data CloudSAP's umbrella over the data estate: installed intelligent content and data products, a governed catalog they are published through, and a path out to SAP Databricks.sap official, btp as an open lakehouse: the abstract states that it holds third-party data beside SAP data and its semantic context on Apache Iceberg and Apache Polaris, that architects and developers publish governed data products and ontologies from it, which is the cataloguing and lineageCataloguing and lineageFinding what data exists across the estate and what it promises — catalogs and data products, the contract a consumer can rely on, where a field came from, and what a column actually contains once you profile it. The question asked before modelling starts and again when somebody asks where a number came from.SAP and community, unassessed concern, and that agents built on them for SAP JouleSAP JouleSAP's unified AI engagement layer across SAP applications: Joule Work is where a user expresses intent, Joule Assistants coordinate agents across business functions, and Joule Agents carry out the tasks, provisioned on BTP as a formation against SAP Cloud Identity Services.sap official, btp can be reached from outside over A2A. How a data product is defined, and what the ontology layer adds to it, is not in the abstract. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Rahim Bhojani and Sivakumar N, written here from SAP's abstract; the recording is not yet published.
Where it sits
Properties
About this work
Details
Graph
Source
History
- Entered the atlasDiscovered via SAP TechEd — session catalogue · build/teched.
For your agent
- Ref
content:teched-2026-xp113- JSON
- /content/teched-2026-xp113.json
- MCP
- Connecting an agent