Moving SAP S/4HANA Data to a Third-Party Lake, Hourly: What Changed and What It Costs You
ODP-RFC is now technically blocked. Here is which extraction paths still work for SAP data lake integration, and where the licensing bill really lands.
Quick answer: Since June 9, 2026, SAP support packages block third-party ODP-RFC calls. Hourly extraction from S/4HANA to Databricks, Snowflake, Amazon S3 or Azure Data Lake Storage is still possible through Datasphere replication flows, Business Data Cloud with Delta Sharing, ODP via OData, SLT or a native CDS rebuild. Each path has different speed, cost and licensing trade-offs.
Why Your Data Pipeline May Already Be Broken
If you are planning or running a SAP S/4HANA implementation, the data pipeline strategy you sketched six months ago may no longer work. The usual method for pulling delta data out of S/4HANA and into a third-party lake relied on ODP-RFC. As of June 9, 2026, that framework is not just unsupported; it is technically blocked. A security patch validates incoming ODP-RFC calls and rejects those that are not SAP-internal, so a connector built on it goes silent when your system applies its next support package.
This guide is for architects, data engineers and IT leaders who need a clear picture of sap data integration today: what happened, which extraction paths are legitimate, and what each option costs. Whether you run on-premise S/4HANA or are moving to SAP S/4HANA Cloud, the details below help you decide before you find out the hard way. Our consulting team supports this work end to end through our data integration services.
What Is ODP-RFC and Why Did It Dominate SAP Data Lake Integration?
The Operational Data Provisioning (ODP) framework was designed by SAP for delta-capable extraction. Called over the Remote Function Call (RFC) protocol, it let third-party tools read only changed records instead of full data sets. A connector could ask, “Give me everything that changed in the last hour,” and get exactly that.
Azure Data Factory’s SAP CDC connector, Qlik Replicate, Fivetran’s SAP module and most enterprise ETL tools built on this interface. It was fast, delta-native and broadly supported, which made it the default way to move SAP data into a lake for years.
The ODP-RFC Enforcement Timeline
SAP signalled this change for years. Many teams treated each step as a warning rather than a deadline, which is why June 2026 caught so many pipelines off guard.
| Date | What happened |
|---|---|
| 2022 | SAP Note 3255746 first described third-party ODP-RFC usage as “unsupported.” |
| February 2024 | The wording hardened to “not permitted.” Still a policy statement, not enforcement. |
| April 2026 | Version 11 of the note explicitly prohibits any customer or third-party use, on-premise or private cloud. |
| June 9, 2026 | Enforcement goes technical. A patch in support packages blocks ODP-RFC calls that are not SAP-internal. |
Important nuance: the block targets the ODP Data Replication API over RFC only. Plain RFC or BAPI table reads, BW OpenHub extraction and DeltaQ are untouched. SAP’s self-assessment tool (Note 3439624) lets you check your landscape before the next support package lands.
What Is a Data Lake and Why It Matters for SAP
If you are asking what is a data lake: it is a central store that keeps raw and curated data in open formats such as Parquet, typically on Amazon S3, Azure Data Lake Storage, Databricks or Snowflake. An sap data lake setup brings S/4HANA transactions together with non-SAP sources for analytics and machine learning, away from the core ERP. Teams also use a hana data lake inside SAP’s own cloud stack, and the right data lake model (raw, cleaned and business-ready layers) keeps costs and governance under control.
Choosing among data lake vendors and data lake solutions is easier once you know which extraction path your s4hana integration can legally use. Most real landscapes mix sap and non-sap tools, with SAP handling governed access and partners handling orchestration and analytics.
What Still Works for Hourly SAP Data Lake Integration
Hourly extraction remains achievable. Each alternative trades off speed, cost, vendor dependency or build effort.
| Approach | How it works | Fit for hourly |
|---|---|---|
| Datasphere Replication Flows | SAP’s recommended path. Pushes data to a lake as Parquet files, no ODP-RFC. | Good, fastest to deploy |
| Business Data Cloud / Delta Sharing | Zero-copy, governed sharing. SAP’s long-term direction. | Good, built for the long haul |
| ODP via OData | Same delta mechanism over a compliant transport. Roughly 10x slower. | Works, watch volume |
| SLT (trigger-based) | Not ODP-RFC, so unaffected. Lake writes usually need staging or middleware. | Viable, extra middleware |
| Native CDS / OData rebuild | Most build effort, never touched the deprecated interface. | Good, most vendor-independent |
| Direct HANA DB reads | Bypasses the application layer. Creates serious licensing exposure. | Risky |
Datasphere replication flows: the recommended fast path
For most teams that need compliant lake extraction quickly, SAP Datasphere replication flows are the fastest route to production. Data lands as Parquet in your lake with native delta handling. The trade-off is capacity-unit licensing that scales with volume, so model consumption before you sign off on hourly loads of large tables.
Business Data Cloud and Delta Sharing: the strategic path
SAP Business Data Cloud with Delta Sharing gives governed, zero-copy access instead of physically moving data. It removes replication overhead, which helps with large tables and data sovereignty. The product is still maturing and availability depends on your contract, but for a net-new architecture or an S/4HANA Cloud migration it is worth serious evaluation.
ODP via OData: compliant but slow
OData uses the same delta mechanism over a transport SAP has not restricted, but expect roughly a 10x drop in speed. That is workable for narrow, low-volume hourly jobs. It is a bottleneck for large tables such as BKPF, BSEG or VBAK at scale, so benchmark your peak hourly volume first.
SAP S/4HANA to Snowflake and Databricks Integration
For sap s/4hana to snowflake integration, the most direct compliant route is a Datasphere replication flow that writes Parquet to cloud storage, which Snowflake or Databricks then ingests. Delta Sharing avoids copying altogether. Teams also ask about parquet to sap hana real-time integration tools for the return trip; these combine change-data-capture or streaming services with Datasphere or SAP HANA Cloud, and true real time depends on latency, volume and licensing. Whatever the target, confirm your vendor has a non-ODP-RFC path live today.
Unsure which extraction path fits your landscape?
Get a free, no-pressure architecture and licensing review from a certified SAP partner.
Where the Licensing Bill Actually Lands
This is where surprise invoices come from, and exposure sits in several places at once.
HANA license tier
A runtime license covers only SAP-licensed software. A third-party tool reading the HANA database directly needs a full-use license priced by memory, often a six-figure gap.
SLT licensing
SLT is licensed separately unless your target system bundles it. Feeding a CDC connector that writes to a non-SAP target usually triggers the full license.
Datasphere and BDC capacity units
More data moved, more often, means higher consumption. Model hourly jobs across large entities against your contracted capacity.
Digital and indirect access
Read-only analytics replication generally avoids document-based fees, but verify your contract, especially under RISE or GROW with SAP.
Vendor certification matters too. SAP’s partner rules now name certain extraction technologies as prohibited. Ask connector vendors whether a non-ODP-RFC path has shipped, not whether it is “on the roadmap.” A roadmap is not a pipeline that runs today.
Special Considerations for SAP S/4HANA Cloud Customers
The enforcement applies equally to public cloud and RISE-managed private cloud, but remediation differs. Public edition customers cannot easily install middleware like SLT, so Datasphere replication flows and Delta Sharing are the practical options. Review what your subscription already includes before buying more capacity; some RISE customers hold an unused Datasphere entitlement. Retailers planning a similar move can also read our guide on SAP Intelligent ERP public cloud in 2027.
The Practical Sequence: What to Do This Week
- 1Run the SAP self-assessment (Note 3439624). Find out whether anything uses ODP-RFC before the next support package arrives. It takes under a day.
- 2Confirm your licensing in writing. Get clarity on HANA tier, SLT entitlement and any bundled Datasphere or BDC capacity.
- 3Pick an architecture for your situation. Replication flows to move fast, Delta Sharing for a long horizon, native CDS for independence, ODP-OData as a short bridge.
- 4Get vendor statements. Ask ETL and connector vendors to confirm in writing a compliant path is available on your current contract version.
- 5Verify before migrating to S/4HANA Cloud. Let the target architecture guide your extraction design so you do not build a bridge you must replace in six months.
Frequently Asked Questions
The Bottom Line
Hourly extraction from S/4HANA to a third-party lake is not going away, but the interface most of the market used just became unavailable. Teams that handle this smoothly almost always know before they build. Treat the ODP-RFC change as a forcing function to get your data lake integration architecture right, and let the extraction conversation happen before an S/4HANA Cloud contract is signed, while you still have leverage.
The tools exist, the paths are clear and compliance is achievable. Run the right checks, ask vendors the right questions and lock in licensing in writing. Explore our ERP for retail industry solutions or talk to 2iSolutions today.
Fix Your SAP Data Pipeline Before It Goes Silent
Talk to 2iSolutions for an honest assessment of the extraction path, licensing position and architecture that fit your landscape.