SAP Note 3255746 · ODP-RFC · opt-out until December 2026
Your SAP interface needs replacing? We build the new connection.
We replace your ODP-RFC connection with OData, CDS views or BAPIs, with source code, documentation and data reconciliation. SAP prohibits ODP-RFC for third-party and in-house applications. The June 2026 security update blocks these calls, and the temporary opt-out ends in December 2026. The SAP core remains unchanged.
What has changed at SAP
As of 3 November 2026
- SAP Note 3255746
- ODP-RFC is reserved for data exchange between SAP applications. Third-party and in-house applications must not use this interface.
- SAP Note 3748819
- The security update of 9 June 2026 blocks unpermitted ODP-RFC calls.
- Opt-out
- The temporary opt-out ends in December 2026. SAP Note 3731818 then enforces the block with no further exception.
- Still permitted
- Among others OData services, CDS views, BAPIs and SLT.
- SAP API Policy
- Published APIs may be used for their documented purpose. Each API has its own limits for bulk extraction and replication. AI systems that plan or execute API calls themselves are permitted only through SAP-endorsed architectures.
Where this typically shows up
- An ODP extraction fails with the message “Unknown caller; Call rejected”.
- A BI application or data warehouse no longer loads data from SAP.
- An AI application is meant to access SAP data.
- An in-house application outside SAP extracts data via ODP-RFC.
- A vendor reports that its ODP connector is no longer supported.
Which route fits which purpose
| Route | Suitable for |
|---|---|
| OData services | Standardised web interface for reading and writing, including OData-based data extraction |
| CDS views | Data models in the SAP system, exposed via OData, suitable for reporting |
| BAPIs | Released functions for business transactions, such as creating an order |
| SLT and table replication | Continuous replication of entire tables, including deltas |
What matters in the migration
Re-initialise the delta
A new route starts with a new delta initialisation. The takeover point is fixed in advance.
Align formats
OData returns some date and number formats, keys and field names differently. Downstream load processes are adapted accordingly.
Plan for throughput
OData transfers data much more slowly than RFC. Load windows and data volumes are therefore part of the planning.
Reconcile the result
Record counts, totals and samples per source show whether the new route delivers the same data.
What we implement, for example
Replacing existing interfaces
We move the connection to published SAP interfaces. Development usually runs against mock services for your SAP interfaces with test data. The new component runs outside your SAP system and provides the agreed data.
Connect SAP to a shop, warehouse or portal
Connection via released interfaces, tested with test data.
Data migration
Extraction from the legacy system, transformation into the target structure, reconciliation against expected values.
Reporting and exports outside SAP
Reporting via published interfaces, output format as you specify.
E-invoices from SAP data
ZUGFeRD and XRechnung from your invoice data. E-Invoicing
Interfaces to systems other than SAP: Software & Interfaces →
How the migration is measured
In our test environment, the old and new connection are compared using the same sample data. How the results are compared and verified in your test system, and by whom, is defined in the statement of work.
EXAMPLE · DATA WAREHOUSE WITHOUT ODP
What a project can look like
- Your input
- Metadata of the required CDS views, released by your SAP Basis team, sample data from the test system, list of the fields loaded so far.
- Result
- The data warehouse loads the agreed data via OData, reconciled with the existing data by record count and totals.
Illustrative example of a possible project.
Frequently asked questions
- What exactly has been blocked since June 2026?
- Access by third-party and in-house applications to the ODP Data Replication API over RFC.
- What happens when the opt-out ends?
- The opt-out ends in December 2026. SAP Note 3731818 then enforces the block with no further exception. The opt-out does not change the usage rules in Note 3255746.
- Which routes are still permitted?
- Among others OData services, CDS views, BAPIs and SLT.
- How can we tell whether our interface is affected?
- Useful indicators are the application’s configuration, transaction ODQMON and SAP Note 3439624. Otherwise we check this based on your information.
- Can existing RFC connections be replaced?
- Yes, if there is a released route for the same data. We check this before work begins.
- Does anything change in our SAP system?
- The SAP core remains unchanged (clean core). Any required configuration, such as activating OData services in SAP Gateway, is set out beforehand in the statement of work.
- Do you need access to our SAP system?
- Usually not. Your team usually carries out the checks in your test environment.
- Will there be additional SAP licence costs?
- That depends on your SAP contract. The statement of work lists every interface used, so you can check this in advance.
Sources: SAP Note 3255746 · SAP Note 3748819 · SAP Note 3731818 · SAP API Policy (as of April 2026)
How scope, testing and handover are handled: How we work →
Which SAP connection needs to change?
Tell us briefly which application extracts which data. I will get back to you within one business day.
Stephanie Escarciga · +49 15679 281048Mon–Fri, 7 a.m. to 6 p.m. (CET)