TL;DR
SAP Business Data Cloud is SAP’s managed data layer that keeps SAP and non-SAP data together as governed data products with their business meaning intact. It bundles Datasphere, SAP Analytics Cloud, SAP BW, SAP HANA Cloud, Master Data Governance and SAP Databricks under one subscription. Its BDC Connect feature shares data with Databricks, Snowflake, Microsoft Fabric and Google BigQuery without copying it. Availability differs by partner, so check each connector before you plan around it. Pricing runs on Capacity Units with no public list price, which makes a bounded first project the safe start. Adopt BDC where SAP semantics drive your reporting, and connect it to the lakehouse you already run.
Key Takeaways SAP Business Data Cloud (BDC) is a managed business data fabric that SAP launched with Databricks in February 2025. It brings Datasphere, SAP Analytics Cloud, SAP BW, SAP HANA Cloud, Master Data Governance, SAP Reltio and SAP Databricks into one product. Data products keep SAP’s fiscal calendars, hierarchies and currency rules attached, so every consumer starts from the same figure. BDC Connect shares data both ways without copies, but BigQuery is generally available while Fabric’s connector was announced with GA planned for Q3 2026. BW 7.5 mainstream maintenance ends in 2027, which puts a date on the BDC question for many SAP analytics teams. BDC is priced in Capacity Units with no public list price, so start with one outcome and one data product. Watch on YouTube
LLM Hallucination in Enterprise Data: The Semantic Layer Fix
Kanerika explains why AI answers go wrong when business meaning is stripped from data, and how a semantic layer fixes it, the same problem SAP built BDC data products to solve.
The Promise in SAP’s Launch Announcement
SAP announced Business Data Cloud on 13 February 2025, and one sentence in the launch press release matters more than the rest. “These data products maintain their original business context and semantics, providing immediate access to high-quality data without costly extraction processes.”
Anyone who has rebuilt an SAP fiscal calendar inside a lakehouse knows why that line landed. A generic extract drops the company-code hierarchies, currency rules and fiscal periods that give a revenue figure its meaning. Then the data team spends months putting them back by hand.
BDC is SAP’s answer to that rebuild, and it arrives at an awkward moment. For one thing, BW 7.5 is close to the end of mainstream maintenance. At the same time, many SAP teams already run Databricks, Fabric or Snowflake on the other side of the estate.
So the decision in front of most data leaders is about architecture, not about a product swap. In practice, ask where BDC sits next to what you already own, and which parts of your stack should stay exactly where they are.
What Is SAP Business Data Cloud?
BDC is a managed SaaS layer where SAP data arrives already modeled, governed and labeled for analytics, planning and AI. SAP’s own definition calls BDC “a connected, end-to-end solution that bridges SAP and third-party data sources through a business data fabric “. In practice, it is the place where SAP wants all of your SAP analytics to live.
A Managed Business Data Fabric, in Plain English
A data fabric connects data where it already lives instead of forcing every table into one store. BDC applies that idea to SAP’s own applications first, then opens the door to third-party sources. It also went live alongside SAP Databricks , a Databricks product built natively into the platform.
The positioning has moved since launch. SAP’s product page now calls BDC “the trusted data foundation for SAP Business AI Platform,” which tells you where SAP sees the product heading. In other words, BDC is the data underneath SAP’s AI plans as much as an analytics product.
Why SAP Built It
For years, extraction has been the weak point of SAP analytics. Pull a table out of S/4HANA through a generic pipeline and you get columns without meaning. So every downstream team rebuilds the logic its own way. SAP cites a survey of 1,200 business and technology leaders in which 55% name poor data quality as their biggest obstacle.
In effect, BDC is SAP’s bet that keeping semantics attached at the source removes a large share of that rework. It is also a commercial bet, because data that stays inside SAP’s layer keeps SAP at the center of the analytics estate.
Data Products and Business Semantics
SAP describes its data products as curated, governed packages of data “with context, business semantics, and documentation.” Take revenue. In SAP, that number depends on the fiscal calendar, the company-code hierarchy and the currency translation rules.
Watch on YouTube
Why IBM Spent Billions on Confluent Acquisition | AI-Driven Data Fabric
A look at why data fabric has become the design pattern for AI-ready data, and what connecting data where it lives means in practice for an enterprise like an SAP shop.
A raw extract, however, carries none of that context. A BDC data product, by contrast, carries it with the data. That way, an analyst in SAP Analytics Cloud and a data scientist in SAP Databricks start from the same figure. SAP’s November 2025 release also added a data product studio for building custom data products with visual and SQL tools.
What BDC Does Not Solve for You
BDC packages data well, but it does not settle arguments about what “net revenue” means in your company. The split below is worth agreeing with your sponsor before anyone signs an order form.
What BDC Provides What Your Organization Still Owns Prebuilt data products with SAP semantics One agreed definition per KPI across finance, sales and planning Governance tooling and a shared catalog Named data owners who approve changes Zero-copy sharing with partner platforms Source data quality in S/4HANA and non-SAP systems Prebuilt Intelligent Packages for lines of business Deciding which legacy reports retire and which survive
The right-hand column is where most programs slip, and it is plain data governance work that no subscription includes. A data quality framework agreed early will save more time than any connector.
SAP BDC Components: What Is Inside the Box
SAP says BDC “brings together Datasphere, SAP Analytics Cloud, SAP Master Data Governance, SAP HANA Cloud, SAP Databricks, and SAP BW with a unified experience”. The product page FAQ also adds SAP Reltio to that list. Most SAP customers already own one or two of these, which changes what adoption actually means for them.
Component Job in BDC If You Already Own It Question to Ask SAP SAP Datasphere Integration, semantic modeling, data products Keeps running as the modeling layer Which of our models map to SAP-managed data products? SAP Analytics Cloud Dashboards, analytics and planning Reads data products directly How does our current licence move into Capacity Units? SAP BW and BW/4HANA Existing warehouse logic, modernized in place Lift first, then shift to data products Which BW objects can the Data Product Generator convert? SAP Databricks Data engineering, ML and AI on SAP data Separate from your own workspace Which workloads belong here, and which stay native? SAP HANA Cloud In-memory database engine underneath Usually consumed, rarely managed What storage and compute does our estimate assume? SAP MDG and SAP Reltio Master data governance and multi-domain MDM Reltio became generally available in BDC in October 2026 Do we need both, and who owns the golden record?
Is SAP BDC the Same as Datasphere?
SAP answers that one directly. “No, SAP Business Data Cloud is not the same as SAP Datasphere. However, SAP Datasphere is a core component of SAP Business Data Cloud”. Datasphere first launched in 2023 as the successor to SAP Data Warehouse Cloud. So Datasphere customers are already inside the box.
What BDC adds on top is the layer of prebuilt data products, the AI tooling and the open sharing with outside platforms. So for a Datasphere team, the change is mostly in scope and contract, not in daily modeling work.
SAP Databricks vs the Databricks Workspace You Already Run
SAP sells SAP Databricks as part of BDC, and it is a separate environment from any Databricks account you hold today. Even so, the two can share data in both directions through Delta Sharing , with governance handled by Unity Catalog . So an existing lakehouse does not need to move to get SAP data products.
The practical question, then, is placement. Heavy ML on SAP data may sit well in SAP Databricks, while cross-domain pipelines usually stay in the workspace your engineers already know.
Intelligent Packages: SAP’s Prebuilt Applications
SAP’s name for its prebuilt analytics apps has changed twice. They were “insight apps” at launch, then intelligent applications, and SAP’s commercial material now calls them Intelligent Packages. Today the product page lists Cloud ERP, Finance, Supply Chain, People, Spend and Revenue Intelligence.
Not every package is equally mature, though. SAP’s April 2026 pricing briefing listed Finance and Retail Intelligence in controlled availability for early adopters, with several others still on the roadmap.
SAP Business Data Cloud Architecture: From Source to Consumption
The BDC architecture is easiest to read as three layers. Sources feed a knowledge core, and the knowledge core serves a set of consumers inside and outside SAP. Each layer raises its own design questions, and they are rarely the same people’s questions.
Sources: SAP Applications, BW Landscapes and Non-SAP Systems
The richest sources are SAP’s own applications, from finance and supply chain data in S/4HANA to spend data in Ariba and talent data in SuccessFactors. BW landscapes then come in as a second stream, often carrying a decade of custom logic. Non-SAP sources arrive through Datasphere’s integration layer, which is the same enterprise data integration problem every data team already knows.
That last stream is where projects underestimate effort. A CRM or a logistics feed has no SAP semantics to inherit. Therefore somebody has to model it before it can sit next to a data product. For that reason, Kanerika’s data integration services often start exactly there.
Watch on YouTube
Microsoft Fabric vs Databricks vs Snowflake: The Real Architecture Differences
Kanerika compares how Fabric, Databricks and Snowflake are built, which helps you judge which BDC Connect partner suits the lakehouse you already run.
The Knowledge Core and SAP Knowledge Graph
SAP puts it plainly. “A central knowledge core organizes data into governed data products enriched with business semantics”. The SAP Knowledge Graph then supplies a semantic layer on top. For example, it maps which cost center belongs to which company code.
In other words, this layer is the part that makes BDC different from a plain warehouse. It is also the part that SAP’s AI agents read when they answer a question, which is why its quality matters twice.
Consumption: SAC, SAP Databricks, Joule Agents and External BI
On the consuming side, SAP Analytics Cloud handles dashboards and planning, while SAP Databricks runs notebooks, pipelines and models. Joule Agents also use the same data products and knowledge graph. SAP says this “enables Joule agents to automate tasks, generate insights, and take action with greater accuracy, transparency, and reliability”. Finally, outside platforms reach the data through BDC Connect.
Zero-Copy Sharing vs Replication: Where Data Still Moves
Zero-copy is the headline, but it covers specific paths, not the whole estate. It applies when a data product is shared through BDC Connect to a supported partner on a supported cloud. Data still moves in four common cases.
Loading non-SAP sources into BDC. Those records are ingested and stored, not shared in place.Transforming in another engine. If a lakehouse job persists its output, that output is a new copy with its own lineage.Meeting tight latency targets. Some dashboards need a materialized table close to the consumer.Waiting on a connector. Until a partner connector is generally available for your hosting cloud, replication is the fallback.So map every flow on your diagram as shared or copied before you promise anyone zero-copy. Each copied flow needs an owner, a refresh schedule and a data lineage record.
What SAP Announced at TechEd in October 2026
At SAP TechEd Berlin on 29 October 2026, SAP said it had completed its acquisition of Dremio. The same announcement said BDC now supports native Apache Iceberg and a universal catalog powered by Apache Polaris. It also described federated zero-copy queries across lakehouses and databases such as SQL Server, MongoDB, Oracle and Postgres.
SAP Databricks also gained Lakeflow, Agent Bricks, Unity Gateway and Lakebase in the same release. SAP also introduced SAP Application Data Foundation and a BDC Ontology Manager, which gives agents domain-specific views of the knowledge graph. Treat these as announced capabilities, because SAP stated general availability only for SAP Reltio.
BDC Connect: How SAP BDC Works with Databricks, Microsoft Fabric, Snowflake and BigQuery
BDC Connect is the piece that decides how BDC lives next to the platform you already run. SAP says it lets organizations “securely share data between Business Data Cloud and leading platforms such as SAP Databricks, Snowflake, Microsoft Fabric, Google BigQuery, and Amazon Athena”. In theory, data and metadata move both ways without copies. However, the status of each connector is different.
Partner How It Connects Status as of November 2026 Best Fit Databricks (your own workspace) Delta Sharing with SAP Databricks, governed in Unity Catalog Launched with BDC in February 2025, staged rollout on AWS, Azure and Google Cloud Existing Databricks lakehouse and ML estates Microsoft Fabric SAP data products in OneLake, OneLake data available in BDC Announced November 2025, GA planned for Q3 2026; confirm current status Power BI and Microsoft-centered estates Snowflake BDC Connect for Snowflake, plus the SAP Snowflake solution extension sold by SAP Announced November 2025; no GA date stated Snowflake-first analytics estates Google BigQuery BDC Connect for BigQuery Generally available since 27 July 2026 for BDC on Google Cloud and AWS; Azure-hosted support “coming soon” BigQuery and Google Cloud AI users
Databricks: Two Environments, One Share
Databricks has the longest track record with BDC, because SAP Databricks shipped on day one. If you run your own workspace, the pattern is a Delta Sharing link between the two. Unity Catalog then applies the same access rules on both sides. Kanerika works with this setup as a Databricks partner , and the first design call is always which side owns each pipeline.
Kanerika Service
Data Integration Services
Kanerika models and connects non-SAP sources, CRM, logistics and finance feeds, so they sit cleanly next to SAP data products in one governed estate.
Explore Data Integration Microsoft Fabric and Power BI
SAP and Microsoft announced BDC Connect for Microsoft Fabric on 18 November 2025. Under that plan, SAP data products would land in OneLake, and OneLake data sets would be visible inside BDC. The announcement put general availability in Q3 2026. We found no GA notice from SAP or Microsoft by early November 2026. SAP’s October 2026 TechEd release lists Microsoft among its zero-copy partners without a date, so confirm the current status before you plan around it.
For Power BI teams, that connector is the route to watch, since Microsoft Fabric puts Power BI on top of OneLake. Until it is live for your tenant, keep your current SAP connection path and test the Fabric route in parallel. Validate authentication, refresh timing and row-level security before you move a single production report.
Snowflake
SAP announced two Snowflake options at TechEd in November 2025. BDC Connect for Snowflake shares data products with an existing Snowflake account, while the SAP Snowflake solution extension is sold directly through SAP. Neither had a stated GA date on SAP’s page, so treat both as announced.
Google BigQuery
Among the connectors announced since launch, BigQuery is the only one with a published GA date. Google says BDC Connect for BigQuery supports BDC instances hosted on Google Cloud and AWS, with Azure-hosted support “coming soon”. So check where your own BDC tenant runs before you plan around it.
Whichever partner you pick, the extraction questions do not vanish. Our guide to SAP data integration covers replication, ODP and the flows that still need a pipeline.
What BDC Means If You Already Run BW, Datasphere or SAC
Fortunately, existing SAP analytics customers are not starting from zero. SAP says they “can continue to use their current tools while benefiting from deeper integration, expanded data, and access to governed data products and AI-ready data”. Even so, the real difference between customers is the clock they are on.
Starting Point SAP’s Stated Path What to Validate First Datasphere and SAC Keep the tools, gain data products Which SAP-managed data products replace custom models BW 7.5 on premises Lift to private cloud edition, then shift Maintenance dates and a full BW object inventory BW/4HANA Shift gradually, maintenance to 2040 Which flows gain from data products now Non-SAP BI reading SAP through ODP Certified connectors or BDC Connect Connector certification and licensing terms
BW 7.5 and BW/4HANA: The Maintenance Clock
According to BARC , mainstream maintenance for SAP BW 7.5 ends in 2027, with extended maintenance to 2030 at extra cost. SAP BW/4HANA receives maintenance until 2040. For this reason, BW 7.5 shops feel the BDC question first, because their clock runs out sooner.
Lift, Shift, Innovate and the Data Product Generator
BARC describes SAP’s recommended path in three stages. First, Lift moves the existing BW system to a private cloud edition, with maintenance to 2030. Shift then migrates BW artifacts into customer-managed data products, helped by a Data Product Generator that SAP planned to provide from 2026.
Kanerika Service
Data Modernization Services
Kanerika maps BW objects, reports and custom logic, then plans a staged move so SAP analytics keep working while the platform underneath changes.
Explore Data Modernization Innovate is the last stage, where critical flows switch to SAP-managed data products. SAP calls the whole route a “gradual, low-risk modernization journey to the cloud,” and that is SAP’s framing, not a guarantee. Our SAP modernization guide covers the program side, and the SAP data migration guide covers moving the data itself.
Running a Non-SAP Analytics Stack
Teams that read SAP data into third-party tools, meanwhile, face a quieter change. BARC notes that SAP no longer certifies the ODP interface as a recommended access path. Instead, SAP now promotes certified connectors that steer customers toward BDC. So check connector certification and licensing early, before a renewal forces the conversation.
SAP BDC vs Fabric, Databricks and Snowflake: Adopt, Extend or Defer?
People search for “SAP BDC vs Fabric” or “BDC vs Databricks,” but the comparison is lopsided. BDC is where SAP data keeps its semantics, and the lakehouse is where everything else meets it. So the useful question is which role BDC should play in your estate, and the answer is usually one of three.
Starting Condition Path Evidence Required Reason to Wait SAP semantics drive most reporting and BW is on the clock Adopt BDC as the SAP data layer BW report inventory and a Capacity Unit estimate None, once one use case is funded A Databricks, Fabric or Snowflake lakehouse holds most non-SAP data Extend the lakehouse and connect it through BDC Connect Connector status for your cloud and a tested data product share The connector is not GA where your BDC runs No prioritized use case or unclear KPI ownership Defer and fix ownership first A named owner and one measurable outcome Until both exist
Adopt BDC as the SAP Data Layer
Adopt when SAP semantics drive most of your analytics and BW 7.5 is close to its maintenance date. In that case, BDC replaces work your team would otherwise rebuild by hand, and the Lift stage buys time for the rest.
Extend the Lakehouse You Already Run
Extend when your non-SAP data already lives in a mature lakehouse. Here BDC becomes the SAP side of the estate, and BDC Connect feeds data products into the platform your engineers know. In fact, nothing about that lakehouse has to move.
Defer Until the Basics Are in Place
Defer when nobody can name the use case or the KPI owner, or when the connector you need is not GA for your cloud. Waiting a quarter costs less than building data products on definitions that are still in dispute.
SAP Business Data Cloud Pricing: How Capacity Units Work
SAP does not publish a list price for BDC. The clearest public explanation is SAP’s April 2026 user-group pricing briefing , given by its BDC commercialization team.
BDC Core and Capacity Units
BDC Core is a subscription measured in Capacity Units (CU). Those units can be applied across the underlying services in varying amounts, including Datasphere, SAC, BW, MDG, HANA Cloud, BDC Connect and SAP Databricks. SAP also publishes a BDC Capacity Unit Estimator for sizing.
Intelligent Packages, however, sit outside that pool. Each one uses a metric tied to its SAP source application, and each requires BDC Core underneath it.
The Entry Signal for Customer-Managed Data Products
SAP’s briefing gave one useful floor. The customer-managed data products route carries a minimum BDC Core attach of 640 Capacity Units. SAP sized that on the smallest viable setup, an SAC tenant with 25 BI users. Commercial terms change, so treat that as a 2026 signal rather than a quote.
Costs That Sit Outside the Subscription
Of course, the subscription is only part of the bill. Partner platforms charge for their own compute when they read shared data products, and integration, testing, BI rework and operations all add effort. Before procurement, put these five questions to SAP and your delivery partner.
Which services and volumes does our Capacity Unit estimate assume? How do our current Datasphere and SAC subscriptions convert into BDC terms? Which Intelligent Packages carry their own metric, and what drives it? What will the partner platform cost when it reads data products through BDC Connect? Which integration and report rebuild work sits outside the SAP contract? A short data strategy exercise usually answers the last two before the first sales call ends.
Where SAP BDC Earns Its Cost: Finance, Supply Chain and AI
BDC pays off where several teams argue over the same SAP numbers. Three patterns show up most often, and each one depends on something outside the platform.
Use Case Data It Needs Dependency Success Measure Finance close and reconciliation General ledger, cost centers, consolidation Agreed KPI definitions; Finance Intelligence availability Fewer reconciliation breaks per close Supply chain and order visibility Orders, deliveries, inventory, logistics feeds Shared identifiers across SAP and non-SAP systems Late orders spotted earlier AI on SAP data Data products and the knowledge graph Governed access that matches user roles Agent answers accepted without rework
Finance on Consistent Definitions
SAP’s launch example was a CFO who wants to see how inflation hits profitability. BDC would combine the consumer price index with financial data products such as general ledger accounts and cost centers. That works only when finance and controlling agree on what each account rolls up to, and finance teams on Fabric face the same test.
Supply Chain and Order Visibility
In general, order visibility needs one identifier for a customer, a material and a shipment across every system. BDC can carry the SAP side cleanly, but a carrier feed or a warehouse system will not share those keys by default. Freshness also depends on the source, so do not promise real-time views that the source cannot refresh.
AI on SAP Data with Joule Agents
Joule Agents read BDC data products and the knowledge graph to act with business context. Also, SAP’s TechEd 2026 announcement brings Agent Bricks to SAP Databricks for custom agents. Our SAP Joule guide explains what Joule does with that data. The quality of the answers still depends on the quality of the data product underneath.
SAP BDC Readiness Checklist and Failure Modes
Readiness is mostly evidence you can put on one page. Each line below has an owner, because a requirement with no owner is the first one to slip.
Requirement Evidence Owner Report inventory BW queries and SAC stories with usage counts BI lead KPI definitions A signed definition for the top ten KPIs Finance controller Custom logic map Custom tables, extractors and ABAP enhancements listed SAP technical lead Identity mapping SAP roles mapped to partner platform identities Security architect Row-level access Access tested in every consumer, not just SAC Data platform lead Lineage and monitoring Source-to-report lineage and alerts on failed loads Data operations
Source and Semantic Readiness
In our experience, the custom logic map is the line most teams skip. Years of Z-tables and SAP ABAP enhancements hide business rules that no data product knows about. Our SAP clean core guide shows how to find and retire that custom code.
KPI definitions come next, and they cause the loudest arguments. Sales, finance and planning often hold three versions of revenue, each correct in its own system. Agree one before any data product goes live.
Checklist
Enterprise Data Governance Checklist
A step-by-step checklist for the ownership, KPI definition, access and lineage work that an SAP Business Data Cloud rollout depends on.
Get the Checklist → Failure Modes Worth Planning Around
Symptom Cause Prevention Dashboards disagree after go-live Accessible data treated as business-ready Reconcile each data product against a known report Reports rebuilt twice Rebuild started before KPIs were agreed Freeze definitions before the first rebuild Users see rows they should not Permissions assumed to carry across platforms Test row-level access in every consumer Reports break after BW shutdown BW retired before dependencies were mapped Complete the inventory before decommissioning
In short, every row in that table has the same root. The platform worked, but an organizational decision was skipped, so treat the checklist as part of the project plan rather than a pre-sales formality.
How to Get Started with SAP Business Data Cloud
SAP runs a 30-day basic trial at no cost, in a shared tenant with preconfigured data and some functions restricted. It is good for learning the interface, but it will not tell you how your own data behaves. For that, run a stage-gated first project instead.
Pick one outcome. Gate: a sponsor signs off on a single measurable result, such as faster month-end reconciliation.Pick one data product. Gate: the KPI definition behind it is agreed and owned.Pick one consumption path. Gate: SAC, SAP Databricks or a partner platform is chosen, with its connector status confirmed.Reconcile. Gate: the new figure matches a trusted existing report within an agreed tolerance.Scale. Gate: access, lineage and monitoring pass review before a second data product starts.Teams moving data out of older SAP systems can compare options in our roundup of SAP data migration tools .
How Kanerika Helps You Evaluate and Connect SAP Business Data Cloud
Kanerika works on the side of the estate where SAP data meets the lakehouse and the BI layer. We are a Microsoft Fabric Featured Partner, a Microsoft Solutions Partner for Data and AI with the Analytics specialization, and a Databricks consulting partner. That is the ground BDC Connect is built for.
Our engagements usually follow five steps, in order. First, we assess the SAP estate, the reporting layer and the BW clock. Then we design the split between BDC and your Microsoft Fabric , Databricks or Snowflake platform. After that we build the first governed data product and its Power BI or SAC path. Finally, we set up row-level access, lineage and KPI ownership, and train the team that will run it.
SAP Data in a Governed Fabric Lakehouse
One pharmaceutical manufacturer shows the pattern. Its sales and financial data sat across Model N, SQL Server, SAP and SAP Vistex, with no central warehouse, so effort was duplicated and figures did not match. Kanerika consolidated those sources into one Fabric lakehouse with tailored Power BI reports. As a result, the sales and financial KPIs project cut man-hours spent on reporting by 95%.
That project came before BDC Connect. Still, it is the move BDC Connect for Fabric is planned to formalize: SAP data landing in one governed lakehouse that business users trust. The same client also saw a 40% rise in operational efficiency and a 35% cut in operational costs.
Many SAP estates also carry a reporting layer that has outlived its platform. Kanerika’s SAP BusinessObjects migration service moves those reports to Power BI and Fabric. FLIP , our migration accelerator, also converts SAP Crystal Reports to Power BI, and in October 2026 it added a Crystal Reports to DevExpress pathway. If you want a clear read on one SAP analytics workload, talk to our team .
Case Study
95% Less Manual Reporting with Microsoft Fabric
SAP, SAP Vistex, Model N and SQL Server data consolidated into one Fabric lakehouse with Power BI, cutting reporting man-hours by 95%.
Read the Case Study → SAP Business Data Cloud: Where It Fits in Your Stack
BDC is SAP’s governed data layer for estates where SAP data carries most of the business meaning. It also bundles the SAP analytics tools many teams already own, adds prebuilt data products, and shares them with partner platforms through BDC Connect.
For most enterprises, BDC and the lakehouse end up working side by side. Adopt BDC where SAP semantics matter, connect it to the lakehouse you keep, and defer only until ownership and connector status are clear.
Frequently Asked Questions
What is SAP Business Data Cloud?
BDC is SAP’s managed data layer that connects SAP and third-party data through a business data fabric. It packages SAP data as governed data products that keep business semantics such as fiscal calendars and hierarchies. Teams then use those products for analytics, planning, data engineering and AI.
Is SAP Business Data Cloud the same as SAP Datasphere?
No. SAP states that BDC is not the same as Datasphere, but Datasphere is a core component of it. Datasphere handles integration and semantic modeling, while BDC adds prebuilt data products, SAP Databricks, AI capabilities and zero-copy sharing with outside platforms such as Snowflake and Google BigQuery.
Does SAP BDC replace SAP BW?
Not immediately. SAP’s path is to lift BW into a private cloud edition, then shift BW artifacts into customer-managed data products, and finally move critical flows to SAP-managed data products. BW 7.5 mainstream maintenance ends in 2027, so BW 7.5 teams usually face this decision before BW/4HANA teams do.
How does SAP Databricks fit into BDC, and can I keep my own Databricks workspace?
SAP Databricks is a Databricks product sold by SAP as part of BDC for data engineering, machine learning and AI on SAP data. You can keep your own Databricks workspace. The two environments share data in both directions through Delta Sharing, with Unity Catalog applying the same governance rules.
Does SAP BDC work with Microsoft Fabric and Power BI?
SAP and Microsoft announced BDC Connect for Microsoft Fabric in November 2025, placing SAP data products in OneLake where Power BI can use them. General availability was planned for Q3 2026, so confirm the current status with SAP and Microsoft before planning production reports around that connector.
Does SAP BDC work with Snowflake and Google BigQuery?
Yes, through BDC Connect. The BigQuery connector became generally available in July 2026 for BDC tenants hosted on Google Cloud and AWS, with Azure-hosted support still coming. SAP announced BDC Connect for Snowflake and an SAP Snowflake solution extension in November 2025 without a stated release date.
How much does SAP Business Data Cloud cost?
SAP does not publish a list price. BDC Core is a subscription measured in Capacity Units that can be spread across services such as Datasphere, SAP Analytics Cloud and SAP Databricks. Intelligent Packages use their own metric. SAP provides a Capacity Unit Estimator, and your account team quotes the final figure.
Is there a free trial of SAP BDC?
Yes. SAP runs a 30-day basic trial at no cost. It runs in a shared tenant with preconfigured data, and some functions are restricted. The trial is useful for learning the interface and data products, but it will not show how your own SAP data and reports behave.
How does SAP BDC support AI and Joule Agents?
BDC supplies the governed data products and the SAP Knowledge Graph that Joule Agents read when they answer questions or take actions. Because the data keeps its business context, agents can work with correct hierarchies and definitions. SAP Databricks also adds tools for building custom models and agents on the same data.
Do I need SAP S/4HANA to use SAP BDC?
SAP describes it as bridging SAP and third-party data sources, and it does not list S/4HANA as a prerequisite. The prebuilt data products and Intelligent Packages depend on specific SAP source applications, though. So check which of your SAP systems are covered before you plan a use case around them.
What is BDC Connect in SAP Business Data Cloud?
BDC Connect is the part of BDC that shares data and metadata with outside platforms without copying it. SAP names Databricks, Snowflake, Microsoft Fabric, Google BigQuery and Amazon Athena as partners. Each connector has its own release status, so confirm the one you need for your hosting cloud.
