Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Hello everyone. I am new to the forum. The data of my organization resides in SAP S/4 HANA (Public Cloud version) and we would like to extract the data into Fabric for analytics and reporting.
Does anyone have experience in this?
Does the built-in SAP HANA connector support the S/4 HANA Public Cloud version?
I have seen many discussion on importing data from SAP, but none mentioned about the Public Cloud version explicitly.
Thanks in advance!
Solved! Go to Solution.
Hello @chinian811
Hope this helps - please appreciate giving a Kudos or accepting as a Solution!
Hi @chinian811,
Thank you @deborshi_nag for your response to the query.
Along with the information already provided, here are a few key practical points you may want to mention to the customer:
Authentication & security: S/4HANA Public Cloud requires API-based access, so you’ll need to coordinate with your SAP admin to set up Communication Users, Communication Systems, and Communication Arrangements. Only approved APIs and CDS views are accessible.
Data scope: Not all tables or fields are available in the Public Cloud. Reporting is typically based on released CDS views, which may need to be checked to ensure they meet specific requirements.
Performance & data volume: OData extraction works best for incremental or specific datasets and isn’t intended for large-scale replication. For high volumes, consider Datasphere or certified SAP partners.
Change data capture (CDC): OData APIs don’t offer native CDC. Incremental updates rely on delta-enabled CDS views or timestamp filters.
Licensing & roadmap: Some integrations, like SAP Datasphere to Fabric, may depend on license or preview status, so it’s important to confirm availability and SLAs before using in production.
Thank you.
Hi @chinian811,
Following up to check whether you got a chance to review the suggestions given. If the issue still persists please let us know. Glad to help.
Thank you.
Hi @chinian811,
In addition to the OData APIs and Datasphere options already mentioned, another approach to consider — especially for modular and event-driven integration — is using SAP Event Mesh with Azure Event Grid or Azure Logic Apps.
Event-Driven Integration:
If your S/4HANA Public Cloud tenant is configured with Event Mesh, it can emit business events (e.g., SalesOrder.Created, BusinessPartner.Changed, etc.). These can be routed to Azure Event Grid, triggering downstream workflows in Azure Data Factory, Logic Apps, or Fabric Pipelines.
This pattern is useful for:
Near real-time integration
Lightweight processing of specific business events
Reducing the need to pull full datasets periodically
Fabric can then use event-driven triggers to ingest the data or fetch details via OData APIs just-in-time.
Note: This requires coordination with your SAP BTP admin and setup of communication scenarios that enable outbound events from S/4HANA Public Cloud.
If this post helps, then please appreciate giving a Kudos or accepting as a Solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi @chinian811,
We haven’t heard from you on the last response and was just checking back to see if your query was answered.
Otherwise, will respond back with the more details and we will try to help.
Thank you.
Hi @chinian811,
Thank you @deborshi_nag for your response to the query.
Along with the information already provided, here are a few key practical points you may want to mention to the customer:
Authentication & security: S/4HANA Public Cloud requires API-based access, so you’ll need to coordinate with your SAP admin to set up Communication Users, Communication Systems, and Communication Arrangements. Only approved APIs and CDS views are accessible.
Data scope: Not all tables or fields are available in the Public Cloud. Reporting is typically based on released CDS views, which may need to be checked to ensure they meet specific requirements.
Performance & data volume: OData extraction works best for incremental or specific datasets and isn’t intended for large-scale replication. For high volumes, consider Datasphere or certified SAP partners.
Change data capture (CDC): OData APIs don’t offer native CDC. Incremental updates rely on delta-enabled CDS views or timestamp filters.
Licensing & roadmap: Some integrations, like SAP Datasphere to Fabric, may depend on license or preview status, so it’s important to confirm availability and SLAs before using in production.
Thank you.
Hello @chinian811
Hope this helps - please appreciate giving a Kudos or accepting as a Solution!