Irvine Analytics Get in touch
Analytics Catalog/SAP S/4HANA/Extraction ban decoder
Explore the catalogModulesExtraction patternNo history by designThe 10,000-row wallEnterprise model
SAP S/4HANA · Extraction · Reference · status August 2026

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.

RuleCheck your pipelines against the self-assessment note now. December 2026 is the date that binds, because the temporary re-enable expires then.
Neverrebuild everything in a panic because a vendor blog said so. Most extraction paths are untouched; one transport is closing.
◆ 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.

Published October 2022 Unpermitted February 2024 Block ships June 2026 patches Fallback ends December 2026
Four dates, one that matters for planning. The table below carries the detail.
DateWhat happened
October 2022Note 3255746 published: ODP replication over RFC to non-SAP targets is unsupported.
February 2024Wording changed to unpermitted. Same mechanism, now a licensing rule.
June 9, 2026Patch cycle ships the technical block. It lands only where those support packages are applied.
December 2026The temporary re-enable expires. 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.

PathStatus under the note
ODP over RFC to a non-SAP targetBlocked. This combination is the whole ban.
ODP over ODataPermitted.
CDS-view-based extractionPermitted.
SLT replicationPermitted.
BAPI-based extractionPermitted.
Operational Data Hub pathsPermitted.

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.

◆ The compliant route you ownassess first, then land the data on your ground.

SAP note 3439624 is the self-assessment: 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.

Use case
Problem
A licensing note is closing ODP extraction over RFC for non-SAP targets, and every write-up of the change is a sales page for a connector.
What we build
A neutral assessment of your pipelines against notes 3255746 and 3439624, then a compliant extraction path landing in a warehouse you own.
What you get
A clear map of which pipelines are affected, the date that binds, and a route where the next vendor rule change is not a migration.
Which of your pipelines are on the closing route?
We assess them against the note and land the compliant path in your warehouse.
Talk to us
Terms on this page
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.