Solutions ODP RFC exit

Move off ODP RFC before December 2026.

SAP Note 3255746 now ships as a patch that blocks third-party tools from pulling SAP data through the ODP RFC interface, and the temporary opt-out expires in December 2026. Lima Backbone extracts SAP data through the interfaces SAP keeps open to partners. A free one-week assessment tells you exactly which of your extraction jobs are affected and what replaces each one.

Counting to 31 December 2026.
JUN 9, 2026Patch shippedSAP Note 3255746 enforcementDEC 2026Opt-out expiresthird-party ODP RFC calls blockedDEC 31, 2027ECC mainstream maintenance endsS/4HANA programs and ECC retirementTODAYOPT-OUT WINDOW · ABOUT SIX MONTHSPIPELINES BUILT NOW CARRY ACROSS THE S/4HANA MOVE
Three dates, one plan: the patch is live, the opt-out ends in December 2026, and ECC mainstream maintenance ends a year later. Pipelines built now on open interfaces carry across the S/4HANA move.
Jun 9, 2026
the enforcement patch for Note 3255746 shipped
Dec 2026
the opt-out expires; third-party ODP RFC calls stop
Dec 31, 2027
ECC mainstream maintenance ends
~50%
of ECC-era customers expected to still be on ECC at the end of 2027
Panorama · Jul 2026
None
Lima extraction methods that use the ODP RFC interface
compliance statement · pending sign-off
1 week
free assessment: every extraction job inventoried by method
offer
What the note changes

In plain terms

ODP (Operational Data Provisioning) is the framework inside SAP that packages data for consumers such as BW. RFC (Remote Function Call) is the protocol many third-party integration tools used to call it. SAP declared that use unpermitted, and since June 2026 a patch enforces it. Until December 2026 a customer can opt out of the enforcement; after that, any extraction job that reaches SAP through ODP over RFC stops.

OPEN TO PARTNERSRESTRICTED BY SAP NOTESYour SAP systemECC 6.0 or S/4HANAthe same data behind every doorBasis grants the authorizationsTable reads · named function moduleopen · full or filtered · parallelBAPIs and released function modulesopen · reads and acknowledged writesCDS views (S/4HANA)open · delta-capableChange-data captureopen · timestamps, change pointers,triggersIDocsopen · documents in and outODP over RFC (third-party tools)Note 3255746 · patch since Jun 9, 2026opt-out ends Dec 2026RFC_READ_TABLE in productionNote 382318 · barredLog-based capture on HANANote 2971304 · unsupportedLima Backbone uses the open doorsevery method on this page

Interfaces SAP keeps open to partners

  • Table reads through a released or customer-approved function module (ECC and S/4HANA)
  • BAPIs and released function modules — reads and acknowledged writes
  • CDS views with delta capability (S/4HANA)
  • Change-data capture from timestamps, change pointers and triggers
  • IDocs for outbound documents and inbound postings

Interfaces the notes restrict

  • ODP over RFC used by third-party tools — Note 3255746, enforced since June 9, 2026
  • RFC_READ_TABLE for production use — Note 382318
  • Log-based capture on the HANA database by third-party tools — Note 2971304
  • The sanctioned SAP alternatives run through ODP over OData (slower for large volumes in practitioner reports) or through licensed replication services
Why this reaches beyond BW

Many connectors sold for SAP-to-cloud replication were built on the ODP RFC interface because it was convenient. The assessment looks at each of your jobs by the mechanism it uses, whatever tool runs it, and marks the ones that stop in December.

How Lima reads SAP

Every method Lima uses sits on the open list

The same methods work on ECC 6.0 and on S/4HANA, so pipelines you build now are the ones you keep after the migration.

MethodWhat it isLatencyDeletesSAP licence needed
Table reads named function moduleFull or filtered reads of transparent tables such as MARA, MARC, STPO, EKPO and VBAP, in parallelMinutes for full loadsFull compare or change logNone
BAPIs · function modulesBusiness-object reads and acknowledged writes — planned orders, purchase requisitions, material changesSecondsn/aNone
CDS views S/4HANASAP-defined views with built-in delta capabilityMinutesYes, on delta-enabled viewsNone
Change-data captureInserts, updates and deletes since the last run, from timestamps, change pointers or triggers1m 48s behind SAP in the showcase estateYesNone · SLT optional for log-based capture
IDocsOutbound documents and inbound postings in SAP's own document formatNear real timen/aNone
Method table for the public compliance statement; the named table-read function module and the signed statement are on the review list below.
The exit

Four weeks from assessment to cut-over

The assessment is free and takes a week. The conversion of your first ten extractions is a fixed-price engagement.

Week 0
free
Inventory and exposure reportEvery extraction job listed by source object, mechanism and downstream target. Jobs on ODP RFC are marked, and each one gets a named replacement method with its trade-offs stated.
Weeks 1–2
rebuild
First ten extractions rebuilt on open interfacesTable reads, CDS views or change-data capture, with counts reconciled against the old feed. Downstream targets stay exactly as they are.
Week 3
parallel run
Old and new side by sideBoth feeds run; record counts and control totals compared daily; variances routed to owners.
Week 4
cut-over
Cut-over with a reconciliation reportThe old jobs are switched off with the report as evidence. The remaining jobs follow the same pattern on a schedule you set.
What improves

You keep your targets and lose the deadline

Nothing downstream changes

Snowflake, Databricks, Fabric, planning systems and reporting databases receive the same tables at the same cadence; only the extraction path is new.

product
No new SAP licence line

Extraction runs on Lima's capacity through open interfaces, so there is no capacity-unit or replication-service subscription to add for getting data out.

product
Full and change-data loads, counts proved

Every run reports record counts and control totals against the source; exceptions go to an owner.

product
Built once for ECC and S/4HANA

The same methods run on both, so the pipelines carry across the migration and the ECC retirement that follows.

product
Predictable cost

A subscription sized by capacity tier. The bill stays the same whether you move a nightly delta or your full history.

pricing principles
The ECC clock runs at the same time

Half of ECC customers will still be on ECC at the end of 2027. Pipelines on open interfaces serve the planning program now and the decommissioning later.

Panorama · Jul 2026
Lifecycle

This page is about the first two stages; the rest of the lifecycle stays as it is.

One engine underneath every page in this family. It reads from any source and writes to any target, runs batch loads or change-data streams, handles a nightly delta or a multi-terabyte migration, and is licensed by capacity, so the bill stays the same however many rows move. Lima's fabric answers questions on data in place; Lima Backbone moves, transforms and returns data on a deadline. When to federate and when to pipeline · The Backbone hub.

Terms on this page

Plain definitions

ODPOperational Data Provisioning — SAP's framework for packaging and delivering data from an SAP system to a consumer.
RFCRemote Function Call — the protocol used to call functions inside SAP from outside. The note restricts one specific use of it: calling ODP through RFC from a third-party tool.
CDS viewCore Data Services view — an SAP-defined, delta-capable view of business data on S/4HANA.
Change-data capture (CDC)Reading only the rows that were inserted, updated or deleted since the last run.
Opt-outThe temporary setting that lets a customer keep third-party ODP RFC access working until December 2026.
Function moduleA unit of SAP code callable from outside; table reads in Lima go through a named, customer-approved one.
Questions we hear

Asked before the first load.

Is ODP over OData an option?

Yes, SAP supports it, and Lima uses it where it fits. Practitioner reports put it at roughly a tenth of the throughput of RFC-based extraction for large volumes, which is why Lima uses table reads, CDS views and change-data capture where volume matters.

Does Lima install anything in SAP?

There is no ABAP add-on. Lima connects through standard RFC authorizations, and where a customer-approved function module is used for table reads it ships as a transport your Basis team reviews.

What about jobs built on BW extractors?

Jobs that relied on extractors through ODP RFC are rebuilt on CDS views on S/4HANA, or on table reads with change-data capture on ECC and S/4HANA. Counts are compared against the old feed during the parallel run.

Our SAP connector comes from a cloud platform vendor.

Several widely used connectors are built on the ODP RFC interface. The assessment identifies the mechanism behind each of your jobs regardless of the tool that runs it.

Is Lima certified by SAP?

Lima is preparing its listing through SAP's partner program; the certification tier decision is scheduled for the fourth quarter of 2026 and will be stated here with its date.

Will the same pipelines work after we move to S/4HANA?

Yes. Table reads, BAPIs and change-data capture work on both, and CDS views are added on S/4HANA. The migration reuses the pipelines you build now.

Find out which of your extraction jobs stop in December

A free one-week assessment: every job inventoried by mechanism, exposure marked, a named replacement for each.