Forum Discussion

ati_puri's avatar
ati_puri
Resolver III
7 months ago
Solved

SAP ECC Connector Support in MS Fabric

Hi Team,

 

We are looking towards ingesting huge volumes of SAP ECC data into Fabric. As SAP discontinues OData connectivity with ADF and SAP BDC (Datasphere)connector is coming next year, will SAP mirroring help in this case? We need data replication and validation along with CDC.

 

  • Hi ati_puri 

     

    You can use Qlik Replicate to ingest SAP ECC data. This design is widely used for ECC data. 

     

    • Qlik Replicate can directly connect to the underlying ECC database (e.g., Oracle, SQL Server, DB2, HANA), capturing DML changes via log-based CDC or trigger-based CDC.
    • For log-based CDC, it reads the database transaction logs (redo/online/backup logs).
    • In trigger-based CDC, the system installs INSERT, UPDATE, DELETE triggers on selected source tables, which route change information into a CDC table (e.g., attrep_cdc_changes).

    Ingestion Process Overview

    1. Initial Full Load

      • Qlik performs a full extract of tables selected via SAP Business Groups, loading them into the target i.e. OneLake.
    2. Ongoing CDC (Apply Changes)

      • Changes are captured either via log reads or triggers and applied in near-real-time to the target.
      • Qlik ensures transactional consistency and preserves change order. 
    3. End-to-End Flow

      • Source → Full Load → Change Capture → Apply Changes → Target.
      • Qlik creates CDC artifacts (tables/triggers) automatically if authorized, enabling seamless setup.

    Hope this helps, please appreciate giving a Kudos or by accepting as a Solution!

8 Replies

  • Hello ati_puri 

     

    Microsoft Fabric supports SAP data mirroring in two main ways:

     

    1. Mirroring for SAP via SAP Datasphere (Preview)
      If your ECC data is replicated/exposed through SAP Datasphere, Fabric can create a mirrored SAP database that continuously lands the data in OneLake (Delta format) with an auto‑generated SQL analytics endpoint. This is Fabric’s “zero‑ETL” mirroring route, but it relies on Datasphere as the upstream replication from SAP systems (including ECC) into ADLS Gen2, which Fabric then mirrors. 

    2. “Open Mirroring” via partner connectors (for ECC and S/4HANA)
      Several certified partners can directly replicate ECC tables/objects into OneLake Open Mirroring (near real‑time CDC, batch, etc.) without you standing up your own ETL. Examples include ASAPIO, dab: Nexus, Theobald (Xtract Universal), and Simplement. These tools land data in OneLake and use Fabric’s Open Mirroring interface to keep Delta tables up to date. This is the common approach when you want mirroring‑like behavior from ECC without Datasphere.

    SAP mirroring in Fabric is in Preview; check the “SAP Mirroring” docs and limitations before committing to production SLAs.
     
     
    Hope this helps, please appreciate giving a Kudos or accepting as a Solution
  • v-ssriganesh's avatar
    v-ssriganesh
    Community Support

    Hi ati_puri,

    Thank you for posting your query in the Microsoft Fabric Community Forum, and thanks to deborshi_nag & tayloramy for sharing valuable insights.

     

    Could you please confirm if your query has been resolved by the provided solutions? This would be helpful for other members who may encounter similar issues.

     

    Thank you for being part of the Microsoft Fabric Community.

     

    • ati_puri's avatar
      ati_puri
      Resolver III

      I am looking for a workaround here in absence of SAP connectivity at the moment.

      • deborshi_nag's avatar
        deborshi_nag
        Super User

        Hi ati_puri 

         

        You can use Qlik Replicate to ingest SAP ECC data. This design is widely used for ECC data. 

         

        • Qlik Replicate can directly connect to the underlying ECC database (e.g., Oracle, SQL Server, DB2, HANA), capturing DML changes via log-based CDC or trigger-based CDC.
        • For log-based CDC, it reads the database transaction logs (redo/online/backup logs).
        • In trigger-based CDC, the system installs INSERT, UPDATE, DELETE triggers on selected source tables, which route change information into a CDC table (e.g., attrep_cdc_changes).

        Ingestion Process Overview

        1. Initial Full Load

          • Qlik performs a full extract of tables selected via SAP Business Groups, loading them into the target i.e. OneLake.
        2. Ongoing CDC (Apply Changes)

          • Changes are captured either via log reads or triggers and applied in near-real-time to the target.
          • Qlik ensures transactional consistency and preserves change order. 
        3. End-to-End Flow

          • Source → Full Load → Change Capture → Apply Changes → Target.
          • Qlik creates CDC artifacts (tables/triggers) automatically if authorized, enabling seamless setup.

        Hope this helps, please appreciate giving a Kudos or by accepting as a Solution!

  • v-ssriganesh's avatar
    v-ssriganesh
    Community Support

    Hello ati_puri,

    Hope everything’s going great with you. Just checking in has the issue been resolved or are you still running into problems? Sharing an update can really help others facing the same thing.

    Thank you.