SAP Note 3255746 says that the ODP framework’s RFC interface is for SAP’s own applications and that third-party use is prohibited; a patch shipped on June 9, 2026 now checks the caller and rejects third-party programs, and the temporary opt-out expires in December 2026 [1][2][3]. Every extraction tool that used this path has to change. The exit kit has three parts: a scanner that inventories your extraction jobs by method, a guide that says what replaces each one, and a fixed-price conversion of the first ten jobs with a reconciliation report.
SAP's wording (version 11, April 21, 2026): “Any use of ODP-RFC by customer or third-party applications to access SAP ABAP systems … is prohibited” [3]. The June 2026 patch adds a check on the calling program and rejects programs that are not SAP's own [2].
| Path | Status | What it means |
|---|---|---|
| ODP over RFC from a third-party tool | Blocked | Rejected by the caller check since June 9, 2026 unless the opt-out is active; the opt-out expires in December 2026 [1][2]. |
| ODP over OData | Permitted | The OData exposure of ODP remains available for authorised use; throughput is lower than RFC (practitioner reports; measure on your system). |
| Table reads through a released function module | Permitted | The method Lima uses for first loads and history. RFC_READ_TABLE itself is for test and development only (SAP Note 382318) [5]. |
| BAPIs and released function modules | Permitted | Reads and writes of business objects with SAP's logic applied; Lima's write-back path. |
| Released CDS views (S/4HANA) | Permitted | SAP-defined views released for extraction, some with delta handling. |
| Change pointers and extractor delta queues | Permitted | Application-layer change capture; Lima's incremental method. |
| Reading the HANA database log | Unsupported | SAP does not publish or certify an interface for it (SAP Note 2971304) [5]. |
| SAP Datasphere / Business Data Cloud; SLT | Licensed | SAP's own services, metered in capacity units or licensed separately; sanctioned, and a cost line of their own. |
The vendors below have published statements or documentation naming ODP RFC as the mechanism of specific products. The scanner finds the same thing on your system, whatever the tool.
| Tool | What the vendor says | Source |
|---|---|---|
| Qlik Talend Cloud SAP ODP Connector · Qlik Replicate SAP ODP endpoint · Qlik Analytics SAP ODP Connector · Talend Studio tSAPODPInput / tSAPADSOInput (RFC mode) | Named as affected in Qlik's support update of May 27, 2026; alternatives OData and SAP Extractors; a new SAP connector due later in 2026. | [4] |
| Other tools with ODP-based SAP connectors | Check the vendor's documentation for the word ODP and the transport mechanism (RFC or OData). The scanner reports the mechanism observed on your system. | vendor docs |
The scan runs with a read-only user and lists every extraction path on the system.
| What it inventories | How |
|---|---|
| ODP subscriptions | The delta queue monitor (ODQMON) lists every subscriber, its context and its last request. |
| RFC destinations and users | Which external programs connect, with which user, and which function groups they call. |
| Extraction jobs by method | ODP RFC, ODP OData, table reads, BAPIs, CDS views, extractor deltas, SLT. |
| Volumes and cadence | Rows and frequency per job, so the replacement can be sized. |
| What it reports | |
|---|---|
| Exposure | Every job that stops in December 2026, with its downstream consumers. |
| Replacement per job | The permitted method that replaces it and the trade-off (see part 2). |
| Effort bands | Per batch of ten jobs. |
| A date plan | Which jobs to convert first, given the consumers and the run windows. |
| Today | Replacement in Lima | Trade-off, stated plainly |
|---|---|---|
| ODP RFC on a standard extractor (2LIS_*, 0FI_*) | Extractor delta queue read through the released path, or the equivalent tables read through a released function module with change pointers. | A first full load is needed to re-seed the delta; the cadence stays the same. |
| ODP RFC on a CDS view (S/4HANA) | The released CDS view read directly, delta-enabled where SAP provides it. | Views not released for extraction are replaced by table reads of their underlying tables. |
| ODP RFC on an ADSO (BW) | Open Hub destination or active-table read where the licence allows. | Open Hub may need a licence; confirm with the account team. |
| ODP over OData (kept) | Kept where volume allows; otherwise table reads. | OData throughput is lower than RFC; measure it on your system before relying on it for large tables. |
| SLT or Datasphere replication (kept) | Kept where already licensed; Lima reads the replicated tables. | A licence cost that stays. |
| RFC_READ_TABLE in production | Table reads through a named released function module. | None on the SAP side; the compliance statement names the module. |
One week. The scan runs with a read-only user and returns the inventory, the exposure list, the replacement per job and a date plan. No charge.
Get the assessment →Fixed priceFour weeks at a fixed price: the ten most exposed jobs converted to permitted methods, run side by side with the old ones, reconciled per table, and cut over. Later batches priced the same way.
Offers and principles →Your SAP system stays as it is: nothing is installed, and the users and authorisations are the ones your Basis team grants for the released interfaces.
Your warehouse and your downstream tools keep receiving the same tables, on the same schedule, from the new path; the reconciliation report proves it per table.
Until the opt-out expires. The point of the scan is to know exactly which jobs stop then and to convert them in the order their consumers need.
It is permitted. Its throughput is lower than RFC, so it suits small and medium tables; large tables are better read through released function modules with change pointers. The scan sizes each job so you can choose.
No. Lima reads SAP through table reads via a released function module, BAPIs, released CDS views, change pointers and extractor delta queues, with nothing installed in SAP. The compliance statement names the interfaces.
No. The same tables land in the same targets on the same schedule; only the extraction method changes, and the reconciliation report proves the rows match.
The scan needs a read-only user and one week. You get the inventory and the date plan whatever you decide next.
