Data and Analytics on BTP: Capability Map and Component Overview

JinJin48

SAP Consultant | BTP · S/4HANA · US Global Rollout

May 11, 2026 · 13 min read

Where This Article Sits#

References#

1) The Data & Analytics Landscape#

The BTP Data & Analytics domain is composed of four components. They are not substitutes — each one occupies a distinct architectural layer.

An analytics project almost always involves two or more of these components working in sequence.

2) How It Connects to S/4HANA#

The standard cloud-native pattern places S/4HANA as a source system, not as the analytics tier. Each of the four BTP components plays a defined role downstream of S/4HANA.

SAP S/4HANA (source: business transactions, master data)
        |
        | (replication / extraction)
        v
SAP Data Intelligence Cloud
(ETL/ELT pipelines, streaming, data preparation)
        |
        v
SAP Datasphere
(semantic modeling, data federation, governance)
        |
        +--------------------+
        |                    |
        v                    v
SAP Analytics Cloud    SAP HANA Cloud (standalone)
(BI, planning,         (application backends, custom
 reporting)             high-concurrency workloads)

As of 2025–2026, SAP restructured this stack under SAP Business Data Cloud (BDC), which positions Datasphere as the central semantic layer and SAC as the analytics front end ( community.sap.com →). BDC Connect enables BDC to federate data from Databricks (GA since October 2025), Google BigQuery and Snowflake (H1 2026), and Microsoft Fabric (Q3 2026) without moving data into SAP storage.

Key point: S/4HANA is the source of truth for business transactions. Datasphere is the source of truth for governed, semantically enriched analytics data. These two systems must not be confused, and their models must not be duplicated.

3) Maturity Map#

4) Requirements Checklist#

SAP Datasphere#

Source: sap.com →, help.sap.com →

SAP Analytics Cloud#

Source: sap.com →

SAP HANA Cloud#

Source: help.sap.com →, sap.com →

SAP Data Intelligence Cloud#

Source: sap.com →

5) Decision Criteria#

The three questions to ask first#

Q1. What specific, measurable data problem is this initiative solving?

The Data & Analytics domain is broad enough that vague scope (“we need better analytics”) always expands beyond budget. Force the client to name a measurable outcome — for example, “reduce month-end close cycle from 10 days to 5 days” or “enable self-service reporting for 200 business users without IT dependency.” Without a measurable problem statement, no component selection is defensible.

Q2. Where does the data live today, and who owns it?

The architecture choice between Datasphere, HANA Cloud, and Data Intelligence is heavily driven by data topology. If data is scattered across multiple SAP and non-SAP systems with inconsistent semantics, Datasphere’s semantic fabric is the correct starting point ( sap.com →). If data already lives in a well-governed HANA system and the requirement is application-level analytics, standalone HANA Cloud is more appropriate. Data ownership is a governance prerequisite — without a named data owner, catalog and lineage investments in Datasphere will not be maintained.

Q3. Is there a named internal sponsor with budget authority and a funded license conversation with SAP?

All four components carry non-trivial licensing costs. Initiatives that start without confirmed budget frequently stall when the SAP commercial team presents actual pricing. Confirm that the sponsor has approved the commercial framework before committing to an architecture.

Domain selection by project context#

Source: help.sap.com →

Licensing and cost#

Source: sap.com →, sap.com →, help.sap.com →

Specific pricing is not published in SAP public documentation. All four components require a direct conversation with the SAP account team for current commercial terms.

6) Common Failures#

Failure 1: Treating Datasphere, SAC, and HANA Cloud as interchangeable

A BI reporting requirement needs SAC on top of a data model; that data model lives in Datasphere; Datasphere’s computational layer is HANA Cloud. Conflating these three into one “analytics platform” scope item hides three separate procurement, provisioning, and design workstreams. Make the layered architecture explicit in the scope document from day one.

Failure 2: Data governance delayed until after go-live

Datasphere’s catalog, lineage, and data stewardship features require upfront decisions about data ownership, naming conventions, and KPI definitions ( sap.com →). Teams that defer these decisions to post-launch end up with a platform that no one trusts, because the same metric has different definitions in different reports.

Failure 3: Exception handling omitted from pipeline design

Data Intelligence Cloud and Datasphere integration flows are designed for the happy path. Real source systems produce late-arriving records, schema changes, and duplicate keys. Every integration requirement must include an explicit error handling and retry specification ( sap.com →).

Failure 4: HANA Cloud instance undersized at requirements stage

The default starting configuration is frequently insufficient for production analytical workloads, particularly financial consolidation and high-concurrency OLAP queries. Conduct a sizing workshop at requirements stage using SAP’s published HANA Cloud sizing guidance ( help.sap.com →).

Failure 5: SAC planning scope not bounded

“Planning” is understood differently by finance, supply chain, and HR; each function wants its own model, driver tree, and input form. Scope the planning models by name in the requirements document ( sap.com →).

Failure 6: Live connection vs. import mode decision deferred

Import mode is faster to implement but creates data duplication, complicates governance, and is being phased out in favor of Datasphere-backed storage. Teams that choose import mode without documenting the rationale inherit a technical debt item that becomes harder to address after users are dependent on the imported data.

Failure 7: Third-party DWH integration scheduled before GA

BDC Connect integrations with Google BigQuery, Snowflake, and Microsoft Fabric have staggered GA dates (Databricks GA October 2025; BigQuery and Snowflake H1 2026; Microsoft Fabric Q3 2026) ( community.sap.com →). Check the current BDC Connect roadmap against the project timeline and document the dependency explicitly.

FAQ#

Q: Can we use SAP Analytics Cloud without SAP Datasphere?

Yes. SAC can connect directly to SAP HANA Cloud, S/4HANA, BW/4HANA, and non-SAP sources via live or import connections ( sap.com →). However, SAP’s current strategic direction routes SAC storage and planning persistence through Datasphere. For simple reporting-only use cases with a single source system, a direct SAC-to-HANA connection remains a valid and simpler architecture.

Q: How does this stack apply to an on-premises S/4HANA customer?

All four BTP Data & Analytics components are cloud services. An on-premises S/4HANA connects via SAP Integration Suite or direct OData/RFC connectors. Datasphere supports on-premises sources through Smart Data Integration (SDI) agents that run in the customer’s network and replicate or federate data to the cloud tenant ( sap.com →).

Q: What is the licensing model for SAP Datasphere, and how does it differ from SAP Analytics Cloud?

Datasphere is licensed on a consumption basis through BTP capacity units; cost scales with data volume and query activity. SAC uses a per-user subscription model with separate tiers for BI and planning users — planning licenses are more expensive. SAP Business Data Cloud bundles both into a single offering. Contact the SAP account team for current pricing.

Q: When should we descope SAP Data Intelligence Cloud?

Descope it if integration requirements can be met by Datasphere’s native connectors (SDI, SDA, direct source connections) ( sap.com →). Data Intelligence Cloud adds value specifically when the project requires complex multi-step transformation pipelines, high-volume streaming, or ML model embedding within data flows.

Q: How do we document the data and analytics requirement properly?

A well-formed requirement should specify: source systems and data types; refresh frequency; target consumers; semantic model scope (named entities, KPIs, hierarchies); and governance requirements (data owner, retention, access control). A requirement that states only “provide analytics on sales data” is incomplete. Use the SAP Data & Analytics Advisory Methodology as a checklist ( help.sap.com →).

Q: What is SAP Business Data Cloud and how does it relate to Datasphere?

SAP Business Data Cloud (BDC) is the commercial and architectural package that combines SAP Datasphere, SAP Analytics Cloud, SAP BW modernization tooling, and BDC Connect (third-party DWH federation) ( community.sap.com →). Datasphere remains the semantic layer within BDC. BDC is the preferred deployment model for new greenfield implementations.

Q: When is standalone SAP HANA Cloud the right choice over HANA Cloud embedded in Datasphere?

Use standalone HANA Cloud when the project involves a CAP application requiring transactional write capabilities alongside analytics, when the workload demands concurrency tuning that Datasphere’s managed instance cannot expose, or when extending an existing HANA-based application. For pure data warehousing and analytics, the HANA Cloud embedded in Datasphere is simpler to provision and govern ( help.sap.com →).

Summary#

The BTP Data & Analytics domain is not a single product choice — it is a layered architecture ( sap.com →). SAP Data Intelligence Cloud handles complex integration and pipeline orchestration. SAP Datasphere provides the semantic fabric that gives integrated data business meaning and governance. SAP HANA Cloud supplies the computational engine, either embedded within Datasphere or as a standalone instance. SAP Analytics Cloud sits at the top as the user-facing BI and planning platform. The key consultant discipline is to scope each layer explicitly, confirm the licensing for each component separately, and resist the tendency to treat the entire stack as a single line item in a project plan.

What to Read Next#