Concept card

SAP Datasphere — Connections Catalogue

As of 2026-07-23

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is SAP Datasphere — Connections Catalogue?

Whether a Datasphere use case is a 2-hour connector config or a 6-week custom integration project hinges entirely on which of the four connector categories the source system falls into.

What it is

The Datasphere Connections Catalogue is the set of source-system connectors Datasphere ships out of the box — the integration surface that lets a Datasphere space ingest, federate, or replicate data from anywhere the customer's data actually lives. For SAP analytics consultants, knowing what is in the catalogue (and what is not) decides whether a planned analytics use case is a 2-hour configuration or a 6-week custom integration project.

The four connector categories. SAP source connectors — S/4HANA Cloud + on-premise (via SAP Datasphere Agent), BW/4HANA, BW 7.x, ECC, HANA Cloud + on-premise, Ariba, Concur, SuccessFactors, Fieldglass; the SAP family is covered comprehensively, and SAP-to-SAP connections come with SAP-engineered semantic understanding (delta extraction, business content, hierarchy preservation). Cloud database connectors — Snowflake, Google BigQuery, Microsoft Azure SQL, Amazon Redshift, Databricks, MongoDB Atlas, PostgreSQL on cloud; one-click configuration with managed credentials. File-source connectors — Amazon S3, Azure Data Lake Storage Gen2, Google Cloud Storage, SFTP; for landing CSV/Parquet/JSON files into Datasphere. Application connectors — Salesforce, Workday, ServiceNow, Google Analytics 4, Adobe Analytics; primarily for marketing and HR analytics use cases not covered by SAP-source connectors.

Why it matters

SAP-to-SAP connections carry SAP-engineered semantic understanding (delta extraction, hierarchy preservation) that generic cloud or file connectors don't.
Choosing remote table vs. replication flow vs. data flow trades live-query simplicity against performance and transformation needs.
Legacy on-premise databases (old Oracle, Informix, mainframe DB2) and niche SaaS applications aren't in the catalogue — they need Smart Data Integration adapters or a third-party ETL tool.

Key points

Four connector categories — SAP sources (S/4, BW, HANA, Ariba, SuccessFactors, etc.), cloud databases (Snowflake, BigQuery, Azure SQL, Databricks), file sources (S3, ADLS, GCS, SFTP), application sources (Salesforce, Workday, ServiceNow, GA4).
SAP-to-SAP connections — SAP-engineered semantic understanding (delta, business content, hierarchy preservation); the strongest connector class.
Three usage patterns — Remote Table (federation, live query), Replication Flow (periodic full/delta), Data Flow (ETL-style transform-on-ingest).
Not in catalogue — older on-premise databases (Oracle 8i, Informix, DB2 mainframe), specialised SaaS; need SDI custom adapters or external ETL.
First-question decisive — knowing the catalogue cold answers 'can we connect to X?' in 30 seconds, sets project schedule correctly.
SAP Datasphere — Connections Catalogue is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.
Use current SAP, analyst, study, KG, and news signals as evidence, not decoration.
Separate verified facts from directional trends and modeled assumptions.
Define owner, metric, threshold, support path, and rollback before scaling.

Terms used on this page

Connections catalogue: The set of source-system connectors Datasphere ships out of the box — SAP sources, cloud databases, file sources, application sources; the integration surface that determines what data Datasphere can natively reach.
Datasphere Agent: An on-premise component that lets Datasphere connect to on-premise SAP systems (S/4HANA on-prem, BW 7.x, HANA on-prem) and on-premise databases through a customer-controlled gateway; required for any non-cloud SAP source.
Smart Data Integration (SDI): HANA's custom-adapter framework — the fallback for sources not in the Datasphere connections catalogue; lets developers write custom adapters in C++ or use community adapters.
Business Content: SAP-pre-built data models, extractors, and transformations for SAP source systems; the SAP-to-SAP connections inherit Business Content semantics, dramatically reducing modelling effort for SAP-source analytics.
Decision owner: The accountable person who accepts the trade-off and funds the next action.
Semantic contract: The shared definition of business terms, metrics, entities, and access rules used by tools and teams.
Control plane: The layer that applies policy, access, lineage, monitoring, and escalation across the operating model.
Evidence grade: A label that separates verified fact, directional signal, modeled assumption, and field observation.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks.

Open in the app →