SAP Business Data Cloud: A Decision Guide to Cost, Datasphere, AI and Adoption

Treat SAP BDC as a data-product contract, not a tool purchase

Altivate | Published 16 October 2026

1. What is SAP Business Data Cloud (SAP BDC)?

SAP Business Data Cloud (SAP BDC) is SAP’s managed software-as-a-service offering for bringing SAP and third-party data together, governing it and using it for analytics, planning and AI. It combines SAP Datasphere, SAP Analytics Cloud (SAC), SAP Business Warehouse (BW), SAP Databricks and BDC Connect under one capacity-based contract. Its central idea is the data product: a governed, documented dataset with business meaning, which SAP supplies for its own applications and which you can create from your own data. SAP announced it on 13 February 2025 and now describes it as the data foundation of its Business AI platform. SAP also names SAP HANA Cloud and SAP Master Data Governance as core components; confirm scope and region before contracting (sections 2 and 9).

SAP BDC vs SAP Datasphere: what is the difference?

SAP Datasphere is not being replaced. It is one component inside BDC, not a synonym for it, and existing tenants are preserved under BDC; SAP’s 1 July 2025 announcement changed how it is bought (section 3).

For how Datasphere works day to day, see our SAP Datasphere page.

What are intelligent applications and SAP-managed data products? SAP’s BDC FAQ describes intelligent applications as ready to consume: installing one sets up the data, analytics and applications, built on pre-built, SAP-managed data products that you can also reuse for your own insights and AI. Each requires its source SAP application and BDC core (section 4); examples include Cloud ERP Intelligence Private, Spend Intelligence and Consumer Products Intelligence (section 2). Data products you build yourself in Datasphere are separate.

The five questions this guide answers

1. Which decisions, reports or agents need governed SAP data?
2. What does BDC absorb in your current estate, and on what clock?
3. How is capacity metered, and which contract terms decide your cost?
4. How does your existing lakehouse or analytics platform connect?
5. Where may each component run, given Saudi and UAE obligations?

Statuses are dated 16 October 2026; put the questions to SAP in writing.

2. SAP BDC availability: generally available, early access and roadmap

Two things are easy to confuse. SAP Databricks is Databricks hosted inside BDC and bought from SAP. BDC Connect links BDC to a lakehouse or warehouse you already own and contract for yourself. Their dates and regions differ.

For how SAP’s wider AI portfolio is labelled, see SAP AI Needs a Status Ledger; for Altivate’s view, the SAP Business Data Cloud page.

3. Datasphere, SAC and BW: what BDC absorbs and the BW maintenance clock

“Replace” overstates it. For Datasphere and SAC the change is commercial; for BW, the route depends on your release.

Datasphere and SAC. SAP’s announcement of 1 July 2025 says both remain strategic but are offered through BDC: “after December 31, 2025, these services will not be available for renewal” on BTP Enterprise Agreement (BTPEA), Cloud Platform Enterprise Agreement (CPEA) and pay-as-you-go contracts. Current terms run to their end, credits bought before 1 January 2026 stay usable, and existing tenants are preserved under BDC with no technical migration. SAP’s BDC FAQ (an SAP Community post updated 4 December 2025, not contract text) says that happens by rewiring the tenant in place: SAP rewires SAP-managed tenants on the contract start or renewal date; customers must initiate it for customer-managed (BTP-based) tenants after buying a BDC subscription. On BTP credits, compare entitlements with a BDC proposal at your next renewal.

Business Warehouse. BDC offers BW as a capacity service. SAP’s reference architecture (updated 16 September 2025) describes two moves. Lift moves BW 7.5 to BW private cloud edition inside BDC, or BW/4HANA to its private cloud edition. Shift uses the Data Product Generator to copy data from existing InfoProviders into the Datasphere object store, from where it can be published as a data product and shared with SAP Databricks. Starting releases: BW 7.5 on SAP HANA at SPS24 or higher, and BW/4HANA 2021 at SPS04 or higher (older BW/4HANA releases upgrade to 2023).

The order matters for an on-premise BW. SAP’s learning material calls the lift a prerequisite for using BW within BDC, and the service description guide (§4.8) licenses the Data Product Generator under a subscription to SAP BW Capacity Services.

The BW clock, from SAP’s own statements:

The BDC service description guide (version 9, 2026) sets contract dates for the BW services sold inside BDC, and they differ by service:

• §5.5.1, 18 NetWeaver-based services (BW NetWeaver Cloud private edition systems, BI Java and the Business Planning and Consolidation (BPC) for NetWeaver Cloud editions): no mainstream maintenance beyond 31 December 2027 “or sooner”, and subscriptions cannot extend beyond 31 December 2030.
• §5.5.2, the “modernization option” services: supported from 1 January 2031, with subscriptions ending no later than 31 December 2033. SAP’s announcement (10 September 2026) says the option is available to order from September 2026, only for BW 7.5 systems running inside BDC, for at least 12 months, and that the Java stack is not available after 31 December 2030.

None of these BDC dates apply to BW/4HANA, which is not listed in §5.5. Confirm the schedule for your exact service and release.

4. SAP BDC pricing: capacity units and contract questions

How the model works

SAP’s April 2026 deck and the service description guide describe BDC core as a subscription in Capacity Units (CU), spent across the underlying services at each one’s own rate. Per the deck, core covers Datasphere, SAC, BW, the MDG extra stack, HANA Cloud, BDC Connect and SAP Databricks.

On top sit intelligent packages for specific applications. Per the deck, a package uses the metric of its source SAP application, requires both that application and BDC core, and auto-attaches a set quantity of core CUs. The deck also says core capacity must be sold with at least one intelligent application (as of 16 April 2026).

For customer-managed use cases, the same deck presents Customer-Managed Data Products as an “Intelligent Package Alternative”: any enterprise data source, on a flat-fee metric. Guide §6.3 describes that flat fee and, subject to a condition in SAP’s terms, an increase of 1,000 core CUs a month for use on the core capacity services. Ask SAP whether this route fits your use case and meets the intelligent-application requirement.

The link to RISE is contractual. Cloud ERP Intelligence Private requires a RISE with SAP S/4HANA Cloud Private Edition or SAP Cloud ERP Private subscription, with at least as many Full Use Equivalents (FUEs) as the ERP subscription (guide §6.1). That makes BDC part of the RISE conversation; it does not make it a purchase every RISE customer needs. See RISE with SAP.

Published CU rates

The Datasphere, SAC and SAP Databricks rates come from SAP’s 16 April 2026 deck; the connector rates and the Data Sharing Fee are from the service guide (version 9, September 2026), Attachment A Table 3. Confirm the rates in your order form:

A promotional SAP Databricks rate, about 60% of standard, ended on 30 April 2026. Any quote built on it needs re-pricing.

A worked example

Illustrative arithmetic, not a quote, using the published rates above for one month:

That is about 3,260 CU a month before Datasphere compute and storage, SAP Databricks, any minimum attach and any package. In this low-transfer example the connector lines are about 0.74% of the total. That does not describe other estates: at the same rate, 20,000 GB of inter-region transfer would cost 3,700 CU, more than the user and tenant lines here. To turn CU into money, multiply by the CU price in your order form. SAP’s public BDC pricing page shows no CU price (checked 16 October 2026); third-party currency figures are estimates. For BigQuery, budget the Enterprise Plus edition Google requires (section 6) separately from SAP CUs.

Contract questions to put to SAP

• Which services and CU rates are in the order form, and are they fixed for the term?
• For the services guide §2.3.1 lists (Datasphere, BDC Connect, SAP Databricks, Data Composer, HANA Cloud and Reltio), usage is measured at its highest point in the month. SAC counts users per instance (§3.1), and the BW services are not in that list. Capacity Units are not prorated for partial months, and unused units do not carry over (§2.3.2, §2.3.5). What does a peak month cost, can capacity be raised mid-term, and how is each service in your quote measured?
• What is the minimum core attach? The April deck cites 640 CU sized on a 25-user SAC tenant; the guide describes a Customer-Managed Data Products flat fee that entitles 1,000 CU a month. Ask SAP to reconcile the two.
• Where do your integrations sit against Datasphere’s OData and OpenSQL limits, above which SAP may charge more?
• Datasphere capacity may not reach a third-party database licensed under an SAP runtime licence except through application-level APIs. Does any of your landscape do that?
• For your own Snowflake, how is the Data Sharing Fee forecast before go-live?
• Which components are EU Access eligible, and does that matter to your residency position?
• Is there a usage metric for Joule or agents on BDC data? Neither the guide nor the April deck names one for BDC core; the guide defines an “Agent Execution” and prices Reltio AgentFlow per action.

5. How SAP Business Data Cloud supports AI and Joule agents

In short, BDC supports AI by giving Joule, agents and SAP Databricks governed data products that carry business meaning and access rules; the status of each piece is listed below.

An agent that answers a business question needs more than rows. It needs to know what a field means, how entities relate and who may see what. SAP’s design supplies this in three layers. Data products carry the data with its business definitions and access rules. SAP describes the SAP Knowledge Graph as mapping business entities, processes and relationships so an agent can find the right product. Joule and Joule Agents consume both. The status of each piece differs:

• Joule in Datasphere is generally available: in chat it answers product questions, navigates the platform and executes supported tasks (Q1 2026 release highlights).
• Joule insights are, per SAP, powered by governed data products in BDC and the Knowledge Graph (Sapphire, May 2026).
• Joule Agents in BDC are announced: data product search and creation, planning and analytical modelling, surfacing business insights and SAC story generation. No general-availability dates.
• Reltio adds a master-data “golden record” for Joule Agents, with Model Context Protocol (MCP) support. SAP Reltio in BDC is generally available (section 2).
• At SAP Connect (6 October 2026) SAP added Joule’s Agent2Agent reach to third-party agents, but no BDC dates.

Illustrative use case, not a packaged outcome: a demand-planning team reads an authorised SAP sales-history data product in SAP Databricks without replication, adds external demand signals, builds an automated time-series forecast and publishes the predictions back into BDC as a custom data product. The pilot compares forecast accuracy and preparation effort with the current process; the team still owns model validation, permissions and the decision. Confirm feature and region availability first.

Agents inherit the quality of the data products beneath them: a product with no owner, agreed definition or tested access rule produces an agent that is fast and unreliable. Access rules do not travel on their own: SAP says source-system authorizations are not imported into Datasphere through BDC, and Google notes that SAP Delta Sharing tables in BigQuery lack fine-grained access control. See also enterprise AI agent readiness and choosing between RAG, tools, workflows and agents.

6. BDC Connect: Databricks, Snowflake, BigQuery and Fabric

BDC Connect shares SAP data products with other platforms, and their data back, without a separately maintained ETL replica. “Zero-copy” does not mean nothing moves or persists: transfer and requests are metered (section 4), SAP permits the consuming system to cache accessed data, and BigQuery caches cross-cloud query data by default, at rest in the Google Cloud region of the catalog or connection. Include consumer-side caches in your placement design (section 9).

If you already run a lakehouse, decide which platform owns, and pays to serve, each data product.

7. Adopt, pilot or wait: a posture for your situation

Each situation has a default posture and the evidence that would change it. These are Altivate’s judgement from the facts above, not SAP guidance. Apply them per proposed data product and consumer, not per estate: a failed dependency blocks that use case only.

8. The data-product readiness test

A data product, for this purpose, is a governed, documented dataset with an owner, a defined meaning, a quality standard and an access rule, offered to named consumers. Rate evidence, not confidence, using the same discipline as the digital maturity assessment.

Before authorising a pilot. Tick only what you can show:

• ☐ A named owner who can approve changes and answer for quality.
• ☐ A named consumer: a report, a decision or an agent, with a measure of its value.
• ☐ A written definition of each business term, agreed by the consuming functions.
• ☐ A measured quality baseline for the source data from the last 90 days.
• ☐ A classification of the data under your organisation’s classification policy and any applicable regulatory scheme, approved before design.
• ☐ An approved decision on where it may be stored and processed, written down per component.
• ☐ A documented comparison with the current approach: baseline performance, target improvement, implementation, operating and parallel-running costs, and when the existing approach stays preferable.
• ☐ A test plan for quality, access and, for any agent, evaluation.
• ☐ For a paid pilot: a capacity estimate with a peak scenario, an approved spending ceiling, a named monitoring owner, and a dated exit test with pass/fail criteria and a stop or removal procedure.

During the pilot. Use approved test data until the access controls pass:

• ☐ The resulting data product’s quality, measured against its standard.
• ☐ Access rules by role, tested by someone who is not the owner, across Datasphere, the sharing connection and the consuming application, including users who must be denied.

Before production use or expansion. Every check above passes, plus, for any agent that uses the product, an evaluation set and a named owner for wrong answers.

Remediation priorities. These do not block a pilot, but they order the work before scale:

• ☐ Lineage from source to product that someone has actually traced.
• ☐ A plan for the legacy report or extract it replaces.

No score overrides a failed gate, and products are not averaged: one that fails a gate and feeds a payment decision blocks that decision.

Clear the pre-pilot checks before the contract, because the order form fixes capacity and minimum attach.

9. SAP Business Data Cloud in Saudi Arabia and the UAE

Placement is per component. SAP’s Data Center Availability page for BDC lists components by region. SAP’s FAQ (last updated 13 July 2026) adds that Datasphere, SAC, BDC Connect and the BDC Cockpit must be in the same hyperscaler region, while SAP Databricks and BW in BDC may sit in a different one.

SAP’s separate Reltio data-centre page, for sites without BDC, lists no Saudi or UAE site either.

SA30’s “Regulated Customers” label is SAP’s, not a regulatory status. A listing establishes availability, not compliance or a residency contract: confirm dependent services, support access, consumer-side caches, contractual residency terms and inference location separately. As SAP AI Needs a Status Ledger argues, a data centre in Dammam does not tell you where inference runs.

Questions to put to counsel, SAP and your regulator

These are questions, not legal advice. Confirm each with qualified counsel and the competent authority.

Saudi Arabia

• Which classification applies, under which authority’s scheme? The Cloud Cybersecurity Controls (CCC-2:2024) of the National Cybersecurity Authority (NCA) apply to cloud service providers serving in-scope customers, and to Saudi government entities (inside or outside the Kingdom) and private-sector entities that own, operate or host critical national infrastructure and use or plan to use cloud services; NCA strongly encourages other entities in the Kingdom to adopt them. The edition removed two sub-controls requiring in-Kingdom cloud services and transferred localisation to the National Data Management Office at the Saudi Data and AI Authority (SDAIA). What has your counsel confirmed with that office?
• If you are in that scope, does SA30 cover every component your design needs, and what replaces HANA Cloud or SAP Databricks where it does not?
• Under the Personal Data Protection Law (Royal Decree M/19, amended by M/148) and SDAIA’s implementing rules on transfers outside the Kingdom, what lawful basis and assessment will you rely on for any component outside the Kingdom? Ask counsel for their current text.
• If the Saudi Central Bank (SAMA) supervises you, its Cyber Security Framework (3.4.3, Cloud Computing) says that in principle only cloud services located in Saudi Arabia should be used, with explicit SAMA approval for use outside (control 4.b.1), and SAMA approval before using cloud services or signing with the provider (4.a.2). The framework is written for hybrid and public cloud and notes that it does not apply to private (internal) cloud; confirm with counsel and SAMA how a vendor-operated service such as BDC is classified. Has approval been sought for each component?

United Arab Emirates

This list covers federal law and Central Bank rules. Free zones such as the Dubai International Financial Centre (DIFC) (DIFC Law No. 5 of 2020) and Abu Dhabi Global Market (ADGM) have their own data protection regimes, and sector rules apply in areas such as health; ask counsel which apply to you.

• The federal Personal Data Protection Law (Decree-Law 45/2021) has been in force since 2 January 2022 and contains its own provisions on transferring personal data outside the UAE. We found no public government source confirming its executive regulation as of 16 October 2026. Ask counsel which transfer basis applies, and the UAE Data Office about the regulation’s status.
• If you are a licensed financial institution, the Central Bank’s Operational Risk Management Regulation (Circular 1/2026, effective 14 September 2026), Article 8.9, requires your Master System of Record to be continuously maintained and stored in the UAE, including when outsourced. Branches of foreign institutions may, with Central Bank approval, keep an up-to-date copy in the UAE instead.
• If you are a bank, the Outsourcing Regulation for Banks (Circular 14/2021), Article 6.3, bars sharing confidential customer data outside the UAE without Central Bank approval and prior written customer consent, including acknowledgement of possible access under foreign legal proceedings. Does any BDC component hold such data outside the UAE?
• Which non-UAE region would serve each component, and does that satisfy the rules above?

For every component, ask SAP in writing

• Where is the data stored, processed and supported from?
• Which dependent SAP services may be delivered from another region?
• Where does AI inference run when Joule or an agent touches the data product?
• What changes if SAP moves a component or region?
• Where do consumer-side caches and query results reside (ask the consuming vendor too), and what retention and deletion controls apply?

Each answer should be a region name, a date and a document reference. A general statement counts as unanswered.

10. A 90-day path

Days 1 to 30: decide what BDC is for. List the decisions and agents that need governed SAP data, each with an owner and a measure. Record every renewal date across your Datasphere, SAC, BW, lakehouse and RISE contracts. Run section 8’s pre-pilot checks on the three strongest candidate data products, and send SAP the placement questions in section 9.

Days 31 to 60: price it and place it. Get a written CU quote in your currency, with rates, minimum attach and a peak-month scenario, and rerun section 4’s example on your own numbers. Take the placement answers to counsel and, where relevant, your regulator. Choose a posture per use case from section 7.

Days 61 to 90: commit to one slice. One data product that clears the pre-pilot checks, one consumer, one exit test and the measure that proves value; expand only when every section 8 check passes. Negotiate the order form against section 4. Set recheck dates for Fabric, Athena and Joule Agents in BDC, and plan the retirement of what the slice replaces.

The one thing to do after reading: write down the single decision or agent that would justify BDC, and the owner of the data product beneath it. If you cannot, wait.

Next step: Altivate can review your data-product readiness and your CU quote before you sign. See our SAP Business Data Cloud page or contact us.

Sources and verification status

Checked 16 October 2026. Status labels follow the sources named. The readiness test and the posture table are an Altivate synthesis, not SAP guidance or legal advice.

• SAP News Center, Accelerate the Autonomous Enterprise with SAP Business Data Cloud
• Sapphire 2026: HANA Cloud and MDG as core components, Reltio, Joule Agents, partners, Athena.
• SAP News Center, SAP Unveils the Autonomous Enterprise
• the SAP Business AI platform and Knowledge Graph.
• SAP News Center, SAP Puts the Autonomous Enterprise to Work
• SAP Connect, 6 October 2026.
• SAP News Center, How Joule Work and SAP Business AI Platform Are Powering the Next Generation of Business AI
• 8 October 2026; SAP Reltio generally available in BDC.
• SAP News Center, SAP and Databricks: A Bold New Era of Data and AI
• announcement, 13 February 2025.
• SAP News Center, SAP Business AI: Release Highlights Q1 2026
• Joule in Datasphere.
• SAP News Center, New in SAP CX Q2 2026
• 16 July 2026; Consumer Products Intelligence in SAP Early Adopter Care.
• SAP News Center, SAP Ariba Spend Analysis and Insights now available
• 16 September 2026.
• SAP News Center, BDC Connect for Microsoft Fabric
• announced 18 November 2025; planned for Q3 2026.
• SAP Community, SAP BDC Connect for Microsoft Fabric – GA?
• reply by Thierry Audas of SAP, 31 August 2026: general availability now planned for the end of Q1 2027, subject to change. A forum reply, not a roadmap or press statement.
• SAP News Center, SAP and AWS: bi-directional zero-copy data sharing with SAP BDC
• BDC regions on AWS.
• SAP User Groups, Breaking down the SAP BDC pricing model (16 April 2026)
• Capacity Unit model, packages, Datasphere, SAC and SAP Databricks CU rates, Customer-Managed Data Products as the “Intelligent Package Alternative”.
• SAP, SAP Business Data Cloud pricing
• Checked 16 October 2026; shows no CU price.
• SAP Agreements, SAP Business Data Cloud service description guide, version 9, 2026
• September 2026. §2.3 metering, §3.1 SAC user counting, §5.5.1 and §5.5.2 BW dates, §6.1 RISE prerequisite, §6.3 Customer-Managed Data Products, §6.7 Spend Intelligence, Attachment A Table 3 BDC Connect rates and Data Sharing Fee.
• SAP, SAP Business Data Cloud FAQ (last updated 13 July 2026)
• component placement and hyperscalers.
• SAP Community, Announcement: SAP Datasphere and SAP Analytics Cloud availability via SAP Business Data Cloud
• 1 July 2025; BTP removal, renewal and tenant preservation. An SAP post, not contract text.
• SAP Community, SAP Business Data Cloud – FAQs
• updated 4 December 2025; tenant rewiring, intelligent applications and SAP-managed data products. An SAP Community post, not contract text.
• SAP Help Portal, Provisioning SAP Business Data Cloud Connect
• supported hyperscalers per connector (BigQuery: AWS and GCP on the BDC side); consumer-side caching permitted.
• SAP Help Portal, Applying Row-Level Security to Data Delivered through Intelligent Content
• source-system authorizations are not imported; permissions table.
• SAP Community, Announcing General Availability of SAP Snowflake and SAP BDC Connect for Snowflake
• 25 May 2026.
• SAP Community, Maintenance strategy for SAP NetWeaver 7.5 fully aligned with SAP Business Suite 7
• 7 April 2020; BW 7.5 and BW/4HANA maintenance.
• SAP Community, Introducing the SAP BDC Modernization Option for SAP BW NetWeaver
• 10 September 2026; 2031 to 2033 option.
• SAP Architecture Center, Modernizing SAP BW with SAP Business Data Cloud
• Lift and Shift, Data Product Generator starting releases.
• SAP Help Portal, Data Product Generator for SAP Business Data Cloud
• what the generator does.
• SAP Help Portal, Data Center Availability in SAP Business Data Cloud
• components by region, including SA30 and SA31.
• SAP Help Portal, Data Center Availability in SAP Reltio
• Reltio sites where BDC is not deployed.
• SAP Learning, Data Product Generator for SAP Business Data Cloud
• lift as a prerequisite for BW within BDC.
• SAP Help Portal, Regions and API endpoints for the Cloud Foundry environment
• sa30, sa31 and ae01.
• Databricks, General availability of SAP Databricks on SAP BDC
• 30 April 2025.
• Databricks, SAP Databricks release notes, August 2025
• Google Cloud, 26 August 2025.
• Databricks, SAP Databricks documentation
• supported regions, forecasting, publishing data products back into BDC.
• Databricks, General availability of SAP BDC Connect for Databricks
• 6 October 2025.
• Microsoft, SAP Business Data Cloud now available on Microsoft Azure
• 9 October 2025; BDC and SAP Databricks on Azure.
• Microsoft, SAP BDC Connect with Azure Databricks is now generally available
• 15 October 2025; your own Azure Databricks.
• Snowflake, SAP BDC zero-copy connector release note and supported regions
• 4 May 2026.
• Google Cloud, SAP and Google Cloud launch BDC Connect for BigQuery
• 28 July 2026; general availability and regions.
• Google Cloud, Set up a cross-cloud connection to SAP BDC and SAP BDC overview
• updated 15 October 2026; Enterprise Plus requirement, default caching and cache location, AWS/Azure/Google Cloud hosting, naming and access-control limitations.
• National Cybersecurity Authority, Cloud Cybersecurity Controls CCC-2:2024
• scope, levels, localisation transfer.
• Saudi Central Bank, Cyber Security Framework 3.4.3 Cloud Computing
• hybrid and public cloud scope, controls 4.a.2 and 4.b.1, private-cloud note.
• SDAIA, Personal Data Protection Law
• decree references.
• UAE Government portal, Data protection laws
• in force 2 January 2022; lists DIFC Law No. 5 of 2020.
• Central Bank of the UAE Rulebook, Operational Risk Management Regulation, Article 8
• Circular 1/2026, Article 8.9.
• Central Bank of the UAE Rulebook, Outsourcing Regulation for Banks
• Circular 14/2021, Article 6.
• Not confirmed in a public document as of 16 October 2026: Fabric and Athena general availability, general availability of Consumer Products Intelligence and of the full Spend Intelligence package, a currency price per CU, the current text of SDAIA’s transfer rules, the UAE PDPL executive regulation, any BDC region in the UAE, and the last-updated date of SAP’s BDC data-centre list.