Making Sense of SAP: 16 Questions on Data, BDC, and Modern Analytics

We’ve been hearing the same thing more and more in conversations with customers and organisations navigating SAP: “SAP data is messy”, “What’s going on with SAP Business Data Cloud?”, “It feels complicated”.

At the same time, SAP has been introducing major changes to how SAP data is accessed, governed, and analysed, particularly with SAP Business Data Cloud (BDC), Datasphere, and tighter integration with platforms like Snowflake and Databricks. For many organisations, it’s not always clear what problem SAP is actually trying to solve, or how these pieces fit together.

To unpack this, I sat down with Jorel Digman, our Head of New Business, to answer the 16 questions we’re most often asked about SAP.

1. What do most people misunderstand about SAP data? 

Most people assume SAP data is messy. In reality, it is highly structured. Its complexity simply reflects the complex business processes it supports. 

2. Is that a technology problem or more of a legacy problem? 

It’s primarily a problem of limited understanding. SAP contains tens of thousands of tables because it models diverse business processes. Within their own domain, people usually understand the data well, but cross‑domain understanding is often limited. 

3. When clients say their SAP data is a mess, what are they actually dealing with? 

They are usually referring to how SAP data appears in analytics or management reports. By the time data reaches those reports, it has been extracted, transformed, and often mixed with other sources, sometimes even manually manipulated in Excel. The mess is typically in the extraction and modelling, not the SAP source data itself. 

4. How would you explain SAP Business Data Cloud to a finance or operations leader? 

SAP Business Data Cloud provides SAP‑authored reporting models built on deep understanding of SAP processes. These models get organisations most of the way to meaningful reporting out of the box. BDC also introduces AI‑enabled analytics, allowing faster insights with prebuilt models and AI features. 

5. What problem is SAP trying to solve with BDC? 

Traditionally, analytics systems were separate from SAP and required overnight data extractions. BDC makes SAP data instantly available for analytics, dramatically reducing time and effort to move data and enabling near real‑time insights. 

6. What doesn’t BDC try to do? 

BDC is not designed to be a repository for all enterprise data. It focuses on SAP sources, while enabling easy integration with external big‑data platforms such as Databricks and Snowflake. 

7. BDC isn’t built for a single destination, right? 

Correct. BDC integrates seamlessly with popular cloud data platforms like Snowflake and Databricks, giving customers flexibility to use BDC alongside their preferred data cloud environments. 

8. How should customers think about Snowflake vs. Databricks in relation to BDC? 

The choice typically comes down to cost and in‑house skill sets. Teams strong in Python and code‑first engineering may prefer Databricks; teams focused on SQL‑based warehousing may prefer Snowflake. From a BDC standpoint, both are supported equally well. 

9. Where does the SAP Datasphere fit into all of this? 

Datasphere focuses on preparing SAP data for analytics, machine learning, and AI. Workloads may run in Snowflake or Databricks, but Datasphere governs and models the SAP data and makes it available to those workloads. 

10. Does Datasphere matter more once AI or advanced analytics enter the picture? 

Yes. AI requires high‑quality, trusted data. Because SAP data represents critical business processes, it is essential for AI initiatives. Datasphere provides well-modelled, accessible SAP data to support AI workloads effectively. 

11. What does zero‑copy data change in practice? 

Zero‑copy data allows workloads to access data without moving or duplicating it. It enables rapid provisioning of non‑production environments for development or testing, often in minutes, without the overhead of traditional data cloning. 

12. If an organisation is still on SAP ECC, do they need to wait to use BDC? 

No. BDC works with ECC as well as S/4HANA. While S/4HANA provides additional features, ECC customers can already benefit from BDC’s predefined models and data‑management capabilities. 

13. If an organisation has shifted to S/4HANA, what changes for their data architecture? 

S/4HANA combined with BDC creates a fully integrated, real‑time data platform. This enables near real‑time analytics, embedded AI capabilities, and tighter coupling between operational systems and analytics. 

14. What’s the biggest myth to clear up? 

The myth that SAP data is difficult. With the right expertise and accelerators, both those built into BDC and those provided by partners, working with SAP data can be efficient and highly effective. 

15. What is one thing companies walk away with from Snap Analytics’ SAP BDC Readiness Workshop? 

A clear roadmap showing where BDC will deliver business value. The workshop highlights opportunities to move beyond traditional BI reporting and begin leveraging AI‑enabled analytics supported by BDC’s accelerators and governance features. 

16. Is the retirement of BW 7.5 a good opportunity to evaluate future direction? 

Yes. BDC’s bridge functionality allows organisations to maintain their existing BW backend while modernising the front end through BDC. This enables a controlled, phased migration from BW to BDC without a disruptive big‑bang transition. 

Extracting data from SAP: CDS views or tables?

For every SAP data-centric data platform, data engineering teams must decide whether to extract data from Core Data Services (CDS) views or directly from SAP tables. While CDS views offer significant advantages in data modeling—ensuring that models are fit for purpose—they are not always the best option. Many organisations may lack the right technology, skills, or processes to fully leverage CDS views for data extraction. Having gone through many implementation projects myself, and prompted by a post on Linkedin from my friend and colleague Ronald Konijnenburg, I thought I’d share my views on the topic here. 

What Are SAP CDS Views?

SAP CDS views are a powerful abstraction layer that allows for defining data models within SAP applications. They simplify data access and help organise SAP data for analytics consumption. For an introduction to CDS views, see for example this article on the SAP community site. However, despite their benefits, CDS views are not always the best choice for data extraction. Below, we explore the key technological, skill-based, and process-related challenges associated with CDS view-based extraction compared to table-based extraction.

1. Technology

A common approach for extracting data from source system is the use of a Change Data Capture mechanism. This mechanism is widely available for databases, using either trigger- or log-based replication. Both SAP and third parties provide out-of-the-box solutions for a wide range of databases and applications, including SAP ERP. These methods enable efficient, incremental data extraction.
CDS views, however, are SAP proprietary, and CDC mechanisms are not readily available in third-party tools.  To the best of my knowledge, only SAP DataSphere and SNP Glue offer an efficient, CDC based extraction for CDS views.
OData extraction is available for CDS views, but it does not scale well for enterprise-level workloads. Large-scale data extractions using OData often run into performance limitations, making direct table extraction a more viable approach for enterprises handling high data volumes.

2. People (Skills)

Maintenance on CDS views require SAP-specific skills, which are not always available in data & analytics teams. This skill gap can create a bottleneck when changes or troubleshooting are required. Many CDS views are not delta-enabled, meaning they cannot support incremental data extraction. This makes them unsuitable for large-scale data pipelines that depend on efficient updates. Not all SAP tables are included in CDS views. If a required table is missing from existing CDS views, the engineering team must either create a new CDS view or revert to direct table extraction.

3. Processes

Changes to CDS views must follow the SAP S/4HANA change process, which is significantly more rigorous than data platform governance. This level of control is justifiable, given that SAP is the core system of record in most enterprises, but it means even small adjustments can take a long time to implement. In contrast, adding a table to an extraction process can be as simple as selecting a checkbox, making it a far quicker and more flexible option.

Conclusion

If you are on a technology stack which supports CDC for CDS views and you have a team comfortable with the maintenance of CDS views and the governance processes around it, then using CDS views for data extraction can give you better data products more quickly. 
If you wish your data & analytics team to be independent from the SAP governance processes, you don’t have an ETL tool supporting CDC for CDS views and you don’t have easy access to SAP skills, then you are probably better of with direct table extraction. It’s often said that creating models on SAP tables is very difficult as SAP has several hundreds of thousands of tables.  You only need a fraction of those though, and it really is not that complicated to create a data model suitable for analytics. The initial hundred or two hundred tables will easily support the first use cases and even for larger implementations I often see fewer than a thousand tables being used.  

With the considerations outlined in this article, organisations can prioritise and score the different approaches and choose the data extraction strategy that works best for them.