SAP Business Data Cloud

What is SAP Business Data Cloud?

SAP Business Data Cloud (BDC) is SAP’s managed data platform, announced in February 2025. It brings SAP Datasphere, SAP Analytics Cloud, SAP BW and SAP Databricks together in one SaaS offering. The core idea: instead of every customer extracting, cleaning and modelling SAP data alone, SAP ships data products. These are curated, zero-copy, semantically consistent datasets from S/4HANA, SAP Ariba, SuccessFactors and other SAP applications, kept current through every release. On top sit intelligent applications: prebuilt analytics for finance, people and ERP.

That solves the problem most companies actually have. Not “we need another BI tool”, but “our CRM says one number, our ERP says another, and nobody trusts either.”

What is in BDC in 2026

BDC has grown fast since the launch. As of October 2026, it consists of:

• Data products from SAP applications, plus customer-managed data products you build yourself, for example from CRM data or from SAP BW.
• SAP Datasphere for modelling and SAP Analytics Cloud for dashboards and planning.
• SAP BW private cloud edition for companies with existing BW investments.
• Compute of your choice: SAP Databricks or SAP Snowflake inside BDC, or SAP BDC Connect for zero-copy sharing with the Databricks, Google BigQuery or Snowflake you already run.
• SAP HANA Cloud and SAP Master Data Governance as core components since Sapphire 2026, with Reltio for master data.
• Joule agents that search and create data products and generate Analytics Cloud stories.

Why this matters for the Swiss mid-market

Large enterprises have data engineering teams. Swiss mid-market companies, the manufacturers, distributors and industrial firms we work with every day, usually don’t. They have an ERP, a CRM, a warehouse of spreadsheets, and a management team that wants answers without a two-year data programme.

BDC changes the economics: the extraction and modelling work that used to need a dedicated team now ships as a maintained SAP product. What remains is the part that differentiates: deciding which questions matter, connecting the right domains, and putting the answers where people work. That part is consulting, not plumbing, and we scope it domain by domain. And since March 2026, BDC runs on Microsoft Azure in Switzerland, so data residency is settled.

BDC and Datasphere: what changes, what stays

If you already run SAP Datasphere, nothing you built is lost: Datasphere is a component of Business Data Cloud, and existing spaces and models carry over. What changes is the packaging and the ceiling: SAP-managed data products replace hand-maintained replication flows, and machine-learning workloads run inside SAP governance instead of in a parallel shadow platform. We wrote up the details in BDC and Datasphere: what changes, what stays. Running SAP BW? Read From BW to Business Data Cloud: the modernisation path.

The data foundation under your CX and ERP

This is our angle, and it is different from the classic BI house. Spadoom is a Swiss SAP Gold Partner for Cloud ERP and Customer Experience; our core business is SAP Sales Cloud V2, Service Cloud V2 and S/4HANA Public Cloud. We implement the systems that produce the data: pipeline, orders, cases, margins. BDC is where that data becomes usable:

• Pipeline-to-cash in one view. Opportunities from Sales Cloud V2 joined with orders and invoices from S/4HANA: the report every CFO asks for and almost nobody has.
• Service profitability. Cases and SLAs from Service Cloud V2 against contract margins from the ERP.
• Forecast you can defend. CRM forecast quality measured against what actually shipped.

One honest note: SAP does not ship managed data products for Sales and Service Cloud V2 yet. Its CX package, Revenue Intelligence, is on the roadmap. Until it arrives, we bring the CX data in through SAP Integration Suite and Datasphere and model it next to the ERP data products. The patterns are in Connecting SAP Sales Cloud V2 with Business Data Cloud.

Still on ECC? The five-day S/4HANA readiness check sets the timeline and cost range for the ERP move, and our transformation guide shows how data, ERP and CX fit together.

Typical first use cases

Start with one question that management asks every month and nobody can answer quickly. The use cases we see most often:

• Working capital and cash on the S/4HANA finance data products.
• Pipeline-to-cash with Sales Cloud V2 data next to S/4HANA orders and invoices.
• Service margin per contract or customer, from Service Cloud V2 cases and S/4HANA costs.
• BW data as data products, shared with SAP Databricks for forecasting.

Common pitfalls, and how we avoid them

• Platform first, question second. A BDC tenant without a use case is an expensive empty room. We start with one KPI and its owner.
• Assuming a data product exists. Check the catalogue for your sources and release. For CX data, plan the bridge.
• Dirty master data. A clean model on duplicate customers gives clean-looking wrong answers. See why your CRM data is only as good as your data foundation.
• Choosing compute before the question. Datasphere, SAP Databricks, SAP Snowflake and BDC Connect overlap. The use case decides, not the logo.
• Unclear licence. Capacity units, intelligent packages and existing BW contracts need one sizing exercise up front, with SAP’s estimator.

More in Five mistakes to avoid when starting with SAP Business Data Cloud.

What Spadoom delivers

We deliver BDC the same way we deliver ERP and CX: fixed scope, Swiss directness, and adoption over shelfware. A typical first engagement: size the licence with you, activate BDC, connect the S/4HANA data products, bring in the Sales Cloud V2 and Service Cloud V2 data, model one business domain end to end, and ship the first dashboard to the people who need it. From there you extend domain by domain, each one paying for the next.

Start with the fundamentals if you want the full picture: SAP Business Data Cloud explained. The latest developments are in SAP Business Data Cloud timeline 2025 to 2026.

BDC and SAP Business AI

Every AI conversation ends at the same place: the data. Joule agents, AI forecasting in Sales Cloud V2, automated service resolution: all of it runs on the data underneath, and AI on messy data is expensive noise. Since Sapphire 2026, SAP positions BDC as the data layer of its Business AI Platform, next to SAP BTP. That makes BDC the foundation layer of our SAP Business AI practice: clean, governed, connected data first, then AI that holds up in production.

What good looks like

A BDC implementation is working when management stops debating whose number is right and starts debating what to do about it. One semantic model, consumed by dashboards, Databricks notebooks and Joule agents alike, and a mid-market data foundation that one team can own without a data engineering department.