CTM: Microsoft Fabric / OneLake from One Cockpit addresses a problem most SAP landscapes know too well: Fabric investments idle when SAP feeds are late, opaque, or manually rebuilt.
Fabric connections are maintained once; SQL and REP pipelines can target the lake by name — same monitoring habits as on-prem SQL Transfer.
CTM completes the cloud leg so analytics teams are not stuck exporting CSV from SAP manually.
Capabilities you use in iDataEngine
- Load statistics dashboard
- Fabric / OneLake connection maintenance
- Job schedule and alert via MF
- Health probe on connections
- Structured Data Lake loads
- Incremental watermark resume
Recommended workflow
- Configure source objects, fields, mappings, or rules using session language and customer/system context.
- Save and capture the generated URL, job ID, or snapshot reference in your change record.
- Run Test (iDataView Test, SQL First Row, API Test Service, or AG scan) before scheduling or publishing.
- Extend the same definition to the next channel (API, SQL, MF, BI) without redesigning from scratch.
Real-world scenario (2025)
Controlling loads actuals from SAP into OneLake for Power BI enterprise datasets — CTM job history proves refresh for audit.
Why it matters
Analytics on OneLake only matter if SAP operational truth arrives on schedule — CTM is that bridge.
Your next step is a controlled pilot: Test in cockpit, save with evidence, then extend to the next channel without redesign.