Concept card

SAP BW Bridge: The Runtime Inside Datasphere

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 BW Bridge: The Runtime Inside Datasphere?

How SAP BW Bridge actually runs inside a Datasphere tenant: what the SAP transfer tooling carries across, how ECC and S/4HANA ODP extractors keep feeding it unchanged, why custom ABAP must be rewritten against the released API set, and how its objects reach the semantic layer as Datasphere remote tables. Whether to bridge at all is arbitrated on a separate card.

What it is

SAP BW Bridge is a BW/4HANA ABAP runtime provisioned inside an SAP Datasphere tenant. It is not a connector and not an emulation: it is BW — InfoObjects, aDSOs, CompositeProviders, transformations, DTPs, process chains and ABAP routines — running as a managed service under the same subscription as the Datasphere spaces that consume it. This card is the mechanism. Whether to bridge at all, against which alternative and for how long, is arbitrated on the companion card, BW Bridge: The Migration Arbitration.

Where the data enters. The bridge keeps the extraction estate the customer already owns. ODP-based DataSources — the SAP Business Content extractors against ECC and S/4HANA, plus CDS-based and BW-based ODP providers — keep feeding it through the same source-system definitions, with SAP Cloud Connector standing between the cloud tenant and the on-premise system. Nothing in the extractor layer is re-authored. That single property carries most of the bridge's value: the extraction estate is the least documented and most expensive part of a BW landscape to rebuild.

Why it matters

Every migrated CompositeProvider becomes a Datasphere Remote Table, consumable by analytic models, Stories, and Delta Sharing without re-modelling.
Existing ECC/S/4 extractors keep feeding data through the same Source Systems and DataSources the customer has run for years — no re-plumbing required.
It's the wrong choice for greenfield programmes or small, well-documented BW content, where a direct Datasphere re-model is faster and cleaner.

Key points

BW/4HANA runtime embedded in Datasphere — InfoProviders, transformations, DTPs, ABAP exits run as a managed service inside the Datasphere subscription.
Lift-and-shift from on-prem BW/4HANA — SAP-provided migration cockpit moves InfoObjects, aDSOs, CompositeProviders, ABAP code as-is.
ECC / S/4 extractors continue to feed — same Source Systems and DataSources the customer has run for years.
Exposed to Datasphere — every CompositeProvider becomes a Remote Table consumable by analytic models, Stories, Delta Sharing.
Not for greenfield — use native Datasphere when no BW legacy exists; BW Bridge is purely a migration scaffold.
SAP BW Bridge (BW in SAP Datasphere) 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

BW Bridge: A BW/4HANA runtime delivered as a managed service inside a SAP Datasphere tenant; lets customers migrate on-prem BW/4HANA content as-is and expose it to the Datasphere semantic layer.
Migration cockpit: The SAP-provided tool that moves on-prem BW/4HANA objects (InfoObjects, aDSOs, transformations, ABAP code) into a BW Bridge tenant with a structured object inventory and a phased migration plan.
CompositeProvider: A BW/4HANA InfoProvider that unions and joins underlying aDSOs and InfoObjects for query consumption; in BW Bridge, every CompositeProvider can be exposed to Datasphere as a Remote Table.
Remote Table: A Datasphere object that points to data held outside Datasphere — in BW Bridge, an HDP or BTP source, or a Delta Sharing surface — without copying the data.
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 →