Concept card

SAP BDC Connect — Standard Service for Partner Integrations

As of 2026-07-24T14:00:00Z

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 BDC Connect — Standard Service for Partner Integrations?

BDC Connect standardizes what used to be a bespoke connector project per partner — enforcing authentication, schema conformance, lineage propagation, and access-policy inheritance at the integration boundary, across three dated hyperscaler windows.

SAP BDC Connect is the standard integration service SAP introduced to give external data platforms a governed, non-bespoke way to join Business Data Cloud. Before this service existed, every partner integration — connecting a Databricks workspace, a Fabric lakehouse, or an AWS data estate to SAP's semantic layer — required a custom-built connector project: bespoke schema mapping, bespoke authentication, bespoke lineage tracking, repeated for every partner and every customer. BDC Connect replaces that pattern with a single contract: a partner platform registers as a BDC endpoint once, and gains bidirectional, governed access to SAP Data Products and Knowledge Core semantics under rules SAP enforces centrally rather than rules each integration reinvents.

What the service actually enforces

Why it matters

The four enforced contract points are specific: SAP IAS authentication (no custom credential stores), schema-drift rejection at the gateway, lineage propagated back to Knowledge Core, and Datasphere access controls inherited into the partner platform.
Policy inheritance is concrete and testable: a Fabric user lacking rights to a Cost Center in Datasphere cannot query it through Fabric either — access control follows the data, not the tool.
The three-hyperscaler timeline is dated and has already moved once: Databricks Enterprise today, Microsoft Fabric originally Q2 2026 — confirmed slipped to the second half of 2026 (Q3 2026) at Sapphire in May 2026 — and AWS Q3 2026. A customer's hyperscaler choice directly determines when BDC Connect becomes usable for them, and the Fabric slip is a live example of why dates need re-checking before a proposal goes out.

Key points

BDC Connect = standard technical service for external data platform integration into BDC — not a commercial model (that is Solution Extension).
Databricks Enterprise = first partner, available today; register workspace as BDC endpoint, consume SAP Data Products as Delta-native tables.
Microsoft Fabric = originally targeted Q2 2026, confirmed slipped to the second half of 2026 (Q3 2026) at SAP Sapphire, May 2026 — not yet GA as of 2026-08-16; Fabric Lakehouse + OneLake become first-class BDC endpoints enabling Power BI consumption of BDC SAP semantics without ETL once it lands.
AWS = Q3 2026; S3 (Lake Storage), Glue (catalogue), Redshift (analytics) join the BDC fabric for AWS-anchored customers.
Four technical contracts enforced at the integration boundary: authentication (SAP IAS), schema conformance, lineage propagation back to Knowledge Core, and policy inheritance from Datasphere Data Access Controls.
Raw data stays in the partner platform; SAP semantic layer is shared via Knowledge Core — the partner platform is a compute and storage extension, not a data migration target.
SolEx vs BDC Connect distinction: SolEx = commercial (SAP sells product, single PO); BDC Connect = technical (platforms interoperate, separate vendor contracts). A customer can have both simultaneously.
Treat BDC Connect as the multi-cloud answer for customers unwilling to commit to a single hyperscaler or with pre-existing cross-platform investments.
Policy inheritance is the governance differentiator: a Fabric user without Datasphere access to a Cost Center cannot query it through Fabric — access control does not require re-specification at each platform.
Lineage propagation means every Databricks or Fabric transformation on a SAP Data Product is auditable end-to-end in Knowledge Core — satisfying data lineage requirements without a separate metadata catalogue project.

Terms used on this page

BDC Connect: The standard technical integration service in BDC that allows external data platforms (Databricks, Microsoft Fabric, AWS) to register as governed endpoints, consume SAP Data Products, and push enriched outputs back to Knowledge Core under a unified authentication, schema, lineage, and policy contract.
BDC endpoint: A registered external platform instance (e.g. a Databricks workspace, a Fabric Lakehouse, an S3 bucket) that BDC Connect treats as a first-class compute or storage node within the BDC architecture.
SAP Data Product: A published, governed data set in BDC with a defined schema, access controls, SLA, and lineage — the unit of data exchange that BDC Connect partners consume and enrich.
Knowledge Core: The semantic and governance layer in BDC — houses Datasphere (business entity definitions, Data Access Controls, virtual tables) and SAC (analytics and planning surfaces); BDC Connect partners read from and write back to Knowledge Core.
Policy inheritance: The BDC Connect mechanism by which access controls defined in Datasphere Data Access Controls automatically apply to data flowing into partner platforms — a Fabric user cannot access data their Datasphere role does not permit, without any re-specification in Fabric.
Lineage propagation: The BDC Connect mechanism by which any transformation a partner platform (Databricks job, Fabric pipeline) applies to a SAP Data Product automatically records its lineage in Knowledge Core, enabling end-to-end audit without a separate metadata catalogue.
Schema conformance gate: The BDC Connect integration boundary check that validates the partner platform receives SAP Data Products in their published schema; schema drift or version mismatch is rejected at the gateway rather than silently corrupting downstream analytics.
Multi-cloud posture: Customer architectural stance where data services are distributed across multiple hyperscalers (Azure for Fabric, AWS for Redshift, GCP for BigQuery); BDC Connect enables Knowledge Core governance to span this posture without requiring consolidation onto a single cloud.

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 · the facts worth quoting.

Open in the app →

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.