The extraction route that closes in December
A licensing rule is closing the most common route for copying data out. Every write-up of the change sells a replacement connector. This page is the neutral map: what is blocked, what is not, and which dates actually bind.
◆ What the note says, and when it bitesfour dates, one of them real.
SAP note 3255746 first appeared in October 2022 and said that ODP data replication over the RFC interface, feeding non-SAP targets, was unsupported. In February 2024 the wording hardened from unsupported to unpermitted. A rule now, not a warning.
With the June 9, 2026 patch cycle, SAP ships a technical block that switches the interface off. The block arrives only when a system applies those support packages; nothing is pushed to unpatched systems. And SAP allows a temporary re-enable after the block, which expires in December 2026. That expiry is the real deadline.
The re-enable is a named switch: report RODPS_REPL_SECUREACCESS_OPTOUT, run at your own risk, documented in note 3731818; the block itself ships in security note 3748819. Per the opt-out guidance, when the expiry lands SAP re-enforces the restriction with no further opt-out. The door closes once.
| Date | What happened |
|---|---|
| October 2022 | Note 3255746 published: ODP replication over RFC to non-SAP targets is unsupported. |
| February 2024 | Wording changed to unpermitted. Same mechanism, now a licensing rule. |
| April 2026 | Note reaches version 11: the prohibition stated across on-premises and private cloud landscapes, and the self-assessment note ships. |
| June 9, 2026 | Patch cycle ships the technical block. It lands only where those support packages are applied. |
| December 2026 | The temporary re-enable expires; the restriction is then re-enforced with no further opt-out. This is the date to plan against. |
◆ Blocked and not blockedone transport closes; the rest stay open.
The ban covers exactly one combination: ODP extraction carried over RFC, feeding a non-SAP target. It is a rule about the transport, not about extraction as an activity.
| Path | Status under the note |
|---|---|
| ODP over RFC to a non-SAP target | Blocked. This combination is the whole ban. |
| ODP over OData | Permitted. |
| CDS-view-based extraction | Permitted. |
| SLT replication | Permitted. |
| BAPI-based extraction | Permitted. |
The tools reading the blocked path are the mainstream replication products: the Azure Data Factory connector for SAP change data, Fivetran, Qlik Replicate, Talend, and Informatica pipelines built on ODP over RFC. Each vendor has published migration guidance, and each guidance ends at that vendor's product.
SAP’s own pitch in the current note version points at ODP over OData and its newer Business Data Cloud. Both are the vendor answering a licensing question with a product, which is exactly why the destination question below matters more than the connector question.
◆ The compliant route you ownassess first, then land the data on your ground.
SAP note 3439624 is the self-assessment, available since 13 April 2026: it tells you whether your own pipelines use the blocked interface, before any vendor conversation. Run it before you shop.
Then notice that the destination question matters more than the connector question. Every permitted path still ends somewhere, and the durable somewhere is a warehouse you own, fed by the extraction pattern this catalog documents. Move once, to your own ground, and the next transport rule change is a connector swap instead of a migration.
- SAP
- The vendor. Systems, Applications, and Products in data processing.
- HANA
- SAP’s in-memory database, the platform S/4 runs on.
- ERP
- Enterprise resource planning, the system of record for operations and finance.
- ODP
- Operational data provisioning, SAP’s framework for staging data for extraction.
- RFC
- Remote function call, SAP’s proprietary wire protocol. The transport the note closes.
- CDS
- Core data services, the view layer the newer extraction paths read.
- SLT
- SAP landscape transformation, the vendor’s trigger-based replication server.
- BAPI
- Business application programming interface, the older stable extraction interface.