SAP Business Data Cloud Intelligent Applications — Deploy and Extend
As of 2026-09-25
For consultants who need to scope, deploy or extend an SAP Business Data Cloud Intelligent Application at a practitioner level. Covers what distinguishes an Intelligent Application from a data product, the five capabilities SAP announced (People, Cloud ERP, Customer, Finance, Spend Intelligence) with a caution to verify current GA status, the real prerequisite of already-provisioned data products behind SAP's quoted four-to-six-week activation window, the three places extension work concentrates (data products, business rules, the Joule narrative layer), how to validate a narrative's attribution claim against underlying data and the Knowledge Graph, Data Access Controls at the application level, and Capacity Unit sizing. Closes with the BDC certification landscape and three practitioner exercises.
What you will learn
- Distinguish a Data Product from an Intelligent Application and explain how SAP composes the second from several of the first
- Name the Intelligent Applications SAP has announced or shipped (People, Cloud ERP, Customer, Finance, Spend Intelligence) and treat GA status as tenant-verifiable, not assumed
- Explain why an activation timeline depends on whether underlying data products are already provisioned and agent-ready
- Identify the three places extension work concentrates: additional data products, business rules/thresholds, and the Joule narrative layer
- Validate an Intelligent Application's narrative output against its underlying data products and Knowledge Graph relationships rather than accepting it at face value
- Account for Data Access Controls and Capacity Unit sizing when scoping an Intelligent Application activation
Who this is for. Your client has heard the phrase "Intelligent Application" in a Sapphire recap or a partner pitch and wants to know what it actually is, what it takes to deploy one, and whether it can be extended for their specific process. This module is a practitioner's answer: not a marketing tour, but what an Intelligent Application is built from, the real prerequisite that decides whether an activation takes weeks or quarters, and where a consultant's extension work actually happens.
1. What an Intelligent Application actually is
SAP defines Intelligent Applications as "prebuilt, composable applications that seamlessly integrate trusted data products, AI capabilities, and business simulations" — designed to "transcend traditional analytics by automating and orchestrating work across both analytical and transactional workflows." The distinction to hold onto: a Data Product (M343 covers this in depth) is a governed, single business object — invoices, headcount, deliveries. An Intelligent Application is built on top of several data products, stitched together with AI and simulation logic into a named, executive-facing deliverable. SAP's own language is explicit that data products are the foundation and Intelligent Applications the thing built from them — not two names for the same layer.
Prerequisites
- M343 (SAP Business Data Cloud Data Products for AI Agents) or equivalent understanding of data products and their governance metadata
- Working familiarity with SAP Business Data Cloud's Catalog and knowledge-core positioning (C009, C263)
- Basic understanding of Joule as a natural-language interface (C024)
Outcomes
- Decompose a named Intelligent Application into the data products it joins and assess each one's readiness.
- Write an honest two-scenario activation timeline distinguishing provisioned-data-product from not-yet-provisioned cases.
- Propose a realistic extension (data product, threshold, or narrative) and name the governance and Knowledge Graph work it requires.
- Validate a narrative's attribution claim against the Knowledge Graph rather than accepting fluent language as proof.
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.