Forum Discussion
Resolver IIISAP ECC Connector Support in MS Fabric
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
Initial Full Load
- Qlik performs a full extract of tables selected via SAP Business Groups, loading them into the target i.e. OneLake.
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.
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!
Community SupportHi 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.
Resolver IIII am looking for a workaround here in absence of SAP connectivity at the moment.
- 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
Initial Full Load
- Qlik performs a full extract of tables selected via SAP Business Groups, loading them into the target i.e. OneLake.
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.
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!
- ati_puri
Thanks deborshi_nag for the workaround. Could you please also let me know the cost involved for the above process or help me provide details around the efforts, that would be great.
- deborshi_nag
Hi ati_puri
You'd have to factor in the cost of setting up Qlik Replication server on a virtual machine. Aside to the cost of VM on Azure, Qlik Standard has CDC capabilities, so it should work for your requirement. The pricing model depends on data volume - it's best you get in touch with their sales team.
For a small - medium scale deployment it can take between 10 - 12 weeks, including initial load, CDC configuration, incremental load and testing.
Hope this helps, please appreciate giving a Kudos or accepting as a Solution!