fabric mirroring

Hi db042190​,

That changes the picture quite a bit.

For Microsoft’s native SAP Mirroring path, SAP Datasphere is currently part of the architecture. Microsoft documents the flow as:

SAP S/4HANA -> SAP Datasphere replication flow -> ADLS Gen2 -> Fabric Mirroring -> OneLake

The Datasphere replication flow handles both the initial snapshot and subsequent change records, and Fabric then continuously merges those changes into the mirrored database.

Microsoft documents that architecture here: Mirroring SAP in Microsoft Fabric.

So if you do not have SAP Datasphere, I would not expect to be able to enable that exact native SAP Mirroring experience directly against S/4HANA.

You do still have other options though.

If your S/4HANA system exposes data through SAP ODP, Microsoft’s SAP CDC capabilities can extract incremental changes from sources such as ABAP CDS views rather than repeatedly polling the whole source. Microsoft documents that the SAP CDC connector supports S/4HANA and does not rely on simple watermark-based extraction.

That architecture is more along the lines of:

S/4HANA / ODP -> SAP CDC -> Fabric ingestion -> OneLake

rather than native Fabric Mirroring.

Another option is Open Mirroring through one of Microsoft’s partner integrations. Microsoft currently lists solutions such as CData Sync that can mirror SAP sources into Fabric through Open Mirroring.

So I would separate the choices like this:

• Have SAP Datasphere: use Microsoft’s native SAP Mirroring path
• No Datasphere, but SAP ODP/CDS is available: investigate SAP CDC
• Want a mirroring-style experience without Datasphere: evaluate an Open Mirroring partner
• Simple periodic extraction is enough: a normal pipeline/copy approach may still be perfectly reasonable

On your earlier question about telling S/4 users that data has changed, I would also avoid trying to force that notification into the mirroring layer itself. Mirroring/CDC is mainly about capturing and propagating the change. I would usually detect the business-significant change downstream in Fabric and trigger the notification from there.

So no, I would not treat lack of Datasphere as meaning Fabric cannot work with your S/4HANA data. It mainly means the native SAP Mirroring architecture is probably not the route available to you.

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.