Key takeaways
- Only one mechanism is affected: the ODP Data Replication API via RFC (ODP-RFC), when non-SAP applications use it to extract data from SAP. RFC as a protocol remains permitted.
- Technically enforced since June 9, 2026: an SAP security update rejects unpermitted ODP-RFC calls. SAP Note 3255746 defines which usage is permitted.
- Affected: the SAP CDC connector in Azure Data Factory and third-party tools with an ODP-RFC connection, such as Qlik Replicate or Talend.
- Not affected: the SAP Table and SAP OData connectors, table and CDS view extraction via RFC, DeltaQ, BAPIs and function modules.
- Alternatives in Fabric: Mirroring for SAP Datasphere (GA), Copy job for SAP via ABAP Add-On and Open Mirroring partners. SAP’s strategic recommendation is SAP Business Data Cloud.
- Transition period: a temporary opt-out lets existing ODP-RFC usage continue until the end of 2026, at the customer’s own risk.
If you move SAP data into a data lake, a warehouse or Microsoft Fabric, you have probably heard it already: “SAP has banned RFC.” The claim is making the rounds on LinkedIn, but it is not accurate. SAP Note 3255746 does not restrict RFC as a protocol. It restricts one specific access path: the ODP Data Replication API via RFC (ODP-RFC).
Timeline: How SAP Note 3255746 Has Tightened Since 2022
The history of SAP Note 3255746 shows a slow but consistent tightening:
- October 17, 2022: The first version of SAP Note 3255746 declares the use of the ODP-RFC modules by customer and third-party applications “not supported”.
- February 2024: The wording is tightened to “not permitted”.
- April 13, 2026: With SAP Note 3439624, SAP publishes a self-assessment tool that inventories ODP-RFC usage in the system.
- April 2026: The updated version of SAP Note 3255746 (as of April 21) announces the technical block for SAP Patch Day on June 9.
- June 9, 2026 (SAP Patch Day): A security update (SAP Notes 3635619 and 3748819) checks incoming ODP-RFC calls and rejects unpermitted ones with the message “Unknown caller; Call rejected”.
If you have applied the update, unpermitted calls are already being blocked unless an opt-out is active. Postponing the update is not a solution, because it is a regular security update. According to Theobald Software, SAP’s security team rates the previous third-party use of ODP-RFC as a medium security risk, which is given as the reason for the tightening.
Opt-out until end of 2026: The report RODPS_REPL_SECUREACCESS_OPTOUT (SAP Note 3731818) lets you temporarily lift the block, at your own risk. At the end of the year, SAP intends to switch off the opt-out permanently with a further note. This is migration time, not a deadline extension.
What SAP Note 3255746 Actually Blocks
Exactly one mechanism: the ODP Data Replication API via RFC, when a non-SAP application calls it. If your extraction path depends on it, it is affected.
The most prominent case in the Microsoft stack is the SAP CDC connector in Azure Data Factory. It calls the ODP API via RFC modules and stops delivering data after the security update; Microsoft points this out in the ADF documentation itself. The same applies to any third-party tool whose CDC is built on ODP-RFC, including the ODP connectors of Qlik Replicate and Talend. So the problem is not specific to Microsoft.
Related SAP Notes: Two further notes often come up in the same context: 382318 (RFC_READ_TABLE is not intended for productive use) and 2971304 (SAP does not certify redo-log-based replication from HANA). Both concern access paths other than ODP-RFC, but they follow the same trend: SAP is closing access paths that are not officially supported.
What Still Works
This is exactly where the myth “RFC is banned” causes damage: teams rebuild pipelines that are not affected at all. SAP Note 3255746 does not cover:
- Table and CDS view extraction via RFC (for RFC_READ_TABLE, however, Note 382318 applies, see above)
- DeltaQ, BAPIs and function modules
- ODP via OData: SAP’s self-assessment tool lists this path as permitted
- Anything that does not call the RFC modules of the ODP Data Replication API
Xtract Universal: What Changes for Theobald Customers
In short: the tool stays, the license remains valid, and you do not have to rip anything out. What changes is the extraction component you use. Only the ODP via RFC extraction type is affected. All other components are compliant paths, including ODP via OData:
| Component | Use case |
|---|---|
| Table (incl. CDS Views) | Tables and ABAP CDS views |
| Table CDC | Incremental replication at table level |
| DeltaQ | DataSources and extractors |
| BW Cube | BW extractions |
| ODP (OData) | Fallback when nothing else fits; noticeably slower for large volumes, and SAP Basis must provide an OData service per object |
Xtract also includes a compliance view (F6) that lists all extractions still running via ODP. The approach: run the compliance check, list the affected jobs and map each job to the right successor component, rather than switching everything to OData across the board.
Microsoft Fabric & ADF: The Right Alternatives to ODP-RFC
In the Microsoft stack, one connector is affected, not all of them.
SAP CDC Connector (Azure Data Factory): Affected
It is based on ODP-RFC and stops delivering data as soon as the security update is applied in the SAP system. The SAP Table and SAP OData connectors are not affected.
Mirroring for SAP Datasphere (GA)
Supported by SAP and without third-party ODP-RFC: a Datasphere replication flow extracts the snapshot and changes from the SAP source system and lands them in ADLS Gen2, from where Fabric continuously mirrors them into OneLake. Supported sources are S/4HANA, ECC, BW/4HANA, BW and Datasphere itself. A Datasphere license is required, and the export incurs costs for Premium Outbound Integration.
Copy Job for SAP via ABAP Add-On
Publicly available since Microsoft Build 2026: an ABAP add-on provided by Microsoft and installed in the SAP system via transport. It reads data with ABAP SQL on the application server and does not use the ODP-RFC API. Both full and incremental (watermark-based) copies are supported. You also need an on-premises data gateway (May 2026 version or later) with the SAP .NET Connector (NCo) and a Fabric capacity. Supported systems: S/4HANA and BW/4HANA (all versions), ECC 6.0 EhP8 and BW 7.50, each on NetWeaver 7.50; NetWeaver 7.40 and earlier are not supported.
SAP Business Data Cloud Connect for Microsoft Fabric (Announced at Microsoft Ignite 2025)
Announced at Microsoft Ignite in November 2025: a bi-directional zero-copy connection through which SAP Business Data Cloud (BDC) and Fabric share data products instead of physically copying them. General availability was originally planned for the third quarter of 2026; according to a note in the SAP Community, it is now expected at the end of the first quarter of 2027. BDC is a prerequisite; according to Microsoft, SAP’s terms of use may restrict further use of the data.
Open Mirroring Partner Solutions
SAP-certified partners from Microsoft’s Open Mirroring ecosystem, such as Theobald Software, bring SAP data directly into OneLake, also without ODP-RFC.
What the Migration Really Costs
“Compliant” does not mean free. The costs depend on the path you choose:
- Theobald license: unchanged. Converting the jobs costs engineering time, but no additional license fees.
- OData fallback: indirectly more expensive. According to a Microsoft answer on Microsoft Q&A, OData is around ten times slower than ODP-RFC. That means more compute and less up-to-date data.
- Copy job with ABAP Add-On: likely no additional Microsoft license. Microsoft only lists a Fabric capacity as a prerequisite; the documentation does not show separate costs for the add-on or the gateway. Check the current terms before starting the project. Whether SAP-side licensing questions (e.g. indirect use) are affected should be checked against your SAP contract.
- Datasphere or SAP Business Data Cloud: real new license costs, because extraction runs through SAP’s own paid services. This also applies to Mirroring for SAP Datasphere.
The technical conversion is usually inexpensive. The architecture decision is where the money goes. How the costs of a Fabric capacity add up is explained in our article Microsoft Fabric: Costs & Licensing.
Your Roadmap in Four Steps
- Take inventory. Run the self-assessment tool from SAP Note 3439624 or use the F6 view in Xtract, and record every ODP-RFC extraction from S/4HANA, BW and ECC.
- Map instead of converting across the board. Assign each extraction to the right component or path. OData is a fallback, not the first choice.
- Rebuild CDC paths. Move ADF SAP CDC jobs to the Copy job with ABAP Add-On, Mirroring for SAP Datasphere or an Open Mirroring partner solution.
- Use the opt-out deliberately. The time until the end of 2026 is meant for testing and parallel operation, not for postponing.
Frequently Asked Questions About SAP Note 3255746
What exactly does SAP Note 3255746 say?
The note prohibits customer and third-party applications from using the RFC modules of the ODP Data Replication API (ODP-RFC) to access SAP ABAP systems, both on-premises and in the private cloud.
Does this mean RFC is banned completely?
No. Table and CDS view extraction via RFC, DeltaQ, BAPIs and function modules are not affected.
Is the SAP CDC connector in Azure Data Factory affected?
Yes, it is based on ODP-RFC.
Is the SAP Table connector affected as well?
No, it does not use the ODP Data Replication API. Since it uses RFC_READ_TABLE depending on the configuration, SAP Note 382318 should be taken into account. The SAP OData connector is not affected either.
What Fabric alternatives are there?
Mirroring for SAP Datasphere (GA), Copy job for SAP via ABAP Add-On and Open Mirroring partner solutions, plus the announced SAP BDC Connect for Microsoft Fabric. None of these paths uses third-party ODP-RFC.
By when do I need to migrate?
The security update has been blocking calls since June 9, 2026. The opt-out ends at the end of 2026; no further exception is planned.
Do I have to switch to SAP Business Data Cloud?
No. BDC is SAP’s recommended platform for non-SAP systems accessing SAP data and is based on a zero-copy architecture with data products. Mirroring for SAP Datasphere and the Copy job with ABAP Add-On are not affected by SAP Note 3255746. Mirroring requires a Datasphere license, the Copy job, according to Microsoft, a Fabric capacity.
Are Qlik Replicate or other third-party tools affected too?
Yes, if their CDC is based on ODP-RFC. Qlik names, among others, the SAP ODP endpoint of Qlik Replicate and the ODP connectors of Talend as affected. The rule applies regardless of platform.
Bring SAP data into Fabric safely
Request a consultation
We are currently applying exactly this approach in several SAP-Fabric environments, turning an unsettling headline into a clear migration plan. Talk to Dennis Mausbach about your situation.
About the author: Yordan Ivanov is a Business Intelligence Expert at oneLake GmbH and supports SAP-to-Fabric migration projects in the DACH region: from the initial inventory of affected ODP-RFC extractions to the productive switch to Fabric-native alternatives.
Sources & further reading
- SAP Notes 3255746, 3439624, 3635619, 3731818 and 3748819: SAP for Me (login required)
- Microsoft Learn: SAP CDC in Azure Data Factory (note on 3255746 and alternatives)
- Microsoft Learn: Mirroring for SAP
- Microsoft Learn: Copy job for SAP via ABAP Add-On
- SAP News: SAP Business Data Cloud Connect for Microsoft Fabric
- Theobald Software: SAP Note 3255746 – How to Achieve Data Integration Without ODP-RFC
- Theobald HelpCenter: ODP Restriction Opt-Out until end of 2026
- Qlik: SAP ODP-RFC changes and affected connectors
- dab europe: SAP Notes 3255746, 382318 & 2971304: Impact & Solutions
- SAPinsider: The ODP-RFC Deadline in June 2026
- Microsoft Q&A: SAP CDC connector and Note 3255746
- E3 Magazine: Use of SAP Interfaces Prohibited
- SAP Community: SAP BDC Connect for Microsoft Fabric – GA?
Questions about your SAP data pipelines?
Get in touch via our contact form. We will get back to you shortly.
